*Not covered by the SRMGSA. Milestone Description  AMS Phase  First-site preparation completed  First-site delivery  First-site training material delivery  Government acceptance  Site-Acceptance Testing completed  First-Site Initial Operational Capability date  Independent Operational Assessment (IOA) completed (for  designated programs)  Any new safety hazards from IOA analyzed accordingly  Safety input to PIR Plan provided  Software Accomplishment Summary prepared and submitted for  government approval  System Safety Assessment Report (including the SRVT) prepared  and approved  PSP updated for In-Service Management (as necessary)  In-Service Decision / Initial Operating Capability  First-Site Operational Readiness date  In-Service Management  Full operational capability  First-site commissioning  Site Operational Readiness date 25 percent complete  PIR conducted  Any new safety hazards analyzed accordingly  Site Operational Readiness date 50 percent complete  Site Operational Readiness date 75 percent complete  Last-Site Operational Readiness date  Last-site commissioning  **Indicates the milestone may also be completed during either the Initial or Final Investment  Analysis.  ***There may be multiple AJI audits conducted during Solution Implementation.  ****There may be multiple iterations of the Software Configuration Index (SCI) submitted for  approval as the system design matures. The SCI should be updated as necessary with each  version of the product and before every formal run of the software test suite.  The PO must demonstrate that software-intensive 3  systems were developed at an appropriate  level of rigor. The PO must establish a development assurance program in accordance with  RTCA DO-278A and document it in the PSP. 4 In addition, RTCA DO-330,  Software Tool  3. A software-intensive system is any system where software influences—to a large extent—the design, construction, deployment, and evolution of the system as a whole. 4. This is one acceptable means of demonstrating this level of rigor. Subject to approval by the Program Management Organization, a developer’s internal procedures may also suffice. 9_SRMGSA_202003  Originally published March 2020  Uncontrolled copy when downloaded  3 9.4  Software-Intensive Systems