Skip to content
WINNIIO
Project phases

A twin project, phased the way engineering already works.

Three layouts of the same SMILE journey. Five gated phases for machine builders, six steps for research partners, three blocks for companies that buy in steps. Each phase names what is done, what is delivered and which gate closes it. The first block is quoted on its own, so a decision to continue rests on delivered work.

Ask for a pilot studyRead the methodology →

Phases, activities, deliverables, gates.

Pick the layout your organisation already reads. The journey underneath is the same, and it reads in the same direction: outcome, decision, insight, information, data.

SuitsEngineering and machine-building partners already working with SDR, CDR, FAT and SAT. The twin's content in the boxes, the client's gates in the bars.

A · Five phases, five gatesThe rhythm of a machine project
Pilot study · quoted separately1 Understand & emulateUnderstand · Reality Emulationapprox. 4–6 weeks
Activities
  • Stakeholder map and SEEN interviews: situation, evidence, effects, needs.
  • One outcome to reach, with metrics and a date.
  • The reverse chain: outcome, decision, insight, information, data.
  • Reality capture: scans, drawings, photos, existing models.
  • Shared reality canvas v0.
  • Scope of the minimal viable twin (MVT).
  • Mock-up and trial in the canvas.
Deliverables
  • Outcome definition with metrics.
  • Reality canvas v0.
  • Requirement list with a source per requirement.
  • MVT scope.
  • Stakeholder matrix (RASIC).
  • Business case.
OROutcome Reviewequals SDR/PDR
2 Concurrent engineeringConcurrent Engineeringapprox. 4–8 weeks
Activities
  • As-is and to-be in the canvas.
  • Virtual user interaction with the roles concerned.
  • Data sources: system, owner, format, refresh rate.
  • Ontology sketch and named standards.
  • Architecture with an exit path per component.
  • Test scope defined.
  • Risk register.
Deliverables
  • MVT specification.
  • Data map: source, owner, format.
  • Test and verification plan.
  • Architecture with exit paths.
TDRTwin Design Reviewequals CDR
3 Ready to buildConcurrent Engineeringapprox. 2–4 weeks
Activities
  • Detailed data model.
  • Integration design per source.
  • Access, row-level security, key handling.
  • Gates and tests written before the build.
  • Hosting and suppliers chosen.
  • Interfaces frozen.
Deliverables
  • Completed design.
  • Runnable test suite.
  • Operations plan with rollback.
DRRData Readiness Reviewequals FDR
4 RealisationCollective Intelligenceapprox. 6–12 weeks
Activities
  • Build of the MVT.
  • Sources connected.
  • Calibration against reality, deviation measured.
  • Nightly checks and CI.
  • User trials in staging.
  • User documentation.
Deliverables
  • MVT in staging, accepted against the test plan.
FATFactory Acceptance
5 Commissioning & handoverContextual Intelligenceapprox. 2–4 weeks
Activities
  • Go-live.
  • Training of the roles concerned.
  • Documentation.
  • Operations agreement and partnership.
  • Usage measured.
  • Vendor-exit pack.
Deliverables
  • Twin in operation.
  • Documentation.
  • Vendor-exit pack.
  • Operations agreement.
SATSite Acceptance
Pilot study · quoted separately

Phase 1 is quoted separately as a pilot study, preferably on current account. The remaining phases are quoted when the pilot study is delivered.

Commercial form

Phase 1 at fixed price or on current account. Phases 2 to 5 are quoted once phase 1 is delivered.

Horizon

After SAT: operations and partnership month by month. Perpetual Wisdom is the horizon, never a milestone.

Five guidelines shared by all three.

Outcome first, data last

Every phase starts in the outcome the client must reach and ends in the data that outcome requires.

Reality as the shared picture

Scans, drawings and photos form one shared reality canvas before anything is built. Meetings happen in the canvas.

Minimal viable twin

Around 95 percent captured reality and 5 percent high detail, placed where the decision is made.

Replaceable at every layer

Every component has a documented exit path. The client owns data, models and keys.

Proof before claim

Every deliverable is accepted against a written test plan, and the test result is reported.

Next step

Start with the pilot study.

The pilot study is quoted on its own, at fixed price or on current account. It ends in a shared reality canvas, one outcome with metrics and the scope of a minimal viable twin. The remaining phases are quoted on that basis.

Ask for a pilot studyHow scoping works →

The method itself is published and citable: read SMILE, and how we deliver answers the technical due-diligence questions.