Factory Model and Nexus
The Factory Model describes native manufacturing objects and their relationships, events and available actions. Nexus presents an explorable map of business objects and the integrations, mappings, Apps, Automations and Recipes that use them. It reads the existing records and configuration; it is not another database you must keep synchronized.
Open Nexus from product navigation or the corresponding Operations Studio explorer domain. Everyday order execution remains in the operational Apps.
Explore configuration
- Open Nexus in the intended site and environment.
- Choose an object or configuration card, or search for the item you need.
- Expand its neighborhood and inspect the directional relationship labels.
- Use category filters to focus on Apps, integrations, workflows or other configuration.
- Open the selected item's configuration when you need its existing editor.
Apps, Automations and Recipes can offer View in Nexus to return to their place in the map. The graph derives saved references. An absent relationship can mean no saved reference or unavailable source access; it does not prove that two business processes have no real-world connection.
Configuration cards can show disabled or incomplete states. The configuration map does not establish live connection health or successful operational execution. A bounded result can be marked incomplete/truncated; narrow the exploration rather than assuming every object is displayed.
Explore an actual record
Record exploration starts with an object type and scoped search/selection. Choose a record to inspect its readable values, source and related records. On desktop, use the adjacent inspector; on narrow screens, switch between list and details and return to the previous selection.
Supported record types include customer orders/positions, production orders, operations, execution splits, work centers, materials, Material Objects, Material Holders and Material Locations. Follow a returned relationship to its authorized related record. The separate Factory Model record browser can offer an operation-confirmation shortcut that preserves the selected operation; preview, confirmation and submission remain explicit steps. Nexus itself does not execute that action.
A related record is subject to its own access check. A readable parent does not automatically grant access to its children or configuration. Unavailable candidates and missing values need investigation; they should not be read as a zero value or completed process.
Activity, documents and Trace
The focused record has its own Activity, Documents and Trace. Selecting a neighbor for inspection does not transfer the focus record's history to that neighbor; choose the explicit exploration action to load the neighbor's own context.
Trace follows recorded cause references between events and authorized Automation runs. It is bounded to three hops and 60 events, with up to 20 linked runs. Shared timestamps or configured App/workflow relationships are not proof that one event caused another. Missing or inaccessible evidence remains a gap, and Automation completion alone does not prove external-system acknowledgement.
Use the owning source's document/activity links to inspect retained evidence. Current relationships do not reconstruct every historical connection. A Trace failure can leave the accessible record details available; report its record and context to support.
Understand sources and identity
Connected object definitions can describe typed fields, explicit status/unit mappings, stable external identity, related references and observation freshness. The connected record stays owned by its source system. Projection into the shared model does not automatically create or overwrite a native production order.
An explicit native-equivalence mapping can associate an external identity with an existing authorized native record. This association is separate from deciding which system is authoritative for data or execution. Integration source/authority settings belong in the connection's reviewed configuration and require management permission.
Do not repair a missing native record by guessing an external identifier. Inspect the connection, published read contract, declared mappings and source observation. Unknown statuses, incompatible units, missing required values and stale/unavailable source observations can prevent a projection from being usable.
Act through the responsible workflow
Use the offered operational action or open the owning App/editor. A Nexus read, a relationship link and an action preview do not perform production confirmation or an external write. Review the proposed target/data and any approval request before execution, then inspect the actual result.
Custom Tables currently have no direct Table/record relationship view in Nexus. Their collection and processing workflow stays in the App's authorized Custom Table view. See Custom Tables, Integrations and Konnie approvals.