The project team will:

• Audit all equipment connected to the network before the work starts in each building, so they can ensure everything is connecting correctly.
• Ask your local representatives to check that they have the details of every device that may require individual attention.
• Prepare lists of all devices showing as connected to the network for each location. They will send these lists to local building or site representatives. Local representatives will check their lists and add any other devices that need to be reconfigured to connect to the network.

Other categories of equipment may require updating individually.

The project team will arrange these so users won’t need to do anything. These include, but are not limited to:

• printers,
• laboratory equipment,
• faculty-based servers,
• and computers linked to equipment or in clusters.

As this will all be done remotely, there will be no service impact.

During this stage, if a device requires reconfiguration this will be done remotely where possible.

On the first day, devices will be switched automatically from the use of static IP addresses to DHCP.

• This may cause a minor disruption of up to 5 minutes for a few users.

Some devices may need to be reconfigured by colleagues from IT Services, or by third-party suppliers. This will be discussed with local representatives.

The local representative will then ask the person responsible for the device to check with that their device has been tested to ensure it is connected correctly, and then report any issues.

Upon local confirmation that everything is working as expected, the project team will notify key contacts at each site that the work has been completed.

From this point any issues arising would be managed by the IT Support Centre.

If you have a managed Windows laptop or desktop the interruption will be minimal. Most users won’t experience any interruption to services as the changes are implemented.

• However, there may be a delay of a few seconds whilst the devices obtain their new IP addresses, though in a few instances it could be for up to five minutes.
• Some faculty and laboratory-based networking equipment and servers may need to be reconfigured.
• Communications about IP address changes with third party equipment providers will be a collaboration between the faculty, the project team and the third party.
• External partners linking into University devices will need to be notified by device owners about the IP address change.

• The project team will work with colleagues in the following service areas to ensure minimal interruption to service:
  • Building Management Services
  • CCTV
  • Door Access Control
  • Printers

Starting six weeks prior to prospective start dates, the project team will begin a staged communications plan for each site to ensure all stakeholders are consulted and kept up to date throughout.

Communications will include:

• Discussions and consultations with delivery partners and key contacts in buidlings, sites and services affected,
• Direct emails for key contacts to cascade for colleagues in buildings, sites and services affected,
• Webpage information, including schedules,
• StaffNet and faculty newsletter articles.

Network Transformation involves:

• Moving the University network to private IP (internet protocol) addresses across the entire estate, from the publicly accessible IP addresses currently in use.
• Moving devices from the use of static IP addresses to DHCP (Dynamic Host Configuration Protocol) issued addresses.