Configure Phase. Mercatus ICS team configures the Platform based on the Customer approved FRD. The Build Phase includes the following areas of implementation, each of which outlines the options available for deployment; Customer specified Options for each in the Service Order: o Entity Structures and Record Hierarchy: Mercatus to configure platform for required Entities and Sub-Entities to fulfill criteria defined in Document Phase; these will be based on necessary hierarchy and relationships between each Entity record based on Customer business process. o Data Definition and Field Setup: Mercatus to configure platform for all defined data fields from Document Phase. This includes the defined workflows and interactions expected from all users.
Configure Phase. Key Activities: Application and Solution Configuration, Data Load
Configure Phase. During the Configure phase, the solution components are built and tested based on the design document details. The process may repeat during this phase as the initial configuration is finalized. During the configuration process, WellSky will perform system testing activities on the configured solution to ensure each setting functions as defined according to what is in the design documents. WellSky will perform a final round of system testing on the final configured solution to ensure all design components are addressed and functioning as defined prior to exiting the Configure phase. The Client assigns a System Administrator prior to the start of the Configure phase to allow for the knowledge transfer to begin.
Configure Phase. The Configure Phase focuses on the configuration of the Campus Management Products to support the functional and technical components of the Business Process Blueprints that have been accepted by Customer and approved by CMC (“Customer Blueprints”). CMC will support the following activities and deliverables: Activities Deliverables/Actions • Customer will complete all configuration of the Campus Management Products utilizing Customer Blueprints and Configuration Workbooks with guidance from CMC • Customer will configure test cases for process testing with guidance from CMC • CMC will conduct a configuration audit to validate Customer Blueprints configuration and document issues with respect to such configuration. Customer is responsible for resolving all such issues. Failure to resolve such issues could delay the project schedule. • Data Migration, as set forth in this SOW • Customer is responsible for providing data from each of the source systems into a common format for all source systems as per the timeline defined in the project schedule. Extracted data will be • Completed Configuration Workbooks • CMC will provide Customer access to CampusNexus Student Data Conversion Resource Center (DCRC) • CMC and Customer will configure DCRC testing based on UAT plans completed by Customer • Customer will update Customer Blueprints based on outcomes from configuration and testing with guidance and approval from CMC • Customer will update Test Cases based on Testing Plan with guidance from CMC • Customer will update Training Plan with guidance from CMC • Customer will provide acceptance of UAT plans provided in a mutually agreeable format (SQL, CSV, Excel, etc.) • CMC will be responsible for the delivery of data loads, initial training of data validation process, and support for data validation across the project lifecycle. • CMC will perform an audit of the quality of the data migration and document issues with respect to such data migration. Customer is responsible for resolving all such issues. Failure to resolve such issues could delay the project schedule. • Customer will develop and configure User Acceptance Testing (UAT) Plans with guidance from CMC • Customer will conduct end-to-end process testing and configuration testing of the Customer Blueprints and data validation of the migrated dataset with guidance from CMC
