Specifications include, but are not limited to: 4.1.1 Respondent must currently have a functioning migrant education data system in place for at least the last two years prior to RFP posting with the capacity to meet the technical specifications. Provide an example of a current functioning respondent system and explanation of how the proposed system meets this specification. 4.1.2 Respondent’s system must be able to collect, store, and report all data on the National Certificate of Eligibility (COE) electronically. More information about the National COE and its’ required data elements can be found in RFP Section 1.2 Definitions and within following web site: https://www2.ed.gov/programs/mep/coepdf2017.pdf. Provide screen shots of respondent’s system that demonstrate examples of respondent’s ability to gather needed COE data. Explain how the eCOE system provides for a data verification workflow customizable to meet the requirements of the Iowa MEP. 4.1.3 Confirm that Respondent’s eCOE system will be able to function even when no internet access is available. This is critically important because data collection will often need to take place at remote locations. 4.1.4 Respondent’s system must be able to collect, store, and report all data required by the Migrant Student Information Exchange (MSIX) and provide a full interface to MSIX. 22 More information about the Migrant Student Information Exchange (MSIX) can be found in RFP Section 1.2 Definitions. Provide examples of some data elements that respondent has uploaded into MSIX in an existing respondent system. Also list the migrant states that respondent works with and describe their success with file submissions. 4.1.5 Respondent’s system must agree to and demonstrate ability to produce all EDFacts files relevant to migrant students. Please see file specifications for years 2016-17, 2017-18 and 2018-19. More information about EDFacts can be found in RFP Section 1.2 Definitions and within following web site: https://www2.ed.gov/about/inits/ed/edfacts/file-specifications.html. Provide screen shots of respondent’s system that demonstrate examples of respondent’s ability to produce relevant EDFacts files. 4.1.6 Respondent’s system must have web-based capability. Provide example of an existing respondent system that is web-based. 4.1.7 Respondent’s system must be accessible via any iOS, Android, or Windows tablet computer.