Set the boundary
Choose the service, platform, site group, or problem. Confirm the sources, owners, and first useful outcome.
IOM Onboarding
One Environment. One Working Model. Thirty Days.
The first 30 days turn one meaningful part of your environment into a working infrastructure model. We begin read-only, use the evidence you already have, and prove a useful operating result before adding any write path.
Week by Week
What happens, in what order.
Connect the evidence
Use read-only APIs, exports, code, records, diagrams, and working knowledge from the people who know the environment.
Build and check the IOM
Map facts, relationships, owners, current state, initial rules, gaps, and drift. Review the model with the team.
Prove the first outcome
Use the IOM for current documents, impact, incident context, change checks, or another agreed result. Set the next plan.
A Good First Scope
Important enough to matter. Small enough to finish.
Meaningful
The environment supports a real service, risk, cost, or change need.
Hard to understand today
The facts, relationships, owners, or current state are spread across systems and people.
Representative
The scope includes common patterns that can guide later expansion.
The first scope is not the whole estate. It is the best place to prove the operating model.
What You Have at Day 30
A usable operating model—not another assessment report.
A synchronized first IOM
The agreed facts, relationships, owners, current state, and initial rules for the scope.
Current operating views
Dependencies, ownership, gaps, drift, impact, and documents drawn from the IOM.
An ongoing operating plan
The cadence, operating model, expansion order, and next connected change paths.
What Thirty Days Means
A working infrastructure model in 30 days does not mean autonomous control in 30 days.
Read-only understanding
The first IOM is built, checked with the team, and used to prove one practical operating outcome.
8–16 weeks to first production gating
When the customer chooses to enable one selected connected change path. Timing depends on access, rules, approvals, and testing.
Authority is not the starting point. A trusted IOM is.
What Comes Next
Expand in the order that creates the most value.
Widen the IOM
Add services, sites, platforms, domains, providers, owners, and rules.
Deepen daily use
Use the IOM for incidents, change impact, current documents, drift, and risk.
Add governed paths
Validate, gate, apply, and verify selected changes at the pace you approve.
What We Need
Use the evidence you already have.
The first build can start with exports and documents or with read-only connections. We use the least access needed for the agreed result.
- Infrastructure and cloud exports
- Infrastructure as Code and Git
- CMDB, ITSM, IPAM, or asset records
- Monitoring and security evidence
- Diagrams, spreadsheets, and documents
- Time with the people who know the exceptions
It all starts with the model.
Start at the Whiteboard
Choose the first environment before anything connects.
The working session defines the boundary, the evidence, the first result, and the people who need to be involved.