Archived - System Under Development Audit of Education Information System - Follow-up Report Status Update as of September 30, 2011
Archived information
This Web page has been archived on the Web. Archived information is provided for reference, research or record keeping purposes. It is not subject to the Government of Canada Web Standards and has not been altered or updated since it was archived. Please contact us to request a format other than those available.
PDF Version (37 Kb, 6 Pages)
Action Plan Implementation Status Update Report to the Audit Committee - As of September 30, 2011
Education and Social Development Programs and Partnerships
System Under Development Audit of Education Information System
Approval Date: 11/19/10
| Project Recommendations |
Action Plan | Expected Completion Date |
Program Response |
|---|---|---|---|
1. In consultations with project stakeholders and the Education Performance Measurement Strategy team, assess whether preventive controls can be implemented to mitigate the risks. In particular, consider the following potential activities to manage the scheduling risks:
a. Inserting greater scheduling buffers between key milestones, particularly for data conversion b. Introducing a pilot implementation prior to the single-release go-live or a phased roll-out to identify and address critical issues prior to introducing the system to all users |
The preventive controls recommended by the audit to mitigate scheduling related risks were identified and addressed during the finalization of the EPA Submission. Key related activities during the EPA finalization process included:
|
Status: Request to Close (Completed) Update/Rationale: As of 30/09/2011: All remaining mitigation activities have been completed:
|
|
| Additionally the project will: 1. Develop a data cleansing plan based on the current conversion strategy that details roles/responsibilities, timelines and costs and is signed-off by impacted stakeholder groups |
2011-03-31 | ||
| 2. Develop an implementation strategy based on the current implementation approach that: a. Includes appropriate risk mitigation strategies including the potential to release the solution in iterations b. Includes identification of opportunities to pilot or prototype specific solution components or features, as they become available |
2011-03-31 | ||
| 2. INAC should assess, independently of the EIS project team, whether the EIS system design is strategically (with respect to performance measurement), technologically and economically feasible. The Department should estimate the total cost of EIS ownership based on all business and system requirements and stated outcomes, within a reasonable degree of precision. | The recent completion of the EPA submission and approval by Senior INAC management and the Treasury Board provided the project with a review of technological, strategic and economic alignment. In order to optimize additional review opportunities the project will ensure the two (2) independent validation and verification reviews that have been built into the project schedule include assessment activities to determine if the project is still on track and has adequately addressed the key audit findings.
|
Status: Request to Close (Completed) Update/Rationale: As of 30/09/2011: All remaining mitigation activities have been completed:
|
|
| Additionally the project will undertake the following actions: 1. Update the project forecast and identify project dependencies that can be funded by the Project |
2010-11-30 | ||
| 2. Confirm funding source for remaining dependencies | 2010-12-31 | ||
| 3. Adjust the project plan to accommodate any shortfall related to the funding of project dependency activities | 2011-02-28 | ||
| 3. In conjunction with Recommendation #2, INAC should clearly define what adoption rates and data are required to meet the mandatory requirements and stated business outcomes. Focus should be placed on the ability to collect reliable data prior to designing a system to house the data. Specifically, the performance measurement outcomes and associated timelines should be clearly defined to prevent overspend or rework on a system that cannot be effectively leveraged within a relevant timeline. | The project is actively addressing the ability to collect reliable data and will continue to address the related concerns by: | Status: Request to Close (Completed) Update/Rationale: As of 30/09/2011: All remaining mitigation activities have been completed:
|
|
| 1. Obtaining Departmental approval of Education's Performance Measurement Strategy | 2010-11-30 | ||
| 2. Identifying key success criteria including adoption rates | 2010-12-31 | ||
| 3. Finalizing the current data mapping activities (tracing the availability of data required to support the planned performance measures) | 2010-12-31 | ||
| 4. Finalizing the changes to Data Collection Instrument's required to support EIS performance measurement. Notes: a. The Sponsor recognizes that while data cleansing activities will improve the quality of historical data it is likely that some quality issues will remain and that there will be gaps in the historical information available. b. Additionally, the Sponsor recognizes that some data that EIS will capture in future may not be available at go-live due to dependence on the successful completion of tri-partite negotiations that are outside the project scope.
|
2010-12-31 |