Attachment__1_Performance_Work_Statement_(PWS)_v28__6_Jun_2017.pdf

PERFORMANCE WORK STATEMENT

FOR

TACTICAL SYSTEMS SUPPORT

PROFESSIONAL ENGINEERING SERVICES

17 May 2017

PREPARED BY:

OPERATING FORCES SUPPORT BRANCH

MARINE CORPS TACTICAL SYSTEMS SUPPORT ACTIVITY

CAMP PENDLETON, CA 92055-5171

PWS for TSS-PES 17 May 2017 ii

TABLE OF CONTENTS

1 INTRODUCTION

Background ................................................... 1 1.1

Scope ....................................................... 2 1.2

2 APPLICABLE DOCUMENTS

Guidance Documents ............................................. 3 2.1

3 PERFORMANCE REQUIREMENTS

TSS On-Site Technical Support ...................................... 5 3.1

TSS Exercise Support ............................................ 6 3.2

TSS Contingency Support .......................................... 6 3.3

Program Management and Administration ............................... 7 3.4

Transition Plan ................................................. 8 3.5

4 DELIVERABLE AND INSTRUCTIONS

Deliverables ................................................... 8 4.1

4.1.1 Monthly Systems Analysis

4.1.2 Monthly Performance Report

4.1.3 Monthly Financial Forecast Report

4.1.4 Weekly Staffing Report

4.1.5 Weekly Embedded Deployed Support Status

4.1.6 Census Report

Instructions .................................................. 10 4.2

4.2.1 Distribution Statement

4.2.2 Delivery

4.2.3 Unclassified End Products

4.2.4 Classified End Products

4.2.5 Schedule of Deliveries

4.2.6 Inspection of Deliverables

5 PERIOD OF PERFORMANCE

6 GOVERNMENT FURNISHED ACCESS

Access to Government Facilities and Equipment .......................... 12 6.1

Access to Government Furnished Information and Networks .................. 13 6.2

7 SECURITY REQUIREMENTS

Security Clearance ............................................. 14 7.1

DD Form 254 ................................................. 14 7.2

Site Security ................................................. 15 7.3

OPSEC Requirements ........................................... 15 7.4

8 STAFFING

Identification ................................................. 16 8.1

9 TRAVEL REQUIREMENTS

10 ORGANIZATIONAL CONFLICT OF INTEREST

iii

APPENDIX A – ACRONYMS ............................................. A-1

ADDENDUM 1 – Notional TSS Billet Requirements by Location ...................... 1-1

ADDENDUM 2 – Notional Estimated Exercise/Event Support Schedule .................. 2-1

ADDENDUM 3 – Contingency Operations...................................... 3-1

LIST OF TABLES

Table 3-1 Notional List of TSS Supported Fielded C4I Systems

1 INTRODUCTION

BACKGROUND 1.1

The Marine Corps has fielded and improved a host of Command, Control, Communications, Computer, and Intelligence (C4I) systems and networks that have become essential to modern warfighting, whether executing security cooperation, counter insurgency, or humanitarian operations.

Because many C4I systems were fielded without fully trained Marines to successfully and continuously accomplish the Command and Control (C2) mission, Marine Corps Tactical Systems Support Activity (MCTSSA) provided support for those systems. This effort also filled the gap of technical expertise, where a Military Occupational Specialty (MOS) did not exist or MOS training was limited or not available.

MCTSSA supported programmed/fielded C4I systems where business case analysis indicated a centralized support process as the preferred alternative, and systems developed in response to an Urgent Unfunded

Needs Statement (UUNS) that were delivered without organic support.

Because MCTSSA provided effective and efficient support, many Marine

Corps programs of record chose to reduce reliance on program/specific

Field Service Representatives (FSRs) and support C4I systems/applications through MCTSSA and define that support in the

Life Cycle Sustainment Plan.

In response to the growing need for C4I Tactical Systems Support

(TSS), MCTSSA established the Operational Forces Support (OFS) group to provide critical, highly specialized interoperability and integration support. OFS includes over-the-shoulder training and troubleshooting for multiple fielded C4I systems and associated networks for in garrison and deployed Marines. Additionally, OFS provides communication between the operating forces and the Marine

Corps Systems Command (MARCORSYSCOM) Program Managers and Program

Executive Offices to address system performance and sustainment issues for fielded systems, resulting in problem resolution and engineering change opportunities.

OFS consists of the Operating Forces Tactical Systems Support Center

(OFTSSC), a help desk staffed by an integrated team of Marines, civil servants, and TSS Contractors available 24 hours a day, Contractors strategically embedded with Marine units worldwide, and highly trained teams deployed from OFTSSC to support various training exercises and contingency operations. OFS provides technical systems expertise for troubleshooting and issue resolution, tactical communications network analysis and diagnostics, and fielded C4I system setup, maintenance, system engineering, technical support, configuration management, and over-the-shoulder training.

Support is provided to Marine Corps units, deployed and in garrison, preparing for and participating in major exercises, to include joint and coalition events, and special purpose missions: Examples include:

the Weapons and Tactics Instructor course, Special Purpose Marine Air-

Ground Task Force (SPMAGTF) expeditionary operations, Dawn Blitz, Island Viper, Marine Expeditionary Unit deployments and Deploying

Group System Integration Testing, and other events in the Continental

United States (CONUS) and Outside CONUS (OCONUS).

OFTSSC provides escalating levels of technical support to operating forces in CONUS and OCONUS.

The three levels of support include:

Tier 1: C4I systems support is provided by personnel who resolve issues in real-time utilizing the OFTSSC online knowledge repository or resolving basic requests for system software, password resets, and account creation.

Tier 2: OFTSSC subject matter expert (SME) personnel, with significant knowledge and experience with specified fielded C4I systems, are consulted to resolve an issue.

Tier 3: MCTSSA SMEs outside of OFTSSC (typically experienced C4I systems and applications engineers) are consulted. If necessary, issues are transferred to a MARCORSYSCOM program office or the

C4I system developer or integrator for resolution.

OFS provides the Marine Corps the flexibility to meet the operating forces C4I technical needs at a high level of performance. OFS works in collaboration with other technical and field service engineering support contracts and Contractors maintained by ongoing programs and systems within the Marine Corps and other Department of Defense (DoD) agencies, such as Space and Naval Warfare Systems Center Atlantic (SSC

Atlantic) and Naval Surface Warfare Center Crane. These efforts are coordinated by OFS at MCTSSA and the program managers at MARCORSYSCOM.

SCOPE 1.2

This Performance Work Statement (PWS) defines the non-personal technical service support efforts required by MCTSSA TSS to meet the operating forces technical support requirements for fielded C4I systems. Support under this effort includes, but is not limited to;

11 hours per day (0630 to 1730), five days a week (Monday through

Friday) at the MCTSSA OFTSSC; full time on-site support of Marine

Corps units worldwide, contingency operations support, training exercise support, and over-the-shoulder training. Additionally, the successful Offeror may be required to provide shift work and on-call support at OFTSSC during off hours (1730 to 0630 Monday through

Friday) and 24 hours a day Saturday and Sunday, based on operational requirements.

TSS support includes technical expertise and assistance with installation of fielded C4I systems, troubleshooting, issue resolution, tactical communications network analysis and diagnostics, maintenance, system engineering, technical support, configuration management, and over-the-shoulder training. Support is provided to

Marine Corps units that are deployed, in garrison, and preparing for or participating in major exercises including combat operations.

Examples include: SPMAGTF expeditionary operations, I Marine

Expeditionary Force (MEF) Amphibious Exercise, and Cobra Gold; Marine

Expeditionary Unit (MEU) deployments and Deploying Group System

Integration Testing, and other events in CONUS and OCONUS.

The primary objective of this service is to provide technical support to MCTSSA OFTSSC and the operating forces worldwide with continuous support of fielded tactical C4I programs of record to ensure that

Marines can successfully set up and operate fielded C4I tactical systems. Table 3-1 list the systems supported under this PWS.

2 APPLICABLE DOCUMENTS

GUIDANCE DOCUMENTS 2.1

The following documents are provided as guidance and may be helpful to the Contractor in performing the work described in this PWS:

a. National Industrial Security Program Operating Manual (NISPOM), DoD Directive 5220.22-M, 28 February 2006.

b. Information Assurance Workforce Improvement Program (IAWIP), DoD

8570.01-M Change 4, 10 November 2015.

c. Information Technology Infrastructure Library (ITIL) v3.

3 PERFORMANCE REQUIREMENTS

The Contractor shall provide qualified, trained personnel to provide technical support and analytical services for the fielded tactical C4I systems (Table 3-1). The Contractor may be required to provide support for other tactical C4I systems as identified by the

Contracting Officer’s Representative (COR) to the Contracting Officer

(KO).

Table 3-1 Notional List of TSS Supported Fielded C4I Systems

TSS Supported Fielded C4I Systems

Common Aviation Command and

Control System (CAC2S)

Marine Civil Affairs Information

Management System (MARCIMS)

Combat Operations Center (COC) Networking On-the Move (NOTM)

Data Distribution System – Modular

(DDS-M)

Satellite Communications

(SATCOM) Family of Systems (FoS)

Fires Support Systems (FSS) Systems Planning, Engineering, and Evaluation Device (SPEED)

Global Command and Control System

(GCCS) – Tactical Combat

Operations (TCO) (GCCS-TCO)

Tactical Radios FoS

Intelligence Operating System

(IOS)

Transition Switch Module (TSM)

Joint Capabilities Release (JCR) Video Scout (VS)

Joint Tactical Common Operational

Picture (COP) Workstation (JTCW)

Task orders issued against this contract will require the Contractor to provide technical support on-site, at exercises, or in support of real world contingencies as discussed below.

TSS ON-SITE TECHNICAL SUPPORT 3.1

As specified in individual task orders, the Contractor shall be prepared to provide fully qualified personnel to support the MCTSSA

OFTSSC, and CONUS/OCONUS remote sites for the duration of the task order period of performance. Locations of remote sites will be specified in individual task orders.

The contractor must be able to provide technical support to Marine forces worldwide. The following is a notional, but non-exhaustive list, of sites with historical on-site technical support:

MCTSSA (San Diego, CA)

I MEF (San Diego, CA)

II MEF (Camp Lejeune, NC)

III MEF (Okinawa, JPN)

MARFORCOM (Norfolk, VA)

MARFOREUR/AFRICOM (Stuttgart, DEU)

MARFORRES (New Orleans, LA)

TTECG (Twentynine Palms, CA)

CTF-51 (Bahrain)

For planning purposes, ADDENDUM 1 contains a notional estimate of the number of contractor personnel currently providing on-site support in these locations. Actual requirements will be specified on individual task orders and may vary significantly.

The contractor must provide qualified personnel to provide subject matter expert (SME) technical support to MCTSSA and operating forces for fielded C4I systems identified in Table 3-1 and other C4I systems as specified in individual task orders or identified by the COR or

Contracting Officer.

On-site technical support includes, but is not limited to, providing:

Troubleshooting

Issue resolution

System administration

Software and hardware installation

Technical guidance

Systems integration

Test support

Engineering assessments

Documentation of tactical systems issues and resolutions

Informal training (i.e., over-the-shoulder training) o This training is intended to provide Marines with technical guidance and expertise, so that the Marine can operate, diagnose, and resolve system integration, configuration, and interoperability issues.

The Contractor shall provide on-site support during normal working hours or as required by supported units. Specific working hour requirements will be specified in individual task orders.

TSS EXERCISE SUPPORT 3.2

Contractor on-site personnel ordered via individual task orders will also provide technical support to various CONUS/OCONUS locations in support of exercises, equipment fielding, systems integration, and test events.

The Contractor on-site personnel must be able to deploy to CONUS /

OCONUS locations as part of a MCTSSA deployed support team (DST). The

Contractor must support all deployments, which are subject to change based on mission requirements, but for planning purposes, ADDENDUM 2 of this PWS provides a notational list of major exercises supported in an annual period.

The Contractor shall coordinate and get approval from the COR or GSR for support that falls outside normal working hours. Normal working hours are set by the supported unit. During exercise support, the hours may be extended to no more than 12 hours per day, seven days a week. Approval by the COR based on requirements of the requesting unit determines periods of support.

TSS CONTINGENCY SUPPORT 3.3

To assist vendors with contingency operations planning, the MCTSSA

Contracting Officer is publishing guidance in ADDENDUM 3 of this PWS.

The Contractor shall provide technically qualified personnel, to support fielded tactical C4I systems during contingency operations at various OCONUS locations (ADDENDUM 2). The Contractor shall have personnel ready to deploy, immediately after issuance of a task order to support contingency operations and for the duration of the period of performance or redeployment to CONUS. The Contractor shall ensure personnel providing support under this task are fully prepared for deployment, and have complied with all deployment processing criteria identified by the COR.

The Contractor shall provide technical support to Marine Corps units engaged in contingency military operations in hostile environments, under hazardous and dangerous conditions. These operations are conducted in conditions of political violence, terrorist activity, armed conflict, insurrection, civil or military strife, and humanitarian aid. Requests for support of military operations are negotiated between the Contracting Officer, Contractor, and the COR.

Contractor personnel supporting contingency operations shall be deployed for no more than one year increments and for the duration of the contingency Operations. Normal working hours are set by the supported unit. During exercise support, the hours may be extended to no more than 12 hours a day, seven days a week.

Contractor support during contingency combat operations under this

PWS, is addressed in DoD Instruction (DoDI) 3020.41.

PROGRAM MANAGEMENT AND ADMINISTRATION 3.4

Program management is embedded in the tasks in sections 3.1 through

3.3.

The Contractor shall support program management reviews on a quarterly basis. The Contractor shall ensure that the requirements of this PWS are met to the standards and conditions identified in the Government’s

Quality Assurance Surveillance Plan (QASP). The Contractor shall keep the Government informed at all times of any personnel staffing or performance issues that have a direct impact on the Contractor’s ability to meet the requirements of the contract.

The Contractor’s program manager shall coordinate with the COR for any issue that may impact cost, schedule, or performance, to include schedule changes required to support activities outside the normal working hours. The Contractor shall coordinate with the COR any changes to the schedule, ten working days prior to the start of the event, to ensure there are no gaps in support.

The Contractor shall provide the Government access to all data and data files developed under this contract, including working-level documents and supporting information. The Government shall have unlimited rights to all data developed under this contract and any or all such data shall be delivered to the government when requested on a mutually agreed schedule that will target two weeks but never exceed

30 days.

TRANSITION PLAN 3.5

The services under this solicitation are vital to the Government and must be continued without interruption. The Offeror is required to submit a written transition plan that describes how the Offeror will be ready to provide services not later than 30 days after the contract award date.

4 DELIVERABLE AND INSTRUCTIONS

DELIVERABLES 4.1

Prior to the first submission of any deliverable, the Contractor shall provide the COR a copy of the formatted deliverable for format approval, unless otherwise stated in this PWS. All deliverables

(Enclosure 1) are to be submitted to the COR.

4.1.1 MONTHLY SYSTEMS ANALYSIS

The primary purpose of the monthly systems analysis is to aggregate the incidents conducted by all OFSG personnel, identify common or trending issues by system and by major operating forces commands

(e.g., MEFs, Marine Forces Reserve, Marine Forces Europe), analyze the issues, and provided recommended solutions to the individual system’s program office and the operating forces headquarters elements.

The contractor shall deliver the monthly systems analysis by the 15th of each month. The report shall include, but is not limited to:

A description of the services provided, and any significant technical data created or collected during the reporting period.

Analysis of incidents encountered the previous month, including significant issues discovered, a description of the identified problem, any temporary or work-around solutions attempted, the temporary or work-around solution of choice, and the recommended permanent.

A list of current programmatic issues with recommended solutions.

The primary purpose of the monthly status report is to identify issues experienced by users that are not addressed by system development and support organizations at MARCORSYSCOM and other acquisition agencies, and directly communicate those issues.

CDRL A001 – CONTRACTOR’S PROGRESS, STATUS, AND MGMT REPORT – MONTHLY SYSTEMS

ANALYSIS

4.1.2 MONTHLY PERFORMANCE REPORT

The primary purpose of the monthly performance report is to tie the performance of the contractors covered under a specific task order to the quality assurance surveillance plan (QASP) standards and metrics.

The report will be provided to each task order customer.

The contractor shall deliver the monthly performance report by the

15th of each month. The report shall include, but is not limited to:

A description of the services provided, and the products, events, and deliverables completed and any technical data created or collected, during the reporting period.

Over-the-shoulder training provided to include number of personnel trained and systems involved.

A report card covering the measures of performance for the reporting month against the targeted measures of effectiveness and the preceding month’s measure of performance.

CDRL A002 – CONTRACTOR’S PROGRESS, STATUS, AND MGMT REPORT – MONTHLY

PERFORMANCE REPORT

4.1.3 MONTHLY FINANCIAL FORECAST REPORT

The Contractor shall deliver an electronic monthly financial forecast status report by the 10th of each month, in the current version of

Microsoft Office® Word or Excel used by MCTSSA.

The Contractor shall provide a monthly financial status report that includes the following:

1. Identification of resources, including hours, labor, and travel costs for completed, pending, and projected tasks, and for each task order.

2. Provide forecasted cost data detailing the pending and projected expenditures to facilitate proper financial management of this task order.

CDRL A003 – CONTRACTOR’S PROGRESS, STATUS, AND MGMT REPORT – MONTHLY FINANCIAL

FORECAST REPORT

4.1.4 WEEKLY STAFFING REPORT

The Contractor shall provide a weekly personnel staffing report. This report is due by close of business 1700 PST every week. The report shall include details for current and projected personnel deficiencies, projected dates of resolution of deficiencies, and any impact to the tasks being affected.

CDRL A004 – CONTRACTOR’S PROGRESS, STATUS, AND MGMT REPORT – WEEKLY STAFFING

REPORT

4.1.5 WEEKLY EMBEDDED DEPLOYED SUPPORT STATUS

The Contractor shall provide a weekly embedded deployed support status report. This report is due by 1700 PST every week. The report shall include the name of the specific TSS task, location of temporary additional duty (TAD), names of C4I analysts, list of tactical systems supported, and dates of deployment.

CDRL A005 – CONTRACTOR’S PROGRESS, STATUS, AND MGMT REPORT – WEEKLY EMBEDDED

DEPLOYED SUPPORT STATUS

4.1.6 CENSUS REPORT

The Contractor shall electronically submit a monthly employee census information report to the Contracting Officer and COR. Information shall be current as of the 25 th day of each month and received by the

Contracting Officer no later than the first business day of the following month. The following information shall be provided for each geographical location in which work was performed:

1. The total number of personnel (prime and subcontractors at all tiers).

2. The total number of U.S. citizens (prime and subcontractors at all tiers).

3. Name of province in which the work was performed.

4. The names of all company personnel who enter and update employee data in the Synchronized Predeployment and Operational Tracker

(SPOT) IAW Defense Federal Acquisition Regulation Supplement

(DFARS) 252.225-7040 or DFARS DOD class deviation 2007-O0010.

CDRL A006 – CONTRACTOR’S PROGRESS, STATUS, AND MGMT REPORT – CENSUS REPORT

INSTRUCTIONS 4.2

4.2.1 DISTRIBUTION STATEMENT

A distribution statement shall appear on the cover or title page of all new and updated unclassified deliverable technical documents, data, and information (including engineering drawings, technical notes, test or technical reports, test procedures, and computer software documentation), whether produced in hard-copy or in digital format: “DISTRIBUTION STATEMENT D: Distribution authorized to the

Department of Defense and U.S. DoD contractors only; Administrative or

Operational Use, APR 2017. Other requests for this document shall be referred to the Commanding Officer, Marine Corps Tactical Systems

Support Activity, Box 555171, Camp Pendleton, California 92055-5171.”

4.2.2 DELIVERY

Deliverables associated with the above specified tasks shall be subject to the performance standards and acceptable quality levels specified in the QASP, Enclosure (2).

4.2.3 UNCLASSIFIED END PRODUCTS

Unclassified end products shall be delivered with a letter of transmittal to the COR.

4.2.4 CLASSIFIED END PRODUCTS

All classified material shall be shipped or mailed, in or out of the command, via Federal Express (FEDEX) or United States Postal Service

(USPS) registered mail. Material shipped out of the command shall be shipped or mailed only by the Classified Material Control Center

(CMCC) custodian. FEDEX or USPS registered mail is the only approved methods for shipping classified material.

Classified material sent via FEDEX, will use the following address:

COMMANDING OFFICER

ATTENTION MCTSSA CMCC

BLDG 31345 SUPPLY

CAMP PENDLETON, CA 92055-5171

Classified material sent via registered mail, will use the following address:

COMMANDING OFFICER

ATTENTION MCTSSA CMCC

BOX 555171

CAMP PENDLETON, CA 92055-5171

A copy of the letter of transmittal shall be forwarded to the COR.

All classified documents shall be handled, marked, transmitted, safeguarded, and controlled in accordance with the NISPOM (DoD

Directive 5220.22-M).

4.2.5 SCHEDULE OF DELIVERIES

The Contractor shall provide a written request for all delivery schedule revisions at least seven calendar days prior to the required delivery date, for Government evaluation and approval. Revised delivery dates may only be authorized by issuance of a duly executed modification to the contract by the Contracting Officer.

4.2.6 INSPECTION OF DELIVERABLES

The COR will inspect all deliverables at the place of delivery

(MCTSSA).

Inspection and acceptance of the contract deliverables are the responsibility of the COR, unless otherwise specified in the contract.

The COR will make official acceptance notification to the Contractor on all final deliverables via signature of acceptance. Rejection of deliverables will be provided to the Contractor via written correspondence. Deliverables requiring minor corrections will be verbally discussed with the Contractor and noted on the deliverable products. A revised deliverable shall be resubmitted to the

Government within three calendar days, unless the Government and

Contractor agree on a different schedule due to the scope of required modifications.

All deliverables shall be submitted to the COR in soft copy format and be clearly labeled to indicate content. All soft copy deliverables shall be in the current version of Microsoft Office® used by MCTSSA.

A contract modification will be signed prior to submission of any agreed to changes in deliverable formats.

5 PERIOD OF PERFORMANCE

The IDIQ contract has a 54 month ordering period beginning on the date of award plus a 6-month option to extend ordering period. The period of performance for individual tasks will be specified on individual task orders and services are expected to begin on 7 September 2017.

6 GOVERNMENT FURNISHED ACCESS

ACCESS TO GOVERNMENT FACILITIES AND EQUIPMENT 6.1

The Government will provide sufficient workspace and equipment to accommodate Contractor staff throughout the duration of the performance period. Access to government telephone services will be available in the designated work area, but restricted to government-contractor coordination and communications necessary for contractor business relevant to this PWS.

The Government will provide access to the required facilities at each work site for the performance of the tasking within this PWS during normal, site-specific working hours. Any unclassified contractor-furnished laptops must be logged in with the applicable entry control point sentry. Access to government facilities must be scheduled with the TSS COR and site Security Officer at least one working day prior to access. The Contractor must obtain prior approval from the COR to access work sites during government holidays.

ACCESS TO GOVERNMENT FURNISHED INFORMATION AND NETWORKS 6.2

The Government will provide the Contractor access to the following information and automated services in support of this PWS:

1. Access to Marine Corps Enterprise Network (MCEN) to include a

Common Access Card (CAC) to support public key infrastructure

(PKI) access and Marine Corps Web Services if determined by the

Government to be necessary for the performance of the tasking within this PWS.

A user and e-mail account on the MCEN Nonsecure Internet Protocol

Routing Network (NIPRNet) MCEN-N, MCEN Secret Internet Protocol

Routing Network (SIPRNet) MCEN-S, and Combined Enterprise

Regional Information Exchange System (CENTRIXS) domains when determined by the Government to be necessary for the performance of the tasking within this PWS.

Network access and special equipment will be commensurate with the working environment of the Marine unit being supported.

Contractors are required to complete the first two classes listed below before being issued an e-mail account the other two classes are required training.

a. DoD-IAA-V12.0 – DoD Cyber Awareness Challenge V2

b. DoD-PII-2.0 – Privacy and Personally Identifiable Information

(PII) Awareness

c. DON Sexual Assault Prevention and Response (SAPR) online refresher training

d. Annual Counterintelligence Awareness Training/Briefing at

MCTSSA or designated area, when available

2. Contractor personnel are authorized to receive training on unique government systems and software, when training is not available in the commercial sector.

7 SECURITY REQUIREMENTS

The Contractor will need to access classified areas and C4I systems at all worksites. All Contractors that require a SIPRNet account shall be provided with a North Atlantic Treaty Organization (NATO) brief.

Technical tasks associated with this PWS require access to classified information. The Contractor shall not divulge information regarding files, data, processing activities, processing functions, user identifications (IDs), passwords, or other knowledge gained to anyone not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standards of conduct.

SECURITY CLEARANCE 7.1

At a minimum a Secret clearance is required for analyst, technical, and engineering personnel supporting this PWS and a security clearance up to the Top Secret with a favorable adjudicated Single Scope

Background Investigation (TS/SBBI) or Tier 5 (T5/T5R) investigation level maybe required in option year one and beyond, for an estimated nine personnel. No interim/temporary access will be accepted. The

Contractor shall possess a Joint Personnel Adjudication System (JPAS) account.

DD FORM 254 7.2

The work to be performed under this PWS as delineated in the DD Form

254, Attachment (2), can involve access to the handling of classified material up to TS/SSBI. For the base period, personnel will require access at the SECRET and below level, however, in option year one and beyond, it is estimated nine personnel will require TS/SSBI access level and the remainder SECRET and below. The requirements in clause

FAR 52.204-2, Security Requirements and FAR 252.225-7048, Export

Controlled Items are applicable to this order. The Contractor shall be responsible for all security aspects of the work performed under this contract and assure compliance with the NISPOM (DoD Directive

5220.22-M).

Contracted personnel’s clearances shall be verifiable in the Joint

Personnel Adjudication System (JPAS).

SITE SECURITY 7.3

The Contractor shall comply with site location security regulations and policies. The Contractor’s staff shall be U.S. or naturalized citizens, whose military duty was not terminated by a dishonorable or bad conduct discharge, are not debarred from handling export controlled materials, are not subject to an outstanding criminal warrant, have no felony convictions, and have no more than three criminal misdemeanor convictions within the last seven years.

Additionally, no criminal misdemeanor or felony conviction for crimes of a sexual nature, crimes of violence, crimes related to gang activity or hate crimes, or crimes resulting from the possession or distribution of any illegal drug are acceptable.

All Contractor personnel aboard military installations, with the exception of emergency personnel, shall wear a properly issued badge at all times. Contractor personnel shall comply with all emergency rules and procedures established for each worksite. All personnel aboard Government installations are subject to random inspections of their vehicles, personal items, and of themselves. Consent to these inspections is given when personnel enter Government installations.

OPSEC REQUIREMENTS 7.4

The practice of Operations Security (OPSEC) prevents the inadvertent compromise of sensitive unclassified and classified activities, capabilities, or intentions at the tactical, operational, and strategic levels. The Contractor’s staff must adhere to all government OPSEC measures currently in place at the Government facility. The Contractor shall provide OPSEC training to all

Contractor personnel supporting this effort.

Contractors shall not take pictures from any device while aboard the compound or in the test areas.

8 STAFFING

The Contractor shall provide the contractor personnel to meet the requirements of the PWS and contract. The contractor shall propose the labor categories required for their technical approach and the personnel required to manage the overall contract. For each labor category, at a minimum, the proposal should address:

Labor Category Job Title and Description of Duties

Qualifications including education and certifications

Experience, specifically including years of experience with C4I systems

Other relevant information

All Contractor personnel must have at least 5 years of experience with two or more USMC/Joint C4I systems. In addition, all contractor personnel shall possess a Security+ Certification (except for the PM) and sign a Non-Disclosure Agreement (NDA).

The labor categories, qualifications, and experience requirements proposed by the successful offeror will be incorporated into the resulting contract and become the minimum qualifications for the life of the contract.

The selection, assignment, reassignment, transfer, supervision, management, and control of Contractor personnel in performance of this

PWS shall be the responsibility of the Contractor.

All Contractor personnel shall be in professional, suitable attire

(appropriate to the particular condition, occasion, location, and job assignment). All Contractor personnel shall conduct themselves in a professional, courteous manner and shall comply with the directives pertaining to privately owned vehicles at the specific location.

All Contractor personnel shall have the ability to communicate clearly in writing and speak English.

IDENTIFICATION 8.1

Contractor personnel shall identify themselves or be introduced as

Contractor personnel supporting the TSS contract, and display badges or other identification for meetings with Government personnel.

Contractor personnel shall appropriately identify themselves as

Contractor personnel supporting the TSS in telephone conversations and in formal and informal written correspondence.

9 TRAVEL REQUIREMENTS

Travel required to support exercises and contingency operations as discussed in PWS 3.0 will be authorized by the issuance of task orders. Travel must be coordinated with the COR. All travel shall be in accordance with FTR, JTR, and FAR Part 31, as applicable.

10 ORGANIZATIONAL CONFLICT OF INTEREST

(a) Organizational Conflict of Interest means that because of activities or relationships with other persons, a person is unable or potentially unable to render impartial assistance or advice to the

Government, or the person’s objectivity in performing the contract work is or might be otherwise impaired, or a person has an unfair competitive advantage. Person, as used herein, includes corporations, partnerships, joint ventures, and other business enterprises.

(b) The Contractor warrants to the best of their knowledge and belief, except as otherwise set forth in the contract, the Contractor does not have any organizational conflict of interest(s), as defined in paragraph (a).

(c) It is recognized that the effort to be performed by the contractor under this contract may create a potential organizational conflict of interest on the instant contract or on a future acquisition. To avoid this potential conflict of interest, and at the same time to avoid prejudicing the best interest of the Government, the right of the

Contractor to participate in future procurement of equipment and/or services that are the subject of any work under this contract shall be limited as described below in accordance with the requirements of FAR

9.5.

(d) (1) The Contractor agrees that it shall not release, disclose, or use in any way that would permit or result in disclosure to any party outside the Government any proprietary information provided to the

Contractor by the Government during or as a result of performance of this contract. Such information includes, but is not limited to, information submitted to the Government on a confidential basis by other persons. Further, the prohibition against release of Government provided information extends to cover such information whether or not in its original form, (e.g., where the information has been included in contractor generated work or where it is discernible from materials incorporating or based upon such information). This prohibition shall not expire after a given period of time.

(d) (2) The Contractor agrees that it shall not release, disclose, or use in any way that would permit or result in disclosure to any party outside the Government, any information generated or derived during or as a result of performance of this contract. This prohibition shall expire after a period of one year after the completion of performance on this contract.

(d) (3) The prohibitions contained in subparagraphs (d)(1) and (d)(2) shall apply with equal force to any affiliate of the Contractor, any subcontractor, consultant, or employee of the contractor, any joint venture involving the Contractor, any entity into or with which it may merge or affiliate, or any successor or assign of the Contractor. The terms of paragraph (f) of this Special Contract Requirement relating to notification shall apply to any release of information in contravention of this paragraph (d).

(e) The Contractor agrees if after award of the contract an actual or potential organizational conflict of interest is discovered; the

Contractor shall make immediate and full disclosure in writing to the

Contracting Officer. The notification shall include a description of the actual or potential organizational conflict of interest; a description of the action the Contractor has taken or proposes to take to avoid, mitigate, or neutralize the conflict; and any other relevant information that would assist the Contracting Officer in making a determination on this matter. Notwithstanding this notification, the

Government may terminate the contract for the convenience of the

Government, if determined to be in the best interest of the

Government.

(f) Notwithstanding paragraph I above, if the Contractor was aware, or should have been aware, of an organizational conflict of interest prior to the award of this contract or becomes, or should become, aware of an organizational conflict of interest after award of this contract and does not make an immediate and full disclosure in writing to the Contracting Officer, the Government may terminate this contract for default.

(g) If the Contractor takes any action prohibited by this requirement or fails to take action required by this requirement, the Government may terminate this contract for default.

(h) The Contracting Officer’s decision as to the existence or nonexistence of an actual or potential organizational conflict of interest shall be final and is not subject to the clause of this contract entitled DISPUTES (FAR 52.233-1).

(i) Nothing in this requirement is intended to prohibit or preclude the Contractor from marketing or selling to the United States

Government its product lines in existence on the effective date of this contract; nor, shall this requirement preclude the Contractor from participating in research and development or delivering any design development model or prototype of any such equipment.

Additionally, sale of catalog or standard commercial items are exempt from this requirement.

(j) The Contractor shall promptly notify the Contracting Officer, in writing, if it has been tasked to evaluate or advise the Government concerning its own products or activities or those of a competitor to ensure proper safeguards exist to guarantee objectivity and to protect the Government’s interest.

(k) The Contractor shall include this requirement in subcontracts of any tier, which involve access to information, situations, or conditions covered by the preceding paragraphs, substituting

“subcontractor” for “Contractor” where appropriate.

(l) The rights and remedies described herein shall not be exclusive and are in addition to other rights and remedies provided by law or elsewhere included in this contract.

(m) Compliance with this requirement is a material requirement of this contract.

(n) Each contractor employee shall sign a Non-Disclosure Agreement

(NDA).

A-1

APPENDIX A – ACRONYMS

Acronyms, Abbreviations, Definitions, Codes, and Symbols

Item Meaning

C2 Command and Control

C4I Command, Control, Communications, Computer, and

Intelligence

CAC Common Access Card

CAC2S Common Aviation Command and Control System

CENTRIXS Combined Enterprise Regional Information Exchange System

CLIN Contract Line Item Number

CMCC Classified Material Control Center

COB Close of Business

COC Combat Operations Center

COCEX Combat Operations Center Exercise

CONUS Continental United States

COP Common Operational Picture

COR Contracting Officer’s Representative

CR/AF Crisis Response (CR)/Africa (AF)

DBA Defense Base Act

DDS-M Data Distribution System – Modular

DFARS Defense Federal Acquisition Regulation Supplement

DoD Department of Defense

DST Deployed Support Team

ECCS Expeditionary Command and Control Suite

FAR Federal Acquisition Regulation

FEDEX Federal Express

FoS Family of Systems

FSR Field Service Representative

FSS Fires Support Systems

G&A General & Administrative

GCCS Global Command and Control System

GCCS-TCO

Global Command and Control System – Tactical Combat

Operations

GSA General Services Administration

A-2

Acronyms, Abbreviations, Definitions, Codes, and Symbols

Item Meaning

GSR Government Service Representative

IAW In Accordance With

IAWIP Information Assurance Workforce Improvement Program

IOS Intelligence Operating System

ITX Integrated Training Exercise

JCR Joint Capabilities Release

JPAS Joint Personnel Adjudication System

JTCW Joint Tactical Common Operational Picture Workstation

KO Contracting Officer

LSE Large Scale Exercise

MAGTF Marine Air-Ground Task Force

MARCENT Marine Corps Forces Central

MARCIMS Marine Civil Affairs Information Management System

MARCORSYSCOM Marine Corps Systems Command

MARFORCOM Marine Corps Forces Command

MARFOREUR/AF Marine Corps Forces Europe and Africa

MARFORRES Marine Corps Forces Reserves

MCB Marine Corps Base

MCEN Marine Corps Enterprise Network

MCEN-N MCEN NIPRNet

MCEN-S MCEN SIPRNet

MCTSSA Marine Corps Tactical Systems Support Activity

MEB Marine Expeditionary Brigade

MEF Marine Expeditionary Force

MEU Marine Expeditionary Unit

MFR Marine Forces Reserve

MIP Multilateral Interoperability Programme

MIT MAGTF Integration Testing

MOS Military Occupational Specialty

MWTC Mountain Warfare Training Center

NATO North Atlantic Treaty Organization

NBC Nuclear Biological Chemical

NDA Non-Disclosure Agreement

A-3

Acronyms, Abbreviations, Definitions, Codes, and Symbols

Item Meaning

NIPRNet Non-secure Internet Protocol Routing Network

NISPOM National Industrial Security Program Operating Manual

NOTM Networking on-the Move

OCONUS Outside Continental United States

ODC Other Direct Costs

OFS Operational Forces Support

OFTSSC Operating Forces Tactical Systems Support Center

OPSEC Operations Security

PII Personally Identifiable Information

PKI Public Key Infrastructure

PPE Personal Protective Equipment

PWS Performance Work Statement

QASP Quality Assurance Surveillance Plan

RA Receipts and Acceptance

SAPR Sexual Assault Prevention and Response

SATCOM Satellite Communications

SIPRNet Secret Internet Protocol Routing Network

SME subject matter expert

SPEED Systems Planning, Engineering, and Evaluation Device

SPMAGTF Special Purpose Marine Air-Ground Task Force

SPOT Synchronized Predeployment and Operational Tracker

SSC Atlantic Space and Naval Warfare Systems Center Atlantic

TAD temporary additional duty

TBMCS Theater Battle Management Core Systems

TCO Tactical Combat Operations

TSM Transition Switch Module

TSS Tactical Systems Support

TTECG Tactical Training Exercise Control Group

USPS United States Postal Service

UUNS Urgent Unfunded Needs Statement

VS Video Scout

VSAT Very Small Aperture Terminal

WAWF Wide Area Workflow

A-4

Acronyms, Abbreviations, Definitions, Codes, and Symbols

Item Meaning

WTI Weapons and Tactics Instructor

YPG Yuma Proving Grounds

1-1

ADDENDUM 1 – NOTIONAL TSS BILLET REQUIREMENTS BY

LOCATION (1 FULL TIME EQUIVALENT = 1,880 HOURS)

Notional TSS Billet Requirements by Location

Location Qty Billet

MCTSSA/OFTSSC*

Program Manager (Built into labor rates)

Technical Manager (Built into labor rates)

1 C4I Analyst (C2 Site Lead)

Command, Control, Communications, Computer and

Intelligence (C41) Analysts (Command and

Control (C2)) Analysts

2 C4I Analysts (Tactical Communications)

2 C4I Analysts (CAC2S)

5 C4I Analysts (Combat Operations Center(COC))

1 C4I Analysts (Communications Security)

C4I Analyst (Identity Dominance System-Marine

Corps)

2 C4I Analysts (Joint Capabilities Release)

3 C4I Analysts (Target Handling System)

C4I Analysts (Marine Civil Information

Management System)

1 C4I Analyst (Fires Support Systems (Indirect))

1 C4I Analyst (Video Scout)

C4I Analysts (Satellite Communications

(SATCOM))

2 C4I Analysts (SharePoint)

2 C4I Analysts (Unit Reference Number Repository)

1 C4I Analyst (Networking On-The-Move)

C4I Analyst (Modeled Meteorological Information

Management System)

I MEF

1 C4I Analyst (C2 Site Lead)

C4I Analyst [Expeditionary Command and Control

Suite (ECCS)]

II MEF

1 C4I Analyst (C2 Site Lead)

1 C4I Analyst ( Tactical Networking)

1 C4I Analyst (C2)

1-2

Notional TSS Billet Requirements by Location

Location Qty Billet

2d MEB

2 C4I Analysts (C2)

2 C4I Analysts (COC)

3 C4I Analysts (SharePoint)

III MEF

1 C4I Analyst (C2 Site Lead)

6 C4I Analysts (Tactical Networks)

2 C4I Analysts (SATCOM)

2 C4I Analyst (SharePoint)

1 C4I Analyst (ECCS)

TTECG (29

Palms) 1 C4I Analyst (C2)

MARFORCOM 2 C4I Analysts (SharePoint)

MARFOREUR/AF

2 C4I Analysts (C2)

4 C4I Analyst (SharePoint)

**5th MEB

BAHRAIN

2 C4I Analysts (SharePoint)

MARFORRES 1 C4I Analyst (C2)

NOTE: C4I analysts with (system) identified, indicates particular emphasis in supporting this system.

* See OFTSSC Deployed Support Team (DST) section 3.2

** Contingency billets

2-1

ADDENDUM 2 – NOTIONAL ESTIMATED EXERCISE/EVENT SUPPORT SCHEDULE

Notional Exercise/Event Support Schedule

Date Exercise/Event Locations

From

Locations

To Systems Persons

Days

12 Hour

Day

May 2016 ITX-3-17 MCTSSA I MEF

COC, NOTM ,C4I

Systems 4 5

May 2016 Emerald Warrior MCTSSA MARFORRES CAC2S 2 7

June 2016 Heavy Metal MCTSSA MARFORRES VSAT, C4I Systems 2 5

June 2016 II MEF COC Upgrade MCTSSA II MEF COC 2 7

June 2016 22d MEU MIT MCTSSA 22d MEU C4I Systems 3 7

June 2016 LSE MCTSSA I MEF COC, C4I Systems 4 7

July 2016 24th MEU MIT MCTSSA 24th MEU C4I Systems 1 7

July 2016 III MEF COC Upgrade MCTSSA III MEF COC 2 7

August 2016 Ulchi Freedom

Guardian 2016 MCTSSA III MEF C4I Systems 2 12

August 2016 MFR COC Upgrade MCTSSA CONUS COC 2 7

September 2016 SPMAGTF CR/AF MCTSSA MARFOREUR COC, C4I Systems 3 17

September 2016 22d MEU FIT MCTSSA 22d MEU C4I Systems 2 5

October 2016 WTI 1-17 MCTSSA YPG, AZ C4I Systems 1 20

October 2016 ITX MCTSSA 29 Palms C4I Systems 2 7

December 2016 31st MEU MIT MCTSSA 31st MEU C4I Systems 2 7

December 2017 Steel Knight MCTSSA I MEF C4I Systems 5 4

January 2017 II MEF COC Upgrade MCTSSA II MEF COC 2 7

2-2

Notional Exercise/Event Support Schedule

Date Exercise/Event Locations

From

Locations

To Systems Persons

Days

12 Hour

Day

January 2017 SPMAGTF CR/AF MCTSSA MARFOREUR C2PC, GCCS, MIP 2 7

January 2017 22d MEU MIT MCTSSA 22d MEU C4I Systems 3 7

February 2017 Cobra Gold MCTSSA III MEF C4I Systems 3 10

February 2017 III MEF COC Upgrade MCTSSA III MEF COCEX 2 7

February 2017 11th MEU MIT MCTSSA 11th MEU C4I Systems 2 7

March 2017 SPMAGTF CR/AF MCTSSA MARFOREUR C2PC, GCCS, MIP 2 5

March 2017 MFR COC Upgrade MCTSSA CONUS COC 2 7

March 2017 Bold Quest MCTSSA III MEF TBMCS, C4 2 10

March 2017 Mountain Warrior MCTSSA MWTC COC, C4I Systems 2 5

April 2017 WTI 2-17 MCTSSA YPG, AZ CAC2S, COC 1 18

April 2017 Balikatan 2017 MCTSSA III MEF C4I Systems 2 12

3-1

ADDENDUM 3 – CONTINGENCY OPERATIONS

To assist vendors with contingency operations planning, the MCTSSA

Contracting Officer is publishing the following guidance.

1. The Contractor shall, in response to formal tasking, dispatch technical personnel in support of contingency operations related to PWS requirements. Contingency operations are defined as operations in response to conditions such as political violence, terrorist activity, armed conflicts, insurrection, or civil/military strife. MCTSSA contracts will provide bilateral notification of such contingency operations.

2. The Contractor shall, when providing support:

a. Identify personnel who will be deploying and provide all required personnel data to MCTSSA.

b. Identify the duration of the deployment period for each individual.

c. Comply with authorized Letters of Instruction and other formal guidance published to support the contingency and deemed applicable by MCTSSA.

d. Ensure that personnel deployed to support contingency operations are medically qualified and fit to endure physical conditions associated with the climate, terrain, and operational environment anticipated for the duration of the duty assignment. The employer shall certify, in writing, that their assigned personnel are fit and qualified to serve in the assignment and have been briefed on the anticipated conditions.

e. Obtain a quote for Defense Base Act Insurance coverage for the affected employees as required by statute and provide this to

MCTSSA for final authorization/approval to incur any costs.

The Government will NOT pay for any additional personal insurance coverage for riders.

f. Identify additional contractor furnished equipment for use on the contract not currently covered by the existing task order.

g. Identify additional medical or immunization requirements, and, if necessary, reimburse the Government for use of military medical services provided to Contractor employees.

h. Identify clothing purchased specifically to support contingency operations, which must be approved by MCTSSA.

3-2

i. Ensure that deployed personnel are not in possession of firearms, explosives or other materials deemed as weapons.

j. Identify transportation requirements anticipated beyond those provided by the Government.

3. The Government will, when support is required:

a. Provide transportation for Contractor personnel and baggage to and from the area of operations and transportation within the area of operations, using military transport. If commercial transportation is required, including commercial air or rental car, it will be billable as an ODC (Other Direct Costs).

Transportation and travel shall be in accordance with Marine

Air-Ground Task Force (MAGTF) Commander directives and joint travel…