Sources and Provenance
This site is based on the public deliverables of the MaaSAI project. Pages attribute their content to the deliverable it comes from, either inline (for example “(D6.1)”) or in source notes and figure captions.
Deliverables Used
Section titled “Deliverables Used”D5.1 and D5.2 describe the design of MaaSAI. The four M20 deliverables report the first release of the solutions; from them, the site takes implementation details such as technology stacks, integrations, APIs and interfaces, user-interface screens, deployment and configuration, and maturity.
| Deliverable | Title | Due | What this site uses it for |
|---|---|---|---|
| D4.1 | MaaSAI Project Vision | M3 (February 2025) | The list of the 23 solutions with their names and codes, the release and piloting milestones on the home page, the Pilots page, and terminology in the Glossary. |
| D4.5 | Problem Analysis and Solutions Strategies Overview | M12 (November 2025) | The business processes of each pilot on the Pilots page, and terminology. |
| D5.1 | MaaSAI Architecture | M6 (May 2025) | The Reference Architecture: conceptual and functional architecture, the three environments, the functional domains and the Cloud, Fog and Edge tiers. |
| D5.2 | MaaSAI Viewpoints | M12 (November 2025) | The design baseline of each solution: actors and use-case diagrams (usage viewpoint), functional components (functional viewpoint) and architecture (implementation viewpoint); the cross-solution Business Viewpoint and Usage Viewpoint pages. |
| D6.1 | Cloud MaaS Marketplace and Supporting Components | M20 (July 2026) | First release of CMM, MDC, RS, MCH, MCA and MPA. |
| D8.1 | Data Integration, Storage and Secure Communication Infrastructure | M20 (July 2026) | First release of DI, DS, PSM, DIP and MSB. |
| D10.1 | Digital Twins Designer, Analytics, Monitoring and Control | M20 (July 2026) | First release of DTD, DA, CP, RMC and MWC. |
| D12.1 | Supply Chain Planning, Simulation and Assessment | M20 (July 2026) | First release of MCP, MPP, SCS, PMT, LCT, R3T and SCT. |
| D16.4 | Standardisation | M12 (November 2025) | Standards terminology in the Glossary. |
Due dates are the contractual months of the project, counted from its start in December 2024 (M1). The Glossary and the Integration Map cite further sections of these deliverables.
Precedence Between Sources
Section titled “Precedence Between Sources”Later deliverables take precedence over earlier ones. Where they differ, the M20 implementation deliverables (D6.1, D8.1, D10.1 and D12.1) take precedence over the design baseline of D5.2, and over D5.1. Solution pages therefore present the D5.2 design baseline together with the first-release details, and follow the M20 deliverables where the two disagree. One exception: the environment and tier of each solution in Solutions at a Glance record the logical placement drawn in D5.1 (Figure 54), which some M20 deliverables describe differently.
Figures
Section titled “Figures”Diagrams marked as redrawn are redrawn as editable SVG from the figures of the cited deliverable. Redrawing corrects obvious spelling errors only; otherwise the diagrams follow the original figures. User-interface screenshots are reproduced from the M20 deliverables.
D5.2 uses the same figure for two solutions in two cases: the MPP dataflow (Figure 71) repeats the MCP dataflow (Figure 70), and the MSB dataflow (Figure 79) repeats the SCT functional components figure (Figure 75). The corresponding pages of this site therefore show the same diagram, as the MPP and MSB captions note.
Reproduction
Section titled “Reproduction”The copyright notice of each of the deliverables listed above (for example D5.1) states: “Reproduction is authorised provided the source is acknowledged.” This site acknowledges the source deliverables in the text and in figure captions.