> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-5-implementation-and-onboarding.md). # Module 5 — Implementation and onboarding Ten videos on standing the framework up and running it: the four-phase plan on an honest calendar with the investment, procurement, workforce and risk plans beside it. {% hint style="info" %} **Why ten videos.** 5.8–5.10 were Module 6 in the v0.1 bundles. Module 6 was retired on 12 September 2026 (as *Developing a Gov Enterprise Architecture (GEA)* retired its AI-plays module on 3 September): its catalogue, role-paths and storyboard repeated the earlier modules and now live on the [course home page](/experience-digital-transformation/gif/building-a-government-interoperability-framework-gif.md); its three genuinely new plays — watching the bus, cross-checking the framework's documents, carrying it to the next sector — are the last three videos here. 5.9 and 5.10 return to the Strategist; every video states its persona and stands alone. {% endhint %} **Persona:** Architect for 5.1–5.8; Strategist for 5.9–5.10. **You leave with:** B28, B29, B30, B31, B32, B33, B34, B35, B36, B37, filed in your framework workbook — the runnable slice, then the framework in operation. Runtime \~44 minutes across 10 videos. Ten videos on standing the framework up and running it: the four-phase plan on an honest calendar with the investment, procurement, workforce and risk plans beside it, Member Requirements and the SLA, registering a member, standing up the Linkup federation, the live once-only exchange that is the framework's acceptance check, what changes for production — and then watching the bus from its logs, keeping the decree, Governance Pack and standards portfolio from contradicting each other, and carrying the framework to the next sector. ## Subtopics | # | Subtopic | Single message | Your play | Kit skill | | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ----------------------- | | [5.1](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.1-plan-the-build-in-four-phases.md) | Plan the build in four phases | Foundation, Pilot, Expansion, Optimisation — four phases with decision gates, an honest calendar, and the four plans beside the schedule that a funder actually reads. | ✍️ B28 | — | | [5.2](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.2-state-what-a-member-must-have-the-member-requirements.md) | State what a member must have — the Member Requirements | The Member Requirements template tells an agency exactly what it must have before it can join — no surprises at go-live. | ✍️ B29 | `ea-governance-drafter` | | [5.3](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.3-make-connected-mean-dependable-the-sla.md) | Make 'connected' mean 'dependable' — the SLA | A Service-Level Agreement turns 'connected' into 'dependable' — the template makes it a fill-in, not a negotiation from scratch. | ✍️ B30 | `ea-governance-drafter` | | [5.4](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.4-admit-a-member-to-the-bus.md) | Admit a member to the bus | An agency is admitted by a validated request and a recorded committee decision — then the join runs itself and proves itself with a real call. | ✍️ B31 | — | | [5.5](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.5-stand-up-the-federation.md) | Stand up the federation | Central Server, Test CA, four Security Servers — the Linkup federation, stood up from the run book and shown healthy, registered and granted exactly. | ✍️ B32 | — | | [5.6](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.6-run-the-once-only-exchange-live.md) | Run the once-only exchange, live | PNEA issues a credential and pre-fills identity from PNIA and enrolment from PLR — a real cross-server call, the data asked once. | ✍️ B33 | — | | [5.7](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.7-from-demonstration-to-production.md) | From demonstration to production | What changes between the sandboxed Linkup demonstration and a production-grade federation a country would actually run. | 🔍 B34 | — | | [5.8](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.8-watch-the-bus-monitoring-and-anomaly-detection.md) | Watch the bus — monitoring and anomaly detection | Point Claude at the bus's operational monitoring data — never its message log — to spot a failing or unusual exchange early. | 🔍 B35 | — | | [5.9](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.9-keep-the-documents-honest-the-consistency-cross-check.md) | Keep the documents honest — the consistency cross-check | Keep the decree, the Governance Pack and the standards portfolio saying the same thing — a cross-check that catches drift across the three. | 🔍 B36 | — | | [5.10](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.10-carry-the-framework-to-the-next-sector.md) | Carry the framework to the next sector | The same four-layer framework stands up interoperability beyond education — the method is sector-portable, and the second sector is cheaper than the first. | ✍️ B37 | — | ## How the plays chain in this module ```mermaid flowchart TD B28["B28 Implementation plan: phased schedule, investment, procurement, workforce, risk register and metrics\n(5.1)"] B29["B29 Member Requirements checklist\n(5.2)"] B30["B30 Service-Level Agreement template\n(5.3)"] B31["B31 X-Road member registration\n(5.4)"] B32["B32 Federation stand-up run book\n(5.5)"] B33["B33 Once-only acceptance script\n(5.6)"] B34["B34 Demonstration-to-production gap checklist\n(5.7)"] B35["B35 Bus-health summary and anomaly list\n(5.8)"] B36["B36 Document-consistency report\n(5.9)"] B37["B37 Sector-portability map\n(5.10)"] M1_B5["Module 1\nB5"] M1_B6["Module 1\nB6"] HOME["The country storyboard\n(course home)"] M4_B22["Module 4\nB22"] M2_B13["Module 2\nB13"] M3_B17["Module 3\nB17"] M4_B26["Module 4\nB26"] M4_B27["Module 4\nB27"] M2_B11["Module 2\nB11"] M3_B19["Module 3\nB19"] M4_B23["Module 4\nB23"] M1_B5 --> B28 M1_B6 --> B28 B28 --> B34 B28 --> B37 B28 --> HOME M4_B22 --> B29 M2_B13 --> B29 B29 --> B31 M3_B17 --> B30 M4_B26 --> B31 B31 --> B32 B32 --> B33 B32 --> B34 M4_B27 --> B33 M2_B11 --> B36 M3_B19 --> B36 M4_B22 --> B36 M4_B22 --> B37 M4_B23 --> B37 ``` The full chain, including where these artefacts come from and go next, is on [Your framework workbook](/experience-digital-transformation/gif/your-framework-workbook.md). {% hint style="info" %} **Before you start.** Every play asks you to paste country context. Build it once with [Play 0](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/play-0-build-your-country-context) — that is **A0** — and add the three interoperability sections from the [Play 0 supplement](/experience-digital-transformation/gif/play-0-supplement.md). No country to hand? Run them on [Progressa](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/progressa-the-demonstration-country), the fictional demonstration country; for Modules 4 and 5 the [build pack](/experience-digital-transformation/gif/the-build-pack.md) is Progressa's finished output. {% endhint %} {% hint style="info" %} New to the plays? Read [How to use the plays](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/how-to-use-the-plays) and [Working with AI](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/working-with-ai-the-ground-rules) first — part of the about fifteen minutes of Start here, and they apply to every module of every Knowledge Product. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/gif/module-5-implementation-and-onboarding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.