Background & Basics

This is a staging area for material for which JRA3 is fully or partially responsible in the GN4-2 PLM Processes.

Any operational material is available at SA2.

The matrix of responsibilities for transition to production is also at SA2

Process

Processes are documented ad interim on Sharepoint pending update of the PLM site.

Useful Templates/Resources

CBA Word document, customised for JRA3
CBA Payback schedule excel, customised for JRA3
Roadmap template
PID Template - general
Production Transition Templates for Service Definition, Policy and Branding and Operational docs- use as early as is sensible, not just in transition.
GÉANT SD Response SLAs - for inspiration

Subtask to Product Mapping

GN4-2 JRA3 > JRA3 PLM Staging Area > JRA3 developments and services.png

eduGAIN

Target Gate: None. In production.

Main service Documents

NIF:

CBA:

v2 Text and Excel. Document was not formally evaluated by management.
v1 Text. Document is over 4 years old.

PID:

Roadmap: Proposal for eduGAIN versioning

Service Description: GN3plus PLM Version; GN4-2 SA2 Operations Version.

Service Policy: https://technical.edugain.org/documents - Declaration v2, Consitution v2, other supplemental policies inc. CoCo v1.

Service Design Documents:

Branding: Materials

Enhanced eduGAIN support (formally "eScience")

Target gate: Completed transition to production gate. Production launch formally in hands of SA2. Including SP registration.

Task: 2.

Pilot Documents

PID: Draft. To be updated with transition plan.

CBA: Document
, Payback xls To be updated to revise figures/estimates, and add in federation of last resort feature.

Roadmap: Feature in main eduGAIN roadmap.

Service Description: Draft To be updated with fed of last resort feature.

Service Policy: To be delivered.

Service Design doc: Draft in progress To be updated.

Pilot plan:

High level outline as presented REFEDS Nov 2016
KPIS: Section 2.1.4 of CBA. To be revised.

Production gate Documents

PID: PID eduGAIN support Production.docx

CBA: CBA eduGAIN support production v4.docx

Payback schedule: Payback scehdule eduGAIN support Production v2.xls

Service Description and Design: Enhanced eduGAIN Support Production Service Design v3.docx

Customer query process flow: Enhanced eduGAIN support customer query process flow.pdf

Roadmap: Enhanced eduGAIN Support Roadmap.pptx

Transition to service Operational documentation: Use templates at Service Template

To include

OLA:
User support worflows:
Operations requirements: e.g Ops KPIs

Branding/visibility:

Branding simply as eduGAIN support.
No special web presence on innovation required - bundle with overall eduGAIN innovation section.
Visibility - outreach at AARC, FIM4R, REFEDS meetings throughout the pilot period.
Already presented at REFEDS/AARC November/December 2016

SIRTFI

Target gate: Transition to production

Target gate review date: Late 2018.

Pilot being designed.

Task 1.

Documents

CBA:

Roadmap: Feature in main eduGAIN roadmap.

Service Description:

Service Policy:

Service Design doc:

Pilot plan:

KPIS:

Branding/visibility:

Branding simply as eduGAIN supports SIRTFI as BCP.
No special web presence on innovation required - bundle with overall eduGAIN innovation section.
Visibility - outreach at AARC, FIM4R, REFEDS meetings throughout the pilot period.
Plans Already presented at REFEDS/AARC November/December 2016

Cross-sector Interoperability

Target gate: Pilot. Dependency on eIDAS engagement.

Task 3

Documents

CBA:

Roadmap: Feature in main eduGAIN roadmap?

Service Description:

Service Policy:

Service Design doc:

Pilot plan:

KPIS:

Branding/visibility:

Branding simply as eduGAIN Cross-Sector/eIDAS interoperability within eduGAIN.
No special web presence on innovation required - bundle with overall eduGAIN innovation section.
Visibility - outreach at AARC, FIM4R, REFEDS meetings throughout the pilot period.

eduGAIN f-ticks Monitoring

Target gate: Transition to production.

Formal pilot gate not required (AL decision)

Task 1

Documents

CBA:

Roadmap: Feature in main eduGAIN roadmap?

Service Description:

Service Policy:

Service Design doc:

Pilot plan:

KPIS:

Branding/visibility: N/a, a regular eduGAIN feature.

OIDC eduGAIN Profile

Target gate: Design work to continue. Formal gate reviews post GN4-2.

Task 3 + task 1

Documents

CBA:

PID:

Roadmap: Feature in main eduGAIN roadmap, TBD on representing individual roadmap

High level baseline Service Description:

Service Policy:

Service Design doc:

Branding/visibility: OIDC Profile of eduGAIN

Assurance/MFA profile:

Target gate: Design, via REFEDs.

Target date: as per REFEDs.

Task 3

Documents

CBA:

PID:

Service Description: BCP for use of MFA in eduGAIN

Service Policy:

Service Design doc:

Roadmap: Product Output is BCP documents. How to represent?

Branding/visibility:

InAcademia

Target gate: Production

Target date: Gn4-3. Business pilot to be launched in GN4-2.

Task 2

Documents

CBA: Cost Benefit Analysis - InAcademia v5 (7).docx Excel payback schedule is inserted in the Word Document

Roadmap: Roadmap InAcademia for Pilot gate.pptx

Service Description: Section 11 of CBA

Service Policy:

Users and usage
- Customers of this service are all services (merchants) that want to provide benefits to members of the Academic community
- Home institutions support an affiliation validation transaction by InAcademia between an enduser and the services/merchants
- All endusers of academic institutions from GEANT partner federations may use this service
InAcademia Cost and Revenue distribution

Service Design Documents:

Pilot Plan: Draft

KPIS: Section 5 of CBA

Branding: Approved by Karl Meyer, and the trademark for InAcademia successfully registered.

eduTEAMS

Target gate: Production (advanced/single tenant model)

Target date: June 2018

Task 2

Documents

CBA: CBA-eduTEAMSPilot.docx, payback-eduteams-pilot.xlsx

PID: eduTEAMS-pilot-PID.docx

Roadmap: eduTEAMS-Roadmap.pptx

EC Deliverable: Background information

Service Description: Included in EC Deliverable

Service Policy: Source material, in development. Principles outlined in CBA.

Service Design Documents: Market Analysis GN4-1, Functional Architecture ; Technical Architecture ; VM Platform, EC Deliverable GN4-2.

Pilot Plan: eduTEAMS-pilot-plan.docx

Branding: Complete in collab with NA2. Website

Baselined Operational Reqs: Initial consultation w SA2 complete. TBD during pilot.

IdP as a Service

Target gate: Production (toolkit only) end GN4-2

Task 1

Target date for material end April.

Documents

CBA: Draft in progress

Baselined PID:

Baselined Roadmap:

Baselined Service Description:

Baselined Service Policy:

Service Design Documents:

StepUp Assurance/MFA

Target gate: Transition (part of eduTEAMS advanced? Or later?)

Task 2

Documents

CBA:

PID:

Service Description:

Service Policy:

Service Design doc:

Roadmap:

Branding/visibility:

eduKEEP

Target gate: Design. No further PLM work expected as it not a service development.

Task 3

Documents

EC deliverables only. Includes recommendations for adoption/BCP

Discovery

Target gate: Pilot

Task 2

Documents

NIF: Draft

CBA: Draft

Baselined PID:

Baselined Roadmap:

Baselined Service Description:

Baselined Service Policy:

Service Design Documents:

eduroam

Target gate: None, in production.

Task 4

Main Service Documents:

See Production wiki.

eduroam Managed IdP

Target gate: Transition to Production

Target date:June 2018

Task 4

Pilot Documents:

PID: Document

CBA: Document, Payback Schedule

Roadmap:

Roadmap, PLM-style
Roadmap, SW-style (outdated)

Service Description: eduroam Managed IdP (Pilot)

Service Policy: idem, chapter 2 - update with additional eligibility to use as discussed 16/2

Service Design Documents:

Pilot Plan:

basic UAT: validate all steps of workflow
initial signup
manual one user creation
CSV user creation
invitation issuance
installer pickup
eduroam usage
credential expiry /revocation
input regarding various design choices
tracing: how important is it group users across credentials with Chargeable-User-Identity?
product exclusivity: Managed IdP XOR normal RADIUS profiles
import: is the choice "manual" and "import by CSV" sufficient? Which other user upload method would people like?
credential communication: is it okay to leave means of sending invitation token to admin? Shall we implement a "Send by email/Skype/Facebook"?
deadman switch: is this appreciated/its necessity understood? What would be a comfortable interval for participants?
end-user import: is the "one time import password" mechanism understood? If any, what are its UX problems?
OS autodetection: does this work well enough - and do end users "get it" that they should visit the download page with the exact device they want to configure?
re-use of invitations: one invitation, one credential, one device? Or should invitation allow multiple devices, or be good for a certain amount of time for an arbitrary number of devices?
Cost recovery and pricing model - verify the assumptions of required income for sustainability post GN4-2 as per CBA figures. Define a final target price before transition to service.