ASSDE_SOW.pdf
PDF 862 KB Posted
- Attached to
- Advanced Sensor System Development and Execution (ASSDE) Federal contract opportunity
- Solicitation number
- N00421-19-R-0069
About this file
This is a sources sought synopsis for an indefinite delivery indefinite quantity contract to provide scientific and engineering support services. Key details include:
-
The Naval Air Warfare Center Aircraft Division is seeking support for design, development and demonstration of sensor technologies including ISR, EO/IR, HSI/MSI, LIDAR, RADAR, ELINT, SIGINT, CBRNE and SONAR systems for manned and unmanned airborne, shipborne and ground platforms.
-
The period of performance is anticipated to be five years with a single award IDIQ contract using cost-plus-fixed fee contract types.
-
Place of performance includes NAS Patuxent River (35%), Yuma Proving Grounds (15%) and a contractor facility (50%).
-
The NAICS code is 541330 for engineering services and the size standard is $38.5 million. Responses are requested from all business sizes.
-
Capability statements are due by March 29, 2019 and must demonstrate experience, facilities, personnel and approach for the tasks in the draft SOW/PWS including scientific and engineering support services.
Draft Statement of Work
View the file
Other files for this federal contract opportunity
Show all 50
Advanced Sensor System Development and Execution (ASSDE) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ADVANCED SENSOR SYSTEM DEVELOPMENT AND
EXECUTION STATEMENT OF WORK/PERFORMANCE
WORK STATEMENT
1.0 Scope
The Department of Navy (DoN), Naval Air Warfare Center Aircraft Division (NAWCAD)
Advanced Concepts & Rapid Transition (AC&RT) Division (AD-4.11.6) was established to support the rapid insertion and transition of advanced technologies, systems, sensors, and weapons to enable programs of record, as well as deliver direct insertion of capabilities to meet urgent fleet needs. AD-4.11.6 works with customers and sponsors to identify capability gaps and requirements; to develop programmatic strategies; to conduct technology development, article testing & evaluation; and to support technology insertion. This Statement of Work
(SOW)/Performance Work Statement (PWS) defines the requirement to support AD-4.11.6.
Specifically, AD-4.11.6 leverages and coordinates the efforts of industry, academia, and
Government laboratories as an organic Lead Systems Integrator (oLSI) to design, develop, and deliver prototype systems to operational users. Using systems engineering and systems of systems management approaches, AD-4.11.6 integrates new technologies, Commercial off the
Shelf (COTS) and Government off the Shelf (GOTS) capabilities, as well as other industry or
Government resources, in order to meet the requirements of each customer.AD-4.11.6 has a requirement to procure services in support of the design, development, and demonstration of sensor technologies including, but not be limited to, Information, Surveillance, Reconnaissance
(ISR); Electro-Optical/Infrared (EO/IR); Hyper-Spectral/Multi-Spectral Imaging (HSI/MSI);
Light Detection and Ranging (LIDAR); Radio Detection and Ranging (RADAR); Electronic
Intelligence (ELINT); Signals Intelligence (SIGINT); Chemical, Biological, Radiological, Nuclear, and Explosive (CBRNE); and Sound Navigation and Ranging (SONAR) for a variety of manned and unmanned airborne and shipborne platforms and fixed and mobile ground stations.
2.0 Applicable Documents
2.1 Department of Defense (DoD) specifications.
2.1.1 DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) 28 Feb 2006.
2.1.2 SECNAV M-5510.36 Information Security Program, 30 Jun 2006.
2.1.3 DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified
Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) 24 Feb 2012.
2.1.4 DoD 5400.7-R, Freedom of Information Program Chapter 3 (pages 31-42) Sep 1998.
2.1.5 DoDD 5230.24 Distribution Statements on Technical Documents, Change 1, Effective 28 Apr 2016.
2.1.6 SECNAV M-5510.30 Personnel Security Program Jun 2006.
2.1.7 OPNAVINST 3440.17A Navy Installation Emergency Management Program, 1 Aug
2014.
2.1.8 SECNAVINST 5239.1 Navy Information Assurance (IA) Program.
2.1.9 SECNAVINST 5239.3B Department of the Navy Information Assurance Policy.
2.1.10 SECNAVINST 5510.36A DON Information Security Program Instruction.
2.1.11 OPNAVINST 3710.7U NATOPS General Flight and Operating Instruction.
2.1.12 OPNAVINST 3750.6S The Naval Aviation Safety Management System.
2.1.13 OPNAVINST 5090.1D Environmental Readiness Program Manual.
2.1.14 OPNAVINST 5100.23G Safety and Occupational Health Program.
2.1.15 OPNAVINST 5102.1D Navy and Marine Corps Mishap and Safety Investigation, Reporting and Record Keeping.
2.1.16 OPNAVINST 5239.1C Navy Information Assurance (IA) Program.
2.1.17 OPNAVINST 8000.16D Naval Ordnance Management Policy.
2.1.18 OPNAVINST 8020.14A Department of the Navy Explosives Safety Management
Policy Manual.
2.1.19 OPNAVINST 8023.24C Navy Personnel Ammunition and Explosives Handling
Qualification and Certification Program.
2.1.20 COMFISCINST 5090.1 Ch. 8 Hazardous Material Control and Management
(HMC&M) Plan.
2.2 DoD standards.
2.2.1 NAVSUP Instructions 4200.85D DON Simplified Acquisition Procedures.
2.2.2 MIL-STD-980 Foreign Object Damage (FOD) Prevention In Aerospace Products.
2.2.3 DoD Regulations 7000-14 DOD Financial Management Regulation Continue to cover all referenced standards.
2.2.4 DODM 4145.26-M DOD Contractor Safety Manual for Ammunition and
Explosives.
2.2.5 DODM 4161.2-M DOD Manual for the Performance of Contract Property
Administration.
2.2.6 DODM 5200.2-R Personnel Security Program.
2.2.7 DODM 5200.01 DoD Information Security Program: Controlled Unclassified
Information (CUI).
2.2.8 DODM 5220.22M National Industrial Security Program: Procedures for
Government Activities Relating to Foreign Ownership, Control, or Influence (FOCI).
2.2.9 DODM 5400.7-R, Freedom of Information Program.
2.2.10 DODINST 4715.06 Environmental Compliance in the United States.
2.2.11 DODINST 5100.76 Physical Security of Sensitive Conventional Arms, Ammunition, and Explosives (AA&E).
2.2.12 DODINST 6055.17 DoD Installation Emergency Management (IEM) Program.
2.2.13 DODINST 8510.01 Risk Management Framework For DoD Information
Technology.
2.2.14 DODINST 8500.01 Cybersecurity.
2.2.15 DODINST 8500.2 Information Assurance.
2.2.16 DODINST 8520.2 Public Key Infrastructure & Public Key Enabling.
2.2.17 DOD Regulation 5200.1-R Information Security Regulation.
2.2.18 DOD Directives 5220-M National Industrial Security Program Operating Manual.
2.2.19 DOD Directives 5230.24 Distribution Statements on Technical Documents.
2.2.20 DOD Directives 5030.61 Department of Defense (DoD) Directive, Airworthiness
Policy.
2.2.21 DOD Directives 8500.1 Information Assurance.
2.2.22 DOD Directives 8140.01 Cyberspace Workforce Management.
2.2.23 DTM 17-001 Cybersecurity in the Defense. Acquisition System.
2.3 Other Government documents (e.g. Naval Air Systems Command (NAVAIR) Documents).
2.3.1 NAVAIRINST 3710.8E Authority for Personnel to Pilot or Fly in Aircraft Under the Controlling Custody of Naval Air Systems Command to Include the Authority for
Naval Air Systems Command Personnel to Participate in (Pilot or Fly In) Commercial
Aircraft Conducting Public Aircraft Operations in Support of Test and Evaluation.
2.3.2 NAVAIRINST 3750.5C Safety Program.
2.3.3 NAVAIRINST 3960.4C Project Test Plan Policy for Testing Air Vehicles, Air
Vehicle Weapons, and Air Vehicle Installed Systems.
2.3.4 NAVAIRINST 8012.2A Identification of Non-Nuclear Ordnance Non-Combat
Expenditure Requirements and Allocations.
2.3.5 NAVAIRINST 10350.3A Use of Lubricants, Fluids and Compounds.
2.3.6 NAVAIRINST 13023.2 Establishment of Guidelines for Preparation of Depot Level
Maintenance Specifications.
2.3.7 NAVAIRINST 13034.1D Flight Clearance Policy for Vehicles and Aircraft Systems.
2.3.8 NAVAIRINST 13050.6A Configuration Management Policy, Procedures and
Responsibilities for Aircraft Assigned to Naval Air Systems Command Aircraft Controlling
Custodian.
2.3.9 NAVAIRINST 13640.1C Naval Aviation Metrology and Calibration Program.
2.3.10 NAVAIRINST 13640.3 Metrology and Calibration Quality Assurance Program.
2.3.11 NAVAIRINST 13650.1D Naval Air Systems Command Aircraft Maintenance
Material Readiness List (AMMRL).
2.3.12 NAWCADINST 3120.1A Shipboard and Off-Site Shore Based Aircraft Test
Operations.
2.3.13 NAWCADINST 5510.1B Information, Personnel and Industrial Security Program.
2.3.14 NAWCADINST 13050.1D Aircraft Modification Configuration Management Policy, Procedures and Responsibilities.
2.3.15 NAWCADINST 3432.1B Operational Security.
2.3.16 NAVTESTWINGLANT 3140.1B Disaster Response and Destructive
Weather/Aircraft Evacuation Plan.
2.3.17 NAVTESTWINGLANT 8020.1J Naval Test Wing Atlantic Ordnance Standard
Operating Procedures.
2.3.18 COMNAVREGMIDATLANTIC 6820.1A Para 5 Regional Consolidated Hazardous
Material Reutilization and Inventory Management Program (CHRIMP).
2.3.19 NASPAXRIVINST 3140.6P Destructive Weather Preparedness and Response Plan.
2.3.20 NASPAXRIVINST 3710.5V Air Operations Manual.
2.3.21 NASPAXRIVINST 3710.17H NAS Air Operations Standard Operating Procedures
(SOP).
2.3.22 NASPAXRIVINST 3721.2E Airfield Vehicle Operators Indoc Course.
2.3.23 NASPAXRIVINST 3750.1B Aviation Safety Program.
2.3.24 NASPAXRIVINST 4602.1A Transportation of Liquid Oxygen and Nitrogen.
2.3.25 NASPAXRIVINST 5090.1B Environmental Management System Implementation.
2.3.26 NASPAXRIVINST 5090.2 Naval Air Station Patuxent River Complex (PRC) Oil and Hazardous Substance Integrated Contingency Plan (ICP).
2.3.27 NASPAXRIVINST 5090.5 Regulated Waste Management Plan Implementation
Order.
2.3.28 NASPAXRIVINST 5100 Commanding Officer's OSHA Policy.
2.3.29 NASPAXRIVINST 5100.35D Safety and Occupational Health (SOH) Manual.
2.3.30 NASPAXRIVINST 8010.1B Naval Air Station Patuxent River Ordnance
Regulations.
2.3.31 NASPAXRIVINST 8010.2B Ordnance Requisition and Turn in Guide.
2.3.32 NASPAXRIVINST 8020.14E NAS Explosive Safety Self-Assessment (ESSA)
Program.
2.3.33 NOSSA Instructions 8020.14E Shore Station Explosives Safety Compliance (ESI)
Program.
2.3.34 NAVSEA Instructions OP-5 Ammunition and Explosives Ashore.
2.3.35 NAVSEA Instructions 8020.6D Navy Weapons System Safety Program.
2.3.36 NAVAIR Manual 00-25-100 Technical Manual Program.
2.3.37 NAVAIR Manual 00-80T-105 CV NATOPS Manual.
2.3.38 NAVAIR Manual 00-80T-120 CV Flight/Hangar Deck NATOPS.
2.3.39 NAVAIR Manual 00-80T-106 LHA/LHD NATOPS Manual.
2.3.40 NFPA Manual 70 National Electrical Code.
2.3.41 NFPA Manual 09 Standard on Aircraft Hangars.
2.3.42 NAVSUP Publication P-409 MILSTRIP/MILSTRAP Desk Guide.
2.3.43 NAVSUP Publication P-485 MILSTRIP/MILSTAP Manual.
2.4 Industry documents.
2.5 Others if needed.
2.5.1 C.F.R. 29 Code of Federal Regulations, Title 14.
2.5.2 DAU Defense Acquisition Handbook.
2.5.3 ISEET Test Planning Integrated Systems Evaluation, Experimentation and Test
Department, Test Planning.
2.5.4 ISEET Test Reporting Integrated Systems Evaluation, Experimentation and Test
Department, Test Reporting.
2.5.5 SOP 50 NAWCAD AVSCSB AIR5168 B142 Gun Ground Firing Ops ATA.
2.5.6 SOP 51 NAWCAD AVSCSB AIR5168 Building 142A Static Test Stand Op
Procedures.
2.5.7 SOP 52 Mass Property Measurement.
2.5.8 SOP 54 Aircraft Stores Drop Pit in Building 2790.
2.5.9 SOP 54 Static Aircraft and Test Stand Tests Utilizing Cartridge Activating
Devices/Squibs and Pneumatic Rack Systems for the Armament Test Area and Aircraft
Hangars and Parking Ramps.
2.5.10 SOP 56 Ground Firing ACFT RKTs MSLs Chaff & Flare BQMs.
2.5.11 Yuma Proving Grounds.
2.5.11.1 YP-YTRO-P-1000 Range Operations.
2.5.11.2 YP-YTAA-P-2001 Aircraft Weapons and Systems Testing.
2.5.11.3 YP-YTAA-P-2601 Unmanned Aircraft Systems Operations.
3.0 REQUIREMENTS
3.1 General Requirements
3.1.1 Compatibility: The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government Information Technology (IT) environment through the security classification of Top Secret (TS). The current operating environment required for this contract includes:
̶ Microsoft Windows 10
̶ Microsoft Project 2010
̶ Microsoft Excel 2010
̶ Microsoft Office Professional Plus 2010
̶ Adobe Acrobat XI (reader)
̶ Internet access
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 maintain state-of the-art virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and Local Area Network (LAN) communications with AD-4.11.6.
Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with AD-4.11.6 during working hours whether at Contractor work site or on travel.
3.1.2 Work Location and Facilities
3.1.2.1 Work Location: Approximately 50% of work will be performed at Government sites and 50% of work to be performed at Contractor site. Government site(s) include Naval Air
Station (NAS) Patuxent River, Webster Field (NAS Patuxent River Annex), and Yuma, AZ
Proving Grounds. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. The geographic location of the Contractor’s primary facility with respect to
NAS Webster Field must be within a fifty (50) mile driving distance of the Government Program
Office at Webster Field.
3.1.2.2 Meeting Support: In support of the tasking outlined in this Statement of Work
(SOW)/Performance Work Statement (PWS), the Contractor shall have the capability to host and conduct meetings at classification levels up to Secret with the capacity to support a minimum of fifteen (15) persons and have Contractor furnished telephone and Video Teleconference (VTC) capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in Paragraph 3.1.1. This support shall be provided within twenty-five (25) miles of NAS Patuxent River, MD
3.1.2.3 Government Facilities: If able, the Government will provide access to facilities in which to perform or support the requirements of this SOW/PWS.
3.1.2.4 Government Equipment: The Government will provide equipment and previously developed in-house and publicly available software at the Government facilities to perform software development; data reduction and analysis; and related integration efforts as applicable.
The Government will provide all office furniture (i.e. tables, chairs, file cabinets, etc.) required to execute the efforts for those who will be located at the Government facility.
3.1.2.5 Additional Government Material and Equipment: As required, the Government will provide the Contractor with the additional Government material and equipment for use during performance of the Contract. This additional Government material and equipment shall remain the property of the Government during performance of the Contract. The material and equipment will include, but is not limited to:
̶ All material centrally procured, locally purchased, General Services Administration
(GSA), Defense Supply Agency, and non-stock listed items
̶ All raw stock required for local manufacture
3.1.2.6 Navy and Marine Corps Intranet (NMCI): The Government will provide NMCI services to include IT related hardware, software, and support necessary for the performance of this SOW/PWS as determined by the Contracting Officer’s Representative (COR) for on-site employees, and select offsite employees as determined by the Government. Implementation of these services shall be coordinated and conducted through the COR.
3.1.3 Contract status reporting: The contractor shall provide the following documentation.
3.1.3.1 Monthly Progress and Financial Status Report: The Contractor shall provide a
Contracting Officer’s Management Report. (Contract Data Requirements List (CDRL) A017)
3.1.3.2 The Contractor shall provide a Management Plan. (CDRL A019)
3.1.4 Work schedule to include Compressed Work Schedule (CWS), overtime, holidays, installation closure, and telework.
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 30-minute lunch break), from 0730 to 1600 each Monday through Friday
(except on the legal holidays specified in paragraph 3.1.4.1.2). Some supported Government offices have flexibility to start as early as 0600/0630 and end as late as 1800, Monday–Friday.
3.1.4.1.1 Compressed Work Schedule (CWS): CWS is an alternative work schedule to the traditional five (5) eight and half (8.5) hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: eight (8) weekdays are worked nine and a half (9.5) hours each
(which includes a 30-minute lunch), one (1) weekday is alternately worked eight and a half (8.5) hours (which includes a 30-minute lunch) and one (1) 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.
3.1.4.1.2 The Contractor may allow its employees to work a CWS schedule. 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 (ACOR).
3.1.4.1.3 Holidays: The Government observes the following holidays:
̶ New Year’s Day, January 1
̶ Martin Luther King Day, 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
̶ Christmas Day, December 25
With the exception of the events in section 3.1.4.1.3 below, the Contractor is permitted to observe the above holidays In Accordance With (IAW) its corporate policy.
3.1.4.1.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 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 Contracting Officer (KO) must concur with any determination that work being performed by contractor personnel is mission essential.
3.1.4.1.5 Overtime: Overtime cannot be charged directly to the Contract unless first approved in writing by the Chief of the Contracting Office (CCO) and shall not exceed the amount specified in FAR Clause 52.222-2 Payment for Overtime Premiums
3.1.4.1.6 Hazardous Duty Pay: At the direction of the COR, the Contractor may be required to travel to and perform work within an area requiring hazard duty pay (aka danger pay).
3.1.4.1.7 Telework: The Contractor may allow its employees to telework on a case-by-case basis depending on the nature of support provided by the Contractor’s employee. For regular reoccurring telecommuting to be authorized, a written company policy for telecommuting must be in place with the Contractor covering all terms and conditions including, but not limited to: a written agreement between the company and employee; work site of telecommute; time and attendance; work performance; overtime; security and equipment; liability and injury compensation; standards of conduct; mileage savings; length of agreement; specifics of the employer’s telework and emergency planning policies; proposed definitive amount of work to be accomplished; expected savings to the Government if authorized to Telecommute; measures in place to ensure project will be on schedule and auditable for reimbursement; and access to
NMCI, if access is required for performance.
If telecommuting is requested after a Contract has been placed, concurrence from the KO and the
COR/ACOR is required. Furthermore, the telework terms and conditions must be addressed in the Contractor’s request for telecommuting. DoD Instruction 1035.01 of 4 April 2012 will be used as a guide for determining situations where teleworking is feasible. The Government reserves the right to prohibit telework where the Government determines it to not be in the
Government's best interest.
3.1.5 Other Direct Costs (ODC) (Contract Line Item Numbers (CLINs) 0016, 0017, 0018, 0019, 0020): ODCs are based on a per annum amount. The COR/ACOR approval shall be obtained prior to the purchase of any material or travel expenses.
3.1.5.1 Travel: Travel will be allowable only when it is essential to the performance of the tasks detailed in section 3.3. Reimbursement for travel performed shall be IAW the DoD Joint
Travel Regulation (JTR) (http://www.defensetravel.dod.mil/site/travelreg.cfm) and NAVAIR clause 5252.252-9509 Travel Approval and Reimbursement Procedures. COR approval shall be obtained for all travel performed in support of this Contract prior to the commencement of the travel. Travel may include general and administrative expenses, but shall not include profit.
Temporary travel to other locations in support of program tasking is required. If required, temporary travel locations include Continental United States (CONUS) and Outside CONUS
(OCONUS) locations. These lists shown in the 3.1.5.1.1-3.1.5.1.2 are not all inclusive as locations may change over the life of the contract.
3.1.5.1.1 CONUS: Locations may include, but are not limited to, St. Inigoes, MD; California, MD; China Lake, CA; and Yuma, AZ.
3.1.5.1.2 OCONUS: OCONUS travel shall be conducted IAW DFARS Clause 252.225-7040, and the requirements set forth in the Task Order (TO). OCONUS locations may include, but are not limited to, Colombia, Djibouti, Philippines, and Italy.
3.1.5.1.3 Synchronized Pre-Deployment & Operational Tracker (SPOT): The Contractor may travel in combatant command locations. SPOT enables the validation of Contractors Authorized to Accompany the Force (CAAF), (i.e. Contractor personnel associated with specific contracts and subcontracts); 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.dmdc.mil to enter and maintain data with respect to traveling/deployment personnel and to generate LOAs.
3.1.5.1.4 Letter of Authorization (LOA): The Government will provide a LOA for office travel supporting this Contract. LOAs will identify local authorizations, privileges, etc., as specified by DoD requirements. All defense Contractors working under this Contract shall carry a LOA with them at all times while deployed.
3.1.5.1.5 Local Travel Reimbursement: Reimbursement of personal travel to-and-from
NAWCAD 4.11.6, NAS Patuxent River, Webster Field Annex and the Contractor’s facility and the surrounding area, by the Contractor or Subcontractor located within (50) driving miles of
NAS Patuxent River, Webster Field Annex, is not an allowable cost.
3.1.5.1.6 Travel request authorization: The Contractor shall provide the COR a written request for authorization to travel at least thirty (30) days in advance of the required travel date, when possible. The request should include: purpose of travel, location, travel dates, number of individuals traveling, and all estimated costs associated with the travel (e.g. lodging, meals, transportation costs, incidental expenses, etc.). Upon completion of travel, the Contractor shall complete a travel report. (CDRL A008) https://spot.dmdc.mil/
3.1.5.2 Material: The Contractor may be required to purchase incidental hardware and software as specified within individual TOs. All incidental hardware and software purchases shall be IAW
Section H NAVAIR Clause, Restriction of the Direct Charging of Material (VARIATION). Any material provided by the Contractor is subject to the requirements of the Federal Acquisition
Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable DoN regulations and instructions. The Contractor shall track the physical location of and maintain software integrity within the licensing agreement of the producer. The Contractor is responsible for maintenance of the hardware during the period of the individual TO. The
Contractor may be required to purchase specific pieces of hardware or software selected by the
Government to meet the strict and specific requirements of the TO in order to satisfy the requirements of the customers.
All materials not depleted during the performance of this contract and subsequent TOs shall become Government property upon completion of this contract and subsequent TOs. The
Contractor shall transfer all materials not depleted to the COR by way of Material Inspection and
Receiving Report (DD Form 250). The Government may choose to supply the Contractor equipment or hardware, via Government Furnished Equipment (GFE) as identified per TO, to be integrated into the various systems. Material costs may include general and administrative expenses but shall not include profit.
3.1.6 Subcontractors and consultants: Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW/PWS shall flow down to subcontractors and consultants providing support under this contract.
3.1.7 Management of Contractor personnel: The Government will neither supervise
Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will 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 the nature of personal services, or give the perception of personal services.
3.1.8 Transition out strategy.
The Contractor shall submit a Transition Out Plan. The Contractor’s overall strategy shall be built around maintaining the mission of AD-4.11.6 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 IAW CDRL A018.
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 establish 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.8.5 Within thirty (30) days prior to termination, the Contractor shall ensure cooperation with the Government in conducting joint wall-to-wall inventories and ensuring continuity of ongoing services. (CDRL A028)
3.1.9 Training requirements.
3.1.9.1 Certification and training: The Contractor is responsible for ensuring all employees have the required training and certification, as stated in SOW/PWS Paragraph 3.4, by verifying experience, special training, and qualifications.
3.1.9.2 Additional training requirements: Contractor employees shall complete Government specific training as required by the COR, provided by the Government, at no cost to the
Contractor. This training includes new and recurring Navy requirements not available commercially.
3.1.9.3 Corporate applications and Information Assurance (IA): The Contractor shall gain access to the appropriate corporate applications. These systems may include, but are not limited to, NMCI, One Touch, and Navy Enterprise Resource Planning (N-ERP). Contractor personnel assigned to perform work under this Contract and who require access to Government IT Systems shall comply with DoN IA and Personnel Security Requirements for Accessing Government IT
Systems.
3.1.10 Contract oversight.
3.1.10.1 The Contractor shall develop and implement Management Information System (MIS) techniques and software tools to improve the productivity and management of TO requirements.
3.1.10.2 The Contractor shall implement standardized program and critical path management techniques and software tools to improve the planning, management, and control of TO requirements.
3.1.11 The Contractor shall implement MIS techniques and tools to automate, manage, and coordinate the flow of information and data to other Government agencies and contractors.
3.1.12 Technical Direction Letters (TDLs). When necessary, technical direction or clarification concerning the details of specific tasks set forth in the contract and the TOs will be given through issuance of written TDLs. TDLs will not, in any manner, alter the scope of the contract or TO. For further direction see Clause 5252.242-9502 TECHNICAL
DIRECTION (May 2011) in Section H.
3.2 Security.
3.2.1 Citizenship Requirements: Only U.S. citizens may perform under this Contract. 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 should include:
a. The individual's name, date, and place of birth; position title; and current citizenship.
b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.
c. A statement of the unusual expertise possessed by the applicant.
d. A statement that access will be limited to a specific government contract (specify contract number).
e. 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 SECNAV 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.
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 controlled unclassified information and materials.
All CUI shall be appropriately identified and marked as For Official Use Only (FOUO) IAW
DoDM 5200.01, Information Security Program: CUI Volume 4 (enclosure 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 DoDM 5200.01 DoD Information Security Program: CUI Vol. 4 enclosure 3 pages 11-18 available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.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.
All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):
Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD
Contractors only (Critical Technology) (dated - _______). Other requests shall be referred to:
Commander, Naval Air Systems Command, Attn: (Program/User Agency mailing address).
3.2.2.2 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 Classification Specification Form.
Contractor personnel shall require access to classified information in performance of this contract up to and including (__________), with a safeguarding level of (__________). The
Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated IAW DoDM 5220.22 National Industrial Security Program Operating
Manual (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.
3.2.2.3 Security Clearance Information: 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
Technical Point of Contact (TPOC)/COR of this contract for approval.
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 DoDM 5200.01 DoD Information Security Program: CUI Vol. 4 enclosure 3 pages 11-18 available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.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.
The Contractor shall be responsible for employing personnel having at least the minimum level of security clearance as stated under each labor category specified herein.
Labor Category
DoD Security
Clearance Level
(Interim Clearance
Acceptable)
Required Days After
Issuance of TO
General and Operations Manager*, Senior, 11-1021
Top Secret with current Favorable
SSBI
Upon Award
Aerospace Engineer, Senior, 17-2011 Secret Upon Award
Aerospace Engineer*, Journeyman, 17-
Secret Upon Award
Electrical Engineer (Systems Engineer)*, Senior, 17-2071
Top Secret with current Favorable
SSBI
Upon Award
Electrical Engineer (Systems Engineer), Journeyman, 17-2071
Top Secret with current Favorable
SSBI
Upon Award
Electrical Engineer (Electrical Systems
Engineer/Scientist), Junior, 17-2071
Secret Within ninety (90) days of Award http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf
Labor Category
DoD Security
Clearance Level
(Interim Clearance
Acceptable)
Required Days After
Issuance of TO
Electrical and Electronic Engineering
Technician, Senior, 17-3023
Top Secret with current Favorable
SSBI
Upon Award
Materials Engineer, Senior, 17-2131 Secret Upon Award
Materials Engineer, Journeyman, 17-2131 Secret Upon Award
Mechanical Engineer (Systems Engineer), Senior, 17-2141
Top Secret with current Favorable
SSBI
Upon Award
Mechanical Engineer (Systems Engineer), Journeyman, 17-2141
Top Secret with current Favorable
SSBI
Upon Award
Mechanical Engineer (Systems Engineer), Junior, 17-2141
Secret Within ninety (90) days of Award
Engineer (Systems Engineer)*, Senior, 17-
Top Secret with current Favorable
SSBI
Upon Award
Engineer (Systems Engineer), Journeyman, 17-2199
Top Secret with current Favorable
SSBI
Upon Award
Engineer (Systems Engineer), Junior, 17-
Secret Within ninety (90) days of Award
Operations Research Analyst, Senior, 15-
Top Secret with current Favorable
SSBI
Upon Award
Operations Research Analyst, Journeyman, 15-2031
Secret Upon Award
Software Developer, Senior, 15-1252 Top Secret with current Favorable
SSBI
Upon Award
Software Developer*, Journeyman, 15-
Top Secret with current Favorable
SSBI
Upon Award
Information Security Analyst, Senior, 15-
Top Secret with current Favorable
SSBI
Upon Award
Logistician, Senior, 13-1081 Secret Upon Award
Technical Writer, Journeyman, 27-3042, SCA 30462
Secret Upon Award
Management Analyst (Program/Project)*, Senior, 13-1111
Top Secret with current Favorable
SSBI
Upon Award
Labor Category
DoD Security
Clearance Level
(Interim Clearance
Acceptable)
Required Days After
Issuance of TO
Management Analyst (Configuration), Journeyman, 13-1111
Secret Upon Award
Management Analyst (Project)*.
Journeyman, 13-1111
Secret Upon Award
Financial Analyst, Senior, 13-2051 Secret Upon Award
All personnel within the labor category should have the requested clearance level within the requested number of days after TO issuance.
*Indicates Key Personnel are part of this labor category. Number of Key Personnel for each category are listed in SOW/PWS paragraph 3.4.2.
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 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.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf.
SAAR-N forms shall be submitted to the COR, Government Technical Point of Contact (TPOC), or to the assigned Government Trusted Associate Sponsorship System (TASS) Trusted
Associate.
3.2.3.2 Common Access Card (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 and shall conform to the Defense Manpower Data Center (DMDC) Trusted Associate Sponsorship System (TASS)
Overview Guide Version 5.3.2, Dec 2014. All CACs and identification badges issued to
Contractor employees shall be returned to the Government Security Department at the
Government site IAW the DMDC TASS Overview Guide Version 5.3.2, Dec 2014 following completion of the Contract; relocation or termination of an employee; or upon request from the
COR. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract.
Badge Requirements – More than ninety (90) Days
If a Contractor is assigned for more than ninety (90) days, a CAC badge will be issued from the appropriate Base Security Office. The TASS form shall be completed and submitted to a designated Trusted Agent (TA) if personnel are on base for more than ninety (90) days and require access to Government IT systems.
Badge Requirements – Less than ninety (90) Days
If a Contractor is assigned for ninety (90) days or less, a badge will be issued from the appropriate Base Security Office. The badge shall have the expiration date that shall coincide http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf with the expiration date of the individual’s tenure at the Government Facility while working 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 FOUO.
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.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 Controlled Unclassified Information
(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 SOW/PWS Paragraph 3.2.5.
3.2.4.1 Marking: All information generated by the Contractor shall be properly marked. FOUO information generated or provided under this Contract shall be marked IAW DoDM 5200.01.
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: Any controlled information pertaining to this contract shall not 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 appropriate U.S. Government (USG) authority. Proposed public releases shall be submitted for approval prior to release through the NAWCAD Public Affairs Office, 47123 Buse Road, RASM
William A. Moffett Building, Patuxent River, MD 20670-1547.
3.2.4.3 Loss, compromise, and electronic spillage of classified information or CUI: All instances of loss, compromise, and electronic spillage of classified information or CUI shall be reported to the COR, TPOC, 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
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 on board NAVAIR or NAVAIR sites, the Contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts.
Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. 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.
3.2.5.1 The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information and to control distribution of controlled unclassified and classified information IAW DoD 5220
NISPOM and DoD 5200.1-R Information Security Regulation.
3.2.5.2 The Contractor shall submit an Operations Security Plan. While performing onboard
NAVAIR sites, the Contractor shall comply with the provisions of NAWCADINST 3432.1B. At all other sites, the Contractor shall comply with the local command and program OPSEC plan.
All Contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents; classified equipment and materials; and other equipment and materials. Additional requirements are further amplified within Block 13 of the DD-254. (CDRL
A010)
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 or Continuity of Operations Plans.
Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and 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 Off-site Contractor support IA requirements. The Contractor shall use DoDI
8500.01 Series Cybersecurity to exercise due-diligence in ensuring IA tenets of confidentiality, integrity, availability, authentication, and non-repudiation are applied to integration design efforts, as required.
3.2.7.1 Contractor Owned Contractor Operated (CO/CO) Networks: The Contractor shall ensure that CO/CO Networks and Information Systems that process, store, display, manipulate, or transmit unclassified Government Program data comply with the protective measures IAW
DoD Directive Type Memorandum (DTM) 08-027, 31 July 2009, Security of Unclassified DoD
Information on Non-DoD Information Systems. Contractor owned information systems that process, store, display, manipulate, or transmit classified Government information shall be
Certified and Accredited by the appropriate Designated Approving Authority, Defense Security
Service (DAA DSS).
3.2.7.2 Electronic transmittal of CUI: The Contractor shall comply with DoD Directive 8520.2
Public Key Infrastructure (PKI) and Public Key (PK) Enabling when transmitting CUI that has not been cleared for Public Release.
3.2.8 On-site Contractor support to include IA support.
The Contractor shall support and perform tasks to protect AD-4.11.6 information and information systems using the principles of “due diligence” and “due care.” The Contractor shall ensure the IA tenets of Confidentiality, Integrity, Availability, Authentication, and Non-
Repudiation are integrated throughout AD-4.11.6 information systems beginning with inception and concluding with retirement or termination as appropriate. The Contractor shall ensure compliance with the following IA policies and procedures for the protection of information and information systems that they have administrator permissions:
̶ DoDI 8510.01 Series, Risk Management Framework For DoD Information Technology.
̶ DoD IA Certification and Accreditation Process (DIACAP), and DODI 8500.01 Series, Cybersecurity.
̶ Public Key Infrastructure and Public Key Enabling, DoDI 8520.2 Series.
̶ Cyberspace Workforce Management, DoDD 8140.01 Series.
̶ Cybersecurity in the Defense Acquisition System, DTM-17-001 Series.
̶ Navy IA Program, SECNAV M-5239.1 Series.
3.2.8.1 IA Training: The Contractor shall complete and document annual IA training IAW IA
Training, Certification, and Workforce Management, DoDD 8570.01, 23 Apr 07. The Contractor shall provide status documentation within one (1) working day when requested by the
Government.
3.2.8.2 Contractor Owned Contractor Operated (CO/CO) Systems Processing Government
Information: The Contractor shall ensure that CO/CO Networks and Information Systems that process, store, display, manipulate, or transmit Unclassified Government Program data comply with the protective measures IAW DoD Directive Type Memorandum (DTM) 08-027, 31 July
2009, Security of Unclassified DoD Information on Non-DoD Information Systems. Contractor owned information systems that process, store, display, manipulate, or transmit classified
Government information shall be Certified and Accredited by the appropriate DAA DSS.
3.2.8.3 Email transmission of CUI: The Contractor shall ensure that when transmitting CUI, over non-secure e-mail (e.g. not connected to the NMCI network through Broadband
Unclassified Remote Access System/Virtual Private Network (VPN)), those transmissions are encrypted using DoD PKI IAW Public Key Infrastructure and Public Key Enabling, DoDI
8520.2, 1 Apr 04.
3.2.8.4 IA and IT workforce: The Contractor shall ensure that IA and IT personnel are properly trained and certified in compliance with DoD 8570.01-M, Information Assurance Workforce
Improvement Program, 19 Dec 2005.
3.3 Detailed support.
The following section specifies the performance objectives and performance elements for the
Contract. The following subparagraphs describe the tasks and functions to be accomplished under the Contract.
3.3.1 Scientific and engineering support. Non-performance-based tasking.
3.3.1 (a) (CLINs 0001, 0002, 0011, 0012). Provide scientific and engineering support. Research, develop, prototype, evaluate, and establish the performance capabilities of Contractor or
Government…
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 .