BIP3203 - Attachment D - Demo Script CMMS Modernization RFP.docx

DOCX document 55 KB Posted

Attached to
CMMS RFP
Solicitation number
27-494DOT-FINAD-B-53247
Issued by
Illinois

About this file

Summary

This is a Demonstration Script document for the Illinois Department of Transportation's (IDOT) Construction and Materials Management System (CMMS) Modernization Request for Proposal. The document serves as a comprehensive evaluation framework for vendor demonstrations of a commercial off-the-shelf (COTS) software-as-a-service (SaaS) solution designed to replace IDOT's existing construction and materials management system. The procurement encompasses configuration and implementation of the SaaS platform, data conversion, and integration with other IDOT applications. The demonstration script is organized into 25 functional categories totaling 7,530 evaluation points, covering general application and administrative functionality (500 points), contract summary management (340 points), construction diary operations (250 points), pay item management (450 points), pay item quantities (520 points), pay estimates and invoices (590 points), liens and deductions (465 points), funding and appropriations (1,015 points), process change control (350 points), obligations management (1,020 points), material assignments (375 points), materials laboratory management (100 points), materials vendor management (275 points), materials specification management (275 points), material and vendor association (275 points), materials inspector management (150 points), materials test sample creation (270 points), materials distribution and testing (270 points), materials plant inspection (280 points), materials mix designs (230 points), workflow (250 points), reporting (500 points), online help (250 points), audit functionality (250 points), and security features (250 points).

The demonstration script requires vendors to demonstrate comprehensive system capabilities including user administration, security role configuration, advanced search functionality, document management with validation controls, notification systems, and data export capabilities. Key contract management features must include contract setup and status tracking, financial and progress summaries, contract time adjustment capabilities, and approval workflows. The system must support construction diary entries with chronological display, attachment capabilities, approval workflows, and search functionality across single and multiple IDOT contracts. Materials management functionality must encompass vendor and supplier selection, material quantity tracking, evidence of inspection management, laboratory operations, test sample creation, mix design management, and plant inspection capabilities. Additional requirements include configurable workflow processes, ad hoc and system reporting with multiple export formats, customizable online help documentation, comprehensive audit logging with timestamp and user tracking, and robust security features including configurable password management, system timeout controls, login attempt restrictions, and mandatory password change intervals.

View the file

Other files

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

State of Illinois Department of Transportation Construction and Materials Management Modernization Demonstration Script

This demonstration is designed to give the Illinois Department of Transportation (IDOT) a comprehensive understanding of vendor’s solution capabilities and constraints.

1. General Application and Administrative Functionality (500 Points)

1. Provide an overview of the main screens upon entry into the system as an administrative user to show similar look and feel provided throughout the system.

a. Demonstrate the dashboard/landing page of the application and whether its content is configurable.

b. Demonstrate how the system is built with responsive design and can be used with a variety of different devices (desktops, mobile devices and tablets).

2. Create a security profile/role

3. Add a new user to the system and assign a security profile/role while demonstrating:

a. Validations in place when required fields are missing and whether those validations are configurable by an administrator

b. Warnings are in place when a user attempts to add a duplicate record and whether those warnings are configurable by an administrator

c. How data is saved as it’s entered in the system (manually or automatically).

d. How the system is built with standard keyboard functions such as tab, copy, paste, cut, etc.

e. How the new user created is restricted from accessing certain areas of the application based on their security profile

4. Search for a contract, while demonstrating any special search features available in the application (partial search, date range search, typeahead search, search history, etc.)

5. Attach/upload a document to a contract and demonstrate:

a. Any validations in place related to the size or type of document

b. How the document is indexed

c. How the document can be viewed and printed

d. Any search, filter or navigation features available on the contract’s document screen

6. Add a note to the contract and demonstrate how a timestamp and username is appended to the note.

7. Demonstrate a notification sent to a defined user group based on an action happening within the system including:

a. User’s ability to subscribe to notifications

b. Whether administrators can configure the content of the notification

8. Demonstrate how data within a grid can be sorted, filtered and exported.

9. Demonstrate how an administrator can create and modify code key values within the system.

2. Contract Summary (340 Points)

1. Demonstrate the set-up of an awarded contract.

2. Demonstrate the ability to search for a contract using a combination of search criteria (e.g. contract number, contract location, letting date and item number, etc.)

3. Demonstrate the establishment and configuration of a defined user group (and user credentials)

4. Demonstrate how view functionality differs based on user security level

5. Demonstrate displaying a contract with all applicable attributes. (Example attributes include, but are not limited to, pay items, materials associated to pay items, contractor details, etc.)

6. Demonstrate how the system captures contract "job stamp" information to identify a contract. (Job stamps contain attributes including but not limited to federal project number, project type, contract number, State job number, district number, county, section, and route.)

7. Demonstrate a user’s ability to assign multiple sub-contractors to a specific contract.

8. Demonstrate a user’s ability to indicate insurance and other pre-requisite requirements (e.g., contract bond information, designer information, key dates, etc.) within a contract.

9. Demonstrate the user’s ability to edit/add contract details only when the contract is active (i.e. not finalized).

10. Demonstrate how the system provides the ability to view ongoing contract progress and summary. (These details contain attributes including but not limited to contract percentage complete, contract location, overages, DBE % assigned and utilized, contract time frame remaining and utilized, and contract personnel.)

11. Demonstrate how the system provides the ability to view ongoing financial summary details for a contract. (These details contain attributes including but not limited to awarded contract value, adjusted contract value, obligated/unobligated amount(s), aggregate fund dollar amount details, etc.)

12. Demonstrate the user’s ability to add comments and indicate if changes are completed at the contract level for review process and how comments and completeness indications are displayed with the user’s name and timestamp.

13. Demonstrate how the system will support contract time adjustments while also retaining and displaying the original contract time limits.

14. Demonstrate the user’s ability to capture key dates, attachments, notes, etc. during a final review of a contract.

15. Demonstrate a user’s ability to approve/disapprove contract completion for contract finalization.

16. Demonstrate a user’s ability to cancel/terminate a contract with appropriate closeout changes as well as inability to change the contract status to indicate it is finalized if the system configurable rules are not met.

3. Construction Diary (250 Points)

1. Demonstrate a user’s ability to create daily diary entries and maintain attributes including but not limited to daily diary date, weather details, multiple traffic control inspections, and number of persons working.

2. Demonstrate the attachment/linking of electronic files to a diary entry (e.g. photographs, .pdf files, etc.)

3. Demonstrate how the system displays construction diary entries chronologically in a list format with attributes including but not limited to the dairy date, diary entry release date, contract status, author/user who last modified daily diary, contract progress indicator (on time/behind schedule) and user defined flags.

4. Demonstrate how the system displays construction diary summary information including but not limited to a count and status of diary entries which have been released, are in draft, or are missing.

5. Demonstrate how a user can search the diary using combinations of search criteria including but not limited to date range, status, progress indicator, author, defined flags, and keywords within a single contract and across multiple IDOT contracts.

6. Demonstrate how the system will display a summary checklist indicating missing daily diary entries.

7. Demonstrate how the system displays draft diary entries.

8. Demonstrate the system’s use of an approval workflow to finalize and lock diary entries after review.

9. Demonstrate how the system allows only one released diary entry per day.

10. Demonstrate a user’s ability to navigate to the previous or next diary entry while viewing diary details.

4. Pay Item Mgmt (450 Points)

1. Demonstrate the system’s ability to maintain a master list of "standard" pay items (i.e. pay items loaded with contracts via contract load files).

2. Demonstrate how standard and non-standard pay items are added to a contract by a defined user group.

3. Demonstrate how members of a defined user group adjust quantities for awarded contract pay items (i.e. demonstrate how contract quantities are increased and decreased)

4. Demonstrate the system’s ability for both basic and advanced searches for locating a pay item using single or combinations of search criterion within a single contract and across multiple IDOT contracts.

5. Demonstrate how the system displays all contract pay items in a list format with attributes including but not limited to pay item number, pay item description, fund key, unit of measurement, etc.

6. Demonstrate a user’s inability to delete an approved pay item from a contract.

7. Demonstrate how the system displays pay item summary information on a contract.

8. Demonstrate a user’s ability to edit pay item details on a contract.

9. Demonstrate a user’s ability to replace/revise a pay item’s assigned fund key with a new fund key.

10. Demonstrate how the system will populate and display pay item adjustment details in a list format in chronological order with attributes including but not limited to process change numbers, original submission date, other dates, and quantities.

11. Demonstrate the system’s ability to associate primary and secondary materials to a pay item and the user’s ability to change associated materials.

12. Demonstrate the system’s ability to apply different conversion formulas for primary and secondary materials associated to a pay item.

5. Pay Item Quantities (520 Points)

1. Demonstrate the creation of daily quantities (i.e. the daily quantities of pay item work completed) for awarded contract pay items.

2. Demonstrate the creation of daily quantities for added contract pay items (i.e. for pay items not anticipated at the time of contract award)

3. Demonstrate how a defined user group includes and excludes daily quantities from upcoming pay estimates

4. Demonstrate how the system will display all pay item daily quantities in a list format in chronological order with attributes including but not limited to pay item number, pay item description, pay item unit of measure, awarded quantity, pay item unit price, dollar amount, quantity type, entry date, quantity amount, quantity work location, work contractor, quantity fund key, material codes, and posting and payment status.

5. Demonstrate the system’s ability to search pay items within the quantity book.

6. Demonstrate how the system will display daily quantity summary information and allow users the ability to maintain attributes including but not limited to awarded quantities, pay item details, quantities placed, estimate/final indicator, and post for payment indicator.

7. Demonstrate a user’s ability to create/modify/delete draft quantity entries/placements and include/exclude placed quantities on a pay estimate.

8. Demonstrate how the system will flag/notify when a placed quantity exceeds the total quantity available.

9. Demonstrate how supporting inspection documentation (e.g. an Inspector Daily Report, Evidence of Material Inspection, etc.) is linked to daily quantities.

10. Demonstrate a user’s ability to create material allowances.

11. Demonstrate how the system will prevent editing of quantity placement details once posted/paid and the system’s ability to reduce a posted/paid quantity.

12. Demonstrate how the system tracks all the placed, posted for payment, and paid quantities.

13. Demonstrate the system’s ability to apply conversion factors and calculate the material quantity placed for pay item associated materials upon entering the pay item quantity placed.

6. Pay Estimates & Invoices (590 Points)

1. Demonstrate a user’s ability to create a pay estimate for a contract and auto populate fields including but not limited to pay estimate number, contract percentage complete at pay estimate creation, and total dollar amount.

2. Demonstrate how the contract dollar balance is affected if pay estimate is approved or denied

3. Demonstrate how the system displays all pay estimates chronologically in a list format with attributes including but not limited to sequence number, pay estimate number, from and to date range, total dollar amount, status, and multiple flags/indicators.

4. Demonstrate the system’s ability to search pay estimates using combinations of search criteria (such as pay estimate submitted date range, dollar amount range, pay estimate number, etc.) within a single contract and across multiple IDOT contracts.

5. Demonstrate how the system displays pay estimate summary information including but not limited to count and status for number of pay estimates and total dollar amount for approved pay estimates.

6. Demonstrate how the system displays draft/test pay estimates and provides a defined user group the ability to modify, save, delete, and submit pay estimates.

7. Demonstrate a user’s ability to delete a draft/test pay estimate and how all quantities related to the deleted pay estimate are reverted to post for payment status.

8. Demonstrate how the system requires draft/test pay estimates be reviewed/approved by designated users prior to submission.

9. Demonstrate how the system prevents the deletion of approved/submitted pay estimates.

10. Demonstrate how the system integrates submitted/approved pay estimates with an accounting/financial management module.

11. Demonstrate the creation and approval of invoices from pay estimates and how invoices are scheduled for payment

12. Demonstrate how the system will apply retainage, liens, deduction, and/or adjustments to an approved pay estimate

13. Demonstrate how the system will break down approved/submitted pay estimate details as per fund key (at fund key level).

14. Demonstrate how the system breaks down approved/submitted pay estimate details at the fund code level and applies retainage, liens, deduction, and/or other adjustments.

15. Demonstrate how the solution displays payment related attributes including but not limited to contract status, pay estimate status, total amount due, total retainage in this estimate, special retainage, other deductions, local agency share, and previous retainage.

16. Demonstrate how the system breaks down pay estimates into invoice(s) by appropriation.

17. Demonstrate how the system displays pay estimate invoices in a list format in chronological order with attributes including but not limited to invoice number, invoice amount, invoice status, appropriation account code, schedule number, voucher number, voucher date, warrant number, and warrant date.

18. Demonstrate how the system provides a multiple level approval process for pay estimate invoices.

19. Demonstrate the system’s ability to hold, skip, and reset pay estimate invoices prior to scheduling the invoice for payment and the system’s ability to credit an invoice back to the account through an expenditure adjustment after scheduling the invoice for payment.

20. Demonstrate the system’s ability to view all invoice schedules in a list format in chronological order with attributes such as sequence number, appropriation number, number of contracts included, schedule create date, etc.

21. Demonstrate the system’s ability to credit an invoice back to the account (i.e. devoucher process).

7. Liens & Deductions (465 Points)

1. Demonstrate a user’s ability to create new liens and deductions.

2. Demonstrate the system’s ability to retain and release liens and deductions for a contract.

3. Demonstrate how the system will display liens and deductions, in a list format in chronological order for a contract with attributes including but not limited to claimant, type, claim amount, established date, expiration date, status, and author.

4. Demonstrate the system’s ability to search liens and deductions within a contract using combinations of search criteria.

5. Demonstrate how the system displays summary information including but not limited to count and total active lien/deduction amounts.

8. Funding/Appropriations (1015 Points)

1. Demonstrate how the solution supports the import of funding and appropriation details from contract load files.

2. Demonstrate a user’s ability to manually add/edit funding details on a contract.

3. Demonstrate a user’s ability to manually add/edit appropriation details on a contract.

4. Demonstrate the system’s ability to assign multiple appropriations to a contract and prioritize the appropriations for creating invoices.

5. Demonstrate the system’s ability to create and maintain a funding source for each specific contract pay item.

9. Process Change Control (350 Points)

1. Demonstrate the system’s ability to create authorizations that add a new pay item(s) to a contract.

2. Demonstrate the system’s ability to create authorizations that add quantity to a pay item that already exists in a contract.

3. Demonstrate how the solution displays all authorizations in a list format in chronological order with attributes including but not limited to process change number, process type tags, dollar amount, and pending decision by user.

4. Demonstrate the system’s ability to search authorizations using combinations of search criteria within a single contract and across multiple IDOT contracts.

5. Demonstrate how the system sequentially numbers authorizations and displays summary information.

6. Demonstrate how the system displays draft authorizations and provides a defined user group the ability to modify the contents, save, delete and submit the draft authorizations for approval.

7. Demonstrate the system’s ability to automatically create and edit balancing authorizations of contract changes for contract pay items.

8. Demonstrate the system’s ability to capture and display all actions/workflow events made by individual users (approve, reject, request for additional information, etc.) with their electronic or digital signatures including a timestamp.

9. Demonstrate how the system supports configurable multi-level workflows for authorization review and approval based on certain attribute inputs with the ability to prioritize routing to manually selected users.

10. Demonstrate how the system applies changes to a contract only after the authorization obtains all required approvals and how the system will recalculate project costs based on approved authorization values.

10. Obligations (1020 Points)

1. Demonstrate the system’s ability to create new COD/obligation transactions using contract load file data

2. Demonstrate the system’s ability to create new COD/obligation transactions resulting from approved authorizations of contract change.

3. Demonstrate how the system merges CODs/obligation transactions prior to release.

4. Demonstrate a user’s ability to manually create obligation transactions on a contract.

5. Demonstrate a user’s ability to manually edit obligation transaction details on a contract including but not limited to appropriation key, sequence #, transaction amount, transaction type, transaction status, release date, and approved date.

6. Demonstrate how the system displays CODs/obligation transactions in a list format in chronological order with attributes including but not limited to assigned number, dollar amount, status, and appropriations.

11. Material Assignments (375 Points)

1. Material Assignment to Contract

1. Provide an overview of the main screens for material assignment, highlighting the consistent look and feel across the system.

2. Demonstrate how users can assign one or more materials to a contract using the Material Assignment interface.

3. Demonstrate the material search screen, enabling users to search using one or more industry-standard data elements or criteria commonly used in material management.

4. Provide an overview of the material search results grid, highlighting how each row displays relevant industry-standard data elements associated with the material record.

5. Demonstrate how users can select a material directly from the search results.

2. Producer/Supplier Selection

1. Demonstrate the ability to search for producers and suppliers of the assigned material using one or more industry-standard data elements or search criteria relevant to material assignments.

2. Demonstrate how the system filters producer and supplier options based on the selected material, when the material is chosen prior to selecting a producer or supplier.

3. Show how the system sets the default supplier based on the selected producer and material compatibility.

4. Provide an overview of the producer/supplier search results grid, highlighting how each row displays relevant industry-standard data elements associated with the producer/supplier record.

5. Demonstrate how users can select a producer and supplier for a material assignment directly from the search results.

3. Material Assignment Progress

1. Demonstrate how users can assign unapproved materials with a flag indicating pending review.

2. Demonstrate how users track and update the progress of material assignments throughout the lifecycle of the contract.

3. Demonstrate automatic logging of changes to material assignment progress.

4. Material Assignment Details

1. Demonstrate how users can set and modify the material assignment’s effective date and expiration date. Show how the system prevents overlapping or invalid date ranges.

2. Demonstrate how users can associate contract pay items to material assignments.

5. Material Quantity Movements

1. Demonstrate how users can record dated material quantity movement, including receipts, transfers, testing, adjustments, and other relevant activities.

2. Demonstrate how users can track material attributes associated with each quantity movement using industry-standard data elements.

3. Provide an overview of how the system displays summary information using industry-standard data elements that support categorization by material characteristics, movement classifications, and transactional groupings.

6. Evidence of Inspection

1. Demonstrate the ability to record multiple evidence of inspection and associate each one to its related material quantity movement.

2. Demonstrate how users can record the actual acceptance methods and inspection types applied to each evidence of inspection.

3. Demonstrate how users can track tests associated with the inspection of the material samples.

4. Demonstrate how the system enables users to manage the approval of evidence of inspections, including the handling of exceptions.

12. Materials Laboratory Management (100 Points)

1. Laboratory Setup

1. Provide an overview of the main screens for laboratory management, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define a laboratory, supporting a configurable set of industry-standard data elements relevant to laboratory identification, classification, and documentation.

2. Laboratory Inspections

1. Demonstrate how the system enables customization of inspection criteria using various field types and validation rules, using the following examples:

a. Add custom fields such as text boxes, radio buttons, checkboxes, date pickers, etc.

b. Apply validation rules such as required fields, numeric ranges, etc.

2. Demonstrate how users can track all inspections performed on a laboratory and view the details of each inspection.

3. Demonstrate the ability to manage the completion and approval of laboratory inspections.

13. Materials Vendor Management (275 Points) Vendor Master Data

1. Provide an overview of the main screens for vendor management, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define a vendor, supporting a configurable set of industry-standard data elements relevant to vendor identification, classification, and documentation.

3. Demonstrate the ability to search for vendors using one or more industry-standard data elements or search criteria relevant to vendor management.

4. Demonstrate how users can manage the vendor status by setting effective and expiration dates.

5. Demonstrate the management of multiple locations per vendor, with each location having its own set of configurable data elements.

6. Demonstrate support for aggregate vendors and associated ledgers.

14. Materials Specification Management (275 Points) Material Master Data

1. Provide an overview of the main screens for materials specification management, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define a material group, supporting a configurable set of industry-standard data elements relevant to material classification and organization.

3. Demonstrate how these material groupings can be applied in the management of materials master data to organize related materials.

4. Demonstrate how users can create and define a material, supporting a configurable set of industry-standard data elements relevant to material identification, classification, validation, and documentation.

5. Demonstrate the ability to search for materials using one or more industry-standard data elements or search criteria relevant to material management.

6. Demonstrate how users can associate Methods of Acceptance and Evidence of Inspection to materials and enforce mandatory versus optional values for each material to ensure compliance.

7. Demonstrate how users assign a predefined set of tests to a material, establishing a default test plan that automatically applies whenever a sample of that material is tested.

8. Demonstrate how the system supports the assignment of multiple configurable attributes to a material to minimize the number of separate material records (e.g., diameter and length for an ASTM A325 Type 1 bolt).

9. Demonstrate the versioning mechanism for material records by creating a new version with a future effective date before expiring the prior version, preserving all linked vendor associations, and maintaining a complete version history for traceability and compliance.

15. Material and Vendor Association (275 Points) Material-Vendor Mapping

1. Demonstrate how users can associate a single material to multiple vendors simultaneously.

2. Demonstrate how users can retrieve and view all materials associated to a vendor along with their respective association statuses.

3. Demonstrate how users can manage material-vendor associations using a configurable set of industry-standard data elements relevant to sourcing, qualification, and classification.

4. Demonstrate how the system supports reverse linking by enabling users to associate a vendor to multiple materials.

5. Demonstrate how users can search and retrieve materials associated with a specific vendor location.

16. Materials Inspector Management (150 Points) Inspector Profile

1. Provide an overview of the main screens for inspector management, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define an inspector, supporting a configurable set of industry-standard data elements relevant to inspector identification, classification, and documentation.

3. Demonstrate how users can manage the inspector status by setting effective and termination dates.

17. Materials Test Sample Creation (270 Points)

1. Sample Creation

1. Provide an overview of the main screens for materials samples, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define a material test sample, supporting a configurable set of industry-standard data elements relevant to sample identification, traceability, and classification.

3. Demonstrate how the system enables a sample to be associated to a vendor at a specific business location.

4. Demonstrate how the system allows the users to define the standard specifications or provisions, including the article number, effective date, and intended use for which the sample must be tested.

5. Demonstrate how the system enables tracking of a sample’s compliance with the following acts, when warranted:

a. Federal Buy American Act

b. Build America/Buy America Act

c. Illinois Steel Procurement Act

6. Demonstrate how users can track sample locations while associating relevant industry-standard data elements that support spatial identification and contextual referencing.

7. Demonstrate how the system supports the generation of multiple samples for a given vendor and sample date.

8. Demonstrate how the system enables users to associate material samples with relevant contract details, including contract numbers, pay items, and material assignments.

9. Demonstrate the ability to search for samples using one or more industry-standard data elements or search criteria relevant to materials sample management.

10. Demonstrate how the system enables the users to assign inspectors to material samples by referencing inspector records stored in the system.

2. Sample Approval

1. Demonstrate how the system tracks material sample statuses—such as Approved, Cancelled, Failed, In Progress, and Needs Validation—while capturing key milestones like Received Date, Start Date, and Completion Date. Show how each status change is logged with the responsible user and timestamp.

2. Demonstrate how the system allows users to reverse a sample’s approval by reverting its status to a previous state, thereby unlocking the record for further editing and updates.

18. Materials Distribution and Testing (270 Points) Test Template Creation

1. Provide an overview of the main screens for materials test templates, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define an individual test template, supporting a configurable set of industry-standard data elements relevant to test planning, execution tracking, and documentation.

3. Show how users can configure field types and validation rules within the test template using a flexible set of industry-standard data elements that support structured input, calculations, and quality control mechanisms.

4. Demonstrate how users can assign a status to each test associated with the material sample using industry-standard data elements that support lifecycle tracking and quality assessment.

5. Demonstrate how users can assign tests that need to be performed on a material sample.

6. Demonstrate how the system allows users to automatically populate the test list with predefined tests associated with the selected material.

7. Demonstrate how users can mark a material sample as ‘Ready for Review’ once all associated tests have been completed.

8. Demonstrate how the system allows designated user groups to mark individual tests as 'Passed' or 'Failed,' authorize or unauthorize the material sample based on test results, attach supporting documents, and automatically capture the authorizing individual's name, username, and timestamp for each action.

9. Provide an overview of how the system displays an on-screen summary view that consolidates key information from defined tests and their results.

10. Demonstrate how the system allows users to update a test template and its configuration table by creating a new version, while preserving previous versions.

19. Materials Plant Inspection (280 Points)

1. Plant Master Data

1. Provide an overview of the main screens for HMA or PCC plants, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define an HMA or PCC plant, supporting a configurable set of industry-standard data elements relevant to plant identification, operational tracking, and documentation.

3. Demonstrate the ability to search for HMA or PCC plant using one or more industry-standard data elements or search criteria relevant to plant management.

4. Demonstrate how the system allows each HMA or PCC plant to be associated to one vendor, while also allowing each vendor to manage multiple HMA or PCC plants.

2. Plant Inspections

1. Demonstrate how users can create and define an HMA or PCC plant inspection template, supporting a configurable set of industry-standard data elements relevant to inspection planning, execution tracking, and documentation.

2. Demonstrate how users can assign required HMA or PCC plant inspections based on defined intervals or frequencies.

3. Demonstrate how users can track all inspections performed on a HMA or PCC plant and view the details of each inspection.

4. Demonstrate how the system tracks HMA or PCC plant inspection statuses—such as In Progress, Approved, Rejected, and Canceled. Show how each status change is logged with the responsible user and timestamp.

20. Materials Mix Designs (230 Points) Mix Design Master Data

1. Provide an overview of the main screens for Mix Designs, highlighting the consistent look and feel across the system.

2. Demonstrate how users can create and define a Mix Design, supporting a configurable set of industry-standard data elements relevant to mix identification, classification, and documentation.

3. Demonstrate how users can create and define Mix Design Components, supporting a configurable set of industry-standard data elements relevant to material sourcing, composition, and classification.

4. Show how the system allows users to associate an unlimited number of components to each mix design.

5. Demonstrate how the system allows users to capture detailed mix formula data—such as gradations, binder content, and other material properties—for each component used in a mix design, including FRAP, RAP, RAS, and more.

6. Show how the system allows users to define and configure individual optimum mix design properties using customizable industry-standard data elements, while supporting a wide range of field types and validation rules.

7. Demonstrate the ability to search for mix designs using one or more industry-standard data elements or search criteria relevant to mix designs.

8. Demonstrate how the system enables users to mark mix designs as approved, unapproved, or canceled, and manage authorization status with full traceability. Highlight how users can manually enter the name of the authorizing individual, while the system automatically records the username and timestamp for each authorization or unauthorization action.

21. Workflow (250 Points)

1. Demonstrate the system’s workflow capabilities including:

a. One example workflow based on a common business process

b. Any administrator workflow tools/reports available to analyze workflow activity systemwide

c. Whether administrators have the ability to build/modify workflows

22. Reporting (500 Points)

1. Demonstrate the features of the system’s ad hoc reporting tool including:

a. How a new ad hoc report is created

b. The ability to save reports and make them available to other users

c. The ability to view and export reports into various formats (PDF, Word, Excel)

d. The ability to export large data sets

2. Demonstrate a user generating a system report (non-ad hoc) with prepopulated contract data.

23. Online Help (250 Points)

1. Demonstrate the features of the system’s online help tool including:

a. +How the online help is organized (by screen, process, etc.)

b. Whether administrators can customize/modify sections of the online help

24. Audit (250 Points)

1. Demonstrate the features of the system’s audit tool including:

a. How to view audit logs for transactions (edits, deletes, additions) occurring in the system. The logs should include:

i. The date and time an auditable event occurs

ii. The objects affected

iii. The identity and role of the actor performing the activity

iv. The outcome (success or failure) of the activity

v. The audit history of a particular record (original data retained)

b. Any audit tracking reports included with the system and how those reports can be viewed/exported.

25. Security (250 Points)

1. Demonstrate the system’s security features including:

a. How the application allows configurable password management features such as minimum password length, password complexity, etc.

b. A configurable system timeout which would require a user to re-authenticate after the timeout is exceeded

c. How the system denies access to a user after a pre-defined number of unsuccessful login attempts

d. How the system provides self-service capabilities for users to reset passwords and recover usernames

e. How the system requires users to change passwords after a configurable period of time

File details come from the government source that posted it. Updated .