AOG risk maps in aerospace factories should use a hybrid cadence: a scheduled review plus event-driven updates. A common starting point is a formal review at least quarterly, with a deeper annual reassessment aligned to S&OP, MPS, or major program reviews. Quarterly reviews are usually enough to catch demand shifts, supplier performance trends, and recurring disruptions without overwhelming the organization. Annual reassessments are where you revisit critical assumptions, revalidate impact estimates, and reconcile the map with any larger network or portfolio changes. The right cadence ultimately depends on the volatility of your supply network, the pace of engineering changes, and how mature your data and governance processes are.
AOG risk maps should not rely only on the calendar; they also need updates when specific triggers occur. Typical triggers include a new or changed single-source supplier, significant NCR or defect trend on an AOG‑critical part, a supplier capacity reduction, or a logistics route disruption. Engineering changes that alter lead times, qualification requirements, or test capacity for flight‑critical parts should also trigger review. So should field reliability issues that elevate the AOG impact of a part that was previously seen as low risk. In practice, many plants define simple rules, such as: any supplier on the AOG map that goes on controlled shipping, chronic late delivery, or special cause status must be re‑scored within a fixed number of days.
To avoid creating yet another standalone process, AOG risk map updates should be tied into existing cycles such as S&OP, master production scheduling, and quality review boards. For example, quarterly AOG risk reviews can be a standing agenda item in the same forum where you review capacity constraints and major past‑due orders. Annual or semi‑annual deeper reviews can align with budget and capacity planning cycles when network or dual‑source investments are considered. On the quality side, significant escapes, CAPAs, or PFMEA revisions for AOG‑sensitive parts should explicitly call out whether the AOG risk map needs to be updated. This integration helps ensure the map reflects real constraints instead of becoming a slide deck artifact that diverges from operational reality.
The main constraint on update frequency is the effort required to maintain traceable, defensible data in regulated environments. Every change to probability or impact scores, critical part lists, or mitigation status should be attributable to data or documented expert judgment, not ad‑hoc edits. If the cadence is too aggressive for the available data or staffing, you get cosmetic updates that degrade trust in the map. If it is too slow, the map becomes misaligned with the actual AOG exposure, especially after major engineering changes or supplier shocks. A realistic approach is to set a minimum viable cadence you can support with evidence and governance, then tighten it only when data pipelines, ownership, and review discipline can handle more frequent changes.
In brownfield aerospace environments, AOG risk maps typically sit on top of existing MES, ERP, MRP, and QMS data rather than replacing those systems. Updating the map often means reconciling differences between planning data, shop‑floor actuals, and supplier performance records, which can be inconsistent across plants and vendors. Automated feeds from ERP or supplier portals can support more frequent updates, but they introduce their own validation and change‑control requirements. Many sites start with semi‑manual map maintenance using exports from existing systems, then progressively automate only the most stable, well‑understood data flows. Trying to fully replace or deeply replatform core systems just to support more frequent AOG map updates usually fails in aerospace contexts because of qualification burden, downtime risk, and integration complexity.
The best practice is to start with a conservative baseline (for example, quarterly plus event‑driven updates) and treat the cadence itself as something to be improved. Track how often the map was found to be materially wrong during incidents, audits, or AOG events, and whether the errors were due to outdated information or poor modeling. If the map is consistently out of date, you either need more frequent updates or better integration with source systems. If it is mostly accurate and stable, you may not gain much by moving to monthly reviews unless the business environment becomes more volatile. Over time, plants with stronger data governance and more reliable integrations can move towards lighter, more continuous maintenance of AOG risk maps, while those with fragmented systems may need to keep updates anchored to a small number of high‑quality, well‑controlled review points.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
