- If Districts are utilizing the IEP system, aren't we still experiencing data redundancy as we send CDE information from both IEP and Data Pipeline? Can the IEP system get its student demographic data from Data Pipeline?
- How will CDE ensure the Local Education Agencies (LEAs) have ownership of the data within Data Pipeline?
- How does this affect the quality of our data?
- Will this increase my workload?
- Will Data Pipeline increase the complexity of data submissions and/or my job? Will we get training?
- Will CDE be collaborating with the Student Information System (SIS) Vendors?
- Will Local Education Agencies (LEAs) have ownership of data within Data Pipeline?
- What is the Ed-Fi solution that the Data Pipeline will be built on?
- If a student leaves my district do I remove that record from the Student Interchange?
- For the districts without a Web services expert will CDE have someone to help us?
- How are the file layouts changing?
- Can you please provide more explanation on the new monthly submission process.
- How does it work if a student attends multiple schools / programs?
- When will LEAs be expected to start using Data Pipeline and stop using ADE?
- What is an Interchange?
- What are the benefits of frequent submissions to Pipeline?
If Districts are utilizing the IEP system, aren't we still experiencing data redundancy as we send CDE information from both IEP and Data Pipeline? Can the IEP system get its student demographic data from Data Pipeline?
CDE is building a process that will extract Special Education data from the State IEP system (Enrich). However, student/staff demographics will come from LEAs to the Pipeline EXCEPT for Part C kids and Parentally placed kids - those will come from Enrich. Staff will come from HR Interchange.
A Data Governance system will be put in place to help manage and clarify data ownership and roles and responsibilities. As mentioned in question 1, this program will extend to LEA data, and will provide guidelines and templates for how all LEAs can work together with CDE to manage education data in a consistent manner.
A major benefit of RISE and the use of Data Pipeline is that the data will be timelier and therefore more accurate. This is because the Data Pipeline is taking more frequently. Data can be submitted on a regular basis (nightly, weekly, monthly) and LEAs will be able to pass through tier 1 edits check to ensure the validity of the data. Data will no longer be gathered in different collections throughout the year. Instead , a data field will be gathered from the Local Education Agency's designated authoritative source and if the response to a particular data field changes for an individual, the next submission will update it within the Data Pipeline. So, outdated information will be overwritten.
The Data Pipeline will also expand its data upload capabilities. LEAs with the technological capabilities will be able to implement web services and therefore send data as frequently as nightly. For those smaller LEAs without those technological capabilities the traditional file upload will still be available. However, even through the traditional file upload, LEAs will be able to upload those files to the Pipeline more frequently to take advantage of error correction sooner.
Initially, your workload may increase as we transition from ADE to Data Pipeline. We understand that changes can be complicated and require some additional effort upfront. We are doing our absolute best to take you through this change in an organized fashion so that your workload continues to be manageable. Keep in mind that any increase in workload will be temporary. Once the Data Pipeline is established, it will be a more efficient and effective method of obtaining Local Education Agency data.
With any new technical system, the Colorado Department of Education recognizes that there are varying degrees of training required to bring Local Education Agencies and even their vendors up to speed. CDE will be providing multiple opportunities for the new Data Pipeline training for both LEA employees and vendor partners. Flexibility was built into the system to allow Local Education Agencies to align with CDE depending on their technical capability.
CDE will be working with the SIS vendors to help them make the appropriate changes. The Districts will also need to work with the vendors to ensure all vendors are informed and aware of the Data Pipeline changes. CDE will also be collaborating with other vendors affected as well like Human Resources and financial vendors.
Yes. Districts are the authoritative data source for the data submitted through the RISE Data Pipeline. They will have ownership over that data. And, to ensure the quality of the data, the data experts within the LEA will collaborate with other LEA and SEA data stewards to manage the data throughout each element's lifecycle. closely. Those individuals who are closest to a particular field should be the ones verifying the accuracy of that information. For example, an administrative unit would be the authoritative source for the primary disability of a student, and cooperation will occur across Local Education Agencies and CDE to ensure integrity of Special Education data. CDE is implementing a formal Data Governance program for just this reason.
The Ed-Fi data toolkit includes an XML-based data specification combined with a free tool suite developed by the Michael & Susan Dell Foundation to improve student achievement in the K-12 education sector. The Ed-Fi solution extracts student information from a variety of educational data systems, and then standardizes, integrates and communicates it to educators and other parties through Web-based dashboards, reports and other applications.
The Ed-Fi solution equips educators with actionable insights, so they can then make informed decisions on steps to improve the academic outcomes of students. School and district administrators, state, and federal agencies can also use this information as a supplement or replacement for broader state or federal accountability reporting purposes. For more information on Ed-Fi see www.ed-fi.org
No. You will populate the "exit date" but they still need to remain in the file for End Of Year purposes.
CDE can provide the xml schemas and layout, as well as guidance on implementing web services. However the Districts will be responsible for implementing web services. Remember, data pipeline will still accept various file formats if you do not have the capability to implement web services.
The file layouts are significantly changing. The ADE system has 19 files that collect some of the same demographic data, creating redundancies. The new Data Pipeline system works on an "interchange" format that will select the information needed just for that category.
Districts will allowed to determine the frequency of their data submissions, however it is recommended that this is done at least monthly. When you upload the data it will go through a Level 1 edit check. When it is time for the collection window you would approve and send that data, which will then go through the Level 2 data clean up, or the more complex business rules. You will make any changes you think are needed and approve them, and then you would only need to regenerate a new snapshot. What this means is that Districts no longer have to submit multiple versions of the same file to CDE. For example, you're just submitting a student interchange file based on the frequency you determined, and then generating a snapshot for Student October specifically.
Data Pipeline will have a primary school flag for each student, so that student will have the capability to be in multiple schools and programs, but for funding purposes, i.e., Student October, the primary flag would be set to one school and this is the information Data Pipeline will utilize.
July 2013 the first year-round collections will open in the new Data Pipeline (Directory, RITS batch, EDIS batch). All other data collections will open in the new Data Pipeline on September 1, 2013. There will be some collections that will start in ADE prior to July 2013 (i.e., Student End of Year on May 2013) that will need to be closed in ADE; however by June 2014, 2013 ADE will be retired.
An interchange is a method of providing data to CDE in which local education agencies (LEAs) may choose from multiple formats of flat files to submit data frequently throughout the year. Although LEAs may submit as often as they wish, CDE will be encouraging the submission of major interchanges (student and staff) at least on a monthly basis.
Data that is sent more frequently will be easier to verify for completeness and accuracy as anomalies are identified as they occur. Data issues can be addressed over time rather than just prior to a collection deadline.
Also, the same data can be used for many purposes which will eliminate collecting the same data in different collections.
Contact: Data Pipeline Support at email@example.com