Most often, catastrophic equipment failures are not the result of a single individual or factor. Rather, it is the result of a systemic failure to implement proper procedures, to ensure appropriate training is conducted, and to maintain equipment consistently and effectively.
Created as a result of the Deepwater Horizon incident, this is precisely what the API Spec Q1, 2 standards aim to remedy.
According to the API Spec Q1,2 guidelines, “the organization shall maintain a documented procedure for the establishment of a PMITP [Preventive Maintenance, Inspection, and Test Program]. The procedure shall address record keeping requirements, inspection, maintenance, redress, repair, make-up, testing, and acceptance criteria for service-related product.”
Specifically, this PMITP must include, at a minimum:
1. Actions which address preventive maintenance;
2. Reports that document usage history, repairs or redress, modifications, remanufacturing, inspection, and test activities that allow direct verification for reuse of product;
3. List of critical spare parts requirements by the customer and/or technical requirements including those recommended by the original equipment manufacturer;
4. Controls that ensure equipment integrity to original performance requirements and design acceptance criteria are maintained
In an organization with dozens, if not hundreds of different products lines, this seems like a daunting task. Many of our adopters had previously managed with only Word documents and Excel spreadsheets. Combine this with additional requirements for training, non-conformities, document control, management of change, and a host of other QMS components, and it is easy to see how overwhelming compliance can be.
However, imagine integrating all of these components, including preventive maintenance planning, into one, seamless application. Moreover, imagine an application that can put all this information in your hands at the touch of a button, whenever you need, wherever you need it.