Section_L_-_Instructions_to_Offerors.pdf

J-Tech II

FA8240-15-R-7218-0001

Section L

J-Tech II Page 1 of 36

SECTION L – INSTRUCTIONS TO OFFERORS (ITO)

1.0 PROGRAM STRUCTURE AND OBJECTIVES

1.1 The J-Tech II Enterprise requires engineering and technical expertise in support of the following participating Western Test Ranges and organizations: 412 Test Wing (TW), Edwards Air Force Base (AFB), California; Nevada Test and Training Range (NTTR), Nellis AFB, NV (includes the Space Test and Training Range (STTR), Schriever AFB, Colorado); Utah Test and Training Range (UTTR), Hill AFB, Utah; and the Naval Air Warfare Center Weapons Division (NAWCWD) Ranges (includes the land and sea ranges at China Lake and Point Mugu, California).

The organizations within the J-Tech II Enterprise are delineated as follows:

• Annex 1: 412 TW

• Annex 2: NTTR

• Annex 3: UTTR

• Annex 4: NAWCWD Ranges

1.1.1 THE FOLLOWING IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.

The Government has developed an estimate of Phase I workload for FY17, inclusive of projected hours and labor types by functional category. This estimate is provided for informational purposes to assist Offerors in quantifying the work identified in the PWSs (see Attachment L-1, Government Estimate). The Phase 2 portion of the RFP could represent an increase of up to 100 percent of like requirements over Phase 1, dependent upon mission demands and associated funding availability.

1.1.2 Offerors are advised the technical and cost/price data submitted to the Government in response to this solicitation may be released to non-government advisors for review and analysis. The non-government advisor support will be provided by Kepler Research, Inc. (Kepler). Kepler is restricted by the Organizational Conflict of Interest provision of its contract from participating as a contractor, subcontractor, or consultant on the J-Tech II program other than on a noncompetitive basis under a prime contract with the Government. A "Certificate of Non-Disclosure" will be executed by each individual from this contractor prior to review of the Technical and Cost volumes of the proposal. The Offeror agrees, by the submission of a proposal, to have it reviewed by Kepler for the purpose of providing technical and cost analysis advisory support.

J-Tech II Page 2 of 36

1.2 TWO-PHASED ACQUISITION APPROACH GENERAL INSTRUCTIONS

1.2.1 The Offeror's proposal (unless otherwise specified means both the Phase 1 proposal and the Phase 2 proposal) must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The Offeror’s proposal shall be compliant with the requirements as stated in the Performance Work Statements (PWS), Contract Data Requirements List (CDRL), and solicitation. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

1.2.2 The Offeror’s proposal shall be clear and concise and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The Offeror’s proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet or exceed the requirements. The Offeror shall assume that the Government has no prior knowledge of their capabilities and experience. The Government will base its evaluation on the information presented in the Offeror's proposal.

1.2.3 Elaborate brochures or documentation, bindings, detailed art work, or other embellishments are unnecessary and are not desired.

1.2.4 The Phase 1 proposal validity period is specified in Section A of the solicitation.

The Offeror shall make a clear statement in Section A of the contract documentation volume that the proposal will be valid for a period of not less than 180 calendar days from receipt of Phase 1 offers. This period may be extended upon the mutual agreement of the Offeror and the Contracting Officer.

1.2.5 The Phase 2 proposal acceptance period will be specified in Section A of the amended solicitation. The Offeror shall make a clear statement in Section A of the contract documentation volume that the proposal is valid for a period of not less than 300 calendar days from receipt of Phase 2 offers. This period may be extended upon the mutual agreement of the Offeror and the Contracting Officer.

1.2.6 In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful Offeror’s proposals.

1.2.7 The Contracting Officer, Mr. Kevin Hugie, is the sole point of contact for this acquisition. Address any solicitation questions or concerns to kevin.hugie@us.af.mil.

1.2.8 Reference documents for this solicitation are available on the Federal Business Opportunities (FBO) website at https://www.fbo.gov, Bidders Library locations as shown

J-Tech II Page 3 of 36 in Table 1.1. Potential Offerors are encouraged to subscribe to the FBO website for real-time e-mail notifications.

Table 1.1 Bidders Library

Location Point of Contact Telephone Annex 1 – Edwards AFB online @ fbo.gov N/A Library posted on FBO

Annex 2 – Nellis AFB Bldg. 625

Primary: Major Eric Staub Alternate: Mr. Mark Kurth

(702)653-5543 DSN 348-5543

(702)653-4502 DSN 348-4502

Annex 3 – Hill AFB Bldg. 1A

Primary: Mr. Frank Marks Alternate: Ms. Marykay Hertzke

(801) 777-0818 DSN 777-0818

(801) 777-5959 DSN 586-5959

Annex 4 – China Lake Bldg. 70150

Primary: Michelle Kaumeyer Alternate: N/A

(760) 939-9069

1.2.9 Indexing. Each volume of the Offeror’s proposal shall contain a detailed table of contents to delineate the paragraphs within that volume. Tab indexing shall be used to identify sections.

1.2.10 Acronyms and Abbreviations. Each volume shall contain an acronym and abbreviation list. Acronym and abbreviation lists do not count against the page limitations for their respective volumes.

1.2.11 Binding and Labeling. Each volume of the proposal shall be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each binder, clearly marked as to volume number, title, copy number, solicitation identification, and the Offeror's name.

The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including security markings and those prescribed in accordance with FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

1.2.12 Page Limitations. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal.

Unless stated otherwise in section L, each page shall be counted except the following:

cover pages, tables of contents, acronym and abbreviation list, tabs, and the Cross Reference Matrix (CRM). The Government may place page limitations on responses to

J-Tech II Page 4 of 36

Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

1.2.13 Page Size and Format. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts.

Pages shall be typed with line spacing set to 1.15. Except for the reproduced sections of the solicitation document and headers and footers, the text size shall be no less than 12-point Arial font. Retain the formatting of reproduced sections of this solicitation document. Headers and footers may be no less than 8-point Arial font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and 1-inch side margins. Pages shall be numbered sequentially by volume. Where the original copy of the proposal includes information not required in the paper copies of the proposal, the Offeror’s paper copies should retain page number consistency with original copy. These page size and format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

1.2.14 Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size.

Tables, charts, graphs, and figures shall be typed with line spacing set to 1.15. Foldout pages shall fold entirely within the volume, and count as a single page (i.e., information shall only be on one side of the page). Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 8 point. These limitations shall apply to both electronic and hard copy proposals.

1.2.15 Electronic Offers. The content and page size of electronic copies must be identical to the hard copies. The Offeror shall use virus-free CD/DVD-Rs for its proposals. The Offeror shall not use CD/DVD-RW. Each electronic copy of a proposal submission shall be on a single CD/DVD. Each volume shall be in a separate directory of the CD/DVD. Use separate files to permit rapid location of all portions including exhibits and attachments, if any. Files shall not be compressed or otherwise altered from their native application’s format. The electronic copies of the proposal shall be submitted in an unlocked format readable and searchable by Adobe Acrobat (Version

9.0 or later), Microsoft (MS) Office Word 2010, MS Office Excel 2010, MS Office Project 2010, and MS Office Power Point 2010, as applicable. In the event there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

J-Tech II Page 5 of 36

1.2.16 If an Offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the Contracting Officer in writing with supporting rationale as well as the remedies the Offeror is asking the Contracting Officer to consider as related to the omission or error.

1.2.17 Exchanges of source selection information between Government and Offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 and 3.104” in the Subject line.

Otherwise, source selection information will be transmitted via other means as appropriate.

1.2.18 Debriefings. The Contracting Officer will notify the Offeror of any decision to exclude them from the competition as soon as practicable whereupon; it may request and receive a debriefing in accordance with FAR 15.505. An Offeror that is not included in Phase 2 may only request and receive a debrief after the Phase 1 Source Selection Authority Determination and cannot delay the debriefing until after award. Any Offeror included in Phase 2 and removed from the competition during Phase 2 may receive a pre-award debriefing or it may choose to wait until after the Phase 2 source selection decision to receive a post-award debriefing. Any Offeror is entitled to no more than one debriefing and must make its request in accordance with the requirements of FAR

15.505 or 15.506, as applicable.

1.2.19 The remainder of Section L is organized in two main segments: 1) Phase 1 Instructions and 2) Phase 2 Instructions.

J-Tech II Page 7 of 36 a classified volume will be appropriately marked according to current DoD classified marking guidance.

2.1.3 Distribution. The “original” Phase 1 proposal shall be identified. Phase 1 proposals shall be addressed to the Contracting Officer and mailed or hand carried to:

AFTC/PZS

Attn: Mr. Kevin Hugie 6082 Fir Avenue

Bldg. 1232 Hill AFB, UT 84056-5820

2.1.4 Phase 1 Pre-Proposal Conference

2.1.4.1 Purpose. The purpose of the Phase 1 Pre-proposal Conference is to provide Industry with answers to RFP questions. Offeror attendance and participation in the Phase 1 Pre-proposal conference is not mandatory. The requirements of the solicitation take precedence over any verbal pronouncements made during the Phase 1 Pre-proposal Conference.

2.1.4.2 Place, Time, Date, and Other Information

2.1.4.2.1 Place: Hill AFB, UT, Bldg.1232

2.1.4.2.2 Time: 0830 – 1100

2.1.4.2.3 Date: 11 August 2015

2.1.4.2.4 RSVP. The Offeror shall send its RSVP to kevin.hugie@us.af.mil by COB 5 August 2015. The Offeror, to include its teammates and subcontractors, may only bring a maximum of six (6) individuals to the Phase 1 Pre-proposal Conference. The Offeror is to provide the full, legal name and driver’s license information (State and number) for all attendees. Please note whether or not the Offeror requires a sponsor to access Hill

AFB, UT.

2.1.4.2.5 RFP Questions. RFP questions must be submitted to the Contracting Officer, kevin.hugie@us.af.mil, by COB 6 August 2015.

2.2 Volume I - Organizational and Team Structure

2.2.1 Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between

J-Tech II Page 8 of 36 conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine which past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a roadmap describing all such changes in the organization of the Offeror’s company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts the Offeror identifies for past performance evaluation/performance confidence assessment. Since the Government may consider past performance information provided by other sources as well as that provided by the Offeror, the roadmap should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.

2.2.2 Team Structure. The Offeror shall provide a structure depicting organizational lines of authority for teaming partners and subcontractors to include a narrative description of each company’s roles and responsibilities as it pertains to the J-Tech II Enterprise-level PWS and Annex-level PWSs for J-Tech II Functional Areas. In the event of a joint venture, diagram the partners that formed the joint venture.

2.3 Volume I - PWS Functional Area Information (Phase 1A)

2.3.1 The Offeror shall submit no more than 20 contracts/projects. Only contracts/projects meeting the definition of recency defined in Section M paragraph

2.1.1.1 will be evaluated. The 20 contract/project submissions may be from any combination of the prime contractor, joint venture partners/members, or subcontractors/teammates.

2.3.2 Each contract/project submitted shall include a completed Phase 1A Past Performance Information Sheet (Section L-2 Attachment) and the corresponding contract/project requirements document(s) in their native format(s) (e.g., Statement of Work (SOW), Contractor SOW, PWS, Contractor PWS, or Technical Requirements Document (TRD)) see Section M paragraph 2.1.1.2. The Offeror shall only include one

(1) corresponding version of the requirements document(s) per contract/project submission. The corresponding contract/project requirements documents for Phase 1A need only be submitted in the original (one hard copy) and electronic submissions provided the electronic document is searchable with Adobe and MS Word functionality (CTRL F). Additionally, the Offeror shall complete the Phase 1A Functional Area Worksheet (tab) in the Phase 1 Past Performance Excel Workbook (Section L-3 Attachment). See Section M paragraph 2.2.

J-Tech II Page 9 of 36

2.4 Volume I - Past Performance Point Screening Breakdown (Phase 1B)

2.4.1 The Offeror shall not submit more than five (5) relevant contracts/projects as defined in Section M paragraph 2.1.1.2. Only contracts/projects meeting the definition of recency defined in Section M paragraph 2.1.1.1will be evaluated. The five (5) contract/project submissions must include at least two (2) submissions from the prime contractor and/or joint venture partners/members, and one (1) submission from a small business joint venture partner/member or small business subcontractor/teammate. The remaining two (2) may be from the prime contractor or any combination of joint venture partners/members or subcontractors/teammates. Additionally, each contract/project submission shall include a minimum of four (4) J-Tech II Enterprise-level PWS Functional Areas. If the contract/project submission includes fewer than four (4) J-Tech II Enterprise-level PWS Functional Areas, the contract/project submission will be rated with zero (0) points (zero (0) for relevancy and zero (0) for quality of performance).

2.4.2 Each contract/project submission shall include a completed Phase 1B Past Performance Information Sheet (Section L-4 Attachment) and the corresponding contract/project requirements document(s) in their native format(s) (e.g., SOW, Contractor SOW, PWS, Contractor PWS, or TRD). The Offeror shall only include one

(1) corresponding version of the requirements document(s) per contract/project submission. The corresponding contract/project requirements documents for Phase 1B need only be submitted in the original (one hard copy) and electronic submissions provided the electronic document is searchable with Adobe and MS Word functionality (CTRL F). Additionally, for each contract/project submission, the Offeror shall submit, if available, the most recent Contract Performance Assessment Reports (CPARS) (up to five CPARS) in their native format(s). In the absence of CPARS, a Past Performance Questionnaire (PPQ) (Section L-5 Attachment) should be completed for each of the five

(5) most recent years of performance. A PPQ may cover multiple years. A year is defined as twelve (12) continuous months of performance. A CPAR or PPQ covering a period greater than 12 months but less than 24 will be counted as one year of performance. For those contracts that have a CPARS covering fewer than twelve (12) continuous months of performance, the Offeror should submit a PPQ for a full twelve

(12) month PoP instead. The Government will not consider CPARS or PPQs of less than twelve months of continuous performance. PPQs and CPARS should not overlap.

Provide a list of questionnaire recipients to include POCs and phone numbers.

2.4.2.1 Example: A submitted contract/project has a Period of Performance (PoP) from 1 Oct 2006 to 30 Sep 2012. The Offeror would submit CPARS, if available, for the first twelve (12) month PoP, the second twelve (12) month PoP, the third twelve (12) month PoP, the fourth twelve (12) month PoP, and the fifth twelve (12) month PoP. If a

J-Tech II Page 10 of 36

CPARS is not available for any twelve (12) month PoP, the Offeror would submit a PPQ for that period. If a PPQ is not completed by contact/project requirements holder, that year of performance would be considered neutral past performance and not count for or against the Offeror (see Section M Example 2.2.3.2.5).

2.4.3 The Offeror shall submit a self-rated Relevancy Submissions Worksheet (tab) and Relevancy Worksheet (tab) in the Phase 1 Past Performance Excel Workbook (Section L-3 Attachment). The Offeror shall not complete any of the “PP Scoring” Worksheet tabs.

2.4.4 Consent Letters. Because a prime contractor is a private party, the Government will need a Consent Letter (Section L-6 Attachment) before disclosing subcontractor/teaming/joint venture partner past performance information to the prime during exchanges. Therefore, the Offeror shall submit a consent letter executed by each teaming/joint venture partner and subcontractor authorizing release of past performance information, including adverse information, to the Offeror, so the Offeror can respond to such information.

2.4.5 Client Authorization Letters. For each submitted contract/project for a commercial customer, the Offeror shall submit a Client Authorization Letter (Section L-7 Attachment) authorizing release to the Government of requested information on the Offeror’s performance.

2.5 Volume II – Contract Documentation

2.5.1 Solicitation Representations and Certifications. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file.

2.5.1.1 Section A – Solicitation/Model Contract. The Offeror shall complete and submit, in its entirety, the “Offeror” portion of the Standard Form (SF) 33. An official having the authority to contractually bind the Offeror shall sign the SF 33 IAW FAR

4.102. The "original" SF 33 shall be clearly marked and shall be provided without any punched holes.

2.5.1.2 Section B – Supplies or Services and Cost/Prices. Do not submit Cost/Prices in Phase 1.

2.5.1.3 Section H – Do not submit section H fill-ins in Phase1.

2.5.1.4 Section K – Representations, Certifications, and other Statements of the Offeror. The Offeror shall complete and submit representations, certifications, J-Tech II Page 11 of 36 acknowledgments, and statements; or indicate if information is contained in the System for Award Management (SAM).

2.5.2 Phase 1 Responsibility Information

2.5.2.1 Organizational Conflict of Interest (OCI). The Offeror shall provide an OCI Mitigation Plan In Accordance With (IAW) H001. If an Offeror does not provide an acceptable OCI Mitigation Plan, the Offeror shall be determined non-responsible.

2.5.2.2 Special Standards Responsibility Information (FAR 9.104-2) For Phase 1

2.5.2.2.1 Foreign Ownership. The Offeror and its subcontractors/teammates/partners shall not be foreign owned. The Offeror shall provide evidence that it and its subcontractors/teammates/partners are not foreign owned. If an Offeror does not provide evidence that it and its subcontractors/teammates/partners are not foreign owned, the Offeror shall be determined non-responsible.

2.5.2.2.2 Security

2.5.2.2.2.1 Personnel Security. The Phase 2 Offerors (the Offeror and its subcontractors/teammates/partners) will require access to classified data to participate in Phase 2. Accordingly, the Phase 2 Offerors shall be required to have the appropriate security clearances. The personnel security clearance level required is a Top Secret (TS), current within the past five (5) years. Additionally, personnel may need to undergo separate access adjudication procedures beyond basic security clearance requirements.

2.5.2.2.2.1.1 The Offeror shall obtain required personnel security clearances for all proposal preparation team members who are expected to require access to Phase 2 classified information (maximum of 20 personnel per Offeror). The number of proposal preparation team members allowed to be accessed into the Phase 2 requirements shall be justified by the Offeror and may be adjusted (never to exceed 20 personnel), as necessary, throughout the acquisition process. The Offeror’s justification shall provide the same information, as specified in I. – V. below, for each individual requiring access and specify completely the reasons each person needs to have access to the Phase 2 classified information. Personnel adjustments shall be submitted to the Contracting Officer for consideration; requests for personnel adjustments will not be made for the convenience of the Offeror and may take months to process. The Offeror shall also identify one of the personnel as the J-Tech II security point of contact. Applications for TS clearances shall be submitted and processed through the Offeror’s cognizant Defense Security Service (DSS). Contact DSS for lead times. The acquisition will not be delayed awaiting Offeror security clearances. Additionally, if Offeror personnel

J-Tech II Page 12 of 36 answer “Yes” to one or more of the Pre-Screening Questionnaire (Section L-11 Attachment) questions, they may be subject to additional security screening and may not be eligible for Phase 2 participation. The original copy of Attachment L-11 requires a wet signature.

2.5.2.2.2.1.2 The Offeror shall provide the following personnel security information, marked appropriately, for each of the Offeror Phase 2 proposal preparation team members (up to 20):

I. Full name, title and Social Security Number of person meeting the above security clearance requirement

II. Type of security clearance and investigation III. Date security clearance was issued and updated IV. Agency which granted the clearance V. Completed Pre-Screening Questionnaire (Section L-11 Attachment)

2.5.2.2.2.2 Physical Security

2.5.2.2.2.2.1 Facility Clearance. A Top Secret facility clearance (including Top Secret level of safeguarding) is required for Phase 2 eligibility. If an Offeror does not provide evidence that it has a facility clearance, or that it has submitted and is awaiting a DSS Facility Clearance Letter (FCL), the Offeror shall be determined non-responsible. The Offeror will not receive the Phase 2 RFP until it has an FCL. The acquisition will not be delayed awaiting Offeror FCL. Information regarding the FCL can be found at:

http://www.dss.mil/isp/fac clear/fac clear.html. The Offeror shall provide the following information:

I. Type of facility clearance II. Date facility clearance issued

III. Name, address, zip code and Commercial and Government Entity (CAGE) code IV. Name, address, zip code, and phone number of cognizant DSS security representative & office

2.5.2.2.2.2.2 Top Secret Proposal Facility. Offerors shall have a facility ready to accredit for Top Secret information in accordance with Joint Air Force Army and Navy (JAFAN) 6/9. The Offeror shall provide a completed JAFAN 6/9 (Section L-12 Attachment) Fixed Facility Accreditation Checklist. If an Offeror does not provide evidence that it has a facility ready to accredit for Top Secret information, the Offeror shall be determined non-responsible.

J-Tech II Page 13 of 36

2.5.3 Exceptions to the Solicitation Requirements. The Offeror is required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. The Offeror shall clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph or specific part of the solicitation to which the exception is taken. The Offeror shall provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. The Offeror shall provide this information in the format and content of Table 2.2. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

Table 2.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph Requirement/ Portion Rationale

PWS, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

J-Tech II Page 15 of 36

3.1.2 Cost or Pricing Related Data. The Offeror shall address all cost or pricing data ONLY in the Cost/Price and Contract Documentation Volumes, unless otherwise specified in the Technical Volume ITO.

3.1.3 Cross-Referencing

3.1.3.1 The Offeror shall write each volume on a stand-alone basis.

3.1.3.2 Cross Reference Matrix (CRM). The Offeror shall complete and submit a Proposal CRM, which ensures the Section L instructions are addressed and easily accessible to the evaluators. The CRM shall be included in Offeror’s proposed Technical Volume (see L-3.3.1.3) but will not be included in the page count. The CRM must provide a single integrated index for the entire proposal. This index shall cross reference Section L, Section M, and the Offeror’s proposal by page and paragraph number.

3.1.4 Phase 2 Classified Information. Phase 2 proposals will contain classified information. Classified information in the Offeror’s response shall be included in the appropriate volume where it naturally occurs. The Offeror shall not divide any volume, factor, or portion thereof into separate classified and unclassified proposals. The Offeror shall mark all pages and paragraphs of the proposal according to current DoD classified marking guidance. The Offeror shall clearly reference the highest classification within the volume on the cover page. The Offeror shall mark any media (e.g. CD, DVD, etc.) with the highest classification of the contents per current DoD classified marking guidance.

3.1.5 Distribution. The Offeror shall conspicuously identify the "original" Phase 2 proposal and shall address Phase 2 proposals to the Contracting Officer, with appropriate markings, and hand carry to:

AFTC/PZS

Attn: Mr. Kevin Hugie 6082 Fir Avenue Bldg. 1232 Hill AFB, UT 84056-5820

3.1.6 Phase 2 Pre-Proposal Conference

3.1.6.1 A Phase 2 Pre-proposal Conference will be scheduled. An invitation to the Phase 2 Pre-proposal Conference will be provided with further instructions to the Phase 2 Offerors. The Phase 2 Pre-proposal Conference will not be a repeat of Industry Day Range Tours, but will focus on the Phase 2 requirements. The Phase 2 Pre-proposal

J-Tech II Page 16 of 36

Conference is provided to assist Phase 2 Offerors in familiarizing themselves with the Phase 2 requirements and to assist Offerors in obtaining information to prepare their Phase 2 proposals. Offeror attendance and participation in the Phase 2 Pre-proposal conference is mandatory. The requirements of the solicitation take precedence over any verbal pronouncements made during the Phase 2 Pre-proposal Conference.

3.1.6.2 The Offeror’s Pre-proposal conference participants are limited to those individuals who are approved by the Government as eligible for Phase 2 participation.

To receive and transport classified documents, recipient must be deemed eligible for Phase 2 participation, authorized to act as courier, and adhere to appropriate DoD security directives and security classification guide(s).

3.2 Volume I – Executive Summary, Table of Contents, and an Acronym and Abbreviation List

3.2.1 Executive Summary. The Executive Summary of the entire proposal should be concise, address the significant risks, and highlight any key or unique features, while excluding cost/price information. The salient features should correlate to the Section M evaluation factors/subfactors.

3.2.2 Table of Contents. Include a table of contents for this volume.

3.2.3 Acronym and Abbreviations. The volume shall include an acronyms and abbreviations list.

3.3 Volume I – Technical Volume

3.3.1 General

3.3.1.1 Offeror responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, explain the actual methodology the Offeror would use for accomplishing / satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By submitting a proposal, the Offeror is representing that it will perform all the requirements specified in the solicitation. The Offeror shall not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.3.1.2 In this volume, explain the Offeror’s technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor.

3.3.1.3 Volume Organization. The Technical volume shall be organized according to the following general outline.

J-Tech II Page 17 of 36

Cross Reference Matrix Executive Summary Table of Contents List of Tables and Drawings Acronym and Abbreviation List Subfactor A: Technical Expertise

- Technical Expertise Approach

- Technical Expertise Scenario Subfactor B: Program Management

- Program Management Approach

- Program Management Scenario 1

- Program Management Scenario 2 Subfactor C: Recruit and Retain a Qualified Workforce Subfactor D: Innovations and Efficiencies

3.3.1.4 Technical Risk. Throughout the Offeror’s responses to the Technical Subfactors A, B, C, and D, the Offeror should explain the Technical Risk associated with those aspects of its proposal it considers to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. The Offeror should classify each risk in accordance with Section M Table 8, Technical Risk Rating. The Offeror should provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. The Offeror should describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of contract requirements. The Offeror should propose a realistic "work-around" or risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level. The Offeror should identify and classify any new risks introduced by such risk mitigation.

3.3.1.5 Cost Savings or Improvements. Throughout the Offeror’s responses to Technical Subfactors A, B, C, and D, the Offeror should identify and explain how areas within its subfactor responses would reasonably result in cost savings or improvements (e.g., qualitative, quantitative) that benefit the Government.

3.3.2 Technical Subfactors. There are four (4) technical subfactors.

3.3.2.1 SUBFACTOR A: TECHNICAL EXPERTISE. This subfactor contains two components. The first component is a narrative explanation of the Offeror’s Technical Expertise Approach and the second component is the application of the Subfactor A Technical Expertise Approach to the Technical Expertise Scenario.

J-Tech II Page 18 of 36

3.3.2.1.1 Technical Expertise Approach. The Offeror shall explain its Technical Expertise Approach. Within the Technical Expertise Approach, the Offeror shall address the following elements:

3.3.2.1.1.1 Explain its approach to operate, maintain, and sustain the following subset of J-Tech II Functional Areas IAW J-Tech II Enterprise and Annex-level PWS Sections:

3.2, Threat Systems, 3.6, Instrumentation Systems, 3.7, Signal Collection/ Monitoring/Measuring, and 3.8, Telemetry Systems.

3.3.2.1.1.2 Explain its approach to institute Systems Engineering (SE) across the operations, maintenance, and sustainment core technical functions IAW J-Tech II Enterprise-level PWS Section 3.16.

3.3.2.1.2 Technical Expertise Scenario

3.3.2.1.2.1 Technical Expertise Scenario Information, Guidance, Instructions, and Assumptions

a) The Offeror shall explain the rationale for successful scenario completion to include, but not limited to processes, activities, products, operations, maintenance, sustainment, challenges, manpower requirements, and skillsets.

b) The Offeror shall list and fully explain assumptions used in the scenario response.

c) Throughout the scenario response, identify any areas where a significant risk is deemed present. Explain how the Offeror will deal with these risks by suggesting a feasible work- around or risk mitigations that will eliminate or reduce the risk to an acceptable level.

d) The Offeror is already on contract and in contract year three.

e) In responding to the scenario, the Offeror shall ensure uninterrupted PWS requirement compliance for a normalized operations tempo.

f) The Foreign Country referenced in the scenario is a nation that will remain generic and unnamed. The Foreign Country's relationship with the US is non-adversarial and standard commercial travel with a US passport is authorized.

g) Mission data classification ranges from Unclassified to Secret.

h) The Government will provide overseas transport of the scenario threat systems.

i) Live missile handling is not an Offeror responsibility.

3.3.2.1.2.2 Technical Expertise Scenario

a) The US Government is in the process of acquiring two SA-8 Gecko systems available for acquisition from the Foreign Country. At this time, no one in the

J-Tech II Page 19 of 36

US has inspected either system or verified their condition.

b) As reported by the Foreign Country vendor:

i. The first SA-8 is an Osa-1T digitally upgraded by the Tetraedr Company.

1. All 9K33M-1t Osa-1T electrical systems, missile, and vehicle upgrades were completed per Tetraedr's standard 9K33M3 OSA- AKM upgrade program.

2. It was upgraded in 2010 but never fielded. After the upgraded system was delivered to the Foreign Country, it was stored indoors and never started or moved.

ii. The second SA-8 is an SA-8B Gecko Mod-1 OSA-AKM analog version that is still employed throughout the world.

1. The system is reported as complete with six (6) missiles that were rendered inert (no warhead, no propulsion) when put in storage.

2. The system was part of the Foreign Country's Air Defense capability from 1988-2006.

3. The system was taken out of inventory and stored in 2008 when it was deemed unserviceable and uneconomical to repair.

4. Most of the original Russian documentation is missing.

3.3.2.1.2.2.1 Explain how the Offeror will determine the status and capabilities of each system and what will make up the Offeror's “buy” or “don’t buy” recommendation to the Government. Describe its processes and techniques that would comprise the “buy” or “don’t buy” recommendation.

3.3.2.1.2.2.2 Assume the Government decided to acquire both systems.

3.3.2.1.2.2.3 The Offeror must site both systems on the NAWCWD China Lake Range:

a) The Offeror shall explain optimal system siting factors and considerations, with supporting rationale and constraints, for both systems.

b) Assume the Offeror’s siting recommendation was accepted and resulted in the following:

i) The SA-8 Osa-1T site was recently in use and contains a suitable pad, commercial power and an outbuilding with DS-3 and multiple T-1 connectivity.

ii) The SA-8 Mod-1 OSA-AKM site is bare earth.

iii) Both sites require integration into the secure mission and maintenance communication system, secure and non-secure phones, secure network connectivity to the enterprise WAN, the enterprise mission data network, and cueing capabilities.

J-Tech II Page 20 of 36

c) The Offeror shall explain the processes, activities, challenges, and mitigations required to prepare the systems and sites for permanent system occupancy.

3.3.2.1.2.2.4 Explain how the Offeror will instrument the SA-8’s and integrate the instrumented data with range systems.

3.3.2.1.2.2.5 Explain how the Offeror will characterize and verify functionality of these systems.

3.3.2.1.2.2.6 The Offeror is tasked to operate, maintain, and sustain both systems to include depot level maintenance. Explain the Offeror's performance of all three (3) J-Tech II Enterprise PWS Core Technical Functions with the following conditions and constraints:

a) The normal mission schedule for the test article is six (6) four (4) hour missions per week.

b) Infrequently, there will be no mission activity for up to two months or very heavy daily activity for up to three weeks.

c) Systems are expected to be operational (exceptions are normal PMI and maintenance activities) for 15 years.

d) Systems must perform consistently. Their performance must be characterized both pre and post mission. System characterization data must be recorded and available for analysis.

e) Spare parts cannot be counted on and must be reverse engineered and manufactured when unavailable.

f) Systems must be deployable with a minimum 90-day notice to any of the J- Tech II ranges. Systems will:

i) Be transportable. There is no requirement to maintain a system in a mobile configuration. Systems will never be required to move or operate under their own power.

ii) Be capable of operating from an unimproved location with limited support.

iii) Autonomously collect and store all instrumented data. Be capable of providing instrumented data to a deployed location's infrastructure.

3.3.2.1.2.2.7 Mission Event

a) The Offeror is expected to fully explain the processes, activities, deliverables, challenges, and mitigations for the mission event.

b) Explain what the Government can reasonably expect to learn from this event and how the data will be used to determine the results.

J-Tech II Page 21 of 36

c) Briefly explain other beneficial tests the J-Tech II ranges should conduct with these SA-8 systems and describe the benefit to the warfighter. To clarify roles, a Government Project Officer will be on hand with decision making authority, however, the Offeror's long term continuity, experience, test conduct background, and knowledge are relied upon heavily for guidance and mission success at all levels.

d) In addition to the range systems explicitly called out within the mission event, the Offeror should also identify any other range systems necessary to fulfill mission test objectives and manage mission safety.

3.3.2.1.2.2.7.1 Mission Event. The Offeror shall explain how it will support a standard flying mission on China Lake.

a) Mission plan: Two CV-22 Ospreys will fly electronic warfare missions against both SA-8 systems. The CV-22s are instrumented with telemetry, radar beacons, and GPS pods. The CV-22s are equipped with Radar Warning Receivers (RWR) and self-protection jammers.

b) Mission objectives: Complete the following at several predetermined ranges, speeds and altitudes:

i) Determine the capability of both SA-8 systems to detect, track, and simulate firing upon the CV-22s whenever possible in jamming and non-jamming environments.

ii) Determine the detection ranges of both SA-8 systems in jamming and non-jamming environments.

iii) Test requirements for the CV-22 RWR capabilities are to ensure it correctly:

(1) Identifies the threat.

(2) Identifies the mode the threat system is in and when it changes modes.

(3) Geolocates the threat.

(4) Executes jamming on the threat.

(5) Identifies the threat's response to jamming.

c) The Offeror shall explain how it will manage all mission planning and direct mission resources, including:

i) Build flight profiles to best meet mission test objectives.

ii) Determine which range systems will be needed to ensure test objectives are met and collected data is sufficient to determine test results.

iii) Ensure all mission systems are operating normally before, during, and after the mission.

iv) Ensure aircraft telemetry, threat system, and other mission data are collected and available for post mission analysis.

v) Ensure all mission participant data (to include instrumentation, audio, video, J-Tech II Page 22 of 36 and telemetry) are made securely available simultaneously, in real time, to the enterprise mission data infrastructure of the western test ranges located within Annex 1 – 4’s span of control.

vi) Direct mission aircraft to their assigned profiles, ensuring they are on condition, and make real time changes based upon events such as failed profile runs due to threat system malfunction or aircraft not on condition.

vii) Manage range airspace, mission safety, mission security and all Mission Control Room activities.

viii) Coordinate activities of all mission participants.

ix) Monitor Control Room Situational Awareness.

x) Ensure operational status and availability of all range systems and perform maintenance callouts as needed.

xi) Identify and explain critical communication requirements.

xii) Process and analyze data post mission.

3.3.2.2 SUBFACTOR B: PROGRAM MANAGEMENT. This subfactor contains two components. The first component is a narrative explanation of the Offeror’s Program Management Approach and the second component is the application of the Subfactor B Program Management Approach to the Program Management Scenarios.

3.3.2.2.1 Program Management Approach. The Offeror shall explain its Program Management Approach. Within the Program Management Approach, the Offeror shall address the following elements:

3.3.2.2.1.1 Provide a detailed top to bottom organizational structure for the entire J- Tech II Enterprise and Annex workforce to include interrelationships between these entities.

3.3.2.2.1.1.1 The organizational structure shall be provided for the Enterprise and each Annex.

3.3.2.2.1.1.2 The organizational structure shall include the number of personnel, skill mix, and labor hours for J-Tech II Enterprise-level PWS Section 2.0 and Annex-level PWSs Section 2.0.

3.3.2.2.1.1.3 The Offeror shall include a descriptive narrative of the organizational structure with supporting rationale for the number of personnel, skill mix, and labor hours for J-Tech II Enterprise-level PWS Section 2.0 and Annex-level PWSs Section 2.0.

J-Tech II Page 23 of 36

3.3.2.2.1.1.4 The organizational structure shall include the number of personnel, skill mix, and labor hours for each PWS Functional Area (PWS Sections 3.2 thru 3.17) and explain deviations, if any, from the Government Estimate.

3.3.2.2.1.1.5 The organizational structure shall include the number of personnel, skill mix, and labor hours by Core Technical Function (Operate, Maintain, Sustain -- where used in the PWS).

3.3.2.2.1.2 Provide a detailed transition plan IAW J-Tech II Enterprise-level PWS Section 4.1.

3.3.2.2.1.3 Explain how the program manager will maintain visibility, quality, and control over all levels of the program IAW J-Tech II Enterprise-level PWS Section 2.2.

3.3.2.2.1.4 Identify not more than 12 Key Leadership/Management Positions, as required in H003, based on the Offeror’s proposed approach. For each Key Position identified, the Offeror shall provide: 1) the rationale for the position being designated as key, 2) the roles and responsibilities of the position, and 3) the minimum qualifications (education and experience) for each position. Do not submit resumes.

3.3.2.2.1.4.1 Identify individuals that meet the qualifications identified in Section L paragraph 3.3.2.2.1.4 to fill exactly six (6) of its proposed Key Management/Leadership Positions. For each individual identified, the Offeror shall submit a letter of commitment from the individual stating that he/she will perform in the assigned position for at least the transition period and first two (2) years of contract performance. Do not submit resumes.

3.3.2.2.1.5 Describe the Offeror’s approach for utilization of employees while they wait for security clearances to be processed.

3.3.2.2.1.6 Address how the Offeror will manage personnel changeovers (planned and unplanned) to ensure no interruption in contract execution.

3.3.2.2.1.7 Explain the process/procedure to award and manage subcontracted efforts IAW J-Tech II Enterprise-level PWS paragraph 2.1.2.

3.3.2.2.1.8 Small Business Participation. Explain the process and procedure for meeting the mandatory small business participation requirement of 25 percent of total dollars obligated.

3.3.2.2.2 Program Management Scenarios

J-Tech II Page 24 of 36

3.3.2.2.2.1 Program Management Scenario One: In March 2018, the Government informs the Offeror that the F-35 Joint Strike Fighter program is completing the initial development testing at Annex 1 and will be reducing its support requirements to a sustainment level expected to continue for the foreseeable future. The sustainment level is a reduction in capacity of Annex 1 real-time mission support requirements by 30 percent, instrumentation support by 40 percent, and Electronic Warfare support by 10 percent. Additionally, assume a proportional loss of funding for each reduction area.

The reduction must be complete by the beginning of Government Fiscal Year 2019 (1 Oct 2018).

3.3.2.2.2.1.1 The Offeror shall explain how it will manage this reduction in scale with no loss in the ability to execute all of the functions in the PWS across all of the Annexes.

3.3.2.2.2.2 Program Management Scenario Two: Assume the Government has accepted the Offeror’s proposed solution to Program Management Scenario One.

Therefore, the Offeror’s Program Management Scenario One proposed solution is in effect. In October of 2020, the Government informs the Offeror that Annex 1 has been selected to conduct the Long Range Strike (LRS) developmental test program. The LRS program will begin build up in the summer of 2021 with the first test article arriving in October of 2022. The LRS program will require an increase in real-time mission support and instrumentation support 25 percent above the nominal Annex 1 levels requiring an additional 100 test engineers spread across all of the test disciplines in support of the LRS. Additionally, assume a proportional increase in funding for each support area. Flight tests are planned to start launching from Annex 1 in March of 2023.

Flight tests will utilize the ranges and test resources of 412 TW, UTTR, and NAWCWD Ranges while being monitored by the 412 TW mission control rooms. A single mission may utilize one, some, or all of the aforementioned ranges with the 412 TW always maintaining mission monitoring capability. Ranges will be required to operate using networked telemetry to support mission monitoring, real time data analysis, mission safety and mission control from the 412 TW.

3.3.2.2.2.2.1 The Offeror shall explain how it will manage this increase in scale with no degradation in the ability to execute all of the functions in the J-Tech II Enterprise-level and Annex-level PWSs.

3.3.2.3 SUBFACTOR C: RECRUIT AND RETAIN A QUALIFIED WORKFORCE. The Offeror shall explain its Recruit and Retain a Qualified…