Deployed_Mission_Support_SOW_and_Labor_Cats.doc

Deployed Mission Support 1.0.

INTRODUCTION. The Naval Air Warfare Center Aircraft Division (NAWCAD) Special Communications Mission Solutions (SCMS) Division, located at St. Inigoes, MD, integrates, delivers, and sustains products for Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems. SCMS has technical authority over a number of C5ISR capabilities, including operation and maintenance support Outside Continental United States (OCONUS) to forward deployed mission support fielded systems. These forward deployed mission locations include Central Command (CENTCOM) and Africa Command (AFRICOM) Areas of Responsibility (AOR). . These essential OCONUS deployed mission support systems are funded by a broad range of customers including Navy and other DOD and non-DOD agencies. To complete these systems, the SCMS Division maintains subject matter expertise in a broad range of technical and programmatic disciplines. The designated Government Project Lead (GPL) will be responsible for all Project Management and Systems Engineering aspects of the project and selects and leads the Integrated Project Team (IPT) for project completion. The GPL will utilize this contract to obtain the OCONUS deployed mission specific technical expertise and deliverables needed to complete each assigned project.

1.1 Scope. The contractor shall provide operations and maintenance support for forward deployed mission OCONUS fielded C5ISR systems supporting OCONUS military units and operations. These services include legacy and current deployed mission C5ISR systems and the rapid inspection, troubleshooting, verification, scheduled and non-scheduled maintenance and modification, integrated logistics support, configuration management, and training of those systems, subsystems, and components. The operations and maintenance support services apply to all phases of the OCONUS systems life cycles. The nature of the work requires pre-deployment training, certifications and qualifications to rapidly support forward mission deployed forces, and the ability to rotate personnel in and out of OCONUS locations every 6 months. Unique OCONUS deployed mission includes:

a.

Force XXI Battle Command, Brigrade-and-Below (FBCB2) Situational Awareness (SA) Capability.

b.

Real-time position, time, elevation, and heading determination using the Global Positioning System (GPS).

c.

Secure and unencrypted multi-band VHF/UHF inter/intra-team communications.

d.

Secure UHF satellite communications.

e.

Internal voice communications between all crew and external radio nets.

f.

Electronic Countermeasures System (ECMS) to protect against Improvised Explosive Device (IED).

g.

A Visual Augmentation System (VAS) to enable operations any time day or night in reduced visibility conditions either because a weather or manmade visual obscurants.

h.

Ability to receive, display, record, and relay real-time full motion video and sensor data transmitted by unmanned aerial vehicles (UAVs).

i.

Antenna system capable of supporting all installed C5ISR subsystem equipment.

2.0 APPLICABLE DOCUMENTS. The following documents and document sources are provided for reference. Requirements for SCMS Division products to have interoperability among military, civilian, U.S., and foreign users may dictate an adherence to a wide variety of specifications and standards. DoD systems shall adhere to the Joint Technical Architecture (JTA) Standards (Current Version). Non-DoD systems may be governed by numerous commercial, national or international standards. The standard development organizations listed are not all inclusive and are presented only as representative sources of the technological interface details which may be required by systems developed with this contract. Unless otherwise noted, the revision level and date for each document, specification, or standard cited shall be that listed in the Department of Defense Assist Database (http://assistdocs.com/search) in effect on the date of contract award or at the time an option is exercised.

Standards, Specifications, Instructions, and Developmental Organizations:

American National Standards Institute (ANSI)

American Society of Mechanical Engineering (ASME) Standards

Association of Public-Safety Communications Officials (APCO) – International – Standards Clinger Cohen Act

Department of Defense and/or Military, e.g. DoD-STD and MIL-STD Series

Electronic Industries Association (EIA), e.g. Recommended Standards RS Series

European Telecommunications Standards Institute (ETSI)

Federal, e.g. FED-STD, FIP Series

Federal Communications Commission

Federal Motor Vehicle and Carrier Safety Standard and Regulations

Institute of Electrical and Electronic Engineers (IEEE)

International Standards Organization (ISO)

International Telecommunications Satellite Organization (INTELSAT)

International Telecommunications Union (ITU), formerly the CCITT

Joint Technical Architecture (JTA) Current Version

National Industrial Security Program Operating Manual

National Institute of Standards and Technology National Television Standards Committee (NTSC)

Society of Automotive Engineers, Inc. (SAE) Handbook

Telecommunications Industry Association (TIA)

Instructions and Directives:

DoD-Directive, 5000 Series

MIL-DTL-31000B

TDP Option Selection Worksheet Product Drawings and Associated Lists

MIL-HDBK 502

Department of Defense Handbook

Acquisition Logistics

MIL-STD-882E

Department of Defense Standard Practice for

Systems Safety

NAVSEA S9095-AD-TRQ-010/TSTP

Total Ship Test Program Manual

NASPAXRIVERINST 5100.35C

Occupational Safety and Health Program

NAWCINST 3432.1

NAWC Operations Security Plan

OPNAVINST 3432.1

Operational Security

SECNAVINST 5000.2E

Implementation of Defense Acquisition Management Policies, Procedures, Documentation, and Reports

USSOCOM 70-1

Acquisition Management System Policy DOD Directive 8500.01E

Information Assurance 3.0 TECHNICAL REQUIREMENTS. The contractor shall provide operations and maintenance support services and incidental supplies to SCMS Division in the performance of studies and application of leading edge technologies for logistical maintenance and sustainment support of OCONUS deployed missions. The contractor shall report results of surveys, analysis and associated technical data in accordance with Exhibit A. Services shall require performance at the contractor’s facilities, Government facilities, and other locations as designated by the Government in the resulting task orders.

3.1 Inspection, Troubleshooting and Verification & Scheduled and Non-Scheduled Maintenance and Modification (CLINs 0110, 0120, and 0130). The contractor shall provide support services for readiness assessment, investigation, and in-service C5ISR discrepancies of forward deployed fielded C5ISR systems. This includes associated technical data of inspection, troubleshooting, and verification of the fielded C5ISR systems as designated per individual task orders (CDRLs A001-A009). The results shall than be documented on maintenance forms in the Government Maintenance Action Reporting Tool as well as, the current required theater maintenance forms, and collection system that may include Standard Army Maintenance System Enhanced (SAMS-E). The contractor shall provide maintenance and modification support services for fielded OCONUS deployed mission SCMS systems. The contractor shall:

3.1.1 Provide technical services to perform system level maintenance activities.

3.1.2 Document and report all maintenance activities, repair part utilization and status, which includes reliability and maintenance (RAM) data, and historical information for review and analysis.

3.1.3 Provide quick-reaction/quick-response support for troubleshooting system technical problems and maintenance support for identified C5ISR system technical problems.

3.1.4 Facilitate the removal and replacement system level maintenance of discrepant items, as well as implement approved modifications through Engineering Change Requests (ECRs), craft alterations, or Engineering Change Proposals (ECPs).

3.1.5 Analyze maintenance data to identify, report, and track significant maintenance trends.

3.1.6 Inspect failed parts, troubleshoot equipment and analyze C5ISR system casualties or deficiencies, and provide recommendations for resolution and on-site repairs. Provide adaptive engineering or modifications to the systems and electronic equipment as quick reaction responses to meet urgent operational requirements and cultivate long-term solutions.

3.1.7 Perform verification on receipt of equipment received and check functionality on equipment and materials.

3.1.8 Analyze C5ISR system performance to identify, report, and track significant trends. Develop design and logistic support changes to correct validated deficiencies.

3.1.9 Provide prototype modification for validation and verification of performance. Document and report results.

3.1.10 Conduct operational assessment inspection at proposed sites.

3.1.11 Analyze system operational readiness, maintenance data, and evaluate new technology to determine if design revisions or incorporation of new technology will cost-effectively enhance readiness.

3.2 Integrated Logistics Support (CLINs 0210, 0220, and 0230). The contractor shall provide integrated logistics support (ILS) planning for OCONUS deployed mission support for, but not limited to, fielded and modified C5ISR OCONUS systems. Required plans and associated reports resulting from analyses shall be provided per CDRLs A003 – A006. The contractor shall:

3.2.1 Support development of tailored supportability strategies, define maintenance planning concepts, and conduct supportability analyses, while ensuring that C5ISR system design and logistics efforts are integrated.

3.2.2 Perform trends, Reliability and Maintainability (R&M), risk management, and support configuration management practices and policies.

3.3.3 Provide "follow-through" support to evaluate C5ISR system performance and reliability, maintainability, and availability data to assist in the development of enhanced or modified performance baselines.

3.3 Configuration Management, Technical Documentation & Training (CLINs 0310, 0320, and 0330). The contractor shall comply with the program Configuration Management Plan (CMP), provided by the government for forward deployed fielded C5ISR systems. These plans prescribe the policies and procedures for identifying and controlling hardware, software, and documentation for each C5ISR system. Related efforts shall include configuration item identification and definition, configuration status accounting, maintenance of physical configuration records and input to configuration reviews and audits. Required technical data shall be provided per CDRLs A005, A007 and A009. The contractor shall:

3.3.1 Identify and report recommended performance improvements for design changes to implement solutions, technical improvements and mandated C5ISR system upgrades.

3.3.2 Verify and validate technical directives, maintenance manuals, installation guides, technical manuals, and related system technical documentation. Document and report identified corrective actions.

3.3.3 Prepare, coordinate, and review ECPs and other documentation for submission of recommended changes to the technical documentation.

3.3.4 Prepare draft ECPs and review for technical accuracy to determine impact as related to the C5ISR systems.

3.3.5 Provide training for any changes to vehicle C5ISR systems, technical manuals, or engineering drawings.

3.3.6 Provide training to end user which includes:

· Troubleshooting

· Maintaining equipment

· Verification of equipment.

3.3.7 Prepare and maintain training plans, and training materials for student and instructor guides.

4.0

REPORTS.

4.1 The contractor shall deliver the Contractor's Progress Status & Management Report in accordance with CDRL A010.

4.2 The contractor shall deliver the Financial Progress Report in accordance with CDRL A011 and Attachment 2, Electronic Transfer of Contractor Expenses and attachment 3, Financial Progress Report Format.

4.3 The contractor shall deliver the Contractor’s Personnel Roster (Workforce Report) in accordance with CDRL A012 and Attachment 4.

4.4 The contractor shall deliver the Task Order Close-Out in accordance with CDRL A013 and Attachment 1.

4.5 Segregation of Cost and Invoice Report (CDRL A014) and Attachment 5.

5. HARDWARE TRACKING SUPPORT.

5.1 The contractor shall provide hardware tracking support to gather data for equipment and hardware requirements in accordance with efforts performed in SOW 3.1-3.3 above (CDRLs A008 – A009 and A015). Required material reports and analyses shall be delivered in accordance with Exhibit A. The contractor shall not accept any products on behalf of the Government. The contractor shall:

5.1.1 Provide tracking and monitoring support for material and supplies required to meet the mission functions for C5ISR systems.

5.1.2 Maintain a current list of on-hand material quantities, as well as material shortages. Document material usage.

5.1.3 Document and report tool shortages and requirements.

5.1.4 Using the Government’s automated system, track acquisition status from initiation to hardware delivery.

6.0

FACILITIES/PROPERTY

6.1 Government Furnished Facilities/Property. The Government will provide furnished housing and work facilities within each OCONUS area of responsibility. Transportation shall be provided in support of the operations and maintenance of the effort. While performing duties in accordance with the terms and conditions of the contract, the applicable safeguarding standards will provide force protection to contractor employees commensurate with that given to Service/Agency civilians in the operations area.

6.1.2 Government Furnished Material. The Government will be required to furnish Gold Kits which include the following: Blue Force Tracker System; KIT MK-3057/V, Switch Box, System Power Supply, Mounting Bracket, Cable Assembly (Power and Spec), Adapter Assembly, Miniature Transmitter, MTX DC-DC Converter, Antennas, Antenna Cables, Antenna Mounts, Antenna Bases, Intercom Loudspeaker and Radio Cables, MTX DC-DC, Antenna Modem, Navigation Set, Harness, Wiring, Backpack Deck, Port Replicator, Transceiver, Receiver/Transmitter, Radio Amplifier, Toggle Switch, Station, Loudspeaker, Radio Interface Terminal, Handsets, Vehicle Adapter/Transceiver Kit, Battery Eliminator, Amplifiers, Ancillary Kit, Remote Control Head, Diplexer, Vehicular Shock Mount, Low Pass Filter, Antenna Coupler, Locking Kit, Rover System and Receiver, ECMS, DC Converter, Remote Control Unit, GPS Antenna, Power Distribution Unit, PDU Equipment Power Cables, DVE Kit, Pelican Transit Case, Dewalt Drill Driver, BLK Oxide Drill Bits.

6.2 Contractor Furnished Facilities/Property. The facility location shall satisfy the daily technical and management operation of the contract located at a primary location for deployed personnel.

6.2.1 Contractor Furnished Material. The contractor will be required to furnish Electronic Tool Boxes, Xcelite TCMB100STW or equivalent and include the following: Portable Solder Iron (Butane); Heat Gun – Small 1000W, 110VAC; Bird 44A Wattmeter w/Elements; Fluke Multimeter; Cordless Compact Drill (with extra battery); Drill Bits (UNIBIT Set); Connector Kit, Coaxial; Tie Strap Gun; 25’ Extension Cord; Worklight; Storage Case for 44A Wattmeter; Foldable Compact Equipment Dolly; Dremel Tool w/attachments; 25’ Tape Measure; and Mini Outlet Reel. The contractor will be required to wear a shirt with collar, long pants, and appropriate footwear while on duty OCONUS, following local command direction.

6.2.2 All property must be tagged as Contractor Furnished Equipment (CFE) assets.

6.2.3 Information Assurance and Personnel Security Requirements. The contractor may be required to access Government IT Systems. Contractor personnel requiring access to Government IT Systems shall comply with NAVAIR Clause 5252.204-9505 (CDRLs A023 and A024).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. DON CIO (Chief Information Officer) 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. “As required, all IA shall be in compliance with the following listed instructions to include those referenced within the below listing:

· SECNAV M-5239.1 DoN Information Assurance Program; Information Assurance Manual

· National Industrial Security Operating Manual (NISPOM)

· CJCSI 6211.02 (series) --Defense Information System Network (DISN): Policy Responsibilities and Processess of 31 July 2003

· CJCSI 6212.01 (series) --Interoperability and Supportability of Information Technology and National Security Systems

· DoDD 8100.1--Global Information Grid (GIG) Overarching Policy

· DoDD 8500.1--Information Assurance

· DoDI 8500.2--Information Assurance Implementation

· DoDI M-8510.1--DoD Information Technology Security Certification and Accreditation Process

(DITSCAP) Application Manual

· DoDI 5200.40, “DoD IT Security Certification and Accreditation (C&A) Process (DITSCAP),” 30 Dec 1997

· CNO N614/HQMC C4--Navy-Marine Corps Unclassified Trusted Network Protection (UTN-Protect) Policy, Version 1.0, 31 October 2002” 6.3 Government or Contractor Furnished Vehicles. Transportation vehicles shall be provided by the Government or Contractor to support and meet delivery and pick up of Government provided equipment and integration materials when scheduled. The Contractor shall request an authorization from the Contracting Officer prior to ordering a vehicle from the Interagency Fleet Management System (IFMS). The transportation vehicles shall not be used to transport Government personnel.

6.3.1 When operating these vehicles, the contractor shall ensure the following:

a.

Possession of a current and valid operator’s license for all vehicles;

b.

Compliance with all state and federal laws pertaining to operating motor vehicles;

c.

Compliance with NAVAIR command policies when operating a vehicle (i.e. no cell phone use, stopping at runway crossing, etc.);

d.

Use the most cost-effective means to fuel vehicles (i.e. fuel farms);

e.

Operation of the vehicles in a safe manner and in accordance with the vehicle/equipment user/operator manual;

f.

Operators shall comply with licensing requirements of country, state, and local Non-Tactical Vehicle (NTV) laws;

g.

That the COR and Contracting Officer are provided evidence of NTV liability insurance covering bodily injury and property damage protecting the Contractor and DoD against third-party claims arising from the ownership, maintenance or use of a NTV IAW FAR 28.307-2(c).

6.3.2 The contractor shall report any known or realized accidents involving the Government owned or leased vehicles to the Government technical point of contact. If the contractor is involved in an accident while operating a Government owned or leased vehicle, they shall notify the Government TPOC, the Contracting Officer, and the COR within 24 hours and shall provide an accident report using Standard Form 91, Motor Vehicle Accident Report, and Form 94, Statement of Witness Report, within 48 hours.

6.3.3 When operating the vehicle, the contractor shall utilize the Government Smart card for fueling, maintenance, and repair services. Contractor use of the Smart Card will be in accordance with the requirements and regulations contained in the GSA Fleet Services Card User Guide (www.gsa.gov/fleetcard). When operating the vehicle, the contractor shall be responsible for any costs associated with violations such as speeding tickets, parking tickets, reckless driving, and any damage caused to the vehicle as a result of vehicle code violations. The contractor shall be responsible for reimbursing the Government for any unauthorized charges made by the contractor, its employees, and subcontractors on the Smart Card.

7.0

QUALITY ASSURANCE.

7.1 Best Commercial Workmanship. The contractor shall utilize ISO 9001-2008. The contractor's quality system shall provide means for inspecting these criteria and assuring compliance.

a.

The contractor is required to maintain and operate a facility wide quality management system that is designed for the products and services to be provided under the contract.

b.

The manufacturing and quality management system will use ANSI/J-STD-001, “Requirements for Soldered Electrical and Assemblies”, IPC-A-610, “Acceptability of Electronic Assemblies”, and IPC-R-700, “Suggested Guidelines for producing electrical and electronic assemblies”.

c.

The quality management system will use the quality requirements as defined in FAR 46.202-4(a) and satisfy ISO 9001:2008 “Quality Systems” – Model for Quality Assurance in Design, Development, Installation and Servicing.

d.

The quality management system documentation and the system’s effectiveness are subject to review by NAWCAD at any time during the period of performance of this Contract.

7.2 The contractor's quality management organization must be clearly defined, and employees providing quality functions must have adequate responsibility, authority, and freedom to identify and evaluate problems and to initiate, recommend, or provide corrective action.

7.3 A periodic review of quality requirements shall be conducted by the contractor to identify the controls, processes, skills, fixtures, tools, and test equipment needed to ensure product quality. The results of this review shall update inspection and testing techniques, instrumentation, and manufacturing methods and processes. Standard program data that may be required by the Government to compile trend studies shall be available as needed. Specific standards and practices shall be provided for individual projects.

8.0 OPSEC PLAN. The Operations Security (OPSEC) plan shall be furnished pursuant to the requirements provided herein. Required information shall be provided in accordance with Exhibit A (CDRL A016).

8.1 The contractor shall provide OPSEC protection for all classified information (as defined by FAR 4.401) and sensitive information (as defined by Section 3 (d) (4) of PL 100-235 (101 Stat 1727)), pursuant to the National Security Decision Directive 298 of 22 January 1998 and DFARs clause 252.239.7016. In order to meet this requirement, the contractor shall develop, implement, and maintain a facility level OPSEC program (CDRL A016) in accordance with Exhibit A to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract.

8.2 The contractor shall be responsible for subcontractor implementation of the OPSEC program requirements for this contract. The OPSEC plan shall be developed in accordance with the requirements set forth in NAWCINST 3432.1 and OPNAVINST 3432.1, and submitted to NAWCAD SCMS Division Patuxent River, St. Inigoes.

9.0 WORK PLACE AND SCHEDULE. The contractor shall provide the required services and staffing coverage during Normal Working Hours (NWHs). NWHs are usually 12 hours a day, seven days a week.

10.0 ESTIMATED MATERIAL. It will be necessary for the contractor to have a material funding process to immediately respond to system development requirements, system failures, and system operational requirements. All incidental material purchases will be approved per the H-1 Clause, Restriction on the Direct Charging of Material.

11.0 TASK CLOSE-OUT. Within 90 days after completing each option year, the contractor shall provide a close-out report. The reports shall include financial data, deliverable status, disposition of Contractor-Furnished Materials, list of Government-furnished materials, and outside services, as a minimum. The close-out report shall then be signed by the contractor program manager and forwarded to NAWCAD, Patuxent River, St. Inigoes, Code 4.11.4.6 the Task Closeout in Attachment (1) provides an example of the required format (CDRL A013).

12.0 INFORMATION TECHNOLOGY (IT) INFORMATION.

The Government will provide all necessary reference documents not generally available to the Contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this Contract, which reports to PBIS-IT, without a Naval Air Systems Command (NAVAIR) Command Information Officer (CIO) approved NAV-IDAS ITPR.

The following paragraphs are for information only:

12.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 National Security Systems (NSS). NSS are defined in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-59. Six factors are used to identify NSS, one of which is IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively and ensure cybersecurity and interoperability. The authority to grant compliance with CCA as a statutory milestone program document resides at either first echelon or second echelon. The level of the Acquisition Category (ACAT) or designation as an Abbreviate Acquisition Program (AAP) determines which echelon has this authority. ACAT III and below acquisition programs CCA compliance assertion confirmation approval authority is delegated to the second echelon Command Information Officers. ACAT I and ACAT II acquisition programs CCA compliance assertion confirmation approval resides at DON CIO (First echelon). Approval of interoperability standards compliance for all acquisition programs resides at DON CIO. Approval of the Cybersecurity Strategy (formerly Acquisition Information Assurance Strategy) is a component of CCA compliance however it is approved separately. Approval authority is divided among the DoD, and DON CIOs as well as the second echelon Command Information Officers. See Table 1 for allocation of approval authorities.

by DON

CIO

Approval by DoD

CIO

X

X

X1

X

X

X

X

III

X

IV

X

AAP

X

1 See Interim DoD 5000.02 Enclosure 11, Section 6.b.(1): For ACAT ID, IAM, and IAC programs, the DoD CIO will review and approve the Cybersecurity Strategy prior to milestone decisions or contract awards.

Table 1: Allocation of Cybersecurity Strategy Approval Authorities

Cybersecurity Strategy approval process begins after the Program Manager signs the Cybersecurity Strategy and puts it forward to the Command Information Officer. The final approved Cybersecurity Strategy is an appendix to the Program Protection Plan (PPP) as well as an element of CCA compliance (Interim DoDI 50000.02, Tables 2 and 9).

a. Interim DoD Instruction 5000.02, “Operation of the Defense Acquisition System”, November 25, 2013

b. OSD Memo, Clinger-Cohen Act Compliance Policy, Mar 8 2002

c. SECNAVINST 5000.2E, Implementation and Operation of the Defense Acquisition

12.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.

12.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. Office of Management and Budget Management of Federal Information Resources, OMB

CIRCULAR NO. A-130 Revised.

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 Amendment to the 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 http:www.public.navy.mil/fcc-c10f/nionorfolk/Pages/AboutWRA.aspx

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B www.navy.mil/navydata/internet/secnav5720-47b.pdf

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines) To request this policy contact the NAVAIR CIO office – 7.2.2 Applications Integration team –Web Manager: Shane Malamphy at 301- 342-1825

h. Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN

061/08) http://www.public.navy.mil/bupersnpc/reference/messages/Documents/NAVADMINS/NAV2008/NAV08061.txt

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07 http://www.public.navy.mil/bupersnpc/reference/messages/Documents/NAVADMINS/NAV2007/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/ContentView.aspx?ID=577

k. Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible Navy

Sites (ALCOM 129/09) http://www.public.navy.mil/fcc‐c10f/niocnorfolk/Documents/NTD‐08‐ 09.txt

12.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.

12.5 Cybersecurity:

NAVAIR’s Cybersecurity 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. Cybersecurity 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 Cybersecurity shall be in compliance with the following listed instructions:

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

b. Chairman of the Joint Chiefs of Staff Instruction CJCSI 3170.01H (series), Joint Capabilities Integration and Development System, 10 January 2012

c. CJCSI 6211.02D Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012

d. CJCSI 6212.01F Net Ready Key Performance Parameter (NR KPP), 21 March 2012

e. CJCSI 6251.01D Narrowband Satellite Communications Requirements, 30 Nov 2012

f. CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND), 09 Feb 2011, certified current 10 Oct 2013

g. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – Incident Handling Program 10 July 2012

h. Chief of Naval Operations/Headquarters, United States Marine Corps CNO N614/HQMC C4 – Navy-Marine Corps Unclassified Trusted Network Protection (UTNProtect) 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 3, 24 Jan 2012)

l. DoDD 8000.01 Management of the Department of Defense Information Enterprise, 10 February 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 8570.01 Information Assurance Training, Certification, and Workforce Management, 15 August 2004, Certified Current as of 23 April 2007

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

p. DoDI 8500.1, Cybersecurity, 14 March 2014

q. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014

r. DoDI 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 01 April 2004

s. DoDI 8551.1, Ports, Protocols, and Services Management (PPSM), 13 August 2004

t. DoDI 8580.1, Information Assurance in the Defense Acquisition System, 9 July 2004

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

v. 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

w. DON letter 5239 NAVAIR 726/2322 of 18 Feb 09, NAVAIR Data at Rest Policy

x. Federal Information Processing Standards Publications (FIPS PUB) http://www.nist.gov/itl/fips.cfm

y. National Security Telecommunications and Information Systems Security Policy NSTISSP No. 11, Revised Fact Sheet National Information Assurance Acquisition Policy, July 2003.

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

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

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

cc. SECNAVINST 5239.3B, Department of the Navy Information Assurance Policy, 17 June 2009

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

ee. The National Security Act of 1947

ff. Title 40/Clinger-Cohen Act

gg. Title 44/ Federal Information Security Management Act

All IT procured on behalf of this contract 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 pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated 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 Cybersecurity 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 the contractor may be connected to any DoD or NAVAIR network in support of this contract. Requirements include:

1. 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;

2. 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;

3. 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;

4. 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;

5. 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.

12.6 Enterprise Architecture:

6. 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.

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

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.

13.0 Personnel Qualifications Requirements

13.1. The contractor shall be responsible for employing personnel having the following levels of education, professional, and technical experience. These qualifications are only a baseline; contractors should strive for technical excellence in personnel by demonstrating experience and qualifications beyond these qualifications.

13.2. The specialized experience included as part of the required qualifications shall have been obtained in the field of endeavor indicated by the applicable labor categories listed below. The experience indicated in the following labor categories must have been performed during the past five years. In cases requiring experience of more than five years, at least five years of the total experience must be within the past five year period. Key personnel are those who will be performing in Key Labor Categories listed below (the number of resumes required per key labor category are shown in brackets).

13.3. One person proposed for each of the labor categories annotated with an (*) below shall be capable of obtaining a Top Secret clearance within 60 days of task order award. All labor categories, except the Financial Analyst will require a Secret clearance. In addition to these categories, Secret and Top Secret clearances may be required for other labor categories depending on actual tasking throughout the duration of the contract. Proof of U.S. citizenship is required to be permitted access to government installations, aircraft, and ships.

Note: All required experience for all labor categories may have been obtained concurrently. All degrees shall be obtained from an accredited college or university.

KEY LABOR CATEGORIES

*Program Analyst *Engineering/Electronics Technician, Senior [2]

NON-KEY LABOR CATEGORIES

*Electronics Technician, Maintenance, Senior *Electronics Technician, Maintenance Junior *Electronics Technician, Maintenance Journey Level *Engineering/Electronics Technician, Junior

*Systems Analyst, Journey Level

Financial Analyst

DEFINITIONS

As used in the minimum personnel qualification descriptions for this contract, the terms indicated shall be defined or their meaning qualified as follows:

academic year - a full or complete year of study at a junior college, college, university, or other academic institution toward which at least 30 semester hours or 45 quarter hours of undergraduate study, or 18 semester hours or 27 quarter hours of postgraduate study, were completed.

accredited institution - a post-secondary educational institution which was approved by an accrediting agency listed as nationally recognized by the U.S. Department of Education.

accredited program - an educational program or course of study offered by on accredited institution.

degree - an academic title conferred by an educational institution upon completion of a unified course of study; if not otherwise qualified, the term shall mean a degree at the bachelor's, master's, or doctoral levels only.

engineering or engineering discipline - when used in relation to educational or work experience requirements, “engineering” shall mean any of the following specific subjects, disciplines, or areas of work experience only: aerospace, civil, computer, electrical, electronics, industrial, mechanical, or nuclear engineering.

experience and years of experience –

a) When used in relation to requirements for past participation in professional work or employment activities, "experience" shall mean full-time (on the basis of a standard forty hour work week) participation, at least one-half of which time was spent performing qualifying functions as practitioner or employee.

b) When used in relation to requirements for a particular term or period of participation, "years of experience" shall mean full, productive years of participation. Productive years are work years of fifty-two weeks reduced by reasonable amounts of time for holiday, annual, and sick leave. If participation was part-time, or if less than one-half of the standard work week was spent performing qualifying functions, the actual time spent performing qualifying functions may be cumulated to arrive at full years (or years and months) of experience. For example, only the actual number of full days (or full-day equivalents) of duty or drills completed during a year of military reserve participation, or in other qualifying part-time employment or practice may be cumulated toward years of experience. Qualifying part-time experience performed in addition to other full-time qualifying employment during the same period of time may be cumulated on a full-time equivalent basis and added to the fulltime experience to satisfy a total experience requirement.

postgraduate degree - a master's, Ph.D., or other professional degree for which completion of an undergraduate curriculum for receipt of a bachelor's degree was a prerequisite.

related field - a “field of study with a similar curriculum of study but is referenced by a different name”.

13.4 Security Clearance Requirements. Personnel must have, or be able to obtain the appropriate security clearance as stated on the DD Form 254. One person proposed for each of the labor categories below shall be capable of obtaining a Top Secret clearance within 60 days of award of task order. In addition to these categories, Secret and Top Secret clearances may be required for other labor categories depending on actual tasking throughout the duration of the contract. Proof of U.S. citizenship is required to be permitted access to government installations, aircraft, and ships.

*Interim clearances are acceptable.

Note: The contractor shall apply the above levels of security clearance requirements to their proposed workforce in support of the SOW as applicable.

14.0 LABOR CATEGORY QUALIFICATIONS:

a. Engineering/Electronics Technician, Senior (KEY). Leads the execution of complex tasks. Applies engineering techniques, principles and precedents to develop, design, modify, install, test, evaluate, or operate electrical, electronic, avionics, mechanical, communications, stores, armament/ordnance, or related data processing systems for military weapon systems or associated support equipment or components. Reviews, analyzes, develops, prepares or applies engineering, technical or maintenance specifications, policies, standards, or procedures. Organizes, analyzes, and prepares reports or presentations of technical data and information. Plans and performs tests and evaluations of systems equipment or components. Compiles, processes, reduces, or analyzes test data results.

Minimum Education: High School diploma or GED; Completion of a technical school, trade school, or advanced armed services technical school curriculum or course of training in electricity, electronics, avionics, mechanics, armaments/ordnance, or engineering technology; or completion of at least 30 semester hours of course studies at an accredited college or university in an engineering, scientific, or technical curriculum.

Minimum Experience: At least ten (10) years of experience in performing engineering technician functions directly involved with electronics.

b. Engineering/Electronics Technician, Junior. Performs tasks under supervision. Applies engineering techniques, principles and precedents to develop, design, modify, install, test, evaluate, or operate electrical, electronic, avionics, mechanical, communications, stores, armament/ordnance, or related data processing systems for military weapon systems or associated support equipment or components. Reviews, analyzes, develops, prepares or applies engineering, technical or maintenance specifications, policies, standards, or procedures. Organizes, analyzes, and prepares reports or presentations of technical data and information. Plans and performs tests and evaluations of systems equipment or components. Compiles, processes, reduces, or analyzes test data results.

Minimum Education: High School diploma or GED; Completion of a technical school, trade school, or advanced armed services technical school curriculum or course of training in electricity, electronics, avionics, mechanics, armaments/ordnance, or engineering technology; or completion of at least 30 semester hours of course studies at an accredited college or university in an engineering, scientific, or technical curriculum.

Minimum Experience: At least one (1) year of experience in performing engineering technician functions directly involved with electronics. ALLOWABLE SUBSTITUTION: Twenty-four (24) credits of post high school classes can be substituted for one (1) year of experience.

c. Electronics Technician, Maintenance, Senior. Applies advanced Communication-Electronics Systems technical knowledge to solve complex problems that typically cannot be solved solely by referencing manufacturers’ manuals or similar documents. Examples of such problems include determining the location and density of circuitry, evaluating electromagnetic radiation, isolating malfunctions, and incorporating engineering; changes.