In the fast-paced world of aerospace and defense manufacturing, precision, quality, and adherence to stringent standards are paramount. As the industry evolves, so do the standards that govern it. A recent development in this regard is the transition from AS9102 Rev. B to Rev. C of the AS9102 Standard for First Article Inspection (FAI) Reports. Utilizing 1factory's cloud platform hosted on AWS GOV Cloud, the transition becomes as effortless as logging into your account. In this blog post, we'll explore what is changing and how 1factory can help you navigate this transition effortlessly.
Understanding the Transition
Aerospace Standard AS9102, which governs the procedures for conducting and documenting first article inspections (FAI), has been undergoing a revision (revision C) led by the International Aerospace Quality Group (IAQG) since 2019. The objective of this revision is to align the standard more closely with the AS9100 production process verification section. This update aims to enhance planning, evaluation, and re-accomplishment activities, while also improving the documentation forms used for FAI Reports (FAIR).
The improved requirements and compliance with the FAI standard will lead to several advantages. These include reductions in escapes, risk, and overall costs, as well as improved product safety. By identifying process issues early on and providing standardized, objective evidence in FAIR reports, organizations can better mitigate risks and validate corrective actions. Revision C of the FAI standard aims to instill confidence in the production of conforming products by demonstrating that manufacturers and processors understand the requirements and can ensure initial product or process conformity, even after changes are implemented.
1factory's Role in the Transition
The introduction of AS9102 Rev. C brings forth stringent requirements for quality control and traceability, which can initially seem challenging and resource-intensive for manufacturers. However, these requirements are crucial in elevating industry standards and ensuring that every product manufactured adheres to the highest levels of excellence. Fortunately, 1factory offers a comprehensive solution to help manufacturers navigate and implement these requirements effectively, thereby reducing the burden associated with compliance.
1factory provides manufacturers with the necessary framework and support to streamline their processes and meet AS9102 Rev. C requirements with ease. By leveraging 1factory's expertise in quality control and traceability, manufacturers can enhance their product quality, reduce risks, and increase customer satisfaction. This not only benefits manufacturers by improving their operations and reducing costs but also ensures that customers receive products that meet the highest standards of quality and safety.
Form 1:
- Field 4: FAI Report number was renamed to FAIR Identifier on all three forms.
- Field 12: P.O. number was renamed to Purchase Order Number.
- Field 13: Detail Part & Assembly FAI was renamed to simply state Detail & Part.
- Field 14: Reason for Partial FAI was renamed Reason for Full / Partial FAI making it a required field for FAI acceptance or rejection.
- Field 17: Part Serial Number was renamed to Part Type .Where as before many customers required all BOM items, even COTS parts to be identified in the COM, the standard has now made it a clearly states “All BOM parts (e.g., detail parts, sub-assemblies, COTS) that are part of the assembly, identified in field 1, shall be listed in this [Fields 15-18] section.”
- Field 18: FAI Report number was renamed FAIR Identifier on all three forms. According to the AS9102 Standard, in cases where no FAIR (First Article Inspection Report) identifier is available, organizations should input their identifier for the FAI or approved configuration. It is anticipated that customers will typically request Certificate of Conformance numbers or similar information to be entered in this field, rather than using "N/A."
- Field 19: FAI Complete / FAI Not Complete was renamed to Does FAIR Contain a Documented Nonconformance(s)?The signature and date (Field 20) requirements have been moved into fields 20 & 21 in Rev C.
- Field 20: Signature, previously Field 19, was renamed to FAIR Reviewed By.
- Field 22: Reviewed by, previously Field 21, was renamed to FAIR Approved/Reviewed By. The Dates were previously in Fields 20 and 22 but have now moved to Fields 21 and 23. Both Fields 20 & 22 are meant to be completed by the organization that is submitting the FAIR, However, AS9102 now states that the individual identified in Field 22 should not be the same individual identified in Field 20.
- Field 24: Customer Approval & Date were previously Field 23 & 24.It should also noted that Customer Approval was previously Optional (O) and is not Conditionally Required (CR).
Form 2:
- Field 14 & 15: Signature and Date have been removed. The visual changes to Form 2 may not be highly significant; nevertheless, it's important to note that the standard now mandates that these requirements should also be flowed down to suppliers conducting special processes.
Form 3:
- Field 12 & 13: Signature and Date have been removed. This change results in a renumbering of Field 14 to Field 12.
By making these necessary adjustments and updates, 1factory ensures that you can seamlessly transition to AS9102 Rev. C without any disruptions in your FAI process.
Conclusion
Staying compliant with industry standards is crucial for aerospace and defense manufacturers. With the transition to AS9102 Rev. C, 1factory is your trusted partner in automating and streamlining the FAI process. These updates make it easier than ever to adapt to the latest industry requirements while maintaining the highest standards of quality and precision in your manufacturing processes. Embrace the change, and let 1factory guide you through this transition seamlessly.