One sign-in. One fabric. Six workspaces connected.
OrvynESG, OrvynCDP, OrvynCEQ, OrvynDPP, OrvynLCA and OrvynPPWR each keep their specialist data plane while sharing identity, context, entitlements, search and a steward-governed data fabric.
Shared deliberately. Reused under governance.
Cross-product reuse is explicit and governed — never silent. A figure shared from one product becomes a platform datapoint a suite steward must clear before any other module may use it. One authoritative value per key, facility and year.
Share from the source
An editor presses “Share with Orvyn360” on a governed figure — a scope total, a recycled-input rate, a passport portfolio signal. It becomes a platform datapoint, pending clearance.
Steward clearance
A steward approves or rejects it in the data clearance queue — with a note, under their identity. Clearing a newer revision supersedes the old one automatically.
Suggested where it answers
The cleared value appears beside the exact field it answers — value, source, author, freshness — with Use as-is, Insert & adjust or Add as note. Every pull is audited.
Mapped landing spots today include CDP C7.6 / C7.7 / C7.8 / C7.30.1 / C9.2.7, energy and waste reconciliation references in the OrvynCEQ Data Hub, and the recycled-content benchmark beside the OrvynDPP bill of materials — extensible per deployment. Products deployed standalone simply hide every fabric affordance.
Approval levels, everywhere they matter.
Enterprise sustainability data is only as strong as its sign-off trail. Every layer has a formal review step — and every decision is recorded with identity, note and history.
| Layer | Chain | Mechanism |
|---|---|---|
| OrvynESG datasets | submit → approve / reject | A Data approvals screen: preparers submit an entry-type × facility × year dataset with a note; admins decide with notes; full history retained. |
| OrvynCDP answers | L1 → L2 → L3 → L4 | Lock & Send moves answers into a configurable four-level approval chain with an audit log, indicative allocation views and governed exports. |
| OrvynCEQ assessments | draft → review → approval → approved | Assessments travel a formal state chain — and even scoring-weight configurations go through governed approval before they apply. |
| OrvynDPP passports | steward → approver → publish | Two-role review before publishing; a published passport's identity is frozen, and public viewer access is granted explicitly. |
| OrvynPPWR controls | prepare → independent approval → issue | Supplier evidence, design assessments and declarations remain governed; approved declarations issue from immutable source snapshots with separation of duties. |
| Platform datapoints | share → steward clearance | The suite-level gate: the data clearance queue on the Orvyn360 home — role-gated, with an append-only audit trail. |
Preparer and approver roles are separated at every layer — designed for assurance conversations, not just submission deadlines.
Shared control plane. Product-owned data planes.
Deliberately not one big database. ESG inventory changes are isolated from published-passport identity, and CEQ engine migrations are isolated from ESG reporting. Products join on stable external identifiers and cleared fabric datapoints rather than foreign keys across schemas.
The control plane
Sign-in and session launch · entitlements and deployment scope · facility code and reporting year · the data fabric with clearance and audit · product discovery, search, preferences and the Orb.
The data planes
Access tokens and signing keys · databases, schemas and migrations · domain permissions and public-passport grants · raw ledgers, evidence and calculations.
Not hard-coded to anyone's industry.
Workspace identity, facilities, currencies, dashboards and circularity rubrics hydrate from the organisation that signs in. Three fully-worked example workspaces ship in the box — see an operation like yours on day one, then provision your own.
Apparel & consumer goods
A synthetic multi-site apparel group with walkthrough-grade data across the connected workspaces — from group GHG inventory through circularity assessment to QR-scannable public passports.
Discrete manufacturing
An illustrative CNC machine-tool maker: Australian head office, machining and assembly plants — combustion, electricity, water, waste, suppliers, targets and projects across two reporting years.
Infrastructure EPC
An illustrative highways EPC: Indian head office, a national-highway package and a precast yard — project-level footprints, BRSR-aligned reporting and infrastructure rubrics.
Example organisations are synthetic reference data with neutral labels — they exercise real workflows for demos and onboarding, and switch off with a single flag in production. OrvynCEQ applies its industry rubric profiles automatically, and a workspace guide covers provisioning a brand-new industry end to end.
Scope the operating model, then the software.
Entitlements determine which connected workspaces are active. The right deployment starts from your obligations, facilities, governance and data readiness; availability, support and integration scope are confirmed in the applicable order form.
One priority workflow
Start with the connected product your immediate obligation demands.
- Defined product and outcome scope
- Organisation and facility context
- Onboarding and support documented
Multiple workflows + the fabric
Combine connected products where governed values have a real reuse path.
- Platform data fabric — share, clear, pull
- Cross-product governance and pulse
- Expansion scoped against readiness
Six connected workspaces
Bring ESG, CDP, CEQ, DPP, LCA and PPWR into one governed operating model.
- Complete connected portfolio + fabric
- Layered approvals and audit trails
- Support model agreed in writing
See one number travel the whole circle.
The clearest platform demonstration is one figure: entered in OrvynESG, cleared by a steward and suggested beside CDP C7.6 with its provenance attached.