| 1 | | | Is there an expectation that Ed-fi infrastructure will be available, or is this a point to point integration? If it is a point to point, is there a potential future where there is Ed-Fi infrastructure to integrate with? |
| Vendors may propose any solution they believe meets the requirements of the RFP, this could include point-to-point integrations or a platform that integrates source systems. It is not expected that an Ed-Fi infrastructure would be available unless vendors include one in their solution. | 07/12/21 | |
| 2 | | | There is mention about "common API development that is either Ed-Fi compliant or can leverage data inter-operability practices defined by Ed-Fi standards". Is it expected that an Ed-Fi ODS/API will be available at the district for this work? How does this work relate to the TEA TSDS Ed-fi work and the Ed-Fi work being planned by the Texas Region Collaborative? |
| It is not expected that every district would have an Ed-Fi ODS/API available on the timeline of this project. This project is separate from the TEA TSDS work or any other initiatives. | 07/12/21 | |
| 3 | | | Will TEA consider any SaaS-based products via a subscription model or is this expected to be custom all app development given that:
"All intellectual property, including design documents, schema definitions, code and test case documentation will be
property of TEA. All applications, APIs, designs, schema definitions, dashboard configuration, and code must be
considered open source and free for use for Texas school districts, service centers, and the TEA in perpetuity without
restriction." |
| TEA will consider existing products, but is not looking for a licensed solution. The intent of this request for proposals is "Work for Hire" in order to ensure solutions are available to Texas school districts, service centers, and TEA in perpetuity. | 07/12/21 | |
| 4 | | | Hello,
Are you able to grant an extension for submitting this proposal? |
| We have extended the submission deadline to August 6, 2021 | 07/16/21 | |
| 5 | | | Can you elaborate on this requirement?
"Develop and provide documentation and guidance to support application development and maintenance, including guidance for updating applications with Ed-Fi Data Standards and Texas Education Data Standards updates as well as LMS and SIS software updates;"
What does this mean if an Ed-Fi infrastructure is not required? Is the thought that this documentation will provide guidance for modifying the applications to integrate with Ed-Fi and TSDS in the future? |
| The intent of this requirement is to provide guidance for a sustainable method for updating the applications as new versions of the Ed-Fi Data Standards and Texas Education Data Standards are made available. | 07/16/21 | |
| 6 | | | Can you elaborate on this statement under the requirements?
"Common API development that is either compliant or can leverage data inter-operability practices defined by Ed-Fi standards to support scalability and flexibility."
If there is no expectation of Ed-Fi infrastructure being in place for this project, does this mean that the code for this project should be developed in a way that allows for Ed-Fi in the future? Something else? |
| Code for this project should be developed in a way that is consistent or interoperable with the Ed-Fi and Texas Education Data Standards. | 07/16/21 | |