Section_L_-_Amendment_001.pdf

UNCLASSIFIED

Protected Tactical Enterprise Service (PTES)

Instructions, Conditions, and Notices to Offerors

SECTION L

FA8808-17-R-0006

29 March 2018

THIS PAGE INTENTIONALLY LEFT BLANK

TABLE OF CONTENTS

1. GENERAL INTRODUCTIONS/INFORMATION - Page 5

2. PROPOSAL SUBMITTAL AND INQUIRIES – Page 7

3. PROPOSAL PREPARATION AND INSTRUCTIONS – Page 8

3.1. BINDING, LABELING, AND TABLE OF CONTENTS – Page 10

3.2. TECHNICAL ATTACHMENTS – Page 11

3.3. ORAL PRESENTATION – Page 12

4. PROPOSAL CONTENT – Page 13

4.1. VOLUME I – EXECUTIVE SUMMARY – Page 13

4.2. VOLUME II – TECHNICAL – FACTOR 1 – Page 14

4.3. VOLUME III – COST/PRICE – FACTOR 2 – Page 20

SECTION 1 – INTRODUCTORY SECTION – Page 22

SECTION 2 – PRINTED COST/PRICE ELEMENT SUMMARIES FOR

COST CLINS (CLINS 0001-0003, 0005-0008) – Page 23

SECTION 3 – DISCUSSION OF COST ELEMENTS FOR COST CLINS

(CLINS 0001-0003, 0005-0008) – Page 28

SECTION 4 – DISCUSSION OF BUSINESS SYSTEMS, GOVERNMENT

PROPERTY REQUIREMENTS, AND OFFEROR UNIQUE APPROACHES

– Page 34

4.4 VOLUME IV – SMALL BUSINESS PARTICIPATION – FACTOR 3 – page 35

4.5 VOLUME V – CONTRACT DOCUMENTATION – Page 37

5. ATTACHMENTS AND EXHIBITS TO THE MODEL CONTRACT – Page 39

6. APPENDICES TO VOLUME V – Page 45

TABLES

Table 1 – Non Government Advisors – Page 6

Table 2 – Number and Type of Copies Required – Page 9

Table 3 – Cross Reference Matrix (Sample) – Page 14

Table 4 – PTES Key Event Schedule – Page 20

Table 5 – Cost/Price Methodology – Page 22

Table 6 – Subcontract and Teaming – Page 23

Table 7 – Total Proposed Price – Page 24

Table 8 – Then Year Funding Requirements – Page 39

Table 9 – Participating Companies/Divisions – Page 45

1.0 GENERAL INSTRUCTIONS/INFORMATION

a. The Offeror’s proposal shall include all data and information requested in Section L and shall be submitted in accordance with these instructions. In developing the proposal the Offeror shall comply with all the requirements contained in the Request for Proposal (solicitation), including all solicitation attachments and appendices, schedule event constraints in Table 4, and the funding profile in Table 8.

b. The Government intends to award without discussions. Offerors are encouraged to present their best technical proposal and prices in their initial proposal submission.

c. The submission of the documentation specified below will constitute the Offeror’s acceptance of the terms and conditions of the solicitation, and all attachments to this solicitation. A written notice of award or acceptance of an offer by the Government, mailed or otherwise furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

d. The Offeror’s proposal shall be clear, concise, and include sufficient detail for effected evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government’s requirements, but rather provide rationale to address how the Offeror intends to meet these requirements. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience. The Government will make its evaluation based solely on the information presented in the Offeror’s proposal.

e. Do not submit elaborate brochures or documentation, binding, detailed artwork, or other embellishments.

f. Proposals that do not address requirements within the SOW or meet program objectives will be classified as an alternate proposal. Alternate proposals will not be considered.

g. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being determined ineligible for award.

h. If an Offeror believes that the requirements in these instructions lack clarity or contain an error, omission, discrepancy, or are 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. Such notices shall be received no later than ten (10) calendar days following release of the solicitation. The Government may choose not to consider any notices after this time. Government responses will be placed in the Bidder’s Library and/or posted on the Federal Business Opportunities website at www.fbo.gov, as appropriate.

i. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. All other proposal copies will be destroyed.

j. The Government reserves the right to cancel this solicitation, either before or after the closing date for receipt of proposals. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an Offeror for any costs.

k. The Procuring Contracting Officer (PCO) will promptly notify an Offeror of any decision to exclude it from the competitive range; whereupon, the Offeror may request and receive a debriefing in accordance with FAR 15.505. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506.

l. Non-Government Advisors. The release of proposal information to Non-Government advisors will be subject to the controls outlined in paragraph 1.4.6.2 of the DoD Source Selection Procedures issued 01 Apr 2016. The Non-Government Advisors the Government intends to use are listed below in Table 1. Non-Government Advisors will not serve as evaluators to determine ratings of Offerors’ proposals. The individuals participating in the review and analysis of proposals have signed individual nondisclosure agreements with the Government which strictly prohibit any release or disclosure of information outside of the source selection team. The Offeror may object to the release of its proposal information to any non-Government advisor. Any such objection must be submitted no later than ten (10) calendar days after solicitation release, and transmitted by email or mail via a written notification to the PCO. The contracting officer shall make a determination whether the non-Governmental advisor shall be permitted to participate in the source selection. The contracting officer shall inform the objecting Offeror of the final determination, and, if the use of non-Government advisors has been changed, shall inform all Offerors of the change. The Offeror shall also expressly state in Volume I, Executive Summary, whether or not it concurs with the release of its proposal information to the following non-Government advisors. Failure to do so may result in elimination from the competition.

Table 1 – Non Government Advisors Company Name

LinQuest Corporation

Act One

MCR Federal, LLC

Alpha Omega Group

The Aerospace Corporation (FFRDC)

Massachusetts Institute of Technology Lincoln Laboratory (MIT LL) (FFRDC)

BTAS

Parsons

TAC Consulting

Millennium Engineering and Integration

m. All unclassified documents for this solicitation are available through either the Federal Business Opportunities (FedBizOpps) website at www.fbo.gov or the PTES Bidder’s Library (LiveLink). Classified documents will be provided to interested parties upon request to the lead Contract Specialist, 1Lt Evan Miller, via email at evan.miller.15@us.af.mil.

n. A Government Reference Architecture (GRA) for Software Environments slide deck has been provided in the Bidder’s Library (Livelink). The Offeror shall develop their proposal in accordance with the information contained in the GRA.

2.0 PROPOSAL SUBMITTAL AND INQUIRIES

a. The Procurement Contracting Officer (PCO), Ms. Eva Rae Hoskins, is the sole point of contact for this acquisition. All questions or concerns must be directed to the PCO via email at eva.hoskins.1@us.af.mil. Courtesy copy the lead Contract Specialist, 1Lt Evan Miller, evan.miller.15@us.af.mil, and the alternate Contract Specialist, Capt Alejandro Sena, alejandro.sena.2@us.af.mil, on all email correspondence with the PCO. Questions regarding the solicitation must be in writing and emailed to the PCO (with a courtesy copy) no later than fifteen (15) calendar days prior to the close of the solicitation due date. The Government may choose not to accept any questions after this time. You may confirm receipt of your question by requesting a return email. A copy of the returned email, along with associated metadata, shall be proof of receipt of the question. All answers to questions and any amendments to this solicitation will be posted to the Federal Business Opportunities (FedBizOpps) website at www.fbo.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

b. All communications between the Government and Offerors will be controlled by the PCO.

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 & 3.104” in the Subject line. In order to facilitate the sending and receiving of encrypted emails, Offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption.

To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). If email cannot be sent and received encrypted, then an alternative transmission approach is to fax the information. The fax number is available on request from the Lead Contract Specialist, 1Lt Evan Miller, or alternate Contract Specialist, Capt Alejandro Sena. The Offeror is responsible for ensuring information is appropriately protected regardless of transmission method.

c. Proposals are due no later than 5:00 P.M., local Los Angeles, CA time on 29 May 2018.

Proposals may be hand carried, mailed, or delivered via courier service to the physical address below so they are received by the contracting office by the due date and time.

For shipments using the United States Postal Service (USPS):

Space and Missiles System Center (SMC) – MILSATCOM/PKJ ATTN: Ms. Eva Rae Hoskins, Procurement Contracting Officer 2310 El Segundo Blvd Aerospace Visitor Center #1 El Segundo CA 90245

For shipments using Couriers/Physical Address (Fed Ex, DHL, and UPS):

Space and Missiles System Center (SMC) – MILSATCOM/PKJ ATTN: Ms. Eva Rae Hoskins, Procurement Contracting Officer 483 N. Aviation Blvd El Segundo, CA 90245

d. Prior to delivering hand carried proposals, the Offeror shall confirm Government representatives will be present to accept the delivery.

e. Proposals received after the specified date and time shall be handled in accordance with FAR 15.208. Delivery of proposals before the proposal due date shall be coordinated with the PCO.

f. The Offeror’s proposal shall be Unclassified. No Classified information will be accepted in response to this RFP.

g. The proposal acceptance period of 270 calendar days is specified in Section A, Block 12 of the model contract/solicitation. The Offeror shall make a clear statement in Volume V, Section A of the proposal that the offer is valid for 270 calendar days from the proposal due date.

3.0 PROPOSAL PREPARATION AND INSTRUCTIONS

a. A complete proposal will consist of five (5) separate volumes all of which shall be within the required page limits specified in Table 2, Number and Type of Copies Required.

b. Offeror’s proposal shall consist of five (5) separate volumes:

Volume I – Executive Summary Volume II – Technical Volume III – Cost/Price Volume IV – Small Business Participation Volume V – Contract Documentation (Includes all Exhibits, Attachments, and Appendices)

1395812781A Highlight

1395812781A Highlight

c. Offerors shall submit two (2) hard copies of their proposal listed in Table 2, below. In addition to submitting hard copies of the proposals, two (2) electronic copies of the proposal shall be delivered on CD-ROMs. The CDs shall be labeled with the Offeror’s name, the submission date, the volume number(s) and title(s) contained therein and the solicitation number. All CDs shall be placed in plastic sleeves in one binder separate from the other proposal volumes.

Table 2 - Number and Type of Copies Required

VOL TITLE

NO.

HARD

COPIES

NO. OF

ELECTRONIC

COPIES

(CD ROM)

PAGE LIMIT

(MAX)

I Executive Summary 2 2 3

Cross Reference Matrix N/A

II

Technical 2 2

40 – aside from page limitations listed below (these pages shall address

Subfactors 2 and 3 only)

Attachment T1: Agile Process Demonstration - Visual Aids

Attachment T2:

Software Architecture Document

Attachment T2a: Rights in Data Discussion

Attachment T3:

Integrated Master Schedule

N/A

III Cost/Price 2 2 N/A

IV Small Business Participation 2 2 4

V

Contract Documentation 2 2 N/A - aside from page limitations listed below

Attachment 8:

Small Business Subcontracting Plan

Attachment 10:

Key Program Personnel

Appendix D: Key Program Personnel Resumes

Note: Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal and shall not be evaluated if found elsewhere in the proposal.

d. The electronic copies of the proposal shall be in a format readable by Adobe Acrobat 8.0 (with ”Select” and “Copy” enabled to allow for text and graphics transfer), Microsoft (MS) Word 2010, MS Excel 2010, Crystal Ball, ACE-IT, MS Project 2010, Palisade @Risk, SEER-SEM 8.1 or MS PowerPoint 2010, as appropriate. Hypertext links may be used to facilitate navigation within the document. Use separate files to permit rapid location of all portions, including exhibits, annexes, and attachments, if any. Each volume shall be in a different CD-ROM directory. If files are compressed, the necessary decompression program (e.g., WINZIP) must be included. The proposal shall include the native file (e.g., .DOC(x)) and .PDF versions of all textual material.

e. In the event of a conflict between the hardcopy and electronic copy, the hardcopy will take precedence over the electronic copy. In the event of a conflict between the native file and .PDF versions, the native file version will take precedence over the .PDF version.

f. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will not be returned to the Offeror. Page limits do not include: covers sheets for volumes, tables of contents, glossary of abbreviations and acronyms, indices, title pages, and section dividers/tables if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. Pages marked “This page intentionally left blank” will not be counted. Pages will be counted if they contain any other information, i.e., diagrams, extraneous data, etc. A cross-reference matrix shall not be counted in the page limits.

When both sides of a sheet display printed material, it shall be counted as two pages. All pages shall be numbered.

3.1. BINDING, LABELING, AND TABLE OF CONTENTS

a. Each hardcopy of the proposal shall be separately bound in a D-3-ring loose-leaf binder, which shall permit the volume to lie flat when open. Do not overload binders and do not use staples. Each binder shall have a cover, spine, and title page clearly marked with the Offeror’s name, volume number, binder identifier, copy number, and solicitation identification. Offerors shall apply all appropriate markings including those prescribed in accordance with FAR 52.215-1, Instructions to Offerors-Competitive Acquisition, and 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

b. Each volume shall contain a detailed table of contents that will not count against the page count identified in Table 2. Tab indexing shall be used to identify sections.

c. The Offeror shall use a common paragraph numbering system among the tasking statements in the SOW, Work Breakdown Structure (WBS), Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) consistent with the SOW numbering scheme.

d. Page size (for text sections of the proposal) shall be 8.5 x 11 inches, not including foldouts.

Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point Times New Roman font printed in black ink on white paper; black and white requirement does not apply to graphics, photos, etc. Use at least 1-inch margins on the top and bottom and 3/4 inch side margins. Pages shall be typed with 1.5 line spacing.

Pages shall be numbered sequentially by volume. These limitations shall apply to both electronic and hard copy proposals.

e. Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, and plans. These displays shall be clear, legible, and shall not be printed on paper greater than 11 x 17 inches in size.

Individual tables, charts, graphs, and figures are permitted to exceed one page in length when necessary. Foldout pages shall fold entirely within the volume, and count as two pages for each side used. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics, but not for pages of text. Text inside graphics, matrices, spreadsheets, focus boxes, and tables shall use single-line spacing and shall be no less than 8-point Times New Roman font. (Exception: the Cost Volume (Volume III) encourages the use of Contractor formats. Contractor font used in Volume III shall be no smaller than 9-point; for text inside graphics, 8-point text shall be acceptable where necessary.)

f. Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other parts of the proposal. Each response to each sub-factor shall be self-contained. No cross-referencing between sub-factor responses is permitted.

3.2. TECHNICAL ATTACHMENTS

a. Attachments T1 through T3 (reference Section L, paragraph 4.2.d.) will be used to evaluate the Technical Subfactors and proposed approach. Except as otherwise indicated in the solicitation, an Offeror’s format is acceptable.

b. Use of second tier references in any Technical Attachment is not acceptable. For example, statements such as the following are unacceptable: “Specific processes at our subcontractor will be in accordance with Subcontractor Process Plan XYX” or “This process will be done using our corporate process XYZ”. Instead, the Offeror shall extract the applicable process information from those documents and include it in the Technical Attachments and the IMP narratives, when appropriate.

c. Offerors shall use separate binders for individual Volume II Technical Attachments.

Offerors shall identify the ‘T’ Attachment numbers contained in the binder in addition to the information required in Section L, paragraph 3.1.a., above.

d. To the greatest extent possible, Volume II shall cross reference to applicable T Attachments or Volume V Attachments. The electronic copy of Volume II shall contain hyperlinks to all such cross-references. All information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. The Offeror shall use a common paragraph numbering and outline system for the volumes and attachments of the proposal.

3.3. ORAL PRESENTATION

a. Each Offeror shall conduct an Oral Presentation consisting of an Agile Process Scenario Demonstration using the Visual Aids submitted as Attachment T1, outlined in Section L, paragraph 4.2.d.a).

b. Scheduling/Location. The Government shall identify the facility, date, and time for the demonstration following receipt of proposals, but no later than six (6) calendar days prior to the demonstration. Offerors may submit a written request to visit the facility NLT the proposal due date via email to the lead Contract specialist, 1Lt Evan Miller, evan.miller.15@us.af.mil. It is the Government’s intent to conduct all Oral Presentations within 30 days of the proposal due date. The Government reserves the right to reschedule presentations at the sole discretion of the Contracting Officer.

c. Offeror Attendees. The Offeror’s Agile Process Scenario Demonstration shall be conducted by the Key Program Personnel listed in Attachment 10 of the model contract.

Each of the Key Personnel must present a portion of the Agile Process Scenario Demonstration. In addition to the Key Personnel, one (1) additional member of the Offeror’s team is permitted to attend in an administrative capacity only; i.e. advance slides or serve as a recorder, but is not permitted to present.

d. Scenario. Upon arrival to the demonstration facility, a scenario will be provided for the Agile Process Scenario Demonstration as outlined in Section L, paragraph 4.2.c.(1)a).

The Government scenario for the demonstration will be the same for all Offerors.

e. Time Limit. The Offeror shall be given 20 minutes to review the scenario within a private caucus room and submit written questions to the Government to clarify aspects of the scenario (20 minute review session along with the question and answer session may not exceed 30 minutes). The Government reserves the right to not answer the Offeror’s questions. Upon receipt of the Government’s response to the questions, Offeror’s shall be given three (3) hours to caucus and prepare for the demonstration. Following the caucus session, the Offeror shall be given a maximum of two (2) hours to present the Agile Process Scenario Demonstration. At the conclusion of the two (2) hour presentation, the Offeror will be given 30 minutes to caucus followed by an additional 15 minutes to present any final remarks to the evaluation team.

f. Clarifications. At the conclusion of the Agile Process Scenario Demonstration, the Government will caucus for up to one (1) hour to determine the need for clarification, as defined in FAR 15.306(a). No exchanges other than clarifications will be allowed.

Offerors will not be allowed to change, amend, or otherwise revise their proposals based on the demonstration or the Government’s clarification questions. No exchanges with Offerors during the demonstration will constitute discussions.

g. Caucus Material. Offerors are not permitted to bring electronic devices or any other outside materials into the caucus room. Writing materials, whiteboards, two (2) easels with easel writing pads, four (4) hardcopies of Attachment T1, and four (4) hardcopies of Section L will be made available for use during the Offeror’s three (3) hour caucus session.

Offerors will be provided a computer loaded with all FedBizOpps and Bidder’s Library (LiveLink) documents. This computer will not have internet access. Offerors are not permitted to create any additional written material during the final 30 minute caucus session. Offerors will not be permitted to keep any caucus material.

h. Presentation Material. The Government will provide a computer to project Attachment T1 during the Agile Process Scenario Demonstration. In addition to Attachment T1, Offerors are permitted to utilize written material created on the easel pads during the three

(3) hour caucus session. Material outside of Attachment T1 will only be considered presented for evaluation if specifically addressed orally during the Oral Presentation. Only the active presenter may modify or add to the written material during the Oral Presentation.

i. Recording the Presentation. The Government will record audio and video of the Oral Presentation to document the Agile Process Scenario Demonstration. The recording will be available to the Source Selection Team for their review and to assist in the evaluation of Section M, paragraph 4.2.1(1)a. In the event of inconsistencies between the written content of Attachment T1 or the additional written material presented during the Offeror’s demonstration and the recording, the voice track of the recording will take precedence.

Offerors are not permitted to record (visual/audio) their demonstration and will not be provided a copy of the recording. The recording will be maintained as part of the source selection record.

4.0 PROPOSAL CONTENT

4.1. VOLUME I – EXECUTIVE SUMMARY

General Instructions. The purpose of the Executive Summary is to provide an overview of the Offeror’s proposal. In the executive summary volume, the Offeror shall provide the following information:

a) Release Statement. The Offeror shall expressly state whether or not it concurs with the release of its proposal information to the Non-Government Advisors listed in Table 1. Failure to do so may result in elimination from the competition.

b) Teaming, Organization and Management. The Offeror shall identify the Offeror’s team including subcontractors, including locations. The Offeror shall describe the organizational relationships, management roles, and responsibilities of the participants.

c) Master Table of Contents and Cross Reference Matrix. The Offeror shall provide a master table of contents for the proposal which includes the traceability and interrelationships between volumes and sections or subsections of the overall proposal, and where material may be found for each major element of the evaluation as defined in Section L of this solicitation. In addition, the Offeror shall provide a cross-reference matrix for the entire proposal containing, at a minimum, the items shown in Table 3, Cross Reference Matrix.

Table 3 – Cross Reference Matrix (Sample)

Proposal SOW WBS IMS IMP CDRL Section L Section M

Volume/ Para

Para Ref Ref Para Item Para Para

4.2. VOLUME II – TECHNICAL – FACTOR 1

a. General Instructions. The Technical Volume shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims in the Offeror’s proposal. The Offeror shall describe its proposed approach for meeting the solicitation requirements addressed by each Technical Subfactor. The Government will evaluate the Offeror’s proposed approach against the Technical and Technical Risk Criteria in Section M of this solicitation. The Offeror’s Technical Volume (Volume II) shall be consistent with its Cost/Price Volume (Volume III). Any assertions of proposal strengths in Volume II should be reflected in the Offeror’s proposed model contract (inclusive of attachments) to the maximum extent possible.

By submitting a proposal, the Offeror acknowledges that it will perform all the requirements specified in the solicitation. The 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 these requirements. Statements that the Offeror understands, can, or will comply with the Statement of Work (SOW) (including referenced publications, technical data, etc.); statements paraphrasing the SOW or parts thereof (including applicable publications, technical data, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience. The Government will base its evaluation on the information presented in the Offeror’s proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

b. Technical Volume Organization. The Technical Volume shall be organized according to the outline below.

Table of Contents List of Tables, Drawings, and Figures Factor 1: Technical/Risk - see below for a detailed breakdown of required documentation:

Subfactor 1: Software Development and Extensibility Subfactor 2: Cybersecurity and Certification

Subfactor 3: PTW Hub Design

Attachments:

Attachment T1: Agile Process Scenario Demonstration Visual Aids Attachment T2: Software Architecture Document (SAD) Attachment T2a: Rights in Data Discussion Attachment T3: Integrated Master Schedule (IMS)

c. Content. The following information shall be submitted and used in the evaluation of the Technical Factor and Subfactors (reference Section M, paragraph 4.2.). Detailed information regarding the Technical Attachments (Attachments T1 – T3) is discussed in Section L, paragraph 4.2.d. When not otherwise specified in Table 2, the information shall be included within the page limitations of Volume II – Technical (max 40 pages). The text of Volume II – Technical (max 40 pages) shall only address Subfactor 2(a), Subfactor 2(b), Subfactor 3(a), and Subfactor 3(b). Subfactor 1(a) and Subfactor 1(b) are to be addressed in Attachments T1 and T2, respectively.

(1) Subfactor 1: Software Development and Extensibility

a) The Offeror shall provide an Oral Presentation consisting of an Agile Process

Scenario Demonstration in accordance with Section L, paragraph 3.3., using the visual aids in Attachment T1. Subfactor 1(a) shall be addressed solely through the Oral Presentation and Attachment T1. The Government will provide a scenario that the Offeror shall address in the Agile Process Scenario Demonstration. The Offeror’s Oral Presentation shall address the following:

i. Describe how the Offeror’s proposed Agile approach is consistent with

Appendix A in Attachment 1 (Statement of Work) of the model contract.

ii. Explain how the proposed number and size of Agile teams described in Attachment T1 were determined to be sufficient to deliver the required IOC capability by the end of software Build 3.

iii. Describe the process for transitioning software from the Offeror’s development environment to the Defense Information Systems Agency (DISA) Core Data Center (CDC) for system integration and test using the plans and tools described in Attachment T1. Describe the process for the transition of developed software from unclassified to classified environments.

iv. Utilizing the Government provided scenario, demonstrate the Offeror’s process for developing Features and User Stories consistent with Attachment T1.

Demonstrate the process for prioritizing User Stories and allocating User Stories to Sprints.

v. Utilizing the Government provided scenario, describe plans and processes for automated software testing using the tools described in Attachment T1.

vi. Utilizing the Government provided scenario, demonstrate the steps involved in

Build planning, Sprint planning, Sprint execution and demonstration, and Build level testing using the process delineated in Attachment T1.

b) The Offeror shall provide a Software Architecture Document (SAD) for MMS, KMS, and KLIF, as defined in Attachment T2. Subfactor 1(b) shall be addressed solely in Attachment T2 and Attachment T2a. Explain how the software architecture is consistent with the mission planning and key management functionality described in the PTES System TRD, including requirements for modularity and extensibility. Discuss how the proposed architecture is extensible to incorporate future mission planning and key management requirements for providing Protected Tactical Waveform (PTW) communications via commercial satellites and PTW-processing satellites. Discuss how the proposed Rights in Data (including Technical Data, Computer Software, & Computer Software Documentation) are consistent with the Government’s desired rights described in Attachment 7 and how the proposed Rights in Data support MOSA as described in Attachment 1 – Statement of Work, CLIN 0001 paragraph 1.1.1.2.d.1., and enable future extensibility of MMS, KMS, and KLIF.

(2) Subfactor 2: Cybersecurity and Certification

a) The Offeror shall describe their cybersecurity design concept, and development approach (including schedule) through Authority to Operate (ATO) for PTES, including concept drawings, functional descriptions. Identify information system components (e.g., routers, firewalls), boundaries, data flows, system interconnections, and protections at entry and exit points. Describe the approach for developing the system, given that the cybersecurity baseline, will be changing throughout system development (e.g., System Technical Implementation Guidelines). Describe the unclassified and classified development, test, and operational environments and the approach to cybersecurity testing, including the effects of the changing cybersecurity baseline. Discuss previous experience and domain expertise with managing changing cybersecurity requirements. Describe plans for protection and assurance activities specified in Section 1.1.1.13 of Attachment 1 (Statement of Work) and include details of these activities in the CSOW and/or IMP as appropriate.

b) The Offeror shall describe their design concepts and development approaches for End Cryptographic Units (ECU) for the Joint Hub and KMS. Provide concept drawings and functional descriptions for each ECU. Identify the major functions and data flows in each ECU design. Describe how the designs are consistent with the functionality described in the Information Assurance Security Requirements Directive (IASRD). Describe the schedule and key events for ECU design and development ensuring consistency between the description and the IMS (Attachment T3) and the Offeror’s plan to support ECU certification by the NSA.

If available, provide up to two relevant examples from the past five years where the Offeror’s proposed approach was used to design and develop an ECU which has received NSA certification or is at least past Critical Design Review (CDR) in the NSA certification process. For each example, the Offeror shall, at a minimum,

a. Describe the applicability to PTES by stating key similarities and addressing the most important differences between the cited examples and the PTES Joint Hub ECU and KMS ECU (e.g., requirements, development timeline, etc.).

b. Identify the milestones in the NSA ECU certification process that have been completed (e.g., CDR, Security Verification Testing, etc.)

c. Describe the status of NSA approval of key ECU design documents and test artifacts (e.g., Security Evaluation Document, Security Verification Plan and Procedure, Security Verification Test Report, etc.)

d. Explain how the example will mitigate development and certification risk for the PTES Joint Hub ECU and KMS ECU.

(3) Subfactor 3: Protected Tactical Waveform (PTW) Hub Design

a) The Offeror shall describe the design concept and development approach for the

Joint Hub. Provide concept drawings and functional descriptions for the proposed Hub design. Identify the major functions, data flows, and interfaces. Describe how the design is consistent with the Hub functionality described in the PTES System TRD and PTES Joint Hub TRD. Describe the schedule and key events for Joint Hub design and development, including integration with MMS/KMS, and Army Forces Strategic Command (ARSTRAT) approval, ensuring consistency between the description and the IMS (Attachment T3). Describe the design of key functions, including processing the PTW waveform, Dynamic Resource Allocation, data transport, and network configuration management. If available, provide up to two (2) relevant examples from the past five (5) years where the Offeror developed a system with functions similar to the Joint Hub. For each example, the Offeror shall, at a minimum:

a. Describe the applicability to PTES by stating key similarities and addressing the most important differences between the cited examples and the PTES Joint Hub (e.g., PTW-processing capability, data networking requirements, development timeline, etc.).

b. Describe the extent to which the example system has successfully demonstrated capabilities similar to the PTES Joint Hub in formal testing.

Identify any areas that require additional development and testing.

c. Explain how the examples will mitigate PTES Joint Hub development risk and risk associated with ARSTRAT approval of the Joint Hub modem.

b) Per Attachment 2, Compliance/Reference Document List & Tailoring, of the model contract, the Offeror shall comply with all threshold requirements within the PTES System TRD and PTES Joint Hub TRD. If the Offeror proposes to fully or partially meet any objective requirements defined in the PTES System TRD and PTES Joint Hub TRD (specified within Attachment 2 of the model contract), then the Offeror shall include the complete text of those requirements in Attachment 2a of the solicitation (reference Section L, paragraph 5.b.c., Compliance and Reference Documents Appendix), without the “objective” label. If the Offeror intends to partially comply with any PTES System TRD or PTES Joint Hub TRD objective requirement, then the text of the requirement included in Attachment 2a of the model contract shall specify the exact performance the Offeror is proposing to provide. If the Offeror does not propose to fully or partially meet any objective requirement defined in the PTES System TRD or PTES Joint Hub TRD, then the Offeror shall provide the statement “Intentionally Left Blank” in Attachment 2a of the model contract.

d. Technical Attachments. As discussed in Section L, paragraph 3.2., the Technical

Attachments will be used in the evaluation of the Technical Subfactors.

a) Attachment T1 to Volume II - Agile Process Scenario Demonstration Visual Aids: The Offeror shall provide visual aids with the proposal to assist in the Agile Process Scenario Demonstration. The visual aids shall be in Adobe pdf format.

Attachment T1 shall:

i. Display an overview of the Agile process for developing PTES software, including:

Roles of Key Program Personnel (Attachment 10 of the model contract)

Interactions between Key Program Personnel and the Agile teams in the planning and execution of the Agile process

The number of Agile teams and the number of personnel per team How the efforts of all development teams are synchronized to enable integrated, multi-segment testing

ii. Display a graphical timeline of the Build and Sprint cadence, including the time phasing of each software Build, each Build Risk Reduction Demonstration, Initial Operational Capability (IOC) and Full Operational Capability (FOC).

iii. Describe the plans and tools to support system integration and test on the DISA

CDC.

iv. Describe the tools for automated software testing including targets for percentage of code covered.

v. The text of Attachment T1 shall be presented in Times New Roman, minimum 12-point font. Text within images, charts, graphs, and tables shall be, at a minimum, 8-point font.

b) Attachment T2 to Volume II - Software Architecture Document (SAD): The Offeror shall provide the PTES software architecture for MMS, KMS, and KLIF in the SAD. The SAD shall:

i. Provide a software architecture for MMS, KMS, and KLIF that is consistent with the mission planning and key management functionality described in the PTES System TRD.

ii. Identify all software modules and describe how they are consistent with modules specified in SOW CLIN 0001 paragraph 1.1.1.2.d.

iii. Identify reuse, COTS, and other non-development software in each module.

iv. For modules with reuse, discuss if the reused software contains capabilities that are not used by the module (known as dead code or unused code) and estimate the percentage of dead/unused code in that module.

v. Describe the method of communication between modules.

vi. Describe your virtualization approach that enables effective deployment at the DISA DECC and describe related Mission Unique Equipment (MUE) as well as connectivity to the DoD SATCOM Gateway sites.

vii. Discuss the architecture’s extensibility and how it could accommodate future mission planning and key management requirements for providing PTW via commercial satellites and via PTW-processing satellites.

viii. For any Commercial Software, ensure a copy of the associated commercial software license be appended to Appendix A of Attachment 7 of the Offeror’s proposed model contract.

ix. The text of Attachment T2 shall be presented in Times New Roman, minimum 12-point font. Text within images, charts, graphs, and tables shall be, at a minimum, 8-point font.

c) Attachment T2a to Volume II – Rights in Data Discussion: The Offeror shall discuss how the proposed Rights in Data (including Technical Data, Computer Software, & Computer Software Documentation) are consistent with the Government’s desired rights described in Attachment 7 and how the proposed Rights in Data support MOSA as described in Attachment 1 – Statement of Work, CLIN 0001 paragraph 1.1.1.2.d.1., and enable future extensibility of MMS, KMS, and KLIF.

d) Attachment T3 to Volume II - Integrated Master Schedule (IMS): The Offeror shall provide a single IMS in Microsoft Project 2010 format reflecting the lowest WBS level in the Offeror’s proposed Volume V, Attachment 3, Contract Work Breakdown Structure, of the model contract.

i. The IMS shall provide detailed task timing of the work effort described in the IMP and SOW. Include the software development schedule including durations for developing software builds and releases. Identify scheduling dependencies among the PTES segments and with external organizations.

Identify delivery dates of GFE/GFP items and key products from the prime, subcontractor, other prime contractor divisions, and suppliers that are required for on time delivery of contractual requirements.

ii. The IMS shall identify the critical path and demonstrate that the schedule aligns with contract deliverables, PTES system events and contract milestone reviews.

Clearly identify schedule margins along the critical and near critical paths.

iii. The IMS shall comply with the key event schedule in Table 4 below and shall be consistent with the integration and demonstration events in the PTES System Integration and Test Plan.

iv. The text of Attachment T3 shall be presented in Times New Roman, minimum 12-point font. Text within images, charts, graphs, and tables shall be, at a minimum, 8-point font.

Table 4 – PTES Key Event Schedule

Event Schedule

Kickoff ATP + 10-20 days

System Requirements Review (SRR) NLT ATP + 3 months

System Functional Review (SFR) NLT ATP + 6 months

Preliminary Design Review (PDR) NLT ATP + 12 months

Critical Design Review (CDR) NLT ATP + 24 months

Initial Operational Capability (IOC) NLT Q3FY2023

Full Operational Capability (FOC) NLT Q1FY2026

4.3. VOLUME III – COST/PRICE – FACTOR 2

a. General Instructions. This section will assist the Offeror to submit information other than certified cost or pricing data for the Government to evaluate the reasonableness, realism, unbalanced pricing, and compliance to the funding profile (Section L, paragraph 4.5.b.g). Compliance with these requirements is mandatory and failure to comply may make an offer ineligible for award. Offers should be sufficiently detailed to demonstrate their reasonableness, realism, and compliance to the funding profile provided.

a) Price Data. Data beyond that required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support their cost/price position. All data relating to the proposed cost/price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

b) Adequate Price Competition. The Contracting Officer has determined there is a high probability of adequate price competition for this acquisition. Upon examination of the initial offers, the Contracting Officer will review this determination and if, in the Contracting Officer’s opinion, adequate price competition exists, no additional cost information will be requested and certification under FAR 15.406-2 will not be required. If at any time during this acquisition the Contracting Officer determines adequate price competition no longer exists, Offerors may be required to submit other than certified cost and pricing information necessary for the Contracting Officer to determine the price fair and reasonable in accordance with FAR 15.402.

c) Cost or Pricing Data Requirements. Certified Cost and Pricing Data are not required to be submitted with the proposal at this time. In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. The PCO will provide further instructions for content and format if additional cost and pricing data will be required.

d) Projected Award Date. Offerors shall assume a contract award date of 31 January 2019 for purposes of pricing, inserting required dates, and understanding required delivery schedules and incentive provisions.

e) Rounding. All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

f) Electronic File Submission. The official copy of the Offeror’s Cost/Price Volume shall be submitted in the following electronic formats as applicable: PDF Acrobat 8.0 (with "Select", "Print", and "Copy" enabled to allow for text and graphics transfer), Microsoft (MS) Word 2010, MS Excel 2010, MS Project 2010, and MS PowerPoint 2010. All electronic files shall be compatible with Microsoft Windows 7.

All working files constructed in Microsoft Excel shall use formulas instead of just pasted values to preserve any calculation logic within the file, including summaries and totals. The Offeror shall provide electronic copies of all cost/pricing models that are used for developing its estimate in the appropriate attachments. All Excel files shall have working formulas. Offerors shall use the “group and Outline” feature of MS excel to facilitate the ease of proposal analysis. If the model requires multiple MS Excel spreadsheets, the “link cell” feature shall be used. The cost/price proposal submitted shall be consistent with the Offeror’s approved estimating system and shall duplicate the logic and mathematical formulas reflected in the official copy of its proposal.

b. Cost/Price Volume Organization. The Cost/Price Volume shall be organized according to the outline below.

Table of Contents List of Tables, Drawings, and Figures Factor 2: Cost/Price - see below for a detailed breakdown of required documentation.

Section 1: Introductory Section Section 2: Printed Cost/Price Element Summaries for Cost CLINs

Section 3: Discussion of Cost Elements for Cost CLINs Section 4: Discussion of Business Systems and Offeror Unique Approaches

Cost Attachments (CP):

Attachment CP1: Working Excel Files – Cost/Price Model with Cost Element Summaries for CLINs 0001 – 0005, 0007, and 0008 Attachment CP2: Working Excel Files – Special Studies Calculation Attachment CP3: Cumulative Funding Constraint Trace from CP1 Attachment CP4: Prime’s Cost/Price Analysis of Sub/IWTA/Team 1 Information Attachment CPX: Prime’s Cost/Price Analysis of Sub/IWTA/Team x Information

c. Content. The Cost/Price Volume shall consist of the following Sections and Attachments as described below. The following information shall be submitted and used in the evaluation of the Cost/Price Factor (reference Section M, paragraph 4.3).

SECTION 1 – INTRODUCTORY SECTION

As an introduction, the Offeror shall provide comprehensive narrative support for the Cost/Price Volume. The narrative shall explain the philosophy, methodology and assumptions used in proposing the dollar amounts for the associated CLINs listed in Table 5 – Cost/Price Methodology. Any apparent imbalances in the pricing, any unrealistically low amounts, and any apparent pricing anomalies shall be clearly explained. The Government expects that consistency exists between the Technical and Cost/Price volume;

any Offeror-intended inconsistency shall be clearly explained and convincingly demonstrate how the promised performance will be achieved at the proposed cost/price.

Table 5 – Cost/Price Methodology

CLIN

Title

Contract Type

Philosophy in Proposing the Dollar Amounts

0001 Design and Development CPIF/AF Offeror to comment

0002 IOC Capability Development CPIF/AF Offeror to comment

0003 FOC Capability Development CPIF/AF Offeror to comment

Joint Hub Procurement (FOC

Capability) CPIF Offeror to comment

Joint Hub Installation and Deployment

(FOC Capability) CPFF Offeror to comment

0006 (RESERVED)

Priced Training and Technical

Orders CPFF Offeror to comment

0008 Special Studies CPFF Offeror to comment

0009 Data and Reports (CPIF) NSP N/A

0010 (RESERVED)

0011 Data and Reports (CPFF) NSP N/A

(If Needed)

Data Rights (Attachment 7) FFP Offeror to comment

a) Time-Phased, person-loading graph. The Offeror shall provide a time-phased, person-loading bar graph for each CLIN. The vertical axis shall be in hours. The horizontal axis shall be in quarters. The bars will be layered – bottom for prime hours and each stack on top will be for each non-prime with at least 20% of the proposed total effort.

b) Offeror Summary table (Prime plus non-prime companies greater than 20% of total proposed dollars). The Offeror shall complete Table 6 below, listing all companies – prime, subcontractors, and team members – who will be involved with the performance and management of the contract. If the relationship is not a prime-subcontractor relationship, provide the legal definition of the relationship between the entities.

Table 6 – Subcontract and Teaming

Company Name

Cage Code

DCMA

Cognizant

Office (Address, Name, &

Phone # of

ACO)

Place of Performance

Brief Work Description (Program

Responsibility)

Total Proposed Amount

Percentage of Total Proposal Dollars

(Sum of all

CLIN

Prices)

SECTION 2 – PRINTED COST/PRICE ELEMENT SUMMARIES FOR COST

CLINS (CLINs 0001-0005 and 0007-0008)

a) Offeror’s Total Proposed Price (TPP) calculation. The Offeror shall complete and submit Table 7, Total Proposed Price, in…