W900KK-18-R-0007-0004_Changes.docx

W900KK-18-R-0007

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

SOLICITATION CLOSING

A.2. SOLICITATION CLOSING

In accordance with submission instructions outlined in Section L.2, Proposal Submission Requirements, proposals for solicitation W900KK-18-R-0007 shall be shall be received by the designated Government official no later than 1:00 pm Eastern Standard Time on 15 December 2017.

*** END OF NARRATIVE ***

SECTION I - CONTRACT CLAUSES

The following have been deleted:

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

L. PROPOSAL SUBMISSION (Section L)

L.1. Proposals for the Basic ID/IQ, Delivery Order 0001, and Delivery Order 0002 shall be compliant with the full solicitation requirements and instructions contained within this section. Proposal submissions for the Basic ID/IQ, Delivery Order 0001, and Delivery Order 0002 will be evaluated for consistencies to ensure the Offeror’s understanding of the entire CCTT M3 requirement. The Government will evaluate each proposal in accordance with this solicitation; offerors are required to comply with all requirements stated herein. Any indication that the offeror does not intend to meet all of the requirements may cause the proposal to be evaluated as non-compliant and ineligible for award.

L.1.1. Introduction. The M3 requirement is a Full and Open Competition, to be competed among companies qualifying under NAICS 333318 (Other Commercial and Service Industry Machinery Manufacturing), with a size standard of 1,000 employees. The M3 technical requirements and the details for the ID/IQ contract, DO 0001, and DO 0002 are defined within section C of this solicitation.

L.1.1.a. Offerors are hereby notified that non-Government participants will have access to the offerors’ proposals. The non-government participants are contracted employees supporting Systems Engineering and Technical Assistance (SETA) contract W900KK-17-D-0002. They will serve as technical advisors to the Government and will be authorized access to only the Offeror’s Volume I – Technical (Systems Engineering), and Volume II – Technical (Product Approaches) proposals, which is necessary to enable them to provide specific advice on CCTT M3 technical and program management matters. All non-Government personnel have signed certificates of non-disclosure and financial interest, or their equivalent documents. Non-Government participants will participate in an advisory role only, and will not be included in any applicable consensus discussion or determination.

L.1.1.b. An offeror’s submission of a proposal in response to this solicitation constitutes approval for disclosure of proprietary information contained within the proposal to non-government participants involved in the source selection. If the contractor is not willing to provide this consent, written notification to the Procuring Contracting Officer (PCO) is required no later than 15 days prior to the proposal due date.

L.1.1.c. Offerors shall demonstrate their capability, understanding, and willingness to satisfactorily perform the effort described in the Base ID/IQ Performance Work Statement (PWS), and the efforts outlined in the PWS for Delivery Order 0001 and the PWS for Delivery Order 0002, located in Section C of this solicitation, for the resultant Single Award ID/IQ contract, Delivery Order 0001, and Delivery Order 0002. Capabilities may be established within either the Offeror’s corporate structure or through contractor teaming arrangements. The Government is neither encouraging nor discouraging teaming arrangements and will focus on the Offeror's proposed approach to perform the full scope of work. The proposal shall be valid for 270 calendar days from date of initial proposal submission. The offeror shall insert the validity date in Block 12 of the SF 33.

L.1.1.d. Unless otherwise specifically stated, the term contract will be synonymous with the words contract, project or effort, when used in reference to information required in association with this solicitation.

L.1.2. The offeror’s proposal shall be submitted in digital copies, as set forth below:

L.1.2.a. The offeror’s proposal shall consist of seven (7) volumes. The Volumes are:

Volume I – Technical (Systems Engineering);

Volume II – Technical (Product Approaches);

Volume III – Program Management;

Volume IV – Past Performance;

Volume V – Small Business Participation;

Volume VI – Cost/Price; and

Volume VII – Solicitation, Offer and Award Documents and Certifications/Representations.

**Files shall not contain classified data.

**The use of hyperlinks in proposals is prohibited.

L.1.3. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the entire requirement and associated risks, and is able, willing, and competent to devote resources necessary to meet the requirement, and has a valid and practical solution for the requirement. Statements that the prospective Offeror understands, can, or will comply with the requirements, and statements paraphrasing the requirements or parts thereof without supporting information/narrative are considered inadequate and unsatisfactory. Mere reiteration of the requirement or standard reference material is discouraged and is considered inadequate and unsatisfactory. The Offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. In presenting material in proposals, Offerors are advised that quality of information is more important than quantity. Offerors are encouraged to use quantitative terms wherever possible and avoid the use of qualitative and subjective terms to the maximum extent practicable. Offerors are cautioned that while the Government will not evaluate every PWS requirement for the purposes of the source selection evaluation, the awardee/Contractor will be required to comply with all PWS requirements during performance of the contract. The offeror’s proposal shall describe its approach to implementing PWS requirements that are being evaluated. The proposal shall reference the related paragraphs of the PWS (e.g. 3.1.2) and Section L, Attachment L5, L+M PWS Reference, and provide the detail necessary to substantiate the proposed approach and methodology for performance. The proposal should identify any unique or innovative approaches which ensure successful performance. The Government will determine that an Offeror's proposal is non-compliant, and therefore ineligible for award, if the proposal indicates that: it cannot or will not meet all the requirements; provides an approach that clearly does not meet any of the requirements; or, includes data which prompts the Government to question the Offeror's compliance with any of the requirements. The Source Selection Authority may reject all proposals received in response to a solicitation, if doing so is in the best interest of the Government. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.

L.1.4. The proposed approach should be specific, detailed, and contain sufficient information to clearly and fully demonstrate the offeror’s understanding of the requirements and the inherent risks associated with this procurement. It is inadequate to simply state that the offeror understands and will comply with the requirements, or to paraphrase the requirements. The proposal shall comprehensively explain how the offeror proposes to comply with the applicable requirements, as well as describe the techniques and procedures the offeror proposes to implement.

L.1.5. Information previously submitted to the Government should be assumed unavailable during this proposal evaluation and source selection process. Proposal data shall not be incorporated into the proposal by referring to another proposal or other source. Proposals submitted will not be returned. Alternate proposals will not be evaluated or accepted.

L.1.6. The portions of the successful offeror’s (Awardee’s) proposal that have merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance will be incorporated into Section C of the resulting contract and resulting Delivery Orders.

L.1.7. The Offerors shall ensure that each proposal volume submitted contains only the information relevant to that specific volume. The Offerors are cautioned that each volume of the proposal is evaluated standalone against the criteria set forth in Section M and the evaluators for one volume may be different than the evaluators of another volume. It is incumbent upon the Offerors to ensure they properly submit their proposals. If the data is not contained in the appropriate volume of the proposal, it will not be evaluated. For example, if Past Performance narratives are submitted under the Price Volume rather than the volume specified, the proposal will be evaluated as if no Past Performance narratives were submitted at all. No cost information shall be included in the Technical or Program Management Volumes of the offerors proposal. The volumes will be evaluated in accordance with the Evaluation Criteria provided in Section L and M. Failure of an offeror to provide all requested proposal information may render the offeror’s proposal as non-compliant and as such, the offeror’s proposal will not be evaluated, at the sole discretion of the PCO. If determined to be non-compliant, the PCO will notify the offeror immediately.

L.1.8. If an offeror believes that the requirements or the RFP contain an error, omission, or are otherwise unsound; the offeror shall immediately notify the Contract Specialist and Contracting Officer, via email at ashley.n.carter55.civ@mail.mil and dunamis.t.triska.civ@mail.mil, with supporting rationale, prior to the RFP due date (See Section A, Executive Summary).

L.1.9. Solicitation Questions: All questions regarding the RFP shall be submitted in writing to the Contract Specialist and Contracting Officer, via email at ashley.n.carter55.civ@mail.mil and dunamis.t.triska.civ@mail.mil, within 15 calendar days after the RFP is published. Offerors shall submit questions using RFP Section L, Attachment L1, Solicitation Question/Comment Form located in Section L. No phone inquiries regarding the RFP will be received or acknowledged. Offerors will receive an acknowledgement of their question via response to the email submission. All inquiry items will be answered via an Amendment to the RFP/Solicitation and posted to fedbizopps.gov website under the solicitation number. Answers will be posted without Offeror identification. The Government will not provide responses to questions that would reveal a potential Offeror’s confidential business strategy, technical solution, or any information that is considered unique to a particular Offeror. The Government reserves the right to decline addressing questions received after 15 calendar days after the RFP posting (See Section A, Executive Summary).

L.1.10. In accordance with FAR Subpart 52.215-1, Instructions to Offerors – Competitive Acquisition, the Government intends to evaluate proposals and award a contract without discussions with offerors (except clarifications as described in FAR 15.306(a)). Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a cost or price and technical standpoint. However, the Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. Should discussions take place, all offerors in the competitive range will be allowed a minimum of 14 calendar days to submit Final Proposal Revisions. The Contracting Officer will schedule the discussion sessions, and each offeror within the competitive range will be notified of the time and place at least three (3) business days prior to their discussion session. Appropriate security clearances should be provided by the offerors in sufficient time to process the requests. The Contracting Officer will provide additional instructions with the notification. The discussion sessions will take place at a facility of the Government’s choosing.

L.1.11. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals. Clarifications are not discussions. Offerors may be given the opportunity to clarify certain aspects of the proposal or resolve minor or clerical errors (see FAR 15.306(a)(1) and (2)). Clarifications shall be documented on, and conducted via transmittal of, Evaluation Notices (EN) to the applicable offeror.

L.1.12. In accordance with FAR Subpart 9.6, the Government will recognize the integrity and validity of contractor team arrangements; provided, the arrangements are identified and company relationships are fully disclosed in the offer. Contractor Team Arrangements are considered as an arrangement in which (1) two or more companies form a partnership or joint venture to act as a potential prime contractor, or (2) a potential prime contractor agrees with one or more other companies to have them act as its subcontractor under a specified Government contract or acquisition program. The prime contractor will be held fully responsible for contract performance, regardless of any team arrangement between the potential prime contractor and its subcontractors. Where the use of subcontractors is proposed, the proposal shall clearly distinguish between the prime and the major subcontractor’s work and responsibilities. Major subcontractors are defined as members of an offeror’s overall team who are expected to perform fifty (50) percent or more of the proposed non-recurring engineering effort on any individual M3 NRE CLIN. The Offeror shall submit signed and binding Contractor Team Arrangement Agreements for ALL major subcontractors and Small Business Participation Plans, when applicable, within Proposal Volume IV-Past Performance, Section 6-Attachments, and Volume V-Small Business Participation, as instructed.

L.1.13. Any proprietary information submitted separately for major subcontractors shall be furnished in the same format, level of detail, and submission due date as prescribed for the prime Offeror. Subcontractor proposals submitted separately are considered part of the offeror’s proposal, including the page count. If subcontractor proposals are submitted separately, directly to the PCO and are late, the entire proposal will be considered late.

L.2. PROPOSAL SUBMISSION REQUIREMENTS

L.2.1. Proposals for solicitation W900KK-18-R-0007 may be hand carried, sent by standard mail delivery through the United States Postal Services (USPS), or by a certified express vendor (i.e., - FedEx) and shall be received no later than 1:00 pm Eastern Standard Time (local time) on 15 December 2017. The Offeror shall use the “Tracking” option for the proposal package(s). The Offeror shall provide a copy of the receipt for USPS and FedEx delivery options via email message to Ashley Carter, ashley.n.carter55.civ@mail.mil AND Dunamis T. Triska, dunamis.t.triska.civ@mail.mil, within 24 hours of mailing the proposals.

L.2.2. All proposals shall indicate the following mailing address: Army Contracting Command-Orlando Attention: Ashley Carter/ Dunamis T. Triska 12211 Science Drive Orlando, FL 32826-3224. The solicitation number shall be clearly visible on each package.

L.2.3. For a hand-carried proposal, the Offeror shall complete Section L, Attachment L6 - Proposal Receipt Form (Company name, Date Delivered, Company Representative’s Name, Company Representative’s Title and Number of CD/DVD Packages Received). The Contracting Officer/Specialist will annotate the date and time of proposal receipt. The Offeror’s Representative will confirm the data and sign the Proposal Receipt. The Contracting Officer/Specialist will provide a copy of the Proposal Receipt Form to the Offeror. The Contracting Officer/Specialist’s signature only denotes the receipt of the proposal package. The Government is not responsible for the proposal delivery content or condition upon delivery.

L.2.4. OFFERORS ARE HEREBY ON NOTICE THAT FAILURE TO SUBMIT ALL THE REQUIRED PROPOSAL INFORMATION IN EXACTLY THE MANNER (TIMELINESS AND FORMAT) AS SPECIFIED IN THE SOLICITATION MAY CONSTITUTE A BASIS FOR THE GOVERNMENT TO REJECT A PROPOSAL AS NON-COMPLIANT AND THEREFORE INELIGIBLE TO BE CONSIDERED FOR AWARD, AT THE SOLE DISCRETION OF THE PCO.

L.2.5. Each volume shall be submitted in digital format. Any pages that are changed (as a result of discussions or proposal revisions) should be of a different color and have changed information clearly marked by a vertical line in the right margin of the page. The revised pages shall be dated. Each volume shall be clearly labeled with its Title and a copy number (e.g., copy 1 of 2).

L.2.6. Paragraphs should be single spaced. Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or New Times Roman fonts are required. Tables shall be 12-point font and may be landscape. Illustrations (e.g. images or diagrams) shall use a font size of no less than 10-point and may be landscape. The IMS shall be submitted using the Microsoft Project 2013 and may use the default font size of the application.

L.2.7. The following volumes of material shall be submitted:

VOLUME TITLE

DIGITAL COPIES

MAXIMUM PAGES

III – Program Management

IV – Past Performance

Section 1 – 1 page Section 2 – 5 pages Section 3 – 3 pages Section 4 – Unlimited Section 5 – Unlimited Section 6 – Unlimited

V – Small Business Participation

VI – Cost/Price

NOTE: Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed and will not be evaluated by the Government.

*Manpower (i.e. staffing) charts, Table of Contents, Title Pages, Glossary, Divider/Blank Pages, Teaming Agreements, Letters of Commitment, IMS, Resumes, Sample Fielding Plans (Section L, Attachment L2), and PWS References (Section L, Attachment L5) are excluded from the page count.

L.2.8. The CD/DVD case of each digital copy of each volume of the proposal shall contain the Offerors name, the solicitation number, the title of the solicitation, the Volume number, and the copy number (i.e., sequentially number the required copies with the original being labeled as Copy No. 1). Company logos and/or names and pictures that identify company identification or personnel shall be used on the CD/DVD case cover only of the Technical (Systems Engineering), Technical (Product Approaches), and Program Management Volumes and not printed on the face of the CD/DVD. The Technical (Systems Engineering), Technical (Product Approaches), and Program Management Volumes CD/DVDs and contents within (pages, including appendices, Table of Contents, Title Pages, Glossary, Dividers/Tabs, Blank pages throughout the digital copies of the Technical (Systems Engineering), Technical (Product Approaches), and Program Management Volumes of the proposal) shall not contain company logos and/or names, pictures or any information that indicates the company’s identification or personnel. The Technical (Systems Engineering), Technical (Product Approaches), and Program Management Volumes shall not contain any pictures that identify company personnel or Government personnel. No quotes or statements made by Government personnel in prior acquisition efforts shall be contained within the Technical (Systems Engineering), Technical (Product Approaches), and Program Management Volumes of the Offeror’s proposal. Each proposal volume (I-Technical (Systems Engineering), II-Technical (Product Approaches), III- Program Management, IV-Past Performance, V-Small Business Participation, VI-Cost/Price, VII- Solicitation, Offer and Award Documents and Certification/Representations) shall be submitted as a separate volume and disc (CD or DVD).

L.3. PROPOSAL FILES

L.3.1. Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume EXCEPT for Volume I, Technical (Systems Engineering), Volume II, Technical (Product Approaches), and Volume III Program Management shall be appropriately numbered and identified by the complete company name, date and RFP number in the header and/or footer. All pages of Volume I, Volume II, and Volume III shall be appropriately numbered and identified by the date and RFP number in the header and/or footer and shall NOT include the company name. All files on each CD/DVD shall be directly supported by Microsoft Office 2013 and verified to be free of any virus or malware. The IMS shall be submitted in Microsoft Project 2013. Please note, self-extracting “.exe” files are not acceptable. A Table of Contents should be created using the Table of Content feature in MS Word. MS Word (doc) files shall use the following page setup parameters:

NOTE: 11” X 17” pages are acceptable for tables/graphic representations ONLY. Each printed side of an 11” X 17” page counts as two pages for the relevant page count.

L.3.2. The following additional restrictions apply:

L.3.3. File Packaging. All of the proposal files shall be compressed (zipped) into one file entitled “Volume <number and name> CCTT M3 proposal zip” proposal zip using WinZip version 6.2 or later, or as separate uploads in their native format, i.e. doc, xls, ppt, etc., and provided on CDs or DVDs. No other electronic media will be permitted. All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2013. For Volume I Technical (Systems Engineering), Volume II Technical (Product Approaches), and Volume III Program Management, each CD/DVD case cover ONLY shall be externally labeled with the volume number, date, RFP number, and the Offeror’s name. Each disc inside the CD/DVD cover of Volume I, Volume II, and Volume III shall be externally labeled with the volume number, date, and RFP number and shall NOT include the company name. For all other volumes, other than Volume I, Volume II, and Volume III, each disc AND CD/DVD case cover shall be externally labeled with the volume number, date, RFP number, and the offeror’s name.

L.3.3.a. Content Requirement. All information shall be confined to the appropriate file. The offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents and the Narrative discussion. Proprietary information shall be clearly marked.

L.3.4. VOLUMES AND FACTORS

L.3.5. VOLUME I – Factor 1: Technical (Systems Engineering). The volume shall demonstrate the offeror’s understanding of the interdependencies among the requirements of the basic ID/IQ, DO 0001, and DO 0002. The work outlined in DO 0001 and DO 0002 are comprehensive of the entire technical requirements of this ID/IQ effort; therefore, this volume shall demonstrate the Offeror’s understanding of the entire technical requirement through the Offeror’s DO 0001 and DO 0002 proposal submission under the technical volume. Relevant PWS sections that will be evaluated are provided under each Subfactor; however, Offerors may include additional material to the extent that it is necessary to describe the proposed approach for meeting the requirements being evaluated. All referenced PWS sections are inclusive of sub-paragraphs and sections (e.g. a reference to paragraph 3.1 implicitly includes all 3.1.x and other nested paragraphs). The Government may consider the impact of the Offerors proposed approach on the ability to meet all solicitation requirements, even if not being specifically evaluated, in the evaluation of each subfactor. The Offeror shall complete, and attach to Volume I, the Section L, Attachment L5 table to provide the specific PWS subparagraphs (e.g. 3.1.3.x) the Offeror deems relevant to each subfactor element in the Technical and Program Management Volumes of the Offerors proposal. Attachment L5 is for informational purposes only and will not be evaluated.

The volume shall be organized sequentially into the following sections:

L.3.5.a Factor 1 - Subfactor 1, Overarching Systems Engineering Approach.

The Offeror shall submit an overarching Systems Engineering (SE) and architectural approach for the asynchronous Non-Recurring Engineering (NRE) of the Input/Output (I/O) System, Site Infrastructure, Visual System, and Concurrency products. The approach shall describe in detail the dependencies between products and how the products are designed to be fully integrated and compatible with each other and the entire system architecture such that no re-engineering or re-development activities are required after Government acceptance of each product. Relevant PWS sections include: DO 0001 PWS: 3.1, 3.3, DO 0002 PWS: 3.1.2

L.3.5.b. Factor 1 - Subfactor 2, CCTT System Configurations.

The Offeror shall describe an approach to support the operation of existing system configurations, new system configurations with newly developed products (e.g. I/O, Site Infrastructure, Visual System), or various combinations of both simultaneously (e.g. a combination of support for new Site Infrastructure at a site that still operates on the existing I/O configuration). This approach shall describe in detail the complexities, challenges, and potential risk mitigation strategies to configure software to utilize either the legacy or M3 infrastructure on a per site basis and to configure software to utilize either the legacy or M3 version of all other M3 products on a per module basis. Relevant PWS sections include: ID/IQ PWS: 3.13.1, DO 0001 PWS: 3.1, 3.3, 3.4.1, 3.4.2, DO 0002 PWS: 3.1.2

L.3.5.c. Factor 1 - Subfactor 3, Modular Implementation and Standards.

The Offeror shall describe their approach for a system architecture that incorporates considerations for maintainability, technology insertion, vendor independence, scalability, extensibility, and long-term supportability. The approach shall describe how the proposed system will allow incremental system improvement and maintenance through modular upgrades of individual hardware or software components. The approach shall include details on the use of standards-based interfaces, widely-supported, consensus-based standards, and Commercial-off-the-Shelf (COTS) technology. The approach shall describe the proposed data rights and software licensing for all modified portions of the system, and explain how the proposed rights will allow the Government to update, modernize and maintain the system in the future through competition. The Offeror shall complete Attachment 12, to Section J, as described in the instructions within the attachment as a part of the data rights evaluation. The approach shall describe how the system architecture ensures access to newer technologies without redesign of entire systems or large portions thereof. Relevant PWS sections include: ID/IQ PWS: 3.1.1, 3.3, 3.4, 3.5.1 (excluding 3.5.1.2), 3.5.3

L.3.6. VOLUME II – Factor 2: Technical (Product Approaches). The volume shall demonstrate the offeror’s understanding of the technical product requirements of the basic ID/IQ, DO 0001, and DO 0002. The work outlined in DO 0001 and DO 0002 are comprehensive of the entire technical requirements of this ID/IQ effort; therefore, this volume shall demonstrate the Offeror’s understanding of the entire technical requirement through the Offeror’s DO 0001 and DO 0002 proposal submission under the technical volume. Relevant PWS sections that will be evaluated are provided under each Subfactor; however, Offerors may include additional material to the extent that it is necessary to describe the proposed approach for meeting the requirements being evaluated. All referenced PWS sections are inclusive of sub-paragraphs and sections (e.g. a reference to paragraph 3.1 implicitly includes all 3.1.x and other nested paragraphs). The Government may consider the impact of the Offerors proposed approach on the ability to meet all solicitation requirements, even if not being specifically evaluated, in the evaluation of each subfactor. The Offeror shall complete, and attach to Volume II, the Section L, Attachment L5 table to provide the specific PWS subparagraphs (e.g. 3.1.3.x) the Offeror deems relevant to each subfactor element in the Technical and Program Management Volumes of the Offerors proposal. Attachment L5 is for informational purposes only and will not be evaluated.

The volume shall be organized sequentially into the following sections:

L.3.6.a. Factor 2 - Subfactor 1, I/O hardware and Software Implementation.

The Offeror shall describe their proposed technical approach to modernize the CCTT I/O hardware and software implementation, including any tradeoffs, challenges, and considerations for future concurrency developments. The Offeror shall describe in detail their proposed I/O software interface standard with the CCTT system to include their approach to automated fault localization. The technical approach shall describe the life cycle aspects of their chosen I/O product(s) with respect to supportability, sustainability, maintainability, scalability, and extensibility. Relevant PWS sections include: ID/IQ PWS: 3.1.2, 3.3.2, 3.3.3, 3.4.1, 3.4.2, 3.5.1 (excluding 3.5.1.2), DO 0002 PWS: 3.1

L.3.6.b. Factor 2 - Subfactor 2, Site Infrastructure Implementation.

The Offeror shall provide their proposed site infrastructure approach. The site infrastructure approach shall describe the proposed solution for the transition of existing CCTT software applications to the new site infrastructure. The site infrastructure approach shall address virtualization details with respect to system performance and hardware compatibility and commonality. The Offeror shall describe the scalability and extensibility of their technical approach to the site infrastructure. The Offeror shall describe how their site infrastructure approach addresses potential network performance challenges and their mitigation strategy. The approach shall address CCTT facility constraints (e.g. existing power and HVAC distribution) on infrastructure design for a sample CCTT fixed and RVTT fixed site (utilize example sites provided in TDP). The Offeror shall describe how their site infrastructure approach addresses projected life cycle considerations (i.e. hardware reduction, maintenance, licensing, training needs, operational availability). The site infrastructure approach shall describe the possible challenges and their mitigation strategy to implement Risk Management Framework (RMF). Relevant PWS sections include: ID/IQ PWS: 3.1.3, 3.3.2, 3.3.3, 3.4.1, 3.4.2, 3.5.1, 3.5.2, 3.5.3, 3.5.10, 3.5.11 (excluding subparagraphs), 3.11.2, 3.11.3, DO 0001 PWS: 3.1.3

L.3.6.c. Factor 2 - Subfactor 3, Visual System Implementation.

The Offeror shall describe in detail their technical approach to the visual system modernization including the video distribution system, displays, Image Generator (IG), and IG content. The technical approach shall describe the proposed solutions for fully digital video distribution and display subsystems, the technical feasibility of each solution, and the potential risks (with associated mitigation solutions). The approach shall describe the IG hardware reduction in terms of the total number of computers, the physical space they require, and projected life cycle considerations (e.g. maintenance, licensing, training needs, operational availability). The approach shall describe how the proposed IG software, including Open API functionality, supports the integration of new capabilities, supports the exchange and use of information and services among CCTT components, and enables future enhancement without redesign of the entire product. The Offeror shall describe their proposed approach to support or convert existing IG content (e.g. terrain databases, models), develop new content, and mitigate any challenges regarding the migration to the new visual system. The approach shall describe the proposed processes and tools required for third-party IG content development. Relevant PWS sections include: ID/IQ PWS: 3.1.4, 3.3.2, 3.3.3, 3.4.1, 3.4.2, 3.5.1 (excluding 3.5.1.2), DO 0001 PWS: 3.1.4

L.3.6.d. Factor 2- Subfactor 4, Concurrency Implementation.

The Offeror shall provide their proposed technical approach to the following hypothetical concurrency scenario: implement the Counter Remote Controlled Improvised Explosive Device (RCIED) Electronics Warfare (CREW) Duke Version 3 on the M1 and M2 manned modules. The technical approach shall describe in detail the impacted subsystems and any required updates to their interfaces. The technical approach shall include a list of anticipated NRE tasks. Relevant PWS sections include: ID/IQ PWS: 3.3.2, 3.3.3 3.4.1, 3.4.2, 3.5.1 (excluding 3.5.1.2), 3.8, 3.9, DO 0001 PWS: 3.1.5, 3.1.6.

L.3.7. VOLUME III – Factor 3: Program Management.

The offeror’s proposed approach for Program Execution for DO 0001, and DO 0002. Relevant PWS sections that will be evaluated are provided under each Subfactor; however, Offerors may include additional material to the extent that it is necessary to describe the proposed approach for meeting the requirements being evaluated. All referenced PWS sections are inclusive of sub-paragraphs and sections (e.g. a reference to paragraph 3.1 implicitly includes all 3.1.x and other nested paragraphs). The Government may consider the impact of the Offerors proposed approach on the ability to meet all solicitation requirements, even if not being specifically evaluated, in the evaluation of each subfactor. The Offeror shall complete, and attach to Volume I, the Section L, Attachment L5 table to provide the specific PWS subparagraphs (e.g. 3.1.3.x) the Offeror deems relevant to each subfactor element in the Technical and Program Management Volumes of the Offerors proposal. Attachment L5 is for informational purposes only and will not be evaluated. The offeror shall demonstrate how they will execute the program for the following:

L.3.7.a. Factor 3 – Subfactor 1, Program Execution.

The Offeror shall provide a detailed execution plan for the management of the multiple overlapping development, production and fielding activities required for this contract. The execution plan shall include a detailed IMS for Delivery Order 2 with details for all engineering, production, and fielding activities. The execution plan shall describe staffing over the ID/IQ PoP specifically as it pertains to the initial program ramp up, including key personnel (see Section J, Attachment 6), and the management of engineering, production, and fielding personnel during the product development, production and fielding efforts. The Offeror shall submit resumes for Key Personnel as an attachment to this Volume III, Factor 3, Subfactor 1, Program Execution and shall submit Letters of Commitments for Key Personnel as an attachment under Volume IV, Section 6 – L.3.8.q . The Offeror shall describe their ability to satisfy the production capacity portrayed throughout the life of the contract. As part of the execution plan, the Offeror shall complete the sample fielding plan scenario (see Section L, Attachment L2) with resource management that minimizes site down time. Relevant PWS sections include: ID/IQ PWS: 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.13 DO 0001 PWS: 3.2, 3.3, 3.4, 3.5, 3.7

L.3.7.b. Factor 3 – Subfactor 2, Program Supportability.

The Offeror shall provide a supportability plan that addresses Diminishing Manufacturing Sources and Material Shortages (DMSMS), training, and the management of Government Furnished Information and Equipment (GFI/GFE) and Contractor Acquired Property (CAP). The supportability plan shall include impacts to operations and maintenance and new processes or tasks resulting from the introduction of new parts/components. The supportability plan shall describe their DMSMS approach and how it addresses both new items introduced under this contract as well as unmodified items. The supportability plan shall describe their process for the development of and method of distribution for training material associated with all M3 products. The supportability plan shall provide a process/plan for management and sustainment of GFI/GFE/CAP throughout the contract. Relevant PWS sections include: ID/IQ PWS: 3.5, 3.6, 3.7, 3.13

L.3.8 VOLUME IV – Factor 4: Past Performance.

Volume IV – Factor 4: Past Performance Organization.

This volume shall be organized as follows by Offerors:

1. Section 1 – Contract Description

1. Section 2 – Performance Narrative

1. Section 3 – Subcontracts

1. Section 4 – Past Performance Questionnaire

1. Section 5 – New Corporate Entities (if applicable)

1. Section 6 – Volume IV Attachments

L.3.8.a. Past Performance Definitions.

1. Recent: Recent contracts are those that are in performance and/or have been completed during the past three years since date of RFP release.

1. Relevant: Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

1. Not Relevant: Present/past performance efforts involved little or none of the magnitude of effort and complexities this solicitation requires.

1. Major Subcontractor: Members of an offeror’s overall team who are expected to perform fifty (50) percent or more of the proposed non-recurring engineering effort on any individual M3 NRE CLIN.

L.3.8.b. The Offeror and major subcontractors shall each provide a Contract Description and a detailed Past Performance Narrative on no more than three (3) contracts for the Prime and no more than two (2) contracts for each major subcontractor in MS Word as prescribed within this solicitation. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. Offerors are advised that the Government is not limited to Past Performance information submitted by Offerors in conducting Past Performance evaluations.

If any firm has multiple functions or divisions, the Offeror shall limit the records of Past Performance to those performed by the division, unit or team member submitting the offer.

If an Offeror is utilizing past performance information of affiliate/subsidiary/parent company, the proposal shall clearly demonstrate that the affiliate/subsidiary/parent company will have meaningful involvement in the performance of the contract. The Offeror shall clearly identify and describe the work that the affiliate/subsidiary/parent company will be performing under the M3 effort. Furthermore, Offerors shall explain how the past performance work specifically relates to the work that will be performed under the M3 effort. The description of the work performed by the affiliate/subsidiary/parent company will be considered in determining the relevancy of the past performance information provided for the affiliate/subsidiary/parent company. If the Offeror fails to demonstrate the affiliate/subsidiary/parent company’s meaningful involvement in the performance of the resultant M3 contract, the contract or effort will not be considered relevant and will not be considered in the evaluation of Past Performance.

When assessing past performance, the Government will focus its inquiry on the past performance of the Offeror and its proposed major subcontractors as it relates to I/O hardware/software implementation, infrastructure modernization, visual system modernization, and concurrency. These requirements include all aspects of schedule, performance, and cost, including the Offerors record of: 1) Quality of products and services, conforming to specifications, and conformance to standards of good workmanship; 2) ability to deliver functional software and define, prioritize, plan, and track incremental updates with full transparency; 3) ability to implement and maintain an asset management program to include, but not limited to, equipment, documentation, tools, and parts for full life cycle support; 4) ability to resolve technical and manufacturing problems quickly and effectively; 5) adherence to contract schedules, including the administrative aspects of performance; 6) maintaining program execution within cost; 7) Program Management to include establishing and maintaining a) a business-like concern for the interest of customers and b) management of personnel and subcontractors.

L.3.8.c. The detailed Past Performance Narrative for each contract submitted shall be organized within five sections, as follows:

L.3.8.d. Section 1- Contract Description

1. Contractor/Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a subcontractor, also provide the name and prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

1. Government contracting activity, and current address, Procuring Contracting Officer’s name, e-mail address, telephone and fax numbers.

1. Government’s technical representative/COR, and current e-mail address, telephone and fax numbers.

1. Government contract administration activity and the Administrative Contracting Officer’s name, address and current email address, telephone and fax numbers.

1. Contract Number and, in the case of Indefinite Delivery type contracts GSA contracts and Blanket Purchase Agreements, include Delivery Order numbers as well.

1. Contract Type (specific type such as Firm-Fixed Price (FFP), Cost Reimbursement (CR), Time and Material (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FFP, CR, T&M, etc.)).

1. Awarded price/cost.

1. Final or projected final price/cost.

1. Original Delivery schedule, including dates of start and completion of work.

1. Final or projected final, delivery schedule, including dates of start and completion of work.

L.3.8.e. Section 2 – Performance Narrative

Offerors shall provide a specific narrative explanation of each contract listed in Section 1, describing the general description, abbreviated scope, and objectives achieved; detailing how the effort is relevant to the requirements of this solicitation.

L.3.8.f. Each detailed Past Performance Narrative shall delineate how the past performance record links to the requirements of this RFP, as applicable, using the past performance elements identified below:

L.3.8.f.(i). Systems Engineering –

1. Ability to plan and control technical program tasks;

1. The quality and adequacy of the engineering support provided throughout all phases of contract/order execution;

1. The integration of the engineering specialties;

1. Management of interfaces, interoperability;

1. The management of a totally integrated effort of all engineering concerns to meet cost, technical performance, and schedule objectives; and

1. Ability to integrate systems engineering disciplines (systems architecture, design, manufacturing, integration and support, configuration control, documentation, test and evaluation) up-front and early in the design/development process that comply with existing architecture.

L.3.8.f.(ii). Software Development and Integration – The Offeror shall, in the Past Performance Narrative, as applicable, describe past efforts to implement common standards and development practices across multiple contractors within an established baseline and existing architecture. The narrative shall also address past software development and integration efforts with respect to 1) ease of operation; 2) ease of software maintenance; and 3) ease of future updates and modifications with the final product.

L.3.8.f.(iii). Logistics Support – The Offeror shall, in the Past Performance Narrative, as applicable, describe past efforts that demonstrate their ability to develop technical data packages, including drawings, operator/maintenance/training manuals, and special tools and test equipment that consider the Initial Spares Support List (ISSL) and the incorporation of Engineering Change Proposals (ECPs).

The Offeror shall describe past efforts of their control of the overall manufacturing process to include material control, shop floor planning and control, status and control, and factory performance (production rates for varying products, assembly of various COTS components) while demonstrating continuous improvement and meeting program quality objectives.

L.3.8.f.(iv). Technical Performance Shortcoming: For any contracts that did not/do not meet technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions.

L.3.8.f.(v). Schedule - The Offeror shall, in the Past Performance Narrative, submit information relative to their adherence to the required delivery schedule to include efforts during the Contractor Performance Assessment Reporting System (CPARS) evaluation period that contributed to or affected the schedule variance. The Offeror shall also address any variance in the original schedule, discuss causes, significance, and assess the effectiveness of corrective actions. The Offeror shall include instances of adverse actions such as the evaluation of liquidated damages or issuance of Cure Notices, Show Cause Notices, and Delinquency Notices, which are indicators of problems which may have resulted in variance to the contract/order schedule and should, therefore, be noted in the Narrative.

For any contracts that did not/do not meet original schedule requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary.

L.3.8.f.(vi). Cost Control – The Offeror shall, in the Past Performance Narrative, submit information relative to cost growth or underrun, discuss the causes and Offeror-proposed solutions for the cost overruns or underruns for completion of the effort. The Offeror shall provide narrative on innovative cost solutions gained during contract performance.

L.3.8.f.(vii). Management - The Offeror shall, in the Past Performance Narrative, annotate identification of past subcontractor challenges and the timely application of corporate resources to preclude subcontract problems from impacting overall performance. The Offeror shall also address past efforts relating to the early identification of problems, corrective action plans, proposal submittals (especially responses to change orders, Engineering Change Proposals (ECPs), or other Undefinitzed Contract Actions (UCAs), and customer satisfaction. The Offeror shall annotate their responsiveness on previous efforts as it relates to meeting contract/order requirements during the CPARS evaluation period. The Offeror shall describe their past performance approach to identifying and applying resources required to meet schedule requirements to include assigning responsibility for tasks/actions required by contract/order; and communicating appropriate information to affected program elements in a timely manner. The Offeror shall ensure that their past performance narrative describes their risk management practices, especially the ability to identify risks and formulate and implement risk mitigation plans. The Offeror shall include examples of previous integration and coordination of activities that reflect those required by the Integrated Master Schedule. The Offeror shall also address previous efforts to select, retain, support, and replace key personnel.

L.3.8.g. Section 3 – Subcontracts All major subcontractors shall be identified. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government PWS subparagraph number. Section 3, Subcontracts, shall not exceed three pages. Written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror shall be included as an attachment under Section 6, L.3.8.p, Volume IV Attachments. In addition, the Offeror shall submit signed and binding Contractor Team Arrangement Agreements for all major subcontractors as an attachment under Section 6, L.3.8.o, Volume IV Attachments.

L.3.8.h. Section 4 – Past Performance Questionnaire. For all contracts identified in Section 1, Contract Descriptions, a Past Performance Questionnaire must be completed and submitted.