Capturing How Data Really Moves

Helping teams build and manage their product data landscapes

We build living data dictionaries that document how your data flows through your people, process, and platforms. We back our solution with expert services to create a foundation that facilitates improved communication, responsiveness, planning, and action.

A documented data flow for
Internal context
Data dictionary · UDI
Endpoint context
Peoplewho owns it
Regulatory AffairsOwner · regional stewards
AMEREMEAAPAC
Processhow it's governed
6Teams
4Processes
5Endpoints
Platformswhere it lives
ERP
PLM
PIM
DAM
System of record · ERP
Entry 01 / 03
Primary Device Identifierudi_di_primary

The unique identifier assigned to the base package level of a device model.

TypeString(14)
Related terms5 endpoint terms
Field
udi_di_primary : String(14)
Code list
GS1HIBCCICCBBAIFA
Documents
EU MDR Annex VI21 CFR 830
Schema
Device › Identification › PrimaryDI
  • EUDAMEDUDI-DI code
    Required
  • FDA
    GUDIDPrimary DI Number
    Required
  • SwissdamedUDI-DI
    Required
  • TGA
    AusUDIDDevice Identifier
    Required
  • NMPA · MFDS · TUDIDProduct identifier
    Required
Start free — explore the connectorsNo credit card. Tell us what you manage and we'll set you up.

Why systems fail lies in keeping people, process, platforms and properties up to date

Landscapes are expensive

The composable landscape is expensive across organizations. Our models show the typical cost for enterprises is:

  • Small — $15,000 to $60,000
  • Midsize — $60,000 to $350,000
  • Large — $350,000 to $2.5M
  • Global — $2.5M to $15M+

Historically underdeliver

Solutions fail and are replaced every 3 to 5 years. Replatforming is both time and resource intensive:

  • 45% of large IT projects run over budget1
  • 60% of AI projects without AI-ready data will be abandoned2
  • 73% of enterprise apps remain unintegrated3

Leave you with costly corrections

AI makes release cycles exponentially faster, but aligning on requirements still takes time — and the cost of change compounds:

  • 1x during requirements and alignment
  • 7x to 16x during build4
  • 29x or more once the system is in production4
  1. McKinsey & Company with the University of Oxford, “Delivering large-scale IT projects on time, on budget, and on value” (2012); projects over $15M.
  2. Gartner, “Lack of AI-Ready Data Puts AI Projects at Risk” (February 2025); prediction through 2026.
  3. MuleSoft, 2026 Connectivity Benchmark Report; 27% of applications connected, 1,050 IT leaders surveyed.
  4. Stecklein et al., NASA, “Error Cost Escalation Through the Project Life Cycle” (2004); cost to fix relative to the requirements phase.

It’s Time to Rethink Managing Requirements

Stop leaving vital information on how you control for product and manage record submission hidden behind solution configurations or lost in requirement specs.

Build Better with Blocks

Start free. Upgrade when you’re ready to bring your team and systems in and connect the context in which you manage data to your registries and partners.

  1. 01 · Free

    Sign up and explore

    Browse every endpoint connector information set to gather requirements.

  2. 02 · Properties

    Build your data dictionary

    Import your data model and see full, partial and missing matches per endpoint.

  3. 03 · People + Process + Platforms

    Connect to ContextHub

    Assign owners and build the process each endpoint needs across the platforms you use.

  4. 04 · Link Context to Endpoints

    Managing requirement change

    Link your data dictionary to regulatory & commercial requirements.

Start free →