Getting Started with WisdomX Orbis
This guide walks you through getting from first login to your first reviewed decommissioning candidates. Most organisations have a working estate map and their first candidate list within two weeks of connecting their first data source.
Before You Begin
Before your first session, it helps to have:
- Access credentials for your primary data sources — your CMDB, Azure or AWS console, or existing asset registers are the best starting points
- A named internal owner for the programme — one person who will lead the initial review
- Clarity on your estate scope — which systems, business units, or environments you want to start with. You can always expand later.
You do not need a complete inventory before you start. Orbis will discover systems as it ingests data from your connected sources. Discovery is part of the process.
Step 1 — Connect Your Data Sources
Navigate to Connectors in the left sidebar. Select Add Connector and choose your system type. Follow the authentication steps. Most connectors use OAuth or API key. Set sync frequency to daily and run an initial sync.
Supported connectors include Microsoft Azure, ServiceNow CMDB, Splunk, AWS, SAP, and manual CSV upload for organisations without a CMDB.
Once your first sync completes, systems begin appearing in your estate map within minutes.
Step 2 — Review Your Estate
Once your first sync is complete, open the Asset Management module and review what Orbis has discovered.
Check that the systems you expected are present. Note any systems you do not recognise. These may be shadow IT or undocumented assets worth investigating. Review whether the lifecycle status assigned to each system (Active, Redundant, Obsolete, Idle) looks accurate, and correct any that do not.
You do not need a perfect estate map to start generating value. A good-enough starting picture is sufficient to surface your first decommissioning candidates.
Step 3 — Understand Your Risk Profile
Open the Risk and Compliance Overview on the dashboard. Review the number of systems carrying compliance issues, security risks, and operational risk.
Click View Risk Analysis to see the full breakdown by system. This tells you which systems are carrying the most risk and should be prioritised, either for remediation or for accelerated decommissioning.
Check the System Dependency Map for any high-risk systems. Understanding what each system connects to is essential context before making any decommissioning decision.
Step 4 — Review Decommissioning Candidates
Open the Decommissions Data Insights table. Orbis will have populated this with systems it has identified as candidates based on their lifecycle status, cost, and risk profile.
For each candidate, review:
- The status — Obsolete, Redundant, or Idle
- The annual cost — what it is currently costing to keep this system running
- The risk level — High, Medium, or Low
- The recommendation — Decommission, Review, or Archive
- The dependency map — check this before approving any closure
If a system is marked Review, it means Orbis needs more data or the dependency picture is incomplete. Investigate before making a decision.
If a system is marked Archive, it should be preserved in cold storage rather than deleted, typically for compliance, legal hold, or reference purposes. Snapshot handles this in the same way as a decommission.
Step 5 — Approve and Initiate Snapshot
When your team is ready to approve a decommission, click the Action menu on the system row and select the decision. This opens the decision flow where you confirm the approval.
On approval, the Snapshot process is initiated automatically. Snapshot captures a complete archive of the system (context, code, data, and documents) into cold storage before anything is closed. You will receive confirmation when the archive is complete.
The system status updates to Decommissioned in your Lifecycle Progress dashboard. Your potential savings figure updates to reflect the cost now being recovered.
Nothing is deleted until the Snapshot archive is confirmed complete. Your team can review the archive at any point before finalising closure.
Typical Timelines
| Milestone | Typical timeframe |
|---|---|
| First connector live and syncing | Day 1 |
| Initial estate map generated | Day 1–3 |
| First candidate list in Data Insights | Day 3–7 |
| First system reviewed and approved | Week 2–4 |
| Snapshot archive complete | Within 48 hours of approval |
| Programme at scale | Month 2–3 |
Getting Support
- In-platform: click the ? icon in the top right corner from any screen
- Email: support@wisdomx.uk
- Diagnostic Engagement: our team works alongside yours for the first 90 days, connecting data sources, reviewing your estate, and identifying your highest-value candidates together
For enterprise accounts, a dedicated Customer Success Manager is assigned from Day 1.