Object types
9
ISA-95 + operational context
INDUSMESH OS
Overview
Your operations, in one place.
Not refreshed
YOUR WORK VIEW
Plant Operator
Prioritized task areas: Operate · Assets · Connect. All authorized capabilities remain available through the sidebar and search.
Choose a starting point for your work. A work view prioritizes relevant tasks; your signed-in identity and permissions stay the same.
Continue setup or explore
Setup progress comes from the canonical project, environment and facility records. Source readiness is reviewed in the owning operations workspace.
FACILITY ONBOARDING
Bring your first facility online
Establish an authorized facility context, connect plant data, verify one exact historian measurement, then enter Operations. Configuration is never presented as live data.
0 / 6evidence-backed steps
1 · CONTEXT & FACILITY
Choose where plant evidence belongs
The project, environment and facility in the workspace bar are the canonical scope for this onboarding journey. No demo object is substituted when scope is incomplete.
2 · CONNECT PLANT DATA
Establish runtime connectivity
Use an industrial connection or interoperability profile appropriate to the source. A configured or certified connector is not treated as healthy until runtime evidence exists.
Advanced edge client tooling
CLI/tunnel installation is an administrator/integration path, not facility onboarding.
3 · MODEL & MAP
Expose a canonical measurement point
A measurement point must belong to this facility and have source-binding evidence before the first-data check can be meaningful.
4 · FIRST DATA
Verify one exact historian measurement
This is a read-only historian verification over the selected authorized facility. no_data, stale, offline, bad-quality, access-denied and context-mismatch responses remain distinct and do not complete onboarding.
5 · OPERATE
Open the meaningful facility workspace
Verify one exact measurement before treating this facility as data-ready. Operations remains available for setup and investigation, but onboarding is not marked complete.
ADVANCED EDGE TOOLING
Administer an edge client
This is an integration/admin workflow for signed edge-client installation and agent-scoped credentials. It is not the first-run facility onboarding journey.
0 / 4steps complete
STEP 1
Install the IndusMesh edge client
The secure updater verifies release checksums and requires the Sigstore-signed checksum bundle through cosign unless you explicitly opt out.
STEP 2
Configure your first agent
ONE-TIME SECRET
Run this on your workstation
Shown once
The raw credential is shown separately so it does not need to appear in shell history. The current edge client retains the TUNNEL_TOKEN environment variable for backward compatibility; set it through a prompt, then run the setup command.
read -rsp 'Agent token: ' TUNNEL_TOKEN; export TUNNEL_TOKEN; echo$env:TUNNEL_TOKEN = Read-Host 'Agent token'tunnel startthen openhttp://127.0.0.1:4040/VERIFY
Connection status
YOUR CONNECTED WORKSPACE
A clearer view.
A better way to operate.
Connect your systems, understand your evidence,
and move your next decision forward.
ACTIVE PROJECTYour workspace
Data and actions follow your selected project.
Workspace snapshot
Connection activity in your selected project.
Pick up where work happens
Purpose-built spaces for your next task.
Recent endpoints
Connections across this project
Agent activity
Your latest connection sessions
Bring a facility online
Use the evidence-backed onboarding journey from facility identity through first verified historian data.
ENVIRONMENTAL MANAGEMENT
Environmental performance, with evidence behind every decision
Monitor obligations, investigate exceptions and prepare reports. Choose a facility to see its latest evidence and available actions.
FIRST-RUN SETUP
Add your first facility
Environmental work starts with a governed facility identity. This creates the canonical site/facility records used by permits, monitoring and evidence.
Your access at this facilityReview permissions, reviewer roles and available actionsCHECKING
Select a facility to resolve effective environmental authority.
MY ENVIRONMENTAL WORK
Operational workspace
Obligations, monitoring, exceptions, investigations, reporting, analysis and specialist evidence remain facility-scoped and evidence-backed.
SOURCE READINESS
Evidence availability at a glance
See whether required environmental evidence is available and current. Detailed connection, mapping and synchronization settings remain in the authorized technical view.
ROLE & ACCESS
Who can work in each area
The workspace adapts to your role, facility and reviewer assignments so each user sees the tools relevant to their responsibilities.
INFORMATION DISPLAY TIERS
Keep technical depth without forcing it on every user
ENVIRONMENTAL ACTION CENTER
Own exceptions from acknowledgement through verified closure
My Work and Team Queue bring together assigned exceptions, investigations and corrective actions. Every transition remains facility-scoped, evidence-backed and auditable.
ACCOUNTABLE QUEUE
My Work & Team Queue
Overdue and critical work is prioritized. Unassigned team work remains visible; My Work contains records assigned directly to you.
Open a queue item to work the governed exception lifecycle.
ENVIRONMENTAL EVIDENCE OPERATIONS
Explain every reported environmental result
Review obligations, governed monitoring state, exceptions, investigations and reproducible report editions from one facility-scoped workspace. Statutory calculations remain authoritative in the governed calculation service.
DATA & REVIEW STATES
Interpret the evidence before the conclusion
DOMAIN WORKSPACES
Move from cross-domain oversight into specialist operations
The Operations page provides the cross-domain summary, while domain workspaces give specialists focused views over the same governed environmental records.
GOVERNED CONVERSATIONAL ANALYSIS
Ask bounded questions over governed evidence
Ask natural-language questions across governed environmental evidence. Results remain traceable to their source records, and root-cause suggestions stay advisory until confirmed through the investigation workflow.
Ask a facility-scoped question to create a reproducible analysis run.
WORK PERMIT & SIMOPS CONTEXT
Review simultaneous-work context against governed plant evidence
Review mirrored work-permit context against approved site conflict rules, qualification and isolation requirements, and current gas evidence. Results are advisory only: IndusMesh cannot issue a permit, release an isolation, or declare work safe.
Load a facility to inspect synchronized external work permits and advisory SIMOPS assessments.
OCCUPATIONAL EXPOSURE EVIDENCE
Review governed TWA, STEL and noise-dose assessments
Review pseudonymous worker or similar-exposure-group sampling, shift coverage, instrument validity, approved exposure limits and hygienist review. Medical records, diagnoses and fitness-for-duty decisions remain outside this workspace.
Load a facility to inspect governed occupational-exposure assessments. Personal session identifiers are not shown in this summary view.
ADVISORY IMAGE OBSERVATIONS
Review observable site-photo hazard proposals
Site-photo assistance is limited to directly observable conditions and always requires human review. An image cannot certify isolation, grounding, permit validity, confined-space atmosphere, safe-to-work state or another hidden safety condition.
Load a facility to inspect governed site-photo observations and their human-review disposition.
REGULATORY EXCHANGE FRAMEWORK
Governed schemas, mappings and reproducible exchange payloads
Installed regulatory programs package approved data through governed schemas and mappings. CBAM is available where configured; programs that are not installed are not presented as supported.
Load a facility to inspect governed schema/mapping revisions, pack lifecycle, reproducible exchange runs and durable dispatch state.
OBLIGATIONS
Applicable environmental rules
MONITORING
Assessment & evidence health
EXCEPTIONS
Exceedances & assessment gaps
INVESTIGATIONS
Ownership & corrective action
WATER & LABORATORY
Samples, qualifiers & assessed discharge periods
WASTE
Inventory, consignments & receipt reconciliation
CARBON ACCOUNTING
Scope 1 & Scope 2 inventory, close & restatement
GROUNDED PERMIT ASSISTANCE
AI-extracted permit clauses awaiting human review
Candidates are bound to document revisions and cited chunks. Approval records the reviewer decision only; permit rules are activated separately through the governed permit workflow.
REPORTING PERIODS
Reviewed and reproducible report editions
SOURCE EVIDENCE DRILLDOWN
Result → calculation → evidence → source state → governing rule
Choose a calculation, exception or report edition to inspect its exact governed lineage.
CURATED ANALYTICS
BI projection reconciled to approved report editions
Scheduled Import is the supported default. The analytics layer projects reviewed period facts; it does not recalculate statutory logic.
REPORTING & EVIDENCE
Move immutable environmental report editions from compilation to independent review and evidence issue
Compile, review, sign and issue immutable environmental report editions. Downloads preserve the approved edition, evidence lineage, signatures and restatement history exactly as reviewed.
REPORTING CALENDAR & READINESS
Active reporting obligations
The register shows governed reporting frequency and existing editions. IndusMesh does not fabricate statutory due dates where the authority record provides only a frequency.
Select a facility.
COMPILE REPORT EDITION
Run the existing governed assessment/report path
Compilation resolves the exact active obligation and evidence through the existing CEMS assessment provider. If evidence is insufficient, generation fails closed rather than creating an issuable edition.
A repeat request for the same immutable calculation run returns the same edition. A corrected calculation for the same reporting period creates a superseding/restatement edition instead of rewriting history.
REPORT EDITIONS
Draft → review → approved → signed / issued package
Select an edition to validate its evidence package, inspect authority/evidence lineage, review, sign and issue the deterministic package.
No report editions loaded.
EVIDENCE PACKAGE & SIGN-OFF
Exact edition custody
Select a report edition.
ENVIRONMENTAL COMPLIANCE
Configure compliance access and qualify facilities
Enable Environmental Compliance only for entitled facilities and approved jurisdictions. Regulatory conclusions remain unavailable until permit, coverage, calibration and reviewer readiness checks are complete.
MODULE ACCESS
Control Environmental Compliance availability
Environmental Compliance is activated separately from Environmental Management and can be suspended without removing historical records or evidence.
No compliance entitlements loaded.
JURISDICTION RULES
Manage approved jurisdiction configurations
Jurisdiction configurations define where compliance features may be used. Drafting, independent review and activation remain separate steps.
No jurisdiction packs loaded.
FACILITY READINESS
Qualify compliance separately for each facility
Select the approved jurisdiction configuration and verify permit, obligation, coverage, calibration and reviewer readiness before enabling new compliance conclusions.
No facility activations loaded.
Module access, facility readiness and regulator acceptance are tracked separately.
ENVIRONMENTAL COMPLIANCE
Separate measured assessment from regulatory conclusion
A governed conclusion is bound to the immutable CEMS calculation run and only reaches COMPLIANT or NON_COMPLIANT when permit validity, an explicit coverage method and a passing calibration authority cover every assessed segment. Missing authority fails closed.
CALIBRATION AUTHORITY
Certificate validity is governed evidence, not a sensor-status guess
Create an immutable calibration authority revision, submit it, obtain independent calibration/environmental review, then activate it. Failed calibration evidence cannot be activated.
REGULATORY DETERMINATION
Determine compliance from approved monitoring evidence
Each conclusion uses the approved monitoring assessment and preserves the exact permit, coverage and calibration evidence used for the decision.
No determinations loaded.
An internal regulatory conclusion does not constitute regulator acceptance, filing acknowledgement, or legal acceptance by a receiving authority.
DEPLOYMENT READINESS
Check readiness before a customer deployment
Software readiness, customer-environment readiness, external-system validation and user acceptance are tracked as separate gates. Test evidence is never presented as a completed customer acceptance activity.
DEPLOYMENT DECISION
Software, customer environment, operations and user acceptance
A software-ready status does not imply live-customer approval while required environment checks, external-system validation or user acceptance remain incomplete.
Qualification evidence not loaded.
READINESS AREAS
Evidence, blockers and next action
Qualification evidence not loaded.
CUSTOMER VALIDATION & USER ACCEPTANCE
Checks that must be completed in the target environment
DOMAIN WORKSPACE · WATER & LABORATORY
Samples, analytical qualifiers, discharge assessments and correction impact
Operate governed laboratory evidence and water assessments without exposing LIMS transport internals. Sample revisions remain immutable; corrected source evidence creates a new revision and impact trail rather than overwriting prior custody.
LABORATORY EVIDENCE
Latest sample revisions
ASSESSED DISCHARGE PERIODS
Water compliance assessments
ASSESS WATER PERIOD
Run the existing governed assessment engine
Select an active obligation revision and bounded period. The server resolves the exact permit/method authority and qualifying laboratory evidence.
Correction impacts
DOMAIN WORKSPACE · WASTE
Waste inventory, manifests, custody transitions and receipt reconciliation
Follow each governed waste lot from generation through consignment and receiving evidence. A transport acknowledgement is not final disposal evidence; receipt reconciliation remains explicit.
INVENTORY
Generated waste lots
CONSIGNMENTS
Manifest custody state
CONSIGNMENT DETAIL
Events and receiving evidence
Open a consignment to inspect its immutable event and receipt history.
DOMAIN WORKSPACE · CARBON & ENERGY
Scope 1 and Scope 2 activity evidence, factors, inventory close and restatement
Review activity revisions, approved accounting authorities and calculated inventories with exact evidence custody. Independent carbon review remains separate from inventory calculation.
ACTIVITY EVIDENCE
Governed carbon and energy activities
ACCOUNTING AUTHORITIES
Boundaries and emission factors
INVENTORIES
Close, review and restatement lineage
Open an inventory to inspect reviews and restatement impacts.
DOMAIN WORKSPACE · PTW / SIMOPS
External permit context and advisory simultaneous-operations assessment
The external PTW system remains the permit authority. IndusMesh mirrors permit context and evaluates reviewed conflict rules, qualification/isolation requirements and governed gas-data freshness. It never issues a permit or declares work safe.
EXTERNAL PERMIT MIRROR
Current work-permit snapshots
SITE PROCEDURES
Reviewed conflict rules
ADVISORY ASSESSMENT
Assess a bounded work window
DOMAIN WORKSPACE · OCCUPATIONAL EXPOSURE
TWA, STEL and noise-dose evidence with hygienist review
This workspace exposes assessment results and approved exposure limits, not medical records or diagnoses. Personal/SEG sampling sessions remain restricted to administrator-scoped endpoints and are intentionally not listed here.
APPROVED LIMITS
Exposure-limit authority
ASSESSMENTS
Coverage and exposure results
SPECIALIST REVIEW
Occupational hygienist disposition
GOVERNED ENVIRONMENTAL AI
Governed Environmental AI
Permit assistance, root-cause hypotheses and visual observations remain advisory and evidence-linked. Authorized human review is required before AI recommendations can influence governed environmental records.
PERMIT ASSISTANCE
Grounded permit-clause candidates
Every candidate links back to the supporting document evidence. Independent permit review is still required before an extracted clause can become governed authority.
RCA SUPPORT
Competing evidence-backed hypotheses
Accepting a hypothesis records the reviewer decision only. Root cause becomes governed through the investigation workflow and must be linked to an existing investigation.
VISUAL OBSERVATIONS
Directly observable labels with specialist review
Image assistance is limited to policy-supported observable labels. It cannot infer hidden isolation state, permit validity, confined-space atmosphere or any safe-to-work conclusion.
REGULATORY EXCHANGE
Prepare, review, dispatch and record external disposition without conflating transport with legal acceptance
Prepare immutable regulatory payloads, review them independently, dispatch approved submissions, and record transport, receiving-system and legal filing outcomes as separate evidence states.
GOVERNED EXCHANGE PACKS
Qualified schemas, mappings and source profiles
Installed packs define deterministic packaging only; they do not infer applicability or regulator acceptance.
EXCHANGE RUNS
Immutable payloads and independent review
Select a run for review, dispatch, receipt recording or corrected resubmission. Prior runs remain immutable.
SELECTED RUN
Review, dispatch & external receipts
Select an exchange run.
ENVIRONMENTAL SOURCE CENTER
Know which environmental sources are ready, current and trustworthy
A source-centric operating view for Environmental Data Stewards. See readiness, latest accepted data, synchronization health, data-quality issues and the next action without needing low-level connection details. Data Preview performs a bounded, audited read to discover fields and profile representative values before mapping. Technical connection and mapping settings remain available in the Advanced tab for authorized administrators.
SOURCE PORTFOLIO
Environmental evidence sources
Each card separates source configuration from actual accepted environmental data. Select a source to inspect its business-facing readiness and operating history.
Select a facility to load environmental sources.
NOT CONFIGUREDCONFIGUREDSOURCE CONNECTEDDATA AVAILABLESTALEERROR
SOURCE DETAIL
Select a source
Choose a source card above to inspect readiness, visual field mapping, bounded source preview/schema profiling, synchronization history and data-quality state.
No source selected.
ADVANCED SOURCE HEALTH INVENTORY
Configured source ≠ received data
NOT CONFIGURED, CONFIGURED, SOURCE CONNECTED, DATA AVAILABLE, STALE and ERROR are distinct states. Plant measurements become environmental evidence only through verified industrial-edge replay.
Select a facility to inspect source readiness.
PLANT SOURCES
Map an existing connection to a governed measurement point
Create and test OPC UA, MQTT, Modbus, historian, REST, SQL or other connections in Industrial Connections first. This mapping does not create synthetic measurement evidence.
No source mappings loaded.
ENTERPRISE SOURCES
Register a reusable connection for this facility and domain
Shared Industrial Connections keep transport and credentials in one place while facility/domain registrations control where each connection may be used. Registration alone does not imply that environmental records have arrived.
No registered environmental enterprise sources.
LIMS PRODUCTION ADAPTER
Synchronize laboratory samples through a governed mapping
REST and SQL connections can synchronize from the control-plane runtime. SFTP and file connections remain edge-executed and post bounded record batches to the same governed transformer. Mapping qualification, checkpoints, corrections, rejects and replay remain visible.
No governed LIMS mapping revisions.
SYNC RUNS
No LIMS synchronization runs.
REJECT / DLQ
No unresolved LIMS records.
PTW AUTHORITY SYNCHRONIZATION
Mirror the external permit-to-work authority through a governed mapping
REST and SQL sources synchronize through the control-plane runtime. SFTP and file sources remain edge-executed and submit bounded batches. The external PTW system remains authoritative; IndusMesh only mirrors permit context for advisory SIMOPS.
No governed PTW mapping revisions.
SYNC RUNS
No PTW synchronization runs.
REJECT / DLQ
No unresolved PTW records.
WASTE MANIFEST INTEGRATION
Synchronize external waste manifests, lifecycle states and receipts
REST and SQL sources synchronize through the control-plane runtime. SFTP and file sources remain edge-executed and submit bounded batches. Manifest source revisions are immutable; incompatible core corrections go to reject/DLQ rather than rewriting prior custody.
No governed waste manifest mapping revisions.
SYNC RUNS
No waste synchronization runs.
REJECT / DLQ
No unresolved waste manifest records.
CARBON ACTIVITY INTEGRATION
Synchronize utility, ERP, procurement and meter activity records
REST and SQL sources synchronize through the control-plane runtime. SFTP and file sources remain edge-executed and submit bounded batches. Corrections create immutable superseding carbon activity revisions; cumulative meter rollover requires explicit reset context.
No governed carbon activity mapping revisions.
SYNC RUNS
No carbon synchronization runs.
REJECT / DLQ
No unresolved carbon activity records.
ENVIRONMENTAL AUTHORITIES
Permit, method and obligation readiness
Use the structured Permit & Obligation Workbench for normal authoring. The advanced compatibility console is intended only for authorized technical administrators.
Advanced raw authority JSON compatibility console
GOVERNED DOMAIN IMPORT
Feed LIMS, waste, carbon or PTW records
This is a bounded import console over existing domain APIs. It is not a bypass: the normal server-side validation, facility scope and domain custody rules still apply.
DATA PATH
Source → mapping/import → governed authority → workspace
Connection / external system→Source binding / governed mapping / sync job→Governed environmental record→Calculation / review→Environmental Evidence
ENVIRONMENTAL INTEGRATION OPERATIONS
Operate governed environmental synchronization
Integration scheduling, retry, exception and replay controls are separated from normal environmental work. Domain acceptance, permit authority, compliance conclusions and safe-to-work decisions remain outside synchronization operations.
ENVIRONMENTAL SYNC OPERATIONS
Schedule and operate LIMS, PTW, waste and carbon synchronization
Schedule and operate LIMS, PTW, waste and carbon synchronization with governed retries, mapping-version traceability, run history, freshness monitoring and controlled repair/replay.
Advanced timing and retry controls
No shared sync jobs configured.
EXECUTION HISTORY
No orchestration executions.
UNIFIED REJECT / DLQ
No unresolved cross-domain dead letters.
No environmental data-quality cases loaded.
SUPPLY CHAIN OPERATIONS
Supply Chain Overview
Start with the work relevant to your authorized role, then move into the owning Supply Chain workspace without losing the current partner scope.
Showing the authorized Supply Chain trust snapshot.
REQUIRES ATTENTION
Lifecycle and expiry signals
Only authoritative SC-00 lifecycle state and recorded expiry dates are used in this wave.
PARTNER PORTFOLIO
Relationship posture
Relationship types and states across the currently authorized network.
SHARED RESOURCES
Resources governed by partner workspaces
RECENT NETWORK ACTIVITY
Recently changed trust records
Home truth boundary
Role-based task entry points are derived from the current server-authorized capability profile. The home does not impersonate another role, create personal assignment, or infer operational KPIs from workflows that have not been loaded.
SUPPLY CHAIN OPERATIONS
Partner Network
Manage the canonical external-party graph: organizations → relationships → workspaces → agreements → shared resources.
Select an organization to inspect its cross-enterprise relationship context.
ORGANIZATIONS
Authorized network
No organization selected.
SUPPLY CHAIN OPERATIONS
Partner Access Center
External identity governance plus purpose-bound vendor/OEM JIT access and supervised privileged support sessions across the authorized partner context.
Partner access records are loaded from the authoritative SC-01 lifecycle APIs.
REQUIRES ATTENTION
Expiry & recertification
Signals are derived from SC-01 identity/sponsorship lifecycle fields and the current clock.
CURRENT SESSION
Effective partner access
Runtime access is re-evaluated server-side on browser requests. This panel does not grant authority.
PARTNER IDENTITIES
External people
Select a partner identity to inspect sponsorship and recertification.
RECERTIFICATION EVIDENCE
Recent access reviews
Reviews are immutable SC-01 evidence. Approval schedules the next review; suspend/revoke immediately changes sponsorship state.
Review history is available to authorized Supply Chain administrators.
VENDOR / OEM JIT ACCESS ·
Purpose-bound access requests
Request → sponsor/admin approval → ephemeral entitlement → one-time activation ticket. Every decision remains tied to partner identity, sponsorship, relationship, workspace, agreement, private-service binding and work order.
REQUEST QUEUE
Authorized requests
No JIT requests loaded.
Select a JIT request to inspect approvals, entitlement, session tickets and evidence.
PRIVILEGED SUPPORT SESSIONS ·
Supervised SSH / RDP / VNC operations
Governed sessions are created only after an approved JIT ticket is consumed by an authenticated private-mesh broker. Recording/transcript, clipboard, file transfer, printing, watermark and idle-timeout controls come from the authoritative SC-03 policy.
SESSION QUEUE
Privileged sessions
No privileged sessions loaded.
Select a privileged session to inspect controls, participants and evidence.
Partner access authority boundary
The browser only projects server-authorized identity, JIT and privileged-session operations. Enterprise directory identity, IdP state, sponsorship, relationship/workspace/agreement ownership, private-service binding, approval separation-of-duty, ephemeral entitlements, one-time ticket consumption and broker lifecycle remain authoritative on the server. Browser activation does not imply that an SSH/RDP/VNC session has started. SAML runtime remains explicitly unsupported by the SC-01 contract.
SUPPLY CHAIN OPERATIONS
Secure Partner Exchange
Governed cross-enterprise files from staged hash to malware/CDR evidence, approval, one-time release and signed transfer receipt. Raw file bytes remain in the approved staging and transfer data plane.
Secure exchange records are loaded from the authoritative SC-04 control plane.
Data-plane boundary
IndusMesh records business context, hashes, policy and evidence. Scanner/CDR and transfer-broker service identities move or attest bytes outside the control database.
EXCHANGE QUEUE
Authorized files
Select an exchange to inspect its policy, scan/CDR evidence, approvals, release and receipt.
SUPPLY CHAIN OPERATIONS
Data Contracts & B2B Interoperability
Run business-document exchange on governed SC-05 contracts, then project canonical semantics through GS1 EDI, UN/EDIFACT or ANSI X12 profiles and qualified AS2/AS4/SFTP adapter boundaries. Business users remain document-first; transport evidence is progressively disclosed.
B2B exchange records are loaded from authoritative SC-05 data-contract and delivery APIs.
Business first, transport second
The Data Exchange workspace keeps Purchase Order, Despatch Advice and Invoice workflows primary while the Interoperability tab exposes standards profiles, mappings, adapter bindings and cryptographic receipt evidence. The adapter executes wire encoding/transport; IndusMesh governs canonical semantics and evidence.
will add protocol/adapter evidenceBUSINESS DOCUMENTS
Cross-enterprise exchange
No B2B records loaded.
Select a business document or data contract to inspect its governed terms and evidence.
EPCIS 2.0.1 TRACEABILITY
EPCIS Traceability Explorer
Follow serialized objects, logistics units, transformations, custody and business context across enterprise boundaries while preserving EPCIS event immutability and GS1 identity truth.
Traceability is loaded from the authoritative SC-08 runtime. External normative/interoperability qualification is not inferred from source presence.
TRACEABILITY WORKBENCH
Explore events, identity journeys and governed distribution
Business context is shown first; canonical hashes, JSON-LD, capture provenance, sensor evidence and delivery dispatches remain available in detail.
EPCIS EVENTS
Authorized event history
No EPCIS events loaded.
Select an EPCIS event to inspect business context, objects, evidence and JSON-LD.
IDENTITY JOURNEY
Custody, aggregation & transformation graph
Select a tracked GS1 identity above to materialize its SC-08 trace graph. The digest covers the returned identity/event relationship projection.
Choose a GS1 identity to inspect its journey.
GS1 IDENTITY & MASTER DATA
GS1 Identity & Master-Data Workbench
Resolve and govern GTIN, GLN, SSCC, GRAI and GIAI against real Supply Chain and Industrial subjects. Syntax/check-digit validity and allocation ownership are deliberately shown as separate truths.
GS1 master data is loaded from the authoritative SC-07 runtime.
MASTER-DATA WORKBENCH
Identity, subject and resolver views
The UI does not mint external GS1 allocations. It records canonical identifiers and the evidence used to verify allocation ownership.
GS1 MASTER DATA
Authorized records
No GS1 records loaded.
Select a GS1 identity or master-data subject to inspect it.
ALLOCATION TRUTH
Validation is not allocation ownership
Canonical identity
SC-07 validates GS1 syntax/check digits, normalizes supported keys, binds the correct subject type and generates the GS1 Digital Link URI.
Allocation verification
An active identity additionally requires explicit document-verified or registry-verified allocation evidence. A valid number alone is never shown as proof of ownership.
CAPTURE PROVENANCE
Accepted EPCIS batches
Capture hashes bind the accepted event set. Capture presence does not imply independent normative schema/SHACL or external repository interoperability qualification.
No EPCIS captures loaded.
GOVERNED DISTRIBUTION
EPCIS subscriptions & dispatches
Subscriptions reuse enabled Enterprise Integration destinations. Matching captured events are enqueued with idempotency and each dispatch records the delivery ID and payload SHA-256.
No EPCIS subscriptions loaded.
Select a subscription to inspect its query and dispatch evidence.
SC-10 DATA-SPACE INTEROPERABILITY
Data-Space / DSP / EDC / Catena-X Workspace
Discover governed offers, verify participant identity, negotiate an SC-05-backed agreement and execute evidence-linked transfers without creating a second contract authority.
Loading SC-10 data-space state…
INTEROPERABILITY TRUTH BOUNDARY
Governed request projection, not external certification
SC-10 projects existing SC-05 bilateral contracts into DSP catalog, negotiation, agreement and transfer lifecycles. It stores credential identity and SHA-256 evidence, not raw credentials or private keys. External DSP 2025-1 TCK, DCP wallet interoperability and independent Tractus-X EDC end-to-end transfer remain SC-12 external qualification gates and are not claimed here.
SC-11 BATTERY DIGITAL PRODUCT PASSPORT
Battery Digital Product Passport Workspace
Govern item-level battery passport identity, completeness, revisions, lifecycle, role-based access, second-life lineage, data carrier and registry evidence from one workspace.
Loading SC-11 battery DPP state…
PUBLICATION & REGISTRY TRUTH
Server-validated passport, external registry boundary
The workspace calculates mandatory-data completeness from the published SC-11 data-point catalog for planning. Activation and waste publication still require server-side validation. Registry payload preparation and recorded outcomes are evidence records; they do not prove that IndusMesh itself submitted to or interoperated live with the EC DPP Registry.
UNIFIED ACTION CENTER
Supply Chain Action Center
One authorized queue for partner reviews, access approvals, secure-exchange release work, B2B exceptions, traceability corrections, data-space operations and Battery DPP stewardship.
Loading authorized Supply Chain work…
ACTION AUTHORITY
Unified read model, authoritative owning workflows
The Action Center derives work from SC-01 through SC-11 records already visible to this session. It never changes lifecycle state directly. Approvals, acknowledgements, release, correction, negotiation, transfer and publication actions remain authorized and recorded by their existing owning APIs and workspaces.
ACCOUNTABLE QUEUE
Open work
Select an action to inspect its source and owning workflow.
AUDIT INTEGRATION
Supply Chain Evidence Graph & Investigation
Trace immutable evidence references across partner exchange, B2B, EPCIS, industrial provenance, data-space and product-passport records without duplicating the authoritative evidence itself.
Loading SC-09 evidence graph…
EVIDENCE TRUTH BOUNDARY
References and hashes, not copied evidence
SC-09 indexes immutable source hashes, organization scope and relationships between authoritative records. Graph reads recompute each source hash and report Current, Changed or Missing. A changed or missing source is an investigation signal, not an automatic finding or compliance conclusion.
RELEASE TRUTH
Evidence, Audit & Deployment Readiness
Separate implemented capability, locally executed software qualification, independent interoperability, customer-site qualification and final production admission. A local PASS never overrides an unexecuted or blocked production gate.
Loading exact SC-12 release truth…
ADMISSION BOUNDARY
Locally qualified does not mean production-qualified
END-USER ACCEPTANCE
Production UX and human acceptance
Automated accessibility, responsive-layout, keyboard-flow and cross-workspace journey checks are qualification evidence for the application build. They do not replace acceptance by real Supply Chain users in the target deployment environment and they do not change the SC-12 production-admission decision.
ZERO TRUST APPLICATION ACCESS
Application Launchpad
Launch only applications currently granted to you, request eligible access, and use unified zero-trust policy enforcement across browser, tunnel and privileged sessions.
CONTINUOUSLY AUTHORIZEDLaunchpad presentation never grants access by itself.
DEVICE TRUST & POSTURE
My Secure Access Devices
User devices are distinct human endpoint principals. Trust, posture and certificate state remain server-authoritative.
ACTIVE AUTHORITY
My Secure Access Sessions
Privileged sessions are shown directly. Browser and native sessions remain governed by their parent application policy and continuous authorization.
ZERO TRUST APPLICATION ADMINISTRATION
Secure Access Administration
Configure application authority and review runtime evidence without bypassing the owning APIs.
INDUSTRIAL DATA FABRIC
Contextualize plant data without exposing plant networks
IndusMesh OS unifies live industrial and enterprise sources into one searchable explorer while preserving private edge mesh connectivity as the secure transport layer underneath.
0%configuration coverage
UNKNOWNVerified connection health unavailable
CANONICAL FLOW
Industrial DataOps lifecycle
EDGE RUNTIME
Edge hubs
TRUSTED OUTPUT
Data products
INDUSTRIAL OPERATOR EXPERIENCE
Run the site from one evidence-backed operational view
Commissioning readiness, source health, governed commands, safety controls, manufacturing context, AAS coverage, enterprise delivery and investigations are derived from the existing authoritative IndusMesh stores.
—verified connection health
SITE READINESS
Commissioning & plant model
CONTROL SAFETY
Approval & failed-write investigation
QUALITY HEATMAP
Bad, stale, suspect & anomalous data
ENTERPRISE HANDOFF
Integration delivery health
BOUNDED TREND INVESTIGATION
Detect → investigate → evidence → governed action → outcome
Times are displayed in the selected facility timezone and sent to the historian as exact RFC3339 instants. No observations is a valid result and is never treated as zero.
GOVERNED QUALITY ALERTS
Priority, acknowledgement, shelving & escalation
SITE HEALTH TIMELINE / EVENT CONSOLE
Commissioning, quality, command, safety & integration events
INVESTIGATION PATHS
Move from symptom to authoritative context
Source & qualityInspect live/configured source paths, protocol health, stale/bad/uncertain quality and historian context through Connections, Explorer and historical query surfaces.
Asset & manufacturingUse canonical asset identity, ISA-95-aligned manufacturing context and AAS 3.2 facade without creating another asset master.
Command & evidenceInvestigate pending approvals, policy state, execution/readback evidence and audit history; no direct write bypass is exposed here.
DRIVER REGISTRY
Connector SDK & capabilities
PRODUCTION MQTT
MQTT & Sparkplug B runtime
MQTT 3.1.1 + MQTT 5TLS/mTLS · QoS 0/1/2 · retained messages · wildcard subscriptions · reconnect/backoff · cached topic reads
ProductionSparkplug BGoverned profile: Primary Host gating · NBIRTH/DBIRTH + DDEATH/NDEATH lifecycle · bdSeq/seq controls · historical flags · governed NCMD/DCMD
ProfileSecret-safe credentialsUse credential_ref with env://NAME or file:///run/secrets/name.json. Raw secrets remain blocked from persisted connection config.
Runtime onlyPRODUCTION OPC-UA
Address-space & tag browser
OPC-UA Binary/TCPProduction driver boundary: browse/read/subscriptions · controlled writes · typed values · reconnect handling
ExecutableFail-closed protocol securityQualified-driver architecture supports configured secure policies and Sign/SignAndEncrypt with X.509 identity. Legacy None-only behavior is not the current production claim; independent interoperability remains pending.
Evidence gatedSelect an OPC-UA connection and browse its address space.
PRODUCTION MODBUS TCP
Register map & tag browser
Modbus TCP clientFC01/02/03/04 reads · FC05/06/15/16 writes · transaction/unit validation · exception handling · safe reconnect behavior
ExecutableIndustrial register semanticsTyped 16/32/64-bit integers and floats · strings/register arrays · byte/word order · scale/offset · explicit writable controls
Address mapPrivate-path protocolModbus TCP has no native authentication or encryption. Use IndusMesh private connectivity, network segmentation, and least-privilege output contracts for writes.
Network protectedSelect a Modbus connection and browse its configured address map.
ENTERPRISE DATA SOURCES
REST, SQL, SFTP & File browser
REST / HTTPTLS/mTLS · Basic/Bearer/API-key auth · mapped JSON resources · governed POST/PUT/PATCH/DELETE writes
ProductionSQL / PostgreSQLSchema metadata · parameterized query/command contracts · TLS · read/write gates · polling
ProductionSFTP & FilesHost-key verification · credential references · root-path containment · atomic/local writes · file polling
ProductionSelect an enterprise source connection and browse its resources.
INPUTS / OUTPUTS
Connection endpoints
INDUSTRIAL INTEROPERABILITY
Industrial Interoperability
Operate incumbent, standards, query, synchronization, migration and governed-write workflows through one capability-aware application boundary.
View interoperability lifecycle
DISCOVERY & SEMANTIC MAPPING
Browse → Preview → Map → Validate → Activate
Browse each source through its authoritative connector hierarchy, inspect live source semantics, bind observations to canonical model fields, validate the mapping, then activate only through server-governed validation.
Activation means the canonical mapping is valid for downstream use. It does not mean the incumbent product/version/interface is exact-target qualified, independently certified, or production qualified.
Choose a source connection and browse its hierarchy.
SOURCE PREVIEW
Observed value and source semantics
Select a readable source item to preview timestamp, value, unit, quality and provenance.
CANONICAL SEMANTIC BINDING
Map source identity to an Industrial Model instance
Mappings are written to the existing IndustrialInstance binding contract. This workspace does not create a second mapping store.
Choose an instance to inspect its model schema and current bindings.
Validation and activation evidence will appear here.
i3X & STANDARDS EXPLORER
Namespace → Type → Object → Relationships → Current → History
Explore the live i3X 1.0 semantic address space through product concepts rather than REST paths. Type, relationship, object and value data come from the existing canonical semantic and evidence authorities.
Open this workspace to load live compatibility posture.
TYPE CONTRACT
Semantic schema
Choose an object type.
OBJECT INSTANCE
Canonical identity
Choose an object.
RELATIONSHIP TYPES
Bidirectional semantic links
Relationship types will appear after namespace selection.
RELATED OBJECTS
Traverse from the selected object
CURRENT VALUE
Value, quality and timestamp
Read current value for the selected object when needed.
HISTORICAL VALUES
Bounded retained history
Choose a bounded time range and read retained history.
Capability boundary: direct normative current-value update, historical update and SSE subscription streaming are not presented as available. Governed changes use the separate IndusMesh request → safety/policy → approval → execution → readback workflow.
INDUSTRIAL INTEROPERABILITY
Coexist with incumbent industrial-data platforms without losing source semantics
Bind an existing Industrial Connection to a named incumbent or industrial-cloud platform and govern discovery, hierarchy, timestamps, quality, units, historical access, federation, backfill and reconciliation through one evidence-gated contract.
Greenfield or coexistenceDeploy IndusMesh as the primary industrial data fabric, or coexist with an existing historian, gateway, Unified Namespace or industrial-cloud platform.
FlexibleTruthful support boundaryCatalog availability means the adapter framework exists. A named product/version/API is supported only after exact external qualification evidence passes.
Evidence gatedPORTFOLIO
Interoperability readiness
INCUMBENT FAMILIES
Reusable adapter framework
These profiles reuse the existing connector, historian and federation runtimes. They do not create parallel transport engines.
QUALIFICATION & EXACT-TARGET READINESS
Evidence-backed interoperability truth
Separate framework availability, exact product/version/interface evidence, independent interoperability, customer-site evidence, i3X compatibility, certification and deployment readiness. Missing or unexecuted evidence never becomes PASS.
Qualification posture not loaded.
No exact-target readiness loaded.
QUALIFIED INTEROPERABILITY PROFILES
Qualified incumbent and time-series compatibility contracts
Choose the exact interface you operate. Each profile has its own evidence scenarios so protocol, historian, SQL, time-series, namespace and cloud evidence cannot be mixed across products.
Loading qualified profiles…
MODERN HISTORIAN & TIME-SERIES
Canary, TimescaleDB and InfluxDB interoperability
Use Canary as an incumbent historian, or connect modern time-series stores without losing source series identity, source timestamps, quality/status, units, bounded query semantics, checkpoints or reconciliation evidence.
Canary HistorianReuses the native Canary Views Read API provider and signed historian qualification boundary.
External targetTimescaleDBPreserves database/schema/hypertable/time-column identity through governed PostgreSQL/SQL connectivity.
External targetInfluxDBPreserves organization/bucket/measurement/field/tag-set identity through the governed query/historian boundary.
External targetUNIFIED NAMESPACE
Coexist with existing MQTT and Sparkplug namespace estates
Consume an existing namespace without replacing its broker or publisher. Broker compatibility is qualified separately from namespace semantics so MQTT connectivity never becomes a false Sparkplug or UNS claim.
MQTT / Sparkplug B UNSPreserves group, edge-node, device, metric, alias, birth/death, sequence, timestamp, quality and unit semantics.
External targetIgnition MQTT / SparkplugQualified as a namespace publisher independently from Ignition OPC UA and Tag Historian evidence.
External targetHighByte Intelligence HubPreserves published topic, model/instance keys, source timestamps, quality and engineering-unit metadata.
External targetLitmus EdgePreserves published asset/tag and payload identity through the existing MQTT and UNS governance runtime.
External targetHiveMQ & EMQXBroker qualification covers MQTT protocol, TLS/mTLS, QoS, sessions, retained messages, ACLs and reconnect behavior; it does not imply namespace semantics.
Broker evidenceINDUSTRIAL CLOUD
Coexist with industrial cloud data platforms without losing plant-source evidence
Use the existing REST, MQTT, semantic, federation and durable-delivery runtimes. Each cloud lane preserves provider-native identity and remains independently evidence-gated; cloud connectivity never proves source quality or another provider's compatibility.
AVEVA CONNECT / SDSPreserves tenant, namespace, stream/property identity, timestamps, status and units across bounded Sequential Data Store access.
External targetCognite Data FusionPreserves CDF project plus instanceId or asset-centric external identity, data-model context and time-series datapoint semantics.
External targetAWS IoT SiteWisePreserves asset/model/property identity, property aliases and timestamp-quality-value semantics. Delivery success never substitutes for source quality.
External targetAzure IoT OperationsReuses MQTT/REST runtimes while preserving data-flow endpoint, route/topic, source timestamp and payload semantics.
External targetMicrosoft Fabric Real-Time IntelligencePreserves workspace, Eventhouse, database/table and source-key identity with bounded query and ingestion reconciliation evidence.
External targetQUERY & FEDERATION
Current, historical and cross-source analysis
Start with the question you need answered, choose governed signals by name, then run the existing authoritative query path. Timestamp, quality, unit and provenance stay visible so a convenient analysis never hides source truth.
Advanced: enter source references manually
Advanced: canonical selector import
Choose governed signals from the source browser.
Add to query
SOURCE BROWSER
Find governed tags, attributes and objects
Select a source to browse available industrial objects.
SOURCE POSTURE
Authority and readiness
Technical route and export boundary
The workbench composes existing source, native historian, i3X and federated-query APIs. No new export authority is introduced; downstream export remains available only through already-authorized product/API paths.
Choose a source, query mode and bounded scope.
DURABLE CONSUMER OPERATIONS
Monitor changes without losing your processing checkpoint
Choose what your consumer watches, check for durable changes, process them downstream, and confirm only the highest sequence actually completed. Sequence gaps and expiry stay visible and fail closed.
Delivery boundary: a returned batch is waiting for your consumer; it does not prove downstream processing. Never acknowledge past a sequence gap. Expired subscriptions fail closed and are not silently revived.
Technical model: Subscriptions, sequence checkpoints & acknowledgement
The underlying i3X durable-consumer contract remains unchanged; this workspace presents it as consumer processing work. SSE streaming is not supported; each returned batch remains pending consumer acknowledgement until the consumer explicitly advances its checkpoint.
Consumer identity
Lifecycle
SUBSCRIPTIONS
Owned consumer subscriptions
No subscriptions loaded.
SELECTED CONSUMER
Queue, checkpoint & expiry
Select or create a subscription.
REGISTERED OBJECTS
Choose semantic objects to monitor
Objects are validated by the existing i3X semantic query context before registration.
Select a subscription to inspect registered objects.
SYNCHRONIZATION
Pull changes & advance acknowledgement
Operations
Synchronization history appears after the consumer synchronizes.
REPLICATION & RECOVERY OPERATIONS
Resume changes safely and reconcile what happened
Define a governed signal scope, inspect its server checkpoint, fetch the next changes or resume after failure, then reconcile a bounded window. Source-read success never becomes target-parity evidence by implication.
Truth boundary: incremental read success proves only that the configured source returned a bounded change set. Target parity is shown only from an existing authoritative reconciliation record; exact-target qualification and production admission remain separate states.
Technical model: Checkpoints, watermarks & reconciliation
The server-owned replication and recovery contract remains unchanged; the guided controls below operate that same authority.
Advanced: enter source references manually
SIGNAL SCOPE
Choose governed source signals
Choose a profile, then browse or enter source references.
Browse the selected source to add signals by name.
RECONCILIATION WINDOW
Choose the period to verify
Custom start/end fields remain available above.
CHECKPOINT & WATERMARK
Durable resume posture
Choose a profile and source references to inspect checkpoint state.
SOURCE / TARGET PARITY
Bounded reconciliation evidence
Target counts are not inferred from source reads.
LATEST INCREMENT
Preserved source observations
Pull an increment to inspect timestamp, quality, unit and source metadata preservation.
RECONCILIATION
Source-window evidence & mismatch investigation
Run a bounded source reconciliation. Target parity remains separate unless an authoritative target reconciliation exists.
RECOVERY LOG
Retries, failures & session operations
Operations in this browser session appear here. Authoritative recovery state is the server-side checkpoint.
Failure recovery contract
FEDERATED QUERY & ZERO-COPY
Query qualified industrial sources in place
Plan and execute bounded historical reads across qualified historian profiles without replicating source observations into IndusMesh. Every row retains profile, source-reference, timestamp, quality, unit and native metadata provenance.
Select qualified profiles and plan a bounded zero-copy query.
HISTORICAL MIGRATION & CUTOVER
Move history through an evidence-bound cutover lifecycle
Configure → Validate → Backfill → Delta catch-up → Reconcile → Acceptance → Cutover → Observe. Reconciliation proves bounded parity; it is not approval. A separate authorized acceptance is required before cutover, and any later catch-up invalidates both reconciliation and acceptance.
GOVERNED MIGRATION MAPPING
Choose source signals and their canonical targets
Build each migration mapping from a browsed source signal and an existing governed source binding. The binding supplies the canonical facility, measurement point, source identity and quantity semantics required by the migration authority.
Source discovery
Add mapping
No governed migration mappings selected.
Advanced: import governed binding tuples
Acceptance is a separate governance decision from reconciliation. The same actor cannot both reconcile and accept. Any new backfill or catch-up batch invalidates previous reconciliation and acceptance before cutover can proceed.
Create or select a bounded migration job to assess readiness.
Cutover truth boundary
Commit Cutover is enabled only for the latest zero-mismatch reconciliation plus explicit acceptance. Customer maintenance-window execution, upstream source freeze, external target certification and post-cutover production behavior remain separate evidence obligations. Rollback never deletes migrated history; it restores authority state while retaining append-only evidence.
GOVERNED BIDIRECTIONAL DATA SYNC
Request and verify bounded data-state changes
Create typed changes against an active allowlist policy, then keep requester, approver, executor and verifier responsibilities separate. Transport acknowledgement is not destination-state proof; provider readback remains the verification authority.
PLC, actuator and setpoint commands are never authorized by this workflow. Industrial control remains exclusively governed by the dedicated safety command plane.
Policy administration · advanced
Create or select a write-back policy to evaluate exact-target authorization.
REQUEST A CHANGE
Typed bounded write request
Choose only allowlisted targets. Idempotency is generated automatically for normal requests. Timestamp and optimistic-current-hash guards remain available under Advanced.
Select a policy to build a typed request.
Advanced request controls
No governed write-back requests in this scope.
i3X and control-command boundary
Normative i3X current-value PUT and historical PUT remain unsupported. The i3X governed-write bridge creates a pending Industrial Command and does not approve or execute it. This interoperability write-back workflow governs bounded data-state synchronization only; PLC, actuator and setpoint commands remain exclusively in the industrial control-safety command plane.
SOURCE / TARGET CENTER
Industrial connections and interoperability bindings
Connect incumbent historians, industrial sources, cloud services, Unified Namespace brokers and i3X endpoints through governed connection records. Credential material stays in external secret stores; only references are retained here.
Loading source and target inventory…
GUIDED CONNECTION ONBOARDING
Connect an industrial source or target
Choose the platform family and exact interface where known, bind or create a governed connection, review the qualification boundary, then create the interoperability profile.
Framework support does not mean an exact installed product/version/interface has passed external qualification.
Complete the guided fields and review the plan before creating a binding.
Advanced profile editor Direct access to the retained interoperability profile controls
CONFIGURED PROFILES
Configured interoperability targets
No interoperability profiles configured.
PROFILE
Select a profile
AVEVA PI SYSTEM
PI Web API & Asset Framework interoperability
Discover PI Data Servers, AF hierarchy, PI Points and Event Frames; preserve source timestamps, quality flags, engineering units and digital states across federated reads, incremental replication and migration reconciliation.
Read-only coexistencePI remains source authority. IndusMesh does not write PI values or infer alarm/regulatory meaning from Event Frames.
Source preservingAuthentication boundaryBasic, bearer and mTLS credential references are supported by the repository adapter. Windows/Kerberos support remains external qualification work.
Fail closedSave an AVEVA PI profile, then probe or discover the configured PI Web API target.
PROCESS HISTORIAN INTEROPERABILITY
Enterprise process historian ecosystems
Deep profiles for AspenTech InfoPlus.21, Honeywell Uniformance PHD, GE Proficy Historian, Rockwell FactoryTalk Historian and Siemens Process Historian / WinCC. Discover tags and hierarchy, preserve timestamps, raw quality/status, engineering units and corrections, query bounded history and server aggregates, resume from durable checkpoints, and reconcile before coexistence or migration cutover.
Source remains authoritativeFederated reads do not rewrite the incumbent historian. Replication and migration retain source identity, quality/status and correction markers for reconciliation.
Read-only sourceInterface boundaryRepository fixtures prove the normalized adapter contract. Proprietary/native interfaces and exact installed versions remain customer-site qualification items.
Evidence gatedSave a supported process historian profile to exercise the governed deep-historian contract.
OPERATIONS, EVIDENCE & INVESTIGATION
Detect → Investigate → Correlate evidence → Act in owning workflow → Verify
A read-only operational projection over qualification, migration, durable subscription, governed-write delivery/readback and exact-target evidence. It does not create a parallel incident, retry, evidence or audit authority.
TARGET HEALTH
Readiness and evidence posture
Target health loads from server-derived interoperability truth.
TRUTH BOUNDARIES
Evidence and compatibility
Truth boundaries load with operations state.
INVESTIGATION QUEUE
Failures, mismatches, expiry and verification gaps
No investigation state loaded.
Select an attention item to correlate evidence and open its authoritative workflow.
EVIDENCE CHRONOLOGY
Exact-target, reconciliation and provider-readback evidence
Evidence references and digests remain attached to their authoritative resource. This view never upgrades missing, failed, expired or local evidence.
No evidence chronology loaded.
OPERATIONAL CHRONOLOGY
Qualification, migration and governed-write state changes
No operational chronology loaded.
READINESS
Exact-target support boundary
Select a profile to evaluate framework and qualification readiness.
RECONCILIATION
Coexistence and migration acceptance plan
Select a profile and mode to generate the evidence-backed reconciliation contract.
QUALIFICATION EVIDENCE
Exact product / version / interface evidence
Recording evidence does not make a claim automatically. A passed qualification must cover every required scenario and retain an evidence digest.
No qualification evidence recorded.
Record qualification evidence
For Ignition or KEPServerEX OPC UA, import the exact commercial-server qualification report. Standard smoke evidence remains partial until all profile semantics are proven.
ENTERPRISE DATAOPS WORKBENCH
From raw industrial source to governed data product in one flow
Browse connected data, curate authoritative fields, shape a reusable model, bind a live instance, design and test a pipeline, then publish a governed contract without losing source lineage.
0%flow readiness
GUIDED JOURNEY
Industrial DataOps lifecycle
ENGINEERING IMPORT & COMMISSIONING WORKBENCH
Preview, diff, validate, commission, snapshot & rollback
Import engineering metadata into the canonical industrial model without writing PLC/controller process values. Source file content is hashed for provenance but is not persisted.
CURRENT PREVIEW
Candidate diff
Run Preview & Diff to inspect create/update/no-op/conflict decisions before commissioning.
GOVERNED LIFECYCLE
Engineering imports
No engineering imports loaded.
01 · DISCOVER & CURATE
Source browser
Search the existing discovery index and curate the exact fields that belong in the semantic contract.
Search connected industrial sources to begin.
CURATED CONTRACT INPUT
Selected source fields
Select readable source fields from the browser.
02 · MODEL & BIND
Semantic model and live instance
03 · TRANSFORM & TEST
Pipeline
04 · PUBLISH
Governed output
FLOW QUALITY
Readiness checks
UNIFIED SOURCE EXPERIENCE
Explore every industrial source from one workspace
Search and browse MQTT topics, OPC-UA nodes, Modbus tags, REST resources, SQL datasets, SFTP paths and mounted files without switching connector-specific tools.
0indexed items
SOURCE CATALOG
Connected industrial & enterprise sources
COLUMNAR STORAGE & TIME-SERIES ENGINE
ClickHouse Streaming Ingestion & Continuous Rollups
DISCOVER & SEARCH
Cross-source search
Search the discovery index or select a source and browse its root.
LIVE VALUES
Selected source values
Use Live read on any readable item to inspect its value, quality and source timestamp.
INDUSTRIAL SEMANTIC GRAPH
Govern semantic change before it reaches industrial operations
Model and resolve canonical industrial semantics, branch from immutable published versions, inspect the industrial blast radius, collect checksum-bound approvals, and promote only governance-ready candidates.
—contract state
GOVERNED VERSION
Semantic graph workspace
EXP-01 · MANUFACTURING STARTER PACK
Install a governed Day-1 manufacturing ontology
Enterprise → Site → Area → Production Line → Machine, plus measurement points, products, production orders and downtime events. Installation creates semantic definitions only—no demo assets, telemetry, source bindings, schedules, predictions or plant commands.
Installs as a scope-bound draft in the current project/environment and follows the existing review/publish lifecycle.
Relationships
8
Topology, measurement, production, downtime
Views
3
Plant, production, reliability
Operational writes
0
Definitions only
EXP-04 · GOVERNED SELF-SERVICE PROPOSALS
Propose → impact → independent review → promotion handoff
Contributors work in isolated candidate drafts anchored to the active published checksum. Submission automatically refreshes blast-radius evidence; self-publish is never granted.
SELF-PUBLISH DENIED — Proposal authoring can change only the isolated candidate. Review and promotion remain independently authorized and checksum-bound.
Create or select a proposal. Preview Impact is optional; Submit Proposal automatically refreshes impact evidence against the exact candidate checksum.
Reviewer assignments, conflicts, proposal warnings and exact-checksum handoff evidence appear here.
ENGINEERING CONTEXT
Permission-aware documents for canonical assets
Links preserve semantic checksum plus immutable document revision/hash. Restricted document titles, snippets and links are filtered server-side for every consumer.
Enter a canonical facility, asset, measurement point or manufacturing reference to load authorized engineering context.
SOURCE → SEMANTIC GRAPH
Canonical resolution preview
Enter an existing IndustrialSourceBinding source ID. Resolution is read-only and authority-owned; it does not duplicate assets or measurements.
Resolve a source to inspect canonical semantic nodes and relationships.
EXP-03 · VISUAL SEMANTIC AUTHORING
Interactive Semantic Canvas
Create governed object types from ISA-95 templates, arrange them on a snap grid, connect relationship ports, and inspect definitions without leaving the existing semantic draft lifecycle.
Select or load a semantic graph version to visualize and author its ontology.
Drop template to place a governed object type
Move: drag node or use arrow keysConnect: drag output port → input port, or click source then targetCancel connection: Esc
OBJECT TYPES
Industrial concepts
Select a semantic graph version.
RELATIONSHIPS
Meaningful connections
Select a semantic graph version.
SEMANTIC VIEWS
Bounded graph projections
Select a semantic graph version.
MODEL INSPECTOR
Select a graph resource
Choose an object type, relationship or view to inspect its governed definition and compiled semantics.
SUSTAINABILITY MODEL LIBRARY
Start from governed industrial semantics, then bind them to real plant data
Use versioned reference models for energy, water, waste, emissions and utility assets. Every installed model becomes a normal IndusMesh semantic contract with canonical library provenance; clone it before customizing canonical fields or units.
0reference models
GOVERNED SELF-SERVICE
Model → instance → binding → validate → proposal → independent review → publish
An installed or active model is a semantic contract, not proof that plant data is live. Materialization reads configured sources; publication and deployment remain separate governed outcomes.
REFERENCE CATALOG
Industrial & Sustainability Model Library
Loading industrial model catalog…
SEMANTIC CONTRACTS
Reusable Models
PHYSICAL CONTEXT
Model Instances
SEMANTIC WORKBENCH
Definition, binding & live materialization
AI MAPPING ASSISTANT
Propose source bindings with confidence & rationale
Ranks governed Data Explorer sources against semantic fields. Suggestions never modify models or sources; Apply is an explicit operator action.
Select a model instance, then analyze the project Data Explorer index.
MODEL FIELDS
Semantic definition
Select a model or instance.
INSTANCE BINDINGS
Source mapping
Select an instance to map source data.
DATA EXPLORER
Bind discovered source
Search the Data Explorer index for a source.
No source selectedChoose a readable source result to bind it to a model field.
LIVE INSTANCE
Materialized values
Materialize an instance to read all bound source values at once.
GOVERNED UNIFIED NAMESPACE
Organize industrial meaning from enterprise to physical instance
Build a governed enterprise → site → area → line → asset → instance hierarchy while preserving model identity, source bindings and live resolution.
0published instances
UNIFIED NAMESPACE
Hierarchy
Create an enterprise root or publish a model instance into the UNS.
SELECTED NODE
Semantic identity & live resolution
Select a namespace node to inspect its identity and publication state.
LIVE INSTANCE
Resolved semantic values
Resolve a published instance node to materialize its bound source values.
PUBLISH MODEL INSTANCE
Place a physical instance into the UNS
Choose an existing asset/line/folder parent, or let IndusMesh create/reuse the canonical enterprise/site/area/line/asset path.
AI PIPELINE COPILOT & OPERATIONS
Describe, design, debug and operate industrial data flows safely
Natural-language Copilot proposals feed the same governed Visual Pipeline Studio, validator, debugger, replay and observability stack without auto-saving or auto-running changes.
0stages in draft
BUILDER STAGE · TRANSFORM & TEST
Draft validity is not production execution
Preview and validation establish only the current pipeline definition. Saving creates a version; running, release admission, target deployment and runtime verification remain distinct evidence-backed steps.
AI PIPELINE COPILOT
Describe the industrial flow you want
Copilot proposes an unsaved Studio draft from governed Connections, Instances and UNS metadata. It never saves or executes the proposal.
Describe a flow to receive a governed pipeline proposal, or explain/repair the current unsaved draft.
Copilot output is advisory. Write stages remain non-retriable and subject to output contracts, residency policy and explicit operator save/run actions.
DAG
Pipeline canvas
Drag a stage from the palette to start designing.
Drag stage cards to repositionDrag an OUT port onto an IN port to connectDelete/Backspace removes the selected stage
VALIDATION & EXECUTION
Run pipeline
Validate the draft or saved pipeline to inspect its executable contract.
STAGE CONTRACT
Execution plan
No execution plan loaded.
AUTOMATION
Schedule & event triggers
No triggers loaded.
PROMOTION & REUSE
Environment lifecycle
Reusable components are write-free and version-pinned. Promotion copies the saved pipeline into a target environment and validates destination references before recording the promotion.
No promotions recorded.
STAGE DEBUGGER
Execute to breakpoint
Select a stage and execute only through that breakpoint.
DURABLE HISTORY
Pipeline runs
No runs loaded.
TRACE
Run inspector
Select a pipeline run to inspect stage attempts, duration, outputs, and failures.
OBSERVABILITY
Pipeline health · 24h
Operational telemetry loads with the selected pipeline.
DEAD LETTER QUEUE
Failed pipeline work
No dead letters loaded.
REPLAY SAFETY
Operator-controlled reprocessing
Replay uses the saved definition snapshot from the original run. Replay from this workspace is restricted to terminal snapshots without write or output stages. Delivery or write recovery requires destination reconciliation in the owning governed workflow.
Legacy historical runs without a definition snapshot are not guessed or upgraded automatically; exact replay fails closed.
DATA PRODUCTS & INDUSTRIAL REST API
Governed data products
Turn models, instances, UNS nodes and pipeline outputs into versioned, access-controlled consumption contracts.
CATALOG
Products
CONTRACT
Select a product
VERSIONS
Immutable contracts
CONSUME
Industrial REST API
Publish a product to generate a stable Industrial REST contract.
CENTRAL HUB & DISTRIBUTED EDGE FEDERATION
Federated industrial sites
Browse governed remote catalogs and read approved edge data without centralizing all plant telemetry.
CENTRAL CATALOG
Edge peers
TRUST & TARGET
Select a peer
REMOTE NAMESPACE
Cached UNS catalog
REMOTE DATA PRODUCTS
Governed edge products
Select a remote namespace node or product to perform a live read through the Edge federation policy.
ENTERPRISE EDGE OPERATIONS
Fleet Command Center
Account fleet snapshot with observation times, drift, credential and storage attention, rollout reports and exact-release eligibility. Reported eligibility and update completion do not prove deployed boot health.
CONFIGURATION DRIFT
Nodes requiring attention
STAGED DELIVERY
Rollout campaigns
ENTERPRISE SECURITY RELEASE ADMISSION
Qualification + supply-chain security gate
Fail-closed admission for exact artifacts. A qualified release can still be blocked by unsigned artifacts, missing SBOM/provenance, or vulnerability thresholds.
Evaluate an exact candidate before starting a fleet rollout.
IEC 62443 READINESS
Security zones, conduits & control coverage
Engineering readiness mapping only; this does not represent formal IEC 62443 certification.
SEMANTIC INDUSTRIAL OPERATIONS STUDIO
One object-centric workspace from machine context to governed action
Search canonical industrial objects, then inspect semantic meaning, live twin state, dependency lineage, scenarios, action governance and command evidence without switching mental models or creating another source of truth.
Boundary: Operations Studio composes existing governed authorities. Contextual actions navigate into the existing SEM/TRACE/TWIN surfaces; scenario-to-command handoff still requires dual-custody Industrial Command approval. This workspace performs no direct plant write.
INDUSTRIAL OBJECTS
Search results
Search for an industrial object to begin.
SELECTED OBJECT
No object selected
Select a result to load its semantic operations context.
LIVE OPERATING CONTEXT
Twin & telemetry health
Digital twin context is available for assets and process segments.
DEPENDENCY CONTEXT
Traceability & consumers
Traceability context will appear for supported objects.
GOVERNED DECISION CHAIN
Scenario → simulation → action package → command
Evidence-oriented chronology for the selected twin subject. Simulation is kept distinct from approved plant control.
No governed lifecycle activity loaded.
RELATED OBJECTS
Canonical neighborhood
Value Ledger · EVIDENCE-BACKED INDUSTRIAL VALUE LEDGER
Measured change → explicit attribution → reviewable value
Create value cases from immutable industrial evidence IDs. Value Ledger never accepts a typed baseline/after number as proof, never converts currencies, and never treats before/after correlation as automatic causality.
Claim boundary: Monetary rates and attribution percentages are explicit assumptions. Approved cases prove the evidence and review chain recorded by Industrial Mesh; they do not independently prove financial causality.
VALUE CASES
Evidence-backed claims
Load Value Ledger to inspect governed value cases.
SELECTED CASE
No case selected
Select a value case.
IMMUTABLE ASSESSMENT
Evidence, attribution & monetization
Assess a draft case to calculate evidence-backed change.
LIVE ASSET / PROCESS DIGITAL TWIN
Operational twin over canonical industrial context
Read-only projection of asset/process topology, ISA-95 context, AAS aliases, semantic classifications, traceability, latest governed telemetry and bounded history. Viewing a twin never polls or writes a device.
Boundary: telemetry freshness/quality is not a physical-condition diagnosis, and live digital twin views perform no prediction or simulation.
LIVE STATE
Latest governed telemetry
Load a twin to inspect live governed values.
CANONICAL TOPOLOGY
Asset & process context
AAS + SEMANTICS
Identity & classifications
BOUNDED HISTORY
Recent operating context
SCENARIO SIMULATION & COMPARATIVE ANALYSIS
Offline what-if laboratory
Capture the current digital twin state, apply explicit bounded overrides, and compare modeled outcomes. Simulated values never leave this offline analysis path and are never written to plant systems.
Load a twin, define a bounded scenario and run it to compare baseline versus simulated state.
SCENARIO → GOVERNED INDUSTRIAL ACTION
Evidence-bound action handoff
Map one changed Twin Simulation value to an explicit governed output endpoint, run static safety preflight, obtain independent package approval, then hand it off as a normal pending Industrial Command. This surface never executes the plant write.
Run a simulation scenario, then map one changed value to an explicit governed output endpoint.
TRACEABILITY
Source → twin → downstream dependencies
PROVENANCE, EVIDENCE & CHAIN OF CUSTODY
Trace every number to its source and evidence
Immutable evidence hashes, append-only lineage, tamper-evident custody events and point-in-time provenance snapshots.
AI-Semantic Modeling · GOVERNED NATURAL-LANGUAGE INDUSTRIAL QUERY
Ask Industrial Mesh
Natural language is translated into a bounded, inspectable semantic/trace plan. The query surface exposes no arbitrary SQL, writes, external network actions or unregistered dependency guesses.
Ask about dependencies, lineage, assets, measurements, pipelines, data products, dashboards or industrial sources.
Traceability · END-TO-END INDUSTRIAL TRACEABILITY
Source → semantic context → transformation → product → consumer
Traverse durable industrial dependencies in either direction. Runtime deliveries, evidence-ledger edges and registered external consumers remain provenance-labeled instead of being guessed.
Select an industrial object to inspect its complete dependency path.
Traceability · EXTERNAL CONSUMER REGISTRY
Register dashboards and applications as governed dependencies
Use this for Grafana dashboards, reports and applications whose dependency cannot be inferred from Industrial Mesh runtime state.
INDUSTRIAL DATA GOVERNANCE
Governance coverage, policy decisions & audit evidence
Composes authoritative provenance, custody, classification, residency, UNS contracts and movement decisions without creating a parallel governance ledger.
RISK SIGNALS
Governance attention
SUBJECT DOSSIER
Ownership, lineage & movement
Select a subject and build its governance dossier.
SUBJECT TRACE
Source-to-output lineage
Select a governed industrial resource to trace its source, transformations, evidence and outputs.
EVIDENCE LEDGER
Evidence objects
CAPTURE
Attach evidence
CHAIN OF CUSTODY
Select evidence
Select an evidence record to verify its content hash and custody chain.
EXPLICIT LINEAGE
Add governed relationship
DATA RESIDENCY & MOVEMENT POLICY ENGINE
Keep industrial data where policy says it belongs
Classify governed resources, assign home residency zones, evaluate every outbound movement and route exceptions through time-bounded approval.
RESIDENCY ZONES
Physical / legal processing locations
DATA CLASSIFICATION
Subject residency identity
MOVEMENT POLICIES
Allow · Deny · Approval Required
POLICY SIMULATOR
Pre-flight movement decision
Select a classified subject, movement type and destination, then evaluate.
APPROVAL QUEUE
Time-bounded exceptions
MOVEMENT LEDGER
Every evaluated boundary crossing
No captured HTTP traffic yet.
Select a request to inspect headers, bodies, timing, and replay.
ENTITLEMENTS
Network & Developer Limits
THIS MONTH
Network Traffic Usage
INDUSTRIAL OT CAPACITY
Edge & DataOps Quotas
INDUSTRIAL UTILIZATION
Active Hubs, Pipelines & Products
AVAILABLE
Plan tiers
BILLING
Subscription
🔒 Secure 256-bit payment via Razorpay. Subject to our Terms, AUP & 7-Day Refund Policy.
RETURNED MINUTE AGGREGATES
HTTP request volume
RETURNED MINUTE AGGREGATES
Bytes per minute
LIVE TELEMETRY
Endpoint health
SECURITY TRAIL
Operational audit & Authentication Events
SETTINGS · MODULES
Product Modules
Activate licensed modules for this organization and choose the facilities or environmental domains where each module is available.
LOADING
PRODUCT CATALOG
Available modules
Environmental Management is the parent module. Environmental Compliance, Regulatory Exchange, Supply Chain Traceability and Industrial Interoperability modules can be licensed and activated independently.
Module catalog has not loaded.
Tenant administrators can activate or suspend licensed modules. Product availability is managed separately by the platform operator.
ORGANIZATIONS
Registered Tenants
TOPOLOGY
Edge Relays & Clusters
AI ASSISTANT
Policy Copilot
Describe your security policy in plain English (e.g. "Allow only 198.51.100.24, rate-limit to 30 req/min, and enable security headers").
PROJECTS
Active Projects
ENVIRONMENTS
Project Environments
AGENT CARDS
Registered Agents
FEDERATION
Delegation Grants
REPOSITORIES
Active Git Bindings
GOVERNANCE
Staged Deployment Plans
CATALOG
Official Extensions & Starter Templates
AGENT MESH
Autonomous Tool & Capability Discovery
Query the registry to match agent requirements against official tools and starter templates, validate security policies, and review procurement rules.
INTEGRITY & PROVENANCE
Cryptographic Checksums & Manifest Hashes
SECURITY & COMPLIANCE
Governance, Safety & Takedowns
MESH PEERING
Multi-Cluster Catalog Synchronization
SYSTEM HEALTH
Live Infrastructure Authority Matrix
LEDGER
Autonomous Economics & Tuning
IDENTITY
User Profile
Display Name—
Email Address—
User ID
—Active Organization—
Account ID
—RoleOwner
Session Expires—
PREFERENCES
Console & CLI Settings
AI AGENT ENGINE & PROVISIONING
LLM Provider & Bring-Your-Own-Key (BYOK)
HIGH AVAILABILITY & LOAD BALANCING
Origin Endpoint Pools & Probes
TENANT-SCOPED L3 OVERLAY
Private Networks
Real WireGuard mesh inventory from the control plane. No browser-local synthetic routes.
SELECTED PRIVATE NETWORK
—
Loading live private-mesh state…
GATEWAY APPLIANCE IDENTITY
Gateway fleet enrollment and heartbeat
APPLICATION SECURITY
Web Application Firewall (WAF) & OWASP Top 10 Guard
Evidence-bound operational status. Loading current runtime evidence…
CURRENT ALERT EVIDENCE
Live Alerts & Triage Inputs
SIMULATION EVIDENCE
Observed Inputs & Persisted Twin Handoff
GOVERNANCE & ADMISSION
Recorded Resilience Leases & Release Decision
COST EVIDENCE
Measured Activity & Cost-Model Boundary
REAL-TIME TELEGRAM OPERATIONS BOT
Telegram NOC Alerting & Command Stream
Generate a server-issued pairing code when the Telegram operations service is configured. External bot delivery, alert routing and command handling are not inferred from this page.
BOT COMMANDS
Bot identity returned by server
/health— Instant cluster, tenant & tunnel status/incidents— List active P1–P4 operational alerts/ack <incident-id>— Acknowledge & silence alerts/tenant <id>— 360° view of tenant health & quota/bind <code>— Authenticate Telegram chat ID
ALERT DISPATCH MATRIX
Escalation Capability Matrix
| Severity | Trigger Condition | Potential Channels | Capability |
|---|---|---|---|
| P1 CRITICAL | Total Ingress Loss / Auth Failover | Telegram, Webhook, Pager when configured | Requires governed runtime configuration |
| P2 HIGH | SLO Breach / Rate Limit Anomaly | Telegram, Dashboard, Email when configured | Requires governed runtime configuration |
| P3 LOW | TLS Expiry (7d) / DNS Sync | Dashboard, Telegram when configured | Requires governed runtime configuration |
STATUS EVIDENCE
Current Runtime Status Boundary
OBSERVABILITY PIPELINE
Real-Time Telemetry Export Destinations
CLOUD NATIVE
Kubernetes source capabilities and deployment gates
FOUNDATION
1. Architecture & Dual-Branding Strategy
IndusMesh OS operates on a decoupled architecture where OT edge nodes stream data to the central control plane over the hardened TunnelMesh Core Wire Protocol.
🏭 IndusMesh OS
Product platform: Unified Namespace (UNS), Visual Pipeline Studio, semantic models, curated data product APIs, and cross-site edge federation.
⚡ TunnelMesh Core Engine
Transport engine: Zero-Trust multiplexed TCP/HTTP streams, mTLS encryption, WireGuard fallback, and reverse proxy agent mesh.
STEP 1
2. CLI & Edge Agent Installation
Install the dual-branded executable (creates both indusmesh and tunnel commands) directly from the VPS without requiring GitHub tokens.
curl -fsSL https://indusmesh.net/downloads/install.sh | shirm https://indusmesh.net/downloads/install.ps1 | iexINGRESS
3. Industrial Protocol Ingress Connectors
Connect edge PLCs, SCADA nodes, and IoT sensors using pluggable industrial drivers:
🔌 OPC-UA Client
Connects to opc.tcp:// endpoints with Basic256Sha256 security, address space node browsing, and live tag subscriptions.
📡 MQTT Sparkplug B
Supports spBv1.0 state management, NBIRTH, DBIRTH, NDATA, and rebirth control for edge brokers.
⚡ Modbus TCP / RTU
Polls Holding Registers (FC03), Input Registers (FC04), Coils (FC01), and Inputs (FC02) with IEEE 754 float decoding.
🏭 Siemens S7 (ISO-on-TCP)
Direct DB block read/write for S7-300, S7-400, S7-1200, and S7-1500 PLCs on port 102.
SEMANTICS
4. Governed ISA-95-aligned Unified Namespace (UNS)
Organize raw telemetry into a standardized ISA-95 enterprise semantic hierarchy:
Enterprise / Site / Area / Line / Cell / Asset / [Telemetry | State | Maintenance]
Example: AcmeCorp/Dallas_Plant/Packaging/Line_2/Cartoner_A/Vibration_RMS
DATA TRANSFORMATION
5. Visual Pipeline Studio & Real-Time ETL
Build event-driven data transformation graphs with live simulation, deadband filtering, unit conversions, and dead-letter queues (DLQ).
GOVERNANCE & API
6. Industrial Data Products & REST APIs
Package curated telemetry into consumable Data Products backed by API token authorization and SLA monitoring.
curl -H "Authorization: Bearer YOUR_API_TOKEN" https://indusmesh.net/api/v1/industrial/data-products/dp_boiler/latestSUPPORT
7. Frequently Asked Questions & Troubleshooting
Q: How do I resolve 401 Unauthorized during sign-in or API calls?
A: Ensure you click "Continue with Google" to refresh your session PKCE tokens, or verify that your API token is included in the Authorization: Bearer <TOKEN> header.
Q: Can edge agents communicate through strict OT firewalls?
A: Yes. Edge agents only establish outbound connections to port 4443 (TCP/TLS) or port 443 (HTTPS WebSockets fallback). No inbound OT ports are needed.
Q: How do I install the Progressive Web App (PWA) on desktop or mobile?
A: On Chrome/Edge, click the "Install App" icon in the address bar. On iOS Safari, tap Share ➔ "Add to Home Screen". The PWA runs offline with full cached navigation.
UNIFIED BUILDER
From semantic model to governed delivery
Build and bind exact models, validate data flows, submit reviewable changes and promote exact revisions without confusing configuration, admission, deployment or runtime truth.