2-Attachment XX- Scope of Work Template.xlsx

XLSX spreadsheet 51 KB Posted Mar 5, 2026

Attached to: RFI - Payroll, Time and Attendance System (OCFO/DoIT) State and local contract opportunity
Solicitation number: 545199
Issued by: Wayne County, Detroit City, Michigan

About this file

Written by GovTribe AI · Mar 10, 2026

This is a Scope of Work Requirements Matrix document for the City of Detroit, Office of the Chief Financial Officer (OCFO) and Department of Innovation and Technology (DoIT), supporting a Request for Information (RFI) for a Payroll and Time & Attendance System. The document outlines comprehensive technical and functional requirements across multiple modules including Personnel Management, Records Management, Security, User Interface, and Training and Support. The RFI is for information and planning purposes only and does not constitute a formal solicitation or obligation for the City to award a contract or provide compensation for submitted information or its use.

The Requirements Matrix specifies critical and desired functionalities that prospective vendors must address in their responses. Key areas include bi-directional integration capabilities with the City's ERP system (Oracle Cloud), LMS system, and UltiPro; comprehensive audit trail and role-based security features with multi-level access controls; robust reporting capabilities including custom report writers and standard templates; mobile device support with screen optimization; compliance tracking and certification management; vendor management and self-registration; electronic bid submission and tabulation; and extensive support and training requirements including 24/7/365 technical support, role-based online training, and zero-cost updates and upgrades as part of the maintenance agreement. The City requires SAML authentication integration with Azure Active Directory for single sign-on functionality, data encryption both in storage and transit, and compliance with the City's Cloud Security Policies.

View the file

Other files for this state and local contract opportunity

Other files attached to RFI - Payroll, Time and Attendance System (OCFO/DoIT), newest first.
File	Type	Posted
1-RFI 545199 Payroll, Time and Attendance System.pdf	PDF	Mar 5, 2026

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

	ATTACHMENT XX - REQUIREMENTS MATRIX
RFP #:			Vendor:
	Available Responses
	C	Requirement Met and Proposed (Standard features in the generally available product)		0	have it
	A	Intent of Requirement Met and Proposed with Alternative		0	don't have it
	N	Requirement Not Met with Proposal		0	third party
					custom
			TOTAL	0

	Note: Proposals that are applicable to only certain system components are not required to complete all tabs within this attachment. In the case where a tab is not applicable, please mark the tab N/A.
	Req #	Personnel Management Module
Function	Requirement	Critical or Desired	Vendor Response
(C, A, N)	Modules Required to Fulfill Requirements	Third Party?	Comments	City of Detroit	Rating

1	Interface/Integration	Ability to interface bi-directionally with the City's LMS system.	Desired	Ability to interface bidirectionally with the City's ERP system (Oracle Cloud), specifically the Procurement modules.	Critical	Note, moved to Technical tab, delete from this tab before finalizing.
2	Interface/Integration	Ability to interface with UltiPro (inbound)	Critical		No
3	Interface/Integration	Ability to fully integrate, bi-directionally, with Scheduling module.	Critical		No
4	General/Technical	Compliance reminders: Certification or training is due at specified intervals (ex: 90 days, 30 days, one week)	Desired	Notifications to suppliers: about bid closing, amendments to bids, responses to questions, extensions of end date, other activity on the bid, bid invitations	Critical
5	General/Technical	Compliance reminders: System is capable of providing multiple reminders for certifications or trainings coming due, at intervals specified by the department, with proper security permissions	Desired	Notifications to buyers: questions asked, bid closing, when a bid is received (need to mask who submitted and what was submitted), intention to bid indicated	Critical
6	General/Technical	Compliance reminders: Certification or training is expired	Critical	View supplier activity, configure what data is available to buyers	Critical
7	General/Technical	Ability to lock out users from entire system if compliance/training has lapsed	Desired
8	General/Technical	Specifies start and end dates that training and certification is valid to/from, including non-expiration option	Critical	The system has the ability to provide role-based, dollar-amount-based, and org-chart-based approvals.	Critical
				The system has the ability to track approval history with timestamps.	Critical
9	General/Technical	Allow users with appropriate permissions to submit/create/upload certifications/training certificates/licenses/images into system	Critical	Allows customers to create custom cross-maps between their commodity codes and common list of commodity codes like NIGP.	Critical
10	General/Technical	Allows the a user with appropriate permissions to conduct mass import of data using CSV or similar (bulk upload)	Critical	Allows the a user with appropriate permissions to conduct mass import of data using CSV or similar (bulk upload)	Critical
11	General/Technical	Allows the for custom field labeling based on customer's need to match terminology.	Desired	Allows for custom field labeling based on customer's need to match terminology.	Desired
12	Reporting	Ability to provide an integrated report writer that allows user-defined custom reports	Critical	Ability to provide an integrated report writer that allows user-defined custom reports	Critical
13	Reporting	Ability to provide a library of standard reports (i.e. "canned" reports).	Desired	Ability to provide a library of standard reports (i.e. "canned" reports).	Critical
14	Reporting	Ability to allow a user to modify existing reports and save as a report template, with appropriate security permissions in place.	Critical	Ability to allow a user to modify existing reports and save as a report template, with appropriate security permissions in place.	Desired
15	Reporting	Ability to provide an integrated report writer that has a consistent look and feel across all proposed system features.	Desired	Ability to provide an integrated report writer that has a consistent look and feel across all proposed system features.	Desired
16	Reporting	Ability to provide an integrated report writer that allows the creation of reports comprised of any discrete data field throughout the system with proper security permissions.	Critical	Ability to provide an integrated report writer that allows the creation of reports comprised of any discrete data field throughout the system with proper security permissions.	Critical
17	Reporting	Ability to configure and save ad hoc reports by individual user, with the ability to provide access to other users or groups with appropriate security permissions.	Critical	Ability to configure and save ad hoc reports by individual user, with the ability to provide access to other users or groups with appropriate security permissions.	Critical
18	Reporting	Ability to report on changes made within the module within certain time parameters as specified by the user	Critical	Ability to report on changes made within the module within certain time parameters as specified by the user	Critical
19	Role based security	The system has the ability to provide role-based security.	Critical	The system has the ability to provide role-based security.	Critical
20	Audit trail	The system has the ability to track and audit changes throughout the system that creates a log of all records maintained and includes:	Critical	The system has the ability to track and audit changes throughout the system that creates a log of all records maintained and includes:	Critical
20a	Audit trail	Date;	Critical	Date;	Critical
20b	Audit trail	Time;	Critical	Time;	Critical
20c	Audit trail	User;	Critical	User;	Critical
20d	Audit trail	Information prior to change;	Critical	Information prior to change;	Critical
20e	Audit trail	Changed information; and	Critical	Changed information; and	Critical
20f	Audit trail	Other administer-configurable information.	Critical	Other administer-configurable information.	Critical
21	APIs	The system has the ability to support API's (Application Programming Interface) for third-party system integration, imports, and exports of data. Proposal shall include description of the type(s) of API(s) available.	Desired	The system has the ability to support API's (Application Programming Interface) for third-party system integration, imports, and exports of data. Proposal shall include description of the type(s) of API(s) available.	Desired
22	Prod/Test Environments	The system has the ability to support a production, test and development (non-production) environment including the ability to track software changes applied to each environment and roll back as necessary.	Critical	The system has the ability to support a production, test and development (non-production) environment including the ability to track software changes applied to each environment and roll back as necessary.	Critical
23	Data Migration	The system has the ability to migrate historical data from DFD/EMS's current solution.	Critical	The system has the ability to migrate historical data from Oracle Cloud platform.	Lightly desired
24	Mobile	The system has the ability to recognize the device that is being used to view the software to make the necessary window adjustments (screen optimization).	Critical	The system has the ability to recognize the device that is being used to view the software to make the necessary window adjustments (screen optimization).	Desired
25	Data Dictionary	The system has the ability to provide a centralized data dictionary, that fully describes table structure and appropriate levels of metadata.	Desired	The system has the ability to provide a centralized data dictionary, that fully describes table structure and appropriate levels of metadata.	Desired
				Public summary page with attached documents that is accessible to all users (including those not registered)	Critical
				Ability to move over all registered Oracle suppliers or invite them to the new system.	Critical
				Self-service registration for suppliers.	Critical
				Suppliers have ability to store commonly-used documents.	Desired
				Contract management - documentation of performance of the contract, features that integrate with Oracle ERP
				Ability to interface with the City's Oracle system.

Requisition - Initiate a RFx event in the system based on the requisition from Oracle - set up parameters on what should be triggering the event Supplier - Feed the active supplier list from Oracle to be included in the bid

	Buyer should be able to invite a new supplier to the bid via email
	Supplier evaluation - Equalization credit handling
RFx Event setup	Setup the event manually or create based on a trigger from Oracle.

RFX Templates.

Ability to copy prior events.

Ability to customize questions or replace attachments on an event created from a template Document library - Buyers should be able to look for documents from other customers in a library.

Ability to add commodities listing.

Ability to batch upload and organize multiple documents by buyers.

Ability to reassign buyers during an open bid.

Event Collaboration	Allow multiple teams to colloborate in setting up the event.
Marketing	Vendors can easily find the open bids in one centralized location on the website

Nice to have - Create customizable overview summary with key dates and share to social media

Inviting Suppliers Ability to associate multiple commodities and add suppliers in bulk on the invitation.

Inviting new suppliers via email.

Pull vendors from other sources or connect to vendor pools.

Amending/Extending events	Ability to amend and/or extend an event
Accepting Suppliers Response	Suppliers should be able to add, save, update, and preview their responses.

Be able to require response/attachments to certain questions.

Masking the responses till the bid is closed.

Response Evaluation Ability to separate and evaluate responses in different sections like technical, pricing.

Build Ethics form in the evaluation process.

Configurable evaluation scorecards including the ability to handle equalization credit.

Ability to store and display business certifications during evaluation.

Award System must be able to acknowledge a joint venture.

Configurable notifications upon award -when to send and who to send

RFx Creation	Create, publish, manage and award all solicitations types, including but not limited to: Request for Proposals (RFP), Invitations for Bid (IFB), Requests for Quotations (RFQ), Request for Qualifications (RFQ), and Cooperative Bids.
RFx Creation	Upload and store multiple boilerplate/standard documents as standard templates (as minimum documents for solicitations), which Court Users can choose to include or exclude in a solicitation. The proposed system must support a variety of document/file types including but not limited to: .docx, .doc, .xls,

.xlsx, .pdf, .jpg, .tif, .rtf, csv and autocad formats. (Contractor’s proposal must identify the document types that are supported.)

RFx Creation 4.3. Upload individualized documents specific to a solicitation. The proposed system must support a variety of document/file types including but not limited to: .docx, .doc, .xls, .xlsx, .pdf, .jpg, .tiff, .rtf, csv and autocad formats. (Contractor’s proposal must identify the document types that are supported.)

RFx Creation	Customize line-items in solicitations.
RFx Creation	Advertise solicitations to potential bidders.
RFx Creation	Court can filter and notify bidders from Vendor’s pre-established Vendor pool.
RFx Creation	Provide suggested Vendors for bid.
RFx Creation	Allow private bids, where only the Vendors chosen by the Court are allowed to see and participate in the bid.
RFx Creation	Support multiple commodity codes used to identify solicited goods and services. Minimally, the system must support; NIGP, UNSPSC, NAICS, and SIC. Contractor’s proposal must identify all commodity codes that are supported on the proposed system.
RFx Creation	Automatically assign a bid number using a given format. The Court must have the ability to override a bid number.
RFx Creation	Allow the Court to upload attachments to the RFP. The attachments must be unlimited in size and number.
RFx Creation	Provide a work area for bids prior to release. These bids can be edited and deleted at any time and will not be accessible to the public.
RFx Creation	Support multiple delivery or work locations.
RFx Management	Provide automated, electronic tracking system of bid activity and document views by each Vendor.
RFx Management	Provide online question and response management tool for each solicitation. Bidders must be able to be notified and view Court responses.
RFx Management	Questions can have multiple answers
RFx Management	Questions and responses must have a time and date stamp
RFx Management	The Court will be notified of incoming questions
RFx Management	The Court must have the ability to respond to questions as they are received
RFx Management	Questions relating to the bid may not be received after the Court’s submittal due date
RFx Management	Questions should be kept anonymous.
RFx Management	Provide a mechanism to block or remove questions deemed to be inappropriate and irrelevant to the solicitation.
RFx Management	Provide both mandatory and non-mandatory Pre-Evaluation meetings with Vendors online. Meetings can be an audio or telephone type conference.
RFx Management	The Court must have the ability to mute all Vendors
RFx Management	Vendors must be able to type questions during the conference
RFx Management	Transcripts of conferences must be available to Vendors after the conference is complete.
RFx Management	The system must record any agency participating in the conference
RFx Management	Ability to amend and create addenda for each solicitation
RFx Management	Distinguish between mandatory and optional bid requirements.
RFx Management	Track and display Vendor qualifications, including but not limited to local businesses, minority owned business, and Disabled Veterans. Describe the proposed system’s capability to include these customizable registration fields.
RFx Management	Allow bidders to revise bids up to the bid closure date and time.
RFx Management	Allow the Court to retract a currently posted bid.
RFx Management	Allow the Court to cancel a bid once the bid has closed.
Bid Submission/Collection	Provide electronic proposal submission of sealed bids via a secure connection. Describe security features in the Bidder Explanation box.
Bid Submission/Collection	Bidder can upload and attach documents as part of the bid.
Bid Submission/Collection	Bidders must have the ability to take exception to forms and list exceptions. The Court’s preference would be for the exceptions to be listed in summary form per submittal.
Bid Submission/Collection	Bidder must digitally accept and sign terms of each document. Indicate the types of electronic signatures that are compatible with the proposed system. Digital or electronic signatures must meet the requirements of the CA State Government Code, Section 16.5 and the CA Code of Regulations, Title 2, Division 7, Chapter 10, and the CA Civil Code Section 1633.1 et seq., and any other applicable laws, rules and regulations.
Bid Submission/Collection	Bidders must have the ability to electronically submit notes, comments, and explanations.
Bid Submission/Collection	Allow bidders to indicate “will bid” or “no bid” response.
Bid Submission/Collection	The Court must have the ability to define a No-Bid Survey for Vendors to complete when they place a no-bid response.
Bid Submission/Collection	Provide an electronic receipt showing date and time of bid submission
Bid Submission/Collection	Seal bid until after bid closing date and time and/or notice of intent to award has been issued.
Bid Submission/Collection	The Court may need to hide pricing information from a bid prior to the award release. Price hiding is used to enforce a pre-selection of Vendors based on non-price criteria. Provide your system’s method to support hidden prices.
Bid Submission/Collection	Once the bid has closed, only a Court User can decrypt the bid.
Bid Submission/Collection	Provide electronic bid tabulation after bid has closed.
Bid Submission/Collection	Court Users can post Notice of Award and any post-submission activity.
Bid Submission/Collection	Customizable reports that can be directly accessed. Reports must be maintained for a minimum of five (5) years after the close of the RFP. Reports include but are not limited to, tabulation reports, bid packet, bid list and questions.
Bid Submission/Collection	Conduct Best and Final Offers (BAFO) through the system. The Court must have the ability to contact specific Vendors who provided a submittal and as designated by the Court based on evaluation criteria (e.g. top three) without notifying all Vendors who participated.
Bid Submission/Collection	Support awarding contracts to multiple Vendors. The Court may need to award to multiple Vendors, split an award, or award to a primary and secondary Vendor.
Vendor Management	Provide easy and free self-registration and self-administration for bidders. Registration information must be available to Court Users.
Vendor Management	Allow multiple contacts per bidder.
Vendor Management	Maintain a large and searchable database of bidders. Court Users must be able to search by, but not limited to, the following: service/commodity type, bidder name, commodity/classification code, etc. Include the number of bidders currently registered on your website. (Provide a brief description on how your business solicits the vendor community for registration.)
Vendor Management	Automated, electronic notification of the release of a competitive solicitation for all Vendors in designated commodity codes. Additionally, provide automated electronic notification for any corresponding notifications, including but not limited to: addendum/changes, questions and answers, pre-award and award notifications, and notices of award.
Vendor Management	Track all notifications and the date and time provided to bidders.
Vendor Management	Method for Court to invite or designate which groups of Vendors will be notified of bid.
Vendor Management	Track bid activity for each Vendor (including filters for DVBE designated vendors, SBE vendors, by commodity/classification code, etc.)
Vendor Management	Allow the Court to invite Vendors to the solicitations that are not currently identified in the Vendor database pool.
Vendor Management	Accommodate mass updates and deletes
Vendor Verification	Track and maintain Vendor submitted certifications: These include but are not limited to Darfur, Iran, DVBE, CA—SBE, CA-Micro
Vendor Verification	Verify Vendors are not listed on the CA Tax Delinquent lists: CA State Board of Equalization & CA Franchise Tax Board

Technical

	ATTACHMENT XX - REQUIREMENTS MATRIX
RFP #:			Vendor:
	Available Responses
	C	Requirement Met and Proposed (Standard features in the generally available product)		0
	A	Intent of Requirement Met and Proposed with Alternative		0
	N	Requirement Not Met with Proposal		0

TOTAL 0

	Req #	Records Management
Function	Requirement	Vendor Response
(C, A, N)	Modules Required to Fulfill Requirements	Third Party?	Comments

1	APIs	The system has the ability to support API's (Application Programming Interface) for third-party system integration, imports, and exports of data. Proposal shall include description of the type(s) of API(s) available.
2	General	Bidders must be able to access the site via any of the major commercially available web browsers, (e.g., Explorer, Safari, Firefox, Chrome, etc.) on any basic configuration Linux, PC or Mac computer. Provide detailed information about the client requirements of the proposed system and include information about supported web browsers, operating systems, and corresponding versions.
3	Hosting and Platform	The provider must clearly identify:
3a		System environments available to the City (e.g., production, development, and test)
3b		Shared components of the system (e.g., network segments, backup tapes, etc.)
3c		Data storage and transfer limits and overage penalties
3d		Normal and peak bandwidth requirements
4	Cloud Solution	The provider must clearly identify:
4a		The proposed service model (i.e. SaaS, PaaS, IaaS, etc.)
4b		The proposed development model ( i.e. Private Cloud, Public Cloud, Community Cloud or Hybrid Cloud)
4c		Whether it relies upon any third parties in the provisioning of its Cloud deployment model;
5	General	Proposal includes plan to keep the software current with Windows 11 update cadence.
6	General	Proposal includes minimum hardware requirements for workstations.
7	General	Proposal confirms current version protocol software system has history of 99.999% or greater uptime reliability.
8	General	Proposal includes data ownership, access, and retention requirements.
9	General	Proposal includes business continuity and recovery requirements.
10	Records Management	The system must securely store and protect records against, but not limited to, the following: technical hardware/software failure or errors, act of human error or failure, unauthorized access, software attacks, forces of nature, etc. Proposer must address specific encryption methods and network protocols. Also include information concerning the data center facilities used for the hosting environment.
11	General	Support generally-accepted commercial standards of accessibility features, including but not limited to, the Americans with Disabilities Act (ADA), the Rehabilitations Act of 1972, and all other applicable regulations.
12	Reporting	Ability to provide an integrated report writer that allows user-defined custom reports.
13	Reporting	The system has the ability to provide an integrated report writer that allows the creation of reports comprised of any discrete data field throughout the system with proper security permissions.
14	Reporting	The system has the ability to provide a library of standard reports (i.e. "canned" reports).
15	Reporting	The software must provide a basis, such as a report wizard, for preparing and generating a variety of statistical and analytical reports.
16	Reporting	The system has the ability to configure and save ad-hoc reports by individual user, with the ability to provide access to other users or groups with appropriate security permissions.
17	Reporting	The system has the ability to drill down on reports.
18	Reporting	The system has the ability to allow a user to modify existing reports, with appropriate security permissions.
19	Reporting	The system has the ability to save favorite reports in a menu or pick-list by individual user.
20	Reporting	The system has the ability to allow reports to be generated that are searchable.
21	Reporting	The system has the ability to schedule reports to be run in the future or on a recurring basis.

Security

	ATTACHMENT XX - REQUIREMENTS MATRIX
RFP #:			Vendor
	Available Responses
	C	Requirement Met and Proposed (Standard features available in the product)		0
	A	Intent of Requirement Met and Proposed with Alternative		0
	N	Requirement Not Met with Proposal		0

TOTAL 0

	Req #	Function	Security Requirement	Vendor Response
(C, A, N)	Modules Required to Fulfill Requirements	Comments
	1	Audit Trail	The system has the ability to track and audit changes throughout the system that creates a log of all records maintained and includes:
	1a		Date;
	1b		Time;
	1c		User;
	1d		Information prior to change;
	1e		Changed information; and
	1f		Other administer-configurable information.
	2	Audit Trail	The system has the ability to allow auditing within features to be determined by the module, and configured by the administrator. Proposer should explain any exceptions or constraints.
	3	Audit Trail	The system has the ability to provide functional security to control what processes can be performed by certain users (i.e. view vs. edit information).
	4	Audit Trail	The system has the ability to allow a City system administrator to configure the duration that time audit logs are retained (e.g. 90 days). Proposer should describe how this feature works.
	5	Audit Trail	The system has the ability to provide access to audit trails for only the users with proper security based upon the user’s security profile.
	6	Audit Trail	The system has the ability to provide customizable audit reports.
	7	Audit Trail	The system has the ability to provide configurable exception reports.
	8	Audit Trail	The system has the ability to allow authorized users to have access to a log of security activity to determine users that have signed on and off the system, as well as unsuccessful attempts to sign on to the system.
	9	Audit Trail	The system has the ability to allow the audit trail to have a date/time stamp to the nearest second.
	11	Role based security	The system has the ability to provide role-based security.
	12	Role based security	The system has the ability to allow the City to determine which fields are visible to roles.
	13	Role based security	The system has the ability to provide security at the following levels:
	13a		Department or Agency;
	13b		Division;
	13c		Role or group;
	13d		User ID;
	13e		Screen;
	13f		Menu;
	13g		Report;
	13h		Field;
	14	Role based security	The system has the ability to provide read, write, update, and delete access using role based security.
	15	Role based security	The system allows for departmental administrative self-service (e.g. ability to make changes to roles and workflows) with audit trail capability.
	16	Role based security	The system has the ability to update all user profiles automatically (user discretion) when a change in their role (s) is/are made.
	17	Role based security	The system has the ability to allow a City system administrator to add and change permissions for system access.
	18	Role based security	The system has the ability to allow department administrators to add and change permissions for system access for a group of users.
	19	Role based security	The system has the ability to provide both read and write access to the system using role based security.
	20	Security	The system has the ability to inherit groups from Active Directory for application authentication.
	21	Security	The system has the ability to store passwords in encrypted form, if applicable.
	22	Security	The system has the ability to encrypt data stored in the database.
	23	Security	The system has the ability to encrypt data stored in the application.
	24	Security	The system has the ability to log users off the system after an administrator-defined period of inactivity, based on user-defined roles.
	25	Security	The system has the ability to apply the same security permissions to system queries and reports as it does to data fields/elements, based on user (e.g. data fields masked on a record or transaction are similarly masked on reports run by the user).
	26	Security	The system has the ability to scan attached files for viruses, malware, or other cybersecurity threats (vendor to specify capability for using City preferred anti-virus solutions).
	27	Security	The system has the ability to capture IP addresses from a requestor.
	28	Security	The system has the ability to comply with the City's Cloud Security Policies (https://detroitmigov.box.com/s/p51hhvpnxvm9g9sdgalb36fh1up1e2is).
	29	Security	The system has the ability to utilize the City's SAML Authentication (Azure Active Directory) for user validation to achieve single-sign-on, regardless of deployment method.
	30	Security	The system has the ability to map SAML groups or App roles from Azure Active Directory for application permissions.

User Interface

	ATTACHMENT XX - REQUIREMENTS MATRIX
RFP #:			Vendor
	Available Responses
	C	Requirement Met and Proposed (Standard features available in the product)		0
	A	Intent of Requirement Met and Proposed with Alternative		0
	N	Requirement Not Met with Proposal		0

TOTAL 0

	Req #	Function	User Interface Requirement	Vendor Response
(C, A, N)	Modules Required to Fulfill Requirements	Comments
	1	Mobile	The system has the ability to support access from mobile devices with appropriate security permissions.
	2	Mobile	The system has the ability to recognize the device that is being used to view the software to make the necessary window adjustments (screen optimization).
	3	Search capabilities	The system has the ability to search by wild cards, based on security permissions.
	4	Search capabilities	The system has the ability to search by fragment or portion of a word.
	5	User Interface	The system has the ability to provide American Disability Act (ADA)-compliant online help documentation.		ADA Compliance
	6	User Interface	The system has the ability to provide error messages that appear in a consistent format across all system features.
	7	User Interface	The system has the ability to provide error messages that are integrated with online help functionality.
	8	User Interface	The system has the ability to create error logs with detail associated with the error.
	9	User Interface	The system has the ability to provide administrator configurable error messages.
	10	User Interface	The system has the ability to provide user-defined fields with appropriate security permissions.
	11	User Interface	The system has the ability to allow the City to determine which fields are required, beyond standard system keys.
	12	User Interface	The system has the ability to provide an administrative messaging system (e.g. a message to alert users of system maintenance activity).
	13	User Interface	The system has the ability to provide customizable screens based on roles and permissions.
	14	User Interface	The system has the ability to provide contextual help (i.e. field descriptions that are displayed based on the location of the mouse or cursor).
	15	User Interface	The system has the ability to store field-level metadata and display it in the user interface when appropriate.
	16	User Interface	The system has the ability to provide customizable help.
	17	User Interface	The system has the ability to provide data validation on entry.
	18	User Interface	The system has the ability to support pre-filled fields in appropriately pre-formatted screens eliminating redundant data entry.
	19	User Interface	The system has an intuitive user interface and simple design which enables users to accomplish tasks with minimal number of clicks and keystrokes.
	20	User Interface	The system has the ability to provide links to associated features from any display screen to minimize backing out of one screen to access another, with appropriate security.
	21	User Interface	The system has the ability to allow the configuration of processes using either the keyboard only, the mouse only, or a combination of the two, depending on a user's preference.
	22	User Interface	The system has the ability to provide the user with integrated application features that offer a consistent user interface to minimize user training and administration of the system.
	23	User Interface	The system has the ability to allow the system administrator to rename field labels.
	24	User Interface	The system has the ability to allow all end user customizations and configurations related directly to the system to be stored in a central database and not stored in files residing on user workstations.
	25	User Interface	The system has the ability to provide drop down boxes or other pick list function for data selection.
	26	User Interface	The system has the ability to attach files to records in the system with the ability to restrict this functionality.

Training and Support

	ATTACHMENT XX - REQUIREMENTS MATRIX
RFP #:			Vendor
	Available Responses
	C	Requirement Met and Proposed (Standard features available in the product)		0
	A	Intent of Requirement Met and Proposed with Alternative		0
	N	Requirement Not Met with Proposal		0

TOTAL 0

	Req #	Function	Support and Training Requirement	Vendor Response
(C, A, N)	Modules Required to Fulfill Requirements	Comments
	1	Support	Proposal includes 24/7/365 technical support for proposed solution.
	2	Support	All calls and e-mails to support will be recorded and available to City of Detroit users
	3	Support	The system has the ability to allow for severity levels for support as defined by the City.
	4	Support	Critical Events (unable to use protocol software with major disruption of user service) - Vendor will accept and commence work on the call immediately and resolved within no more than 2 hours from notification.
	5	Support	Major Events (localized disruption of service, but not system wide) – Vendor will accept and commence work on the call within no more than 4 hours and resolved within 2 working days.
	6	Support	Administrative/Minor Inquiries - Vendor will accept and commence work on the call within no more than 1 working days and resolved within 20 working days or as agreed with user.
	7	Support	The vendor will provide web-based support, with a searchable database of common problems, to assist end users in researching error messages.
	8	Support	All product updates should be available at no additional cost. Maintenance and upgrades must be scheduled and performed at a time with the least impact to the procurement processes of the City. City hours are 8:00 a.m. through 5:00 p.m. EST
	9	Support	Perform daily system backup and provide for recovery from partial and complete disasters
	10	Support	The system has the ability to provide online software documentation for all software application features.
	11	Support	The system has the ability to provide an online tutorial to assist users learning the software.
	12	Support	The system must have the capability to provide support through remote access to the application in accordance with City procedures, if applicable.
	13	Support	The vendor offers software application support during planned upgrades outside of typical operating hours, as requested by the City, if applicable.
	14	Support	The system has the ability to provide functional online help documentation for system end users
	15	Support	The system has the ability to provide technical online help documentation for City system administrators.
	16	Training	The vendor offers a suite of role-based online training features. The materials are updated as the solution is modified or improved.
	17	Training	The vendor offers periodic live webinar training sessions at no cost.
	18	Training	The vendor offers recorded training sessions to be viewed at no cost.
	19	Training	Provide comprehensive training for all user roles, (e.g., Vendors, City Users, administrators). Provide a description of training including training materials.
	20	Updates	The system has the ability to allow for outage times to be based on a 24x7 basis instead of working hours.
	21	Updates	Proposed maintenance plan includes all updates, upgrades, IT phone and/or remote support. Such updates/upgrades shall be provided at no cost to the City so long as a valid maintenance and support agreement, or if applicable software as a service licensing agreement, is in place.
	22	Updates	Proposal includes the method by which software is updated and how often the vendor plans to update any proposed software, as well as any associated costs for said updates.

File details come from the government source that posted it. Updated Mar 10, 2026.