Glossary · Requirements and interfaces
Subsystem requirement
German: Subsystemanforderung
In systems engineering, a subsystem requirement is a requirement allocated to a subsystem, derived from system requirements, that the subsystem must meet so the overall system can meet its own requirements.
- Systems engineering
In one sentence
A subsystem requirement is derived from system requirements and allocated to one subsystem, such as a conveyor, robot cell or control unit.
Example
From the line requirement '1,200 bottles per hour', the capper subsystem gets the requirement 'cap one bottle every 2.5 s or faster'.
How it applies
- Engineering: Requirements are decomposed from system to Subsystem to component; each level must trace to the level above.
- Supply chain: Subsystem requirements often become the specification for a supplier; clear Interface requirements prevent integration surprises.
- Documentation: When subsystems come with supplier manuals, the documentation team should check that their limits match the subsystem requirements and the overall system documentation.
- Verification: Subsystem requirements are usually verified at the supplier (factory acceptance test); results should be traceable to the system requirements they contribute to.
Subsystem requirement vs. system requirement
A System requirement applies to the system as a whole; a subsystem requirement applies to one part. Emergent properties such as overall throughput or safety cannot be verified at subsystem level alone.