DRAFT LCS SOW.docx

STATEMENT OF WORK

LIFE CYCLE SUSTAINMENT

Scope.

The Naval Air Warfare Center Aircraft Division (NAWCAD) Webster Outlying Field (WOLF) Special Communications Mission Solutions (SCMS) Division integrates, delivers, and sustains products for Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems. SCMS provides in-service engineering for C5ISR systems onboard small and large craft, commercial and militarized vehicles, transit cases, mobile communications, fixed base stations, command centers and intelligence systems. These C5ISR products are funded by a broad range of customers including Navy, Special Operations Forces (SOF), Homeland Security, and other Department of Defense (DoD) and non-DoD agencies. SCMS Division will utilize this contract to obtain specific disciplines associated with in-service engineering, logistical support, and training.

This Statement of Work (SOW) scope includes the Life Cycle Sustainment (LCS) of C5ISR systems including in-service and engineering support, Integrated Product Support (IPS), technical data and configuration management, and technical and project management support. Systems consist of but are not limited to Radio Frequency (RF) communications systems, antenna systems, baseband audio/video data systems, signal routing/patching/monitoring, Communications and Electronic (C-E) remote control, Information Technology (IT), power/signal distribution, Audio Video (AV) and Video Teleconference (VTC) systems (referred to as systems/subsystems throughout the remainder of this SOW). This includes legacy, current, and future C5ISR systems and the in-service engineering support, integrated product support and C-E equipment/systems and subsystems training, and technical data and configuration management support of those systems/subsystems.

Applicable Documents.

The following documents and document sources are provided for reference. The SCMS Division requirement to provide C5ISR interoperability among United States (US) military, US civilians, and foreign users may dictate an adherence to a wide variety of specifications and standards. DoD systems shall adhere to the Joint Technical Architecture (JTA) 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.

DoD standards.

SECNAV M-5510.36, Information Security Program DoDM 5200.01, DoD Information Security Program: Controlled Unclassified Information (CUI) DoDM 5400.07, Freedom of Information Act (FOIA) Program DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, 15 Oct 2018.

SECNAV M-5510.30, Personnel Security Program OPNAVINST 3440.17A, Navy Installation Emergency Management Program MIL-STD-810 Environmental Engineering Considerations and Laboratory Tests MIL-STD-1472 Human Engineering MIL-STD-31000 Technical Data Package MIL-STD-882 Department of Defense Standard Practice for Systems Safety MIL-STD-400521-2A Department of Defense Standard Practice for Technical Manuals DoD-STD-2106 Development of Shipboard Industrial Test Procedures DoD and/or Military, e.g. DoD-STD and MIL-STD Electronic Series.

DoD handbooks.

MIL-HDBK 502A DoD Handbook Product Support Analysis MIL-HDBK-61 Configuration Management Guidance MIL-HDBK-237 Electromagnetic Environmental Effects and Spectrum Supportability Guidance for the Acquisition Process.

DoD instructions.

NASPAXRIVERINST 5100.35 Occupational Safety and Health Program.

SECNAVINST 5000.2 Implementation of Defense Acquisition Management Policies, Procedures, Documentation, and Reports.

OPNAVINST 3432.1 Operational Security Plan (OPSEC).

USSOCOM 70-1 Acquisition Management System Policy Other Government documents.

American National Standards Institute (ANSI) American Society of Mechanical Engineering (ASME) Standards Association of Public-Safety Communications Officials (APCO) – International – Standards Other Government documents.

Clinger Cohen Act DoD 5220.22-M, National Industrial Security Program Operating Manual, (NISPOM) Department of Defense Product Support Manager Guidebook Department of Defense Logistics Assessment Guidebook Department of defense Product Support Business Case Analysis Guidebook United States Special Operations Command 700-2, MFP-11 Funded Asset Visibility and Accountability Electronic Industries Association (EIA), e.g. Recommended Standards RS Series European Telecommunications Standards Institute (ETSI) Federal, e.g. FED-STEP, FIP Series Federal Communications Commission Federal Motor Vehicles and Carrier Safety Standard and Regulations Institute of Electrical and Electronic Engineers (IEEE) International Standards Organization (ISO) International Telecommunication Satellite Organization (INTELSAT) International Telecommunications Union (ITU), Formerly the CCITT Joint Technical Architecture (JTA) Current Version National Institute of Standards and Technology National Television Standards Committee (NTSC) Society of Automotive Engineers, Inc. (SAE) Handbook Telecommunications Industry Association (TIA) International Traffic and Arms Regulations (ITAR) Requirements.

General requirements.

Compatibility. The Contractor shall maintain the capability to prepare documents compatible with the Government Information Technology (IT) environment through the security classification of Top Secret. The current operating environment required for this Contract is identified in the SCMS Division Research, Development, Test, & Evaluation (RDT&E) Local Area Network (LAN) Standard Operating Procedures (SOP) for both Contractor site and Government site staff (Attachment X).

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 LAN communications with the SCMS Division. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the SCMS Division during working hours, whether at Contractor work site or on travel.

Work location and facilities.

Government site requirements. Contractors performing support on Government sites will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, and network access including web servers, applicable databases, and/ or other applications necessary to carry out assigned tasks.

Contractor site requirements. The Contractor shall provide its own support facilities to perform the tasking of this Contract within fifty (50) ground transportable miles of WOLF, St. Inigoes, MD in order to satisfy the daily technical and management operations of this Contract. The Government will not assume responsibility to retain the facility or take control of the title after the Contract is completed.

The Contractor’s main facility only shall contain assembly, test, and storage space, as well as attendant office space for the support staff (historically at 25,000 square feet). Considering integration materials will be provided by the Government to the Contractor.

The Contractor shall provide all equipment and office/facility furnishings to support the SOW requirements for Contractor site requirements. It is anticipated that the cost of the facilities will be proposed as an indirect charge to the Government, and the facility may not be located on Government property.

Reserved.

Special Facilities – Field Technical Units (FTUs) The following have been identified as current or projected support sites under this contract. Specific FTUs will be defined at the task order level.

The following have been identified as locations where the contractor may provide on-site support:

The Contractor shall provide access to unclassified office, laboratory, and integration space for Government personnel to support work coordination requirements. Specific FTUs will be defined at the task order level within CONUS. The list below represents the current anticipated need, however, is not all inclusive:

· Located at the contractor provided FTU in Fayetteville, NC (historically approximately 600 square feet)

· Located at the contractor provided FTU in San Diego, CA (historically approximately 600 square feet)

· Located at contractor provided FTU in Chesapeake, VA (historically approximately 200 square feet)

The contractor is required to have liaison office(s) within 50 driving miles of WOLF St. Inigoes, MD.

Contractor facilities are required to have Top Secret security clearance and controlled access work areas as specified in the DD254 form attached hereto.

Contract Status Reporting. The Contractor shall provide the following documentation.

Segregation of Cost and Invoice Requirements Report. The Contractor shall provide deliverables In Accordance With (IAW) the Contracts Data Requirements Lists (CDRLs). (CDRL A001) Financial Progress Report. (CDRL A002) Contractor’s Personnel Roster - Workforce Report. (CDRL A003) Work schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.

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 the legal holidays specified in paragraph 3.1.4.1.2), with the flexibility to start as early as 0600/0630 and end as late as 1800, Monday through Friday.

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

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 COR/Alternate COR (ACOR). The overall schedule must be provided to the COR.

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.

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 Procuring Contracting Officer (PCO) must concur with any determination that work being performed by Contractor personnel is mission essential.

Overtime. Overtime shall be IAW Section I Clause 52.222-2 Payment for Overtime Premiums.

Other Direct Costs (ODCs). (CLIN 0007) 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 are expected to include the forty-eight (48) CONUS states, the District of Columbia (D.C.), and Canada. OCONUS locations include Afghanistan, Alaska, Bahrain, Germany, Guam, Hawaii, Italy, Kuwait, Philippines, Japan, U.S. Territories, United Kingdom, Qatar, and South Korea; this list is not all inclusive as locations may change over the life of the Contract.

The COR/ACOR shall approve all travel performed in support of this Contract prior to the commencement of the travel and result in a trip report. (CDRL A004) Possible travel locations include those that are within the United Stated 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.

Synchronized Pre-Deployment and Operational Tracker (SPOT). The Contractor may travel in USCENTCOM 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 to generate LOA.

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.

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. The Contractor shall not make commitments to procure material without proper approval and sufficient funding allocated to the TO. All materials not depleted during the performance of this Contract shall become Government property upon completion of this Contract. 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.

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 shall flow down to subcontractors providing support under this Contract.

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/give the perception of personal services.

Transition out strategy. The Contractor’s overall transition out strategy shall be built around maintaining the mission of the SCMS 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) 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 on the current Contract shall establish and maintain effective communication with the incoming Contractor or Government personnel for the period of transition via weekly status meetings.

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.

Risk mitigation strategies. The Contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

Data/information transfer. The Contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

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.

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.

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 SCMS 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) and COR 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.

If the Contractor is involved in an accident while operating a Government owned or leased vehicle, they shall notify the GPL, the PCO, and the COR within twenty-four (24) hours and shall provide an accident report within forty-eight (48) hours. (CDRL A006) 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.

Security.

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: the individual's name, date and place of birth, position title, and current citizenship. The waiver should also include 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.

Investigative requirements.

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.

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 with DoD 5220.22-M, National Industrial Security Program Operating Manual (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 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 – 26 June 2019). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: SCMS Division, St. Inigoes, B8185 Unit 11, 17100 Webster Field Road, St. Inigoes MD 20684-4009.

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.

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 (i.e. CUI, FOUO, or 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.

Contractor personnel labor category security requirements. The Contractor shall obtain Interim Top Secret clearances sixty (60) days after TO award for the following labor categories. All other personnel needed to work on Government sites or have access to Government systems shall have interim Secret clearances thirty (30) days after TO award.

First-Line Supervisors of Production and Operating Worker

Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).

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: https://www.public.navy.mil/surfor/ccsg11/Documents/CCSG11_OPNAV_5239_14SAAR_N.pdf. SAAR-N forms shall be submitted to the COR, GPL, or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate (TA).

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

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.

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 when work is performed at the Contractor’s facility. If the work is performed at the Government’s facility, the Contractor shall comply with facility security procedures and controls.

Marking. All information generated by the Contractor shall be properly marked. FOUO information generated and 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.

Public release. 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.

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.

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:

1. Assignment of responsibility for OPSEC direction and implementation.

1. Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

1. Establishment of OPSEC education and awareness training.

1. Provisions for management, annual review, and evaluation of OPSEC programs.

1. 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. The contractor shall also 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. (CDRL A007) 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.

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 that all IT network or website access requirements after award of the Contract and shall be IAW the latest DoD policies and the SCMS RDT&E LAN Standard Operating Procedure (SOP). (Attachment X) 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.

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’ laptop/desk top computers to conduct daily work that meet all of the hardware, software, and standard architecture set forth in the SCMS RDT&E LAN SOP. Portable computers and laptops are not allowed to be connected to the SCMS RDT&E LAN. All Government site staff will require desktop computers to directly connect to the SCMS 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 SCMS RDT&E LAN. Approval is required by COR and SCMS Network Information Site Security Officer prior to connection. All connected desktops will be subject to continuous monitoring.

Navy Marine Corps Intranet (NMCI). Access to NCMI is not anticipated for this Contract. If determined to be necessary, the Government will provide all NCMI 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.

Detailed support.

In-Service and Engineering Support.

3.3.1 (a) (Procurement (PROC)) Perform life cycle planning and integrated product support of efforts to support the modernization and modification of LCS projects. Applicable to paragraphs 3.1.1-3.1.22

3.3.1 (b) (Operations and Maintenance (O&M)) Perform in-service support of both fielded and initial deployment phase LCS systems, including life cycle planning, training, and integrated logistics support. Applicable to paragraphs 3.1.1-3.1.22

3.3.1 (c) (Working Capital Fund (WCF)) Perform life cycle planning and integrated product support of efforts to support the modernization and modification of LCS projects. Perform in-service support of both fielded and initial deployment phase LCS systems, including life cycle planning, training, and integrated logistics support. Applicable to paragraphs 3.3.1.1-3.3.1.22

3.3.1 (d) (Non-Department of Defense (Non-DoD)) Perform life cycle planning and integrated product support of efforts to support the modernization and modification of LCS projects. Perform in-service support of both fielded and initial deployment phase LCS systems, including life cycle planning, training, and integrated logistics support. Applicable to paragraphs 3.3.1.1-3.3.1.22 The Contractor shall plan for, assess, and report on operational readiness problems and provide short-term and long-term solutions. (CDRL A008) The Contractor shall analyze technical problems, correct deficiencies, and provide engineering layouts, and solutions. (CDRL A010) The Contractor shall provide assembly, assimilation, verification, and repair services necessary to support in-service systems/subsystems.

The Contractor shall establish Field Technical Units (FTUs) when scheduled by the COR to facilitate assembly, assimilation, verification, and repair services in support of LCS project requirements.

The Contractor shall perform preventative and corrective maintenance actions to include troubleshooting to identify faults, determine specific interface or operations deficiencies, execute and report repair actions, and provide recommendations for retrofits. (CDRL A008) The Contractor shall deliver quick-reaction/quick-response support (within twenty-four (24) hours) along with engineering solutions for technical problems. (CDRL A008) The Contractor shall deliver specialized technical system support teams to address complex overhauls which may include hardware/software repairs, upgrades, modernizations, maintenance, and training actions based on system operations requirements. (CDRL A015) The Contractor shall assimilate, integrate, test and verify systems/subsystems and components.

The Contractor shall inspect failed parts, engineer and outline systems/subsystems and components necessary for optimization, retrofit or repair; perform preventative maintenance. (CDRL A010) The Contractor shall receive, inspect, and perform Stage 1 through Stage 7 production verification IAW DoD-STD-2106 for equipment and materials. (CDRL A018) The Contractor shall analyze, optimize, and make recommendations and/or report on equipment performance and maintenance data of systems/subsystems being mounted or installed into platforms such as: military or commercial ships or boats, military or commercial fixed or rotary wing aircraft, military or commercial shore-based platforms and facilities, and military or commercial vehicles. (CDRL A024) The Contractor shall simulate the operation of components to perform systems, subsystems, equipment integration verifications, electronic modeling, simulation, and animation. (CDRL A018) The Contractor shall validate equipment performance and reliability, maintainability, and availability data to prepare and recommend new performance baselines. (CDRL A018) The Contractor shall build and integrate modified or upgraded systems/subsystems hardware/software/firmware and user interfaces following the GPLs approved specifications, configuration layouts, Engineering Change Requests (ECRs), craft alterations, or Engineering Change Proposals (ECPs). (CDRL A021) The Contractor shall provide and deliver electronic reporting of all maintenance actions, repair part utilization and stock status, Reliability, Availability, and Maintainability (RAM) data, and historical information. (CDRL A024) The Contractor shall enter all maintenance actions into government provided automated inventory database.

The Contractor shall make recommendations on system/subsystem production, installation, layouts, processes, procedures, and documentation. (CDRL A019) The Contractor shall customize and deliver new performance baselines based on the data analyzed and documented; resolve or repair any causalities or deficiencies. (CDRL A008) The Contractor shall customize and deliver adaptive engineering solutions and/or modifications to systems/subsystems and electronic equipment to meet, urgent and non-urgent, operational requirements.

The Contractor shall draft and validate proposed system engineering modifications and/or upgrades as well as investigating emerging technologies. (CDRL A008) The Contractor shall analyze system operational readiness, maintenance data, and validate new technology to determine if layout revisions or incorporation of state-of-the-art technology will cost-effectively enhance readiness. (CDRL A019) The Contractor shall build, fabricate, integrate, and repair equipment, interface units, and test fixtures.

The Contractor shall prepare system tests and validations plans and procedures to ensure correct operation, compatibility with existing subsystems and equipment, and suitability. (CDRLs A016, A017) The Contractor shall arrange for special in-service or modernized system verification, such as shock, vibration and TEMPEST on systems/subsystems IAW military and commercial standards as specified by the GPL. (CDRL A008) Integrated Product Support (IPS) & Systems

The Contractor shall draft recommendations on the implementation of IPS elements such as: system interface, system modification, product support management, sustaining engineering, supply support, maintenance planning and management, supportability strategies, Packaging, Handling, Storage & Transportation (PHS&T), technical data, milestones, support equipment, training and training support, manpower and personnel, facilities and infrastructure, and IT resources. (CDRL A019) The Contractor shall customize and deliver logistics plans to ensure sustainability, continually improve products affordability, update the plan as technology and requirements change, and analyze and recommend levels of required readiness, including logistics factors associated with achieving readiness. (CDRL A019) The Contractor shall review systems/subsystems program logistic policies and procedures before implementation to ensure they comply with applicable standards, directives, and instructions, deliver implementation plan. (CDRL A023) The Contractor shall define, customize, and document appropriate maintenance and supportability plans to ensure efficient maintenance and supportability using maintenance planning concepts such as: Reliability Centered Maintenance (RCM), Condition-Based Maintenance (CBM), Condition-Based Maintenance Plus (CBM+), and Total Ownership Cost (TOC). (CDRL A019) The Contractor shall deliver supportability analyses and recommend strategies to ensure cost efficiency, analyses could include: Failure Mode, Failure Mode Effects and Criticality Analysis (FMECA), Fault Tree Analysis (FTA), Reliability Centered Maintenance Analysis (RCMA), Diminishing Manufacturing Sources Material Shortages (DMSMS), RAM, Level of Repair Analysis (LORA), Maintenance Task Analysis. (CDRL A008) The Contractor shall perform customization efforts that are concurrent with the system layout so that Integrated Logistics Support (ILS) options and trade-offs can be considered before the layout is frozen, and the optimum balance of logistics support elements can be achieved.

The Contractor shall provide support for identification of an operations and maintenance infrastructure to satisfy the organization and system operational and mission requirements.

The Contractor shall develop an operation and maintenance procedure for the system/subsystem. (CDRL A014) The Contractor shall prepare, maintain, and deliver training plans, course materials, quick reference guides, and materials. (CDRL A015) The Contractor shall deliver training to fleet, aircraft, ground mobile personnel, and in-service field users in areas designated by the GPL. (CDRL A015) The Contractor shall plan and perform formal classroom and on-the-job training. (CDRL A015) The Contractor shall deliver training courses: curriculums, web based training aides, and documentation for personnel based on training packages provided by the Government or commercial sources. (CDRL A015) The Contractor shall define a course curriculum based on identified train the trainer and user training requirements, including data received from manufacturers. (CDRL A015) The Contractor shall provide course material for all trainers and class participants, including comprehensive user packages including quick reference guides, component manuals, and system warranty information. (CDRL A015) The Contractor shall conduct in-house, on-site, and ad-hoc training as required to support end-user training needs, including final user guides, source code, manuals, drawings, equipment list, and warranty information. (CDRL A013) Technical Data & Configuration Management

The Contractor shall prepare and maintain configuration management plans using SCMS Division furnished criteria, configuration control of technical data and documenting the applicable procedures for identifying and controlling hardware and software components. (CDRL A021) The Contractor shall deliver technical and planning analysis and track centrally managed activities related to in-service or production system LCS responsibilities. (CDRL A019) The Contractor shall maintain/update physical configuration records for reviews and audits. (CDRL A020) The Contractor shall deliver engineering analysis for layout changes to implement solutions, technical improvements, and mandated system upgrades. (CDRL A024) The Contractor shall prepare, coordinate, and review Engineering Change Proposals (ECPs) and other configuration documentation for submission of recommended changes to the technical documentation. (CDRL A020) The Contractor shall review ECPs for technical accuracy and present ECPs at Change Control Board (CCB) meetings and related technical reviews with SCMS Division technical personnel.

The Contractor shall track ECP requests through the configuration control process, and attend configuration control board and related meetings when scheduled. (CDRL A008) The Contractor shall draft, update, correct, maintain, prepare, revise, and deliver operation and maintenance manuals, installation guides, technical manuals, and system technical documentation. (CDRL A014) The Contractor shall draft, update, correct, and revise engineering drawings and packages. (CDRL A011) Material and equipment procurement and control.

The Contractor shall provide technical support to recommend possible equipment and material and potential sources for LCS project specific requirements IAW efforts defined in resulting TOs. (CDRL A012) The Contractor shall perform market research per FAR Part 10 to identify potential sources capable of satisfying the Government’s operational and performance parameters.