Implementation handover

Phase 4 packages the design into things an implementation team can act on.

The deliverables library

Phase 4 is a data-first deliverables library. Instead of “pick a template, pick a format”, each card is a deliverable type derived from the engagement’s actual data — the card knows what data it needs, tells you whether that data is there yet, and offers only the formats that make sense for it.

Deliverables span the whole engagement (roughly twenty templates) and render to Word, PowerPoint, PDF, and SVG — capability maps, heat maps, roadmap visuals, design documents, configuration specs, the closure report, and more. See Deliverables for the full list and the completeness check.

The implementation roadmap

The roadmap built in Phase 3 (/engagements/{id}/roadmap) — aligned to the client’s delivery framework, with a Gantt view and a dependency-cycle check — is part of the handover package.

One-way exports to EA tools

The model exports one way to ArchiMate 3 (validated against the schema), LeanIX, Ardoq, and Sparx (XMI). These are exports, not a round-trip — eavantage doesn’t read its own exports back in, and it doesn’t write to those tools. See Exporting to EA tools.

The handover view

The implementation architect gets a dedicated read-only view (/handover/{id}) of the finished design and its artifacts, to build from — they can read every layer and download deliverables, and they can’t change anything.