Attachment 1 - Draft PSMI_MAC_SOW_.pdf
PDF 703 KB Posted
- Solicitation number
- N00421-21-RFPREQ-660000A-0001
About this file
This sources sought notice requests information from companies interested in providing sustainment-focused management services to support the Naval Air Systems Command Sustainment Group Product Support Management/Integration Department and Program Support offices. Services include program management and logistics support across the life cycle for weapon systems, subsystems, systems of systems, and support equipment. Responses are requested by April 30, 2021 to be considered for the follow-on multiple award contract. The notice provides background on the department and outlines the scope of services including general requirements, security, and detailed support requirements across logistics functions like product support management, engineering, supply, training, and configuration management.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Sources Sought - NSG_PSMI.pdf | ||
| Attachment 2 - Questionnaire.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Statement of Work (SOW) For
NAVAL AIR SYSTEMS COMMAND (NAVAIR) SUSTAINMENT GROUP
(NSG)-PRODUCT SUPPORT MANAGEMENT/INTEGRATION (PSMI) DEPARTMENT AND
PROGRAM SUPPORT MULTIPLE-AWARD CONTRACT (MAC)
Version 1
10 March 2021
DISTRIBUTION STATEMENT D: Distribution is authorized to the DOD and to U.S. DOD contractors only; Administrative or Operational Use, XX XXXXX XXXX. Other requests for this document shall be referred to NAVAIR NSG Product Support Management/Integration Department Bldg. 449, 47033 McLeod Road, Patuxent River, MD 20670.
TABLE OF CONTENTS
1.0 Introduction
1.1 Scope
1.2 Background……………………………………………………………………………
2.0 Applicable Documents
3.0 Requirements
3.1 General Requirements…………………………………………………………………….
3.1.1 Compatibility……………………………………………………………………………..
3.1.2 Work Location and Facilities…………………………………………………………….
3.1.3 Contract Status Reporting………………………………………………………………..
3.1.4 Work Schedules………………………………………………………………………
3.1.5 Other Direct Costs……………………………………………………………………
3.1.6 Subcontractors…………………………………………………………………………...
3.1.7 Management of Contractor Personnel………………………………………………..….
3.1.8 Transitioning Out Strategy…………………………………………………………
3.2 Security…………………………………………………………………………………..
3.2.1 Citizenship Requirements…………………………………………………………
3.2.2 Investigative Requirements………………………………………………………
3.2.3 Common Access Cards (CACs)/Public Key Infrastructure (PKI)/System Authorization
Access Request-Navy (SAAR-N)/DD-254………………………………………………………
3.2.4 Information Security (INFOSEC)……………………………………………………….
3.2.5 Operations Security (OPSEC)…………………………………………………….……..
3.2.6 Anti-Terrorism Force Protection Emergency Management……………………………..
3.3 Detailed Support Requirements…………………………………………………………
3.3.1 Product Support Management…………………………………………………………...
3.4 Logistics Requirements Funding Summary (LRFS)/Logistics Budgets………………
3.4.1 Logistics Requirement Funding Summary………………………………………….…...
3.4.2 Logistics Budgets………………………………………………………………………...
3.5 Statements of Work (SOW), Performance Based Specifications, and Contract………… Data Requirements Lists (CDRL)……………………………………………………
3.6 Life Cycle Sustainment Plan(S)(LCSP) User’s Logistics Support Summary(S) (ULSS).
3.7 Business Case Analysis (BCA)……………………………………………………………
3.8 Product Support Value Analysis…………………………………………………………..
3.9 Diminishing Manufacturing Sources and Material Shortages (DMSMS) Planning/Plan...
3.10 Item Unique Identification (IUID) Planning/Plan…………………………………………
3.11 Demilitarization Plan Support…………………………………………………………
3.12 Logistics Inputs to Acquisition Documentation…………………………………………..
3.13 Performance Based Logistics (PBL) Planning/Plans……………………………………..
3.14 Logistics Metrics and Readiness………………………………………………………
3.15 Manage In-Service Cost Wise Readiness……………………………………………….…
3.16 Facilities & Infrastructure and Site Activation………………………………………….…
3.17 Warfighter and Maintainer Requirements Capture…………………………………………
3.18 Supportability Test and Evalluation…………………………………………………………
3.19 Logistics Studies…………………………………………………………………………….
3.20 Product Support Performance Management………………………………………………..
3.21 Configuration Management…………………………………………………………………
3.22 Maintenance Planning and Management…………………………………………………...
3.23 Sustaining Engineering……………………………………………………………………..
3.24 Supply Support……………………………………………………………………………..
3.25 Packaging, Handling, Storage, and Transportation PHST)………………………………...
3.26 Technical Data……………………………………………………………………………...
3.27 Support Equipment/Tooling………………………………………………………………..
3.28 Training and Training Support……………………………………………………………..
3.29 Manpower and Personnel…………………………………………………………………..
3.30 Information Technology (IT) Systems Continuous Support……………………………
3.31 Design Interface…………………………………………………………………………...
4.0 Deliverables…………………………………………………………………………………...
5.0 Control of Contractor Personnel……………………………………………………………..
6.0 Government Furnished Property (GFP)…………………………………………………………..
7.0 Minimum Personnel Requirements.…………………………………………………
7.1 Personnel Qualifications………………………………………………………………….
7.2 Personnel Requirement Definitions………………………………………………………
7.3 Personnel Experience and Years of Experience…………………………………………..
7.4 Labor Catagories………………………………………………………………………….
7.4.1 Key Personnel…………………………………………………………………………….
Appendix A: Acronym List
1.0 INTRODUCTION: This contract requirement is a follow-on Multi-Award Contract (MAC) for sustainment-focused management services, which will support customers across NAVAIR. NAVAIR NSG PSMI Department is the Requirement Owner (RO) for this effort. NAVAIR Program Office sustainment teams and sustainment functional activities are the target users for this vehicle.
1.1 SCOPE: This SOW is intended to provide Integrated Product Support (IPS) program management and logistics support services in acquisition and sustainment for the life cycle of specified weapons systems, system of systems (SoS), sub-systems, and Support Equipment (SE). NAVAIR Program Offices, Echelon III Commands, and NSG Departments are planned customers for the services provided under this contract. These services will support multiple logistics functional leads, including PSMI Department, Program Office Product Support Managers (PSMs), Assistant Program Managers for Logistics (APMLs), respective Integrated Product Team (IPT) Deputy APMLs, Logistics Element Managers (LEMs), and Fleet staffs Resident Independent Logistics Support Detachments. Section
3.3 of the SOW defines the requirements for contract performance. Each Task Order (TO) Award will have its own SOW or Performance Work Statement (PWS) that will identify the specific Program Office and types of funds required. Specific tasking and associated data items will be defined at the TO level.
1.2 BACKGROUND: PSMI supports the NAVAIR acquisition and sustainment process for Naval Aviation weapons systems by providing trained logistics personnel for the execution of NAVAIRs Mission Aligned Organization Concept of Operations (CONOPS). The Sustainment Group provides the resources necessary to plan, manage, and integrate the design, development, acquisition, delivery, and sustainment of naval aviation weapons systems and products for PSMI, and other associated Program Offices. These products include the air vehicle, commodities and capabilities, propulsion system, training systems, SoS, SE and the product support packages to meet the Warfighters’ required availability at optimal life cycle costs (LCCs). In this capacity, the PSMI integrators provide policy, guidance, training and oversight of the logistics management and integration process and resources necessary to execute acquisition and sustainment of the product support system and the twelve product support elements. Additionally, PSMI has technical authority and oversight of product support acquisition and sustainment strategies to sustain naval aviation systems, weapon systems/SoS, its sub-systems and equipment within the Programs/Program Offices associated with PSMI. This technical authority provides Subject Matter Experts (SME) for evaluation and approval of product support strategies, products and support system performance through an array of technical forums, Systems Engineering Technical Reviews (SETRs), requirements reviews, readiness reviews, and Product Support management reviews. The PSMI logistics team members also participate in the Naval Aviation Enterprise (NAE) readiness and cost evaluation improvement review process responsible for development of the NAE Future Readiness activities for NAVAIR.
2.0 APPLICABLE DOCUMENTS: The following documents listed form a part of this SOW to the extent cited herein. The contractor shall comply with the below referenced documents unless otherwise specified within the body of this SOW. The contractor shall propose alternatives to the specifications and standards cited herein if it would enhance system performance or cost effectiveness, as necessary. The issues of non-Government standards are those in effect on the date of contract award. In the event of conflict between the documents referenced herein and the contents of this SOW, the order of precedence clause (52.215.8) of this contract shall apply. When, in the opinion of the contractor, a deviation from standards or requirements of this SOW is in order, the contractor shall make a request for deviation in writing to the Contracting Officer with an information copy to the designated technical representative.
Document Number Date Document Title SECNAVINST 4440.34 22 Dec 2009 Implementation of Item Unique Identification within the
Department of the Navy
SECNAVINST 5000.2F
26 Mar 2019
Department of the Navy Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System
SECNAV-M 5510.30 June 2006 DON Personnel Security Program SECNAVINST 5510.36B 12 Jul 2019 Department of the Navy Information Security Program
Department of Defense (DOD) Guide 1.2
28 Nov 2006 Guidelines for the Virtual Unique Item Identifier (UII) Version 1.2
Acquisition Technology and Logistics (AT&L) Memo
19 Jan 2017 Life Cycle Sustainment Plan Outline Ver. 2.0
OPNAVINST 1000.16L 09 Jan 2019 Navy Total Force Manpower Policies and Procedures OPNAVINST 34321.1 04 Aug 2011 Operations Security OPNAVINST 1500.76C 14 Aug 2013 Training Systems Requirements, Acquisition, and
Management
OPNAVINST 1540.2F 05 Aug 2008 Naval Aviation Technical Training Program Administration and Operations
DoD Directive (DODD) 5000.01
21 Aug 2018 The Defense Acquisition System
DODD 4720.05 31 Aug 2018 Military Construction (MILCON) DoDD 4630.05 23 Apr 2007 Interoperability and Supportability of IT and National
Security Systems (NSS) DODJTR 01 Jan 2021 DOD Joint Travel Regulations DOD FMR 7000.14R June 2017 Financial Management Regulation DOD Instruction (DODI) 8320.04
27 Aug 2019
Item Unique Identification (IUID) Standards for Tangible Personal Property
DODI 4140.01
06 Mar 2019
DoD Supply Chain Materiel Management Policy
DODI 4151,19 31 Aug 2019 Serialized Item Management (SIM) for Life-Cycle Management of Materiel
DODI 4160.28
31 Aug 2018
DoD Demilitarization (DEMIL) Program.
DODI 4161.02 31 Aug 2018 Accountability and Management of Government Contract Property
DoDI 5000.02T 31 Dec 2020
Operation of the Defense Acquisition System
DODI 5000.67 31 Aug 2018 Prevention and Mitigation of Corrosion on DoD Military Equipment and Infrastructure
DODI 5000.64 10 June 2019 Accountability and Management of DoD Equipment and other Accountable Property
DoDI 5200.48 03 Nov 2020
Controlled Unclassified Information (CUI)
DODI 5230.09 25 Jan 2019 Clearance of DOD Information for Public Release DoDI 5230.24 15 Oct 2018
Distribution Statements on Technical Documents
DOD Manual (DODM) 4160.21-M
02 Oct 2019 Defense Materiel Disposition Manual
DODM 1000.13 Vol.1 23 Jan 2014 DOD Identification Cards: ID Card Life-Cycle DODM 5010.12-M May 1993 Procedures for the Acquisition and Management of
Technical Data DODM 5200.01 28 July 2020 DOD Information Security Program: Protection of
Classified Information DoDM 5220.22 01 Aug 2018 National Industrial Security Program Operating Manual.
CJCSI 6212.01E 15 Dec 2008 Interoperability and Supportability of IT and National
Security Systems National Security Decision Directive (NSDD) 298
22 Jan 1988 National Operations Security Program
NAVAIRINST 11000.1 12 Jun 2013 Identification and Documentation of Facility Requirements in Support of Naval Aviation Weapons Systems
NAVAIRINST 13650 1E 10 Apr 2017 NAVAIR Aircraft Maintenance Material Readiness List Program (AMMRL)
NAVAIRINST 4130.1E 19 Dec 2006 Naval Air Systems Command Configuration Management Process
NAVAIRINST 4790.22 18 Aug 2017 Design Interface Maintenance Planning Program NAVAIRINST 5215.12B 16 Dec 2013 Technical Directive System NAVAIR Clause 5252.232- 9509 Oct 2013 Travel Approval and Reimbursement Procedures
(NAVAIR)
TA-HB-0007-1 01 May 2013 Logistics Product Data (LPD) Reports Handbook NAVAIR-M-13650.1 10 Apr 2017 NAVAIR AMMRL Program Manual
TA-STD-007 Oct 2006 Introduction to GEIA-STD-0007
LPD
N/A Dec. 2011 Integrated Product Support (IPS) Element Guidebook CNAFINST 4790.2 15 Jan 2017 The Naval Aviation Maintenance Program (NAMP) CNAFINST 4790.22 15 Jun 2013 Maintenance Plan Program MIL-DTL-81919C 26 Nov 1997 Manuals, Technical: Equipment Operation and/or
Maintenance Instructions, Technical Content Requirements (Work Package Concept)
MIL-DTL-81927C 26 Nov 1997 Manuals, Technical: Work Package Style, Format, and Common Technical Content
MIL-DTL-81928C 26 Nov 1997 Manuals, Technical: Aircraft Maintenance Instructions, Technical Content Requirement (Work Package Content)
MIL-DTL-81929C 26 Nov 1997 Manuals, Technical: Illustrated Parts Breakdown Figures:
Technical Content Requirements (Work Package Content)
MIL-DTL-8130G 31 Mar 2008 Manuals, Technical: Airborne Weapons Stores Loading/Weapons Assembly/SE Configuration
MIL-DTL-82769A 15 Aug 2000
Support of Database, Revisable Interactive Electronic Technical Manuals
SAE-EIA-649-1A 10 Aug 2020 Configuration Management Requirements for Defense Contracts
SAE EIA-649-B 01 Apr 2014 Standard for Configuration Management SAE EIA-649C 07 Feb 2019 Configuration Management Standards SAE GEIA STD 0007B 01 May 2013 LPD Handbook GEIA-649-HBA 01 Jan 2005 Configuration Management Standard Implementation
Guidance MIL-HDBK-502A 8 Mar 2013 Product Support Analysis MIL-HDBK-2097A 23 July 1997 Acquisition of SE and Associated Integrated Logistic
Support (ILS) MIL-HDBK-3001 07 May 2006 General Style and Format of U.S. Navy Work Package
Technical Manuals MIL-STD-3001 Pts 1-8 01 Dec 2016 Digital Technical Information for Multi-Output
Presentation of Technical Manuals
MIL-STD-2073-1E Apr 2019 Standard Practice for Military Packaging
MIL-STD-3007G 01 Nov 2019 Unified Facilities Criteria, Facilities Criteria, and Unified Facilities Guide.
MIL-STD-3034 REV A Note
15 Apr 2019 Reliability-Centered Maintenance (RCM) Process
MIL-STD-38784B 16 Aug 2020 General Style and Format Requirements for Technical Manuals http://www.navair.navy.mil/logistics/4790/library/contents.pdf https://teamworkflow.navair.navy.mil/cyberdocs/portalFiles/EDM_docs_view.asp?altentry=y&doc=195720&app=Directives
MIL-STD-40051-1C 15 Dec 2015 Standard Practice for Preparation of Digital Technical Information for Interactive Electronic Technical Manuals ( IETMs)
14 CFR 1 Jan 2004 Code of Federal Regulations: Federal Aviation Administration
FAR Part 45 and 52.245-1 01 Apr 2020 Federal Acquisition Regulation: Government Property FAR Part 48 and 252.204-
01 Oct 2015 Safeguarding Covered Defense Information and cyber incident Reporting
FAA Order 8110.101 25 Feb 2015 Type Certification Procedures for Military Aircraft SD-22 29 Jan 2016 Diminishing Manufacturing Sources and Material
Shortages (DMSMS) Handbook MCO 3125.1B 30 Apr 2009 Marine Corps Flying Hour Program (FHP)
COMNAVAIRFORINST
35001.
18 Sept 2012 Squadron Training and Readiness
COMNAVAIRFORINST
4440.2 N41
10 Mar 2006 Supply Operations Manual
ASD-S1000D 24 Jan 2005 International Specification for Technical Publications Utilizing a Common Source Data Base
DOD Guidebook 23 Dec 2019 Product Support Manager’s (PSM) Guidebook DOD Guidebook 22 Sep 2020 Defense Acquisition Guidebook NAVAIR 00-25-100 2014 NAVAIR Command Technical Publications Library
Management Program NAVAIR 00-25-300 Jan. 2009 Naval Air Systems Command Technical Directives
System NAVAIR 00-25-604 15 Feb 2008 Naval Air Systems Command Fleet Support/Integrated
Program Team Acquisition and Sustainment of NAVAIR Technical Manuals
NASPAXRIVERINST
5510.15Q
07 Mar 2012 Regulations Governing Admission to NAS Patuxent River, Webster Field Annex, and Navy Recreation Center Solomon’s
SAE TA STD 0017A 26 Apr 2014 Product Support Analysis ISO/ISEE/IEC 15288 2015 Framework for System Life Cycle Processes DoD Guidebook 01 Mar 2014 DAU Product Support BCA Guidebook UFC 1-200-01 01 Oct 2020 DoD Building Code UFC 1-300-01 18 Jul 2018 Criteria Format Standard UFC 1-300-02 01 Apr 2019 Unified Facilities Guide Specifications (UFGS) Format
3.0 REQUIREMENTS:
3.1 GENERAL REQUIREMENTS
3.1.1 Compatibility-The contractor shall maintain the capability to prepare documents and software (SW) packages compatible with the Government IT environment through the security classification substantiated by the requiring Activity at TO level. The current IT operating environment required for this contract includes:
• Microsoft Windows 10
• Microsoft Project 2010
• Microsoft Office Professional Plus 2010
• Adobe Acrobat XI (reader)
• Internet access with capabilities defined by the RO at TO level.
The contractor shall maintain the ability to interface with and transfer data to and from requiring activity office SW applications and their upgraded versions. The contractor shall ensure that all media are virus free when delivered.
The contractor shall be capable of Internet and LAN communications with the requiring activity. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the requiring activity during working hours whether at contractor work site or on travel.
3.1.2 Work Location and Facilities
3.1.2.1 Work location-The percent of work to be performed at a Government site and the percent of work to be performed at contractor site will be determined by the requiring activity at the TO level. Contractors performing on-site support may be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access, as necessary to carry out assigned tasks. Specific support needs will be determined at the TO level.
3.1.2.2 Meeting support- In support of the tasking outlined in this SOW, the contractor shall have the capability to host and conduct meetings at the classification levels as determined by the requiring activity at TO level. The contractor shall have the capacity to furnish telephone and Video Teleconference (VTC) capability, sufficient equipment to conduct meetings with presentations, include compatible software as required in Paragraph 3.1.1, and support a quantity of persons as determined by the requiring activity at the TO level. This support shall be provided at locations as determined by the requiring activity at the TO level.
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 progress and financial status report in accordance with the CDRL provided at the TO level. The report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category as well as material and travel costs.
3.1.4 Government Installation Work Schedules- (to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure). Refer to Section H “Special Contract Requirements” clause 5252.211-9502. To be determined at TO level.
3.1.4.1 Work schedules- The contractor shall provide the required services and staffing coverage during normal working hours at local times (except on the federal holidays specified in paragraph 3.1.4.1.2). Normal working hours will be determined by the requiring activity at the TO level.
3.1.4.1.1 CWS- CWS is an alternative work schedule to the traditional five 8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday (Determined by the Government, is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other.
Unless otherwise prohibited by the requiring activity at the TO level, the contractor may allow its employees to work a CWS schedule provided the requirements of this 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 as required by the Government to the Assistant Contracting Officer’s Representative (ACOR)/Contracting Officer’s Representative (COR).
3.1.4.1.2. Holidays: The Government observes the following holidays:
• New Year’s Day, January 1
• Martin Luther King’s Birthday, the third Monday in January
• President’s Birthday, 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
• Veteran’s Day, November 11
• Thanksgiving Day, the fourth Thursday in November
• Christmas Day, December 25
3.1.4.1.3 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 must concur with any determination that work being performed by contractor personnel is mission essential.
3.1.4.1.4 Overtime- Overtime cannot be charged directly to the contract unless first approved in writing by the Chief of the Procurement Office.
3.1.5 Other Direct Costs (ODCs) – Travel and Material
3.1.5.1 Travel- Travel may include general and administrative expenses but shall not include profit. Temporary travel to local and long distance locations, including in Continental United States (CONUS) and Outside of the Continental United States (OCONUS), may be required for this effort. Required travel, including locations, shall be determined by the requiring activity at the TO level.
All travel and material expenses shall be authorized by the COR. Only those travel expenses having valid receipts and travel claims shall be reimbursed to the contractor as ODCs. Travel shall be reimbursed at cost in accordance with Department of Defense Joint Travel Regulations and NAVAIR Clause 5252.232-9509, “Travel Approval and Reimbursement Procedures (NAVAIR) (OCT 2013)”. Reimbursement of local travel expenses by the contractor or subcontractor shall not be authorized.
3.1.5.2 Material - The contractor may be required to provide material and supplies. The contractor shall purchase miscellaneous supplies and Hardware (HW) for report publication and dissemination and other equipment, supplies, reproduction, special binders, indexes, inserts, special packing and shipping, mailings, long distance telephone calls, and transparencies in support of this effort through ODC’s. All material expenses shall have prior written approval from the COR. Any material expenses incurred without said prior approval will not l be reimbursed to the contractor.
3.1.5.3 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.
3.1.5.4 All travel and material costs shall be reported in the monthly expenditure report in accordance with the CDRL provided at the TO level.
3.1.5.5 The Government estimates for ODCs are based on not-to-exceed amounts. Travel and Material ODCs will be determined at the TO level.
3.1.6 Subcontractors - Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract.
3.1.7 Management of Contractor Personnel - The Government will not supervise contractor employees. The Government will interface with the contractor’s appointed (on-site) Lead for each TO to review day-to-day technical tasking and progress within the scope of the TO. The Government will provide the contractor’s Lead technical feedback on work performed pursuant to a TO. The contractor shall prepare employee work schedules. 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’s overall transition out strategy shall focus on maintaining the requiring activity’s organizational mission as defined at the TO level, 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 in accordance with the CDRL provided at the TO level.
Work Turnover: Once substantiated by the requiring activity at the TO level, 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. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.
• Quality Assurance: Once determined by the requiring activity at the TO level, 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.
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:
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. 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)), 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 CUI and to control distribution of CUI in accordance 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 in accordance with DoD Instruction 5200.48, (CUI).
CUI including 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 DoD Instruction 5200.48, CUI available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3.
All controlled unclassified technical information shall be appropriately identified and marked with the appropriate distribution statement(s). The distribution statement(s) will be determined at TO level.
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 TOP SECRET, with a safeguarding level defined in DODM 5200.01 and DODI 5230.09. The contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. 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.
CUI including 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 DoD Instruction 5200.48, CUI available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3.
3.2.3 Common Access Cards (CACs)/Public Key Infrastructure (PKI)/System Authorization Access Request Navy (SAAR-N).
3.2.3.1 SAAR-N: All contractor personnel requiring access to Government IT systems shall have an approved SAAR-N Form 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, TPOC, or to the assigned government Trusted Associate Sponsorship System Trusted Associate.
3.2.3.2 CAC / Local Badges: Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to DOD Manual 1000.13 Vol.1 DOD Identification Cards: ID Card Life-Cycle.” All CACs and identification badges issued to contractor employees shall be returned to the Government Security Department at the Government site in accordance with DTM 08-003 following completion of the contract, relocation or termination of an employee, or upon request from the COR. The Government will not be able to complete the contractor personnel check-out process unless all CAC’s and identification badges are returned. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with instructions/guidance required at your facility. For instance, at NAS Patuxent River, MD this is NASPAXRIV Instruction 5510.15Q, 07 March, 2012.
The Contractor shall ensure that any new employees prior to their starting on the task have and maintain a DoD Common Access Card or be able to obtain the interim equivalent during the Period of Performance in order to perform the work assigned and access the facilities required to perform
3.2.3.3 DD-254: The contractor shall comply with security requirements specified in the DD-254 attached to the applicable TO. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only.” 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 CUI and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and SECNAV M-5510.36B. If the work is performed at the Government's facility, the contractor shall comply with (Put in instructions/guidance required by your facility).
3.2.4.1 Marking: All information generated by the contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01.
Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDI 5230.24 and program Security Classification Guidance
3.2.4.2 Public Release for Classified and Unclassified Information: Proposed public releases shall be submitted for approval prior to release to the respective NAWC, NAVAIR or Program Executive Office (PEO) level Public Affairs Office prior to release. Any CUI 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 Public Affairs Office.
3.2.4.3 Loss, Compromise and/or Electronic Spillage of Classified or CUI: All instances of loss, compromise and electronic spillage of classified or CUI shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.
3.2.5 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 and Communications Security (COMSEC). The OPSEC program shall be in accordance with NSDD 298, and at a minimum shall include:
• Assignment of responsibility for OPSEC direction and implementation.
• Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.
• Establishment of OPSEC education and awareness training.
• Provisions for management, annual review, and evaluation of OPSEC programs.
• Flow down of OPSEC requirements to subcontractors when applicable.
While performing aboard 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 requiring office and contractor in support of the mission.
The contractor shall assist in the collection, review, analysis and reporting of Product Support Management and technical services data at CONUS and OCONUS locations in accordance, with the documents cited in this SOW to assist with the technical evaluation, inspection, acceptance and implementation by the Government (or Government delegates).
Documentation shall be prepared in accordance with the applicable TO CDRL.
3.2.6 Anti-Terrorism Force Protection and Emergency Management- The requiring activity will determine the required training at the TO level.
3.3 DETAILED SUPPORT REQUIREMENTS
3.3.1 PRODUCT SUPPORT MANAGEMENT The contractor shall provide support to the requiring Program Office logistics organization or Command functional organization in the gathering and correlation of information for the preparation and development of presentations to support team meetings, management reviews, logistics team reviews, audits and other requests for presentation/briefing information. Preparation and development of presentations will range in scope from detailed in-house briefings to Senior Executive type briefings outside the supported organization.
3.3.2 The contractor shall provide support in the preparation, scheduling and documentation of logistics meetings, modification review meetings, maintenance engineering logistics reviews, motor boards, critical parts reviews, affordable readiness initiatives, logistics documentation reviews, logistics data calls, sustainment VTCs, logistics and conference calls or other-directed program meetings, conferences, VTCs, teleconferences, or technical coordination meetings or reviews.
3.3.3 The contractor shall review and provide analysis of the Government’s content recommendations of current and draft NAVIAR instructions, notices, technical management, and guidance manuals, for Government review and approval.
3.3.4 The Contractor shall provide IPS element, technical execution, and tracking, during the acquisition/Life Cycle Logistics (LCL) production phase for domestic and Foreign Military Sales (FMS) efforts.
3.4 LOGISTICS REQUIREMENTS FUNDING SUMMARY (LRFS) / LOGISTICS BUDGETS
3.4.1 LRFS
3.4.1.1 The contractor shall provide support in the analysis of the primary individual system/component LRFSs as well, as the respective IPT-related LRFS’s (end item/system) in support of production, engineering change orders, and budgetary adjustments for PSMI, and Programs/Program Offices associated with PSMI. The LRFS’s shall include the Government funding requirements and justification required for all logistics elements. Based upon Program Office requirements, the LRFS analysis shall be uploaded utilizing the approved NAVAIR LRFS tools and processes.
3.4.2 LOGISTICS BUDGETS
3.4.2.1 The contractor shall provide technical support and analysis for the weapon systems’ in-service Program Related Logistics (PRL) and Non-Program Related Logistics (NPRL) support requirements; budgeting for PRL/NPRL requirements, participation in the Baseline Assessment Model process for spares determination and other PRL/NPRL support requirements for PSMI and Program Offices associated with PSMI for Government review/approval. Assist in the development/updating of the Optimized Performance Model for the establishment of PRL and in-service funding levels to support logistics program requirements. The contractor will provide LRFS support using the Common Spend Plan Tool (CSPT). Assist in the identification of funding requirements.
3.4.2.2 The contractor shall maintain the LRFS CSPT to ensure the allocation of resources in accordance with in-service program requirements, out year program requirements, and spend plans; track and report the obligation and execution of PRL funds utilizing various NAVAIR reporting tools to include Navy Enterprise Resource Planning (ERP). Provide recommendations for mitigation or solutions to budgeting shortfalls for plus up funding as identified by the Government to support PSMI and Program Offices associated with PSMI.
3.4.2.3 The contractor shall assist the Government Program Office Cost team in developing and maintaining comprehensive affordable in-service readiness plans for Government approved weapon systems, training equipment, subsystems, SoS, or support systems. The plans shall be developed utilizing Government developed templates. The plan shall contain Operations and Support (O&S) cost, should cost/will cost reduction targets, define initiatives to achieve those targets, identify metrics used to measure program progress, and identify barriers, impediments and timeline sensitive requirements to reach program goals for PSMI and Program Offices associated with PSMI.
3.4.2.4 The contractor shall maintain in-service funding spend plans; ensure the allocation of resources is in accordance with those spend plans; and track/ report the obligation and execution of those resources utilizing various NAVAIR tracking tools to include CSPT and Navy ERP.
3.4.2.5 The contractor shall document the results of the Flying Hour Program (FHP) impact analysis utilizing the Cost Adjustment Sheet. The contractor shall assist in the development of the yearly FHP budget impact data call for PSMI and all associated Programs/Program Offices.
3.4.2.6 The contractor shall assist in processing and routing of Procurement Initiation Documents (PIDs) through the Comptroller. The contractor shall review PID financial data elements and addendum sheets to ensure correct accounts are identified and have been coordinated with the designated Business Financial Manager to ensure information is accurate and the funds are transferred correctly.
3.4.2.7 The contractor shall provide recommendations for the usage of Operation and Maintenance Navy (O&MN) (1A5A, 1A9A and 1D4D) funds to support Depot overhaul requirements of aircraft, aircraft systems, SoS, sub-subsystems and engines and emergency In-Service Repair requirements.
3.4.2.8 Provide technical support for the identification of in-service aircraft and PRL/NPRL financial support requirements as well, as budgeting for in-service financial requirements. Maintain in-service funding reports and spend plans, ensure the allocation of resources is in accordance with those spend plans; and coordinate funding status with activities tasked with spending the money. Assist in maintaining in-service and command staffing requirements for all Logistics requirements. Coordinate with other activities as required.
3.4.2.9 The contractor shall assist in updating All Weapons Information System (AWIS), to include target performance reports.
3.5 SOW, PERFORMANCE BASED SPECIFICATIONS, AND CDRL
3.5.1 The contractor shall conduct technical research, provide recommendations for the Government’s development of SOW /Specification/ CDRLs for new acquisitions and modification programs that include the elements of supportability, Reliability, Availability, and Maintainability (RAM) for PSMI and Program Offices associated with PSMI.
3.5.2 The contractor shall develop/evaluate Reliability, Maintainability and Supportability goals for inclusion in the SOW/SPEC.
3.5.3 The contractor shall review draft HW/SW LCL support data requirements specified in the weapon systems Statement of Objectives/ SOWs/ PWSs, including CDRLs and associated Data Item Descriptions. Provide recommendations concerning which data deliverables shall be required to support the planned acquisition.
3.6 LIFE CYCLE SUSTAINMENT PLAN(S) (LCSP)/USER’S LOGISTICS SUPPORT SUMMARY(S)
(ULSS)
3.6.1 The contractor shall assist the Government in developing, modifying, and revising the LCSP/ULSS as defined in the 2017 AT&L Memo Streamlining LCSPs and NAVAIR Standard Work Packages.
3.7 BUSINESS CASE ANALYSIS (BCA)
3.7.1 The contractor shall provide assistance while the Government conducts BCA by providing recommendations for developing and modifying alternative supportability solutions for weapon systems, subsystems, SoS, and/or support systems to identify the most cost-effective plan to ensure the accomplishment of program objectives. Provide recommendations on identifying program support requirements and associated metrics for PSMI and NAVAIR Program Offices.
3.7.2 The contractor shall provide support to the Government Program Office Cost Team in conducting, developing, documenting, and completing Cost Benefit Analyses and BCAs by collecting and analyzing projected/baseline support cost data.
3.7.3 The contractor shall conduct Product Support BCAs in accordance with the DoD Product Support BCA Guidebook, 2014 and Cost Assessment and Program Evaluation (CAPE) O&S Cost Estimating Guide 2020.
3.8 PRODUCT SUPPORT VALUE ANALYSIS
3.8.1 The contractor shall assist the Government in conducting a Best Value analysis making recommendations on the optimum level of support based on the IPS elements to include the following areas:
• Supply Chain Management Strategy
• Workload allocation strategy
• Technical Data Rights (TDRs) Technical Strategy (TDS)
• LCC control and risk mitigation
• Investment/Cost Benefit/Return on Investment Strategy
3.8.2 The contractor shall assess systems compliance with Title 10 USC Sections requirements:
• Section 2460: Definition of Depot Level Maintenance
• Section 2464: Core Logistics Capability
• Section 2466: Depot Level Maintenance Limitations
• Section 2469: $3M Rule (Competition)
• Section 2474: Centers of Industrial and Technical Excellence
• Section 2563: Depot Subcontracting
3.9 DMSMS PLANNING / PLAN
3.9.1 The contractor shall prepare, review and revise, once approved by the Government, DMSMS Plans following the policy, standards and guidance provided by the Deputy Assistant Secretary of the Navy (DASN) (Sustainment), PEO, Commander, Naval Air Systems Command, or other authority.
3.9.2 The contractor shall document the Government approved disposition and solution for DMSMS issues on the Government/NAVAIR server.
3.9.2.1 The contractor shall assist the Government by maintaining records associated with all DMSMS issues, their approved disposition and resolution and the cost associated with the approved disposition and resolution.
Provide DMSMS records as resource material in developing annual budget requirements for the DMSMS program.
3.9.2.2 The contractor shall analyze and assess Bill of Materials (BOMs) to assist in DMSMS planning and management.
3.9.2.3 The contractor shall develop, maintain, and provide minutes and action items from DMSMS review boards.
3.10 ITEM UNIQUE IDENTIFICATION (IUID) PLANNING / PLAN
3.10.1 The contractor shall provide assistance to the Government in the development, preparation and/or revision of IUID Plans, following the policy and guidance provided by the Under Secretary of Defense for Acquisition and Sustainment & Research and Engineering, DASN (Logistics), PEO, Commander, Naval Air Systems Command, or other authority.
3.10.2 The contractor shall provide assistance to the Government in compiling data for the development and revision of budget requirements to support IUID implementation plans.
3.10.3 The contractor shall provide assistance to the Government in development of IUID content for SOWs/SOOs to include parts marking, registration, and property management per IUID policy memos, directives and instructions.
3.10.4 The contractor shall provide assistance with the implementation and execution of IUID plans to include but not limited to; Original Equipment Manufacturer (OEM), Single Process Initiatives (SPI).
3.10.5 The contractor shall assist with the preparation of IUID Exhibits.
3.10.6 The contractor shall develop, collect, document and track metrics for IUID Implementation.
3.11 DEMILITARIZATION PLAN SUPPORT
3.11.1 The contractor shall assist the Government in the development of a Demilitarization and Disposal Plan.
3.11.1.1 The contractor shall review and analyze specified parts lists and BOMs and provide options for disposition in accordance with DOD Manual 4160.21-M and DODI 4160.28.
3.11.1.2 The contractor shall review and analyze specified program documentation for records management purposes. Provide the Government with a proposed list of permanent or long-term, temporary and short-term records.
3.11.1.3 The contractor shall analyze and review designated permanent or long-term records and recommend the appropriate Standard Subject Identification Classification code for each document.
3.11.1.4 The contractor shall develop and maintain a Master Index Records for each designated document assigning a unique filename to each record.
3.11.1.5 The contractor shall…
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 .