CAML AMP-36K Lbs. Variant Request for Solutions Brief.pdf

REQUEST FOR SOLUTIONS BRIEF (RFSB)

Common Autonomous Multidomain Launcher (CAML)

Autonomous Mobility Platform (AMP) Prototype – 36K Lbs. Variant, Leader Vehicle Autonomy Kit, and Autonomy Command and Control (C2)

Introduction

This RFSB is a standalone effort with its own unique requirements, distinct from prior CAML solicitations.

A CAML system is comprised of the following sub-systems:

• AMP – A platform that is an optionally crewed autonomous vehicle platform designed to autonomously load and download via its Load Handling System (LHS), transport, fire, and reload various Unique Munition Pallets (UMP) weighing up to 36,000lbs.

• UMP – Multiple unique launcher systems reconfigured into a standardized palletized design. Each pallet integrates the munition system's bespoke launcher electronics directly onto the pallet, enabling a single AMP to transport and fire a variety of unique munitions. There are four (4) variants of the CAML UMP: (1) Tomahawk, (2) PAC-3/Missile Segment Enhancement (MSE), (3) Indirect Fire Protection Capability (IFPC) AIM-9X, and (4) Multiple Launch Rocket System (MRLS) Family of Munitions (MFOM) pods. Each variant of the UMP will be equipped with the munitions appropriate Fire Control C2 interface (e.g.

Integrated Battle Command System (IBCS), Tactical Tomahawk Weapons Control System (TTWCS), or Advanced Field Artillery Tactical Data System (AFATDS) / Artillery Execution Suite (AXS)).

• Leader Vehicle Autonomy Kit – A modular, AMP-vendor-provided, kit designed to integrate onto both autonomous and non-autonomous vehicles. Once installed, it serves as the C2 node to synchronize multiple CAML systems during convoys, fire missions, and rapid emplacement or displacement activities.

The CAML system enforces MOSA standards to secure full USG ownership of critical system data, including Interface Control Documents (ICDs), Technical Data Packages (TDPs), and data rights of all sub-systems. This unrestricted data ownership eliminates proprietary vendor lock and enables the USG to distribute the technical baseline, consisting of the applicable ICDs and TDPs, as Government Furnished Information (GFI).

RFSB Request

This RFSB is for CAML AMP and Leader Vehicle Autonomy Kit, and complete autonomy software suite for C2.

The CAML’s AMP autonomy is the critical capability enabling tactical employment of multiple munition payloads, convoy cohesion, and self-resupply without human intervention.

Furthermore, any CAML AMP must possess the inherent system redundancy to operate autonomously as a follower or, when required, transition to lead commanding other CAML AMPs within its formation.

CAML’s AMP is a common, optionally crewed, autonomous vehicle platform, designed with the primary function to autonomously load and download UMPs, reload, transport, and fire multiple munition payloads. The AMP also functions as an Autonomous Self-Resupplying System (ASRS) using an integrated LHS to autonomously load up to 36,000 pounds, The AMP vendor is solely responsible for the AMP’s overall design, fabrication, production, integration, and delivery of the mechanical, electrical, and logical command interfaces. While the AMP's boundaries do not encompass the UMP or the launcher electronics themselves, the interfaces the AMP defines directly inform the design, physical footprint, and functionality of the UMP

The AMP vendor will deliver the complete system platform, which includes the common, optionally crewed autonomous vehicle, AMP, alongside the Leader Vehicle Autonomy Kit required to command and synchronize other CAML AMPs. Concurrently, the vendor must deliver the defined mechanical, electrical, and logical interfaces to inform UMP design, the ASRS/LHS, and a complete autonomy software suite for driving and self-resupply tasks. The AMP vendor shall provide a complete autonomy software suite that communicates directly with UMP launcher electronics to control stow, deploy, and initiate firing operations, while supporting convoy, waypoint, teleoperation, and manual driving modes augmented by advanced obstacle detection and avoidance (ODOA) systems.

The related agreement efforts will be formally linked together through the execution of Associate Contractor Agreements (ACAs). The ACAs will outline the terms and conditions under which each associated Contractor collaborates with another to support the overall CAML system effort.

This RFSB invites eligible entities to present complete solutions directly to the Army.

Submissions must identify all team members, their roles, and the value they bring to the prime.

Ultimately, these briefs will inform PAE FIRES of the technical and competitive landscape capable of meeting or exceeding program objectives.

GENERAL CAPABILITY DESCRIPTION

This RFSB is a standalone effort establishing a completely new mission profile and operational framework.

The CAML provides multi-domain fires across all echelons, delivering a mobile, autonomous, or optionally crewed launcher that far exceeds current capabilities.

RFSB OVERVIEW & KEY MILESTONES

PAE FIRES intends to exercise 10 U.SC. § 4022 authority. This RFSB and any subsequent activities are intended to satisfy competition requirements of the statute, including potential follow-on production without further competition per 10 U.SC. § 4022(f). This phased competition will consist of the following three (3) phases in the review and selection process as follows:

1. Phase 1 – RFSB: Ten (10) pages, inclusive of a cover page, of a technical discussion of a prototype development solution, any teaming arrangements, a rough project development schedule, data rights assertions (if applicable), and rough order of magnitude (ROM) price corresponding to the Government provided Work Breakdown Structure (WBS). The Solutions Brief will be based on the attached Performance Work Statements (PWS). While not required, the Government encourages offerors to also address their availability for site visits and/or live demonstrations of their operational capabilities.

2. Phase 2 – Oral Presentation/Pitch: Companies whose Solution Brief are evaluated to be of the most merit may be invited to provide an in-person pitch to provide further details of their proposed complete solution and the technical and business viability of the solution to PAE Fires subject matter expert panel, potentially consisting of representation across the PAE Fires and Army/DoD Community of Interest. The Government expects to limit the number of companies invited to pitch. As such, a company’s solution may be evaluated to be of merit but not invited to pitch. The Government may elect to proceed to Phase 3 without inviting any companies to Oral Presentation/Pitch.

3. Phase 3 – Proposal / Site Visit / Demonstration: Following the evaluation of Solution Briefs (and oral presentation/pitches if requested), the Government may elect to conduct a site visit and/or request a demonstration of operational capabilities. The Government reserves the right to limit the number of Proposal /Site Visit / Demonstration invitations;

therefore, a solution may be deemed to have merit but not be selected for Proposal /Site Visit / Demonstration. The Government is under no obligation to conduct a site visit or demonstration and reserves the exclusive right to do so at our sole discretion. A selection may be made based solely on the content of the written Solution Brief.

The Government may issue a Request for Prototype Proposal (RFPP), subject to the availability of funding. The RFPP response will be concurrent with the site visit/demonstration preparation and conducting the demonstration.

The Government may, at its discretion, elect to issue RFPPs prior to, simultaneously with, following, or without a Proposal/Site Visit/Demonstration invitation.

Only U.S. companies with the ability to process and store SECRET information and hardware are eligible to submit a solutions brief. Interested Offerors shall submit Commercial and Government Entity (CAGE) code and Offeror POC to the following Government Security POC:

- Jessica Salmon at jessica.j.salmon.civ@army.mil

- Abigail Chatlain at abigail.e.chatlelin.civ@army.mil

Upon validation of facility clearances, the Government will coordinate with the Offeror’s POC to provide the CONTROLLED UNCLASSIFIED INFORMATION (CUI) PWS on the date indicated in Table 1. The PWS will support the creation of the Solution Brief technical content mailto:barbara.a.cantrell2.civ@army.mil mailto:abigail.e.chatlelin.civ@army.mil and the ROM pricing. Offerors shall submit a Solution Brief in accordance with the Format and Content of Solution Brief described below. Failure to submit required CAGE Code information in a timely manner, or related Offeror errors, will not be a basis for extensions of time for questions or Solution Brief submissions.

Solution Briefs are due at 12:00 PM/1200 ET on Tuesday, September 01, 2026, via the following PAE FIRES email addresses. Contact the individuals below if you require a DOD SAFE site drop for CUI submissions:

- Abbie Chatelain at abigail.e.chatelain.civ@army.mil

- James Bedsole at james.e.bedsole.civ@army.mil

- Amy Johnson at amy.d.johnson30.ctr@army.mil

- Jamalia Manor at jamalia.p.manor.ctr@army.mil

Key Milestones are listed in Table 1 below. Dates are subject to change at Government’s discretion.

RFSB Release Date 11 AUG 2026 Offeror Submission of CAGE Code Due 14 AUG 2026 Release of PWS to Cleared Offerors 18 AUG 2026 RFSB Questions Due 20 AUG 2026 RFSB Responses Due 01 SEP 2026 Invitation to Oral Presentations 04 SEP 2026 Oral Presentations 09-11 SEP 2026 RFPP Release / Demonstration Invite TBD RFPP Responses Due TBD OTA Award TBD

TABLE 1

SOLUTION BRIEF GUIDELINES

Eligible entities may respond to this RFSB with a Solution Brief. Solution Briefs shall not exceed ten (10) one-sided pages, inclusive of a cover page with company information. Solution Briefs shall be single-spaced, 12-point font with at least one-inch margins on 8 1/2” x 11” page size.

ROM price and ROM price ground rules and assumptions will not count against the 10-page limit but must be kept on separate page(s). Total file size shall not exceed a 10 MB e-mail limit for all items associated with this RFSB response. Solution Briefs must specifically address the requested information detailed below. Respondents shall not initiate oral communications with the Contracting Office, the Program Office or other PAE FIRES personnel regarding this opportunity during this phase; violations of this requirement may constitute non-compliance with mailto:abigail.e.chatelain.civ@army.mil mailto:amy.d.johnson30.ctr@army.mil mailto:jamalia.p.manor.ctr@army.mil the established procedures. It is Respondents’ responsibility to properly mark proprietary information/portions if company proprietary information is included within a Solution Brief.

The 10-page Solution Brief, in contractor format, may focus on describing details of the proposed prototype solution, including capabilities and how it could address or improve the technical requirements and objectives, and potential impacts and benefits to the CAML System. While there is no guarantee of a future request for prototype proposal, the Solution Brief should state whether the contractor would participate in future pitches or prototype proposals for the concepts outlined in their Solution Brief.

The Solutions Brief should be outlined as follows:

1. Cover Page (1 page) to include Company name and address, and CAGE Code; whether it is a traditional or non-traditional defense contractor (defined below); how the company qualifies for award under 10 U.SC. § 4022; the Technical and Business Points of Contact (POC) to include:

Telephone Numbers and Email Addresses; headquarters location; size designation of company (i.e., large or small business concern), annual revenues, and number of employees; if the Company’s proposed approach has been proposed to or previously funded by any federal agency, to include SBIR/STTR, please identify each specific agency and all applicable contract/agreement numbers; and a brief abstract.

2. Technical Approach (6 pages):

a. Project objectives and scope.

b. Proposed AMP solution for the host vehicle, specifically reviewing the detailed capabilities of the CAML Leader Vehicle Autonomy Kit, the physical AMP chassis (including its ASRS and LHS capabilities), and the overarching Autonomy C2 architecture.

c. Design viability of the modular Leader Vehicle Autonomy Kit and its actual modularity onto multiple different platforms with seamless integration.

d. Facilities/equipment available to carry out the proposed prototype effort and to be positioned to fabricate additional quantities.

e. Outline the development approach and schedule for logical sequencing and achievability of the PWS operational assessments. Discuss how long lead requirements, if any, will be addressed and associated risk/risk mitigation.

f. Identify any intellectual property involved in the effort and associated restrictions on the Government’s use of that intellectual property.

g. MOSA Strategy: A detailed mapping of module boundaries and the specific open standards used for interfaces. Provide the specific level of rights offered for interfaces.

3. Qualifications and Experience (3 pages):

a. Prior, or current, work related to integrating missiles (of the type, size and range similar to the CAML variant proposed) and command and control systems (ie, IBCS, TTWCS, AFATDS, AXS) into autonomous weapon systems. Provide contract numbers and POCs for Government sponsored efforts.

b. Prior or current work developing and fabricating vehicles similar to the CAML Leader and Follower.

c. Identify team members, if any, and their role assignments and each team member's qualifications and experiences in comparison to the respective performance requirement(s) the team members are proposed to perform. If the Respondent proposes utilizing one or more Non-Traditional Defense Contractor (NDC), the Respondent must identify the specific contribution of each NDC and explain the significance of the NDC’s participation.

4. ROM Price (no page limit) Provide a price ROM to complete the prototype project and provide any other data or supporting information that is necessary to show the estimated costs are realistic for the technical approach described. Describe the estimated price for the proposed technical approach by following the Government provided Work Break Down Structure (WBS) by Fiscal Year (FY) and any assumptions pertaining to price for how this concept could be achieved.

5. (Optional) Availability for site visits and/or live demonstrations. (1 page)

6. Solution Briefs shall be clearly marked, “Company Name_RFSB_CAML_AMP_Leader Solution.” Only UNCLASSIFIED or CUI submissions will be accepted. Any submissions with classified information will not be reviewed and will be deleted. There will be no mailed submissions, and telephone inquiries will not be accepted. Review of Solution Briefs does not promise nor guarantee that a company will receive a contract, and the Government reserves the right, at any point, to modify and/or cancel the RFSB. Please be advised, only an Agreements Officer has the authority to enter, or modify, a binding agreement on behalf of the Government.

BASIS OF EVALUATION

Phase 1 - Request for Solutions Brief:

All Solution Briefs correctly submitted in response to and compliance with this announcement will be evaluated against the stated criteria below. The Government reserves the right to review the content of Solution Briefs against various AI tools to determine whether it appears Offerors relied on AI to write and submit Solution Briefs. If the Government, in its sole discretion does this, and receives indication that a Solution Brief correlates closely to AI provided solutions, this will be viewed as an indication of a lack of knowledge and understanding by the Offeror, and the solution may be determined unacceptable or otherwise negatively rated.

Technical Approach:

1. The approach addresses the Government’s requirements as outlined in the PWS with no exceptions and provides a holistic approach demonstrating understanding of the problem to include risk and opportunities.

2. The approach demonstrates sufficient understanding and capabilities to model AMPs loaded with a UMP for both static and dynamic loads.

3. The approach demonstrates sufficient understanding of the autonomous system operations.

4. Proposed facilities/capabilities (software models/tools, system simulators, ability to fabricate hardware prototype and/or special tooling).

5. Schedule, including key milestones, projected timelines and proposed critical path(s), that is realistic to include long leads, meet PWS delivery dates and supports technical approach.

6. Data rights - the degree to which asserted data rights restrictions, as well as any proposed option(s) for additional data rights, affect the proposed technical solutions and the Government's ability to use, modify, reproduce, release, perform, display or disclose the resulting technical data and computer software for Government purposes as defined in DFARS 252.227-7013(a)(12) and 252.227-7014(a)(11) in terms of demonstrating its ability to execute the proposed approach. Emphasis will be placed on the Government’s ability to use, release, and disclose technical data or computer software documentation and preference may be given to Solution Brief submissions with the least amount of data rights restrictions.

7. MOSA Compliance – The degree to which the architecture uses non-proprietary standards, with a willingness to grant GPR for interfaces.

Qualifications and Experience:

1. Relevant past performance (within last five (5) years) or current work experience and relevancy of that experience for the development and integration of autonomous weapon systems like CAML.

2. Effective team member role assignments.

3. Team member qualifications and experiences.

ROM Price:

1. Is the price realistic to meet the PWS and schedule requirements, and aligned with the proposed technical approach?

2. Is the price affordable based on Government expectations and available resources?

Any Solution Briefs which offer to prototype beyond the scope of the PWS will be determined non-compliant and unacceptable and will not be reviewed (e.g. an AMP and Leader Solution Brief which adds a UMP solution). The Government will not consider or evaluate partial solutions.

Solution Briefs will be initially evaluated on the basis of merit of the proposed solution/concept in addressing the PWS, not against other Solution Briefs submitted in response to this announcement. Following initial evaluation, PAE FIRES may select offerors who submit Solution Briefs of particular merit or benefit to provide an oral presentation/pitch, or as noted above, for Demonstration or RFPP selection.

Phase 2 – Oral Presentation/Pitch:

Individual pitches, if requested, are expected to provide additional insight into the Solutions Brief and as such will be evaluated against the same factors as the Solution Brief.

Individual pitches will be initially evaluated on the basis of merit of the proposed concept in addressing the PWS and the factors above, not against any other pitches held under this announcement.

Pitch evaluation will consider the full content of the actual Oral Presentation (including answers or inability to answer any questions posed) and the content of the slides presented. Pitch evaluation will also consider the previously submitted Solution Brief; thus, inconsistencies between the Solution Brief and presentation, or between the digital copies of the slides and the oral presentation itself, may be viewed unfavorably. It is anticipated that pitches will be conducted in-person with an up to one hour presentation and up to 30-minute question/answer session, though specific parameters of the Oral Presentation may change before the presentation date.

Phase 3 - Proposal / Demonstration

Subject to the availability of funds and mission need, the Government may issue a RFPP and/or a request for site visit and/or live demonstration to the offeror or offerors with the most meritorious Solution Briefs. Unless otherwise noted in the RFPP. Further details regarding the prototype proposal instructions will be provided in the RFPP.

Upon favorable review and available funds, the Government may choose to make an award for the CAML AMP and Leader effort. In making a final award determination, the Government will consider the technical approach and experience from the Solutions Brief, with additional insight from the capability demonstration results, and lastly, the price proposal submission requested in the RFPP.

Questions: The Government will consider and answer relevant questions to this RFSB. Submit questions to the POCs identified above NLT 1200 ET on Thursday August 20, 2026.

Depending on the nature of the question, the Government may respond directly to the inquiry or post questions and answers as an amendment to this announcement.

Non-Government Advisors: All government or contractor personnel that may review RFSB responses have executed Non-Disclosure Agreements (NDAs) for project information related to this initiative.

Eligibility Requirements: Only U.S.-based companies or organizations are considered eligible to participate in this RFSB. Submissions from entities or organizations that do not have a primary place of business in the U.S. will not be considered.

Each eligible entity:

1. U.S.-based firms shall be incorporated in, and maintain, a primary place of business in the U.S.

2. May not be a U.S. Federal Government entity or employ a U.S. Federal employee acting within the scope of their employment.

3. Is required to register in System for Award Management (SAM) and have, or be able to obtain, an active CAGE code, DUNS number, and not be on the exclusion lists (debarred, suspended, or ineligible).

PAE FIRES’s RFSB is voluntary and open to all entities that meet the eligibility requirements.

Submittals to the RFSB must be received by 12:00 PM ET on Tuesday, September 1, 2026.

Late submissions will not be accepted, and any other failure to comply with RFSB submission instructions (content, approach, etc.) may not be evaluated by the Government.

INTELLECTUAL PROPERTY

The Army is a strong proponent of deliberate intellectual property (IP) rights and management by the private sector and the Department of Defense.

For the RFSB:

1. Nothing in this RFSB shall diminish the Government’s rights in patents, technical data, technical information, computer software, computer databases, and computer software documentation that the Government had prior to this effort, or is entitled to, under any other Government Agreement or contract, or is otherwise entitled to under law; and

2. The Federal Government may negotiate licenses for the use of IP developed by a registered participant in the future.

Furthermore, the Government understands that information provided in response to this solicitation is presented in confidence and may contain trade secret or commercial or financial information, and it agrees to protect such information from unauthorized disclosure to the maximum extent permitted or required by Law, to include:

1. 18 USC 1905 (Trade Secrets Act),

2. 18 USC 1831 et seq. (Economic Espionage Act),

3. 5 USC 552(b)(4) (Freedom of Information Act),

4. Executive Order 12600 (Pre-disclosure Notification Procedures for Confidential Commercial Information), and any other statute, regulation, or requirement applicable to Government employees.

COST AND SOFTWARE DATA REPORTING (CSDR)

Based on projected expenditures and the acquisition pathway utilized, the Government anticipates the inclusion of cost and software data reporting (CSDR) requirements as part of this effort in accordance with the requirements of Section 3227 of Title 10, U.S.C., and DoD Instruction 5000.73.

NOTES AND DEFINITIONS

Non-traditional defense contractor is defined in 10 U.S.C. § 3014 as an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section.

Prototype projects are defined as submissions that may improve Army platforms, Army weapons systems, or Army support systems. A prototype project can generally be described as a preliminary pilot, test, evaluation, demonstration, or agile development activity used to evaluate the technical or manufacturing feasibility or military utility of a particular technology, process, concept, end item, effect, or other discrete feature. Prototype projects may include systems, subsystems, components, materials, methodology, technology, or processes. By way of illustration, a prototype project may involve: a proof of concept; a pilot; a novel application of commercial technologies for defense purposes; a creation, design, development, demonstration of technical or operational utility; or combinations of the foregoing, related to a prototype.

NON-GOVERNMENT PERSONNEL

Offerors are advised that employees of the firm identified below may serve as a non-Government advisor in the review and evaluation of Solution Briefs. Such firms are expressly prohibited from competing on the subject acquisition. The non-Government advisor will be required to submit to the Government a Non-Disclosure Agreement reflecting the effort(s) that they will be supporting.

The Offeror’s submission of a Solutions Brief under this RFSB indicates concurrence with the aforementioned use of non-Government advisors.

Apex Defense, LLC

12601 Old Silo Trail SW Huntsville, AL 35803-3342

Dexter Wright (Director) Telephone: (256) 738-2710 dexter@apexdef.com

Astrion Group, LLC (fka Axient, LLC)

360A Quality Circle, Suite 100 Huntsville, AL 35806-4596

Cindy Moon (Sr. Contracts Administrator)

(256) 658-6104 cynthia.moon@axientcorp.com

Banner Defense, Inc

9668 Madison Blvd, Suite 205 Huntsville, AL 35758

DeLayna Shepard (Contracts Manager)

(256) 653-4475 dshepard@bannerdefense.com

Cahaba Federal Solutions, LLC

445 Jan Davis Drive NW, Suite Huntsville, AL 35806-4540

Tim Sitterson

(703) 915-0109 tim.sitterson@cahabafederal.com

Envisioneering, Inc 5904 Richmond Hwy, Suite 600 Alexandria, VA 22303 Christopher Secor (CFO)

(571) 483-4128 mailto:dexter@apexdef.com mailto:cynthia.moon@axientcorp.com mailto:dshepard@bannerdefense.com mailto:tim.sitterson@cahabafederal.com csecor@envisioneering.com

Intrepid, LLC 990 Explorer Blvd. NW Huntsville, AL 35806

Firuza Baria (Director of Contracts) 256-705-6804 firuza.baria@intrepid.llc

Intuitive Research & Technology Corporation

5030 Bradford Dr. NW, Huntsville, AL 35805

POC: Tiffany Perry Email: tiffany.perry@irtc-hq.com Work: (256)-936-4238

Kairos Analytics, LLC

24160 Piney Creek Drive Athens, AL 35613-8136

Matthew Eddy (Owner & Operator)

(256) 777-7809 matthew.e.eddy@kairos-analytics.com

KODA

Technologies Inc.

620 Discovery Drive Building 2, Suite 100 Huntsville, AL 35806-2816

POC: Amanda Zimmerman Email:

amanda.zimmerman@kodatech.com Work: (256) 509-2710 Derek Gouker derek.gouker@kodatech.com

MDW Associates, LLC

1750 Tysons Blvd, Suite 1500 McLean, VA 22102

Nikki McMenamin (Director of Contracts & Pricing)

(410) 458-9375 nikkimcmenamin@mdw-associates.com

Monte Sano Research Corporation

(MSRC)

700 Boulevard South SW, Huntsville, AL 35802

POC: Angela S. Fazah, Vice President of Contracts Email: afazah@msrc.com Work: (256) 937-2407

Penta Research, Inc 641 Wynn Drive NW, Suite 104 Huntsville, AL 35816-1890

Mike A. Anderson (Sr. Business Administrator)

(256) 837-5553 X 122 Mike.anderson@penta-inc.com

PeopleTec, Inc.

4901-I Corporate Drive, Huntsville, AL 35805

Kristen Hepler (Contracts Administrator) kristen.hepler@peopletec.com

(256) 801-9051

Radiance Technologies, Inc

310 Bob Heath Dr NW Huntsville, AL 35806

Nicole Fletcher (Contracts Administrator)

(256) 489-8543 nicole.fletcher@radiancetech.com mailto:csecor@envisioneering.com mailto:firuza.baria@intrepid.llc mailto:matthew.e.eddy@kairos-analytics.com mailto:derek.gouker@kodatech.com mailto:nikkimcmenamin@mdw-associates.com mailto:Mike.anderson@penta-inc.com mailto:kristen.hepler@peopletec.com mailto:nicole.fletcher@radiancetech.com

T5 Solutions, LLC 18 Old Cove Place SE Gurley, AL 35748

Mark E Talbot

(256) 527-8091 talbot@t5solutionsllc.com

DISCLAIMER:

All information contained in this RFSB is preliminary as well as subject to modification and is in no way binding on the Government. This notice and the information presented herein will not obligate the Government in any manner. The Government does not intend to pay for information received in response to this RFSB. Respondents are solely responsible for all expenses associated with responding to this RFSB. This RFSB will be the basis for collecting information on capabilities available. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed.

mailto:talbot@t5solutionsllc.com