W900KK-17-R-0015_Amendment_01.pdf.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this Amendment is to reflect an update to dates in Sections L.1.16, L.1.17, and L.12.0.

1. CONTRACT ID CODE PAGE OF PAGES

1 24

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 21-Mar-2017

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W900KK-17-R-0015

X 9B. DATED (SEE ITEM 11)

14-Mar-2017

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

21-Mar-2017

CODE

U.S. ARMY PEO STRI ACQUISITION CENTER

ATTN: KOC/OPS

12350 RESEARCH PARKWAY

ORLANDO FL 32826

W900KK 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W900KK-17-R-0015

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L: INSTRUCTION TO OFFERORS

Section L - Instructions, Conditions and Notices to Bidders

PROPOSAL SUBMISSION

L.1.0. INTRODUCTION

L.1.1. The SE Core source selection process will utilize a written proposal including a Sample Task. The intent of Sample Task is to supplement the management and technical volumes of the written proposals to allow the offeror to demonstrate practical understanding of SE Core requirements and demonstrate effective and application of the proposed management and technical approach.

L.1.2. Hard Copy/Electronic Submission: Volumes I – VI proposals are due in one original hard copy and three electronic (via CD) copies by 1:00 PM, Eastern Time on April 24, 2017 to the POC listed in paragraph L.1.3 below. Please note that telegraphic or facsimile offers are not authorized for this solicitation. See Table L-1 for additional details pertaining to proposal submission.

In accordance with FAR 15.208(b), failure of an Offeror to submit its proposal in accordance with the date and time deadlines or the manner specified in the solicitation may result in a determination that the proposal is “late” and ineligible to be considered for award.

L.1.3. The point of contact (POC) for this solicitation for Offerors is Ms. Michelle D. Williams, Contract Specialist.

Army Contracting Command (ACC) - Orlando ATTN: Michelle D. Williams, Contract Specialist

W900KK-17-R--0015

12211 Science Drive Orlando, FL 32826-3275 Telephone number: 407-384-5296 E-mail: michelle.d.williams1.CIV@mail.mil

L.1.4. The alternate point of contract (APOC) for this solicitation for Offerors is Ms. Terri Harvey

ATTN: Terri Harvey, Contract Specialist Solicitation #W900KK-17-R-0015 12211 Science Drive Orlando, FL 32826-3275 Telephone number: 407-208-3338 E-mail: terri.l.harvey10.civ@mail.mil

L.1.5. The Procurement Contracting Officer (PCO) for this solicitation is Robert M. Minjack

ATTN: Robert Minjack, PCO Solicitation #W900KK-17-R--0015 12211 Science Drive Orlando, FL 32826-3275 Telephone number: 407-384-3803 E-mail: robert.m.minjack.civ@mail.mil

L.1.6. All proposals must clearly and convincingly demonstrate the Offeror has a thorough understanding of the requirements and associated risks, and is able, willing, and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for all requirements. Statements that the prospective Offeror understands, can, or will comply with the specifications, and statements paraphrasing the requirements or parts thereof are considered inadequate and unsatisfactory. Mere reiteration of the requirement or standard reference material is discouraged.

L.1.7. Any data previously submitted in response to another solicitation, whether submitted to ACC-

Orlando, the Program Executive Office for Simulation, Training and Instrumentation (PEO STRI) or another agency will not be considered 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.

L.1.8. The Offerors shall ensure that each proposal volume submitted contains 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 of the Request for Proposal (RFP) and the evaluators for one volume may be different than the evaluators of another volume. The only exceptions are that:

a) Evaluators of the Management Volume WILL have access to the Technical Volume in support of their evaluation of the Management Volume.

b) Evaluators of the Technical Volume WILL have access to the Management Volume in support of their evaluation of the Technical Volume.

L.1.9. If the data is not contained in the appropriate volume of the proposal it may not be evaluated. For example, if the Sample Task response is submitted under the Past Performance volume rather than the volume specified, the proposal may be evaluated as if no Sample Task response was submitted at all.

L.1.10. NOT USED AT THIS TIME

L.1.11. The proposal and any requested updates shall be valid for not less than 300 calendar days from the proposal due date.

L.1.12. The Government reserves the right to request additional information (for purposes of clarification only) after receipt of Offeror’s response to the RFP.

L.1.13. Proposals shall not contain classified information.

L.1.14. Security Clearance Requirements: Contractor employees working under the resultant contract must comply with the security requirements of the contract as documented in the RFP.

L.1.15. Offerors may submit a request for additional Government Technical Data as necessary to support proposal preparation. In order to obtain this Government Furnished Information (GFI)

Offeror shall complete the Distribution Agreement (DA), included as Attachment 45 to the solicitation, and email to leonard.l.hobbs2.ctr@mail.mil. The email shall also include the following:

a) The Offeror’s preference for receipt of the technical data package (pick-up from

Government location or Government will mail the package).

b) If the Offeror prefers the package to be mailed, include a point of contact, phone number and address to which the package will be mailed.

The Government will provide for pick-up or will mail the technical data package within five business days from receipt of email request including all of the above, to the extent practical.

L.1.16. Questions regarding this solicitation shall be submitted by electronic mail to the POC identified in paragraph L.1.3, L.1.4, and L.1.5 with the solicitation number in the subject line. The Government will answer all questions through the issuance of a solicitation amendment prior to the deadline for final proposal submissions provided those questions are received by 3:30 PM, Eastern Time on the 10th calendar day after RFP release. Questions received after this date may not be answered prior to proposal submission deadline. The Government does not anticipate that the closing date for receipt of offers will be extended. The Government will answer all questions via FedBizOpps prior to the proposal due date. The Government will post the answers, without Offeror identification, to the FedBizOpps website for this solicitation.

Offeror shall not make any changes to the solicitation. Any objections to the terms and conditions of the solicitation should be addressed to the PCO prior to the closing date and time for proposals.

If the proposal takes exceptions to the terms and conditions of the solicitation, all exceptions shall be denoted in a cover letter to the proposal; however, exceptions to the solicitation taken in the proposal may result in the offer being unacceptable.

L.1.17. The following milestones apply to this acquisition:

Release of Draft RFP 22 Nov 2016 Deadline for Submission of Questions on Draft RFP 09 Dec 2016 Release of Final RFP 14 Mar 2017 Deadline for Submission of Questions on Final RFP 24 Mar 2017 Target for Answers to Questions 03 Apr 2017 Deadline for Submission of Past Performance Questionnaires 04 Apr 2017 Proposals Due 24 Apr 2017 Contract Award 06 Nov 2017

L.2.0. PROPOSAL MAILING/DELIVERY

L.2.1. Submission of telegraphic or facsimile offers is not authorized for this solicitation. The outside shipping container shall be marked with the RFP Number. Proposals shall be mailed/delivered as follows:

ACC-Orlando ATTN: Ms. Michelle D. Williams

W900KK-17-R-0015

12211 Science Drive Orlando, FL 32826-3276

If the proposal/final proposal revision is hand carried, the Offeror shall notify the PCO and Contract Specialist by email 48 hours in advance of its intent to hand deliver its proposal. The email must include the name of the organization, the name and phone number of the individual delivering the proposal, and the make, model, and license plate number of the delivery vehicle.

L.2.2. For hand carried proposals, the Offeror shall obtain a Proposal Receipt Form from the POC identified in paragraph L.2.1 above and deliver the completed form with the proposal. The POC will date/time stamp the original of the form, annotate the number of boxes received and sign in the “Signature of Contract Specialist” portion of the form. This information will also be annotated on the copy that will be provided to the Offeror. The Contract Specialist’s signature only denotes the receipt of the sealed proposal. They are not responsible for the proposal contents inside the sealed proposal. In the event the POC in L.2.1 is unavailable to receive the Offeror’s hand carried proposal, the PCO or an authorized individual approved by the PCO will be assigned.

L.3.0. PROPOSAL FORMAT

L.3.1. Paper Copies - Binding. Offerors shall submit an original paper copy of all volumes in standard size 3-ring binders that will facilitate the insertion of change pages and additional information the Offeror may be required to provide during the source selection process.

L.3.2. Paper Copies - 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 shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in Microsoft (MS) Word 2013. MS Word Files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right - 1” Gutter – 0” From Edge – Header, Footer - 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

The following additional restrictions apply:

Each paragraph shall be separated by at least one blank line. Page orientation shall be portrait style in an easily readable font with a size of no smaller than 10 point.

Tables or figures may be printed on fold-out sheets, which shall not exceed 11 x 17 inches. Font size for tables and figures shall be no smaller than 8-point and may use landscape orientation. Fold-out sheet count limitations for the Management and Technical Factors are provided in Table L-1.

Pages shall be numbered sequentially by volume and marked with the Offeror’s name and any applicable data use restrictions in the header/footer area of each page.

All printed pages shall contain the phrase: “SOURCE SELECTION INFORMATION" (printed or stamped) in addition to the FAR 3.104 proprietary data notice.

L.3.3. Electronic File Packaging. Offerors shall submit each proposal volume on a separate compact disc

(CD). CDs shall be appropriately marked with the Offeror’s name and address, volume identification, and distribution restrictions. All files on each CD shall be directly supported by Microsoft Office 2013 and verified to be free of any virus or malware. All files shall be clearly identified with a filename appropriate to the content (e.g., Volume-1_Management_Appendix-A).

L.4.0 PROPOSAL VOLUMES

The proposal must consist of Volumes I through VI as set forth in Table L-1.

Table L-1. Proposal Volume Organization

VOLUME

TITLE

COPIES

SIZE LIMITS

I Management 1 Paper Submission**

3 Electronic Submissions*

Volume I not to exceed 30 total pages including the Sample Task response. This total includes a maximum of 5 fold-outs.

II Technical 1 Paper Submission

3 Electronic Submissions*

Volume II not to exceed 25 pages total. This total includes a maximum of 5 fold-outs.

III Past Performance 1 Paper Submission

3 Electronic Submissions*

Volume III not to exceed 25 pages plus 2 pages for each major Subcontractor (as defined in L.7.1.1) total

(No more than 5 recent, relevant programs for the Prime Offeror and no more than 3 for each relevant Subcontractor Offeror).

IV Small Business Participation

1 Paper Submission

3 Electronic Submissions*

Volume IV

Unlimited relevant and required pages, V Cost/Price 1 Paper

3 Electronic Submissions*

Volume V

Unlimited relevant and required pages.

VI Administrative Information

1 Paper

Volume VI not to exceed 30 pages total

Small Business Subcontracting Plan will be included asas an Appendix to Volume VI, and is not considered in the 30 page count.

This piece of the volume maymay include Unlimited relevant and required pages.

VII Cross-Reference Matrix

1 Paper

Volume VII

Unlimited relevant and required pages.

*Electronic Submission shall be on an appropriately marked compact disc (CD), as per paragraph L.3.3.

**Paper submission is not required for the Sample Task Updated DCR, which will be provided electronically in Google Earth Pro™ *Keyhole Markup Language (KML).

L.4.1. Page Count: Those pages that exceed the page counts in Table L-1 for each volume or attachment will not be evaluated. PAGE COUNTS DO NOT INCLUDE THE FOLLOWING ITEMS, however, offerors are cautioned to include only necessary information required to meet RFP content requirements and support their proposal:

1. Required Appendices that are explicitly requested in the proposal instructions below, which are to be provided as Appendices the volume (e.g., Project Schedules, Staffing Plans, Updated Database Content Requirements (DCR) (provided as a Google Earth Pro™ Keyhole Markup Language (KML) electronic format only), Bill of Material and Travel for the Sample Task, Small Business Subcontracting Plan, etc.).

2. Cover Sheet, Table of Contents, Glossary, List of Figures and Tables, Lists of Acronyms (if used), section separators, and any blank pages marked “Not used”.

3. Executed Contract Attachments (e.g., completed Sections B, G, J, Attachment 46, etc.).

4. Resumes and Letters of Commitment for Key Personnel.

5. Volume Summaries. A Volume Summary shall be provided for each Volume. The

Volume Summary shall be no more than one page that shall not count against the Volume page count and will not be used for evaluation purposes.

L.4.2. Content Requirements: All information shall be confined to the appropriate volume. The Offeror shall confine submissions to essential matters, sufficient to define the proposed approach and provide adequate basis for evaluation. Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. Each volume of the proposal shall consist of a Table of Contents, Volume Summary, the required content, and required Appendices. The Volume Summary Section shall contain a brief abstract of the Volume. Proprietary information shall be clearly marked. Cost/Price information shall be contained ONLY in the Cost/Price Volume except for the specific cost information required in the Small Business Participation and Administrative Information. The Offeror’s Cost/Price proposal shall contain a face page containing the information specified in FAR 15.408, Table 15-2, titled “Instructions for Submitting Cost/Pricing Proposals when Cost or Pricing Data are required.”

L.4.3. Failure of an Offeror to provide all requested proposal information may result in a determination that an Offeror is ineligible to be considered for award.

L.5.0. VOLUME I – MANAGEMENT

The Offeror’s Management Volume shall address subfactors A, B and C for this factor. The Offeror should consider the relative order of importance of the subfactors.

L.5.1 Sub-factor A: Program Management: The Offeror shall clearly demonstrate their approach to effectively plan, organize, staff, control, and lead to meet contract requirements. This subfactor rating will be determined based upon evaluation of the following information which IS NOT separately rated. (PWS 5.1)

a. Project Organization. The Offeror shall describe their proposed project organization depicting and describing the Offeror’s key personnel, internal project teams, and their relationships with supporting corporate organizations, the Government, Confederate programs, and subcontractors/suppliers (PWS 5.1.16). The Offeror shall identify key personnel, as indicated in PWS 1.6.8. A one-page resume shall be provided for each of the key personnel as an Appendix to this Volume. Letters of Commitment shall be provided with the resume for all key personnel.

(PWS 1.6.8)

b. Status Reporting. The Offeror shall describe how the Government Program Office will be provided real time (weekly) visibility into status of terrain generation tasks. This shall describe and provide example graphics of the Offeror’s depiction of historical progress including planned versus actual labor, estimate to complete plans and milestones for overall database generation efforts – with a breakout of data for the most costly terrain generation tasks (e.g., vector editing, map generation, static model development, sourcing, runtime database generation, integration and testing). (Reference PWS 5.1.16, 5.5.1.4)

c. Project Schedule. The Offeror shall provide a Project Schedule for the Base Year and OY 1 for each CLIN – specifically including each ITE and constructive database and each database maintenance request (DMR) deliverable. Key tasks, milestones, and external dependencies shall be depicted. The required Project Schedule shall be provided as an Appendix to the Management Volume in both hard copy and Microsoft Project 2013. The level of detail in this schedule shall be strictly limited to that appropriate to the Government Program Office (specifically excluding detail that will not enhance the Government’s understanding of the schedule). (PWS 5.1.1, 5.1.2)

d. Staffing Plan. The Offeror shall provide a staffing plan for all priced CLINs in the Base Year and Option Years 1 through 4. This plan shall depict staffing levels by month, by function (e.g., program management, network maintenance, requirements definition, sourcing, vector editing, modeling, map generation, integration & test, configuration management, quality assurance, etc.)

and by Offeror labor category. The Offeror shall describe – and justify – significant variances between their proposed staffing plan for each year and the “Approximate Workload Data” provided in PWS 7.3. The Offeror shall provide a description of the offeror’s proposed labor categories by experience, education, and qualifications/certifications, and crosswalk these to the labor categories in PWS 7.3. The Offeror shall address significant differences in labor effort proposed versus PWS 7.3. The Offeror shall convincingly demonstrate that they have not underestimated the required work and that the proposed work is based on the Offeror’s use of approved processes. The Offeror shall describe any expected savings in staffing resulting from approved process changes over the course of the proposed contract. The Offeror shall describe how any such savings will be applied as additional labor to allow increases in extents or complexity of the required databases over time. The required staffing matrix – and supporting labor category descriptions and crosswalk – shall be provided as an Appendix to the Management Volume in both hard copy and Microsoft Excel 2013.

e. Surge Capability. The Offeror shall describe their proposed approach to rapidly and efficiently respond to meet “surge” staffing requirements (PWS 5.5.1.8, 5.5.1.15).

L.5.2 Sub-factor B: Sample Task – Database Request Response (DBRR): The Offeror shall provide a database request response (DBRR) in response to the Sample Task preliminary database content requirements (DCR) that has been provided as RFP Attachment 43. This Sample Task shall demonstrate the Offeror’s:

(1) Understanding of SE Core requirements across all domains (PWS 5.2),

(2) Understanding and application of the SE Core SE generation process (PWS 5.5),

(3) Agility and innovation in adjusting resources and applying appropriate trade-offs as necessary to satisfy program cost/schedule/technical requirements and minimize impact on mission tasks (PWS 5.1, 5.2, 5.5).

(Note: The Government does not plan to answer RFP questions concerning the Sample Task, but expects Offerors to handle issues/ambiguities as they deem appropriate.) The subfactor rating will be determined based upon evaluation of the following information which IS NOT separately rated.

a. Sample Task/Scenario. The Offeror shall assume the following relative to this Sample Task:

(1) Offeror is executing the Base contract with no other options except the Phase-In, on cost and on schedule as proposed in response to this RFP.

(2) At seven months after prime contract award, the Government provides the Preliminary DCR at Attachment 43, requesting information leading to an additional integrated training environment (ITE) database, requiring a database request response (DBRR) to address the plan to deliver the required ITE database without reducing the required 2 ITE and 3 constructive databases in the Base Year or OY 1.

(3) This new ITE database is contractually authorized by the Government at 9 months after prime contract award with a requirement for database delivery to ALL CONFEDERATES to be completed, and change control board (CCB) release NLT 12 months after exercise of the change.

(4) No new System Engineering/Capability Development or Capability Maintenance tasks will be authorized to support this new database.

b. Sample Task/DBRR Content. The Offeror shall prepare and deliver a DBRR for this Sample Task with the Management Proposal. The DBRR shall provide a summary of labor hours by function, labor category and month; and any material and travel associated with your proposed approach. Cost and Pricing Data shall NOT be submitted. The Offeror’s DBRR shall include:

(1) Assumptions. The Offeror shall provide the list of assumptions including any corrections or interpretations necessary to the DCR. The Offeror shall consider work that may be available from prior or parallel efforts in assessing the required labor and schedule.

(2) Updated DCR. The Offeror shall provide an updated DCR in the form of a Google Earth

Pro™ *Keyhole Markup Language (KML) file incorporating all proposed corrections, updates, and changes as an electronic Appendix to this Volume. The updated DCR shall retain the basic structure as provided in the RFP. This updated DCR shall form the basis for the DBRR and shall constitute the offeror’s recommended practical solution/final requirements for this database while maintaining existing Base Year and OY1 deliveries.

In a real-world case, this DCR would be subject to further negotiation and finalization with the Government.

(3) Trade-off Issues, Concerns, and Recommendations for Changes/Adjustments to the DCR.

The Offeror shall provide a description of issues, concerns, and proposed changes/updates to the DCR to correct problems/ambiguities/errors in the DCR, address resource and schedule constraints, and to enable on-time delivery. The Offeror shall describe trade-offs that led to each recommended change to the DCR and a description of requirement trades and details concerning the proposed approach (such as handling the “surge” for certain labor types) that may accommodate the limited schedule and provide efficient application of resources while satisfying critical confederate requirements – without impacting delivery of the 2 ITE and 3 constructive databases and DMR efforts prior to the end of the Base and OY1 period of performance. The Offeror shall assess source material data for adequacy.

(4) Project Schedule and Staffing Matrix. The Offeror shall provide a Project Schedule for the Sample Task database as an Appendix to this Volume, including changes to the Base Year and OY 1 schedules. The Project Schedule shall describe all key events and dependencies on the Government and/or confederates (e.g., decisions, data, access, testing, etc.). Detail not important to the Government’s understanding of the Offeror’s approach is not desired. Any changes to the baseline Project Schedule for Base Year and OY 1 shall be clearly described. The Offeror shall provide a staffing matrix to show labor requirements loading by schedule month by functional area (systems/requirements, sourcing, vector editing, test, etc.) for the Sample Task database. Any changes or adjustments to the baseline staffing matrix for Base Year and OY 1 shall be clearly described. The Sample Task Staffing Matrix shall be provided as an Appendix to this Volume in hard copy and Excel. The Offeror shall provide a narrative description of this staffing plan depicting trade-off results and describe how the proposed approach accommodates the “surge” for certain labor types by adding staff or changing the schedule to minimize loading on critical skill types to that will accommodate the limited schedule and resource constraints. The offeror shall provide an unpriced Sample Task Bill of Material (BOM) for any additional material and a list of any travel that will be required to support the Sample Task. This BOM and travel list shall be provided as an Appendix to this Volume. The offeror shall describe schedule and staffing impacts on the Base Program and OY 1 that result from the Sample Task ITE database. The Offeror shall describe how impacts are minimized on the Base Year and OY 1 mission efforts.

(5) Risks. The Offeror shall summarize risks and risk mitigation for this Sample Task in light of its co-occurrence with the required Base Year and OY 1 mission databases and DMR efforts.

L.5.3 Sub-factor C: Cost Control: The Offeror shall describe the processes and procedures that will be used to ensure cost effective execution of the SE Core Program in accordance with PWS 5.1. The subfactor rating will be determined based upon evaluation of the following information which IS NOT separately rated.

a. Cost Control and Visibility. The Offeror shall describe the proposed approach to controlling program costs and the Offeror’s approach to providing timely visibility to planned versus actual costs to the Government Program Office for items identified by Government of to be of particular interest (including but not limited to., ITE and constructive databases, a particular capability development task, etc.). The Offeror’s extension of the Government’s Contract Work Breakdown Structure (CWBS) as an Appendix to the Management Volume. (PWS 5.1, 5.1.3, 5,1,4, 5.1.6, 5.2.1, 5.3, 5.5.1.4, 5.5.1.15)

b. Earned Value Management System (EVMS). The Offeror shall provide the status of their EVMS validation from Defense Contract Management Agency (DCMA) (DFARS 252.234-7001).

The Offeror’s approach to prevent loss of program agility (e.g., avoid delays in starting newly authorized changes while awaiting update of the EVMS records) and excessive costs associated with EVMS shall be specifically described. The extent to which Earned Value Management System (EVMS) or other cost reporting requirements will be flowed down to primary subcontractors shall be explained. (PWS 5.1.4, 5.5.1.15)

c. Subcontract Cost Control. The offeror shall describe the type contract (FFP, CPFF, T&M, etc.) for each subcontractor with considerable subcontracted labor content, including all those named in the Small Business Volume. (PWS 5.1.5, 5.1.7, 5.1.16.1)

d. Procurement. The offeror shall describe their approach to ensure timely and cost-effective procurement of materials and software in accordance with PWS 5.8. The offeror shall describe how their procurement system maintains integrity and provides best value for the Government.

(PWS 5.8)

L.6.0 VOLUME II – TECHNICAL

The Offeror’s Technical Volume shall address the subfactors A, B and C for this factor. The Offeror should consider the relative order of importance of the subfactors.

L.6.1 Sub-factor A: Synthetic Environment (SE) Generation Process: The Offeror shall describe their proposed implementation of the synthetic environment generation process in response to PWS 5.5 as follows. The subfactor rating will be determined based upon evaluation of the following information which IS NOT separately rated.

a. Synthetic Environment (SE) Generation Process Description. The Offeror shall describe how they will implement the approved SE Core processes for generation of ITE and constructive DB, including key processes and milestones. (PWS 5.5)

b. Facilities and Infrastructure. The Offeror shall identify the facilities and infrastructure they propose to meet the SE Core requirement. (PWS 4.1, 5.1.14.1) The Offeror shall provide the following:

(1) A facility diagram depicting the physical location and layout of the facilities proposed for execution of the program.

(2) Diagram(s) showing the physical and logical design of the proposed SE Core computing resources, including clear identification of that which is government versus contractor-owned.

(3) Identification of hardware, software, and facilities infrastructure that will be provided by the Offeror – beyond Bill or Material items and GFE/GFI – such as deskside computers, telephone system, commercial internet access, facility/infrastructure utilities, etc.

c. Vector Editing Rates. The Offeror shall describe and explain the metrics they propose for the Government’s assessment of vector editing (PWS 7.1, PRS#5) in each year of performance. The Offeror shall provide rationale explaining why those rates are appropriate, challenging, and achievable. (PWS 5. 5.1.4)

d. Bill of Materials. The Offeror shall provide their proposed Bill of Materials to supplement GFE/GFI for each year of performance as a separate attachment to the Technical Volume.

Recurring license renewals shall be clearly identified. Technical equipment refresh shall be clearly identified. (PWS 5.1.14.7)

L.6.2 Sub-factor B: System Engineering, Capability Development, Capability Maintenance: The

Offeror shall describe their system engineering approach in response to PWS 5.2, their capability development approach in response to PWS 5.3, and their approach to Capability Maintenance in response to PWS 5.4 to describe the following. The subfactor rating will be determined based upon evaluation of the following information which IS NOT separately rated.

a. Capability Development. The Offeror shall describe how they will identify, gain development approval for, develop, and incorporate new technologies including new hardware and software products, tools, and processes to improve the cost and schedule efficiency for terrain database and model production and integration, and improve correlation of the common integrated training environment across the full spectrum of live, virtual, and constructive training applications. The Offeror shall outline specific innovations/improvements/updates they plan to introduce to improve the SE Core program and understanding that they will gain government approval prior to implementing any such changes. (PWS 5.3) The Offeror shall describe how software documentation and technical data developed under this contract with at least Government purpose rights in accordance with DFARS 252.227-7013 and -7014. (PWS 1.6.12).

b. Capability Maintenance. The Offeror shall describe how they will maintain and update program hardware, software, and infrastructure to maintain concurrency/supportability and support cybersecurity updates. The Offeror shall describe their approach to maintain the program cybersecurity authority to operate (ATO) over the life of the contract based on experience with similar projects. The Offeror shall describe their capability to maintain Virtual-OneSAF in coordination with affected confederates. (PWS 5.2.6, 5.4)

L.6.3 Sub-factor C: Transition Phase-in/Phase-out. (PWS 5.10) The subfactor rating will be determined based upon evaluation of the following information which IS NOT separately rated.

a. Phase-in. The Offeror shall describe their proposed Phase-in plan in accordance with PWS

5.10.1. The Offeror shall describe how the Offeror will staff the project with personnel who can quickly and efficiently assume project responsibilities. The Offeror shall describe how the specified synthetic environment and model generation process and progress on system engineering, capability development, and capability maintenance will be maintained without interruption exceeding 90 days, while in-phasing into the contract from the incumbent, addressing staffing/training, infrastructure, GFE/GFI, cybersecurity, and facilities. This shall explicitly address how the Offeror will staff with personnel suitably trained and able to execute the existing processes within the allowed 90-day transition. The Offeror shall specifically describe how they plan to assume responsibility for and complete the two ITE and three Constructive Databases prior to end of the fiscal year. Include an Integrated Master Schedule (IMS) for Phase-In showing key In-Phasing events – including dependencies on the Government and Incumbent contractor. The Offeror shall specifically address plans to ensure the required cybersecurity status.

b. Phase-out. The Offeror shall describe their proposed Phase-out plan in accordance with PWS

5.10.2. The Offeror shall briefly describe how they will Phase-out the program to a follow-on contractor in a manner to ensure that specified synthetic environment generation process and progress on system engineering, capability development, and capability maintenance can be maintained until handover without interruption within the specified period of 90 days. The Offeror shall specifically address plans to ensure transfer of cybersecurity status.

L.7.0 VOLUME III – PAST PERFORMANCE

Offerors shall prepare and submit a Past Performance Volume containing no more than the number of pages outlined in Table L-1. This volume shall be organized into the following sections:

L.7.1 Past Performance Volume Content:

L.7.1.1 Section 1 – Past Performance List. This section shall include a list of all Government awarded contracts to the business unit or division proposed to perform this effort over the past three (3) years prior to the closing date of the solicitation that are relevant to the efforts required by this solicitation. Relevant efforts are defined as efforts involving work on Defense simulation systems that include content such as that required on this program. This may include work where the relevant business unit or division was a prime or major subcontractor. Data concerning the prime Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. A major subcontractor is defined as one whose subcontract is for more than 15% of the total proposed price and/or provide critical services. Critical services are those that if not performed can negatively impact meeting the contract requirement(s) to the point of failure.

L.7.1.2 Section 2 – Contract Descriptions. The Offeror shall provide detailed information concerning past performance on a maximum of five (5) most recent and relevant programs that are most representative of the Offeror’s proposed performance on the SE Core Program. A similar list shall be prepared for each major subcontractor describing a maximum of three (3) most recent and relevant programs for that subcontractor. This section shall include the following information on each program:

1. Contractor/Subcontractor place of performance, CAGE Code and DUNS

Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

2. Government contracting activity, and current address, Procurement Contracting Officer's name, e-mail address, telephone and fax numbers.

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

4. Government contract administration activity and the Administrative Contracting Officer's name, and current e-mail address, telephone and fax numbers.

5. Government contract administration activity's Pre-Award Monitor's name and current e-mail address, telephone and fax numbers.

6. Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Task Order Numbers also.

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

8. Awarded price/cost.

9. Final or projected final price/cost.

10. Original delivery schedule, including dates of start and completion of work.

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

12. Narrative explanation describing the objectives achieved and detailing how the effort is relevant to the requirements of this solicitation.

13. Provide a brief explanation of the reason(s) for problems or shortcomings that occurred during contract performance and any corrective action(s) taken to avoid recurrence. Address any failures to meet the proposed delivery schedule, requirements for Requests for Deviation and Requests for Waiver with respect to causes and corrective actions, and any Cure Notices or Show Cause Letters received along with a description of any corrective action implemented.

14. Provide a summary description of how the Offeror tracked, managed, and closed discrepancies during contract execution

L.7.1.3 Section 3 – Subcontracts. Offerors shall provide an outline of how the effort required by the solicitation 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.

L.7.1.4 Section 4 – New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and key personnel. However, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

L.7.1.5 Performance Risk Assessment Questionnaire. For each of the maximum five (5) contracts and three (3) major subcontracts identified in Section L.7.1.2, the Government requests completion of the Performance Risk Assessment Questionnaires provided as Attachment 50 to the RFP. This questionnaire should be submitted to their customer Program Manager, Lead Engineer, and Procuring Contracting Officer (or their representative) for completion and returned as follows:

1. The Offeror shall complete Part A of the Performance Risk Assessment Questionnaire and e-mail the questionnaire to each of the customer representatives.

2. The customer representatives shall be instructed to electronically complete Part B of the questionnaire and e-mail the entire questionnaire to the POC specified in the RFP by the date specified in the RFP.

3. The Offeror shall provide a list of all the customer representatives that were sent a questionnaire by email to the POC specified in the RFP. The Government must receive this list within 18 calendar days after release of the RFP. This list of customer representatives shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number;

Government Agency; Customer Representative Last Name, First Name; Title;

Telephone Number; E-mail Address; Date E-Mailed to the Customer Representative (month/day).

L.8.0 VOLUME IV – SMALL BUSINESS PARTICIPATION

This volume shall consist of the Offeror’s Small Business Participation Plan. It shall provide the following information:

L.8.1 Large Business Offerors are required to certify that they will perform in a manner that small business participation shall be at least 28% of the total contract value in each twelve months of performance beginning upon contract award. Each Offeror shall submit a Small Business Participation Plan as Appendix A (for large business this Participation Plan is in addition to the Subcontracting Plan required by Clause 52.219.9) to this Volume that shall clearly demonstrate a viable plan for meeting or exceeding the required minimum level of small business participation as follows:

Small Business: 28% of the total contract value;

Small Disadvantaged Business: 7% of the total contract value;

Woman-Owned Small Business: 5% of total contract value;

Historically Underutilized Business Zone (HUB Zone) Small Business: 3% of total contract value;

Service Disabled Veteran Owned Small Business: 3% of the total contract value

The Small Business Participation Plan shall contain information in accordance with DFARS

215.304 that shall include the following:

L.8.1.1 Type of Business of Prime Contractor: Check all applicable boxes

{ } Large { } Small (also check type of Small Business below) { } Small Non-Disadvantaged Business { } Small Disadvantaged Business { } Woman-Owned Small Business { } HUB Zone Small Business { } Veteran Owned Small Business { } Service Disabled Veteran Owned Small Business

L.8.1.2 Total Contract Value: (Include the base period, first option, second option, third option, fourth option and one half the fourth option) $___________

L.8.1.3 Dollar Value of your participation as a Prime Contractor: $__________

L.8.1.4 Dollar Value and Percentage of Total Contract Value of Subcontracts Planned For:

Dollar Percentage of Total Value Contract Value

Large $________ %_________

Total Small $________ %_________

Small Non-Disadvantaged $________ %_________

Small Disadvantaged $________ %_________

Woman-Owned Small $________ %_________

HUB Zone Small $________ %_________

Veteran Owned Small $________ %_________

Service Disabled Veteran $________ %_________ Owned Small

Each participation percentage above shall be accompanied by detailed supporting documentation regarding the individual commitments. Detailed explanations shall also be provided when the percentages fall short of the DOD goals. Offerors are to provide justification for any goals resulting in zero percent.

A short description of the specific services to be provided or components to be produced and the nature of complexity by each small business; rationale supporting small business selection(s); and the estimated total dollars for each product or service. Complexity is defined as- level of involvement for development/performance of components/services provided by the Small Business Concerns.

NOTE: The sum of the dollar values and percentages of Small Non-Disadvantaged and Small

Disadvantaged should equal the entries for Total Small. However, the sum of all the percentages under Section L.8.1.4 need not equal 100% since the prime is not included and individual subcontractors may be counted towards more than one category. All percentages should use TOTAL CONTRACT VALUE as a baseline.

L.8.1.5 List principal supplies/services (be specific) to be subcontracted to:

Name of Company Type of Service/Supply Large:

Small:

Small Non-Disadvantaged:

Small Disadvantaged:

Woman-Owned Small:

HUB Zone Small:

Veteran Owned Small Business:

Service Disabled Veteran Owned Small:

NOTE: For purpose of subcontracting, Historically Black Colleges and

Universities/Minority Institutions (HBCUs/MIs) are considered as disadvantaged and should be broken out separately.

L.8.1.6 Prior Performance Information: Provide any information substantiating the Offeror’s track record of utilizing small business on past contracts. For Large Businesses: include ACO rating and SF 295 Information. For Large and Small businesses: provide descriptive information for all small business categories. Any information concerning long-term relationships with Small Business subcontractors, such as mentor-protégé relationships, should be provided.

In addition, Offerors are to provide description of performance, over the past three (3) calendar years as of the closing date of the solicitation, in complying with the requirements of FAR 52.219-8, Utilization of Small Business Concerns to include description and available documentation of the methods employed to promote small business utilization, the internal methods used to monitor such utilization, and any other information substantiating the Offeror will satisfy the requirements of FAR 52.219-8. Large business Offerors are to provide a description of complying with the requirements of FAR 52.219-9, Small Business Subcontracting Plan, for the past three calendar years, including documentation of accomplishment of the goals such as copies of SF 295 or Summary Subcontract Report (SSR) using the Electronic Subcontracting Reporting System (eSRS). Large businesses that have never held a contract incorporating 52.219-9 shall so state.

L.8.1.7 Extent of Commitment: Provide documentation regarding enforceable commitments to utilize any Small Business category, as defined in FAR Part 19, as subcontractors.

L.8.2 Each Large Business Offeror shall additionally provide a Small Business Subcontracting Plan as an Appendix to Volume VI - Administrative that contains all the elements required by FAR 52.219-9. (This plan shall be submitted separately from the Small Business Participation Plan information required above, which applies to both large and small businesses.) The Small Business Subcontracting Plan is not a requirement for evaluation in source selection, but rather a requirement for award to a large business and will be incorporated into any resultant contract, therefore shall be submitted in VOLUME VI – ADMINISTRATIVE.

L.9.0 VOLUME V – COST (for cost CLINs) / PRICE (for FFP CLINs)

Offerors shall submit the basis of estimates and include other than cost or pricing data (CLIN-by-CLIN) in support of all CLINs. In addition, Offerors shall submit a summary of the proposed cost for each CLIN, as well as the total price including fee. Details of cost proposal will be submitted separately in the cost proposal section below. Since the preponderance of this contract is CPFF, the Offeror shall show their rationale for fee percentage for those applicable CLIN’s. No fee shall exceed FAR guidelines for maximum fee IAW FAR 15.404-4(c)(4)(i)(A).

Offerors shall prepare and submit a Cost/Price Volume containing the following information.

L.9.1 Breakdown.

A breakdown of cost data is required under this solicitation as set forth below.

L.9.2 Cross Reference.

The Offeror shall provide a cross-reference between the Performance Work Statement (PWS), WBS and CLINs/SLINs. The Offeror’s cost proposal (for all cost CLINs) shall mirror the structure of the proposed Project Plan and Program Schedule.

L.9.3 Unbalanced Pricing.

Offerors shall avoid presenting unbalanced pricing information. Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more price…