Sir Robert McAlpine

From an initial five licenses in October 2023, SRM scaled to 78 hubs and 116 active users in just two years, with numbers increasing daily. Information delivery planning is now deployed on all new projects as a business standard, including a complete package of in-hub quality and tracking resources, Power BI dashboards, CDE connections, training materials, formal SRM procedures, and designated project sponsors and super users.

Model QA tracking provides a standardised process for recording pass/fail results from Solibri and Navisworks checks, with rejection reasons visible to submitting teams , the team is aiming for 20,000 model file reviews within the platform by end of 2026. A form-based sustainability risk and opportunity tracker lets external teams submit categorised items for internal review. And automated monthly reporting replaced the previous Word document process: discipline leads update their sections in Morta, data flows to Power BI for a client-facing report with historical data accessible by month.

The governance framework itself became a measurement tool. Five KPI themes track success: hub deployment and onboarding duration, records tracked, initiatives at each development stage, resource and hub traffic, and resource-specific metrics like the percentage of MIDP items matched to CDE for reporting accuracy.

SRM previously managed TIDPs and MIDPs through multiple Excel files of all different shapes and sizes, with inconsistent formats across projects and no shared standard for information delivery planning. Model QA checking lived in ad hoc spreadsheets with no portfolio-level visibility into pass/fail trends. Sustainability risk and opportunity tracking had no shared submission platform, and monthly client reports were compiled by hand in Word documents that were difficult to keep current month-on-month.

With over 150 years of operational history and projects across multiple sectors, SRM needed a structured way to identify the right use cases for a database-led approach, scale them from a project trial through to business-wide rollout, and apply consistent governance , without each project re-inventing the wheel.

SRM developed a three-stage work stream development process that gives every new idea a structured path from inception to business standard. All work streams start with an idea , usually driven by a project need , and pass through a Gate 1 review with stakeholders. If approved, they get built and trialled on a specific project at Stage 2. If the trial succeeds, Stage 3 develops the resource for company-wide rollout with sponsor sign-off and full documentation.

The hub structure mirrors SRM’s company management system and document naming conventions, ensuring the layout is immediately familiar to project teams. A dedicated admin section houses shared resources , including a single categorised data validation table that replaced per-work-stream duplicates, driving consistency and reducing repeated information. A project directory table feeds into everything: responsibility assignments, definitions, permission settings, and organisational task alignment. Each Stage 3 resource ships with a complete deployment package: in-hub quality and tracking resources, Power BI dashboards, CDE connections, training materials, formal SRM procedures, and designated project sponsors and super users. Clear governance routes between group sponsors, technology owners, group admins, Morta support through weekly catchups, project admins, discipline leads, and end users ensure accountability at every level.

SRM started with five licenses in October 2023 and no particular intention , just a focus group exploring the platform’s unique functionality through trials. After the first year, the team had a clear understanding of which functions Morta was most effective for and launched initial resources onto live projects: handover information management, sustainability tracking, and information delivery planning.

Year two brought structured scaling. A second working group focused on creating learning and support resources, and by summer, IDP was being rolled out on all new projects with a complete support package. In September, SRM joined the Morta scale-up plan and purchased 50 licenses. Group admins now have weekly technical support sessions with Morta, discussing resource development problems, new features, and training. But despite group-level support, the team recognises that on-project support from project admins and discipline leads is critical , as Mark puts it, regardless of the amount of support provided at group level, you need that local champion. Every deployment includes designated project sponsors and super users.