| Estimate of Reg Year Secondary Newly Documented Migrant Students | Course Hist. Data Element Collection Hrs./Student for most recent prior enrollment in State | Effort to Collect Course History Data Elements for most recent prior enrollments in State | |||
| 19,768 | 1.17 | 23,062.8 | |||
| Assumptions: | Number of Responses (for OMB 83-C) | 19,768 | |||
| - Estimate of Regular Year Secondary Newly Documented Migrant Students is defined on Tab 1 | |||||
| - Course History data element collection hrs./student based on feedback from States | |||||
| 1.17 x 60 = 70 minutes | |||||
| 1 hour 10 minutes | |||||
| Assessment Data Elements | Summary | ||||||||||||
| Total # Students Assessed | # Terms / Year Assessed | Assessment Collection Hrs./Student | Total Effort (hours) | Assessment Data Elements | Course History Data Elements | Core Data Elements | Total Effort (hours) | ||||||
| 81,027 | 1 | 0.08 | 6,752.3 | 6,752.3 | 55,225.8 | 153,094.2 | 215,072.3 | ||||||
| Assumptions: - Assessment results are made available once per student per year, regardless of when the test is administered - Effort to collect assessment data based on State feedback |
|||||||||||||
| Number of Responses (for OMB 83-C) | 218,706 | ||||||||||||
| Course History Data Elements | |||||||||||||
| Total # Secondary Students Enrolled | Course History Collection Hrs./Student | Total Effort (hours) | |||||||||||
| 60,246 | 0.92 | 55,225.8 | |||||||||||
| Assumptions: - Effort to collect course history data based on State feedback |
|||||||||||||
| Core Data Elements | |||||||||||||
| Total Number of Enrolled Students | Percentage of Students with new data each year | Core Data Collection Hrs./Student | Total Effort (hours) | ||||||||||
| 218,706 | 100% | 0.70 | 153,094.2 | ||||||||||
| Assumptions: - Effort to collect Core (non-COE) data based on State feedback regarding the effort to provide Core data elements for initial submission, then reduced from 0.88 to 0.70 to make allowance for states with automated processes to collect and provide updates, and to also account for the fewer number of data elements that are expected with an update instead of an initial submission. - It is assumed that Core enrollment data elements will need to be updated at least once per year for 100% of the students. These updates will be submitted by States at the end of the next occurring term. |
|||||||||||||
| 70 x 60 minutes = 42 minutes | |||||||||||||
| Number of Requests for Data Correction per State per Year | Number of Participating SEAs | Hours/student to review and correct data | Total Effort (hours) | ||||
| 1 | 46 | 0.63 | 28.8 | Number of Responses (for OMB 83-C) | 46 | ||
| Assumptions: - Number of Data Correction requests per state based on State feedback - Each correction request will only involve one category of data (core, assessment, or course history) - Effort to review and correct data is assumed to be equal average effort to collect data across all data element groups, based on State feedback |
|||||||
| Number of Requests for Data Correction per Year | Hours/student to review and correct data | Total Effort (hours) | ||||
| 6 | 0.63 | 3.8 | Number of Responses (for OMB 83-C) | 6 | ||
| Assumptions: - Number of Data Correction requests based on past OME requests and estimated future increases as parental awareness of MSIX increases - Each correction request will only involve one category of data (core, assessment, or course), but could inolve any of these categories of data - Effort to review and correct data is assumed to be equal average effort to collect data across all data element groups, based on State feedback |
||||||
|
|||||||
| Median Response (Hours) | Median Response (Minutes) | Question | Florida Response (Minutes) | Montana Response (Minutes) | Penns. Response (Minutes) | Colorado Response (Minutes) | Illinois Response (Minutes) | Virginia Response (Minutes) | Oregon Response (Minutes) | California Response (Minutes) | State 9 Response (Minutes) |
| 0.88 | 52.5 | 1) How many minutes in total does it take to collect the Core data elements for one student and enter them into your state MEP system? Please note that these data elements do not include any information contained in the National COE. However, it may be necessary to collect information from sources such as SEA systems, LEA systems, MEP files, parents, or students. Please see the provided list of "Core" data elements for definitions. | 45 | 1000 | 30 | 180 | 60 | 100 | 17.5 | 25 | |
| 2) Please summarize how the activities addressed in Question 1 are completed in your state and by whom. Please be concise, but as thorough as possible. |
Between 5-30 mins | ||||||||||
| 0.08 | 5.0 | 3) How many minutes in total does it take to collect the Assessment data elements for one student's current year State Assessments only and enter it into your state MEP system? Use the average time spent per student regardless of the number of tests. Please see the provided list of "Assessment" data elements for definitions. | 1000 | 30 | 1000 | 5 | 1 | 0.01 | 3 | ||
| 4) Please summarize how the activities addressed in Question 3 are completed in your state and by whom. Please indicate which, if any, parts of this process are automated. Please be concise, but as thorough as possible. |
Fully automated | ||||||||||
| 0.92 | 55.0 | 5) How many minutes in total does it take to collect current year Course History data elements for one secondary student and enter the data into your state MEP system? This should be the average time per student regardless of the number of courses. Please see the provided list of "Course History" data elements for definitions. | 1000 | 30 | 180 | 80 | 0.01 | 3 | |||
| 6) Please summarize how the activities addressed in Question 5 are completed in your state and by whom. Please indicate which, if any, parts of this process are automated. Please be concise, but as thorough as possible. | Fully automated | ||||||||||
| 1.17 | 70.0 | 7) How many minutes in total would it take to collect secondary education Course History data elements for the most recent prior secondary school enrollment in your state for one student? The most recent prior secondary enrollment may be prior to the student's MEP eligibility. Please provide an estimated effort if this activity is not currently performed in your state. See the provided list of "Course History" data elements for descriptions. | 1000 | 60 | 180 | 80 | 0.01 | 3 | |||
| 8) Please summarize how the activities addressed in Question 7 are completed in your state and by whom. Please indicate which, if any, parts of this process are automated. If this task is not currently being executed in your state, please indicate how you envision it would be performed. | Fully automated | ||||||||||
| - | 9) How many hours would it take to create a new Data Element to indicate (Yes or No value only; the content of the transcript does not need to be collected, entered, or transmitted) whether out-of-state secondary school transcripts are present in your state for a migrant student? Please do not include the effort to request and receive an out-of-state transcript. Instead, please include the effort to modify your existing state MEP system to enter and store only whether or not an out-of-state transcript exists in your state for a student, the effort to modify the state's MSIX interface to transmit this data, and the effort to update your state procedures to collect this data. | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 0.67 | 40.0 | 10) Assuming the new data element discussed in Question 9 was added in your State MEP system to indicate (Yes or No) whether out-of-state transcripts are present in your state for a migrant secondary student, how many minutes would it take to research (e.g., contacting LEAs, research other state systems and the existing state MEP system, file review) whether an out-of-state transcript is present and then indicate (Yes/No) in the state system? | 100 | 30 | 100 | 40 | 36 | 17.5 | 90 | ||
| 80% | 11) For what percentage of migrant students does new or updated Core data element information become available during a typical school term? Please see the provided list of "Core" data elements for definitions. | 80% | 100% | 10% | 100% | 100% | 20% | 72% | |||
| 1.0 | 12) Approximately how many times per year does staff in your state update a Student's record in your state MEP system as the result of a request from a parent or student to correct inaccurate data contained in your state MEP system for the student? | 0.5 | 1 | 1 | 1 | 3 | 2 | 0.5 |
| State | Florida | Montana | Pennsylvania | Illinois | Colorado | Virginia | Oregon | California | |
| How many minutes in total does it take to collect the Core data elements for one student and enter them into your state MEP system? Please note that these data elements do not include any information contained in the National COE. However, it may be necessary to collect information from sources such as SEA systems, LEA systems, MEP files, parents, or students. Please see the provided list of "Core" data elements for definitions. | 1000 | 30 | 60 | 180 | 100 | 5 to 30 | 25 minutes | ||
| Please summarize how the activities addressed in Question 1 are completed in your state and by whom. Please be concise, but as thorough as possible. | Our estimated answer for #1 is: 30-60 min;The local educational agencies (LEAs) school registrar/MEP staff collect this data on each migrant student and enter it into their local student database. LEAs are required to submit migrant student records from the local student database to the state student database through the Florida Automated System for Transferring Electronic Records (FASTER). FASTER is considered the conduit. Migrant records are submitted to the state based on the OME established time frames. | The information is collected generally by recruiters and directors in an interview setting at the family's temporary home, school, or other setting. The data collection and entry is dependent upon whether the student is: 1)interstate new/returning 2)intrastate new/returning Can take from 30 minutes to three days; nothwithstanding PFS information. | Most of this data is collected at time of Recruitment by Recruiters using electronic COE;s and then reviewed at several levels. A few items, such as LEP, IEP, Immunization, Health Alert may be gathered by Recruiters, but are more likely to be gathered by Student Support Specialists, which is also done using direct data entry electronically and also is reviewed. The Facility/District/Project detailed information is primarily maintained by Data Specialists and simply referenced by the staff supplying the correct facility code from a drop-down menu and the rest of the information is automatically looked-up;. Some of these time saving factors may make our time per student slightly less than other states. | Information is gathered by recruiters, teachers, counselors, and health care providers from student records, parent and student interviews and LEA data systems. Data entry specialists enter the information on NGS. State support staff provide technical assistance to data entry specialists as needed and identify errors in data entry that need to be corrected. | SEA/Regional staff performs various activities to collect and report the Core data elements in the State Student Information System, NGS. Data sources include the following; State Information System, Local Student Information Systems, Other Data Sources within the Department, MEP Files, Parent Surveys, Pre-school Surveys, Student Secondary Transcript, Out-of-School Youth Surveys. The core data elements are collected through regional programs, with support from the LEA. Regional programs have established working relationships with participating school districts and developed a method for collecting student data on an agreed schedule. Through these efforts some districts have granted regional programs direct access to the district internal student database. Districts have designated internal staff to provide student academic information to the regional programs. Core data elements collected by the regional programs included but not limited; Local district formal assessments, local district PK assessments, medical alerts, immunizations, health/dental, enrollment, student state IDs, and course history. The SEA sends data request to the department's data warehouse requesting student demographic data on State Assessments, Language Proficiency, Special Needs, Dropped Out, Received GED, Graduated, students tested in reading and math, MEP Projects and school campus information, as well as, FTE and MEP job classifications. | Migrant coordinators or designee enter core elements in the state database which transfers to the MSIX. Migrant recruiters can spend 1-2 days recertifying students and/or identifying new students. The migrant coordinator/designee will enter data to the state system which takes about 30-45 minutes depending upon if they are entering a new record versus updating a student record. | Per Sue Cheavtharn: It takes 5-30 minutes to actually request the data, then enter it into OMSIS. There is additional time to wait for information to be provided by the LEA, but the staff person is doing other work during the waiting period. Oregon’s MEP program operates at two different levels: Local Education Agency and Regional Education Service Districts (ESD). Oregon has 19 regional MEP programs seven are LEA and eight are Regional ESDs; the regional ESD operates and cover many districts. Obtaining information for an LEA is quick and efficient whereas the opposite is said the ESD’s level. LEA access to information is within minutes, if the local data specialist has access to the information. ESDs access to information could range from 15 minutes to weeks or even months, depending on the accessibility to information and personnel. The main MEP liaisons at the regional program are the Recruiters, Data Specialists and/or Coordinators. Communication protocols are set-up at each local MEP offices. Information about student comings or goings is at times reported to the recruiters and at times to no one. Once information is obtain about a student arrival or departure, data is compiled and appropriate forms are completed either by the Recruiter or Data Specialists. Information is then entered to the Oregon Migrant Student Information (OMSIS) by the data specialist. |
Migrant Region and/or LEA staff enter program center information into COEstar that is sent and aggregated to the State Migrant Longitudinal Data System (MLDS). Other core data is linked as part of a back office process to distinct state systems files for aggregation into the MSIX data feed. WestEd MSIN staff, CDE Data Management Division staff, CDE Assessments staff all participate. This time includes updates, full history and notes for the student unit record. LEA efforts comprise most of the time, ensuring student identifiers used to match within the state reporting and data products are entered and are accurate |
|
| How many minutes in total does it take to collect the Assessment data elements for one student's current year State Assessments only and enter it into your state MEP system? Use the average time spent per student regardless of the number of tests. Please see the provided list of Assessment data elements for definitions. | 1000 | 30 | 5 | 1000 | 1 | less than 1 minute | 3 Minutes | ||
| Please summarize how the activities addressed in Question 3 are completed in your state and by whom. Please indicate which, if any, parts of this process are automated. Please be concise, but as thorough as possible. | Once assessments are administered, they are collected and scored. Data entry into local student data base for the test data including scores occur at the LEA/school district level. The assessment data/results are then sent electronically to the state student database through FASTER. The amount of time to collect, score, conduct data entry, etc. is difficult to determine at this time. | Assessment data is collected yearly at the SEA level and entered through uploads of the state data system to NGS on MT. based students. For interestate students, it can take directors/data personnel at the SEA and LOA level months to obtain. Tests are giving annually, results take up to five months to appear in state systems; then for interstate students we have to match student IDs. | Annually, we collect what we can electronically from our State Assessment system as well as state Language Assessments. This is a semi-automated process. However, staff may have to collect other data manually if the child leaves before the electronic version is not available or if there are other assessments that are not available electronically. The time required to manipulate the electronic file is also included. With the broad range of possibilities, it is hard to determine the average time, but this is our best estimation. | Illinois student assessment data is maintained in a state student data base. The NGS staff generate a file of eligible migrant students each year. The Illinois state student data base staff use the file to run a data match to identify the assessment results of all migrant students on the IL student data base. The migrant student assessment results are sent in a file to NGS, where staff load the information into NGS to populate the individual migrant student records. | The SEA sends a list of migrant student state IDs to the data warehouse and requests assessment information on the following state assessments; CSAP, CSAP A, CELA. Once this information is received, the State electronically imports the information into NGS. A validation sample is completed prior to importing all information. State assessment data is not available until late August or September. For students that do not have state assessments, regional programs are required to request local assessments and manually enter them in the students record in NGS. | The assessment information is transmitted directly from the state assessment system (separate from migrant database) to the MSIX for migrant students with assessment files. The local coordinators do not enter this information. | Per Sue C: The Assessment data is automatically provided to OMSIS. It takes less that 5 minutes to download data for all Oregon students once per year. State assessment information is not easily accessible by any of Oregon’s regional MEP programs. Because assessment information is considered “Resisted” data, one must have rights and authorization to access “Current” state assessments. The time to collect the information varies from programs to programs, depending on consortium agreements. The times it takes to collect the “current assessment” data can range from one week to possibly never. The OMSIS system does not allow entry of state assessments, however, local and state language proficiency assessments are allowed on OMSIS. On a yearly basis, Oregon extracts previous school year state assessment data and submitted it to MSIX. This usually occurs after the completion of the CSPR Part II. Ideally, current assessment information should be easily accessible for MEP staff in order to evaluate and identify Priority for Service (PFS) students; reality wise, this is not the case. Very few of Oregon’s regional MEP programs have access to current assessment information. When current information is not available then last school year state assessments are used to determine PFS for the new school year. Many of the LEAS perform PFS determination for immediate services. Oregon is anticipating with the development of the new OMSIS version 2.0, the state assessments would be easily assessable for all LEA MEP staff. |
California maintains wholly separate systems for MEP, Assessments, and state longitudinal student records. The data for assessments for the MEP students is merged as part of a back office process with linkages to state systems and is integrated with the process used to generate other Federal reports, e.g. CSPR, EdFacts. The time included in the estimate is based on the overall process performed each year to bridge the systems and prepare the file for linking to MSIX feeds. The linkages are between relational database tables from the three systems. This estimate does not include the initial development time that was required. WestEd MSIN staff, CDE Data Management Division staff, CDE Assessments staff all participate. LEA efforts comprise most of the time, ensuring student identifiers used to match within the state reporting and data products are entered and are accurate. |
|
| How many minutes in total does it take to collect current year Course History data elements for one secondary student and enter the data into your state MEP system? This should be the average time per student regardless of the number of courses. Please see the provided list of Course History data elements for definitions. | 1000 | 30 | 80 | 180 | less than 1 minute | 3 Minutes | |||
| Please summarize how the activities addressed in Question 5 are completed in your state and by whom. Please indicate which, if any, parts of this process are automated. Please be concise, but as thorough as possible. | The time varies because data collection occurs at several levels, i.e., from instructional staff on to MIS staff. The local educational agencies (LEAs) school instructional, guidance, registrar, and MEP staff collect this data on each migrant student and enter it into their local student database. LEAs are required to submit migrant student records from the local student database to the state student database through the Florida Automated System for Transferring Electronic Records (FASTER). FASTER is considered the conduit. Migrant records are submitted to the state based on the OME established time frames. | Depends on if student is interstate/new/returning; intrastate new/returning. In summer, difficult to obtain from LOAs who are not there and if most recent information has been entered at homebase. Done by youth coordiator, directors. Can take up to three days if not in system. Data entry on partial credits or updating for interstate students takes much less time (30 minutes) for recieving state; to build an entire course history for a new student takes much more time, again depedning on whether the student is new, returning, interstate or intrastate. Entry done by data entry persnonell, advocate; collection by youth coordiantor/teacher. | Secondary Student Support Specialists go to schools and collect what courses students are enrolled in. Depending on the School, this may be done by obtaining a printout from the school or it may require manually searching through records. They may then enter that data into their Tablet or put it on a data collection form and submit to the Data Specialist. At the end of each term or if a child leaves the area, the staff return and collect the current grade and clock hours or possibly the final grade and credits as appropriate and record in the same manner. There is no Central Data System from which to automate this collection. | The migrant project staff request course history data from the school counselor. The school counselor retrieves this information from the student record. The NGS data entry specialist enters the information in NGS. | At this time, the SEA is not currently collecting course history data elements. On April 10, 2012, the SEA will be holding Secondary Course History Training. All regional programs are required to participate in this training. Currently, course history information is not reported to the State and therefore must be collected by the districts. The information will be collected electronically and either entered or imported into the State's Migrant Student Information System, the New Generation System (NGS). We established the time it will take the SEA and regional programs to collect and enter course history in the beginning will take 30-180 minutes per student. | At this time, the state does not upload course history data. | Per Sue C.: Course History is automatically downloaded into OMSIS. It takes less than a minute of work to process data for all Oregon students. Oregon MEP programs personnel do not collect Course History on MEP students. This process happens automatically when a child is flagged as withdrawn on the OMSIS and checked against the KIDs system with an associated enrollment line then the Course History is extracted and set to MSIX. Oregon extracts Course History data from a system call the KIDs. KIDs is a system that store collections of information sent from the LEAs. All LEAs in Oregon are encouraged to join what is called a regional Data Warehouse. All regional Data Warehouse data feeds into the KIDs system. |
California maintains wholly separate systems for MEP, and state longitudinal student records. The data for assessments for the MEP students is merged as part of a back office process with linkages to state systems and is integrated with the process used to generate other Federal reports, e.g. CSPR, EdFacts. The time included in the estimate is based on the overall process performed each year to bridge the systems and prepare the file for linking to MSIX feeds. The linkages are between relational database tables from the three systems. This estimate does not include the initial development time that was required. WestEd MSIN staff, CDE Data Management Division staff participate. LEA efforts comprise most of the time, ensuring student identifiers used to match within the state reporting and data products are entered and are accurate |
|
| How many minutes in total would it take to collect secondary education Course History data elements for the most recent prior secondary school enrollment in your state for one student? The most recent prior secondary enrollment may be prior to the student's MEP eligibility. Please provide an estimated effort if this activity is not currently performed in your state. See the provided list of Course History data elements for descriptions. | 1000 | 60 | 80 | 180 | less than 1 minute | 3 minutes | |||
| Please summarize how the activities addressed in Question 7 are completed in your state and by whom. Please indicate which, if any, parts of this process are automated. If this task is not currently being executed in your state, please indicate how you envision it would be performed. | The time varies because data collection occurs at several levels, i.e., from instructional staff on to MIS staff. The local educational agencies (LEAs) school instructional, guidance, registrar, and MEP staff collect this data on each migrant student and enter it into their local student database. LEAs are required to submit migrant student records from the local student database to the state student database through the Florida Automated System for Transferring Electronic Records (FASTER). FASTER is considered the conduit. Migrant records are submitted to the state based on the OME established time frames. | See number six | This is difficult to answer. If it is at a school we are already dealing with for a child, it would probably be an additional 15 minutes per student, and this is something we are already doing. If while the staff are collecting the information in #5/6 and know that the student has previous course history at that school, they collect it and we enter the required enrollment information (enrollments are required in both MIS2000 and MSIX in order to enter Course History data). If it would require going to another school that would take at least some, if not considerable additional time, especially if it is a school outside the region where the student is or if it is a school where we do not have an established relationship. | The migrant project staff request course history data from the school counselor. The school counselor retrieves this information from the student record. The NGS data entry specialist enters the information in NGS. | Regional programs are required to share a Secondary Course History Template with their participating districts, which requires them to report all MSIX course history data elements. Districts will complete this template for each student's subject and course for grades 9-12. | At this time, the state does not upload course history data. | If enrollment information matches on the OMSIS and KIDs, then the collection of Course History happens in seconds. However, if OMSIS does not have an enrollment line that matches the KIDs then nothing is transferred to MSIX. | This step and activity is not currently performed at the SEA level. Because these are back office operations between distinct longitudunal systems this would require new rules for the data linkages and would leverage, thus be an extension of the existing data processes. This estimate does not include the initial development time that was required. WestEd MSIN staff, CDE Data Management Division staff participate. LEA efforts comprise most of the time, ensuring student identifiers used to match within the state reporting and data products are entered and are accurate |
|
| How many hours would it take to create a new Data Element to indicate (Yes or No value only; the content of the transcript does not need to be collected, entered, or transmitted) whether out-of-state secondary school transcripts are present in your state for a migrant student? Please do not include the effort to request and receive an out-of-state transcript. Instead, please include the effort to modify your existing state MEP system to enter and store only whether or not an out-of-state transcript exists in your state for a student, the effort to modify the state's MSIX interface to transmit this data, and the effort to update your state procedures to collect this data. | 100 | 10 | 40 | 100 | 36 | Per Sue C: 16 to 32 hours Oregon cannot give you an estimated time to create a new Data Element without knowing what data elements are being considered. Adding new data elements would involve many staff, not to mention the changes to the database structure, identifying the source and the validity of the data source. Also we need to add in to the timeline the project flow on obtaining the work approval. |
10 | ||
| Assuming the new data element discussed in Question 9 was added in your State MEP system to indicate (Yes or No) whether out-of-state transcripts are present in your state for a migrant secondary student, how many minutes would it take to research (e.g., contacting LEAs, research other state systems and the existing state MEP system, file review) whether an out-of-state transcript is present and then indicate (Yes/No) in the state system? | 100 | 30 | 40 | 100 | 36 | 5 to 30 | 90 | ||
| For what percentage of migrant students does new or updated Core data element information become available during a typical school term? Please see the provided list of Core data elements for definitions. | 80 | 100 | 100 | 10 | 100 | Per Sue C: This would follow essentially the same process to collect data as in Question 1, so the same timeframes would apply. We are unable to provide an estimated time. It all depends on the accessibility and the location of the MEP child. |
72% of the 10-11 count had a core data level entry or unpdate. | ||
| Approximately how many times per year does staff in your state update a Student's record in your state MEP system as the result of a request from a parent or student to correct inaccurate data contained in your state MEP system for the student? | 1 | 1 | 3 | 1 | 2 | Per Sue C: Oregon receives less than 1 request per year. Oregon receives very few requests from parents or students to update academic records. If updates are done it is mainly with the child’s date of birth and not necessary the academic data. |
Unknown - would need to research. There are 23 Regional Centers and 500 participating LEAs to query and verify. | ||
| Please provide your name and state so we can contact you if we have any additional questions or need further clarification. | For #9, in general, it would take Florida 1.5-2 years to add any new Data Element, if it was not already in existence in the state student database. However, for #9 and #10, specifically, Florida already has the capacity to collect, store, and send out-of-state secondary school transcript information. Question #11 is not very clear. Florida updates core data elements records at least once a year and as needed for every migrant student. Our estimated response for #12 is less than one time per year. For #12, Florida receives infrequent requests to update a student's academic record from a parent or student. If updates are done, it is generally about updating the DOB. | Angela Branz-Spall;MT | This is provided by Vaughn Murray in consultation with Carmen M. Medina, State Director as well as Regional Data staff on behalf of the Pennsylvania MEP | Beth Robinson, Illinois | Colorado;Brenda Meyer General Professional Colorado Department of Education Data Services Unit 201 E. Colfax Avenue, Room 507 Denver, CO 80203 Phone: 303-866-6744 Work Cell: 303-913-0282 Fax: 303-866-6888 Email: [email protected] |
Patience Scott, Virginia | Jonathan Fernow, Oregon Sue Cheavtharn, Oregon Follow-up discussion (as noted in Sue C comments above) between Sue Cheavtharn and John Carden on 4/3/12 |
Glenn Miller, Project Director WestEd MSIN Project. California. |
| IC Data Form Part 1 | ||||||
| Section 5: ICR SUMMARY OF BURDEN | ||||||
| Annual Cost to the Federal Government ($) | $5,191,760 | |||||
| Requested | Program Change Due to New Statute | Program Change Due to Agency Discretion | Change Due to Adjustment in Agency Estimate | Change Due to Potential Violation of the PRA | Previously Approved | |
| Annual Number of Responses | 343,880 | 0 | 0 | -41,100 | 0 | 384,980 |
| Annual Burden Hours | 391,338 | 0 | 0 | -8,436 | 0 | 399,774 |
| Annual Cost Burden (Dollars) | $15,348,284 | 0 | $0 | $1,720,001 | 0 | $13,628,283 |
| IC Data Form Part 2 | ||||||
| Section 2: BURDEN DETAIL | ||||||
| Number of Respondents | 46 | |||||
| Responses per Respondent | 7,476 | |||||
| Annual Nbr of Responses | 343,880 | |||||
| Burden per Response | Annual Burden | |||||
| Time per Response | Hours | Cost Per Response | Annual Time Burden (Hours) | Annual Cost Burden (Dollars) | ||
| Reporting | 1.14 | 1.14 | $44.63 | Reporting | 391,338 | 15,348,284 |
| Record Keeping | Record Keeping | |||||
| Third Party Disclosure | Third Party Disclosure | |||||
| Total | 1.14 | 1.14 | $44.63 | Total | 391,338 | 15,348,284 |
| Annual Burden with Changes | ||||||
| Requested | Program Change Due to New Statute | Program Change Due to Agency Discretion | Change Due to Adjustment in Agency Estimate | Change Due to Potential Violation of the PRA | Previously Approved | |
| Annual Number of Responses | 343,880 | 0 | 0 | -41,100 | 0 | 384,980 |
| Annual IC Burden Hours | 391,338 | 0 | 0 | -8,436 | 0 | 399,774 |
| Annual IC Cost Burden (Dollars) | $15,348,284 | 0 | $0 | $1,720,001 | 0 | $13,628,283 |
| State | Parent Phone 2 | Parent Email 1 | Parent Email 2 | Total Hours | ||
| WA | 300 | 300 | 300 | 900 | ||
| CA | 552 | 552 | 552 | 1,656 | ||
| MI | 53 | 53 | 53 | 159 | ||
| NY | 33 | 0 | 33 | 66 | ||
| PA | 20 | 20 | 20 | 60 | ||
| TX | 1866 | 1866 | 1866 | 5,598 | ||
| FL | 355 | 355 | 355 | 1,065 | ||
| ID | 200 | 200 | 200 | 600 | ||
| CO | 25 | 121 | 121 | 267 | ||
| TOTAL | 3404 | 3467 | 3500 | 10,371 | ||
| AVG/STATE | 378 | 385 | 389 | 1,152 | ||
| National Total - 46 States | 17,398 | 17,720 | 17,889 | 53,007 | ||
| Median Response (hours) | 200 | 200 | 200 | 27600 | ||
| The median response was calculated instead of an average response to minimize the impact of State responses that deviated significantly (both high and low) from those provided by the other States. | ||||||
| State | Parent Phone 1 | Parent Phone 2 | Parent Email 1 | Parent Email 2 | Graduation Date | HSE Date | Qualifying Activity | QA - free text versus list |
| WA | Presently Collecting one phone number for the entire family. Stored in our COE table with connection to each student connected to the COE. No major Change in the amount of time to collect this number as it is already collected. We would just need some time to program the new location on our paper COEs, our eCOEs and to update the database with the new name of the field being added. This data is already being entered by the District Recruiters and/or Records Clerks within each of our Project Districts and by our Statewide Recruiters within our Non-Project Districts. Since they are already doing this for a phone number, there is no time commitment for the entry of the data. |
We are not presently collecting a second phone number for the families by parent. We are only collecting one. This change would add 1 minute per COE to the person filing out the new COEs which would be somewhere in the neighborhood of 6800 minutes (>100 hour) on an average year. There would also be the time need to add this field to the MSIS database and to the COE form and the eCOE form. We would also need programming time to add the field to our HTML screens for viewing and verification of field value as well as the time to update the nightly process to MSIX. This data would need to be entered by the District Recruiters and/or Records Clerks within each of our Project Districts and by our Statewide Recruiters within our Non-Project Districts. Since they are already doing this for the one phone number. |
We are not presently collecting an Email Address for either parent nor for the individual students. This change would add 1 minute per COE to the person filing out the new COEs which would be somewhere in the neighborhood of 6800 minutes (>100 hour) on an average year. There would also be the time need to add this field to the MSIS database and to the COE form and the eCOE form. We would also need programming time to add the field to our HTML screens for viewing and verification of field value as well as the time to update the nightly process to MSIX. This data would need to be entered by the District Recruiters and/or Records Clerks within each of our Project Districts and by our Statewide Recruiters within our Non-Project Districts. Since they are already doing this for the one phone number. |
We are not presently collecting an Email Address for either parent nor for the individual students. This change would add 1 minute per COE to the person filing out the new COEs which would be somewhere in the neighborhood of 6800 minutes (>100 hour) on an average year. There would also be the time need to add this field to the MSIS database and to the COE form and the eCOE form. We would also need programming time to add the field to our HTML screens for viewing and verification of field value as well as the time to update the nightly process to MSIX. | We are presently collecting The Graduation Date in our MSIS, so there would be no major change in the amount of time to collect this number as it is already collected. We would just need some time to program the new location on our paper COEs, our eCOEs and to update the database with the new name of the field being added if we determine it will need a separate field. We receive this data on our Monthly reconciliation with our State Office in Olympia, by way of Web Services between the MSIS and Wa State Student Database. This data comes to us as a spreadsheet variable with a single value shared with HSE Date which is a termination date in one field and the termination reason in another. The data is uploaded to our MSIS monthly for each eligible student within the MSIS. |
We are presently collecting The HSE Date in our MSIS, so there would be no major change in the amount of time to collect this number as it is already collected. We would just need some time to program the new location on our paper COEs, our eCOEs and to update the database with the new name of the field being added if we determine it will need a separate field. We receive this data on our Monthly reconciliation with our State Office in Olympia, by way of Web Services between the MSIS and Wa State Student Database. This data comes to us as a spreadsheet variable with a single value shared with Graduation Date which is a termination date in one field and the termination reason in another. The data is uploaded to our MSIS monthly for each eligible student within the MSIS. |
We are presently collecting this value on our paper and eCOEs as a single field. This field has values such as: Pruning, Picking, Trimming, etc. Based on the discussion we have had with this option in other SUGAR meetings, what this really means is “activity and crop” which we store in our system as “Activity” and “Crop” in two separate field in a table in our DB. To combine our two fields into one to upload to MSIX, we would need time to program the new value into the MSIX Web Service that runs nightly to transfer data from the MSIS (Washington DB) to the MSIX. This data is already being entered by the District Recruiters and/or Records Clerks within each of our Project Districts and by our Statewide Recruiters within our Non-Project Districts. Since they are already doing this for the qualifying activity (just the action), there is no time commitment for the entry of the data. |
|
| CA | Manually entered by LEA MSIN recruiters on each COE, then updated as needed, and during annual verification to each child profile | Manually entered by LEA MSIN recruiters on each COE, then updated as needed, and during annual verification to each child profile | Manually entered by LEA MSIN recruiters on each COE, then updated as needed, and during annual verification to each child profile | Manually entered by LEA MSIN recruiters on each COE, then updated as needed, and during annual verification to each child profile | Manually entered by LEA MSIN data specialists to each child profile upon graduation | Manually entered by LEA MSIN data specialists to each child profile upon HSE | Manually entered by LEA MSIN recruiters on each COE | For question 2) we definitely prefer to keep option 1 with a free text field, which would not create any additional burden. We do not see how a comprehensive list could be created with all the different qualifying activities that we see on CA COEs. In addition to more time during recruitment because recruiters would have to match the information collected from the parent to an option on the qualifying activity list (calculating 3 minutes per COE x 16,500 COEs completed last year= 827 hours) Option 2 would also require a tremendous amount of work such as: •120 hours- development to refactor the COE (which would cause a pause in current development) •80 hours- finding a way to match previous definitions to what the field is already accustomed to entering (if there is not an option for "other") •40 hours- creating tables to map CA-specific activities to OMEs master list •40 hours- edit and republish the COE instructions •40 hours- recreate and distribute User Guide videos •40 hours- retraining the field to use this new functionality •40 hours+ ongoing- additional TA to the field |
| MI | Recruiter collects at time of interview & documents on paper COE; data entry clerk enters # into MIS2000 which then connects with MSIX. | Recruiter may collect at time of interview & document on paper COE; would need add’l field created in MIS2000 to enter the # as currently there isn’t one. | Not currently collected; would need add’l field created in MIS2000 to enter the # as currently there isn’t one | Not currently collected; would need add’l field created in MIS2000 to enter the # as currently there isn’t one | Data entry clerks enter date into MIS2000 upon end of performance period that student graduates and/or upon receiving/researching notification of student’s completion date. *Districts would have to research students who leave the state but are potential grads or HSE students. |
Data entry clerks enter date into MIS2000 upon end of performance period that student graduates and/or upon receiving/researching notification of student’s completion date. *Districts would have to research students who leave the state but are potential grads or HSE students. |
Recruiter collects at time of interview & documents on paper COE; data entry clerk enters into MIS2000 which then connects with MSIX. | We also concur with Vaughn’s comments on the need for this to be free text. Any other type of drop down would be significant work to implement. Free text would assist recruiters in completing COEs based on history which would be helpful. I don’t see a significant need to be able to do anything else with the data. I’m sure if it were standardized we could do more reporting and analysis of types of work, but it’s not necessary data to implement or improve MEP programming. |
| NY | Recruiter will collect this information and we are already completing this. | Instead of parent 2 the recruiters collect a next of kin phone number. This would be a minimal change for New York State. | This information is collected by the recruiter and is currently being completed. | This would be an additional field for us with minimum amount of time expended | This is collected via the state data repository and splitting this would require very little work or additional time. | This is collected via the state data repository and splitting this would require very little work or additional time | This information is currently being collected by the recruiter. We may want to try to standardize this field so it has more value across the country. Things like Apple-Picking instead of picking apples should be uniform. If we just send in what we have this requires no additional time. | We do not use free text for our qualifying activities. We have a table that recruiters are allowed to pick existing qualifying activities. If one is not available it can be easily be added to the table. Speaking from an ID/R perspective having this information in a consistent table is helpful for planning and organizing ID/R. That being said either option works for New York. |
| PA | We already collect a phone number, but it’s only a single number per student/family | Not opposed to adding a 2nd number, but not sure assigning it to each parent is the best way and that would require re-working a bunch of things, so it really depends. Preference would be to allow primary and alternate per student/family – would require some programing/training, but annually it would be minimal depending on how implemented | We do not currently collect an email, but we have had requests for it and don’t feel it would be a “burden” to collect -- 20 hours initial for programming and roughly 5 minutes per family recruited each year or < 20 hours per year and well worth the effort. | Probably similar to #3, but again, not sure if best to link to a parent, but maybe two per student/family. | We currently split Graduation vs HSED, so really no burden – just a mapping change for MSIX | We currently split Graduation vs HSED, so really no burden – just a mapping change for MSIX | No burden – already collected on our COE | |
| TX | This information is already collected by LEA or Regional recruiters or data specialists and entered by data specialists into the State database if entering from a paper COE but entered by recruiter if using an electronic COE. Data from the COE is also reviewed by a Designated State Agency Reviewer (one per LEA). | This information would be collected by LEA or Regional recruiters or data specialists and entered by data specialists into the State database if entering from a paper COE but entered by recruiter if using an electronic COE. Data from the COE is also reviewed by a Designated State Agency Reviewer (one per LEA). | This information would be collected by LEA or Regional recruiters or data specialists and entered by data specialists into the State database if entering from a paper COE but entered by recruiter if using an electronic COE. Data from the COE is also reviewed by a Designated State Agency Reviewer (one per LEA). | This information would be collected by LEA or Regional recruiters or data specialists and entered by data specialists if entering from a paper COE but entered by recruiter if using an electronic COE. Data from the COE is also reviewed by a Designated State Agency Reviewer (one per LEA) | This information is already collected by LEA or Regional data specialists and entered by data specialists into the State database. | This information is already collected by LEA or Regional data specialists and entered by data specialists into the State database, but prompt might come from the recruiter when notified by the family | This information is already collected by LEA or Regional recruiters or data specialists and entered by data specialists into the State database if entering from a paper COE but entered by recruiter if using an electronic COE. Data from the COE is also reviewed by a Designated State Agency Reviewer (one per LEA). | We are in favor of Option 1. We concur with the other members on the need for this to be free text. A drop down would be significant work to implement for us as well. Free text is what recruiters use in completing eCOEs. This would not cause a change in burden from what we previously estimated. |
| FL | This MDE would need to be added to our state migratory child database and school district data collection tool. School districts would need to format their student databases to capture this information (if they are not already doing so). Then the district Management Information System (MIS) staff would send batch files with this information to our state database for transmission to MSIX. | This MDE would need to be added to our state migratory child database and school district data collection tool. School districts would need to format their student databases to capture this information (if they are not already doing so). Then the district MIS staff would send batch files with this information to our state database for transmission to MSIX. | This MDE would need to be added to our state migratory child database and school district data collection tool. School districts would need to format their student databases to capture this information (if they are not already doing so). Then the district MIS staff would send batch files with this information to our state database for transmission to MSIX. | This MDE would need to be added to our state migratory child database and school district data collection tool. School districts would need to format their student databases to capture this information (if they are not already doing so). Then the district MIS staff would send batch files with this information to our state database for transmission to MSIX | This MDE would need to be added to our state migratory child database. School district MIS staff could then send batch files with this information to our state database for transmission to MSIX. | This MDE would need to be added to our state migratory child database. School district MIS staff could then send batch files with this information to our state database for transmission to MSIX. | This MDE would need to be added to our state migratory child database and school district data collection tool. School districts would need to format their student databases to capture this information (if they are not already doing so). Then the district MIS staff would send batch files with this information to our state database for transmission to MSIX | a.Option 1: The free text field would provide the best flexibility nationwide, as it allows each SEA to provide very specific information which can then be cross-checked against the activities reported on children’s COEs. This would require typing in the qualifying activities manually, which would take the most time. It would not change Florida’s estimated number of hours needed to report this MDE; I already factored it into what I sent for the MDE burden survey. b.Option 2: The prepopulated selection list could work well for MSIX because, as Dr. Starr mentioned, it would make it possible to run reports. I think the way to do it would be to have two or three list levels, like this: i.Level 1: Industry Select Agriculture or Fishing ii.Level 2: Type of Activity Select Temporary Employment, Seasonal Employment, or Personal Subsistence iii.Level 3: Type of Work 1.For Agriculture: Select one or more of – Crop Production, Initial Crop Processing, Livestock Production, Initial Livestock Processing, Poultry Production, Initial Poultry Processing, Plant Production, Initial Plant Processing, Dairy Production, Initial Dairy Processing. 2.For Fishing: Select one or more of – Catching Fish or Shellfish, Initial Processing of Fish or Shellfish, Fish Farm Production, Fish Farm Initial Processing. Option 2 would probably be a little more complicated to set up, since it would require each district to update its data base with those option levels. But I actually like Option 2 better, since the reports we could run would provide very helpful data that our recruiters can use. Also, once it’s set up, it could prove to be faster to enter the data |
| ID | Currently we only have one phone number collected on the COE and no emails | Many districts collect some of this information; others may not. It would also require a coding change to our state database to add a second phone number and tie phone numbers to a specific parent/guardian and to add spaces to enter emails. I feel that this would really benefit ID&R (especially the phone numbers) and is worth the time spent. | Many districts collect some of this information; others may not. It would also require a coding change to our state database to add a second phone number and tie phone numbers to a specific parent/guardian and to add spaces to enter emails. I feel that this would really benefit ID&R (especially the phone numbers) and is worth the time spent. | Many districts collect some of this information; others may not. It would also require a coding change to our state database to add a second phone number and tie phone numbers to a specific parent/guardian and to add spaces to enter emails. I feel that this would really benefit ID&R (especially the phone numbers) and is worth the time spent. | We do collect HSE and graduation dates and the qualifying activity, so that wouldn’t be a burden at all. | We do collect HSE and graduation dates and the qualifying activity, so that wouldn’t be a burden at all. | We do collect HSE and graduation dates and the qualifying activity, so that wouldn’t be a burden at all. | Option 1 is the only option possible for our state and is what the burden statement was based on. I can’t imagine how we could even do option 2 without an enormous burden and major re-writing of our eCOE system. The list of activities and crops is nearly endless and our eCOE is a free text field to accommodate that. I thought of something else too (surprise!). As far as analyzing the qualifying activities with a free text field, there are some advanced filters that would allow for partial matches so that, while it wouldn’t be as accurate as we could wish, I could filter looking for the keyword for an activity or a crop (e.g. *hops,* *slaughtering*) and I would probably get some useful information. We do teach liaisons to include use “verb+ing noun,” (e.g. tying hops) so there is some consistency that would help us filter or sort a report. |
| CO | Colorado already collects one parent/guardian phone number on its COE. | The additional MDE of Parent/Guardian phone number will be collected by the recruiter during the 2022-23 Performance Period. | Colorado currently does not collect a parent/guardian/self (worker) email address. This new MDE has been added to the state’s COE and will be collected by the recruiter during the 2022-23 Performance Period. This also includes adding the email address information to necessary reports. | Colorado currently does not collect a parent/guardian/self (worker) email address. This new MDE has been added to the state’s COE and will be collected by the recruiter during the 2022-23 Performance Period. This also includes adding the email address information to necessary reports. | The graduation and HSE information are pulled in via webservices from the Department’s Data Pipeline and imported into SMART as reported by the districts. | The graduation and HSE information are pulled in via webservices from the Department’s Data Pipeline and imported into SMART as reported by the districts. | The qualifying activity is already being captured by the recruiter as a required data element on the National COE data qualifying move and work section | In the beginning of implementing SMART, the qualifying activity field was a ‘free text field’. We ran into issues with how users were adding irrelevant information and typo’s. Additionally, Colorado also invoked a character limitation. The solution was standardizing the list with ‘AutoComplete’ functionality. Not quite a Drop Down Menu but typing something in the field that would bring up selectable choices. The standardization for collecting the ‘qualifying activity’ is essentially implemented in SMART today. We already have a table in our database that captures this information. The ‘AutoComplete’ feature for the ‘qualifying activity’ field can easily be modified to a structured Drop-Down List provided by OME. From a code change perspective, Colorado would obviously need to modify all stored procedures to accommodate the changes in the User Interface (UI) and provide a method to transmit this information to MSIX. MSIX will most likely develop some testing criteria in its test environment to prove the concept first and Colorado is including our estimate in our accumulated time. All activities considered, our estimate is 100 hours of development time, as this would be a minor change to our UI. User training and materials, estimate is 40 hours for development and technical assistance. |
| File Type | application/vnd.openxmlformats-officedocument.spreadsheetml.sheet |
| File Modified | 0000-00-00 |
| File Created | 0000-00-00 |