OGAS Design Principles

Origin. Viktor Glushkov's All-State Automated System for the Gathering and Processing of Information (OGAS), developed 1962-1970s at the Institute of Cybernetics, Kyiv. Never fully implemented due to political opposition.

Mechanism. A hierarchical network of computing centers linking the entire economy, enabling real-time information flow and decentralized decision-making within centrally-set parameters. The design recognized that central planning fails not from bad intentions but from information overload: the center cannot process the variety required for detailed control. OGAS distributed processing while maintaining coordination through standardized data formats and hierarchical aggregation.

Procedure. Design the information architecture before the decision architecture. Identify what decisions are made at each level and what information they require. Design data collection at the source (enterprises, warehouses) with automatic capture. Aggregate upward only what the next level needs for its decisions; do not send raw data to the center. Enable lateral information flow between units that must coordinate. The center sets parameters and constraints; lower levels optimize within them.

Applies to. Large-scale system design, enterprise architecture, federated data systems, any system requiring coordination without centralization.

Limitations. OGAS was blocked by ministries that correctly perceived it as a threat to their information monopolies. The technical design assumed honest data input, but enterprises had incentives to misreport. Any system that relies on local reporting for central decisions must address the incentive to distort. Also: the network effects meant partial implementation had little value; OGAS required critical mass that was never achieved.