1. Purpose This guide shows how to build a Power BI report using the standard DataMart wireframe. It demonstrates how: The wireframe is not just a template — it is a working example of how reporting should be built. 2. The Principle Engineering defines the data.Analysts define the question.The wireframe allows both to operate without … Read more
1. Identity Core identifiers and object naming. PurposeObject identifiers. 2. Structural Keys Structural identifiers used to link datasets. PurposeIdentify or reference core business entities. 3. Commercial Context Customer and contractual relationships. PurposeDescribe commercial relationships and contracts. 4. Sales & Pipeline Sales organisation and opportunity tracking. PurposeAnalyse pipeline, opportunity probability, and sales ownership. 5. Financial Values … Read more
Purpose META_TYPE is used within CDM metadata views (such as meta_codes, meta_dates, and meta_values) to group related attributes into meaningful analytical categories. Rather than storing hundreds of unrelated attributes, META_TYPE provides a semantic grouping layer that helps analysts understand the nature of the data. Each row therefore follows a pattern similar to: OBJECT → META_TYPE … Read more
Provides project role assignment metadata in the standard CDM meta_codes structure, with regional view variants for APC, CAD, USD, UKS, and future IFS-aligned sourcing. Purpose The project.meta_codes_roles family provides a standardised project-role metadata pattern for identifying named project responsibilities against a project object. This allows project role assignments to be consumed consistently across regions even … Read more
Order.item_dates_stage captures the order lifecycle timeline as a status-history “item” table. Each row represents a single lifecycle event (a status entry) for an order, with the event date carried as a meta-date value and the event details stored as JSON metadata. Use it when you need to answer questions like: Grain and keys This is … Read more
What this is MP8 and MP9 are regional “Opportunity & Order Intake” extracts used to provide sales pipeline and win/loss visibility where the opportunity lifecycle is not yet fully represented in IFS (or where we need historic continuity). This logic standardises the two extracts into a single, report-ready shape that aligns to our BusOpp-style reporting … Read more
What this view is for Project.item_values provides the numeric and financial measures for projects. Where: If you’re asking:“how much has this project cost?”,“how much revenue has it generated?”, or“what is the current forecast or contingency?” — this is where you look. Architectural maturity This view is delivered as a cvw (collated view). It is assembled … Read more
What this view is for Project.meta_dates provides the date-based and lifecycle attributes for projects. Where Project.core_details defines what a project is,and Project.meta_codes defines how a project is classified,Project.meta_dates defines when things happen in the life of a project. If you’re asking “when did this project start?”, “when is it due to finish?”, or “when did … Read more
What this view is for Project.meta_codes provides the categorical and classification attributes for projects. Where Project.core_details defines what a project is,Project.meta_codes defines how a project is described and grouped. If you’re asking “what type of project is this?”, “which programme does it belong to?”, or “how should this project be categorised?” — this is where … Read more
What this view is for Project.core_details is the starting point for all project-based reporting. Where: This view defines the project as a business object and provides the identity and links needed to relate delivery activity back to opportunities, orders, customers and ultimately invoicing. If you’re asking “what projects are we running, for whom, and how … Read more