Inactive

AMENDMENT 05: This Amendment provides a clarification to one on the responses in the Government File: AIMMS_PPON_Step_1_QAs_2021_06_11.pdf Reference Question #29, Statement of Need, p 23 para 2.4.1, l... AMENDMENT 05: This Amendment provides a clarification to one on the responses in the Government File: AIMMS_PPON_Step_1_QAs_2021_06_11.pdf Reference Question #29, Statement of Need, p 23 para 2.4.1, lines 772-773. "Comment: Section 2.4.1 states that BI/data analytics capabilities must be provided on the SIPRNET. Section 2.3.2 states that only ECM capabilities must be available on the Secret Internet Protocol Router Network (SIPRNet). Question: If BI/Analytics is required on SIPRNet, please provide more details on the required capabilities and the data sources." ---------------------------------------------------------------------------------------------------- GOVERNMENT [ORIGINAL] RESPONSE: "Change Made: SoN 2.3.2 (lines 607-608) contained an error and will be revised to remove the words "providing only ECM capabilities. The new sentence will read "A separate instance of AIMMS providing only ECM capabilities must be available on the Secret Internet Protocol Router Network (SIPRNet)." Response: Army Futures Command (AFC) has been and will continue to move increasing amounts of test data into the CLASSIFIED realm, meaning that usage of SIPRNET is reliably anticipated to increase. As such, AIMMS BI / analytics capabilities on NIPRNET and SIPRNET are expected to be equal." ----------------------------------------------------------------------------------------------------- CLARIFICATION: The original Response and “Change Made” note contained an editorial error. Offerors are instructed to strike the words “providing only ECM capabilities” from SoN lines 607-608. The SoN will not be changed, revised or re-published. The original Government Response which cited a requirement for Army Futures Command is correct. Additional details on this and other requirements will be provided in the Performance Work Statement (PWS) and its enclosed Requirements Traceability Matrix (RTM). Those documents will be published with Upward Invite #2, for Step 3 Prototype Proposal. The SoN page 23, Section 2.4.1 Cloud Computing in Multiple Environment, lines 770-776 that “The AIMMS Solution must provide the full featured “solution environment” to be hosted on an unclassified Army network. Also, a duplicate set of the AIMMS Solution Capability, (same solution version) providing project and portfolio management, content management, workflow, and BI/data analytics capabilities must be provided on the SIPRNet. Application integration capabilities are not required on SIPRNet (IL 6) due to lack of relevant systems to connect and integrate with on that network,” remains correct. A new SoN will not be published. No Extensions will be granted. Amendment 04 The Government has attached the updated Industry Q&A under the file AIMMS_PPON_Step_1_QAs_2021_06_11. The attachment fixes clerical error in the previous Q&A attachment, and provides previously missing responses. Amendment 03 The Government has attached the Industry Q&A under the file AIMMS_PPON_Step_1_QAs_2021_06_10. No further extensions will be contemplated at this time. AIMMS Step 1 Submission of White Papers to 21 June 2021. Amendment 02 The Government has extended the date of the AIMMS Step 1 Submission of White Papers to 21 June 2021. This extension will allow the Government time to provide responses to industry submitted questions, and allow Offerors time to review those responses to the Step 1 Questions and Comments received and specifically those regarding the Statement of Need Enclosure B AFARS 5111.106, Appendix HH, Common Data Services. Responses shall be posted be via a subsquent Amendment to this PPON. No further extensions will be contemplated at this time. No further questions are permitted for this Step 1. Amendment 01 This amendment addresses the following: i. Update the description to the PPON. Under paragraph 5, of this PPON, removed reference to consortia/consortium, as this is a PPON for a stand-alone OTA. ii. Incorporate Enclosure D, as an attachment, to this PPON. iii. Update the due date for White paper submissions to 14 June 2021, taking into account 31 May 2021 is a Federal Holiday. Questions are still due NLT 28 May 2021. ----- US Army Contracting Command - New Jersey posts this Prototype Project Opportunity Notice (PPON) on behalf of the Army Test and Evaluation Command (ATEC). ATEC requires a cloud-based enterprise software solution combining project management, content (data and documents) management, workflow management, application integration, and business intelligence/data analytics capabilities in order to more efficiently plan and execute T&E projects, manage T&E results data and reports, and track ATEC organizational performance metrics. The new ATEC Integrated Mission Management System (AIMMS) will replace several obsolete, “siloed,” legacy information systems. The Army seeks prototype(s) of commercially available software solution(s), including low-code/no-code solution(s) which must be able to obtain Authority to Operate (ATO) on Government Furnished Equipment (GFE) in both classified (Impact Level 6, ie IL6) and controlled unclassified (IL5) environments. The overall goal of this prototyping project is for one or more industry competitors to demonstrate that their software can meet ATEC’s operational needs. PM ARDAP is the materiel developer supporting ATEC’s requirement through a competitive, iterative prototyping effort authorized under 10 USC § 2371b and DoD Instruction (DoDI) 5000.74. The attached PPON provides the six Steps of the source selection process, the instructions for each Step, and the associated evaluation criteria. The instructions and criteria for Steps 2-6 are subject to change. Step 1 of the process (this solicitation) begins with a four-page (plus one cover sheet) White Paper submission and other ancillary files. To enter Step 1, Offerors must submit the required files. This PPON Solicitation is published as a “Full and Open” competition. The Government intends to award one or more Other Transaction Agreements (OTA) under the authority of 10 USC § 2371b for Phase 1 Prototype Development. To best facilitate providing all interested Offerors in the AIMMS Prototype Project the maximum time to fully consider the requirements, the Government will make available the Department of Defense Architecture Framework (DoDAF) Operational View (OV) diagrams. The Statement of Need (SoN) Enclosure C (OV diagrams) are marked as “Controlled Unclassified Information” (CUI). To receive the CUI file: See PPON Attachment 0001, sample DD Form 2345 Militarily Critical Technical Data Agreement. Offerors that request to receive the CUI AIMMS file shall follow the process to first submit and receive an approved DD Form 2345 by coordinating directly with the Defense Logistics Agency Joint Certification Office (DLA JCO). Instructions and the digital form are available at: https://www.dla.mil/HQ/LogisticsOperations/Services/JCP/DD2345Instructions/ Once a JCO approved form is in hand, see PPON Table 1 to Optionally Submit the Form “early” by email to the Agreement Points of Contact in Table 2 (Agreements Officer and Specialists) and as Required, submit in the appropriate Gate File as defined in PPON Table 4 on the Day the Proposed Step 1 Files are due, (date as defined by beta.SAM.gov). The CUI marked file will only be transmitted using the DoD Secure Access File Exchange (SAFE) Site to the Data Custodian named on the approved DD Form 2345. In accordance with 10 U.S.C. § 2371b(f), an agreement entered under this action for a prototype project, may provide for the award of a follow-on production contract or transaction to the participants in the transaction. Any agreement awarded as a result of this proposal will include language requiring your company to confirm compliance with Section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232). If you are not able to comply with the law, the Government may not be able to award the agreement. Please see the PPON and all attachments for the format, method, and the timeline for submitting questions and/or comments on any of the posted files.