First conversation
You
Describe the labels, the systems that feed them and the deadline
Numaco
Free first engagement: a half-day review of your label print chain, ending in a written list of gaps

In a regulated plant, three parties share the work of putting a label system into use: you, as the regulated company; Numaco, as the integrator; and the vendor of the label software. Most project trouble starts where nobody wrote down which of the three owns a step. This page writes it down.
The split follows GAMP 5, Second Edition. Under GAMP 5 the regulated company always owns the validation, and suppliers contribute documents and testing. So the last column is never ours.
Describe the labels, the systems that feed them and the deadline
Free first engagement: a half-day review of your label print chain, ending in a written list of gaps
Give access to the label layouts, the printers and the data sources
Record every layout, data field, printer and interface in use today
Write and approve it
Comment on what the label software can and cannot do
Lead it and approve it
Contribute what we know of the system's failure modes, such as a wrong template or a lost print job
Review and approve
Write it: how the system will meet each requirement in the URS
Product documentation
Build the label templates, connect the data source, for example SAP output, and set up the printers
File it
Pass it on and explain it
Release notes, quality documents and any validation package for the product
Witness and sign
Support your team while it runs the tests on your site
Approve the protocols and the results
Support your team in drafting and executing the protocols
Test scripts, where the vendor supplies them
Run it in production, with your products and your people
Support on site or remotely
Write, approve and release
Raise and approve every change
Make the change, test it and document it under your change control
Product updates and their release notes
Validation is yours. We support your team through it, and we write the specification and the traceability matrix. We cannot approve documents, and we never release a system for GMP use.
Changes go through your change control. A label layout is a controlled document. We do not change a template on a validated system without a change request you have approved, and we document every change we make against that request.
The vendor's documents are inputs, not proof. A software vendor's validation package shortens the work. It does not replace testing the system as you configured it.
The functional and configuration specification from step 5 and the traceability matrix, signed by us, in English, German or Italian, as PDF and as editable files so your quality unit can bring them into its own templates. The full list is on page 1.4, IQ/OQ/PQ scope.
The first engagement is free: a half-day review of your current label print chain, ending in a written list of gaps.