CostWorksheet_DPS.xls
XLS spreadsheet 42 KB Posted
- Attached to
- E-Licensing
- Solicitation number
- S116333-vCurrent
- Issued by
- Middlesex County, Suffolk County, Boston City, Chelsea City, Massachusetts
About this file
This document contains a cost worksheet for a Licensing and Inspections System for the Massachusetts Department of Public Safety (DPS) and Department of Fire Services (DFS). The system must include a Licensing Module, Inspection Module, Public Website, Document Imaging and Management, Payments and Invoicing, Administrative Interface, and other required components. The system must integrate with existing databases and external interfaces. The bid requires conversion of existing license data, provision of hardware and operating systems, and a maintenance and support program. Respondents must provide a detailed training program. The bid specifies separate databases for each agency, installation at the Public Safety Data Center, and a delivery timeline by June 30, 2009 for any hardware purchased in the current fiscal year.
The cost worksheet requires pricing for a bundled enterprise system and itemized components that can be purchased individually. Pricing should indicate if items are included in the standard package, available as add-ons, or require customization. The bid reserves the right to select any or all of the license types or databases to integrate into the system, based on available funding.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 2009_05_12_DPSELICENSEFY09RFR_EvaluationCriteria_AwardInfo.docx | DOCX document | |
| S116333-vCurrent_OD.xlsx | XLSX spreadsheet | |
| eft_form.doc | DOC document | |
| ProcurementCalendar_DPS.doc | DOC document | |
| po.doc | DOC document | |
| standard_contract_frm.doc | DOC document | |
| LicensingRFR_DPS.doc | DOC document | |
| w9.doc | DOC document | |
| LicenseList_DPS.xls | XLS spreadsheet | |
| Questions_Answers_Forum.xls | XLS spreadsheet | |
| ampplanform.doc | DOC document | |
| consig.doc | DOC document | |
| consltfm.doc | DOC document | |
| ctc.doc | DOC document |
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
Sheet1
| DPS/DFS Licensing System | |||||
| Vendor Cost Sheet | |||||
| Price the cost of the system as an all inclusive enterprise system AND as itemized components that can be purchased a la carte. For the bundled Enterprise system, please check off any items in the Deliverable list which are included in the bundled price. For the itemized deliverables, please list if the price is included in the standard package; is an add-on that can be purchased seperatel; or is an item requiring customization. If customization is required, please list hours and hourly rate. | |||||
| Included in Bundled Enterprise System | Per User | Per License Type | Included in Standard Package or Purchased as add-on | Customization Required | |
| Bundled System | |||||
| Please Check off what the bundled system includes and add other items | |||||
| Deliverable 1: Licensing & Inspections System | |||||
| Licensing Module: | |||||
| a. Manage Applications intake process | |||||
| b. Manage Renewal process | |||||
| c. Names: current, prior, and maintain history | |||||
| d. Addresses: current, prior, and maintain history | |||||
| e. Robust search capabilities | |||||
| f. Maintains application history | |||||
| g. Records Continuing Education information | |||||
| h. Records criminal background check results | |||||
| i. Records results of any pre-inspection needed for license issuance | |||||
| j. Records exam results | |||||
| k. Integrates with 3rd party testing services via internet | |||||
| l. Ability to assign application status | |||||
| m. Ability to set unique fees for each license type & Renewal | |||||
| n. Ability to link one-to-many relationships between objects in database | |||||
| o. Automated workflow | |||||
| p. Drop-down tables and type-ahead for data validation | |||||
| q. Some quantity of blank user-customizable fields | |||||
| r. Ability for user or administrator to add new Master License and new license types | |||||
| s. Document imaging functionality | |||||
| t. Ability to store .jpg images | |||||
| u. Ability to import photos via ‘cut and paste’ for ex: Registry of Motor Vehicles Photo. | |||||
| v. Data searching, mining and analysis | |||||
| w. Data reporting (management, performance, statistical) | |||||
| x. Active alerting based on pre-defined conditions | |||||
| 3. License Printing: | |||||
| a. License cards requiring a picture will be printed on a Datacard CP70 | |||||
| b. Printing on-demand & Batch | |||||
| c. Printing card-stock certificate | |||||
| d. User Defined Fields to appear on each printed license | |||||
| 4. Inspection Module: | |||||
| a. Inspections can be created independent of licenses. | |||||
| b. Ability to link inspection to existing database objects | |||||
| c. Inspection functionality intranet users and mobile device internet users | |||||
| d. User-defined triggers for launching an inspection | |||||
| e. The system must have functionality to allow inspectors to self-schedule inspections | |||||
| f. Inspection scheduling with 3rd party inspectors and licensees via intranet & internet. | |||||
| g. Produce summary report of each inspection | |||||
| h. Produce a history of inspections for each entity or object in the system | |||||
| 5. Regulations: Ability to store/create a repository of Regulations | |||||
| a. User updatable, as laws/regs change | |||||
| b. Ability to for user to import templates | |||||
| c. Functionality needed to place the specific violation from repository into enforcement doc | |||||
| 5. Public Website: Must meet Com of MA standards for websites. | |||||
| a. | |||||
| b. Same header and format used by the state portal at http://www.mass.gov/dps | |||||
| c. Secure registration of users to conduct licensing and ePayment. | |||||
| d. The public website should have the ability for the public to view general licensing information about licensees as designated by each agency without requiring a login or special access | |||||
| e. The license holder should have a login in and password the will allow them to view their own personal information, apply for a new or renewal license, update address information, perform ePayment transactions and print-up copies of certain license or permit documents as allowed by the business rules of each agency | |||||
| f. The 3rd party inspectors should be able to log in and information as designated by the business rules of each agency. | |||||
| g. The data on the public website should be updated promptly by the system | |||||
| 6. Document Imaging & Management – system has ability to integrate with document imaging systems | |||||
| 7. Version Control: For documents, images and data | |||||
| a. Dating system for documents & images on the system | |||||
| b. If data is not live on either intranet or internet, then a data stamp must be present for users to see the ‘age’ of the data | |||||
| 8. External Interfaces: | |||||
| a. Must be able to link to other databases via ODBC | |||||
| b. Credit Card processing via ePayment | |||||
| c. Bank Lockbox services | |||||
| 9. Payments and Invoices: | |||||
| a. Credit Card processing via ePayment | |||||
| b. Manual entry of payments | |||||
| c. Ability to process refunds, bounced checks and other problem payments | |||||
| d. Ability to process one payment for multiple licenses | |||||
| e. Ability to process late fees | |||||
| f. Invoicing feature | |||||
| g. Ability to link payments to budgetary accounts and object codes | |||||
| h. Reporting by accounts and object codes | |||||
| i. Reconciliation retorts built-in and ad hoc | |||||
| 10. Administrative Interface: | |||||
| a. Robust administrative tools | |||||
| b. Allow for the modification of business process rules | |||||
| c. Ability to define or modify workflow | |||||
| d. Ability to define or add customizable fields to screens | |||||
| e. Ability to add new license types to existing Master License Type forms | |||||
| f. Ability to modify relationships between database objects (individual & company licenses, company & complaint, inspection & company etc.) | |||||
| g. Auditing would track administrative changes | |||||
| h. Admin would manage logins | |||||
| 11. Advanced/strong Authentication and password controls | |||||
| a. Locally managed by system administrators | |||||
| b. Self-management for users including username lookup and password reset via e-mail features | |||||
| c. Rights would be set using groups | |||||
| 12. System auditing: | |||||
| a. Ability to reconstruct or roll-back records to a specific date. | |||||
| 13. On-line help system(s): | |||||
| a. Context sensitive on-screen help | |||||
| b. Link back to vendors site for advanced help would be desirable | |||||
| 14. Documentation: Bidders must provide copies of the software package documentation with each response. | |||||
| Desired Features: List cost for customizing system to add these features. | |||||
| 1. Geographical Information Systems | |||||
| a. Ability to integrate with handheld devices (Blackberry Curve) | |||||
| b. Ability to schedule inspections by geographic proximity | |||||
| 2. Data Validation: ability to validate street addresses against external databases | |||||
| 3. Document Imaging: | |||||
| a. Full integration with document imaging systems | |||||
| b. Image and retrieve original license application documents from the licensing screen | |||||
| c. Capability to run batch OCR / ICR processes | |||||
| 15. Reports: | |||||
| a. Third party reporting software can be used | |||||
| b. Ability to add ad hoc reports to menu system | |||||
| 16. External Interfaces | |||||
| a. MMARS – MA State accounting system | |||||
| b. MA GIS System | |||||
| c. 3rd party Insurance Inspections (Hartford/Travelers) | |||||
| Deliverable 2: | |||||
| Turn-key Package Installation: Although this solicitation is seeking a single interface, in order to meet enterprise security mandates: | |||||
| 1. The data for each agency must be stored in separate databases. | |||||
| 2. The installation will be done at the Public Safety Data Center in Chelsea MA | |||||
| 3. Provide a timetable for the installation of the standard turn-key software package. | |||||
| Data Integration & Installation: Conversion of Existing Data. Attached to this solicitation is a list of all the existing license types. Each bidder is required to include in its response: | |||||
| 1. Cost of converting each license by Master License Type | |||||
| 2. Method of conversion | |||||
| 3. Timetable for conversion using business days as the metric | |||||
| Note: DPS/DFS reserves the right to select any or all of the license types or databases to integrate into system. | |||||
| Deliverable 3: | |||||
| Hardware & Operating System | |||||
| 1. Production system | |||||
| 2. Failover system | |||||
| 3. Test system | |||||
| 4. Disaster recovery system | |||||
| 5. Storage | |||||
| Vendor is required to provide a quote for each of these systems. Actual amount of equipment purchased will depend upon available funding. Any hardware purchased in the remainder of this fiscal year must be delivered by June 30, 2009. | |||||
| Deliverable 4: | |||||
| Maintenance and Support program for the systems and services proposed. | |||||
| Deliverable 5: | |||||
| Respondents must provide a detailed training program | |||||
| Other: | |||||
| Add other items included in the bundled system price or other items required to make the system run and the related costs |
Sheet2
Sheet3
File details come from the government source that posted it. Updated .