as-planned

Meaning in manufacturing and operations

In manufacturing and industrial operations, **as-planned** refers to the baseline definition of how a product, process, or schedule is intended to be executed *before* any actual work occurs. It is the authoritative reference for what should happen, against which **as-built**, **as-executed**, or **as-run** records are later compared.

The as-planned view is typically established in engineering, planning, or ERP/MES systems and can include:

– Product structure and configuration (planned bill of materials, options, and variants)
– Routing and operations sequence (which steps, in what order, at which work centers)
– Planned resources (machines, tools, fixtures, skills, and standard labor time)
– Planned quality requirements (test steps, inspection points, and acceptance criteria)
– Planned schedule (promised start/finish dates, takt time, and capacity assumptions)

Use in real workflows and systems

In integrated ERP/MES and PLM environments, as-planned information is commonly used to:

– Generate work orders and operation lists based on planned routings and bills
– Set expected configuration for serialized units (for example, aerospace assemblies)
– Define standard work instructions, checklists, and inspection plans
– Provide targets for variance analysis (time, material usage, scrap, rework)
– Support impact analysis when engineering changes modify the planned configuration

Manufacturing execution, quality, and maintenance systems then record **what actually happened**, enabling comparisons such as:

– As-planned vs. as-built (final product configuration)
– As-planned vs. as-executed (operations performed, sequence, and timing)
– As-planned vs. as-maintained (configuration after service or retrofits)

Boundaries and exclusions

In this context, **as-planned**:

– **Includes**: planning data, reference models, and baselines stored in systems like PLM, ERP, APS, or MES prior to execution.
– **Excludes**: real-time production data, deviations, nonconformances, rework paths, and actual resource usage (these belong to as-built/as-executed/as-run views).

It describes **intent**, not outcome.

Common related terms and confusion

As-planned is often contrasted with several related terms:

– **As-designed**: Typically the engineering design definition (e.g., from CAD/PLM). As-planned may adapt the design for manufacturability, routing, and plant-specific constraints.
– **As-built / as-assembled**: The actual configuration and content of the delivered product or unit, including substitutions and deviations.
– **As-executed / as-run**: The detailed record of how work was actually performed (times, resources, exceptions, and quality events).

In some organizations, **as-planned** and **as-designed** are used interchangeably, but in regulated or complex manufacturing (such as aerospace or pharmaceuticals), they are typically managed as distinct views.

Site context: complex assemblies and MES visibility

For complex, serialized assemblies such as those in aerospace, **as-planned** data in MES and related systems defines:

– The planned operation sequence and work instructions for each unit or serial number
– The planned parts, kits, and configuration options to be installed
– Planned inspections and quality checkpoints across the route

MES uses this as-planned baseline to:

– Link work orders, operations, and quality data at the unit/serial-number level
– Highlight deviations from plan (skipped steps, rework, alternative parts)
– Support traceability by comparing planned versus actual configuration and process history