Complex asset organizations rarely suffer from a complete lack of systems. They have Enterprise Resource Planning (ERP) platforms, product lifecycle management (PLM) systems, maintenance tools, engineering databases, and reporting platforms.
Yet the work itself often continues through spreadsheets, emails, shared folders, paper instructions, and local databases. Enterprise systems contain plans and records, while frontline teams rely on separate tools to assemble, inspect, maintain, and support the asset.
The missing connection is an execution layer: the part of enterprise architecture that turns enterprise data into controlled operational work and returns validated evidence of what happened.
For organizations managing assets across decades, that connection is fundamental to effective asset lifecycle management for OEMs.
ERP and PLM systems perform essential roles. They manage materials, configurations, engineering definitions, work orders, inventory, costs, and other authoritative records.
However, knowing that work is required is different from controlling how it is performed.
A maintenance order may exist in the ERP, while the maintainer still needs to find the relevant instructions, confirm the asset configuration, request approval, document measurements, and record any deviation. An assembly plan may be available centrally, while fitters coordinate the actual sequence through printed documents and informal handovers.
In our experience with complex asset programs, this is where fragmentation usually appears. The organization has enterprise systems, but task ownership, reminders, evidence, approvals, and operational context remain distributed across separate tools.
The result is a gap between the system of record and the point of work. Operational status must then be reconstructed from manual updates after the work has taken place, contributing to the wider problems described in Why Lifecycle Data Is Broken in Most Organizations.
An execution layer is the part of enterprise architecture that converts plans and data from systems such as ERP and PLM into controlled tasks for the people performing the work.
It typically manages:
The concept has an established architectural foundation. The International Society of Automation’s ISA-95 standard for enterprise-control system integration defines how enterprise business systems (such as ERP) interact with manufacturing operations. It introduces a layered model in which Level 4 systems manage business planning and logistics, while Level 3 systems manage manufacturing operations, including production scheduling, quality, maintenance, and performance tracking.
Within this framework, ISA-95 describes the functions needed to execute work: dispatching tasks, managing workflows, tracking personnel and equipment, collecting production and quality data, and ensuring that operations follow defined procedures. These Level 3 activities effectively define what an execution layer is: the set of capabilities that translate enterprise plans into controlled, traceable operational work and capture the results of that work in a structured way.
ISA-95 is primarily associated with manufacturing, but the underlying problem continues after production. Complex assets require the same kind of controlled execution during assembly, inspection, deployment, maintenance, modification, and sustainment.
A simplified enterprise architecture for complex assets can be viewed as three connected layers.
ERP, PLM, EAM, inventory, engineering, and configuration systems manage authoritative data, plans, resources, and product definitions.
The execution layer turns that information into work. It delivers the relevant context to each user, controls task progression, captures results, and manages approvals or exceptions.
This is where fitters, maintainers, inspectors, and operators interact with the asset, component, tool, or support equipment.
Information should move in a continuous loop:
Enterprise records → structured execution → validated operational data → enterprise and lifecycle systems
Each layer has a distinct responsibility. The execution layer does not need to absorb the functions of ERP or PLM. Its purpose is to govern operational work while allowing authoritative data to remain in the appropriate source systems.
APIs, middleware, and data platforms can move information between systems. They cannot determine how a maintainer should respond to an unexpected defect or what evidence an inspector must capture before approving a task.
A technically integrated architecture may still leave the frontline workflow fragmented.
For example, an integration can send a work order from an ERP to another system. The execution layer determines who receives it, which instructions apply, what asset configuration is relevant, which values must be recorded, and what happens when the result falls outside an accepted range.
This difference is easy to overlook. Enterprise integration focuses on the movement of data. Operational execution focuses on how that data is used to complete and govern work.
The architecture must support both. Otherwise, organizations risk connecting their systems while leaving the process between them dependent on spreadsheets, emails, and individual knowledge.
A digital thread connects information across the asset lifecycle. Engineering data describes what the asset should be. Enterprise systems record what was planned, ordered, or scheduled. Execution data records what was actually built, inspected, changed, maintained, or approved.
NIST describes the digital thread as information running through design, manufacturing, and product-support processes. Its work focuses on the methods, protocols, and standards needed to exchange that information between lifecycle phases.
Operational execution therefore provides an essential part of the thread. Without it, the organization may know the original design and current ERP record while lacking reliable evidence of the events that changed the physical asset.
This is the practical connection between an execution layer and the Digital Thread.
Execution data also keeps digital representations aligned with physical reality. The difference between these concepts is explored further in Digital Twin vs Digital Thread.
Organizations often try to improve lifecycle data through reporting projects, data lakes, or analytics platforms. These initiatives remain limited when the underlying operational records are incomplete or inconsistent.
Reliable lifecycle data must be captured while work is performed.
During execution, the organization can record:
Capturing this information within the workflow makes it easier to validate, structure, and connect to the correct asset. It also reduces the need to interpret disconnected notes later.
An execution layer should first fit the operational environment. Fitters, maintainers, and inspectors need clear tasks and relevant context without navigating the full complexity of the underlying enterprise systems.
It should also provide governance. Responsibilities, permissions, validations, approvals, and audit history must be built into the workflow rather than added through manual reporting.
Finally, it should support interoperability. Execution results should be available to ERP, PLM, maintenance, analytics, and customer-support systems without creating another isolated repository.
A useful evaluation question is therefore not simply whether the software integrates with the ERP. Organizations should ask whether it can reliably convert enterprise information into operational work and return structured evidence from that work.
An enterprise architecture is incomplete when it connects databases but leaves people to coordinate critical work manually.
Systems of record manage authoritative data and resources. Integration moves information between systems. The execution layer governs how operational work is performed and documented.
Together, these capabilities create a reliable connection between enterprise intent, asset reality, and lifecycle learning.
For complex asset organizations, the final test of enterprise architecture is not how many systems are connected. It is whether the architecture helps people perform work correctly and creates reliable data while they do it.