GovKM
Integrated Operational State

Eleven Thousand Schedules Are Not a Master Schedule.

GAO found that FAA had 11,389 individual BNATCS project schedules that were not integrated, while an AI scheduling tool remained under testing without established business rules. The case shows why AI optimization depends on a governed, authoritative portfolio state rather than a collection of disconnected plans.
Published:
September 17, 2026
|
7
min read
|
Organizational Continuity
|
Series:
Case Study
Organizational continuity framework representing thousands of separate FAA project schedules that must be integrated into one authoritative modernization plan before optimization.
Expand image

Thousands of accurate project schedules do not automatically create one authoritative program schedule.

GAO reported on September 14, 2026 that the Federal Aviation Administration had not integrated the schedules for 11,389 projects supporting the 13 programs in phase 1 of its Brand New Air Traffic Control System modernization effort. As a result, different projects could schedule work at the same installation sites without systematically identifying conflicts, coordinating resources, or minimizing disruptions to air traffic operations.

FAA said its systems integrator was developing an advanced scheduling tool using AI to coordinate the portfolio. GAO noted that as of May 2026 the tool was still undergoing testing, the business rules for using it had not been established, and it was unclear when effective improvements would result.

Fragmented plans are not an integrated state

Each project can have a valid schedule while the institution still lacks a reliable portfolio state. A master schedule exists only when dependencies, locations, shared resources, sequencing, third-party obligations, and operational constraints are connected strongly enough to support coordinated decisions.

GovKM maps the gap as Source / individual project schedules → Evidence / planned activities → Authority / program and project owners → Context / integrated portfolio state → Decision / sequencing → Action / deployment.

AI cannot substitute for missing continuity

The AI scheduling capability is the most important architectural detail. AI may be able to identify collisions and optimize sequences, but optimization is downstream of continuity.

Before an AI tool can optimize the program, the institution must establish which schedules are authoritative, how they relate to locations and resources, which dependencies are binding, and which business rules control tradeoffs.

Otherwise the AI is being asked to infer institutional state from fragments rather than operate on an authoritative representation of that state.

Integration is more than aggregation

Putting 11,389 schedules into one tool would not, by itself, solve the problem. The continuity requirement is relational: project A depends on site B, resource C, authority D, and timing constraint E. Those relationships must be explicit and governable.

GovKM interprets the case as evidence that AI optimization cannot repair organizational fragmentation unless the institution first establishes the continuity object being optimized.

Source

U.S. Government Accountability Office, “Air Traffic Control Systems: Ambitious New Modernization Effort Needs to Improve Cost and Schedule Planning,” GAO-26-107992, September 14, 2026. https://www.gao.gov/products/gao-26-107992

RELATED FRAMEWORK DOMAINS

Explore the Connected Framework

Continue through the framework domains connected to this article.

FRAMEWORK DOMAIN

Information Continuity

Keep information trustworthy, accessible, and connected regardless of the technology used to create or manage it.

FRAMEWORK DOMAIN

Governance Architecture

Design governance structures that connect authority, policy, evidence, and organizational intelligence.

FRAMEWORK DOMAIN

Corporate Operational Knowledge

Transform institutional knowledge into a connected operational asset supporting mission execution.

RELATED CORE PRINCIPLES

Principles Applied in This Article

Explore the core principles connected to this article.

CORE PRINCIPLE

Continuity Through Change

Allow knowledge systems and operating models to evolve without severing their continuity with prior understanding.

CORE PRINCIPLE

Contextual Understanding

Preserve the relationships and context that allow organizational knowledge to retain meaning across time and change.

CORE PRINCIPLE

Relationship Governance

Connect and govern information, authority, evidence, context, decisions, actions, records, and institutional memory as one continuity architecture.

RELATED TOPOLOGY ELEMENTS

Follow the Continuity Relationships

Explore the continuity topology elements connected to this article.

CONTINUITY TOPOLOGY

Source

The originating person, system, record, event, or environment from which information enters institutional use.

CONTINUITY TOPOLOGY

Evidence

The verifiable material that supports, qualifies, challenges, or constrains an institutional claim.

CONTINUITY TOPOLOGY

Context

The circumstances, relationships, constraints, and meaning required to interpret information correctly for a specific institutional purpose.

CONTINUITY TOPOLOGY

Decision

The governed selection, judgment, or determination made from available evidence, authority, and context.

CONTINUITY TOPOLOGY

Action

The execution, intervention, communication, or operational change performed in response to a decision or authorized objective.

CONTINUITY TOPOLOGY

Record

The durable institutional evidence of information, decisions, actions, transactions, and their governing relationships.

RELATED KNOWLEDGE

Continue Exploring

Explore related research, framework domains, and continuity concepts.
CONTINUE WITH THE FRAMEWORK

Explore the continuity relationships that support trustworthy organizational intelligence.

Continue through the GovKM Framework to examine the doctrine, knowledge, and implementation guidance behind Organizational Continuity.
Explore the Continuity FrameworkView All Articles