Enterprise Business Systems - Convergence (EBS-C) Prototype Project Opportunity Notice (PPON)

AWARD NOTIFICATION: The following Agreements awards were made for EBS-C Phase 1 Prototype Development Agreement Number: W519TC-23-9-2054- Telesto Group, LLC, McLean, VA Agreement Number: W519TC-23-9-2055 - IBM Corp, Reston VA Agreement Number: W519TC-23-9-2056- Accenture Federal Services, LLC, Arlington, VA Contract Value: Not to exceed $7.5M **** The purpose of Amendment 0004 is to respond to 2 additional questions received and provide a text only revision to PPON Section 4.4: Q1: Will the Government accept CUI materials in offeror submissions? If not, please clarify how the Government would like to receive Cloud Service Provisional Authority (PA) Memo(s) as they are classified as CUI. Yes- please see revision to PPON section 4.4 below - e) For any Offeror Gate Files or Step Proposal Materials marked CUI or PII, submit those in a separate transmission with the appropriate marking(s) in the message subject and on the files. Follow the instructions within SAFE to check the - Encrypt Every File checkbox for the transmission. The Government POCs listed in PPON Table 2 - Agreement Points of Contact are - cleared recipients and have Government furnished computer systems rated to handle the files with appropriate safeguards in place to protect them. See the SAFE Website for details at https://safe.apps.mil/help/dod-safe-help.xml - Q2: For Demonstrated Experience, will the Government allow offerors to remove the SoN Sections and performance and capability requirements description in Table 1? No changes will be made at this time **** **** The purpose of Amendment 0003 is to update the Step 1 Response Date from: 17 Jan to 31 Jan 2023. In addition the following files are included: 1. EBS-C_Prototype_Project_Opp_Notice_Amd_0003_2022_12_20.pdf = PPON - Updated with changes highlighted in YELLOW to reflect responses to the Industry Questions and revise the Submission Process to now use DoD SAFE. 2. EBS-C_Industry_Qs_Comments_Amd_0003_2022_12_20.pdf = Reponses to Industry Questions and Comments 3. PPON_Attch_0005_EBS-C_SW_Solution_List_Amd_0003_2022_12_20.xlsx = Updated Attachment 0005, responding to Industry Comments that corrects the instructions, resolves the Data Validation error (Drop Down List) and edits the format. The data entry fields for Offeror content remain the same. 4. PPON_Attch_0009_EBS-C_Price_Matrix_Amd_0003_2022_12_20.xlsx = Updated Attachment 0009, responding to Industry Comments that changes the data entry fields for the Rough Order of Magnitude. The ROMs are now divided by Fiscal Year. ******* Amendment 0002 is made for the following purposes: 1. Address a concern from Industry and provide pending PPON changes related to the timing of the requirement for: A) Achieving an Interim Authority to Test (IATT) for Impact Level (IL) 4 & 6 environments, previously as part of the Evaluation at the end of Step 4 (6 months after Agreement Award), now moved to Step 5 with progress accepted. B) Achieving an Authority to Operate (ATO) for IL4 and IL6, previously at the end of Step 5 (9 months after Award), now removed. 2. Communicate the following PPON changes (Changes will be HIGHLIGHTED in the Amended PPON, to be posted after 2 January): PPON Section 3 - OTA Acquisition Process, Page 9: Figure 4 and paragraph 3.1.4 Step 4; Page 10: Figure 5 and paragraph 3.1.5 Step 5; and Page 11: Figure 6 and paragraph 3.1.7 Step 7 and Step 8 though - N, will be revised to reflect the edits noted within the Instructions and Evaluation Steps noted below. --------------- Page 24: GE.1.2 Offeror Letter and Enclosures: Reworded from: b) Commercial Cloud Service Offering - a clear statement that describes the Offeror's Cloud Service Offering Solution that addresses IL4 and IL6. To: b) Commercial Cloud Service Offering - a clear statement that describes the Offeror's Cloud Service Offering Solution and addresses the approach to achieve IL4 and IL6 (i.e., in cArmy or external as SaaS). --------------- Page 51: S.4 Step 4: Instructions for - Prototype Phase 1, Reworded from: c) Achieve an Interim Authority to Test (IATT) at IL4 and IL6. To: c) Perform steps to achieve an Interim Authority to Test (IATT) at IL4 and IL6. SE.4 Step 4: Evaluation of - Prototype Phase 1 and Tech Demo #2 Reworded from: c) Successfully achieving an IATT at IL4 and IL6. To : c) Successfully achieving an IATT at IL4 and IL6 or providing a complete and executable Plan of Action and Milestones (POAM) for IL4 and IL6. ------------ Page 52: S.5 Step 5: Instructions for - Prototype Phase 1 Reworded from: a) d. Complete RMF Tasks and Obtain ATO at IL4 and IL6 To: a) a.4. Complete RMF Tasks and Obtain IATT at IL4 and progress toward IL6 SE.5 Step 5: Evaluation Criteria for - Prototype Phase 1 and Tech Demo #2 Reworded from: b) ATO Approved at IL4 and IL6 To: b) IATT Approved at IL4 and progress toward IL6 (or providing a complete and executable POAM for IL6) ------------ Page 54: S.7 Step 7: Prototype Phase 2 Instructions Reworded from: a) c. Maintain cATO To: a) a.4 Maintain Cybersecurity posture for IL4 and IL6 SE.7 Step 7: Prototype Phase 2 and Initial Limited Deployment Assessment Criteria Reworded from: a) c. cATO maintained To: a) a.4 Cybersecurity posture maintained for IL4 and IL6 Rationale for Changes: The Government timeline and methods for granting an IATT under Risk Management Framework 2.0 are still in review for changes. The revised EBS-C evaluation criteria leaves room for a POAM to be presented in case the Government cannot grant an IATT within the original EBS-C OTA projected timeline. An ATO will not be required in steps 4 or 5. ******* ******** The purpose of this first amendment to W529TC-23-R-EBSC is to accomplish the following: 1. Add Enclosure K (Enc_K_Army_Data_Governance_Memo_Amendment_0001_11_22.pdf) 2. Add Enclosure I (Enc_I-Sampling_of_Key_Design_Decisions_(KDDs)_2022_11_7.xlsx) 3. Add Attachment 12a (PPON_Attch_0012a_EBS-C_Offeror_Cloud_Requirements_2022_11_7.xlsx) 4. Delete Attachment 0009 (PPON_Attch_0009_EBS-C_Price_Matrix_2022_11_7.xlsx) 5. Update Attachment 0008 to reflect the changes listed above. 6. Call specific attention to the deadline to submit questions: December 8, 2022, 1300 Eastern 7. Clarify the Due date for Step 1 Gate Files / White Paper & Attachments is January 17, 2022, 1300 Eastern (The PPON, Table 1 will be updated in a later amendment). 8. Remind Industry that all correspondence in response to this opportunity shall be directed to the following individuals: Elizabeth (Liz) Zaharopoulos: Elizabeth.w.zaharopoulos.civ@army.mil; and Jordan Cosgrove: Jordan.e.cosgrove.civ@army.mil; and Jason Brunsvold: Jason.l.brunsvold.civ@army.mil ****** This notice serves as the PPON for the EBS-C requirement. All previous announcements and draft releases for this requirement can be found on www.SAM.GOV under the announcement number W52P1J-22-R-EBS. The purpose of this PPON, published under the Other Transaction Authority (OTA) of 10 USC - 4022[1], is to fulfill the Army requirements for the EBS-C Prototype Project. The Army is seeking Technical Integration Provider(s) (TIP(s)) to develop EBS-C Solutions to meet the requirements in the Statement of Need (SoN). All correspondence related to this notice shall be emailed to all three of the individuals listed below: Elizabeth Zaharopoulos, Agreements Officer, Elizabeth.w.zaharopoulos.civ@army.mil Jordan Cosgrove, Agreements Specialist, Jordan.e.cosgrove.civ@army.mil Jason Brunsvold, Agreements Specialist, Jason.l.brunsvold.civ@army.mil PLEASE NOTE: Funds are not presently available for this effort. The Government's obligation under this notice is contingent upon the availability of appropriated funds. No legal liability on the part of the Government for any payment may arise until funds are made available to the Agreements Officer for any resultant agreement and until the Awardee(s) receive notice of such availability, to be confirmed in writing by the Agreements Officer.