Non-routine card

Under AS9100, risk management in design is proactive, model- and requirement-driven, and tightly coupled to configuration control and design change. In MRO, it is more condition-driven, field-data-based, and focused on continuing airworthiness, maintenance errors, and repair deviations. Both must be documented, traceable, and integrated with the QMS, but the triggers, data sources, and control levers differ substantially, especially in brownfield environments with legacy systems.

Digital systems can materially improve control of life-limited parts in MRO, but only if part master data, usage rules, maintenance records, and system integrations are reliable. They help track remaining life, enforce workflow checks, preserve traceability, and reduce manual errors. They do not remove the need for validated data, disciplined change control, or human review of exceptions.

For aerospace maintenance content, access control should be role-based, need-to-know, and tightly integrated with identity management, export control, and configuration management. Expect multiple layers: RBAC/ABAC, segregation of duties, workflow-based approvals, read-only vs authoring separation, strong authentication, and detailed audit trails across MES, MRO, PLM, and document systems. Exact controls depend on your mix of ITAR/export-controlled data, system integrations, and process maturity.

Common integration pitfalls in aerospace MRO include weak configuration control between ERP, MRO, and engineering systems; broken traceability across tail/serial, part, and task history; over-customized legacy tools; underestimated data cleansing and mapping; ITAR/export control gaps; and rollout plans that ignore hangar realities and validation burdens. These risks are magnified in brownfield, multi-vendor stacks.