ISO 22000 clause 7.1.3: make infrastructure support reliable food safety
ISO 22000 clause 7.1.3 requires resources for determining, establishing and maintaining the infrastructure necessary to meet FSMS requirements. Infrastructure can include facilities, utilities, equipment, transport and relevant information technology. The decision is whether those resources support the actual food safety operation, not whether the site owns an impressive equipment list.
What clause 7.1.3 requires in practice
Clause 7.1.3 asks the organisation to provide the resources for determining, establishing and maintaining the infrastructure it needs to meet the FSMS requirements. Three verbs mark the expectation: infrastructure is first worked out, then put in place and then kept in condition. A one-off purchase does not complete the requirement.
A note says infrastructure can include land, vessels, buildings and their utilities; equipment, including hardware and software; transport; and information and communication technology. The list is illustrative, so the relevant items depend on the operation.
The test is whether the infrastructure supports the arrangements the system relies on, such as cleaning, controlled storage, process control and information used in product decisions. The outputs are suitable facilities, equipment and systems, with provision for their upkeep. The clause sets no layout, brand or specification, because suitability comes from the product, the legal setting and the hazard-control decisions.
Connect infrastructure with its food safety purpose
Identify the processes and controls that depend on each significant facility or system. A utility may support cleaning or a control measure; transport may preserve required conditions; an information system may hold specifications or traceability relationships. Understanding the purpose helps define what needs to be established and maintained.
Consider interfaces rather than assets in isolation. An adequate storage facility can still be undermined by an unsuitable transfer arrangement. A sound production line can depend on maintenance access or utilities that were not considered in the project. Bring operational and technical personnel into the resource decision.
The clause does not prescribe a universal building layout or equipment brand. Specific suitability needs come from the operation, applicable requirements, prerequisite programmes and hazard-control decisions. Avoid turning an example from another site into an assumed technical requirement.
Provide for maintenance and change
Resources need to support continued suitability, not only purchase and installation. Establish who maintains relevant infrastructure, what information is needed and how a problem reaches the responsible decision-maker. A maintenance plan should relate to the equipment's role and the consequences of deterioration.
When infrastructure changes, consider the effect on FSMS information and controls. A different layout can alter material movement or cleaning access. A software change can affect data used for a release or traceability decision. Coordinate the work through planned change and the relevant technical reviews.
Maintenance activity itself may need appropriate controls and handback arrangements. Completion of a repair does not establish that the affected process is ready for routine operation. Define the necessary checks using competent personnel and the relevant requirements.
Why reliable infrastructure matters to the business
Equipment, premises, transport and software are the physical means by which food safety plans are carried out. Poor access for cleaning, unreliable utilities or an information system that loses lot relationships can undermine controls that look sound on paper. Repairs and replacements can also change the conditions on which earlier decisions were based. Clause 7.1.3 encourages the business to consider infrastructure as part of food safety, not only as a capital or maintenance matter. That usually saves money, since suitability is checked before commitment, downtime is reduced and product holds are avoided. For customers, dependable infrastructure is a visible sign that the business can keep its promises.
How to make infrastructure support reliable food safety
Look at each significant facility or system through the food safety work that depends on it. Avoid copying technical expectations from another site, because suitability depends on your product, your processes and the legal setting. Involve those who clean, maintain and operate the item, since they notice problems first.
- List the premises, utilities, equipment, transport and information systems that support PRPs, hazard controls or traceability.
- For each, note what food safety purpose it serves and who is responsible for its upkeep.
- Bring technical, production and maintenance staff into decisions on purchase, layout and change.
- Plan maintenance in proportion to the consequences of deterioration, and decide who learns of a problem and who decides what follows.
- Before a changed item enters routine use, check the effect on cleaning access, information and control arrangements.
- Define the checks needed after a repair or installation before affected operations resume.
- Review temporary arrangements regularly and decide whether they should end.
Illustrative food-manufacturing example
A manufacturer replaces equipment with a model offering higher throughput. Before routine use, the team examines the implications for cleaning access, maintenance, process information and control arrangements. It identifies the resources required to establish and maintain the new setup.
The review discovers that a previously accessible inspection point is now obstructed. The organisation resolves that issue before relying on the former verification arrangement. A signed purchase acceptance would not have answered the food safety question.
Illustrative food-logistics example
A distributor replaces its warehouse application. The system supports lot relationships and the location status used when affected product must be controlled. The organisation assesses the migration and relevant interfaces, provides resources for checks and confirms that users can obtain dependable information.
This example concerns infrastructure supporting a food-chain operation. It does not imply that a generic software company is itself a food producer or that installing software establishes traceability effectiveness.
Evidence and common mistakes
Useful evidence can include suitability decisions, maintenance arrangements, relevant checks and action taken after problems. Follow a significant infrastructure change from the initial need to operating use. Does the current FSMS information describe the actual arrangement?
Common weaknesses include funding purchase but not upkeep, leaving essential utilities outside responsibility assignments and accepting a contractor's completion note without the relevant operational check. Another is allowing temporary infrastructure to continue indefinitely without reviewing its suitability.
Connect this resource requirement with PRPs and monitoring and measuring controls where appropriate. Those requirements provide additional decisions that an asset register alone cannot satisfy.
Frequently asked questions
Does infrastructure include software?
It can, where the software supports the FSMS and its operation. Assess its relevant role and controls rather than treating every business application as equally significant.
Does new equipment automatically improve food safety?
No. Its suitability, operation, maintenance and effects on existing arrangements need evaluation. A newer model can introduce different dependencies.
Can outsourced maintenance meet the need?
It can contribute where suitable. Define requirements, responsibilities and relevant verification rather than assuming outsourcing removes oversight.
Review the infrastructure decision before commitment
Discuss a facility, equipment or system change with Sterling to identify its FSMS interfaces. Documentation, learning and agreed Effivity ISO & GRC automation software support can accompany implementation. Explore ISO 22000 Food Safety Awareness; see resource planning and the hub.