CfWP Topic 0013 - Automated API Management_C2Next_Updated.pdf

Solicitation: BAA-21-R-NCFT Call #:0013 Topic #: N2104 – Command Post Mobility/Survivability

FEDERAL AGENCY NAME: Army Contracting Command-Aberdeen Proving Ground (ACC-APG) on behalf of the Army Futures Command (AFC), Network Cross-Functional Team (Network-CFT)

BROAD AGENCY ANNOUNCEMENT NUMBER: BAA-21-R-NCFT

Originally published on beta SAM: 30 OCT 2020 Last Updated: N/A

CALL ANNOUNCEMET NUMBER: 0013

CALL SCHEDULE: Dates: All dates are subject to change

Event Date BAA Released on beta.SAM.gov 30 Oct 2020 Call 0015:

White Paper (WP) Submission Opens 08 July 2024 WP Submission Closes 28 July 2024 Government begins notifying Vendors of WP evaluations: 30 Aug 2024

• Selected for Further Consideration (Invitation to participate in the no-cost technological demonstration)

• Not Selected for Further Consideration Technological Demonstration 09-13 Sept 2024 Government begins notifying Vendors of results of technological demonstration: 04 Oct 2024

• Selected for Further Consideration (Invitation to submit proposal)

• Not Selected for Further Consideration

Government begins accepting proposals from selected Vendors 15 Oct 2024 Government begins notifying Vendors selected for award (if any) 15 Nov 2024

*White papers received after the due date/time shall be governed by the provisions of FAR 52.215-1(c) (3).

BAA TYPE: This is a call for WPs only and will be governed by the two-step process described in General Information of the BAA-21-R-NCFT. Offerors that submit a proposal without first submitting a WP will not be eligible for award.

WP INSTRUCTIONS: Detailed instructions on format for WPs and the two-step submission process can be found in the overarching BAA.

TWO-STEP BAA, CALL ANNOUNCEMENT

BAA-21-R-NCFT, WHITE PAPER CALL # 0013

Title: Automated API Management_C2Next Date: 28 June 2024

Important Please assess the entire solicitation carefully prior to any response. The Network-CFT BAA utilizes a two-phase process to solicit offers and select a source for award.

• Phase One – Step One: Submission of White Papers *Step Two: Technological Demonstration (By Invitation Only)

• Phase Two – Submission of Proposals (By Invitation Only)

*Please note the Government reserves the right to skip step two of phase one and go directly to Phase Two after white paper evaluations.

WP SUBMISSION: All WPs shall be submitted via Joint Tactical Networking Center (JTNC) Joint Communications Marketplace (JCM) Technical Exchange Meeting (TEM) Industry Community, via https://jtnc.experience.crmforce.mil/TEMIndustry/s/.

TECHNOLOGY AREAS OF INTEREST:

The U.S. Army Program Executive Office Command Control Communications-Tactical (PEO C3T), in support of Network Modernization priorities, is issuing this call for WPs in association with Topic Number 0013. To be eligible for consideration and possible contract award, the WP shall be of basic research, applied research, and/or that part of development not related to the development of a specific system or hardware procurement in the following “Technology Areas of Interest” specific to this call:

A. BAA TOPIC NUMBER: N2104: Command Post Mobility/survivability

WHITE PAPER CALL #0013

Operational Description of the Problem: Future Army Mission Command Information Systems (MCIS) will be developed with MOSA-native composable architectures, highlighting microservices and applications to provide commanders with access to real-time data. To ensure data is accessible and components of the supporting software framework operate seamlessly to meet reliability and performance requirements, Application Program Interfaces (APIs) will become critical. Just like components and subcomponents of the composable architecture will be monitored and updated to keep pace with the changing operational environment, APIs will also require management. The Army will not have time, resources, or technical expertise to provide the level of support to APIs to does to maintain other equipment during operations and cannot create a dependency on developers and field service representatives (FSRs). Instead, to fight and win in large scale combat operations (LSCO) and be able to transition an “always on” system from competition to conflict rapidly, the Army will need an automated way to manage diverse and dynamic APIs across an operational, enterprise architecture.

Technical Description of the Problem: The Army requires government control and oversight of APIs in future composable software architectures to ensure design, documentation, test, monitoring, and governance of APIs meets specifications required for the full range of Army operations. Whenever possible, these activities should be automated, with a priority placed on updating any manual processes to automated ones immediately, or over time. Automated API management enables a functional agile environment for DevSecOps and CI/CD. For example, “API testing is an essential part of the API-first development model, as it enables teams to verify their API's quality by confirming it is working as expected. But ensuring API quality is only half the battle; teams must also iterate quickly in order to release new features that will help them stay competitive. These teams typically follow the agile development methodology, which involves shipping small code changes multiple times a day or week.

While this approach supports fast-paced development cycles, it also increases the risk of breaking changes. API test automation has emerged as the answer to this problem, as it helps teams remain agile without compromising API quality or losing test coverage. Automated API tests can be executed on a schedule, or they can be executed within CI/CD pipelines whenever a developer pushes new code. This hands-free approach can be seamlessly integrated into any development team's existing workflow, so they don't have to worry about issues falling through the cracks. Historically, software testing has been performed by dedicated QA teams at the very end of long development cycles. This approach is time-consuming and prone to human error, and it can lead to delays as teams work to fix unexpected issues at the last minute. Shift-left testing involves running tests earlier and more frequently during the development process, which helps remove this bottleneck. Automation plays a key role in the shift-left https://jtnc.experience.crmforce.mil/TEMIndustry/s/ https://www.postman.com/api-platform/api-testing/ https://www.postman.com/api-first/ https://www.postman.com/api-first/ approach, as it lets developers automatically execute tests within CI/CD pipelines whenever they push new code. This enables development teams—including those that are responsible for building APIs—to continuously validate their work and catch issues before they reach production. Teams that leverage automated testing can therefore release features quickly, confidently, and cost-effectively.”*

Required Capabilities:

Any automated API management tool shall account for API gateways and developer portals. Tools shall manage the full API lifecycle to include by not limited to observe usage, create, secure, document, test, version, publish, promote, monetize, and retire the API. Tools should also include or integrate with analytics engines.

** The vendor shall identify any current ongoing same/similar efforts associated with the proposed white paper solution/technology area. The vendor shall provide the contract/agreement number and a brief description of the effort.

WP QUESTIONS/ANSWERS: Government will publish WP Q&As in the JCM TEM Industry Community applicable Topic Collaboration Group area. Instructions for the Q&A session shall be posted to the JCM TEM Industry Community (https://jtnc.experience.crmforce.mil/TEMIndustry/s/) when the call is issued.

WP PREPARATION, SUBMISSION, AND REVIEW PROCESS: Instructions for submissions of WPs, including response content and format, are covered in Section B of the baseline BAA, BAA-21-R- NCFT. The submitted white paper shall not exceed eight (8) pages.

TECHNOLOGY READINESS LEVEL (TRL): For all the subtopic areas listed above, the maturity of the proposed technology shall be at a TRL 6 or higher (please see enclosed TRL definitions). The end state of the effort shall be a set of demonstration/proof-of-concept systems that can be tested in a field environment.

WP EVALUATION CRITERIA:

The Government will evaluate WPs to determine which have the potential to best meet the Network- CFT’s needs utilizing a two-part evaluation criteria as follows:

• Part One (1): WPs will be evaluated using “Go” or “No-Go” gate criteria listed below.

The “Go” or “No-Go” requirements are listed below which will determine if the WP will receive further consideration. If during the evaluation one of the “Go” or “No-Go” requirements is not met, that evaluation will automatically receive a “No-Go” determination and will not receive further consideration.

o Cost. The Government will review the Offeror’s Rough Order of Magnitude (ROM) cost estimate for compliance with the BAA. ROM must be broken out by Base and Option, to include applicable cost elements.

o TRL. The Government will review the Offeror’s TRL to ensure it meets requirements as detailed in the Call for WP. Offeror must meet at a minimum TRL 6 at delivery.

o Schedule. The Government will review the Offeror’s proposed schedule to ensure the Offeror meets the period of performance, when the Government specifies a Not-to-Exceed schedule. The Not-to-Exceed schedule for this effort is 24 Months (one

(1) up to 12 month base period, which means vendors can deliver their prototype https://www.postman.com/api-platform/api-test-automation/ https://jtnc.experience.crmforce.mil/TEMIndustry/s/ before 12 months, and one (1) up to 12 month option period). If either the base or option period proposed exceeds 12 months, the white paper will be considered “No- Go”.

o Compliance with all white paper submission requirements outlined in BAA-21-

R-NCFT.

• Part Two (2): WP will be evaluated using the following factors, which are listed in descending order of importance:

o Importance to Agency Programs (Relevance/Potential for Impact). The Government will review the Offeror’s description of the technology proposed on how it solves the capability/gap/problem presented, the relevance to the Highly Desired/Desired Capabilities, scalability of the solution, and assess its worth in relation to the stated “Technology Areas of Interest.” WPs will be scored as highly likely, likely, or marginally likely to address the stated operational and technical descriptions of the problem.

o Technical Merit/Challenge (Innovative or Revolutionary Technology (Scientific & Engineering Viability)). The Government will review the Offeror’s technology proposed to satisfy the technical challenges and design objectives by reviewing the Offeror’s enabling technology (innovative or revolutionary approach); feasibility;

technical risk and mitigation plan; alternatives (other technical data/information conveyed); technology maturation (the ability to achieve technology maturity); and time to field solution. WPs will be scored as fully or partially meeting or exceeding the stated Highly Desired and Desired capabilities.

o Schedule. The Offeror’s schedule will be evaluated based on the reasonableness of the allocation of time to meet major activities/milestones, deliverable, metrics measures of success, potential risks, and mitigation plans. WPs will be scored as having a preferable, acceptable, or questionable schedule for delivery.

TECHNOLOGICAL DEMONSTRATION EVALUATION CRITERIA:

Commercialization/Transition Potential (50%), Technical Feasibility/Risk (25%), Firm Ability (15%), Alignment with HQDA priorities and National Defense Strategy (10%)

Note: The process outlined below is subject to change.

“Technology demonstration” entails a prototype sample presented by an offeror to showcase the proposed characteristics of the offered product described in the whitepaper as well as expand on aspects of the product that cannot be adequately described by specifications, purchase descriptions, or white paper (e.g. ease of use, quality of user experience, etc.). Demonstrations of capabilities not yet ready for a practical demonstration may be provided by an in-person paper or slide show presentation. This demonstration is also an opportunity to clarify and expand upon concepts not fully explored in the white paper and to field Government questions about the proposed prototype solution.

The Contractor must present the technology demonstration during the time specified in the Invitation to Demo. Individual time slots will be allotted to the Contractors selected to attend. If the Contractor fails to present the technology demonstration on time the Government will reject the invitation to continue through the selection process

1. Unless otherwise specified in the solicitation, technology demonstration shall be:

(1) Presented at no expense to the Government.

(2) Operated and maintained by the Contractor during technology demonstration evaluation.

2. The Government will not be liable for any damages to technology demonstration during evaluation or shipping.

Rules & Expectations

The Contractor’s technology demonstration will be observed during a 45 minute session. Time slots will be provided to afford Contractors time to prepare for the demonstration at the venue.

The technology demonstration evaluation will consist of the following:

Activity Time Allotted Setup/Tear Down: Up to 15 min Presentation/Demonstration: 45 minutes Q&A: 15 minutes Total Technology demonstration time:

60-75 Minutes

The Government will allow the Contractor to prepare their equipment in a classroom prior to beginning of the event. It is recommended not to show up more than 60 minutes prior to demonstration time to prevent crowding of the classroom.

The Government will allow each Contractor up to 15 minutes to set up and fix any problems encountered between the classroom and demonstration area. After 15 minutes has elapsed, the timer will start for the 45 minute technical evaluation.

The Government will provide the Contractors a space to deliver their technology demonstration. This area will consist of a table, podium, and a projector with screen. The Contractors should expect 3-4 Government leaders presiding over the demonstration event with supporting technical evaluators.

Contractors invited to attend the event will only be allowed in the demonstration area during their allocated time until the day has concluded.

Please note the Government reserves the right to eliminate the technical demonstration and go directly to a Request for Proposal OR hold the technical demonstration virtually.

EXPECTED NUMBER OF AWARDS: The Government reserves the right to award as many (or as few) contracts as it deems appropriate. There are no set percentages of funding allocated to each investment category.

AWARD INFORMATION: The Army may elect to award a base period with an option period as follows:

• Base Period: Design and Build a Prototype (Up to 12 Months)

(a) The Offeror shall deliver the prototype(s) necessary to prove their technology proposed.

o A Safety Assessment Report (SAR) shall be delivered with the prototype.

(b) The Offeror shall provide training after prototype delivery that will allow the Government to conduct an operational assessment of the technology proposed.

o In support of the training/operational assessment, the Offeror shall conduct a training for Government personnel (i.e., N-CFT, PEO C3T, and other C5ISR representatives) onsite at Aberdeen Proving Ground (APG) and provide draft training materials.

Note: Training during Phase 1 is for the program office and support organizations only.

Soldier touch-point training will occur during Phase 2 as delineated below.

o Contractor shall specify exact prototypes.

Before the completion of the base period, the Government will conduct an assessment of the technology proposed, looking at the broad areas of technical performance and suitability for experimentation with Army units. Based on this assessment, the Government may decide to exercise the option period.

• Option Period: Follow-On Training and Experimentation (Up to 12 Months)

(a) The Contractor shall provide follow-on training and experimentation for the prototype solution at a location in the Contiguous United States (CONUS) with an equipped Army unit. Contractors shall provide:

o A training and experimentation session at a U.S. military installation and/or facility.

Contractor shall propose the number of days required to train an Army unit on their proposed solution(s).

o User and training manuals.

o Technical support necessary to make repairs and replace parts as required to keep the proposed technology operational throughout this phase.

The Rough-Order-of-Magnitude (ROM) shall be broken out by base and option period, as the Government may only fund the base period and not the option period.

ANTICIPATED FUNDING: The Government reserves the right to select all, part, or none of the WPs received, subject to the availability of funds. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

ANTICIPATED TYPE OF CONTRACTS/INSTRUMENTS: The Government reserves the right to award the instrument best suited to the nature of research proposed.

PERIOD OF PERFORMANCE: The contract(s) will have one (1) base period and one (1) option period, each of which will be up to 12 Months. The option period is not guaranteed and is subject to funding availability.

CALL AMENDMENTS: Offerors should monitor the SAM site, via https://sam.gov/, and Joint Tactical Networking Center (JTNC) Joint Communications Marketplace (JCM) Technical Exchange Meeting (TEM) Industry Community, via https://jtnc.experience.crmforce.mil/TEMIndustry/s/, for additional notices to this Call that may permit extensions of the WP submission date or otherwise modify this announcement.

APPLICABILITY OF BASELINE BAA: All requirements of BAA-21-R-NCFT apply. For complete information regarding BAA-21-R-NCFT, refer to the BAA announcement as posted on SAM.Gov. It contains information applicable to all calls issued under the BAA and provide information on the overall program, proposal preparation and submission requirements, proposal review and evaluation criteria, award administration, agency contacts, etc. If there is conflicting information, this call for white paper and instructions contained herein takes precedent over the BAA.

http://www.fbo.gov/ https://jtnc.experience.crmforce.mil/TEMIndustry/s/

Rules & Expectations