30-26050-DPH Lead and Asbestos Management System (LAMS)

STATE OF NORTH CAROLINA	REQUEST FOR PROPOSAL NO. 30-26050-DPH
DEPARTMENT OF HEALTH AND HUMAN SERVICES Division of Public Health	Contract Name: Lead and Asbestos Management System (LAMS)
	Bid Opening Date: February 16, 2026 @ 2pm ET
Refer ALL inquiries regarding this RFP to: Jace Bounds Jace.bounds@dhhs.nc.gov	Issue Date: January 15, 2026
	Commodity Code: 811118 System and System Component Administration Services
	Purchasing Agency: NC Department of Health and Human Services, Division of Public Health
	Requisition No.: RQ224506

OFFER

The Purchasing Agency solicits offers for Services and/or goods described in this solicitation. All offers and responses received shall be treated as Offers to contract as defined in 9 NCAC 06A.0102(12).

EXECUTION

In compliance with this Request for Proposal (RFP), and subject to all the conditions herein, the undersigned offers and agrees to furnish any or all Services or goods upon which prices are offered, at the price(s) offered herein, within the time specified herein.

Failure to execute/sign offer prior to submittal shall render offer invalid. Late offers are not acceptable.

OFFEROR:
STREET ADDRESS:	P.O. BOX:	ZIP:
CITY, STATE & ZIP:	TELEPHONE NUMBER:	TOLL FREE TEL. NO
NAME & TITLE OF PERSON SIGNING:	FAX NUMBER:
AUTHORIZED SIGNATURE:	DATE:	E-MAIL:

Offer valid for one hundred twenty (120) days from date of offer opening unless otherwise stated here: ____ days

ACCEPTANCE OF OFFER

If any or all parts of this offer are accepted, an authorized representative of North Carolina Department of Health and Human Services, Division of Public Health shall affix its signature hereto and any subsequent Request for Best and Final Offer, if issued. Acceptance shall create a contract having an order of precedence as follows: Best and Final Offers, if any, Special terms and conditions specific to this RFP, Specifications of the RFP, the Department of Information Technology Terms and Conditions, and the agreed portion of the awarded Vendor’s Offer. A copy of this acceptance will be forwarded to the awarded Vendor(s).

FOR PurchasiNG AGENCY USE ONLY Offer accepted and contract awarded this date , as indicated on attached certification, by (Authorized representative of Purchasing North Carolina Department of Health and Human Services, Division of Public Health).

Table of Contents

1.0 ANTICIPATED Procurement Schedule

The Agency Procurement Agent will make every effort to adhere to the following schedule. Funding for the project will expire on December 31, 2026.

Action	Responsibility	Date
RFP Issued	Agency	1/15/2026
Written Questions Deadline	Potential Vendors	1/27/2026 @ 2pm ET
Agency’s Response to Written Questions/ RFP Addendum Issued	Agency	2/04/2026
Offer Opening Deadline	Vendor(s)	2/16/2026 @ 2pm ET
Offer Evaluation	Agency	3/06/2026
Selection of Finalists	Agency	3/06/2026
Oral Presentations and/or Product Demonstrations by Finalists	Selected Vendors	3/20/2026
Negotiations with Finalists	Agency designees and selected Vendor(s)	4/03/2026
Best and Final Offers Deadline from Finalists	Selected Vendors	4/10/2026
Contract Award	Agency	4/24/2026
Protest Deadline	Responding Vendors	15 days after award

2.0 Purpose of RFP

2.1 Introduction

The purpose of this RFP is to solicit Offers from Vendors for software and professional services to implement and support a new Lead and Asbestos Management System (LAMS) for the State of North Carolina (State), Department of Health and Human Services (NCDHHS or DHHS), Division of Public Health (DPH or Division), Health Hazards Control Unit (HHCU).

The Vendor shall provide a centralized, web-based Commercial off-the-Shelf (COTS) Solution that is vendor-managed, compliant with the U.S. Environmental Protection Agency (EPA) Cross-Media Electronic Reporting Rule (CROMERR), and configurable to meet the requirements of the HHCU. The Solution shall be hosted within the State’s infrastructure. Select the link below for the details of EPA CROMERR.

https://www.epa.gov/cromerr

The proposed Solution must comply with CROMERR, EPA standards, and meet Program goals by:

o Supporting essential business functions for the LAMS, including application, reporting, curriculum, permit, payment, content, communication, and compliance management. It will also manage identity and access, integrate with the HHCU website, and generate reports online.

o Replacing the existing system of five SQL databases maintained by NCDHHS Information Technology Division (ITD) Applications.

o Ensuring modularity for easy updates, cost efficiency, adaptability to leading practices, rapid deployment of new technologies, and centralized maintenance to meet federal standards.

o Complying with State architecture and security standards to protect data at rest and in motion.

The Division estimates that there will be about 8,992 users of the Solution as described in Table 1 below. The estimate as described in Table 1 is a conservative estimate and the Solution should provide the ability to scale user capacity as needed for optimal performance.

Table 1: Health Hazards Control Unit User Estimate

Solution User	Description	Access Site	Estimated Number of Users
HHCU Staff	Review and process applications for certification and accreditation, review and issue permits and notifications, manage training, perform program monitoring and reporting	State-wide	25
Division IT Staff	Collaboratively maintains the solution with the Vendor	State-wide	6
Lead and Asbestos Professionals	Submit applications for certifications and accreditation along with required supporting documentation and payment; submit permit requests; receive communications regarding applications statuses and permit requests	State-wide	7,600
Training Providers	Submit initial/renewal course applications, supporting documentation, and course information; receive communications regarding application statuses and courses	State-wide	49
Local Education Agencies	Submit asbestos management plans and re-inspection reports, receive communications regarding submitted documentation	State-wide	1,312
General Public	Via the HHCU website, search for Lead and Asbestos Professionals and receive search results based on the data in the Solution and submit applications for a permit for asbestos removal, lead abatement, and demolition notifications in the Solution and receive notifications and receipts from the third-party payment platform for submitted fees.	State-wide	7,286 average monthly website visitors, 2,719 permit/demo applicants
Total Estimated Direct Access Users (Excludes General Public users):	11,711

The Minimum Viable Product (MVP), includes all requirements in Section 3.4 Business and Technical Requirements and specifications in Section 3.5 Business and Technical Specifications (excluding specifications in Section 3.5.14 Optional Business and Technical Specifications), must be fully deployed by no later than December 31, 2026.

2.2 Agency Background

HHCU Agency Background:

Pursuant to North Carolina General Statute (N.C. Gen. Stat). §130A-1.1, it is the mission of the public health system of North Carolina, administered by NCDHHS, to promote and contribute to the highest level of health possible for the people of North Carolina by promoting a safe and healthful environment. Pursuant to N.C. Gen. Stat. §130A-29, the Commission for Public Health (CPH, formerly the Commission for Health Services) is authorized to adopt rules necessary to implement the public health programs administered by NCDHHS. The Secretary of NCDHHS has the authority to enforce the state health laws and the rules of the Commission pursuant to N.C. Gen. Stat. §130A-5. The HHCU was established in the early 1990s and has nearly 30 years of electronic data managed across five relational databases with limited interactivity.

Asbestos Authority:

The HHCU administers the North Carolina Asbestos Hazard Management Program (AHMP) and the National Emission Standards for Hazardous Air Pollutants (NESHAP). The AHMP Rules address the requirements of the Asbestos Hazard Emergency Response Act (AHERA) of 1986, and the Asbestos School Hazard Abatement Reauthorization Act (ASHARA) of 1990, which expands many of the AHERA requirements to public and commercial buildings. Activities regulated under AHMP Rules include accreditation of personnel, review and approval of training courses, review of school management plans, and permitting and inspection of asbestos removal projects.

On January 1, 1991, the AHMP also assumed responsibility for enforcement activities resulting from NESHAP violations. The NESHAP regulations require notification, specific work practices, proper disposal of materials removed at asbestos abatement projects and no visible emissions to the outside air.

In 1994, legislation was enacted which revised the General Statutes to include the requirements of EPA's revised Model Accreditation Plan (MAP) promulgated in March 1994 in response to the requirements of the ASHARA. In addition, the new legislation added authority to assess administrative penalties for violations of the AHMP Rules and transferred authority for the demolition/renovation portions of the NESHAP from the Environmental Management Commission to the CPH. Rules adopted by the CPH to implement the new legislation became final on January 1, 1995.

Lead-Based Paint Authority:

Title X, the Residential Lead-Based Paint Hazard Reduction Act of 1992, delegated the EPA the responsibility of issuing regulations governing individuals engaged in lead–based paint activities and renovations, to ensure they are properly trained, that Training Providers are accredited, individuals and firms are certified, lead-safe work practices are conducted, and that required records are maintained. EPA, through Section 402, 403 and 406 of the Toxic Substances Control Act (TSCA) has promulgated regulations which govern Lead-Based Paint Rules and has encouraged states to develop and seek authorization for implementing, administering and enforcing their own lead-based paint programs.

North Carolina became authorized to administer a lead-based paint program on August 24, 1998, by implementing the Lead Hazard Management Program (LHMP), a program that is as protective as EPA’s and has adequate enforcement. The North Carolina renovation program was authorized on January 21, 2010, and the Lead-Based Paint Hazard Management Program for Renovation, Repair and Painting (LHMP-RRP) was implemented on January 1, 2010.

2.3 SUMMARY OF PROBLEM Statement

DPH works to protect the public's health across North Carolina and helps shape positive health outcomes for North Carolinians and the communities in which they live, learn, work, worship, and play. One component of that responsibility is promoting a safe and healthy environment for residents to participate in their daily routines and activities. This is achieved through business partnerships, the delivery of consistent education, utilization of best practices in the management of asbestos and lead-based paint hazards, issuance of permits and certifications, and compliance monitoring.

Currently, the program data to manage these services is housed in five (5) separate SQL databases with nearly thirty (30) years of electronic data that contains limited interactive capabilities and is maintained by limited internal human resources and using a Gupta software platform that is outdated. Refer to Attachment K: HHCU Solution Context Diagrams (As-Is and Envisioned) to view the databases. These databases house application and asbestos accreditation lead certification data, asbestos and lead-based paint permits and notifications, lead-based paint certification data, training records, and asbestos management plans for schools as required by AHERA and ASHARA. The current set of databases does not provide the essential functionality to manage the 30 years’ worth of program data. For example, the current system does not provide online application submissions, processing, and notifications of asbestos and lead removal permits, asbestos accreditation, certification for lead-based paint and renovation activities, and training management. The system does not permit payment submission and processing, requiring manual payment, collection, and refund processes with limited acceptable forms of payments. Additionally, the limited availability of skilled resources makes it difficult to maintain the growing program needs and requirements. Further, the system is not CROMERR compliant, which is required by the EPA.

To meet the demands of the HHCU, the NCDHHS seeks a LAMS that is CROMERR compatible and able to:

1. maintain continued compliance with CROMERR and EPA regulations,

2. replace the existing outdated legacy system of five (5) SQL databases depicted in Attachment K: HHCU Solution Context Diagrams (As-Is and Envisioned) to support the business functions and processes within scope for the Solution, as depicted in Figure 1: Health Hazards Control Unit Functional Decomposition Diagram and described as follows:

• Application Management: allow statewide individuals and organizations to apply for certifications and accreditations and generate photo identification cards.

• Reporting: generate reports online and support report distribution

• Curriculum Management: permit administration and management of the catalog of relevant offered courses

• Permit Management: issue and manage permits and demolition notifications

• Payment Processing: permit the submission, collection, and refunding of payments for in-scope processes

• Electronic Content Management: serve as a document repository

• Communication Management: manage communications including mass electronic distribution of program information via email when necessary and the potential for electronic submission of inspection reports which are currently collected on paper

• Compliance Management: manage state-wide compliance with federal and state regulations and enforcement processes

• Identity and Access Management and System Administration: support the management of authenticated and authorized use of the Solution

• Enterprise Content Management: integrate with the HHCU website

3. support efficiency and cost effectiveness as the system adapts to leading practices and standards

4. promote rapid deployment and innovation to leverage and rapidly implement new technologies

5. use resources efficiently to ensure proper development and maintenance in a centralized manner that promotes standardization with federal requirements.

6. comply with State privacy and security requirements, and technical standards to protect collected and stored data at rest and in motion

Figure 1: Health Hazards Control Unit Functional Decomposition Diagram

2.4 Contract Term

A contract awarded pursuant to this RFP shall have an effective date as provided in the Notice of Award. The term shall be three (3) years and will expire upon the anniversary date of the effective date unless otherwise stated in the Notice of Award, or unless terminated earlier. The State retains the option to extend the Agreement for seven (7) additional one (1) year periods at its sole discretion.

2.5 Effective Date

This solicitation, including any Exhibits, or any resulting contract or amendment shall not become effective nor bind the State until the appropriate State purchasing authority/official or Agency official has signed the document(s), contract or amendment; the effective award date has been completed on the document(s), by the State purchasing official, and that date has arrived or passed. The State shall not be responsible for reimbursing the Vendor for goods provided nor Services rendered prior to the appropriate signatures and the arrival of the effective date of the Agreement. No contract shall be binding on the State until an encumbrance of funds has been made for payment of the sums due under the Agreement.

2.6 Contract Type

Definite Quantity Contract - This request is for a close-ended contract between the awarded Vendor and the State to furnish a pre-determined quantity of a good or service during a specified period of time.

The State reserves the right to make partial, progressive or multiple awards where it is advantageous to award separately by items; where more than one supplier is needed to provide the contemplated specifications as to quantity, quality, delivery, service, geographical areas; or where other factors are deemed to be necessary or proper to the purchase in question.

2.7 Contract Phases

The Contract will have the following two (2) Contract Phases:

a) Project Execution Contract Phase: The portion of the contract duration during which the Vendor develops and implements the Solution. Reference Section 3.6 Management Specifications and Attachment J: Quality Specifications for Project Management and O&M Deliverables for details regarding the approach, deliverables, tasks, and activities necessary for the Solution to be released for production. The Vendor is to deliver and stabilize a Solution that contains all Business and Technical Requirements and Specifications before initiating the Operations and Maintenance Contract Phase.

b) Operations and Maintenance (O&M) Contract Phase: The Vendor will perform all tasks and/or activities related to operating and maintaining the Solution after the Stabilization Period (i.e., warranty) has been completed. The Vendor will maintain the Solution, provide support and updates and/or new releases, and modify the Solution as requested by the Agency. Reference Section 3.6.10 Vendor Approach to Operations and Maintenance and Attachment J for details regarding the approach, deliverables, tasks, and activities necessary to support the Solution during O&M.

3.0 RFP Requirements and Specifications

3.1 General requirements and Specifications

REQUIREMENTS

Requirement means, as used herein, a function, feature, or performance that the System must provide. If the offer cannot meet the requirements, they will not be evaluated.

SPECIFICATIONS

Specification means, as used herein, a detailed description that documents the function and performance of a system or system component.

The apparent silence of the specifications as to any detail, or the apparent omission of detailed description concerning any point, shall be regarded as meaning that only the best commercial practice is to prevail and that only processes, configurations, materials and workmanship of the first quality may be used. Upon any notice of noncompliance provided by the State, Vendor shall supply proof of compliance with the specifications. Vendor must provide written notice of its intent to deliver alternate or substitute Services, products, goods or other Deliverables. Alternate or substitute Services, products, goods or Deliverables may be accepted or rejected in the sole discretion of the State; and any such alternates or substitutes must be accompanied by Vendor’s certification and evidence satisfactory to the State that the function, characteristics, performance and endurance will be equal or superior to the original Deliverables specified.

SITE AND SYSTEM PREPARATION

Vendors shall provide the Purchasing State Agency complete site requirement specifications for the Deliverables, if any. These specifications shall ensure that the Deliverables to be installed or implemented shall operate properly and efficiently within the site and system environment. Any alterations or modifications in site preparation, which are directly attributable to incomplete or erroneous specifications provided by the Vendor and which would involve additional expenses to the State, shall be made at the expense of the Vendor.

3.1.1 EQUIVALENT ITEMS

Whenever a material, article or piece of equipment is identified in the specification(s) by reference to a manufacturer’s or Vendor’s name, trade name, catalog number or similar identifier, it is intended to establish a standard for determining substantial conformity during evaluation, unless otherwise specifically stated as a brand specific requirement (no substitute items will be allowed). Any material, article or piece of equipment of other manufacturers or Vendors shall perform to the standard of the item named. Equivalent offers must be accompanied by sufficient descriptive literature and/or specifications to provide for detailed comparison.

3.1.2 ENTERPRISE LICENSING

In offering the best value to the State, Vendors are encouraged to leverage the State’s existing resources and license agreements, which can be viewed here:

https://it.nc.gov/resources/statewide-it-procurement/statewide-it-contracts

a) Identify components or products that are needed for your solution that may not be available with the State’s existing license agreement.

b) Identify and explain any components that are missing from the State’s existing license agreement.

c) If the Vendor can provide a more cost-effective licensing agreement, please explain in detail the agreement and how it would benefit the State.

3.2 Security Specifications

3.2.1 Solutions Hosted on State Infrastructure

Vendors should provide a completed Vendor Readiness Assessment Report State Hosted Solutions (“VRAR”) at offer submission. If it is not supplied with offer submission, the State may ask you for this documentation and/or others mentioned prior to an award. If any security documentation is not returned to the State within seven (7) business days, the Vendor’s offer will be rejected.

This report is located at the following website:

https://it.nc.gov/documents/vendor-readiness-assessment-report

The LAMS will be required to receive and securely manage data that is classified as High Risk. Refer to the North Carolina Statewide Data Classification and Handling policy for more information regarding this data classification. The policy is located at the following website: https://it.nc.gov/document/statewide-data-classification-and-handling-policy

To comply with the State’s Security Standards and Policies, State agencies are required to perform annual security/risk assessments on their information systems using NIST 800-53 controls.

3.3 Enterprise Specifications

3.3.1 Architecture Diagrams

For Vendor Completion:

The State utilizes architectural diagrams to better understand the design and technologies of a proposed solution. Details on these diagrams can be found at the following link: https://it.nc.gov/resources/statewide-it-procurement/vendor-engagement-resources#Tab-Architecture-1192

The provision of these diagrams is a requirement at offer submission. If they are not supplied at that time, the Vendor’s offer will be considered non-responsive and will not be evaluated.

There may be additional architectural diagrams requested of the Vendor after contract award. This will be communicated to the Vendor by the Agency as needed during the project.

3.3.2 Solution Roadmap

A Solution Roadmap defines the vision and strategic elements of the solution.  The Solution Roadmap is a plan of action for how a Solution will evolve over time. The minimum content should include:

• Vision for the solution

• High-level functionality expected for each solution release into production environment

• High-level timeline

• Description of how customer feedback is collected and incorporated into solution enhancements

For Vendor Completion:

Describe the solution roadmap for your product.  Include content on release strategies for functionality, roadmap for technical architecture, how scalability of solution is planned.

3.3.3 Identity and Access Management

The proposed Solution must externalize identity and access management. The protocols describing the State’s Identity and Access Management can be found at the following link: https://it.nc.gov/services/vendor-engagement-resources#Tab-IdentityAccessManagement-1241

For Vendor Completion:

Describe how your solution supports the above protocols, as well as making them available for application integration/consumption.

3.3.4 Integration Approach

For Vendor Completion:

Describe proposed solution capabilities to interoperate with other solutions. Identify the standards supported, integrations platforms, adaptors, APIs, and the like.

Refer to Figure 2: Health Hazards Control Unit Lead & Asbestos Context Diagram – As-Is State for the current system context to be replaced. Also see Attachment K: HHCU Solution Context Diagrams (As-Is And Envisioned) for the associated details described in the relationship table.

Refer to Figure 3: Health Hazards Control Unit Lead & Asbestos Context Diagram – Envisioned State for a proposed system context with interoperability to achieve project goals supporting in-scope business functions and processes. Also see Attachment K: HHCU Solution Context Diagrams (As-Is And Envisioned) for the associated details described in the relationship table.

Figure 2: Health Hazards Control Unit Lead & Asbestos Context Diagram – As-Is State

Figure 3: Health Hazards Control Unit Lead & Asbestos Context Diagram – Envisioned State

3.3.5 Disaster Recovery and Business Continuity

For Vendor Completion:

Describe the proposed Solution capabilities related to the following areas:

a) Disaster Recovery Plan (DRP) – describe how the proposed Solution supports Recovery Point Objectives (RPO) of 0 seconds and Recovery Time Objectives (RTO) metrics of 12 hours.

b) System Backup – describe backup plan capabilities.

c) Disaster Recovery Testing – describe the frequency and test procedures for end-to-end disaster recovery testing. Business Continuity Plan (BCP) – describe capabilities proposed solution can provide in support of Agency’s continuity of operations and incident responses.

d) Business Continuity Plan (BCP) – Describe capabilities proposed solution can provide in support of Agency’s continuity of operations and incident responses.

3.3.6 Data Migration

For Vendor Completion:

Describe approaches available for data conversion and/or data migration to load current data into the proposed Solution. Refer to Table 2: Magnitude of Legacy Data Sources for Migration for the existing source systems (tables and spreadsheet file), number of tables, database languages, and table/file sizes.

Include in your response:

a) Describe the approach to ensure migrated data is transformed into the appropriate formats for in-scope reporting.

b) Describe how the proposed Solution retains unique identifiers migrated from the Legacy system. Examples of unique identifiers include, but are not limited to NESHAP number, state permit identifier, etc.

c) Describe the approach to data cleansing, normalization of Legacy Data, and data mapping prior to migration into the proposed Solution. List all tools that will be used, and State resources required to perform the data migration, conversion, cleansing, mapping, and normalization.

d) Describe how the proposed Solution centralizes access to data for geographically dispersed users.

e) Describe how the proposed Solution allows HHCU Staff to have user defined data validation.

f) Describe how the proposed Solution allows HHCU Staff to have user-configured field values for templates.

Table 2: Magnitude of Legacy Data Sources for Migration

Existing Source System*	# Tables	Total File Size (MB)
Gupta Lead & Asbestos Access Database – Accreditations and Certifications*	44	37,105
Gupta Lead Access Database – Lead RRP Certifications*	37	221
Gupta Lead & Asbestos Access Database – Permits*	63	326
Gupta Lead & Asbestos Access Database – AHERA Asbestos in Schools*	40	12
Gupta Lead & Asbestos Access Database – Training*	37	14
Lead & Asbestos Payment Tracking (MS Excel File)	Due to manual data entry and physical storage dating back 30+ years, this data set will NOT be migrated.
*Language: SQL Windows Development Environment: Gupta Team Developer Server: SQLBase

3.3.7 Application Management

For Vendor Completion:

a) Describe how the proposed Solution monitors and reports the metrics on system performance.

b) Describe how the proposed Solution manages user administration.

c) Describe the audit capabilities of proposed Solution related to management of the application.

3.3.8 Accessibility

For Vendor Completion:

Describe how the proposed Solution complies with industry accessibility standards.

Provide product documentation that demonstrates how the proposed Solution is digitally accessible or if not fully accessible, provide the roadmap with timeline for remediation.

Standards include:

a) W3C Web Accessibility Initiative - Web Content Accessibility Guidelines (WCAG) 2.1: https://www.w3.org/TR/WCAG21/

b) Section 508: https://www.section508.gov/

c) Voluntary Product Accessibility Template (VPAT®): https://www.itic.org/policy/accessibility/vpat

3.3.9 Enterprise, Services, and Standards

Vendors should refer to the Vendor Resources Page for information on North Carolina Department of Information Technology regarding architecture, security, strategy, data, digital, identity and access management and other general information on doing business with state IT process.

The Vendor Resources Page found at the following link: https://it.nc.gov/vendor-engagement-resources . This site provides Vendors with statewide information and links referenced throughout the RFP document. Agencies may request additional information.

3.4 Business and Technical Requirements

The Division seeks a Vendor-managed, centralized web-based Commercial-off-the-Shelf (COTS) solution, compliant with the U.S. Environmental Protection Agency (EPA) Cross-Media Electronic Reporting Rule (CROMERR), and configurable to meet the requirements of the HHCU. The Solution shall be hosted within the State’s infrastructure.

The Solution must meet the following requirement for the Minimum Viable Product (MVP) to be evaluated. Vendors must respond to this requirement and indicate whether the proposed Solution meets the requirement and describe how the requirement is met.

3.4.1 REPORTING

3.4.1.1 the Solution must comply with the Cross-Media Electronic Reporting Rule (CROMERR) according to the EPA standards.

3.5 Business and Technical Specifications

3.5.1 General Specifications

For Vendor Completion:

3.5.1.1 Describe how the proposed Solution provides web-based, online capabilities to submit and process applications.

3.5.1.2 Describe how the proposed Solution allows applications and forms to be submitted only after all required fields are complete and required documentation is uploaded according to business rules (i.e., the Solution does not permit the submission of partially completed applications and forms). Refer to Attachment L: HHCU Forms with Instructions Containing Business Rules and Required Documentation.

3.5.1.3 Describe how the proposed Solution minimizes the addition of duplicate records (e.g., prevents a user from adding an individual or firm that exists in the database, etc.).

3.5.1.4 Describe how the proposed Solution permits records to be merged, by whom, and how the Solution associates all IDs with the merged record. Include whether IDs of merged into the main record remain with the merged record or whether they are re-used.

3.5.2 Application Management

3.5.2.1 Certify Firms – Accredit Individuals (Lead, Asbestos, and RRP)

For Vendor Completion:

3.5.2.1.1 Describe how the proposed Solution allows Lead and Asbestos Professionals to submit applications according to business rules and upload supporting documentation. Refer to Attachment L: HHCU Forms with Instructions Containing Business Rules and Required Documentation.

3.5.2.1.1.1 Describe how the proposed Solution allows individuals and firms to apply for lead-based paint certification according to business rules.

3.5.2.1.1.2 Describe how the proposed Solution allows individuals to apply for asbestos accreditation according to business rules.

3.5.2.1.1.3 Describe how the proposed Solution allows individuals and firms to upload supporting documentation according to business rules.

3.5.2.1.1.4 Describe how the proposed Solution allows individuals and firms to provide information requested by HHCU and re-submit an application.

Refer to Attachment M: HHCU Workflows (As-Is) and Attachment N: HHCU Workflows (Envisioned) for the current and envisioned business processes to certify and accredit Lead and Asbestos Professionals.

3.5.2.1.2 Describe how the proposed Solution allows HHCU Staff to process submitted applications and supporting documentation to certify and accredit Lead and Asbestos Professionals.

3.5.2.1.2.1 Describe how the proposed Solution allows HHCU Staff to access and review submitted applications and supporting documentation for individuals and firms.

3.5.2.1.2.2 Describe how the proposed Solution allows HHCU Staff to approve, pend for additional information, and reject applications for individuals and firms. Indicate whether and how the Solution displays the application status.

3.5.2.2 Accredit Training Providers

For Vendor Completion:

3.5.2.2.1 Describe how the proposed Solution allows Training Providers to submit applications according to business rules and upload supporting documentation. Refer to Attachment L: HHCU Forms with Instructions Containing Business Rules and Required Documentation.

3.5.2.2.1.1 Describe how the proposed Solution allows Training Providers to apply for accreditation according to business rules.

3.5.2.2.1.2 Describe how the proposed Solution allows Training Providers to upload supporting documentation according to business rules.

3.5.2.2.1.3 Describe how the proposed Solution allows Training Providers to provide information requested by HHCU and re-submit an application.

Refer to Attachment M: HHCU Workflows (As-Is) And Attachment N: HHCU Workflows (Envisioned) for the current and envisioned business processes to accredit Training Providers.

3.5.2.2.2 Describe how the proposed Solution allows HHCU Staff to process submitted applications and supporting documentation to accredit Training Providers.

3.5.2.2.2.1 Describe how HHCU Staff can access and review submitted applications and supporting documentation submitted by Training Providers.

3.5.2.2.2.2 Describe how the proposed Solution allows HHCU Staff to approve, pend for additional information, and reject applications for Training Providers. Indicate whether and how the Solution displays the application status.

3.5.2.3 Approve Training Instructors

For Vendor Completion:

3.5.2.3.1 Describe how the proposed Solution allows Training Instructors to submit applications according to business rules and upload supporting documentation. Refer to Attachment L: HHCU Forms with Instructions Containing Business Rules and Required Documentation.

3.5.2.3.1.1 Describe how the proposed Solution allows Training Instructors to apply for approval to teach courses.

3.5.2.3.1.2 Describe how the proposed Solution allows Training Instructors to upload supporting documentation.

3.5.2.3.1.3 Describe how the proposed Solution allows Training Instructors to provide information requested by HHCU and re-submit an application.

Refer to Attachment M: HHCU Workflows (As-Is) and Attachment N: HHCU Workflows (Envisioned) for the current and envisioned business processes to approve Training Instructors.

3.5.2.3.2 Describe how the proposed Solution allows HHCU Staff to process submitted applications and supporting documentation to approve Training Instructors.

3.5.2.3.2.1 Describe how the proposed Solution allows HHCU Staff to access and review submitted applications and supporting documentation submitted by Training Instructors.

3.5.2.3.2.2 Describe how the proposed Solution allows HHCU Staff to approve, pend for additional information, and reject applications for Training Instructors. Indicate whether and how the Solution displays the application status.

3.5.3 Reporting

3.5.3.1 Generate Federal Reports/Queries

For Vendor Completion:

3.5.3.1.1 Describe how the proposed Solution permits the generation of federal reports and queries.

Refer to Attachment O: HHCU Reports List for a list of minimum federal reports.

...