Mapping the future state before buying it.
The Maricopa Association of Governments is the regional planning agency for the Phoenix metropolitan area. Its ERP upgrade began with a review of what the current system actually did.
You cannot specify a future state you have not drawn.
MAG initiated a project to upgrade its Enterprise Resource Planning system to improve operational efficiency and data management.
The work began with a detailed review of the existing ERP — workflows, processes, functional components, related applications, and integrations — rather than with a market scan.
From that review, Avèro produced Business Process Modeling and Notation diagrams of the optimized future state, giving the agency a drawn target instead of a described one.
The deliverables.
Current-state review
A detailed review of the existing ERP covering workflows, processes, functional components, related applications, and integrations — establishing what is actually in use before anything is specified.
Future-state process modeling
BPMN diagrams visualizing optimized future-state workflows. A diagram can be argued with and corrected; a paragraph of requirements usually cannot.
Data flow mapping
Mapping how data moves between components, which is where most ERP upgrades discover their real constraints.
Upgrade management
Ongoing management and strategic planning through the upgrade, with the future-state workflows and data flow maps serving as the reference the work is held to.
Status and outlook.
Where it stands
The upgrade is in progress, with the future-state workflows and data flow maps guiding it.
Why modeling first
The diagrams outlive the project. They remain the agency's description of how it intends to work, independent of which product implements it.
Related engagements.
Every engagement is reference-available. Ask us to connect you with the people who hired us.
Thirty minutes.
No pitch.
Tell us where you are. We'll say honestly whether we can help. If we can't, we'll point you to someone who can.