ITI Project Brief - RSS202 New Network Architecture Impacts

Document Sign-off

  Name                              

  Role

 Date signed off 

  Maurice FRANCESCHI

  Programme Manager

   05/06/20

  David Fergusson

  Service Owner/ Project Sponsor

   05/06/20

  Peter Sanderson

  Project Manager

   05/06/20

  Aaron Turner

  Senior Business Supplier - RSS Systems

   05/06/20

  Mike Wallis

  Senior Business Supplier - RSS Support

   05/06/20

 

The University has a two Projects currently running outside the direct involvement of Research Services:

  1. CIS014 - Network Infrastructure Development; University Core Network Upgrade which has procured hardware, software and services to replace the majority of its data network infrastructure, including the current ResNet network which services the University's residential estate operated by Accommodation, Catering and Events (ACE)
  1. CIS015 - Data Centre Networking; Data Centre Upgrade aims to upgrade the network infrastructure in the University's data centres at JCMB and Appleton Tower. The scope covers the replacement of EOL 1GigE switches and consolidation of others in the data halls. The scope covers all switches, apart from the Brocade 10GigE switches, recently installed at the data centres. The switches in comms/server rooms in secure corridors at AT/JCMB are to be assessed to ascertain if they are in scope. The replacement of switches will potentially be a mix of new and existing, recycled (HP 5130-48) switches to meet budget limitations

 This Project is to conduct a review and provide recommendations and solutions to the impact of these Projects to Research Service Services and Systems to ensure minimum disruption or impact to the Researchers and Users.

Background

Research Service systems are critically dependent on university network architecture and its implementation, for instance using a number of specific VLANs.

This means that potentially any changes to the university network could impact on the RSS services, possibly in unpredictable ways.

Therefore RSS needs to be able to respond to the changes which will result from the immanent refresh of the University network.

As the majority of the hardware that is used to provide Research Service's Services is located in Data Centres, any upgrades to Data Centres may critically impact these Services provided.

RSS therefore needs to be able to react to changes brought about by the planned Data Centre Upgrades.

This Project will:

  • Provide a Full Impact Report on RSS Operations for the proposed implementation of the new Network Infrastructure Development
  • Provide Recommendation and Future Actions that can be implemented to reduce or mitigate the impact to Users during the new Network Infrastructure Development implementation
  • Provide a Plan, in conjunction with the new Network Infrastructure Development Project and implementation plan that could be implemented to mitigate  any circumstances required
  • Provide Reassurance for the User that demonstrates disruption to Users will be nil or minimal during the new Network Infrastructure Development
  • Provide another Full Impact Report on RSS Operations by the proposed Data Centre Networking Project
  • Provide Recommendation and Future Actions that can be implemented to reduce or mitigate the impact to Users during the upgrade of the Data Centre Networking
  • Provide a Plan, in conjunction with the Data Centre Networking Project and implementation plan that could be implemented to mitigate  any circumstances required
  • Provide Reassurance for the User that demonstrates disruption to Users will be nil or minimal during the upgrade of the Data Centre Networking

 

Scope

The following are in scope of this project:

  • All Research Services
  • All Research Services Hardware and Hardware Locations (Data Centres)

Any changes to Scope documented in this Project Brief will be via a Change Request, recorded on the Issue, Change and Decision Logs in the Projects RAIDD xls.

Out of Scope

The following Services are out of scope of this project:

  • N/A

Objectives and Deliverables and Success Criteria

The overarching objectives of this project are to (via the help of various internal 3rd parties):

  1. Provide a Full Impact Report on RSS Operations for the proposed implementation of the CIS014 - Network Upgrade
  2. Provide any Recommendations and Future Actions that can be implemented to reduce or mitigate the impact to Users during the CIS014 - Network Upgrade implementation
  3. Provide a Plan if required, in conjunction with the CIS014 - Network Upgrade project and implementation plan that could be implemented to mitigate any circumstances required
  4. Provide reassurance for the User that demonstrates disruption to Users will be nil or minimal during the CIS014 - Network Upgrade implementation
  5. Provide a Full Impact Report on RSS Operations for the proposed implementation of the CIS015 - Data Centre Upgrade
  6. Provide any Recommendations and Future Actions that can be implemented to reduce or mitigate the impact to Users during the CIS015 - Data Centre Upgrade implementation
  7. Provide a Plan if required, in conjunction with the CIS015 - Data Centre Upgrade project and implementation plan that could be implemented to mitigate any circumstances required
  8. Provide Reassurance for the User that demonstrates disruption to Users will be nil or minimal during the CIS015 - Data Centre Upgrade implementation

All whilst providing the correct levels of support, training and technical documentation.

This will improve deploy-ability, maintenance, functionality, manageability and performance for the users.

The duration of the project is expected to be 6 month from the start of the Project, not the Financial Year or from the Approval and Sign Off of the Project Brief.  This may increase if the other Project Team and information are unavailable.

 

Unless otherwise indicated, the objectives and deliverables are a success when accepted by the Project Sponsor and the Service Owner as listed in the Requirements Success Criteria.

Objective   

Description of the Objective

Success Criteria

Objective 1         

A Full Impact Report on RSS Operations for the proposed implementation of the CIS014 - Network Upgrade

A Full Impact Report on RSS Operations for the proposed implementation of the CIS014 - Network Upgrade

Objective 2

Recommendations and Future Actions that can be implemented to reduce or mitigate the impact to Users during the CIS014 - Network Upgrade implementation

Recommendations and Future Actions are provided that can be implemented to reduce or mitigate the impact to Users during the CIS014 - Network Upgrade implementation

Objective 3

A plan, in conjunction with the CIS014 - Network Upgrade project and implementation plan that could be implemented to mitigate  any circumstances required

An RSS plan that could be implemented to mitigating any circumstances required in conjunction with the CIS014 - Network Upgrade project and implementation plan

Objective 4

Reassurance for the User that demonstrates disruption to Users will be nil or minimal during the CIS014 - Network Upgrade implementation

Reassurance is provided that disruption to Users will be nil or minimal during the CIS014 - Network Upgrade implementation

Objective 5

A Full Impact Report on RSS Operations for the proposed implementation of the CIS015 - Data Centre Upgrade

A Full Impact Report on RSS Operations for the proposed implementation of the CIS015 - Data Centre Upgrade

Objective 6

Recommendations and Future Actions that can be implemented to reduce or mitigate the impact to Users during the CIS015 - Data Centre Upgrade implementation

Recommendations and Future Actions are provided that can be implemented to reduce or mitigate the impact to Users during the CIS015 - Data Centre Upgrade implementation

Objective 7

A plan, in conjunction with the CIS015 - Data Centre Upgrade project and implementation plan that could be implemented to mitigate  any circumstances required

An RSS plan that could be implemented to mitigating any circumstances required in conjunction with the CIS015 - Data Centre Upgrade project and implementation plan

Objective 8

Reassurance for the User that demonstrates disruption to Users will be nil or minimal during the CIS015 - Data Centre Upgrade implementation

Reassurance is provided that disruption to Users will be nil or minimal during the CIS015 - Data Centre Upgrade implementation

Requirements

Requirements are what is required and aligned to deliver the project objectives and deliverables to ensure the benefits recorded are realised.  These are documented in the RAIDD Log on the RTC TAB.

Requirements are set as MoSCoW:

MUST - we would see the project as failing totally or partially if these are not achieved

SHOULD - we have a high expectation that these will be doable with planned work and budget - but if necessary these can be de-scoped

COULD - if all goes very well, these might be possible

WON'T - we want to be explicit about certain things that people might expect us to deliver but we want to be clear we won't deliver

 

Benefits

The benefits to this project delivery are:

  1. Investigation into the New Network Architecture and Data Centre Upgrades will provide Research Services with a clear idea of what the new upgrades/changes are and how they will impact RSS operation
  2. Investigation into the New Network Architecture and Data Centre Upgrades will provide Research Services with recommendations and future actions required to reduce or mitigate any impact from the implementation of new upgrades/changes to the Network and Data Centres
  3. Investigation into the New Network Architecture and Data Centre Upgrades will provide Research Services with a clear idea of the New Network Architecture and Data Centre Upgrades implementation plans and project timescales and how and when they will impact RSS operation
  4. Provide reassurance to Researchers that any impact will reduce disruption to Researchers during the new upgrades/changes to the Network and Data Centres

 

Governance

Portfolio Governance  

Role

Name

Division / Group / Team / College / School and Title

Project Sponsor

David Fergusson

IT Infrastructure Division / RSS / Edinburgh University

Programme Owner

N/A

N/A

Programme Manager

Maurice Franceschi

IT Infrastructure Division / University of Edinburgh

Portfolio Owner

N/A

N/A

Portfolio Manager

N/A

N/A

Service Owner

David Fergusson

IT Infrastructure Division / RSS / Edinburgh University

Project Board

Role

Name                    

Division / Group / Team / College / School and Title

Project Sponsor

  David Fergusson  

IT Infrastructure Division / RSS / Edinburgh University

Service Owner

  David Fergusson

IT Infrastructure Division / RSS / Edinburgh University

Project Manager

  Peter Sanderson

Projects Services / RSS / Edinburgh University

Senior Business Supplier - RSS Systems  

   Aaron Turner 

IT Infrastructure Division / RSS / Systems Team / Edinburgh University  

Senior Business Supplier

- RSS Support

  Mike Wallis

IT Infrastructure Division / RSS / Support Team / Edinburgh University

Tolerances

The following are the tolerances for this project at which point the Project Manager must request approval of the change from the Sponsor and / or the Board via the Change Request process.

Escalating to programme/portfolio manager will be under direction from the Project Sponsor.

 

  Tolerance

  Level

      +/-

   Remarks

  Budget

 £0,000

  £0,000  

   No need for escalation if under  

  Timeline

 6 Month

  1 week  

   No need for escalation if under

  Scope

 As Documented  

1

   Any Change

  Quality /

   Success Criteria  

 As Documented

1

   Any Change

 

Resources Skills and Cost

Initial Resources are were based on a project start up estimate provided and approved at the start of the project:

  • RSS Resource                                 38 Days
  • IT PM                                                 12 Days
  • College/Schools                              0 Days
  • External Development                  0 Days (TBC)

(Subject to change with further analysis and Planning)

  • RSS Resources                               19 Days
  • IT PMs                                                19 Days
  • College/Schools                              0 Days
  • External Development                  0 Days (TBC)

Budget

The total budget calculated for the Project is calculated in the table below with £0k Capital + £0k Revenue.

Budget may need to be sourced further into the Project, subject to analysis findings.

Spending:

Internal

Resource

Required

Expected

Project Cost

Remarks

College / School Resources

- Various Stakeholders

  0 Days

 0 Days

No Project Cost

 

ITI Resources

- David Fergusson

- Aaron Turner

- Jan Winter

- Barry Horne

- Mike Wallis

   0 Days

 14 Days

 12 Days

 12 Days

   0 Days

 5 Days

 5 Days

 3 Days

 3 Days

 3 Days

No Project Cost

No Project Cost

No Project Cost

No Project Cost

No Project Cost

 

User Services

- Data Centre Upgrade Project Team

- New Network Project Team                   

   0 Days

 

 

   0 Days

 3 Days

 

 

 3 Days

No Project Cost

 

Project Services

- Peter Sanderson

- Maurice Franceschi

 12 Days

    0 Days

10 Days

  3 Days

Capital Spend

No Project Cost

 

Totals    

 

50 Days

 38 Days

 19  (RSS)

 

Approved

External

 

Resource

Required

Expected

Project Cost

Remarks

N/A

N/A

    0 Days

     0 Days

£0,000 (R)

Initial + TBC

Totals    

 

    0 Days   

     0 Days   

£0,000 (R)

 

 

Priority and Funding

Priority                                                          - 3 

UoE Funding      Approved                         - £0,000            - (0k Capital + £0k Revenue)

UoE Funding      Required                          - £0,000               - (0k Capital + £0k Revenue)

 

Project Team

Role

Name

Division / Group / Team / College / School and Title

Project Sponsor  

David Fergusson

IT Infrastructure Division / RSS / Edinburgh University

Project Manager

Peter Sanderson

IT Infrastructure Division / Project Services / RSS / Edinburgh University

Senior Business Supplier RSS Systems

Aaron Turner

IT Infrastructure Division / RSS / Systems / Edinburgh University

Senior Business Supplier RSS Systems

Jan Winter

IT Infrastructure Division / RSS / Systems / Edinburgh University

Senior Business Supplier

RSS Support

Mike Wallis

IT Infrastructure Division / RSS / Systems / Edinburgh University

Testing, Contributor

N/A

N/A

New Network Project Team                   

Rick Arnautovic

 

IT Infrastructure Division / Project Services / Edinburgh University

Data Centre Upgrade Project Team

Richard Bailey

IT Infrastructure Division / Project Services / RSS / Edinburgh University

Business Stakeholders

The Project Team consists of the following to be informed at key points (if required):

Role

   Name

   Division / Group / Team / College / School and Title   

Informed    

   David Perry

   CMVM - (IGMM) / Edinburgh University

Informed

   Fraser Muir

   CAHSS / Edinburgh University

Informed

   Victoria Dishon  

   CSE / Edinburgh University

Informed

   Sheila Fraser

   CMVM / Edinburgh University

Preferred Supplier

The Preferred Suppliers are listed below:

  Company  

  Contact  

  Expertise  

  Remarks  

  N/A

 

 

 

Quality of Project and Deliverables / Key Project Milestones

The milestones are a key tool in ensuring that the project process itself is followed as set out by ITI, and that the product deliverables are to the required Quality; the quality for the deliverables are to be confirmed by the respective Service Owner / SME as per the Requirements/Success Criteria table above.

Any changes to major milestones achievements and changes (Initiation, Planning, Delivery, and Closure) will be discussed with the Project Sponsor and Project Team and must be approved by Change Request by the Project Board and WIS as necessary.

The approach for this project outlined by the key milestones below.  A more detailed plan will/has been produced, with the latest on the project SharePoint site:

RSS202 Project Plan_New Network Architecture Impacts

Milestone

Sign-Off means

Date of Milestone

Who signs-off (Accountability)

1. Start Date for Project

-Initial resources and funding approved

-Stakeholders Identified          

-GDPR Assessed Complete

03/02/20

-Programme Manager

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

2. Project Documentation / Website/SharePoint Updating

-Project Website Updated

-Project SharePoint Site folder structure created and Updated

-Project Outlook Folders created

-Project RAIDD started and updated

07/02/20

-Programme Manager

-Project Manager

3. Outline Requirements

-Initial Requirements confirmed, documented and agreed

-Outline plan produced

28/02/20

-Programme Manager

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

4. New Network Infrastructure Development Stakeholder Engagement

-Project Stakeholders to engaged contacted and project deliverables explained

31/03/20

-Project Manager

-Senior Business Supplier Systems

5. Data Centre Networking Upgrade Stakeholder Engagement

-Project Stakeholders to engaged contacted and project deliverables explained

30/04/20

-Programme Manager

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

6. Project Planning

-Outline plan confirmed

-Resources Estimated

-Resources Booked

06/05/20

-Programme Manager

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

7. Produce Project Brief

-Project Brief Approved and Signed Off                                  

-Project Kicked Off with Project Team

28/05/20

-Project Manager

8. New Network Infrastructure Development RSS Impact Assessment

-Information Reviewed and Impacts Recorded / Investigated

16/06/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

9. Produce Network Infrastructure Development Impact ppt

-Covert all information provided by the New Network Infrastructure Development Team to usable information for the RSS Teams

 

08/06/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

10. New Network Infrastructure Development Impact Assessment Review Period

-All Teams provide Impacts found and possible solutions and how and when to implement if required

15/06/20

-Project Manager

-RSS Teams

11. New Network Infrastructure Development Impact Assessment Results Meeting

-Complete Draft Report

-Recommendations

-Actions to carry out if required

-Plan to implement if required

-Communication to RSS and Colleges

16/06/20

-Project Manager

-RSS Teams

12. New Network Infrastructure Development Impact Report

- Final New Network Infrastructure Development Impact Report is produced and Approved by RSS Management

19/06/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

13. Data Centre Networking Upgrade RSS Impact Assessment

-Information Reviewed and Impacts Recorded / Investigated

16/06/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

14. Produce Data Centre Networking Upgrade Impact ppt

-Covert all information provided by the Data Centre Networking Upgrade Team to usable information for the RSS Teams

 

08/06/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

15. Data Centre Networking Upgrade Impact Assessment Review Period

-All Teams provide Impacts found and possible solutions and how and when to implement if required

 

15/06/20

-Project Manager

-RSS Teams

16. Data Centre Networking Upgrade Assessment Results Meeting

-Complete Draft Report

-Recommendations

-Actions to carry out if required

-Plan to implement if required

-Communication to RSS and Colleges

16/06/20

-Project Manager

-RSS Teams

17. Data Centre Networking Upgrade Impact Report

- Final Data Centre Networking Upgrade Impact Report is produced and Approved by RSS Management

19/06/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

18. Acceptance

-Both Reports Accepted

-Overall quality of deliverable is Accepted

-Any outstanding issues has an approved Owner, resolution and plan

02/07/20

-Project Sponsor        

-Project Manager

-Senior Business Supplier Systems

-Senior Business Supplier Support

19. Closure Project

-All Objectives met

-All Project documentation completed

03/07/20

-Programme Manager

-Project Sponsor        

-Project Manager

Assumptions

The Assumptions for this project are that:

  1. CIS014 - Network Upgraded Project will add RSS Dependency to the Project RAIDD and add it to the Requirements of the Project
  2. The RSS Dependency and Requirement will be/have been included in the CIS014 - Network Upgraded Project
  3. CIS014 - Network Upgraded Project Information will made available to the RSS202 Project Manager/RSS Teams
  4. CIS014 - Network Upgraded Project Architecture will made available to the RSS202 Project Manager/RSS Teams
  5. CIS014 - Network Upgraded Project plan and timescales will made available to the RSS202 Project Manager/RSS Teams
  6. CIS015 - Data Centre Upgrade Project will add RSS Dependency to the Project RAIDD and add it to the Requirements of the Project
  7. The RSS Dependency and Requirement will be/have been included in the CIS015 - Data Centre Upgrade Project
  8. CIS015 - Data Centre Upgrade Project Information will made available to the RSS202 Project Manager/RSS Teams
  9. CIS015 - Data Centre Upgrade Project Architecture will made available to the RSS202 Project Manager/RSS Teams
  10. CIS015 - Data Centre Upgrade Project plan and timescales will made available to the RSS202 Project Manager/RSS Teams

Dependencies

The Dependencies for this project are:

  1. The availability of the CIS014 - Network Upgraded Project PM
  2. The availability of the CIS014 - Network Upgraded Project Information
  3. The availability of the CIS014 - Network Upgraded Architecture
  4. The availability of the CIS014 - Network Upgraded Project implementation Plan
  5. For the CIS014 - Network Upgraded Project, the RSS Requirements
  6. The availability of the CIS015 - Data Centre Upgrade Project PM
  7. The availability of the CIS015 - Data Centre Upgrade Project Information
  8. The availability of the CIS015 - Data Centre Upgrade Architecture
  9. The availability of the CIS015 - Data Centre Upgrade Project implementation Plan
  10. For the CIS015 - Data Centre Upgrade Project, the RSS Requirements

Constraints

The Constraints on this project are:

  1. The availability of the CIS014 - Network Upgrade PM
  2. The availability of the CIS014 - Network Upgrade Information
  3. The availability of the CIS014 - Network Upgrade Architecture
  4. The availability of the CIS014 - Network Upgrade implementation Plan
  5. The availability of the CIS015 - Data Centre Upgrade PM
  6. The availability of the CIS015 - Data Centre Upgrade Information
  7. The availability of the CIS015 - Data Centre Upgrade Architecture
  8. The availability of the CIS015 - Data Centre Upgrade implementation Plan

Previous Lessons Learned

The project manager will ensure that a Lessons Leaned Log is created, maintained and reviewed by the project team at every team meeting.  The following are Lessons Learned from the ITI Projects SharePoint and team’s previous experience:

  1.  N/A

Risks

The project manager will ensure that a Risk Log is created, maintained and reviewed by the project team at every team meeting; ensuring project owners update their risks at least once a month or more as appropriate to the project.

The initial Risks highlighted are:

  1. Project Delay - Due to Strike Action, there may be a lack of resources
  2. Project Delay - Due to BAU or other project work, there may be a lack of resources
  3. Project Delay - Due to not being able to secure the Network Infrastructure Development Project Team Time/Resource
  4. Project Delivery - Due to Network Infrastructure Development Information, Architecture and Implementation Plan not being available
  5. Project Product - Due to BAU or other project work, the Resources have not been available to Complete or Approved the Project Brief
  6. Project Delay - Due to Data Centre Networking Project Team Resources not being available
  7. Project Delay - Due to Data Centre Networking Upgrade Information, Architecture and Implementation Plan not being available

Issues

The project manager will ensure that an Issue Log is created, maintained and reviewed by the project team at every team meeting.  The following are Lessons Learned from the ITI Projects SharePoint and team’s previous experience:

  1.  N/A

Communication

The project manager will also ensure all changes to cost/timeline/scope are recorded in the issue log, and reflected in milestones log, budget and estimations, and the project Scope Change log.

 

Project Sites - There are two Project Management Sites for the project:

  1. Project Web Page: Project information for all to see, with the Logs being restricted by the project manager to the required project members:

                                New Network Architecture Impacts Website

  1. Project SharePoint Site: Project information repository for project members only, mainly used for storing documents to enable a single source for updating and completing:

                                New Network Architecture Impacts SharePoint

Stakeholders - The project manager will produce a Stakeholder Map and complete a Stakeholder Engagement Grid; which will be agreed at the Kick-off meeting and reviewed and maintained during the project life cycle.

Communication Plan - The project manager will produce a Communications Plan for the project and ensure all parties understand the communications routes and timescales. This will also be agreed at the Kick-off meeting and cover the headings in this section.

Meetings - The Project Team Meeting Agenda template will be used to record all meetings and saved to the Project SharePoint Site:

  1. Project Board Update Meeting                                      On request or issue
  2. Project Sponsor and Project Manager Meeting      Weekly
  3. Project Team Meeting                                                        Weekly

Reporting -

  1. ITI Project Monthly Report                                             Monthly
  2. Project Sites                                                                          Weekly
  3. Project Logs                                                                          Weekly

Escalations - Project Escalations will be directed to the Project Manager, who will document the escalation as a Risk/Issue then escalate via the appropriate Governance level:

  1. Escalate area SME
  2. Project Team
  3. Project Board – Project Sponsor
  4. Programme Board – Programme Manager
  5. University

 

Run / Grow / Transform

This project is to help Transform and improve the Services and Support for RSS Systems Team and all Users.

 

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

Alignment with Strategic Vision  

Guidance (please remove)

This project will deliver benefits, change and innovations in alignment with the IS Strategic Vision and the University's Strategic Vision for 2025. ** Check the Annual Plan on ITI Sharepoint to see how the project's deliverables and benefits have been aligned to Run/Grow/Transform and the Strategic Themes **

IS Strategic Vision the main elements of the vision that this projects contibutes to are highlighted in bold.

Student Experience

Commentary
Student experience and the unique Edinburgh offer  
Online and distance learning leaders  
Library national and international leadership  
   

Research and Innovation

 
Research IT and Data Sciences  
Innovation  
Collaborative leadership  and social responsibility  
   

Service Excellence

 
Process improvement, efficiency, quality and best practice  
Long‐term IS strategic planning and linked professional services  
Information Security  

 

University's Strategic Vision for 2025 the main elements of the vision that this projects contributes to are highlighted in bold.

Vision Themes Commentary
A unique Edinburgh offer for all of our students  
• all of our undergraduates developed as student/ researchers with clear, supported pathways through to Masters and PhD  
• all our students offered the opportunity to draw from deep expertise outside their core discipline  
• a highly satisfied student body with a strong sense of community.  
   
Strong and vibrant communities within and beyond the University – making the most of our unique offer of world-leading thinking and learning within one of the world’s most attractive cities  
   
A larger, more international,staff who feel valued and supported in a University that is a great and collegial place to work, develop and progress  
   
More postgraduate students – underpinned by the best support in the sector to ensure we attract the brightest and best regardless of ability to pay  
   
   
   
A strong culture of philanthropic support focussed especially on our students and on outstanding research capabilities.  
   
Many more students benefiting from the Edinburgh experience (largely or entirely) in their own country – supported by deep international partnerships and world- leading online distance learning  
   
Sustained world leading reputation for the breadth, depth and interdisciplinarity of our research supported by strong growth in research funding and strong international partnerships – drawing from well-established and less well developed sources

 

   
An estate that matches expectations, responds flexibly to changing student and staff needs, and showcases the University

 

   

A deeper and earlier collaboration with industry, the public sector and the third sector – in terms of research; knowledge exchange; and in giving our students the best possible set of skills for their future

 
   

 

 

Digital Transformation Commentary
Describe how the changes this project delivers will contribute to the digitial transformation of the Service                               

 

 

IS Change Programme - How will this project's Deliverables and Benefits promote the Themes  

Guidance (please remove)

Indicate if the project deliverables and benefits contribute to the themes with the IS Change Programme.

 

IS Change Programme Theme How the project deliverables and benefits contribute to change
Project Management  
Working Together  
Standards and Technical Leadership  
Staff Learning and Development  
Service Based Culture  
Equality and Diversity  
Partnerships and Philanthropy  
Flexible Resourcing  
Communication and Branding

 

 

Service Excellence - Information and Security

 

Guidance (please remove)

Are we using standard builds for the project (that is, pre-validated security controls will be in place for infrastructure and data)? Or Do we anticipate having to develop non-standard infrastructure?

Will we have third party integrations on installations?

Are we dealing with data outwith our standard set of controls?

If so, What level of risk is associated with the data? What are the appropriate controls?

The project must outline how it is dealing with risk, how the need to design/build/test impacts on project scope, budget and timeline.

Confirm which University or divisional polices are providing guidance here.

Set Security design, execution and acceptance as a Deliverable Quality Assurance

Create a Security Milestone for Delivery - and Design, Build and Acceptance depending on project complexity - that must be signed-off by Project Manager and Section Head.

Create any specific risks around security

 

 

Service Excellence - Process Improvement, efficiency, quality and best practice (Social Responsibility and and Sustainability)

Guidance (please remove)

If the project could or will lead to recycling of hardware then Create a milestone called 'Recycle - Engagement' so that the project can engage with the Department for Social Responsibility and Sustainability at the appropriate time

Add a Benefit to the ITI Benefits Management and Realisation log (ITI Projects Sharepoint)

Is there an opportunity to take advantage of the Green IT Initiative for further funding?

Otherwise set as Not Applicable.

 

 

Digital Transformation

Guidance (please remove)

Indicate if and how the project itself is contributing to Digital Transformation.

WiIl it use available resources or funding specific to the initiative? e.g. using the services of the ISG Usability Team, applying for Digital Transformation funding.

Are we using new techniques or tools or processes in this project that can be used to transform how we work in general?

 

 

IS Change Programme - How will the execution of this project promote the Themes

Guidance (please remove)

Indicate if the project itself (during plan, execution, implementation) contributes to the themes with the IS Change Programme.

Some expectations and suggestions from ISG Directors - what to think about for each them when planning the project   some_expectations_and_suggestions_from_isg_directors.pdf

 

IS Change Programme Theme How the project process will contribute to change
Project Management  
Working Together

 

Guidance (please remove)

Will the project team talk to other colleagues across IS?

Can they bring previous experience and fresh thinking to the project?

Add working together to your Communication Plan - go beyond the stakeholders.

How will you raise awareness of the project with your colleagues across the divisions?

Might you work closer - co-locate, for example?

Could the processes involved in the project itself be improved - what is difficult to do? Is the Admin cumbersome, time-consuming?

Add to the Closure Report.

Look to guidance from the IS Change Management team on how to approach this.

 

 

Standards and Technical Leadership  
Staff Learning and Development

Guidance (please remove)

Is there an opportunity for the project to offer development opportunities for colleagues?

Could someone from another team in our division or another ISG division be seconded to the project to provide skills we may be struggling to find in this period?

Can we offer a development opportunity for someone in our division at a lower grade - to come into our project and be skilled up, fulfil a higher grade role for a while?

For planning, make sure you allow the necessary time to engage / recruit in your project, and feed back to the annual plan/forward look?

 

 

 

Service Based Culture

Guidance (please remove)

Are we helping the service to shift-left? For services impacted by the change we are delivering : check the Service Catalogue (due for 2016/17) for Service Owner and Service Operations Manager. Confirm with them who should be stakeholders on the project. Also check with head of IS Helpline. Confirm at what stages if the project SO/SOM want representation and sign-off - especially around Design and UAT and Delivery. Do we need a Handover? Add Stakeholders to these Milestones. Is there a CMDB entry to update to reflect changes?

 

 

Equality and Diversity

Guidance (please remove)

Planning: Discuss the Project Board, project team and key stakeholders with your Sponsor - do the groupings reflect/promote diversity?

Be aware of particular periods or dates that may conflict with religious or social or domestic obligations.

Design: Are we designing a User Interface? Are we designing with best practice in Usability and Accessibility for all devices?

Please explicitly ensure that the Design of the UI has been checked for promotion of Equality and Diversity. e.g. Use 'Mx' in the Honorifics section- - but do we even need honorifics - how much information do we actually need to collect from a user?

Does our interface make assumptions about the kinds of people our users are?

Do we accommodate people who are at a distance, working flexibly, may not wish to be identified by gender, race, age or show a photo?

Do we give options as to what services users might want or do we assume they will want what we want, or what users have wanted in the past?

Are we being creative in thinking about use cases beyond the metrics and other ‘evidence' we have for users in the past - not simply recreating/perpetuating old ways of working? How are we naming a Service (or even Hardware) ?

Consider a naming convention to highlight or promote Equality and Diversity.

Do we have the opportunity in this to promote role models or show our understanding of diversity?

Would this give us an additional route for comms or stakeholder engagement? e.g UCL named their HPC ‘Grace’ https://www.ucl.ac.uk/isd/news/isd-news/research-it/introducing-grace which gave them an added ‘good news story’ and a chance to dispel myths that there are no women in computing.

Quality Assurance: Add a Design Milestone and a separate Milestone for Acceptance Sign-Off.

The Design Milestone confirms that the UI has been checked for promotion of Equality and Diversity, and that we have designed an inclusive UI.

Add to the Design Milestone, or better, create a separate Usability Milestone for Design and QA.

There must be a separate EqIA Milestone to show that this has been done.

Ensure that appropriate authority is signing off on the legal aspects of Equality and Diversity.

 

 

Partnerships and Philanthropy

Guidance (please remove)

Does/can/might this project promote or leverage partnerships?

Are there any philanthropic aspects around the execution of this project - are we providing free resources or software, for example?

 

 

 

Flexible Resourcing

Guidance (please remove)

Have we considered contract staff, students and interims (and in future, apprentices)?

Can a difficult resourcing situation be resolved by use of fixed term staff or limited secondments?

For planning, make sure you allow the necessary time to engage / recruit in your project, and feed back to the annual plan/forward look.

 

 

 

Communication and Branding

Guidance (please remove)

Communication: Ensure that you have a session as part of planning for Stakeholder identification and analysis.

Set out the communication plan by the end of the project brief - or set a milestone date for when you will have this in place if end of planning not possible.

Project Manager is the accountable person and will sign-off the milestone.

 

Branding: Are you delivering a new Service or significantly upgrading a new service?

If so, then the project team must engage with the new Branding guidelines and Change Management Theme team for ISG, the branding for the school or college via the college marketing team, the University's Comms and Marketing team - potentially all of these.

Use gel.ed.ac.uk to access assets and guidelines for branding of communications, websites, mobiles.

Use the Student Digital Guidelines.

 

Quality Assurance: A milestone must be created for Branding and the Project Manager must sign-off as the accountable person.

 

 

 

 

 

Project Sponsor – Project Responsibilities

The sign-off milestones are associated with specific responsibilities of the Sponsor role .

Guidance (please remove)

This sets out the Sponsor responsibilities on this project - please review and amend as appropriate for this project and agree with Sponsor

Start of project – Explicitly Included in the Initiation Milestones Sign-Off

  1. Negotiates and confirms funding for the project
  2. Ensures the project is in line with organisational strategy and priorities
  3. Chairs the project board, appoints its members and ensures they are effective
  4. Advises the project manager of protocols, political risks, issues and sensitivities
  5. Makes the project visible within the organisation  

End of Planning – Explicitly Included in the Planning Milestone Sign-Off

  1. Works with the project manager to develop the Project Brief
  2. Ensures a realistic project plan is produced
  3. Sets tolerance levels for escalation to themselves and to the project board
  4. Ensures that project team have representation and engagement from users and suppliers
  5. Helps identify Stakeholders
  6. Approves Communication Plan
  7. Agrees on frequency of meetings with Project Manager
  8. Agrees of frequency of meetings with Project Team
  9. Agrees on milestones and who signs-off

 

Execution – ongoing

  1. Provides strategic direction and guidance to the project manager as directed by the Board
  2. Approves changes to plans, priorities, deliverables, schedule
  3. Encourages stakeholder involvement and maintains their ongoing commitment
  4. Chief risk taker
  5. Makes go/no-go decisions
  6. Communicates change in organisational structure, priorities, business benefits or funding
  7. Helps the project manager in conflict resolution
  8. Helps resolve inter project boundary issues
  9. Gains agreement among stakeholders when differences of opinion occur
  10. Assists the project by exerting organisational authority and the ability to influence  

Delivery – Explicitly Included in the Delivery Sign-Off

  1. Ensures that Service is ready for change

 

Closure - Explicitly Included in the Closure Milestone Sign-Off

 

  1. Helps with publicity for the change delivered
  2. Ensure that benefits will be managed, measured and realised post-project
  3. Evaluates the project’s success upon completion

Project Info

Project
New Network Architecture Impacts
Code
RSS202
Programme
ITI - Research Services (RSS)
Management Office
ISG PMO
Project Manager
Peter Sanderson
Project Sponsor
David Fergusson
Current Stage
Close
Status
Closed
Project Classification
Transform
Start Date
03-Feb-2020
Planning Date
06-May-2020
Delivery Date
01-Jul-2020
Close Date
03-Jul-2020
Programme Priority
3
Overall Priority
Highest
Category
Discretionary