| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

NANSLO RDN Management Model

Page history last edited by ron.evans@nic.bc.ca 11 years, 9 months ago

Return to Sustainability Model

Return to Potential Business Model

 

NANSLO RDN Management Model

(RDN = RWSL Distributed Network)   

 

This page defines a proposed governance model for the NANSLO RDN.

 

Transitional Oversight Council (TOC):

The TOC will be made up of 1 representative each from the original NANSLO partners; WICHE, CCCS, BCcampus.  The TOC will oversee the transition from the NANSLO project to the NANSLO RWSL Distributed Network (RDN).  Once the NANSLO Board and other governance structures are in place and functioning the TOC will disband and WICHE, CCCS, and BCcampus reps will become part of the NANSLO Board.  This will probably be a 1 to 2 year transition.

 

NANSLO Board (NB):

The NANSLO Board is the primary governing body of the NANSLO RDN.  It is made up of one representative from each institution that is hosting at least one RWSL node.  The NANSLO Board will make all pecuniary decisions for the NANSLO RDN.  The NANSLO Board employs the RDN Coordinator, who will carry out the decisions of the NANSLO Board.  The standing sub-committees of the NANSLO Board will be the RWSL R&D and Technical Standards Committee, the NANSLO Finance Committee, and the various Discipline Panels (These are defined below).  Based on recommendations from its standing committees and constituent participating institutions the NANSLO Board will determine the Policies and Procedures required to implement and maintain a robust responsive NANSLO RDN.  They will also be the final arbiter of which labs will be developed for RWSL mediation based on input from the standing committees.  The NANSLO Board may strike other ad-hoc committees as required and define their terms of reference.

 

RDN Coordinator: This person will be an employee of the NANSLO Board and answer directly to them.  His/her job will be to implement the directions of the NANSLO Board and manage the NANSLO RDN on a day-to-day basis.  In addition to administrative skills this person will also have enough technical skills to understand and direct over-all technical aspects of the NANSLO RDN.

 

NANSLO Finance Committee (NFC):

The NANSLO Finance Committee will be a sub-committee made up of NANSLO Board members.  It will track the budgetary state of the NANSLO RDN and recommend on financial matters.  It will also be tasked with tracking and recommending funding opportunities to the NANSLO Board.

 

RWSL R&D and Technical Standards Committee (RTC):

The RTC reports to the NANSLO Board and will be made up of an RWSL Tech representative from each RWSL serving institution.  The RTC will recommend to the NANSLO Board the technical standards that all RDN participants will adhere to so that RWSL node hardware, software, and labs are shareable and compatible across the entire NANSLO RDN.  This will also include the technical specifications of the scheduling solutions that will be adopted.  The RTC will also oversee the RWSL Tech and User Support Network and receive feedback from them.  Based on input from the various Discipline Panels, the RTC in consultation with the Discipline Panels will recommend to the NANSLO Board which labs will be developed for RWSL mediation.

 

RWSL Tech and User Support Network (TUS Network): This network will be made up of RWSL techs from RWSL serving institutions and will share expertise across the entire NANSLO RDN.  The TUS Network will report to the RTC.  There will be 2 levels to this network; a network for techs supporting techs, and a help desk to support RDN users.  All RWSL Techs will be supplied with modern internet communications services so that there can be continuous communications between various RWSL Techs in real-time.  This will facilitate the day-to-day operations and problem solving required to operate the NANSLO RDN.  The members of the RTS Network will have ready access to RDN Scheduling and be able to re-route student usage on the fly should a particular RWSL node go down unexpectedly thus making the NANSLO RDN a robust remote lab sharing service.


Discipline Panels (DP)

The DPs report to the AB.  There will be 1 DP for each discipline that will utilize RDN services.  Initially this will be a DP-Physics, DP-Biology, and DP-Chemistry, but additional DPs can be created as other disciplines begin using RDN remote lab services.  The DPs are made up an academic discipline representative from each participating institution, including those institutions that are strictly RDN service consumers.  The DPs will review the pedagogical implications of remote labs and recommend learning outcome standards, so that courses using remote labs and the individual labs will be of high academic quality and have the highest probability of achieving and maintaining accreditation.  The DP from each discipline will also, after consulting with the RTC, recommend to the NANSLO Board which new RWSL mediated labs should be developed.  This process will be something like the representatives of a DP will bring their suggestions on which new RWSL mediated labs they would like to see developed.  After coming up with a detailed list of proposed labs they will consult with the RTC to find out the technical implications of each desired lab and the cost of development.  Using this information they will develop a short list that they will recommend to the NANSLO board.  The NANSLO Board will look at budgetary constraints and other factors and then approve the development of those labs that will meet criteria that they will develop and update from time to time and that meet budgetary constraints.

 

Peer-to-Peer Exchange

This will be a forum where all NANSLO RDN participating institutions can discuss academic matters relating to NANSLO RDN remote lab services.  All participating institutions and their faculty may participate.  This form will be monitored by members of the discipline panels.

 

NANSLO RDN Serving Institutions (or just "Serving Institutions"): 

These are institutions (schools, colleges, universities, etc) who host at least 1 RWSL node that serves remote lab services to the NANSLO RDN at some minimum level (to be established by the NANSLO Board).  Serving Institutions can supply representatives to all NANSLO RDN governance bodies and functions.

 

 

NANSLO RDN Participating Institutions (or just "Participating Institutions"): 

These are institutions (schools, colleges, universities, etc) who consume or serve remote lab services via the NANSLO RDN.  Participating institutions that are not Serving institutions will have representation on the Discipline panels.

 

 

So what have I missed?  What needs to change?  Will something like this work do you think?

 

See NANSLO RDN Services and Advantages for participating Institutions.

 

Document End

---------------------------------------------------------------------------------------------------

Input: Everyone, please insert anything you think I should include or any pertinent comments in the comments at the bottom of this document.  I will incorporate them into this section when I write it.  Thanks!

-----------------------------------------------------------------------------------------------------

Hi Ron, I haven't been able to recreate my table in the comments below so I am including a link here. ~Gina

 

From April Meeting:

Might be useful to have a nonprofit organization represent NANSLO to funnel donations, manage the admin and centralized scheduling.

Need to standardize things but allow growth.

Need to build international scheduling system that coordinates/pools needs and availability, (security of access & integration with LMS). CCCS building their own in house. NIC could potentially adopt and modify for own use. System needs to locally manage scheduling with excess capacity to go up centrally for access.

NANSLO needs R&D Development – development environment & developer, create new labs, multiple Albert’s linked to discipline panels, standards, conduct research      

Could have an annual/biannual Conference

NANSLO needs Management/Admin/Coordination (WICHE)

- director

- Admin

- Web site/PR

- Financial budgeting

- Grant writing & opportunities

- Membership development

- Systems development – scheduling, transactions

- Communications infrastructure – tech team, discipline panels

NANSLO Board will have subcommittees

- standards committee (technical/configuration)

- support committee

- discipline panel chairs

 

 

 

Comments (1)

Gina Bennett said

at 10:16 am on Mar 13, 2012

This model (above) looks pretty good but I'm thinking that maybe if we were to draft out the PROCESS & come up with a list of what needs to happen over an annual cycle within NANSLO, it might help us envision the various roles that would be needed. I have come up with a rudimentary table to detail what needs to happen to support NANSLO activities over the year but couldn't paste it in the comments section so I have included a link above.

You don't have permission to comment on this page.