Bouygues TP Murphy JV

Morta became the entry point for all deliverables on the project , you cannot create a document in Asite or ProjectWise without first registering it in Morta, which is the key to maintaining a single source of truth across two CDEs and two JV organisations. Document codes are managed centrally to prevent duplicates, and user profiles determine which CDE receives each deliverable.

By syncing P6 data into Morta, the planning team , now one of the biggest user groups , can reorganise, filter, and enrich programme data without touching the master schedule. Teams self-serve answers to common questions about submittal dates, consent timelines, and tendering schedules without burdening planners. The component catalogue ingests industry standards from bSDD, National Highways, Uniclass, and carbon requirements, and drives automated configuration of CAD/BIM software platforms to produce standards-conforming IFC 4x3 files.

From the MIDP foundation, the team expanded brick by brick into consent tracking, procurement management, temporary works packaging, and carbon reporting , each building on shared master data. Rather than centralising all Morta work, the team established digital champions across functions who build and own their own solutions. When something gets defined once in Morta, it is defined once and reused across everything , spatial locations, site activities, plant, equipment, people , eliminating the constant reinvention that plagues large infrastructure projects.

There is a persistent gap in the industry between advanced enterprise systems , data warehouses, AI, drones , and the reality of day-to-day project work where Excel still dominates. Neither extreme served the team’s needs for accessible, collaborative data management on a project of this scale.

The Primavera P6 programme is an excellent tool for what it does, but extracting and sharing information from it was always challenging. The planning team was constantly fielding ad-hoc questions from hundreds of stakeholders, taking time away from maintaining the programme and interacting with production teams. Different teams referred to the same things by different names , on previous projects like HS2, asking what the South Portal was to different departments always produced different answers.

Two separate JV organisations needed to align on standards, naming conventions, column headers, RAG colours, navigation, and processes from day one , all while using different CDEs. With ProjectWise and Asite running in parallel, there was significant risk of duplicate document codes, inconsistent naming, and fragmented information unless a single entry point controlled creation across both systems. And as teams saw the potential, there was an initial temptation to do everything in Morta immediately , without governance, teams could develop independently and miss the chance to share standards and reuse data.

The team chose Morta for its plug-and-play nature , unlike enterprise solutions requiring months of IT setup, ETL pipelines, and data warehouse configuration, Morta delivered value immediately. The contractor and designer JVs had admin rights from day one and built the system together, establishing consistent column header colours, RAG colour standards, categorisation conventions, naming standards, and tile-based navigation for the landing page.

The MIDP drives CDE creation , you cannot create a deliverable in Asite or ProjectWise without first registering it in Morta. Document codes are managed centrally to prevent duplicates, and user profiles determine which CDE receives each deliverable. The project component catalogue was built in Morta by ingesting industry standards and requiring every discipline to create their components within the system, driving automated CAD/BIM software configuration and IFC 4x3 file delivery.

P6 data synced into Morta allows the planning team to reorganise, filter, and enrich programme data without touching the master schedule. Rather than trying to do everything at once, the team deliberately added use cases one at a time , consent tracking, procurement, temporary works, carbon , each building on shared master data and proven foundations. Five criteria determine whether a use case belongs in Morta: Is it a new data set? Will it interact with other data sets? How is it being shared? Does it need permission management? How is it being tracked?

Both the contractor and designer JVs had admin access from day one and built the system collaboratively, ensuring shared ownership and consistent standards from the outset rather than one party imposing their structure on the other. They developed tile-based navigation for the landing page, consistent column header colours across all documents and tables, standardised RAG colour schemes for validation, and clear naming and categorisation conventions.

Both the AMDG designer TIDPs and BMJV contractor TIDPs are managed in Morta, along with supply chain TIDPs. The process ensures document codes are unique across both CDEs and that user profiles route deliverables to the correct system. The team ingested bSDD, National Highways standards, Lower Thames Crossing-specific requirements, Uniclass codes, and carbon requirements into Morta, and each discipline created their components within this framework.

Rather than centralising all Morta work in the digital team, the project trains digital champions across different functions who build and maintain their own solutions. People have ownership of what they’re doing , they can create their own views and organise their information. The team actively communicates with the Morta community, sharing custom solutions and advocating for features to be incorporated into the core product. The flexibility of Morta is powerful, and as Thibaud notes, getting the most out of it rewards a high level of organisation and vision from the start.