1-RFP26-06 Court Case Management Software FINAL 20251008.pdf

REQUEST FOR PROPOSALS (RFP)

Incorporated County of Los Alamos Procurement Division

101 Camino Entrada, Building 3 Los Alamos, NM 87544

RFP26-06 Court Case Management Software

Template Version: 20250321

NOTIFICATION REGARDING SUBMISSION PROCESS AND REGISTRATION INSTRUCTIONS

The Incorporated County of Los Alamos (“County”) has recently implemented a new on-line eProcurement portal. This new platform, Euna Procurement powered by Bonfire, provides the County’s electronic Bid and Proposal process (“County’s Procurement Portal”). It is where the County will post solicitation opportunities, including Invitation for Bids (IFB), Request for Proposals (RFP), Request for Qualifications (RFQ) and Request for Information/Interest (RFI). The County’s Procurement Portal will streamline the County’s Bid process for Bid or Proposal submission, acceptance, evaluation, and award. For vendors, the County’s Procurement Portal will enhance communication, allow for fast and accurate Bids and Proposals, and provide automatic notification about projects.

Registered vendors will view and submit Bids and Proposals electronically. The past practice of submitting electronic Bids and Proposals by email or submitting paper Bids and Proposals is being phased out. If you are seeing this notification in a solicitation document, submissions will be accepted ONLY electronically through the County’s Procurement Portal for this solicitation. It is every Offeror’s responsibility to read, understand, and submit Bids and Proposals in accordance with the instructions provided in and specific to each solicitation document.

Requested Action: Please register as a vendor on the County’s Procurement Portal by visiting https://losalamosnm.bonfirehub.com and click on “Register”. Registration is free and only takes a few minutes. Please be sure to select the applicable NIGP: The Institute for Public Procurement (“NIGP”) Commodity Codes for your business when you are prompted so that you can receive notification of recommended opportunities when they are sent out by the County to the NIGP Commodity Codes you have selected.

Already Have a Bonfire Vendor Account? If you already have a Bonfire vendor account and are already registered for another agency’s portal, you will still need to visit the County’s Procurement Portal at https://losalamosnm.bonfirehub.com and click on “Log In” to provide County-requested information, view open opportunities, receive opportunity notifications, and submit Bids and Proposals through the County’s Procurement Portal. You will be able to manage the multiple agencies with whom you do business through the button labelled “My Supplier Hub” in your Bonfire account.

For Bonfire Support, visit the Vendor Help Center at https://vendorsupport.gobonfire.com where you can view support articles and videos and search FAQ’s on all aspects of Bonfire. For personal assistance, you can email Support.Bonfire@eunasolutions.com . Support is available Monday to Friday from 6:00 a.m. to 6:00 p.m. Mountain Time.

https://losalamosnm.bonfirehub.com/ https://vendorsupport.gobonfire.com/ mailto:Support.Bonfire@eunasolutions.com

Template Version: 20250321

NEEDS STATEMENT

The Incorporated County of Los Alamos (“County”) is seeking a qualified service provider to provide a Court Case Management Software (“Software”) which is either On-Premise, Hybrid, or Hosted for use in the Los Alamos Municipal Court that complies with all federal, state, and local laws, rules and regulations, and to provide project implementation and management services to implement the Software (“Project”).

SOLICITATION INFORMATION

Solicitation No.

RFP26-06

Solicitation Title

Court Case Management Software

Single-step or Multi-step

Single-step

Requesting Dept.

Municipal Court

SOLICITATION SCHEDULE

Advertised October 12, 2025

Pre- Proposal Conference

Non-Mandatory – Virtual Format October 21, 2025 1:00 p.m. Mountain Daylight Time (MDT) via Microsoft Teams https://tinyurl.com/344fbp5y

Question Submission Deadline

October 28, 2025 2:00 p.m. MDT

Responses to Questions Issued by County

October 29, 2025 2:00 p.m. MDT

County reserves the right to issue responses at any time prior to this date.

Proposal Due Date and Closing

November 4, 2025 2:00 p.m. MDT

Late responses will not be considered

CONTACT INFORMATION

Procurement Contact Name

Derrill Rodgers

Title Deputy Chief Purchasing Officer

E-Mail derrill.rodgers@losalamosnm.gov

Phone No. 505.663.3507

ESTIMATED PROCESS SCHEDULE AFTER CLOSING

The estimated dates of the solicitation process after closing are tentatively planned as follows, are provided here for informational purposes only, and at County’s discretion, may be subject to change without prior notification. Discussions may be conducted with responsible offerors who submit Proposals determined to be reasonably likely to be selected for award for the purpose of clarification to ensure full understanding and conformation with the solicitation requirements for the purpose of obtaining best and final offers.

Proposal Evaluation

October 31, 2025 – November 21, 2025 mailto:derrill.rodgers@losalamosnm.gov

Template Version: 20250321

Contract Drafting, Legal Review, and Negotiations

November 24, 2025- December 22, 2025

County Council Approval

Required for contracts >$300,000.00 January 6, 2026

Estimated Contract Effective Date

July 1, 2026

1 ELECTRONIC SUBMISSIONS

A full copy of the solicitation and all associated documents can be found on the County’s Procurement Portal at https://losalamosnm.bonfirehub.com/. Only Proposals submitted through the County’s Procurement Portal by the Proposal Due Date stated herein, or as may be modified by addendum, will be considered. Late responses will not be considered. To register to view and download solicitation documents and submit a Proposal through the County’s Procurement Portal, follow the instructions on page 1 of this solicitation.

2 ADDITIONAL DOCUMENTS AND INFORMATION INCLUDED AS A PART OF THIS RFP

Additional documents are referenced in this RFP, which may include, but are not limited to, exhibits, attachments, links to documents online, and documents that are provided through the County’s Procurement Portal. Any such documents are considered to be a part hereof and constitute, along with this solicitation document and any addenda, the complete solicitation package. Documents required to be submitted as a component of Offeror’s Proposal will be noted as such in each individual solicitation posted on the County’s Procurement Portal, and Offerors will be unable to submit their Proposals through the County’s Procurement Portal until all required documents and information have been uploaded or provided by Offerors.

Please also reference “Proposal Format and Response Components” below.

3 GRANT RELATED INFORMATION

It is not anticipated that this project will be funded by a grant; no additional grant-related information provided.

4 QUESTIONS

Any questions must be received in writing at least five (5) business days prior to the submission due date, unless otherwise stated herein or in an addendum. Questions must be submitted through the County’s Procurement Portal. Please follow the instructions on page one (1) of this document to register for the County’s Procurement Portal to submit written questions. Offerors who submit questions via e-mail or by phone shall be redirected to submit written questions through the County’s Procurement Portal.

Offerors must submit in writing through the County’s Procurement Portal, as stated herein, any questions or requested clarification necessary for Offeror to provide a complete response with all Proposal response components and pricing included. Offerors are asked to refrain from including in Proposals statements such as “more information available upon request,” “pricing to be determined,” or other similar statements. Such statements and failure of Offeror to seek clarification

Template Version: 20250321 needed for Offeror to provide the requested information may result in an Offeror being found non-responsive or non-responsible. This in no way may be construed to conflict with County’s right to hold interviews and discussions for clarification with Offerors, as further described herein.

5 PRE-PROPOSAL CONFERENCE

The County will hold an optional, non-mandatory pre-Proposal conference via a virtual format on the date and time noted in the Solicitation Schedule for this RFP and on the County’s Procurement Portal.

The purpose of this conference is to allow potential Offerors to ask questions regarding this RFP and the County’s RFP process. Information about the virtual meeting will be sent to all entities that have registered for this solicitation opportunity through their County Procurement Portal Vendor Account.

County reserves the right to send pre-Proposal conference information to any vendors or requesting individuals.

6 MULTI-STEP PROCESS

This is a single-step RFP; multi-step process information does not apply.

7 DEMONSTRATION INFORMATION

The County, may at its sole discretion request that Offerors who, after initial review of Proposals, are found to be responsive and responsible provide a demonstration of their software during a virtual meeting held via MS Teams, or other virtual format acceptable to County. The primary purpose of demonstration is to evaluate how the software can meet the required software functionality and technical specifications as described in Proposals.

If the County elects to conduct Demonstrations, the meeting date, time, location, questions, and software demonstration instructions will be coordinated with and e-mailed to responsive and responsible Offerors before the demonstration. County will release demonstration scripts to each responsive and responsible Offeror via-e-mail approximately one (1) week in advance of scheduled demonstrations. Scripts may include instructions and questions common to all responsive and responsible Offerors. And may also include questions specific to an Offeror for the purpose of clarification to ensure full understanding and conformation with solicitation requirements for the purpose of obtaining best and final offers.

Each demonstration will consist of no more than two (2) hours for responsive and responsible Offerors to demonstrate how the proposed software provides the requested software features and functionality as described in the RFP and no more than one (1) hour for Evaluation Committee Member questions and answers.

The responsive and responsible Offerors team should include, but not be limited to, the following individuals unless otherwise proposed and accepted by County:

Person(s) who supports server and database hardware.

Person(s) who support integrations with those County systems specified herein.

Person(s) who are able to discuss helpdesk support functions and roles.

Person(s) who will answer committee member questions.

The person with primary responsibility and final authority for the project throughout the term of any potential Agreement.

8 GENERAL INFORMATION

8.1 About Los Alamos County. The Incorporated County of Los Alamos is situated at the foot of the

Jemez Mountains on the Pajarito Plateau with an elevation ranging from 6,200 feet to 9,200 feet.

Los Alamos is an incorporated county, established under a special provision of the State

Template Version: 20250321 constitution, giving it both county and municipal authority and powers. Two distinct communities, Los Alamos Town site and White Rock, each with its own visitor center, are home to ~19,000 people. Los Alamos is mostly known for the historic accomplishments of its largest employer, Los Alamos National Laboratory, and continues to gain notice for its vast scenic assets and recreational opportunities. Visit the Los Alamos County website (www.losalamosnm.us) and the tourism website (www.visitlosalamos.org) for more information.

8.2 Unless otherwise defined, the following terms may be used interchangeably throughout this RFP:

“Offeror,” “Contractor,” and “Vendor” “Proposal,” “Response,” and “Submittal” “Software,” “Solution,” and “System” “Project” and “Services” “RFP” and “Solicitation”

8.3 The County invites Proposals from all qualified respondents. No Proposal may be withdrawn after the scheduled closing time. Proposals will not be accepted after the scheduled closing time.

Please make note of the submittal requirements outlined in this solicitation. Read and follow the instructions carefully. Include the required documents stated in this RFP as part of your submittal packet. Any misinterpretation or failure to comply with the submittal requirements could result in rejection of the Proposal. Proposal preparation is at the Offeror’s expense.

8.4 Any change(s) to the solicitation will be conveyed through the written addenda process. Read carefully and follow all instructions provided on any addendum, as well as the instructions provided in the original solicitation. Offerors are expected to acknowledge receipt of addenda by submitting signed copies of addenda with the submitted Proposal.

8.5 County reserves the right, at its sole discretion, to accept or reject any Proposals; to waive any and all irregularities in any or all statements or Proposals; to request additional information from any or all respondents; and to award a contract to the responsible Offeror whose Proposal is most beneficial to County. While County intends to execute a contract for the services listed herein, nothing in this document shall be interpreted as binding County to enter into a contract with any Offeror.

8.6 Proposals are Public Records. Pursuant to the New Mexico Inspection of Public Records Act, NMSA 1978, Chapter 14, Article 2, all materials submitted under this RFP shall be presumed and considered public records. Except to the extent any information may be protected by state or federal law, Proposals shall be considered public documents and available for review and copying by the public. County declines to sign any non-disclosure agreements or confidentiality agreements submitted by potential Offerors. If an Offeror fails to submit information requested in the RFP that Offeror considers to be confidential, the County reserves the right to find any Offeror’s Proposal non-responsive or non-responsible based on the information provided in or excluded from Offeror’s response.

8.7 The County contemplates a multi-term contract as a result of this RFP. The term of the contract may be for a period of up to fifteen (15) years. This is the written determination of the Chief Purchasing Officer that such a contract will serve the best interests of the County by promoting economies in County procurement.

8.8 Offerors are notified that they must propose pricing for each potential year of the contract. County may consider, but is under no obligation to accept proposed cost escalators (e.g., a proposed specific dollar amount) or a cost escalator mechanism (e.g., an annual percentage escalator or use of a Consumer Price Index or Producer Price Index) for future years of an agreement.

Pursuant to County Ordinance, the use of a cost-plus-a-percentage-of-cost contract is prohibited.

Template Version: 20250321

8.9 Offerors are informed that State law requires that all foreign corporations (NMSA 1978 §53-17-5) and limited liability corporations (NMSA 1978 §53-19-48) procure a certificate of authority to transact business in the state prior to transacting business in the State of New Mexico.

8.10 The Chief Purchasing Officer has determined a preference is applicable to this solicitation. Offerors must submit a written request for preference, using the Request for Preference form provided through the County’s Procurement Portal, with a copy of the applicable state-issued preference certificate, with its Proposal to qualify for preference. Ref. County Code Section. 31-261(b) and Section13-1-21 NMSA 1978 et al.

9 PROPOSAL REVIEW AND EVALUATION

Proposals shall be handled so as to prevent disclosure of the identity of any Offeror or the contents of any Proposal to competing Offerors during the process of negotiation.

After the RFP has closed, Procurement Division staff prepares a register of Proposals containing the name of each Offeror, the number of modifications received, if any, and a description sufficient to identify the item offered. The register of Proposals is open to public inspection only after contract award.

Procurement Division staff releases Proposals to the Evaluation Committee. The Evaluation Committee reviews and evaluates the submittals. If interviews are conducted, they may only be for the purpose of clarification and may be used for adjusting the final score. Discussions may be conducted with responsible offerors who submit Proposals determined to be reasonably likely to be selected for award for the purpose of clarification to ensure full understanding and conformation with solicitation requirements for the purpose of obtaining best and final offers. For proposals that qualify for Preference, as described in the Request for Preference form provided through the County’s Procurement Portal, preference factors will be applied as applicable in accordance with the most current County Code Section 31-261(b) and NMSA 1978 Section 13-1-21 et al., as may be modified from time to time.

The Evaluation Committee Chairperson provides final evaluation results to the Procurement Division.

Award shall be made to the responsible Offeror whose Proposal is determined in writing by the Evaluation Committee to be the most advantageous to the County, taking into consideration the evaluation criteria set forth in the solicitation.

10 AWARD OF SOLICITATION

Following award of the solicitation, the successful Offeror will be required to execute a contract with County in accordance with the terms and conditions set forth in the Sample Agreement, which is provided through the County’s Procurement Portal. Offerors must identify any exception or other requirements, if any, to the terms and provisions in the Services Agreement, along with proposed alternative language addressing the exception. County, as a governmental entity, is subject to certain laws and prohibitions and may, but is not required to, negotiate changes in contract terms and provisions, but will not agree to language that is in violation of the law. The Agreement as finally agreed upon must be in form and content acceptable to County.

11 OBLIGATIONS OF FEDERAL CONTRACTORS AND SUBCONTRACTORS; CONTRACT

CLAUSES

Federal Contractors and Subcontractors shall abide by applicable state and federal requirements, which may include but are not limited to all the provisions set forth in 29 CFR Part 471, Appendix A to Subpart A, and may be required to be included or incorporated by reference into the Agreement.

Template Version: 20250321

12 ILLEGAL ACTS

The County Procurement Code, Article 9, imposes remedies and penalties for violation of the County Code. In addition, New Mexico criminal statutes impose felony penalties for illegal bribes, gratuities, and kickbacks.

13 CERTIFICATION FORM REGARDING DEBARMENT, SUSPENSION, AND OTHER

RESPONSIBILITY MATTERS

Offerors are requested to complete the Certification Regarding Debarment, Suspension, and Other Responsibility Matters Form, provided through the County’s Procurement Portal, and submit with the Proposal. If this completed document is not included with the Proposal, it must be provided prior to the evaluations of the received Proposals, otherwise the Offeror’s Proposal will not be considered. This Form serves as a warrant of the Offeror’s responsibility and may not necessarily preclude the Offeror from consideration for award.

14 CAMPAIGN CONTRIBUTION DISCLOSURE FORM

A Campaign Contribution Disclosure Form is provided through the County’s Procurement Portal.

Offerors are requested to complete and submit with the Proposal. If the Form is not submitted with the Proposal, upon award, Contractor must submit this form prior to County’s obligation to pay for the services.

15 VERIFICATION OF AUTHORIZED OFFEROR

A Verification of Authorized Offeror Form is provided through the County’s Procurement Portal. Offerors are requested to complete and submit with the Proposal. This Form provides County with the name and information of the authorized Officer who can obligate the selected firm in providing the services to the County.

16 BACKGROUND INFORMATION RELATED TO THE SCOPE OF WORK OR SERVICES

The current solution utilized by the County is an On-Premise solution and contains roughly 2500 tables, housed in an Oracle Database, 19c Standard Edition 2. The solution currently holds 25 Gigabytes of data, and contains cases as far back as the 1950s. The records retention requirement for most cases is seven (7) years, with Driving Under the Influence (DUI) case retention is fifty-five (55) years. The current system interfaces with the County’s Computer Aided Dispatch (CAD) and Records Management System (RMS), provided by Infor Public Sector and EIS to allow for the transfer of citation information from CAD and RMS to the Court Case Management solution.

17 SCOPE OF WORK OR SERVICES (“SCOPE”)

17.1 Software Requirements.

17.2 Licensing and/or Subscription. Selected Offeror shall provide for County an On-Premise, Hybrid, or Hosted Solution, developed, owned, and operated by Contractor (“System,” “Software,” or “Solution”) that complies with all federal, state, and local laws, rules, and regulations to provide Court Case Management. Offerors are asked to describe in their RFP response all related licensing or subscription information County will be asked to consider prior to utilizing the Services.

17.2.1. Should Offeror’s product roadmap include a transition from On-Premise to a Hybrid or

Hosted Solution, during the contemplated term of up to fifteen (15) years , describe in the response how such a transition would be conducted, what implementation services would be provided, and what training services would be provided for the transition from On- Premise to a Hybrid or Hosted Solution. County anticipates that such a transition would be conducted at no additional fee.

Template Version: 20250321

17.3 Maintenance and Support Services and Service Level Agreement. Contractor shall use commercially reasonable efforts to make sure the Software is available with the uptime percentage proposed in Contractor’s RFP response. Offerors are asked to describe in their RFP response their Service Level Agreement (“SLA”), guaranteed uptime for their Software, describe any remedy or rebates should Offeror not meet the service commitment, and describe how such a remedy or rebate would be applied throughout the term of an agreement.

17.3.1. Contractor shall provide product maintenance and customer support throughout the term of an Agreement. Offerors are asked to describe in their RFP response all offered Software maintenance and support services and tools, including Software patches and updates, access to any available online libraries, issue reporting tools, toll-free numbers, hours of service, process for requesting after-hours support in case of emergencies, and the process for issue resolution and/or escalation. Descriptions of offered support should be separated between the support offered to different types of Users so that the level of support and methods for requesting support for each different type of User is clear and all support costs must be provided in Offeror’s cost Proposal in the Cost Proposal Worksheet, document provided on the County’s Procurement Portal.

17.3.2. Contractor shall provide and adhere to a communication plan for communicating System upgrades and all other maintenance and service interruptions. Offerors are asked to describe this communication plan in their Proposals, which should include, but is not limited to the following:

17.3.2.1 The methodology for testing and certifying upgrades and patches to ensure that they work properly and the mechanism of versioning rollback in case of issues;

17.3.2.2 The process of applying upgrades and patches including if there are County responsibilities and a responsibility matrix for the tasks involved;

17.3.2.3 A brief history of product upgrades and interim patches or fixes released in the last eighteen (18) months; and

17.3.2.4 Identification of the most current stable release and patch level, certified for support, for all Software and firmware and acknowledge that all Software and firmware will be installed to those levels.

17.4 Warranty. Contractor shall, at a minimum, warrant that the Software shall be without material defects for the term of an Agreement. If Software does not perform as warranted, Contractor shall use reasonable efforts, consistent with industry standards to cure the material defects or provide County with a functional equivalent at no additional cost. Offerors are asked to describe in their RFP response their warranty for Software performance.

17.5 Data Security and Ownership. Offerors are asked to describe in detail in their RFP response how they provide data security and are asked to note any deviations or exceptions to the data security and ownership stated here in the Scope of Services.

17.5.1. At a minimum, Contractor shall maintain adequate security and disaster recovery protocols.

Contractor’s Cloud Service Provider (“CSP”) and data center, preferably in Government Cloud (“GCC”), shall be located within the United States. Offerors are asked to describe the following in their Proposal:

17.5.1.1 How the Solution meets any applicable statutory requirements for data;

17.5.1.2 Security measures in place to protect the System and its data, including disaster recovery and continuity plans;

17.5.1.3 Information on hosted or cloud service provider’s data center, including location and internet connectivity, and information security compliance;

17.5.1.4 Identify any encryption algorithms used; and

17.5.1.5 The policies that apply to and notification measures to be used in the event of a security breach;

17.5.2. All data that: (i) is owned by County; and (ii) uploaded into the Software will remain owned by County. County is responsible for the accuracy and legality of all such data and shall represent and warrant the right to use and manage all data in connection with its use of the Software. Use of Contractor’s Software confers no ownership rights to the Contractor and County materials and data may be used by the Contractor only as necessary to provide contracted Services.

Template Version: 20250321

17.5.3. Upon County’s request Contractor shall provide a data extract at any time in various formats including, but not limited to, comma separated value (“CSV”) or Microsoft SQL Server (“MSSQL”). Offerors are asked to describe access to the County’s data via Open Database Connectivity (“ODBC”) or alternative method, and any limitations to that access.

Affirm the ability to provide data to County within a forty-eight (48) hour window or describe Offeror’s proposed timeframe.

17.5.4. Contractor shall timely provide any other records requested by the County for response to Public Records Inspection requests under NMSA 1978, Chapter 14, Article 2. Offerors are asked to describe support provided for performing legal discovery on the System.

17.5.5. Upon termination of an Agreement, Contractor shall provide all data to County in CSV or MSSQL format, or a different format agreed to by County. Contractor shall then ensure destruction of any remaining County data in their System. Offerors are asked to describe the method(s) of turning over County data and providing a reader for that data upon termination of Services and describing how County’s data would be recovered should Contractor cease operations.

17.6 Software Functional Descriptions, Technical Specifications, and Integration with County Systems.

17.6.1. Software Functional Descriptions and Technical Specifications.

17.6.2. Contractor’s Software shall substantially conform to the functional descriptions and technical specifications proposed in Offeror's RFP response and agreed to by County.

17.6.3. The Software Functionality Matrix describes County’s base mandatory and preferred

Software functionality and technical specifications requested. County requests a complete and comprehensive list and description of all Software features and functionality currently offered that may be considered by County for inclusion in an Agreement with the selected Offeror, whether they are included as a standard part of the base Software subscription or offered optionally for free or optionally for purchase for an additional fee.

17.6.3.1 Offerors are asked to describe in their RFP response, using the Software Functionality Matrix, additional and optional tools, features, functionality that are included by Offeror as part of the base Software subscription pricing, which may not already be described in the Software Functionality Matrix, and include the pricing in their cost proposal.

17.6.3.2 Offerors are asked to describe in their RFP response, using the Software Functionality Matrix any additional and optional, tools, features, and functionality offered that are not included by Offeror as part of the base Software subscription pricing, but may be purchased and included in an Agreement upon County request, and include pricing in their cost proposal.

17.7 System Users and Use.

17.7.1. Authorized County users should, at a minimum, be able to access the Software via local personal computer (PC)-based internet browsers and the internet through secure internet connections and protocols. Software should have the ability to keep and maintain account usernames and passwords in a secure manner using industry standard encryption algorithms.

17.7.2. Offerors are asked to describe in their RFP response, using the Software Functionality Matrix where requested how different types of users would be granted access to the Software and how many County users would be given access.

17.8 Integration with or Migration to County Systems.

17.8.1. Offerors are asked to describe in their RFP response, using the Software Functionality

Matrix if and how their proposed Software integrates with any of the Systems described therein and any of the Systems described herein under Background Information and Section 18.8.

17.8.2. County’s preference is that Offeror’s Software have the ability to interface with Tyler Munis and/or Tyler Cashiering Financial Management System. The interface may either be through use of an API or through a file upload of financial/cashiering transactions from the Software. Offerors are asked to describe this available process in detail. Offerors are

Template Version: 20250321 asked to include in their cost proposals any fees for such integration services and automated updates.

17.8.3. County’s preference is that Offeror’s Software have the ability to interface with First Data, the County’s current Credit Card Processing contractor. Offerors are asked to describe this available process in detail. Offerors are asked to include in their cost proposals any fees for such integration services and automated updates. If First Data is not an available option Offerors are asked to identify the Credit Card Processors who can be integrated with Offerors Software.

17.8.4. Integration with County Systems Offerors are asked to describe in detail in their RFP response, using the Software Functionality Matrix, if and how their proposed Software can share data with all of the County Systems described therein and the integration process for any of the data requirements defined therein. Those systems are summarized below again for the convenience of Offerors. The exact manner in which systems integrate or data is shared between systems is to be determined based on methods proposed.

17.8.4.1 Infor - CAD

17.8.4.2 EIS – Law Enforcement RMS – ability to download and upload into the Court

Case Management system needed.

17.8.4.3 Tyler Munis (Cashiering)

17.8.4.4 First Data (Credit Card Processing)

17.8.4.5 Authorize.net (includes Citepay)

17.8.4.6 Single Sign On (“SSO”) to County’s MS Azure Active Directory

17.8.5. Migration of Data. County currently has 25 GB of files which represent 75 years of data housed in the current on premises solution, in an Oracle database format. Offeror’s are asked to describe in their RFP response, their capabilities to migrate the data and the process for doing so.

17.9 County Technical Standards. Software shall conform to the applicable County requirements for on-premise, hybrid or cloud/hosted Solutions as defined in the Los Alamos County Technology Standards. Using the County Technology Standards Requirements for On-Premise, Hybrid, or Cloud/Hosted Solution Solicitations, provided in the County’s Online Procurement Portal. Describe Offeror’s ability to conform to the applicable County requirements for on-premise, hybrid or cloud-hosted solutions. and to briefly describe how they meet the requirements, or describe alternate methods for how they meet applicable requirements. County may, at County’s sole option, consider proposed Software Solutions that offer an alternate method for meeting applicable requirements.

Note that On-Premise solutions should utilize Microsoft (MS) Windows Server 2019, 64 bit or current (Standard and Datacenter), and the database should utilize Microsoft (MS) SQL server version 2019 and above, per the County Technology Standards.

17.10 Compliance with Laws, Regulations, and Industry Standards and Audit Reports.

Contractor and Software shall, throughout the term of an Agreement, comply with any and all applicable provisions of local, state, or federal law regulating such Software. Offerors are asked to describe in their RFP response their compliance with applicable laws, regulations, and industry standards and to describe any regulatory compliance related assistance Offeror may provide to County and any associated costs. It is expected that Offerors have knowledge of all applicable industry standards, laws, and regulations and are able to fully describe how they comply.

18 Project Initiation Meeting. Contractor shall, within ten (10) business days from the Effective Date of an Agreement, or within a timeframe proposed in Offerors RFP response and agreed to by the County, schedule a Project Initiation Meeting with the County’s Project Manager and designated County staff (“Project Team”) at a date, time, and format to be agreed upon by both Parties. Offerors are asked to propose in their RFP response their process for scheduling and conducting a virtual Project Initiation Meeting, the length of the meeting, the materials Offeror would provide, any deliverables to be prepared in advance, and any additional topics to be addressed during the Project Initiation Meeting. As part of the Project Initiation Meeting, the Parties shall, at a minimum, unless otherwise proposed by Offeror in their RFP response and agreed to by County:

18.1 Establish a mutually agreed upon Project Schedule to accomplish key tasks with durations for each task conforming substantially to the Offeror’s Proposed Project Plan and Schedule. The Project

Template Version: 20250321

Plan and Schedule shall include, at a minimum, due dates for deliverables, Project phases, and milestones.

18.2 Review the scope of work and identify any Project issues to be addressed in the course of the Project.

18.3 Establish communication protocols, meeting frequency, and meeting format, with meetings occurring online in a virtual format.

18.4 Identify document format and data transfer methods between Contractor and Project Team related to the performance of the Agreement.

18.5 Contractor shall provide detailed and complete written documentation of this meeting and a Project Plan and Schedule to the County within ten (10) business days of the meeting. The Project Plan and Schedule shall be subject to the County Project Manager review and approval and Project Implementation shall commence only after the County approval of the Project Plan and Schedule, which may be adjusted throughout Project implementation upon mutual written agreement of both parties.

19 Project Management

19.1 Contractor shall provide experienced, competent, and knowledgeable staff to provide Project management services for the successful implementation of the Software, which may include, but may not be limited to Project planning in coordination with the County’s Project Manager; data transfer from County’s current records, Project monitoring, control, and reporting; Project development and execution of tasks; scope management; risk management; and Project scheduling.

19.2 County and Contractor shall designate in writing a primary contact (the “Project Manager”) to represent each party to serve as a primary point of contact, to manage the overall implementation, and help coordinate personnel during the design, development, installation, training, and maintenance of the System.

19.3 County shall not be liable for, and shall not provide insurance for, any loss or damage incurred by Contractor or its employees, agents, contractors, or subcontractors or to equipment or property owned by Contractor, regardless of whether such losses are insured by Contractor.

19.4 Contractor shall provide experienced, competent, and knowledgeable staff to successfully complete the implementation and any mutually agreeable Project Implementation Management Plan and Project Plan. In the event that any Contractor employee is found to be unacceptable to County, in County’s reasonable discretion, Contractor will be given an opportunity to cure the deficiency upon notice thereof from County. In the event the deficiency persists, County may require removal of the employee. Contractor shall provide a suitable replacement, acceptable to County in its reasonable discretion, as soon as reasonably possible. To the extent County delays in confirming Contractor's proposed replacement, Contractor will not be held liable for project delays that arise because of County’s delay.

19.5 County acknowledges that Contractor assigned personnel may leave the project for reasons outside Contractor's control, such as resignation, medical leave, or similar absences. Contractor shall use its best efforts to ensure the continuity of Contractor employees assigned to the County’s implementation. Should Contractor remove or reassign its employees assigned to perform Services, Contractor will, a) provide reasonable advance notice to County, and b) assign alternate employees with equivalent or greater competence, knowledge, and experience to perform Services hereunder within a commercially reasonable timeframe. Contractor's failure to provide the continuity of Contractor employees shall result in Contractor's sole responsibility for any delay and/or cost for such failure and may result in breach of an agreement.

19.6 Contractor's personnel and subcontractors, if any, shall observe all applicable laws, rules and policies of County, while providing Services to County, working on County’s premises, including working remotely on County systems.

19.7 Contractor shall represent and warrant to County, with respect to the Services to be performed, that each of its employees assigned to perform those Services shall have the proper skill, training, and background to be able to perform his or her assigned Service(s) in a competent and professional manner, and that all Services will be performed in accordance with the resulting Agreement.

Template Version: 20250321

19.8 County acknowledges that the implementation is a cooperative process requiring the time and resources of County personnel. County shall, and shall cause County personnel to, use all reasonable efforts to cooperate with and assist Contractor as may be reasonably required to timely implement the Products as mutually agreed Contractor shall not be liable for County’s failure(s) to comply with the foregoing commitment.

20 Project Implementation.

20.1 The County’s preference is to conduct all project implementation and training tasks remotely with

Contractor.

20.2 The County’s preference is that Offerors use a table or spreadsheet format or a critical path schedule generated from a project management software to provide this information in summarized form with a more detailed narrative provided separately to explain Offeror’s approach and methodology.

20.3 Project phases proposed should include, but should not be limited to, a phase for initial set-up, implementation, and training of a smaller group comprised of the County’s Project Implementation Team, and a separate later phase to include user account set-up, rollout, and training to a larger group of County-wide system users and administrators, including users, and administrative staff.

All training should be described in more detail as described in section 24 below.

20.4 Offerors are asked to state the estimated length of complete implementation for the County. Rather than using a specific start date, Offerors are asked to use “Upon the Effective Date of an Agreement” as their starting date and conclude with the conclusion of System testing and acceptance and a minimum “30-day System Reliability Testing Post Go Live” period to define the estimated length of time project phases or tasks may take to complete.

20.5 Offerors should include in the proposed schedule a phase or task that includes coordination with the County’s Project Manager, and Information Management staff, if necessary to perform any data migration described herein, and specifically identified in section 17.8.5.

20.6 Offerors are asked to describe their methodology for developing Test Plans during implementation to ensure proper setup and functionality of all features prior to the County acceptance of each deliverable and prior to the County’s overall System acceptance prior to Go Live. Describe the methodology for User Acceptance and Final Acceptance and describe any other processes that are employed for quality assurance. Include these phases or tasks in the proposed implementation strategy and schedule.

20.7 The proposed strategy, schedule, and naming conventions used in the narrative and proposed schedule should align clearly with the Project Management and Implementation costs and deliverables proposed in the Software Functionality Matrix clearly demonstrate costs associated with each task or phase of implementation.

20.8 Offerors are asked to describe their project change order process and controls during the implementation.

20.9 If proposing progress payments throughout Project implementation, Offerors should affirm their understanding that the County will only pay for services successfully provided and accepted as complete by the Project Manager, should describe their process for obtaining acceptance of completion by the Project Manager, and should describe at which stages or phases in the implementation payments would be requested by Offeror after deliverables or milestones are accepted by the County.

20.10 Offerors are asked to disclose if any national and regional user groups exist or if Offeror provides online forum access for users to meet and discuss the different ways in which the System can be implemented.

21 Training and Consulting.

21.1 Contractor shall provide, upon County’s request, training or consulting to County staff for the use of the Software. County’s preference, though not a requirement, is that all costs for Offeror to provide any training is rolled into the license or subscription fees proposed and that Offeror’s provide training as needed and requested by County at no additional cost to County. County may consider, but is under no obligation to accept, pricing for training and consulting that is charged

Template Version: 20250321 separately from license or subscription fees. Offerors are asked to describe in detail in their RFP response, using Cost Proposal Worksheet Tab 05, all training and consulting Offeror may provide throughout the term of an Agreement, the length of the training, the format of the training (e.g., virtual or in-person), the cost per session, the total number of attendees allowed, and specifically which training and consulting is included in Year 1 Project Management and Implementation Services and which training is available after conclusion of Project Implementation. Year 1 Training during Project implementation should include, at a minimum:

21.1.1. Training sessions for the Project Team, users and administrative staff, estimated to be approximately ten (10) trainees, which County may, at County’s sole discretion increase or decrease; and

21.1.2. Ongoing on demand training as needed for users and administrators.

21.2 Offerors are asked to include in Proposals a list of any subcontractors or third parties Offeror may use to provide training and consulting services.

22 Additional, Optional, and Future Functionality and Services. For award of an agreement, County requires a not to-exceed (“NTE”) amount for total compensation for the entire term of an agreement.

In order to estimate the total NTE amount of a potential agreement, the County requests proposed pricing or a proposed pricing mechanism for additional, optional, and future functionality and services, which may include, but is not limited to tools, modules, apps, add-ons, or professional services not specifically named or requested herein. County’s desire is for Offerors to propose all potential additional, optional, and future functionality and services and all associated fees for County’s consideration.

22.1 Contractor may continually develop, alter, deliver, and provide to the County ongoing innovation to the Services in the form of new features, functionality, and efficiencies as long as the functionality of the Services and Licensed Software does not fall below the functionality requirements proposed and agreed to by County. Upon County request, and at County’s sole discretion, Contractor shall provide additional, optional, managed, and professional services as proposed and in accordance with fees proposed and agreed to by County.

22.2 No-Cost Offerings. Contractor, as part of the Service, throughout the term of an Agreement may offer at no additional cost to the County, additional, optional, and future functionality and services not specifically named herein or in the RFP response and may provide such free services upon County request.

22.2.1. For such free offerings and enhancements, Offerors are asked to describe in their RFP response their migration, customization, upgrade process, and change order process and controls for the addition of these additional, optional, and future functionality and services after completion of Project Implementation and initial System acceptance and how they would be made available to County.

22.3 Offerings for a Fee. Contractor, as part of the Service, throughout the term of an Agreement may offer additional, optional, and future functionality and services, not specifically named herein, at an additional cost to the County, provided sufficient information about the process for implementation, customization, upgrades, costs and pricing details are provided in the Offeror’s RFP response and included in the awarded Agreement.

22.4 Offerors are asked to describe in their RFP response their migration, customization, upgrade process, and change order process and controls for the addition of additional, optional, and future functionality and services after completion of Project Implementation and initial System acceptance; how they would be made available to County; and describe how they would be priced as they become available (e.g., on a per quote/per project basis).

22.4.1. Offerors should propose in their RFP response, using the Cost Proposal Worksheet, their fees and hourly rates, for all applicable personnel types, that would be charged throughout the term of an Agreement to provide any future implementation or professional services County may require and request.

22.5 Possible Future Replacement or Implementation of Integrated Systems. If the County, throughout the term of an Agreement with the selected Offeror, implements new or modified software that must integrate with the Contractor’s Software, Contractor will work with County to ensure integration between County’s new or modified systems and Contractor’s Software, if

Template Version: 20250321 integration is possible, and will provide other implementation services that may be necessary for integration. Offerors are asked to propose hourly rates, or some other type of fee structure, to provide such professional services throughout the term of an agreement and describe their process for County to request such integration services in the future.

23 PROPOSAL FORMAT AND RESPONSE COMPONENTS

23.1 Offerors must submit a Proposal to the County in the format described herein, subject to Section 8.5, and through the County’s Procurement Portal. Information provided in the Proposal may be used in the contract between the successful Offeror and the County.

23.2 To facilitate the review process, unless otherwise stated herein, County’s preference, though not a requirement, is that Proposals be limited to fifty (50) pages, not including exhibits, attachments, or marketing materials; that Proposals are 8.5 x 11 inch format; and that general marketing materials should not exceed ten (10) pages.

23.3 Unless otherwise specified herein or on the County’s Procurement Portal, Proposal documents should be submitted in PDF format.

23.4 For uniformity in the Proposal review process, please sequence Proposals as shown below using the same header names as below. Additional information may be included by Offerors in attachments, provided that Proposals include and address, in the sequence requested, the elements requested in the Proposal Format and Scope.

23.5 Whenever describing Offeror’s ability to provide the services described in the Scope, reference the header for that section and restate the section to which Offeror is responding.

23.6 As determined acceptable by the evaluation committee, the successful Offeror will be selected to provide some or all of the services described herein,…