Translate EquatorOps terminology across industries.

Foundational operational capability that powers shared workflows across industries. Engines are infrastructure primitives—not features—that adapt to any vertical.

API domain that exposes tenant-owned data and workflows. Each tenant API maps to one or more universal engines and defines the operational surface customers integrate with.

Canonical record created by tenant workflows—assets, inspections, work orders, ledger entries. All artifacts are tenant-owned and API-accessible.

The Verification Graph Engine computes the change impact of any proposed change—traversing BOMs, documents, work orders, compliance records, and procurement pipelines to produce severity scores, verification packs, and cost-of-change estimates.

Global Serialized Item Identifier. A 24-state lifecycle engine for serialized asset tracking with full lineage history, chain of custody, and provenance records.

License Plate Number. An identifier assigned to a handling unit (pallet, case, or tote) to track it through its lifecycle—analogous to a GS1 SSCC in broader supply chain labeling. Supports recursive nesting (pallets contain cases, cases contain units) with full location resolution at every level.

The complete set of artifacts impacted by a proposed change, computed by traversing the operational dependency graph. Each impacted node receives a severity score (0.0–1.0).

Generated bundle of validation plans, document packages, acknowledgement tasks, and operation checklists required to execute a change safely. Supports preview mode before committing.

A 0.0–1.0 score assigned to each impacted node during change impact computation. Factors include graph depth, edge weight, asset criticality, and effectivity status.

An auditable trace showing exactly why a given artifact is impacted by a change—every hop in the dependency graph is recorded and defensible.

A reliability pattern that writes domain events to the database in the same transaction as the business operation, then delivers them asynchronously. Guarantees at-least-once delivery without dual-write risk.

The guarantee that repeating an API request produces the same result without side effects. Critical for payment processing, stock movements, and any operation where duplication causes real-world harm.

A workflow checkpoint that blocks downstream operations (procurement release, payment, shipment) until inspection criteria are satisfied. Gates are configurable per tenant.

A governed process for modifying any operational asset—BOM revisions, document updates, supplier changes—with full audit trail, approval workflows, and optional VGE impact analysis.

A structured signal emitted when a business operation completes—inventory received, work order released, quality gate passed. Events drive webhooks, integrations, and downstream automation.

A lifecycle-managed unit of operational work with dependencies, material allocation, time entries, and approval gates. Supports linked chains for multi-step processes.

A versioned composition definition—what components make up an assembly, with alternates, quantities, and revision history. The Composition Engine manages BOM lifecycle.

Configure, Price, Quote. The Commercial Offer Engine that produces versioned quotes with scenario modeling, approval workflows, and margin guardrails.

Policy that governs how changes apply to existing work—GRANDFATHER_EXISTING, REPLAN_IF_NOT_STARTED, LOT_ONLY, SERIAL_RANGE. Effectivity-aware traversal ensures only actionable work is flagged.

A decision-routing system for non-standard events that require human judgment. Cross-change collisions, supplier disputes, and quality exceptions are routed here for resolution.

A configurable structure for tracking regulatory requirements—FDA 21 CFR Part 11, ISO 13485, AS9100, SOC2, HIPAA—with certification lifecycle and evidence collection.

Engine that transforms physical space into addressable digital assets. Locations form recursive hierarchies—campus → building → floor → zone → bin—with full inventory resolution at every level.

Immutable cradle-to-grave traceability for any asset—every custody change, status transition, and location movement is recorded in a tamper-evident chain.

A tenant-scoped, lease-based lock that prevents concurrent execution of the same critical operation. Locks self-heal on expiry to prevent deadlocks.

When two or more active changes have overlapping change-impact radii. High-severity collisions automatically create triage queue entries for human-in-the-loop resolution.

A user-defined dependency link between any two operational artifacts (e.g., Marketing Claim to Test Result) with rationale and evidence. Extends the analysis beyond automatically detected relationships.

Lifecycle management for high-value equipment—acquisition, depreciation, maintenance scheduling, utilization tracking, and ROI analysis.

Multi-stage invoicing with payment gates tied to operational milestones. Payments release only when quality, delivery, and compliance conditions are met.

Webhook delivery signed with HMAC-SHA256 for tamper detection. Supports key rotation, replay protection, and configurable retry policies.

A safe exploration mode for VGE analysis—see the full impact, verification pack, and cost estimate without persisting any artifacts. The default experience for change review workflows and sales demos.

A configurable rule that uses a boolean DSL (AND/OR/NOT predicates) to match change characteristics and automatically generate typed verification artifacts. Templates are versioned (DRAFT → PUBLISHED → ARCHIVED), validated by a test harness before activation, and include evaluation traces explaining exactly why each template matched.

VGE separates every cost line item into NRE (non-recurring engineering: re-tooling, docs, replanning) or recurring (per-unit COGS delta: material cost increase, added inspection step). The estimate output provides separate NRE and per-unit recurring totals with min/likely/max uncertainty bounds.

A comparison of two impact analysis snapshots showing nodes added/removed, edges added/removed, and severity changes. Used for baseline-vs-proposed comparison or to track how change impact evolves as a change is refined.

A verification plan item with a specific validation_type that tells downstream systems what kind of verification is required: MANUAL_CHECKLIST (manufacturing), DOCUMENT_REVIEW (pharma), AUTOMATED_TEST (SaaS), FIRST_ARTICLE_INSPECTION (aerospace), or DATA_ASSERTION (any industry).