Migration order
- Most consequential system: Legacy ERP module (stops 4 items).
- For this scenario: none stops none.
AutoDiscover
One model of the organisation
Each tool keeps its own idea of who, what and which system, so they disagree.
Demonstration: Marlowe Textiles Ltd (fictional) · Manufacturing and export. Fictional data and a scripted answer.
The situation
- Organisation
- Marlowe Textiles Ltd (fictional)
- Who is asking
- Enterprise architect
- Industry
- Manufacturing and export
- What happened
- The company will retire an old ERP module next year and wants to know which business entities depend on it for their only source.
The question asked
If a source system is retired, which parts of our business model lose their data?
What it reads, and who can see the result
- Discovered source systems registerSystems found and the entities each one holds.
- Entity mappings registerWhich source feeds which entity.
- Reads
- The system list and the mapping of systems to entities.
- Does not read
- The records in the systems.
- Permission
- Enterprise architecture access.
- Who sees it
- The enterprise architect and the business owners of each entity.
Try it
Fail one or more items and see what stops and what only degrades, worked out by following the dependencies.
Choose what is retired. Hard dependencies stop with it; soft ones carry on, degraded.
- Scheduled for retirement.
- Modern, supported.
- Modern, supported.
- Master record in the customer system.Depends on: Customer system (hard)
- Only in the legacy ERP.Depends on: Legacy ERP module (hard)
- Held in the legacy ERP; contacts copied to the customer system.Depends on: Legacy ERP module (hard), Customer system (soft)
- HR system.Depends on: HR system (hard)
- Needs products and customers.Depends on: Product and bill of materials (hard), Customer (hard)
- Needs suppliers.Depends on: Supplier (hard)
- Needs employees and production orders.Depends on: Employee (hard), Production order (soft)
- is retired
- 0
- Stops as a result
- 0
- Degraded
- 0
- Unaffected
- 10
The answer
Simulated answer. Written for this fictional case, not produced by a live model. Only the figures in it are computed, from what you decided above.
Retiring none stops 0 item(s) and degrades 0.
Following the mappings, none stops none and degrades none [S1][S2]. The most consequential system in this map is Legacy ERP module, whose retirement stops 4 other item(s).
A knowledge model of the organisation is what lets such a question be answered before the retirement, not after. The only-source entities (here, products) need a new home first.
Relies on: S1 · Discovered systemsS2 · Entity to source mapping
Review and approval
The enterprise architect decides. Approving fixes the migration order for the retirement plan. It does not move any data or switch off any system.
Not ready to approve. Fail at least one item first, to see what depends on it.
In the product this is a different person with the right permission. Here you play that role to see the rule.
What it produces
Limits of this example
- Depends on the mappings being complete; an undiscovered feed is not shown.
- Shows consequence, not effort or cost of migration.
- This is a scripted demonstration on fictional data. No model was called and no real organisation, person or result is shown.
More in AutoDiscover
- AutoDiscover from a folder you approveNobody has time to organise years of files before they can benefit from any tool.
- Understand a database, read onlyBusiness data lives in systems whose structure only a few people understand.
- The ways your information can reach the platformOrganisations differ in what they will share, with whom, and how.
The AutoDiscover story · This capability in the full register