Julian.Kellett What this view is for Order.core_details is the starting point for all order-based reporting. Where Busopp represents sales intent, Orders represent contracted commitments.This view defines the order as a business object and provides the identity and links needed to connect it back to opportunities and forward to invoicing. If you’re asking “what work has been … Read more
What this view is for Busopp.item_values_lines provides the numeric values associated with business opportunities. If: then item_values_lines tells you how much. This is the view where pipeline value lives. A note on “lines” in the CDM For convinience, in the Common Data Model (CDM), the term lines is used as a version indicator. For opportunities, … Read more
What this view is for Busopp.meta_dates provides the key lifecycle and timing dates for business opportunities. If core_details tells you what the opportunity is and meta_codes tells you how it should be categorised, meta_dates tells you when important things happened (or are expected to happen). This view is essential for understanding pipeline flow, forecasting, and … Read more
What this view is for Busopp.meta_codes provides the categorisation and contextual labels for business opportunities. If core_details tells you what the opportunity is, meta_codes tells you how it should be grouped, classified or interpreted. This is where things like type, category, region, ownership and other descriptive attributes live. Level of detail (grain) This view is … Read more
What this view is for Busopp.core_details is the starting point for all sales pipeline reporting. It represents a single business opportunity in its simplest, most recognisable form and provides the identity and linkage needed to explore the rest of the pipeline. If you’re asking “what opportunities do we have, and how do they connect to … Read more
The Sales Pipeline DataMarts are designed to help you move confidently from opportunities, through orders, and on to invoices — without having to relearn the data model each time. The most important thing to remember is this: these views are meant to be combined. Once you understand the pattern, building modular, reusable reporting becomes much … Read more
The meta_codes, meta_dates (and any derived meta_values) views are intentionally long and thin. This structure: That said, long thin tables aren’t always the easiest shape to work with directly in a reporting tool. Shaping meta data into a report-friendly form Once you’ve applied some basic filtering (for example, keeping only the code or date types … Read more
This process describes how to take a new data source from landing → Bronze → DataMart view, and fully define its attribute lineage in myBMT. 1. Prepare and review the new data source 2. Catalogue and land the source 3. Plan the DataMart view(s) 4. Set up attribute lineage in myBMT For each new view … Read more
1. Core Detail Views Updated views Change Impact / Rationale 2. Project Meta Values Views Updated views Changes / Notes Risks / Considerations 3. Meta Codes Views Updated views Changes Impact / Rationale 4. Feedback Meta Satisfaction View View Changes / Notes Action 5. Infrastructure OSH Records View Changes / Notes Impact 6. Base Architecture … Read more
Version: 1.0Owner: Regional Finance DirectorPrepared by: Data Engineering 1. Purpose The purpose of this report is to provide clear and consistent visibility of margin performance across all active projects, comparing the originally approved bid margin with the latest forecast outturn margin. The report will support financial oversight, early risk identification, and commercial performance management at project, PRU, and regional levels. 2. Objectives 3. … Read more