RFP 25-005 EAMS - Exhibit 10 Compliance Matrix.xlsx
XLSX spreadsheet 116 KB Posted
- Attached to
- Enterprise Asset Management Software
- Solicitation number
- S-KS2410-00013228
- Issued by
- Marion County, Oregon
About this file
The document is a Compliance Matrix (Exhibit 10) for RFP 25-005 from the Salem Area Mass Transit District (SAMTD) for an Enterprise Asset Management Software (EAM) procurement. The matrix provides a structured template for vendors to respond to specific software requirements using a standardized legend that includes response categories such as "Supported Natively" (SUP), "Supported with 3rd Party Software" (3RD), "Potential Support through Customization" (CST), "Not Supported" (NS), and "Roadmap" (RDMP) for future development.
The compliance matrix is designed to allow respondents to indicate their solution's capabilities against specific enterprise asset management requirements by marking the most appropriate selection for each requirement. Vendors are instructed to complete the worksheet by entering an "X" in the appropriate column, exclude entries for shaded rows, and optionally provide brief explanatory notes. The document emphasizes that links to external websites or reference materials will not be reviewed, focusing instead on direct, concise responses within the matrix itself.
View the file
Other files
Show all 20
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
Instructions & Legend
| Respondant Name: (Enter Below) |
| (Respondent) |
| Instructions: |
| Respondents are asked to complete the worksheet by entered an "X" to indicate their most appropriate selection for each requirement based on the legend provided below. Exclude entries for shaded rows. |
Notes section may be used to provide brief explanations, however, links to external websites or reference material will not be reviewed.
| Legend | Code | Definition |
| Supported Natively | SUP | The demonstrable solution can satisfy the specified requirement with only minor configuration changes within the product. |
| Supported with 3rd Party Software | 3RD | The demonstrable solution can satisfy the specified requirement through a partnership between the vendor submitting the proposal and a 3rd party subcontractor. |
| Potential Support through Customization | CST | The specified requirement can be satisfied through the development of additional functionality. |
| Not Supported | NS | The specified requirement cannot be satisfied. |
| Roadmap | RDMP | Requirement is on Proposer roadmap for future development or release |
EAMS
| Exhibit 10 - Compliance Matrix | |||||||||||||||
| SALEM AREA MASS TRANSIT DISRICT (SAMTD) RFP 25-005 Enterprise Asset Management Software (EAM) | |||||||||||||||
| Enterprise Asset Management | Required or Desired | Rating Response | Configuration / Customization Complexity (indicate with 'X') | ||||||||||||
| Requirement # | Requirement Description | Priority | SUP | 3RD | CST | NS | RDMP | Notes/Explanation - Links Not To Be Reviewed - <500 Characters | High | Medium | Low | None | Format | Counter | Req# |
| 1. Preventive Maintenance | 1 | 0 | 0 | ||||||||||||
| EAM-1 | a. Forecast preventative maintenance scheduling as well as review, modify and print the forecasted schedules. | Required | 1 | 1 | |||||||||||
| EAM-2 | b. Create, add, subtract and modify tasks associated to the preventive maintenance cycle as well as link and unlink maintenance tasks. | Required | 1 | 2 | |||||||||||
| EAM-3 | c. Create work orders and/or tasks for a group of assets or a type of assets. For example, agency may run a maintenance campaign to replace brake components on all buses of a certain make/model. | Required | 1 | 3 | |||||||||||
| EAM-4 | d. Provide for, at minimum, the management of spare parts, tools, and other materials (separately) including the forecast of materials. | Required | 1 | 4 | |||||||||||
| EAM-5 | e. Create preventive maintenance plans for a variety of schedules, such as by date, by mileage or by a specific calendar date. For example, some cycles are 28 days and will fall on a different calendar date each month. | Required | 1 | 5 | |||||||||||
| EAM-6 | f. Create preventive maintenance cycles for a piece of equipment and be able to add to, subtract from, delete, or combine cycles as needed. | Required | 1 | 6 | |||||||||||
| EAM-7 | g. Preventative Maintenance cycles shall have the ability to be hierarchical. For example, the 100,000 mile cycle could include all of the 50,000 mile tasks, and the 50,000 mile cycle could include all of the 12,000 mile tasks. The cycle for Cherriots will be based upon a 6,000 mile interval. | Required | 1 | 7 | |||||||||||
| EAM-8 | h. Flexibility to have preventive maintenance schedules based on previously completed preventative maintenance tasks performed, as well as a previous scheduled date. | Required | 1 | 8 | |||||||||||
| EAM-9 | i. Have a 'Master' tab for each vehicle that includes vehicle data and notes for major vehicle milestones. | Required | 1 | 9 | |||||||||||
| EAM-10 | j. Provide an intuitive, user friendly, interface that minimizes user clicks and navigation to complete tasks. | Required | 1 | 10 | |||||||||||
| 2. General Work Order Requirements | 1 | 0 | 10 | ||||||||||||
| EAM-11 | a. Create work orders for repair, inspections, and other purposes as the business needs require. | Required | 1 | 11 | |||||||||||
| EAM-12 | b. Allow multiple open work orders on the same asset, which may be in various phases of completion. | Required | 1 | 12 | |||||||||||
| EAM-13 | c. Create work orders with multiple tasks and add tasks to the same work order. | Required | 1 | 13 | |||||||||||
| EAM-14 | d. Allow work orders to be related to other work orders and grouped as needed. | Required | 1 | 14 | |||||||||||
| EAM-15 | e. Generate a work order as a result of a problem found during a preventative maintenance or inspection and link the preventive maintenance or inspection and the repair work orders. | Desired | 1 | 15 | |||||||||||
| EAM-16 | f. Create a set of standard templates for all work order types within the system. Agency must be able to modify these templates as new situations require. | Desired | 1 | 16 | |||||||||||
| EAM-17 | g. Track any type of event and manage follow up activities. For examples, accidents, emissions, and spills. | Desired | 1 | 17 | |||||||||||
| EAM-18 | h. Relate costs, allocate and reserve parts and material to work orders. For example, when work has been performed on an asset, the user should be able to view the work performed as well as the costs related to the work (including equipment, labor, and materials). | Desired | 1 | 18 | |||||||||||
| EAM-19 | i. Track various phases of a work order. For example, on completion of work the status may change to automatically invoke approval from a supervisor prior to the work order being deemed closed and therefore not allowing any further processing to the work order. | Required | 1 | 19 | |||||||||||
| EAM-20 | j. Allow documents attached to work orders be searchable. If the documentation is an image or contains images, that the tag be searchable. | Required | 1 | 20 | |||||||||||
| EAM-21 | k. List required parts (Bill of Material) needed to complete a work order. | Desired | 1 | 21 | |||||||||||
| EAM-22 | l. List on the work order, the most recent time the asset was worked on, when a new repair work order is created. | Required | 1 | 22 | |||||||||||
| EAM-23 | m. List current cumulative mileage and/or hours on work orders for any equipment that has mileage and/or hours readings at time of work order creation. | Required | 1 | 23 | |||||||||||
| EAM-24 | n. End users will be able to dynamically schedule work to employees by user parameters such as hours, dates, geographic location, equipment number, maintenance type, part availability, and others available within the system. | Required | 1 | 24 | |||||||||||
| EAM-25 | o. Split line item costs across multiple accounts on a work order. | Required | 1 | 25 | |||||||||||
| EAM-26 | p. Have a log file showing the history of work order status changes | Required | 1 | 26 | |||||||||||
| EAM-27 | q. Each technician will be able to clearly document each step of work completed on each work order and include comments and notes | Required | 1 | 27 | |||||||||||
| EAM-28 | r. Generate, modify, or complete work orders and other transactions in the field via handheld devices. | Required | 1 | 28 | |||||||||||
| 3. Inspections | 1 | 0 | 28 | ||||||||||||
| EAM-29 | a. Each inspection record must be signed or electronically coded by the employee making the test. | Required | 1 | 29 | |||||||||||
| EAM-30 | b. Create, monitor and report on vehicle and component condition. Measurement tolerances and other parameters would be entered in a standard job or a preventative maintenance task, and then qualified as pass or fail. | Required | 1 | 30 | |||||||||||
| EAM-31 | c. Perform event-based maintenance. Examples include detection of a fault during an inspection, accident, or other cause. | Required | 1 | 31 | |||||||||||
| EAM-32 | d. Vehicle inspection results are assigned a numeric rating as part of the asset condition monitoring. The rating must be user-configurable in order to remain compliant with either the FTA’s 5-point or 10-point TERM (Transit Economic Requirements Model) ratings schedule. | Required | 1 | 32 | |||||||||||
| EAM-33 | e. Approvals/rejections for vehicle inspections and other transactions to be locked down once made. | Required | 1 | 33 | |||||||||||
| EAM-34 | f. Perform condition monitoring for items such as oil samples and to import data from a third party system. | Required | 1 | 34 | |||||||||||
| 4. Warranty | 1 | 0 | 34 | ||||||||||||
| EAM-35 | a. Notify a group when equipment is due for warranty work. Agency requires this for warranties. However, we reserve the option to extend this requirement to any type of work. | Required | 1 | 35 | |||||||||||
| EAM-36 | b. Segregate costs associated with warranty management (labor, stock items, services, etc.) for a detailed understanding of warranty claims. | Required | 1 | 36 | |||||||||||
| EAM-37 | c. Track warranty status of any item. | Required | 1 | 37 | |||||||||||
| EAM-38 | d. Warranty program will record and track multiple warranties on a single asset, summarize, and create reports. | Required | 1 | 38 | |||||||||||
| EAM-39 | e. Capability to differentiate between warranty types. | Required | 1 | 39 | |||||||||||
| EAM-40 | f. Track and monitor warranty claims including creating data and reporting to notify the vendor. | Required | 1 | 40 | |||||||||||
| EAM-41 | g. Notify designated user(s) in advance that an item (part or component/sub-system) is nearing an expiration date (shelf-life) prior to creating a work order. | Required | 1 | 41 | |||||||||||
| EAM-42 | h. Notify designated user(s) in advance that an item (part or supply) is reaching the warranty expiration date. | Required | 1 | 42 | |||||||||||
| 5. Asset/Equipment Management | 1 | 0 | 42 | ||||||||||||
| EAM-43 | a. Track equipment and tool calibration records. | Required | 1 | 43 | |||||||||||
| EAM-44 | b. Inspection records will show the name of the service, location, date, equipment tested, results of tests, repairs, replacements, adjustments made, Cherriots inventory number, and condition. | Required | 1 | 44 | |||||||||||
| EAM-45 | c. Provide real time vehicle and equipment availability. | Required | 1 | 45 | |||||||||||
| EAM-46 | d. Track linear equipment work orders and expected life. | Required | 1 | 46 | |||||||||||
| EAM-47 | e. Track serialized component repair work orders and provide historic asset associations. | Required | 1 | 47 | |||||||||||
| EAM-48 | f. Assign a distinct reason code for equipment (and vehicle) failure which can be used for trend analysis and part consumption. | Required | 1 | 48 | |||||||||||
| EAM-49 | g. Monitor equipment and component failures and warranties, identifying the number of occurrences, causes of failures and associated costs. | Required | 1 | 49 | |||||||||||
| EAM-50 | h. Include the decay modeling from the TERM-Lite database, created by the FTA, and be able to perform the necessary calculations to depreciate assets over time. For example, if an asset has an expected life of 15 years, and is 5 years old; the asset should be expected to have 10 years of remaining use. The TERM Lite model can be found at: http://www.fta.dot.gov/13248_13251.html | Desired | 1 | 50 | |||||||||||
| EAM-51 | i. Calculate and identify high-risk assets or areas within the transit system based on the scoring of select parameters including, but not limited to: condition assessments, importance to the overall network, Transit Economic Requirements Model (TERM) score. | Desired | 1 | 51 | |||||||||||
| EAM-52 | j. Allow attachment of any format (.pdf, .docx, .jpg, etc.) of instructions, diagrams, drawings, parts lists, photos, or any outside source of documentation that can be linked to template types within the asset management system. The diagrams and drawings can be available via scanned documents, a hyperlink, or the ability to attach to a standard set of work instructions. | Required | 1 | 52 | |||||||||||
| EAM-53 | k. Calculate total cost of ownership for assets under management and provide reports. | Required | 1 | 53 | |||||||||||
| EAM-54 | l. Track all fluids used in the maintenance process and be able to associate them to individual assets/vehicles. | Required | 1 | 54 | |||||||||||
| EAM-55 | m. Track tire usage utilizing a unique tire number. The tracking will be able to report tire position, lifetime mileage per tire and usage history. | Required | 1 | 55 | |||||||||||
| 6. Timekeeping and Labor Tracking | 1 | 0 | 55 | ||||||||||||
| EAM-56 | a. Allow labor entry related to the work order by employee number and cost those transactions. | Required | 1 | 56 | |||||||||||
| EAM-57 | b. Utilize standard labor hours and rates for planning (setting up standard jobs, benchmarked hours). | Required | 1 | 57 | |||||||||||
| EAM-58 | c. Capture assigned and unassigned time, or direct or indirect labor, and track productivity. | Required | 1 | 58 | |||||||||||
| 7. Parts Ordering | 1 | 0 | 58 | ||||||||||||
| EAM-59 | a. Provide complete vendor listing including the ability to track minority business types. | Desired | 1 | 59 | |||||||||||
| EAM-60 | b. Generate purchase orders and a receiver simultaneously | Required | 1 | 60 | |||||||||||
| EAM-61 | c. Receive ordered parts and hold the receiver open until the shipment is complete. | Required | 1 | 61 | |||||||||||
| EAM-62 | d. Enter different part due dates per line item and actually print on the PO and receiver. Currently, dates can be entered, but don’t print. Comments/notes do print. | Required | 1 | 62 | |||||||||||
| EAM-63 | e. Provide staff the ability to enter comments, notes, and vehicle info. | Required | 1 | 63 | |||||||||||
| EAM-64 | f. Configured to use every Unit Of Measurement and conversions tailor it to each vendor. | Required | 1 | 64 | |||||||||||
| EAM-65 | g. Make immediate price changes to a part number and have it retain in the system. | Required | 1 | 65 | |||||||||||
| EAM-66 | h. Run reports on past due PO’s. | Required | 1 | 66 | |||||||||||
| EAM-67 | i. Search/lookup a part number in any order and pull up information. | Desired | 1 | 67 | |||||||||||
| EAM-68 | j. Provide for old and new vendor part numbers after creation of an internal part number. | Required | 1 | 68 | |||||||||||
| EAM-69 | k. Create an assembly/kit part number that contains several parts. We would need to be able to return a part back to inventory that wasn’t needed. | Required | 1 | 69 | |||||||||||
| EAM-70 | l. PO’s must not have a “dash” and followed by more numbers. E.g. 24009, 24010 instead of 24-009 or 24-010. | Desired | 1 | 70 | |||||||||||
| EAM-71 | m. Efficient way to receive parts. | Required | 1 | 71 | |||||||||||
| EAM-72 | n. Ability to print part numbers on a self-adhesive label, with the bar code capabilities. | Desired | 1 | 72 | |||||||||||
| EAM-73 | p. Provide total fuel purchased and total fuel cost for any given time period. | Required | 1 | 73 | |||||||||||
| EAM-74 | q. When new tires are purchased, Solution will assign to each tire on the list, their in-common descriptors (tire size, tread depth, date received, etc.). | Required | 1 | 74 | |||||||||||
| 8. Additional Reporting | 1 | 0 | 74 | ||||||||||||
| EAM-75 | a. Forecast likely asset failure points. | Desired | 1 | 75 | |||||||||||
| EAM-76 | b. Perform ad-hoc queries and run ad-hoc reports on all data available within the enterprise asset management system. Work orders shall be searchable by keyword, part number and labor code. | Required | 1 | 76 | |||||||||||
| EAM-77 | c. Generate reports on user selected criteria from data available to the asset management system. For example, Preventative Maintenance Due report based on user selected criteria (60 day, or 7500 mile, by department, class, location, date, type, age, etc.). | Required | 1 | 77 | |||||||||||
| EAM-78 | f. Fuels and consumables integrated from Fuel Force must be deducted from inventory. Mileage updated from Fuel Force and will automatically update Life To Date (LTD) mileage and Preventative Mileage (PM) forecasting reports. | Required | 1 | 78 | |||||||||||
| EAM-79 | g. Place equipment, parts, vehicles, labor codes and employees readily in either an 'active' or 'inactive' category. Inactive listings will not be shown in regular maintenance query's. | Required | 1 | 79 | |||||||||||
| EAM-80 | i. Report fuel used and cost of that fuel for a list of vehicles for any time period. | Required | 1 | 80 | |||||||||||
| EAM-81 | j. Create a list of active vehicles and their Life To Date (LTD) mileage for any given date. | Required | 1 | 81 | |||||||||||
| EAM-82 | k. Migrate existing historical data from the current maintenance software to include vehicle history, parts inventory, labor and asset management. | Required | 1 | 82 | |||||||||||
| EAM-83 | l. Provide out-of-box reporting tools that satisfy the needs of various users such as executives and managers, business analysts, finance, claims, underwriting, marketing, etc. | Required | 1 | 83 | |||||||||||
| EAM-84 | m. Ability to generate aging reports. | Desired | 1 | 84 | |||||||||||
| EAM-85 | n. Configure built-in reports to SAMTD needs and specifications. | Required | 1 | 85 | |||||||||||
| EAM-86 | o. Reporting functionality integrates with the other system modules. | Required | 1 | 86 | |||||||||||
| 9. System Security | 1 | 0 | 86 | ||||||||||||
| EAM-89 | a. Capability to encrypt both "data in flight" and "data at rest." | Required | |||||||||||||
| EAM-90 | b. Capability to provide Single Sign-On (SSO). Describe how the user is authenticated and authorized, user role and permissions. Is multi factor authentication an option? | Required | |||||||||||||
| EAM-91 | c. Capability to track all changes, deletions, and additions, whether initiated by a user or by the system. The result must be a configurable, detailed transaction audit log that records at minimum the user, date, time, and the change that was made. | Required | |||||||||||||
| EAM-92 | d. Create and maintain an unlimited number of user levels/roles. | Required | |||||||||||||
| EAM-93 | e. Flexibility for administrators to title and enable user levels. | Required | |||||||||||||
| EAM-94 | f. Control areas where the user is able to view and the functions to which they have access. | Desired | |||||||||||||
| EAM-95 | g. Role administration to delegate the limited assignment of user roles/authority within defined parameters. | Desired | |||||||||||||
| EAM-96 | h. Access management controls are granular when necessary, but also provide for standard pre-configured roles. | Desired | |||||||||||||
| EAM-97 | i. Unauthorized users cannot obtain additional privileges within the application without Administrator permission. | Required | |||||||||||||
| EAM-98 | j. Protection against unauthorized access. | Required | |||||||||||||
| 10. Integration and Support | 1 | 0 | 86 | ||||||||||||
| EAM-99 | a. Flexibility to accommodate bidirectional synchronization between external data sources. | Desired | |||||||||||||
| EAM-100 | b. Capable of integrating with Fuel Force as a means to update mileage, fuel and fluid dispensing. | Required | 1 | 87 | |||||||||||
| EAM-101 | c. Capable of integrating with Tyler Munis for purposes of calculating fully burdened employee costs in order to accurately reflect individual repair costs. | Required | 1 | 88 | |||||||||||
| 11. Options | 1 | 0 | 88 | ||||||||||||
| EAM-102 | a. Utilize Telematics functionality to notify management teams of error codes and potential issues as flag by vehicles of on board monitoring systems where available. | Desired | |||||||||||||
| EAM-103 | b. Allow addition of remote workstations via tablets or other wireless device for mobile work stations | Desired | |||||||||||||
| EAM-104 | c. Permit use of a bar code scanner that can be used for work orders and parts. | Desired | |||||||||||||
| EAM-105 | d. Allow access from smart phones such as iPhone and Android | Desired | |||||||||||||
| 12. Database/Data Management | |||||||||||||||
| EAM-106 | a. Audit details must be able to be captured when data in the database is created, queried, changed, updated or deleted based upon configurable parameters. This audit capability must allow for compliance with ORC 1347.15. Describe how this capability will be implemented. | Required | |||||||||||||
| EAM-107 | b. Allow for bulk data load and extract capability | Desired | |||||||||||||
| EAM-108 | c. Provide for high-availability operation. The acceptable level of uptime performance for this software will be between 99.5% and 99.79% of the time each calendar month, measured on a 7 x 24 basis (7 days a week, 24 hours per day). | Required | |||||||||||||
| EAM-109 | d. Provide near real-time access to all data from any module. Describe how this capability is achieved. | Required | |||||||||||||
| 13 Performance and Scalability | |||||||||||||||
| EAM-110 | a. Capability of ninety-five percent (95%) of all transactions shall process at no more than one (1) second; no single transaction shall take longer than five (5) seconds to process. Provide any available independent testing results (including number of CPUs, disk space, memory, transaction size, peak number of transactions, concurrent users, and volume of data) | Required | |||||||||||||
| EAM-111 | b. Provide failover and redundancy capabilities to prevent downtime. | Required | |||||||||||||
| 14. Application Configuration | |||||||||||||||
| EAM-112 | a. Utilize a common user interface across all modules | Required | |||||||||||||
| EAM-113 | b. Trigger business processes as the result of a user-defined event. The business process could be logic that completes multiple steps such as creating work orders and recording warranty processes | Desired | |||||||||||||
| EAM-114 | c. Produce and distribute documents like work orders, inventory reports, etc. | Required | |||||||||||||
| EAM-115 | d. Support configuration to add new objects (or entities) and new fields (attributes) to new or existing objects | Desired | |||||||||||||
| EAM-116 | e. Allow administrators to "turn off" via configuration unwanted data objects, attributes and functionality. How are the fields removed? Is it removed just on the screen or from the database as well? | Desired | |||||||||||||
| EAM-117 | f. Allow customizable user help functions | Desired | |||||||||||||
| 15 Application Customization | |||||||||||||||
| EAM-118 | a. Identify customizations from base product, and retain customizations during upgrades | Required |
Sheet2
| 1 | I | i | i. | i. |
| 2 | II | ii | ii. | ii. |
| 3 | III | iii | iii. | iii. |
| 4 | IV | iv | iv. | iv. |
| 5 | V | v | v. | v. |
| 6 | VI | vi | vi. | vi. |
| 7 | VII | vii | vii. | vii. |
| 8 | VIII | viii | viii. | viii. |
| 9 | IX | ix | ix. | ix. |
| 10 | X | x | x. | x. |
| 11 | XI | xi | xi. | xi. |
| 12 | XII | xii | xii. | xii. |
| 13 | XIII | xiii | xiii. | xiii. |
| 14 | XIV | xiv | xiv. | xiv. |
| 15 | XV | xv | xv. | xv. |
| 16 | XVI | xvi | xvi. | xvi. |
| 17 | XVII | xvii | xvii. | xvii. |
| 18 | XVIII | xviii | xviii. | xviii. |
| 19 | XIX | xix | xix. | xix. |
| 20 | XX | xx | xx. | xx. |
| 21 | XXI | xxi | xxi. | xxi. |
| 22 | XXII | xxii | xxii. | xxii. |
| 23 | XXIII | xxiii | xxiii. | |
| 24 | XXIV | xxiv | xxiv. | |
| 25 | XXV | xxv | xxv. | |
| 26 | XXVI | xxvi | xxvi. | |
| 27 | XXVII | xxvii | xxvii. | |
| 28 | XXVIII | xxviii | xxviii. | |
| 29 | XXIX | xxix | xxix. | |
| 30 | XXX | xxx | xxx. | |
| 31 | XXXI | xxxi | xxxi. | |
| 32 | XXXII | xxxii | xxxii. | |
| 33 | XXXIII | xxxiii | xxxiii. | |
| 34 | XXXIV | xxxiv | xxxiv. | |
| 35 | XXXV | xxxv | xxxv. | |
| 36 | XXXVI | xxxvi | xxxvi. | |
| 37 | XXXVII | xxxvii | xxxvii. | |
| 38 | XXXVIII | xxxviii | ||
| 39 | XXXIX | xxxix | ||
| 40 | XL | |||
| 41 | XLI | |||
| 42 | XLII | |||
| 43 | XLIII | |||
| 44 | XLIV | |||
| 45 | XLV |
Ref
| a | a. | The proposed solution provides an on-line Help Function. | a. The proposed solution provides an on-line Help Function. |
| b | b. | The proposed solution have detailed audit tracking, showing field changed and before/after value(s). Also show date/time & userid. | b. The proposed solution have detailed audit tracking, showing field changed and before/after value(s). Also show date/time & userid. |
| c | c. | The proposed solution run on a standard Microsoft Windows desktop platform. | c. The proposed solution run on a standard Microsoft Windows desktop platform. |
| d | d. | The proposed solution supports mobile devices including IOS, Android and/or Windows. | d. The proposed solution supports mobile devices including IOS, Android and/or Windows. |
| e | e. | Please indicate if the solution utilizes a web based presentation layer. | e. Please indicate if the solution utilizes a web based presentation layer. |
| f | f. | Please indicate if the solution utilizes a client/server based presentation layer. | f. Please indicate if the solution utilizes a client/server based presentation layer. |
| g | g. | The database schema is provided and updated as changes are made to the application (over the life of the application). | g. The database schema is provided and updated as changes are made to the application (over the life of the application). |
| h | h. | Third party applications or plugins are identified. Please indicate this information in the notes section. | h. Third party applications or plugins are identified. Please indicate this information in the notes section. |
| i | i. | The solution has the ability to link associated documents to a record. | i. The solution has the ability to link associated documents to a record. |
| j | j. | The solution has the ability to integrate with ESRI ArcGIS suite of software. | j. The solution has the ability to integrate with ESRI ArcGIS suite of software. |
| k | k. | The proposed solution support data-transfer via flat files (e.g., ASCII, variable and/or fixed length, comma-delimited, etc.). | k. The proposed solution support data-transfer via flat files (e.g., ASCII, variable and/or fixed length, comma-delimited, etc.). |
| l | l. | The proposed solution provides a Software Development Kit (SDK) that allows the technical staff to enhance and integrate the system. | l. The proposed solution provides a Software Development Kit (SDK) that allows the technical staff to enhance and integrate the system. |
| m | m. | The proposed solution allow for the definition of default printers for each user. | m. The proposed solution allow for the definition of default printers for each user. |
| n | n. | The proposed solution provide the ability to export to RTF, XML, PDF, HTML, XLS (and XLSX), DOC (and DOCX), etc. | n. The proposed solution provide the ability to export to RTF, XML, PDF, HTML, XLS (and XLSX), DOC (and DOCX), etc. |
| o | o. | The proposed solution support standard Internet security including, but not limited to Secure Socket Layers (SSL). If SSL is not supported, please describe the supported Digital Certificates. | o. The proposed solution support standard Internet security including, but not limited to Secure Socket Layers (SSL). If SSL is not supported, please describe the supported Digital Certificates. |
| p | p. | The proposed solution provide the ability to monitor executing jobs | p. The proposed solution provide the ability to monitor executing jobs |
| q | q. | The proposed solution's on-line help should be updated with each new version release. | q. The proposed solution's on-line help should be updated with each new version release. |
| r | r. | The proposed solution vendor's support site should contain a knowledge base where users can access system related reference material and documents. | r. The proposed solution vendor's support site should contain a knowledge base where users can access system related reference material and documents. |
| s | s. | The proposed solution vendor's support site should contain complete and up-to-date manuals for all system modules and functionalities. The manuals should be available for all available versions of the software. | s. The proposed solution vendor's support site should contain complete and up-to-date manuals for all system modules and functionalities. The manuals should be available for all available versions of the software. |
| t | t. | The proposed solution vendor's support site should contain a complete data dictionary for all system tables and data fields. | t. The proposed solution vendor's support site should contain a complete data dictionary for all system tables and data fields. |
| u | u. | The proposed solution provide the ability to AutoFill based on a related field (i.e. auto completion of one field based on prior data entry). | u. The proposed solution provide the ability to AutoFill based on a related field (i.e. auto completion of one field based on prior data entry). |
| v | v. | The proposed solution provide the capability to store, retrieve, display and print imaged documents. The solution must provide the capability to receive scanned documents from document scanners having industry-standard connection protocols (SCI, TCP/IP, etc.) | v. The proposed solution provide the capability to store, retrieve, display and print imaged documents. The solution must provide the capability to receive scanned documents from document scanners having industry-standard connection protocols (SCI, TCP/IP, etc.) |
| w | w. | w. | |
| x | x. | x. | |
| y | y. | y. | |
| z | z. | z. | |
| aa | aa. | aa. | |
| bb | bb. | bb. | |
| cc | cc. | cc. | |
| dd | dd. | dd. | |
| ee | ee. | ee. | |
| ff | ff. | ff. | |
| gg | gg. | gg. | |
| hh | hh. | hh. | |
| ii | ii. | ii. | |
| jj | jj. | jj. | |
| kk | kk. | kk. | |
| ll | ll. | ll. | |
| mm | mm. | mm. | |
| nn | nn. | nn. | |
| oo | oo. | oo. | |
| pp | pp. | pp. | |
| qq. | qq. | ||
| rr | rr. | rr. |
| The proposed solution provides an on-line Help Function. | a. The proposed solution provides an on-line Help Function. |
| The proposed solution have detailed audit tracking, showing field changed and before/after value(s). Also show date/time & userid. | b. The proposed solution have detailed audit tracking, showing field changed and before/after value(s). Also show date/time & userid. |
| The proposed solution run on a standard Microsoft Windows desktop platform. | c. The proposed solution run on a standard Microsoft Windows desktop platform. |
| The proposed solution supports mobile devices including IOS, Android and/or Windows. | d. The proposed solution supports mobile devices including IOS, Android and/or Windows. |
| Please indicate if the solution utilizes a web based presentation layer. | e. Please indicate if the solution utilizes a web based presentation layer. |
| Please indicate if the solution utilizes a client/server based presentation layer. | f. Please indicate if the solution utilizes a client/server based presentation layer. |
| The database schema is provided and updated as changes are made to the application (over the life of the application). | h. The database schema is provided and updated as changes are made to the application (over the life of the application). |
| Third party applications or plugins are identified. Please indicate this information in the notes section. | i. Third party applications or plugins are identified. Please indicate this information in the notes section. |
| The solution has the ability to link associated documents to a record. | j. The solution has the ability to link associated documents to a record. |
| The solution has the ability to integrate with ESRI ArcGIS suite of software. | k. The solution has the ability to integrate with ESRI ArcGIS suite of software. |
| The proposed solution support data-transfer via flat files (e.g., ASCII, variable and/or fixed length, comma-delimited, etc.). | l. The proposed solution support data-transfer via flat files (e.g., ASCII, variable and/or fixed length, comma-delimited, etc.). |
| The proposed solution provides a Software Development Kit (SDK) that allows the technical staff to enhance and integrate the system. | m. The proposed solution provides a Software Development Kit (SDK) that allows the technical staff to enhance and integrate the system. |
| The proposed solution allow for the definition of default printers for each user. | n. The proposed solution allow for the definition of default printers for each user. |
| The proposed solution provide the ability to export to RTF, XML, PDF, HTML, XLS (and XLSX), DOC (and DOCX), etc. | o. The proposed solution provide the ability to export to RTF, XML, PDF, HTML, XLS (and XLSX), DOC (and DOCX), etc. |
| The proposed solution support standard Internet security including, but not limited to Secure Socket Layers (SSL). If SSL is not supported, please describe the supported Digital Certificates. | p. The proposed solution support standard Internet security including, but not limited to Secure Socket Layers (SSL). If SSL is not supported, please describe the supported Digital Certificates. |
| The proposed solution provide the ability to monitor executing jobs | q. The proposed solution provide the ability to monitor executing jobs |
| The proposed solution's on-line help should be updated with each new version release. | r. The proposed solution's on-line help should be updated with each new version release. |
| The proposed solution vendor's support site should contain a knowledge base where users can access system related reference material and documents. | s. The proposed solution vendor's support site should contain a knowledge base where users can access system related reference material and documents. |
| The proposed solution vendor's support site should contain complete and up-to-date manuals for all system modules and functionalities. The manuals should be available for all available versions of the software. | t. The proposed solution vendor's support site should contain complete and up-to-date manuals for all system modules and functionalities. The manuals should be available for all available versions of the software. |
| The proposed solution vendor's support site should contain a complete data dictionary for all system tables and data fields. | u. The proposed solution vendor's support site should contain a complete data dictionary for all system tables and data fields. |
| The proposed solution provide the ability to AutoFill based on a related field (i.e. auto completion of one field based on prior data entry). | v. The proposed solution provide the ability to AutoFill based on a related field (i.e. auto completion of one field based on prior data entry). |
| The proposed solution provide the capability to store, retrieve, display and print imaged documents. The solution must provide the capability to receive scanned documents from document scanners having industry-standard connection protocols (SCI, TCP/IP, etc.) | w. The proposed solution provide the capability to store, retrieve, display and print imaged documents. The solution must provide the capability to receive scanned documents from document scanners having industry-standard connection protocols (SCI, TCP/IP, etc.) |
File details come from the government source that posted it. Updated .