Non conformance management

Lascom PLM nonconformance process tracks all events and makes the proper link between the event and the associated product items. To speed response time, Lascom PLM nonconformance process optimizes the processing of the defaults and ensures the fastest possible turnaround time. The process benefits from the capacity of Lascom PLM to manage the process itself as well as its ability to extract information from individual projects or products to build a complex knowledge database.

Projects and products are becoming complex and reaction time to technical problems or non conformance issues is become critical:

• An aircraft on the ground represents lost money, customers waiting and a global disturbance for the airline. Getting the plane back in the air as fast as possible is a top priority.
• Manufacturing faults and quality control lapses must be tracked and properly followed up. It can lead up to product recall.

Online processes, launched by support or production technicians as soon as they receive notification of a technical request, are replacing paper-based requests. Lascom PLM automatically builds up each case folder with all the necessary sections that need to be answered.

Impact management :

At every stage of the process, the user can look at the impact of the default on the design chain :

• Impact of the possible changes on the product portfolio
• Impact on the associated documents
• Impact on the projects
• Associated documents or data
  

At every stage of the process, user can add specific various files or data such as:

• Notes or data that describe the event
• List of the actions that are being taken
• Drawings
• List of parts

Commission management

Commissions or meetings are part of the process. These meetings will give a status to the problems as well as the corrective actions. These comments and actions are part of the process audit trail.

Modification folder

Often a modification folder (or several folders) or ECO will be associated to the fault. Lascom PLM WizardFlow can easily link the technical events process to the ECO process, making it easy to track the modifications back to the initial request.