Safety & Quality Compliance in the Cloud

Myth 3: You do not own your data in cloud-based applications. You can and should own your data, and this should be in your vendor contract. If you decide to leave a vendor, you will have the right to take your data with you.

Harmonizing FSQA in the Cloud

A comprehensive cloud-based FSQA suite will typically include upstream, internal, and downstream functionality. This might include modules for Supplier Compliance, Food Safety and Quality Management, and Regulatory/GFSI Compliance.

Cloud-based solutions operate on mobile devices and via secure login portals, allowing you to automate and streamline FSQA at all points along your value chain—from anywhere, at any time. They collect and analyze FSQA data at the point of origin: in the field, in the plant, on the road, or at the receiving dock. Information can come in from suppliers, equipment, and labs—and go out to distributors and customers. Workflow engines ensure all tasks—for every plan, across all facilities—are completed. In the cloud, FSQA data is analyzed against specifications in real-time because there’s no paper. Alert systems, “food safety smoke alarms in the cloud,” if you will, push non-conformance alerts in real-time, facilitating timely corrective and preventive actions (CAPAs).

Regardless of how many facilities, suppliers or customers you have, all FSQA program components and records live in your own central data repository that can be accessed from any computer or mobile device with a web browser. This is where harmonization of FSQA comes in.

All prerequisite programs, good manufacturing practices, standard operating procedures (SOPs), and the like, along with associated forms, live in the central repository. This means that regardless of where an FSQA team member is located, updated forms and specifications are always used.

Quality and operations directors, for example, can access dashboards on tablets anywhere to view and compare status of FSQA across the entire operation.

And there’s no more “data rich and information poor.” All FSQA data and records are centralized, actionable, and accessible for trending, reporting, continuous improvement, and audit readiness.

Impact on Daily FSQA Operations

There are literally thousands of examples that can demonstrate the impact of cloud-based, mobile technologies on FSQA operations. The following two focus on upstream and production scenarios.

Scenario 1: Going to supplier fields to inspect produce prior to harvesting for packaging at the plant.

Traditional Manual System:

• Inspector goes to field to do visual inspection; records a direct observation non-conformance, such as signs of animal intrusion, on paper forms.
• Goes back to office; faxes forms to FSQA manager or enters into spreadsheets and sends via email along with notations of observed non-conformances.
• When manager receives, he/she sends back a CAPA; if unable to reach manager, or if manager isn’t logged into email, it could take hours for this step to happen, and as we know in the food industry, time equals money.
• Inspector returns to field, has CAPA executed, records again on paper, and files forms upon return to office (hoping they can be easily found for audit).

Cloud-Based Mobile Empowered System:

• Inspector goes to fields and records all observations on mobile device form.
• If a non-conformance against a spec is detected during the real-time analysis, an auto-alert is sent to the FSQA manager, who receives a push notification on his or her mobile device, regardless of where he are she is.
• A CAPA is generated in real-time and sent back immediately to the inspector.
• When the CAPA is complete, it’s recorded on the mobile form, including before/after digital pictures, and automatically becomes part of the permanent record—accessed on-demand for audits and continuous improvement.

Scenario 2: Plant floor SOP for metal detector calibration prior to production line startup to package bags of cookies.