B01 - PM LOG-FIN CFS 001 Industry Event Transcript 6.17.26.docx

PM LOG-FIN CFS 001 Industry Event-20260617_150540UTC-Meeting Recording June 17, 2026, 3:05PM 56m 39s

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 0:10 Good morning.

My name is Charles Davis.

I am a acquisition manager for PM LOGFIN and I want to thank you for attending this industry event for the call for solutions for PM LOGFIN.

Just a little housekeeping before we get started.

On behalf of Gabriel Chuli, the acting Army Chief Information Officer Miranda Coleman, the Capability program executive Colonel Melvin Mitchell, the PM for LOGFIN and Mr. Michael Gormley, the deputy PM for LOG-FIN, we welcome you to the event. We deeply appreciate your participation.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 1:00 And we look forward to what comes out of this.

Enrique gomez 1:02 Eckerd.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 1:03 Umm.

To to go over some quick objectives here.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 1:11 I think someone has a hot mic.

Anyway.

To go over the objectives. This is an informational meeting. We will be going over the high level objectives that are requested within this call for solutions for you to.

Write your solution briefs against this will be a deep dive description, followed by contracting going over submission.

And regulations surrounding this and then we will end the session.

With pre received questions and then at the end of those questions, with time we will open up to the audience.

Please be aware.

That this broadcast as well as the associated slides and all of the questions that have been provided within this within this session.

As well as questions that can be submitted 48 hours following this session.

At the same link that was provided before.

Will all be summarized, answered and posted on sam.gov.

So again, this is an informational exercise.

Please make sure to try to experience.

And taking as much information as you can, we look forward to reviewing all of your presented solutions.

But this is not a sales venue.

Thank you very much.

And with that, I will hand this over to Miss Coleman the CPE.

Coleman, Miranda A CIV USARMY CPE ES2 (USA) 3:05 Thank you.

Good morning, everybody.

We really appreciate everyone attending today.

We know this was short notice, so again, thank you to our industry partners for joining us today.

I wanted to really foot stomp that modernizing our business systems is still our top priority.

These systems are critical warfighting enablers that are essential for us to track equipment, pay our bills.

Timely manner.

Leveraging Insights gained from real-world operations that have been happening recently, we recognize that there is a need to accelerate the enhancements of these core ERP to fill critical gaps that we are recognizing in the field and to support soldiers in any condition.

And this really means ensuring that soldiers can do their job, not just behind their desk.

But in the field as well.

And our main driver here is really speed and modernization.

So this this call for solution is an example of how we are committed to move at speed and really leverage industry's innovations.

I know we have a lot to go over today, so I don't want to take up too much time.

So again, I just want to thank everyone for attending today and we understand that this has been a quick.

Turn and we are moving fast on this.

So with that, I will turn it over to Mr. Gabe to lead the Army CIO, Gabe, over to you.

Chiulli, Gabriele J HQE USARMY HQDA CIO (USA) 4:52 Wanna do a quick mic?

Check you guys hear me.

Coleman, Miranda A CIV USARMY CPE ES2 (USA) 4:56 Yes, we can.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 4:56 Loud and clear, Sir.

Chiulli, Gabriele J HQE USARMY HQDA CIO (USA) 4:57 Fantastic. All right, well, appreciate it.

Miranda for the handoff here.

So welcome everybody.

Really, really appreciate you guys tuning in to this, this, this meeting here. Looks like we've got over 200 and 62160 people on so it's great to see a lot of collaborative partners from industry come tuning in to to kind of hear what's going.

On.

Just want to say a couple pieces here.

Obviously you know this, this is definitely.

A kind of a a new approach.

What you'll see is we kind of separated out kind of EBS into.

Four common areas what I'd ask industry to do from, you know from our viewpoint is really look at these different opportunity areas and look at them for the perspective of what areas are you are you able to address.

And and be truthful to the idea of what areas are you capable of doing? You know, with within the means of your capability set.

What we're not looking to do is take something, you know, I'll just use an analogy of.

Not looking to take a capability meant to build cars and say you can do create ice cream as well. So you know looking at the areas, seeing the areas that you you organizationally are capable of doing.

Very well, and even if it's a subset of an area, it's great for us to understand.

Hey, you know if if you looked at logistics and you say, hey, I can do logistics, but I can't do the entire logistics chain I can.

I can inform or I can be part of that, or I want to be part of that.

That's really what we're looking for is that feedback that helps us better understand where there's areas that the industry can be can be inclusive if there's kind of any sort of notional teaming.

And the other thing is is understanding where we have existing relations and how they can be leveraged and if we don't have an existing ELA, how that can be introduced as a as a set of capabilities.

So across the board.

It is a new approach. I think what we're looking to do is figure out what's the best, best way to operate within these different 4 areas. And then if you are capable of answering all four of them, it's good to know that as well. So, Across the board, look at it from that perspective is we are.

We are definitely interested if you if you believe that we, you know we have something in this.

Area that that looks oops. Say the words confusing or looks like you know we included a mistake or.

What you think should be adjusted that feedback is definitely valuable to us.

You know we are always trying our best to provide the best information as we as we are, you know transparency obviously and how we're trying to get after this.

So if something looks very confusing and that feedback is, is definitely helpful.

During this process so.

With nothing else, I will turn it over to Mr. Galbraith.

Galbraith, William Stephen CIV USARMY HQDA DCS G-4 (USA) 8:10 Hey, Sir. Good morning, ladies and gentlemen. Good morning.

Thank you so much William Galbraith.

I am the G4 munitions division chief for Headquarters, DA, Department of the Army, and what I'm going to give is a quick overview and then go in a little bit more in depth.

So what are we trying to do?

We need to resolve the challenge siloed ammunition data across distributed army property systems of record.

So the AP, SRS, the future Enterprise ammunition management must.

And I say must serve as a signal, a single authoritative source for truth.

It will consolidate the data across all echelons, delivering complete visibility, precision tracking and actionable intelligence for senior leaders, and to meet this, we need to meet the needs of the highly specialized units, such as the joint forces as well as.

The SOCOM.

Or Special operations command.

The system must operate seamlessly across the secure and also unclassified domains, thus ensuring immediate access to critical munitions data.

In the operational environment, some of the key capabilities establishing a single authoritative source.

To view ammunition, assets and the process to eliminate data silos.

And to ensure absolute consistency across the echelons, deliver that end to end. Total asset visibility across the full munitions lifecycle tracking assets seamlessly, from procurement to transport to storage to consumption, and then finally demilitarization.

You got to integrate the desperate, the desperate legacy data systems and enable planning and forecasting through predictive analytics, transforming the historic records into actionable strategic insights.

Got to support the tactical users.

Operating in the disconnected low bandwidth environments, guaranteeing uninterrupted operational capabilities at the tactical edge.

Maintain interoperability with the enterprise systems and to support the SAS mod Sunset Path, ensuring a secure, orderly transition to continuous data synchronizations.

They'll go over a few other pieces of the core objectives.

In the capabilities area and then also performance objectives and requirements, universal asset accountability provide the complete asset visibility categorized by storage location.

DoD identification codes, or DoDACs the national stock numbers lot numbers, serial numbers, condition codes and ownership to meet this intended purpose.

For the financial audibility piece ensures strict compliance with the financial improvement and audit remediation and all the mandates the system architect must maintain immutable transaction ledgers to guarantee the end to end accountability and precise financial evaluation of all conventional ammunition stocks.

And we're looking at end to end transaction management process comprehensive.

Inventory and stock adjusting transactions.

This includes goods.

Issued and received seamlessly managed at the Army depots, the retail facilities and also at the end user.

With the regulatory physical inventories, support and execute regulatory compliant physical inventories, the system must reconcile physical counts with the digital records and process necessary discrepancy adjustments under the strict internal controls.

We're looking at movements.

Tactical conveyance is track and manage the ammunition assets stored or transported within the primary and nested technical.

Conveyances. This is container rule on roll off platforms, ISO containers, and flat racks that joint interoperability.

We discussed a little while ago enable a robust integration and interoperability with the joint enterprise data fabrics and auxiliary systems to fully support unified multi domain operations. We go back to the Cyber Nipper connectivity providing full operational accessibility.

On both secret as well as Nipper capabilities.

For security and the planning of requirements for the joint forces as well as special operations forces.

Brazilian operations delivering continuous operational functionalities in denied and degraded and intermittent and limited or DDIL network environments guaranteeing local operations when communications are disrupted or blocked, and then looking at historical data migrations preserve the legacy inventory records historical transaction letters.

Due in due out records and the net explosive weight.

Which limits to the structured data domain.

While fully supporting the sunset path of legacy SAS mod systems.

Explosive safety and new management net explosive weight management equip Expeditionary ammunition support areas ASAS to manage explosives safely. This includes automated.

Automatically determining the new limits for the individual storage.

Structures, which is your magazines, your pads and your warehouse and assessing risk mitigation strategies.

At the tactical echelon visibility providing a complete tactical ammunition visibility and control from retail levels down to the individual users within divisions and brigades.

Automation enabling automated consumption tracking and standardized unit on hand for this platform.

So bottom line is the logstat generation.

Moderate user experience. Deploy an intuitive, moderate web-based graphical user interface.

Designed to streamline receipt, store and issue and reporting workflows to minimize operator error and training timelines.

In the last couple predictive and analytic dashboards, integrating a predictive model and automated visualization dashboards to allow commanders to focus.

On ammunition demands preempt critical shortages and optimize the distribution networks, and again, back in the digital world.

Capturing instantly an archived sign pick up, turn in and residue documentation.

Providing authorized users real time automated retrieval capabilities to eliminate the manual cross system search.

Information technologies.

Here's where integrating the modern handheld devices.

And AIT capabilities with active and passive scanning to replace manual keyboard data entries, accelerating the process times and ensuring data integrity.

And lastly, to provide a dedicated, readily accessible training module that maintains user proficiency.

Without altering or impacting live operations, stockpile records.

So, ladies and gentlemen, that was a big mouthful, but that is what I have in the ammunition area of interest.

Over to Ken Beam.

Beam, Kenneth E CIV USARMY HQDA DCS G-4 (USA) 16:41

OK.

Thanks bill.

I'm Ken beam with DAG 46.

So I'm going to start by summarizing the objectives described in the logistics area of interest.

One feeling critical operational logistics gaps while maintaining financial accountability.

Integration 2.

Providing comprehensive lifecycle visibility of all of our physical assets.

3rd enabling the real time tracking of assets along with fully audible processes.

And 4th is maximizing the working capital efficiency from the strategic support area, the tactical edge.

A few guiding principles we're looking for in our modernized capability.

One emphasis on agility and flexibility to enable rapid modification and deployment of capabilities and next would be support across all classes supply and finally integration with financial systems for auto compliance.

We want to transition to talk about functions we're looking for across 13 capabilities.

Areas for logistics and again, this is strategic tactic, one skill.

So the first one is sustainment and supply chain management.

Key functions in there include providing total asset visibility, automating the capture of consumption and supply demand signals from the tactical edge, maintaining demand forecasting models, the integration of operational requirements with supplies and supplier capability to provide timely sustainment to the warfighter.

And finally, the identification and mitigation of supply chain risks.

2nd is product lifecycle and master data management.

So there we're looking for the functions of managing bombs, product structures and material master data creation and management.

3rd capability areas procurement. So functions include generation and validation of purchase requests and checking them against funding availability, processing of invoice payments.

4th integrated maintenance operations.

Some key functions there include automating PMCS and tactical maintenance operations.

Integration of platform health and usage sensor data to enable predictive maintenance.

And then, you know, finally being able to manage or fleet management and readiness, being able to manage our industrial equipment as well as facility upkeep.

5th capability areas manufacturing so high level functions releasing make repair or D mail orders tracking of Labor and material consumption and managing production close out costing 6. Quality management and surveillance. So managing product quality deficiency reports supply discrepancy reports and enforcing quality assurance across the material life Cy.

7th Property Accountability and Asset management.

Yarnell, MARY ANN CIV USARMY CPE ES2 (USA) 19:37 Folders that we have in dates, but you don't get to.

Beam, Kenneth E CIV USARMY HQDA DCS G-4 (USA) 19:41 I think we have a hot mic out there.

OK. Our property accountability and asset management automating edge inventory operations, being able to track asset transfers and hand receipts and providing commanders in accurate real time picture of assigned equipment.

8th inventory and warehouse management.

So functions there will be automate and integrate receipt, store issue and disposal processes and the overseeing of inbound and outbound warehouse movements.

9th Transportation and distribution.

So integrating transportation supply planning from request to close out, managing transportation resources and finally executing intra theater distribution to it and short timely delivery to the warfighter.

Penth order management automating custom order processing that could be internal to the army as well as external customers. Tracking of fulfillment status and then finally financial billing for sold material and services based on Army working capital and policies.

11 theory is financial management accountability, so functions there include providing audible financial tracking, resource prioritization and reporting for the Olcoff general Ledger.

And in general, we're looking for a core system of record for financially relevant log transactions.

12th, 4th deployment in theater sustainment. So that is the management of end processes for projecting our forces and subsequently establishing and operating resilient integrated sustainment nodes in support of large scale contingency operations. And then our final capability area is secure sustained, so as required.

Having the ability to secure logistics data and processes within a high side classified boundary, and then finally, I just wanted to highlight what we view as key enablers across the capability areas I just described.

They include predictive analysis and artificial intelligence for predictive sustainment, demand forecasting and inventory optimization.

Large language models and natural language processing, self-service analytics.

And reporting automatic identification and data capture to support data collection and reduce the manual burden on the soldier for data entry, data management, governance and decision support systems, and finally, modern user experience tools.

So with that, that captures the logistics area of interest and I want to transition over to Kyle Coles for finance.

Kohles, Kyle M CIV USARMY HQDA ASA FM (USA) 22:32 All right.

So good morning all.

Thanks for coming on to hear us talk a little bit about this.

My name is Kyle Kolas.

I'm chief of Enterprise Systems transformation security with ASA FM NC.

I'll be going over the finance portion and also that the personnel HR requirements for this call for solution, I'm assuming most of you have read through that CFS.

I'll cut the chase.

Just provide a little overview of this finance piece 1st and then head into the details for personnel.

In general, really what we need to focus on is a modern integrated.

Financial management and personnel solution.

And here's a little bit about what we're looking for in each of those efforts. The big one up front is that legacy system modernization. And this is really exactly what it sounds like.

We're looking for that improved modern technology, leading to a better experience for our users and also better operational support to our warfighters across the globe.

Additionally, we need to make sure that is audit ready.

And we can meet audit requirements as we develop and release.

And so that's going to meet compliance with federal and Dow financial management standards with organic, automated internal controls.

And lastly, just that integrated Ledger for standardized and aligned chart of accounts real time general Ledger data and improved fiscal year end processes than reported.

So a little bit more detail on the actual finance piece is that we know Department of War, financial Management community operates across fragmented decades old legacy systems.

That were never really designed for modern accounting standards.

Or real time data sharing. The sideload architecture forces manual reconciliations, delays funding to the tactical edge and historically contributed to disclaimer of opinion audit results.

So here's what we really need to focus on as we take that big operational view of challenges for that financial community.

So one of the major things is logistics. Finance systems cannot easily talk to each other, which has lead to mismatched asset valuations and manual data entry.

And so making sure as we develop this.

Consolidating and simplifying that database.

Line that metadata governance is going to be important across all of this legacy systems also lack automated posting logic and end to end integration.

Making army financial managers execute all of that manually, taking much needed time out of their schedule for doing more critically important tasks.

Additionally, financial managers are bogged down with administrative data entry and manual reconciliations.

Meeting commanders at the tactical edge lack real time visibility into their actual spending power closing out fiscal year requires massive manual catch up.

Work and journal entries prone to human error.

Acting software cannot support modern accounting standards and generate compliant audit trails and heavily customized government software is expensive to maintain, slow to update.

And so really what those are, the main problems were getting after in this financial solution.

The main pieces sections of development that we're working on for capabilities list off. I think we have about 12 here.

So first one would be budget budget execution.

Next is financial asset information management.

Then there's payable management and payment processing.

Reimbursable management, debt management and cost management.

We also have general Ledger management and period end close financial reconciliation, financial performance reporting and internal controls, finance, data integration, security and user experience.

And finally, capitalized asset management are kind of those main pieces that we are focusing on and we'll have a little more detail on that at another time.

With that, can we switch the side over to personnel?

Perfect. Thank you.

And so I'll also be going over the basics of the personnel listing on this CFS. Just giving a little bit more detail for personnel.

We're looking for ideas to provide financial accounting and cost accounting capabilities required to support payroll related transactions for civilian, military and foreign national personnel.

That includes payroll, calculation, payroll, administration and payroll disbursement.

As the main responsibility of external payroll providers.

For decades, the Army's civilian human resources and payroll operations have relied on a Patrick legacy systems. These systems operate in silos, requiring intensive manual intervention and batch processing.

The Fug Mandan architecture results in pay discrepancies, delayed financial reporting, and lack of real time visibility into those workforce labor costs.

And really, the goal for this solution is to simplify and improve time and attendance to ensure accurate payroll and give leaders visibility into how labor costs are impacting their operational budgets and readiness.

Don't have a ton more detail on that at this moment and so really I'll just wrap up right now.

I hope these details help bring to life the call for solutions we need for these critical army challenges and appreciate your time and support today.

Look forward to seeing your responses. Thanks all.

Hitt, Shelly A CIV USARMY ACC (USA) 27:35 Good morning.

I'm Shelley Hitt, the contracting officer alongside contracting specialist Jessica Rooks.

And I'm going to provide a brief, brief overview of the submission requirements and the phased evaluation process to ensure you have all the information needed to submit a compliant and compelling solution.

We're executing this effort using commercial solutions, opening procedures under the Army Open solicitation.

So our goal here is flexibility and speed to acquire innovative commercial solutions.

The Government may award one or more firm fixed price contract or OT agreements resulting from this call, and the government also reserves the right to make no award at all.

First, the submission process.

It's critical that you follow these instructions carefully.

All submissions are due by noon central time on June 30th and please be advised that late submissions will not be accepted or evaluated.

Under any circumstances.

Please ensure your submission is sent to the e-mail address provided in the CFS posting and ensure that the e-mail submission subject line follows the exact format detailed in the CFS. Your submission package must be broken into separate files with specific naming conventions. So first is the administrative file.

Which should include your title, page, executive summary, business certifications, and any IP OCI statements.

2nd is going to be your solution brief and this is limited to a maximum of four pages per area of interest. If you're submitting on multiple AO is, be sure to submit a separate PDF for each one, and then finally the ROM and schedule file you should sub.

A separate ROM and schedule file corresponding to each AOI solution brief you submit.

Please note any pages exceeding the specified page limits will be removed and not evaluated.

And Please remember to monitor Sam, Gov for any updates to this posting. Next, I'm going to walk you through the phased evaluation process which has up to three phases.

Phase One is the solution.

Beef brief evaluation. We will assess your written submission against four key criteria.

Technical merit. We're looking for solutions that demonstrate.

Relevance, innovation, scalability and feasibility.

Next schedule.

Your proposed timeline must be realistic.

ROM compliance, your pricing estimates must align with the effort. And finally, data rights. Your IP and data rights assertions must comply with the solicitation.

So based on this, each brief is categorized as selected for further consideration or not selected.

So advancement depends on those criteria. Government need and funding availability. So be aware even if your brief has merit, we reserve the right to limit the number of companies we carry forward.

All offers will be notified of their status in writing. Phase two is a pitch session.

Selected companies may be invited to present their solution, which could include a demonstration.

Please note that the government reserves the right to limit the number of participants in a pitch or bypass this phase entirely.

And finally, the phase three is the solution proposal following the preceding phases.

Select companies may be invited to submit a full, detailed proposal.

It's important to understand that the government may down select or award at any phase, and any award is always contingent upon government need and availability of funding.

Thank you for your attention so much.

We encourage you to submit your most innovative solutions and look forward to reviewing them. And again, please refer to the call for solutions document on Sam Gov for complete details.

Before we begin addressing the previously submitted questions, I wanted to highlight how we're going to manage the Q&A process after today's event to ensure fairness and transparency.

So please submit any additional questions electronically using the Microsoft Lync or by scanning the QR code currently displayed on the industry event announcement.

We want to make sure everyone has ample opportunity to seek clarification as you refine your concept.

Therefore, the government is going to keep this Q&A submission link active for an additional 48 hours following the conclusion of today's invet. And if you think of further questions after we log off today, you'll have until approximately noon on Friday the 19th to submit through.

That portal, as we address your inquiries, please keep two critical guidelines in mind.

Do not submit questions containing proprietary information. Any Q&A.

Containing proprietary or company sensitive data will not be published or answered publicly.

Any questions?

We do not get to during today's live session, inclusive of all compliant questions submitted prior to this event and through the 48 hour post event, window will be compiled, answered and posted formally to Sam, Gov. And this will serve as the official record for all parties I.

Want to thank you again for your time and participation.

And that will move towards beginning to address the question submitted so far.

Gormley, Michael J CIV USARMY CPE ES2 (USA) 33:16

OK.

Good morning, everybody.

I'm going to go ahead and start as Miss Hitt alluded to the questions that have been submitted through roughly midday yesterday.

Any questions that were submitted after that, we'll have answers posted to Sam Gov along with the answers that are being.

Discussed here. So with that I'm going to start off with the 1st and just run through them all.

And look forward to if we got time at the end for some open Q&A.

If time allows so with that, starting with the first question, will the government intend to use any existing software licenses for this CFS?

Yes, the government will utilize existing licenses and agreements where applicable.

See also the call for Solutions Section 5.

General submission notes submit your responses accordingly.

Next question, our considerations for prebuilt solutions weighted equally in comparing low code.

No code submissions for each area of interest.

Answer the CFS phase one evaluation criteria does not include weights.

C CFS, Page 8 evaluation criteria.

Subsection a technical merit to align your response.

Next question, why is Palantir Advantage listed on separate ASIC platforms?

The separate references to Palantir and Army vantage are listed or as listed in the CFS tables as Appendix C.

Approved product list APL reflect table headings A.

That army vantage is sustained by the Army Software Innovation Center and separately B that Palantir is also an approved development platform. For more information, see Appendix B reference references #10 Army low code, no code development guides, 31 July 2025.

Next question is SAP considered an approved Ocio landing zone.

Answer The CFS does not address or mention Ocio landing zone within the cfsa.

SAP is called out five times in the first section.

And in Appendix C, the approved products list APL, second table, CIO, approved development platforms, item number seven, SAP.

Next question, what are your biggest workforce challenges supporting these modernization efforts?

Answer it appears that this questions surrounds functionality within ipsay.

This would be outside of the scope for PM LOGFIN and this CFS.

With me.

Next question, are you experiencing shortages in labor?

Excuse me.

Cyber Cloud software, or AI talent.

Answer the question is not relevant to the CFS. Talent shortages are not in the scope of this CFS.

Next question, how are you currently onboarding and training new personnel?

Answer the question is not relevant to the CFS. Neither onboarding nor training.

New personnel are in scope of this CFS, unless that is specifically related to.

A software deployment. Next question.

Our work.

Our workforce Development solutions eligible under future calls for solution.

Answer no. Workforce development is not in the scope of this or future CF. s s under PM logon.

Next question.

Are there workforce related activity capability guh?

Pardon me.

I'll restart.

Are there workforce related active capability gaps currently being evaluated?

Answer Please refer to CFS Section 2 Objective Statements area of Interest, Page 3.

Area of interest for personnel, which provide the needed context.

Next question, please clarify the following language in section one call objective and problem statement, Section 3, sentence 3.

Development is restricted to the following approved platforms. Appian, Armyvantage, volunteer power apps, Salesforce, SAP and ServiceNow does this.

Does this restriction mean that proposed solutions?

Must be developed.

Posted or deployed on one of the identified platforms.

Answer Yes, as correctly quoted development is restricted to the following approved platforms.

Follow on question to that was does does it mean that only companies associated with with those platforms are eligible to submit a proposal?

No, it means that a company can propose development in any of the approved platforms.

Next question.

Additionally, may an offer that is not on, excuse me, not one of the listed platform providers submit a proposal independently, provided its solution uses or integrates with an approved platform. Or must the offer establish a formal partnership with one of the listed platform providers to be eligible for?

Consideration answer in alignment to the previous answer.

Any company can propose development in any of the approved platforms.

Next question.

Is there a particular technology area that the CPE is prioritizing or notes a gap in? Currently yes, refer to CFS Section one call objective and problem statement.

This specifically states the objective of this call is to solicit concise solution brief for innovative commercial technologies, specifically low code, no code and software modernization solutions.

The Army will focus first on ammunition based on available funding.

Additional capabilities will be targeted subject to funding availability.

Next question, what is the range of funding for each of the area?

Excuse me, what is the range of funding for each of the focus areas?

Answer The Army's approved budget is publicly available.

The army has not determined a range of funding for each of the focus areas.

Next question, is it better to submit with partners?

Answer The CFS does not address any references to submissions with partners.

5th next question, what does a winning solution brief look like?

Answer Please refer to CFS section 6.1 in its entirety.

A solution that fully responds to the phase one requirements with a compliance submission that addresses the evaluation criteria.

Now, with the consideration of section 612 solution, brief selection process will be categorized as selected for further consideration or not selected for further consideration.

Next question.

According excuse me is is the government open?

To disaggregating types of services.

For example, separating strategic support to development and to develop an accelerated ERP slash capability road map triage, use cases and define commercial business processes from systems integration efforts.

Answer this question may need additional detail. The government is open to solutions that address the objective statements for any of the four AO is ammunition, logistics, finance, and personnel.

Next question, can vendors accelerate solutions that address specific functional requirements within the broader ES2 logfin ecosystem? Rather than proposing a complete end to end platform answer?

The CFS does not include any reference or does not include any reference for the need for accelerator solutions, nor does the CFS refer to the broader ES2 logfin ecosystem.

This CFS provides 4 AOIS with objective statements.

Company should submit a response to section 6.1 phase one solution brief.

Next question in particular, would the government consider accelerator capabilities supporting human resources, financial management, workflow automation, data integration and process orchestration?

Answer Yes, the government would consider partial or notional solutions.

Does next question.

Was the army envision a role for no code low code accelerators that can integrate with existing or proposed enterprise solutions to accelerate process modernization, workflow automation, data management, reporting, and user experience improvements?

Answer See-one call objective and problem statement.

Second sentence. The objective of this call is to solicit concise solution briefs for innovative commercial technology.

Specifically, low code, no code and software modernization solutions. Just as a reminder, as I continue going through the questions and answers that these all will be posted to sam.gov.

Next question, will the government evaluate modular capabilities independently or is there an expectation that submissions demonstrate coverage across multiple functional domains within the ES2 logfin scope?

Answer the CFS permits solutions that address one or more objectives.

Next question.

Pardon me.

How would the government assess solutions that primarily provide acceleration, integration and modernization capabilities versus replacement systems of record?

Answer The government would consider a partial or notional solutions.

Next question are AI enabled capabilities such as intelligent workflow automation, document processing, knowledge management, digital assistance and decision support tools within scope.

For for this call for solutions answer, possibly the Department of War and the Army have embraced the use of AI operating insidethe.mil cloud security impact levels.

This CFS does not specifically call out or require the use of AI. However, for Section 1, the objectives of this call is to seleuce a concise solution brief for innovative commercial technologies, specifically low code, no code, and.

Software modernization solutions.

Next question, does the office have any feedback from from the known low code?

No code engagement layers that.

You have tried like Pega Neptune, Appian, Paralleline etc.

No, the office does not have feedback to publish on known engagement layers.

The CFS provides the Army's objective statement that have not been met.

Next question, what AO is, does the army want to address in government fiscal year 27?

Answer this CFS provides 4 AOI.

Section 5.

General submission notes.

5th bullet.

Note the government reserves the right to issue one or multiple awards from the CFS. It's similarly reserves the right to refrain from making any in government fiscal year 27 or any government fiscal year.

The government does not excuse me.

Correct that the government does intend to address ammunition.

The ammunition AOI first, though this is subject to change. Next question.

Is there funding to support the AO? Is that the army wants to address in government fiscal year 27 answer the fiscal year 27 budget is public information and subject to change based on Department of war and army needs.

Next question.

Please clarify which which systems are in scope for for the personnel area.

Answer Please See Systems listed in CFS Section 9.

The THE personnel objective statement relates requirements for financial transactions.

Transactions, as many are currently performed in Appendix A current ERP systems.

Next question, what is the intended modernization path for SAS mod sunset partial replacement?

Continued sustainment or integration into new capabilities?

Answer SAA's mod will be sunset based on a company's approach and when its proposed scheduled delivery delivers a replacement capability to the Army.

Next question, the government seeking is the government seeking point solutions that sit on top of existing ER, PS or does this effort also include ERP modernization, migration to S4, the CFS section, one call objective and problem statement includes a clear problem statement. The objective of this call.

Is to solicit concise solution briefs for innovative commercial technologies.

Specifically, low code, no code and software modernization solutions.

These technologies will support a transformation, transformative modernization of the Army's five SAP based defense business systems, a critical effort.

Designed to directly improve operational efficiency, enhance data visibility and reduce overall sustainment costs across the Army's business mission area, the CFS does not include any references of S4.

However, SAP is listed as one of the approved development platforms.

Next question, the CFS restricts development to Army CIO approved platforms. If a solution uses an approved platform.

Example, powerapps or ServiceNow as the delivery layer, while the core IP resides in a separate loco.

No code solution with open AI integrations. Does that satisfy the platform constraint?

Or must the entire solution be built natively within an approved platform?

Answer following the wording in in the CFS at section One, page two last sentence.

Additionally, all solutions must be hosted within or directly connected to the CRM 2.0 cloud environment and development is restricted to the following approved platforms, Appian, Armyvantage, Palantir.

Power apps Salesforce.

SAP and ServiceNow?

Also review.

Review the wording at page a. Evaluation criteria technical merit.

Last question, does the Army plan to deprecate any of the existing, ER, PS as part of the described implementation?

For example, should vendors assume that all listed systems including SAS MOD and ASIP will continue to be utilized throughout the life cycle of the solution?

Answer The Army plan is dependent on the awarded contractor or contractors approach.

The desired end state goals are to deprecate.

The existing ERPS.

And with that, I turn it back to you, Mr. Davis.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 49:25 All right, with remaining time, we will.

Now entertain any live questions with the 5 minutes remaining.

Right.

I see Mr. Devon.

Deven Joshi (C5MI ) 49:50 Yes, Sir.

Want to understand Army stance on data and IPI?

Think I know in the past there have been some concerns about vendor lock in and data ownership, so just want to hear.

For this exercise, what is army stance in terms of protecting its own data and its own IP?

Thank you.

Gormley, Michael J CIV USARMY CPE ES2 (USA) 50:21 I'm not sure if this is if Mr. Julie is still on or not. If not, I will go ahead and jump in and answer.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 50:22 Appreciate.

Gormley, Michael J CIV USARMY CPE ES2 (USA) 50:29 OK, not heard.

I'm not sure if he he's still here.

So bottom line is that we always want to respect and protect contractor IP, right? Our intent is not to expose that unless it has been agreed to in in from a contractual perspective.

So you know, as we progress through the phases and as applicable, any contracts that would be awarded would outline how we will manage IP for those particular in those particular instances, right. And that's all part of the negotiation.

Deven Joshi (C5MI ) 51:01 Mr.

Mr. Gormley, my question is more around army protecting its own data and its own IP versus the contractor.

Gormley, Michael J CIV USARMY CPE ES2 (USA) 51:12 OK, fair.

Sorry about that.

So if I'm understanding the question then correctly we will use the normal courses of action to protect that data.

So it will reside appropriately within the proper impact levels, so 4-5 or six as as a standard or customary practice today.

Deven Joshi (C5MI ) 51:34 Thank you, Sir.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 51:42 Further questions.

Mr. Moore.

Jim Moore 51:50 Hey Charles, sorry if I didn't hear this.

Are vendors allowed to submit non approved platforms for consideration?

Is there any appetite for that or is this solely locked down to army approved platform list?

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 52:02 The approved platform list is what we need the solutions.

Submitted for. Unless anyone else has.

A exception to that. That is what the CFS says.

So that is the appetite we have at this point.

Appreciate your time and participation, Mr. Selly.

Gary Celli 52:29 Good morning. For phase two, will the army be providing scenarios to demonstrate?

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 52:39 You will actually if selected for phase two when you do receive the invitation to either propose or pitch, you will then receive the evaluation criteria associated.

Does that cover it?

Gary Celli 53:00 Thank you.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 53:05 Minister Robinson.

Matthew Robinson 53:09 Good morning, Sir. Thank you.

Appreciate the time.

Just to clarify towards the end of the question and answer session, I believe there is a reference to deprecating the SAP. The five SAP platforms within the army.

Did I understand that correctly?

Or perhaps is there an intent by the army to consolidate their?

SAP instances and continue.

With, with that.

With that technology over.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 53:43 I'll allow somebody smarter than me to answer that.

Matthew Robinson 53:45 All right, Sir. Thanks.

Gormley, Michael J CIV USARMY CPE ES2 (USA) 53:47 Not that I'm smarter than you, Charlie, but I'll. I'll take that.

So yes, we are planning to essentially sunset those current ERPS, whether there is convergence or not will be dependent upon the proposed solutions that we receive and directions that that may or may not take us.

Matthew Robinson 54:06 Roger, thank you.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 54:12 Alright.

I see Siva.

Siva 54:19 Yes, Sir, this is Sivan Balagan.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 54:19 Mr. Steven.

Siva 54:22 Good question on the on the.

Section that talks about low code, no code and modernization as part of the CFS.

I think when we talk about low code, no code and modernization, does it include the modernization language include?

A.

A technical upgrade of the existing ERP's in support of capabilities that are listed in in the.

In the CFS.

Gormley, Michael J CIV USARMY CPE ES2 (USA) 54:52 Yes.

Siva 54:54 Thank you.

Davis, Charles Dennis CIV USARMY CPE ES2 (USA) 54:56 All right.

In order to remain respectful of everybody's time, we are at an hour. Questions that were provided in the chat will also be aggregated into the posted document on Sam.

Does anybody else have anything, Sir?

Gormley, Michael J CIV USARMY CPE ES2 (USA) 55:25 Yep, Nope. Just want to say you know big thank you from the Army team as, as you saw, you got to see some of the functional representatives.

The goal here is to go in as one team and tackle the army's hardest problems and get after modernizing the business system ecosystem that we have today. That includes current ERP's and other defense business systems that, for example, SASMOD, which has been.

Talked about as well.

So with that though, we do appreciate your time and I'll just put stop and echo what was said before.

At the following the end of this, there will be an additional 48 hour period where we'll continue to receive answers or excuse me questions and we will post answers to Sam. Gov as soon as possible.

Also, this video did see a question in the in the chat.

Just wanted to iterate or.

I know somebody affirmatively answered that with a positive yes.

This will this video will be made available.

So with that avid you would do.

Thank you so much and appreciate your time.

stopped transcription image6.png image7.png image8.png image9.png image10.png image11.png image12.png image13.png image14.png image15.png image16.png image1.png image2.png image3.png image4.png image5.png