Follow

Introduction and implementation checklist

 

vImplementaiton
In General, the responsibility of implementing KnowledgeNET into a school rests with the school themselves. Dataview will assist by providing training, manuals, implementation plans, guidelines etc, however overall responsibility lies with the school.
 
Likewise, the responsibility for implementing and maintaining the ‘WebSYNC client’ application lies with the school. Dataview will assist by providing manuals, implementation plans and telephone/email support as may be required, but the overall responsibility lies with the school.
When SMS-LMS interoperability is sold to a school, the school needs to be made clearly aware that they will need a competent technical resource to install and configure their WebSYNC client.
 
That technical resource will need to know the following:
-          Where the school’s SMS is located and how to configure it
-          Have administration access to the server on which the SMS is located
-          Know how to download and correctly install applications onto their server including the ‘Java Runtime Environment’.
-          Know enough about the school’s network and internet access to be able to correctly configure WebSYNC with the appropriate internet access details and network proxy settings.
 
If the school does not have this technical resource, then they will need to organize it - as without a technical resource, we will not be able to help set up WebSYNC.
 
Responsibility for SMS
The school is responsible for updating their SMS as required to such new versions as are released by their SMS providers to support SMS – LMS interoperability and/or any bug fixes.
The school is also responsible for understanding how to configure and operate their SMS for initiating SMS - LMS batch transfers.
Any issues with e SMS need to be referred by the Scholl to the SMS provider.
 
Data Integrity in the SMS
The school is responsible for ensuring the integrity of the data in their SMS. Experience has found that at the start of enabling SMS – LMS batch transfers, many issues may be reported with regard to the data held within the SMS. These issues will need to be resolved by the school. (typical issues include missing data eg NSN numbers, or data in the wrong fields etc).  
 
 
 
Dataview’s responsibility is as follows:
 
Assistance with Implementation
Dataview will provide the school’s technical resource with instructions on what is required to download, install and configure the WebSYNC Client application. If the technical resource has any issues, then they are welcome to contact Dataview Support and we will do everything that we can to assist them.
 
Ongoing Monitoring
Dataview will monitor the ongoing operation of WebSYNC and will notify the school’s KnowledgeNET administrator if any errors or unusual events are reported. Part of this notification will include what the school may need to do to rectify the problem or that we are rectifying the problem, liaising with the SMS provider etc.
 
Liaison with SMS Providers
Dataview will work with the SMS providers to try to resolve any problems associated with individual SMS provider. In this case Dataview will keep any schools affected by such a problem updated with resolution progress. However as resolution may involve action by a third party, eg the SMS provider, Dataview make no guarantee as to the quality or timeliness of any such resolution. Dataview may also call on the school to contact their SMS provider directly to potentially help speed up the resolution process.
Liaison with the MoE
Dataview will regularly liaise with the MoE with regard to the ongoing development of the MoE’s SMS-LMS data transfer schema. To this extent, Dataview will certainly be representing the school’s best interests.

To set up interoperability for your school, please follow the simple steps below. We suggest printing out the attached page and following the checklist through from start to finish. 

 

If you have any questions at all please contact KnowledgeNET Support:

Phone: 09 283 7460

Email: support@circle.education

 

We have provided links to help documents from each of the SMS providers, however if you have a specific question about configuring/ setting up the SMS part we would suggest contacting your SMS Support help desk.

 

Allow at least 2 hours to setup and configure both your SMS / LMS and to install and configure WEBSYNC. 

 

Implementation Plan

Step Action Who Date Completed
1 Pre-configuration Checks  IT Technician  
2 LMS Configuration KN Administrator  
3 SMS Configuration SMS Administrator/ KN Administrator  
4 Install & Configure WEBSYNC IT Technician  
5 Initial Data Export & Upload SMS Administrator/ KN Administrator  
6 Review & Monitoring KN Administrator  
7 Generate List of Usernames & Passwords KN Administrator  

 

Roles & Responsibilities

Role Responsibility
IT Technician

School's own technical support person who needs to know the following:

  • Where the schools SMS is located and how to configure it
  • Have admin access to the server on which the SMS is located
  • Know how to download and correctly install applications onto their server including 'Java Runtime Environment'
  • Know about the school's network and internet access to be able to configure WebSYNC with internet access details and proxy settings
KN Administrator School's own KnowledgeNET administrator who has admin rights in KnowledgeNET
SMS Administrator  School's own SMS administrator who has admin rights to their Student Management System

 

Special Notes

 

SMS Version

The school is responsible for updating their SMS as required to such new versions as are released by their SMS providers to support SMS/ LMS interoperability and/or any bug fixes. The school is also responsible for understanding how to configure and operate their SMS for initiating SMS/ LMS batch transfers. Any issues with the SMS need to be referred by the school to the SMS provider. 

Data Integrity in the SMS

The school is responsible for ensuring the integrity of the data in their SMS. Experience has found that at the start of enabling SMS/ LMS batch transfers, many issues may be reported with regard to the data held within the SMS. These issues will need to be resolved by the school. Typical issues include missing data eg NSN numbers, or data in the wrong fields etc.    

 

Dataview's Responsibility

Please contact our help desk if you require any assistance with any of the steps outlined above but please contact your SMS provider for any assistance with Step 3 - SMS Configuration

 

Ongoing Monitoring

Dataview will monitor the ongoing operation of WebSYNC and will notify the school’s KnowledgeNET administrator if any errors or unusual events are reported. Part of this notification will include what the school may need to do to rectify the problem or that we are rectifying the problem, liaising with the SMS provider etc. 

 

Liaison with SMS Providers

Dataview will work with the SMS providers to try to resolve any problems associated with individual SMS provider. In this case Dataview will keep any schools affected by such a problem updated with resolution progress. However as resolution may involve action by a third party, eg the SMS provider, Dataview make no guarantee as to the quality or timeliness of any such resolution. Dataview may also call on the school to contact their SMS provider directly to potentially help speed up the resolution process.

 

Liaison with the MoE

Dataview will regularly liaise with the MoE with regard to the ongoing development of the MoE’s SMS-LMS data transfer schema. To this extent, Dataview will certainly be representing the school’s best interests.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk