Specifications include, but are not limited to: Deliverables months 1-8 •Create a fully mapped CEDS or EDFI data model with scheduled extract-transform-load services from the Department’s existing data structure to the CEDS or EDFI data model.oThe Department plans to align all SLDS data elements with the CEDS or EDFI data model. If an element from our SLDS does not align with the CEDS or EDFI data model, the Department will extend the CEDS or EDFI data model to incorporate it. The mapping should be guided by the Common Education Data Standards found at https://ceds.ed.gov/ or the ED-FI Unified data model at https://dellfoundation.force.com/c365/s/. oWindows Active directory will be used to maintain security to the new data warehouse.oDDL script to be used to create the initial CEDS or EDFI data model that will be completed by DoIT.oCEDS or EDFI data models to follow best practices procedures with backups and proper maintenance procedures.oData dictionary aligns from current SLDS to the CEDS or EDFI data model saved in the Harvest repository.•Ensure that the generated CEDS or EDFI data model element definitions are well documented to reflect our SLDS data use.oThe goal from adopting the CEDS or EDFI data model is to benefit from the data dictionary services offered through the Align tool.Deliverables months 9-12 •Deploy the Generate tool. oOnce the CEDS or EDFI data model is in place, the vendor is to work with staff to deploy the Generate tool to create all required regulatory EdFacts reports. •Assist with transition to the new CEDS or EDFI data model.oAssist staff with any transformations needed to transition the new CEDS or EDFI data model to be the new primary SLDS to streamline operations. The current SLDS will serve as a stagingarea for the CEDS or EDFI data model. The vendor is to work with staff to initially run the old and new data models in parallel until the transition is completed and verified.