Draft PBWS as of 3-9-11.doc

PERFORMANCE-BASED WORK STATEMENT (PBWS) FOR

FOR

JOINT PRECISION APPROACH AND LANDING SYSTEMS (JPALS) SYSTEM DEVELOPMENT AND DEMONSTRATION PHASE (SD&D), NAVY UNMANNED COMBAT AERIAL SYSTEMS (N-UCAS), UNMANNED CARRIER-LAUNCHED AIRBORNE SURVEILLANCE AND STRIKE (UCLASS), BROAD AREA MARITIME SURVEILLANCE (BAMS), WAR FIGHTER NETWORKING (WFN), UNMANNED AIRCRAFT SYSTEM (UAS)/GROUND BASED SENSE AND AVOID (GBSAA) AND AUTOMATED AERIAL REFUELING (AAR) SUPPORT

1.0 INTRODUCTION

The Air Traffic Control (ATC) Systems Division, Naval Air Warfare Center, Aircraft Department (NAWCAD) Patuxent River Code 4.5.8, located at St. Inigoes, MD is the In-Service Engineering Agent (ISEA) and Software Support Activity (SSA) for Air Traffic Control and Landing Systems (ATC&LS). The ATC Division provides systems engineering support to developmental programs such as the Joint Precision Approach and Landing System (JPALS), Navy Unmanned Combat Air System (N-UCAS) and Unmanned Carrier-Launched Airborne Surveillance and Strike (UCLASS) programs. The JPALS program is developing the next generation air traffic control and landing system for Navy air-capable ships as well as providing the Precision Global Positioning System (PGPS) solution for N-UCAS/UCLASS auto-land functions. Satisfactory performance of the system will depend on both aircraft and shipboard algorithms that can adequately integrate Global Positioning System (GPS) and inertial sensor outputs through a robust data link.

NAWCAD 4.5.8 is tasked to prototype, test, integrate and evaluate JPALS equipment, into aircraft and ship platforms. During the Technology Development (TD) phase, JPALS prototyping will be conducted. This will require the installation and integration of JPALS components into test aircraft, JPALS Mobile Test Vehicle (JMTV), and into two test facilities (the Satellite Navigation (SATNAV) Facility and Technical Evaluation Center (SAFTEC), and the Landing Systems Test Facility (LSTF) JPALS extension, B2110) that were developed during the on-going TD phase. Support of this testing requires the management and operation of the test facility at NAS Patuxent River, MD, and the mobile test facility for the JPALS program.

The N-UCAS/UCLASS program is a Navy effort to demonstrate the technical feasibility, military utility and operational value for a networked system of high performance, weaponized Unmanned Air Vehicles (UAVs) to effectively and affordably prosecute combat missions. The Northrop Grumman X-47 platform is the current candidate UAV system being evaluated. Key parts of the integration of these unmanned air vehicles into the military force structure is an auto-land capability, incorporation within military air traffic control, Automated Aerial Refueling (AAR), and Warfighter Networking (WFN) development. Program activities will include efforts to simulate system performance, evaluate sensor units in operational environments, prototype ATC interfaces, and provide operator feedback geared toward anticipated landing on a carrier suitable platform. NAWCAD 4.5.8 is tasked to prototype and integrate the auto-land function, ATC interface, and AAR functionality into aircraft and ship platforms as appropriate and conduct testing. This will require the installation of these components into civil and military aircraft, Navy Aircraft Carrier (CV/CVN) platforms, the LSTF JPALS extension, the N-UCAS Aviation/Ship Integration Facility (NASIF), and the N-UCAS Mobile Test Platform (UMTP). Support of this testing will require the use of multiple mobile test vehicles requiring prototyping and integration efforts, and the set up and operation of the required test facilities.

1.1 Scope

The contractor shall provide technical products and engineering services in the above mentioned areas in accordance with this Performance Based Work Statement (PBWS) and Contract Data Requirements Lists (CDRLs) for the various systems under the NAWCAD Code 4.5.8 ATC Systems Division's cognizance. The scope of this contract includes research and development in the performance of prototype development and testing by accomplishing the following performance tasks.

a. Execute management and testing of JPALS systems into civil and military aircraft, SAFTEC, LSTF JPALS extension, and the JMTV. The contractor shall design and implement the installation and provide some systems components.

b. Execute N-UCAS/UCLASS CV Segment Hardware/Software Integration (HSI) in multiple test beds including CVN’s, the NASIF, and the UMTP.

c. Execute integration of AAR components and subsystems into civil and military surrogate aircraft and the NASIF and UMTP.

d. Supply engineering RDT&E labor to support the management, design, development, and test of the Shipboard Relative Global Positioning System (SRGPS), Precision Global Positioning Systems (PGPS) systems, War Fighter Networking (WFN), and the precision guidance source in support of the Automated Aerial Refueling (AAR) Program. Provide RDT&E to support management and testing of AAR, JPALS, WFN and the N-UCAS/UCLASS systems residing in civil and military aircraft, CVN platforms, the LSTF JPALS extension, the NASIF, and the UMTP. The contractor shall design the installation and provide some systems components.

e. Supply engineering RDT&E labor to support the flight clearance processes associated with AAR, N-UCAS/UCLASS, and JPALS surrogate aircraft by providing engineering and data items that support approvals.

f. Support the integration activities by configuring tools such as the Naval Avionics Platform Integration Emulator (NAPIE) to allow for non-production system prototyping on surrogate systems, and/or by sharing expertise gained during TD phase integrations. Support lab and field-testing of incremental integration efforts. Provide subject matter consulting services in the areas of GPS, inertial sensors, and data links/networking.

g. Configure the SAFTEC facility to support any post-TD phase testing. Perform maintenance of the SAFTEC while maintaining the current leasing agreement. Ensure that the configuration documentation of the SAFTEC is kept current.

h. Configure the JMTV to support any post-TD phase testing. Perform maintenance of the JMTV. Ensure that the configuration documentation of the JMTV is kept current.

i. Configure the UMTP to support any post-TD phase testing. Perform maintenance of the UMTP. Ensure that the configuration documentation of the UMTP is kept current.

j. Supply technical RDT&E labor to obtain or manufacture the components necessary to produce SRGPS systems, PGPS systems, mobile test platforms and N-UCAS/UCLASS CV Segment subsystems, and to assemble the components into a complete system.

k. Provide rapid prototyping and evaluation capabilities necessary to support evolving GPS, inertial, and data link/networking technologies.

2.0 APPLICABLE DOCUMENTS

The following is a list of known documents that will be needed, used and referred to during the performance of the technical and engineering services required by this performance work statement. Unless otherwise specified, the revision level and date of each document, specification or standard cited, or referred to, within this solicitation/contract shall be the most current or superseding version.

2.1 Military Specifications / Military Standards

NUMBER

TITLE

DoD 5200.1-R

Information Security Program Regulations

Joint Travel Regulations Vol. 1

DoD 5000.2

Operation of the Defense Acquisition System

NAVAIRINST 4355.19D

Systems Engineering Technical Review Process

Naval Systems Engineering Guide October 2004

MIL-STD-2036

General Requirements for Electronic Equipment

Specifications

OPNAVINST 3432.1

Operations Security

2.2 Other Documents

N-UCAS Common Objectives Document (COD)

Concept of Operations for Future Air Traffic Control Operations using the Sea based Joint Precision Approach and Landing System (JPALS)

JPALS Capability Development Document (CDD)

JPALS System Requirement Document (SRD)

JPALS Ship System Integration Requirements Document (SSIRD)

3.0 REQUIREMENTS

The contractor personnel shall work in conjunction with the JPALS, N-UCAS/UCLASS, AAR, WFN, BAMS and UAS/GBSAA teams defined within the NAWCAD 4.5.8 division. Analysis, recommendations, alternatives, estimates, reviews, research, or plans, shall be presented by the contractor in report form, in accordance with (IAW) the respective DD Form 1423.

3.1 General Requirements

3.1.1 Contract Program Management

The contractor shall provide the following program management services:

3.1.1.1 Project Control

a. Budget: Maintain cost accounting data (including data on utilization of proposed labor and reimbursable expenses). (CDRL A001)

b. Milestones/Schedules: Monitor work performed against milestones planned to assure that each project objective is met according to schedule. (CDRL A002)

c. Material Control: Track, manage, and otherwise account for incidental material during performance of a task order.

d. Contract Management Reports (Periodic, recurring submissions of resource expenditures and progress against the applicable planned activities). (CDRL A003 & CDRL A004)

3.2 Technical Development Planning

The contractor shall perform trade-off analyses, engineering approach analyses, prepare an Integrated Master Plan and recommend the specific avionics and shipboard system development/engineering efforts, facilities, and task requirements necessary to meet technical program objectives and milestones. The contractor shall define the major milestones, schedules and relevant resource requirements for each phase of a project. The contractor shall define:

a. Project estimating including cost, schedules, manpower, resources, size and Work Breakdown Structure. (CDRL A005, CDRL A006, CDRL A007)

b. Risk identification, assessment, impact, metrics, and mitigation (CDRL A005)

c. Milestones corresponding to tangible products, procurement cycle requirements, or achievement levels (CDRL A002)

d. Development methodologies and management processes, metrics, tools, configuration and quality control measures/procedures. (CDRL A008)

3.3 Systems Engineering

It is the Government’s intention to conduct a set of system engineering reviews, at their discretion, for projects that include system design and delivery as outlined in NAVAIRINST 4355.19D. In the case that the NAVAIR instruction is not applicable, the Government will specify the relevant directive to be followed. For non-ACAT programs, it is likely that, at a minimum, System Requirement Reviews (SRRs), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs) and System Verification Reviews (SVRs) will be conducted on projects where a system will be developed or delivered. (CDRL A009, CDRL A010) Other reviews that may occur at the Government’s discretion are: Initial Technical Reviews (ITRs), Alternative System Reviews (ASRs), System Functional Reviews (SFR’s), Software Specification Reviews (SSRs), Integration Readiness Reviews (IRRs), Test Readiness Reviews (TRRs), Physical Configuration Audits (PCAs), and In Service Reviews (ISRs). (CDRL A011, CDRL A012, CDRL A013, CDRL A014, CDRL A015) In an effort to successfully navigate the System Engineering Technical Review (SETR) process, the contractor must have a robust Systems Engineering model utilized in the engineering of their systems. Upon contract award, the contractor’s System Engineering process will be reviewed by the Government for completeness and acceptability. Additionally, at the Government’s discretion, the contractor shall be required to develop a Systems Engineering Management Plan (SEMP) for projects/programs deemed to have sufficient complexity. (CDRL A016) The SEMP will encompass the project/program’s technical approach including processes, resources, metrics, applicable performance incentives, and the timing, conduct, and success criteria of technical reviews for tasking that includes system design or delivery.

3.4 Research and Technical Analysis

The contractor shall provide research and analysis support in the area of system studies and analysis. This support shall include, but not be limited to, meteorological and oceanographic analysis, computer-based modeling analysis, navigation and guidance analysis, and advanced data and signal processing analysis. The contractor shall analyze techniques as applied to the processing of test data and systems performance improvement. (CDRL A017, CDRL A018)

3.5 Functional and Design Requirements

The contractor shall perform engineering studies and analyses for the purpose of generating functional and design requirements for sensor and support subsystems. The contractor shall prepare, from approved operational requirements documents, a detailed mission scenario and time line analysis. (CDRL A019, CDRL A020, CDRL A021, CDRL A022)

3.6 Aircraft and Ship Integration Analysis

The contractor shall perform engineering analysis of Government Furnished Information (GFI) pertaining to physical integration of sensors and supporting subsystems on the aircraft and ship. (CDRL A023)

3.7 Test and Evaluation Requirements Analysis (TERA)

The contractor shall prepare a Test and Evaluation Requirements Analysis which identifies the test activities required to verify attainment of all functional and performance requirements of each sensor and system. This analysis shall include all levels of testing from technology concept demonstration through Technical Evaluation (TECHEVAL). As part of this analysis, the contractor shall develop and deliver a test and evaluation matrix that identifies the system functional requirements and the test activities that demonstrate satisfactory compliance. An optimization process shall be performed which will identify those individual tests that may satisfy multiple requirements. (CDRL A024, CDRL A025)

3.8 Test Plans and Procedures

The contractor shall provide detailed test plans and procedures for test and evaluation activities. For test plans and procedures developed by other activities, the contractor shall analyze these test plans and procedures and identify their relationship with the test and evaluation matrices. (CDRL A026, CDRL A027)

3.9 Development Facilities

The contractor shall prepare development facility requirements and associated planning information to support the development, integration and evaluation of JPALS and N-UCAS/UCLASS technologies into civil aircraft, SAFTEC, JMTV, LSTF JPALS extension, NASIF and UMTP vans. The contractor shall provide the functional design and development of the hardware and software necessary for the laboratory system. The contractor shall also provide test and validation of the systems necessary to support development and test of the JPALS, N-UCAS/UCLASS, WFN, and AAR programs. These systems shall be fully documented to facilitate operator use, maintenance, and facilities updates. Data deliverables shall include user manuals for the facilities and for each system and software program delivered.

3.9.1 SATNAV Facility and Technical Center (SAFTEC)

The SAFTEC will contain the engineering space, facilities, and equipment required to execute JPALS shore-based ground and flight tests of prototypes at NAS Patuxent River, MD. The SAFTEC is located near Building 2110 at the Naval Air Station, Patuxent River, MD. The total square footage of the SAFTEC interior building is 2820 square feet (60'x47'). The deck square footage is 252 square feet (8' x 31.5'). The loading dock is 144 square feet. The contractor shall:

a. Provide maintenance coordination of the SAFTEC in response to service calls. (CDRL A029)

b. Perform monthly inspections of the building and perform minor or routine, operational upgrades as required to solve day to day work issues.

c. Configure the SAFTEC to support any planned testing.

d. Deliver SAFTEC configuration documentation and continuously update that document to reflect the latest configuration of the SAFTEC. (CDRL A028)

3.9.2 JPALS Mobile Test Vehicle (JMTV)

The JMTV is used for JPALS testing while subjecting the GPS and inertial sensors to motion. Since the JMTV is mobile, it acts as both a stationary ground station, and as a moving ship reference station. The JMTV will be moved, as required to support testing at other test facilities. This will allow testing that cannot be conducted at NAS Patuxent River such as open-air jamming tests. Lab facilities within the JMTV will allow collection, reduction, analysis, and storage of test data. The JMTV will be configured to support sensor testing (GPS, inertial, antennas) and testing of aircraft and ship system integrations. The JMTV is GFP, as noted in Attachment 4 and Attachment 5. The contractor shall:

a. Deliver JMTV configuration documentation and continuously update that documentation to reflect the latest configuration of the JMTV. (CDRL A028)

b. Configure the JMTV to support any planned testing.

c. Execute all mission related maintenance of the JMTV, including any breakdown repair. (CDRL A029)

3.9.3 N-UCAS/UCLASS Mobile Test Platform (UMTP)

The UMTP’s will be used for N-UCAS/UCLASS testing as a surrogate carrier. One UMTP is a modified commercial RV while the second is a commercial truck. The UMTP’s will host the GPS and INS sensor units, prototype ATC equipment, data link, Ship Interface Processor (SIP), NAPIE, and test engineer workstations. The UMTP’s will be moved to support testing at other test facilities. This will allow testing that cannot be conducted at NAS Patuxent River such as open-air jamming tests. The UMTP’s will be configured to support sensor-testing (GPS, inertial, antennas), auto-land testing, and testing of air and ship system integrations. Lab facilities within the UMTP’s will allow collection, reduction, analysis, and storage of test data. UMTP’s are GFP, as noted in Attachment 4 and Attachment 5. The contractor shall:

a. Purchase, install, and integrate the required equipment into the UMTP vehicle, and check out all test equipment and associated software.

b. Deliver UMTP configuration documentation and continuously update that documentation to reflect the latest configuration of the UMTP. (CDRL A028)

c. Configure the UMTP’s to support any planned testing.

d. Execute all mission related maintenance of the UMTP’s, including any breakdown repair. (CDRL A029)

3.10 Prototype Development and Testing

The contractor shall employ rapid prototyping techniques into the system development process where appropriate for quick assessment of proposed system design and implementation capabilities (with a minimum of CMMI LEVEL 2 for both hardware and software processes within the NAPIE Real Time Operating System (RTOS) development environment.)

3.10.1 JPALS SD&D/Demonstration Phase

The contractor shall derive from the pre-existing Demonstration Systems Requirements Document (DSRD), detailed hardware requirements for both ruggedized and non-ruggedized NAPIE units. Any unit shall be capable of hosting either the ship or aircraft software. The design of the units shall maximize the ease with which a given unit can be reconfigured for integration into either a ship or aircraft platform. Prototyping of JPALS equipment during TD phase was accomplished via the fabrication of NAPIE units. NAPIE is a set of platform integration tools designed to facilitate rapid prototyping of new concepts into aircraft and ship platforms. In generic form, the NAPIE consists of a commercial-off-the-shelf computer, a data recorder, interfaces to the relevant systems on the host platform systems, and interfaces to required sensors such as GPS, inertial sensors, and data link systems. Any and all prototype algorithms will be implemented in the NAPIE software load. The contractor shall provide the facilities required for fabrication of the NAPIE hardware components. NAPIE units will be used to integrate post-TD phase JPALS components into aircraft platforms and into shore-based test facilities. These components and the integration design shall be provided by the contractor. Non-production system prototyping for NAPIE is accomplished using VxWorks Tornado, version 2.2 and applicable upgrades and Polytron Version Control Software (PVCS) (or equivalent). These tools, and the facilities in which they reside, are Government assets. The contractor shall be given access to these assets. See Paragraph 6.4 for a list of major items received by the contractor. The contractor shall:

a. Install JPALS equipment into civil aircraft, the SAFTEC, LSTF JPALS extension, and the JMTV. Design the installations and provide the system components.

b. Support the JPALS integration activities by configuring existing NAPIE units, performing NAPIE system prototyping, and providing expertise to other Government entities as well as various DoD contractors gained during the TD phase integrations.

c. Provide software development support to the lab and installed testing of the platform integrations.

d. Provide subject matter experts in the areas of GPS, inertial sensors, and data links.

e. Design integrations of JPALS prototype equipment. Integrations may be required in aircraft platforms, ship platforms, the SAFTEC, LSTF JPALS extension, and JMTV. The design shall include the NAPIE units, NAPIE software, required interfaces to the host platform and all required hardware including sensors, data recorders, racks, wiring, and connectors. The Contactor shall prepare and deliver integration design documentation for both the initial design and for the as-built configuration. (CDRL A030)

f. Prepare and deliver a Test and Evaluation Requirements Analysis that identifies the test activities required to verify attainment of all software and hardware functional requirements for each integration effort. This analysis shall include all levels of testing including, human-based software testing (walkthroughs, formal inspections, review), computer based software testing, integration (hot bench), testing in the System Integration Lab (SIL), and testing within the host platform. (CDRL A024)

g. Investigate and recommend, as directed, NAPIE lab technology upgrades.

3.10.2 N-UCAS/UCLASS / WFN /AAR Support

Prototyping of N-UCAS/UCLASS/AAR PGPS equipment is also accomplished via the fabrication of NAPIE units. The contractor shall provide facilities required for fabrication of the NAPIE hardware components. NAPIE units will be used to integrate required components into aircraft platforms and into shore or ship-based test facilities. The contractor shall:

a. Act as an interface for the PGPS system to the N-UCAS/UCLASS/AAR government lead.

b. Act as the lead engineering activity and have primary responsibility for program documentation to include: Integrated Master Schedule, System Requirements Specification, System Specification, Software Description Document, Software Development Plan, Interface Control Documents, Test Plans/Test Procedures and Engineering Documents. (CDRL A031, CDRL A032, CDRL A033, CDRL A034, CDRL A035, CDRL A036, CDRL A026)

c. Coordinate with the Government and other contractors on system design.

d. Provide adept RDT&E software code to integrate elements developed by the Government or other contractor support.

e. Provide RDT&E labor to support the system after delivery; including platform integration, troubleshooting, and system operation during testing and evaluation.

f. Provide technical support that includes procurement, manufacture and configuration management services required to produce the PGPS systems, including the organization and coordination of a configuration control board. (CDRL A028)

g. Assemble, pack and re-assemble system equipment and parts as required.

h. Investigate and recommend, as directed, NAPIE lab technology upgrades.

4.0 PROGRESS REPORTS

4.1 Funds Expenditure Report

The contractor shall prepare monthly funds expenditure reports that depict the costs associated with each PBWS paragraph including a breakout of costs for each task order. The contractor shall reconcile monthly vouchers with these cost data and explain any discrepancies. (CDRL A004)

4.2 Time Expenditure Report

The contractor shall prepare monthly time expenditure reports including monthly and year-to date work hours (straight time), hourly rate, and costs expended per individual. These reports may be reviewed by a support contractor for compilation of data and verification purposes. The support contractor will submit a nondisclosure form. (CDRL A037)

4.3 Progress Reports

The contractor shall prepare monthly contractor’s Progress, Status, and Management Reports (CPSMR) describing tasks performed each month. The CPSMR shall cover overall delivery order status, contract deliverables status, and specific status on each effort or task. (CDRL A038)

5.0 NAVY MARINE CORPS INTRANET (NMCI) INSTRUCTION

The contractor is advised that Information Technology (IT) services shall be ordered from the Navy Marine Corps Intranet (NMCI) contract in accordance with the provisions of 5252.237-9503. The contractor shall order NMCI seats and services and provide a copy of purchase order, itemized by name, seat type, and locations to the NAVAIR NMCI Customer Technical Representative (CTR) via the local 4.5 NMCI POC. Where applicable, application tool suites under this effort shall be modernized and developed in accordance with the Navy Enterprise Application Developer’s Guide (NEADG), which includes Functional Area Manager (FAM), NMCI and Task Force Web requirements. Any tools developed that will be hosted by NMCI or run on NMCI workstations will need to be certified for NMCI and comply with NMCI and Navy policy. Servers and/or applications supporting this effort may also be transitioned in accordance with the NAVAIR Server Consolidation plans and policies.”

5.1 Any tools developed that will be hosted by NMCI or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.

5.2 Future development will be performed in accordance with the Navy Enterprise Application Developer's Guide (NEADG), DON/NAVAIR FAM and Task Force Web (TFWeb) mandates. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure as soon as possible. A transition plan will be provided within 60 days. Registration of all Web sites will be completed within 30 days, if not yet completed.

6.0 FACILITIES/PROPERTY

6.1 Government Accessible Facilities

The Government will provide facilities or access to facilities and equipment in which to perform applicable performance work statement requirements. These facilities are located at Patuxent River and St. Inigoes, Maryland. Twenty percent of the work is to be performed at Government facilities.

6.2 Contractor’s Facilities

The contractor’s facility shall consist of engineering and support staff offices, design, implementation, document development and production equipment, and storage spaces as necessary to fulfill the requirements of the applicable task order. The contractor’s facility shall meet the requirements of the DD Form 254 applicable to this contract. It is anticipated 80% percent of the work is to be performed at contractor facilities.

6.3 Government Furnished Property

The contractor shall maintain records of all Government Furnished Property (GFP) and provide a completed DD Form 1662, “DoD Property in the Custody of Contractor”, annually in accordance with DFARS 245.505-14. GFP that will be furnished with the contract is identified in Attachment 5. Access to RDT&E workstations and laptops required for this effort will be provided by the Government. Provide a completed DD Form 1662 for all Government furnished property in the contractor’s custody as of 30 November annually by 31 December in accordance with DFARS 245.505-14.

6.4 Government Furnished Equipment and Facilities

The Government will provide the contractor the Satellite Navigation Facility and Technical Evaluation Center (SAFTEC), JPALS Mobile Test Vehicle (JMTV), and N-UCAS/UCLASS Mobile Test Platforms (UMTP) as necessary to fulfill the requirements of the applicable task orders.

7.0 MATERIAL

It will be necessary for the contractor to have a material funding allocation (CLIN) to immediately respond to system development requirements, system failures, and system operation requirements. All incidental material purchases will be approved per the H-2 Clause, Restriction on the Direct Charging of Material.

8.0 TRAVEL

The contractor may be required to travel to provide a range of site support services, including but not limited to attending meetings/conferences, training, installation, integration, maintenance or system tests to support field experiments and tests and evaluation in support of the JPALS and NUCAS/UCLASS programs. The contractor shall provide personnel with passports and that can respond to travel requirements within 24 hours notice. The number of trips to each destination will vary by task order as program requirements dictate. Contractor personnel shall submit travel requests to the COR for all travel authorizations. Travel requests are to include project supported breakdown of travel costs (i.e. airfare, per diem, rental car). Contractor personnel shall submit complete trip reports documenting the purpose of the trip, persons contacted, commitments, accomplishments, outstanding problems and recommendations within 10 working days after trip completion. (CDRL A039, CDRL A040)

The contractor may, on occasion, be required to provide transportation to Government members of the TDY team when it is deemed most economical to the Government and is otherwise in the Government’s best interest, and the cost for such transportation will be reimbursed in accordance with the CLINS included in this contract.

9.0 OPERATIONS SECURITY (OPSEC)

The contractor is required to provide OPSEC protection for all classified information and sensitive information, pursuant to the National Security Decision Directive 298 of 22 January 1988. The current editions of DoD Manual 5200.1-R Information Security Program Regulation, Chapter IX and OPNAVINST 3432.1 Operations Security, shall be used as guidance. In order to meet this requirement, the contractor shall develop, implement and maintain a facility level OPSEC program in accordance with to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract. The contractor's OPSEC program shall be described in a facility level OPSEC planning document. The contractor shall submit the document to the Government for approval. The contractor is responsible for subcontractor implementation of the OPSEC program requirement for this contract. (CDRL A041) The work to be performed will involve access to handling of classified material up to and including Top Secret SSBI.

10. INFORMATION TECHNOLOGY

10.1 Clinger-Cohen Act:

In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain and dispose of information technology. In accordance with the following Department of Defense Directive (DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo, and Secretary of the Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance (IA) strategy depends on the Acquisition Category (ACAT).

a. DoDD Number 5000.01 “The Defense Acquisition System,” May 12, 2003, Certified Current as of November 20, 2007

b. DoDI 5000.02, “Operation of the Defense Acquisition System,” December 8, 2008

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” Mar 8 2002

d. SECNAVINST 5000.2D, “Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System,” October 16, 2008

10.2 System Software / Application Compliance:

"All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), Department of the Navy (DON)/Naval Air Systems Command (NAVAIR) Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates."

10.3 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services:

“All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. OMB Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised http://www.whitehouse.gov/omb/circulars_a130_a130trans4

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf

c. Section 508, Rehabilitation Act of 1973 http://www.section508.gov/

d. Department of Defense Web Policies and Guidelines http://www.defense.gov/webmasters

e. Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team Website https://www.nioc-norfolk.navy.mil/wra/index.html

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B http://www.doncio.navy.mil/PolicyView.aspx?ID=421

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines https://mynavair.navair.navy.mil/portal/server.pt/community/dcio_applications_integration___business_intelligence_%287_2_2%29/1491/web_enablement/57583

h. DISA Hosting of All Navy Websites (NAVADMIN 061/08)http://www.npc.navy.mil/NR/rdonlyres/A4E463D0-02AF-4094-A054-BB1D807F631B/0/NAV08061.txt

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07 http://www.npc.navy.mil/NR/rdonlyres/787908B8-55E8-4A6F-9BD8-A74B3C0824F0/0/NAV07145.txt

j. DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators http://www.doncio.navy.mil/PolicyView.aspx?ID=577

10.4 Software Development/Server Procurement:

“Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.”

10.5 Information Assurance (IA):

NAVAIR’s Information Assurance (IA) Program is a unified approach to protect unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. IA is required operationally throughout the DON. The DON CIO is responsible for IT within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the Federal Information Security Management Act of 2002.

“All IA shall be in compliance with the following listed instructions to include those referenced within the below listing:

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems, July 31, 2009

b. (Chairman of the Joint Chiefs of Staff Instruction) CJCSI 3170.01G (series), “Joint Capabilities Integration and Development System”, 1 March 2009

c. CJCSI 6211.02C (series) – “Defense Information System Network (DISN): Policy and Responsibilities,” 9 July 2008

d. CJCSI 6212.01E (series) – “Interoperability and Supportability of Information Technology and National Security Systems,”15 December 2008

e. CJCSI 6250.01C (series) – “Satellite Communications,” 30 April 2007

f. CJCSI 6510.01E, “Information Assurance (IA) and Computer Network Defense (CND),” 15 August 2007

g. (Chairman of the Joint Chiefs of Staff Manual) CJCSM 6510.01A – “Information Assurance (IA) and Computer Network Defense (CND) Volume I (Incident Handling Program”, 24 June 2009

h. [Chief of Naval Operations/Headquarters, United States Marine Corps] CNO N614/HQMC C4 – “Navy-Marine Corps Unclassified Trusted Network Protection (UTN-Protect) Policy, Version 1.0,” 31 October 2002

i. Defense Acquisition Guidebook – Chapter 7 “Acquiring Information Technology, Including National Security Systems,”; Section 7.5 “Information Assurance (IA)”

j. DoD 5220.22-M, “National Industrial Security Program Operating Manual,” February 28, 2006 (NISPOM)

k. DoD 8570.01-M, “Information Assurance Workforce Improvement Program”, 19 Dec 2005 (Incorporating Change 2, Feb 25, 2010)

l. DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” February 10, 2009

m. DoDD 8100.02, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April 2007

n. DoDD 8500.01E (series), “Information Assurance (IA),” October 24, 2002, Certified Current as of April 23, 2007

o. DoDD 8570.01 “Information Assurance Training, Certification, and Workforce Management,” August 15, 2004, Certified Current as of April 23, 2007

p. DoDI 4630.8, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS),” June 30, 2004

q. DoDI 8500.2, “Information Assurance Implementation,” February 6, 2003

r. DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process (DIACAP),” November 28, 2007

s. DoDI 8520.2, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling, April 1, 2004

t. DoDI 8551.1, “Ports, Protocols, and Services Management (PPSM),” August 13, 2004

u. DoDI 8580.1, “Information Assurance in the Defense Acquisition System,” July 9, 2004

v. DoDI 8581.01, “Information Assurance (IA) Policy for Space Systems Used by the Department of Defense,” June 8, 2010

w. DON CIO Memo 02-10, “Department of the Navy Chief Information Officer Memorandum 02-10 Information Assurance Policy Update for Platform Information Technology,” 26 April 2010

x. DON ltr 5239 NAVAIR 726/2322 of 18 Feb 09, “NAVAIR Data at Rest Policy”

y. Federal Information Processing Standards Publications (FIPS PUB) [http://www.itl.nist.gov/fipspubs/by-num.htm]

z. (National Security Telecommunications and Information Systems Security Policy) NSTISSP No. 11, “Revised Fact Sheet National Information Assurance Acquisition Policy,” July 2003

aa. (Office of the Chief of Naval Operations) OPNAV INST 5239.1C, “Navy Information Assurance (IA) Program,” 20 Aug 08

ab. SECNAV M-5239.1, “Department of the Navy Information Assurance Program; Information Assurance Manual,” November 2005

ac. SECNAVINST 5230.15, “Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software,” 10 April 2009

ad. SECNAVINST 5239.3B, “Department of the Navy Information Assurance Policy,” June 17, 2009

ae. SECNAVINST 5239.19, “Department of the Navy Computer Network Incident Response and Reporting Requirements,” 18 March 2008

af. The National Security Act of 1947

ag. Title 40/Clinger-Cohen Act

For more information on determining the applicability of these documents to the specific requirements of your program, contact your local information assurance point of contact for assistance. An IA Manager is available via the NAVAIR portal at https://mynavair.navair.navy.mil/portal/server.pt/gateway/PTARGS_32_0_856_0_-1_47/http;/C27VMWARPAXR274.nadsusea.nads.navy.mil;11930/collab/do/document/overview?projID=135128&documentID=290394 All IT procured on behalf of NAVAIR shall meet all DoD/DON and NAVAIR IA polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These IA policies are standard across the Department and ensure IA compatibility and interoperability.

IT systems and or networks operated by contractors subsequent to a NAVAIR contract, regardless of the level of data processed shall be operated and in accordance with the NISPOM.

Contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet DoDI 8500.2 IA Controls, is subject to validation scanning and must be approved by the NAVAIR site IA Manager prior to connection. The following specific criteria must be met before being connected to any DoD or NAVAIR network in support of this contract. Requirements include:

a.

Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with DoD Contracts. The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection the system to the networks; Results of approvals shall be documented via Memorandum of Agreement with the Facility Security officer and the Defense Security Service Representative for that contractor;

b.

Extent of Validation Scanning. To prevent scanning of “corporate” assets, all such networks, equipment and connections shall be physically segregated from any government/contractor “corporate” networks that are not in direct support of DoD contracts;

c.

Circuit Provisioning. Any circuit or connection between NAVAIR and/or DoD site and the contractor site shall be provisioned via the Defense information Security Agency and comply with CJCSI 6211.02C (series), “Defense Information System Network (DISN): Policy and Responsibilities,” 9 July 2008;

d.

Servicing Systems from a Remote Contractor Site. Remote Access Service connections that allow off-station operation and/or administration of contractor owned systems, located at any NAVAIR facility or site, shall not be permitted, with the exception of those systems connecting to the Command via the Outreach Services identified in Section 7, Enterprise Architecture;

e.

Memorandum of Agreement and Inter-connection Agreements. An Information Assurance Memorandum of Agreement (MOA) between the contractor owning the equipment and AIR-7.2.6 shall be developed and signed before the equipment can be connected to NAVAIR networks. Failure to comply with the signed MOA shall be grounds for disconnection from the network.

10.6 NMCI: Reserved

10.7 Enterprise Architecture:

a. Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.

b. Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.

c. Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

d. IT Approval. The contractor shall not purchase any IT equipment on behalf of NAVAIR in support of a contract without a NAVAIR CIO signed IT approval.

10.8 Software Process Improvement Initiative (SPII):

The SPII Policy requires that standardized contract language be included in solicitations or contracts under which contractor(s) are required to perform “software development”.

As defined in the Assistant Secretary of the Navy (ASN) Memorandum, Software Process Improvement Initiative (SPII) Guidance for Use of Software Process Improvement Contract Language dated 13 July 2007, ““Computer Software development” or “software development” means, as applicable developing or delivering new source code, modifying existing source code, coding computer instructions and data definitions, building databases schema, and performing other activities needed to implement the design of a noncommercial computer software product. This definition recognized that even small changes to software code can result in significant changes to software system behavior and quality, and, consequently, that it is necessary for developers to define and follow disciplined and appropriate processes.”

Mandatory elements of the SPII policy language are:

a. The requirement that Offerors submit a proposed Software Development Plan (SDP) with their proposals, and, during contract performance, deliver a completed SDP (based on the proposed SDP) as a Contract Data Requirements List (CDRL) deliverable, subject to Government review and approval.

b. The information content of the SDPs, which shall follow the framework of Institute of Electrical & Electronics Engineers (IEEE)/Electronics Industries Association (EIA) IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness.

c. The requirement that the SDP serve during contract performance as the benchmark for the contractor’s software development effort.

d. The requirement that the SDP shall be periodically evaluated and updated, as a part of continuous process improvement subject to Government review and approval.

Discretionary elements of the SPII policy language are:

a. Where the language is incorporated in the solicitation and contract.

b. The format of the SDP (including whether it needs to be a single volume or may consist of multiple volumes.)

c. The other elements of IEE/EIA Std 12207 that must be included, as based on the needs of the system to be acquired and its associated work content.

The policy and additional information can be found at http://acquisition.navy.mil/content/view/full/5144

12. IT APPROVAL

The contractor shall not purchase any IT equipment on behalf of NAVAIR in support of a contract without a NAVAIR CIO signed IT approval.

13. WORK SCHEDULE

The contractor shall provide the required services and staffing coverage during normal working hours (NWHs). NWHs are usually 8.5 hours (including a 30-minute lunch break), from 0730-1600 each Monday through Friday (except on the legal holidays specified elsewhere). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800 Monday - Friday. Services and staffing shall be provided for each office at least 8 hours per day (during the 8.5 hour workday which includes the 30-minute lunch break).

Government Employees are allowed to voluntarily work a "Compressed Work Schedule" (CWS). CWS is an alternative work schedule to the traditional five 8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule an employee completes the following schedule within a two-week period of time: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.

The contractor awarded this contract, with agreement by COR, may allow its employees to work a CWS schedule. Any contractor that chooses to allow its employees to work a CWS schedule in support of this contract, agrees that any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the government. Furthermore, all contractors shall comply with the requirements of the Fair Labor Standards Act and particularly with Section 7 regarding compensatory overtime. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government facility.