Solutions

INOVIVO Transform makes your enterprise legible.

Every programme starts somewhere different. Each needs the same first step: a clear view of the organisation it's changing.

The 5D Method™ DiscoverDesignDeployDeliverDrive

Modernising a live site

The airport can't close while you change it. Every upgrade touches systems, contracts and people the day's operation depends on, and most of those links sit in documents nobody has read together.

  • A baseline of the operation, built from the documents you already have.
  • Ask what a change touches, and get an answer with its sources.
  • It sits above the systems that run the day. It doesn't replace them.

Starts at DiscoverDesign

What would replacing the East Terminal baggage system touch?

  1. It receives bag messages from the departure control system.Technology, Applications and Data Inventory
  2. It produces the bag-message data, which carries a thirty-day retention rule.Data Dictionary and Governance
  3. The replacement traces to a board decision, and its completion date is under review.Board Paper
High confidence 3 sources

Illustrative example. A fictional airport built for demonstration.

Building new

Building new means moving an operation that has never stopped. Before anything moves, you need to know what the current one depends on.

  • The systems, suppliers, teams and constraints the current operation depends on, each traced to a source document.
  • A confidence rating on each, so you can see which dependencies rest on weak evidence.

Starts at Discover

What the operation depends onTraced to source
East Terminal Baggage Handling System
System · Technology, Applications and Data Inventory.xlsx
Verified
IOP flight data feed
Data flow · Technology, Applications and Data Inventory.xlsx
Strong
Baggage systems OEM (supplier)
Stakeholder · Vendor Contract Summary, East Terminal Baggage.docx
Weak
Live terminal operations continuity
Constraint · Enterprise Risk Register.xlsx
Strong

Illustrative example. A fictional airport built for demonstration.

Behind schedule

The status report says green. The documents say otherwise, and nobody has put the two side by side.

  • Reported status checked against the evidence, and flagged wherever the two disagree.
  • The board pack drafted from the model, with the evidence attached.
  • Each decision kept with the assumptions it rests on, so you can find the one that slipped.

Starts at Deliver

Reported status against the evidence3 workstreams
East Terminal baggage replacement
Reported on track · Board Paper: completion date under review
Disagrees
West Terminal redevelopment
Reported on track · Completion date differs across three documents
Disagrees
Sustainability reporting
Reported on track · Sustainability Performance Data Book
Agrees

Illustrative example. A fictional airport built for demonstration.

Board baseline

The board wants one view of where the transformation stands. What it gets is a stack of reports from different engagements, each ageing from the day it was delivered.

  • A board-ready baseline across eight layers of the organisation, in weeks, not quarters.
  • A source document and a confidence rating behind every element.
  • The model and the decision record are yours, and stay with you when the engagement ends.

Starts at Discover

Baseline · The model8 layers
Strategic 34 Capability 96 Process 141 Organisation 78 Technology 112 Data 64 Risk & Compliance 51 Decision 29
NameConfidenceSource document
Live terminal operations continuityStrongEnterprise Risk Register.xlsx
Strategy and GovernanceVerifiedTarget Operating Model v3.pdf
Night-works noise restrictionsStrongCorporate Strategy and Transformation Plan.pdf

Every element carries its source document and a confidence rating.

Illustrative example. A fictional airport built for demonstration.

Start with one decision.

Schedule a call