ACES NST Spiral 2-3 Software Development SOW_8 June 11

Arms Control Enterprise System (ACES) New START Treaty (NST)

Spiral 2 and 3

Software Development

Statement of Work (SOW)

8 June 2011

Arms Control Enterprise System (ACES) Software Development

Indefinite Delivery / Indefinite Quantity (IDIQ) Program

Statement of Work (SOW)

1.0 Introduction

DoD Directive 2060.1 dated 9 Jan 01, states, “It is DoD policy that all DoD activities shall be fully compliant with arms control agreements of the U.S. Government.” To comply with this directive, the former Defense Nuclear Agency (DNA) was tasked by the Office of the Secretary of Defense (OSD) to develop an information processing system to support arms control treaties and agreements; the Compliance Monitoring and Tracking System (CMTS) was the Defense Nuclear Agency’s (DNA) response to satisfy this requirement.

The Arms Control Enterprise System (ACES) is the web-based U.S. National automated tool designed to support U. S. Government compliance with international arms control treaties and agreements and supporting United States Government (USG) policies and practices. The ACES tool was developed and fielded by DTRA RD with DTRA retaining Operations & Maintenance (O&M) responsibility for the fielded system. The automated system includes functionality supporting data reporting requirements and formatted notifications for treaty limited equipment (TLE) and treaty accountable items (TAI). The system includes data handling capabilities, hardware and software, and reporting procedures/methodology for compliance tracking of United States weapons systems, facilities, inspection activities, and personnel subject to USG negotiated treaty provisions, and related procedures and practices.

The New START Treaty was signed by President Obama on 8 April 2010. At that time, OSD AT&L directed the DoD Services and Agencies to execute all taskings required to implement the NST and provide full life-cycle support for the life of the treaty. One action required by DTRA is to update the existing ACES with these new treaty requirements, protocols and notifications. OSD AT&L Policy has requested an ACES NST Fully Operational Capability (FOC) software fielding date as close to Entry Into Force (EIF) as possible. EIF occurred on 5 February 2011, officially starting the requirement to meet all NST data notification and data exchange milestones. NST data notifications started 6 February 2011. The first data exchange occurred 22 March 2011 and was generated and validated manually due to ACES NST software development efforts. The next three NST data exchange milestones occur September 2011, March 2012 and September 2012. OSD AT&L Policy & Treaty Compliances' rationale for the immediate software fielding date is to minimize the operational user requirement for manual data processing to meet NST requirements while the ACES is being updated. To field software capability as quickly as possible, a spiral approach was been adopted. This approach consisted of three software spiral increments fielded to the user at roughly 12 months after initial contract award with the 2nd and 3rd spiral 6-months and 12-months after the first spiral deployment. To meet this requirement, a one-year letter contract was initiated with NGIS to develop, test and deploy Spiral 1 which is scheduled for deployment 30 September 2011. Spiral 1 provides ACES NST Initial Operating Capability (IOC). Spiral 2 and 3, scheduled for deployment 6-months and 12-months after Spiral 1 deployment will provide Fully Operational Capability (FOC) for the ACES NST. This effort is for the Spiral 2 and Spiral 3 software development and deployment activities along with providing full life-cycle support to include planning and executing the program management responsibility transfer and software support tasks and activities to allow for a successful program management transfer from DTRA RD-IS to DTRA OP-OS During the software development, the treaty compliance officers (ACES NST users), must perform manual data processing which is man-power intensive, impacting the operational units, service and agency headquarters, Joint Staff and OSD who are currently are not staffed for this level of effort.

2.0 Scope

DTRA’s Research and Development (RD) Enterprise, Innovations & Systems Engineering Directorate (RD-IS) requires NGIS software development expertise to implement the New START Treaty requirements, protocols and notifications into the existing ACES software structure. This effort will allow for NSIG to develop, test, integrate and field the ACES New START Treaty Spiral 2 and Spiral 3 software into the ACES software structure along with providing full life-cycle support to include planning and executing the program management responsibility transfer and software support tasks and activities to allow for a successful program management transfer from DTRA RD-IS to DTRA OP-OS.

This effort calls for two software spirals (Spiral 2 and Spiral 3)to be fielded to the user at the 6-month and 12-month time period after contract award. These deployment milestone dates have been coordinated with OSD AT&L TC to be Spiral 2 deployment NLT 30 March 2012 and Spiral 3 deployment NLT 30 September 2012 with program management transfer and software support activities to complete NLT 30 March 2013 to ensure full life cycle support capability. Included within the program management transfer and software support activities in one NST maintenance software release.

Additional requirements included NGIS support to the Independent Verification & Validation (IV&V) assessment of each spiral and software maintenance release prior to fielding and maintaining existing external interface requirements. The external arms control information technology interfaces include: DTRA Inspection Planning Module (IPM), DTRA Open Skies (OSMAPS), and the NAVY Strategic Programs Automated Reporting Treaty Accountable Notification System (SPARTAN), Organization for Security Cooperation within Europe's (OSCE) Integrated Notification Application (INA), WINPAC Automated Data System (ADS) and Global Ground Communication Link (GGCL). Knowledge of these databases and programs are required to ensure planned updates and requests for ACES.

In addition, this software upgrade must maintain compliance with the ACES required treaties / agreements which requires subject matter expertise of the following treaties: Conventional Forces within Europe (CFE), Open Skies, Vienna Documents 1999 (VDoc99), GEMI, United Nationals Transparency In Armaments (UNTIA), Wassenaar and INF.

3.0 Applicable Documents:

3.1 DoD Directives

DoD 5000.2-R: Mandatory Procedures for Acquisition Programs (MDAPS) and Major Automated Information System (MAIS) Acquisition Programs, 5 April 2002

DoD Directive 8500.1: Information Assurance (IA)

DoD Directive 8500-M: Information Assurance Manual

DoD Instruction 8500.2: Information Assurance (IA) Implementation

DoD Directive 8320.1: DoD Data Administration DoD 2060.1: Implementation of, and Compliance with, Arms Control Agreements, 9 January 2001

3.2 Other Directives

Joint Technical Architecture User Guide and Component JTA Management Plan, Version 1.0, 14 September 2001 IEEE/EIA 12207: Standard for Information Technology – Software Life Cycle Processes, March 1998 (see Section 1.4 for mapping/tailoring)

Section 508 of the Rehabilitation Act Amendments to the Workforce Investment Act of 1998 3.3 Directives/Guidance Not applicable.

3.4 ACES Documentation

ACES Training Plan June 2009

Configuration Management Plan (CMP) June 2009

Concept of Operations (ConOps)-Strategic June 2009

Continuity of Operations Plan (COOP) - June 2009

Database Design Description (DDD) June 2009

Interface Design Description (IDD) Strategic June 2009

Measurement Plan Aug 2009

Quality Assurance Plan (QAP) Sep 2009

System Architecture and Requirements Allocation Description (SARAD) June 2009

System Engineering Management Plan (SEMP) July 2009

Software Requirements Specification (SRS) June 2009

System Security Authorization Agreement (SSAA) June 2009

System Requirements Specification (SyRS) Strategic June 2009

Validation and Verification Plan (VVP) June 2009 3.5 Treaty / Agreement Requirements

Treaty between the United States of America and the Russian Federation On Measures For The Further Reduction And Limitation of Strategic Offensive Arms, 8 April 2010 Protocol To The Treaty Between The United States of America And The Russian Federation On Measures For The Further Reduction And Limitation Of Strategic Offensive Arms, 8 April 2010 Annex on Notifications to the Protocol to the Treaty Between the United States of America and the Russian Federation on Measures for the Further Reduction and Limitation of Strategic Offensive Arms, undated

Annex on Telemetric Information to the Protocol to the Treaty Between the United States of America and the Russian Federation on Measures for the Further Reduction and Limitation of Strategic Offensive Arms, undated

Annex on Inspection Activities to the Protocol to the Treaty Between the United States of America and the Russian Federation on Measures for the Further Reduction and Limitation of Strategic Offensive Arms, undated

Article-By-Article Analysis of New START Treaty Documents, 5 May 2010 USD AT&L Memo, “Planning for Implementation of the New START Treaty”, 12 Feb 2010

Assistant Secretary of Defense Memo, Implementation of the New START Treaty, 8 April 2010

NST Security Classification Guide, 6 May 2011 Draft Initial Arms Control Enterprise System (ACES) Requirements Elicitation for New START Treaty (NST), date14 Sept 2010

4.0 Objectives

The ACES Software Development, Integration and Fielding and full life-cycle support objectives addressed in this SOW encompass the full life cycle of information technology (IT) programmatic and technological activities, including, but not limited to:

· Program and project management activity

· Risk Analysis / Mitigation

· Requirements definition / analysis, to include Software Change Request (SCR) and Software Problem Report (SPR) tracking, investigation, correction and management

· Documentation of Operational Concept Description

· Systems engineering and integration

· Design and development of software and user interface for new / updated treaties / agreements and software modifications / upgrades

· Test & Evaluation

· Independent Verification & Validation Support

· Deployment

· Training

· Documentation Preparation, Approval and Delivery

· Systems, Network, and Security (Information Assurance) Administration

· Treaty/Agreement Data Exchange Support

5. Tasks or Requirements

The contractor shall provide all of the resources necessary to complete all tasks under this statement of work unless specifically identified as Government-furnished.

5.1 Spiral 2 Software Development, Integration, Test and Deployment (Base) 5.1.1 Software Development, Integration, Test and Deployment Management. The contractor shall plan, provide, manage and execute processes and activities in program management, data management, configuration management, systems engineering, software development, verification and validation, test & evaluation, deployment and fielding, software support, training, risk management, software resolution, etc. for the ACES NST Development Program IAW IEEE/EIA 12207.0 and 12207.1 and existing ACES Program processes while coordinating with on-going ACES Operational & Maintenance implementation activities to maximum extent possible. (CDRLs A006, A007, A008, A009, A010, A011, A012, A013, A014, A015, A017, A020, A023, A025, A026, A027 and A028) NOTE: The ACES SME Team will provide software development, integration, test and fielding recommendations to the government program manager during this development effort. The contractor shall work with the SME Team to provide the most cost effective, operationally sound solution.

5.1.2 Requirements Management. The contractor shall perform requirements definition, analysis, and decomposition of Spiral 2 requirements to include the ACES interface, user and system-level requirements listed in Section 3.0 “Applicable Documents”). (CDRLs A001, A002, A003, A004, and A024). The contractor shall maintain consistency with existing ACES Human-User Interfaces. The contractor shall maintain support for existing ACES interface (for example: IPM and SPARTANS), user, and system-level requirements during software development, integration, test and fielding. (CDRL A005) The contractor shall participate in the ACES Development & Integration Integrated Product Team (IPT) and ACES Configuration Control Board (CCB) to assess the impact of new requirements.

5.1.3 Independent Verification & Validation (IV&V) Support. The contractor shall support the Independent Verification & Validation (IV&V) activities, user, and operational testing and user training, ensuring these activities are integrated into the overall ACES development, test, and fielding milestones. NOTE: The ACES Development & Integration IV&V Team shall provide fielding recommendations to the government program manager prior to ACES NST spiral fielding to the operational environment.

5.1.4 Software Fielding. The contractor shall deploy the Spiral 2 software to the ACES operational environment upon government concurrence, ensuring that all training, user fielding, interface requirements (IPM and SPARTANS) and coordination tasks are planned for, supported and executed. The planned software fielding date is no later than 6 months after contract award.

5.1.5 Training Requirements. The contractor shall prepare and conduct familiarization training sessions with OSD, Joint Staff, NRRC, Air Force, Navy and DTRA personnel and all other personnel for new or revised ACES functionality related to Spiral 2. (CDRL A019)

5.1.6 Software Documentation. The contractor shall document, update and maintain all required software documentation to meet IV&V documentation requirements, fielding, and software support requirements for Spiral 2. (CDRLs A018, A021, and A022) The contractor shall establish and/or actively maintain a web portal through which project stakeholders may be kept informed of relevant activities and have access to the latest ACES technical documentation and information. The functionality of the portal shall be established in accordance with DTRA requirements.

5.1.7 Security Requirements. The contractor shall manage, maintain, execute and keep current Accreditation & Certification (A&C), DoD IT security update requirements activities and tasks, DTRA requirements and certifications as required to support Spiral 2 operational testing and software deployment to the operational environment. (CDRL A016)

5.2 Spiral 3 Software Development, Integration, Test and Deployment (Option 1) 5.2.1 Software Development, Integration, Test and Deployment Management. The contractor shall plan, provide, manage and execute processes and activities in program management, data management, configuration management, systems engineering, software development, verification and validation, test & evaluation, deployment and fielding, software support, training, risk management, software resolution, etc. for the ACES NST Development Program IAW IEEE/EIA 12207.0 and 12207.1 and existing ACES Program processes to ensure all full life-cycle support requirements are met. (CDRLs A006, A007, A008, A009, A010, A011, A012, A013, A014, A015, A017, A020, A023, A025, A026, A027 and A028) NOTE: The ACES SME Team will provide development, integration, test and fielding recommendations to the government program manager during this development effort. The contractor shall work with the SME Team to provide the most cost effective, operationally sound solution.

5.2.2 Requirements Management. The contractor shall perform requirements definition, analysis, and decomposition for the Spiral 3 software to include the ACES interface, user and system-level requirements listed in Section 3.0 “Applicable Documents”. (CDRLs A001, A002, A003, A004, and A024). The contractor shall maintain consistency with existing ACES Human-User Interfaces. The contractor shall maintain support for existing ACES interface (for example: IPM and SPARTANS), user, and system-level requirements during software development, integration, test and fielding. (CDRL A005) The contractor shall participate in the ACES Development & Integration Integrated Product Team (IPT) and ACES Configuration Control Board (CCB) to assess the impact of new requirements.

5.2.3 Independent Verification & Validation (IV&V) Support. The contractor shall support the Independent Verification & Validation (IV&V) activities, user, and operational testing and user training, ensuring these activities are integrated into the overall ACES development, test, and fielding milestones for Spiral 3. NOTE: The ACES Development & Integration IV&V Team shall provide fielding recommendations to the government program manager prior to ACES NST spiral fielding to the operational environment.

5.2.4 Software Fielding. The contractor shall deploy the Spiral 3 software to the ACES operational environment upon government concurrence, ensuring that all training, user fielding, interface requirements (IPM and SPARTANS) and coordination tasks are planned for, supported and executed. The planned deployment date is no later than 6 months after Spiral 2 deployment.

5.2.5 Training Requirements. The contractor shall prepare and conduct familiarization training sessions with OSD, Joint Staff, NRRC, Air Force, Navy and DTRA personnel and all other personnel, with the focus of this training on new or revised ACES functionality related to Spiral 3. (CDRL A019)

5.2.6 Software Documentation. The contractor shall document, update and maintain all required software documentation to meet IV&V documentation requirements, fielding, and software support requirements for Spiral 3. (CDRLs A018, A021, and A022) . The contractor shall establish and/or actively maintain a web portal through which project stakeholders may be kept informed of relevant activities and have access to the latest ACES technical documentation and information. The functionality of the portal shall be established in accordance with DTRA requirements.

5.2.7 Security Requirements. The contractor shall manage, maintain, execute and keep current Accreditation & Certification (A&C), DoD IT security update requirements activities and tasks, DTRA requirements and certifications as required to support Spiral 3 operational testing and software deployment to the operational environment. (CDRL A016)

5.3 Program Management Transfer & Software Support (Option 2) 5.3.1 Software Development, Integration, Test and Deployment Management. The contractor shall plan, provide, manage and execute processes and activities in program management, data management, configuration management, systems engineering, software development, verification and validation, test & evaluation, deployment and fielding, training, risk management, software support, software resolution, etc. for the ACES NST Development Program IAW IEEE/EIA 12207.0 and 12207.1 and existing ACES Program processes to ensure full life-cycle support requirements are met. (CDRLs A006, A007, A008, A009, A010, A011, A012, A013, A014, A015, A017, A020, A023, A025, A026, A027 and A028) NOTE: The ACES SME Team will provide development, integration, test and fielding recommendations to the government program manager during this development effort. The contractor shall work with the SME Team to provide the most cost effective, operationally sound solution.

5.3.2 Requirements Management. The contractor shall perform requirements definition, analysis, and decomposition of the planned NST maintenance software release to include the ACES interface, user and system-level requirements listed in Section 3.0 “Applicable Documents” at contract award (CA). (CDRLs A001, A002, A003, A004, and A024). The contractor shall maintain consistency with existing ACES Human-User Interfaces. The contractor shall maintain support for existing ACES interface (for example: IPM and SPARTANS), user, and system-level requirements during software development, integration, test and fielding. (CDRL A005) The contractor shall participate in the ACES Development & Integration Integrated Product Team (IPT) and ACES Configuration Control Board (CCB) to determine and finalize the content of the NST maintenance software release.

5.3.3 Independent Verification & Validation (IV&V) Support. The contractor shall support the Independent Verification & Validation (IV&V) activities, user, and operational testing and user training for the NST software maintenance release, ensuring these activities are integrated into the overall ACES development, test, and fielding milestones. NOTE: The ACES Development & Integration IV&V Team shall provide fielding recommendations to the government program manager prior to ACES NST software maintenance fielding to the operational environment.

5.3.4 Software Fielding. The contractor shall deploy the NST software maintenance release to the ACES operational environment upon government concurrence, ensuring that all training, user fielding, interface requirements (IPM and SPARTANS) and coordination tasks are planned for, supported and executed. The planned NST software maintenance release deployment date is no later than 6 months after Spiral 3 deployment.

5.3.5 Training Requirements. The contractor shall prepare and conduct familiarization training sessions with OSD, Joint Staff, NRRC, Air Force, Navy and DTRA personnel and all other personnel. The focus of this training shall be on all new or revised ACES functionality related to the NST-level software fielding. (CDRL A019)

5.3.6 Software Documentation. The contractor shall document, update and maintain all required software documentation to meet IV&V documentation requirements, fielding, and software support requirements for the NST software maintenance release and the NST-level software deployment. (CDRLs A018, A021, and A022) . The contractor shall establish and/or actively maintain a web portal through which project stakeholders may be kept informed of relevant activities and have access to the latest ACES technical documentation and information. The functionality of the portal shall be established in accordance with DTRA requirements.

5.3.7 Security Requirements. The contractor shall manage, maintain, execute and keep current Accreditation & Certification (A&C), DoD IT security update requirements activities and tasks, DTRA requirements and certifications as required to support NST software maintenance release operational testing and software deployment to the operational environment. . (CDRL A016)

6.0 Period of Performance

Base (Spiral 2):

6 months Option 1 (Spiral 3):

6 months Option 2 (PM Transfer):

6 months 7.0 Place of performance/Travel The contract work will be performed primarily at the contractor’s facility. Contractor may be required to participate in user meetings at other locations such as DTRA HQ, Ft Belvoir, at the Pentagon, or at other local facilities. Long distance travel (both CONUS and OCONUS) is possible and specific travel requirements shall be included in task order requirements.

The Contractor shall provide a detailed estimate of any required out-of-town travel in advance to the Task Manager in writing via memorandum or email. Included in this information is a summary of the travel requirement, e.g., who is traveling, reason for travel, etc. All travel shall be in accordance with the Joint Travel Regulation (JTR) and all out-of-town travel shall be approved by the Task Manager in writing via memorandum or e-mail prior to the contractor incurring any travel expenses and prior to any departure. Anticipated Out-of-Town Travel requirements will be determined by each Task Order. Travel costs shall be provided in monthly cost reports. Per-diem shall be in accordance with the Federal Travel Regulation for the locations visited.

Anticipated travel for Spiral 2, Spiral 3 and Program Management Transfer/Software Support activities are expected to be the same for each major activity and is given below:

The Contractor shall perform travel on a cost reimbursable basis as required in the performance of this contract. No profit or fee shall be added. The Contractor shall , make travel arrangements enough in advance of travel to obtain the most advantageous rates and documentation of this approval shall be included with each travel report, primarily via copy of e-mail records. Short-notice trips shall be approved verbally, with e-mail follow-up immediately thereafter.

8.0 Government Furnished Property (GFP)/Government Furnished Material (GFM) Government Furnished Equipment (GFE)

The contractor shall purchase materials to satisfy full life-cycle support requirements. Such material may include license and maintenance agreements or support activities by other vendors. All materials purchased by the Contractor for the use or ownership of the Federal Government will become the property of the Federal Government. In the monthly progress report, the Contractor shall document expenses and the transfer of materials or any licenses or agreements. The Contractor must furnish evidence of having obtained three competitive quotes for like items prior to any purchases. In some instances, materials may be available from Government supply sources, including GSA schedules. When applicable, the Government will provide the Contractor authorization to use Government supply sources in accordance with FAR 51.101.

9.0 Security

The contractor shall possess a SECRET Facility Clearance. Employees working on this program must be U. S. citizens, and contractor personnel with access to the operational ACES data will require a minimum of a DOD SECRET clearance in order to provide the required support. Selected individuals may require Top Secret clearances. Clearances must be in place prior to contract award (or contractor submitting a proposal) in accordance with the attached DD254.

10.0 Deliverables

The contractor shall provide electronic versions of each CDRL, using the appropriate format (Microsoft Word, Excel, or PowerPoint, or other format as approved by the Project Office) per the applicable Contract Data Requirements List (CDRL), DD Form 1423. Delivery and approval requirements are per the applicable CDRL DD Form 1423. All deliverables shall include on the cover or first page: Contractor Name, Contract Number, Order Number (On the face of the award document), and Deliverable Number (When report is prepared several times, as Monthly or Quarterly reports).

The government will have ten (10) business days to conduct its review of completed products with the exception of the System/Software Requirements Specification A001 which is an extensive document requiring fourteen (14) business days to review. On receipt of comments, the contractor shall have ten (10) business days to prepare revisions and to submit final versions of the deliverables and the products.

PAGE