Amendment 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

This amendment revises the solicitation closing time and date to 9:00AM on Monday, 07 December 2020. Additionally, this amendment adds COR authorized telew ork language to the Performance Work Statement. All other terms and condiotns remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 15

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 25-Nov-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X N0018921Q0012

X 9B. DATED (SEE ITEM 11)

18-Nov-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

25-Nov-2020

CODE

NAVSUP FLC NORFOLK CONTRACTING

NORFOLK OFFICE

ATTN:A GEUSIC

1968 GILBERT STREET STE600

NORFOLK VA 2351-3392

N00189 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0018921Q0012

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 02-Dec-2020 10:00 AM to 07-Dec-

2020 09:00 AM.

The following have been modified:

LIST OF ATTACHMENTS

Attachment I Price Worksheet Attachment II Past Performance Information Form Attachment III Past Performance Report Attachment IV Wage Determination Attachment V CDR

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT

USFF FLEET CONOPS DEVELOPMENT SUPPORT

Attachments:

(I).Task Order Performance Work Statement (PWS) Format

1.0 BACKGROUND: United States Fleet Forces Command (USFFC) supports both the Chief of Naval Operations (CNO) and Combatant Commanders worldwide by providing responsive, relevant, sustainable Naval forces ready-for-tasking. The command provides operational and planning support to Combatant Commanders and integrated warfighter capability requirements to the CNO. Additionally, USFFC serves as the CNO's designated Executive Agent for Anti-Terrorism/Force Protection, and Individual Augmentees (IA).

In collaboration with Commander, U.S. Pacific Fleet and Commander, U.S. Naval Forces Europe, USFFC organizes, mans, trains, maintains, and equips Navy forces, develops and submits budgets, and executes readiness and personnel accounts to develop both required and sustainable levels of Fleet readiness. Additionally, the command serves as the unified voice for Fleet training requirements and policies to generate combat-ready Navy forces per the Optimized Fleet Response Plan using the Fleet Training Continuum.

This performance work statement specifies the tasks and deliverables as they relate to the core functions of USFFC (N8/N9) Fleet Capabilities Requirements, Capability Transition for the period of performance. USFFC N8/N9 is Commander Fleet Forces Command’s agent to manage Fleet Concept of Operations (CONOPS) development.

To accomplish its mission, USFFC N8/N9 performs the following:

Coordinates development of innovative warfighting CONOPS to better employ Navy capabilities. This involves assigning CONOPS leads, providing developmental guidance and executing overall process management for individually tasked CONOPS efforts as approved in the annual Fleet CONOPS Development plan. Once assigned, leads are accountable to USFFC for CONOPS development according to the timelines assigned.

Coordinates development of innovative CONOPS to better man, train for, and equip new platforms as they are delivered to the Fleet. This involves assigning CONOPS leads, providing developmental guidance and executing overall process management for individually tasked CONOPS efforts as approved in the annual Fleet CONOPS Development plan. Once assigned, leads are accountable to USFFC for CONOPS development according to the timelines assigned.

Conducts advanced analysis and assessment of USFFC assigned CONOPS.

Conducts oversight and management of capability gaps mitigation efforts. Each Fleet CONOPS document presents mitigation actions to close identified capability gaps. During the CONOPS development process capability gaps are assessed using a methodology based on Doctrine, Organization, Training Materiel, Leadership and education, Personnel, Facilities and Policy (DOTMLPF-P) categorization. Assigned Offices of Primary Responsibility (OPR) work mitigation actions for each gap addressed in the Fleet CONOPS document.

Each Fleet CONOPS defines the necessary demonstration goals to support a feedback loop on how the capability implementation into Fleet missions and operations. The organization which developed the CONOPS is responsible to assess and report annually. USFFC N8/N9 staff provides oversight on this activity.

USFFC N8/N9 works directly with Commander, Pacific Fleet, Commander, U.S. Naval Forces Europe, assigned Echelon III Numbered Fleet Commanders and Type Commanders, such as Commander, Navy Surface Force Atlantic; Commander, Navy Air Forces Atlantic; Commander, Submarine Forces Atlantic; Commander Navy Cyber Force; Commander Navy Expeditionary Forces; and Commander Military Sealift Command and coordinates with Navy Component Commanders and Warfighting Development Centers to continuously improve warfighting effectiveness and platform wholeness.

2.0 SCOPE: The contractor shall provide subject matter experts (SME) for developing the draft word document with a collaborative team for up to seven (7) to ten (10) CONOPS in various stages of development as noted in Table 1 below and with estimated completion times as indicated. These tasking’s shall be individually described by USFFC N8/N9 in a Task Order PWS (Attachment I), providing references for format and expectations for content, participants, scope and timelines for delivery.

Table 1

Title Status Suspense from Start

MQ-25 New Start 33 Weeks

Arctic Communications New Start 33 Weeks

Naval Integrated Fire Control-Counter Air Rev B New Start 33 Weeks

Resilient and Assured Command and Control New Start 33 Weeks

Counter Intelligence, Surveillance, Reconnaissance and Targeting

New Start 33 Weeks

Joint War at Sea New Start 33 Weeks

Ready Relevant Learning Application Information Technology Hosting and Transport

New Start 33 Weeks

These SMEs shall possess expertise in Navy CONOPS development, Navy warfighting areas, and organization, planning and communication skills to support all facets of USFFC’s mission and functions cited above.

Additionally, SMES assigned to work a specific CONOPS shall have additional skills as indicated in the following table:

Table 2

CONOPS Skills

MQ-25 Minimum Years’ Experience - 20 years’ experience as a surface/aviator/submarine line officer in the US Navy

Minimum Education Level - Undergraduate Knowledge of Air Defense and airborne battle management Knowledge of Naval aviation operations Knowledge of man/train and equip issues as they may relate to implementing capability

Arctic Communications Minimum Years’ Experience - 20 years’ experience as a surface/aviator line officer in the US Navy

Minimum Education Level - Undergraduate Knowledge of strike group operations Knowledge of command and control as it relates to execution of operational and tactical level warfare Knowledge of man/train and equip issues as they may relate to implementing capability

Naval Integrated Fire Control-Counter Air Minimum Years’ Experience - 20 years’ experience as a surface/aviator line officer in the US Navy

Minimum Education Level - Undergraduate Knowledge of surface & airborne fire control systems and associated capabilities Knowledge of tactical data links Knowledge of man/train and equip issues as they may relate to implementing capability

Resilient and Assured Command and Control Minimum Years’ Experience - 20 years’ experience as a line officer in the US Navy

Minimum Education Level - Undergraduate Knowledge of Information Warfare Knowledge of communications capability Knowledge of Maritime Operations Center capabilities Knowledge of man/train and equip issues as they may relate to implementing capability

Counter Intelligence, Surveillance, Reconnaissance and Targeting

Minimum Years’ Experience - _20 years’ experience as a surface/aviator/submarine line officer in the US Navy

Minimum Education Level - Undergraduate Knowledge of Information Warfare Knowledge of Strike Group operations Understanding of Combatant Commander coordination requirements and challenges Knowledge of man/train and equip issues as they may relate to implementing capability

Medium Unmanned Surface Vehicles/Large Unmanned Surface Vessels

Minimum Years’ Experience - 20 years’ experience as a surface/aviator/submarine line officer in the US Navy

Minimum Education Level - Undergraduate

Knowledge of surface warfare Knowledge of subsurface warfare Knowledge of information warfare Knowledge of ISR capabilities Understanding of Combatant Commander coordination requirements and challenges Knowledge of man/train and equip issues as they may relate to implementing capability

Ready Relevant Learning Application Information Technology Hosting and Transport

Minimum Years’ Experience - 20 years’ experience as a line officer in the US Navy

Minimum Education Level - Undergraduate Knowledge of navy training programs and practices Knowledge of man/train and equip issues as they may relate to implementing capability

Once assigned to develop a CONOPS, SMEs will work on a daily basis with the CONOPS lead (military personnel) and a collaborative of Fleet representatives to meet the suspense timelines for delivery.

3.0 REFERENCE DOCUMENTS: COMFLTFORCOM Instruction 5401.1 (series); Fleet CONOPS Writers Guide, The Navy Warfare Library (NTTP 1-01); and U.S. Government Printing Office Style Guide (series) will guide production and format of a draft document that is coherent, well written and meets the basic requirements of the commander’s intent promulgated in the task order PWS for each CONOPS project. These reference documents will be sited for use in each PWS.

4.0 REQUIREMENT: USFFC’s CONOPS SME support requirements are technically rigorous and highly dynamic. They can encompass a wide variety of maritime disciplines including logistics; tactical aviation; various gun/missile systems; communications systems, Maritime Operations Center command and control activity, cyber systems; information warfare; and surface, aviation, expeditionary and submarine warfare. SMEs with the requisite experience/skills noted in Paragraph 2; Table 2 will be needed for various periods during the contract period to meet USFFC Fleet CONOPS development requirements. The contractor shall provide subject matter expertise (SME) to develop the draft CONOPS documents with the support of a collaborative team input and will coordinate/collaborate with the CONOPS military lead (e.g., C3F if assigned as a CONOPS lead, SME provides direct support). The demand signal to develop documents will be articulated in the Fleet CONOPS Plan, notionally promulgated every 18-24 months. It is anticipated that up to seven (7) to ten (10) CONOPS will be in development in any one year.

Each CONOPS SME must have the requisite skills specifically applicable to the assigned CONOPS. Information and expectations with respect to specific CONOPS will be provided by USFFC CONOPS program manager using the PWS format provided in Attachment I.

4.1 Historical Level of Effort: The historical level of effort (LOE) for CONOPS task orders is approximately 4 full-time employees (FTEs).

5.0 PROJECT MANAGEMENT: The contractor shall provide for Project Management via a senior analyst in conjunction with assigned SMEs. Project Management includes monitoring and reporting of SME assignments, deliverables, and schedules. The Project Manager shall act as a single point of contact regarding all contract deliverables and metrics. The Project Manager shall receive and consolidate SME monthly reports. The Project Manager shall be the primary interface for the Government's Contracting Officer Representative (COR) regarding all technical and business related issues.

A “Phased Transition” (Phase-In and Phase-Out) strategy will be required to accommodate in-progress production from a pre-existing plan supported by a deliverable based contract. Therefore, the contractor shall develop, submit and maintain a “Phased Transition Plan.” This plan shall be submitted to the COR and ACOR no later than the five

(5) days after start of contract performance.

5.1 The deliverable shall be development of Fleet CONOPS documents tasked by USFFC N8/N9. In performing this PWS, the contractor SMEs shall at times interact with staff from Fleet Forces Command, Commander, Pacific Fleet, Navy Component Commanders, Numbered Fleet Commanders, Type Commanders, Warfare Centers of Excellence, other relevant Navy organizations, other Services and DoD agencies. The contractor SMEs shall have an experience profile that contains significant, senior Navy operational experience in maritime missions/functions/tasks and shall demonstrate a robust working knowledge of Navy and naval capabilities and concept. Minimum requirements are 20 years’ experience in subject matter area and an undergraduate degree.

Other specific requirements include the following.

5.1.1 Coordinate with the assigned Fleet stakeholder commands to develop a USFFC tasked CONOPS document.

5.1.2 Draw on Operational fleet experience to describe and illustrate capability employment in draft CONOPS documents.

5.1.3 Coordinate with Navy Warfare Development Command (NWDC) staff and USFFC N8/N9 warfare leads to review and ensure adequacy of CONOPs in a joint context.

5.1.4 When capability gaps are identified during Fleet CONOPS development, work with the collaborative team to identify Doctrine, Organization, Training, Materiel, Leadership & education, Logistics, Personnel and Policy (DOTMLPF-P) actions to mitigate identified gaps and ease capability transition into the Fleet.

5.1.5 Work with the collaborative team to identify demonstration and experimentation opportunities to evaluate operational capabilities proposed in the CONOPS. Articulate those opportunities and venues in the draft CONOPS document.

5.1.6 Work with the collaborative team to provide language in the draft CONOPS on recommendations to address critical operational issues, and capability shortfalls.

5.1.7 Organize material and technical support for work sessions, briefings and other meetings that support CONOPS development.

5.1.8 Coordinate planning and execution of Fleet key stakeholder SME participation in CONOPS development work session events.

5.1.9 Refine CONOPS draft documents based on guidance from the Fleet stakeholders during work sessions to improve CONOPS document content.

5.1.10 Assist in drafting, editing and staffing reviews of CONOPS document drafts.

5.1.11 Attend working groups, focus groups, tiger teams, integrated product teams, etc. as requested by the USFFC CONOPS program manager or designated representative.

5.1.12 Establish coordination protocols to manage DOTMLPF-P actions associated with each approved and promulgated Fleet CONOPS document. Communicate and collaborate with stakeholders on a quarterly basis to update the status of each action. The use of the USFF Command Task System, e-mail and phone conversations will be required to coordinate this information.

5.1.13 Manage the Fleet CONOPS DOTMLPF-P action database. Assess data and provide periodic reports to the USFF N81/N81B regarding action progression and closure.

5.1.14 Establish coordination protocols with USFF N90, NWDC and Fleet CONOPS owners to manage demonstration information associated with each Feet CONOPS document. Areas to include planning and execution of demonstration objectives, data collection plans, and feedback assessment, report generation (as needed) per the “Demonstration Chapter” in each Fleet CONOPS document.

5.1.15 Provide monthly progress reports to the CONOPS program manager that include at a minimum; progress on the CONOPS development (include: outline, content, flow), key events accomplished, major stakeholders engaged, developmental suspense’s met, developmental suspense’s in jeopardy of not being met, any issues impacting the progress and/or quality of the CONOPS development effort.

5.1.16 When the length of the CONOPS effort warrants (greater than 3 months), provide a quarterly in progress review that leverages the monthly reports and which provides an aggregated view of CONOPS deliverable status, funding expended, any issues impacting quality and delivery of draft CONOPS.

6.0 GOVERNMENT FURNISHED EQUIPMENT (GFE): While performing work at government facilities, the Contractor will be provided office space as appropriate by the assigned lead for the CONOPS development. The Contractor will have access to a computer, printer, facsimile machine, copy machine, and telephone on a temporary and not-to-interfere basis with existing services. The Contractor will also be provided access to reference material, Web site access, and CD ROMs for required research. All provided databases will remain property of the U.S.

Navy. The contractor shall not retain any government furnished equipment or materials without approval from

USFFC N8/N9.

7.0 TRAVEL: No specific travel is anticipated at this time; however, certain task orders may require travel. If travel is necessary, it will be approved on a case by case basis by the Contracting Officer. Travel may be required by contractor SME to coordinate the initial development of a document with the assigned supporting organization. A 3-day trip in CONUS per document is the threshold.

8.0 QUALITY CONTROL: The contractor will be responsible for quality control while performing under this contract and will ensure that the requirements of the contract are adhered to as specified in the Quality Assurance Surveillance Plan (QASP).

9.0 POLICY AND PROCEDURES: All Contractors working at or on a USFFC contract must comply with all USFFC Security and Administrative policy and procedures, as identified by the Agency Contracting Officer Representative (COR).

10.0 NON-DISCLOSURE AGREEMENTS: Due to the interrelationship of contractor workforce assigned to USFFC, all contractors assigned to a USFFC contract shall sign a non-disclosure agreement in accordance with DFARS 227.7103-7 and/or a USFFC Non-Disclosure agreement.

11.0 GOVERNMENT PURPOSE RIGHTS AND INTELLECTUAL PROPERTY: All products generated by personnel assigned to this effort shall be considered both the physical and intellectual property of the government.

This shall include, but not limited to, all documents, spreadsheets, reference material and briefs, (both verbal and written). All information, techniques, strategy, and derived components that are associated to this effort shall also be considered intellectual property of the government. No dissemination of information shall occur without the consent of the agency COR.

12.0 SECURITY CLEARANCE REQUIREMENTS: Contractor personnel supporting this effort are required to obtain and possess a secret security clearance under this effort. Contractor deliverables will be up to and including Secret only. It is the Contractor’s responsibility to obtain and maintain the appropriate security clearances for its personnel prior to the start and during the performance of work in accordance with the requisite DD254. All security requirements shall be coordinated with the COR and command security office personnel.

12.1 DD254: The DD254 attached to this solicitation provides further details as to the security requirements of this contract. Contractor shall comply with all security instructions and references included in the DD254 throughout the life of this contract and beyond if required. Contractor shall comply with the COMUSFLTFORCOMSTAFFINST

5531.1A (INDUSTRIAL SECURITY PROGRAM).

12.2 BASE ACCESS: The Contractor is responsible for and shall obtain CACs for all contractor personnel and vehicle passes for vehicles requiring entry onboard Government installations. The Contractor shall complete and submit the requisite documentation to the COR. Contractors who do not have/require NMCI access are not required to obtain CAC. Contractor shall comply with the COMUSFLTFORCOMSTAFFINST 5531.1A (INDUSTRIAL SECURITY PROGRAM) at all times during the performance of this effort.

12.3 PHYSICAL SECURITY: The Contractor shall be responsible for safeguarding all Government property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured. The Contractor shall follow established Government security procedures for the facility for which they are assigned and/or supporting. Contractor shall comply with the COMUSFLTFORCOMSTAFFINST 5530.2A (PHYSICAL SECURITY PLAN) at all times during the performance of this effort.

12.4 KEY CONTROL: The Contractor shall establish and implement methods of making sure all keys and key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards, CAC, and individual security identification badges. No keys issued to the Contractor by the Government shall be duplicated.

The Contractor shall adhere to the methods/procedures included in their proposed/accepted QCP covering key control. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas.

The Contractor shall immediately report any occurrences of lost or duplicate keys and key cards to the COR and local security official.

In the event keys other than master keys are lost or duplicated the Contractor shall upon direction of the Contracting Officer re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

The Contractor shall prohibit the use by any persons other than the Contractor’s employees of Government keys and key cards issued to members of that Contractor’s team.

The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas or those personnel authorized entrance by the Government (usually through the use of facility- or event-specific identification badges).

12.5 LOCK COMBINATIONS: The Contractor shall ensure that all lock combinations are not revealed to unauthorized persons.

13.0 OPSEC: IAW DODM 5205.02M, SECNAVINST 3070.2, and COMUSFLTFORCOMINST 3070.2, contractor shall protect information listed in the Critical Information List (CIL) and any other sensitive, but unclassified information that may be useful to our adversaries. Contractor shall abide by OPSEC policies and procedures, as detailed in DODM 5205.02M, SECNAVINST 3070.2, COMUSFLTFORCOMINST 3070.2, and/or as directed by the OPSEC Program Manager or directorate OPSEC Coordinator. Contractor shall accomplish USFF initial OPSEC training within 90 days of in-processing and complete refresher OPSEC training at least annually.

Contractor shall notify their directorate OPSEC Coordinator or the OPSEC Program Manager of recommendations for the OPSEC program or potential OPSEC concerns. POC: USFF OPSEC Program Manager, phone 757-836- 3987. The critical information list can be found in COMUSFLTFORCOMSTAFFNOTE 3070 (CRITICAL

INFORMATION LIST).

14.0 CONTRACT DELIVERABLES: The contractor shall provide the deliverables in accordance with the USFFC Annual Fleet CONOPS Development Plan listed in Paragraph 2, and Table 1. Deliverables shall be submitted in hard copy and fully editable soft copy. Deliverables are subject to review and, if warranted, may be returned to the contractor for revision due to content inaccuracies and/or clerical errors. Upon receipt of Government comments, the contractor shall provide the final revised report according to the USFFC Annual Fleet CONOPS Development Plan schedule provided by the Fleet CONOPS program manager.

All documentation shall provide traceability to enable Government review and verification. At specific milestones, the contractor shall provide interim reviews of the work accomplished to permit determination of the quality of the effort or receive government guidance. If deficiencies are found, the contractor shall provide for timely and corrective action.

15.0 PLACE OF PERFORMANCE:

Performance will be onsite with the USFF Fleet CONOPS development program manager co-located within the N8 government workspace. Fleet CONOPS development is managed from the USFF headquarters (Building NH-4N, Room 256) located on the Naval Support Activity Headquarters Complex Norfolk, Virginia.

Work tasks may be performed at remote locations (telework) by contracted personnel subject to approval by the Contracting Officer's Representative (COR). Ability and specific timeframe for contractor personnel to work remotely will be at the COR’s discretion. The Government reserves the right to rescind this ability to work remotely at any time. Authorization to work remotely shall incur no additional cost to the Government.

16.0 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA):

The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Navy via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address https:///www.sam.gov.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.sam.gov.

17.0 Navy Use of AbilityOne Support Contractor - Release of Offeror Information: NAVSUP FLC Norfolk may utilize contractor support through the AbilityOne Program, as needed, to perform contract closeout functions for this acquisition. Information, including business sensitive/confidential or proprietary data, that the offeror provides to the Government or information already in the possession of the Government may be viewed and utilized by the AbilityOne Program support contractor personnel during the course of its contract performance. The information that may be made available to the support contractor may include, for example, pricing and technical proposals, historical contract, pricing and performance information, Commercial Asset Visibility (CAV) reporting information and similar data/information.

By submission of a proposal in response to this solicitation, the offeror and its subcontractors consent to a release of their business sensitive/confidential or proprietary data to the Government's AbilityOne Program support contractor personnel in order to perform close out services. Prior to the release of any such information to the support contractor, the support contractor will have in place with the Government a Non-Disclosure/Non-Use Agreement in accordance with the terms of the AbilityOne Program support contract.

Offerors may execute their own Non-Disclosure Agreement with the AbilityOne Program (AbilityOne contact information available from the contracting point of contact). The support contractor must provide copies of the executed agreements to the Contracting Officer and the Contracting Officer's Representative (COR) for the support contract; and the offeror/contractor for this acquisition must provide copies of the executed Agreement to the Contracting Officer for this acquisition. If the offeror/contractor seeks such a Non-Disclosure Agreement with the AbilityOne Program support contractor, the Agreement must be executed no later than the date of final delivery under the resulting NAVSUP FLC Norfolk contract.

18.0 Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information:

Executive Order 13467, Reforming Processes Related to Suitability for Government Employee, Fitness for Contractor Employees and Eligibility for Access to Classified National Security Information, Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The 5 CFR 32 Part 157 in concert with DoD Manual 1000.13, Vol 1, implements the Federal Standards.

APPLICABILITY

This text applies to all DoD sponsored individuals who require CAC eligibility (or login and P/W if acceptable per contract) for: Physical access to DoD facilities or non-DoD facilities on behalf of DoD; Logical access to information systems (whether on site or remotely); or remote access to DoD networks that use only the CAC logon for user authentication, or access to sensitive and protected information. This applies to the Office of the Secretary of Defense, the Military Departments, the Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office of the Inspector General of the DoD, the Defense Agencies, the DoD Field Activities and all other organizational entities within the DoD (hereinafter referred to collectively as the "DoD Components").

Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

ACCESS TO FEDERAL FACILITIES

Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command’s Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.

START-UP PERIOD

All contractor resource onboarding documents must be submitted via the prime contractor. The prime contractor shall make all necessary preparations to assume full responsibility for productive performance of the performance start date.

Definition of “productive”:

a. Visit Authorization Request (VAR)

b. Contractor Information Sheet (CIS)

c. Completed EQIP (Electronic Investigation)

d. All contractor resource(s) must have an active JPAS profile.

e. Common Access Card (CAC)

Note (1): Invoicing by the contractor will begin as of the commencement of the performance period of services and no reimbrusement will be paid by the government for efforts expended during the start-up period.

Note (2): Foreign Nationals are not allowed acces sot the functional/system side of Enterprise Resource Planning

(ERP).

ACCESS TO DOD INFORMATION TECHNOLOGY ( IT) SYSTEMS

In accordance with (IAW) Secretary of the Navy (SECNAV) M-5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M- 5510.30, includes positions which require access to sensitive information. Sensitive information includes information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information System Security Manager (ISSM)/Information Assurance Manager (IAM).

Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation , which is a higher level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s CSM and ISSM/IAM upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor”.

The SAAR-N shall be forwarded to the Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Cyber Awareness training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

INTERIM ACCESS

The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

DENIAL OR TERMINATION OF ACCESS

The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

CONTRACTOR’S SECURITY REPRESENTATIVE

The contractor shall designate an employee to serve as the Contractor’s Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity’s Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor’s Security Representative. The Contractor’s Security Representative shall be the primary point of contact on any security matter. The Contractor’s Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR

CONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE

DUTIES

Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non- Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:

• SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)

• Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

• Original Signed Release Statements

Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

Regardless of their duties or IT access requirements ALL contractor employees shall in-process with the CSM upon arrival to the command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Employees requiring IT access shall also check-in and check-out with the Navy Command’s ISSM/IAM. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date.

The contractor shall ensure that each contract employee requiring access to IT systems or networks complete annual Cyber Awareness training, and maintain a current requisite background investigation. Contractor employees shall accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command’s Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command’s Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.

If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor’s Security Representative. Although the contractor will take JPAS “Owning” role over the contractor employee, the Navy command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee’s performance under the contract.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR

CONTRACTORS ASSIGNED TO OR PERFORMING NON-SENSITIVE DUTIES

Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc. ...) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:

• Must be either a US citizen or a US permanent resident with a minimum of 3 years of legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and

• Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.

To be considered for a favorable trustworthiness determination, the Contractor’s Security Representative must submit for all employees each of the following:

• SF-85 Questionnaire for Non-Sensitive Positions

• Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

• Original Signed Release Statements

The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM

Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

* Consult with your CSM and ISSM/IAM for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.

(End of performance work statement)

Attachment I

Task Order Performance Work Statement Serial Number 2020 XXX

Date:

I. CONOPS Title: TBD

II. CONOPS Description: TBD

III. SME Skills Required: TBD

IV. Security Clearance Required: TBD

V. Organizational Lead; Numbered Fleet Commander, or Type Commander Contact Information:

VI. CONOPS Development References: COMFLTFORCOM Instruction 5401.1 (series); Fleet CONOPS

Writers Guide, The Navy Warfare Library (NTTP 1-01); and U.S. Government Printing Office Style Guide (series)

VII. Anticipated CONOPS Development Participants: TBD

VIII. Timeline: Table of Contents & Terms of Reference, Working Draft, Planner Draft, Flag Draft and Final

Draft

IX. Comments: TBD

(End of Summary of Changes)