scope

In industrial and regulated manufacturing environments, scope is the formally defined boundary of what a system, project, or activity covers. It specifies what is included, what is excluded, and the conditions under which the defined elements apply.

Scope in management systems and standards

In management system standards (such as many ISO standards), scope commonly refers to the boundary of the management system. This typically includes:

• Sites, locations, and organizational units covered
• Activities, processes, and value streams included
• Products, services, or product families in scope
• Interfaces with other functions or organizations
• Defined exclusions and their justification

In regulated manufacturing, the declared scope is expected to match operational reality, be supported by evidence (such as process maps, system inventories, and organizational charts), and be controlled under change management when boundaries change.

Scope in projects and systems

In projects, IT/OT programs, or system implementations, scope describes which objectives, deliverables, and work are included. For example:

• An MES deployment may define scope in terms of plants, lines, products, and process stages it will cover.
• An ERP integration project may specify which data objects, transactions, and interfaces are in scope.
• A validation effort may define the scope of functions, configurations, and risks that must be assessed.

Clear scope definition helps distinguish between core project work and items that are explicitly out of scope or deferred.

Operational use of scope

Operationally, scope often appears in:

• Policies and procedures: describing which processes, roles, and facilities the document applies to.
• Quality management documents: defining which products, lots, or processes are covered by a specification or control plan.
• System records and configurations: indicating which assets, data sources, or workflows are monitored, controlled, or governed.
• Audits and assessments: setting the boundary of what the audit will examine and which requirements will be applied.

Common confusion

Scope vs. requirements: Scope describes the boundary (what is covered); requirements describe what that boundary must achieve or satisfy. A system can be in scope for a standard while specific requirements within that standard apply differently to parts of the scope.

Scope vs. objective: Scope defines where and to what the work or system applies; objectives define what results are intended within that scope.

Link to ISO-related usage

In ISO-style management system standards, scope commonly refers to the formally documented boundary of the management system. It is typically described in a scope statement, covering applicable locations, activities, products or services, and justified exclusions. In manufacturing environments, this scope statement is expected to align with real operations and be maintained under document control and change management.