This page contains service description outlining how and where service should be used, targeted users, service delivery model and service elements and topology. RESPONSIBLE: Information provided in this page is initially populated by the development team (during the transition phase), and revised based on the need or in a yearly service check by service_name Service Manager, with exception of CBA which remains the responsibility of business development team. |
Service Description
eduroam Managed SP enables eligible institutions to outsource the technical setup of the roaming uplink functions in an eduroam SP to the eduroam Operations Team. eduroam SP administrators use the service instead of a local RADIUS infrastructure. A unique selling point of this service is that the typical limitation of being required to have a static IP address is waived - eduroam SP Wi-Fi infrastructure can be managed by the system even on IP connectivity with changing IP addresses (e.g. DSL, mobile networks).
The service includes:
- web-based user management interface where eduroam SP deployment details can be created and deleted;
- web-based institution management interface where institutions are enabled or disabled to use the service;
- technical infrastructure ("RADIUS") which accepts RADIUS/UDP requests independently of client IP addresses, processes them according to eduroam Service Definition best practices, and forwards them to eduroam IdPs via the established eduroam roaming infrastructure.
The aspects of eduroam SP operationm beyond the RADIUS uplink remain in the responsibility of the eduroam SP administrator, and are subject to the eduroam Service Definition as usual. This includes (but is not limited to) local logging of IP leases to MAC addresses in the Enterprise Wi-Fi session, having sufficient Wi-Fi coverage, and making sure the IP uplink works within expected parameters.
Users
Add definition of who are the targeted users, estimate about possible number of users etc.
Contacts
All operations, business development and stakeholders contacts
| Service Manager | Deputy Service Manager | L1 support | L2 support | L3 support |
|---|---|---|---|---|
Service Delivery Model
Add explanation about organisation of service delivery
Service Elements
Service Elements, with brief descriptions (or links) to products, resource types or instances and technical components or software stack, and indications of their types - if they are developed internally (in-house), OSS, or commercial off-the-shelf products or software. Service elements are grouped in two categories:
Technology Infrastructure
Add list and description of products and resources used to deliver main functionalities of the service. Add service technical architecture - i.e. it is good to have a conceptual architectural diagram and topology diagram.
Supporting Infrastructure
Add list and descriptions of products and resources used to deliver supporting services such as specialized monitoring and measuring systems, configuration management system, issue/request (ticket) management system, reporting system, etc.
Cost Benefit Analysis (CBA)
Provide URL to the last valid CBA.