DRAFT SOW TS_SCI EXCOMM.docx
DOCX document 91 KB Posted
- Solicitation number
- N00421-21-D-0018NegotiatedMod
About this file
This document is a draft statement of work for exterior communications engineering and installation services. The Naval Air Warfare Center Aircraft Division Webster Outlying Field Integrated C2 and Intel Division requires research, design, verification, validation, engineering, equipment installation, and logistics support for command, control, communications, computers, intelligence, surveillance, and reconnaissance systems. Services include engineering and equipment installation from concept through deployment of command, control, communications, computers, and intelligence systems for shipboard, shore, airborne, and transportable platforms. Products and services must meet requirements for top secret/sensitive compartmented information facilities used by various Department of Defense and intelligence community agencies. Key support areas involve satellite communications, high frequency radio, tactical communications, digital networking, encryption, and broadcast engineering. The statement of work outlines requirements for research and development, verification and validation, system engineering, assimilation, installation, integrated product support, material procurement and control, technical and project management, and personnel qualifications.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| TS_SCI DRAFT LOE Hours EXCOMM.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Section C - Descriptions and Specifications
STATEMENT OF WORK – EXTERIOR COMMUNICATIONS (EXCOMM)
1.0 Scope.
The Naval Air Warfare Center Aircraft Division (NAWCAD) Webster Outlying Field (WOLF) Integrated C2 and Intel (IC2&I) Division integrates and delivers products for Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems. As the organic Lead Systems Integrator (oLSI), IC2&I Division provides non-repetitive, rapid response solutions to close critical communication capability gaps for the U.S. Military, National Agencies, and other Government Program Offices. This Statement of Work (SOW) scope includes engineering and equipment installation services from concept through deployment of Command, Control, Communications, Computers, Intelligence (C4I) systems including legacy, current, and next generation shipboard interior and Exterior Communications (EXCOMM); shipboard radios; and transportable, airborne, and fixed shore termination communications systems, subsystems, and components. The systems designed by the IC2&IS Division may be used by various Department of Defense and Intelligence Community Agency Sensitive Compartmented Information Facilities (SCIFs), both on ships and shore facilities in support of TS/SCI networks run by various DoD organizations and used across the DoD, Department of State, Department of Homeland Security and Department of Justice to transmit especially sensitive classified information.
The following are representative of the programs, systems, and technology areas to which the requested engineering and technical services may be applied: Satellite Communications (SATCOM) including Military Ultra High Frequency (UHF), Super High Frequency (SHF), Extremely High Frequency (EHF), Global Broadcast System (GBS), Global Positioning System (GPS), and tri-ban and Commercial Inmarsat, Iridium, Ku, C, Ka, Low Earth Orbit (LEO), and Very Small Aperture Terminal (VSAT); High Frequency (HF) radio communications/ technologies to include Automatic Link Establishment (ALE), Near Vertical Incidence Skywave (NVIS), and Internet Protocol (IP) over HF; short haul tactical communications to include UHF, Very High Frequency (VHF), Line of Sight (LOS), HAVEQUICK, Single Channel Ground and Airborne Radio System (SINCGARS), and Microwave; digital networking technologies to include Personal Area Network (PAN), Local Area Network (LAN), Wide Area Network (WAN), and Metropolitan Area Network (MAN) of various topologies connected via copper, fiber optics, or wireless connections; networking protocols, Asynchronous Transfer Mode (ATM), frame relay, Integrated Services Digital Network (ISDN), Digital Subscriber Line (DSL), Synchronous Optical Network (SONET), Transmission Control Protocol/Internet Protocol (TCP/IP), Multiprotocol Label Switching (MPLS), Voice Over IP (VOIP), quality of service, and latency; encryption, database, Information Technology (IT) security, and cybersecurity technologies to include integration and installation of current Type 1 approved cryptographic devices into electronic systems and the design and configuration of multi-level/multi-domain security systems; analog and digital broadcast engineering to include radio, television, and Audio/Video (AV) equipment; Video Teleconferencing (VTC) to include fixed, mobile, and portable; electrical power generation and distribution technology; computer-aided dispatch solutions; integrated backbone systems; blue force tracking and other global positioning technologies; and tactical and commercial telephony.
2.0 Applicable Documents.
The following documents and document sources are provided for reference. IC2&I Division requirements to provide C4I interoperability among military, civilian, U.S., and foreign users may dictate an adherence to a wide variety of specifications and standards. Department of Defense (DoD) systems shall adhere to the Joint Technical Architecture (JTA) 2.0 Standards. Non-DoD systems may be governed by numerous commercial, national, or international standards. The documents listed below are presented only as representative sources of the technological interface details that may be required during contract performance. Likewise, the documentation listed is not all-inclusive but is representative of the types of information that may be necessary to perform the work. Each Task Order (TO) will provide additional details if necessary. The document version applicable to tasking will be the most current published document at the time of TO award.
2.1 DoD standards.
2.1.1 MIL-STD-461F Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment.
2.1.2 MIL-STD-464A Electromagnetic Environmental Effects Requirements for Systems.
2.1.3 MIL-STD-882D System Safety.
2.1.4 DoD and/or Military, e.g. DoD-STD and MIL-STD Electronic Series.
2.2 DoD handbooks.
N0042121D0018
N0042121D0018
2.2.1 MIL-HDBK 502 DoD Handbook Acquisition Logistics.
2.2.2 MIL-HDBK-1785 Systems Security Engineering.
2.2.3 MIL-HDBK-237D Electromagnetic Environmental Effects and Spectrum Supportability Guidance for the Acquisition Process.
2.3 DoD instructions.
2.3.1 NASPAXRIVERINST 5100.35 Occupational Safety and Health Program.
2.3.2 SECNAVINST 5000.2 Implementation of Defense Acquisition Management Policies, Procedures, Documentation, and Reports.
2.3.3 OPNAVINST 3432.1 Operational Security Plan.
2.3.4 NAWCINST 3432.1 Naval Air Warfare Center (NAWC) Operations Security Plan.
2.4 Other Government documents.
2.4.1 Clinger-Cohen Act.
2.4.2 DoDI 8510.01 Risk Management Framework (RMF) for DoD IT.
2.4.3 DoD-DIRECTIVE, 5000 Series.
2.4.4 DoD-M 5220.22 National Industrial Security Program Operating Manual (NISPOM).
2.4.5 MIL-PRF-49506 Logistics Management Information.
2.4.6 NACSIM/NACSEM National Communications Security Information Memoranda (NACSIM) and Emanations Memoranda (NACSEM).
2.4.7 NSTISSI ICD 705 Physical Security Standards for Sensitive Compartmented Information Facilities.
2.4.8 Committee on National Security Systems Policy (CNSSP) - National Policy Governing the Acquisition of Information Assurance and Information Assurance (IA)-Enabled Information Technology Products.
2.4.9 National Security Agency (NSA) Information Assurance (IA) Guidance.
2.4.10 Federal, e.g. FED-STD, Fiber Channel over Ethernet (FCoE) Initialization Protocol (FIP) Series Federal Communications Commission.
2.4.11 Federal Motor Vehicle and Carrier Safety Standard and Regulations.
2.4.12 National Security Decision Directive 298, dated 22 January 1998 Public Law 100-235, Section 3(d) (4).
2.4.13 Occupational Safety and Health Administration (OSHA) Regulations.
2.4.14 Video Services Policy - Security Technical Implementation Guide Overview - Developed by the Defense Information Systems Agency (DISA) for DoD.
2.4.15 Defense Federal Acquisition Regulation Supplement (DFARS) Procedures, Guidance, and Information (PGI) 225.371 Contractor personnel supporting U.S. Armed Forces deployed outside the U.S.
2.4.16 U.S. Army Europe (USAREUR) Regulation 600-700 dated 09 January 2018.
2.4.17 North Atlantic Treaty Organization (NATO) Status of Forces Agreement (SOFA).
2.4.18 DoDM 5105.21 (All Volumes) – SCI Administrative Security Manual
2.5 Industry documents and organizations.
2.5.1 American National Standards Institute (ANSI).
2.5.2 American Society of Mechanical Engineering (ASME) Standards.
2.5.3 Association of Public-Safety Communications Officials – International (APCO) – Standards.
2.5.4 Building Industry Consulting Service International (BICSI), A Telecommunications Association https://www.bicsi.org.
2.5.5 Industries Association (EIA), e.g. Recommended Standards RS Series.
2.5.6 European Telecommunications Standards Institute (ETSI).
2.5.7 InfoComm International, an Accredited Standards Developer (ASD), Standard 10:2013.
2.5.8 Institute of Electrical and Electronic Engineers (IEEE).
2.5.9 International Organization for Standardization (ISO).
2.5.10 International Telecommunications Satellite Organization (INTELSAT).
2.5.11 International Telecommunications Union (ITU).
2.5.12 Internet Engineering Task Force (IETF).
2.5.13 JTA, National Institute of Standards and Technology.
2.5.14 National Security Telecommunication and Information System Security (NSTISS).
2.5.15 National Television System Committee (NTSC) Standard.
2.5.16 Society of Automotive Engineers, Inc. (SAE) Handbook.
2.5.17 DISA Technical Implementation Guides (STIGs).
2.5.18 Telecommunications Industry Association (TIA).
2.5.19 Worldwide Aeronautical Radio Commission (WARC) – Standards.
2.5.20 International Traffic and Arms Regulations (ITAR).
3.0 Requirements.
3.1 General requirements.
3.1.1 Compatibility. The Contractor shall maintain the capability to prepare documents compatible with the Government IT environment through the security classification of Top Secret. The current operating environment required for this Contract is identified in the IC2&I Division Research, Development, Test, & Evaluation (RDT&E) LAN Standard Operating Procedures (SOP) for both Contractor site and Government site staff (Attachment 14). The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with IC2&I Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with IC2&I Division during working hours whether at Contractor work site or on travel.
The technical requirements identified in paragraphs 3.1 through 3.9 may require the contractor to not only have access to SCI and U.S. Government SCIFs, but also to use the SCIF’s capability of storing and electronically processing SCI.
The contract deliverables (including but not limited to engineering documents, cyber security vulnerabilities assessments, accreditation packages, and monitoring of deployed systems) will be classified at the SCI level, as defined in paragraphs 3.3.1.1 – 3.3.1.2; 3.3.1.4 – 3.3.1.5; 3.3.1.8; 3.3.3.1 – 3.3.3.5; 3.3.4.2 – 3.3.4.3; 3.3.3.7.1.
3.1.2 Work location and facilities.
3.1.2.1 Work location. Approximately 21% of the work will be performed at Government sites and 79% of the work will be performed at the Contractor’s site(s). Government sites include building 8185, Webster Outlying Field, St. Inigoes, MD and Panzer, Germany. Contractor sites must be near NAS Patuxent River Webster Outlying Field St. Inigoes, MD and United States Army For Bragg Fayetteville, NC as described in paragraph 3.1.2.1.2.
3.1.2.1.1 Government site requirements. Contractors performing at government sites will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.
3.1.2.1.2 Contractor site requirements. The Contractor shall provide its own main support facilities needed to perform the tasking of this Contract within fifty (50) driving miles of NAS Patuxent River Webster Outlying Field St. Inigoes, MD in order to satisfy the daily technical and management operations of this Contract. Additionally, a smaller location for seven (7) FTEs is required within thirty (30) driving miles of United States Army Fort Bragg, Fayetteville, NC. The Government will not assume responsibility to retain the facility or take control of the title after the Contract is completed.
3.1.2.1.2.1 The Contractor’s main facility shall contain assembly, test, and storage space, as well as attendant office space for the support staff considering integration materials will be provided by the Government to the Contractor. The main facility shall be a minimum of 50,000 square feet to include adequate production and storage space. The storage space needs to be environmentally controlled.
3.1.2.1.2.2 The Contractor shall provide all equipment and office/facility furnishings to support the SOW requirements for Contractor site requirements.
3.1.3 Contract Status Reporting. The Contractor shall provide the following documentation.
3.1.3.1 Segregation of Cost and Invoice Requirements Report. The Contractor shall provide deliverables In Accordance With (IAW) the Contracts Data Requirements Lists (CDRLs). (CDRL A001)
3.1.3.2 Financial Progress Report. (CDRL A002)
3.1.3.3 Contractor’s Personnel Roster - Workforce Report. (CDRL A003)
3.1.4 Work schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.
3.1.4.1 Work schedule. The Contractor shall provide the required services and staffing coverage during normal working hours. Normal working hours are usually eight and a half (8.5) hours (including a thirty-minute lunch break), from 0730 to 1600 each Monday through Friday (except on federal holidays specified in paragraph 3.1.4.1.2) with the flexibility to start as early as 0600 and end as late as 1800, Monday through Friday.
3.1.4.2 CWS is an alternative work schedule to the traditional five (5) eight and a half (8.5) hour workdays (which includes a thirty-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two (2) week period of time: eight (8) weekdays are worked at nine and a half (9.5) hours each (which includes a thirty-minute lunch), one weekday is alternately worked as eight and a half (8.5) hours (which includes a thirty-minute lunch) and one weekday is not worked by the employee. The result is eighty (80) hours worked every two (2) weeks, with forty-four (44) work hours one (1) week and thirty-six (36) work hours the other. The Contractor may allow its employees to work a CWS schedule provided the requirements of the SOW are met. If the Contractor chooses to allow its employees to work a CWS schedule in support of this Contract, 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. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government to the COR/Alternate COR. The overall schedule must be provided to the COR.
3.1.4.3 Holidays. The Government observes the following holidays: New Year’s Day (January 1); Martin Luther King’s Birthday (the third Monday in January); Presidents Day (the third Monday in February); Memorial Day (the last Monday in May); Independence Day (July 4); Labor Day (the first Monday in September); Columbus Day (the second Monday in October); Veterans Day (November 11); Thanksgiving Day (the fourth Thursday in November); and Christmas Day (December 25). With the exception of the events in section 3.1.4.4, the Contractor is permitted to observe the above holidays IAW its corporate policy.
3.1.4.4 Installation closure. When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, Contractor personnel assigned to work at that facility performing non-mission essential work in support of such Federal employees shall follow their parent company’s policies. While generally Contractor personnel may not perform work on-site at a Government facility without oversight from Federal personnel, in very limited circumstances, work being performed by Contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by Contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant PCO must concur with any determination that work being performed by Contractor personnel is mission essential.
3.1.4.5 The Contractor, upon notification to, and concurrence from, the Contracting Officer's Representative (COR) that the employees' work tasking is eligible for telework, may utilize alternate worksites/locations and telework to support continued performance of its contract in accordance with company policy. Contractor discretion is required when making alternate worksite and telework decisions based upon the nature of support provided by the employees. In the event telework is utilized, the Contractor remains responsible for performance and compliance with any applicable cost accounting standards and contract cost principles / procedures.
3.1.4.6 Overtime. Overtime shall be IAW Section I Clause 52.222-2 Payment for Overtime Premiums.
3.1.5 Other Direct Costs (ODCs) (CLIN 0008)
3.1.5.1 Travel. Travel may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of this Contract is required. Temporary travel locations include Continental United States (CONUS) and outside the Continental United States (OCONUS) locations.
The lists show in paragraphs 3.1.5.1.1 and 3.1.5.1.2 are not all inclusive as locations and may change over the life of the contract.
3.1.5.1.1 CONUS: Locations may include the forty-eight (48) CONUS states, the District of Columbia (D.C.), Alaska, Hawaii, U.S. Territories and Canada.
3.1.5.1.2 OCONUS: Locations may include Cuba, South Korea, Kuwait, Bahrain, Qatar, Afghanistan, Pakistan, Japan, France, Germany, Poland, Belgium, and Italy.
3.1.5.1.3 Under this Contract, contractor employees, spouses and family members assigned overseas within the European Theater in Germany will be regulated by Army in Europe (AE) Regulation 600-700 dated 28 May 2009, or its replacement as superseded. Individual Logistics Support for Civilian Contractor Personnel will be provided in accordance with Chapter 7 of this Regulation.
3.1.5.1.4 Contractor employees working at SHAPE in Mons, Belgium are part of the U.S. Civilian Component and shall fall under (be eligible for) Status of Forces Agreement (SOFA) status in Belgium. Support Services available to the contractor are in accordance with Clause 5152.225-5908- Government Furnished Contract Support.
3.1.5.1.5 The COR/ACOR shall approve all travel performed in support of this contract prior to the commencement of the travel and all travel will result in a trip report. (CDRL A004)
3.1.5.1.6 Possible travel locations include those that are within the United States Central Command (USCENTCOM) Area of Responsibility (AOR). OCONUS, travel may be required in potentially dangerous environments. Contractors may be eligible for Danger Pay as a percent of their basic compensation per Department of State guidelines for Danger Pay.
3.1.5.1.7 Synchronized Pre-Deployment and Operational Tracker (SPOT). The Contractor may travel in United States Central Command (USCENTCOM) Area of Responsibility (AOR) locations. IAW Clauses 252.225-7040 and 5152.225-5908, SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF), their authorization and eligibility for access to specific DoD facilities, and their eligibility for specific Government- Furnished Support (GFS). The Contractor shall initiate a Letter of Authorization (LOA) for each prospective traveler. The Contractor shall use the SPOT link https://spot.altess.army.mil to enter and maintain data with respect to traveling/deployed personnel, and to generate LOA.
3.1.5.1.8 LOA. The Contracting Officer will provide LOA for official travel OCONUS, when applicable, supporting the contract. LOA will identify local authorizations, privileges, etc. as specified by DoD requirements. All defense Contractors working under this contract shall carry LOA, when applicable, with them at all times while deployed OCONUS.
3.1.5.2 Material. Incidental material will be required in the performance of this Contract. The Government will reimburse the Contractor for allowable material costs, exclusive of fee, incurred by the Contractor in performance of this Contract IAW the H-1 Restriction of the Direct Charging of Material clause. All materials not depleted during the performance of this Contract shall become Government property upon completion of this Contract (CDRL A019). The Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses but shall not include profit/fee.
3.1.6 Subcontractors. Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this Contract. All provisions of this SOW shall flow down to subcontractors providing support under this Contract.
3.1.7 Management of Contractor personnel. The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstance shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. The Contractor shall manage its employees and guard against any actions that are of a personal services nature or give the perception of personal services.
3.1.8 Transition out strategy. The Contractor’s overall transition out strategy shall be built around maintaining the mission of IC2&I Division with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the Contract, the Contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The Contractor shall submit a Transition Out Plan, to include the minimum elements listed below. (CDRL A005)
3.1.8.1 Work turnover. The Contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the Contract to the successor company. The Contractor shall stablish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.
3.1.8.2 Quality Assurance (QA). The Contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.
3.1.8.3 Risk mitigation strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.
3.1.8.4 Data/information transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.
3.1.9 Vehicles. The Contractor shall be required to transport Government-owned systems/subsystems on a daily basis. Contractor personnel may also be required to operate Government-owned and/or Government-leased vehicles in the performance of this Contract.
3.1.9.1 Contractor provided vehicles. The Contractor shall be responsible for transportation of equipment in support of this Contract. The cost of material transport vehicles supporting SOW requirements for the Contractor will not be considered as an allowable direct cost in the performance of the Contract.
3.1.9.2 Government provided vehicles. The Contractor shall be required, as defined at the TO level, to operate Government-owned or leased vehicles in performance of the Contract. Government-owned or leased vehicles that the Contractor may use includes, but is not limited to, general purpose passenger carrying vehicles, special-purpose (tactical) vehicles, and IC2&I Division authorized vehicles. All vehicles shall be operated IAW Naval Air Systems Command (NAVAIR) and site-specific processes and requirements. In general, there is no need for specialized licenses; however, if a requirement is identified in a specific TO, there will be time allotted for individuals to obtain the necessary licensing. The Contractor shall report any damage observed on the vehicle/equipment, and shall notify the Government Project Lead (GPL) of any need for service or repair of the Government-owned or leased vehicles. When operating these vehicles, the Contractor shall ensure: possession of a current and valid operator’s license for all vehicles; compliance with all state, federal, and host nation laws pertaining to operating motor vehicles; compliance with NAVAIR Command policies when operating a vehicle (e.g., no cell phone use, stopping at runway crossing, etc.); use of the most cost-effective means to fuel vehicles; and operation of the vehicles in a safe manner and IAW the vehicle/equipment user/operator manual.
3.1.9.3 The Contractor shall report any known or realized accidents involving the Government-owned or leased vehicles to the GPL. If the Contractor is involved in an accident while operating a Government-owned or leased vehicle, they shall notify the GPL, the Procuring Contracting Officer (PCO), and the COR within twenty-four (24) hours and shall provide an accident report within forty-eight (48) hours. (CDRL A018)
3.1.9.4 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.
3.2 Security.
3.2.1 Citizenship requirements. Only U.S. citizens may perform under this Contract, unless waived. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request shall include: the individual's name, date and place of birth, position title, and current citizenship; a statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements; a statement of the unusual expertise possessed by the applicant; a statement that access will be limited to a specific government contract (specify contract number); and a statement that the Contractor has obtained an export license for the information required to perform the Contract.
3.2.2 Investigative requirements.
3.2.2.1 Unclassified. All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by The Secretary of the Navy (SECNAV) Manual (M)-5510.30. All Contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management (OPM). The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the Contractor’s Electronic Questionnaire for Investigations Processing (eQIP), and shall do a preliminary screening of the Contractor’s eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor’s eQIP. In such cases, the Contractor employee may not perform on the Contract.
3.2.2.2 The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of Controlled Unclassified Information (CUI) and to control distribution of CUI IAW DoD 5220.22-M, NISPOM and SECNAV M-5510.36. All Contractor facilities shall provide an appropriate means of storage for CUI and materials. All CUI shall be appropriately identified and marked as For Official Use Only (FOUO) IAW DoDI 5200.48,Controlled Unclassified Information (CUI).
3.2.2.3 CUI including FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204– 7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoDI 5200.48 Controlled Unclassified Information (CUI) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 Distribution Statements on Technical Documents; and have this statement displayed per DoDI 5230.24, Enclosure 3.
3.2.2.4 Classified. All Contractor personnel shall maintain security clearance eligibility commensurate with the level of classification of the work performed as annotated in the Contract’s DD-254, Contract Security Specification Form. Contractor personnel shall require access to classified information in performance of this contract up to and including Top Secret, with a safeguarding level of Top Secret. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW DoDM 5220.22 NISPOM. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the Contract.
All personnel designated for access to SCI access must possess a current Single Scope Background Investigation (SSBI), Phase Periodic Review (PPR), Single Scope Background Periodic Reinvestigation (SBPR), T5 or equivalent investigation. All identified personnel are required to hold a TS clearance based upon a current T5 or equivalent investigation and must be eligible to be briefed into various SCI compartments. Designated individuals requiring access to NSANet require a successful Counterintelligence (CI) Polygraph.
3.2.2.5 The Contractor shall comply with security requirements specified in the DD-254 attached to this Contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled IAW the appropriate designation (CUI; FOUO; Covered Defense Information). Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this Contract shall be referred to the TPOC/COR of this Contract for approval.
3.2.2.6 Contractor personnel labor category security requirements. The Contractor shall obtain Interim Top Secret clearances sixty (60) days after contract award for the following labor categories. All other personnel who are planned to work on Government sites shall have interim clearances thirty (30) days after TO award.
| Labor Category |
| Security Clearance Level |
Required Full Time Equivalents
| General and Operations Manager, Senior (Program Manager) (KEY) |
| Top Secret |
| 1 |
General and Operations Manager, Journeyman (Project Manager) (KEY)
| Top Secret |
| 2 |
| Electrical Engineer, Senior (KEY) |
| Top Secret |
| 1 |
| Electrical Engineer, Journeyman (KEY) |
| Top Secret |
| 1 |
| Mechanical Engineer, Journeyman (KEY) |
| Top Secret |
| 1 |
First-Line Supervisors of Mechanics, Installers, and Repairs (non-KEY)
| Top Secret |
| 3 |
| Engineering Technician III (non-KEY) |
| Top Secret |
| 2 |
| General and Operations Manager, Senior (Program Manager) (KEY) |
| Top Secret/SCI |
| 1 |
General and Operations Manager, Journeyman (Project Manager) (KEY)
| Top Secret/SCI |
| 1 |
| Electrical Engineer, Senior (KEY) |
| Top Secret/SCI |
| 1 |
| Electrical Engineer, Journeyman (KEY) |
| Top Secret/SCI |
| 1 |
| Mechanical Engineer, Journeyman (KEY) |
| Top Secret/SCI |
| 1 |
Personnel not labeled as Key and not listed in the above table must be capable of obtaining a Secret clearance if needed during the performance and within sixty (60) days once identified.
3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).
3.2.3.1 SAAR-N. All Contractor personnel requiring access to Government IT systems shall have an approved SAAR-N Form Office of the Chief of Naval Operations (OPNAV) 5239/14 Rev Sep 2011 on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR-N forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.cnic.navy.mil/content/dam/cnic/hq/pdfs/Homepage/Command%20and%20Staff/OPNAV_52 39_14_Rev_9_2011.pdf. SAAR-N forms shall be submitted to the COR, GPL, or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.
3.2.3.2 CAC/Local Badges. Contractor CACs and facility specific identification badges will be issued by the Government to on-site Contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges. All CACs and identification badges issued to Contractor employees shall be returned to the TASS following completion of the Contract, relocation or termination of an employee, or upon request from the COR/PCO. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this Contract.
3.2.3.3 DD-254. The Contractor shall comply with security requirements specified in the DD-254 attached to this Contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as FOUO. Distribution is authorized to the Requiring Office’s Organization and supported Activities only. Other requests for deliverables under this Contract shall be referred to the COR of this Contract for approval. The Contractor shall obtain facility clearance at Top Secret per the Contract DD-254 within sixty (60) days after contract award.
3.2.4 Information security. If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and CUI and to control distribution of CUI IAW DoD 5220.22-M NISPOM and SECNAV M-5510.36. If the work is performed at the Government’s facility, the Contractor shall comply with facility security procedures and controls.
3.2.4.1 Marking. All information generated by the Contractor shall be properly marked. FOUO information generated and provided under this Contract shall be marked IAW DoDI 5200.48. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings IAW DoDD 5230.24 and program Security Classification Guidance.
3.2.4.2 Public release for Classified and Unclassified Information. No information pertaining to this Contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the office listed in Block 12 of the Contract’s approved DD-254.
3.2.4.3 Loss, compromise, and electronic spillage of Classified or CUI. All instances of loss, compromise, and electronic spillage of Classified or CUI shall be reported to the COR, GPL, and Government Security Office within twenty-four (24) hours of the incident occurring.
3.2.5 Operations Security (OPSEC). The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the Contract. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance (IA) and Communications Security (COMSEC). The OPSEC program shall be IAW National Security Decision Directive (NSDD) 298, and at a minimum shall include:
a. Assignment of responsibility for OPSEC direction and implementation.
b. Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.
c. Establishment of OPSEC education and awareness training.
d. Provisions for management, annual review, and evaluation of OPSEC programs.
e. Flow down of OPSEC requirements to subcontractors when applicable.
While performing at Government sites, the Contractor shall:
a. Comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts.
b. Include OPSEC as part of its ongoing security awareness program and take all required Agency training.
c. Be responsive to the Supporting OPSEC Manager on a non-interference basis.
d. Protect sensitive unclassified information and activities, which could compromise classified information or operations or degrade the planning and execution of operations performed by the Requirements Owner and Contractor in support of the mission. (CDRL A006)
3.2.6 Anti-Terrorism Force Protection and Emergency Management. The work performed on this Contract is not Emergency Essential IAW OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism, and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism, and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials’ direct curtailment of operations to “Mission Essential
Only.” All Contractor personnel assigned to a Government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.
3.2.7 IT access. All Contractor personnel with access to unclassified information systems, including e-mail, shall have, at a minimum, a favorable National Agency Check (NAC). The Contractor shall coordinate with the COR all IT network or website access requirements after award of the Contract and shall be IAW the latest DoD policies and the IC2&I RDT&E LAN SOP. (Attachment 14)
3.2.7.1 Contractor facility IT access. Employees requiring access to various DoD IT network or network resources from a Contractor facility are mandated by DoD policy to use Government-approved Public Key Infrastructure (PKIs) along with an appropriate hard key (i.e. Smart Card). Defense Information Systems Agency (DISA) will be the primary source for these certificates.
3.2.7.2 Government facility IT access. Contractor-owned equipment will be permitted connection to NAVAIR/DoD networks in order to carry out the performance of this Contract. Upon contract award, the Contractor shall provide all Government site employees desk top computers to conduct daily work that meet all of the hardware, software, and standard architecture set forth in the IC2&I RDT&E LAN SOP. Portable computers and laptops are not allowed to be connected to the IC2&I RDT&E LAN. All Government site staff will require desktop computers to directly connect to the IC2&I RDT&E LAN. Desktop computers shall have sufficient memory, hard disk space, a network interface card, CAC readers, and the capability of running a full range of standard software including current versions of Microsoft Windows Operating System and Microsoft Office Professional. All Contractor-owned hardware or software shall meet DoD 8500.2 IA controls. Technical support from the manufacturer of Contractor- owned hardware and software must be available. All Contractor-owned desktop computers provided for Government facility access will be submitted for re-imaging and validation scanning prior to allowing connection to the IC2&I RDT&E LAN. Approval is required by COR and IC2&I Network Information Site Security Officer prior to connection. All connected desktops will be subject to continuous monitoring.
3.2.7.3 Navy Marine Corps Intranet (NMCI). Access to NCMI is not anticipated for this Contract. If determined to be necessary, the Government will provide all NMCI services, to include hardware, software, and IT support necessary for the performance of this Contract. Coordination of these services is to be conducted through the COR.
3.3 Detailed support.
3.3.1 Research, develop, design, verify, and validate new, production, or in-service systems.
3.3.1 (a) (RDT&E) Provide research and development support for design, verification, and validation activities associated with the engineering and installation support of new EXCOMM C4I systems. Applicable to paragraphs 3.3.1.1–3.3.1.11.
3.3.1 (b) (Procurement (PROC)) Provide modernization and modification support of EXCOMM C4I systems, including product improvements during production engineering and verifying, validation, kitting, customizing, installing, assimilation, and logistics support. Applicable to paragraphs 3.3.1.1–3.3.1.11.
3.3.1 (c) (Operations and Maintenance (O&M)) Provide life cycle planning and Integrated Product Support (IPS) during the design and validation support phase of in-service, fielded, and out-of-production EXCOMM C4I systems. Applicable to paragraphs 3.3.1.1–3.3.1.11.
3.3.1 (d) (Working Capital Fund (WCF)) Provide research and development support for design, verification, and validation activities associated with the engineering and installation support of new EXCOMM C4I systems. Provide modernization and modification support of EXCOMM systems, including product improvements during production engineering and verifying, validation, kitting, customizing, installing, assimilation, and logistics support.
Provide life cycle planning and Integrated Product Support (IPS) during the design and validation support phase of in-service, fielded, and out-of-production EXCOMM C4I systems. Applicable to paragraphs 3.3.1.1–3.3.1.11.
3.3.1(e) (Non-Department of Defense (Non-DoD)) Provide research and development support for design, verification, and validation activities associated with the engineering and installation support of new EXCOMM C4I systems. Provide modernization and modification support of EXCOMM C4I systems, including product improvements during production engineering and verifying, validation, kitting, customizing, installing, assimilation, and logistics support. Provide life cycle planning and Integrated Product Support (IPS) during the design and validation support phase of in-service, fielded, and out-of-production EXCOMM C4I systems. Applicable to paragraphs 3.3.1.1–3.3.1.11.
3.3.1.1 The Contractor shall assess new operational, production, or in-service systems and equipment for possible improvements including investigating new technologies, examining requirements, and providing recommendations on how best to meet C4I mission performance capabilities or modernization requirements. (CDRL A007)
3.3.1.2 The Contractor shall research new or assess production system or in-service system component capabilities to meet design or production goals and standards considering the operational environment and identify risks making alternative recommendations considering cost and feasibility. (CDRLs A007, and A008)
3.3.1.3 The Contractor shall assess new or production system or in-service system design, including evaluation of historical development and draft technical studies and evaluations. (CDRL A007)
3.3.1.4 The Contractor shall assess interoperability, operability, reliability, and maintainability in intended environments considering lifecycle cost effectiveness, and identify new or existing design inadequacies, report results, implications, and prepare Analysis of Alternatives (AoA). (CDRLs A007, and A008)
3.3.1.5 The Contractor shall develop concept, preliminary, and detailed designs for operational and product systems based on approved requirements and recommend technical standards for installation, maintenance, accreditation, and certification. (CDRLs A007, and A009)
3.3.1.6 The Contractor shall conduct component design and production engineering at the unit level on a specific piece of hardware and conduct system design and production engineering on new, developing, or existing systems undergoing improvement modification with the totality of intrasystem and future intersystem performance considered. (CDRL A007)
3.3.1.7 The Contractor shall develop and maintain engineering drawings throughout design and testing to include the creation of detailed electrical and mechanical assembly and installation drawings and engineering sketches. (CDRL A008)
3.3.1.8 The Contractor shall prepare single line block diagrams, system cable block diagrams, system wire run sheets, communication space arrangement drawings, antenna systems arrangement drawings, and installation control drawings in a format suitable for incorporation into Master Equipment Lists (MELs) and Master Parts Lists (MPLs). (CDRLs A008, and A010)
3.3.1.9 The Contractor shall prepare full-scale mockups or production planning for a specified communication site or system to serve as an evaluation/production tool for development and verify optimum arrangements within the communication spaces. (CDRLs A007, A008, and A009)
3.3.1.10 The Contractor shall develop test beds for advanced development models or plans for verification and validation of production systems; conduct system laboratory test or validation efforts; and evaluate alternate design modernization efforts. (CDRL A007)
3.3.1.11 The Contractor shall prepare and maintain implementation plans identifying recommended approaches and schedules for the design, development, fabrication, equipment assimilation, and verification efforts to include when requested drawings; lists of material with associated space and weight characteristics; special purpose verification and validation equipment; facility requirements identifying space allocations; site preparation requirements; power requirements; environmental control requirements; and personnel requirements. (CDRLs A007, A008, A009, A010, and A011)
3.3.2 Verification and validation.
3.3.2 (a) (RDT&E) Provide research and development support to identify operational requirements, design, verification, and validation activities associated with the engineering and installation support of new EXCOMM C4I systems. Applicable to paragraphs 3.3.2.1–3.3.2.8.
3.3.2 (b) (PROC) Provide verification and validation planning efforts to support the modernization and modification of EXCOMM C4I systems. Applicable to paragraphs 3.3.2.1–3.3.2.8.
3.3.2 (c) (O&M) Provide life cycle planning and IPS during the verification and validation support phase of in- service, fielded, and out-of-production EXCOMM C4I systems. Applicable to paragraphs 3.3.2.1–3.3.2.4.
3.3.2 (d) (WCF) Provide research and development support to identify operational requirements, design, verification, and validation activities associated with the engineering and installation support of new EXCOMM C4I systems. Provide verification and validation planning efforts to support the modernization and modification of EXCOMM C4I. Provide life cycle planning and IPS during the verification and validation support phase of in- service, fielded, and out-of-production EXCOMM C4I systems. Applicable to paragraphs 3.3.2.1–3.3.2.8.
3.3.2 (e) (Non-DoD) Provide research and development support to identify operational requirements, design, verification, and validation activities associated with the engineering and installation support of new EXCOMM C4I systems. Provide verification and validation planning efforts to support the modernization and modification of EXCOMM C4I. Provide life cycle planning and IPS during the verification and validation support phase of in- service, fielded, and out-of-production EXCOMM C4I systems. Applicable to paragraphs 3.3.2.1–3.3.2.8.
3.3.2.1 The Contractor shall provide verification and validation support for new, in-service, and modified C4I systems that are located in both laboratory settings and end user locations and take corrective action, when approved, to resolve identified problems.
3.3.2.2 The Contractor shall conduct and support verification and validation following approved test plans and procedures, including assessing vulnerability of new and existing C4I systems to Electronic Counter Measures (ECM). (CDRL A007)
3.3.2.3 The Contractor shall provide techniques, design changes, or other strategy recommendations aimed toward reducing ECM vulnerability. (CDRL A007)
3.3.2.4 The Contractor shall develop test aids for use in verification and validation, and testing and evaluating specified systems or equipment, and provide end user training when requested. (CDRLs A007, A008, and A014)
3.3.2.5 The Contractor shall verify C4I systems and components meet performance criteria throughout the build and delivery of the system.
3.3.2.6 The Contractor shall provide independent and objective review of existing verification plans, procedures, results, and data; identify and track deficiencies to closure; and recommend corrective measures. (CDRL A007)
3.3.2.7 The Contractor shall perform breadboard and bench tests and assess overall system effectiveness, reliability, maintainability, human engineering, and logistic supportability. (CDRLs A007, A012, and A013)
3.3.2.8 The Contractor shall prepare test plans and procedures that establish basic requirements for and relationships among First Article Tests (FATs), factory acceptance tests, system integration tests, installation tests, acceptance tests, technical evaluations, operational Test & Evaluations (T&Es), and test outlines in addition to providing inputs to existing Test Bed Implementation Plans, Test and Evaluation Master Plans (TEMPs), and T&E Plans. (CDRLs A007, A012, and A013)
3.3.3 System Engineering (SE), assimilation, and installation.
3.3.3 (a) (RDT&E) Provide research and development support to identify operational requirements and evaluate possible solutions while conducting SE,…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .