| Table of Contents |
|---|
...
Background & Basics
This is a staging area for material for which JRA3 is fully or partially responsible in the GN4-2 PLM Processes.
...
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
eduGAIN
Target Gate: None. In production.
...
- v2 Text and Excel. Document was not formally approved evaluated by management.
- v1 Text. Document is over 4 years old.
...
Service Design Documents:
Branding: Materials
...
Enhanced eduGAIN support (formally "eScience")
Target gate: PilotTarget review date: Feb 13Completed 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
Enter transition gate:
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
Exit transition gate:
Transition roadmap: eduGAIN Enhanced Support - Transition Timeline
CBA: CBA eduGAIN support - for production gate.docx
Roadmap: eduGAIN Support Roadmap - for production gate.pptx
Operational documentation:
- Support workflows manuals and documentation, including proactive and reactive: eduGAIN Support Manuals
- The team staffing and rotation: eduGAIN Support Staffing and Rotation
...
- Branding simply as eduGAIN support - address added at the https://edugain.org/contact/ and https://technical.edugain.org/contact
Branding/visibility:
- The support contacts were published in the redesigned pr and technical web sites: https://edugain.org/contact/ and https://technical.edugain.org/contact
- 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.
...
Cross-sector Interoperability
Target gate: Pilot. Dependency on eIDAS engagement.
Task 3
Documents
CBA:
Roadmap: Feature in main eduGAIN roadmap?
...
- 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: ProductionTransition to production.
Formal pilot gate not required (AL decision)
Task 21
Documents
CBA:
Roadmap: Feature in main eduGAIN roadmap?
...
Service Policy:
Service Design doc:
Operational RequirementsPilot plan:
Operational Docs:
...
- KPIS:
...
Operational Processes:
User Support:
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
...
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: PilotProduction
Target date: Material ready jan 23Gn4-3. Business pilot to be launched in GN4-2.
Task 2
Documents
CBA: (GN4-1 format) - rebaseline to payback schedule during pilot Cost Benefit Analysis - InAcademia v5 (7).docx Excel payback schedule is inserted in the Word Document
Roadmap: Roadmap InAcademia for Pilot gate.pptxRoadmap:
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: PilotProduction (advanced/single tenant model)
Target date end Feb.: June 2018
Task 2
Documents for Pilot
CBA: In Progress, CBA-eduTEAMSPilot.docx, payback-eduteams-pilot.xlsx
PID: How does this relate to the GN4-2 workplan?
Roadmap:
Roadmap: eduTEAMS-Roadmap.pptx
EC Deliverable: Background information
Service Description: Included in EC DeliverableService Description: COPaaS.pptx (Needs updating/customising)
Service Policy: Source material, needs writingin development. Principles outlined in CBA.
Service Design Documents: Market Analysis GN4-1, Functional Architecture ; Technical Architecture ; VM Platform, EC Deliverable GN4-2.
Pilot Plan: TBC - Umbrella in Q1 2017...what else? eduTEAMS-pilot-plan.docx
Branding: Complete in collab with NA2. WebsiteBranding: In progress
Baselined Operational Reqs: In prgress
eduTEAMS Advanced
Target gate: Design
Task 2
Documents
CBA: , Market Analysis GN4-1
PID:
Roadmap:
Service Description:
Service Policy:
Service Design Documents:
Branding: In progress
Initial consultation w SA2 complete. TBD during pilot.
Documents for Production
eduTEAMS production CBA: CBA-eduTEAMS-Production Gate-Final.docx
eduTEAMS roadmap: eduTEAMS-High-level roadmap.pptx
IdP as a Service
Target gate: DesignProduction (toolkit only) end GN4-2
Task 1
Target date for material end April.
Documents
CBA: Draft in progress
Baselined PID:
...
Service Design Documents:
StepUp Assurance/MFA
Target gate: DesignTransition (part of eduTEAMS advanced? Or later?)
Task 2
Documents
CBA:
PID:
Service Description:
...
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: Product Output is BCP documents. How to represent?
Baselined Service Policy: Product Output is BCP documents. Policy BCP can be developed, is this what is wanted?
Service Design docDocuments:
eduroam
Roadmap: Product Output is BCP documents.
Branding/visibility: GÉANT/EC to be acknowledged as sponsor of work. Material to be available on GÉANT website as White Papers/BCP documents.
OIDC Standardisation
Target gate: Design? Pilot?
Task 3
Documents
CBA:
PID:
Service Description: Product Output is standards, not a service. How to represent?
Roadmap: Product Output is standards, not a service. How to represent?
Service Policy: Product Output is standards, not a service. How to represent?
Service Design doc:
Branding/visibility: GÉANT/EC to be acknowledged as sponsor of work.
eduroam
Target gate: None, in production.
Task 4
Main Service Documents:
NIF:
CBA:
PID:
Roadmap:
Service Description:
Service Policy:
Service Design Documents:
eduroam Managed IdP
Target gate: Pilot
Task 4
Documents:
CBA:
Roadmap: roadmap-eaas.pdf
Service Description: eduroam Managed IdP (external testing)
Service Policy:
Service Design Documents:
Pilot Plan:
KPIS:
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:
- Original GN4-1 deliverable 9.3
- Client CA - architecture
- Server CA - architecture
- Components and Workflow
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.
KPIS - See CBA and PID.
Branding: eduroam Managed IdP - agreed with KM. Visible only on parts of user interface. (name-brainstorming)
Exit-Pilot Gate Documents:
CBA: CBA-eduroamManagedIdP exit pilot gate PROPOSED FINAL.docx
Costs and funding requirements: eduroam Managed IdP costs and funding exit pilot gate.xlsx
Service design:
- Original GN4-1 deliverable 9.3
- Client CA - architecture
- Server CA - architecture
- Components and Workflow
Service description and policy
GDPR assessment data mapping: eduroam data inventory
Roadmap: eduroam Supporting Services Roadmap-GN4-3.pptx
eduroam Managed IdP Milestones to Production Service.xlsx
| Anchor | ||||
|---|---|---|---|---|
|
CBA: CBA-eduroamManagedIdP production gate 12.12.18.docx
Costs and funding requirements: eduroam Managed IdP costs and funding production gate 12.12.18.xlsx
Service definition, service operations, service support, and monitoring & reporting all at: eduroam Managed IdP
Roadmap: eduroam Supporting Services Roadmap production gate 12.12.18.pptx
geteduroam
Target date: Design
NIF: Document
Branding: TBD