Include listing of the basic features that will initially be included in the MVP. This is not ALL features just the high level overview of the most important or required features of the CRM for the specific end users supported. This can also be included as an attachment and not in the SOO. Example: One centralized constituent record per citizen with links to all associated vital data and correspondence records Newsletters (bulk e-mail) Reports and dashboards Advanced search External web forms (Contact Us) Internal web forms (Greetings) Rules engines, workflow, analytics, and service-level-agreements Ad-hoc data import and export Document version control, workflow, and library templates/repository 7.2.1 The contractor architect system objects, fields, and database entries to support the associated business processes. The contractor shall utilize the system support business processes as described in APPENDIX B-Vignettes Slide Deck and APPENDIX C Stories as the basis for the CRM application. While it is anticipated the MVP will include these initial features the final User Stories implemented will be prioritized and managed by the Product Owner and/or COR in conjunction with the contractor based upon a mutual agreed upon Product Roadmap and Backlog. The contractor shall ensure the system is configured to support expansion for additional requirements. The contractor shall configure the system in a way to support Source” “Open publishing. Task 3: Data Import collected from Legacy Systems Objective: The contractor import data collected from legacy systems in a manner that maintains vital record data such as name, address, e-mail address; association data such as interests, contact preferences, flags, and affiliations; as well as correspondence items, linkage with constituent record, contact history, and attachments. The contractor analyze, assist with exports, de-duplicate/scrub, prepare, and import data that has been collected from legacy systems including: The primary legacy CRM system, Provided as a government intermediary MySQL database available to the contractor Approximately 40GB of data and 400GB of file attachments
Include listing of the basic features that will initially be included in the MVP. This is not ALL features just the high level overview of the most important or required features of the CRM for the specific end users supported. This can also be included as an attachment and not in the SOO. Example: One centralized constituent record per citizen with links to all associated vital data and correspondence records Newsletters (bulk e-mail) Reports and dashboards Advanced search External web forms (Contact Us) Internal web forms (Greetings) Rules engines, workflow, analytics, and service-level-agreements Ad-hoc data import and export Document version control, workflow, and library templates/repository 7.2.1 The contractor architect system objects, fields, and database entries to support the associated business processes. The contractor shall utilize the system support business processes as described in APPENDIX B-Vignettes Slide Deck and APPENDIX C Stories as the basis for the CRM application. While it is anticipated the MVP will include these initial features the final User Stories implemented will be prioritized and managed by the Product Owner and/or COR in conjunction with the contractor based upon a mutual agreed upon Product Roadmap and Backlog. The contractor shall ensure the system is configured to support expansion for additional requirements. The contractor shall configure the system in a way to support “Open Source” publishing. Task 3: Data Import collected from Legacy Systems Objective: The contractor import data collected from legacy systems in a manner that maintains vital record data such as name, address, e-mail address; association data such as interests, contact preferences, flags, and affiliations; as well as correspondence items, linkage with constituent record, contact history, and attachments. The contractor analyze, assist with exports, de-duplicate/scrub, prepare, and import data that has been collected from legacy systems including: The primary legacy CRM system, Provided as a government intermediary MySQL database available to the contractor Approximately 40GB of data and 400GB of file attachments
CRMTaskOrder%20Sample%20DRAFT.docx