Choose the relevant areas
Explore logistics, supply, manufacturing, people, customers and financial operations as distinct systems.
Monument
MONUMENT SUITE · IN DEVELOPMENT
One foundation.
Your choice
of modules.
A modular ERP suite for the connected work of a business. Choose the systems you need, with a shared foundation that brings people, data and operations together.
In development · Release details to comeINDEPENDENT SYSTEMS. A SHARED CORE.
Built to connect
the work between departments.
A warehouse movement, a purchase and a customer order belong to different workflows, but they share a business context. Monument is being built as independent systems that use one platform core, so each area can develop without losing that connection.
People & accessShared identity and business access.
Business contextA common organization and tenancy foundation.
Master dataShared items, locations and business partners.
Connected activityEvents that carry relevant changes between systems.
A SUITE THAT FITS THE WORK
Start with the systems
your organization needs.
Build a deliberate mix
Select modules and consider tier choices individually, rather than applying one tier across the whole suite.
Keep the broader picture
Use a shared foundation to connect neighboring workflows as the suite develops.
THE MONUMENT MODULE DIRECTORY
Explore each part
of the foundation.
Open a module to see its intended focus, the teams it serves and an example of the work it connects.
Inventory & Logistics
See the work inside each module.
Open a module to see its desktop workspace and, where relevant, an Android RF task view. Tap a screenshot to enlarge it.
Interface concepts use fictional records to illustrate the planned desktop and RF experience. The nine documented business modules are in development; the six planned modules show a proposed experience. Android RF views illustrate scanner workflows; device integration is not demonstrated.
Warehouse ManagementIn development · Interface preview
THE INTERFACE
Warehouse Management · Desktop
Follow assigned picks by item, quantity and location. Receiving, packing, loading and counting stay connected to warehouse records.
Interface concept · Fictional data · In developmentVerify the pick location
Aisle, bay, level and position give the worker a precise destination.
Interface concept · Fictional data · In developmentCheck incoming goods
Match the item to the expected receipt before recording the quantity.
Interface concept · Fictional data · In developmentRecord a blind stock count
Record the physical quantity without displaying an expected count.
Interface concept · Fictional data · In developmentVerify a package for loading
Check that the package belongs to the warehouse shipment and assigned trailer.
Interface concept · Fictional data · In developmentWarehouse teams coordinating inventory and the movement of goods.
From arrival to dispatch.
Receiving and storage
Record the incoming delivery and any quantity differences.
Stock visibility
Place accepted goods into the appropriate storage locations.
Picking and dispatch
Prepare the available stock for picking and dispatch.
A workflow to consider: A distributor receives a delivery needed for several customer orders.
- Record the incoming delivery and any quantity differences.
- Place accepted goods into the appropriate storage locations.
- Prepare the available stock for picking and dispatch.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Yard ManagementIn development · Interface preview
THE INTERFACE
Yard Management · Desktop
See trailer positions and door availability, then verify the assigned trailer before confirming a yard movement.
Interface concept · Fictional data · In developmentVerify the trailer
Identify the trailer before recording its destination.
Interface concept · Fictional data · In developmentTeams coordinating trailers, yard locations, and dock activity.
Bring the yard into view.
Arrival and departure
Record the trailer arrival.
Yard placement
Identify a waiting location and coordinate its move to a dock.
Dock coordination
Record the departure after loading or unloading.
A workflow to consider: A trailer arrives before its assigned dock is available.
- Record the trailer arrival.
- Identify a waiting location and coordinate its move to a dock.
- Record the departure after loading or unloading.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Transportation ManagementIn development · Interface preview
THE INTERFACE
Transportation Management · Desktop
Review booked consignments, transport modes, journey milestones and delivery windows alongside the warehouse shipment.
Interface concept · Fictional data · In developmentDispatchers and logistics teams coordinating shipments.
Keep the delivery journey connected.
Shipment coordination
Review the shipments ready for transport.
Dispatch planning
Organize their dispatch and delivery requirements.
Delivery progress
Follow progress and record exceptions for follow-up.
A workflow to consider: Several outgoing orders need to reach customers on different schedules.
- Review the shipments ready for transport.
- Organize their dispatch and delivery requirements.
- Follow progress and record exceptions for follow-up.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Supply & Operations
Procurement ManagementIn development · Interface preview
THE INTERFACE
Procurement · Desktop
Review requisitions with quantities, need dates, estimated values and approval context before the next purchasing step.
Interface concept · Fictional data · In developmentBuyers and teams responsible for business purchasing.
Give purchasing a clear path.
Purchasing needs
Capture the purchasing requirement.
Supplier and order records
Review the supplier and purchase order details.
Receipt coordination
Coordinate receipt and resolve any differences.
A workflow to consider: A team needs to replenish an important operating supply.
- Capture the purchasing requirement.
- Review the supplier and purchase order details.
- Coordinate receipt and resolve any differences.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Supply Chain ManagementIn development · Interface preview
THE INTERFACE
Supply Chain Management · Desktop
Connect shortages to affected demand, planning runs and proposals to buy, make or transfer supply.
Interface concept · Fictional data · In developmentTeams coordinating supply across suppliers, inventory, and demand.
See the connections behind supply.
Supply visibility
Identify the affected supply and commitments.
Operational dependencies
Review the operational impact with the relevant teams.
Exception follow-up
Coordinate a response and track the exception.
A workflow to consider: A supplier delay affects stock needed for upcoming commitments.
- Identify the affected supply and commitments.
- Review the operational impact with the relevant teams.
- Coordinate a response and track the exception.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Demand Planning & ForecastingIn development · Interface preview
THE INTERFACE
Demand Planning & Forecasting · Desktop
Compare consensus and baseline forecasts, review changes, and use history and accuracy analysis to refine the demand plan.
Interface concept · Fictional data · In developmentPlanning teams considering future demand and supply requirements.
Prepare for what comes next.
Demand patterns
Review the demand pattern and relevant assumptions.
Planning assumptions
Develop a forecast for the upcoming period.
Forecast review
Compare actual demand with the plan and revise the outlook.
A workflow to consider: A business prepares for a recurring seasonal increase in demand.
- Review the demand pattern and relevant assumptions.
- Develop a forecast for the upcoming period.
- Compare actual demand with the plan and revise the outlook.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Manufacturing ExecutionIn development · Interface preview
THE INTERFACE
Manufacturing Execution · Desktop
Guide floor workers through operations, work instructions, materials and output recording, with batch records and scheduling available for deeper work.
Interface concept · Fictional data · In developmentVerify the work center
Verify the station before opening the operation instructions.
Interface concept · Fictional data · In developmentProduction teams coordinating work orders, materials and execution.
Connect the plan with work on the floor.
Work orders
Review the work order and the materials needed.
Materials and work in progress
Coordinate execution and record progress on the floor.
Execution follow-up
Follow exceptions and completed work into the next step.
A workflow to consider: A production team begins a scheduled work order with materials and resources to coordinate.
- Review the work order and the materials needed.
- Coordinate execution and record progress on the floor.
- Follow exceptions and completed work into the next step.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓People & Relationships
Human Resources ManagementIn development · Interface preview
THE INTERFACE
Human Resources · Desktop
Give workers their shift, time and leave context while keeping restricted HR information under separate access controls.
Interface concept · Fictional data · In developmentHR teams and managers coordinating employee information and processes.
Bring people processes together.
Employee information
Organize the employee information needed for onboarding.
People workflows
Coordinate the relevant tasks and responsibilities.
Organizational coordination
Review outstanding items with the responsible teams.
A workflow to consider: A new employee is joining a team.
- Organize the employee information needed for onboarding.
- Coordinate the relevant tasks and responsibilities.
- Review outstanding items with the responsible teams.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Order ManagementIn development · Interface preview
THE INTERFACE
Order Management · Desktop
Keep sales-order acceptance, promised dates and warehouse fulfillment progress in view, with customer, pricing and credit context nearby.
Interface concept · Fictional data · In developmentTeams coordinating customer orders and fulfillment.
Follow the commitment to the customer.
Order information
Capture and review the order details.
Fulfillment progress
Coordinate availability and fulfillment requirements.
Order exceptions
Follow the order through completion and resolve exceptions.
A workflow to consider: A customer places an order with several lines and a requested delivery date.
- Capture and review the order details.
- Coordinate availability and fulfillment requirements.
- Follow the order through completion and resolve exceptions.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Customer Relationship ManagementPlanned module · Interface preview
PLANNED EXPERIENCE
Customer Relationship Management · Desktop
The planned experience connects customer follow-ups with order and delivery context.
Planned module · Design conceptSales and customer-facing teams managing business relationships.
Keep customer context close.
Customer information
Capture the customer context and conversation notes.
Relationship activity
Coordinate the next action and its owner.
Follow-up coordination
Carry the relevant context forward as the relationship develops.
A workflow to consider: A prospective customer needs a follow-up after an initial conversation.
- Capture the customer context and conversation notes.
- Coordinate the next action and its owner.
- Carry the relevant context forward as the relationship develops.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Finance & Performance
Financial ManagementPlanned module · Interface preview
PLANNED EXPERIENCE
Financial Management · Desktop
The planned invoice-review experience brings purchasing, receipt and approval evidence together.
Planned module · Design conceptFinance teams managing business financial records and review.
Put operational activity in financial context.
Financial records
Review the purchase, receipt, and related financial information.
Operational transactions
Identify discrepancies that need resolution.
Financial review
Include the reconciled activity in the financial review.
A workflow to consider: A received purchase needs to be reviewed against its financial records.
- Review the purchase, receipt, and related financial information.
- Identify discrepancies that need resolution.
- Include the reconciled activity in the financial review.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Enterprise Performance ManagementPlanned module · Interface preview
PLANNED EXPERIENCE
Enterprise Performance Management · Desktop
The planned overview compares operational results with targets and connects variances to underlying work.
Planned module · Design conceptLeadership and planning teams reviewing business performance.
Connect plans with performance.
Business plans
Define the plan and the measures being reviewed.
Performance measures
Compare results with the expected performance.
Variance review
Investigate differences and agree on next actions.
A workflow to consider: A team reviews results against its quarterly operating plan.
- Define the plan and the measures being reviewed.
- Compare results with the expected performance.
- Investigate differences and agree on next actions.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Projects, Assets & Quality
Quality ManagementPlanned module · Interface preview
PLANNED EXPERIENCE
Quality Management · Desktop
The planned inspection experience shows the source record, sample checks and disposition.
Planned module · Design conceptRecord each sample check
Future concept: an explicit inspection checklist and an issue path for failures.
Planned module · Design conceptQuality teams coordinating checks, exceptions, and follow-up.
Keep quality issues in focus.
Quality checks
Record the inspection outcome and affected batch.
Issue records
Coordinate the handling of the issue.
Corrective follow-up
Follow the corrective action and review the outcome.
A workflow to consider: An incoming batch does not meet an inspection requirement.
- Record the inspection outcome and affected batch.
- Coordinate the handling of the issue.
- Follow the corrective action and review the outcome.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Equipment ManagementPlanned module · Interface preview
PLANNED EXPERIENCE
Equipment Management · Desktop
The planned service experience pairs equipment records with approved maintenance instructions and history.
Planned module · Design conceptIdentify the equipment
Future concept: equipment identification before the approved job procedure.
Planned module · Design conceptTeams responsible for equipment records and upkeep.
Keep equipment and its work connected.
Equipment information
Review the equipment record and upcoming maintenance need.
Maintenance coordination
Coordinate the work with the responsible team.
Activity history
Record the activity and any follow-up requirements.
A workflow to consider: A frequently used piece of equipment needs scheduled attention.
- Review the equipment record and upcoming maintenance need.
- Coordinate the work with the responsible team.
- Record the activity and any follow-up requirements.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Project Management SystemPlanned module · Interface preview
PLANNED EXPERIENCE
Project Management · Desktop
The planned project workspace shows assigned tasks, dependencies and milestones alongside related operational records.
Planned module · Design conceptTeams coordinating project responsibilities and delivery.
Give shared work a clear structure.
Project milestones
Organize the milestones and responsibilities.
Responsibilities
Review progress and outstanding dependencies.
Progress review
Coordinate follow-up as the project moves toward completion.
A workflow to consider: Several teams are contributing to a customer implementation.
- Organize the milestones and responsibilities.
- Review progress and outstanding dependencies.
- Coordinate follow-up as the project moves toward completion.
Illustrative workflow. Release capabilities and tier differences will be confirmed during development.
Include this area in your configuration ↓Monument remains in development. These descriptions explain the suite’s scope and intended workflows; public availability will be announced separately.
BUILT AROUND THE PERSON DOING THE WORK
Simple tasks.
Room for deeper decisions.
Workers start with the next action. Supervisors see exceptions and approvals. Authorized users find General, Supervisor, Admin and Maintenance together in the left sidebar; sections without access stay out of view.
A clear starting point
A personal work queue helps workers find their next task across modules.
Interface concept · Fictional data · In developmentSupervisor decisions
Shift workload, assigned owners and exceptions stay together.
Interface concept · Fictional data · In developmentAdmin access
Keep module access, decision authority and approval-routing groups distinct.
Interface concept · Fictional data · In developmentMaintenance · Items
Maintain shared item definitions without changing transaction history.
Interface concept · Fictional data · In developmentMaintenance · Locations
Use Aisle → Bay → Level → Position. The client independently chooses letters or numbers for each level; bays can be racks or groups of positions, and positions can be bins, pallet spaces or other storage spaces.
Interface concept · Fictional data · In developmentMaintenance · Workstations
Maintain MES work centers, their type, capacity and operational availability.
Interface concept · Fictional data · In developmentRole and access screens show the proposed interface. Maintenance manages definitions such as Items, Locations and Workstations; physical equipment servicing belongs to Equipment Management.
YOUR MODULE MIX
Choose a starting point.
Select the areas you want to discuss. Choose Basic, Standard, Advanced or Enterprise for each eligible module; Yard Management scales by site allowances rather than a feature ladder. This explorer prepares an inquiry without creating an account or purchase.
SEE THE CONNECTIONS
The work does not
stop at a department boundary.
Plan demand
Consider the demand and supply assumptions behind upcoming work.
Coordinate supply
Connect purchasing requirements with suppliers, availability and receiving.
Execute the work
Follow the materials, movements and operational activity involved.
Review the outcome
Bring quality, customer and financial context into the next decision.
An illustrative cross-module sequence. Integration behavior will depend on the released modules and configuration.
ABOUT THE SUITE
Plan with a clearer view.
Is Monument available to purchase?
Monument is in development. Contact Aurvandil to discuss the suite, its intended scope and future release availability.
Do I have to use every module?
The suite is designed around independent but integrated systems. Start by identifying the operational areas relevant to your business.
Can different modules use different tiers?
The configuration model lets you consider Basic, Standard, Advanced or Enterprise independently across eligible modules. Yard Management scales by site allowances rather than a feature ladder. Final feature allocations and pricing will be confirmed separately.
What does the configuration explorer do?
It creates a summary of the modules and tiers you select and puts that summary into an email inquiry. It does not provision software, charge you or send an email automatically.
Where do I find Monument on the Aurvandil site?
Monument has its own top-level navigation tab and dedicated suite page. It is no longer listed in the Business solution or the general Products catalog.
MONUMENT SUITE · BY AURVANDIL
Build around
the work ahead.
Tell us about the systems your organization needs and the connections that matter.