Tessera mark
Tessera · tesserabi.com

Tessera MDL — Record Map

Tessera Metric Definition Layer · 15 custom record types in v1 · 5 layers · Hover any record for a description

Structural Core
One parent, five child record types — defines and stores the metric
Records 1–6
Metric Definition
parent of → Query Component Filter / Scope Formula Pattern Query Template Metric Result assigned to → Approval Domain Approval Domain references → Formula Pattern Formula Pattern versioned: immutable after approval
Governs the metric definition — formula pattern, version chain, approval status, sign-off record, and effective dates. Immutable once approved.
Query Component
child of → Metric Definition parent of → Filter / Scope Filter/Scope references → Account Config Query Template
One record per formula variable (A, B, C…). Defines query type, template, account scope, period window, and refresh policy.
Filter / Scope
child of → Query Component Query Component extensible: new types = data not code
A single filter or scope condition attached to a Query Component. Written in plain English and reviewed by the Controller at sign-off.
Dimension Scope
child of → Metric Definition references → Segment Segment
Named formula pattern (e.g. Ratio: Trailing Days). Stores the formula string and variable definitions. Seed records ship with Tessera.
Minor Change Log
child of → Metric Definition rule: if the number could differ → new version
Parameterized SuiteQL template with named slot manifests. Tessera ships six standard templates covering the most common financial metric shapes.
Metric Result
child of → Metric Definition (specific version) references → Segment Segment immutable: closed-period results stored permanently
The computed result for a specific period and subsidiary scope. Permanent for closed periods. Marked stale and recomputed for open periods when transactions post.
Governance
Approval authority, version conflicts, routing, and override audit trail
Records 7–10
Approval Domain
assigned to → Metric Definition (every metric) influences → R9 Resolution Policy scope (v2) standalone — not child of any record
Defines a governance scope — which metrics require sign-off from which named approver. Every metric belongs to exactly one domain.
produces comparison when two definitions exist for the same metric
Metric Comparison (v2)
references → Metric Definition (Definition A + Definition B) parent of → Resolution Policy Resolution Policy
Tracks the side-by-side comparison of two metric definitions against the same period. Used to resolve definitional disagreements across teams. v2.
approved comparison produces a policy that governs what each user sees
Metric Resolution Policy (v2)
child of → Metric Comparison Metric Comparison references → Metric Definition Preferred Definition references → Approval Domain Approval Domain (scope) governs → Portlet Config Portlet Config
Records the outcome of a comparison: which definition was selected as preferred, applicable scope, and written rationale. v2.
policy recommendation recorded at portlet placement; any override permanently logged
Dashboard Portlet Configuration
references → Metric Definition Metric Definition (version) references → R9 Resolution Policy (v2) owned by → Employee or Role
Assigns a metric definition version to a specific portlet slot on a NetSuite home dashboard. One record per deployed portlet.
Shared Library
Reusable patterns stored as data — adding a new template or formula is a data change, not a code deployment
Records 11–12
Query Template
referenced by → Query Component Query Component v1: Ratio:Trailing Days · Simple Aggregation:Period · Simple Aggregation:Trailing Days · Running Balance
Stores account-level Tessera configuration: default subsidiary scope, notification email, CRL settings, license state.
Formula Pattern
referenced by → Metric Definition Metric Definition v1: Single Value · Ratio · Ratio:Trailing Days · Gross Margin% · Percent Change · Difference · Multi-Component Sum · Three-Component Margin%
Customer-defined formula pattern extending the seed library. Same structure as R4 but owned and maintained by the customer.
Benchmark
Industry reference data — series define the dataset, data points store the values by industry and revenue band
Records 13–14
Benchmark Series
references → Metric Definition Metric Definition parent of → Benchmark Data Point Benchmark Data Point
A benchmark data series from a named source (e.g. APQC). Stores metadata, vintage, industry, and revenue band. Conditional v1.
Benchmark Data Point
child of → Benchmark Series Benchmark Series displayed on → Portlet Config Portlet Config (as reference band)
One data point within a Benchmark Series: percentile, value, industry, revenue band. Used to render benchmark overlays. Conditional v1.
Segment
Shared hierarchy record — dimension values with Tessera-defined rollup groupings; referenced across structural layer
Record 15
Segment
referenced by → Formula Pattern Dimension Scope (default segment) referenced by → Metric Result Metric Result (which segment was applied) self-referencing → Parent Segment FK for tree navigation reparenting via → Map/Reduce script (tessera_segment_reindex.js)
Mirrors a NetSuite dimension record (Class, Dept, Location, or custom segment) with a materialized path for efficient ancestor queries.
Resolved at query time (Rollup nodes)
Audit
Query Infrastructure & Event Log
Query slot definitions, verification sources, and the append-only domain event store
Records 16–18
Query Template Slot
child of → Account Config Query Template many per template
Defines how a custom segment field joins to transaction tables. Required for non-standard segment dimensions.
Verification Source
associated with → Account Config Query Template used at → Wizard Step 5 pre-flight
A saved search or SuiteQL query registered as an approved verification source for Controller pre-flight sign-off.
Event Log
written by → User Event scripts (cache invalidation) written by → Wizard + approval workflow (lifecycle) append-only — no FK enforced (soft reference only)
Append-only domain event log capturing both cache invalidation events and metric lifecycle transitions.
R1 — Core parent
R2–6 — Structural children
R7–10 — Governance chain
R11–12 — Shared library (query + formula)
R13–14 — Benchmark (series + data points)
R15 — Segment hierarchy
R16–18 — Query slots · Verification · Event log
Click any record card to expand key fields  ·  R3 and R5 can have many child records per parent