Posted Date : February 15,2022
Product (RFP/RFQ/RFI/Solicitation/Tender/Bid Etc.) ID : SW-53446
Government Authority located in Ontario; Canada based organization looking for expert vendor for enterprise content management services.
[A] Budget: Looking for Proposals
[B] Scope of Service:
(1) Vendor needs to provide enterprise content management services
- The Enterprise Resource Planning System (ERP) referenced to in this document is Ellucian Colleague Release 18 running on Rocket Software’s Unidata RDBMS. Unidata is employed for both the application layer and the database layer. Microsoft Sequel Server may be employed for the database layer in the near future
- To fit with our current ERP infrastructure, the ECM should be a Windows-based solution
- Document Input:
- The ability to upload documents to the ECM via the web. The web interface should be mobile-friendly so that clients can use their smartphones or tablets to upload documents.
- A mobile application (iOS and Android) would be an asset, unless the web interface is very well refined for mobile use.
- The capability of accepting documents through Web Services.
- The ability to scan paper documents directly into the ECM.
- The ability to perform batch uploads of documents into the ECM.
- The ability to automate batch uploads
- Document Indexing and Organization:
- The capability to index documents should be built into the product.
- The capability to index document metadata.
- The ability to index document revisions.
- The indexing of documents should be customizable.
- Documents should be organized in a standard, well laid-out fashion
- Document Search:
- Documents should be searchable from an intuitive web interface (preferred) or a rich client.
- It would be considered an asset to have an advanced search feature and a basic search feature.
- Both the data and metadata of the documents should be searchable.
- Workflow Automation:
- The ECM should be able to automate the flow of incoming and outgoing documents.
- The ability to perform rules-based processing of the incoming and outgoing documents.
- Document actions should be user-definable.
- Due dates should be customizable in the system
- Workflows should be definable. Delivered workflow templates would be considered an asset.
- The ECM should be able to send out documents to proper signing authorities, whether they be internal or external to the university.
- The ability to obtain multiple signatures from different people for a document
- User Interface (UI) /Dashboard:
- Should be very user-friendly and intuitive – this is critical for user adoption
- As mentioned in the “Document Input” section, it would be preferable for the UI/Dashboard to be web-based using a modern implementation.
- A “workflow inbox” and a “document inbox” should be present on the ECM UI
- An alert and notification system should be built in to send e-mails, pop-ups, or SMS messages.
- There should be a reporting dashboard
- A calendaring system should be integrated to display any upcoming or past due documents or workflows
- ERP Integration:
- ERP integration is vital to the success of an ECM implementation. The solution should have a proven track record working alongside an Ellucian Colleague-based ERP solution with a high adoption rate from institutions using Colleague as an ERP.
- The ECM solution should be able to work integrate with Colleague using Ethos Integration and the Colleague Web API.
- In addition to working well with Ellucian Colleague, the ECM should be fairly ERP agnostic in the case of a transition to a new ERP
- The ability to upload documents to the ECM via the ERP and vice-versa should be present.
- The ability to search for documents in the ECM from the ERP should be present.
- A direct mechanism to update the ERP within workflow automation would be considered a major asset.
- Indirect methods that are simple to create and implement to updating the ERP
- Professional Services Implementation / Support:
- The ECM solution should have an offsite professional services implementation. Onsite implementation services in addition to offsite services would be considered an asset.
- The ECM solution should have an online support portal
- Customer Service representatives should be an option after the professional services implementation has been completed.
(2) All the questions must be submitted no later than February 21, 2022.
[C] Eligibility:
Onshore (Canada organization Only)
[D] Work Performance:
Performance of the work will be Offsite. Vendor needs to carry work in their office premises.
Budget :
Deadline to Submit Proposals: March 07,2022
Cost to Download This RFP/RFQ/RFI/Solicitation/Tender/Bid Document : 5 US$
Product (RFP/RFQ/RFI/Solicitation/Tender/Bid Etc.) ID : SW-53446
Government Authority located in Ontario; Canada based organization looking for expert vendor for enterprise content management services.
[A] Budget: Looking for Proposals
[B] Scope of Service:
(1) Vendor needs to provide enterprise content management services
- The Enterprise Resource Planning System (ERP) referenced to in this document is Ellucian Colleague Release 18 running on Rocket Software’s Unidata RDBMS. Unidata is employed for both the application layer and the database layer. Microsoft Sequel Server may be employed for the database layer in the near future
- To fit with our current ERP infrastructure, the ECM should be a Windows-based solution
- Document Input:
- The ability to upload documents to the ECM via the web. The web interface should be mobile-friendly so that clients can use their smartphones or tablets to upload documents.
- A mobile application (iOS and Android) would be an asset, unless the web interface is very well refined for mobile use.
- The capability of accepting documents through Web Services.
- The ability to scan paper documents directly into the ECM.
- The ability to perform batch uploads of documents into the ECM.
- The ability to automate batch uploads
- Document Indexing and Organization:
- The capability to index documents should be built into the product.
- The capability to index document metadata.
- The ability to index document revisions.
- The indexing of documents should be customizable.
- Documents should be organized in a standard, well laid-out fashion
- Document Search:
- Documents should be searchable from an intuitive web interface (preferred) or a rich client.
- It would be considered an asset to have an advanced search feature and a basic search feature.
- Both the data and metadata of the documents should be searchable.
- Workflow Automation:
- The ECM should be able to automate the flow of incoming and outgoing documents.
- The ability to perform rules-based processing of the incoming and outgoing documents.
- Document actions should be user-definable.
- Due dates should be customizable in the system
- Workflows should be definable. Delivered workflow templates would be considered an asset.
- The ECM should be able to send out documents to proper signing authorities, whether they be internal or external to the university.
- The ability to obtain multiple signatures from different people for a document
- User Interface (UI) /Dashboard:
- Should be very user-friendly and intuitive – this is critical for user adoption
- As mentioned in the “Document Input” section, it would be preferable for the UI/Dashboard to be web-based using a modern implementation.
- A “workflow inbox” and a “document inbox” should be present on the ECM UI
- An alert and notification system should be built in to send e-mails, pop-ups, or SMS messages.
- There should be a reporting dashboard
- A calendaring system should be integrated to display any upcoming or past due documents or workflows
- ERP Integration:
- ERP integration is vital to the success of an ECM implementation. The solution should have a proven track record working alongside an Ellucian Colleague-based ERP solution with a high adoption rate from institutions using Colleague as an ERP.
- The ECM solution should be able to work integrate with Colleague using Ethos Integration and the Colleague Web API.
- In addition to working well with Ellucian Colleague, the ECM should be fairly ERP agnostic in the case of a transition to a new ERP
- The ability to upload documents to the ECM via the ERP and vice-versa should be present.
- The ability to search for documents in the ECM from the ERP should be present.
- A direct mechanism to update the ERP within workflow automation would be considered a major asset.
- Indirect methods that are simple to create and implement to updating the ERP
- Professional Services Implementation / Support:
- The ECM solution should have an offsite professional services implementation. Onsite implementation services in addition to offsite services would be considered an asset.
- The ECM solution should have an online support portal
- Customer Service representatives should be an option after the professional services implementation has been completed.
(2) All the questions must be submitted no later than February 21, 2022.
[C] Eligibility:
Onshore (Canada organization Only)
[D] Work Performance:
Performance of the work will be Offsite. Vendor needs to carry work in their office premises.
Budget :
Deadline to Submit Proposals: March 07,2022
Cost to Download This RFP/RFQ/RFI/Solicitation/Tender/Bid Document : 5 US$