The purpose of this document is to outline the Business Processes Supported by PASI. These processes have been identified and detailed based on consultation with many stakeholders across the education enterprise within Alberta, including Alberta Education staff, School Authority staff, School Administration, and more.

The processes as outlined do not outline how any one particular organization completes the process, but reflect a generic model of how the process is performed based on the consultations conducted. Any one organization may perform the process in a slightly different manner. These variances should be considered when deciding how to best incorporate relevant PASI Core Services within an organization and/or software product.

In addition, the processes as outlined in this document are not intended to prescribe how a PASI client (e.g. a Student Information System) should implement the process within their software product, but are intended to illustrate the context in which a PASI client would use the services being offered by PASI.

The goal of this section is to outline to the reader when the PASI Core services should be used, by outlining the business processes that should use them. The definition of each process includes:

• A high level description of the process
• A listing of the PASI Core Services used by the process
• A diagram outlining the context in which these services are used in the process
• A listing of scenarios describing the various business scenarios addressed by the process

This process is performed by a PASI Client for the purposes of obtaining updates to information contained within PASI, ensuring information stored within the PASI Client is kept in-sync with the information stored within the PASI Core.

The PASI Synchronization Overview provides an overview of the synchronization model that PASI supports.

This process is performed by a PASI Client when a student registers to be enrolled in their school/authority. The PASI Client uses this process to identify the student, create the student if needed and add a school enrolment.

See Onboard Student for more information.

This process is performed by a PASI Client for the purpose of viewing and maintaining the student's information in the PASI Core.

In general only organizations that are associated to the student are able to do this. For more information refer to Student Association.

See Manage Student Information and Manage a Student's Record for more information.

This process is performed by a PASI Client for the purposes of managing any Core Alerts/Work Items that might have been raised on students that are enrolled in their school/authority.

See Manage Work Items for more information.

PASI uses many common approaches when processing service requests. These concepts are not repeatedly described in each the Service Descriptions, as they are overarching and apply to most (if not all) the services offered by the PASI Core.

These concepts are described in the PASI Concepts and Guidelines section of the wiki.

PASI Business Processes are used to provide insight into the processes and procedures captured that describe how PASI meets the the needs of the various PASI stakeholders (both internal and external to Alberta Education).

These processes are described in the Business Processes section of the wiki.

The PASI Core Service pages outline each of the PASI Core services from a business point of view. Where the Business Processes outline when to use the PASI Core Services, readers of the Service descriptions will obtain an understanding of how to use a particular service, and the functionality implemented by the service.

These Service descriptions do not include the technical details outlining how to connect and call the PASI Core services , but should provide a general overview of the services and how they should be used. This will include the following information for each service:

• A high level description of the service
• A description of the information that is provided to the service as part of the service request
• A listing of the validation rules applied to the request.
• A description of the functionality performed by the service
• A description of the information that is returned in response to the service request
• A list of important requirements placed on the PASI Client that is using the service

Service Data Definitions describe the structure and general formatting rules for the data to be submitted or retrieved from PASI.

Service definitions are available in the Business Objects section of the wiki.

PASI Validation Rules are used to validate the requests being submitted to PASI as well as to validate the data already contained within PASI.

This information is available within the Validation Rules section of the wiki.

PASI Code Classes describe the permissible values that can be used when submitting data to PASI.

All the PASI Code Classes/Values are available in the Code Classes sections of the wiki. The wiki documents the code values that are in the UAT environment.

The processes included in this appendix are available only to PASI Client’s representing Alberta Education (aka the Ministry Client). They have been included for completeness.

These processes are performed for the purpose of managing the Alberta Student Number (ASN) associated to a student. They incorporate the identification and linking of multiple ASNs to a single student, and the retiring of an ASN. They cannot be used to update the information about a student or the student’s enrolment information.

These processes will only be available to PASI Clients who represent Alberta Education (i.e. the Ministry Client):

• Link Secondary ASN to Primary ASN
• Manage ASN Deactivation

This process is performed by a PASI Client for the purposes of providing updated school and school authority information to the PASI Core.

• Manage School and School Authority Data