Connect · systems of record
Term register
Every figure this platform publishes rests on a word, and a word is only worth what the estate agrees it means. This register holds one definition per term, the person who signed it, the system that is its book of record, the local fields bound to it, and the places where two systems use the same word for two different populations. No verdict below is written into the data. Each one is derived when this page loads, from whether a book of record is named, whether that system can be reached, whether every binding under the term matches, and whether a disagreement is still open.
Health
What the estate agrees on
Terms by the strongest claim the record supports behind each one.
The register
22 terms. Each row is a word, its owner, the system that holds it and the state this page derived on load.
| Term | Domain | Chair | Book of record | Approved by | Bindings | Fields | State |
|---|---|---|---|---|---|---|---|
| Revenue Net revenue · Top line · Booked revenue · Sales | Finance | cfo | Group ERP — Financials | Ines Baumann | 2 / 4 | 13 | Contested |
| Customer Account · Client · Payer · Sold-to party | Commercial | cro | Customer Relationship Management | Nobody | 1 / 4 | 6 | Contested |
| Supplier Vendor · Trading partner · Payee | Procurement | cpo | Source-to-Pay Suite | Marta Oyelaran | 1 / 3 | 6 | Contested |
| Open purchase order Open PO · Committed spend · Outstanding commitment | Procurement | cpo | Group ERP — Materials and Inventory | Marta Oyelaran | 2 / 3 | 6 | Agreed |
| Supplier invoice AP invoice · Payable · Vendor bill | Procurement | cfo | Invoice Capture and AP Automation | Nobody | 1 / 3 | 10 | Proposed |
| Cash position Cash balance · Available cash · Liquidity | Treasury | cfo | Treasury and Cash Management | Nobody | 1 / 3 | 4 | Proposed |
| Applied exchange rate FX rate · Translation rate · Conversion rate | Finance | cfo | Group ERP — Financials | Ines Baumann | 1 / 3 | 7 | Agreed |
| Cost center Cost centre · Department code · Responsibility center | Finance | cfo | Planning and Consolidation | Nobody | 1 / 3 | 5 | Proposed |
| Headcount Heads · People count · Staff numbers | People | chro | Core HR and Payroll | Nobody | 1 / 3 | 7 | Proposed |
| Full-time equivalent FTE · Effort · Capacity | People | chro | Core HR and Payroll | Nobody | 1 / 3 | 7 | Contested |
| Contract Agreement · Master agreement · Paper | Legal | cco | Contract Lifecycle Management | Peter Vandermolen | 2 / 3 | 5 | Agreed |
| Incident Outage · Ticket · Failure | Technology | cio | IT Service Management | Nobody | 1 / 3 | 6 | Contested |
| Service level SLA · Target · Commitment | Operations | coo | None named | Nobody | 0 / 3 | 6 | Unbacked |
| Transaction Item · Unit of work · Volume | Operations | coo | Enterprise Data Warehouse | Nobody | 1 / 3 | 5 | Contested |
| Lead time Replenishment time · Supply time | Supply | cpo | Supply and Demand Planning | Nobody | 1 / 3 | 9 | Contested |
| On-hand inventory Stock · Inventory · Available quantity | Supply | cpo | Group ERP — Materials and Inventory | Nobody | 1 / 3 | 11 | Proposed |
| Pipeline Funnel · Open opportunity value · Coverage | Commercial | cro | Customer Relationship Management | Nobody | 1 / 3 | 6 | Contested |
| Discount Concession · Price reduction · Off-list | Commercial | cro | Configure, Price and Quote | Devon Achebe | 1 / 3 | 5 | Agreed |
| Part revision in force Current revision · Released revision · Rev level | Engineering | cto | Product Lifecycle Management | Hiroshi Tanabe | 1 / 3 | 4 | Agreed |
| Configuration item CI · Asset · Service component | Technology | cio | Configuration Management Database | Nobody | 1 / 3 | 5 | Proposed |
| Tower operating cost Run cost · Cost to serve · Tower cost | Operations | cfo | Group ERP — Financials | Nobody | 1 / 3 | 7 | Contested |
| Reported measure Metric · KPI · Measure | Analytics | cfo | Reporting Semantic Layer | Nobody | 1 / 3 | 3 | Contested |
Operations
One term at a time
The definition, the reason a system was named as its book of record, every local field bound to it, and what breaks if the word is read the wrong way.
Revenue
Finance · owned by the CFO chair · finance, sales, revenue-operations
Consideration recognized against a performance obligation that has been satisfied, net of credits, rebates and returns provisions, stated in the reporting currency at the rate applied on the posting date.
The general ledger is the only system whose figure is signed off at period close and carried into the statutory statements. Every other system holds a working view of the same idea.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-REV-01 | Group ERP — Financials | Revenue account balance | Posted line, legal entity, periodReporting currency | Sum of accounts in the revenue range, net of credit memos and the returns provision, at the posting-date rate. | Matches |
| TB-REV-02 | Customer Relationship Management | Closed won value | Opportunity, close dateDeal currency | Sum of opportunity amounts whose stage is closed won and whose close date falls in the period. | Differs |
| TB-REV-03 | Planning and Consolidation | Revenue plan line | Entity, product family, monthPlan currency at plan rate | Plan value spread across months by the seasonality profile attached to the product family. | Differs |
| TB-REV-04 | Enterprise Data Warehouse | Revenue fact table | Posted line, entity, periodReporting currency | Copy of the ledger extract with the same netting applied downstream. | Matches |
Finance close and consolidation workflows, the revenue operations forecast agents, and every benefit line that expresses a saving as a share of revenue.
2 of 2 declared fact keys appear in the lineage record, across 270 lineage facts, 0 of them below 0.7 confidence. Those facts reach 2 connector contracts carrying 13 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Customer
Commercial · owned by the CRO chair · sales, marketing, revenue-operations, customer-service
A legal entity that has, or is being pursued to have, a contractual relationship to buy. Sites, divisions and billing addresses belonging to that entity are not separate customers.
Commercial coverage, territory and pipeline all hang off the account record, so the customer relationship system holds the widest population. That is a reason of convenience rather than authority, and it is contested.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-CUS-01 | Customer Relationship Management | Account | Account record with a global parent linkCount of accounts | Accounts of type customer, rolled to the ultimate parent through the hierarchy field. | Matches |
| TB-CUS-02 | Group ERP — Financials | Payer master record | Payer per company codeCount of payers | Distinct payer numbers with at least one open item. | Differs |
| TB-CUS-03 | Contact Center Platform | Contact | Individual callerCount of people | Distinct verified callers in the period. | Differs |
| TB-CUS-04 | Contract Lifecycle Management | Counterparty | Signing legal entityCount of counterparties | Distinct signing entities on executed customer contracts. | Differs |
Territory and coverage agents, service routing in the contact center, credit exposure checks in finance, and the customer-impact test that decides escalation tier.
2 of 2 declared fact keys appear in the lineage record, across 306 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 6 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Supplier
Procurement · owned by the CPO chair · procurement, supply-chain, finance
A legal entity onboarded through supplier qualification and holding at least one active category assignment. A remit-to bank record is an attribute of a supplier, not a supplier.
Qualification, category assignment and the risk questionnaire all live in the source-to-pay suite, and nothing may be paid without a record there.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-SUP-01 | Source-to-Pay Suite | Supplier profile | Onboarded supplier, globalCount of suppliers | Profiles in an active or conditionally active onboarding state. | Matches |
| TB-SUP-02 | Group ERP — Materials and Inventory | Vendor master | Vendor per company code and purchasing organizationCount of vendor records | Vendor records not flagged for deletion. | Differs |
| TB-SUP-03 | Invoice Capture and AP Automation | Remit-to party | Bank remittance destinationCount of remit-to parties | Distinct remittance destinations used in the period. | Differs |
Supplier onboarding and requalification workflows, duplicate payment checks, third-party risk scoring, and the concentration figures shown on the procurement desk.
1 of 1 declared fact key appears in the lineage record, across 134 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 6 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Open purchase order
Procurement · owned by the CPO chair · procurement, supply-chain, finance
A released purchase order with remaining value greater than zero and no closure flag, measured as ordered value less the greater of goods received and invoiced value.
The materials module holds the released order and the goods receipt against it, so the residual can be computed there without joining across systems.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-OPO-01 | Group ERP — Materials and Inventory | Open purchase order line | Purchase order lineGroup currency | Ordered value less receipted value on lines not flagged as complete. | Matches |
| TB-OPO-02 | Source-to-Pay Suite | Order in flight | Purchase order headerGroup currency | Header value of orders dispatched to the supplier and not closed. | Differs |
| TB-OPO-03 | Group ERP — Financials | Purchase commitment | Commitment item on the cost objectGroup currency | Commitment balance carried against the cost center or project. | Matches |
Commitment reporting, the accrual proposal agents at period close, and the maverick-spend detection that compares invoices against released orders.
1 of 1 declared fact key appears in the lineage record, across 136 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 6 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Supplier invoice
Procurement · owned by the CFO chair · finance, procurement
A demand for payment received from a qualified supplier, counted once from the moment it is captured, whether or not it has been coded, matched or posted.
Capture happens at the automation layer, which is the first point at which the document exists in the estate. The ledger only ever sees the ones that pass matching.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-INV-01 | Invoice Capture and AP Automation | Captured invoice | Invoice documentCount and gross value | Documents captured, from the timestamp of capture, whatever their downstream state. | Matches |
| TB-INV-02 | Group ERP — Financials | Vendor invoice document | Posted accounting documentGroup currency | Documents that have posted, from the posting date. | Differs |
| TB-INV-03 | Indirect Tax Engine | Taxable inbound document | Invoice lineNet and tax amount | Lines carrying a tax treatment, exploded from the document. | Differs |
Invoice capture, three-way match and exception routing workflows, the duplicate detection control, and every payables cycle-time figure on the transaction desks.
2 of 2 declared fact keys appear in the lineage record, across 285 lineage facts, 0 of them below 0.7 confidence. Those facts reach 2 connector contracts carrying 10 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Cash position
Treasury · owned by the CFO chair · finance
Bank-confirmed cleared balances across all in-scope accounts at a stated cut-off, before any adjustment for items in transit or intraday sweeps.
The treasury system is where account structures and sweep rules are held. It is named as the book of record even though the bank gateway that would confirm the balances is not connected.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-CSH-01 | Treasury and Cash Management | Cash position | Bank account, value dateGroup currency | Cleared balances by value date, translated at the closing rate. | Matches |
| TB-CSH-02 | Bank Connectivity Gateway | Statement balance | Bank account, statement dateAccount currency | Closing balance as stated by the bank. | Differs |
| TB-CSH-03 | Group ERP — Financials | Bank clearing account | General ledger accountReporting currency | Ledger balance on the bank and clearing accounts. | Differs |
Daily liquidity reporting, the payment run release check, and the working capital figures carried on the finance desk.
1 of 1 declared fact key appears in the lineage record, across 142 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 4 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Applied exchange rate
Finance · owned by the CFO chair · finance
The rate actually used to translate a transaction into the reporting currency, being the daily rate loaded to the ledger on the posting date, not the rate at invoice date and not a period average.
The rate that matters is the one the ledger applied, because that is the number that survives into the statements. Any other source describes what the rate could have been.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-FXR-01 | Group ERP — Financials | Daily translation rate | Currency pair, posting dateRate to six decimal places | The rate loaded for the posting date and used on the document. | Matches |
| TB-FXR-02 | Treasury and Cash Management | Deal rate | Individual dealRate to six decimal places | The rate actually contracted on a hedge or a spot deal. | Differs |
| TB-FXR-03 | Planning and Consolidation | Plan rate | Currency pair, plan versionRate to four decimal places | The rate fixed for the plan version and held flat for the year. | Differs |
Consolidation, intercompany elimination, and every agent that restates a local figure into the reporting currency.
1 of 1 declared fact key appears in the lineage record, across 124 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 7 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Cost center
Finance · owned by the CFO chair · finance, administration
The smallest unit of the organization to which spend is charged and for which a named manager carries a budget. It is a planning object, not a legal entity and not a team.
The planning and consolidation system holds the hierarchy that budgets are set against, and the ledger inherits its codes from there rather than the other way round.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-CCT-01 | Planning and Consolidation | Cost center node | Node in the planning hierarchyCount of nodes | Nodes valid in the current plan version. | Matches |
| TB-CCT-02 | Group ERP — Financials | Cost center master | Cost center per controlling areaCount of masters | All masters, including those closed to new postings. | Differs |
| TB-CCT-03 | Core HR and Payroll | Position cost assignment | Position, effective dateCount of assignments | The cost center attached to a position at a date. | Differs |
Budget checks before commitment, allocation of shared service charges, and the cost-per-tower figures on the transaction desks.
1 of 1 declared fact key appears in the lineage record, across 138 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 5 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Headcount
People · owned by the CHRO chair · human-resources, finance
A count of individual workers holding an active employment contract with a group entity on the measurement date. One person holding two contracts counts once.
The core human resources system holds the contract, which is the thing being counted. Nothing else in the estate knows when a contract starts or ends.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-HDC-01 | Core HR and Payroll | Active worker count | Person, effective dateCount of people | Persons on an employment contract with the group, active at the date. | Matches |
| TB-HDC-02 | Workforce Management | Scheduled resource count | Person on a rosterCount of people | Distinct persons appearing on a published roster in the week. | Differs |
| TB-HDC-03 | Recruiting and Applicant Tracking | Accepted offer | Candidate with a signed offerCount of offers | Offers accepted and not withdrawn. | Differs |
Workforce planning, cost-to-serve modeling, span-of-control reporting, and the productivity denominators used across the transaction towers.
1 of 1 declared fact key appears in the lineage record, across 144 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 7 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Full-time equivalent
People · owned by the CHRO chair · human-resources, finance, ai-gbs
Contracted hours for a population divided by the standard full-time hours for the country in which those hours are worked. It measures contracted capacity, not hours actually worked.
Contracted hours and country standards both sit in the core human resources system, so the ratio can be formed there without an assumption.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-FTE-01 | Core HR and Payroll | Contracted effort | Person, country, periodEquivalent persons | Contracted hours divided by the country standard for full time. | Matches |
| TB-FTE-02 | Workforce Management | Rostered effort | Roster line, weekEquivalent persons | Scheduled hours divided by a fixed forty-hour week. | Differs |
| TB-FTE-03 | Planning and Consolidation | Budgeted establishment | Cost center, plan versionEquivalent persons | Approved establishment held in the plan, filled or not. | Differs |
The 2,219 figure carried on the transaction towers, workforce cost modeling, benefit lines expressed as effort released, and every capacity comparison between towers.
2 of 2 declared fact keys appear in the lineage record, across 290 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 7 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Contract
Legal · owned by the CCO chair · legal, procurement, sales
A signed instrument creating enforceable obligations between a group entity and a counterparty. Amendments, statements of work and order forms are documents within a contract, not contracts of their own.
The contract lifecycle system holds the executed instrument and the obligation extract taken from it, which is what downstream obligations are tracked against.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-CTR-01 | Contract Lifecycle Management | Contract family | Parent instrument with amendmentsCount of families | Executed parents, with amendments and order forms rolled into the parent. | Matches |
| TB-CTR-02 | Document and Matter Management | Filed agreement document | DocumentCount of documents | Documents filed under an agreement matter type. | Differs |
| TB-CTR-03 | Source-to-Pay Suite | Supplier agreement | Agreement with its amendmentsCount of agreements | Executed supplier agreements, amendments rolled to the parent. | Matches |
Obligation tracking, renewal and expiry workflows, clause position reporting, and the contractual basis checks that gate several controls.
2 of 2 declared fact keys appear in the lineage record, across 294 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 5 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Incident
Technology · owned by the CIO chair · information-technology, customer-service
An unplanned interruption to a service, or a reduction in its quality, raised as a record and worked until service is restored. Restoration ends the incident; the cause may still be open.
The service management system is where a record is raised, prioritized and closed, so the population and its clock both exist in one place.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-INC-01 | IT Service Management | Incident record | Record from raise to restorationCount of records | Records of type incident, any priority. | Matches |
| TB-INC-02 | Contact Center Platform | Escalated contact | Contact flagged by an agentCount of contacts | Contacts an agent marked as a service failure. | Differs |
| TB-INC-03 | Configuration Management Database | Service in degraded state | ServiceCount of services | Services whose state is other than operational. | Differs |
Service reporting, the incident registers on the function pages, availability arguments, and the sixteen agentic failure records this platform keeps under the same word without ever having reconciled the two populations.
2 of 2 declared fact keys appear in the lineage record, across 298 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 6 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Service level
Operations · owned by the COO chair · ai-gbs, administration, customer-service
A stated threshold a service is expected to meet, together with the measurement window it is judged over and the consequence of missing it.
No system holds this. The platform carries 28 service levels and 12 of them have no function attached, while the thresholds themselves live in contract text, vendor portals and spreadsheets that nobody has reconciled to one another. Naming a book of record here would be an assertion, not a fact.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-SVL-01 | IT Service Management | Resolution target | Priority bandHours to restore | Target hours by priority, measured in business hours in the region of the raiser. | Differs |
| TB-SVL-02 | Contract Lifecycle Management | Contractual service commitment | Clause in a contractFree text with a number in it | Extracted from the service schedule at contract load. | Differs |
| TB-SVL-03 | Contact Center Platform | Answer target | QueueSeconds to answer | Percentage of contacts answered within a threshold, per queue. | Differs |
Breach counts on every chair desk, the service level panels on the function pages, vendor performance conversations, and several escalation triggers.
1 of 1 declared fact key appears in the lineage record, across 163 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 6 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Transaction
Operations · owned by the COO chair · ai-gbs, finance
One completed unit of processing work counted at the point it leaves the tower that performed it. A single business document may produce several transactions if several towers touch it.
The warehouse is the only place the batches from every tower land together, so it is the only place a single count can be formed at all. It is not an authority on what should be counted.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-TRX-01 | Enterprise Data Warehouse | Processed item fact | Completed unit, tower, weekCount per week | Batches landed from each tower, summed. | Matches |
| TB-TRX-02 | Group ERP — Financials | Document posting | Accounting documentCount of documents | Documents posted in the period. | Differs |
| TB-TRX-03 | IT Service Management | Fulfilled request | Request recordCount of requests | Service requests closed as fulfilled. | Differs |
The declared throughput figure, tower volumes, unit cost, and the summed figure this platform publishes alongside the declared one because the two do not agree.
1 of 1 declared fact key appears in the lineage record, across 203 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 5 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Lead time
Supply · owned by the CPO chair · supply-chain, procurement
Elapsed calendar time from the moment a replenishment need is confirmed to the moment the goods are receipted and available to use.
Planning holds both ends of the clock, the confirmed need and the receipt signal, so the elapsed figure can be formed without joining across systems.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-LDT-01 | Supply and Demand Planning | Planned replenishment lead time | Material, receiving locationCalendar days | Confirmed need date to goods available date. | Matches |
| TB-LDT-02 | Transportation Management | Transit time | Lane, carrierCalendar days | Pickup to delivery on the lane. | Differs |
| TB-LDT-03 | Group ERP — Materials and Inventory | Material master lead time | Material, plantWorking days | Static value maintained on the material master. | Differs |
Replenishment parameters, availability commitments to customers, supplier scorecards, and the working capital argument for inventory held.
2 of 2 declared fact keys appear in the lineage record, across 283 lineage facts, 0 of them below 0.7 confidence. Those facts reach 2 connector contracts carrying 9 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
On-hand inventory
Supply · owned by the CPO chair · supply-chain
Physical quantity present at a location and owned by the group, before any commitment against it is deducted.
The materials system is where a movement is posted, so it is the only record that changes when the physical position changes.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-OHI-01 | Group ERP — Materials and Inventory | Unrestricted stock | Material, storage locationBase unit of measure | Quantity posted to unrestricted use. | Matches |
| TB-OHI-02 | Supply and Demand Planning | Available to promise | Material, location, dateBase unit of measure | On hand less committed demand within the horizon. | Differs |
| TB-OHI-03 | Enterprise Data Warehouse | Inventory snapshot | Material, location, dayBase unit of measure | Daily snapshot taken at the close of the reporting day. | Differs |
Availability checks, inventory value in the ledger, planning inputs, and the inventory element of the working capital position.
2 of 2 declared fact keys appear in the lineage record, across 272 lineage facts, 0 of them below 0.7 confidence. Those facts reach 2 connector contracts carrying 11 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Pipeline
Commercial · owned by the CRO chair · sales, revenue-operations, marketing
The sum of expected values of opportunities that are open, have a named customer and a close date in the period being reported. Opportunities without a close date are excluded and reported separately.
The customer system holds the opportunity record, its stage and its close date, which are the three things the definition depends on.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-PIP-01 | Customer Relationship Management | Open opportunity value | Opportunity, close periodGroup currency | Open opportunities with a named account and a close date in the period. | Matches |
| TB-PIP-02 | Marketing Automation | Influenced pipeline | Opportunity touched by a programGroup currency | Full opportunity value credited to every program that touched it. | Differs |
| TB-PIP-03 | Configure, Price and Quote | Live quote value | QuoteQuote currency | Quotes issued and not expired. | Differs |
Coverage ratios, forecast conversations, marketing contribution claims, and the revenue positions carried on the commercial chair desk.
3 of 3 declared fact keys appear in the lineage record, across 485 lineage facts, 166 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 6 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Discount
Commercial · owned by the CRO chair · sales, revenue-operations
The difference between the list price in force at the moment of quotation and the price actually quoted, expressed as a percentage of list. Rebates settled after invoice are not discounts.
The quoting system holds the price book version that was in force when the quote was made, which is the denominator the definition requires.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-DSC-01 | Configure, Price and Quote | Line discount percentage | Quote linePercentage of list | List price in the price book version in force at quotation, less quoted price, over list. | Matches |
| TB-DSC-02 | Group ERP — Financials | Sales deduction | Billing document lineGroup currency | Deduction accounts netted against gross revenue. | Differs |
| TB-DSC-03 | Customer Relationship Management | Deal discount field | Opportunity headerPercentage typed by a person | Whatever the owner entered on the header. | Differs |
Approval thresholds in the quote workflow, margin reporting, the duty conflict checks on pricing authority, and several agent recommendations on deal desk cases.
2 of 2 declared fact keys appear in the lineage record, across 316 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 5 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Part revision in force
Engineering · owned by the CTO chair · engineering, supply-chain
The revision of a part that has been released for manufacture and whose effectivity date has passed. A revision that is approved but not yet effective is not in force.
Release and effectivity are both recorded in the product lifecycle system, and the definition turns on the pair of them.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-PRV-01 | Product Lifecycle Management | Released revision | Part, effectivity dateRevision identifier | Latest revision released with an effectivity date that has passed. | Matches |
| TB-PRV-02 | Group ERP — Materials and Inventory | Material revision level | Material, plantRevision identifier | Revision copied across when the change order is released to manufacturing. | Differs |
| TB-PRV-03 | Document and Matter Management | Filed drawing revision | Drawing documentRevision identifier | Highest revision filed against the part. | Differs |
Manufacturing release, purchasing specifications sent to suppliers, change order impact, and the engineering positions on the technology chair desk.
2 of 2 declared fact keys appear in the lineage record, across 348 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 4 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Configuration item
Technology · owned by the CIO chair · information-technology, engineering
A component under change control whose failure would affect a service, together with a named owner and the services that depend on it.
The configuration database is the only place ownership and dependency are held together, although it is currently the stalest source in the estate, which weakens everything derived from it.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-CFG-01 | Configuration Management Database | Configuration item | Component with an ownerCount of items | Items under change control with a named owner and at least one service dependency. | Matches |
| TB-CFG-02 | IT Service Management | Affected item reference | Free-text field on a ticketCount of distinct strings | Whatever was typed into the affected item field. | Differs |
| TB-CFG-03 | Group ERP — Financials | Fixed asset | Asset numberCount of assets | Capitalized assets in the technology asset classes. | Differs |
Change risk assessment, incident impact, dependency mapping on the technology pages, and the recovery scope used in drills.
2 of 2 declared fact keys appear in the lineage record, across 314 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 5 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Tower operating cost
Operations · owned by the CFO chair · ai-gbs, finance
Direct cost of running a transaction tower for a week, comprising people, inference and the licenses consumed by that tower alone. Allocated corporate overhead is excluded.
The ledger holds the money, but it has no tower dimension. The mapping from cost center to tower is maintained by hand outside every system in this estate, so the book of record answers only half the question.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-TOC-01 | Group ERP — Financials | Cost center actual | Cost center, periodGroup currency | Actual postings on the cost centers a spreadsheet maps to the tower. | Differs |
| TB-TOC-02 | Planning and Consolidation | Tower plan cost | Tower node, plan versionGroup currency | Planned cost at the tower node, inclusive of allocated corporate overhead. | Differs |
| TB-TOC-03 | Core HR and Payroll | Tower people cost | Position, tower assignmentGroup currency | Fully loaded people cost for positions assigned to the tower. | Matches |
The weekly run cost figure, unit cost per transaction, the inference share, and every benefit line expressed as cost avoided.
2 of 2 declared fact keys appear in the lineage record, across 366 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 7 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Reported measure
Analytics · owned by the CFO chair · finance, revenue-operations
A named calculation published to a reporting audience, comprising a formula, the population it runs over and the period it covers. Two calculations that differ in any of the three are two measures, not one.
The reporting semantic layer exists to hold measure definitions, which makes it the obvious book of record and also the sharpest irony in this register: the estate already runs a system whose entire product is meaning, and this register does not govern it.
| Ref | System | Local name | Local grain and unit | Rule | Match |
|---|---|---|---|---|---|
| TB-RPM-01 | Reporting Semantic Layer | Semantic measure | Measure definitionVaries | Formula, population and period held together as one governed object. | Matches |
| TB-RPM-02 | Enterprise Data Warehouse | Warehouse calculation | View or columnVaries | Calculation written into a view, sometimes duplicating one that already exists in the semantic layer. | Differs |
| TB-RPM-03 | Digital Analytics | Digital metric | Session or eventVaries | Metric computed at session grain inside the analytics product. | Differs |
Every figure published to a board pack or a chair desk that was not read straight from a source system, including several on this platform.
1 of 1 declared fact key appears in the lineage record, across 203 lineage facts, 0 of them below 0.7 confidence. Those facts reach 1 connector contract carrying 3 fields. None of those contracts is live, so the binding describes an intended read rather than an observed one.
Actions
Where two systems mean different things
Every disagreement on the register, in full. Nothing here is summarized to a count, because a count is not something anybody can settle.
TD-01 · Revenue
timing disagreement · raised by Ines Baumann 160 days ago · owned by the CFO chair
Revenue arises when the performance obligation is satisfied and the entry posts.
Revenue arises when the opportunity is marked closed won.
TD-02 · Customer
grain disagreement · raised by Devon Achebe 180 days ago · owned by the CRO chair
A customer is a buying organization rolled to its ultimate parent.
A customer is a payer, and a payer exists once per company code.
TD-03 · Customer
scope disagreement · raised by Yolanda Prieto 138 days ago · owned by the CRO chair
A customer is an organization.
A customer is the person on the line.
TD-04 · Supplier
scope disagreement · raised by Marta Oyelaran 208 days ago · owned by the CPO chair
A supplier is the legal entity contracted to supply.
A supplier is whoever the money is sent to.
TD-05 · Full-time equivalent
unit disagreement · raised by Anneke de Vries 141 days ago · owned by the CHRO chair
Contracted hours over the country standard for full time.
Scheduled hours over a fixed forty-hour week.
TD-06 · Incident
scope disagreement · raised by Rashid Malouf 96 days ago · owned by the CIO chair
An incident is a service interruption raised as a ticket by a person.
An incident is one of the sixteen agentic failure records this platform keeps.
TD-07 · Transaction
inclusion disagreement · raised by Ines Baumann 172 days ago · owned by the COO chair
A transaction is a completed unit landed from a tower into the warehouse.
A transaction is whatever each tower declares it processed.
TD-08 · Service level
scope disagreement · raised by Rashid Malouf 119 days ago · owned by the COO chair
The target is the resolution time held against the priority band.
The target is the number written into the service schedule of the contract.
TD-09 · Lead time
unit disagreement · raised by Tomas Lindqvist 166 days ago · owned by the CPO chair
Elapsed calendar days from confirmed need to goods available.
Working days maintained on the material master.
TD-10 · Pipeline
inclusion disagreement · raised by Devon Achebe 82 days ago · owned by the CRO chair
Each opportunity counts once, at its expected value.
Each program that touched an opportunity is credited with its full value.
TD-13 · Tower operating cost
inclusion disagreement · raised by Ines Baumann 70 days ago · owned by the CFO chair
Direct cost only, mapped to towers by a spreadsheet held outside every system.
Cost at the tower node inclusive of allocated corporate overhead.
TD-14 · Reported measure
grain disagreement · raised by Ines Baumann 106 days ago · owned by the CFO chair
A measure is one governed object holding formula, population and period together.
A measure is whatever the view computes, and several views compute the same one.
TD-11 · Supplier invoice
timing disagreement · raised by Marta Oyelaran 215 days ago · owned by the CFO chair
An invoice exists from the moment it is captured, whatever happens to it afterwards.
An invoice exists once it has posted.
TD-12 · Applied exchange rate
timing disagreement · raised by Ines Baumann 191 days ago · owned by the CFO chair
The rate applied is the daily rate at the posting date.
The rate applied is the plan rate fixed for the year.
Live observability
Words an agent acts on that nobody ever defined
Not authored. This is a scan of prose already stored in the estate, counting whole-word matches for phrases that gate a decision without stating a threshold.
Undefined phrases in use
6 phrases found, 359 occurrences, in a scan of 5,842 stored records across the policy, strategy, escalation, decision, control, workflow, mandate, agent, work, failure, duty, service level, queue and remediation registers.
| Phrase | Found | Where | Nearest defined term | Why it matters |
|---|---|---|---|---|
| material | 4 | agent roles 1 · work in flight 1 · duty conflicts 1 · human queue 1 | None on the register | Carries a precise accounting meaning and a loose everyday one. Where it gates an approval, two readers can reach opposite conclusions and both be reasonable. |
| at risk | 8 | work in flight 6 · service levels 2 | None on the register | Names a state with no entry or exit condition. Items enter this state by judgment and leave it the same way. |
| customer impact | 2 | work in flight 2 | Customer | Rests on a word two systems already count differently. Impact on organizations and impact on people are not the same population. |
| critical | 90 | work in flight 80 · strategy positions 2 · escalations 2 · sub-function mandates 2 · human queue 2 · agent roles 1 · duty conflicts 1 | Incident | Overlaps a priority band that does have a definition, which makes the loose use harder to spot rather than easier. |
| exception | 254 | strategy positions 218 · work in flight 11 · agent roles 6 · duty conflicts 6 · human queue 4 · workflow register 3 · sub-function mandates 3 · remediation register 2 · policy register 1 | None on the register | Names a population that several registers count differently and none define. Exception rates are quoted without stating what fell into the numerator. |
| in scope | 1 | service levels 1 | None on the register | Scope statements refer to it without ever bounding it, so the same control can be read narrowly or broadly by the same reader on different days. |
Is policy and strategy coming to fruition
What the register does not settle
Four things this page found that a reader would otherwise take the wrong way.
Approved and still contested
Approval settles the wording. It does not settle the disagreement.
Terms with nowhere to go
No book of record, or one that cannot be read.
What this page still does not prove
Read before quoting anything above.
Coverage. The register holds 22 terms. The estate runs on far more words than that, and every word nobody nominated is absent from this page and therefore looks fine. 1 of 26 sourcesystems carries no binding here at all, which means this register says nothing about it rather than that it agrees.
Enforcement. Nothing on this page changes what a system computes. There is no check anywhere in the estate that fails when a report uses a word its own way, and no agent is prevented from doing so. The definitions are a statement of intent held next to systems that have not been altered to match.
Independence. Every approval on this register was given by an employee of the company, in the function that benefits from the definition. Nobody outside the company has read any of it. The same limitation the assurance register carries applies here in full.
Distance from the data. All 26 source systems are described and none is connected, and none of the 18 connector contracts these terms reach is live. Every binding below is therefore a statement about a field somebody read a specification for, not a field this platform has ever read.
- Discount: agreed, but its book of record Configure, Price and Quote is behind its own freshness commitment.
Actions
What is waiting on a person
Nothing below is a data quality defect. Each line is a place where two parts of this estate use one word to mean two things, and the count of what that costs in records already stored.
occurrences of a phrase that gates a decision and has never been defined
6 distinct phrases found in a scan of 5,842 stored records. The scan counts whole-word matches; it cannot tell a careful use from a careless one.
system bindings that do not match the definitions they sit under
Every binding names the local field, its grain, its unit and the rule behind it. 44 of 68 differ from the register, and each difference is stated rather than reconciled away.
definitions nobody has signed
Written here, owned by a named chair, and never approved by anybody in the owning function. Until somebody signs, this platform is the only party asserting what the word means.
terms two systems mean differently, with disputes open
Each one is a word that appears in board material, in agent instructions and in contracts, carrying a different population in each system that holds it. 12 disputes are open and 3 of the 14 on the register have ever been sized.
term with no book of record at all
No system holds it. It is measured, reported and escalated on anyway, from thresholds that live in contract text, vendor portals and spreadsheets nobody has reconciled.
source system no term in this register points at
25 of 26 systems carry at least one binding. The remaining one holds data this register says nothing about, which is not the same as holding data that agrees.
agreed term whose book of record is behind its own freshness commitment
Agreement is about wording. It says nothing about whether the system holding the word is current, so the two are checked separately and reported separately.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This page holds definitions and nothing else. It records 22 terms across 11 domains, binds them to 68 named fields in 25 source systems, and re-derives every verdict from live rows on load. It does not change a system, rename a field, block a report or stop an agent using a word its own way. Agreeing a definition and enforcing it are two projects, and only the first has started.
Live observability
What the record shows right now
22 terms, split by what the estate can actually support behind each one. The second band is the one most often read as the first.
Current distribution
22 terms
Is policy and strategy coming to fruition
Whether the written intent is holding here
No. 22.7% of the register is signed, held and undisputed, and 10 of the words this estate reports on mean different things in different systems.
Not holding on the record
The strategy assumed the estate had a shared language. What the record supports is narrower. 7 of 22 definitions carry a named approval, 5 clear every test this page applies, and 10 are contested by an open dispute. The oldest open disagreement, TD-04 on supplier, was raised by Marta Oyelaran 208 days ago and is still open. Every figure here counts only the words somebody thought to nominate. The words nobody nominated are absent from this page and therefore look fine.