N66001-17-R-0169 RFP Amendment 0001.pdf

1300612846

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this solicitation amendment is to incorporate changes resulting from questions and answ ers.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 38

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 14-Jul-2017

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N66001-17-R-0169

X 9B. DATED (SEE ITEM 11)

14-Jun-2017

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

13-Jul-2017

CODE

SPAWAR SYSTEMS CENTER PACIFIC

CARLOS A. TRIAY, CODE 22560

CARLOS.TRIAY@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152

N66001 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N66001-17-R-0169

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 18-Jul-2017 04:00 PM to 27-Jul-2017 04:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

Global Readiness & Force Management Enterprise (GRFME)

1.1 BACKGROUND

The Defense Authorization Act for Fiscal Year 1999 required the Secretary of Defense to implement a comprehensive readiness system capable of accurately and objectively measuring readiness to support execution of the National Security Strategy (NSS), National Military Strategy (NMS) and Title 10 responsibilities. This system must be able to measure readiness in a timely manner to ensure responsiveness to support National Command Authority (NCA) review of crucial national security issues. Department of Defense Directive 7730.65, May 11, 2015, establish policy and assigns responsibilities for the Department of Defense Readiness Reporting System (DRRS) in accordance with section 117 of Title 10, United States Code. Applicable to the entire Department, this directive prescribes the role of the capstone Defense Readiness Reporting System – Strategic (DRRS-S) and in turn the Services’ need for readiness reporting systems able to provide current readiness data, in an appropriate contextual manner, that supports the Department’s needs, through DRRS-S.

Department of Defense Instruction 7730.66 establish further detailed policy and responsibilities for capabilities-based, adaptive, near real-time readiness reporting within the Department of Defense, as well as the need for this reporting to be fully integrated with vital DoD initiatives supporting training, adaptive planning, and global force management (GFM).

Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3401.02B establishes further policy, procedures and criteria for reporting of authoritative information to the President and Secretary of Defense including the requirement to report the readiness of military forces to meet missions and goals to the DRRS Enterprise and into the DRRS-S.

Information from the DRRS enterprise is used by the Combatant Commanders (CCDRs), Military Services, Joint Chiefs of Staff, Combat Support Agencies (CSAs), and senior leaders within DoD to inform key decisions on a daily basis. This information supports, crisis response planning, deliberate or peacetime planning, and management responsibilities to organize, train, and equip combat-ready forces for the unified commands. Additionally, the systems in the enterprise form the basis for reporting readiness to the National Command Authority (NCA), comprised of the President and the Secretary of Defense, and to Congress. Systems within the enterprise are designated as high as Mission Assurance Category I (MAC I), meaning they handle information that is determined to be vital to the operational readiness or mission effectiveness of deployed and contingency forces in terms of both content and timeliness. Consequently, the most stringent of protections measures are required. Any loss of integrity or availability of these systems is unacceptable and could cause the immediate and sustained loss of mission effectiveness.

The components of the Department’s readiness enterprise are primarily hosted in the Non-Secure Internet Protocol Router Network (NIPRNet) and Secret Internet Protocol Router Network (SIPRNet), however, work within, and integration with, networks of higher classification is sometimes necessary to support the comprehensive readiness information needs of the Department. The components of the readiness enterprise are hosted in numerous locations, to include, but not limited to, various Defense Information Support Activity (DISA) Defense Enterprise Computation Centers (DECCs) and Navy networks in locations such as Naval Computer and Telecommunication Center (NCTS) San Diego. Although the core components of the readiness enterprise are SIPRNet based, even their operation and support often requires personnel with privileged access to these systems possess either Top Secret level clearances or have current Single Scope Background Investigations (SSBIs).

2.0 SCOPE

The scope of this contract will include systems engineering, software design/development, integration, testing, installation, training, life cycle maintenance, procurement support, help desk services, management support, and system documentation for DRRS-S and all systems reporting readiness data into DRRS-S and into the enterprise.

This contract is meant to support the Government’s readiness reporting strategy and readiness and resources processes and policies and DoD transformational initiatives to enable a comprehensive view of readiness and resources for coordination, integration, analysis, and assessment of capabilities, deficiencies, resource status, and military risk.

This initiative provides for system engineering, system sustainment, system integration, enterprise data integration support, data warehousing, sharing of enterprise components and services, testing, installation, training, life cycle maintenance, configuration management, procurement support, help desk services, management support, and system documentation for the systems and modules that support readiness reporting. This includes data sources, modules, components and methodologies essential to meeting the Government’s current and future readiness reporting requirements and objectives.

This is an Enterprise-wide initiative intended to provide the support and services mentioned above, to current and future programs and systems considered part of the Global Readiness & Force Management enterprise. The following list of included systems is illustrative, and should not be considered an exhaustive or exclusive list of system included within the enterprise:

• Defense Readiness Reporting System – Strategic (DRRS-S)

• Defense Readiness Reporting System – Army (DRRS-A)

• Defense Readiness Reporting System – Marine Corps (DRRS-MC)

• Aviation Maintenance Supply Readiness Reporting (AMSRR)

• Navy Expeditionary Combat Command Readiness and Cost Reporting Program (RCRP) Included under this initiative are all pertinent versions of these (and other systems) to include, but not be limited to, Government owned or controlled, Production, COOP, Pre-Production, Tests, Integration, and Development systems.

This initiative provides for the continued development and integration of software components, interfaces and authoritative systems necessary to access DoD, service, and agency data sources to support the Government’s readiness reporting strategy. This initiative also provides for the tailoring of existing readiness systems, system components and interfaces to expedite delivery of capability to organizations with like deployment models and resource management processes within the enterprise.

The contract will continue to support reporting under the mission essential task construct and readiness metrics that indicate the Force’s ability to execute broader Mission Area or Mission. The construct requires that readiness measures for personnel, equipment, supply, training, ordnance and facilities be integrated with or supportive of the mission essential tasks associated with each Command level, and a technical architecture be supported that enables data exchange, near real time, between all Services and Agencies to support the Office of Secretary of Defense view of readiness capability.

To ensure overall effectiveness and efficiency of communications, operations, information transport, and network management capabilities, this effort shall adopt the National Information Infrastructure (NII) Global Information Grid (GIG). The GIG is defined as a seamless web of communications networks, computers, software, databases, applications, data, and other capabilities in a network centric environment that meet the information processing and transport needs of DoD users during all contingencies of peacetime and conflict

2.1 Applicable Standards and Documents

2.1.1 Standards

Systems within the DRRS enterprise are to be based on Service-Oriented Architecture (SOA). Service-Oriented architecture is a flexible set of design principles used during the phases of system development and integration.

Functionality is packaged as a suite of interoperable services providing a means for the enterprise to build distributed enterprise systems based SOA. Services are discrete units of application logic that support interoperability with services and systems internal or external to the enterprise and expose evocable interfaces to consumers. To address interoperability, extensibility, reusability and reliability, governing program architectures must include:

• Global Information Grid Enterprise Architecture

• Net-Centric Enterprise Services Existing Department of Defense approved product, process and procedural implementation frameworks that embody and facilitate interoperability with the Network-Centric Warfare (NCW) environment shall be used. Technical implementation guidance includes:

• Net-Centric Assistant Secretary of Defense (Networks and Information Integrations) (ASD (NII)) Checklist

Guidance

• Net-Centric Migration Guidance

• Net-Centric Node Architecture Guidance

• Net-Centric Developers Guidance

• Net-Centric Data Strategy The GFM Community of Interest (COI) data standards development effort shall be supported. The GFM-COI, through the GFM Data Initiative (GFM-DI), shall provide the data identification, data definitions, data schema, XML schema, Web Services Definition Language (WSDL) and data exchange architecture. These data standards shall provide the basis for the Net Centric Data Strategy for development to support DRRS enterprise initiatives.

2.1.2 Documents

The documents listed below are applicable for this contract. If additional documentation is required for the performance of a task, the Government shall identify this documentation at the task order level and provide access to the contractor. The DRRS enterprise shall support the following standards and policies:

• 10 United States Code (U.S.C.) §117, Readiness Reporting System: Establishment; Reporting to Congressional Committees.

• Defense Readiness Reporting System Strategic (DRRS-S)/Global Visibility Capability (GVC) Capability Requirements Document (CRD), 22 October 2009

• 44 U.S.C. Chapter 35, Subchapter III, Coordination of Federal Information Policy (also known as the “Federal Information Security Management Act (FISMA) of 2002”)

• Department of Defense Instruction 5000.02, 7 January 2015, Operation of the Defense Acquisition System.

• Department of Defense Directive 7730.65, 11 May 2015, Department of Defense Readiness Reporting System.

• Department of Defense Instruction 7730.66, 8 July 2011, Guidance for the Defense Readiness Reporting System (DRRS).

• Department of Defense Directive 8140.01, 11 August 2015, Cyberspace Workforce Management.

• Department of Defense Instruction 8260.03, 19 February 2014, The Global Force Management Data Initiative (GFM DI).

• Department of Defense Instruction 8320.02, 5 August 2013, Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense.

• Department of Defense Instruction 8320.02, 3 August 2015, Implementing Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense.

• Department of Defense Instruction 8330.01, 21 May 2014, Interoperability of Information Technology (IT), Including National Security Systems (NSS).

• Department of Defense Instruction 8510.01, 12 March 2014 (Incorporating Change 1, May 24, 2016), Risk Management Framework (RMF) for DoD Information Technology (IT).

• Department of Defense 8570.01-M, 19 December 2005 (Incorporating Change 4, November 10, 2015), Information Assurance Workforce Improvement Program.

• OSD Memo 2 Aug 2010, Defense Readiness Reporting System (DRRS) Standards and Technical Interface Specifications for Interoperability.

• DoD Architecture Framework, Version 2.02, August 2012

• Chairman of the Joint Chiefs of Staff Manual 3150.02B, 25 March 2011, Global Status of Resources and Training System (GSORTS).

• Chairman of the Joint Chiefs of Staff Instruction 3170.01I, 23 January 2015, Joint Capabilities Integration and Development System (JCIDS).

• Chairman of the Joint Chiefs of Staff Instruction 3401.02B, 31 May 2011, (Current as of 17 July 2014,), Force Readiness Reporting.

• Department of Navy, SECNAVINST 5000.36A, 19 December 2005, Department of the Navy Information Technology Applications and Data Management.

• Department of Navy, SECNAVINST 5230.14, 09 November 2009, Information Technology Portfolio Management Implementation.

• Department of Navy, SECNAVINST 5239.20A, 10 February 2016, Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management, Oversight and Qualification.

• Department of Navy, SECNAV M-5239.2, 27 June 2016, Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual.

• Department of Navy, OPNAVINST 3501.383, 20 October 2010, Fleet Readiness Reporting Guidance.

• Department of Navy, OPNAVINST 3501.389, 5 December 2012, Navy Readiness Reporting Enterprise Configuration Control Board Policy and Guidance.

• Department of Navy, Navy Tactical Reference Publication (NTRP) 1-03.5, February 2016, Defense Readiness Reporting System-Navy Reporting Manual.

• Chief of Naval Operations letter Ser N4/14U129002 of 28 February 2014, Mission Assurance Category Designation for Systems in the Navy Readiness Reporting Enterprise.

• ISO/IEC 12207:2008(E) (IEEE STD 12207-2008) Systems and Software Engineering-Software Life Cycle Processes.

• IEEE/EIA 12207.1-1997 IEEE Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data.

• ISO/IEC 14764:2006(E) (IEEE STD 14764-2006) Software Engineering - Software Life Cycle Process - Maintenance.

2.2 Abbreviations and Acronyms

CBT Computer Based Training NIPRNET Non-Secure Internet Protocol Router Network

CCB Configuration Control Board NMCI Navy Marine Corps Intranet CMCP’s Mission Capable Packages NMS National Military Strategy COOP Contingency of Operations NOSC Naval Oceans Systems COR Contracting Officer Representative NPC Navy Personnel Command COTR Contracting Officer Technical representative NSS National Security Strategy

CRF Coastal Riverine Force NTA Naval Tasks DBDD Database Design Description NTIMS Navy Training Information Management

System DII-COE Defense Initiative Common Operating

Environment NTMPS Navy Training and Management

Program System DISA Defense Information System Agency NUWC Naval Undersea Warfare Center DITSCAP DOD Information Technology Security

Certification & Accreditation Process OCD Operational Concept Description

DOD Department of Defense OFSC Organizational Force Structure Construction

DODAF Department of Defense Architecture Framework

OLAP Online Analytical Processing

DON Department of Navy OPLANS Operation Plans DRRS-N Defense Readiness Reporting System-

Navy OPNAV Office of the Chief of Naval Operations

DRRS-S Defense Readiness Reporting System- Strategic

OSD Office of the Secretary of Defense eMASS Enterprise Mission Assurance Support Service

PESTOF Personnel, Equipment, Supply, Training, Ordnance, Facilities

EOD Explosive Ordnance Disposal PCMCIA Personal Computer Memory Card International Association

PIA Privacy Impact Assessment EPMAC Enlisted Placement Management Center PMP Program Management Plan ERPS Emergency Response Procedures POA&M Plan of Actions and Milestones ETG Expeditionary Training Group POE Projected Operational Environment

FRTP Fleet Response Training Plan POP Period of Performance FTP File Transfer Protocol PRIMAR Primary Mission Area GFF Government Furnished Facilities PWS Performance Work Statement RM Records Management GFM Global Forces Management ROC Required Operational Capabilities GFMIEDM Global Forces Management Information

Exchange Data Model SDD Software Design Description

GIG Global Information Grid SDLC System Development Life Cycle GNFPP Global Naval Forces Presence Plan SDP Software Development Plan GR/GPM Government Representative/Government

Project Manager SIOM Software Input/output Manual

HAG High Assurance Guard SIP Software Installation Plan IDD Interface Design Description SIPRNET Secure Internet Protocol Router Network INFOSEC Information Security SME Subject Matter Expert IPR In Progress Review SOA Service Oriented Architecture IRS Interface Requirements Specification SOP’s Standard Operating Procedures ISP Information Support Plan SPS Summary Performance Sheet JCA Joint Capability Areas SRS Software Requirements Specification JNTA Joint Naval Tasks SSAA System Security Authorization

Agreement JPG Joint Planning Guidance SSDD System/Subsystem Design Description KO Contracting Officer SSO Single Sign On MCAST Maritime Civil Affairs and Security

Training Command SSS System/Subsystem Specification

MDSU Mobile Dive and Salvage Unit STD Software Test Description MOA Memorandum of Agreement STP Software Test Plan MOU Memorandum of Understanding STR Software Test Report MS Microsoft STRP Software Transition Plan MSR Monthly Status Report SUM Software User Manual N8 N8 Department (Warfare Programs and

Readiness) SVD Software Version Description

NAVELSG Naval Expeditionary Group TA Technical Assistant NAVICP Naval Inventory Control Point TCP/IP Transmission Control Protocol/Internet

Protocol NAVSEA Naval Sea Systems Command TOA Table of Allowances NCA National Command Authority UJTL/UNT

L Universal Joint Task List / Universal Navy Task List

NCEA Non-Combat Expenditure Allocations USFF US Fleet Forces NCF Naval Construction Force XML Extensible Markup Language NECC Navy Expeditionary Combat Command NEIC Navy Expeditionary Intelligence

Command

NII National Information Infrastructure

3.0 TECHNICAL REQUIREMENTS

The enterprise systems are aligned with the Warfighting Mission Area (WMA) portfolio. WMA information technology investments support and enhance the Chairman of the Joint Chiefs of Staff's joint warfighting priorities while supporting actions to create a net-centric distributed force, capable of full spectrum dominance through decision and information superiority. WMA information technology investments ensure Combatant Commands can meet the Chairman of the Joint Chiefs of Staff's strategic challenges.

Systems within the enterprise are designated as high as Mission Assurance Category I (MAC). As stated above, they handle information that is determined to be vital to the operational readiness or mission effectiveness of deployed and contingency forces in terms of both content and timeliness. Consequently, the most stringent of protections measures are required. Any loss of integrity or availability of these systems is unacceptable and could cause the immediate and sustained loss of mission effectiveness.

Enterprise requirements are defined by a set of capability categories that are designed to support an evolutionary and modular approach to satisfying DoD readiness reporting requirements by building upon the readiness reporting processes and readiness assessment systems and tools used across the enterprise. These capabilities are defined in the DRRS-S/GVC CRD.

Joint Mission Readiness This capability enables CCDRS, Service, and Combat Support Agency Headquarters to assess all current readiness metrics (e.g. Joint Capability Area (JCA) and MET-based Mission Assessments) as well as any future assessment metrics. The intent of this capability category is to capture the highest strategic level readiness data from a “Headquarters” perspective, and assess what Joint Pub 1-02 calls “joint readiness.”

Unit Mission Readiness (Force Readiness) This capability relates to the distinct unit-level reporting requirements across the Department. Force readiness is intended to provide the overall unit readiness (C-level), unit personnel (P), equipment and supplies on-hand (S), equipment condition (R), and training (T). This includes the “unit” type information for Joint entities and Service Headquarters type entities as directed, and exemplifies “unit readiness” as described in Joint Pub 1-02.

Global Force Management The capability provides military and civilian organizations with a system for managing unit and organizational data.

The GFM Data Initiative (GFM-DI) is the authoritative repository of Force Structure for the Department of Defense (DoD) and supports Joint Force Management processes, Planning, Programming, Budgeting and Execution (PPBE) processes, and operational planning.

Individual Readiness The capability relates to the deploy ability of individuals and impact on mission readiness. This includes the assessment of integrated metrics associated with personnel readiness portfolios, Individual Medical Readiness (IMR), and training.

Asset Visibility This capability enables obtaining, displaying, and integrating Service Authoritative Data Systems (ADS) information. It is focused more on system architecture and periodicity requirements to take the disparate service data sets and conform them into one cohesive picture for the Department of Defense.

Business Intelligence (BI) This capability delivers the ability to query, sort, display, and analyze readiness and asset visibility data based on the desires and needs of the user.

Installation Readiness This capability enables reporting on infrastructure, installations, training ranges (small Arms-Navy), etc. as directed by the Under Secretary of Defense (USD) for Personnel and Readiness (P&R) Serial Guidance.

Readiness Reviews This capability enables force-wide readiness reviews, to include functionality to support the Joint Combat Capability Assessment (JCCA) and Joint Force Readiness Review (JFRR) process, National Guard Bureau (NGB) State Dashboard, and other reviews.

Planning/Execution Support This capability enables interaction with the Global Force Management and Adaptive Planning and Execution communities. It meets the intent of DODD 7730.65, which requires “ESORTS information, where appropriate” to be integrated with planning systems and processes.

Historical Data Warehousing This capability fulfils the historical analysis and trend reporting requirements of the Department. It is related to the BI capability, but focused on historical collection and presentation of information (including continuity of operations (COOP) capability) rather than data queries.

System Architecture The goal of this capability is to capture the underlying information technology system specifications including security architecture, machine-to-machine interfaces, bandwidth, and other issues.

End-User Usability This capability fulfils end-user support for training, customer support and documentation.

3.1 Program Life Cycle Support

As specified in the individual task orders, the contractor shall provide program life cycle support, systems engineering and analysis, integration, network engineering, systems maintenance, testing, training, implementation, hardware/software installation, life cycle management, and documentation to support the systems in the readiness reporting enterprise.

DRRS

DRRS-S is a dynamic, on-going evolutionary development aimed at providing the Department of Defense, Combatant Commanders, Services and Agencies the highest level of readiness reporting, collection, display, and analysis for readiness assessment and planning.

DRRS-S is the enterprise hub linking readiness data and readiness systems providing the ability to view Mission Capability and readiness metrics cross DoD. From the Secretary of Defense to the Unit Commander, from the Geographic Combatant Commander to the State Joint Force Headquarters, for all DoD organizations, DRRS-S establishes a common language of tasks, conditions, and standards describing the capabilities essential to the completion of assigned missions across the readiness spectrum. DRRS-S allows the commander to manage rather than monitor readiness. It places the commander in a proactive position with a holistic readiness common operational picture.

As a mission–focused, capabilities-based application, DRRS-S provides Department of Defense (DoD) users a collaborative environment to facilitate operational decision-making via readiness evaluation of U.S. Armed Forces in support of assigned missions.

DRRS-S establishes a unique network of applications identifying the capabilities of military forces. The information in enterprise goes well beyond the standard resource accounting approach of traditional readiness reporting by providing assessments of each organization’s ability to conduct assigned tasks either in the context of their core mission or assigned operations. In addition, DRRS-S improves the efficiency of readiness reporting by merging stove piped data into a single integrated, authoritative source.

The contractor shall provide support to DRRS-S as described in this SOW including the development of enhancements and additional capabilities as specified by the DRRS-S Program Management Office (PMO).

AMSRR

The Aviation Maintenance Supply Readiness Reporting (AMSRR) Program provides objective assessment and reporting of readiness status on aircraft, installed/non-installed mission equipment, and support equipment. It also provides supply management data and reports. AMSRR supports DoD readiness reporting requirements through integration with the Aviation Data Warehouse (ADW), the Maintenance Figure of Merit (MFOM), and the Readiness Enterprise. AMSRR shares aviation maintenance and material data with Naval Aviation Logistics Command Management Information System (NALCOMIS) and provides aviation material status to the Defence Readiness Reporting Program – Strategic (DRRS-S). The following are integral components of AMSRR.

AMSRR Ashore AMSRR Web Ashore is the primary tool used to generate aircraft and equipment material condition data at the unit level for Ship, Wing, and Squadron users. It serves as the primary tool for quick access to AMSRR readiness information by users to view and analyze the data via pre-formatted reports and graphical representations. The AMSRR Web makes AMSRR data available on the Non-Classified Internet Protocol Router Network (NIPRNet).

AMSRR Afloat AMSRR Web Afloat is identical to the Web Ashore and is specifically designed to support deployed units and to capture aircraft and equipment material condition data.

RCRP

RCRP provides the Navy Expeditionary Combat Command (NECC), the Navy Bureau of Medicine and Surgery (BUMED) Command, and the Combat Camera Pacific Command (COMCAMPAC) operating forces a standardized, enterprise-wide capability to: measure, display and report the readiness status of forces' Personnel, Equipment, Supply, Training, and Ordnance PESTO resources to DRRS-N; support adaptive force packaging by granulating forces' capabilities and supporting resources to the level required to provide the necessary visibility and supporting readiness picture; stimulate cost-wise behaviour and shape future investment by providing a capability for future resource planning based on resource priority in the context of capabilities; and provide metrics-based planning support to improve the balance of readiness and cost by tying readiness to cost. RCRP includes a more granular set of capability categories that support detailed reporting and resource analysis for NECC.

Individual Readiness The capability relates to the deploy ability of individuals and impact on mission readiness. This includes the assessment of integrated metrics associated with personnel readiness portfolios, Individual Medical Readiness (IMR), and training (Qualifications, Certifications & Licenses).

Personnel Readiness This capability provides an assessment of how well the personnel currently assigned fulfill the requirements for each Navy Mission Essential Task (NMET) assigned to each unit. This includes six categories: Officer, Enlisted, Civilian, Navy Enlisted Classification (NEC), Training and Education (T&E), and Qualifications, Certifications and Licenses (Q/C/L). The critical metrics are based on the determination of whether there is a sufficient number of personnel assigned and whether the assigned personnel have the required professional experience, training, and technical expertise to fulfill the requirements for a given UIC.

Equipment Readiness This capability relates to the measurement of how well a unit is equipped to perform all missions. This includes the sufficiency and material condition of equipment for each NMET assigned to each unit.

Supply Readiness This capability relates to the measurement of a unit’s ability to sustain itself or other units, and to track items that support equipment or personnel. These items are broadly described as items that are normally consumed in use and lose their identity such as repair parts and consumables. The Supply Pillar provides a quantitative assessment of a unit’s supply readiness status for each Supply task, Training Readiness The capability relates to the training readiness calculation recorded against a valid NMET for a given unit. The training readiness indicator is calculated by both the performance factor (Pf) and the experience factor (Ef) for a given NMET and unit (Tr=Pf×Ef). This rule applies to systems or individual units that provide performance and experience observations or calculations representing the units combat potential.

Ordnance Readiness This capability relates to the measurement of units on hand ordnance or ability to possess or has access to ordnance necessary to conduct each applicable NMET assigned to each unit. The Ordnance Pillar is applicable to deployable units that are Ordnance Information System (OIS) Account Holders, and calculates a readiness score for combat requirements for ordnance.

RCRP is a customized, web-based, enterprise software application with a Service Oriented Architecture (SOA) that integrates with over 20 authoritative data sources supporting management of PESTO resources, mission and unit data-related sources based on an applied weighting methodology. RCRP operates on both the Non-Classified Internet Protocol Router Network (NIPRNet) and the Classified Internet Protocol Router Network (SIPRNET) networks.

RCRP supports reports generation for ad-hoc, user-defined and standardized resource and readiness reports.

Additionally, Decision Support tools aid in mitigating readiness risks, support identification of critical resources and prioritized gaps used in Program Objective Memorandum (POM) submission, buy plans, spend plans, and other resource justification processes.

3.1.1 Operation and Maintenance

As specified in the individual task orders, the contractor shall maintain a stable, efficient, and productive system and environment. The contractor shall perform software installation and updates, ensuring installations and updates are in compliance with all DoD Information Technology (IT) cyber security instructions and requirements.

Software installation and maintenance tasks shall be performed in Locations identified in the individual task orders.

The contractor shall support the maintenance of the operating systems and hardware, disaster recovery and COOP, data access, data delivery, disaster recovery procedures and backups.

The contractor shall manage accounts, system configuration, and other system administrative duties. The contractor shall maintain system documentation and procedures. The contractor’s systems administration process shall afford opportunities for input and oversight by the Government.

As specified in individual task orders, the contractor shall provide support to server and Disaster Recovery sites.

The contractor shall provide a contingency plan to support operations in event of a Government shutdown, furloughs, emergencies and critical situations.

3.1.2 Business Intelligence, System Administration and Database Maintenance As specified in the individual task orders, the contractor shall provide systems design, systems analysis, systems engineering, data base management and integration support to develop and maintain the system architecture and data. The contractor shall collect requirements and make necessary changes to support integrating readiness reporting systems and data into the enterprise. The contractor shall provide systems design and systems engineering support to create and implement and maintain a framework for net-centric compliant interoperability between applications that collect, analyse, and report readiness information within the enterprise and between the enterprise and other segments of the DoD that need readiness data.

The contractor shall provide technical and analytical services in support of database development, integration and maintenance in an operational environment. The contractor shall develop, publish, and maintain schemas and database dictionaries for the systems.

The contractor shall manage and maintain the data warehouse to ensure all data is cleaned, transformed, catalogued and made available for online data mining, analytical processing and decision support. The contractor shall provide systems design, systems analysis, systems engineering and life cycle maintenance support for Business Intelligence (BI) and other integrated technologies that provide technical solutions for analyzing historical, current and predictive views of readiness data.

The contractor shall provide the capability to extract data from legacy and enterprise sources to support decision-making at the enterprise level. The contractor shall develop methods to improve decision-making and capability assessment by retrieving and revealing information from the enterprise data sources. At a minimum, this will include creating all relationships to effectively query the database and to build a performance oriented data warehouse which includes information cubes that will support a commercial OLAP engine.

The contractor shall maintain the readiness reporting business function data and access procedures to support end user requirements. The contractor shall provide technical/functional support for systems and the data warehouse during working hours for staff personnel and after hours as specified in individual task orders.

3.1.3 Electronic Messaging Support

As specified in the individual task orders, the contractor shall maintain the Electronic Messaging Data Exchange capabilities currently employed by the programs under this effort. The contractor shall collect requirements, maintain, integrate, test and support any changes necessary to the Data Exchange capability, mandated by the Enterprise Messaging protocols which at a minimum includes the following:

• Provide a seamless data exchange service between programs and authoritative data sources (For example, data exchanges between DRRS-S and other relevant readiness systems (e.g. DRRS-N, DRRS-A, DRRS-

MC, JOPES, GCSS-J, GFM)

• Guarantee message transmission reliability

• Provide for dynamic routing between data sources and subscribers

• Provide for dynamic message building based on Government requirements

• Provide support for managed metadata for readiness community

• Provide transmission for a message in any Government-requested format

• Provide for security, and process classified data based on Government requirements

• Provide a scalable data exchange service

3.1.4 System Integration and Product Support

As specified in the individual task orders, the contractor shall develop installation plans using Government-approved configuration requirements. The contractor shall install and configure systems (hardware and software) developed by the contractor, tested and passed Certification and Accreditation (C&A) by the Government. The contractor shall participate in meetings with Government commands and activities to discuss development, Test and Evaluation (T&E), C&A coordination, implementation policy, and schedule issues. Installation schedules are under the direction of the appropriate Program Office representative who will direct installation schedules.

The contractor shall also be responsible for the installation of developed software or Government-approved Commercial off-the Shelf (COTS) purchased software under this contract necessary to support programs under this effort.

3.1.5 Network Support

As specified in the individual task orders, the contractor shall provide systems design and systems engineering support to implement and maintain a framework for net-centric compliant interoperability between applications that collect, analyze, and report readiness information within the enterprise and between the enterprise and other segments of the DoD that need readiness data.

The contractor shall provide telecommunications requirements analysis and network maintenance. The contractor shall provide networking, engineering and installation services. The contractor shall provide network-cabling services, install necessary software and hardware (e.g. routers and servers), and troubleshoot network operations.

The contractor shall participate in the installation of work stations, in the realignment of existing network capabilities.

3.2 Software Life Cycle Support

As specified in the individual task orders, the contractor shall provide software engineering, software development, systems engineering and analysis, integration, network engineering, systems maintenance, testing, training, implementation, hardware/software installation, life cycle management, and documentation to support DoD readiness system integration, sustainment and support.

The contractor shall provide software life cycle support, and the development of enhancements and additional capabilities for systems within the DRRS enterprise as specified in individual task orders.

3.2.1 Life Cycle Support

The contractor shall provide life cycle support, to include the maintain and sustainment current programs’ functionality and viability within the ever-evolving IT environment the Department of Defense must operate. This support may include, but is not limited to:

• Recommend software engineering approaches which describe program modules, classes, objects, databases, graphic user interface displays and reports needed to successfully implement the application program functional requirements

• Asset management and procurement of COTS software

• Provide analysis and documentation of high-level design of application software, hardware, and data interfaces

• Participate in system requirements collection, analysis and functional requirements definition

• Provide Transition Planning

3.2.2 COTS Procurement

The contractor shall procure the necessary maintenance and licenses required to maintain the Government-owned hardware and software required to support the Production, COOP, Pre-Production, test and development environments. Examples of procurement to include: SQL Server, Windows Server, FootPrints, Cognos, InfoSphere DataStage and SolarWinds. The contractor shall submit all draft licenses to the Contracting Officer’s Representative (COR) and Procuring Contracting Officer (PCO) for approval prior to purchase. All licenses shall be held by the Government.

3.2.3 Government Registry

The contractor shall ensure that all databases that use database management systems (DBMS) designed, implemented, and/or hosted on servers and/or mainframes supporting Navy applications and systems be registered in Department of Navy application and Database Management System (DADMS) and are Functional Area Manager (FAM) approved. The contractor shall ensure all integrated, installed, or operational applications hosted on Navy networks shall be registered in DADMS and approved by the FAM.

The contractor shall ensure that all networks, servers, or associated devices procured and/or connected to a Navy network complete DADMS registration and receive FAM (Functional Area Manager) approval per Secretary of the Navy (SECNAV) instructions.

The contractor shall as assist the DRRS Implementation Office (DIO) as required with maintaining FISMA (Federal Information Security Management Act) and accreditation information for the program.

3.2.4 Software Design Specification Compliance

The contractor shall sustain a web services based system, exposing all data via Extensible Markup Language (XML), employing a DoD standards compliant XML schema and interfaces for the enterprise. All software will be certified as fully compliant IAW the DISA NII Net Centric Warfare policy. The unclassified software and classified application software must meet all DoD policy requirements for operation on the Non-Secure IP Router Network (NIPRNET) and the Secret IP Router Network (SIPRNET) respectively.

3.2.5 Interoperability

The contractor shall support requirements for interoperability as identified in CJCSI 6212.01 (series). This includes the requirement to support the DoD Architecture Framework requirements and processes, interoperability testing and certification, JCS-Interim Certificate to Operate (ICTO) and CTO briefings, reports and remediation, and coordination and support for Joint Interoperability Testing through approved forums.

The contractor shall ensure that all Service-Oriented Architecture (SOA) applications will support integrated Identity Management, Permissions Management and Digital Rights Management ensuring that adequate confidentiality, availability and integrity are provided.

3.2.6 Software Configuration and Repository

The contractor shall document the production environment used to support the programs under this effort. The contractor shall identify the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developer's plans for transitioning deliverable items to the support agency. The contractor shall indicate how the end-product is compiled, tested, and distributed from the development environment to the production environment. The contractor shall indicate how data bases are maintained and updated in both the development environment and production environment.

The contractor shall assist the Government with the upload and management of the source code along with the implementation and maintenance of source code management processes.

The contractor shall provide technical support and quality assurance support with the Government repository for program software and artifacts repository.

3.2.7 Requirements Management

The contractor shall analyze current business processes and document potential improvements. The contractor shall collect, manage, and report to the Technical Representative requirements to code functionality to establish a common understanding among the stakeholders. The contractor shall coordinate recommendations and requirements with the Technical Representative. The contractor shall provide data on feedback from users, requirements and requirements traceability.

The relationships between these identified factors shall be used as a basis for estimating, planning, performing, and tracking the cost and schedule of products.

3.2.8 Engineering Changes

The contractor shall provide input and recommendations to the Technical Representative on defect corrections, enhancements and new requirements, including those changes proposed by system users. The contractor shall analyze the proposed changes to baseline requirements and provide detail descriptions of implementation requirements and impacts to the Government.

The contractor shall have a formal process to accept and track engineering change proposals, including changes to scope, requirements, defect reports and work items. The contractor shall capture data on priority of change, level-of-effort cost estimate, and completion status. The contractor’s configuration management process shall afford opportunities for input and oversight by the Government.

3.2.9 Documentation

The contractor shall maintain an up to date library that contains the complete set of documentation. The contractor shall update existing documentation or create new documentation as required by the Technical Representative.

Format and content of the changes shall not deviate significantly from that of the existing documentation.

3.2.10 Transition Planning

As part of the life cycle support for DRRS enterprise initiatives, the contractor shall provide technical support with the development of Software Transition Plans and assist the Government in setting up, configuring, and providing quality assurance with an on-going Government repository of the software and development and production environment.

The contractor shall identify the hardware, software, and other resources needed for life cycle support of deliverable software and describe the developer's plans for transitioning deliverable items to the support agency. The contractor shall indicate how the end product is compiled, integrated, tested, and distributed from the development environment to the production environment. The contractor shall indicate how data bases are maintained and updated in both the development environment and production environment.

3.2.10.1 Transition Plan – System Transfer Out

The contractor shall provide system life cycle and technical support for systems that are transitioned out from their area of responsibility to another organization or group. In support of this transfer, the contractor shall provide documentation consistent with the system being transitioned to include analysis of the following:

• Baseline system specification

• Interface specifications

• Database specifications

• Source code and build instructions

• Concept of Operations (CONOPS)

• User interface standards

• Requirements and requirements traceability

• Operations manuals and key personnel

• Hardware configuration and hardware inventory

• Software inventory and licenses, and software settings

• Dependencies

• Architecture descriptions

• Relationships to other Agencies and projects

The contractor shall develop a Transition Plan identifying a transition strategy, management controls, risks and contingencies, and a transition impact statement on: operations, technology, culture and organization.

The contractor shall assist the Government in developing service level agreements on:

• Operational and transition readiness

• End-to-end testing

• Validating performance and functional capabilities

• Operational effectiveness and suitability for day-today operations The Government may request the contractor to provide post transition system support to include documentation updates, training and troubleshooting.

3.2.10.2 Transition Plan – System Transfer In

The contractor shall develop a Transition Plan that describes how the contractor shall ensure sufficient operational capability and support immediately prior to undertaking support…