THE BUSINESS PROBLEM Most operational losses do not begin when the loss becomes visible. They begin earlier. A supplier starts delivering a little later. Inventory starts disappearing slightly faster than expected. Quality variance rises across several production runs. A freight route begins accumulating small delays. Customer complaints increase from occasional to recurrent. At first, none of these conditions necessarily looks critical. The data exists. The problem is that the organization has not yet converted the change into a signal important enough to alter what it does. That is where Operational Intelligence Asymmetry begins. Two companies can receive the same information and still react at very different moments. One recognizes deterioration while inexpensive options remain available. The other recognizes the same deterioration only after the remaining options have become expensive. That difference can determine whether the response is: a supplier conversation, a production adjustment, a routine rerouting, or a normal inventory correction, instead of: emergency air freight, overtime, expedited sourcing, lost sales, discounting, penalties, or customer loss. The signal may have been visible in both companies. Its operational value was not the same. THE WARNING CAME AFTER THE SIGNAL A warning is not necessarily the beginning of a problem. Often, it is the moment when an existing condition finally becomes important enough for the system to demand action. That creates a crucial distinction: SIGNAL EXISTENCE ≠ SIGNAL QUALIFICATION ≠ ESCALATION ≠ ACTIONABILITY A signal can exist without being recognized as consequential. It can be recognized without being escalated. It can be escalated without reaching the right response authority. And it can finally become actionable after much of its operational value has already disappeared. This is why KYOTEN does not define Operational Intelligence as simply having more information or faster dashboards. The asymmetry exists in how reliably consequential signals move through the organization while useful options still remain.

THE SIGNAL A previous KYOTEN analysis established that deployment and normalized operation are not the same event. The question now is different. Where does that separation become visible from outside? The U.S. Department of Veterans Affairs operates the largest integrated healthcare system in the United States. It serves approximately nine million veterans across 150 medical centers. In 2018, it committed to replacing its legacy electronic health record system with a commercial platform from Oracle Health. The contract was signed. The budget was allocated. Initial deployments began in 2020. By June 2026, the U.S. Government Accountability Office documented the following condition: Oracle Health facilities operate their scheduling and referral management across a multi-system environment that includes Oracle applications, additional scheduling systems, and some of the same tools used by facilities still running the legacy VistA platform. The system is live. It performs core functions. But ordinary scheduling work at deployed facilities has not consolidated into a single operational platform. This is the signal. SIGNAL CONFIRMED — CONDITIONED CONFIRMED: Post-go-live operational fragmentation is documented by the highest U.S. government audit authority. CONDITIONED: The root cause is mixed. GAO identifies technical issues, patient-safety concerns, usability challenges, configuration problems, and organizational change-management shortcomings. This Radar does not isolate a single cause. It identifies the observable condition. WHAT GAO ACTUALLY DOCUMENTS The evidence base rests primarily on GAO-26-109213, published June 2026, titled Veterans Health Care: Scheduling Systems and Related Challenges. Additional context comes from GAO-26-108812 and verified public reporting from Federal News Network, Nextgov, Becker's Hospital Review, and official VA communications. The factual timeline: May 2018. VA awarded a contract to replace its VistA electronic health record with a commercial system from Cerner, now Oracle Health. The original contract value was reported at sixteen billion dollars. The projected completion was 2028.