{ "coverage": { "by_status": { "ambiguous": 0, "context_only": 0, "direct": 0, "not_found": 8, "partial": 0, "possible": 0 }, "mapped_or_plausible": 0, "requirements_identified": 8 }, "coverage_explanation": "The workbook explicitly states that `Target Fields` is the authoritative register and that the other sheets are synthetic illustrations (`Read Me`!B8). Accordingly, the primary denominator is the eight register rows `Target Fields`!A2:J9, all marked required. Result: 0 direct, 0 partial, 0 possible, 0 ambiguous and 8 not_found. The sample, reference and KPI sheets were used only to clarify intended grain, domains and calculation behaviour; they were not counted as additional authoritative objects. `not_found` means absent from the available discovered current-gold boundary, not proven absent elsewhere in the client estate.", "limitations": [ "The current-gold boundary contains only the selected finance current-state page and a journal-controls evidence page. Absence from these pages is not proof of enterprise-wide absence.", "The workbook states that all sample values are fictional and intended for design discussion, not reconciliation or production reporting (`Read Me`!B10). Ordinary numeric values were deliberately excluded from the evidence rendering, so prototype inputs and calculated outputs cannot be inspected or reconciled.", "Formula text was extracted, but stored formulas do not prove successful recalculation, current cached values or production correctness.", "No workbook connections, queries, external links, Power Query/DataMashup, pivots, charts, slicers or embedded Power Pivot model were found. Therefore, the workbook evidences requirements and prototypes, not implemented data integration or a semantic model.", "No comments, notes, hyperlinks, validation rules or conditional-formatting rules were found. The reference lists therefore do not demonstrate enforced data validation.", "The workbook extraction was included without reported truncation or omitted items, but opaque binary payloads are indicator-only by profile and ordinary non-text data values are outside scope.", "Exact DAX definitions for the four current-gold finance measures were not available, so their detailed semantics cannot be independently compared. Their observed names and the model structure nevertheless provide no supporting object for either requested sales measure.", "The authoritative register does not explicitly declare `SalesOrder.CustomerIdentifier` or a relationship, although the synthetic order sheet implies that linkage. This is a requirements completeness issue rather than current implementation evidence." ], "report_markdown": "# Workbook-to-current-gold assessment\n\n## Executive conclusion\n\nThis workbook appears to specify a **new customer and booked-sales-order analytics subject area** for FY2026\u2013FY2027. It requires customer identity, segmentation and relationship ownership; sales-order identity, gross value and acquisition channel; and two commercial measures: Customer Lifetime Value and Gross Order Intake.\n\nThe workbook explicitly designates `Target Fields` as its authoritative register (`Read Me`!B8). That register contains eight rows and marks every row required (`Target Fields`!F2:F9). None of the eight declared objects was found in the available current-gold model.\n\nThe current-gold landscape instead describes a small finance ledger model with `Account`, `Calendar`, `Ledger` and `Metrics` as its business-facing tables. Its observed measures are `Actual Net`, `Actual Revenue`, `Budget Net` and `Net Variance`; its observed amount is `Ledger.SignedAmount`. There are no observed Customer, SalesOrder or SalesMetrics objects [fde-finance.current-model]. The separate journal-controls page concerns two finance-ledger attributes and does not supply customer/order coverage [fde-finance.journal-controls].\n\n**Authoritative coverage:** **0/8 mapped**; **8/8 not found** in the available discovered landscape.\n\n## Interpreted business and data requirements\n\nThe authoritative register implies two principal business entities and a calculation layer:\n\n- **Customer**, at customer-level grain, with enterprise identity, commercial segment and accountable relationship owner (`Target Fields`!A2:I4; corroborated by `Customer Sample`!A1:C3).\n- **SalesOrder**, at representative booked-order grain, with order identity, gross value before discounts and sales channel (`Target Fields`!A5:I7; corroborated by `Sales Orders`!A1:D3).\n- **SalesMetrics**, containing Customer Lifetime Value and Gross Order Intake (`Target Fields`!A8:I9; corroborated by `Sales KPI Prototype`!A3:C5 and formulas B4:B5).\n\nThe sample order sheet also contains `CustomerIdentifier` on each order (`Sales Orders`!B3:B15), implying a customer-to-order linkage. However, that order-side field is not declared as its own row in the authoritative register, so it is treated as design context rather than a ninth authoritative requirement.\n\nThe hidden reference sheet supplies candidate controlled domains for CustomerSegment and SalesChannel (`Reference Data`!A2:C7). These are design semantics, not proof of implemented validation or a production reference-data solution.\n\n## Authoritative mapping results\n\n| ID | Required object | Workbook evidence | Result | Current-gold assessment |\n|---|---|---|---|---|\n| TF-01 | `Customer.CustomerIdentifier` | `Target Fields`!A2:J2 | Not found | No Customer table or customer identifier was observed [fde-finance.current-model]. |\n| TF-02 | `Customer.CustomerSegment` | `Target Fields`!A3:J3 | Not found | No Customer table or commercial-segment attribute was observed [fde-finance.current-model]. |\n| TF-03 | `Customer.RelationshipOwner` | `Target Fields`!A4:J4 | Not found | No Customer table or relationship-owner attribute was observed [fde-finance.current-model]. |\n| TF-04 | `SalesOrder.OrderIdentifier` | `Target Fields`!A5:J5 | Not found | No SalesOrder table or order identifier was observed [fde-finance.current-model]. |\n| TF-05 | `SalesOrder.OrderGrossValue` | `Target Fields`!A6:J6 | Not found | `Ledger.SignedAmount` is a finance-ledger amount, not evidence of gross order value before discounts; no SalesOrder amount was observed [fde-finance.current-model]. |\n| TF-06 | `SalesOrder.SalesChannel` | `Target Fields`!A7:J7 | Not found | No SalesOrder table or acquisition-channel attribute was observed [fde-finance.current-model]. |\n| TF-07 | `SalesMetrics.Customer Lifetime Value` | `Target Fields`!A8:J8 | Not found | The current `Metrics` table contains only four named finance measures. A generic measure table does not establish this commercial measure [fde-finance.current-model]. |\n| TF-08 | `SalesMetrics.Gross Order Intake` | `Target Fields`!A9:J9 | Not found | No measure with this name or booked-order semantics was observed. `Actual Revenue` and other finance measures cannot be treated as equivalents because their exact DAX and business semantics are unknown [fde-finance.current-model]. |\n\n## Calculation interpretation\n\n- **Gross Order Intake** is declared as the sum of `OrderGrossValue` (`Target Fields`!H9), and the prototype stores `=SUM('Sales Orders'!C4:C15)` (`Sales KPI Prototype`!B4). This is evidence of intended stored logic, not proof of successful recalculation, current cached results or production-ready semantics.\n- **Customer Lifetime Value** is described as average gross order value multiplied by expected order frequency (`Target Fields`!H8). The prototype stores `=B4/COUNTA('Customer Sample'!A4:A11)*3.2` (`Sales KPI Prototype`!B5). The multiplier 3.2 is explicitly illustrative for discovery (`Sales KPI Prototype`!C5), so the production frequency basis, time horizon, cohorts and treatment of discounts, cancellations and returns remain undefined.\n\n## Contextual design observations\n\n1. **Customer-order relationship:** The order sample places `CustomerIdentifier` on orders (`Sales Orders`!B3:B15), but the authoritative register does not request `SalesOrder.CustomerIdentifier` or explicitly declare a relationship. A production semantic model will require a documented customer/order key and cardinality.\n2. **Controlled values:** The workbook proposes CustomerSegment values Enterprise, Mid-market and Small business, and SalesChannel values Direct, Partner and Online (`Reference Data`!A2:C7). No workbook data-validation rule was found, so these are reference examples rather than enforced constraints.\n3. **Planned sources:** Customer fields point to a CRM customer master, order fields to an order-management platform, and measures to a sales analytics calculation layer (`Target Fields`!I2:I9). The workbook contains no connections, queries or external links, so source accessibility and integration status are not evidenced.\n4. **Current-model mismatch:** The available gold model is finance-ledger oriented, while this workbook requests customer/order analytics [fde-finance.current-model]. This may represent a genuine greenfield gap, a different subject-area model, or selection of a current model that was not intended to satisfy this request.\n\n## Consultant guidance\n\nThe supplied consultant-guidance object contained no workbook-level or sheet-level comments. Consequently, no steering note changed the interpretation; the workbook's own explicit authority statement determined the denominator.\n\n## Recommended decisions and next steps\n\n1. Confirm whether the audited finance model is actually the intended destination for this customer/order subject area, or whether another semantic model/workspace should be discovered.\n2. Add or explicitly reject `SalesOrder.CustomerIdentifier` in the authoritative register and document the customer-to-order relationship, key uniqueness and handling of unmatched customers.\n3. Define production semantics for Gross Order Intake: booked-status event, booking date, cancellations, returns, discounts, tax, currency conversion and late changes.\n4. Define production semantics for Customer Lifetime Value: forecast horizon, order-frequency method, customer cohort, margin versus gross value, churn assumptions and refresh cadence.\n5. Confirm source contracts and ownership for the CRM customer master, order-management platform and calculation layer.\n6. Re-run discovery against the intended sales/customer model or source estate before concluding that the objects are enterprise-wide gaps.", "requirements": [ { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Customer.CustomerIdentifier column", "questions": [ "What is the governed customer key, and is it stable and unique across all CRM records?", "Must source-system identifiers be retained alongside an enterprise customer identifier?" ], "rationale": "The authoritative register requires a String customer identity sourced from the CRM customer master. The current-gold model has no Customer table or customer identifier. AccountKey is an accounting key and is not evidence of enterprise customer identity.", "requirement_id": "TF-01", "source_cells": [ { "coordinate": "A2:J2", "sheet": "Target Fields" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Customer.CustomerSegment column", "questions": [ "Are Enterprise, Mid-market and Small business the complete governed segment domain?", "Is segmentation current-state only, or must historical segment changes be analysed?" ], "rationale": "The required commercial segment and its illustrative ENT/MID/SMB domain are not present in the observed finance-ledger model. AccountType is not a supported equivalent because it describes accounting accounts rather than customers.", "requirement_id": "TF-02", "source_cells": [ { "coordinate": "A3:J3", "sheet": "Target Fields" }, { "coordinate": "A2:C4", "sheet": "Reference Data" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Customer.RelationshipOwner column", "questions": [ "Should the model retain owner identifiers as well as display names?", "How should reassignment history, vacancies and shared ownership be represented?" ], "rationale": "No customer entity or accountable relationship-owner attribute was observed in current gold.", "requirement_id": "TF-03", "source_cells": [ { "coordinate": "A4:J4", "sheet": "Target Fields" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "SalesOrder.OrderIdentifier column", "questions": [ "What defines a unique order across order-management systems or legal entities?", "Are revisions, split orders and cancelled orders represented by the same identifier or separate records?" ], "rationale": "No SalesOrder table or customer-order identifier was observed in the current model. Ledger keys and finance entries do not establish order identity.", "requirement_id": "TF-04", "source_cells": [ { "coordinate": "A5:J5", "sheet": "Target Fields" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "SalesOrder.OrderGrossValue column", "questions": [ "Does gross value include tax, freight or other charges?", "Which currency fields and conversion rules are required?", "How are cancellations, returns and subsequent order amendments reflected?" ], "rationale": "The workbook requires gross order value before discounts at order grain. Current gold contains Ledger.SignedAmount at finance-ledger grain, which is not a semantic or structural match to gross booked order value.", "requirement_id": "TF-05", "source_cells": [ { "coordinate": "A6:J6", "sheet": "Target Fields" }, { "coordinate": "A1:D3", "sheet": "Sales Orders" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "SalesOrder.SalesChannel column", "questions": [ "Are Direct, Partner and Online exhaustive governed channels?", "Can an order have multiple contributing channels, and if so what attribution rule applies?" ], "rationale": "No sales-order acquisition-channel attribute was observed. The workbook's Direct, Partner and Online values are illustrative reference data, not a current-gold implementation.", "requirement_id": "TF-06", "source_cells": [ { "coordinate": "A7:J7", "sheet": "Target Fields" }, { "coordinate": "A5:C7", "sheet": "Reference Data" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "SalesMetrics.Customer Lifetime Value measure", "questions": [ "What forecast horizon and expected-order-frequency method should production CLV use?", "Should CLV use gross order value, net revenue, gross margin or contribution margin?", "How should churn, returns, discounts and customer tenure affect the calculation?" ], "rationale": "No Customer Lifetime Value measure or supporting customer/order structure was observed. The current model's four finance measures are differently named and have unknown exact DAX. The workbook prototype's 3.2 frequency multiplier is illustrative and does not establish a production definition.", "requirement_id": "TF-07", "source_cells": [ { "coordinate": "A8:J8", "sheet": "Target Fields" }, { "coordinate": "A5:C5", "sheet": "Sales KPI Prototype" }, { "coordinate": "B5", "sheet": "Sales KPI Prototype" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "SalesMetrics.Gross Order Intake measure", "questions": [ "What event makes an order count as booked intake, and which date drives reporting?", "Should cancelled or amended orders restate prior periods?", "Are intake values reported before discounts, tax and currency conversion in all views?" ], "rationale": "The required sum of OrderGrossValue and its prototype formula have no observed counterpart in current gold. Actual Revenue cannot be assumed equivalent to gross booked order value, particularly because exact DAX and production semantics for current measures were not returned.", "requirement_id": "TF-08", "source_cells": [ { "coordinate": "A9:J9", "sheet": "Target Fields" }, { "coordinate": "A4:C4", "sheet": "Sales KPI Prototype" }, { "coordinate": "B4", "sheet": "Sales KPI Prototype" } ], "status": "not_found" } ], "review_flags": [ { "priority": 1, "queue_name": "scope", "reason": "Urgently confirm whether the selected finance-ledger model is intended to satisfy this customer and order analytics request; the subject areas do not align.", "subject": "workbook" }, { "priority": 5, "queue_name": "client_question", "reason": "The synthetic order sheet requires CustomerIdentifier for linkage, but the authoritative Target Fields register omits the order-side foreign key and any relationship declaration.", "subject": "Customer-order relationship" }, { "priority": 10, "queue_name": "client_question", "reason": "Customer Lifetime Value is not production-defined; horizon, frequency, churn, margin/value basis and change handling require business decisions.", "subject": "TF-07" }, { "priority": 15, "queue_name": "client_question", "reason": "Gross Order Intake needs governed booking-event, date, cancellation, amendment, discount, tax and currency semantics.", "subject": "TF-08" }, { "priority": 20, "queue_name": "evidence_research", "reason": "Discover the CRM customer master, order-management platform and intended sales calculation layer to determine source availability and existing implementations.", "subject": "Planned source systems" }, { "priority": 30, "queue_name": "consultant_review", "reason": "Review register completeness, particularly keys, dates, currency, status, customer-order linkage and measure dependencies needed for a viable semantic model.", "subject": "Target Fields register" }, { "priority": 40, "queue_name": "revalidation", "reason": "After confirming the intended workspace/model, rerun discovery and mapping before treating the eight not-found results as implementation gaps.", "subject": "Current gold coverage" } ], "summary": "The workbook is a discovery/design pack for a new customer and sales-order analytics subject area. Its explicitly authoritative `Target Fields` register declares eight required objects: six columns across Customer and SalesOrder plus two SalesMetrics measures. None of those eight objects was observed in the available current-gold Power BI landscape. The discovered current model is instead a finance-ledger model containing Account, Calendar, Ledger and Metrics, with four finance measures; generic similarities such as a Metrics table or a decimal amount column do not establish customer/order semantic matches. Authoritative coverage is therefore 0 of 8 direct, partial or possible mappings, and 8 of 8 not found within the bounded current-gold evidence." }