24R8000 Amendment 01_Attachment 1 TMIT PWS_Rev 1_ Clean.pdf
PDF 1 MB Posted
- Attached to
- Trackless Mobile Infantry Targets
- Solicitation number
- M6785424R8000
- Issued by
-
United States Marine Corps
About this file
This performance work statement (PWS) outlines requirements for providing trackless mobile infantry targets (TMIT) training services to the United States Marine Corps. The contractor must support Marine Corps training with semiautonomous human-type TMITs capable of moving on training ranges within established boundaries to present realistic moving threats. Services include TMIT system operations and support for pre-exercise planning and after-action reviews. The contractor must maintain 90% operational availability of the TMIT solution at multiple locations simultaneously. Locations include Marine Corps bases in North Carolina, California, Hawaii, Japan, and Virginia. The contractor shall provide TMIT support for an average of 64 hours per week across all locations. The performance period is for one base year with four one-year options. The contractor must meet all requirements of the PWS, including information security, personnel qualifications, travel, property, program management, and quality control.
View the file
Other files
Show all 28
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
t 1
Version: 0.23
15 Feb 2024
UNCLASSIFIED
Prepared By:
Program Manager, Training Systems
Base Contract Performance
Work Statement (PWS)
For
Trackless Mobile Infantry
Targets (TMIT)
PM TRASYS BASE CONTRACT PWS FOR TMIT
UNCLASSIFIED ii
CONTENTS 2
1 INTRODUCTION................................................................................................................. 1 3
1.1 General ........................................................................................................................................................... 1 4
1.2 Mission ............................................................................................................................................................ 1 5
1.3 Background .................................................................................................................................................... 1 6
1.4 Scope ............................................................................................................................................................... 1 7
2 APPLICABLE DOCUMENTS ............................................................................................ 4 8
2.1 Department of Defense (DoD) Instructions, Directives, Standards, and Guides ......................................... 4 9
2.2 Department of the Navy Instructions, Directives, Standards, and Guides ................................................... 4 10
2.3 Marine Corps Orders (MCO), Manuals, Directives, and Guides ................................................................. 4 11
2.4 Availability of DoD Documents ..................................................................................................................... 5 12
2.5 Other Documents, Drawings, and Publications ............................................................................................ 5 13
3 REQUIREMENTS ................................................................................................................ 6 14
3.1 General Requirements .................................................................................................................................... 6 15
3.1.1 Non-Personal Services ...................................................................................................................... 6 16
3.1.2 Business Relations ............................................................................................................................ 6 17
3.1.3 Contractor Personnel, Disciplines, and Specialties .......................................................................... 8 18
3.1.4 Resource Requirements ..................................................................................................................... 8 19
3.1.5 Security Requirements ..................................................................................................................... 11 20
3.1.6 Safety ............................................................................................................................................... 16 21
3.1.7 Locations and Hours of Work ......................................................................................................... 18 22
3.1.8 Travel .............................................................................................................................................. 20 23
3.1.9 Government Property ...................................................................................................................... 23 24
3.1.10 Program Management .................................................................................................................... 24 25
3.1.11 Operational Availability ................................................................................................................. 31 26
3.1.12 Spectrum ......................................................................................................................................... 32 27
3.1.13 Risk Management Framework (RMF) Support ............................................................................... 34 28
3.1.14 Configuration Management ............................................................................................................ 36 29
3.1.15 Privacy Act Information .................................................................................................................. 36 30
3.1.16 Disclosure of Information ............................................................................................................... 36 31
3.1.17 Transportation of Contractor Equipment in Hawaii ....................................................................... 36 32
3.1.18 Technology Readiness ..................................................................................................................... 37 33
3.1.19 Performance in Japan ..................................................................................................................... 37 34
3.2 Specific Requirements .................................................................................................................................. 38 35
3.2.1 System Characteristics .................................................................................................................... 38 36
3.2.2 After Action Reviews (AARs) ........................................................................................................... 38 37
3.2.3 Scheduling And Training Requirements .......................................................................................... 39 38
APPENDIX A. SYSTEM CHARACTERISTICS…………………………………….……………………………..41 39
APPENDIX B. CONTRACTS TO BE PERFORMED IN JAPAN .......................................................................... 47 40
UNCLASSIFIED iii
I. SOFA ARTICLE XIV STATUS ................................................................................................................... 47 41
II. SOFA ARTICLE I(b) STATUS ................................................................................................................... 49 42
III. LOGISTIC SUPPORT ................................................................................................................................. 51 43
IV. Further Information. .................................................................................................................................... 52 44
APPENDIX C. PERFORMANCE STANDARDS…………………………………………………………………..53 45
APPENDIX D. CUSTOMER COMPLAINT RECORD (CCR)…………………………………………………….57 46
APPENDIX E. ACRONYMS……………………………………………………………………………………...…58 47
Revision Log 48
Date Version Revision Description
28 Jul 2023 0.13 PWS prepared for MAT review
21 Aug 2023 0.14 MAT review complete
29 Dec 2023 0.20 PWS Restructured
10 Jan 2024 0.21 Minor revisions
19 Jan 2024 0.22 CDRL numbering revisions
15 Feb 2024 0.23 Additional security information
UNCLASSIFIED Page 1
1 Introduction 50
1.1 General 51
The Trackless Mobile Infantry Targets (TMIT) contract is a single award, Indefinite 52
Delivery/Indefinite Quantity (IDIQ) contract. The contract provides flexibility and an expedited 53 ordering process to satisfy the Marine Corps’ need for TMIT’s in accordance with the systems 54 characteristics defined in the PWS. Each task order will identify the performance objectives, 55 performance standards, Acceptable Quality Levels (AQL), locations, and schedules in the PWS. 56
1.2 Mission 57
Training and Education Command’s (TECOM) mission is to lead the Marine Corps Training and 58
Education continuum from individual entry-level training, professional military education and 59 continuous professional development, through unit, collective, and service-level training in order 60 to produce warfighters and enhance warfighting organizations that enable the FMF to build and 61 sustain the combat readiness required to fight and win today and in the future. The TMIT 62 capability supports TECOM’s mission by providing the Fleet Marine Forces with a dynamic and 63 realistic representation of human targets for use in live-fire / non-live fire training to increase 64 lethality and unit readiness. 65
1.3 Background 66
Marine Corps operational training ranges are comprised of a sophisticated infrastructure spread 67 across multiple geographic locations. Training requirements are determined by expected 68 missions, and training and readiness programs focus on training to successfully accomplish 69
Marine Air-Ground Task Force (MAGTF) missions across the range of military operations, 70 including stability operations, contingency operations, and major theater wars. To that end, the 71
Range Training Program Division (RTPD), Training and Education Command (TECOM), has a 72 requirement for education and training services to meet a need for combat marksmanship 73 training incorporating Trackless Mobile Infantry Targets (TMITs). 74
1.4 Scope 75
The specific scope of this PWS includes, but is not limited to, the following: 76
• Supporting Marine Corps training with TMITs capable of moving on a training range 77 within established geographic boundaries to ensure safety, and to present shooters with 78 realistic, moving threats on live-fire ranges and training areas used by the Marine Corps; 79
• Providing TMIT system operations and pre and post exercise support for Marine Corps 80 training; 81
• Providing data to training audiences for After Action Reviews (AARs); 82
UNCLASSIFIED Page 2
• Creating (new), or modifying (existing) TMIT training scenarios; 83
• Developing TMIT training concepts; 84
• Supporting live-fire and non-live fire training events with TMITs so that military 85 personnel can evaluate the skills of individuals, leaders, teams, and units, and sustain 86 operational readiness. 87
The contractor shall provide TMIT support to the following locations (see Figure 1): 88
Figure 1 – Places of Performance 89
Please note, with respect to the locations identified in Figure 1, Section B of the IDIQ identifies a 90 corollary CLIN/SLIN for each location which prescribes the total number of hours of training 91 time and the number of trailers. (One TMIT trailer shall be comprised of at least 8 TMITs that 92 shall be available to meet Marine Corps training requirements at the identified location). It is the 93 contractor’s responsibility to determine how to meet the availability requirements for each 94 location. Therefore, the contractor shall consider, for their system, how often failures occur, and 95 corrective maintenance required, how often preventative maintenance is performed, how quickly 96 failures can be isolated and repaired, how quickly preventive maintenance tasks can be 97 performed, and how long logistics support delays contribute to down time. 98
Note 1: Performance in Hawaii will primarily occur on the island of O’ahu. However, the 99 contractor is expected to provide services for at least two (2) Pohakuloa Training Area (PTA) 100 deployments, that are on average, four (4) consecutive weeks (approximately 8 total weeks) at 101
PTA, on the island of Hawaii for each 12-month period. If supporting training at PTA, the 102 contractor will not be required to support training on the island of O’ahu. Stated differently, the 103 contractor shall provide service on either O’ahu or at PTA, but not at the same time. 104
Reimbursement for the cost to travel for offsite training is as specified in the Travel section of 105 this PWS. 106
Note 2: On occasion, the Government may require that the contractor support training that takes 107 place at locations other than the main locations included in Figure 1. These CONUS-to-CONUS 108 requirements will only be conducted when requested in advance and approved in writing by the 109
COR. When offsite training requests are approved by the COR in writing, the contractor will be 110 expected to support training exercises at the main location commensurate with the number of 111 remain behind training assets at the main location from which the offsite training assets are 112
Marine Corps Base (MCB) Camp
Lejeune, Camp Lejeune, NC
(See Note 2)
Qty 3 Trailers
Marine Corps Air- Ground Combat
Center, Twentynine Palms, CA
(See Note 2)
Qty 3 Trailers
MCB Camp Pendleton, Camp
Pendleton, CA
(See Note 2)
Qty 3 Trailers
MCB Hawaii, Kaneohe Bay, HI
(See Note 1)
Qty 2 Trailers
MCB Camp Smedley D. Butler, Okinawa, Japan
Qty 1 Trailer
MCB Camp Quantico, Quantico
VA
(See Note 2)
Qty 1 Trailer
UNCLASSIFIED Page 3 sourced. Reimbursement for the cost to travel for offsite training is as specified in the Travel 113 section of this PWS. 114
2 APPLICABLE DOCUMENTS 115
The current version of the following documents form a part of this PWS to the extent specified 116 herein. Moreover, the latest version of the following documents in effect at the time a task order 117 is issued under this contract will supersede the prior version of the document cited in this PWS. 118
Unless otherwise noted, in the event of a conflict between the PWS and the references cited 119 herein, the text of this PWS takes precedence. 120
2.1 Department of Defense (DoD) Instructions, Directives, Standards, and Guides 121
• DoDM 5200.01 Volume 1 – DoD Information Security Program: Overview, 122
Classification, and Declassification 123
• DoDM 5200.01 Volume 2 – DoD Information Security Program: Marking of Information 124
• DoDI 5030.59 – National Geospatial Intelligence Agency (NGA) Limited Distribution 125
Geospatial Intelligence (GEOINT) 126
• DoDI 5200.48 – Controlled Unclassified Information (CUI) 127
• DoDD 5205.02E – DoD Operations Security (OPSEC) Program 128
• DoDI 5200.46 – DoD Investigative and Adjudicative Guidance for Issuing the Common 129
Access Card (CAC) 130
• DoDI 5230.09 – Clearance of DoD Information for Public Release 131
• DoDI 5230.24 – Distribution Statements on Technical Documents 132
• DoDI 8500.01 – Cybersecurity 133
• DoDI 8510.01 – Risk Management Framework (RMF) for DoD Information Technology 134
(IT) 135
• DoD 8570.01-M – Information Assurance Workforce Improvement Program 136
• Department of Defense Foreign Clearance Guide 137
2.2 Department of the Navy Instructions, Directives, Standards, and Guides 138
• SECNAVINST 3070.2A – Operations Security 139
• SECNAV M-5216.5 – Department of the Navy Correspondence Manual 140
• SECNAV M-5239.1 – Department of the Navy Information Assurance Manual 141
• SECNAV M-5510.30 – Department of the Navy Personnel Security Program 142
• SECNAVINST 5510.30C – Department of the Navy Personnel Security Program 143
2.3 Marine Corps Orders (MCO), Manuals, Directives, and Guides 144
• MCO 1553.1B – The Marine Corps Training and Education System 145
• MCO 1553.3B – Unit Training Management (UTM) Program 146
• MCO 1553.10 – Marine Corps Training Information Management System (MCTIMS) 147
Standard Operating Procedures (SOP) 148
UNCLASSIFIED Page 5
• MCO 3070.2A – The Marine Corps Operations Security (OPSEC) Program 149
• MCO 3500.72A – Marine Corps Ground Training and Readiness (T&R) Program 150
• MCO 3550.10 – Policies and Procedures for Range and Training Area Management 151
• MCO 3570.1C – Range Safety 152
• MCO 5090.2 – Environmental Compliance and Protection Program 153
• MCO 5100.29 B – Marine Corps Safety Program 154
• MCO 5239.2B – Marine Corps Cybersecurity Program 155
• MCO 5510.18B – United States Marine Corps Information and Personnel Security 156
Program (IPSP) 157
• MCO 5510.20C – Disclosure of Military Information to Foreign Governments and 158
Interests 159
• MCO 3570.1 – Range Safety 160
• NAVMC 1553.1A – Marine Corps Instructional Systems Design/Systems Approach to 161
Training and Education Handbook 162
• NAVMC 1553.2 – Marine Corps Formal School Management Policy Guidance 163
• NAVMC 3500.65A – Operational Culture and Language Training and Readiness Manual 164
• NAVMC 3500.44 – Infantry Training and Readiness Manual 165
• MCRP 8-10B.1 – Operational Training Ranges Required Capabilities 166
• MCRP 8-10B.2 – Rifle Marksmanship 167
• MARCORSYSCOMO 11010.1 – Construction Acquisition Guidelines 168
• MARCORSYSCOM Information Systems Cybersecurity Security Classification Guide 169
2.4 Availability of DoD Documents 170
• DoD Directives, Manuals, Instructions and Publications are available online at 171 https://discover.dtic.mil/products-services/ or from the National Technical Information 172
Services (NTIS), 5285 Port Royal Road, Springfield, VA 22161 173
• DoN Directives, Manuals, Instructions and Publications are available online at 174 https://www.secnav.navy.mil/doni/allinstructions.aspx 175
• USMC Orders, Manuals, Directives, and Guides are available online at 176 https://www.marines.mil/News/Publications/ELECTRONIC-LIBRARY/ 177
• Electronic Foreign Clearance Guide available online at 178 https://www.fcg.pentagon.mil/fcg.cfm 179
2.5 Other Documents, Drawings, and Publications 180
• FED-STD-313E, Federal Standard: Material Safety Data, Transportation Data and 181
Disposal Data For Hazardous Materials Furnished To Government Activities 182
• Parts 730-774 of Title 15, Code of Federal Regulations (also known as the “Export 183
Administration Regulations”) 184 https://discover.dtic.mil/products-services/ https://www.secnav.navy.mil/doni/allinstructions.aspx https://www.marines.mil/News/Publications/ELECTRONIC-LIBRARY/ https://www.fcg.pentagon.mil/fcg.cfm
UNCLASSIFIED Page 6
• Parts 120-130 of Title 22, Code of Federal Regulations (also known as the “International 185
Traffic in Arms Regulations”) 186
• Part 1910 of Title 29, Code of Federal Regulations (also known as OSHA Occupational 187
Safety and Health Standards) 188
• U.S. Forces Japan Instruction 36-2611 – Change of Status by Persons in Japan to One of 189 the Categories Authorized by the Status of Forces Agreement 190
• U.S. Forces Japan Instruction 36-2808 – USFJ Quarterly Strength Report 191
• U.S. Forces Japan Instruction 36-2811 – Indoctrination Training Programs 192
• U.S. Forces Japan Instruction 64-100 – Contract Performance in Japan 193
• U.S. Forces Japan Instruction 64-102 – United States Contractors and their Employees 194
• Installation Range Regulations and Standard Operating Procedures 195
• RFMSS User Manual 196
3 REQUIREMENTS 197
All requirements identified in this PWS are for delivering training services to support, primarily, 198 the Marine Corps Fleet Marine Forces (FMF) requirements for combat marksmanship training 199 with TMIT’s in accordance with the systems characteristics defined in Appendix A of this PWS. 200
3.1 General Requirements 201
3.1.1 Non-Personal Services 202
The Government will neither supervise contractor employees nor control how the contractor 203 performs the required tasks. The Government will not assign tasks nor prepare work schedules 204 for individual contractor employees. 205
To provide a clear distinction between Government employees and contractor employees, 206 contractor employees shall introduce themselves as contractor personnel, display distinguishing 207 badges or other visible identification for meetings with Government personnel, and identify 208 themselves as employees of the contractor in telephone conversations and formal and informal 209 written correspondence. 210
If the contractor believes that any actions constitute or are perceived to constitute personal 211 services, it shall be the contractor’s responsibility to notify the contracting officer and the 212
Contracting Officer’s Representative (COR) immediately. 213
3.1.2 Business Relations 214
The contractor shall integrate and coordinate all activity needed to accomplish the requirements 215 herein and any task order issued under this contract. The contractor shall perform program 216 management for the contract’s duration and any task order issued under this contract. When 217
UNCLASSIFIED Page 7 applicable, the contractor shall submit corrective action plans and provide timely resolution of 218 issues. 219
Contract Administration 220
The contractor shall establish processes and assign appropriate resources to effectively 221 administer the requirements of this contract and any task order issued under the contract. The 222 contractor shall respond to contract modification changes or direction from the contracting 223 officer in a timely fashion. 224
Responsibility in Subcontracting 225
The contractor shall be responsible for any subcontract management necessary to integrate work 226 performed and shall be responsible and accountable for subcontractor performance for any task 227 order issued under the contract. The prime contractor shall manage work distribution to ensure 228 there is no Organizational Conflict of Interest (OCI) considerations. The contractor may add 229 subcontractors to their team after notification to the contracting officer and COR. The contractor 230 is responsible for ensuring that all applicable contractual provisions and clauses are passed 231 through to its subcontractors and that those provisions are enforced. 232
Contracting Officer’s Representative 233
One individual may serve as the COR for the base contract in addition to one or more task orders 234 issued under this contract, or there may be one individual appointed to perform COR duties for 235 the base contract, with other individuals appointed to perform COR duties for task orders issued 236 under this contract. The Government will provide the contractor with the name and contact 237 information for the COR appointed for the contract and any task order issued under this contract. 238
The duties of the COR are not delegable. 239
Additionally, ACORs may be assigned under a task order and will be assigned to a specific 240 geographic location. 241
Third-Party Coordination 242
There may be instances when more than one contractor or vendor is required to perform work for 243 the Government that affects the same program or project or, for unrelated matters, perform work 244 under separate contracts or agreements in proximity to one another. In such instances, the 245
Government expects that each contractor or vendor extend basic professional courtesy and 246 interaction to satisfy all of the Government’s requirements. 247
Should an issue arise, the Government expects the contractor(s) or vendor(s) to resolve the issue 248 without the assistance of the Government. However, if the contractor(s) or vendor(s) cannot 249 resolve an issue without the Government’s assistance, the contractor must promptly notify the 250 contracting officer in writing, furnishing recommendations for a solution. 251
UNCLASSIFIED Page 8
The contractor shall not be relieved of its obligations under this contract because of its failure to 252 promptly refer matters to the contracting officer or implement the contracting officer’s 253 directions. Furthermore, the contractor is not relieved of any contract requirements or entitled to 254 an adjustment to the contract’s terms and conditions or price because it fails to resolve a 255 disagreement with another contractor or vendor unless the contractor can demonstrate, to the 256 contracting officer’s satisfaction, that the failure to resolve the issue was not due its negligence, 257 fault, failure to cooperate, or failure to perform its obligations in good faith. 258
Should contracting officer intervention be required, the Government reserves the right to 259 terminate this contract and any task order issued under this contract for convenience at no cost to 260 the Government. 261
Task Orders 262
Task orders will be individually funded. Accounting classification citation data will be 263 incorporated in one or more Accounting Classification Reference Numbers (ACRN) included 264 with each task order. In addition, the contractor may be required to track separately identifiable 265
Contract Line-Item Numbers (CLINs) or Subline Items Numbers (SLINs) to submit invoices 266 accurately and facilitate the timely payment of valid invoices. The pricing on task orders that 267 cross ordering periods will be based upon the pricing that is effective at the time the order is 268 issued and will be effective throughout the period of performance for the task order. 269
3.1.3 Contractor Personnel, Disciplines, and Specialties 270
The contractor shall satisfy the requirements of any task order issued under this contract by 271 employing and utilizing personnel with an appropriate combination of education, knowledge, 272 skills, abilities, certifications, and experience. The contractor shall assign appropriate labor 273 categories and the labor hours necessary to meet all of the work requirements of a task order. All 274 personnel training, licenses, certification, and qualifications required to meet the requirements of 275 a task order, whether specified or not, shall be obtained, maintained, paid for, and otherwise 276 provided for by the contractor. 277
3.1.4 Resource Requirements 278
Except as otherwise provided, the contractor shall provide all personnel, equipment, tools, 279 materials, supervision, and quality control necessary to perform the requirements of this contract 280 and any task orders issued under this contract. TMIT system shall not require DoD personnel to 281 operate, maintain, or support the TMIT system beyond exercise planning. 282
Marine Corps Enterprise Network (MCEN) 283
Except as otherwise provided, all computer assets required by the contractor to meet the 284 performance requirements of this contract and any task order issued under this contract, whether 285
UNCLASSIFIED Page 9 to be connected to the MCEN or to be employed by the contractor as standalone assets, shall be 286 provided for by the contractor. 287
Marine Corps Enterprise Network (MCEN) Computer Access – Contractor personnel accessing 288
Marine Corps Systems Command Information Systems must maintain compliance with United 289
States Marine Corps Enterprise Cybersecurity Manual 007 Resource Access Guide. Contractor 290 personnel will submit a DD 2875 and a completion certificate for the CYBERC course located 291 on MarineNet located at https://www.marinenet.usmc.mil. The CYBERC course consist of the 292
DOD Cyber Awareness Challenge and the Department of the Navy Annual Privacy Training 293
(PII). Contractors will have to create a MarineNet account in order to complete the required 294 training. 295
MCEN IT resources, if provided, are designated for official use only and other limited authorized 296 purposes. DOD military, civilian personnel, consultants, and contractor personnel performing 297 duties on MCEN information systems may be assigned to one of three position sensitivity 298 designations. 299
1) ADP-I (IT-1): Favorably adjudicated T-5, T5R, (formerly known as Single Scope 300
Background Investigation (SSBI)/SSBI Periodic Reinvestigation (SBPR)/SSBI 301
Phased Periodic Reinvestigation (PPR)) 302
2) ADP-II (IT-2): Favorably adjudicated T-3, T3R, (formerly known as Access National 304
Agency Check and Inquiries (ANACI)/ National Agency Check with Law and Credit 305
(NACLC)/Secret Periodic Review (S-PR)) 306
3) ADP-III (IT-3): Completed T-1, (formerly known as National Agency Check with 308
Inquiries (NACI)) 309
Privileged users must maintain the baseline Cyberspace Workforce Information Assurance 310
Technical (IAT) or Information Assurance Manager (IAM) relating to the position being filled. 311
Privileged users are defined as anyone who has privileges over a standard user account as in 312 system administrators, developers, network administrators, code signing specialist and Service 313
Desk technicians. 314
All MCEN users must read, understand, and comply with policy and guidance to protect 315 classified national security information, CUI, and prevent unauthorized disclosures in accordance 316 with United States Marine Corps Enterprise Cybersecurity Manual 007 Resource Access Guide 317 and CJCSI 6510.01F. 318
MCEN Official E-mail usage – MCEN IT resources are provided for official government use 319 only and other limited authorized purposes. Authorized purposes may include personal use 320 within limitations as defined by the supervisor or the local Command. Auto forwarding of e- 321 mail from MCEN-N to commercial or private domains (e.g., Hotmail, Yahoo, Gmail, etc.) is 322
UNCLASSIFIED Page 10 strictly prohibited. E-mail messages requiring either message integrity or non-repudiation are 323 digitally signed using DOD PKI. All e-mail containing CUI, an attachment, or embedded active 324 content must be digitally signed. 325
MCEN users will follow specific guidelines to safeguard CUI, which includes Personally 326
Identifiable Information (PII) and Health Insurance Portability and Accountability Act (HIPAA) 327 information. Non-official e-mail is not authorized for and will not be used to transmit any CUI. 328
Non-official e-mail is not authorized for official use unless under specific situations where it is 329 the only means for communication available to meet operational requirements. This can occur 330 when the official MCEN provided e-mail is not available but must be approved prior to use by 331 the Marine Corps Authorizing Official (AO). 332
All personnel will use DOD authorized PKI certificates to encrypt e-mail messages if they 333 contain any of the following: 334
1. CUI. 335
2. Any contract sensitive information that normally would not be disclosed to anyone 336 other than the intended recipient as this is considered CUI. 337
3. Any privacy data, PII, or information intended for inclusion in an employee’s personal 338 file or any information that would fall under the tenets of MSGID: DOC/5 USC 552A. Personal 339 or commercial e-mail accounts are not authorized to transmit unencrypted CUI. 340
4. Any medical or health data, to include medical status or diagnosis concerning another 341 individual. 342
5. Any operational data regarding status, readiness, location, or deployment of forces or 343 equipment. 344
Contractor assets connectivity to the MCEN – The contracting company will comply with 345
MCENMSG-Unification 003-14 ENABLING CONTRACTOR ASSET CONNECTIVITY TO 346
THE MCEN. The Contractor representative will transfer the contractor owned laptops to the 347
Marine Corps Systems Command (MARCORSYSCOM) Information Technology Asset 348
Management (ITAM) department to have the MCEN images places on each laptop before it is 349 authorized to connect to the MCEN. 350
All contractor owned laps must meet or exceed the USMC laptop specifications. A list of 351 laptops authorized to be attached to the MCEN can be obtained from MARCORSYSCOM IT 352 upon request. 353
Upon completion of the contract or at such time as the contractor reclaims the asset from the 354
USMC, non-Government owned internal\external hard drives shall become the property of the 355
U.S. Government. Once the hard drives have been removed, the laptops\assets will be returned 356
UNCLASSIFIED Page 11 to the Contractor. For additional questions regarding current system specifications contact the 357
MARCORSYSCOM, Electronic Maintenance Facility, lead at Berton.whisenant@usmc.mil 358
Magnetic Hard Drive Storage Devices – This paragraph covers the requirements of classified and 359 unclassified internal and removable magnetic and solid state hard drives that store Government 360 data. This includes, but is not limited to, storage area network (SAN) devices, servers, 361 workstations, laptops/notebooks, printers, copiers, scanners and multi-functional devices (MFD) 362 with internal hard drives, removable hard drives and external hard drives. Upon disposal, 363 replacement, turn in of hard drives or completion of the contract, non-Government owned 364 internal\external hard drives shall become the property of the U.S. Government in accordance 365 with GENADMIN Processing of Magnetic Hard Drive Storage Media for Disposal. 366
3.1.5 Security Requirements 367
The information provided to the contractor will be unclassified and/or CUI. The contractor is not 368 required or expected to have Facility Clearance and contractor personnel supporting this effort 369 are not required to possess Personnel Clearance Levels. If the company has a DISS account, the 370
Facility Security Officer (FSO) is required to establish, populate, and own the DISS record of 371 every contractor processed for and/or issued a Common Access Card (CAC). Any contractor 372 personnel requiring access to U.S. Government CUI shall possess a completed background 373 investigation (minimum of a T-1/NACI) for this Public Trust Position. Due to Insider Threat 374 concerns, the Company is requested to notify the MARCORSYSCOM Personnel Security 375
(PERSEC) Office at 703-432-3952/3490/3374, within 24 hours of any adverse/derogatory 376 information associated with the 13 Adjudicative Guidelines concerning any contractor 377 performing on this contract if they have been issued a CAC and/or a Government building badge. 378
In accordance with DoDI 5200.48, “Controlled Unclassified Information (CUI),” all contractors 379 supporting MARCORSYSCOM who receive, store, or generate CUI are required to take the 380
DoD Mandatory CUI Training, available on the Security Awareness Hub at: 381 https://securityawareness.usalearning.gov/cui/index.html. Per DoDI 5200.48 and pursuant to 382 contractual requirements, DoD contractors require initial CUI training and annual CUI refresher 383 training. Additional MARCORSYSCOM specific CUI training and guidance can be attained by 384 contacting the MARCORSYSCOM Security Classification Management Office at 703-432-3141 385
/ 3140 or MCSC_ACSG2_SCMO@usmc.mil. 386
While performing aboard NAVY/USMC sites, the contractor shall comply with the provisions of 387
DoD Directive 5205.02E, “DoD Operations Security (OPSEC) Program,” SECNAVINST 388
3070.2A, “Operations Security,” MARCORSYSCOMO 3070.1B, “Operations Security 389
Program,” Marine Corps Order 3070.2A, “The Marine Corps Operations Security (OPSEC) 390
Program,” and the MARCORSYSCOMO P5510.2C, “Security Manual,” at all other sites the 391 contractor shall comply with the local command and/or program OPSEC plan. The contractor 392 must comply with all local/Service requirements if required to perform at any other DOD 393
UNCLASSIFIED Page 12 location. Contractor personnel shall follow OPSEC concepts and principles in the conduct of this 394 requirement to protect critical information, personnel, facilities, equipment, and operations from 395 compromise. All Contractors (including Subcontractors) shall supplement their current security 396 practices by requiring any personnel involved in executing this contract to complete OPSEC 397
Awareness for Military Members, DOD Employees and contractor training, available on the 398
Security Awareness Hub at: https://securityawareness.usalearning.gov/opsec/index.htm 399
Data Management 400
The contractor shall provide a point of contact for data oversight for this contract and for each 401 task order issued under this contract to ensure that all data delivered, furnished, or otherwise 402 provided to the Government includes the appropriate version, format, and associated rights. The 403 security of the data and the protection of Controlled Unclassified Information (CUI), or 404 proprietary data shall be the contractor's responsibility. 405
Common Access Card (CAC) Requirement 406
The task order COR will identify and only approve those contractor employees performing on 407 this contract that require a CAC in order to perform their job function. In accordance with 408
Headquarters, United States Marine Corps issued guidance relative to Homeland Security 409
Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a 410
CAC. In order to meet the eligibility criteria, contractor employees requiring a CAC must obtain 411 and maintain a favorably adjudicated Personnel Security Investigation (PSI). Prior to 412 authorizing a CAC, the employee’s Defense Information System for Security (DISS) record must 413 indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been 414 submitted and accepted (opened). The minimum acceptable investigation is a T-1 or a National 415
Agency Check with Written Inquiries (NACI). If a contractor employee’s open investigation 416 closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked. 417
CACs are not issued for convenience. 418
Facility Security Officers (FSOs) are responsible for notifying the MARCORSYSCOM 419
Personnel Security Office (PERSEC Office) at 703-432-3490/3952 if any contractor performing 420 on this contract receives an unfavorable adjudication after being issued a CAC. Due to Insider 421
Threat concerns, the Company is requested to notify the MARCORSYSCOM Personnel Security 422
Office (PERSEC Office) at 703-432-3952/3490/3374, within 24 hours of any adverse/derogatory 423 information associated with the 13 Adjudicative Guidelines concerning any contractor 424 performing on this contract, if they have been issued a CAC and/or a MARCORSYSCOM 425
Building Badge. 426
Each CAC is issued with a “ctr@usmc.mil” e-mail account that the individual contractor is 427 responsible to maintain as active by logging in on a regular basis (at least twice a month), 428 sending an e-mail and clearing any unneeded e-mails. Contractors issued a CAC are prohibited 429 from “auto- forwarding” their .mil e-mail account to their .com e-mail account. If the 430
UNCLASSIFIED Page 13
“ctr@usmc.mil” e-mail account is not kept active, G-6 will deactivate the account and the CAC 431 will also lose its functionality. Contractor employees shall solely use their government furnished 432
“ctr@usmc.mil” e-mail accounts for work supporting the USMC, conducted in fulfillment of this 433 contract, and shall not use a contractor supplied or personal e-mail account to conduct official 434
U.S. government business. The use of a contractor or personal e-mail account for contractor 435 business or personal use is allowed, but only when using cellular or a commercial internet 436 service provider. 437
If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have 438 also lost their eligibility to perform on MARCORSYSCOM contracts. 439
Physical Security 440
The contractor shall take reasonable care to safeguard Government property (real and personal) 441 and information provided by the Government for the contractor’s use as part of this contract or 442 any task order issued under this contract. At the close of each work period, the contractor shall 443 secure Government facilities, equipment, materials, etc., for which the contractor is responsible. 444
Within two (2) hours, the contractor shall notify the COR of any suspected security breach, theft, 445 or vandalism. In addition, the contractor shall notify the Government when systems, training 446 spaces, and/or workspaces under the contractor’s control cannot be adequately secured. 447
The contractor shall implement procedures to ensure that keys, key cards, identification cards, 448 access badges, etc., whether Government or contractor provided, are not misplaced, lost, or used 449 by unauthorized persons. Keys issued to the contractor by the Government shall not be 450 duplicated without the written permission of the contracting officer or COR. 451
The contractor shall prohibit the use of Government-issued keys/key cards by any persons other 452 than the contractor’s authorized employees. In addition, the contractor shall prohibit access to 453 secured areas by other than authorized Government or contractor employees. 454
Installation Access 455
The commander for each installation has broad authority to remove or exclude any person to 456 protect personnel and property, maintain good order and discipline, and ensure the successful 457 and uninterrupted performance of the Marine Corps’ mission. By exercising this authority, the 458 commander, or their designee, may refuse to grant access to the installation. Refusal to grant 459 installation access to a contractor’s employee does not relieve the contractor of its responsibility 460 to continue performance under this contract or any task order issued under this contract. 461
The contractor shall ensure that contractor and subcontractor personnel, at any tier, comply with 462 local security policies and procedures for the installations and facilities to which they are 463 assigned or to which they have been granted access. The contractor shall provide all necessary 464 information required to perform background checks to meet installation access requirements as 465
UNCLASSIFIED Page 14 set forth by the cognizant Provost Marshal Office or Security Office. Host installations may 466 require one, or all, of the following for entry: proof of a valid state driver’s license, vehicle 467 insurance, or a DoD CAC or Defense Biometric Identification (DBID) card. 468
If the Force Protection Condition (FPCON) at a facility or installation changes, then the 469 contractor shall comply with the posted FPCON and notify the contracting officer or COR as 470 soon as practicable. If FPCON changes affect one or more of the places of performance provided 471 for under any task order issued under this contract, the Government will determine whether the 472 total contract price is affected due to FPCON changes. If FPCON changes affect the total 473 contract price, a negotiated settlement will be reached as deemed appropriate by the contracting 474 officer. Generally, one of the following two situations apply: 475
1. If there is sufficient funding and contractor employees can continue to perform (either 476 on-site or at a site other than their regular work location), then they shall continue to 477 perform, and the contract price will not be adjusted. 478
2. If contractor employees cannot continue performance (either on-site or at a site other than 479 their regular work location) due to FPCON changes, they may be asked to stop work, and 480 the contract price may be adjusted. 481
Visit Requests 482
When required, the contractor shall submit a visit request via the DISS system a minimum of (5) 483 working days before the scheduled visit. 484
Identification of Contractor Employees 485
Each contractor employee shall wear a visible, contractor-furnished identification badge or card 486 that shall include, as a minimum, the full name and signature of the employee, a picture of the 487 employee, and the name of the individual contractor’s employer (prime or, if applicable, a 488 subcontractor). 489
All contractor personnel attending meetings, answering Government telephones, and working in 490 other situations where their contractor employee’s status is not apparent to third parties are 491 required to identify themselves as contractors to avoid creating an impression in the minds of 492 members of the public that they are Government officials. 493
All contractor personnel shall identify themselves as contractor employees in written 494 correspondence (to include letters, memos, or emails) related to efforts undertaken to support a 495 task order issued under this contract. 496
The contracting officer may, at their sole discretion, direct the contractor to remove any 497 contractor employee from Government real property or facilities for misconduct or security 498 reasons. However, removing a contractor’s employee as described herein does not relieve the 499
UNCLASSIFIED Page 15 contractor's responsibility to continue meeting the performance requirements for an individually 500 awarded task order. 501
The contractor shall deliver to the Government a list of all contractor personnel assigned to any 502 task order issued under this contract. 503
STD: Timeliness. 504
AQL: 90 percent compliance with CDRL submission timelines. 505
CDRL B001: DI-MGMT-81928 NOT 1 Contractor’s Progress and Status Report 506
Defense Biometric Identification (DBID) Card 507
Certain contractors may require the issuance of a DBID card to gain access to Marine Corps 508 bases/stations. The COR will identify and approve only those contractor employees performing 509 on this contract that require a DBID card to perform their job function aboard the base. All 510 contractor personnel accessing Marine Corps Base Quantico and Marine Corps Systems 511
Command must comply Access Control policy identified within MCSCO 5530.2A Access 512
Control Order. 513
Marine Corps Base Quantico (MCBQ) Installation Gate Access 514
Access onto MCBQ requires the use of an active Department of Defense Personally Identifiable 515
Verification (PIV) credential (i.e., Common Access Card (CAC), Military Dependent 516
Identification Card, Military Retiree Identification Card, Transportation Worker Identification 517
Credential) that can be scanned at all installation Gates prior to being granted access onto the 518 installation. Contractors/vendors who require routine/reoccurring access to MCBQ and are not 519 receiving a CAC in support of this contract effort (or do not already have an acceptable PIV), are 520 eligible for a DBID card. DBID cards may be obtained at no cost from the MCBQ Provost 521
Marshall’s Office (PMO) after coordination with the COR and the MCSC Physical Security 522
Team (PHYSEC Team). To obtain a DBID card, the vendor shall submit a completed Vendor 523
Screening Form (obtained from the COR or the PHYSEC Team) via: encrypted email to 524 mcsc_physicalsecurity@usmc.mil, faxing to 703-432-3481 (attn.: Physical Security), or a hand 525 delivered typed hard copy to the PHYSEC Team at Building 2200. The information on the 526
Vendor Screening Form will be used by MCBQ PMO to conduct a background check. The 527 vendor will be notified of the results of their vendor screening background check by the 528
PHYSEC Team and/or COR. Vendors who do not meet the eligibility standards, will not be 529 cleared for access onto MCBQ or MCSC. Vendors who meet the eligibility standards and receive 530 a favorable response to the background check will be required to complete the DBID registration 531 process using a website address/link that will be provided by the PHYSEC Team or COR. Once 532 the Vendor has successfully completed the DBID registration process, a registration code will be 533 provided. The registration code shall be printed, and hand carried by the Vendor to MCBQ PMO, 534
Bldg. 2043, between the hours of 0700 – 1500 to be issued the DBID card. DBID cards will be 535
UNCLASSIFIED Page 16 issued for a period of 3 years regardless of contract expiration. For additional questions 536 regarding submission of the Vendor screening Form or access requirements, you may contact the 537
PHYSEC Team at mcsc_physicalsecurity@usmc.mil or by calling 703-432-3964/3909. 538
Marine Corps Systems Command (MCSC) Facility Access 539
All contractor personnel accessing Marine Corps Systems Command facilities/buildings, must 540 maintain compliance with access control policy identified within MCSC Order 5530.2A - Access 541
Control Order. Access into MCSC facilities requires use of a Command facility access badge 542 issued by the PHYSEC Team. Contractor personnel assigned to sit within MCSC spaces with a 543 dedicated (by name) workspace will be considered “on-site” contractors and may be issued a 544
Green badge with the holder’s photograph. Contractor personnel that frequently visit (three or 545 more times a week) MCSC spaces will be considered “off-site” contractors and may be issued an 546
Orange badge with the holder’s photograph. Issuance of a MCSC facility access badge shall be 547 initiated by the COR using the Badge Request process hosted on the MCSC VIPER website. 548
Vendors may be issued a MCSC facility badge prior to issuance of a CAC or DBID card; 549 however, receipt of an unfavorable response will result in deactivation of any currently issued 550
MCSC facility access badge. All other vendors supporting this contract who do not meet the 551
“Green” or “Orange” badge standards shall be required to have their visit to MCSC notified in 552 advance using the MCSC Visitor Notification System hosted on the MCSC VIPER website. 553
Visitor Notifications shall only be submitted by a MCSC sponsor with access to the MCSC 554
VIPER website. Visitors who arrive at MCSC facilities without an approved Visitor Notification 555 on file shall be turned away unless a MCSC escort with a “White,” “Powder Blue,” or “Green” 556 badge can be reasonably coordinated. Vendors possessing an “Orange” badge are not authorized 557 to escort visitors without an approved Visitor Notification on file. All “Green” and “Orange” 558 badges will be programmed with unescorted access into approved MCSC facilities Monday 559 through Friday from 0630-1700. Unescorted access outside of these times to include federal 560 holidays, furloughs, shutdowns, etc. is restricted. For additional questions regarding MCSC 561 facility access requirements, you may contact the PHYSEC Team at 562 mcsc_physicalsecurity@usmc.mil or by calling 703-432-3964/3909. 563
3.1.6 Safety 564
Accidents and Mishaps 565
The contractor shall immediately report any accident/incident with safety/security implications 566 along with any other condition or incident that could reasonably be expected to be of interest to 567 the Government. The contractor shall report damage to Government property or injury to 568
Government employees, contractor employees, or any other person must be reported to the 569 contracting officer and COR within four (4) hours. Initial reports from the contractor may be 570 verbal but shall be followed up in writing using OSHA Form 301, Injury and Illness Incident 571
Report, which shall be submitted to the contracting officer and COR within 24 hours. Contractor 572
UNCLASSIFIED Page 17 reports of incidents with security implications shall include the full details of the incident, any 573 remedial actions taken by the contractor and shall otherwise comply with all applicable security 574 instructions. 575
The contractor shall investigate all accidents and mishaps occurring on Government property 576 involving contractor employees and report the findings (on applicable forms) to the contracting 577 officer and COR within (3) three calendar days of the incident.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .