Attachment_1_NOTM_FSR_PWS_2.16.17_Amendment_0003_final.pdf

Amendment 00013

SECTION C DESCRIPTIONS AND SPECIFICATIONS

PERFORMANCE WORK STATEMENT (PWS)

MARINE CORPS SYSTEMS COMMAND

NOTM Field Service Representative (FSR) Support

1.0 BACKGROUND

Networking On-The-Move (NOTM) program includes both a ground combat vehicle mounted and air element. NOTM’s Ground Combat Vehicles provide the Marine Air Ground Task Force

(MAGTF) with a robust, over-the-horizon/beyond line-of-sight, digital command, and control combat capability while on-the-move and at-the-halt. NOTM allows maneuvering forces to seamlessly conduct digital command and control (C2) through access, collaboration, and exchange of tactical voice, video, and data, including e-mail and chat, using the Joint Tactical

COP Workstation (JTCW) software applications and services. NOTM has been fielded to all levels of the Marine Air-Ground Task Force (MAGTF) enabling forces to access C2 and intelligence, surveillance, and reconnaissance applications.

One NOTM system includes one (1) Point of Presence (POP) vehicle kit, two (2) Staff Vehicle

(SV) Kits and four (4) Staff Kits. In addition, NOTM connects to the Combat Operations Center

(COC) via the Tactical Modem Kit (TMK). NOTM provides the following capabilities, using the four Principle End Items (PEI) listed below.

POP Vehicle Kit. The NOTM POP, mounted on the host vehicle platform, is the primary hub for mounted and dismounted users, connecting them to the tactical network.

The POP provides beyond Line-Of-Sight (LOS) Satellite Communications (SATCOM), LOS wireless Radio Frequency (RF) to the data network and communications security equipment within the host platform. The POP also hosts the VideoScout system enabling receipt of Unmanned Air Systems (UAS)/Full Motion Video (FMV) and video dissemination across the tactical network.

SV Kit. NOTM SV Kits, mounted on the host vehicle platforms, are the vehicular mounted user extension nodes. The SV Kit hosts the mobile user’s laptops/handheld devices and provides network connectivity and access to C2 applications through the

POP to the tactical network. NOTM’s SV Kit consists of LOS wireless devices and data network equipment. The SV Kits also provide users with FMV access via the POP.

Staff Kit. The NOTM Staff Kit is the dismounted user extension providing connectivity from the laptop to the POP via LOS wireless technologies and to the SV Kit via an ethernet cable.

TMK. The TMK is the point through which the POP connects to the COC for services.

NOTM GCV systems achieved Full Operational Capability (FOC) in August 2014. However, the Authorized Acquisition Objective (AAO) increased from 56 to 140 GCVs in FY15. The additional 84 GCV systems will be fielded incrementally starting in FY17 and ending in FY21.

The AAO for NOTM-Air (NOTM-A) Increment 1 has also increased. Appendix A to the PWS, provides the location of all NOTM assets currently fielded and a projected fielding schedule to support these AAO increases as well as to support NOTM-A Increment 2 and NOTM-ITV requirements described below.

NOTM-A Increment 1 (formerly referred to as the Hatch Mounted SATCOM Antenna System

(HMSAS)) provides a networking package for the KC-130J aircraft. The approved AAO is five

(5). Facilitated by a hatch mounted Ku-Band antenna and Global Network Services, this system allows SPMAGTF-CR units to conduct C4 while en-route to a distant objective. HMSAS provides VoIP, Chat, email, and file exchange extended to disadvantaged users via LOS ANW2 network.

NOTM-A Increment 2. The NOTM Program Office has received a requirement to develop, field and support fourteen (14) NOTM-A systems which will be mounted to the MV-22 aircraft.

NOTM-A will provide an airborne, multi-enclave, local area network (LAN) with reach-back to a static command post, allowing users across one or more aircraft the ability to conduct en-route mission planning. The C2 suite shall be modular, utilize existing NOTM equipment, and capable of being rapidly integrated onto a variety of Marine Corps airframes in a “carry-on / carry-off” fashion. These systems will be fielded sometime starting in FY18 and will be a pre-priced option to this PWS.

NOTM Internally Transportable Vehicle (ITV) System. The Program Office has also received a requirement to field and support five (5) MV-22 Internally Transportable Vehicle

(ITV) systems. The NOTM-ITV will provide an airborne, multi-enclave, LAN with reach-back to a static command post for the purposes of en-route communication, collaboration and mission planning, and continued access to network connectivity and C2 applications after disembarking from the aircraft in the objective area, even in the absence of an airborne SATCOM gateway.

These systems will be fielded insometime after 2018 and will be a pre-priced option to this PWS.

2.0 SCOPE

The Contractor’s role in support of the Networking On The Move (NOTM) Program under this contract is to provide a workforce of Field Service Representatives (FSRs). The Contractor shall be responsible for recruiting, hiring, and preparing prospective FSR candidates for duties. The

Contractor and perspective FSRs shall possess both experience and in-depth knowledge of

SATCOM-based, on-the-move command/control systems utilizing multiple external network enclaves and secure wireless LAN venues. Examples of these type systems are Mobile Modular

Command and Control (M2C2), (NOTM), and Warfighter Information Network - Tactical

(WIN-T). The Contractor and FSRs shall also possess in-depth knowledge of integrated

MAGTF C2 systems and how NOTM fits into the integrated MAGTF C2 combat capability. In addition, the Contractor shall support the NOTM Integrated Product Team (IPT) by deploying and providing fielding support, post-fielding support, and unit training for all NOTM assets provided in Appendix A at their respective unit locations, one TMK located at Sheik Isa

Airbase, Bahrain, and one TMK located at Ahmed Al Jaber Air Base, Kuwait. Post-fielding contract requirements include, but are not limited to: on-site service calls, troubleshooting, and

Line Replaceable Unit (LRU) fault isolation/diagnostics support.

The Contractor shall perform a Limited Technical Inspection of each NOTM system every quarter and provide the Government with a report on the material readiness of each system and the ability of Marines to operate and maintain it. Unit training includes, but is not limited to:

New Equipment Training (NET), Sustainment Training, and follow-on over-the-shoulder training.

With the exception of the FSR Team Lead, the FSR team shall perform their duties at the following locations: Marine Corps Base Camp Lejeune, NC; Marine Corps Base Camp

Pendleton, CA; Marine Corps Air Ground Combat Center 29 Palms, CA; Marine Corps Base

Hawaii, HI; and, in the future, Okinawa Japan. Contractor performance, as outlined in this PWS, shall be measured in accordance with the metrics detailed in the Quality Assurance Surveillance

Plan in Attachment 2 to the RFP.

2.1 Place of Performance/Potential Travel Locations. In addition to the resident locations specified in paragraph 2.0, the Contractor shall travel, upon Government request, to the following locations in support of NOTM exercises, training events, etc.

2.1.1 Marine Corps Systems Command (MARCORSYSCOM), Quantico, VA

2.1.2 SPAWAR Systems Center, Pacific (SSC PAC), San Diego, CA

2.1.3 Marine Corps Base, Camp Pendleton, CA

2.1.4 Marine Corps Tactical Systems Support Activity (MCTSSA), Camp Pendleton, CA

2.1.5 Marine Corps Air Ground Combat Center 29 Palms, CA

2.1.6 Marine Corps Air Station Miramar, CA

2.1.7 Marine Corps Air Station Yuma, AZ

2.1.8 Marine Corps Base, Camp Lejeune, NC

2.1.9 Marine Corps Base, Camp Johnson, Jacksonville, NC

2.1.10 Marine Corps Air Station, New River, NC

2.1.11Marine Corps Air Station, Cherry Point, NC

2.1.12 SPAWAR Systems Center, Atlantic (SSC LANT), Charleston, SC

2.1.13 Marine Corps Air Station, Beaufort, SC

2.1.14 Camp Schwab, Okinawa Japan

2.1.15 Marine Corps Base, Hawaii, HI

2.1.16 Sheik Isa Airbase, Bahrain

2.1.17 Ahmed Al Jaber, Kuwait

2.1.18 Moron de la Frontera, Spain

2.1.19 Others as required when directed by the Program Office

2.2 Contract Transition Planning. This contract will be broken down into separate contract line items (CLIN). One for I MEF support with a limited Period of Performance (PoP) and then another for I, II and III MEF support. Upon initial contract award, the Contractor will obtain transition training from SSC-PAC and SSC-LANT Government support personnel. This initial training will be coordinated by the Government. The Contractor shall provide all subsequent training required to support additional FSR personnel.

The Contractor shall coordinate with the Government to obtain training on all currently fielded

NOTM systems within 30 days of contract award. This training may require travel to San Diego, CA and/or other Continental United States (CONUS) locations. The Contractor shall coordinate with the Government to obtain required training on NOTM-A Increment 2 and NOTM ITV in accordance with the Government’s Instructor and Key Personnel (I&KP) Training schedule.

This I&KPT schedule is not yet developed and will be developed by the NOTM Logistics IPT, of which the Contractor shall be a member.

2.3 Contract Close-Out Transition Planning. No less than 30 days prior to contract close-out, the Contractor shall provide transition training to the awardee of the follow-on contract at I, II, and III MEF locations. This training shall be provided in the Contractor’s format but shall be reviewed and approved by the Government no less than 90 days prior to contract close-out.

2.4 Safety. The Contractor shall comply with all safety requirements such as, but not limited to:

cautions and warnings provided within NOTM technical manuals. All technical manuals will be provided by the Government during the post-award conference.

3.0 PERSONNEL REQUIREMENTS AND MANAGEMENT

3.1 General. The Contractor shall have the necessary security clearances (see paragraph 6.0) and shall possess both experience and in-depth knowledge of SATCOM-based, on-the-move command/control systems utilizing multiple external network enclaves and secure wireless LAN venues. Examples of these type systems are Mobile Modular Command and Control (M2C2), Networking On The Move (NOTM), and Warfighter Information Network - Tactical (WIN-T).

The Contractor shall also possess in-depth knowledge of integrated MAGTF C2 systems and how NOTM fits into the integrated MAGTF C2 combat capability. It is desired that all personnel proposed under this contract have a working knowledge and/or hold certifications in the following: Network Plus and or Security Plus as a fundamental IT 101 course, Cisco

Certified Network Associated (CCNA), Voice Over Internet Protocol (VOIP), Voice Over

Secure Internet Protocol (VOSIP) and Cisco Certified Network Profession (CCNP).

3.2 Key Personnel. The Contractor’s personnel shall at all times meet the requirements specified below and as provided in the Contractor’s proposal submission, the qualifications of which will be All personnel proposed under this contract are considered key personnel. Key personnel are defined as those labor categories, qualifications and individuals that are proposed in the Contractor’s proposal submission and will be listed in the resulting contract. Thus if, e.g., the Contractor wishes to change the Program Manager then the new Program Manager must have the same or higher skills, qualifications, certifications, etc., as proposed by the Contractor for that position and as incorporated into the contract. No substitutions shall be made except in accordance with this paragraph. Substitution requests must be submitted in writing, at least fifteen (15) days [thirty (30) days if a security clearance is to be obtained] in advance of the proposed substitutions, to the Contracting Officer. All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitution, and any other information requested by the Contracting Officer. All proposed substitutes shall have qualifications that are equal to or higher than the qualifications required of the person to be replaced. The Contracting Officer or his/her authorized representative will evaluate such requests and promptly notify the Contractor of his/her approval or disapproval thereof. The following provides the designated key personnel to include a description of expected performance.

3.2.1 Program Manager. This individual shall be the primary point of contact for the Program

Management Office (PMO) and will forward all deliverables, reports and correspondence to the

PMO assigned Contract Officers Representative (COR) Insure that all deliverables are received by the COR, oversee fielding events as well as the training of all assigned Field Service

Representative (FSR) personnel in accordance with the provisions of this PWS. The Program

Manager will have overall responsibility to interface with the Program Management Office via the assigned COR, supervise the efforts of the FSRs, contribute to the development of and updates to all NOTM technical manuals, develop or update all training materials, to include

Computer Based Training (CBTs) materials, as required.

3.2.2 FSR Team Lead. The FSR Team Lead shall not be the Program Manager and shall be cross-trained in network management, vehicle integration, and troubleshooting/diagnostics. This individual’s primary competency shall be network management. This individual shall also oversee fielding events as well as training of other FSR personnel, be responsible for all service calls, contribute to the development of and updates to all NOTM technical manuals, develop and update all training materials, to include Computer Based Training (CBTs) materials, as required.

In addition, the FSR Team Lead shall ensure the FSR Teams are providing the training necessary to enhance the operational competency and full mission capable status of U.S. Marine NOTM operators and NOTM systems. Government spot checks in the field with the Marine Operating

Forces will confirm the Contractor’s performance in this area.

The FSR Team Lead shall be knowledgeable of all FSR duties and:

3.2.2.1 Shall be the single point of information flow from the program office to the FSR teams across each MEF.

3.2.2.2. Be responsible for overseeing field troubleshooting, diagnostics and LRU/SRU-level fault isolation.

3.2.2.3 Manage FSR resources.

3.2.2.4 Have real-world experience/the ability to train Marines on C2 systems.

3.2.2.5 Have the ability to communicate effectively with senior Marines.

3.2.2.6 Understand the USMC rank structure, roles, responsibilities, and protocol.

3.2.7.7 Understand and be able to accomplish assigned tasks within a Marine Corps working environment.

3.2.7.8 Shall ensure the FSR Teams are proactively reaching out to their respective MEF(s), demonstrating operational capabilities and training personnel on the various NOTM platforms and components.

3.2.3 FSR Personnel. FSRs shall have an in-depth knowledge of network management and system installation of all platforms used by the NOTM components. Vehicle integration shall include training the units on the installation and removal of NOTM system on High Mobility

Multipurpose Wheeled Vehicle (HMMWV), MRAP (Mine Resistant Ambush Protected) All-

Terrain Vehicle (M-ATV), ITV, and Assault Amphibious Vehicle (AAV) variants. Additionally, the FSR may be expected to transfer this expertise to other ground combat vehicles and/or aircraft, such as those designated to host NOTM-A systems (C-130 and MV-22 aircraft). FSRs shall ensure they are proactively and aggressively reaching out to their respective MEF(s) demonstrating operational capabilities and training personnel on the various NOTM platforms and components to enhance the operational competency and full mission capable status of U.S.

Marine NOTM operators and NOTM systems. FSRs shall have the following knowledge, skills and abilities:

3.2.3.1. Experience operating and supporting MAGTF Command and Control, expeditionary networking, radio, and satellite communications systems, to include system set up/configuration, troubleshooting, and fault isolation.

3.2.3.2. Experience/knowledge in cable routing such as the capability of performing vehicle installation procedures.

3.2.3.3. Experience with troubleshooting cryptographic equipment, while alongside Marines and

Electronic Key Management System (EKMS) personnel.

3.2.3.4. Able to read and understand technical drawings, schematics, and wiring /cable routing diagrams.

3.2.3.5. Basic knowledge of Marine Corps maintenance structure and resources.

3.2.3.6. Ability and experience training Marines in both a class room and real-world practical application conditions.

3.2.3.7. Ability to communicate effectively with senior Marines.

3.2.3.8. Understand United States Marine Corps rank structure, roles, responsibilities, and protocol.

3.2.3.9. Understand assigned tasks and the ability to accomplish tasks in a United States Marine

Corps environment.

4.0 OBJECTIVES

4.1 The Contractor shall provide system fielding support, post-fielding support, modification installation support, unit training, and technical support services for all NOTM systems. Refer to Appendix A for projected fielding schedule. In addition to the detailed FSR responsibilities provided in paragraph 5.2, the following definitions are provided for clarity. Marine units operating NOTM will be queried quarterly as to the effectiveness and responsiveness of contract

FSR personnel. These queries and the unit's NOTM readiness will be considered by the

Government in writing the Contractor's CPARS evaluations.

Fielding Support. Fielding support is defined as vehicle integration support and providing New

Equipment Training (NET).

Post-Fielding Support. Post-Fielding support is defined as assistance with troubleshooting, diagnostics, vehicle integration as well as those activities defined in para 5.2. In addition, it includes assistance tracking warranty repairs and assistance coordinating with Repair Issue

Points and other sources of supply to track replacement assets as well as assets in the repair cycle.

Unit Training Support. Unit training support includes NET, Sustainment Training, and over-the-shoulder training. Unit training support will not exceed one man-year or 1,920 hours of effort at I and II MEF location is and not to exceed a .25 man-year at III MEF locations.

Training requirements that go beyond this amount will be coordinated with the Government and the Government will establish work level priorities.

Modification Installation Support. The Contractor shall perform system modifications/installations in accordance with modification instructions provided by the Program

Office. The specific modifications required for NOTM systems will vary from one year to the next. However, Table 1 provides projections for planning purposes. If modification requirements exceed these projections and the Contractor is not able to support all support requirements, the Government will set the priority of work efforts.

Table 1: Modification Event Projections

Modification Event Projections per year for each NOTM End Item/

TAMCN Fielded

(Including Firmware/Software Updates)

Level Duration

Projected # of

Events

Level 1 1 to 2 hours 6

Level 2 >2 to 4 hours 4

Level 3 >4 to 6 hours 2

Level 4 >6 to 8 hours 2

Level 5 >8 to 24 hours 1

4.2 FSR Team Responsibilities. The FSR Team Lead shall be based out of the Contractor’s facility within the National Capital Region. The rest of the FSR team shall be comprised of the

FSRs who shall be located at the Government appointed facility aboard Marine Corps Base

Camp Lejeune, NC; Marine Corps Base Camp Pendleton, CA; Marine Corps Air Ground

Combat Center 29 Palms, CA; Marine Corps Base Hawaii, HI; and in the future, Camp Schwab, Okinawa Japan. The Government will provide CACs, in accordance with paragraph 3.1, to enable access to military facilities and the NOTM SharePoint data repository for access to all

NOTM technical publications and training materials. A list of NOTM technical publications and training materials is provided in paragraph 9.

4.2.1 The FSR team shall coordinate with users, including the warranty coordinator, Program

Office, MCTSSA, and the Marine Corps Logistics Command in order to perform the following functions:

4.2.2.1 Participate in Instructor and Key Personnel (I&KP) training with the SSC-PAC

Government personnel located at Point Loma, CA when requested by the Government.

4.2.2.2 Provide fielding integration support and NET for all POPs, SV Kits, SKs, and

TMKs fielded to I MEF, II MEF, and III MEF at their designated fielding locations.

4.2.2.3 Support NOTM training request from MEF G-3/6, once approved by the

Contracting Officer’s Representative (COR) or Contracting Officer (KO).

4.2.2.4 Field/install Program Office approved modifications changes to NOTM systems and provide associated operator training to MEF units.

4.2.2.5 Conduct fault isolation and identify/verify faults reported by the user.

4.2.2.7 Input system failure data in to MCTSSA’s Knowledge and Information

Management System (KIMS) site. Note: In order to gain access to MCTSSA’s KIMS database, FSRs will be required to successfully complete a KIMS training course, provided by MCTSSA (at no cost) within 30 days of contract award. This training can be conducted over the phone.

4.2.2.8 Send weekly reports to the NOTM Program Office and MCTSSA by the work week’s close of business using CDRL A001. This weekly report will include activities such as fielding activities, unit support requests, and any open Return Material

Authorizations (RMAs). The format and content for the weekly report will be agreed upon during the post-award conference.

4.2.2.9 Collect data from NOTM service requests for maintenance actions performed each month and report them to the Program Office using CDRL A002. The Government requires this data to support Reliability, Availability, and Maintainability (RAM) Analysis.

4.2.2.10 Support Requests for Information (RFI) and serve as subject matter experts to assist the Government in the development of curriculum updates and technical publication updates. In addition, the Contractor shall demonstrate specific installation, operation and maintenance tasks, and provide feedback such as changes to procedure required, input on graphics, and input on wording and the sequence of tasks. This support shall not exceed 80 hours total, per year.

4.2.2.11 Support exercises and test events as directed by the Marine Corps users and the

Program Office. FSRs shall help support exercises and test events by troubleshooting issues that arise with the systems with the approval of the Program Office. FSRs shall check IP addresses, address communication problems, and check connections and cables for any issues. FSRs shall make sure Marines are using the right frequencies to prevent interference with other equipment in the area. FSRs shall provide over-the-shoulder training to Marines in conjunction with service calls to assist with troubleshooting and diagnostic upon request. FSRs shall guide the Marines through the troubleshooting/diagnostics process and LRU-level fault isolation. The FSR shall provide after action reports of support exercises or test events to the Program Office using CDRL

A003 no later than ten (10) working days after the end of the event. The format will be agreed upon at the post-award conference.

4.2.2.12 Coordinate with the Repairable Issue Point (RIP) to ensure a RMA request is submitted by the warranty coordinator and that the RMA is received by the Marine Corps

Logistics Command warranty administrator.

4.2.2.13 Perform technical and logistics functions for routine troubleshooting.

4.2.2.14 Participate in IPT meetings as required.

4.2.2.15 Participate in weekly conference calls with the Program Office.

4.2.2.16 Follow all applicable safety guidelines and industry standards for mechanical and electrical equipment.

4.2.2.17,Package equipment originating from I MEF, II MEF, and III MEF in support of exercises and test events. All packaging and shipments will be in accordance with all applicable policies and procedures for the Department of Defense and the United States

Marine Corps.

4.2.2.18 Participate in Program Management Review events upon request from the

Government.

5.0 COMPUTER BASED TRAINING (CBT)

CBT efforts shall be pre-priced options to this contract.

5.1 CBT Pre-Priced Option One. The Contractor shall update all previously developed CBT material to address configuration changes that affect more than 30% of each module’s content. .

The Contractor shall conduct a validation/verification event with Government oversight before the changes are finalized.

5.2 CBT Pre-Priced Option Two. The Contractor shall develop a Networking/System

Configuration CBT module that provides details for operator system configuration/set up, network diagrams, network management (including data layers), and Command Line Interface

Tools, such as Commands (e.g. Show IP Interface Brief, Show Running-Configuration, Show IP

Route, Show IP EIGRP Neighbors, and Show IP EIGRP Topology), Pings, Traceroute, and

Make backup configurations to Flash or other locations. The Contractor shall conduct a validation/verification event with Government oversight prior to finalizing any modules. This

CBT can be in the Contractor’s format per CDRL (A004).

6.0 SECURITY REQUIREMENTS

This contract will require the Contractor to have access to a Government Secret Facilities and will require certain Contractor employees to obtain and maintain a secret classified access. The

Contractor shall have a valid Secret Facility Clearance prior to classified performance. The prime Contractor and all subcontractors and teammates shall adhere to all aspects of DOD

Directive 5220.22-M. All personnel identified to perform on this contract shall maintain compliance with Department of Defense, Department of the Navy, and Marine Corps

Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract includes a DoD Contract Security

Classification Specification (DD Form 254) as Attachment 3. The Contractor shall notify the

Government (written notice) within twenty-four hours of any Contractor personnel, added or removed from the contract, that have been granted classified access, issued a Common Access

Card and/or MARCORSYSCOM Building access.

6.1 Common Access Card (CAC) Requirement

The COR will identify and approve those Contractor employees performing on this contract that require Common Access Cards (CACs) in order to perform their job function. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security

Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a

CAC. In order to meet the eligibility criteria, Contractor employees requiring a CAC, must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI.) Prior to authorizing a CAC, the employee’s JPAS record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened.) The minimum acceptable investigation is a National Agency Check with Written Inquiries (NACI).

If a Contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked.

Facility Security Officers (FSOs) are responsible for notifying the MCSC Security Director if any Contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also notify the MCSC Security Director of any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning any Contractor issued a CAC, regardless of whether a JPAS Incident Report is submitted.

Each CAC is issued with a “ctr.usmc.mil” e-mail account that the individual Contractor is responsible to keep active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any unneeded e-mails. Contractors are prohibited from “auto-forwarding” their .mil e-mail account to their .com e-mail account. If the ctr.usmc.mil e-mail account is not kept active, then G-6 will deactivate the account and CAC will lose its functionality.

CACs will only be issued to those Contractors supporting this contract that has been authorized by the COR. The COR will only authorize CACs for those Contractors that meet current HSPD-

12 criteria and have a definitive requirement.

If a Contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on MCSC contracts. CACs are not issued for convenience.

7.0 OTHER GOVERNMENT CONTRACTORS AND THEIR SUBCONTRACTORS

During the performance of the resultant contract, the Contractor’s staff shall be required to work with other Government Contractors and their subcontractors at all locations. The NOTM

Program Management team is supported by Contractors and subcontractors covering a wide variety of skill sets that could range from logistics management, configuration management, financial management, and acquisition management. These Contractors are located throughout the NOTM program and may have continuous interaction with the Contractor.

8.0 POST-AWARD CONFERENCE (FAR 42.503)

In accordance with Federal Acquisition Regulation (FAR) 42.503 Post Award Conference, the

Contractor shall host a Post Award Conference at its facility located in the National Capitol

Region, within thirty (30) calendar days after contract award. Discussions at the meeting shall include: Contractor’s Program Management; Staffing; Identified Risk Areas to include

Mitigation Plan; and all other technical requirements (i.e. quality assurance; transition).

9.0 DATA DELIVERABLES

Contract Data Requirements List is provided in Exhibit 1 to the RFP.

10.0 TRAVEL

Travel and Temporary Duty (TAD). Travel to other Government facilities, field activities, Marine operating forces (U.S. and overseas) may be required and will be cost reimbursable. All travel requirements (including plans, agenda, itinerary and dates) shall be pre-approved by the Government COR on a strictly cost reimbursable basis. The Contractor shall make necessary travel arrangements for its employees after approval from the Government COR.

Travel must be reimbursed in accordance with the Joint Travel Regulation (JTR). Per Diem shall be per Government rates at http://www.defensetravel.dod.mil/site/perdiemCalc.cfm .

When sufficient lead time allows, travel requests shall be submitted at least ten (10) working days in advance of the travel date. The request will include total cost and a break out of costs to include airfare, rental vehicle, per diem, mileage, parking, fuel, and tolls. Travel requests will include the purpose of trip and why VTC or phone conversations would not meet the business requirement.

If more than one traveler is traveling, then sharing of rental vehicles is required. Differing arrival and departure times will not justify separate rental vehicles. For rental cars carrying three or more travelers, larger vehicles may be authorized in advance. The Government will reimburse economy lot parking. The Government will not reimburse valet parking.

11.0 DEFENSE BASE ACT (DBA) INSURANCE

Due to the requirement for Travel and/or Temporary Duty (TAD) Outside the Continental United

States (OCONUS), Contractors are required to obtain DBA Insurance. DBA Insurance shall be

Formatted: Font: (Default) Times New Roman, 12 pt

Formatted: Font: (Default) Times New Roman, 12 pt

Formatted: Font: 12 pt carried individually by the Prime and its Subcontractor(s). Subcontractors must carry their own

DBA insurance policy in their OWN NAME. The Prime Contractor cannot insure the subcontractor(s) under its insurance and cannot carry subcontractor employees as its own employees. Immediately following contract award, the Prime Contractor and if applicable its

Subcontractor(s) shall obtain DBA Insurance (refer to https://www.dol.gov/owcp/dlhwc/lsdba.htm).

The Contractor shall not start work in an OCONUS location until the Contracting Officer (KO) and Contracting Officer’s Representative (COR) is provided with a certificate of insurance or endorsement to the KO and COR when finalized.

Contractor’s will be reimbursed DBA insurance costs under the contract Travel/ODC CLIN. To be eligible for reimbursement of the DBA insurance, Contractor’s shall submit a copy of the

Contractor paid Insurance premium as an attachment.

121.0 TECHNICAL PUBLICATIONS AND TRAINING MATERIALS

There is no Government Furnish Information (GFI) associated with this contract. However, the

Contractor will be provided with a copy of the following technical publications during the post-award conference. In addition, the Government will provide all Computer Basted Training materials, to include M-ATV and AAV POP and M-ATV and AAV Staff Vehicle Removal and

Installation modules. .

Publication Title Short Title PCN

CMD/CNTL SYS NOTM PT of Presence TM 12271A-OR/1 18412271000

CMD/CNTL SYS NOTM PT of Presence TM 12271A-QRG 18412271000

NTWRK MGMT SYS NOTM SV Kit TM 12272A-OR/1 18412272000

NTWK MGMT SYS NOTM SV Kit TM 12272A-QRG 18412272100

CMD/CNTL SYS NOTM Staff Kit TM 12279A-OR/1 18412279000

CMD/CNTL SYS NOTM Staff Kit TM 12279A-QRG 18412279100

MODEM Communications TM 12268A-OR/1 18412268000

NOTM Tact Entry PT Comm TMK TM 12268A-QRG 18412268100

Command and Control System (AAV) TM 12445A/OR/1 18412445000

Command and Control System (AAV) TM 12445A-QRG 18412445000

Network Management System (AAV) TM 12444A-OR/1 18412444000

Network Management System (AAV) TM 12444A-QRG 18412444100

Hatch Mounted SATCOM SYS TM 12542A-12/1 18412542000

Command and Control System (HMSAS) SL-3-12542A 12312542000

Computer Based Training Installation & Removal

12.0 ACRONYMS

AAO - Authorized Acquisition Objective

ANW2 – Adaptive Networking Wideband Waveform

Formatted: Font: 12 pt

Formatted: Font: 12 pt

Formatted: Font: 12 pt https://www.dol.gov/owcp/dlhwc/lsdba.htm

ATH – At-The-Halt

AAV – Amphibious Assault Vehicle

BLOS – Beyond Line of Sight

C2 – Command & Control

CBT - Computer Based Training

CDRL – Contract Data Requirements List

COC – Combat Operations Center

EKMS - Electronic Key Management System

FMV – Full Motion Video

FSR – Field Service Representative

FY – Fiscal Year

FOC – Full Operational Capability

GCV - Ground Combat Vehicle

HMSAS – Hatch Mounted SATCOM Antenna System

I&KP – Instructor and Key Personnel

IOC – Initial Operational Capability

IPT – Integrated Product Team

JTCW - Joint Tactical COP Workstation

MAGTF - Marine Air-Ground Task Force

MCTSSA – Marine Corps Tactical System Support Activity

NET – New Equipment Training

NOTM – Networking On-The-Move

NOTM-A – Networking On-The-Move-Air

NOTM-ITV - Networking On-The-Move-Internally Transportable Vehicle

OTH – Over-The-Horizon

POP – Point of Presence

PEI – Principle End Item

RMA – Return Material Authorization

RF - Radio Frequency

RFI – Request for Information

SATCOM – Satellite Communication

SL-3 – Stock List / Components List

SPMAGTF – Special Purpose Marine Air-Ground Task Force

SV – Staff Vehicle

SVK – Staff Vehicle Kit

TMK – Tactical Entry Point (TEP) Modem Kit

VoIP – Voice Over Internet Protocol

133.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 NOTM FSR Support effort 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) S, Utilities ONLY;

(5) V, Freight and Shipping ONLY.

The Contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil. 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://doncmra.nmci.navy.mil.

14.0 OPTIONAL FSR SUPPORT (ALL SYSTEMS; GCV, INCREMENT 1&2 AND ITV)

During the life of this contract, the FSR support required per location and the need to add locations may vary. This acquisition consists of 1) “Core” requirements and 2) Optional FSR

Support. Core requirements are listed in this PWS. To meet mission needs throughout the various periods of performance, additional FSR support is included in the contract as an option

CLIN, in order to provide the NOTM program the ability to increase support based on AAO increases and Operation Tempo. The additional support provided under this option shall provide all of the services described in the PWS.

15.0 SYNCHRONIZED PRE-DEPLOYMENT & OPERATION TRACKER (SPOT) AND

MC3 DEPLOYMENT INSTRUCTIONS

15.1 The Government maintains FSR data in the Synchronized Pre-deployment & Operational

Tracker (SPOT) IAW the 48 CFR, AKA; the Defense Federal Acquisition Regulation

Supplement (DFARS) 252.225-7040. Contractors are required to have accounts and utilize the

SPOT system when OCONUS Travel is required.

15.2 Deployment Package: MC3 Program Office (via Contracting Officer’s Representative

(COR) requires a 90 day advance notice for OCONUS Travel. Traveler shall coordinate with the

COR on specific instructions and requirements for overseas travel. In accordance with Defense

Federal Acquisition Regulation (DFAR) part 252.225.7040, as well as Marine Corps Systems

Command policy regarding contractor personnel supporting U.S. Armed Forces deployed outside the United States and contracts performed outside the United States; require certain pre-deployment screening training and innoculations. As fulfillment of these prerequisites may take up to two weeks, timely coordination with the COR with regard to specific instructions for the candidate FSRs must be rapidly accomplished immediately after contract award. Appendix C to this PWS, provides the current MCSC Deployment Checklists for all Area’s of Operation (AOA) for 30 days or less and 31 days or longer. These checklists are being provided as sample documents only and will not be completed until after contract award and/or awardee is requested to deploy. In accordance with each of these checklists, the contractor is required to adhere to all medical, training and administrative form(s) requirements prior to deployment. As specified in

DFARS Clause 252.225-7040, any military-specific immunizations and/or medications not available to the general public, will be provided by the Government prior to deployment.

https://doncmra.nmci.navy.mil/

Finally, travel costs associated with FSR personnel travel to required deployment centers, will be reimbursed under the contract Travel/ODC CLIN.

16.0 ACRONYMS

AAO - Authorized Acquisition Objective

ANW2 – Adaptive Networking Wideband Waveform

ATH – At-The-Halt

AAV – Amphibious Assault Vehicle

BLOS – Beyond Line of Sight

C2 – Command & Control

CBT - Computer Based Training

CDRL – Contract Data Requirements List

COC – Combat Operations Center

EKMS - Electronic Key Management System

FMV – Full Motion Video

FSR – Field Service Representative

FY – Fiscal Year

FOC – Full Operational Capability

GCV - Ground Combat Vehicle

HMSAS – Hatch Mounted SATCOM Antenna System

I&KP – Instructor and Key Personnel

IOC – Initial Operational Capability

IPT – Integrated Product Team

JTCW - Joint Tactical COP Workstation

MAGTF - Marine Air-Ground Task Force

MCTSSA – Marine Corps Tactical System Support Activity

NET – New Equipment Training

NOTM – Networking On-The-Move

NOTM-A – Networking On-The-Move-Air

NOTM-ITV - Networking On-The-Move-Internally Transportable Vehicle

OTH – Over-The-Horizon

POP – Point of Presence

PEI – Principle End Item

RMA – Return Material Authorization

RF - Radio Frequency

RFI – Request for Information

SATCOM – Satellite Communication

SL-3 – Stock List / Components List

SPMAGTF – Special Purpose Marine Air-Ground Task Force

SV – Staff Vehicle

SVK – Staff Vehicle Kit

TMK – Tactical Entry Point (TEP) Modem Kit

VoIP – Voice Over Internet Protocol

Appendix A.

Table 1 lists the four (4) types of NOTM-GCVs and the TMK. The TMK is a hub that interfaces with the Combat Operations Center and Very Small Aperture Terminal Large (VSAT-L) to gain access to Defense Information Systems Network (DISN) services for the Non-secure Internet

Protocol Router Network (NIPRNET), the Secure Internet Protocol Router Network (SIPRNET), the Mission Specific (MS), and other Department of Defense (DoD) networks authorized for

Networking On-

Table 1. NOTM GCV systems currently fielded at each MEF.

NUMBER OF NOTM GCV SYSTEMS CURRENTLY FIELDED TO EACH MEF

LOCATION

POP

(A03877G)

SV Kit

(A03887G)

AAV POP

(A04337G)

AAV SV

Kit

(A04357G)

TMK (A03957G)

Not GCV

I MEF 39 77 2 4 9

Support Establishments 4 8 0 0 2

II MEF 7 14 0 0 4

III MEF 3 6 0 0 1

FIELDING SUB TOTAL 53 105 2 4 16

NOTE: HQMC/II MEF redistributed one (1) NOTM system to JLTV during 2Q FY16 showing only seven (7) systems in TFSMS. One

NOTM system consists of one (1) POP/TAM A0387 and one (2) SV Kits/TAM A0388.

Table 2. NOTM-GVC systems to be fielded at each MEF by year

PLANNED NUMBER OF NOTM GCV SYSTEMS TO BE FIELDED

FY

POP (A03877G) SV Kit (A03887G) AAV POP (A04337G) AAV SV Kit (A04357G)

TMK (A03957G)

Not GCV

Location/Qty Location/Qty Location/Qty Location/Qty Location/Qty

SE

I II III

SE

I II III

SE

I II III

SE

I II III

SE

I II III

MEF MEF MEF MEF MEF

ME

F

MEF MEF MEF MEF MEF MEF MEF

M

E

F

ME

F

FY17 8 16 3

FY18 2 17 3 3 35 6 4 2

FY19 2 3 4 1 4 5 8 2 1 1

FY20 3 1 5 14 6 2 10 30 1 2 1 3 4

FY21 9 2 7 18 4 14 1 2 2 4 3 2

Location

Totals 5 15 36 25 10 28 73 52 0 1 2 1 0 2 4 2 2 3 10 9

Totals being

Fielded

FY17 to

FY21

81 163 4 8 24

Table 4. NOTM-A Increment 1 Fielded and Planned Fielding

FY

NOTM A (A04557G)

Location/AAO Qty (6)

I MEF II MEF PTP I MEF PTP II MEF

FY15

Fielded 2 2

FY16

FY17 1 1

FY18

FY

NOTM A (A04557G)

Location/AAO Qty (6)

I MEF II MEF PTP I MEF PTP II MEF

FY19

FY20

FY21

Totals 2 2 1 1

Table 5. NOTM-A Increment 2 Planned Fielding

FY

NOTM A (A04557G)

Location/AAO Qty (6)

I MEF II MEF PTP I MEF PTP II MEF

FY15

Fielded 0 0

FY16

FY17 2 2 2 2

FY18 2 2 1 1

FY19

FY20

FY21

Totals 4 4 3 3

Table 6. NOTM ITV Planned Fielding

FY

NOTM ITV (TAMCN TBD)

Location/AAO Qty (5)

I MEF II MEF

FY15

Fielded

FY16

FY17

FY18 3 2

FY19

FY20

FY21

Totals 3 2

NOTE: Tables 3, 4, 5 and 6 are fielding projections only and are subject to change throughout the life of the contract. The Government will coordinate changes in this fielding schedule with the Contractor on a quarterly basis during in-progress reviews. Additional assets may be fielded to MEF locations based on emerging (unforeseen) requirements and assets could be fielded earlier to later than projected.

Appendix B

Table 1. NOTM-GCV Total Acquisition Objective.

Totals Fielded and Planned to meet AAO

POP (A03877G) SV Kit (A03887G)

AAV POP

(A04337G)

AAV SV Kit

(A04357G)

TMK (A03957G)

Not GCV

Totals fielded from Table 1.

53 105 2 4 16

Totals

Planned for fielding from

Table 2.

81 163 4 8 24

AAO Total 134 268 6 12 40

Table 2. Projected FTEs by MEF.

FTE (Full Time Equivalent) Rough order of Magnitude (ROM) Estimate FSR Staffing Levels

Locations Base Period 11 months – I

MEF & 6

months – II and III MEFs 29 Mar 2017– 30 Mar 2018

Option Year 1 29 Mar 2018- 30 Mar 201912 months

Option Year 2 29 Mar 2019- 30 Mar 202012 months

Option Year 3 29 Mar 2020- 30 Mar 202112 months

Option Year 4 29 Mar 2021- 30 Mar 202212 months

I MEF 5 5 5 5 5

II MEF 3 3 4 3 3

III MEF 1 1 1 2 2

Quantico 1 1 1 1 1

Note: Staffing levels derived from parametric evaluation on historical support data.