Draft_17R7602_PWS_v23_-_10_Mar_2017.pdf

PERFORMANCE WORK STATEMENT

FOR

TACTICAL SYSTEMS SUPPORT

CONTRACTOR SUPPORT SERVICES

10 Mar 2017

PREPARED BY:

OPERATING FORCES SUPPORT BRANCH

MARINE CORPS TACTICAL SYSTEMS SUPPORT ACTIVITY

CAMP PENDLETON, CA 92055-5171

PWS for TSS 14 Dec 2016 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

OFTSSC On-Site Technical Support ........................... 6 3.1

OFTSSC Exercise Deployed Support Team (DST) ................ 6 3.2

CONUS On-Site Support ...................................... 6 3.3

CONUS Exercise Deployment Support .......................... 7 3.4

OCONUS On-Site Support ..................................... 7 3.5

OCONUS Exercise Support .................................... 8 3.6

Contingency Support ........................................ 8 3.7

Training ................................................... 9 3.8

Program Management and Administration ...................... 9 3.9

4 DELIVERABLE AND INSTRUCTIONS

Deliverables .............................................. 10 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 .............................................. 12 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

5 PERFORMANCE LOCATIONS

6 INSPECTION OF DELIVERABLES

7 PERIOD OF PERFORMANCE

8 GOVERNMENT FURNISHED ACCESS

Access to Government Facilities and Equipment ............. 15 8.1

Access to Government Furnished Information and Networks ... 15 8.2

9 SECURITY REQUIREMENTS

Security Level ............................................ 16 9.1

Security Clearance ........................................ 17 9.2

DD Form 254 ............................................... 17 9.3

Site Security ............................................. 17 9.4

OPSEC Requirements ........................................ 18 9.5

10 PERSONNEL

iii

Key Personnel ............................................. 18 10.1

Non-key Personnel (Contractor Staff) ...................... 18 10.2

Identification ............................................ 19 10.3

11 TRAVEL REQUIREMENTS

12 INVOICING

13 ADMINISTRATIVE AUTHORITY

Contracting Officer ....................................... 20 13.1

Contracting Officer Representative (COR) .................. 20 13.2

14 ORGANIZATIONAL CONFLICT OF INTEREST

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

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

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

ADDENDUM 3 – TSS Billet RGMTS by Location .......................... 3-1

ADDENDUM 4 – Schedule of Allowable Costs ........................... 4-1

LIST OF TABLES

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

Table 3-2 TSS Supported Sites

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 and Table 3-2 list the systems, units, and organizations 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. OFTSSC Standard Operating Procedures (SOP), June 2016.

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)

Technical support includes eleven hours a day, Monday through Friday at the MCTSSA OFTSSC, on-site technical support at specified Marine

Corps organizations worldwide, and discrete exercise and operational support based on the mission of the supported unit (e.g., hazardous duty, combat operations, peace-keeping, humanitarian relief). The

Contractor shall plan shift work and on-call support during the off hours (1730 to 0630, Monday through Friday) and 24 hours a day

Saturday and Sunday, based on operational requirements. Shift work and on-call applies to OFTSSC only and is a collaborative effort between Contractor and Government personnel within the OFTSSC. The schedule for shift work and on call support is managed by Contractor

Leads and adheres to an eight hour per day work schedule.

The Contractor shall provide full-time, on-site technical support to the Marine Corps units listed in Table 3-2.

Table 3-2 TSS Supported Sites

TSS Supported Sites

Organization Para

3.1

Para

3.2

Para

3.3

Para

3.4

Para

3.5

Para

3.6

Para

3.7

Para

3.8

Para

3.9

MCTSSA (San

Diego, CA) X X X X X

I MEF (San

Diego, CA) X X X

II MEF (Camp

Lejeune, NC) X X X

III MEF

(Okinawa, JPN) X X X

MARFORCOM

(Norfolk, VA) X X X

MARFOREUR/

Africa

(Stuttgart, DEU)

X X X

MARFORRES (New

Orleans, LA) X X X

Tactical

Training

Exercise

Control Group

(TTECG)

Twentynine

Palms, CA

X X X

2d Marine

Expeditionary

Brigade (MEB)

Camp Lejeune, NC

X X X X X

5th MEB Marine

Corps Forces

Central

(MARCENT)

Bahrain

X X

OFTSSC ON-SITE TECHNICAL SUPPORT 3.1

The Contractor shall be prepared to provide fully qualified personnel to support the MCTSSA, OFTSSC, upon issuance of a task order and for the duration of the period of performance.

The support is for fielded tactical C4I systems (Table 3-1) and includes issue resolution, troubleshooting, assistance with system administration, system software and hardware installation, technical guidance, systems integration, test support (e.g., Developmental

Testing (DT), Operational Testing (OT), and engineering assessments), the documentation of issues, recommendations, and resolutions, and limited training. OFTSSC technical support is primarily provided via telephone, e-mail, internet chat, and other communications protocols.

For planning purposes, the Contractor can expect to receive an estimated 25 requests for support per day, spread across the systems identified in Table 3-1. The Contractor shall expect a range of trouble calls, from requests for password resets to systems troubleshooting concerns. Approximately 80% of trouble calls are resolved within 24 hours from the receipt of the call. Complex issues

(non-contingency related support) are normally resolved within several weeks.

The Contractor shall assist in managing the receipt, routing, resolution, and trend analysis of requests for support in accordance with (IAW) the OFTSSC SOP.

OFTSSC EXERCISE DEPLOYED SUPPORT TEAM (DST) 3.2

Contractor personnel supporting OFTSSC will provide technical support to various CONUS locations in support of exercises, equipment fielding, and test events. The Contractor shall also expect to deploy to OCONUS locations as part of the DST. On average, the DST deploys each Contractor four times a year for one to two weeks. Contingency deployments are scheduled for no more than 90 days (with an average of

60 days) to assist Marine Corps units engaged in contingency operations (ADDENDUM 1).

CONUS ON-SITE SUPPORT 3.3

The Contractor shall provide technically qualified personnel for on-site technical support to CONUS units and organizations upon issuance of a task order and for the duration of the performance. The technical support provided is for the fielded C4I systems identified in Table 3-1 or identified by the COR to the KO.

The Contractor shall provide on-site technical support to Marine Corps units throughout CONUS (see Table 3-2 and section 5 for the units and locations). The support is for fielded tactical C4I systems identified in Table 3-1, and includes issue resolution, troubleshooting, assistance with system administration, system software and hardware installation, technical guidance, systems integration (e.g., OT, DT, engineering assessments), documentation of issues, recommending solutions, and over-the-shoulder training. The

Contractor shall provide on-site support during normal working hours.

Normal working hours are set by the supported unit, not to exceed eight hours a day, Monday through Friday. Any support required above the normal work day, shall be coordinated with the COR or Government

Service Representative (GSR) for approval.

CONUS EXERCISE DEPLOYMENT SUPPORT 3.4

The Contractor shall provide technical support, to include assisting with planning, coordination, deployment of qualified technical support personnel, and post-exercise reporting, for limited-duration events

(e.g., system fielding and upgrades, preparation for or conduct of training, testing, or exercises). If additional support is required, Contractor personnel assigned to the OFTSSC may be required to augment on-site contractor technical support. For planning purposes, section

11 – Travel Requirements, refer to ADDENDUM 2 of this PWS, which provides a notational exercise/event support schedule for the contract 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.

OCONUS ON-SITE SUPPORT 3.5

The Contractor shall provide on-site technical support with fielded tactical C4I systems to OCONUS Marine Corps units and locations listed in Table 3-2 and section 5. On-site support includes assistance with issue resolution, troubleshooting, system administration, system installation, technical guidance, systems integration, test support

(e.g., DT, OT, and engineering assessments), documentation of issues, recommendations, resolutions, and over-the-shoulder training. The

Contractor shall provide on-site support during normal working hours.

Normal working hours are set by the supported unit, not to exceed eight hours a day, Monday through Friday. The Contractor shall coordinate with the COR or GSR for hours outside the normal working hours.

OCONUS EXERCISE SUPPORT 3.6

The Contractor shall provide technical support with fielded tactical

C4I systems to the OCONUS Marine Corps units and locations listed in

Table 3-2 and section 5, during exercises. The support shall include planning, coordination, deployment of qualified technical support personnel, and post-exercise reporting, for limited-duration events

(e.g., system fielding and upgrades, preparation for or conduct of training or testing events, operations and field exercises). If additional support is required, Contractor personnel assigned to the

OFTSSC may be used to augment on-site technical support. ADDENDUM 2 provides a notional exercise/event support schedule for the contract.

The Contractor shall coordinate and get approval from the COR or GSR for support that falls outside the 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 a day, seven days a week.

CONTINGENCY SUPPORT 3.7

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.

TRAINING 3.8

The Contractor personnel shall provide over-the-shoulder training for fielded tactical C4I systems to Marine Corps units worldwide as required. Over-the-shoulder training is not formal training. 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. Over-the-shoulder training is embedded in the tasks listed in sections 3.1 through 3.7.

PROGRAM MANAGEMENT AND ADMINISTRATION 3.9

Program management is embedded in the tasks in sections 3.1 through

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

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, DEC 2016. 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.

5 PERFORMANCE LOCATIONS

The performance of work associated with TSS will be performed at the following locations in CONUS and OCONUS:

Support of the OFTSSC, per section 3.1, will be performed primarily at MCTSSA, Camp Pendleton, CA and as required in support of other sites worldwide as part of the Deployed Support

Team.

Support of CONUS locations, per section 3.3, will be performed at various Marine Corps garrison locations. Examples include I MEF

(Marine Corps Base (MCB), Camp Pendleton, CA), II MEF and 2d MEB

(MCB, Camp Lejeune, NC), MARFORCOM (Norfolk, VA), Marine Forces

Reserve (New Orleans, LA), and TTECG (MCB Twentynine Palms, CA).

Performance of work in support of OCONUS locations, per section

3.5, will be performed at various overseas Marine Corps garrison locations. Examples include III MEF (MCB, Okinawa, Japan) and

Marine Forces Europe/Africa (Stuttgart, Germany). See ADDENDUM 2 for an estimated/notional number of personnel required by location.

Performance of work in support of contingency operations, per section 3.7, will be performed at various locations around the world in support of combat operations, such as 5 th

MEB MARCENT,

Bahrain.

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.

7 PERIOD OF PERFORMANCE

The base period of performance for this task is anticipated to be 6 months in duration from the date specified in the award, with four one-year option periods.

8 GOVERNMENT FURNISHED ACCESS

ACCESS TO GOVERNMENT FACILITIES AND EQUIPMENT 8.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 8.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.

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

SECURITY LEVEL 9.1

Technical tasks associated with this PWS require access to classified information and a security clearance up to the Secret level. 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 9.2

A Secret clearance is required for analyst, technical, and engineering personnel supporting this PWS. No interim clearance will be accepted.

The Contractor shall possess a Joint Personnel Adjudication System

(JPAS) account.

DD FORM 254 9.3

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

254, Attachment (2), involves access to the handling of classified material up to TOP SECRET with Single Scope Background Investigation.

It is estimated nine personnel will require this access level and the remainder working with 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 able to be confirmed in the

Joint Personnel Adjudication System (JPAS).

SITE SECURITY 9.4

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 9.5

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.

10 PERSONNEL

KEY PERSONNEL 10.1

The Contractor shall provide the relevant and recent experience for the key personnel identified below:

1. Program Manager

2. Technical Manager

Key personnel performing tasks under this PWS shall have at least ten years of recent experience and expertise with at least two or more of the Marine Corps fielded tactical C4I systems listed in Table 3-1 and shall be otherwise qualified to perform the work described in this

PWS. The Contractor shall provide the following documentation for key personnel:

Company name

Years of experience

C4I Projects managed

Degrees and Certifications

NON-KEY PERSONNEL (CONTRACTOR STAFF) 10.2

The Contractor staff shall have at least five years of recent experience and expertise with at least two or more of the Marine Corps fielded tactical C4I systems listed in Table 3-1 and shall be otherwise qualified to perform the work described in this PWS. The

Contractor shall employ and maintain a technically trained and experienced work force skilled on the C4I systems identified in Table

3 1. The billet requirements by location are listed in ADDENDUM 3.

The Contractor shall provide the COR a list of Contractor personnel by name, position, title, and location. All Contractor personnel shall possess a Security+ Certification and sign a Non-Disclosure Agreement

(NDA).

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 10.3

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.

11 TRAVEL REQUIREMENTS

The Contractor shall be required to travel when notified by the COR to the locations listed in ADDENDUM 2 in support of this PWS. Authorized travel shall be IAW FTR, JTR, and FAR Part 31. Actual travel will vary depending on technical issues and schedules, as they evolve throughout the period of performance. Schedule of other direct costs

(ODC) are contained in ADDENDUM 4.

12 INVOICING

The Contractor shall submit an electronic copy of invoices and supporting documentation no more than once a month via the Wide Area

Workflow (WAWF) Web site.

The Contractor shall be required to implement the DFARS process to submit an electronic payment request. To implement DFARS 252.232-

7003, Electronic Submission of Payment Requests (March 2008), the

Marine Corps utilizes WAWF- Receipt/Acceptance (WAWF-RA) to electronically process vendor requests for payment. This process allows DoD vendors to submit and track invoices and RA documents electronically. The Contractor shall be required to utilize this system when processing invoices and receiving reports. The Contractor shall 1) ensure an Electronic Business Point of Contact (EBPOC) is designated in Central Contractor Registration (CCR) at http://www.ccr.gov, and 2) register to use WAWF-RA at https://wawf.eb.mil, within ten calendar days after award of this contract or modification. Step-by-step procedures to register are available at https://wawf.eb.mil.

13 ADMINISTRATIVE AUTHORITY

CONTRACTING OFFICER 13.1

Only the Contracting Officer has sole authority to authorize deviations from the terms and conditions of this contract, including deviations from the specifications and requirements stated in this

PWS. In the event of a Contractor deviation, without the issuance of a duly executed contract modification, any related risks and costs shall be the responsibility of the Contractor.

CONTRACTING OFFICER REPRESENTATIVE (COR) 13.2

The COR is limited to providing program specific clarification to the contractor’s project manager. The COR does not have the authority to take action (directly or indirectly) that would change the pricing, quality, place of performance, delivery schedule, or any other terms and conditions of this contract or to authorize work outside the scope of this PWS. If the Contractor perceives the COR or other Government personnel is requesting an effort outside the scope of this contract, the Contractor shall promptly notify the Contracting Officer in writing. No action shall be taken by the Contractor until the

Contracting Officer has issued a contractual change or otherwise resolved the issue. The Government reserves the right to reassign the

COR position.

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

http://www.ccr.gov/ https://wawf.eb.mil/ https://wawf.eb.mil/

(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

DT Developmental Testing

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

A-2

Acronyms, Abbreviations, Definitions, Codes, and Symbols

Item Meaning

GSA General Services Administration

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…