Design / Technical integration
Integrate the approved project basis into one solution.
M4Forge connects property, technology, security, operations, engineering, specialist equipment and human requirements. For built assets, the commission can align to the RIBA Plan of Work; other project types follow the client’s applicable design and delivery framework.
01 / The buyer test
Does the proposed solution work across every system it depends on?
A drawing, specification or technology selection does not demonstrate maturity on its own. Before authorisation, the operational, spatial, technical, security, commercial and acceptance interfaces need to be resolved to the level required for the next decision.
02 / When it adds value
Use technical integration before unresolved dependencies reach procurement or delivery.
01
Requirements
Operational, user, security, property and technology requirements conflict or remain open to interpretation.
02
Interfaces
Design packages, systems or organisations are progressing without named ownership of the dependencies between them.
03
Authorisation
The solution needs a controlled route into procurement, implementation, construction or operational acceptance.
03 / Interface control
Solution maturity is demonstrated at the interfaces.
Each material dependency needs an owner, the required input, the decision and the record that closes it.
| Interface | Question before release | Required record |
|---|---|---|
| Requirements | Which approved outcome, user need or constraint does this decision satisfy? | Requirements trace and decision |
| Property and technology | Where do space, assets, systems, data, services, equipment or tolerances meet? | Interface owner and decision |
| Security and assurance | How do protection, information, resilience and independent authority alter the solution? | Authorised design decision |
| Operation and support | Can the solution be used, supported, maintained, changed and recovered? | In-use requirement |
| Acceptance | What has to be tested, witnessed and recorded before use? | Acceptance criterion |
04 / Defined result
The authorised solution carries traceable requirements, resolved interfaces and named owners.
- A coordinated solution and design basis for the agreed project stage.
- A requirements, interface and responsibility schedule.
- Recorded decisions across property, technology, security, operations, cost and delivery.
- A controlled issue for procurement, implementation, construction, testing or acceptance.
The appointment states the disciplines, design duties, checking arrangements and independent authorities in scope.
Design
Which dependency is preventing authorisation?
Start with the intended outcome, the open interface and the decision required before the next controlled issue.