{ "coverage": { "by_status": { "ambiguous": 1, "context_only": 2, "direct": 0, "not_found": 8, "partial": 0, "possible": 0 }, "mapped_or_plausible": 0, "requirements_identified": 9 }, "coverage_explanation": "Coverage is effectively 0 of the 8 explicitly required register entries: 0 direct, 0 partial, 0 possible, 7 not found, and 1 ambiguous. The ambiguous item, Customer Lifetime Value, is also not represented in current gold, but its workbook definition is not sufficiently complete to assess implementable semantic equivalence. Three supporting design concepts\u2014the customer/order association, reference-value domains, and prototype KPI presentation\u2014are context-only or not found rather than counted as explicit registered fields. All non-observation is bounded to the selected current-gold build and does not prove that suitable data or models do not exist elsewhere in the client estate.", "limitations": [ "Only literal non-empty text cells were available; numeric cells, formulas and other non-text workbook content were intentionally excluded.", "Synthetic sample values cannot be used as production evidence, and gross-value amounts were not present in the text extraction.", "The available current-gold boundary contains one observed finance semantic model and one method page; it is not a complete inventory of the enterprise estate.", "Exact DAX expressions for the four current Metrics measures were not returned by the bounded audit, although their documented business meanings still do not establish order-KPI equivalence.", "Workbook-planned sources and implementation notes are declarations only; no source connectivity, lineage, refresh, quality, history, currency or access-control evidence was supplied.", "The workbook gives an FY2026\u2013FY2027 planning horizon but does not specify delivery phases, required dates, fiscal treatment or historical data depth.", "No report-page inventory is available in current gold, so prototype presentation requirements can only be treated as contextual.", "The Target Fields sheet is described by the workbook as authoritative, but workbook authority does not establish business approval or implementation status." ], "report_markdown": "# Workbook-to-current-gold assessment\n\n## Apparent requirement\n\nThe workbook declares a new customer, sales-order and commercial KPI subject area for a discovery workshop and a FY2026\u2013FY2027 planning horizon (`Read Me!B3`, `Read Me!B4`, `Read Me!B6`). It states that the field register contains the requested data objects, while the other sheets are synthetic design illustrations rather than production or reconciliation evidence (`Read Me!B8`, `Read Me!B10`).\n\nThe register contains eight required objects:\n\n- Customer identity, segment and relationship owner.\n- Sales-order identity, gross value before discounts and acquisition channel.\n- Customer Lifetime Value.\n- Gross Order Intake.\n\nThe working sheets additionally imply customer-level and order-level grains, linkage of orders to customers, controlled segment/channel values, and a booked-order KPI view. These are useful design signals, but they are not implementation evidence.\n\n## Current-gold comparison\n\nThe available current-state page describes a six-table Import finance model: `Account`, `Calendar`, `Ledger`, `Metrics`, and two hidden date tables. Its business measures are Actual Net, Actual Revenue, Budget Net and Net Variance. Its relationships connect Ledger to Account and Calendar. No Customer, SalesOrder, customer identifier, order identifier, segment, relationship owner, sales channel, CLV or Gross Order Intake object is documented [fde-finance.current-model].\n\nAccordingly, none of the eight explicitly required workbook objects has a direct or partial mapping in the available discovered landscape. `Ledger.SignedAmount` and `Metrics.Actual Revenue` are monetary finance objects, but their documented meanings do not establish equivalence to gross booked order value or gross order intake. Likewise, the existence of a table named `Metrics` does not map it to the requested `SalesMetrics` measures [fde-finance.current-model].\n\n## Requirement results\n\n| ID | Requirement | Result | Current-gold assessment |\n|---|---|---|---|\n| R1 | CustomerIdentifier | Not found | No Customer entity or enterprise customer identity is documented [fde-finance.current-model]. |\n| R2 | CustomerSegment | Not found | No customer segmentation attribute is documented [fde-finance.current-model]. |\n| R3 | RelationshipOwner | Not found | No customer/account relationship-owner attribute is documented [fde-finance.current-model]. |\n| R4 | OrderIdentifier | Not found | No sales-order entity or customer-order identity is documented [fde-finance.current-model]. |\n| R5 | OrderGrossValue | Not found | `Ledger.SignedAmount` is decimal monetary data, but it is a signed ledger amount rather than documented gross order value before discounts; structural similarity is not semantic equivalence [fde-finance.current-model; fde-finance.evidence-method]. |\n| R6 | SalesChannel | Not found | No order-acquisition channel attribute is documented [fde-finance.current-model]. |\n| R7 | Customer Lifetime Value | Ambiguous | No CLV measure is documented. The workbook calculation is also incomplete because \u201cexpected order frequency\u201d has no defined source, grain, period, or calculation in the extracted text [fde-finance.current-model]. |\n| R8 | Gross Order Intake | Not found | No gross booked-order measure is documented. `Metrics.Actual Revenue` is not enough to infer booked gross intake, and exact current DAX was unavailable [fde-finance.current-model]. |\n| R9 | Customer-to-order analytical association | Not found | The sample order sheet carries CustomerIdentifier, implying order-to-customer analysis, but current gold only documents Ledger-to-Account and Ledger-to-Calendar relationships [fde-finance.current-model]. |\n| R10 | Controlled CustomerSegment and SalesChannel values | Context only | The workbook supplies illustrative code/display lists, but no equivalent dimensions, columns or code sets are documented in current gold [fde-finance.current-model]. |\n| R11 | Booked-order KPI prototype | Context only | The workbook illustrates two metrics in a booked-order view. Current gold inventories model objects but does not establish a corresponding report page or intended report behaviour [fde-finance.current-model]. |\n\n## Important uncertainty\n\n- The result is a bounded non-observation. The gold method explicitly states that no-candidate findings do not prove enterprise-wide absence and should be revalidated if broader estate access or approved source designs become available [fde-finance.evidence-method].\n- Numeric cells and formulas were intentionally excluded. Therefore, sample gross values, metric results, formula implementation and validation outcomes cannot be assessed.\n- The workbook names planned sources\u2014CRM customer master, order management platform and a sales analytics calculation layer\u2014but provides no connection, lineage, keys, refresh, history, currency, discount, cancellation or security design.\n- Although the workbook calls the Target Fields register authoritative, that is a workbook declaration, not evidence that these objects are implemented or approved.\n\n## Recommended discovery focus\n\n1. Locate candidate CRM and order-management semantic models, dataflows, lakehouse/warehouse objects or source specifications outside the currently audited finance model.\n2. Confirm the customer/order grain and key design, especially whether one enterprise customer can have multiple source-system identifiers.\n3. Define commercial event semantics: booked, submitted, accepted, invoiced, cancelled, returned and discounted orders.\n4. Complete the CLV specification, including horizon, expected-frequency source, treatment of margin/discounts/retention, currency and aggregation behaviour.\n5. Confirm whether Gross Order Intake is gross before discounts, and how cancellations, amendments, taxes and currency conversion are handled.\n6. Decide whether segment/channel codes are persisted source codes, conformed dimensions or presentation mappings.", "requirements": [ { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "CustomerIdentifier \u2014 enterprise customer identity", "questions": [ "What system and key-management process define the enterprise customer identifier?", "Must identifiers be historised or cross-referenced across multiple CRM/source systems?" ], "rationale": "The required String column belongs to a Customer entity and is defined as enterprise customer identity. The current model documents Account, Calendar, Ledger and Metrics objects, with no Customer table or customer identifier. AccountKey is a finance account key and is not documented as a customer identity.", "requirement_id": "R1", "source_cells": [ { "coordinate": "A2:I2", "sheet": "Target Fields" } ], "status": "not_found" }, { "confidence": 0.94, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Reference domains for CustomerSegment and SalesChannel", "questions": [ "Are these complete governed domains or merely sample values?", "Where will code-to-display mappings be mastered and maintained?", "Are unknown, other and inactive values required?" ], "rationale": "The workbook supplies code/display pairs for three customer segments and three channels, but the sheet may be illustrative and no equivalent objects are documented in current gold. These values support design discussion but do not independently establish required implementation.", "requirement_id": "R10", "source_cells": [ { "coordinate": "A1:C7", "sheet": "Reference Data" } ], "status": "context_only" }, { "confidence": 0.93, "gold_page_ids": [ "fde-finance.current-model", "fde-finance.evidence-method" ], "label": "Booked-order KPI report behaviour for Gross Order Intake and CLV", "questions": [ "What dimensions, slicers, drill paths and time comparisons are required for the KPI view?", "Should CLV be additive, averaged, or shown only at customer grain?", "Are KPI targets, variance, trends or security-specific views required?" ], "rationale": "The prototype indicates intended display of two amount metrics in a booked-order view, but formulas and numeric outputs were excluded and the workbook says working sheets illustrate behaviour. Current gold inventories semantic-model objects and does not document a corresponding report view, so no implementation mapping can be asserted.", "requirement_id": "R11", "source_cells": [ { "coordinate": "A1:C5", "sheet": "Sales KPI Prototype" }, { "coordinate": "B8", "sheet": "Read Me" } ], "status": "context_only" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "CustomerSegment \u2014 commercial segment", "questions": [ "Are ENT, MID and SMB the governed source codes or only illustrative design values?", "Is segment current-state only, or is historical segment-at-order-date analysis required?" ], "rationale": "No customer segmentation column or equivalent customer entity is present in current gold. AccountType is a finance account classification and cannot be treated as a customer segment.", "requirement_id": "R2", "source_cells": [ { "coordinate": "A3:I3", "sheet": "Target Fields" }, { "coordinate": "A2:C4", "sheet": "Reference Data" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "RelationshipOwner \u2014 accountable customer relationship owner", "questions": [ "Is the required value an employee identifier, display name, team, or all three?", "Should reports use the current owner or the owner effective when an order was booked?" ], "rationale": "No customer relationship-owner, salesperson, account manager or employee attribute is documented in the observed model.", "requirement_id": "R3", "source_cells": [ { "coordinate": "A4:I4", "sheet": "Target Fields" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "OrderIdentifier \u2014 customer order identity", "questions": [ "Is OrderIdentifier unique enterprise-wide or only within an order-management source/company?", "Are order versions, amendments, lines and cancellations represented separately?" ], "rationale": "The available model contains a Ledger fact but no SalesOrder entity or order identifier. No semantic equivalence can be inferred from generic fact-table structure.", "requirement_id": "R4", "source_cells": [ { "coordinate": "A5:I5", "sheet": "Target Fields" } ], "status": "not_found" }, { "confidence": 0.98, "gold_page_ids": [ "fde-finance.current-model", "fde-finance.evidence-method" ], "label": "OrderGrossValue \u2014 gross order value before discounts", "questions": [ "At what grain is OrderGrossValue stored: order header, order line, or derived aggregate?", "Does gross value include tax, freight, amendments, cancelled orders or multi-currency conversion?", "If value is before discounts, is a separate discount/net-order-value requirement expected?" ], "rationale": "Current gold contains Ledger.SignedAmount as a Decimal monetary column, but it is documented as a signed ledger amount. The requested field is gross customer-order value before discounts. Matching data types and monetary character do not establish semantic equivalence.", "requirement_id": "R5", "source_cells": [ { "coordinate": "A6:I6", "sheet": "Target Fields" }, { "coordinate": "A2:D3", "sheet": "Sales Orders" } ], "status": "not_found" }, { "confidence": 0.99, "gold_page_ids": [ "fde-finance.current-model" ], "label": "SalesChannel \u2014 order acquisition channel", "questions": [ "Are DIR, PAR and ONL governed codes or illustrative values?", "Can channel change after booking, and are mixed-channel orders possible?" ], "rationale": "No sales-channel or acquisition-channel column is documented in the current model. The workbook's Direct, Partner and Online values have no observed counterpart.", "requirement_id": "R6", "source_cells": [ { "coordinate": "A7:I7", "sheet": "Target Fields" }, { "coordinate": "A5:C7", "sheet": "Reference Data" } ], "status": "not_found" }, { "confidence": 0.97, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Customer Lifetime Value measure", "questions": [ "What is the approved CLV business definition and prediction horizon?", "How is expected order frequency calculated or sourced?", "Is CLV revenue-based or margin-based, and does it include retention/churn, discounting and customer acquisition cost?", "At what date and customer grain must CLV be evaluated?" ], "rationale": "No CLV measure or customer/order model is documented in current gold. The workbook defines CLV as average gross order value multiplied by expected order frequency, but expected order frequency, time horizon, customer grain and treatment of retention/margin are not specified in the extracted text. The prototype further labels the multiplier illustrative for discovery only.", "requirement_id": "R7", "source_cells": [ { "coordinate": "A8:I8", "sheet": "Target Fields" }, { "coordinate": "A3:C5", "sheet": "Sales KPI Prototype" } ], "status": "ambiguous" }, { "confidence": 0.98, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Gross Order Intake measure", "questions": [ "Which order status/event makes value count as intake?", "How should cancellations, returns, amendments and duplicate bookings affect the measure?", "What currency and booking-date rules apply?" ], "rationale": "The requested measure is defined as sum of OrderGrossValue and gross booked order value. Current gold has Actual Revenue and SignedAmount, but neither is documented as gross booked order intake. Exact current DAX was not available, further preventing semantic validation.", "requirement_id": "R8", "source_cells": [ { "coordinate": "A9:I9", "sheet": "Target Fields" }, { "coordinate": "A3:C4", "sheet": "Sales KPI Prototype" } ], "status": "not_found" }, { "confidence": 0.96, "gold_page_ids": [ "fde-finance.current-model" ], "label": "Customer-to-sales-order association and analytical grain", "questions": [ "Is the intended relationship one customer to many order headers?", "Are guest, prospect, merged or unidentified customers allowed on orders?", "Is line-level analysis required even though the prototype is order-level?" ], "rationale": "The sample metadata shows customer-level records and order-level records carrying CustomerIdentifier, implying a customer-to-many-orders association needed for customer analytics and CLV. Current gold documents Ledger relationships to Account and Calendar only; there is no Customer-to-SalesOrder relationship.", "requirement_id": "R9", "source_cells": [ { "coordinate": "A1:C3", "sheet": "Customer Sample" }, { "coordinate": "A1:D3", "sheet": "Sales Orders" } ], "status": "not_found" } ], "review_flags": [ { "priority": 1, "queue_name": "client_question", "reason": "Customer Lifetime Value is required but its frequency input, horizon, grain and commercial definition are incomplete; this blocks reliable modelling and acceptance criteria.", "subject": "R7" }, { "priority": 2, "queue_name": "client_question", "reason": "Gross Order Intake needs explicit booking-event, cancellation, amendment, discount, tax and currency rules.", "subject": "R8" }, { "priority": 3, "queue_name": "mapping", "reason": "Locate the intended customer and order sources/models and validate customer-to-order keys and grain beyond the currently audited finance model.", "subject": "R9" }, { "priority": 4, "queue_name": "evidence_research", "reason": "Search broader CRM and master-data evidence for the enterprise customer identifier and identity-resolution design.", "subject": "R1" }, { "priority": 5, "queue_name": "evidence_research", "reason": "Search order-management evidence for order header/line/version structures and identifiers.", "subject": "R4" }, { "priority": 6, "queue_name": "scope", "reason": "Confirm whether the eight Target Fields rows are the complete approved MVP scope or only an initial discovery subset; common date, currency, status and order-line requirements are absent.", "subject": "workbook" }, { "priority": 7, "queue_name": "client_question", "reason": "Clarify gross-value grain and inclusion rules, including discount, tax, freight, cancellation and currency handling.", "subject": "R5" }, { "priority": 8, "queue_name": "client_question", "reason": "Confirm whether customer segment needs effective-dated history and whether the listed codes are governed.", "subject": "R2" }, { "priority": 9, "queue_name": "client_question", "reason": "Confirm relationship-owner identifier, hierarchy and effective-date requirements.", "subject": "R3" }, { "priority": 10, "queue_name": "consultant_review", "reason": "Determine whether reference codes are authoritative master data, a semantic-model dimension, or illustrative presentation mappings.", "subject": "R10" }, { "priority": 11, "queue_name": "client_question", "reason": "Elicit report interactions, dimensions, time analysis, targets, drill-through and metric aggregation behaviour.", "subject": "R11" }, { "priority": 12, "queue_name": "revalidation", "reason": "Re-run the comparison when broader estate discovery, source specifications or a later semantic-model snapshot becomes available.", "subject": "current-gold boundary" } ], "summary": "The workbook appears to define a planned FY2026\u2013FY2027 customer and booked-sales-order analytics subject area, with six required attributes and two required commercial measures. It also implies a customer-to-order analytical grain, controlled values for customer segment and sales channel, and a prototype booked-order KPI view. Against the available current-gold boundary, no direct or partial business-semantic mappings were found. The observed current model is a finance-ledger model containing Account, Calendar, Ledger and Metrics objects; none of the requested Customer, SalesOrder or SalesMetrics objects are present. Superficial similarities\u2014decimal monetary fields, a generic Metrics table, and a fact-to-dimension relationship pattern\u2014are insufficient to establish mappings. Customer Lifetime Value is additionally ambiguous as specified because its declared calculation refers to an expected order frequency that is not itself defined in the extracted text." }