Attachment 0001 SOW 20 Jul 22.pdf

STATEMENT OF WORK (SOW)

FOR

SMALL TACTICAL ELECTRIC POWER 3-KILOWATT (STEP

3kW)

20 July 2022

Prepared By:

Project Manager Expeditionary Energy and Sustainment Systems (PM E2S2) Product Director Mobile Electric Power Systems (PD MEPS)

Fort Belvoir, VA

Table of Contents 1

1. Scope Determination ......................................................................................... 3 2

2. Program Objective ............................................................................................. 3 3

3. Background ........................................................................................................ 3 4

4. Design, Analysis, and Test ................................ Error! Bookmark not defined. 5

5. Configuration Management ................................................................................ 5 6

5.4. Product Drawings and Associated Lists ............. Error! Bookmark not defined. 7

6. Quality Control ................................................................................................... 9 8

7. Logistics ............................................................................................................. 9 9

7.1. Logistics Support Package ................................................................................ 9 10

8. Management Objectives and Data Deliverables .............................................. 13 11

9. Security ............................................................................................................ 14 12

10. Safety ............................................................................................................... 15 13

11. Risk Management ............................................................................................ 17 14

12. Software ........................................................................................................... 18 15

1. Scope Determination 17

This SOW is for development of a new 3kW generator design to replace the legacy 3-18 kilowatt (3kW) Tactical Quiet Generator (TQG) as part of the Small Tactical Electric 19 Power (STEP) program. 20

2. Program Objective 21

The Program Objective is to address the Government’s need for a generator set rated 22 at 3kW or greater, but less than 5kW, and operates on common military fuels: F-24 fuel 23 conforming to STANAG 3747, Jet Propulsion (JP)-8 fuel conforming to MIL-DTL-83133, 24 and diesel fuel conforming to ASTM D975. The intent of this EMD effort is to utilize a 25 new (or existing) design and improve it to meet or exceed the requirements delineated 26 in the Purchase Description (PD), Item Specification for the Generator, Small Tactical 27 Electric Power: 3 < Kilowatts < 5 (PD 6115-0133) and provide novel enhancements. 28 Solutions should include prototype improvements for increased reliability, operation on 29 common military fuels, remote control through the Tactical Microgrid Standard (TMS), 30 and diverse paralleling capabilities. It is desired that proposed solutions support early 31 achievement of initial operational capabilities for support of an expanding user 32 community. 33

3. Background 34

The STEP program is intended to replace the legacy 2kW Military Tactical Generator 35 (MTG) and 3kW Tactical Quiet Generator (TQG), with this SOW seeking to replace the 36 3kW TQG, specifically. The program received a Materiel Development Decision in 37 3QFY14, but in JUN 2016, the Program Executive Office, Combat Support & Combat 38 Service Support (PEO CS&CSS) directed Milestone (MS) B to be delayed. The 39 program is now moving toward a MS B decision in 1QFY23. 40

This project aims to procure, test, and mature both technology and reliability of 41 generator sets of 3kW or higher, but less than 5kW alternating current (AC) power, 42 while adding additional capabilities such as inherent remote control through the Tactical 43 Microgrid Standard (TMS) and the ability to parallel with other sets. The main technical 44 goals of this effort are to validate power outputs of at least 3kW, demonstrate reliability 45 of 687 hours Mean Time Between Failure (MTBF), and demonstrate safe paralleling 46 operation and remote control, while also meeting the other performance requirements 47 specified in PD 6115-0133. 48

4. Period of Performance / Place of Performance 49

This project is expected to consist of four phases: Phase 1: Preliminary Design Review 50 (PDR); Phase 2: Critical Design Review (CDR); Phase 3: Prototype Build; and Phase 4: 51 Test Support. Phases 1–3 will be accomplished in 21 months or less. (The exact 52 length of Phases 1, 2 and 3 will be determined by the Technical Proposal for each 53 Offeror and incorporated at the time of award.) Phase 4, consisting of the 54 Government’s test and evaluation of the prototypes, will be accomplished in 12 months. 55 Phases 1 through 4 must be completed in 33 months or less. The place of performance 56 for Phases 1–4 shall be the location established by the Contractor. During Phase 4, the 57

Contractor may also require Contractor personnel to work from the Aberdeen Test 58 Center, as necessary to provide the required level of Test Support. 59

The STEP 3kW developed under this SOW shall conform to the performance 60 requirements in the Purchase Description (PD 6115-0133). The Government envisions 61 the Open Architecture Tactical Microgrid Standards (TMS) being used for this system 62 for remote autostart capability and communications to a future hybrid power system. 63 The Contractor will perform analysis and tests, as needed, to aid the design process. 64

During Phase 4, the Government will perform developmental testing to ensure that the 65 end item satisfies the user’s performance requirements. This testing is expected to last 66 for approximately 12 months. The Government will work with an Army unit to perform a 67 user evaluation during this same 12-month time period. The Contractor will provide 68 support during both the developmental testing and user evaluation to include performing 69 root cause analysis to determine the cause for poor system performance and 70 incorporating necessary design changes into the system’s design baseline when the 71 recommended change is approved by the Government. The support will consist of 72 operator training, operational troubleshooting, and all maintenance and repair actions 73 which are not covered in the user manual. Repairs or changes shall be made with new 74 hardware. If there is a change in the system’s design baseline, all end items received 75 from the Contractor shall be updated with the change. This does not mean that a 76 lengthy “test-fix-test” approach is desired by the Government. If a change to the 77 system’s design is significant, such as one which would require retesting of multiple 78 tests or which would cause a significant schedule delay, the Government may note the 79 failure to meet a requirement and may choose not to continue testing, which may affect 80 the Contractor’s competitiveness for any follow-on production contract. 81

5. Design and Configuration Management 84

This effort will establish a product baseline to define the configuration of the STEP 3kW 85 generator set with a demonstrated capability to satisfy the requirements in Purchase 86 Description PD 6115-0133. During the first two phases of the effort, the Contractor shall 87 design the system and develop this baseline. They shall present the design and 88 baseline at two reviews, a Preliminary Design Review (PDR) and a Critical Design 89 Review (CDR). The Contractor shall establish this baseline and present it to the 90 Government prior to the building of the final prototypes. The baseline shall be 91 demonstrated with the delivery of STEP 3kW prototypes at a Test Readiness Review at 92 the end of the third phase. The Contractor shall deliver presentation materials from all 93 reviews to the Government in accordance with (IAW) Contract Data Requirements List 94 (CDRL) C001, PDR / CDR / TRR Presentation Materials, and as stated below. If the 95 Contractor deems any configuration changes to be warranted during testing and 96 evaluation, those shall be presented to the Government at the bi-weekly update 97 meetings and agreed to by the Government prior to changes being performed. Any 98 changes shall also be documented and presented to the Government in a final report at 99 the end of the phase. 100

5.1. Preliminary Design Review 101

The Contractor shall participate in a system-level Preliminary Design Review (PDR) and 102 have all studies, estimates, analyses, designs, and reports available for the Government 103 to review at least 14 days prior to the PDR, IAW CDRL C001. The PDR shall be used 104 to resolve any issues in the purchase description; however, it will not be used as an 105 opportunity to impose additional requirements. The PDR shall include each equipment, 106 hardware and software configuration item, and related peculiar support equipment. The 107 Contractor shall show and/or demonstrate that evaluations of materials, lead times, 108 tooling, fabrication techniques, assembly methods, test equipment, skills, processes, 109 and inspection techniques have been accomplished for each equipment, hardware and 110 software configuration item, and related support equipment; shall show and/or 111 demonstrate that producibility objectives have been achieved; and shall identify all 112 single source, sole source, and diminishing source(s). This review will evaluate the 113 progress, technical adequacy, and risk resolution (on a technical, cost, and schedule 114 basis) of the design and will assess the technical risk associated with the selected 115 manufacturing (assembly) methods (processes). Topics the Contractor shall cover at 116 the PDR shall include, but not be limited to, the following: 117

a. Detailed Program Plan indicating Design, Fabrication, and Test Phases 118

b. Electrical and mechanical design 119

c. Environment control and thermal design aspects 120

d. Electromagnetic compatibility of the preliminary design 121

e. Power distribution and grounding design aspects 122

f. Preliminary mechanical and packaging design of consoles, racks, drawers, 123 printed circuit boards, connectors, etc. 124

g. Environmental, Safety, and Occupational Health engineering considerations 125

h. Preliminary lists of materials, parts, and processes 126

i. Pertinent reliability/maintainability/availability data 127

j. Preliminary weight data 128

k. Corrosion prevention/control considerations 129

l. Transportability, packaging, and handling considerations 130

m. Standardization considerations 131

n. Trade-studies and design studies results 132

o. Functional flow, requirements allocation data, and schematic diagrams 133

p. Equipment layout drawings and preliminary drawings, including any proprietary 134 or restricted design/process/ components and information 135

q. Interface requirements contained in configuration item development 136 specifications and interface control data (e.g., interface control drawings) derived 137 from these requirements 138

r. Any deviations from original proposed design 139

s. Status of the Technical Performance Measures (TPM) Program 140

5.2. Critical Design Review 141

The Contractor shall participate in a system-level Critical Design Review (CDR) and 142 have all studies, estimates, analyses, designs, and reports available for the Government 143 to review at least 15 days prior to the CDR IAW CDRL C0001. The Contractor shall 144 present a final design that incorporates all deficiencies identified from the PDR. The 145 Contractor shall provide a detailed review of the hardware design for the set and all data 146 items required by the contract. The Contractor shall provide a trace capable of 147 demonstrating that the design furnished at CDR implements the performance 148 requirements of the PD, and present the methods used to verify and validate the design. 149 The Contractor shall present the results of producibility analyses conducted on system 150 hardware for Government assessment to ensure detailed producibility design solutions 151 satisfy the established requirements. Topics the Contractor shall cover at the CDR shall 152 include, but not be limited to the following: 153

a. Detailed Program Plan indicating Design, Fabrication, and Test Phases 154

b. Interface specification/drawings 155

c. Detailed Electrical/Mechanical/Software Design 156

d. EMI/Thermal/Cooling Design 157

e. Detailed Reliability/Maintainability Analysis 158

f. Detailed weight data 159

g. Environment, Safety, and Occupational Health (ESOH) Analysis 160

h. Packaging/Handling/Storage/Transportation 161

i. Testing documents 162

j. Interoperability considerations 163

k. Transportability considerations 164

l. Corrosion Prevention and Control (CPAC) 165

m. Critical Safety Items (CSIs) 166

n. Diminishing Manufacturing Sources and Material Shortages (DMSMS) 167

o. Open Systems Design 168

p. Quality and Producibility for manufacturing 169

q. Supportability 170

r. Mock-ups, breadboards, and/or prototype hardware developed 171

s. Any deviations from design presented at PDR 172

t. Status of the Technical Performance Measures (TPM) Program 173

5.3. Test Readiness Review 175

The Contractor shall participate in a Test Readiness Review (TRR) and have all studies, 176 estimates, analyses, designs, and reports available for the Government to review at 177 least 15 days prior to the TRR, IAW CDRL C0001. The TRR shall be used to assess 178 the system under review for development maturity, cost/schedule effectiveness, and risk 179 to determine readiness to proceed to formal testing. Topics the Contractor shall cover 180 at the TRR shall include, but not be limited to, the following: 181

a. Interface specification/drawings 182

b. Test data or engineering analysis to support confidence in meeting performance 183 requirements 184

c. Results of all testing conducted on prototype designs 185

d. Basic review of operation and maintenance procedures 186

e. Quality and Producibility for manufacturing 187

f. Supportability 188

g. Hardware demonstration 189

h. Any deviations from design presented at the most recent design review 190

i. Status of the Technical Performance Measures (TPM) Program 191

5.4. Technical Data Package 192

A complete set of 3D Product Level TDP with Product Drawings/Models and Associated 193 Lists shall be delivered. The Product Drawings and Associated Lists shall be delivered 194 IAW the following: 195

1) STEP 3kW Statement of Work, paragraph 5.1 196

2) Appendix A, the TDP Selection Worksheet 197

3) MIL-STD-31000B 198

4) CDRL C002, Product Drawing and Associated Lists 199

The TDP shall depict all end item components and the assembly and integration 200 thereof. The Product Drawings shall define the requirements of form, fit, function, and 201 interface as required in this SOW. Product Drawings/Models and Associated Lists shall 202 provide the design, engineering, manufacturing, and quality assurance requirements 203 information necessary to enable the procurement or manufacture of an interchangeable 204 item that duplicates the physical and performance characteristics of the original product 205 without additional design engineering effort or recourse to the original design activity. 206 Product Drawings shall also contain all test procedures associated with individual 207 components, subassemblies, and assemblies as necessary to comply with this SOW. 208 All information, documentation, software, and firmware necessary to produce and utilize 209 required test fixtures shall be included in the drawings. The PD shall be used as the 210 base specification for the TDP. 211

5.4.1. Drawing requirements. The drawings shall comply with: 212

a. ASME Y14.1 – Decimal Inch Drawing sheet size and format 214

b. ASME Y14.1M – Metric sheet size and format 215

c. ASME Y14.24 – Types and applications of engineering drawings 216

d. ASME Y14.34 – Associated Lists 217

e. ASME Y14.35M – Revision of engineering drawings 218

f. ASME Y14.41 – Digital products definitions 219

g. ASME Y14.5 – Dimensioning and Tolerancing. Tolerances on dimensions 220 that locate features of size shall be specified by use of the positional 221 tolerance method. If irregular shaped features are specified, use of profile 222 tolerancing may be used. Tolerance values selected shall allow the end 223 items to be 100% interchangeable where any end item purchased shall 224 interface properly with the mating part 225

h. ASME Y14.100 – Engineering drawing practices 226

i. Drawings shall not be smaller than C (A2), nor larger than D (A1) 227

j. Drawings with multiple sheets shall include all sheets in a single PDF file. 228

k. All drawings shall specify marking per MIL-STD-130L for assemblies and 229 detailed parts. 230

5.4.2. Control Drawings 231

The Contractor may provide control drawings IAW ASME Y14.100 and CDRL C002, 232 Product Drawing and Associated Lists. Commercial or vendor-developed items or items 233 purchased directly "off-the-shelf," not covered by Government design activity drawings, 234 and not developed with Government funds, shall be represented by appropriate control 235 drawings. Where practical and if applicable, a minimum of two qualified and accepted 236 manufacturing sources of supply shall be provided for each source control drawing, 237 except for the engine, main alternator (generator), and control system. 238

5.4.3. Envelope Drawings 239

The Contractor shall develop envelope drawings depicting the configuration item from 240 all four sides and top. The envelope drawings shall describe key characteristics such as 241 the overall housing dimensions, door swing dimensions, forklift pocket locations, center 242 of gravity locations, control box location, etc., IAW CDRL C002, Product Drawing and 243 Associated Lists. 244

5.4.4. Technical Data Package List (TDPL) 245

The Contractor shall deliver a TDPL IAW CDRL C002, Product Drawing and Associated 246 Lists. The TDPL shall be as specified in MIL-STD-31000B. The TDPL submittal shall 247 be editable to enable future updates. 248

5.5. Technical Performance Measures (TPM) Program. 249

The Contractor shall develop a TPM program which identifies critical technical 251 parameters (CTP) that are at risk of not being met during system design. The 252 Contractor shall forecast the CTPs’ values at each Government technical review. At a 253 minimum, the TPM program shall address the following PD paragraphs as CTPs: 254

• 3.2.1 Set rating 256

• 3.3 Reliability 257

• 3.8 Starting, operating, and stopping (with sub-paragraphs) 258

• 3.23 Non-linear load 259

• 3.30 Governing system (with sub paragraphs) 260

• 3.31.12 Voltage performance (with sub-paragraphs) 261

6. Quality Control 262

The Contractor shall manage quality control with internal processes. The Government 263 will review, and approve at the Government’s discretion, the Contractor’s Quality 264 Control Plan IAW CDRL C003, Quality Control Plan. 265

7. Logistics 266

The Contractor shall develop and deliver an Operator and Maintainer and Repair Parts 267 and Special Tools List (RPSTL) Electronic Technical Manual (ETM) IAW CDRL C004, 268 Electronic Technical Manual (ETM), to support the STEP 3kW (including all 269 troubleshooting, maintenance, and repair actions that will not be covered by test 270 support). The Contractor shall also conduct user training prior to the user evaluation. 271 This training should consist of no more than eight (8) hours to include materials and 272 instructors for up to 20 students. Hardware delivery will include consumables, with the 273 exception of fuel and oil, for up to 2,000 hours of operation for developmental testing 274 and user evaluations. The Contractor will provide repair parts as needed during test and 275 evaluation support. 276

7.1. Logistics Support Package 277

Electronic Technical Manual (ETM). The Contractor shall develop an ETMsIAW criteria 279 outlined in MIL-STD-40051-2 in an editable electronic format. The manual shall provide 280 safe, comprehensive, and accurate operating procedures that can be accomplished 281 within the aptitude and physical capabilities of the designated military user. The 282 maintenance information shall allow for safe, comprehensive, and accurate 283 troubleshooting, diagnosis, repair/replacement, checkout and return to service of the 284 equipment by the designated military maintenance technician. Illustrations shall be 285 drawn to comply with MIL-STD-40051-2. Newly developed graphics shall be in vector in 286 native format. The Contractor shall prepare a separate figure for each breakdown of a 287 repairable assembly. Per DI-SESS-81759A, the Contractor shall also submit all digital 288 source files for each ETM electronically by e-mail, file transfer protocol (FTP), or 289 alternate method, as arranged with the AOR, and by CD ROM or DVD readable. The 290 Contractor shall develop ETM source data items in Extensible Markup Language (XML) 291 using the Contractor’s choice of XML editor that works with the Document Type 292 Definitions (DTD) and stylesheets available online at the following location: 293 https://ent.ldac.army.mil/etmapp/#/etm/search. The Government will furnish target 294 audience descriptions, and front matter, rear matter, and supporting information 295 boilerplate content. 296 Technical Manual Review. At 30%, 70%, and 90% completion, the Contractor shall 298 deliver draft technical manuals in digital format to the Government IAW MIL-STD-299 40051-2. Preceding the submission of 30%, 70%, and 90% (final draft) completion 300 deliverables, at least two monthly in-Process Reviews (IPRs) shall take place with 301 stakeholders and shall include, but not be limited to: Contractor, Government technical 302 writer, Government provisioner, Government engineer, Government equipment 303 publications control officer representative, and Government AOR. The Government will 304 provide comments to the draft submissions within 25 days of review. The Contractor 305 shall incorporate all technical manual change comments provided to the Contractor by 306 the Government within 21 days of the receipt of the comments. Any deviation from the 307 in-process reviews shall be documented and provided to the AOR for review and 308 response. If approved, minor changes can be reviewed at the final draft completion and 309 will be documented in the ETM, IAW MIL-STD-40051-2. 310 Technical Manual Validation. The Contractor shall submit a Technical Manual 312 Validation Plan IAW DI-TMSS-81818. The Contractor shall validate the technical 313 manuals at the Contractor’s facilities or at an alternate location, determined in 314 coordination with the Government. In addition to content validation, the XML tags shall 315 be parsed and any errors corrected, and all technical manual functional features shall 316 be validated as operational and correct. Contractor personnel performing operating and 317 maintenance procedures on the equipment during validation should have a similar 318 training and skill level to that which would be expected of Soldiers using the equipment. 319 Contractor validation records shall be subject to Government inspection at any time 320 during the performance of the Contract, without prior notice. The Contractor shall deliver 321 upon completion a Technical Manual Validation Certificate IAW DI-TMSS-81819. The 322 Government reserves the right to witness the Contractor validation. The Contractor shall 323 incorporate all red-line changes identified in the validation process prior to delivery to 324 the Government. 325

The Contractor shall update the ETM (CDRL C004, Electronic Technical Manual) based 326 on feedback from the Government and the user evaluation. The manual shall provide 327 safe, comprehensive, and accurate operating procedures that can be accomplished 328 within the aptitude and physical capabilities of the designated military user. The 329 maintenance information shall allow for safe, comprehensive, and accurate 330 troubleshooting, diagnosis, repair/replacement, checkout and return to service of the 331 equipment by the designated military maintenance technician. 332

The Contractor shall perform a Failure Modes, Effects, and Criticality Analysis (FMECA) 333 for the system. The analysis shall examine each separable part in the system and 334 determine how it might fail, and the effect of failure on the system. The results of the 335 FMECA shall be provided in a FMECA Report IAW CDRL C005, Failure Modes, Effects, 336 and Criticality Analysis (FMECA) Report. In addition to the information required by DI-337 SESS-81495A, the FMECA Report shall include: 338

• Part number 339

• Manufacturer 340

• Estimated service life 341

• Unit cost (to be used by the Government for potential future sustainment planning 342 purposes) 343

The Contractor shall analyze the maintenance support functions necessary for the 344 system and identify recommended maintenance requirements. The analysis shall 345 determine the maintenance tasks (including Preventive Maintenance Checks and 346 Services), task intervals, and tools required for the task. The analysis shall consider: 347 FMECA results, component manuals and data, economic consequences of failure, and 348 when scheduled maintenance could prevent failures. The Contractor shall identify any 349 commercial sources of maintenance for the system, and for major assemblies or 350 components. The results of the analysis shall be provided in a Maintenance Analysis 351 Report IAW CDRL C006, Maintenance Analysis Report. 352

• 353

7.2. Item Unique Item Identification (IUID) 354

7.2.1 The Contractor shall identify all items that may require an IUID in accordance with 355 DFARS clause 252.211-7003 and submit an implementation plan CDRL Item Unique 356 Item Identification (IUID) Marking Plan for Government review/concurrence. A draft list 357 of components to be marked shall be presented at the Logistics Start of Work Meeting. 358

7.2.2 IUID Construct and Method. The Contractor shall create the IUID and marking 359 method IAW MIL-STD-130N. The Contractor shall use IUID Construct #2. The UID 360 marking shall include the (UII) on the IUID plate or label, or on the item identification 361 plate, or directly on the item in 2D Data Matrix barcode symbology. The end item UID 362 marking shall be embedded on the system data plate. A 2D Data Matrix, ECC 200 363 compliant bar code (ISO/IEC 16022) shall be used to carry the IUID data elements. The 364 machine readable information (MRI) shall contain discrete elements including: 365

• Unique item identifier (Construct 2) 366

• Enterprise Identifier 367

• Original Part Number 368

• Serial Number 369

7.2.2.1 Identification/Data Plate for End Items. The Contractor shall use MIL-STD-130 370 (current revision), as a guide when developing the “SYSTEM” data plate. The end item 371 UID marking shall be embedded on the system data plate. The End Item 2D matrix shall 372 contain human and machine-readable markings and shall be no less than 1 cm wide 373 and no less than 40% contrast. The minimum data plate information for the Parent End 374 Item is listed below: 375

a) Nomenclature 376

b) National Stock Number (NSN) 377

c) Design Activity: (MFR ID Cage Code) 378

d) Government Ownership Designation: US Property 379

e) Contract Number 380

f) 2-dimensional IUID data matrix 381

g) Unique Item Identifier (UII) 382

7.2.2.2 Data Plates for Subassemblies, Components, or Other Parts. All spare parts, 383 secondary repairables, and consumables candidates that determined from the DFARS 384 clause 252.211-7003 shall also be marked with the IUID prior to delivery to the 385 Government. The Contractor shall ensure all use MIL-STD-130, figure 9 as a guide 386 when developing the IUID marking for subassembly, component or parts. The Child End 387 Item 2D matrix shall contain human and machine-readable markings when possible and 388 shall be no less than 1 cm wide and no less than 40% contrast. If the item has a data 389 plate, the IUD marking shall be embedded on the data plate. 390

7.2.3 IUID Location and Marking. The locations and marking methods selected should 391 bear no impact on the performance of the part and minimal configuration change(s) to 392 the part. All 2D data matrices shall be permanently affixed and have the ability to 393 withstand and perform within the same environmental conditions as the SYSTEM. 394

The Contractor shall perform engineering analysis required to determine the appropriate 395 method for marking each item that requires IUID. The Contractor shall ensure that the 396 IUID marking location will be optimized for ease of scanning and shall avoid applying 397 IUID markings on curved or rounded surfaces. 398

The IUID marking should be incorporated into existing data plates when possible. The 399 end item UID marking shall always be embedded on the system data plate. The 400 Contractor shall document the location and marking method on the engineering 401 technical documentation (e.g. drawings). 402

7.2.4 IUID Registration. The Contractor has the responsibility to furnish IUID data to the 403 IUID registry. The Contractor shall register and validate all IUIDs with the DoD IUID 404 Registry and shall ensure all item parent/child relationships are accurately recorded in 405 the IUID Registry. Data submission of IUID data and acquisition cost should be 406 submitted via Wide Area Work Flow (WAWF), IUID XML file, IUID flat file or web entry. 407 Additional information regarding data submission as well as the actual marking can be 408 found at https://dodprocurementtoolbox.com/site-pages/overview-iuid-registry. CDRL 409 Data Registry 410

7.2.5 IUID Data Records. The Contractor shall maintain an accurate, current list of UIIs 411 for all items procured under this contract. This list shall be supplied to the Government 412 upon request. The list shall include UII, P/N, Serial Number, CAGE, Parent UII (if 413 applicable), construct used, IUID location, type of marking, and registration method 414 used. The list shall be prepared and delivered IAW CDRL C015, IUID Marking Plan). 415

7.2.6 Item Unique Identification (IUID). The Contractor shall update the Government 416 IUID plan and deliver an updated IUID Implementation Plan that includes the IUID 417 marking of all “SYSTEM” unique components IAW MIL-STD-130N, and the latest 418 guidance found on the Defense Procurement and Acquisition Policy IUID website 419 (https://dodprocurementtoolbox.com/site-pages/unique-id-overview). The Contractor 420 shall develop and assign IUID constructs for components and assemblies IAW MIL-421 STD-130N or current revision. IUID shall be applied to items IAW MIL-STD-130N or 422 current revision. The Contractor shall upload IUID records into the DoD registry. 423

7.2.7 Hardware Changes in IUID. For any hardware change as a result of an 424 engineering change proposal (ECP), the Contractor shall recommend and the 425 Government concurs on the determination of tag locations. As changes are made to the 426 “System,” the Contractor shall use the above information in deciding if changes need to 427 be made or revised to insure IUID tag marking. 428

8. Management Objectives and Deliverables 429

The Contractor shall support a kick-off meeting detailing administrative roles, technical 430 approach, and programmatic approach and submit presentation materials IAW CDRL 431 C009, Post-Award Orientation Meeting Presentation Materials. Additionally, the 432 Contractor shall attend bi-weekly technical telecons with the Government and deliver bi-433 monthly progress reports IAW CDRL C010, Bi-monthly Progress Report. Bi-monthly 434 progress reports that coincide with an end of phase report are not needed. The 435 Contractor shall also deliver a final summary / technical report and final presentation for 436 each project phase in which the Contractor performs work IAW CDRL C014, End of 437 Phase Report. During phases 1–3, at a minimum, the Contractor shall attend and lead a 438 kick-off meeting, attend bi-weekly teleconferences to present project status, submit bi-439 monthly progress reports, and attend phase final reviews as stated in Sections 5.1, 5.2, 440 and 5.3. During Phase 4, the Contractor shall provide support to any issues 441 encountered in testing while continuing to attend bi-weekly teleconferences and 442 submitting bi-monthly progress reports on any test support which is provided. 443

[As part of proposal preparation, additional meetings, reports, or other management 444 work may be offered but are not required by the Government]. 445

The work performed under this SOW shall include the development and delivery of all 446 data necessary to support the STEP 3kW (including provisioning, installation, 447 operational and repair manuals; engineering data; and technical data) consistent with 448 the maintenance concept. Compatibility (form and format) of the data with existing 449 Government systems is required. The following provides a summary of the data 450 deliverables: 451

CDRL Deliverable Frequency/Expected Delivery

C001 Preliminary Design Review (PDR) / Critical Design Review (CDR) / Test Readiness Review (TRR) Presentation Material

Twice: 14-days prior to the PDR/CDR/TRR and 7 days following each review

C002 Product Drawings and Associated Lists Twice: 7-days following CDR; 14-days prior to end of phase 3

C003 Quality Control Plan Once; 90-days after contract award

C004 Electronic Technical Manual (ETM) Three times; at 30%, 70% and at 90% completion

C005 Failure Modes, Effects, and Criticality Analysis (FMECA) Report

Once: 14-days prior to end of phase 3

C006 Maintenance Analysis Report Once: 14-days prior to end of phase 3

C007 ) CDRL C007 Has Been Deleted C008 Bar Code Identification Report Concurrent with delivery of equipment C009 Post-Award Orientation Meeting Presentation

Materials Once: 30-days after contract award

C010 Bi-monthly Progress Report Bi-monthly with first submission due at the end of the second calendar month after award;

subsequent submissions due at the end of every other month

C011 Safety Assessment Report (SAR) Four times: 21-days prior to end of each phase

C012 Software Requirement Specification Once, 30-days prior to end of phase 3

C013 Computer Software Product Once, 30-days after the start of phase 4

CDRL Deliverable Frequency/Expected Delivery

C014 End of Phase Report Four times: 14-days prior to end of each phase

C015 IUID Marking Plan Twice: draft NLT end of phase 3 and final NLT five months after start of phase

The following is a list of hardware deliverables. All hardware deliverables are due at the 452 conclusion of Phase 3, Prototype Build. Any accessory which is listed as “if required” in 453 the Purchase Description shall be included as a hardware deliverable if it is required to 454 demonstrate that the system meets a proposed technical requirement. 455

Deliverable Quantity PD Reference

STEP generator set, every set includes:

• Stacking accessory

• Ground rod

• Battery(ies)

• Auxiliary fuel line

30 3.2

3.18.1 3.18.7.1 3.28.2.1 3.29.2.2

AC/Dual use feeder Box (with accessories) 27 3.35.6

DC feeder box (with accessories) 23 3.35.6

Wheel and Handle Accessory 4 3.12.9

PDU to M46 Adapter Cable 5 3.19.2.4

Remote one receptacle cable 10 – 25ft 5 – max length 3.34.4

Remote two receptacle cable 5 – max length 3.34.5

Remote three receptacle cable 5 – max length 3.34.6

PoE Ethernet switch 5 3.34.7

Parallel receptacle cable 5 3.35.4

Winterization Accessory 3 3.28.6.2

Consumables for testing Sufficient for 30 sets for 2,000 hours

SOW 7

Repair parts for testing As required SOW 7

9. Security 457

9.1. The contract shall be performed at the UNCLASSIFIED level. 458

9.2. Controlled Unclassified Information (CUI) generated and / or provided under the 459 contract shall be safeguarded and marked as specified in DoDM 5200.01, Vols 1–4. 460

9.3. The Contractor shall prepare a DD Form 1540, Registration for Scientific and 461 Technical Information Services, in advance of any work to be performed, through the 462 office listed in Block 12 for registration to the Defense Technical Information Center 463 (DTIC). DD2345, Militarily Critical Technical Data Agreement, will be completed for 464 release and acceptance of Military Critical Technical Data. 465

9.4. Contract deliverables will be marked with the DISTRIBUTION STATEMENT listed 466 on the applicable CDRL. The Government many unilaterally change the required 467 Distribution Statement(s) at any time. Requests for contract-related documents shall be 468 referred to the Point of Contacts listed on the applicable CDRL. All other Deliverables 469 will be marked with a DISTRIBUTION STATEMENT E: Distribution authorized to DoD 470 components only. Other requests for this document shall be referred to Product 471 Manager, Mobile Electric Power Sources (PM MEPS), Bldg 324, 5850 Delafield Rd, Ft. 472 Belvoir, VA 22060. 473

9.5. Contractor-employees that do not require Common Access Cards (CACs), but 474 require access to a DoD facility or installation: employees shall comply with adjudication 475 standards and procedures using the National Crime Information Center Interstate 476 Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 477 2014-05/AR 190-13), applicable installation, facility and area commander 478 installation/facility access and local security policies and procedures (provided by 479 Government representative). 480

9.6. A Threat Awareness and Reporting Program (TARP) briefing is required for 481 Contractor employees supporting this contract. The Contractor and its employees shall 482 be aware of and report threat-related incidents, behavioral indicators, and other matters 483 of Counterintelligence (CI) interest as specified in Army Regulation (AR) 381-12, Threat 484

Awareness and Reporting Program, Chapter 3. Incidents will be reported to Defense 485 Security Service (DSS), the COR, or nearest military CI office. 486

9.7. Per AR 530-1, Operations Security (OPSEC), new Contractor employees 487 supporting this contract must complete Level I OPSEC training. New Contractor 488 employees must be trained within 30 calendar days of reporting for duty performing and 489 annually thereafter. OPSEC awareness training is available at: 490 http://securityawareness.usalearning.gov 491

10. Safety. 493

10.1 System Safety. 495

The Contractor shall implement an Environmental, Safety, and Occupational Health 496 (ESOH) program in accordance with MIL-STD-882E that will identify, assess, and 497 mitigate ESOH hazards to an acceptable level for the life of the program. The ESOH 498 program shall evaluate the system as well as any hardware and software upgrades for 499 ESOH impact, and shall ensure that ESOH requirements flow down to subcontractors. 500

10.2 Safety Assessment Report (SAR). 502

The Contractor shall prepare a Safety Assessment Report (SAR) in accordance with 503 task 301 of MIL-STD-882E and CDRL C011, Safety Assessment Report, which shall 504 evaluate the Environmental, Safety and Occupational Health (ESOH) hazards of the 505 overall system. The SAR shall describe the safety program established by the 506 Contractor, the various safety tasks and activities, and the interrelationship between 507 system safety and other program functional elements. It shall describe the methods, 508 analyses, and tests used to identify and assess hazards (both hardware and software) 509 and their associated risks, the methodology used to rank hazards, and how ESOH 510 requirements flow down to subcontractors. 511 As a minimum, the SAR shall include the purpose and intended use of the system; a 513 historical summary of development; a description of components, to include 514 photographs, diagrams and schematics; and description of any other interfacing 515 systems. The SAR shall identify all ESOH features of the system hardware and 516 software design; identify specific controls, limitations, or precautions required; and shall 517 verify compliance to safety requirements identified in the performance specifications 518 and/or applicable consensus safety standards. The SAR shall include a complete list of 519 warnings, cautions, and safety procedures required in technical manuals and training 520 courses. Conclusions and recommendations shall also be provided along with a 521 summary of significant residual hazards. The SAR shall have a statement signed by the 522 Contractor safety manager and program manager stating that all hazards have been 523 identified, eliminated and/or controlled. Safety Data Sheets for all hazardous materials, 524 a printout of the hazard log, and a completed SEL Form 1183 System Safety Design 525 Verification Checklist will also be appended to the SAR. 526 The SAR shall include an analysis of all applicable potential health hazards, such as 528 heat and cold stress, noise, inadequate ventilation, exhaust, vibration, Nuclear 529 Biological Chemical (NBC) protection, toxic substances, and ionizing and non-ionizing 530 radiation. If the equipment produces non-ionizing radiation, the Contractor shall provide 531 calculations for the hazard range. Radioactive materials may not be used in the system 532 without specific Government approval. The SAR must contain a statement verifying 533 absence of radioactive materials. Hexavalent Chromium may not be used in the system 534 without specific Government approval. The SAR must contain a statement verifying 535 absence of Hexavalent Chromium. 536 The Contractor shall identify any hazardous materials used in the design, operation or 538 maintenance of the system and shall assess the associated occupational health and 539 environmental impact risk. The Contractor shall identify the impacted components 540 along with the necessary controls to mitigate risk. 541

10.2.1 Health Hazards. The SAR shall include an analysis of all potential health 543 hazards such as heat and cold stress, noise, inadequate ventilation, exhaust, vibration, 544 NBC protection, toxic substances, and ionizing and non-ionizing radiation. Sufficient 545 detail shall be provided to clearly define the specific problem, issues involved and 546 reasoning behind the analysis. The assessment must include an analysis of data, 547 observations, findings, reports and other sources of information. If the equipment 548 produces non-ionizing radiation, the Contractor shall provide calculations for the hazard 549 range. 550

10.2.2 Toxic Substances. The SAR shall address toxic substances used in the system. 552 The evaluation shall include any exposure concerns to personnel during operational or 553 maintenance procedures to include fabrication, transportation, setup and tear down, or 554 resulting from damage to the equipment. Any special disposal procedures shall be 555 addressed. 556

10.2.4 Hazard Materials and Pollution Prevention. 558

The Contractor shall describe the hazardous materials management effort implemented 559 to assure that appropriate consideration is given to the elimination/reduction of 560 hazardous material, and to the proper control of hazardous materials that are not 561 eliminated, for systems and system components and associated support items 562 throughout all phases of the system life cycle per Task 108 of MIL-STD-882E and 563 NAS411. NAS 411-1 describes targeted HAZMAT in the prohibited, restricted and 564 tracked categories. The Contractor shall describe the method of ensuring subcontractor 565 hazardous material compliance and reporting. The Contractor shall assess the 566 occupational health and environmental risk associated with identified hazardous 567 materials, shall identify the necessary controls, and shall document any trade-off 568 analysis for alternative materials and the associated cost impact. 569

10.2.5 Safety Inspection and Verification. The Contractor shall schedule sufficient time 571 in the program schedule to permit a safety inspection of the system by the Government 572 prior to technical testing, user testing, and contract completion (Phase II). The 573 inspections will be used to verify the information contained in the SAR. The Contractor 574 must allow sufficient time to correct any unresolved high or serious risk hazards prior to 575 testing or delivery of the system to the Government. 576

10.2.6 Hazard Tracking. 578

The Contractor shall identify, assess, and track potential system hazards in a hazard log 579 in accordance with Task 106 of MIL-STD-882E. The hazard log shall be appended to 580 and summarized in the Safety Assessment Report (SAR). A Risk Assessment Code 581 (RAC) shall be assigned to each identified hazard as defined in MIL-STD-882E. All 582 potential hardware and software hazards shall be included in this hazard log and shall 583 be tracked until final resolution. Hazards that cannot be eliminated by design shall be 584 considered residual hazards unless the Government agrees that the design meets or 585 exceeds applicable consensus and/or military design standards and that the 586 environment in which it will operate is consistent with that envisioned by the design. 587 Government concurrence is required for any actions that eliminate, mitigate, or close 588 hazards listed in the hazard log. 589

11. Risk Management. The Contractor shall conduct risk identification and analysis 591 during all phases of the program and apply appropriate risk management strategies and 592 plans. The Contractor shall support, as required, Government risk management efforts, 593 such as by participating in a Risk Management Board conducted by the Program Office 594 or similar meeting; reporting issues to senior management and other stakeholders; and 595 training program personnel. The Contractor shall also use testing to identify and limit 596 the impact of potential risks as described below. 597

• Conduct early risk-focused developmental testing with adequate time for necessary 599 regression tests. 600

• Conduct testing with predefined success criteria to facilitate resolving integration 601 activities and failure modes before the start of Government testing in Phase 4. 602

12. Software. If software (embedded or otherwise) is required for the Contractor’s 604 system to enable TMS compliance or to meet another requirement specified in PD 605

6115-0133, the Contractor shall provide information about the Software Requirement 606

Specification IAW CDRL C012, Software Requirement Specification, and shall provide 607 the software and its source code IAW CDRL C013, Computer Software Product. The 608

Government requires the source code to evaluate the software for vulnerabilities; the 609

Government’s software vulnerability analysis may be performed by third-party 610 companies providing that service to the Program Office, regardless of the level of data 611 rights license proposed for the software. 612

Appendix A: TDP Selection Worksheet 614

TDP OPTION SELECTION WORKSHEET

SYSTEM: STEP 3kW DATE PREPARED: 18 MAR 22

A. CONTRACT NO.

B. EXHIBIT/ATTACHMENT

NO.

C. CLIN

D. CDRL DATA ITEM NO.

C002

1. TDP Level ((CHOOSE ONLY ONE PER WORKSHEET). Note: The level selected must coincide with the requirements of the elements selected in block 5.

A. CONCEPTUAL LEVEL

DEVELOPMENTAL LEVEL

PRODUCTION LEVEL

B. REMARKS:

2. TYPE AND FORMAT (X all that apply and complete as applicable) A. TYPE 2D: 2D DRAWINGS (describe in detail in remarks below or in block 11):

NATIVE CAD (SPECIFY TYPE) ________________________

ISO32000 PORTABLE DOCUMENT FORMAT: ____________________

HARDCOPY: _______________________________________________

OTHER ELECTRONIC FORMAT (SPECIFY TYPE) ________________________________

REMARKS:

B. TYPE 3D: 3D MODEL BASED (describe in detail in remarks below or in block 11):

NATIVE CAD (SPECIFY TYPE) _CREO or Solidworks_______________________ 3Di VIEWABLE* FORMAT DERIVED FROM 3D NATIVE MODELS (Specify type, i.e. ISO 32000 PDF etc.).

NEUTRAL FORMAT DERIVED FROM 3D NATIVE MODELS (Specify type, i.e. STEP AP203, AP 214 etc.).

2D DRAWINGS DERIVED FROM 3D NATIVE MODELS (Specify type, i.e. ISO 32000 PDF etc.).

OTHER FORMAT (SPECIFY TYPE): __See Remarks__________________________ *NOTE: 3Di viewable will be in ISO 32000 pdf format unless otherwise specified.

REMARKS: When 2D software is used for things like Schematics, Wiring Diagrams, etc., the native files shall be delivered in AutoCAD.

3. CAGE CODE AND

DOCUMENT NUMBERS

A. CONTRACTOR CAGE AND DOCUMENT NUMBERS

GOVERNMENT CAGE (COMPLETE 3B & 3C OR 3D)

B. USE CAGE CODE:

30554

C. USE DOCUMENT NUMBERS:

To be provided

D. To Be Assigned By:

The Government

4. DRAWING FORMATS (X one and complete as applicable)

CONTRACTOR FORMAT GOVERNMENT FORMAT.

REMARKS: PM E2S2 Format to be provided

5. TDP ELEMENTS REQUIRED (X all that apply)

ELEMENTS REQUIRED TO BE DETERMINED BY CONTRACTOR

-OR THE FOLLOWING ARE REQUIRED:

CONCEPTUAL DRAWINGS/MODELS AND ASSOCIATED LISTS

DEVELOPMENTAL DESIGN DRAWINGS/MODELS AND ASSOCIATED LISTS

PRODUCT DRAWINGS/MODELS AND ASSOCIATED LIST

COMMERCIAL DRAWINGS/MODELS AND ASSOCIATED LIST

QUALITY ASSURANCE PROVISIONS

SPECIAL INSPECTION EQUIPMENT (SIE) DRAWINGS/MODELS AND ASSOCIATED LISTS

SPECIFICATIONS

SOFTWARE DOCUMENTATION

SPECIAL PACKAGING INSTRUCTIONS (SPI) DRAWINGS/MODELS AND ASSOCIATED LIST

6. APPLICABILITY OF STANDARDS. The following Standards apply: (X as applicable)

ASME Y14.100

ENGINEERING DRAWING

PRACTICES WITH

APPENDICES:

B C D E

COMPANY STANDARDS

PERMITTED? YES NO

ASME Y14.24 TYPES AND APPLICATIONS OF

ENGINEERING DRAWINGS

ASME Y14.34 ASSOCIATED LIST

ASME Y14.35 REVISION OF ENGINEERING

DRAWINGS AND ASSOCIATED LIST

ASME Y14.41 DIGITAL PRODUCT DATA PRACTICES

ASME Y14.5 DIMENSIONING AND TOLERANCES

OTHER STANDARDS APPLY

AS DESCRIBED:

TDP OPTION SELECTION WORKSHEET

A. CONTRACT NO.

B. EXHIBIT/ATTACHMENT

NO.

C. CLIN

D. CDRL DATA ITEM NO.

7. ASSOCIATED LISTS (X and complete as applicable)

A. PARTS LIST (X ONE)* (1) INTEGRAL (2) SEPARATE

B. DATA LIST (X ONE) (1) NOT REQUIRED (2) REQUIRED (SPECIFY LEVELS OF ASSEMBLY)

C. INDEX LIST (X ONE) (1) NOT REQUIRED (2) REQUIRED (SPECIFY LEVELS OF ASSEMBLY)

D. WIRING LIST (X ONE) (1) NOT REQUIRED (2) REQUIRED (SPECIFY LEVELS OF ASSEMBLY)

E. APPLICATION LISTS (X ONE) (1) NOT REQUIRED (2) REQUIRED (SPECIFY…