Implementation of the PASI Usage Agreement


Published on

"Implementation of hte

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Previously: There were islands of information for each school authority and the MinistryNow: PASI central repository/ database facilitates two-way communication and data sharing by schools, school authorities and the Ministry Achieved the a foundational step with respect to technology which is required to move towards education transformation PASI is a single source of truth Student data now coordinated across the enterpriseA process for collecting and sharing student-related data in an on-line, real-time environment that will enhance opportunities to improve program delivery and student access and learning by providing: “The right information…to the right people…at the right time!”
  • Implementation of the PASI Usage Agreement

    1. 1. Provincial Approach to Student Information (PASI)<br />JTC Conference<br />4825 Mount Royal College<br />Calgary, AB<br />Thursday, May 5, 2011<br /> (2:15 – 3:15 PM; Room 75; fv)<br />by:<br />Alec Campbell, PASI Privacy Lead &<br />John Myroon, PASI Communications Lead<br />
    2. 2. Agenda<br />PASI current status and upcoming plans<br />PASI Usage Agreement<br />Boiler Plate security policy<br />SIS vendor update<br />Q’s & A’s<br />2<br />
    3. 3. PASI Current Status & Plans<br />3<br />
    4. 4. September 2010: Current State<br />School Authorities<br />Ministry<br />PASI Shared Data Repository<br />2 Authorities<br />Real-time PASI-enabled<br />Student School Enrolment<br />Student Personal Information<br />400+ authorities <br />Using PASIprep<br /> “The right information…to the right people…at the right time!”<br />4<br />
    5. 5. PASI & the Student Information Roadmap<br />April 2012 – Dec 2013<br />Oct 2013 – Sept 2014<br />April 2011 – Sept 2012<br />Completed<br />PASI Phase 2<br />PASI<br />Phase 3<br />PASI Phase 1<br />Extend Administrator and Student Access interface<br />Course Mark extracts, Diploma exam registration processing;<br /> Statement of marks; <br />Transcripts; Diplomas<br />Course Mark Collection;<br />Course Mark processing; Ministry credentials<br />Student Personal information and Student School Enrolment collection & processing<br />System Integration Projects<br />5<br />
    6. 6. Roadmap High Level Timeline<br />Phase 2– Apr 2011 to Sept 2012<br />PASI – Course mark collection, course mark processing, Ministry Credentials<br />Ministry Integration Planning<br />Phase 3 – April 2012 to Dec 2013<br />PASI – Course mark extracts, DER collections, statement of marks, transcripts<br />Ministry Integration – personal information, enrolment, course marks<br />Phase 4–Oct2013 to Sep2014<br />PASI – Student Information access<br />PASI Program<br />Ministry Integration Program<br />Ministry legacy decommissioning<br />Final warranty<br />Apr 2011<br />Apr 2013<br />Apr 2015<br />Apr 2012<br />Apr 2014<br />6<br />
    7. 7. PASI Phase 2 – Key dates for School Authorities <br />April 20 – May 12 2011-Phase 2 Academic Records Requirements workshops<br />November 2011 – Ministry-led course mark submission workshops<br />December 2011 – Authority-led training for schools and central offices<br />January 2012 – Begin course mark submission using PASIprep<br />7<br />
    8. 8. The Road Ahead…<br />Action on Inclusion<br />Action on Curriculum<br />Inspiring Action<br />Electronic CUME<br />….Completing the foundation to support Education Transformation<br />Road to Transformation<br />Student Disengagement<br />Student Personal Info<br />Student School Enrolment<br /> HS Course Marks<br /> Credentials<br /> Diploma Exam Reg<br /><ul><li>Facilitate student placement
    9. 9. Support teacher lesson planning
    10. 10. Support student-based instruction
    11. 11. Support potential future interoperability to other Ministry systems
    12. 12. (e.g. Children & Youth Services)</li></ul>Diverse learning needs<br />Drop outs<br />2010 2014<br />8<br />
    13. 13. PASI Usage Agreement & Boiler Plate security policy<br />9<br />
    14. 14. Requirement<br />To meet PASI FOIP obligations, each school authority must have a:<br />Signed PASI usage agreement<br />Reasonable security policy and procedures in place<br />10<br />
    15. 15. Why a Usage Agreement?<br />Student data now exposed beyond a single school authority boundary via PASI core, which is the responsibility of Alberta Education<br />FOIP Act requires that parties ensure the collection, use and disclosure of personal information contained in the PASI Core is properly managed and secured<br />11<br />
    16. 16. Information Security Controls<br />PASI Usage Agreement has several components:<br />PASI Usage Agreement body<br />Schedule A: Minimum Security Requirements<br />Security Policy Boilerplate (optional)<br />School Technology Services Framework<br />School authority security controls assessment tool <br />12<br />
    17. 17. Key Requirement – Student Information Systems<br />SIS functions and support for access control measures<br />Ability to provide Alberta Education with SIS vendor contracts and agreements upon request<br />13<br />
    18. 18. Key Requirement – Personal Information<br />Security policies and procedures for:<br />Collection of personal information<br />Use and disclosure of personal information<br />Advise Alberta Education of related breaches<br />14<br />
    19. 19. Key Requirement – Audits<br />Provide Alberta Education access to authority premise, records and computing facilities for investigation or audit purposes<br />SIS creates and maintains audit trails and records to support investigations<br />15<br />
    20. 20. Key Components - Information Security Controls<br />Schedule A based on ISO/IEC 27001:2005<br />Approved information security policy<br />Confidentiality & non-disclosure agreements<br />Defined roles & responsibilities<br />Security controls include any third party delivery<br />Agreements established for exchange of information with external parties<br />Detection, prevention and recovery controls<br />Access control policy<br />16<br />
    21. 21. Key Components - Information Security Controls<br />Continued:<br />Password security practices<br />Secure operating systems<br />Formal policy and security measure related to mobile computing and communication facilities<br />Management responsibilities and procedures to address information security incidents<br />Data protection and privacy reflected in polices, procedures and contractual clauses<br />Compliance checks against security standards<br />17<br />
    22. 22. PASI Usage Agreement<br />18<br />
    23. 23. School Authority To-Do’s<br />Review the draft PASI Usage Agreement to understand requirements<br />Compare the Boilerplate security policy with your own - Are there potential improvements you can make?<br />Ensure future SIS vendor contracts provide for required audit features and access controls<br />Check out the<br />“PASI Community Site” <br />For the draft usage agreement, getting started planning & quick reference guides and security boilerplate template<br /><br />19<br />
    24. 24. Managing Signed PUA Agreements<br />Official notification of availability & need to sign<br />Copy of PUA will be available on Extranet<br />Send signed copy to ABED Info Exchange Services (IES) - manage process<br />IES will: 24<br /><ul><li>Acknowledge receipt of signed PUA
    25. 25. Provide school authority CEO with copy of </li></ul> Ministry & School Authority signed PUA<br /><ul><li>Maintain “registry” of signed PUAs </li></ul>20<br />
    26. 26. SIS Vendor Update<br />21<br />
    27. 27. Vendor Status – Pilot<br />Maplewood current plans<br />Make application changes for year end processes<br />Plan second pilot with a new school authority for September 2011 enrolment submission<br />Rollout PASI-enabled enrolments to remaining school authority clients (Oct 2011 to Feb 2012)<br />22<br />
    28. 28. Other SIS Vendor Activity<br />Pearson <br />Completed high level design; starting development<br />Plan Conformance test for late fall 2011<br />Pilot enrolments starting early 2012 (Edmonton Public, Edmonton Catholic & Peace Wapiti)<br />MIG<br />Start design/development soon<br />Plan to start pilot (Lethbridge #54) early 2012 <br />Other Vendors<br />Starting integration activities<br />PASI receiving inquiries from new small vendors <br />23<br />
    29. 29. School Authority To-Do <br />Understand your vendor’s plans and timelines<br />Determine your authority’s plans to become PASI-enabled (Deadline – Aug 2013)<br />Consider your internal business cycle<br />Consider vendor product readiness<br />Check out the<br />“SIS Vendor Status” <br />On the PASI Community Site <br /><br />24<br />
    30. 30. Questions & Answers<br />25<br />
    31. 31. Questions<br />Please email your feedback on the PASI Usage Agreement or questions before May 26, 2011 to:<br />26<br />