2. Capability Need 2.1. Business Need(s) 2.2. Business Need Capability Gap 2.3. CURRENT SITUATION: 3. Operations and Support Desсrіption 3.1. Missions (Primary/Secondary) 3.2. Users and Other Stakeholders 3.3. Policies, Assumptions and Constraints 3.3.1. Policy 3.3.2. Assumption 3.3.3. Constraint 3.4. Operational Desсrіption 3.4.1. Operating Concept (OpCon) 3.4.2. Employment Modes 3.4.3. Scheduling and Operations Planning 3.4.4. Operating Environment 3.4.5. Geographic Area(s) 3.4.6. Environmental Conditions 3.4.7. Interoperability with Other Elements 3.5. Product Support Desсrіption 3.6. Potential Impacts 3.7. Scenarios 3.8. Operations Scenarios 3.8.1. Functional Capabilities Needed 3.8.2. Functional Capabilities Delivered by Alternatives 3.9. Support Scenarios 3.9.1. Support Name 3.9.2. Functional Capabilities Needed 4. Functional Capabilities 4.1. Operations 4.2. Support 4.3. Functional Capabilities Matrix 4.3.1. Operations Matrix 4.3.2. Support Matrix A. Additional Information A.1. Analysis Reports A.2. Glossary of Terms A.3. Acronyms and Abbreviations A.4. References So the Concept of Operations (CONOPS) would need to go over requirements and dependencies to ensure the cloud software can maintain a intranet connection without needing to connect to the internet for DNS, NTP. etc.
