OCAD - Ops Control Content Guidelines.pdf

This is a NASA presentation providing guidelines for Operations Control and Analysis Database System (OCADS) content and Flight Operations Directorate (FOD) disciplines. The presentation outlines requirements and expectations for writing operations controls, which are described as the least-desirable form of hazard control.

The document details specific requirements for OCAD submissions, including a 30-day template review period, expectations for clearly identifying hazards being controlled, ensuring all pertinent information is present (op nom, part numbers, locations, torque values), and avoiding procedural steps. Key guidelines include making OCADs standalone documents, using impersonal statements, spelling out acronyms on first use, and distinguishing between design controls and ops controls. The Flight Ops Safety Office (FOSO) will pre-screen OCADs before distribution to Ops Disciplines, with incomplete or inadequate submissions being rejected. The presentation emphasizes that last-minute OCADs should be avoided, with any control needed within 30 days to be handled via Chit instead.