1 / 38

System Engineering Documentation Presentation for INCOSE Orlando Chapter Meeting on 17 Sep 09

System Engineering Documentation Presentation for INCOSE Orlando Chapter Meeting on 17 Sep 09. Dave Krigelman, President Krigelman and Associates, Inc 813 Cebu Place Melbourne, FL 32940 Voice/Fax: (321)242-7598 Mobile: (321)544-1862 E-mail: krigelman@prodigy.net.

judith
Download Presentation

System Engineering Documentation Presentation for INCOSE Orlando Chapter Meeting on 17 Sep 09

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Engineering DocumentationPresentation for INCOSE Orlando Chapter Meeting on 17 Sep 09 Dave Krigelman, President Krigelman and Associates, Inc 813 Cebu Place Melbourne, FL 32940 Voice/Fax: (321)242-7598 Mobile: (321)544-1862 E-mail: krigelman@prodigy.net

  2. PROGRAM ORGANIZATION CHART LSI TECHNICAL AND MANAGEMENT INTERFACE TECHNICAL AND MANAGEMENT ADVISORS PROGRAM MANAGER • OPERATIONS: • SUBCONTRACTS • PURCHASING • MANUFACTURING • QA/QC & TEST • LOGISTICS SUPPORT • PM OFFICE: • PROGRAM CONTROL • CONFIG & DATA MGMT • FINANCE & CONTRACTS HW ENG LEAD SW DEVEL LEAD INTEG VERIF & TEST LEAD INTEG LOGISTICS LEAD SUBJECT MATTER/DOMAIN EXPERTS CHIEF ENGINEER/ SYSTEM ENGINEER AAR IPT LEAD VMRE IPT LEAD

  3. PROGRAM MANAGEMENT PROCESS FLOW POLICIES, INSTRUCTIONS, AND OPERATING PROCEDURES PROGRAM MANAGEMENT PLAN PROGRAM DIRECTIVES PROGRAM TEAM ORGANIZATION CONTRACT TECHNICAL AND MANGEMENT REQUIREMENTS PROGRAM TEAM INTEGRATION, MONITORING, AND CONTROL WORKING LEVEL INTEGRATION DAILY STAND-UP MEETINGS WEEKLY PROGRAM MEETINGS MONTHLY MANAGEMENT REVIEWS STATUS/PROBLEM CORRECTIVE ACTION IDENTIFICATION AND RESOLUTION ACTION ITEM CLOSEOUT ACTION ITEM LIST ACTION ITEM FOLLOW-UP

  4. SYSTEM ENGINEERING PROCESS FLOW Process Input System Analysis and Control (Balance) Requirements Analysis System Level Tradeoffs Requirements Loop Equipment Level Tradeoffs Functional Analysis/ Allocation Modeling Design Loop Simulation Testing Synthesis Verification Process Output The Analysis Loop and the Synthesis (Design) Loop are Key Elements of the System Engineering Process. Reference: MIL-HDBK-502, Acquisition Logistics

  5. Introduction • The objective of this presentation is to review the purpose and scope of SE documents prepared on a program. • SE documents that will be discussed include the following: • System Documentation Tree • System Engineering Management Plan (SEMP) • Integrated Master Plan (IMP) • Integrated Master Schedule (IMS) • System Performance Specification (PS) • System Design Description (SDD) • System Interface Specification (IS) • Interface Design Description (IDD) • Requirements Traceability Matrix (RTM) • Requirements Verification Matrix (RVM) • Detail Specifications (DS) • Software Documents • System Integration Documents • System Verification Documents • System Test Documents • System Support Documents

  6. System Documentation Tree • The System Documentation Tree describes: • the program-required System Engineering (SE)–oriented documents and • their relationships in a top-down structured format. • The tree is prepared by the System Engineer during the proposal phase based on the Statement of Work (SOW) and Contract Data Requirements List (CDRL) in order to identify required documentation tasks for subsequent costing and scheduling. • It should be approved by the Program Manager (PM) and maintained current for the life of the program.

  7. SYSTEM DOCUMENTATION TREE SYSTEM REQUIREMENTS DOCUMENT CONTRACT PERFORMANCE WORK STATEMENT CONTRACT DATA REQUIREMENTS LIST REQUIREMENTS TRACEABILTY MATRIX SYSTEM ENGINEERING MANAGEMENT PLAN SYSTEM PERFORMANCE SPECIFICATION SYSTEM DESIGN DESCRIPTION SOFTWARE DOCUMENTS SYSTEM INTEGRATION DOCUMENTS REQUIREMENTS VERIFICATION MATRIX SYSTEM INTERFACE SPECIFICATION INTERFACE DESIGN DESCRIPTION INTEGRATED MASTER PLAN SYSTEM VERIFICATION DOCUMENTS DETAIL (HW) SPECIFICATIONS INTEGRATED MASTER SCHEDULE SYSTEM TEST DOCUMENTS SYSTEM SUPPORT DOCUMENTS

  8. System Engineering Management Plan (SEMP) • The System Engineering Management Plan (SEMP) describes: • the program SE task and schedule requirements and • how they will be managed and implemented. • The plan is prepared by the System Engineer based on the SOW and CDRL during the proposal to describe the SE process and how the SE requirements will be planned, organized, integrated, monitored, controlled, and measured. • It should be approved by the PM and maintained current for the life of the program.

  9. SYSTEM ENGINEERING MANAGEMENT PLAN IAW DI-MGMT-81024 • PART I – SYSTEM ENGINEERING • FUNCTIONAL ALLOCATION • TRADE STUDIES • DESIGN OPTIMIZATION AND EFFECTIVE ANALYSIS • SYNTHESIS • TECHNICAL INTERFACE COMPATIBILITY • LOGISTIC SUPPORT ANALYSIS • PRODUCIBILITY ANALYSIS • TRAINING PROGRAMS FOR USERS • REQUIREMENTS ALLOCATION • GENERATION OF SPECIFICATIONS • OTHER SYSTEM ENGINEERING TASKS • PART II – TECHNICAL PROGRAM PLANNING AND CONTROL • PROGRAM RISK ANALYSIS • ENGINEERING PROGRAM INTEGRATION • CONTRACT WORK BREAKDOWN STRUCTURE AND SPECIFICATION TREE • ASSIGNMENT OF RESPONSIBILITY AND AUTHORITY • PROGRAM REVIEWS • DESIGN REVIEWS • INTERFACE CONTROL • DOCUMENTATION CONTROL • ENGINEERING TESTING • TRADEOFF STUDIES • TECHNICAL PERFORMANCE MEASUREMENT • OTHER TECHNICAL PROGRAM TASKS • PART III – ENGINEERING INTEGRATION

  10. Integrated Master Plan (IMP) • The Integrated Master Plan (IMP) describes the program major milestones, the entrance criteria for each milestone, and the exit criteria for each milestone. • Entrance criteria are those requirements that must be met prior to initiation of the milestone. • Exit criteria are those requirements that must be met upon completion of the milestone. • The IMP is prepared by the Program Manager during the proposal based on inputs from the SE and others in accordance with the CDRL.

  11. INTEGRATED MASTER PLAN

  12. Integrated Master Schedule (IMS) • The Integrated Master Schedule (IMS) describes: • the responsible organization and/or individual, • start dates, durations, stop dates, and • network interdependencies for each task listed on the Work Breakdown Structure (WBS). • The IMS is prepared by the Program Manager during the proposal based on inputs from the SE and others in accordance with the CDRL.

  13. INTEGRATED MASTER SCHEDULE IAW DI-MGMT-81650

  14. System Performance Specification (PS) • The System Performance Specification describes: • the system functional performance, • design and construction constraints, • external and internal interfaces, • environmental design criteria, • physical requirements, and • their allocation to lower levels of design. • The specification is prepared by the System Engineer prior to the System Requirements Review (SRR) and the System Design Review (SDR) in accordance with the CDRL based on the System Requirements Document (SRD), the System Requirements Analysis (SRA), and trade-off study reports.

  15. SYSTEM PERFORMANCE SPECIFICATION IAW DI-SDMP-81465A/MIL-STD-961E • SCOPE • APPLICABLE DOCUMENTS • REQUIREMENTS • 3.1 MISSIONS • 3.2 THREAT • 3.3 REQUIRED STATES AND MODES • 3.4 ENTITY CAPABILITY REQUIREMENTS • 3.5 RELIABILITY • 3.6 MAINTAINABILITY • 3.7 DEPLOYABILITY • 3.8 AVAILABILITY • 3.9 ENVIRONMENTAL CONDITIONS • 3.10 TRANSPORTABILITY • 3.11 MATERIALS AND PROCESSES • 3.12 ELECTROMAGNETIC RADIATION • 3.13 NAMEPLATES OR PRODUCT MARKINGS • 3.14 PRODUCIBILITY • 3.15 INTERCHANGEABILITY • 3.16 SAFETY • 3.17 HUMAN FACTORS ENGINEERING 3.18 SECURITY AND PRIVACY 3.19 COMPUTER RESOURCE REQUIREMENTS 3.20 LOGISTICS 3.21 INTERFACE REQUIREMENTS 3.22 COMPUTER HARDWARE REQUIREMENTS 3.23 COMPUTER COMMUNICATIONS REQUIREMENTS 3.24 COMPUTER SOFTWARE REQUIREMENTS 3.25 CSCI INTERNAL INTERFACES 3.26 CSCI INTERNAL DATA REQUIREMENTS 3.27 DESIGN AND CONSTRUCTION 3.28 SOFTWARE DESIGN 3.29 WORKMANSHIP 3.30 PRODUCT CHARACTERISTICS 3.31 CHEMICAL, ELECTRICAL AND MECHANICAL PROPERTIES 3.32 STABILITY 4. VERIFICATION 5. PACKAGING 6. NOTES

  16. System Design Description (SDD) • The System Design Description (SDD) describes: • the system hardware and software configuration and • the degree to which the requirements described in the System Performance Specification have been met. • The document is prepared by the System Engineer prior to the Preliminary Design Review (PDR) and the Critical Design Review (CDR) in accordance with the CDRL based on inputs from the hardware engineers and software developers.

  17. SYSTEM DESIGN DESCRIPTION IAW DI-IPSC-81432A 1. SCOPE 1.1 IDENTIFICATION 1.2 SYSTEM OVERVIEW 1.3 DOCUMENT OVERVIEW 2. REFERENCED DOCUMENTS 3. SYSTEM-WIDE DESIGN DECISIONS 4. SYSTEM ARCHITECTURAL DESIGN 4.1 SYSTEM COMPONENTS 4.2 CONCEPT OF EXECUTION 4.3 INTERFACE DESIGN 4.3.1 INTERFACE IDENTIFICATION AND DIAGRAMS 4.3.2 (PROJECT-UNIQUE IDENTIFIER OF INTERFACE) 5. REQUIREMENTS TRACEABILITY 6. NOTES A. APPENDICES

  18. System Interface Specification (IS) • The System Interface Specification describes: • the system external interface allocation and internal interfaces at lower levels of design. • Interfaces may be hardware-to-hardware, hardware-to-software, software-to-hardware, and software-to-software. • The specification is prepared by the System Engineer prior to the SRR and the SDR in accordance with the CDRL based on the System Requirements Document (SRD), the System Requirements Analysis (SRA), and trade-off studies.

  19. SYSTEM INTERFACE SPECIFICATION IAW DI-SESS-81632 • 1. INTRODUCTION • 1.1 OVERVIEW • 1.2 RELATED DOCUMENTS AND DATA • 1.3 INTERFACE SCOPE • 1.3.1 SYSTEM SUMMARY • 1.3.2 INTERFACE BOUNDARIES • 1.3.3 LAYERED INTERFACE DEFINITION (LID) • 1.3.4 CONFIGURATION ITEM (CI) RELATIONSHIPS • 1.4 SECURITY • 2. REFERENCED DOCUMENTS • 2.1 GOVERNMENT DOCUMENTS • 2.2 NON-GOVERNMENT DOCUMENTS • 3. INTERFACE REQUIREMENTS AND DESIGN • 3.1 INFO INTERFACES (CHARACTERISTICS REQUIRED TO TRANSFER INFORMATION ELECTRONICALLY) • 3.2 NON-INFO INTERFACES (CHARACTERISTICS NECESSARY TO SUPPORT THE INFORMATION TRANSFER) • 4. QUALITY ASSURANCE PROVISIONS • 4.1 SUMMARY • 4.2 VERIFICATION CROSS-REFERENCE MATRIX (VCRM) • 5. NOTES • 5.1 DEFINITIONS AND ACRONYMS/ABBREVIATIONS • 5.1.1 DEFINITIONS • 5.1.2 ACRONYMS/ABBREVIATIONS • 5.2 TUTORIALS AND EXPLANATIONS • A. APPENDICES • B. APPENDIX-REQUIREMENTS TRACEABILITY MATRIX (RTM)

  20. Interface Design Description (IDD) • The Interface Design Description (IDD) describes: • the system hardware and software interfaces and • the degree to which the requirements described in the System Interface Specification have been met. • The document is prepared by the System Engineer prior to the PDR and the CDR in accordance with the CDRL based on inputs from the hardware engineers and software developers.

  21. INTERFACE DESIGN DESCRIPTION IAW DI-IPSC-81436A • 1. SCOPE • 1.1 IDENTIFICATION • 1.2 SYSTEM OVERVIEW • 1.3 DOCUMENT OVERVIEW • 2. REFERENCED DOCUMENTS • 3. INTERFACE DESIGN • 3.1 INTERFACE IDENTIFICATION AND DIAGRAMS • 3.2 (PROJECT-UNIQUE IDENTIFIER OF INTERFACE) • 3.3 ETC. • 3.4 ETC. • 3.5 ETC. • 4. REQUIREMENTS TRACEABILITY • 5. NOTES • A. APPENDICES

  22. Requirements Traceability Matrix (RTM) • The Requirements Traceability Matrix (RTM) describes: • the allocation of system requirements to lower levels within the system, including hardware and software. • Normally, it is prepared as a stand-alone document or as part of the System Performance Specification. • The RTM should be prepared bi-directional, which shows “from-to” traceability as well as “to-from” traceability. • The matrix is prepared by the System Engineer in accordance with the CDRL prior to the SRR and the SDR based on the System Requirements Document (SRD), the System Requirements Analysis (SRA), and trade-off study reports.

  23. REQUIREMENTS TRACEABILITY MATRIX

  24. Requirements Verification Matrix (RVM) • The Requirements Verification Matrix describes: • how the requirements within Section 3 of a specification are verified by the means described in Section 4. • Normally, it is prepared as part of the specification to which it applies. • The verification may include the methods of analysis, demonstration, inspection, and test. • The matrix is prepared by the System Engineer or Responsible Design Engineer in accordance with the CDRL prior to SRR and the SDR based on information in the system and lower-tier specifications.

  25. REQUIREMENTS VERIFICATION MATRIX

  26. Detail Specifications (DS) • Item Detail Specifications describe: • the requirements that have been allocated from a System Performance Specification. • These may include functional performance, design and construction constraints, external and internal interfaces, environmental design criteria, and physical requirements. • The specification is prepared by the Responsible Design Engineer prior to the PDR and the CDR based on the System Performance Specification, the System Requirements Analysis (SRA), and trade-off studies.

  27. DETAIL SPECIFICATION IAW DI-SDMP-81464A/MIL-STD-961E 1. SCOPE 2. APPLICABLE DOCUMENTS 3. REQUIREMENTS 3.1 MISSIONS 3.2 THREAT 3.3 REQUIRED STATES AND MODES 3.4 ENTITY CAPABILITY REQUIREMENTS 3.5 RELIABILITY 3.6 MAINTAINABILITY 3.7 DEPLOYABILITY 3.8 AVAILABILITY 3.9 ENVIRONMENTAL CONDITIONS 3.10 TRANSPORTABILITY 3.11 MATERIALS AND PROCESSES 3.12 ELECTROMAGNETIC RADIATION 3.13 NAMEPLATES OR PRODUCT MARKINGS 3.14 PRODUCIBILITY 3.15 INTERCHANGEABILITY 3.16 SAFETY 3.17 HUMAN FACTORS ENGINEERING 3.18 SECURITY AND PRIVACY 3.19 COMPUTER RESOURCE REQUIREMENTS 3.20 LOGISTICS 3.21 INTERFACE REQUIREMENTS 3.22 COMPUTER HARDWARE REQUIREMENTS 3.23 COMPUTER COMMUNICATIONS REQUIREMENTS 3.24 COMPUTER SOFTWARE REQUIREMENTS 3.25 CSCI INTERNAL INTERFACES 3.26 CSCI INTERNAL DATA REQUIREMENTS 3.27 DESIGN AND CONSTRUCTION 3.28 SOFTWARE DESIGN 3.29 WORKMANSHIP 3.30 PRODUCT CHARACTERISTICS 3.31 CHEMICAL, ELECTRICAL AND MECHANICAL PROPERTIES 3.32 STABILITY 4. VERIFICATION 5. PACKAGING 6. NOTES SELECT, AS APPLICABLE

  28. Software Documents • Software Documents include plans, specifications, and description documents described as follows: • The Software Development Plan (SDP) describes the requirements for software development and how they will be implemented. • The Software Requirements Specification (SRS) describes the software technical performance requirements derived from the System Performance Specification. • The Interface Requirements Specification (IRS) describes the software technical interface requirements derived from the System Performance Specification. • The Software Design Description (SDD) describes the degree to which the SRS requirements have been met. • The Interface Design Description (IDD) describes the degree to which the IRS requirements have been met. • The documents are prepared by the organization and/or lead individual that is responsible for software development in accordance with the CDRL.

  29. SOFTWARE DEVELOPMENT PLAN IAW DI-IPSC-81427A SOFTWARE REQUIREMENTS SPECIFICATION IAW DI-IPSC-81433A INTERFACE REQUIREMENTS SPECIFICATION IAW DI-IPSC-81434A SOFTWARE DESIGN DESCRIPTION IAW DI-IPSC-81435A INTERFACE DESIGN DESCRIPTION IAW DI-IPSC-81436A SYSTEM PERFORMANCE SPECIFICATION/ SYSTEM INTERFACE SPECIFICATION CONTRACT PERFORMANCE WORK STATEMENT CONTRACT DATA REQUIREMENTS LIST REQUIREMENTS TRACEABILTY MATRIX SOFTWARE DEVELOPMENT PLAN SOFTWARE REQUIREMENTS SPECIFICATION SOFTWARE DESIGN DESCRIPTION SOFTWARE INTEGRATION DOCUMENTS REQUIREMENTS VERIFICATION MATRIX INTERFACE REQUIREMENTS SPECIFICATION INTERFACE DESIGN DESCRIPTION INTEGRATED MASTER PLAN SOFTWARE VERIFICATION DOCUMENTS INTEGRATED MASTER SCHEDULE DETAIL (SW) SPECIFICATIONS SOFTWARE TEST DOCUMENTS SOFTWARE SUPPORT DOCUMENTS

  30. System Integration Documents • System Integration Documents include plans, procedures, and reports described as follows: • The System Integration Plan describes the requirements for integrating the system during development. These may include the following levels of integration: hardware-to-hardware, hardware-to-software, software-to-hardware, and software-to-software. • The System Integration Procedures describe how the requirements of the plan will be implemented. • The System Integration Report describes the results of the integration that has been performed. • The documents are prepared by the organization and/or lead individual that is responsible for integration in accordance with the CDRL.

  31. SYSTEM INTEGRATION PLAN SYSTEM INTEGRATION PROCEDURES SYSTEM INTEGRATION REPORT SYSTEM INTEGRATION PLAN 1. SCOPE 2. APPLICABLE DOCUMENTS 3. REQUIREMENTS 3.1 FLOW DIAGRAM 3.2 SCHEDULE 4. MANAGEMENT 4.1 PLANNING 4.2 ORGANIZATION 4.3 MONITOR AND CONTROL 4.4 REPORTING 5. INTEGRATION PLANS 5.1 HW TO HW PLANS 5.2 HW TO SW PLANS 5.3 SW TO HW PLANS 5.4 SW TO SW PLANS SYSTEM INTEGRATION PROCEDURES 1. INTEGRATION PROCEDURES 1.1 HW TO HW PROCEDURES 1.2 HW TO SW PROCEDURES 1.3 SW TO HW PROCEDURES 1.4 SW TO SW PROCEDURES SYSTEM INTEGRATION REPORT 1. SCOPE 2. APPLICABLE DOCUMENTS 3. REQUIREMENTS 4. MANAGEMENT 5. INTEGRATION REPORTS 5.1 HW TO HW REPORTS 5.2 HW TO SW REPORTS 5.3 SW TO HW REPORTS 5.4 SW TO SW REPORTS

  32. System Verification Documents • System Verification Documents include plans, procedures, and reports described as follows: • The System Verification Plan describes the requirements for verifying the system have been met. These may include verification by analysis, demonstration, examination, and test at various stages of the program. • The System Verification Procedures describe how the requirements of the plan will be implemented. • The System Verification Report describes the results of the verification that has been performed. • The documents are prepared by the organization and/or lead individual that is responsible for verification in accordance with the CDRL.

  33. SYSTEM VERIFICATION PLAN SYSTEM VERIFICATION PROCEDURES SYSTEM VERIFICATION REPORT SYSTEM VERIFICATION PLAN 1. SCOPE 2. APPLICABLE DOCUMENTS 3. REQUIREMENTS 3.1 FLOW DIAGRAM 3.2 SCHEDULE 4. MANAGEMENT 4.1 PLANNING 4.2 ORGANIZATION 4.3 MONITOR AND CONTROL 4.4 REPORTING 5. VERIFICATION PLANS 5.1 ANALYSIS PLANS 5.2 DEMONSTRATION PLANS 5.3 EXAMINATION PLANS 5.4 TEST PLANS SYSTEM VERIFICATION PROCEDURES 1. VERIFICATION PROCEDURES 1.1 ANALYSIS PROCEDURES 1.2 DEMONSTRATION PROCEDURES 1.3 EXAMINATION PROCEDURES 1.4 TEST PROCEDURES SYSTEM VERIFICATION REPORT 1. SCOPE 2. APPLICABLE DOCUMENTS 3. REQUIREMENTS 4. MANAGEMENT 5. VERIFICATION REPORTS 5.1 ANALYSIS REPORTS 5.2 DEMONSTRATION REPORTS 5.3 EXAMINATION REPORTS 5.4 TEST REPORTS

  34. System Test Documents • System Test Documents include plans, procedures, and reports described as follows: • The System Test Plan describes the requirements for testing the system. These may include development , qualification, and acceptance tests at various stages of the program. • The System Test Procedures describe how the requirements of the plan will be implemented. • The System Test Report describes the results of the testing that has been performed. • The documents are prepared by the organization and/or lead individual that is responsible for testing in accordance with the CDRL.

  35. SYSTEM TEST PLAN AND PROCEDURES IAW DI-SESS-81704 SYSTEM TEST REPORT IAW MIL-HDBK-831 • SYSTEM TEST PLAN AND PROCEDURES • 1. TEST OBJECTIVES • 2. TEST ITEM CONFIGURATION AND SUCCESS CRITERIA • 3. MISSION PROFILES • 4. TEST SCHEDULES • 5. INSTRUMENTATION REQUIREMENTS AND CALIBRATION INSTRUCTIONS • 6. DATA PROCESSING AND REPORTING PROCEDURES • 7. INTERFACE IDENTIFICATIONS • 8. SAFETY • 9. FLOW DIAGRAM • 10. TEST SUPPORT REQUIREMENTS • 10.1 TEST LOGISTICS • 10.2 PERSONNEL PLANNING INFORMATION • 10.3 PERSONNEL SUPPORT REQUIREMENTS • 10.4 TEST INFORMATION SHEETS (TIS) • 10.4.1 PLANNING INFORMATION • 10.4.2 PROCEDURAL INFORMATION • 10.4.3 TIS SUMMARY • SYSTEM TEST REPORT • 1. SUMMARY • 2. REASON FOR THE TEST • 3. DESCRIPTION OF TEST SAMPLES • 4. DISPOSITION OF TEST SAMPLES • 5. NARRATIVE ABSTRACT, CONCLUSIONS AND RECOMMENDATIONS • 6. REFERENCES • 7. FACTUAL DATA • 7.1 DESCRIPTION OF TEST • 7.2 APPARATUS • 7.3 TEST PROCEDURE • 7.4 RESULTS OF TEST, SUMMATIONS AND ANALYSIS • 7.5 TEST DATA • A. APPENDICES

  36. System Support Documents • System Support Documents include: • Configuration and Data Management (C&DM), Quality Assurance (QA), and Integrated Logistic Support (ILS) plans, procedures, and reports, which describe the requirements in the SOW and how they will be implemented. • The documents are prepared and maintained by the organizations and/or lead individuals that are responsible for C&DM, QA, and ILS in accordance with the CDRL.

  37. SYSTEM SUPPORT PLANS SYSTEM SUPPORT PROCEDURES SYSTEM SUPPORT REPORTS IAW THE STATEMENT OF WORK AND THE CDRL/DIDs • SYSTEM SUPPORT • PLANS • CONFIGURATION MANAGEMENT PLAN • DATA MANAGEMENT PLAN • QUALITY ASSURANCE PLAN • INTEGRATED LOGISTIC SUPPORT PLAN • SYSTEM SUPPORT REPORTS • CONFIGURATION MANAGEMENT REPORTS • DATA MANAGEMENT REPORTS • QUALITY ASSURANCE REPORTS • INTEGRATED LOGISTIC SUPPORT REPORTS • SYSTEM SUPPORT PROCEDURES • CONFIGURATION MANAGEMENT PROCEDURES • DATA MANAGEMENT PROCEDURES • QUALITY ASSURANCE PROCEDURES • INTEGRATED LOGISTIC SUPPORT PROCEDURES

  38. Questions?

More Related