A map of your company, with live state on every step
The Atlas is a view of the system by process rather than by module. It shows the value chains a company actually runs on — opportunity to cash, need to payment, plan to delivery, document to report — and on every node it shows what is happening there right now.
- 4 value chains
- 8 end-to-end processes
- Crossings on shared nodes
- Live state per node
A company is not a linear process
Which is why the Atlas is neither one chain of arrows nor a radial drawing with the product in the middle.
The usual process map in an ERP pitch runs left to right: sales, then procurement, then production, then finance. That picture is tidy and wrong. Procurement does not always follow sales — MRP raises it from the production plan. Production does not always follow stock. Service does not hang off sales: a customer's report starts on its own. A company runs several chains in parallel, and a map that hides this teaches the reader the wrong model of their own business.
So the Atlas shows four parallel chains rather than one. They cross on the nodes they genuinely share: a supplier receipt, finished goods from the floor and a delivery to a customer all move the same stock balance — three chains, one availability figure, which is precisely why a customer reservation can see material still in transit. A crossing is a fact from the data model, not a line the illustrator added to make the picture look connected.
The practical value of the Atlas is not that it looks good on a wall. When someone asks where the time goes, the answer is not inside a module but between modules — at the handover where a delivery note becomes an invoice, or where an invoice waits for approval. The Atlas is the only screen where those handovers appear as handovers rather than as two separate lists.
Three views of one system
The Atlas is not one screen but three levels of insight over the same data. They differ by the question they answer, not by what they show.
The company map
Four value chains side by side, with crossings on the shared nodes. It answers how the company works as a whole — and where one chain depends on another. This is the view for whoever decides, not for whoever enters data.
End-to-end business flows
Eight end-to-end processes, each a sequence of steps from start to outcome: Lead-to-Cash, Procure-to-Pay, Plan-to-Fulfill, Record-to-Report, Hire-to-Retire, Case-to-Resolution, Project-to-Cash and Acquire-to-Retire. It answers what happens between two documents.
My role
The same flows, reduced to the steps that are yours. It answers what is waiting for you today and where your step feeds someone else's. This is the view a user opens in the morning, and it shows work rather than a map.
The company map
The four chains a company runs in parallel. A cyan thread marks a step the system handles on its own; a footnote on a node leads to the chain it crosses.
Revenue
Lead-to-Cash
Opportunity
7 opportunities in negotiation
Quote
12 quotes awaiting a reply
Order
9 orders ready to ship
Delivery1
3 picking tasks are late
Invoice2
18 invoices raised from delivery notes with no entry
automatedCollection
average collection 37 days
automated
Procurement
Procure-to-Pay
Requisition
14 purchase proposals from stock minimums
automatedApproval
6 approvals awaiting a decision
Purchase order
23 purchase orders open
Goods receipt1
4 shipments arrive today
Invoice2
93% of invoices matched automatically
automatedPayment
31 payment orders prepared by due date
automated
Operations
Plan-to-Fulfill
Plan
demand plan confirmed for 6 weeks
Material sourcing
MRP proposed 17 purchase orders
automatedProduction
8 work orders on the floor
Quality
2 lots in quarantine
Stock1
41 items below minimum
Delivery1
3 picking tasks are late
Finance
Record-to-Report
Document2
47 inbound documents read and proposed for posting
automatedPosting
47 documents posted with no manual entry
automatedControls
83% of the bank statement matched
automatedClose
2 checks open before period close
Reporting
VAT return ready 4 days before the deadline
Employees, working time, absences and Serbian payroll — in the core of the system, not in a separate program next to it.
One document kernel, one approval path and one decision trail — underneath every document in the system.
The command center for decisions — evidence behind every insight, a trail behind every automation.
StockProcurement · Operations · Revenue
A supplier receipt, finished goods from the floor and a delivery to a customer all move the same balance. Three chains, one availability figure — which is why a customer reservation can see material still in transit.
- ProcurementGoods receipt
- OperationsStock
- RevenueDelivery
InvoiceRevenue · Procurement · Finance
The outgoing invoice from sales and the incoming invoice from procurement are different documents, yet they enter the same journal and the same tax records. Record-to-Report picks both up as a single stream.
- RevenueInvoice
- ProcurementInvoice
- FinanceDocument
The four chains of the company map are shown here. The remaining four end-to-end processes — people, support, projects and fixed assets — run through them and appear in the business-flow view.
Live state is the point, not the decoration
A process map that does not know what is happening on it is a slide. The Atlas reads the real state of the system on every node.
Each step carries a number: how many quotes await a reply, how many shipments arrive today, how many items are below minimum, what share of invoices the system matched. These are not illustrations of a process but figures from the same tables the work runs on — no nightly transfer, no second version of the number. Clicking a node leads into the space that step belongs to, onto the list the figure came from.
That is what makes the Atlas navigation rather than documentation. When the 'Approval' node reads six, that is not a description of a flow but six decisions someone has to make today — and the path to them is one click, not a hunt through a menu.
The same holds for the automated share: it is not a grade for the system but the state of your rules. If a node reads that 93% of purchase invoices matched without a person, the remaining 7% is not a fault but work that is waiting — and the Atlas shows it in the same place, instead of showing only the success.
See the Atlas on your own flows
Tell us how the path from quote to collection runs in your company today and we will show where the map makes the delay visible — on your steps and your handovers, not on a demo chain that always flows smoothly.