260225 Revised Attachment A - Traceability Matrix.xlsx
XLSX spreadsheet 176 KB Posted
- Attached to
- Environmental Information Management System EIMS
- Solicitation number
- 26-532EPA-FISCP-B-51295
- Issued by
- Illinois
About this file
This is a Traceability Matrix template for the State of Illinois Environmental Protection Agency (IEPA) Environmental Information Management System (EIMS) Procurement, serving as Attachment A to a Request for Proposal (RFP). The document establishes comprehensive requirements for a cloud-hosted environmental information management solution that will support IEPA's business operations across six major functional areas: General Operations, Compliance Monitoring & Enforcement, Financial Management, Program Management, Public Online Services & Public Engagement, and Technical Submission Processing. The solicitation (26-532EPA-FISCP-B-51295) requires vendors to address 146 business functionalities, 196 technical functionalities, and 142 service delivery requirements organized into twelve service domains. The solution must comply with CROMERR (Compliance Reporting on the Management of Environmental Records and Regulatory) standards and State of Illinois security requirements, with particular emphasis on electronic submission capabilities, audit trail maintenance, multi-factor authentication, and disaster recovery protocols with a Recovery Time Objective (RTO) of one hour and Recovery Point Objective (RPO) of fifteen minutes.
The evaluation methodology allocates 5,000 technical response points distributed across Experience & Staffing (15 percent), Business Functionality (24 percent), Technical Functionality (24 percent), Services (24 percent), State Standard Security Requirements (3 percent), and Demonstrations (10 percent), with Commitment to Diversity weighted at 20 percent and Price at 30 percent of total procurement points, resulting in 7,200 total evaluation points. Vendor performance is measured through 15 service level requirements addressing CROMERR compliance, system availability, submission processing time, data integrity, incident resolution, and application performance, with state credits ranging from 2 to 5 percent of monthly or quarterly fees for non-compliance. The contract structure includes multiple deliverable phases spanning project management, requirements validation, solution design and configuration, data migration, comprehensive testing, user training, cloud hosting and provisioning, cutover/deployment with one month of hypercare support, and ongoing maintenance and operations throughout the contract term, with requirements for knowledge transfer and exit transition planning to ensure continuity should the vendor relationship conclude.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| state-of-illinois-standard-it-terms-and-conditions-v26-1.pdf | ||
| c2d-vendor-answer-sheet-v.24.4 ~3.docx | DOCX document | |
| Bureau of Air Operating and Construction Permit Fee Tables - Attachment C.docx | DOCX document | |
| EIMS Pre-Submission Conference Sign-In Sheet 1 of 2.pdf | ||
| BEP U-Plan.pdf | ||
| ipg-active-registered-vendor-disclosure-formerly-forms-b-v.23.1~8.docx | DOCX document | |
| information-and-technology-request-for-proposal-offer-to-the-state-of-illinois.pdf | ||
| 260225 Attachment B - IL Cost Workbook .xlsx | XLSX spreadsheet | |
| 260227 EIMS Rebid RFP.docx | DOCX document | |
| 2600415 IEPA EIMS Rebid Q and A.docx | DOCX document | |
| c2d-vendor-guidance.pdf | ||
| vendor-disclosure-formerly-forms-a-v26-1-6-25-2025~1.docx | DOCX document | |
| 260410 EIMS Rebid RFP~1.docx | DOCX document | |
| EIMS Pre-Submission Conference Sign-In Sheet 2 of 2.pdf |
Show all 14
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Utilization Step-by-Step
| Information & Instructions |
| The goal of this worksheet is to guide the Gartner resource through complete population and utilization of this Traceability Matrix Template. Following the steps below, checking them off as you completed using the check box in column B. Follow any additional steps provided within each subsequent worksheet. If you find errors or have ideas on how this template can be enhanced/improved, please reach out to Stacy Feldmann. |
| Review and revise, as needed, Business Functionality Level 0 Capabilities and Level 1 Capabilities. |
| Review and revise, as needed, Business Functionality Priorities. (If you are not prioritizing, this step can be skipped) |
| Review and revise, as needed, Business Functionality Solution Methods. |
| Review and revise, as needed, Technical Functionality Level 0 Capabilities and Level 1 Capabilities. |
| Review and revise, as needed, Technical Functionality Priorities. (If you are not prioritizing, this step can be skipped) |
| Review and revise, as needed, Technical Functionality Solution Methods. |
| Review and revise, as needed, Service Domains and Subdomains. |
| Populate the requested information into rows 1-4. This information will auto-populate at the top of each worksheet within this workbook. |
| Review & revise all instructions in row 9 to align with your RFP. Double check all attachment/worksheet,/section/column/row//cell references. |
| Review & revise all worksheet names and descriptions as needed to align with your RFP. Update hyperlinks as needed. |
| Review and revise the information & instructions as needed to align with your RFP. Note: If your RFP has not identified a desired Solution Method (i.e., COTS) you will likely be unable to score TM responses based on Solution Method. |
| Populate ID#s. Use provided drop-down menus to align Level 0 and Level 1 Capabilities (these are driven by the Data Validation worksheet). Define Functionality Descriptions; add hyperlinks as applicable. |
| Identify Priorities, if appliable. (If your RFP is not establishing priorities, hide this column) |
| Note: If more Level 0 or Level 1 Capabilities are populated in the Data Validation worksheet, the drop-down menu data validation will have to be updated. |
| Review and revise the information & instructions as needed to align with your RFP. |
| Populate ID#. Use provided drop-down menus to align Level 0 and Level 1 Capabilities (these are driven by the data validation worksheet). Define Functionality Descriptions; add hyperlinks as applicable. Identify Priorities, if appliable. |
| Identify Priorities, if appliable. (If your RFP is not establishing priorities, hide this column) |
| Note: If more Level 0 or Level 1 Capabilities are populated in the Data Validation worksheet, the drop-down menu data validation will have to be updated. |
| Review and revise the information & instructions as needed to align with your RFP. |
| Populate ID#. Use provided drop-down menus to align Service Domains and Subdomains (these are driven by the data validation worksheet). Define Descriptions of each Service. An example has been left for how to address Deliverables. |
| Note: The State does not like to include any services for which they are responsible. Services documented should be only those requested of the Vendor. |
| Note: If all services are considered mandatory, ensure to draft a Mandatory with Evidence in the RFP to support this. If not, a column will need to be added for Offeror's to respond Yes/No. |
| Note: If more Service Domains or Subdomains are populated in the Data Validation worksheet, the drop-down menu data validation will have to be updated. |
| Review and revise the information & instructions as needed to align with your RFP. |
| Establish applicable SLRs and populate all details within the corresponding column. |
| Note: State Credit is a % of the cost deducted from the State's invoice if the Vendor is non-compliant. IL does not have a method to allow Vendor Earn Backs, so those should not be established. |
Review all the details, descriptions, definitions, etc. within this worksheet and revise as needed to align with your RFP and the client. This information supports the enforcement of the SLRs established in worksheet 4. Vendor Performance.
| Table 2: RFP Category Weight / Point Distribution |
| Populate the light orange cell (D60) with the total number of points you plan to use for the technical response. This total can be changed later if needed, but gives a good starting point for establishing the evaluation methodology. |
| Populate light orange cells (B60 - B69) with what weight % of the total technical response points should be distributed across these high-level evaluation categories. Column C will auto-calculate the points. |
| B72, C2D, must remain 20%. |
| B74, Price, should be at least 20% (B74) unless otherwise agreed to by both the client and their agency procurement officer. Revise the light orange cell as needed. |
| Populate the light orange cells (B62 & B63) with how the Business Functionality points should be distributed across the narrative and TM response. This should add up to 100%. |
| Populate the light orange cells (B65 & B66) with how the Technical Functionality points should be distributed across the narrative and TM response. This should add up to 100%. |
| Table 3. Maximum Available Points (MAP): Business Functionality Response |
| MAP will auto-populate once step 8.1 is complete. |
| Note: Level 0 Capabilities will auto-populate from the Data Validation worksheet. If more than 10 capabilities are used, you will need to add rows and pull down the cell link. |
| Populate the light orange cells in column C with how Business Functionality points should be distributed across Level 0 Capabilities. |
| In column B, ensure there is a higher weight % in for more important capabilities and a lower weight & for less important capabilities. The total must equal 100%. |
| Note: Conditional formatting is in place to ensure there is no inconsistency between the High-Level Eval Category table and this table. |
| Column C will auto-calculate the available points for each Level 0 Capability. Total available points will be equal to C63. If it is not, the total cell will flag red. Please double check the formulas. |
| Column D will auto-calculate the total Business Functionalities set as Essential Priority with that Level 0 Capability. TM content should have been added in during Step 5. |
| Column E will auto-calculate the total Business Functionalities set as Optional Priority with that Level 0 Capability. TM content should have been added in during Step 5. |
| Column F will auto-calculate the total Business Functionalities with that Level 0 Capability. TM content should have been added in during Step 5. |
| Columns G & H will auto-calculate the total points per Essential/Optional Business Functionality of that Level 0 Capability. This will auto-populate column F in worksheet 1. Business Functionality. |
| Table 4. Maximum Available Points (MAP): Technical Functionality TM Response |
| MAP will auto-populate once step 8.1 is complete. |
| Note: Level 0 Capabilities will auto-populate from the Data Validation worksheet. If more than 10 capabilities are used, you will need to add rows and pull down the cell link. |
| Populate the light orange cells in column C with how Technical Functionality points should be distributed across Level 0 Capabilities. |
| In column B, ensure there is a higher weight % in for more important capabilities and a lower weight & for less important capabilities. The total must equal 100%. |
| Note: Conditional formatting is in place to ensure there is no inconsistency between the High-Level Eval Category table and this table. |
| Column C will auto-calculate the available points for each Level 0 Capability. Total available points will be equal to C66. If it is not, the total cell will flag red. Please double check the formulas. |
| Column D will auto-calculate the total Technical Functionalities set as Essential Priority with that Level 0 Capability. TM content should have been added in during Step 5. |
| Column E will auto-calculate the total Technical Functionalities set as Optional Priority with that Level 0 Capability. TM content should have been added in during Step 5. |
| Column F will auto-calculate the total Technical Functionalities with that Level 0 Capability. TM content should have been added in during Step 5. |
| Columns G & H will auto-calculate the total points per Essential/Optional Business Functionality of that Level 0 Capability. This will auto-populate column F in worksheet 1. Business Functionality. |
| Table 5. Maximum Available Points (MAP): Services Narrative |
| Populate the light orange cells in column C with how the Services points should be distributed across the Service Domains. |
| In column B, ensure there is a higher weight % in for more important services and a lower weight & for less important services. The total must equal 100%. |
| Table 1. Desirable Elements |
| Review and revise the desirable elements in the orange cells in column A as needed to align with your RFP. |
| Populate MAP for these desirable elements. |
| Populate MAP for the Response to State of Illinois Security Requirements 1 to 6. The total points should not exceed what is allocated to State Standard Security Requirements in Table 2. |
| Review all instructions and revise as needed. |
| Check all formulas to ensure correct cells are being referenced. |
| Check all formatting (font type, color & size consistency, cell fill color consistency, boarder application, hyperlinks. |
| Run spell check by holding Shift while clicking on all worksheets so all are highlighted, and then run spell check. |
| Clear authoring history by selecting File > Info > Check for Issues > Inspect Document |
| Hide this worksheet as well as Data Validation and Weights & Points by right clicking on each and selected Hide. |
| Ensure that all Worksheets are protected and that cells that should be locked are locked and editable cells remain editable after protection is enabled. |
| Suggestion, provide some instructions for protecting a worksheet. |
Introduction
| State of Illinois Environmental Protection Agency |
| Environmental Information Management System (EIMS) Procurement |
| 26-532EPA-FISCP-B-51295 |
| Attachment A - Traceability Matrix |
| Introduction |
| Information & Instructions |
| This worksheet serves as the table of contents for this workbook. The table below provides hyperlinked worksheet titles and descriptions to support the review and response to this Traceability Matrix as part of the Offer. Additional information and instructions are provided within each subsequent worksheet. The Offeror should thoroughly review all worksheets to gain a complete understanding of the scope, scale, and complexity of this solicitation before completing the necessary responses. The details provided within this document should be leveraged when developing the written technical response using the Response Template provided in G.5. of the main RFP document. |
Note: It is highly recommended that all Excel documents included in this RFP package be opened using the desktop version of Microsoft Excel. This ensures full compatibility and functionality, which may not be fully supported in web-based or mobile version. After opening the documents, please verify that all row heights are correctly set to display all content within each cell. This step is crucial to ensure no information is overlooked or hidden due to compressed row height settings.
| Worksheet Title | |||
| Hyperlinked | Description | ||
| 1. Business Capability Model | Defines the Business Capability Model Level 0 and Level 1 Capabilities utilized to structure the business functionalities identified in worksheet 2 of this document. |
No response required in worksheet
2. Business Functionality Details all business functionalities desired of the solution.
Response required in worksheet
3. Technical Functionality Details all technical functionalities desired of the solution.
Response required in worksheet
4. Services Details all services and associated deliverables required for the solicitation.
No response required in worksheet
5. Vendor Performance Details all vendor performances for the solicitation.
No response required in this worksheet
6. Performance Definitions Details performance metrics and definitions for the solicitation and resulting contract.
No response required in this worksheet
Run spell check by holding Shift while clicking on all worksheets so all are highlighted, and then run spell check.
1. Business Capability Model
| State of Illinois Environmental Protection Agency |
| Environmental Information Management System (EIMS) Procurement |
| 26-532EPA-FISCP-B-51295 |
| Attachment A - Traceability Matrix |
| Business Capability Model |
| Information & Instructions |
| Business functionalities are structured into a Business Capability Model (BCM) with two district capability levels to provide clarity and strategic planning for IEPA. |
• Level 0: Foundation capabilities serve as the major building blocks of the program, clearly communicating "what" the business does by encompassing core operational and support functions. These foundational capabilities require further decomposition to identify specific tasks necessary for achieving the agency's mission, goals, and objectives.
• Level 1: Strategic capabilities offer more granularity and are directly linked to Level 0 capabilities. At this level, enterprise architecture techniques such as pace layering, maturity analysis, initiative mapping, and application portfolio management are employed to assess solution needs.
Understanding these levels is crucial for Offerors responded to this RFP as they highlight the core functions and strategic direction of IEPA, ensuring that proposed solutions align with the agency's long-term goals and operational requirements. Familiarize yourself with the below definitions prior to starting the review of worksheet 2. Business Functionality.
| Level 0: General Operations | |
| Definition: Perform cross-agency operations to ensure consistent and efficient support. | |
| Level 1 Capability | Definition |
| Manage Site / Facility Information | Maintain site and facility information by assigning unique identifiers, storing historical documents and records, and managing compliance information. |
| Manage Metrics & Operation Reports | Collect and analyze data on employee performance, operational efficiency, and organizational resource management. |
| Manage Customer Service | Provide responsive support to the public and other stakeholders by addressing inquiries, resolving issues, and facilitating access to information and services. |
| Data Sharing With State & Federal Agencies | Coordinate efforts and share data across state and federal agencies to effectively implement environmental policies, ensure regulatory compliance, and address cross-jurisdictional environmental challenges. |
| Maintain GIS Data & Mapping | Manage Geographic Information System (GIS) data and represent relevant EPA data geospatially, including providing that data externally for public consumption and generating related exhibits, such as maps. |
| Manage Safety Training & Health Monitoring | Develop and implement comprehensive safety training programs and maintaining ongoing health monitoring to assess and address potential risks. |
| Report On & Analyze Data | View raw data and graphical representations, calculate statistics and monitor over time (i.e., past versus current data), forecast future performance or events (i.e., end of year based on trend). |
| Store & Retrieve Data | Maintain comprehensive databases that houses environmental, energy, and regulatory information. Allow access to data for analysis, reporting, and decision-making. |
| Records Retention & Maintenance | Manage the storage, retention, and maintenance of all records and documents. Ensure all retention obligations requirements are met. |
| Level 0: Compliance Monitoring & Enforcement | |
| Definition: Investigate and resolve non-compliance issues and incidents | |
| Level 1 Capability | Definition |
| Intake Complaints & Reported Incidents | Intake and process complaints or reported incidents about a potential violation(s), including assigning investigations to the appropriate personnel for follow up. |
| Manage & Track Investigations & Inspections | Conduct an investigation or inspection (with reviews as needed) and record the results. |
| Investigate Compliance Issues | Engage in enforcement investigations of non-compliance. Manage post-inspection activities in preparation for legal action involving transmission of sensitive information to other state agencies. |
| Issue Notice of Violations / Fines | Send out notices related to violations including descriptions, evidence, corrective actions, timelines, and fines (if applicable). |
| Monitor & Enforcement | Monitor the status of non-compliance issues and incidents, tracking any conditions, performing any necessary follow-up work (e.g., inspections), and ensuring resolution is documented. |
| Level 0: Financial Management | |
| Definition: Ensure accurate accounting, control of cash flow, payment reporting, and adherence to financial requirements. | |
| Level 1 Capability | Definition |
| Manage Agency Billing & Track Payments | Generate invoices, monitor payment statuses, and ensure timely collection of payments. |
| Manage Cost Recovery | Manage cost recovery by identifying and documenting expenses incurred during operations to ensure accurate reimbursement from responsible parties. |
| Manage Agency Grants & Rebates | Oversee the application, distribution, and compliance processes to ensure funds are allocated effectively and in accordance with program guidelines. |
| Manage Federal Agreements | Review and manage federal contractual documents and agreements to ensure fiscal accountability and alignment with organizational objectives. |
| Perform Financial Reconciliation | Verify that the EPA’s financial information is aligned with the applicable counterparty; make necessary adjustments if issues are identified. |
| Level 0: Program Management | |
| Definition: Oversee and coordinate various environmental / energy programs, initiatives, and research efforts. | |
| Level 1 Capability | Definition |
| Support Regulatory Policy Development | Provide research, analysis, and expertise to inform the creation and refinement of regulations and standards. |
| Monitor Environmental & Energy Conditions & Risks | Collect and analyze data to assess current state and identify potential threats to public health and ecosystems. |
| Manage Environmental & Energy Programs | Coordinate resources, evaluate program effectiveness, and engage stakeholders for various initiatives. |
| Level 0: Public Online Services & Public Engagement | |
| Definition: Provide various online services including submissions, searching / downloading documents and data, and receiving communications and notifications. | |
| Level 1 Capability | Definition |
| Provide Data For Public Consumption | Publish or make data available online for searching, viewing, download and analysis by external customers/partners. |
| Provide Self Service Resources | Provide needed and relevant tools to customers online and enabling customers to perform common business transactions at their convenience (e.g., submit permit application). |
| Manage Customer Transactions & Submissions | Track customer activity via account management to preserve a record of system transactions (e.g., submittals and payments) and to ensure any service levels and due dates are met. |
| Manage Public Notifications & Outreach | Create and distribute communications to inform and engage the public (or other relevant parties) on updates, issues, initiatives, services, etc. |
| Process FOIA Requests | Manage processing of FOIA requests, involving receipt and logging, review and clarification, assignment, search and retrieval, review for exemptions, redaction, response package preparation, release of information, follow-up (if necessary), and recordkeeping. |
| Level 0: Technical Submission Processing | |
| Definition: Manage the lifecycle of technical submissions and authorization requests submitted to the organization. | |
| Level 1 Capability | Definition |
| Intake Submission | Intake and process submissions for permits, licenses, and other applicable authorizations. Capture necessary information and route submissions to the appropriate personnel for next steps. |
| Review Submission | Review plans and accompanying submission documents that have been submitted for compliance with all applicable requirements and providing comments back to the applicant for correction (if needed). |
| Manage Decision on Submission | Upon approval, issue the necessary documents, permits, licenses, or certificates to the applicant, ensuring all information is accurate, up-to-date, and verifiable. Upon denial, notify the applicant of the rejection, informing them of the reasons for rejection and sending applicable documents from the application review. |
XACT
X1A0T
2. Business Functionality
| State of Illinois Environmental Protection Agency |
| Environmental Information Management System (EIMS) Procurement |
| 26-532EPA-FISCP-B-51295 |
| Attachment A - Traceability Matrix |
| Business Functionality |
| Information & Instructions |
| • Column A: Provides the unique ID for the Desired Business Functionality. |
• Column B: Classifies the functionalities by Level 0 Capabilities.
• Column C: Classifies the functionalities by Level 1 Capabilities.
• Column D: Provides a detailed description of the functionalities.
• Column E: Offeror shall use this column to identify the documentation name, section, and page number within the offer that speaks to the proposed solution's ability to meet this desired functionality. Note: If "None" is selected in Column F, please place N/A in this cell.
• Column F: Solution Method - The Offeror shall use the provided drop-down menu to identify how the proposed solution meets the desired functionality. Possible Values include:
| - Out of the Box / Configuration (The desirable functionality will be met through available functionality or adjusting the settings and options within the solution to meet the desirable functionality without altering the core code of the solution) |
| - New Development/Customization (The desirable functionality will be met through customization, which requires custom code development) |
| - Third-Party Product (The desirable functionality will be met by commercially available third-party solution and is not included in the offer) |
| - Functionality Not Met (The desirable functionality will not be met by the solution) |
• Column G: If "Third Party Product" is selected in column F, the Offeror shall use this column to specify which third party product is used to meet the desired functionality. No other information should be added here.
| ID# | Level 0 Capability | Level 1 Capability | Functionality Description | Offer Documentation Name, Section, & Page Number | Solution Method | Explanation |
| BF-1 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should assign a unique primary ID to each site/facility. It should support the creation and assignment of multiple levels of secondary IDs, allowing for hierarchical categorization and classification of related site information. | |||
| BF-2 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should support storing and managing all site/facility-related information, including but not limited to, site/facility name, address, operator information, contact information, permits and licenses, compliance history, inspections records, violations and enforcement actions, emissions data, remediation information, etc.. It should support the synchronization of this data and information if changes or updates are made by IEPA staff or site/facility owners or operators. | |||
| BF-3 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should enable IEPA users to view and manage all associated IDs within a site/facility record, providing a comprehensive view of related data. It should maintain a clear relationship between primary and secondary IDs, ensuring that all related information is grouped within the same family of data. | |||
| BF-4 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should allow for customization of ID structures and hierarchies to accommodate different types of relationships and IEPA needs. | |||
| BF-5 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should maintain historical documents and records of site/facility data. | |||
| BF-6 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should record, monitor, and maintain information related to incident and issue management related to each site/facility. | |||
| BF-7 | 1. General Operations | 1.1. Manage Site / Facility Information | The solution should maintain metadata for each site/facility record, including but not limited to, source bureau, data type, and timestamp. | |||
| BF-8 | 1. General Operations | 1.2. Manage Metrics & Operation Reports | The system should support the automatic and manual assignment, reassignment, and claiming of workflow tasks to users based on business rules, skill sets, availability, and location, including bulk reassignment and capturing the reason for reassignment. | |||
| BF-9 | 1. General Operations | 1.2. Manage Metrics & Operation Reports | The solution should provide dashboards for workload and performance metrics, supporting real-time resource management. | |||
| BF-10 | 1. General Operations | 1.3. Manage Customer Service | The solution should support certified mail processes, including but not limited to, tracking delivery, sending related notifications, logging delivery, etc.. | |||
| BF-11 | 1. General Operations | 1.3. Manage Customer Service | The solution should have the capability to create, update, and track customer service cases or inquiries, supporting assignment to IEPA staff member(s) based on configurable business rules. | |||
| BF-12 | 1. General Operations | 1.3. Manage Customer Service | The solution should support multi-channel notifications (email, SMS, mail) with tracking and resend capabilities. | |||
| BF-13 | 1. General Operations | 1.3. Manage Customer Service | The solution should track and log all notifications, including undeliverable notifications, and preserve copies of communications associated with relevant records. | |||
| BF-14 | 1. General Operations | 1.4. Data Sharing with State & Federal Agencies | The solution should support secure and standardized data exchange protocols to facilitate data sharing with state and federal agencies. | |||
| BF-15 | 1. General Operations | 1.4. Data Sharing with State & Federal Agencies | The solution should integrate with external systems and databases (where applicable). | |||
| BF-16 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should provide tools to create and customize searches and reports tailored to specific needs, including the ability to define report templates and formats. | |||
| BF-17 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should offer advanced analytics capabilities, including statistical analysis, trend identification, and predictive modeling. | |||
| BF-18 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should include data visualization tools such as charts, graphs, and dashboards to help users interpret and present data effectively. | |||
| BF-19 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should support real-time data processing. | |||
| BF-20 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should enable automated report generation and scheduling, allowing IEPA users to receive regular updates without manual intervention. | |||
| BF-21 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should support integration with external data sources, enabling comprehensive data analysis across multiple platforms and datasets. | |||
| BF-22 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should provide ad-hoc querying capabilities. | |||
| BF-23 | 1. General Operations | 1.6. Report On & Analyze Data | The solution should support data quality assurance processes, including but not limited to, data profiling, data cleansing, data validation, data governance and compliance, and data quality metrics. | |||
| BF-24 | 1. General Operations | 1.7. Records Retention & Maintenance | The solution should manage public records, complying with retention schedules. | |||
| BF-25 | 1. General Operations | 1.7. Records Retention & Maintenance | The solution should create and maintain a unique ID for recorded/archived documents, supporting search capabilities to locate records based on keywords, metadata, or other criteria. | |||
| BF-26 | 1. General Operations | 1.7. Records Retention & Maintenance | The solution should support notifications for different steps of the records process, such as when a bureau's document is ready to be filed, when a record is filed, etc. | |||
| BF-27 | 1. General Operations | 1.7. Records Retention & Maintenance | The solution should support the development of a "copy of record" that is preserved for legal, regulatory, or historical reasons, with formatting options for printing. | |||
| BF-28 | 1. General Operations | 1.7. Records Retention & Maintenance | The solution should support bulk exports of documents for reviewing and filing. | |||
| BF-29 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should support capturing, storing, and managing spatially-referenced data. | |||
| BF-30 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should manage spatially-referenced data. | |||
| BF-31 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should support a GIS hub accessible by internal and external users. | |||
| BF-32 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should integrate with existing GIS platforms and tools to ensure compatibility and data sharing. | |||
| BF-33 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should support multiple layers of geospatial data, allowing internal and external users to overlay various datasets. It solution should provide mapping functionality, allowing users to select/deselect data layers on a map to create customized views and visualizations. | |||
| BF-34 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should support integration of external (state and federal) GIS systems and the mapping of data extracted from these external data sources. | |||
| BF-35 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should support importing and exporting GIS data in standard formats such as shapefiles, GeoJSON, etc., to facilitate data exchange with external systems. | |||
| BF-36 | 1. General Operations | 1.5. Maintain GIS Data & Mapping | The solution should support the ability to associate files/documents with GIS locations, allowing users to link various types of data to specific geographic features on a map. | |||
| BF-37 | 1. General Operations | 1.8. Manage Safety Training & Health Monitoring | The solution should have the capability to track and organize safety training activities, such as HASWOPER, CPR, and First Aid. | |||
| BF-38 | 1. General Operations | 1.8. Manage Safety Training & Health Monitoring | The solution should maintain records of all training sessions and provide automated reminders for upcoming training requirements and deadlines. | |||
| BF-39 | 1. General Operations | 1.8. Manage Safety Training & Health Monitoring | The solution should provide documentation of each training session, tracking the number of employees participating, schedule and completion dates, and manage the issuance and storage of related certificates. | |||
| BF-40 | 1. General Operations | 1.8. Manage Safety Training & Health Monitoring | The solution should generate reports for regulatory bodies and internal review, detailing health monitoring activities and compliance status. | |||
| BF-41 | 1. General Operations | 1.8. Manage Safety Training & Health Monitoring | The solution should track medical monitoring compliance for a subset of IEPA staff, maintaining records of new hire, annual, and exit physicals to document compliance with Occupational Safety and Health Administration (OSHA). | |||
| BF-42 | 1. General Operations | 1.9. Store & Retrieve Data | The solution should provide easy access to stored data for authorized IEPA users. | |||
| BF-43 | 1. General Operations | 1.9. Store & Retrieve Data | The solution should facilitate seamless access to stored data for authorized IEPA staff. | |||
| BF-44 | 1. General Operations | 1.9. Store & Retrieve Data | The solution should offer robust search functionality, including the ability to apply filters and utilize saved search queries. | |||
| BF-45 | 1. General Operations | 1.9. Store & Retrieve Data | The solution should enable IEPA staff to upload documentation, including digitized paper documents. | |||
| BF-46 | 1. General Operations | 1.9. Store & Retrieve Data | The solution should support document versioning with version control capabilities, utilizing configurable naming conventions, and capturing essential metadata such as upload timestamp and file format. | |||
| BF-47 | 1. General Operations | 1.9. Store & Retrieve Data | The solution should be capable of assigning and searching unique IDs for the various identifiers of EPA records (e.g., permits, sites, violations, Bureau). | |||
| BF-48 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should support complaint submissions from the public via the online portal. | |||
| BF-49 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should capture detailed complaint information in a structured format, including, but not limited to, the nature of the complaint, alleged violator, incident location, complaint type, and submission method. It should also provide the option to include contact information for follow-up. | |||
| BF-50 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should enable the upload of supporting documentation, including but not limited to, images, documents, and video/voice recordings associated with complaints. | |||
| BF-51 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | Upon submission, the solution should generate a unique ID for each complaint for tracking and reference purposes. | |||
| BF-52 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should initiate workflow for the appropriate next steps, including, but not limited to, initiating an investigation, investigation reports, or an enforcement related activities. | |||
| BF-53 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should automatically route complaints to the appropriate IEPA staff member(s) based on configurable business rules. | |||
| BF-54 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should notify relevant IEPA staff upon receipt of a complaint. | |||
| BF-55 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should track the status and history of each complaint, providing visibility into the progress and actions taken. | |||
| BF-56 | 2. Compliance & Enforcement | 2.1. Intake Complaints & Reported Incidents | The solution should associate complaints with corresponding permits, facilities, sites, etc., where one exists and is known based on configurable business rules. | |||
| BF-57 | 2. Compliance & Enforcement | 2.2. Manage & Track Inspections & Investigations | The solution should provide templates and structured methods for documenting investigation and inspection details, including, but not limited to, incident location, property ownership, and violation history. | |||
| BF-58 | 2. Compliance & Enforcement | 2.2. Manage & Track Inspections & Investigations | The solution should track actions taken by field staff, with history tied to the case ID, and support search capabilities for existing investigations. | |||
| BF-59 | 2. Compliance & Enforcement | 2.2. Manage & Track Inspections & Investigations | The solution should support IEPA staff performing investigations and inspections using mobile devices, providing access to the Geographical Information System (GIS) data, enable photo capture, and functioning offline when necessary. | |||
| BF-60 | 2. Compliance & Enforcement | 2.2. Manage & Track Inspections & Investigations | The solution should support bidirectional data transmission from the field and automatically synchronize results with the central database. | |||
| BF-61 | 2. Compliance & Enforcement | 2.2. Manage & Track Inspections & Investigations | The solution should initiate workflow for the appropriate next steps, including, but not limited to, initiating enforcement activities, creating new investigations, and auto populating inspection reports. | |||
| BF-62 | 2. Compliance & Enforcement | 2.3. Investigate Compliance Issues (Legal) | The solution should generate comprehensive case files containing all relevant information necessary for compliance resolution and potential legal proceedings. | |||
| BF-63 | 2. Compliance & Enforcement | 2.3. Investigate Compliance Issues (Legal) | The solution should manage permissions and follow configurable business rules to protect confidential and privileged information. | |||
| BF-64 | 2. Compliance & Enforcement | 2.3. Investigate Compliance Issues (Legal) | The solution should facilitate effective communication and collaboration between IEPA staff and legal teams, including electronic sharing of case files and tools for tracking the status of cases referred to other entities. It should include configurable access control for case files. Add | |||
| BF-65 | 2. Compliance & Enforcement | 2.3. Investigate Compliance Issues (Legal) | The solution should support notifications and updates on the progress of compliance resolution efforts. | |||
| BF-66 | 2. Compliance & Enforcement | 2.4. Issue Notice of Violations / Fines | The solution should track violation history for locations and violators, linking violations to associated complaints, investigations, and enforcement actions. | |||
| BF-67 | 2. Compliance & Enforcement | 2.4. Issue Notice of Violations / Fines | The solution should generate enforcement-related documents, using customizable templates and prepopulated data when applicable. | |||
| BF-68 | 2. Compliance & Enforcement | 2.4. Issue Notice of Violations / Fines | The solution should utilize business rules to route Violation Notices (VNs) to the appropriate staff member for review, issuance, or other next steps. | |||
| BF-69 | 2. Compliance & Enforcement | 2.4. Issue Notice of Violations / Fines | The solution should manage the display of authorized violation information to the public in accordance with EPA policies | |||
| BF-70 | 2. Compliance & Enforcement | 2.4. Issue Notice of Violations / Fines | The solution should support the association of violations with fines and penalties, that are customizable and capable of being used for unique, site specific penalties. | |||
| BF-71 | 2. Compliance & Enforcement | 2.4. Issue Notice of Violations / Fines | The solution should include customizable fields for recommendations and mitigations in Violation Notices (VNs). | |||
| BF-72 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should manage and track Violation Notices (VNs), providing a status and including relevant information like related certifications, stack test data, corrective actions, risk management plans. | |||
| BF-73 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should track compliance with enforcement actions, including, but not limited to, re-investigations and unresolved violations, and reroute information for further action as necessary | |||
| BF-74 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should generate detailed reports on complaints and violations, supporting the analysis of type, volume, and resolution time. | |||
| BF-75 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should automate workflow tasks related to complaint and violation management, including, but not limited to, follow-up on discharge conditions and associated deadlines. | |||
| BF-76 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should provide real-time dashboards for monitoring complaint processing metrics and enforcement actions. | |||
| BF-77 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should support scheduled and unscheduled audits for compliance. | |||
| BF-78 | 2. Compliance & Enforcement | 2.5. Monitoring & Enforcement | The solution should monitor renewals and alert EPA staff and customers when renewals are upcoming or expired. | |||
| BF-79 | 3. Financial Management | 3.1. Manage Agency Billing & Track Payments | The solution should integrate with the State of Illinois's Finance platform, SAP. | |||
| BF-80 | 3. Financial Management | 3.1. Manage Agency Billing & Track Payments | The solution should integrate with the State's Payment Processing tool, JetPay, or alternative system as agreed to by both entities. | |||
| BF-81 | 3. Financial Management | 3.1. Manage Agency Billing & Track Payments | The solution should allow IEPA staff to track subcontractor information, including but not limited to, costs (contract/work order amounts), dates, and company name. It should allow IEPA staff to input approved invoice amounts to track overall expenditures against approved totals. | |||
| BF-82 | 3. Financial Management | 3.1. Manage Agency Billing & Track Payments | The solution should allow IEPA staff to access a read-only view of billing information, enabling them to query and review billing information tied to specific facilities or projects for enhanced visibility at the project management level. This functionality should support various query parameters, including but not limited to, project ID, billing period, and vendor details, to facilitate comprehensive financial oversight and decision-making. | |||
| BF-83 | 3. Financial Management | 3.1. Manage Agency Billing & Track Payments | The solution should support calculating fees, fines, and reimbursements, including but not limited to, those related to permits, licenses, certifications, site reimbursements, and violation fines. | |||
| BF-84 | 3. Financial Management | 3.1. Manage Agency Billing & Track Payments | The solution should have the ability to track the status of fees, fines, and reimbursements, noting when payments are incomplete or outstanding. | |||
| BF-85 | 3. Financial Management | 3.2. Manage Cost Recovery | The solution should support cost tracking capabilities, allowing IEPA staff to capture and categorize direct and indirect costs by project, bureau, activity, etc.. | |||
| BF-86 | 3. Financial Management | 3.2. Manage Cost Recovery | The solution should provide tools to create reports on cost recovery performance, including but not limited to, outstanding payments and payment status. | |||
| BF-87 | 3. Financial Management | 3.3. Manage Agency Grants & Rebates | The solution should provide tools to oversee and manage the application process for grants and rebates, including but not limited to, submission tracking, evaluation workflows, and disbursement tracking. | |||
| BF-88 | 3. Financial Management | 3.3. Manage Agency Grants & Rebates | The solution should integrate with the State of Illinois's Grant Management Platform, AmpliFund. | |||
| BF-89 | 3. Financial Management | 3.4. Manage Federal Agreements | The solution should provide tools to store, review, and evaluate contractual documents and agreements to support fiscal accountability with terms, conditions, and agreements. | |||
| BF-90 | 3. Financial Management | 3.4. Manage Federal Agreements | The solution should support the monitoring of performance metrics, document changes and amendments, and maintain audit trails. | |||
| BF-91 | 3. Financial Management | 3.5. Perform Financial Reconciliation | The solution should support performing financial reconciliations, comparing transactions with actual fees collected. | |||
| BF-92 | 3. Financial Management | 3.5. Perform Financial Reconciliation | The solution should identify when there is a discrepancy between IEPA records and State records. | |||
| BF-93 | 4. Program Management | 4.1. Support Regulatory Policy Development | The solution should support data analysis, enabling the identification of trends and patterns that inform regulatory policy decisions. | |||
| BF-94 | 4. Program Management | 4.1. Support Regulatory Policy Development | The solution should store public hearing data, including but not limited to, decisions, public comments, and video recordings. | |||
| BF-95 | 4. Program Management | 4.2. Monitor Environmental & Energy Conditions & Risks | The solution should support importing and exporting data from various sources, including external databases and government systems. | |||
| BF-96 | 4. Program Management | 4.2. Monitor Environmental & Energy Conditions & Risks | The solution should be capable of managing large volumes of environmental and energy data. | |||
| BF-97 | 4. Program Management | 4.2. Monitor Environmental & Energy Conditions & Risks | The solution should support the identification and monitoring of environmental justice sites and other location-based risks. | |||
| BF-98 | 4. Program Management | 4.3. Manage Environmental & Energy Programs | The solution should provide basic tools to track project timelines, costs, and milestones. It should allow users to monitor progress against deadlines/milestones. | |||
| BF-99 | 4. Program Management | 4.3. Manage Environmental & Energy Programs | The solution should include simple visual indicators or lists to help users stay informed about upcoming deadlines and completed tasks. | |||
| BF-100 | 4. Program Management | 4.3. Manage Environmental & Energy Programs | The solution should support storing, managing, and sharing data and information needed for educational programs. | |||
| BF-101 | 4. Program Management | 4.3. Manage Environmental & Energy Programs | The solution should manage processes needed for scheduling, administering, and evaluating certification exams for operators. | |||
| BF-102 | 5. Public Online Services & Public Engagement | 5.1. Provide Data for Public Consumption | The solution should allow public data searches without a login, returning relevant results via the online portal. | |||
| BF-103 | 5. Public Online Services & Public Engagement | 5.1. Provide Data for Public Consumption | The solution should enable data exports in various formats, including but not limited to, XLS/XLSX, CSV, PDF, and TXT. | |||
| BF-104 | 5. Public Online Services & Public Engagement | 5.1. Provide Data for Public Consumption | The solution should allow for robust search capabilities, including but not limited to, searching by keyword, advanced filters, geospatially, and bureau. | |||
| BF-105 | 5. Public Online Services & Public Engagement | 5.1. Provide Data for Public Consumption | The solution should allow external users to perform bulk data downloads of information they are authorized to access. | |||
| BF-106 | 5. Public Online Services & Public Engagement | 5.1. Provide Data for Public Consumption | The solution should support publishing public data, including but not limited to, site information, inspection results, citations, and public comments. It should update and synch public information if changes are made by IEPA staff. | |||
| BF-107 | 5. Public Online Services & Public Engagement | 5.2. Provide Self-Service Resources | The solution should support account creation and authentication, implementing secure login mechanisms to authenticate external users and manage access rights based on user roles and permissions. | |||
| BF-108 | 5. Public Online Services & Public Engagement | 5.2. Provide Self-Service Resources | The solution should allow external users to specify preferred communication methods and reauthenticate communication methods according to a defined frequency. | |||
| BF-109 | 5. Public Online Services & Public Engagement | 5.2. Provide Self-Service Resources | The solution should provide support for online external users through a Help or FAQ section that addresses common user queries and issues, with content updated regularly according to a defined schedule. | |||
| BF-110 | 5. Public Online Services & Public Engagement | 5.2. Provide Self-Service Resources | The solution should allow external users to manage their own accounts, including but not limited to, updating personal information, resetting passwords, managing preferences, and consolidating information. | |||
| BF-111 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | The solution should allow IEPA staff to create, edit, publish, and share forms needed for submissions. | |||
| BF-112 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | The solution should support Optical Character Recognition (OCR) capabilities to convert scanned documents into editable and searchable text. It should allow for easier data extraction and management from paper documents. | |||
| BF-113 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | The solution should be able to maintain customer information, including but not limited to, name, mailing and billing address, phone numbers, email address, and business/company name, and owner/operator. | |||
| BF-114 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | The solution should provide an online portal capable of processing all submission types, transactions, and their associated workflow and business rules. | |||
| BF-115 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | The solution should provide receipts for submissions with data, including but not limited to, purpose, date submitted, and submitting party. | |||
| BF-116 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | A unique ID should be assigned to submissions, enabling searching and tracking of submissions. | |||
| BF-117 | 5. Public Online Services & Public Engagement | 5.3. Manage Customer Transactions & Submissions | The solution should provide tools to track the status of submissions, allowing customers to monitor progress and receive updates on their submissions, payments, and requests. | |||
| BF-118 | 5. Public Online Services & Public Engagement | 5.4. Manage Public Notifications & Outreach | The solution should manage the creation, storage, and distribution of public communication materials, including but not limited to, public notices, permit noticing, Environmental Justice Notices, Public Relations (PR) Releases, and Notice of Funding Opportunity (NOFO). | |||
| BF-119 | 5. Public Online Services & Public Engagement | 5.4. Manage Public Notifications & Outreach | The solution should maintain documentation and records of all public notifications. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .