Attachment Functional and Technical Requirements “B” – The City of Cleveland’s functional and technical requirements for the Project are listed in this ATTACHMENT. The Vendor must respond to each of the requirements by placing an in the column of the appropriate response (see table below for response code “X” definitions). For any requirement without a response, the City will assume the Vendor cannot provide the functionality. Response Code Definition Y Yes Requirement can be implemented of box” without customizations or modifications to the existing application – “out N No Requirement will not be implemented – Cu Customization Requirement can be met by changing existing software or through use of software tools (NOTE: In Comments column, describe the – customization and the estimated level of complexity High, Medium, or Low) – F Future Requirement will be met by packaged software currently under development, in Beta test, or not yet released (NOTE: In Comments column, – indicate expected release date and any anticipated additional cost) Requirement will be met by 3rd party software package that is included in this proposal (NOTE: In Comments column, indicate name of 3 3rd Party – proposed 3rd party software package and proposed interface/integration services) Co Configuration Requirement can be met through changes to setting of tables, switches and rules without modification to source code (NOTE: In Comments, – describe any changes to of box” workflow functionality) “out City of Cleveland Requirements for Automatic Vehicle Locator System Response to Requirement # Requirement Comments Y N Cu F 3 Co Functional Requirements The AVL system shall be a web-based application capable of being 1 viewed on a desktop or tablet device If a mobile app is available proposers should include information about the functionality, features and limitations
Attachment “B” – Functional and Technical Requirements The City of Cleveland’s functional and technical requirements for the Project are listed in this ATTACHMENT. The Vendor must respond to each of the requirements by placing an “X” in the column of the appropriate response (see table below for response code definitions). For any requirement without a response, the City will assume the Vendor cannot provide the functionality. Response Code Definition Y – Yes Requirement can be implemented “out of box” without customizations or modifications to the existing application N – No Requirement will not be implemented Cu – Customization Requirement can be met by changing existing software or through use of software tools (NOTE: In Comments column, describe the customization and the estimated level of complexity – High, Medium, or Low) F – Future Requirement will be met by packaged software currently under development, in Beta test, or not yet released (NOTE: In Comments column, indicate expected release date and any anticipated additional cost) 3 – 3rd Party Requirement will be met by 3rd party software package that is included in this proposal (NOTE: In Comments column, indicate name of proposed 3rd party software package and proposed interface/integration services) Co – Configuration Requirement can be met through changes to setting of tables, switches and rules without modification to source code (NOTE: In Comments, describe any changes to “out of box” workflow functionality) City of Cleveland Requirements for Automatic Vehicle Locator System # Requirement Response to Requirement Comments Y N Cu F 3 Co Functional Requirements 1 The AVL system shall be a web-based application capable of being viewed on a desktop or tablet device If a mobile app is available proposers should include information about the functionality, features and limitations
AutomatedVehicleLocatorSystemAttachmentB.docx