Thank you to everyone who participated and sent us questions during the Campus Update sessions. We have compiled the answers for these queries below. If you have any questions not covered in the topics below. Please do not hesitate to get in touch with us or see us during our next round of Information Sessions in schools.
When is the "Go Live" date?
In February 2020, the SMS Project recommended a delay to the planned go-live date of September 2020. The reason for this delay was due to the impacts of COVID-19. We are grounded in our commitment to ensuring a quality outcome for students and staff, ensuring Western has the capacity to adopt the new solution and ensuring our people have the capability necessary to leverage the new solution effectively. Since this decision, the project team has been working hard on the re-planning of the project and conducting detailed planning for go-live. The project team have identified a revised go-live date of 10th May 2021.
Are we introducing single sign-on?
As part of the implementation of the new SMS we are introducing an industry standard identity management system (an Ellucian variant of “WSO2 Identity Server”, https://wso2.com/library/articles/2017/08/what-is-wso2-identity-server/). This will enable Western to move towards a comprehensive single sign on (SSO) setup, supporting as many applications as possible.
The main challenge of implementing single-sign-on comes from the existing technology much of which does not support standards based SSO. Another difficulty is being able to incorporate the different SSO services available in cloud, such as Microsoft Office 365, Adobe Cloud etc. To achieve this the new Identity service needs to support Federated Identity Services, which WSO2 does.
We still refer to old (paper-based) handbook information to help past students identify what they can be credited for, how can this data be managed?
Options for handbook exploration is underway. This point has been taken into consideration to assure that the new system will handle equivalencies of older versions of units. Once we are provided with more information we will respond to you with more detailed information.
Will everyone have access to Banner? How will security roles be set?
Users will only have access to the systems they require to perform their duties and, within those systems, access will be role based so that what they have access to can be controlled. For example, a student casual at the contact centre will not get access to results in the SMS but may have access to enrolment information to assist students who have issues enrolling. We will be conducting more consultations to get a better picture of what functionalities are necessary for certain stakeholders.
Would the system run in any browser?
Yes. Banner is browser agnostic and in the cloud, so no need for Citrix to run it remotely or in MACs.
Will all existing discoverer reports be kept and replicated in Banner?
We have done extensive work to review the reports that currently reside within Discoverer. That environment has become over complicated and there are a large number of reports that are different versions of one simple report. Over time we will be building a new repository of reports where we can apply filters rather than writing new reports to extract the data.
Will the new Student Management System integrate with existing systems or solutions that currently integrate with Callista, such as library systems, fees and encumbrances, OES systems, TRIM etc?
Yes – unless they are identified for replacement, all systems or solutions that currently integrate with Callista will be integrated with the new Student Management System. Integrations are being reviewed to ensure that current functionality will be maintained or improved when the new system goes live.
More responses for information session queries are currently under review. As more information becomes available, this page will be updated. We will be sending news about this through our monthly newsletter. Contact us for further inquiries or to subscribe to the newsletter.