DRAFT_IDIQ_Section_L_For_Release_9Feb12.pdf

SECTION L 4

INSTRUCTIONS, CONDITIONS, AND NOTICES TO 6

OFFERORS AND RESPONDENTS 7

Xx XXX 20xx 8

Prepared By: 36 Electronic Systems Center 37

Operational Command and Control Division 38

ESC/HSGG 39

11 Barksdale Street, Building 1614 40 Hanscom AFB, MA 01731-1700 41

DRAFT

Page 2 of 48 DRAFT

Revision History 46

Rev Number Date Description Sections

Page 3 of 48 DRAFT

Table of Contents 52

Contents 53

1.0 Program Structure and Objectives .......................................................................................................... 6 54

1.1 Command and Control Applications and Information Services Development (C2AD) Overview and 55

Objectives ................................................................................................................................................. 6 56

1.2 ATOMS Overview and Objectives ....................................................................................................... 6 57

1.3 RISC2 Overview and Objectives .......................................................................................................... 7 58

2.0 General Instructions ................................................................................................................................ 8 59

2.1 General Information ........................................................................................................................... 8 60

2.1.1 Point of Contact ........................................................................................................................... 9 61

2.1.2 Debriefings ................................................................................................................................... 9 62

2.1.3 Discrepancies ............................................................................................................................... 9 63

2.1.4 Electronic Reference Documents ................................................................................................. 9 64

2.1.5 Mandatory and Optional Proposal Submissions .......................................................................... 9 65

2.2 Organization/Number of Copies/Page Limits ..................................................................................... 9 66

2.2.1 Page Limitations ......................................................................................................................... 10 67

2.2.2 Cost or Pricing Information ........................................................................................................ 11 68

2.2.3 Tables, Charts, Graphs and Figures ............................................................................................ 11 69

2.2.4 Cross Referencing ...................................................................................................................... 11 70

2.2.5 Indexing ...................................................................................................................................... 11 71

2.2.6 Glossary of Abbreviations and Acronyms .................................................................................. 11 72

2.3 Page Size and Format ........................................................................................................................ 11 73

2.4 Binding and Labeling ......................................................................................................................... 12 74

2.5 Electronic Offers................................................................................................................................ 12 75

2.6 Distribution ....................................................................................................................................... 12 76

3.0 Volume I – Executive Summary ............................................................................................................ 13 77

3.1 Executive Summary ........................................................................................................................... 13 78

3.1.1 Teaming Arrangements .............................................................................................................. 13 79

3.2 Table of Contents .............................................................................................................................. 13 80

4.0 Volume II –Technical Proposals ............................................................................................................ 16 81

4.1 General .............................................................................................................................................. 16 82

Page 4 of 48 DRAFT

4.2 Format and Specific Content ............................................................................................................. 17 83

4.2.1 Volume II.a Organization: C2AD Contract ................................................................................. 17 84

4.2.2 Volume II.b Organization: RISC2 ............................................................................................... 18 85

4.2.3 Volume II.c Organization: ATOMS ............................................................................................. 20 86

5.0 Volume III – Relevant Past Performance .............................................................................................. 22 87

5.1 General .............................................................................................................................................. 22 88

5.2 Relevant Contracts ............................................................................................................................ 22 89

5.2.1 Specific Content ......................................................................................................................... 23 90

5.2.2 Section 1: Previous Contracting Efforts ..................................................................................... 23 91

5.2.3 Section 2: Customer Assessment ............................................................................................... 24 92

6.0 Volume IV.a and Volume IV.b – Cost/Price Proposals .......................................................................... 24 93

6.1 Introduction ...................................................................................................................................... 24 94

6.2 General Instructions .......................................................................................................................... 25 95

6.2.1 Estimating Techniques and Methods ......................................................................................... 25 96

6.2.2 Cost/Price Information ............................................................................................................... 25 97

6.2.3 Cost or Pricing Information Requirements ................................................................................ 25 98

6.2.4 Subcontractor/Interdivisional Transfer Cost Proposals ............................................................. 25 99

6.2.5 Rounding .................................................................................................................................... 26 100

6.3 Volume IV.a and Volume IV.b Content ............................................................................................. 26 101

6.3.1 Volume IV.a and Volume IV.b Organization............................................................................... 26 102

6.3.2 Section 1: Introduction .............................................................................................................. 27 103

6.3.3 Section 2: Materials/Software Licenses/Services/Subcontracts Summary ............................... 29 104

6.3.4 Section 3: Basis of Estimate ....................................................................................................... 29 105

6.3.5 Section 4: Other Information ..................................................................................................... 30 106

6.3.6 Section 5: Cost Formats Instructions - Submission of Cost Formats ......................................... 33 107

6.3.7 Cost-Plus-Incentive-Fee (CPIF) Arrangement (Volume IV.a) ...................................................... 34 108

6.3.8 Fixed-Price-Incentive-Firm (FPIF) Arrangement (Volume IV.b) ................................................. 34 109

6.3.9 Performance Incentive (Over and Above) Award ...................................................................... 35 110

7.0 Volume V Contract Documentation ...................................................................................................... 35 111

7.1 Model Contract/Representations and Certifications ........................................................................ 35 112

7.1.1 Section A – Solicitation/Contract Form ...................................................................................... 35 113

Page 5 of 48 DRAFT

7.1.2 Section B – Supplies or Services and Costs/Prices ..................................................................... 35 114

7.1.2.1 CLIN Definitions and Prices ................................................................................................. 35 115

7.1.3 Section E – Inspection and Acceptance ..................................................................................... 35 116

7.1.3 Section F – Delivery or Performance ......................................................................................... 35 117

7.1.5 Section G – Contract Administrative Data ................................................................................. 35 118

7.1.6 Section H – Special Contract Provisions ..................................................................................... 35 119

7.1.7 Section J – List of Attachments .................................................................................................. 36 120

7.2 Exceptions to Solicitation Requirements .......................................................................................... 40 121

7.3 Other Information Required ............................................................................................................. 41 122

7.3.1 Authorized Offeror Personnel .................................................................................................... 41 123

7.3.2 Government Offices ................................................................................................................... 41 124

7.3.3 Company/Division Address, Identifying Codes and Applicable Designations............................ 41 125

7.3.4 Data Rights ................................................................................................................................. 41 126

7.4.5 Associate Contractor Agreements ............................................................................................. 42 127

7.4.6 Organizational Conflict of Interest (OCI) Mitigation Plan .......................................................... 42 128

Page 6 of 48 DRAFT

1.0 Program Structure and Objectives 134

1.1 Command and Control Applications and Information Services 136

Development (C2AD) Overview and Objectives 137

a. The goal of this multiple award indefinite delivery indefinite quantity (ID/IQ) contract is to provide a 138 flexible and responsive contract vehicle for the Air Force Electronic Systems Center Operational 139 Command and Control Division (ESC/HSG) to develop, train, field and sustain Command and Control (C2) 140 software applications and services throughout the software lifecycle. The contract is designed to create 141 a pool (C2AD pool) of qualified vendors to meet the software lifecycle needs of various programs within 142 ESC/HSG. Programs supported by this ID/IQ contract vehicle include, but are not limited to: 143

1) Command and Control Air Operations Suite (C2AOS) 145

2) Command and Control Information Services (C2IS) 146

3) Unit Level/Unit Command and Control (UL/UC2) and Unit Command and Control (UC2) 147

4) Personnel Recovery Command and Control (PRC2) 148

b. ID/IQ contracts will be awarded to a number of Offerors possessing the necessary skill set to 150 accomplish the anticipated efforts envisioned for the Period of Performance (PoP) of the contract. 151 Specific work efforts will be accomplished through individual delivery orders (DO) which will be 152 competed among the pool of ID/IQ awardees in accordance with the Fair Opportunity Procedures under 153 FAR Part 16.5 and supplements. 154

c. All Offerors awarded an ID/IQ contract will also be awarded a DO encompassing a Post-Award 156 Conference (PAC). The PAC fulfills the minimum guarantee requirement (FAR Part 16.5). Concurrent with 157 the initial ID/IQ contract awards, the Government intends to award two additional DOs: Request 158 Information Services for Command and Control (RISC2) and Air Tasking Order Management System 159 (ATOMS). Only C2AD pool awardees may compete for the award of one or both of the additional DOs. 160

1.2 ATOMS Overview and Objectives 161

a. Today, the Theater Battle Management Core System-Force Level (TBMCS FL) provides the Joint 162 Forces Air Component Commander (JFACC) with the means to plan, direct, and control all theater air 163 operations in support of Command objectives and to coordinate with ground and maritime elements 164 engaged in the same operation. TBMCS FL provides tasking for all air assets in the Area of Responsibility 165 (AOR) (not just Air Force assets) and produces the joint Air Tasking Order (ATO) and Airspace Control 166 Order (ACO). As future net-centric capabilities intended to replace functionality that is currently 167 provided by TBMCS FL, C2AOS and C2IS will provide the C2 air battle planning and execution software 168 needed to support the JFACC in the future, net-enabled C2 environment. 169

b. Command and Control Air Operations Suite (C2AOS) and Command and Control Information Services 171 (C2IS) are companion programs intended to develop, field, and sustain modular net-centric Command 172 and Control (C2) applications and data management solutions for current and future C2 systems that are 173 not planned or delivered by systems, or programs, of record (SoR/PoR). ATOMS is part of the C2AOS 174 and C2IS programs. C2AOS and C2IS will address many of the functional requirements currently met by 175 the operationally-fielded TBMCS-FL. However, there are several key differences between the “as is” 176 TBMCS-FL program/architecture and the envisioned role/contribution of C2AOS and C2IS in the future 177

Page 7 of 48 DRAFT

C2 environment. Figure 1.3-1, below, shows the key differences between the current “as is” and the 178 future “to be” environments. 179

Figure 1.3-1. TBMCS “As Is” and C2AOS/C2IS “To Be” Environments 182

c. ATOMS, will focus on the replacement of TBMCS-FL Theater Air Planner (TAP) and Execution Manager 184 Replanner (EMR), Master Air Attack Planning Toolkit (MAAPTK), and associated databases. ATOMS will 185 provide foundational web services to create, read, update, and delete Air Mission data as defined by the 186 Air Operations Community of Interest (AO COI). For more information, please see the C2AOS/C2IS 187 Capability Definition Package (CDP), Attachment TBD to the Request for Proposal. 188

1.3 RISC2 Overview and Objectives 190

a. Currently, in TBMCS-FL, there is no central hub for requests. This means that it is often difficult for 191 operators to obtain any information about their requests after submitting them. Request Information 192 Service for Command and Control (RISC2) will correct this issue and enable better request tracking, 193 auditing, and handling. 194

b. The RISC2 effort will begin with a development effort for three service request types: 196

1. Air Support Requests (ASR) 197

2. TBMCS-FL Immediate Service Requests (ImmSR) 198

3. Airspace Coordinating Means Requests (ACMREQ) 199

TBMCS 1.1.3

Mission Capabilities

COP &

GCCS - I3

Capabilities

Infrastructure

Hardware

“TO BE” “AS IS”

C2AOS & C2IS

• GCCS - J COP

• GCCS - I3/JTT

• Others

Service - Provided Interoperable Infrastructure

Service - Provided Hardware

C2AOS & C2IS are software - only mission capabilities that:

Address JC2 CDD Requirements...cover a majority of NECC FEA&S

Requirements, and

Ride on Service-provided HW/SW Infrastructure

C2AOS & C2IS provide TBMCS v1.13-equivalent functionality NOT being planned/delivered by other Systems of Record

Page 8 of 48 DRAFT

2.0 General Instructions 203

a. This section provides general guidance for preparing proposals as well as specific instructions on the 204 format and content of the proposals. The Offeror's proposals must include all data and information 205 stated herein and must be submitted in accordance with these instructions. Non conformance with the 206 instructions provided may result in an unfavorable proposal evaluation. All proposed technical, 207 management, performance and schedule capabilities to meet the requirements shall be realistic and are 208 subject to verification by the Government. The proposal shall be compliant with the requirements as 209 stated in the Statement of Work (SOW), Statement of Objectives (SOO), Requirements Documents, 210 Contract Data Requirements List (CDRL), DD Form 254, and Model Contract. Non-conformance with the 211 instructions provided may result in an unfavorable proposal evaluation. All claimed technical, 212 management; performance and schedule capabilities to meet the requirements shall be realistic and are 213 subject to verification by the Government. 214

b. The Offeror's proposals shall consist of the written submittal. All information provided by the Offeror 216 (as long as it is consistent with the constraints of this RFP, e.g., page limitations) is subject to evaluation 217 as described in Section M. The Government will not award individual CLINs in the RFP to any one 218 contractor, but shall award ALL CLINs for each of the two development DOs RISC2 and ATOMS. 219 Proposals for a single CLIN, or group thereof, shall be rejected. 220

c. Offerors are advised that the proposal submitted should represent their best efforts and most 222 complete response to the solicitation. Cursory responses or responses which merely reiterate the SOO, 223 SOWs or other components of the Request for Proposals will be considered unacceptable. Evidence of 224 experience, capability, and qualifications, that clearly demonstrate and support the Offeror’s claims, is 225 essential. 226

d. The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for 228 substantiating the validity of stated claims. Offerors shall assume that the Government has no prior 229 knowledge of their facilities and experience and will base its evaluation on the information presented in 230 the Offeror’s proposal. 231

e. Elaborate brochure or documentation, binding, detailed artwork, or other embellishments are 233 unnecessary and are not desired. 234

f. The proposal validity period is specified in Section A of the model contract/solicitation. The Offeror 236 shall make a clear statement in Section A of the proposal documentation volume that the proposal is 237 valid for 270 days. 238

g. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one 240 copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy 241 extra copies of these unsuccessful proposals. 242

h. Offeror’s are instructed to insert their Taxpayer Identification Number (TIN) in Section G, clause 244 G015, titled “Implementation of Taxpayer Identification Number (APR 1998). 245

2.1 General Information 247

Page 9 of 48 DRAFT

2.1.1 Point of Contact 249

a. The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any 250 questions or concerns you may have to the PCO. Written requests for clarification may be sent to the 251 PCO at the address located in Section A of the model contract/solicitation or via email to the addresses 252 listed in the RFP cover letter. 253

2.1.2 Debriefings 255

a. The PCO will promptly notify Offerors of any decision to exclude them from the competitive range, 256 whereupon they may request and receive a debriefing in accordance with FAR 15.505. The PCO will 257 notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with 258 FAR 15.503(b). Offerors desiring a debriefing must make their request in accordance with the 259 requirements of FAR 15.505 or 15.506, as applicable. Post-award debriefings will be conducted in 260 accordance with AFFARS 5315.506. 261

2.1.3 Discrepancies 263

a. If an Offeror believes that the requirements in these instructions contain an error, omission, or are 264 otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale. 265 The Offeror is reminded that the Government reserves the right to award this effort based on the initial 266 proposal, as received, without discussion. 267

2.1.4 Electronic Reference Documents 269

a. All referenced documents for this solicitation can be found on an established electronic “Bidder’s 270 Library.” Instructions for obtaining access to the Bidder’s Library will be made available via the Federal 271 Business Opportunities (FedBizOpps) web site at https://www.fbo.gov/. Potential Offerors are 272 encouraged to subscribe for real-time e-mail notifications when information has been posted to the 273 websites for this solicitation. Please contact this office at 274 ESC.HSG.C2IS.C2AOS.Workflow@hanscom.af.mil if you are unable to locate any of the referenced 275 material. 276

2.1.5 Mandatory and Optional Proposal Submissions 278

a. The Government intends to award a multiple award ID/IQ contract (C2AD), plus a DO for a Post-279 Award Conference to each of the most highly-rated offerors (“the members of the C2AD Pool”). 280 Additionally, the Government intends immediately to award two software development DOs to one or 281 more members of the C2AD Pool: a RISC2 DO, and an ATOMS DO. To compete to become a member of 282 the C2AD Pool, an offeror must, at a minimum, submit proposals for both C2AD and the RISC2 DO. 283 Optionally, an offeror may also submit a proposal for the ATOMS DO. Although Offerors are encouraged 284 to submit a proposal for ATOMS, that proposal will not be the basis for the C2AD or RISC2 awards. 285 Although the Government encourages proposal submission on delivery orders solicited under the C2AD 286 contract in the future, there are no further obligatory proposal submissions required from members of 287 the C2AD Pool. The DO for the C2AD Post-Award Conference will satisfy the minimum order 288 requirement of that ID/IQ contract. A member of the C2AD Pool is not guaranteed a DO beyond the 289 initial one for the Post-Award Conference. 290

2.2 Organization/Number of Copies/Page Limits 292

a. The Offeror shall prepare the proposal as set forth in Table 2.1-1 Proposal Organization below. The 293 titles and contents of the volumes shall be as defined in this table, each of which shall be within the 294 required page limits and with the number of copies as specified in Table 2.1-1. The attachments 295 mailto:ESC.HSG.C2IS.C2AOS.Workflow@hanscom.af.mil

Page 10 of 48 DRAFT identified in the table shall be separately bound in three-ring, loose-leaf binders as necessary. The 296 Appendices in Section L support the development of the attachments below. Attachments to the 297 volumes do not count toward the volume page counts. The contents of each proposal volume are 298 described in the Instructions to Offerors paragraph as noted in Table 2.1-1. Each proposal volume shall 299 be unclassified. 300

Volume Title Page Limit Copies Applicability

I Master Table of Contents (MTOC)

Letter of Transmittal (LoT)

Executive Summary (ES)

Proposal Master Cross Reference

(PMCRM)

MTOC: No Page Limit

LoT: 2 Pages

ES: 5 Pages

PMCRM: No Page Limit

5 Paper and

1 CD

Mandatory

II.a Technical Proposal C2AD (Mandatory) 20 Pages 5 Paper and

1 CD

Mandatory

II.b Technical Proposal - RISC2 (Mandatory)

20 Pages 5 Paper and

1 CD

Mandatory

II.c Technical Proposal - ATOMS (Optional)

30 Pages 5 Paper and

1 CD

Optional

III Relevant Past Performance 4 Page Limit per Contract, 6 Contract Total Limit

5 Paper and

1 CD

Mandatory

IV.a Cost/Price – RISC2 (Mandatory) No Page Limit 3 Paper and

1 CD

Mandatory

IV.b Cost/Price – ATOMS (Optional) No Page Limit 3 Paper and

1 CD

Optional

V Contract Documentation Model Contract (Sections A-K)

Attachments to the Model Contract

No Page Limit (except CSOW supplements: RISC2 = 6 page limit, ATOMS = 10 page limit)

3 Paper and

1 CD

Mandatory

Table 2.1-1 – Proposal Organization 303

2.2.1 Page Limitations 305

a. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or 306 considered in the evaluation of the proposal and (for paper copies) will be returned to the Offeror as 307 soon as practical. Page limitations will be placed on responses to Evaluation Notices (EN). The specified 308 page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. When 309 both sides of a sheet of paper (including foldouts) display printed material, it shall be counted as two 310 pages. Each page shall be counted except the following: cover pages, tables of contents, tabs, glossaries, 311 resumes, tables and charts submitted as separate files. 312

Page 11 of 48 DRAFT

2.2.2 Cost or Pricing Information 314

a. All cost or pricing information shall be addressed ONLY in the Cost/Price proposal and Contract 315 Documentation Volumes. Cost trade-off information, work-hour estimates, and material kinds and 316 quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or 317 design and trade-off decisions. 318

2.2.3 Tables, Charts, Graphs and Figures 320

a. Legible tables, charts, graphs and figures should be used wherever practical to depict organizations, 321 systems and layout, implementation schedules, plans, etc. Large drawings, tables or charts shall be 322 separately provided and will not be included in the overall page count. Large drawings, tables or charts 323 shall be used only if necessary for clarity or legibility. For tables, charts, graphs and figures, the text shall 324 be no smaller than 10 point. These limitations shall apply to both electronic and paper proposals. 325

2.2.4 Cross Referencing 327

a. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its 328 contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. 329 Information required for proposal evaluation which is not found in its designated volume will be 330 assumed to have been omitted from the proposal. Cross Referencing within a proposal volume is 331 permitted where its use would conserve space without impairing clarity. The Offeror shall provide a 332 cross-reference matrix, table 3.2-1 , the corresponding proposal paragraph in that section which 333 addresses the referenced item. This matrix does not count against the page limitations for their 334 respective volumes. 335

2.2.5 Indexing 337

a. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within 338 that volume. Tab indexing shall be used to identify sections in all volumes. 339

2.2.6 Glossary of Abbreviations and Acronyms 341

a. Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for 342 each. Glossaries do not count against the page limitations for their respective volumes. 343

2.3 Page Size and Format 345

a. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced. Except for the 346 reproduced sections of the solicitation document, the text size shall be no less than 12 point. Use at 347 least 1-inch margins on all sides of each page. Pages shall be numbered sequentially by volume. Legible 348 tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and 349 layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall 350 not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as one 351 page, unless printed on both sides in which case they will count as two pages. Foldout pages may only 352 be used for large tables, charts, graphs, diagrams, and schematics; not for pages of text. For tables, 353 charts, graphs and figures, the text shall be no smaller than 10-point. These limitations shall apply to 354 both electronic and hard copy proposals. These page format restrictions shall also apply to responses to 355 ENs. Page limitations apply to electronic proposals, as well. If there are discrepancies in page counts 356 and/or content between hard copy and electronic volumes, the hard copy version shall be used for 357 evaluation (e.g., if the hard copy version of a volume is 51 pages, and the electronic version of the same 358 volume is 48 pages, the Government will treat the volume as having 51 pages). 359

Page 12 of 48 DRAFT

2.4 Binding and Labeling 361

a. Each volume of the proposal shall be separately bound in a three-ring loose leaf binder, permitting 362 the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, 363 clearly marked as to volume number, title, copy number, solicitation identification and the Offeror’s 364 name. The same identifying data should be placed on the spine of each binder. All unclassified 365 document binders shall have a color other than blue, red, and orange. Be sure to apply all appropriate 366 markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and 367 Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal 368 Information and Source Selection Information. 369

2.5 Electronic Offers 371

a. The Offeror shall submit Volumes I-V in electronic format, using read-only CDs or DVDs. Each volume 372 shall be in a different directory on the media, with the exception of the cost volume which shall be 373 located on a separate CD. The content and page size of electronic copies must be identical to the hard 374 copies. In the event of a discrepancy between the electronic copies and hard copies, the hard copies 375 submittal shall be used for evaluation. For electronic copies, indicate on each CD or DVD the volume 376 number and title. Use separate files to permit rapid location of all portions, including subfactors, 377 exhibits, annexes, and attachments, if any. If files are compressed, the necessary decompression 378 program must be included. The electronic copies of the proposal shall be submitted in a format readable 379 by Microsoft (MS) Word 2007, MS Excel 2007, MS-Project 2007, and MS-Power Point 2007, or PDF as 380 applicable. Large drawings, charts and tables or other documentation not readily included in the above 381 formats shall be supplied in PDF format. All data files and electronic media delivered to the Government 382 must be reviewed to ensure that they are virus-free. In the event hardcopy and softcopy content 383 conflict, hardcopies will take precedence over softcopies. 384

2.6 Distribution 386

a. The original proposal shall be so identified as such. The total hard copies (including the original) and 387 soft copy quantities of all volumes listed in Table 2.1-1 shall be addressed and delivered to the following: 388

ESC/AQ 390

104 Barksdale St 391 Bldg 1520 392 Hanscom AFB, MA 01731 393 ATTN: Mr. Richard Hartford 395 Contracting Officer 396 781-225-9473 397

b. All proposal material must be received no later than 2:00 p.m. Eastern Time (ET) on the required 399 submission date (block 3 of SF 1707). If proposals are to be hand-delivered, Offerors are cautioned that 400 they will need to process through the Hanscom AFB visitors entrance in order to gain access to the base 401 and should allow appropriate time. 402

c. An additional copy of each volume shall be distributed by the proposal due date to the Offeror's 404 cognizant Administrative Contracting Officer (ACO). Be sure to advise the Administrative Contracting 405 Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the 406 proposal is "For Official Use Only" and "Source Selection Information--See FAR 3.104". 407

Page 13 of 48 DRAFT

3.0 Volume I – Executive Summary 409

a. In the Executive Summary volume, the Offeror shall provide the following information: 410

3.1 Executive Summary 412

a. A signed letter of transmittal or executive cover letter shall be included within your proposal 413 submission. This cover letter will not be counted against the page limitations of the Executive Summary 414 volume. This letter shall not exceed two (2) pages in length. The Offeror shall provide a concise narrative 415 of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding 416 cost/price. The content of Volume I is for information only and will not be evaluated for the purpose of 417 contract award. The format of this volume is at the discretion of the Offeror, but should specifically 418 indicate where material may be found for each major element of the evaluation as defined in Section M 419 of this RFP. The salient features should tie in with Section M evaluation factors/subfactors. Any 420 summary material presented here shall not be considered as meeting the requirements for any portions 421 of other volumes of the proposal. Within this volume, the Offeror shall state that its proposal is valid for 422 270 days. 423

b. The Executive Summary shall also identify all subcontractors and joint venture partners for the 425 overall ID/IQ effort, as well as each DO proposed to in response to this RFP. A brief description of their 426 planned roles in the effort shall be included. A list of all participating divisions and locations (prime, 427 subcontractors, and joint venture partners) shall be furnished indicating whether teaming agreements 428 have been executed or not. An organization chart of the proposed team shall be provided to show all 429 key personnel (Offeror, subcontractors, joint venture partners, etc.) and to depict how the Offeror’s 430 team fits within the company. The organization chart shall start at the level of the Offeror’s Chief 431 Executive Officer and clearly identify the entire chain of command specifying the name, title, and 432 division name and location. The reporting lines and names, title, and division name and location of 433 personnel responsible for quality assurance shall also be included. Phone numbers for points of contact 434 including the Division’s Vice President (VP), program manager, program manager alternate, and 435 contracting officer shall be provided. The contact list should also identify those personnel authorized to 436 negotiate on behalf of their company. Furthermore, the list should indicate the person to contact in the 437 event the Offeror is awarded a contract (provide, at a minimum, contact’s title, phone number, fax 438 number, email address and mailing address). 439

3.1.1 Teaming Arrangements 441

a. The Government, in general, encourages teaming arrangements between prime and sub-contractors 442 for the ID/IQ contracts and individual DOs. For the ID/IQ awards and each subsequent DO, proposals will 443 be evaluated on the basis of the entire proposed team rather than just the capability of the prime 444 contractor. 445

3.2 Table of Contents 447

a. Include a Master Table of Contents for the entire proposal. 448

b. Complete a Master Cross Reference Matrix as shown in the following table: 450

Page 14 of 48 DRAFT

C2AD SOW RISC2 SOO ATOMS SOO Section L Section M Written Proposal (Volume & Section)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.1(a) 2.2.1(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.1(b) 2.2.1(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.2(a) 2.2.2(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.2(b) 2.2.2(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.3(a) 2.2.3(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.3(b) 2.2.3(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.4(a) 2.2.4(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.4(b) 2.2.4(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.5(a) 2.2.5(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.5(b) 2.2.5(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.1.5(c) 2.2.5(iii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.1(a) 2.2.6(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.1(b) 2.2.6(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.1(c) 2.2.6(iii)

Page 15 of 48 DRAFT

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.1(d) 2.2.6(iv)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.1(e) 2.2.6(v)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.2(a) 2.2.7(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.2(b) 2.2.7(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.2(c) 2.2.7(iii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.3(a) 2.2.8(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.3(b) 2.2.8(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.3(c) 2.2.8(iii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.2.3(d) 2.2.8(iv)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.1(a) 3.4.3(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.1(b) 3.4.3(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.1(c) 3.4.3(iii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.1(d) 3.4.3(iv)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.2(a) 3.4.4(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.2(b) 3.4.4(ii)

Page 16 of 48 DRAFT

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.3(a) 3.4.5(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.3(b) 3.4.5(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.3(c) 3.4.5(iii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.3(d) 3.4.5(iv)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.3(e) 3.4.5(v)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.4(a) 3.4.6(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.4(b) 3.4.6(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.4(c) 3.4.6(iii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.5(a) 3.4.7(i)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.5(b) 3.4.7(ii)

[TO BE

COMPLETED IN

FINAL RFP]

4.2.3.5(c) 3.4.7(iii)

Table 3.2-1 – Master Cross Reference Matrix 452

4.0 Volume II –Technical Proposals 454

4.1 General 456

a. Volume II Technical Proposals must be specific and complete. The Technical Volume will provide the 457 Government visibility into the Offeror’s proposed approach and understanding of the proposed effort. 458 Legibility, clarity and coherence are very important. Your responses will be evaluated against the 459 technical subfactors for each separate item: C2AD, RISC2 and ATOMS as defined in paragraphs 4.2.1, 460

4.2.2 and 4.2.3 and associated sub-paragraphs. Using the instructions provided below, provide as 461 specifically as possible the actual methodology you would use for accomplishing/satisfying these 462 subfactors. By your proposal submission, you are representing that your firm will perform all the 463 requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the 464 requirements specified in the solicitation. 465

Page 17 of 48 DRAFT

4.2 Format and Specific Content 467

4.2.1 Volume II.a Organization: C2AD Contract 469

a. All Offerors must submit a technical proposal for the ID/IQ contract. In the C2AD Written Technical 470 Proposal, address your proposed approach for meeting the C2AD SOW tasks represented by each 471 technical subfactor. In addition, identify any overall risks in the scope of the C2AD areas in terms of 472 technical/performance, cost, and/or schedule. Describe the impact of each identified risk in terms of its 473 potential to interfere with or prevent the successful accomplishment of other contract requirements 474 which might arise on individual DOs, whether or not those requirements are identified as elements. 475 Suggest realistic, generalized risk management/mitigation for identified risks that will eliminate or 476 reduce risk. Explain why the risk handling should be considered acceptable. The Written Technical 477 Proposal shall be organized according to the following general outline: 478

a. Table of Contents 480

b. List of Table and Drawings 481

c. Glossary 482

d. Cross Reference Matrix 483 (Note: Items a-d are applicable to all Volume II binders) 484

e. Subfactor 1: Domain Knowledge 485

f. Subfactor 2: Software Development 486

g. Subfactor 3: Sustainment 487

h. Subfactor 4: Training 488

i. Subfactor 5: Test and Information Assurance 489

4.2.1.1 Subfactor 1 – Domain Knowledge 491

a. The Offeror shall describe their approach to leverage existing domain knowledge in the areas 492 indicated in the C2AD SOW. The specific SOW paragraphs can be found in the Cross-Reference Matrix, 493 Table 3.2-1. Examples of C2AD domains are: 494

1. Theater of Operation-Level Command and Control 495

2. Air Battle Planning 496

3. Search and Rescue Mission Tasking/Monitoring 497

4. Wing-level Command and Control 498

b. The Offeror shall describe their knowledge of specific challenges and circumstances unique to the 500 fielding of systems to the Air Force and Joint military environments as well as an understanding of the 501 risks in fielding to those environments and an approach to mitigating inherent risks of fielding to those 502 environments. 503

4.2.1.2 Subfactor 2 – Software Development 504

a. The Offeror shall describe their approach to 1) create new interoperable software systems, 2) 505 leverage existing interoperable software systems and 3) maintain currency with evolving open 506 communication standards meeting the C2AD SOW objectives; the approach should highlight developing 507 platform agnostic software both on the applicable host systems and communicating with other systems 508 on different platforms. 509

Page 18 of 48 DRAFT

b. The Offeror shall describe their software development capabilities, especially in agile environments 511 emphasizing short-turn, iterative development cycles; the software development capabilities should 512 include adherence to industry best-practices and leverage knowledge of current Information Technology 513 products. 514

4.2.1.3 Subfactor 3 – Sustainment 516

a. The Offeror shall describe their approach for sustaining 1) Command and Control systems developed 517 by the Offeror and 2) Command and Control systems developed by another vendor. The approach shall 518 describe specific processes for maintaining configuration management/data management and ensuring 519 currency with Information Assurance requirements. 520

b. The Offeror shall describe their approaches for minimizing software lifecycle sustainment costs from 522 development to fielding and maintenance with an emphasis on continuous process improvements. 523

4.2.1.4 Subfactor 4 – Training 525

a. The Offeror shall demonstrate their ability to train users of newly developed systems as well as 526 provide refresher training for updated systems. 527

b. The Offeror shall describe approaches to continuously improve training efficiency by reaching more 529 end-users with better quality training products at reduced costs. 530

4.2.1.5 Subfactor 5 – Test and Information Assurance 532

a. The Offeror shall summarize their test and evaluation processes for ensuring successful, iterative 533 testing via minimizing all categories of deficiency reports. In addition, the Offeror shall describe their 534 overall approach for testing software products, tracking test findings/deficiencies and correcting issues – 535 especially in an agile software development environment. 536

b. The Offeror shall describe their approach for developing systems which adhere to DoD Information 538 Assurance requirements. The approach should outline how the Offeror will structure their development 539 program to achieve the applicable DoD Information Assurance Certification and Accreditation Process 540 (DIACAP) products for a given effort such as: Interim Authority to Test (IATT), Authority to Operate (ATO) 541 and Authority to Connect (ATC). 542

c. The Offeror shall describe their techniques to continuously improve internal test processes in order to 544 increase product quality, and reduce development time. The techniques should include the use of 545 automated test tools. 546

4.2.2 Volume II.b Organization: RISC2 548

a. All Offerors must submit a technical proposal for RISC2. In the RISC2 Written Technical Proposal, 549 address your proposed approach for meeting the RISC2 SOO tasks represented by each technical 550 subfactor. In addition, identify the risks in your proposed approach in terms of technical/performance, 551 cost, and/or schedule. Describe the impact of each identified risk in terms of its potential to interfere 552 with or prevent the successful accomplishment of other contract requirements (for example: SOW or 553 specification requirements), whether or not those requirements are identified as elements. Suggest 554 realistic risk management/mitigation for identified risks that will eliminate or reduce risk. Explain why 555

Page 19 of 48 DRAFT the risk handling should be considered acceptable. The Written Technical Proposal shall be organized 556 according to the following general outline: 557

a. Table of Contents 559

b. List of Table and Drawings 560

c. Glossary 561

d. Cross Reference Matrix 562

e. Subfactor 1: Technical Approach 563

f. Subfactor 2: Demonstration and Test 564

g. Subfactor 3: Program Management 565

4.2.2.1 Subfactor 1 – Technical Approach 567

a. The Offeror shall describe their approach to meeting all requirements described in the RISC2 SOO and 568

RISC2 SRD. 569

b. The Offeror shall describe their approach to ensure the RISC2 product maintains interoperability with 571 TBMCS-FL interfaces, as defined in the RISC2 SOO and TRD, as well as other external Mission Request 572 systems. 573

c. The Offeror shall describe their understanding of the risks associated with developing the RISC2 575 capability to include mitigation strategies to prevent or preclude adverse cost, schedule or performance 576 impacts. 577

d. The Offeror shall describe their approach to ensuring support for future request types beyond the 579 three (3) described in the RISC2 SOO with no interruption to operations. 580

e. The Offeror shall describe their approach to ensuring the RISC2 product is in compliance with the Air 582 Operations Community of Interest (AO COI) standards and can maintain compliance with future versions 583 of the AO COI standards with minimal rework. 584

4.2.2.2 Subfactor 2– Integration, Test and Information Assurance 586

a. The Offeror shall describe their approach to demonstrating that the RISC2 software meets the 587 requirements found in the RISC2 SOO in a Government approved operationally relevant test facility, 588 with multiple types of requestors of missions, proposed by the Offeror. 589

b. The offeror shall demonstrate their thorough understanding of requirements and specific challenges 591 to incorporation of Information Assurance requirements described in the RISC2 SOO and Information 592 Assurance Technical Requirements Document 593

c. The offeror shall propose a product test approach that ensures: 1) delivery timelines are met, and 2) 595 deficiencies are minimized, enabling positive fielding decisions 596

4.2.2.3 Subfactor 3 – Program Management 598

a. The Offeror shall provide a comprehensive CSOW, CWBS and CWBS Dictionary to cover all tasks 599 associated with meeting the RISC2 SOO requirements at the lowest level managed, but at least to a 600

Page 20 of 48 DRAFT minimum of Level 3. The Offeror shall also provide a complete and comprehensive Integrated Master 601 Plan (IMP) and Integrated Master Schedule (IMS) to cover all tasks as described in the RISC2 SOO as well 602 as risk mitigation plans for significant risks identified. Being complete and comprehensive includes, but is 603 not limited to, addressing all objectives described in the RISC2 SOO and incorporation of all required 604 CDRL items 605

b. The Offeror shall identify all proposed data rights in technical data and computer software 607 development at private expense with emphasis on the use of non-proprietary solution. 608

c. The Offeror shall describe their plan to manage the program to ensure Government visibility into the 610 project schedule, performance, and risk, as well as encouraging joint (Contractor/Government) problem 611 solving. 612

d. The Offeror shall provide a Small Business Sub-Contracting Plan which describes plans to involve 614 Small Business firms in the DO execution. 615

4.2.3 Volume II.c Organization: ATOMS 617

a. Submitting a technical proposal for ATOMS is optional. In the ATOMS Written Technical Proposal, 618 address your proposed approach for meeting the ATOMS SOO tasks represented by each technical 619 subfactor. In addition, identify the risks in your proposed approach in terms of technical/performance, 620 cost, and/or schedule. Describe the impact of each identified risk in terms of its potential to interfere 621 with or prevent the successful accomplishment of other contract requirements (for example: SOW or 622 specification requirements), whether or not those requirements are identified as elements. Suggest 623 realistic risk management/mitigation for identified risks that will eliminate or reduce risk. Explain why 624 the risk handling should be considered acceptable. The Written Technical Proposal shall be organized 625 according to the following general outline: 626

a. Table of Contents 628

b. List of Table and Drawings 629

c. Glossary 630

d. Cross Reference Matrix 631

e. Subfactor 1: Technical Approach: Functional Requirements 632

f. Subfactor 2: Technical Approach: Architectural Tenets 633

g. Subfactor 3: Integration, Test and Information Assurance 634

h. Subfactor 4: Transition, Fielding and Sustainment 635

i. Subfactor 5: Program Management 636

4.2.3.1 Subfactor 1 – Technical Approach: Functional Requirements 638

a. The Offeror shall describe their plan to meet the functional requirements described in the ATOMS 639 Functional Requirements Document. 640

b. The Offeror shall demonstrate domain knowledge of air battle planning for geographical theaters of 642 operation. 643

c. The Offeror shall describe how the proposed solution will incorporate an existing capability which 645 fulfills at least 50% of the functional requirements described in the ATOMS SOO and…