Data Governance system
Data Governance · Shop-floor-led · DMBOK-aligned

Find every production asset, by the line and plant it lives on. Then ask the steward.

Find every regulated asset, by the part of the world it lives in. Then ask the steward.

Find every civic record, by the register and office it lives in. Then ask the steward.

A catalogue that publishes outside the data catalog — to colleagues on the line, in quality, and across supply who are authorised to know about production data but don't hold a catalog licence. Click into the plant, the line, or the supplier network. Discover the data. Open a stewardship conversation in one click.

Production lines
18
in demo plant set
Catalogued assets
340+
Avg. quality
87 / 100
Last refresh
12 min
ago
line_a_batch
Asset · Manufacturing · Line A Approved

Batch Genealogy — Tableting Line A

Line / lot traceability record · last refresh 12 min ago · steward: 品質保証 (QA)

Confidential PII ISA-95 ISO 9001
Workflow · #WF-2026-0428-117 Closed

PII flag for column operator_id — confirmed

Resolved by DG Council in 2 days · 4 messages · audit trail saved on asset

Task · Review & Respond New

How do I update the supplier material-master attributes?

Posted by 生産管理 · Auto-escalates in 6d 14h

One governance model. Your sector's reality.

The catalogue is sector-agnostic — the same discovery, stewardship, and audit primitives underneath. The framing is not. Choose the world you operate in.

Isometric illustration of a manufacturing plant — production lines, quality stations, and warehouse feeding one data catalogue
製造 · Manufacturing

Production and quality data, across every line and plant.

  • Production, quality, and supply data unified across lines, plants, and suppliers.
  • Batch records, inspection results, and equipment lineage catalogued in one place.
  • Trace any asset upstream and downstream — raw material to shipped lot.

Three industries. Three maps. One interaction model.

In pharma, the discovery primitive is human anatomy. In manufacturing, the factory floor. In logistics, the trade-lane network. Same click-region-to-discover-assets pattern; different physical primitive per industry. The asset-detail surface (chips, status, regulatory frameworks) is identical underneath.

3D anatomy view of the human body — therapeutic areas mapped to body regions
Anatomy view · Drag to rotate
CNS · Oncology
Cardiology · Pulmonology
Gastroenterology
Immunology · L
Immunology · R
Orthopaedics · L
Orthopaedics · R
Click any region to filter the catalogue
● Live · demo dataset shipped

Anatomy → therapeutic areas

Click a body region to surface every catalogued asset for the corresponding therapeutic area. Cross-system programmes (Oncology, Pharmacovigilance, Immunology) light up multiple regions with connecting paths. Therapeutic area is the discovery primitive in pharma — and it is, literally, anatomy.

21 CFR Part 11 ICH E6 R3 EU CTR ICH E2B R3 GVP CDISC SDTM CDISC ADaM MedDRA
Pharmaceutical manufacturing facility floor plan with labelled production lines, quality stations, packaging, and warehouse
Factory view · Drag to pan
Line A · Tableting
Line B
Coating
Tableting QA
QC
Packaging
Warehouse
Click any zone to filter the catalogue
◆ Parallel · same interaction model

Factory floor → production zones

Plant-floor map as the discovery primitive. Click a production line, a quality station, a packaging zone, or the warehouse to surface its data assets — batch records, deviation logs, equipment lineage, calibration histories, GMP documentation. Same interaction, different primitive.

ICH Q7 ICH Q9 ICH Q10 EU GMP Annex 11 ISO 9001 ISA-95 21 CFR Part 211
World-map trade-lane network with major logistics hubs
Trade-lane view · Drag to rotate
New York · JFK
London · LHR
Frankfurt · FRA
Tokyo · NRT
Singapore · SIN
Sydney · SYD
Click any hub or lane to filter the catalogue
◆ Parallel · same interaction model

Trade lanes → hubs & carriers

Network map as the discovery primitive. Click a hub, a lane, or a carrier to surface shipment manifests, customs filings, temperature-excursion records, and chain-of-custody data — across borders, modes, and regulators. Cold-chain pharma logistics is the highest-stakes example.

GDP (EU) IATA TCR USP <1079> PIC/S Annex 13 WHO TRS 957 ICH Q9

Every asset, told the way regulators read it.

Status. Certified. Classification. PHI / PII / GxP. Regulatory framework alignment. Standards mapping. Source system. Upstream lineage. Column-level schema. Each chip is a known shape; together they tell a regulator-grade story at a glance — same shape regardless of industry.

Manufacturing / Line A / Batch Genealogy

Batch Genealogy — Tableting Line A (Lot Traceability)

batch_genealogy_line_a_v3.parquet · Line / lot traceability dataset · Source: MES · /lines/A/batch

Approved Certified 🔒 Confidential 🔒 PII

Description

Line- and lot-level genealogy joining raw-material lots, in-process quality checks, and finished-lot IDs for Tableting Line A. Locked at lot disposition. Used by quality, production, and supply as the source of truth for tracing any finished lot back to its inputs and forward to shipment.

Standards & frameworks

ISO 9001 ISA-95 ISO 27001 GS1 traceability

Upstream lineage

ERP · material master MES · process data QMS · inspection results batch_genealogy_line_a_v3

Column-level schema (excerpt)

ColumnKeyTypeDescription
LOT_IDPKChar(20)Finished-lot identifier
MATERIAL_IDFKChar(20)Raw-material lot reference
LINE_IDFKChar(8)Production line
OPERATOR_IDPIIChar(12)Operator on record
YIELD_PCTNum(5,2)Lot yield percentage

Skip the navigation. Type the asset.

Instant client-side search across English display names, Japanese display names, physical names, descriptions, and tags. No round-trip — answers appear as you type.

⌘K esc
B
Batch Genealogy — Tableting Line A (Lot Traceability)
MES · Approved
B
バッチ系譜 — 打錠ライン A(ロット追跡)
JP · 同義検索
B
Batch Genealogy MES Source — line_a.parquet
MES · Approved
B
Batch Yield Report (Line A — 2025 Q3)
Obsolete

Discovery is a question. Stewardship is the answer.

Every catalogue asset has a one-click Ask the steward button. It opens a Message Workflow — a bidirectional Q&A on that asset, handled by the responsible resource roles in the catalog. Every message is saved as a comment on the asset; the audit trail lives where the asset lives. The 4 tabs below reproduce the actual message-workflow screens.

catalog.example.com / assets / aerd_oncology_pivotal_v3 / actions / message-workflow
WORKFLOW·messageWorkflow· New

Start a question

Posting on asset aerd_oncology_pivotal_v3 · Stewards will be notified by email

Max 255 characters
Max 4000 characters
A
aerd_oncology_pivotal_v3
asset-uuid-9f3a-b21c-7d8e
catalog.example.com / tasks / task-98765 / Review and Respond
USER TASK·receiverTask· New· Assigned to Oncology_DG · Auto-escalates in 6d 14h

Review and Respond

Posted by John Doe (jdoe) on May 15, 10:30 JST

John Doejdoe@example.com2026-05-15 10:30 JST Question
For the safety summary tables in section 12.3, can I use this dataset as-is? The freshness is 12 minutes — that looks too recent for a locked study.
Reply continues the conversation · Escalate routes to DG_Council · Close ends the workflow.
catalog.example.com / tasks / task-98766 / Review Response
USER TASK·senderReplyTask· In Progress·Assigned to you

Review Response

Maria Tanaka (Steward · Oncology DG) replied to your question

You2026-05-15 10:30 JST
For the safety summary tables in section 12.3…
Maria TanakaOncology DG2026-05-15 14:08 JST
Use this dataset directly. The 12-min freshness reflects metadata refresh, not data — the underlying ADaM was locked on 2026-04-22 and is signed for the CSR.
catalog.example.com / tasks / task-98770 / Handle Escalated Issue
USER TASK·escalatedTask· Escalated· Assigned to DG_Council · Auto-escalated after 7d

Handle Escalated Issue

Originally posted by John Doe · Receiver group did not respond within 7 days

John Doe2026-05-15 10:30 JST
Posted question on aerd_oncology_pivotal_v3
System2026-05-22 10:30 JST
Auto-escalated to DG_Council — receiver group did not respond within 7 days.
  • Resource-Role assignmentRoutes via catalog resource roles, not raw user IDs. Stewards see questions for assets they're responsible for.
  • BidirectionalSender ↔ steward can exchange messages indefinitely until resolution. Not a one-shot ticket.
  • Auto-escalationNo response in 7 days → escalates to the configured DG Council group automatically.
  • Audit-grade historyEvery message saved as an asset comment. Persists long after the workflow closes.
  • DMBOK-alignedModeled on DMBOK's Communication function, consistent with the catalog's operating model.

The full BPMN flow.

Reproduced from workflow/message-workflow.bpmn. Topology is real; visualisation is yours to refine.

▶ Start
Initialize
status = New
?
Save initial
comment
Notify
receiver group
User Task
Review & Respond
⏱ 7d auto-escalate
?
Save reply
comment
Notify
sender
User Task
Review Response
?
Reply
(loop back)
or
▣ Close · End
Start / End event
User task (form)
Service task (system)
Gateway (branching)

First-class Japanese — not bolt-on translation.

Display names, physical names, descriptions, and tags all index in both languages. Japanese typography uses phrase-aware line breaking, hanging punctuation, and pretty-text wrap — never mid-word breaks at column boundaries.

EN · default

Discover by the plant floor

Find the data behind every production line and plant, from a single floor map. Click a line, a quality station, or the warehouse to see which assets hold data there. Cross-line programmes such as yield improvement or supplier changes light up multiple zones at once with connecting paths.

JP · 日本語

工場フロアから探す

工場のフロアマップから、各ラインや工場に紐づくデータを一目で探す。ライン、品質ステーション、倉庫をクリックすると、その場所に関わるデータ資産が表示されます。歩留まり改善やサプライヤー変更のように複数の工程に跨る取り組みは、関連するゾーンが同時に光り、線で繋がります。

Built on catalog primitives — nothing exotic.

Resource-Role assignment

Tasks route via the catalog's resource role system, not raw user IDs or emails. One role definition, every team member who holds it sees the task. Works with your existing responsibility model.

Asset-anchored audit trail

Every message saved as a comment on the related asset via the Comment API. Conversation history lives where the asset lives, surviving long after the workflow closes.

Static publication

Catalogue publishes as a static site (SharePoint document library, internal CDN, GitHub Pages). Authorised colleagues browse without consuming a catalog licence.

Configuration-driven

5 workflow variables tune behaviour without code changes: recipientGroup, escalationGroup, escalationDuration, emailNotificationEnabled, mailSubjectPrefix.

Plug into where your data already lives. Publish where your people already work.

You don't need everything in your data catalog to start. The connector reads from the systems you already use — your data catalog, Excel files, SharePoint folders, Google Sheets, Google Drive, your databases — and unifies them into one catalogue. The catalogue then publishes to wherever your colleagues already browse: SharePoint, an intranet, a single bookmark. Nobody needs a catalog licence to discover.

1 Where your data already lives
C
the data catalog OAuth · REST API
Excel files .xlsx · OneDrive / local
SharePoint Document libraries · lists
Google Sheets via Drive API
Google Drive Files · folders · metadata
Databases & data platforms your warehouse, transactional DB, lakehouse, or integration layer — wherever your data sits
PostgreSQL MySQL SQL Server Oracle Snowflake BigQuery Redshift Databricks Informatica
Cloud storage & other systems object stores, custom APIs, CSV exports — we read what you have
Amazon S3 Azure Google Cloud OneDrive Dropbox Box
collected · normalised · unified
2 We collect and unify into one catalogue
LV3 Connector Python · scheduled or on-demand

One unified catalogue

Every asset from every source, normalised into one searchable shape — catalog-style status, classification, regulatory framework chips, lineage, schema, bilingual EN/JP. The discovery surface your colleagues actually open.

340+Assets
12Domains
EN / JPBilingual
HourlyRefresh
published · static · zero licence
3 Where your people already work
SharePoint
SharePoint document library set as a site home page
CDN
Internal intranet / CDN any static host
GitHub Pages
GitHub Pages auto-deploy on every refresh
🔗
A single bookmark colleagues just open a link

Plain-language version: we read your existing files, sheets, and databases — wherever they are — and turn them into one searchable catalogue that opens in any browser. No catalog licences for the readers. No re-platforming for your data.

Deploy it on your data catalog in days, not quarters.

LV3 handles connector wiring, Resource-Role configuration, industry-map customisation, and bilingual rollout. We don't sell licences — we deliver working governance.

Engagement modes, flow, and procurement checklist: see how we work. Service one-pager: English PDF · 日本語版 PDF