Final_TSS_PWS_2013_02_11.docx.pdf

Performance Work Statement

For

Tactical Systems Support

11 February 2013

Prepared by:

Operating Forces Support Branch Marine Corps Tactical Systems Support Activity

Camp Pendleton, CA 92055-5171 i

TABLE OF CONTENTS

1 INTRODUCTION

1.1 Background

1.2 Scope

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

2.2 Guidance Documents

3 PERFORMANCE REQUIREMENTS

3.1 OFTSSC Technical Support

3.2 OFTSSC Deploy Support Team (DST)

3.3 Continental United States (CONUS) Support

3.4 CONUS Exercise Support

3.5 Outside Continental United States (OCONUS) Support

3.6 OCONUS Exercise Support

3.7 Contingency Operations Support

3.8 Training

3.9 Program Management & Administration

4 DELIVERABLES

4.1 Monthly Status Report

4.1.1 Monthly Financial Forecast

4.1.2 Weekly Staffing Status

4.2 After Action Report (AAR)

4.3 Census Report

4.4 Distribution Statement

4.5 Delivery Instructions

4.6 Unclassified End Products

4.7 Classified End Products

4.8 Schedule of Deliveries

5 PERFORMANCE LOCATION

6 INSPECTION OF DELIVERABLES

7 PERIOD OF PERFORMANCE

8 GOVERNMENT FURNISHED EQUIPMENT AND FACILITIES

8.1 Government Furnished Property

8.2 Access to Government Property

8.3 Access to Government Facilities

8.4 Government Furnished Material

8.5 Government Furnished Information

9 SECURITY REQUIREMENTS

9.1 Security Level

9.2 DD Form 254

9.3 Security Clearance

9.4 Site Security

10 PERSONNEL

10.1 Key Personnel

10.2 Contractor Staff

ii

10.3 Identification

11 TRAVEL REQUIREMENTS

12 INVOICING

13 ADMINISTRATIVE AUTHORITY

13.1 Contracting Officer

13.2 Contracting Officer Representative (COR)

14 ORGANIZATIONAL CONFLICT OF INTEREST

TABLE OF FIGURES

Table 3-1 TSS Supported Fielded C4 Systems Table 3-2 TSS Supported Sites

ADDENDUMS

1 Estimated Exercise/Event Support Schedule 2 TSS Billet requirements by Location 3 Contingency Operations 4 Schedule of Allowable Costs

PWS for TSS 11 Feb 2013

1 INTRODUCTION

1.1 Background

Over the years, the Marine Corps has fielded and improved a host of Command, Control, Communications, and Computer (C4) systems and networks that have become essential to modern Warfighting, whether executing Security Cooperation Operations, Counter Insurgency Operations, or Humanitarian Operations. Because many C4 systems were fielded without enough fully trained Marines to successfully and continuously accomplish their 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 deliberately programmed/fielded C4 systems where business case analysis indicated a centralized support process as the preferred alternative, as well as systems developed in response to an Urgent Unfunded Needs Statement (UUNS) that were delivered without any organic support. Because MCTSSA provided effective and efficient support, many Marine Corps programs of record chose to reduce the reliance on program/specific unique Field Service Representatives, support their C4 systems/applications through MCTSSA, and define that support in their Integrated Logistics Support Plan (ILSP).

In response to the growing need for C4 Tactical Systems Support (TSS), MCTSSA established the Operational Forces Support (OFS) Branch to provide critical, highly specialized interoperability and integration support, including over-the shoulder training and troubleshooting for multiple fielded C4 systems and associated networks to Marines deployed and in garrison.

Additionally, OFS provides a feedback loop between the Operating Forces and Marine Corps Systems Command (MARCORSYSCOM) Program Managers and applicable Program Executive Offices to address system performance and sustainment issues for fielded systems, resulting in problem resolutions and/or 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 that responds 24 hours a day; contractors strategically embedded with Marine units across the world; and task-organized, highly trained and capable teams that deploy from OFTSSC to support various training exercises and contingency operations. OFS provides technical systems expertise for trouble-shooting and issue resolution; tactical communications network analysis and diagnostics;

and fielded C4 system set-up, maintenance, system engineering, technical support, configuration management, and over-the-shoulder training. Support is provided to Marine units, both deployed and in garrison, preparing for and/or participating in major exercises. Examples include:

Operation Enduring Freedom; Exercises Javelin Thrust, Bold Alligator, Dawn Blitz, and Cobra Gold; 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 CONUS and

OCONUS:

• Tier 1: C4 systems support provided by personnel who resolve issues in real-time by reference to the OFTSSC online knowledge repository.

• Tier 2: OFTSSC Subject Matter Expert (SME) personnel who have significant knowledge of and experience with the specified fielded C4 systems are consulted to resolve an issue.

• Tier 3: MCTSSA SMEs (outside OFTSSC, typically experienced C4 systems and applications engineers) are consulted. If necessary, issues are transferred to a MARCORSYSCOM program office, or the C4 system's developer or integrator for resolution.

OFS provides the Marine Corps the flexibility to meet the operating forces C4 technical needs at a high level of performance. OFS works in collaboration with other technical and field service engineering support contracts/contractors maintained by ongoing programs/systems within the USMC and other DoD agencies, such as Naval Surface Warfare Center Crane, Space and Naval Warfare Systems Center-Atlantic (SSCLANT), etc. These efforts are coordinated by OFS at MCTSSA in conjunction with the Program Managers at MARCORSYSCOM.

1.2 Scope

This Performance Work Statement defines the non-personal technical service support efforts required by MCTSSA, Tactical Systems Support (TSS) to meet the operating forces technical support requirements for fielded C4 systems. Support under this effort include but it is not limited to 16 hours, 5 days a week Monday through Friday at the MCTSSA, Operating Forces Tactical Systems Support Center (OFTSSC); full time onsite support to Marine Corps units located worldwide, contingency operations support, training exercise support and over the shoulder training. Additionally, the successful bidder may be required to provide shift work and on-call support at OFTSSC during the off hours (2300 to 0700 Monday through Friday) and twenty four hours (24) a day Saturday and Sunday.

TSS support includes technical expertise and assistance with installation of fielded C4 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, preparing for and/or participating in major exercises, and including combat operations.

Examples include: Operation Enduring Freedom (OEF); Exercises Javelin Thrust, Bold Alligator, I MEF’s Amphibious Exercise, and Cobra Gold; Marine Expeditionary Unit (MEU) deployments and Deploying Group System Integration Testing; and other events in the Continental United States (CONUS) and Outside CONUS (OCONUS.)

The primary objective is to provide technical and engineering support to MCTSSA Operating Forces Tactical Systems Support Center (OFTSSC) and the operating forces worldwide with continuous support of fielded tactical C4 programs of record to ensure that Marines can successfully setup and operate fielded C4 tactical systems. See section 3 below for a list of systems and units and organizations to be supported under this PWS.

This contract does not and shall not provide support for the following, unless specifically addressed in Section 3 and 4 of this PWS:

a. Information Assurance (IA)

b. Video Teleconferencing (VTC) setup and or administration

c. Internet Service Provider (ISP) support such as network uptime, connectivity

d. Logistics Functions (inventory management or accounting for systems and components)

e. Document Development (Power Point, Word documents, Spreadsheets, etc.)

f. SharePoint Development

2 APPLICABLE DOCUMENTS

2.1 Compliance Documents

The following documents are applicable to this PWS to the extent specified herein:

a. DoD Civilian Expeditionary Workforce, DoD Directive 1404.10, 23 January 2009

2.2 Guidance Documents

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

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

c. OFTSSC IOP

3 PERFORMANCE REQUIREMENTS

The contractor shall provide fully qualified, trained personnel to provide technical support and analytical services for the fielded tactical C4 systems identified in Table 3-1. The contractor may be required to provide support for other tactical C4 systems as they are identified by the COR.

Table 3-1 TSS Supported Fielded C4 Systems

Common Aviation Command and Control System

(CAC2S)

Joint Enhanced Core Communications System

(JECCS)

Combat Operations Center (COC) Secure Mobile Anti-jam Reliable Tactical Terminal

(SMART-T)

Data Distribution System (DDS) Systems Planning Engineering and Evaluation Device

(SPEED)

Digital Technical Control (DTC) Tactical Collaborative Work Suite (TCWS) Expeditionary Command and Control Suite (ECCS) Transition Switch Module (TSM) Joint Tactical Common Operational Picture (COP) Workstation (JTCW)

Global Command and Control System (GCCS)- Tactical Combat Operations (TCO) (GCCS TCO)

Joint Capabilities Release (JCR) Video Scout (VS)

Technical support under this effort includes on-site sixteen (16) hours a day, five (5) days a week Monday through Friday at the MCTSSA Operating Forces Tactical Systems Support Center (OFTSSC), on-site technical support at specified Marine Corps organizations worldwide, as well as exercise and operational support based upon the mission of the supported unit, (e.g., hazardous duty, combat operations, peace-keeping, humanitarian relief) on a discrete basis. The contractor shall plan shift work and on-call support as required during the off hours (2300 to 0700 Monday through Friday) and twenty four hours (24) a day Saturday and Sunday. Shift work and on-call applies to OFTSSC only and is a collaborative effort shared amongst the contractor personnel and government personnel within the OFTSSC. The on-call support usage varies dependent on ongoing exercise requirements primarily from CONUS exercises.

The contractor shall provide full time, onsite, non personal technical support to Marine Corps units identified in Table 3-2 below:

Table 3-2 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 (Stuttgart, DEU) X X X MARFORPAC (Hawaii) X X X MARFORRES (New Orleans, LA) X X X EWTGLANT (Norfolk, VA) X X X MCCES, MCB 29 Palms, CA X X MEF Forward (Worldwide) X X X X MARCENT (Tampa, FL) X X X

3.1 OFTSSC Technical Support

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 contractor may be required to provide shift work and on-call support at OFTSSC during the off hours (2300 to 0700 Monday through Friday) and twenty four hours (24) a day Saturday and Sunday. The support to be provided is for fielded tactical C4 systems identified above (Table 3-

1) and include but it is not limited to: issue resolution, troubleshooting, assistance with system administration, system software and hardware installation, technical guidance, systems integration, test support (e.g. Developmental Testing, Operational Testing, and engineering assessments) documentation of issues, recommendations, and actual resolutions, and limited training as required. The OFTSSC technical support is provided primarily via telephone, e-mail, internet chat and other communications protocols.

For planning purposes, the contractor can expect to support an estimated twenty five (25) requests for support per day, spread across the systems identified in Table 3-1. The contractor shall expect to support a range of trouble calls, from requests for password reset to systems troubleshooting concerns. Most trouble calls are resolved within a twenty four (24) hour period from receipt of a trouble call, while more complex issues are resolved within one (1) to two (2) weeks.

The contractor shall use the Government-provided tools/software [Incident Management System (IMS)] to capture and catalog support requests and resolution actions. The contractor shall assist in managing receipt, routing, resolution, and trend analysis of requests for support in accordance with the OFTSSC Standard Operating Procedures (SOP).

3.2 OFTSSC Deployed Support Team (DST)

The contractor personnel supporting the OFTSSC can expect to provide technical support to various CONUS locations in support of exercises, equipment fielding and test events. The contractor shall also expect the OFTSSC personnel to deploy to OCONUS locations as part of the DST as required. On average the DST deploys one (1) contractor, two (2) times a year, for no more than ninety (90) days each, with an average of sixty (60) days as required to assist Marine Corps units engaged in contingency operations abroad.

3.3 Continental United States (CONUS) Support

The contractor shall be prepared to provide technically qualified personnel for onsite technical support to CONUS units/organizations, upon issuance of a task order and for the duration of the period of performance. The technical support provided is for the fielded C4 systems identified in Table 3-1, or as identified by the COR.

The contractor shall provide onsite technical support to Marine Corps units throughout CONUS see this PWS Section 3/Section 5 for listing of units to be supported. The support to be provided is for fielded tactical C4 systems identified in (Table 3-1) above and include but it is not limited to: issue resolution, troubleshooting, assistance with system administration, system software and hardware installation, technical guidance, systems integration, (e.g. Operational Testing, engineering assessments) documentation of issues, recommending solutions, and over the shoulder training as required. The contractor shall provide onsite support during normal working hours. Normal working hours are set by the supported unit, not to exceed eight (8) hours a day Monday through Friday. Any support required above the normal work day, shall be coordinate with Contracting Officers Representative (COR)/Government Service Representative (GSR) for approval.

3.4 CONUS Exercise Support

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, i.e. 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 of this PWS provides an estimated Exercise/Event Support Schedule for the contract period.

The contractor shall coordinate and get approval from the COR/GSR for any 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 twelve (12) hours per day seven days a week.

3.5 Outside Continental United States (OCONUS) Support

The contractor shall provide onsite technical support with fielded tactical C4 systems to OCONUS Marine Corps units listed in Sections 3/5 of this PWS. On-site support include assistance with issue resolution, troubleshooting, system administration, system installation, technical guidance, systems integration, (e.g. Operational Testing, engineering assessments) documentation of issues, recommendations, and actual resolutions, and over-the-shoulder training as required. The contractor shall provide onsite support during normal working hours.

Normal working hours are set by the supported unit, not to exceed eight (8) hours a day Monday through Friday. The contractor shall coordinate with the COR/GSR for hours above the normal working hours.

3.6 OCONUS Exercise Support

The contractor shall provide technical support with fielded tactical C4 systems to OCONUS Marine Corps units listed in Sections 3/5 of this PWS, during exercises. The support shall include planning, coordination, deployment of qualified technical support personnel, and post-exercise reporting, for limited-duration events, i.e. 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. Section 11 Travel Requirements contains a tentative exercise/event support schedule for the contract.

The contractor shall coordinate and get approval from the COR/GSR for any 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 twelve (12) hours a day seven days a week.

3.7 Contingency Operations Support

The contractor shall provide technically qualified personnel, to support fielded tactical C4 systems during Contingency Operations at various OCONUS locations. 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 ouster 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 COR.

Contractor personnel supporting Contingency operations shall be deployed for no more than one

(1) year increments and for the duration of the Contingency Operations. Normal working hours are set by the supported unit, during contingency operations support to no more than twelve (12) hours a day seven days a week.

The contractor personnel performing work under this PWS, supporting contingency combat operations are hereby designated as civilian noncombatant personnel who are authorized to accompany the military forces of the United States in areas of military operations and are designated as "emergency essential personnel" as defined in DoD Directive 1404.10.

3.8 Training

The contractor personnel shall be prepared to provide “over-the-shoulder” training for fielded tactical C4 systems to Marine Corps units worldwide as required. Over the shoulder training is not formal training, it is intended as impromptu training to help Marines get refreshed with fielded C4 systems integration and configuration so that the Marine can operate, configure, diagnose and conduct basic troubleshooting of the systems. Over the shoulder training is embedded in tasks 3.1 – 3.7 of the PWS.

The contractor shall document in the IMS all instances of over-the-shoulder training and ensure that the information is captured in the monthly status report.

3.9 Program Management & Administration

The contractor shall establish a single TSS Program Management & Administrative office. The contractor shall provide a program management plan to document the program management system. The contractor shall implement the program management plan as approved by the Government. Program management is embedded in tasks 3.1 – 3.8 of the PWS.

The contractor shall develop, define, monitor, report, and maintain program cost, schedule, performance, and risk metrics for Government approval. The contractor shall support Program Management Reviews on a quarterly basis or as required. 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 PM 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

(10) working days prior to the start of the event, to ensure no gap in support.

The contractor shall provide the Government access to all data/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.

4 DELIVERABLES

Prior to the first submission of any deliverable, the contractor shall provide COR a copy of the formatted deliverable for format approval, unless otherwise stated herein. All deliverables are to be submitted to the COR.

4.1 Monthly Status Report

The contractor shall deliver to the COR an electronic monthly status report by the 15th of each month, in the current version of Microsoft Office® Word or Excel in use by MCTSSA. The report shall include, but is not limited to:

a. Description of services provided and products, events, and deliverables completed during the reporting period;

b. Analysis of trouble calls for the previous month;

c. Significant issues discovered to include a description of the problem, temporary/work-around solutions tried, temporary/work-around solution of choice, recommendation to the Government for a permanent solution;

d. List of current programmatic issues with recommended solutions.

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

The primary purpose of monthly status report is to identify issues experienced by users which are not addressed by system development/support organizations at Marine Corps Systems Command and other acquisition agencies, and directly communicate those issues.

4.1.1 Monthly Financial Forecast

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

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

b. Staffing Status report that details any projected personnel deficiencies and impact to the tasks being affected.

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

The monthly financial forecast is due to the COR no later than the 10th of each month.

4.1.2 Weekly Staffing Status

The contractor shall provide a weekly personnel staffing report for all out of country personnel supporting this PWS. The weekly staffing report is due to the COR by close of business (COB) every week.

4.2 After Action Report (AAR)

The contractor shall deliver to the COR an electronic AAR (3) working days after the completion of an exercise, in the current version of Microsoft Office® Word or Excel in use by MCTSSA.

The report shall include, but is not limited to:

a. Description of services provided during the exercise;

b. Summary of issues discovered during the exercise;

c. Identification of issues discovered to include description of the problem, temporary/work-around solutions tried, temporary/work-around solution of choice, recommendation to the Government for a permanent solution;

d. Resource reporting including dollar cost of support, hours of support provided including travel time, The primary purpose of the AAR is to identify issues experienced by users at exercises which are not addressed by system development/support organizations at Marine Corps Systems Command and other acquisition agencies, and directly communicate those issues.

A secondary purpose is to identify the costs (personnel, time, money, facilities) of the support provided.

4.3 Census Report

Contractor shall submit electronically, an employee census information report monthly to the Contracting Officer. Information shall be current as of the 25th day of each month and received by the Contracting Officer no later than the first day of the following month. The following information shall be provided for each geographical location in which work was performed:

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

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

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

d. The names of all company personnel who enter and update employee data in the

Synchronized Pre-deployment & Operational Tracker (SPOT) IAW DFARS 252.225- 7040 or DFARS DOD class deviation 2007-O0010.

4.4 Distribution Statement

The following statement regarding distribution 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: EXAMPLE:

“DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S.

DoD contractors associated with the system(s) identified in this document; document contains technical, operational, or test and evaluation information (Feb, 2013). 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.5 Delivery Instructions

Deliverables associated with the above specified tasks shall be subject to the performance standards and acceptable quality levels specified in the Quality Assurance Surveillance Plan, Enclosure (1).

4.6 Unclassified End Products

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

4.7 Classified End Products

All classified material shall be shipped or mailed in or out of the command via Federal Express or United States Postal Service (USPS) registered mail. Material shipped out of the command shall be shipped or mailed only by the CMCC custodian. Federal Express or USPS registered mail is the only approved methods of shipping classified material.

Classified material sent via Federal Express (FEDEX), will use the following address:

COMMANDING OFFICER

ATTENTION CMCC

MCTSSA

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 classified, handled, marked, transmitted, safeguarded, and controlled in accordance with the NISPOM (DOD Directive 5220.22-M).

4.8 Schedule of Deliveries

The contractor shall provide a written request for all delivery schedule revisions at least seven

(7) 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 LOCATION

Performance of work associated with Tactical Systems Support will be performed at the following locations in CONUS and OCONUS:

Support of the OFTSSC, PWS 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, PWS section 3.3 will be performed at various USMC garrison locations; examples include I MEF, (MCB, Camp Pendleton, CA), II MEF, (MCB, Camp Lejeune, NC), MARFORCOM (Norfolk, VA), Expeditionary Warfare Training Group Atlantic (Norfolk, VA), Marine Forces Reserve (New Orleans, LA), MAGTFTC (MCB 29 Palms CA) and MARCENT (Tampa, FL).

Performance of work in support of OCONUS locations, PWS section 3.5 will be performed at various overseas USMC garrison locations; examples include III MEF (MCB, Okinawa, Japan), MARFORPAC (MCB, Camp Smith, HI), and Marine Forces Europe (Stuttgart, Germany). See Addendum 1 for an estimated/notional number of personnel required by location.

Performance of work in support of contingency operations, PWS Section 3.7 will be performed at various locations around the world in support of combat operations.

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. Minor corrections required to deliverables will be verbally discussed with the contractor and noted on deliverable products. A revised deliverable shall be resubmitted to the Government within three (3) calendar days unless a different schedule is agreed to between the Government and contractor because of the scope of required modifications.

All deliverables shall be submitted to the COR in soft-copy format and shall be clearly labeled to indicate content. All soft-copy deliverables shall be in the current version of Microsoft Office® suite of products in use by MCTSSA. The COR will approve in writing any agreed to changes in deliverable formats in advance of submission.

7 PERIOD OF PERFORMANCE

The base period of performance for this task is anticipated to be twelve (12) months in duration from date specified in the award, with three (3), one-year option periods.

8 GOVERNMENT FURNISHED EQUIPMENT AND

FACILITIES

8.1 Government Furnished Property

Government Furnished Property (GFP) provided, to include work area, work furniture, supplies, NMCI, NIPRNET, SIPRNET, and CENTRIX access and special equipment, will be commensurate with the working environment of the Marine unit being supported. GFP is limited to items necessary to perform assigned tasks to meet the operational requirements. Laptops, cellular phones, and other items of convenience are not reimbursable as Other Direct Charges (ODCs). ODCs associated with the cost of business (e.g., cellular service, special computer applications, etc.) must be identified in the proposal for consideration and the Contracting Officer‘s approval.

Government printing requirements are MANDATED to use Government Printing Offices (GPO) per FAR 8.8, 1-877-DAPS-CAN. ODC requests for printing requirements MUST be obtained and approved by the Contracting Officer ONLY, prior to conducting these services and after getting applicable waivers. Any exceptions must be identified in the Contractor‘s proposal at the time of submission.

8.2 Access to Government Property

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

8.3 Access to Government Facilities

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

8.4 Government Furnished Material

No Government Furnished Material will be provided under this PWS.

The contractor shall furnish its own computer equipment, administrative supplies, and office supplies required for the performance of the tasking within this PWS.

The Government will not reimburse the contractor for cell phone charges under this PWS.

8.5 Government Furnished Information

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

a. A user and email account on the NMCI to include a CAC card to support PKI access and Marine Corps Web Services when determined by the Government to be necessary for the performance of the tasking within this PWS.

b. A user and mail account on SIPRNET, NIPR, and CENTRIX domains when determined by the Government to be necessary for the performance of the tasking within this PWS.

c. Contractor personnel are authorized to receive training on unique government systems and software where such training is not available in the commercial sector.

9 SECURITY REQUIREMENTS

The contractor will need to access classified areas and C4 systems at all worksites. All contractors that require a Secret Internet Protocol Router Network (SIPRNET) account shall be provided with a North Atlantic Treaty Organization (NATO) brief.

9.1 Security Level

Technical tasks associated with the PWS require access to classified information and a security clearance up to the SECRET level. The contractor shall not divulge any information regarding files, data, processing activities/functions, user ID’s, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standards of conduct.

9.2 DD Form 254

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 and including Secret. The requirement of the clause FAR 52.204-2, Security Requirements is applicable to this order. The contractor shall (1) be responsible for all security aspects of the work performed under this contract, and (2) assure compliance with the NISPOM (DOD Directive 5220.22-M).

Contracted personnel’s clearance shall be able to be confirmed in the Joint Personnel Adjudication System (JPAS).

9.3 Security Clearance

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

9.4 Site Security

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, who are not subject to an outstanding criminal warrant, have no felony conviction, and no more than three criminal misdemeanor convictions within the last seven years, and 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.

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 considered to have been given when personnel enter Government installations.

10 PERSONNEL

10.1 Key Personnel

The contractor shall provide key personnel identified below and provide resumes:

a. Program Manager

b. Technical Manager

Key personnel performing tasks under this PWS shall have at least five (5) years of recent experience and expertise with Marine Corps fielded tactical C4 systems, and shall be otherwise qualified to perform the work described herein. The contractor shall provide resumes for key personnel.

Key personnel shall not be substituted without the permission of the Contracting Officer. During the term of the contract performance, no personnel substitutions will be permitted unless such substitutions are necessitated by an individual’s sudden illness, death, or termination of employment. Request for approval of substitutions shall be made in writing with a detailed explanation of the circumstances along with a resume of the proposed individual. Proposed substitutions shall at a minimum have the equivalent qualifications of the person being replaced.

10.2 Contractor Staff

The contractor shall employ and maintain a technically trained and experienced work force skilled on the C4 systems identified in Table 3.1. Addendum 2 is a list of personnel requirements by location. The Contractor shall provide the COR a by name list of contractor personnel, position title and location. All contractor personnel shall posses 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 and prerogative of the contractor. The contractor shall comply with the requirements of this PWS and observe and be familiar with USMC regulations concerning personnel conduct as referenced herein.

All contractor personnel shall be in professional, suitable attire, considering on 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 operation of privately owned vehicles at the site specific location.

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

10.3 Identification

Contractor personnel shall identify themselves or be introduced as contractor personnel “supporting Tactical Systems Support contract” and displaying distinguishing badges or other visible identification for meetings with Government personnel. Contractor personnel shall appropriately identify themselves as contractor personnel “supporting Tactical Systems Support contract” in telephone conversations and in formal and informal written correspondence.

11 TRAVEL REQUIREMENTS

The contractor shall be required to travel to locations such as those listed in addendum 1 in support of this PWS when notified by the COR. Authorized travel shall be in accordance with DoD Joint Travel Regulations. Actual travel required will vary depending on the technical issues and schedules as they evolve throughout the period of performance.

12 INVOICING

The contractor shall submit an electronic-copy of an invoice and any necessary supporting documentation not more often than once a month via Wide Area Workflow (WAWF).

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 United States Marine Corps (USMC) utilizes WAWF-RA to electronically process vendor requests for payment. This process allows DoD vendors to submit and track Invoices and Receipt/Acceptance documents electronically. The contractor shall be required to utilize this system when processing invoices and receiving reports. The contractor shall (i) ensure an Electronic Business Point of Contact is designated in Central Contractor Registration at http://www.ccr.gov and (ii) register to use WAWF-RA at the https://wawf.eb.mil site, within ten (10) calendar days after award of this contract or modification. Step by step procedures to register are available at the https://wawf.eb.mil site.

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

13 ADMINISTRATIVE AUTHORITY

13.1 Contracting Officer

Only the Contracting Officer has the authority to authorize deviations from the terms and conditions of this contract, including deviations from the specifications and requirements stated herein. In the event the contractor does deviate, without the issuance of a duly executed contract modification, such deviation shall be at the risk of, and any costs related thereto shall be borne by the contractor.

13.2 Contracting Officer Representative (COR)

Ms. Maria Hahn (maria.hahn@usmc.mil, (760) 725-0551) is the COR for this contract. The COR is limited to providing program specific clarification to the Contractor's Project Manager for this contract, and does not have the authority to take any action, either 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 direct work that goes beyond the scope of this contract’s PWS. If the contractor perceives that the COR or any other Government personnel is requesting an effort outside the existing scope of this contract, the contractor shall promptly notify the Contracting Officer in writing. No action shall be taken by the contractor under such direction until the Contracting Officer has issued a contractual change or otherwise resolved the issue. The Contracting Officer’s Representative will be appointed at the time of contract award.

The Government reserves the right to reassign the COR position.

14 ORGANIZATIONAL CONFLICT OF INTEREST

(a) “Organizational Conflict of Interest” means that because of other 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 that to the best of its knowledge and belief, and 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. In order 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 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 that, if after award, it discovers an actual or potential organizational conflict of interest; it 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, which 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 (f) 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 ward 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 form 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 in order 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, or situations/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).

14 ORGANIZATIONAL CONFLICT OF INTEREST