Invitation to Negotiate

ITN SJAA 2026000005:

Professional Licensing and Regulation Platform Published February 26, 2026

Vendor Response Signature Page *(ITN# SJAA 2026000005 and Professional Licensing and Regulation Platform) VENDORS: See the solicitation document below for the response deadline and other response submission information and requirements.

Vendors responding to this solicitation must fill out this page in its entirety, sign and return with vendor’s response. This page must bear a physical or electronic signature, as electronic signature is defined in the "Uniform Electronic Transactions Act", section 24-71.3-102 (8), evincing an intent by the vendor to be bound by its response. Failure to do so may disqualify the vendor response.

The undersigned understands and agrees that misrepresentation made in this response and/or subsequent discussions or information presented to the State may be deemed sufficient cause for the refusal by the State to execute a contract as a result, and that that later discovery of any omission or misrepresentation made in the solicitation response and/or subsequent discussions or information presented to the State may be grounds for the cancellation of an existing contract.

LEGAL COMPANY NAME (OFFEROR)

VENDOR INSERT: Full Legal Company Name

AUTHORIZED SIGNATURE

By: Name of Person Signing for Contractor V42225 Invitation to Negotiate Page 2 of 32

TYPED/PRINTED NAME

VENDOR INSERT: Signer’s Full Name

TITLE

VENDOR INSERT: Title of Signer

PHONE NUMBER

VENDOR INSERT: Signer’s Phone Number

EMAIL ADDRESS

VENDOR INSERT: Signer’s Email Address

CONTACT FOR CLARIFICATIONS

VENDOR INSERT: Name of Contact

TITLE

VENDOR INSERT: Title of Contact

PHONE NUMBER

VENDOR INSERT: Phone Number of Contact

EMAIL ADDRESS

VENDOR INSERT: Email Address of Contact

TABLE OF CONTENTS

1. GENERAL INFORMATION

A. General Information On behalf of the State of Colorado (“State”), Department of Regulatory Agencies is issuing this Invitation to Negotiate for a Professional Licensing and Regulation Platform.

B. Purpose of this ITN The purpose of this ITN is to obtain a long-term technology solution to facilitate all aspects of state professional regulation within an enterprise environment. The term professional regulation management for purposes of this ITN encompasses:

· The licensing, permitting, registration or certification of any individual, organization, facility, equipment, product or service.

· Associated regulatory enforcement activities, including file management, case processing and disposition, inspection and investigation management and compliance monitoring.

· Associated tasks and processes, including contact information, ownership and management relationships, document management, exam and experience history and Continuing Education (CE).

· Cash management, electronic credit card and checks in addition to currency in the form of cash, checks and money orders for payment of application fees, fines, permits, etc.

The Department prefers to obtain a single solution but reserves the right to award to more than one vendor and/or to separate the goods/services into multiple awards with different vendors if determined to be in the best interest of the State.

C. ITN Overview and Authority

i. This ITN is issued pursuant to, and subject to the State of Colorado Procurement Code (§24-101-101 through §24-112-101, CRS) and its enabling Procurement Rules, 1 CCR 101-9. Any conflict between the information in this ITN and the Procurement Code or Procurement Rules will be resolved in favor of the applicable provision of the Procurement Code or Procurement Rules.

ii. For more information on the ITN solicitation process, reference our Invitation to Negotiate process overview training for vendors.

iii. Unless otherwise specified elsewhere in this ITN, any definitions in this ITN are supplemental to the definitions in the Procurement Code and Rules. In the event of a conflict of terms, the order of precedence will be the Colorado Revised Statutes, the Procurement Rules, the Personal Services Draft Contract, and finally this ITN.

D. Electronic Procurement System (EPS)

i. The State posts solicitations on an electronic procurement system (EPS). Vendors who have an interest may submit a response in accordance with the terms of the ITN.

ii. This solicitation is being published on Colorado Vendor Self Service (Colorado VSS), so that Offerors who have an interest may submit a proposal in accordance with the terms of this solicitation.

iii. Vendors can self-register for this system free of charge, or may click on “Public Access” on the website to view solicitation documents and modifications without registering. Vendors are encouraged but not required to register prior to or at the time they submit their response. The State also recommends that interested vendors check the EPS on a regular basis throughout this solicitation process.

E. State Point of Contact

i. The State’s sole point of contact for this solicitation is Kristine Contreraz, Purchasing Agent IV, who may be reached via email at Kristine.Contreraz@state.co.us, or via phone at 303-894-7765.

ii. Because phone lines may not be consistently monitored, email is the preferred method of communication. The individual listed above is the sole point of contact for this solicitation. Initiating contact with anyone other than this individual may result in Offeror disqualification.

F. Schedule of Activities

i. This Schedule of Activities is for information and planning purposes only. Schedules for Activities listed as “Estimated” may be subject to change depending on the needs of the State. All times are considered in Mountain Time (MT), as adjusted for daylight savings.

Send Inquiries to Kristine.contreraz@state.co.us

ii. Performance Period

a. It is anticipated the contract performance period will begin September 1, 2026, for an initial period of three years with up to seven renewals of one year or less. This is subject to negotiation and final award date.

G. [RESERVED]

H. Vendor Inquiries

i. Vendors may make written inquiries (via mail or email) concerning this ITN to obtain clarification of requirements. The State may not accept inquiries after the date and time indicated in the Schedule of Activities. Send all inquiries to the State POC identified above. Inquiries must be clearly marked with the ITN number and title. Where appropriate, inquiries should include references to any relevant section/paragraph of the ITN.

ii. The State will publish responses to vendors’ inquiries collectively, in a timely manner, as a modification on the EPS. Vendors are responsible for monitoring Colorado VSS for such publication(s). Vendors shall not rely on any verbal statements that alter any specification or other term or condition of the ITN. Such changes are valid only if provided in writing by the State POC.

I. Contract Term Unless otherwise negotiated, the estimated contract performance period is expected to be three (3) years upon executing an awarded Contract with up to seven (7) renewals of one year or less. Note that the period beginning as negotiated with the Awarded Offeror, will be a period for transitioning the Contract from the current vendor to a new vendor, if necessary. The State shall not incur or pay for any costs associated with the transition.

The successful bidder shall absorb the costs associated with the transition period, if applicable. If the proposer includes any costs associated with a transition in their proposal, those costs MUST be clearly identified in the proposal. Any such costs will be added to the overall cost of the proposed solution. Offerors shall include the anticipated date by which its proposed solution would be fully functional to go live. The contract is expected to be awarded for a term of ten (10) years. No volume of work is guaranteed under this ITN.

The State reserves the right to perform an annual survey of State contract partners (or more frequently if deemed necessary) to determine the level of service that the Vendor is providing. The survey will provide data to ensure that the selected vendor is meeting all the contract requirements.

The initial contract(s) will be effective upon approval by the State Controller or designee. The contract performance contemplated herein shall commence upon the effective date of applicable contracts and shall be undertaken and performed in the sequence and manner set forth herein J. Modifications and/or supplemental information to the ITN

i. The State will publish any modifications, amendments or supplemental information to the ITN on the EPS. In the event that it becomes necessary to revise any part of this ITN, the State will post a modification notice on the EPS.

ii. It is the vendors’ sole responsibility to check the EPS on a regular basis, prior to the response submission deadline, as this is the primary means for communicating any clarifications or changes to ITN content, timeline and/or requirements.

iii. After the deadline for submission of a response to the ITN and during evaluation, all official communications are through the State POC.

K. Modifications or Withdrawal of Responses A vendor may modify or withdraw its response by written notice to the State POC prior to the established response submission deadline. Withdrawal of a vendor’s response following the response submission deadline and prior to award may be allowed, in the State’s discretion. Withdrawal of a vendor’s response after award is not allowed. Reference Procurement Rules R-24-103-201-08 and R-24-103-201-09 L. Mistakes and Minor Informalities in Vendor Responses In certain circumstances, a vendor may correct a mistake(s) in its response and/or the State may waive minor informalities. Reference Procurement Rule R-24-103-201-08.

M. Vendor Acceptance of ITN Terms / Vendor Response Content

i. A vendor response to this ITN shall constitute a binding offer. The autographic signature of the vendor shall indicate acknowledgment of this condition. Signature shall be that of a person legally authorized to execute contractual obligations. The response, including pricing, shall allow for a minimum of 180 calendar days for acceptance by the State, unless otherwise specified in this ITN. Reference Procurement Rule R- 24-103-201-11(d). It is acceptable for a vendor to offer a longer term.

ii. The contents of the response of the successful vendor, as negotiated, will become contractual obligations if acquisition action ensues. Failure of the successful vendor to accept these obligations in a contract, purchase order, or similar authorized commitment voucher may result in cancellation of the award to that vendor.

N. ITN Response Material Ownership All material submitted in response to this ITN becomes the property of the State.

O. Incurring Costs Vendors are solely responsible for all costs incurred as a result of responding to the ITN, to include participation in presentations or negotiations.

P. Confidentiality of the ITN Process

i. Following the ITN response submission deadline, individuals/entities may request from the State POC a list of the names of the responding vendors. All other information related to the ITN evaluation/negotiation/award process will remain confidential until award.

ii. Following the notice of intent to award, all vendor responses will be open to public inspection with the exception of information determined by the State to be a trade secret or confidential or proprietary. Reference §24-72-201 et seq., CRS, as amended, Public (Open) Records.

Q. ITN Cancellation / Rejection of Vendor Responses

i. The State may cancel this ITN, or any or all responses may be rejected in whole or in part, without penalty, at any time before a contract is executed, when it is in the best interests of the State. Reference §24-103-301, CRS, and related Procurement Rules. The reason and documentation supporting the decision to cancel the ITN or reject response(s) shall remain confidential for the lesser of six months or until the contract at issue is awarded by the State. Reference Procurement Rule R-24-101-401-05.

ii. If the ITN is cancelled after responses are received, the responses that have been opened shall be retained in the procurement record, or if unopened, returned to the vendors upon request, at vendor expense, or otherwise disposed of.

R. News Releases and Announcements Vendors shall not issue any news releases, communications or announcements of any kind pertaining to this ITN, vendor responses or award without prior written approval by the State.

S. Protested Solicitations and Awards An aggrieved party may file a protest concerning a material issue(s), at any phase of solicitation, including but not limited to, specifications, award or a disclosure of information marked confidential in the response. The protest shall be submitted to Department of Regulatory Agencies Procurement Official within ten (10) business days after such aggrieved person knows, or should have known, of the facts giving rise thereto. Reference §24-109-102, C.R.S., as amended, and Procurement Rule R-24-109-102-01, et seq. Protests should be submitted in writing via email to Kristine Contreraz at Kristine.Contreraz@state.co.us.

T. Vendor Assistance Any vendors needing support responding to solicitations may contact the Colorado Supplier Diversity Navigator at the Statewide Equity Office of Supplier Diversity. Services provided include assistance with responding to solicitations, interpretation of solicitation documents, technical assistance referrals, availability of resources, construction bond assistance through the Construction Statewide Bond Assistance Program, and free business directory listings and verifications through the Colorado Supplier Diversity Directory. The office can be reached during normal business hours by calling 303-866-5765 or emailing DPA_SupplierDiversityHelp@state.co.us.

2. BACKGROUND, OVERVIEW, AND GOALS

A. Background The State of Colorado (State) Department of Regulatory Agencies (DORA) is issuing this ITN on behalf of its Division of Professions and Occupations (DPO). At DORA, Consumer Protection is our Mission. The Division of Professions and Occupations provides consumer protection through its regulation of over 550,000 licenses, registrations, certifications and permits within more than 60 professions, occupations and entities in the State of Colorado.

DORA is seeking to identify and implement a long-term solution for a Professional Licensing and Regulation Platform (PLRP) that will provide enhanced features while maintaining quality delivery and furthers DORA’s strategic goal of offering as many licensing management services online as possible without compromising the quality of data or public access. The intent is to implement a PLRP that has the capability to expand features through technology, provides a scalable platform that supports increased transaction volumes and additional State entities. Exhibit 5 “Department Profile”, outlines the current Enterprise participation and volume levels in DORA’s existing system. Offerors may infer that DPO participation levels may increase by up to 20 percent over the next 3 years.

B. Definitions The following definitions speak to this document, as well as all Exhibits associated with Section 3, Statement of Work.

· API: Application Programming Interface. A set of functions and procedures allowing the creation of applications that access the features or data of an operating system, application, or other service.

V42225 Invitation to Negotiate Page 2 of 32

· Action Step: A process that can be added to a workflow on an as needed basis.

· Anytime Task: A task that can occur at any time that supports a license but is not part of the application, renewal, or reinstatement. These tasks are normally associated with changes to the underlying license information (such as addresses, ownership, required relationships, key management, DBA name).

· Application Path: A license may have multiple optional requirements defined for an application. Significant options comprise different "paths" toward a license. These paths may include a standard application and documentation, reciprocity, completion of practical experience, completion of an exam.

· Audit Trail: The collection of information that details any data changes within the solution. This audit trail is available to authorized users to view who, when, where, and why, a change in the database was made.

· Awarded Offeror: “Awarded Offeror” means the Offeror whose Proposal the State determines to be most advantageous considering the factors set forth in this ITN and is awarded the contract.

· Batch: The processing of multiple licenses or records at the same time.

· Board: A State governmental entity created by State law or regulation responsible for the administration of a set of licenses.

· Bond: Issued by a bank or a financial institution, a (performance) bond guarantees the fulfillment of a contract.

· Brand: A collection of products. Brand attributes apply to each of the products.

· Business Unit: This is an identifiable organization within the enterprise such as an agency, a department within an agency, or a board within a department. Business units are hierarchical and rules applying to a higher business unit apply to sub units of that business (i.e. rules that apply to an agency also apply to all departments within that agency and all boards within that department).

· Case Number: Unique identifier for a case or complaint. May be both alpha and numeric.

· Certificate: The formal document provided to the license holder that indicates the approval of a license.

· Compliance Agreement: A consent order, an Assurance of voluntary compliance, memorandum of agreement or other statement which stipulates that a license holder or contact must achieve certain tasks in order to remain in or achieve good standing.

· Cloud: a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

· Consolidation: The merging of complaints, investigations and/or inspections into single complaints, investigations or case resolutions

· Contract: The Contract to be entered into between the State and the Successful Offeror as a result of this ITN, its terms and conditions, attached exhibits, documents incorporated by reference under the terms of the Contract, and any future modifying agreements, exhibits, attachments or references that are incorporated pursuant to State Fiscal Rules and Policies.

· Contractor: The Offeror that is awarded a contract as a result of this ITN; same as “Awarded Offeror.” Also used interchangeably with “Offeror” to define an organization or individual submitting a proposal to this ITN.

· CORE: The Colorado Operations Resource Engine.

· CRS: Colorado Revised Statutes

· Correspondence Method: How correspondence is transmitted from the State to a contact. Typically this is a letter or an email. This may also be a certified letter or a text message.

· Credential: Is a license. This is a State issued license, permit, certification, or registration.

· Customer (Citizen) Relationship Management (CRM): In this ITN, CRM refers to practices, strategies and technologies used to manage system Contact data and interactions throughout the Credential lifecycle, with the goal of improving efficiencies.

· Custom Attribute: This is a data item that is created to collect information concerning a specific business function or group of functions. The data item is defined and formatted according to the Business Rules governing that function. The data stored in association with these attributes is available for all functionality (e.g. calculations, reporting, correspondence )

· Division or DPO: The Division of Professions and Occupations, a division within DORA.

· DORA: The Department of Regulatory Agencies.

· EPRP: Enterprise Licensing Management System

· Enforcement: The process of investigating and resolving complaints and allegations. May result in a compliance agreement.

· Enforcement Action: The result of an enforcement. It may include a surrender or a loss of license, fine or a compliance agreement.

· Enterprise: A group of State Departments utilizing a single software

· Enterprise Solution: A single software system platform designed to operate in an environment such as business or government. These solutions are complex, scalable, component-based, distributed, and mission critical.

· Entity Relationship View: The entity relationship provides linkage of all related contacts, cases, inspections, and license record views for a related entity (a contact, case, inspection, or license).

· FY: State’s fiscal year, which runs from July 1 through June 30.

· GAAP: Generally Accepted Accounting Principles (GAAP) is a framework of accounting standards, rules and procedures defined by the professional accounting industry.

· GASB: GASB (Governmental Accounting Standards Board) is a private not-for-profit organization that establishes improved standards of accounting and financial reporting for U.S. state and local governments

· GIS: A geographic information system (GIS) is a system designed to capture, store, manipulate, analyze, manage, and present all types of spatial or geographical data.

· Hybrid Mobile App: A smartphone or tablet application that is written in the standard Web programming format (HTML, JavaScript and CSS) but the Web elements (the "WebView") are wrapped within a native shell for iOS or Android. The shell allows the app to access inherent functions such as the camera, notifications, GPS receiver and sensors. As with a native app, the hybrid app must be installed and updated from the app store.

· Key Management: Contacts associated with an organization or facility performing specific roles. For example, a key management may be an owner or a manager. Key managers may be required or optional based upon business rules. Key management may be required to have a valid license.

· License: A permit from an authority to own or use something, do a particular thing, or carry on a trade. License = Credential, certification, and registration.

· License Basis: The rules for licenses vary according to the submission materials. For example, alternate licensing paths may exist for individuals who are applying for reinstatement of a lapsed license, have an existing out-of-state license or have passed a course of study/exam.

· License Holder: The individual, equipment or organization that has been approved for a license.

· License Management: The functions, operations, or activities associated with the regulatory requirements supporting State licenses.

· License Number: A unique identifier for a license. May be both alpha and numeric.

· License Profile: Data used to further describe an individual, piece of equipment or facility but does not impact the licensing process. Some data is used to satisfy statutory requirements to publish a profile. This data is collected through the application and renewal process.

· Logical Branching: A situation where requirements change according to the answers to a specific question. Example: If asked, do you have a license in another state is answered yes the applicant is required to enter information on that state license, otherwise the applicant must satisfy education and exam requirements.

· Multi-Tenant: Multi-tenancy is an architecture in which a single instance of a software application serves multiple tenant groups. A tenant is a group of users who share a common access with specific privileges to the software instance. With a multi-tenant architecture, a software application is designed to provide every tenant a dedicated share of the instance including its data, configurations, user management, tenant individual functionality and non-functional properties.

· Multi-Tiered: An approval process that requires approval by more than one individual in a defined sequence.

· Native Mobile App: A native mobile app is a smartphone application that is coded in a specific programming language, such as Objective C for iOS or Java for Android operating systems. Native mobile apps provide fast performance and a high degree of reliability. They also have access to a phone's various devices, such as its camera and address book. In addition, users can use some apps without an internet connection.

· Notification: A message sent to an individual based upon a system event, an action or a status change.

· Offeror: Any organization or individual submitting a Proposal in response to an ITN. Sometimes used interchangeably with the term ‘bidder or vendor.’

· OIT: Governor’s Office of Information Technology, State of Colorado.

· Online Form: A web page that collects a defined set of information and/or documents from an external user.

· Outside Agencies: Governmental agencies that are not participants in the system. Normally these are not State of Colorado Departments.

· Participant: An individual who is associated with a case but is neither a respondent nor the complainant. Often the individual may be a witness.

· Peer Monitor: A third party actor who is selected and agrees to monitor an individual's progress toward completion of a compliance agreement. This may require periodic inspections and/or reporting to the State Agency.

· PLRP: Professional Licensing and Regulation Platform

· PMP: Project Management Professional certification

· Product: A commodity which may be registered to the State. This may be a subset of a Brand.

· Program(s): A credential may have several programs. A program is a defined set of activities that may fall under additional regulation. A program may require its own license but that license must be supervised.

· Proposal: An offer in response to an ITN). Sometimes used interchangeably with the terms ‘bid,’’offer,’ or ‘response.’

· Provider: An organization that is authorized to offer classes, courses or exams.

· Reciprocal/Reciprocity: An optional application path where having a current license from another state allows an applicant to bypass some requirements, or approval of a license based upon an approved state's prior approval of a similar license.

· Regional Assignment: The assignment of tasks based on the location of a task, what region that location is placed in and the assignment of that regional responsibility to an authorized user.

· Respondent: A role in a case or a compliance agreement. In legal usage, this specifically refers to the defendant in a legal proceeding.

· Responsive Mobile App: A responsive website automatically changes to fit the device you're reading it on. Typically there have been four general screen sizes that responsive design has been aimed at: the widescreen desktop monitor, the smaller desktop (or laptop), the tablet and the mobile phone.

· Reviewer: An authorized user, normally a manager, who is authorized to complete an approval step required in a workflow.

· Self-Attestation: The process of an individual validating that something is true that that individual has submitted.

· Shopping Cart: Fees for licenses, as well as fines and other charges are initially placed in the shopping cart. The cart is an electronic holding area that accumulates items until the external area confirms and pays for the items.

· Single Sign-on: Single Sign-On (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them.

· Software Bug: An error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, improper presentation or to behave in unintended ways.

· Software Wizard: A software wizard or setup assistant is a user interface type that presents a user with a sequence of dialog boxes that lead the user through a series of well-defined steps. Tasks that are complex, infrequently performed, or unfamiliar may be easier to perform using a software wizard.

· Solicitation: A document issued by a state buyer that requests competitive offers from organizations or individuals to sell the goods or services. A solicitation typically results in an award of a contract or purchase order for the goods or services, based on an award methodology defined in the solicitation. Types of solicitations issued by State of Colorado agencies include: Requests for Proposals (RFPs), Documented Quotes, Invitation for Bids (IFBs),and Invitation to Negotiate (ITN).

· Supervisee: A license that requires an association with a "superior credential " (a real estate agent (the Supervisee) must have a real estate broker as the supervisor)

· Supervisor: A credential or contact that is responsible for other credentials. That responsibility is established through a business rule (an electrical apprentice must be supervised by a licensed electrician).

· Tag: An identifier used within a document or correspondence template that dynamically calls a predefined attribute from the database. Example: "<Contact Last Name>" would add the last name of the contact to the document.

· Template: A template is a file that serves as a starting point for a new document or correspondence. The template is designed for reuse and combines with tags and a business record to form a complete document. A template may be edited before publication.

· Thin Client: A thin client is a lightweight computer that has been optimized for establishing a remote connection with a server-based computing environment. A thin client is a stateless, fanless desktop terminal that has no hard drive. All features typically found on the desktop PC, including applications, sensitive data, memory, etc. are stored back in the data center when using a thin client.

· UPC Code: The Universal Product Code (UPC) is a barcode type used for tracking trade items in stores.

3. PROBLEM STATEMENT / SCOPE OF WORK

DORA is seeking a solution that is a vendor-hosted, user-centered design product that has a mobile component, consumer facing user interface, internal administrative user interface and configuration capabilities. The user- centered design should not be restricted to user interfaces, but must account for user characteristics, goals, and environments. The implementation will include a data conversion / migration phase from multiple legacy systems. Costs will be recovered through per-transaction fees retained by the vendor. No other funding is available for this project.

The Offeror shall propose dates for roll out, conversion and full system implementation and associated deliverables. A project plan is required within 30 days of an awarded contract. Costs for build-out and implementation will be recovered from per-transaction fees in concert with system implementation, and must occur evenly across the first several years of system functionality after which transaction fees will be adjusted downward to support ongoing maintenance costs rather than system build-out and development costs. Pricing proposals should incorporate this anticipated schedule of cost recovery. A transaction is an electronic payment (credit card or echeck) made through online services (i.e. initial license application, reinstatements, renewals).

The successful Offeror must work with DORA and the Governor’s Office of Information Technology (OIT) to convert the data from the existing system, train the administrators of the system, train the users of the system which includes approximately 200 staff, provide documentation, and provide support during the roll out followed up by supporting issue resolution. The successful Offeror shall comply with all applicable rules, policies, procedures and standards issued by the OIT, including change management, project lifecycle methodology and governance, technical standards, documentation, and other requirements posted at: https://oit.colorado.gov/standards-policies-guides/technical-standards-policies.

The PLRP shall ensure the secure storage and masking of PII (Personally Identifiable Information), CJIS data and all other data in compliance with OIT and CJIS standards.

The PLRP shall comply with all applicable provisions of §§24-85-101, et seq., C.R.S. and the Accessibility Standards for individuals with a disability, as established by OIT pursuant to section §24-85-103(2.5), C.R.S. and all State of Colorado technology standards related to technology accessibility and with level aa of the most current version of the web content accessibility guidelines (WCAG), incorporated in the State of Colorado technology standards.

VENDOR BACKGROUND, EXPERIENCE, AND QUALIFICATIONS

Offeror’s background and implementations are important to understand vendor stability and viability.

The Offeror must be an established provider of the proposed PLRP with demonstrated experience successfully implementing/operating a solution(s) of similar scope or similar functionality capabilities within the past five (5) years.

Offeror must have the capacity to provide qualified personnel and sufficient resources to successfully implement, operate, and maintain the proposed PLRP.

Offeror, must be prepared to present evidence of experience, ability, staffing, service facilities and financial standing necessary to meet the requirements set forth in its ITN response and/or as proposed in clarifications/negotiations.

Section 3 requirements:

The following items in Section 3 require a Yes or No response only. Any Offeror that cannot meet the requirements listed in 3, adds conditions to their Yes or No response, answers “No” to any item in Section 3 or does not provide any response to any item, shall be removed from further award consideration.

The provision of a PLRP solution shall enable DORA to achieve the following:

A. Design PLRP to solve current issues as well as continually respond, adapt, and innovate;

Proposer shall confirm the proposed system shall meet this requirement:

Yes No

B. Proposed PLRP solution shall be designed in partnership with communities of users inside and outside of state government to not only optimize the user experience, but utilize transformational design concepts;

Yes No

C. Proposed solution shall provide an enterprise multi-tenant solution that features contact based Customer (citizen) Relationship Management (CRM) functions;

Yes No

D. Proposed solution shall provide the ability for the public, both licensed or not, to utilize online services for self service and to conduct business and individual transactions;;

Yes No

E. Proposed solution shall provide regulatory enforcement features integrated across the PLRP that tracks complaints, inspections, and investigations from the intake process through conclusion and compliance monitoring;

Yes No

F. Proposed solution shall provide the ability to work with high volumes of transactional data that an enterprise environment presents;

Yes No

G. Proposed solution shall enable customized business unit views, enhanced search capability, management of relationships, and filtered user selections based on business rules;

Yes No

H. Proposed solution shall provide authorized user access to an intuitive configuration environment that allows creation or modification of multi-level user groups, emerging processes, and views required to administer the EPRP;

Yes No

I. Proposed solution shall provide standardization of reports, the ability for the client to develop reports/queries on the database, as well as ad hoc reporting capability;

Yes No

J. Proposed solution shall provide the ability to work with exam and Continuing Education providers to add, review, and approve exams/courses, and schedules through integration, interfaces or online self-service;

Yes No

K. Proposed solution shall provide a configurable inspection tool that can be used remotely (mobile), while supporting multiple business models across Divisions;

Yes No

L. Proposed solution shall establish a vendor contract and support agreement that is consistent with Colorado State Government standards;

Yes No

M. Proposed solution shall provide for future enterprise entities expansion with minimal impact to the existing users;

Yes No

N. Proposed solution shall include the provision of implementation and project management services;

Yes No

O. Proposed solution shall include the provision of maintenance and ongoing support post implementation.

Yes No

P. The proposed solutions shall at a minimum include:

a. Enterprise multi-tenancy architecture

b. Online license processing (initial applications, renewal applications, reinstatements applications, reactivation applications, status change applications, etc), license lookup/verification and license reporting

c. Online complaint reporting

d. Online permit processing, lookup and reporting for licensees and homeowners

e. Online Continuing Education/Continuing Competency services (both Provider & Participant)

f. Online supervision services to update and maintain supervision/relationship requirements (both supervisor & supervisee)

g. Online payment processing for any contact related fees

h. Integrated workflow management features

i. Configurable remote inspection solution

j. Scheduling, frequency reminder settings and notifications

k. Scalable high volume email correspondence features to communication via scheduled, initiated by action or ad hoc.

Yes No

Q. The proposed solution shall be a fee based model where the vendor’s sole source of compensation shall be from the fees collected during the term of the contract.

Section 3.1 Statement of Work and Proposal Requirements

The following sections are Scored Requirements. If additional documentation is required Proposers SHALL clearly identify the section number and restate the requirement before each response. Any information submitted that is not clearly marked to show the Statement of Work section being addressed will not be considered.

The items within this section outline specific information required in your response to determine how well the Offeror will be able to meet these requirements. Offeror must respond to ALL portions of the ITN and submit responses for each section as indicated.

3.1 REQUIREMENTS

3.1.1 Completed Client References Profile (Exhibit 1). Include three references

· Include two clients who have a statewide enterprise level (multi-tenant) implementation

· One client should have implemented in the last five years

3.1.2 Project Requirements Workbook (Exhibit 2)

· Provide an answer to all Response Required questions in the workbook based on your proposed architecture model and the Department Profile (Exhibit 5)

· Please provide a narrative that describes the proposed platform and include the following:

· Describe the process for receiving, validating, prioritizing, and estimating level of effort for requested enhancements to the proposed solution.

· Provide the technology roadmap for the Respondent’s proposed solution detailing planned improvements/enhancements/expansions to functionality and how they will be made available to the State.

· Describe the Offeror’s plan to ensure the proposed solution is responsive to and able to incorporate technological innovations in governmental regulation and administration of professional licensing.

· Provide a complete list of all individually licensed products that the proposed platform requires (e.g., product type, name, and function).

· Describe the nature of the proposed solution (e.g., Software as a Service [SaaS] - cloud specific, SaaS - cloud agnostic, cloud hybrid, or other).

· Detail the available licensing models for each proposed product in the solution (e.g., subscription, perpetual/maintenance, etc.).

· Describe a typical departure from the proposed platform. What aspects of the solution as configured are possessions of the State, and in what format would the data be returned to the State? By what medium are the digital assets transferred, and how long does that process take to complete (estimation based on extraction speed per unit of storage is acceptable)?

· Attach the following implementation documents:

· Project Implementation Plan: Provide a high level project plan presented in a project tool format with tasks, timeline, deliverables, & milestones. MS Project or similar is the preferred format.

· Project implementation team: Provide a description of the proposed project implementation team – including an explanation of each team member’s experience, relevant background, anticipated duties and if they will be available on site

· Project team resumes: Provide brief resumes for each key member of your implementation team

· Process documentation: Provide process documentation on business process flows built into the proposed EPRP. Microsoft Visio is the preferred format.

3.1.3 Product Requirements Workbook (Exhibit 3) .

· Provide an answer to all Response Required questions in the workbook based on your proposed architecture model and your responses to the Department Profile (Exhibit 5)

3.1.4 Product Pricing (Exhibit 4).

· Edit and add to this document based on your proposed pricing model and the Department Profile (Exhibit 5). Provide additional explanations within the “Comments” section where necessary. This document will be the basis for cost evaluation.

3.1.5 Department Profile (Exhibit 5)

· Attach a proposed technical architecture design document based on the Department Profile.

3.1.6 UI/UX Provisions (Exhibit 6)

· Describe if you accept the Transformational and User-Centered Design Concepts and UI/UX Provisions or provide guidelines that you feel provide superior design.

3.1.7 Contractor Client List (Exhibit 7).

· Complete the Contractor Client Listing worksheet. List all current State or Province clients utilizing the proposed solution.

3.1.8 Service Level Agreement (Exhibit 8)

· Describe if you accept the Service Level Agreement (SLA) or provide a SLA you feel provides superior support.

3.1.9 Financial Statements

· Contractor, together with any subcontractors, shall be required to demonstrate they have the financial resources to perform the requirements of this ITN. Attach the last two years of audited (as applicable to organization structure) financial statements for your company and provide information on the financial strength of your organization.

3.1.10 Termination

· Indicate whether or not you have been terminated from any agreement (e.g., contract, purchase order, etc.) prior to the expiration of that agreement. If yes, please provide a narrative describing the circumstances that led to that (or those) agreement(s) being terminated.

4. VENDOR RESPONSE

A. General Information for ITN Response

i. Vendors are encouraged to review the ITN and related attachments in its entirety to assure understanding of and compliance with requirements that may be included in these documents.

ii. To facilitate evaluation of responses, a response should be thorough yet brief. A response should address the requirements set forth in the ITN and should provide sufficient details to allow the committee(s) to determine whether the response evidences:

a. Understanding of the State’s needs, requirements and contracting terms and conditions; and

b. Ability to meet the State’s needs, including the experience and resources necessary to carry out the work towards meeting the State’s needs; and

c. Costs that are reasonable and consistent with the industry.

B. Response Submission Deadline See Schedule of Activities, above.

C. Timeliness of Response Submission

i. Responses received after the submission deadline shall not be opened and shall be rejected as a late response, unless otherwise permitted by the procurement official in accordance with Procurement Rule R-24-103-201-10.

ii. The responsibility for ensuring that a vendor's response is received on time rests with the vendor. Reasonably foreseeable problems inherent in the delivery of responses are not extraordinary circumstances permitting acceptance of late responses. Vendors mailing their responses shall allow sufficient mail delivery time to ensure receipt of their responses by the date and time specified.

D. Response Submission Instructions

a. Colorado Vendor Self Service This solicitation is being published on the Colorado Vendor Self Service page (Colorado VSS), so that Offerors who have an interest may submit a proposal in accordance with the terms of this solicitation.

b. All bids must be submitted electronically via Colorado Vendor Self Service (VSS).

c. Colorado VSS can only accommodate attachments up to 20mb in size. You can attach more than one document as long as they do not exceed 20 mb each.

d. More information on how to submit solicitations can be found via the Colorado VSS website. For Instructions please visit Submitting an Online Solicitation Response.

e. The VSS Help Desk is available Monday through Friday 8:00 a.m. to 5:00 p.m. MT and can be reached by calling (303) 866-6464 or emailing VSSHelp@state.co.us.

f. Offerors should submit all required documents as attachments in either MSWord and or PDF format, all responses shall include the following title: ITN# 2026000005, Professional Licensing and Regulation Platform and also include Offeror’s name.

g. Please do not encrypt your email. The e-submission program automatically encrypts attachments and any additional encryption may result in failure to upload the response.

ii. The solicitation submission application is only for response submission. All inquiries, questions, comments, or concerns should be submitted to the Procurement Contact via email and not through the online submission application.

E. Vendor Information / Parent Company The vendor response must include a valid tax identification number for the vendor. The vendor must be a legal entity with the legal right to contract in the State of Colorado. If a vendor is owned or controlled by a parent company, the response must also identify the name, main office address, and tax identification number of the parent company. The tax identification number provided with the vendor’s signature must be that of the vendor responding to this ITN.

F. Vendor Response Signature Page The vendor must submit a completed and signed signature page. By its signature, vendor agrees to be bound by its response and the provisions set forth in this ITN and certifies it is in compliance with requirements set forth in the ITN.

G. Vendor Requests for Confidentiality

i. The State of Colorado is subject to the requirements of §24-72-201, CRS, et seq., Public (Open) Records.

ii. A vendor may submit, as a part of its response, a written request for classification of certain portions of the response as a trade secret or other confidential or proprietary information. Material for which the vendor is requesting confidentiality shall be readily identifiable and separable from other portions of the ITN response to facilitate public inspection of the non-confidential portion of the response. Commingling of confidential and non-confidential information is not acceptable. Neither response price information nor any information that will be included in a resulting contract will be considered confidential.

iii. The vendor must include the rationale for any request to classify portions as a trade secret or confidential or proprietary, including references to the authority that allows for such treatment.

iv. In no event shall an entire response be classified as…