A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study...

20
A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting 1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners, and Campus Constituents Art Vandenberg Director, Advanced Campus Services Information Systems & Technology Georgia State University [email protected]

Transcript of A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study...

Page 1: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 1

Georgia State University – Case Study 1 Middleware:

Working with Policy Makers, Data Owners, and Campus Constituents

Art Vandenberg

Director, Advanced Campus Services

Information Systems & Technology

Georgia State University

[email protected]

Page 2: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 2

Culture, business needs& project methodology

• CIO - top level sponsor of eUniversity• Analogous to eCommerce, higher ed needs:

– Directory services (not limited point solutions) for id, authN, authZ per application

– Seamless interfaces to applications: libraries, email, calendaring, eLearning, room/resource access, etc.

– Reduction of multiple electronic identities

• Specific commitment, assignment & charge for Advanced Campus Services - broad coordination

Page 3: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 3

Specific direction& action plans

• Feb 2000, ACS charged with: – University-wide directory, metadirectory

– Universal account creation (namespace)

– Universal email solutions

– Interface to other electronic domains (one card, library…)

– Public-private key infrastructure

• NOTE: Georgia State’s ERP domain:– Peoplesoft financials, Student SCT begun, WebCT…

Page 4: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 4

Stakeholders

• CIO and IT directors– Steering Group, scope doc, charter

• Data Stewards for Person Working Group:– registrar, hr, financials, card office, person registry

• LDAP Technical Working Group• Application domains

– WebCT, student email, Rec Center, one card office

• University System - discussion, promotion– CIOs, Vice Chancellor, Technical staff

Page 5: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 5

Pitfalls/missed opportunities?

• Misjudging readiness– Competing ERP deployments– “Not ready for prime time” PKI

• Business needs not obvious– Hard to engage ERP teams focused on their core tasks– “But we can already do that!” (finding a killer app…)– “We’ll do that later, as soon as finished with priorities.”

• Lack of trust from data custodians?– Not really, but challenges with“technical” custodians

Page 6: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 6

… opportunities?…

• Re: Bringing in key stakeholders– Deference to ERP teams (hindsight is 20/20… but)– However…aircraft carriers need room (time) to turn

• Changes the way we do business– Easier for new applications to embrace change?

• WebCT, student email, Rec Center

– Major event horizon (inevitable…)• First stop is person registry, then HR• Change process, not business

• University System - a necessary engagement

Page 7: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 7

Legal risks with data

• Limit initial issues (but be aware)– If risky, leave data behind ERP wall (cf. bank accounts)

• Person registry actually inserts level of protection– Publishing/provisioning can have appropriate limits– Registry remains behind access controls

• White pages: “print” directory (Registrar/HR)• Core principles:

– Authoritative sources remain ERP systems– Data Stewardship & Access Policy governs all data

Page 8: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 8

Silos and fortresses?

• What about aircraft carriers?– Major ERP implementations already underway– Production and operations culture vs. R&D– Technical debates can be: <invigorating/debilitating>

• Tactical versus strategic– Just do it (works well initially)– Iterative process, that keeps focusing on strategy– Remember, we’re part of a state system– Keeping one eye on national initiatives in middleware

Page 9: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 9

Communication model

• Enterprise Directory Infrastructure Steering Group– CIO and IT directors

• Start biweekly, phase toward monthly end year 2• Level setting, resource identification, priorities

• University System– Burton Group directory/PKI seminars (1999-2000)– Directory Working Group (3 research, system office)

• Establish vocabulary, concepts, general consensus• Recommendation to ACIT (CIOs & V.Chancellor)• Directory of directories/system-wide id/ERP integration

Page 10: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 10

Communication…

• Conferences– University System Rock Eagle, CUMREC

• Focus-IT newsletter, campus contacts• System Committee on policy for SSN• Internet2 Middleware working groups

– Support group, sanity check, best practices– Consider as “retreat & renewal” for more evangelism

• Technical staff (listen, be patient, leverage)• Work it until it’s part of the IT vocabulary

Page 11: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 11

The sales pitch…

• Focus on application areas– Middleware may be too arcane, except for “initiates”

• “Printed Directory” as a metaphor• Provisioning - as it impacts colleges/depts:

– Automatic course rolls for WebCT– Universal email(and for admitted students)– New staff hires (get them online “day one”)

• Account management - as it impacts technical– User X has what accounts? Who is in application Y?

Page 12: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 12

Hot buttonsInternal pressures

• Doesn’t everyone use same email? (No!)• President: Why can’t I send email to all faculty?• “I want to choose my own unique ID”• New hire online “day one”• Group email, paperless office, email check advice• Too many ids, too little management• Operational/production missions take priority• Resources: staff, time, money (in that order)

Page 13: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 13

Worm holes…Strategic goals

• Goose & gander (student email policy… staff too)• Aha! (Metamerge & NMI-R1 for dynamic groups)• Just do it! (Forgiveness negotiable)• Involve faculty & students (competitive edge)

• Support teaching & learning mission• Integrate with ERP systems (Campus Pipeline…)• 3 years… but directory services on VC’s plan!

Page 14: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 14

Carrots & sticks

• We’ll do this app for you if… vs• We can do this app better if…• Involve from beginning?

– Advantage sometimes, sometimes not– Good for us: research faculty & students– Find customer app that sells: WebCT, demographics

• The problem you want: middleware advisors!– You’ve really arrived!

Page 15: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 15

Georgia State University – Case Study 2 Policy and Data Sore Points

Art Vandenberg

Director, Advanced Campus Services

Information Systems & Technology

Georgia State University

[email protected]

Page 16: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 16

Technical implementationof institutional policy

• Data owners and control issues– Data Stewardship & Access Policy. Very helpful– Consensus: source systems retain authority– There is control and there is control. Do technical staff

“know” functional needs? (Careful)– Who drives project? (Remember: Organization is the

winner… Strive for consensus)– End users are data owners too!– Person registry has data steward

Page 17: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 17

Implementing…policy

Policy Framework from the 1990s management– FERPA: Based on printed directory (annual, static),

not directory services (online, dynamic)– Was: Name, title, address, phone… Now: email, uid,

URL, pager, cell, mobile, jpeg…– Now: multiple roles overlaid with privacy issues– Now: lifetime CRM – pre- & post-relationship– Publication of employee info – We’re lucky (I think)

being public institution– Know your institutional policy process

Page 18: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 18

Implementing… policy

Implementing triggers of institutional policy– ERP policy in person registry – be specific, be careful– “Current, active” student? 25,000 vs 61,000– If student elects FERPA suppress, what about directory

entry?– Definition of privileges: application by application– Do not ASSUME agreement on definitions (spell it out)– Technical staff defer to functional – nothing is simple– Be careful how you change business process (cf.

payroll doesn’t/can’t/shouldn’t initiate identity)

Page 19: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 19

Implementing… policy

Role definitions: faculty, staff, affiliate…– “Hey cool! I’m faculty at the Library!”

– More student employees than faculty…

– Are student employees covered by FERPA?

– When does (can) an employee “start”?

– Concept of “provisional hire” (need date triggers)

– Hierarchy: “payments out” trumps “fees paid in”

– Retirees, survivors & “passed away”

– Vendors, affiliates – require sponsor, date limits

Page 20: A.Vandenberg October 21, 2001 Internet2 Fall Member Meeting1 Georgia State University – Case Study 1 Middleware: Working with Policy Makers, Data Owners,

A.VandenbergOctober 21, 2001

Internet2 Fall Member Meeting 20

Suggestions

Communication is good, and builds buy-in– CIO, IT Directors, data stewards, technical staff, campus– System & peer institutions, Internet2 Middleware

– Aim high,but focus on application specifics

– Iterative development. Iterative review

– Don’t underestimate group & organizational dynamics

• Allow stewardship to work– Identity management is shared

– Think metadirectory services (value add, not replace)


Working with Data Managers Renee Woodten Frost Internet2 Middleware Initiative University of Michigan.

Working with Data Managers Renee Woodten Frost Internet2 Middleware Initiative University of Michigan.

Internet2 Middleware Drinking Kool-Aid From A Fire Hose or Sniffing Glue-Ware

Internet2 Middleware Drinking Kool-Aid From A Fire Hose or Sniffing Glue-Ware

Internet2 spring meeting1 Making the phone not ring Henning Schulzrinne Department of Computer Science Columbia University hgs@cs.columbia.edu Internet2.

Internet2 spring meeting1 Making the phone not ring Henning Schulzrinne Department of Computer Science Columbia University [email protected] Internet2.

Middleware Planning and Deployment 201: Implementation Roadmap Keith Hazelton, University of Wisconsin/Internet2 Renee Woodten Frost, Internet2/University.

Middleware Planning and Deployment 201: Implementation Roadmap Keith Hazelton, University of Wisconsin/Internet2 Renee Woodten Frost, Internet2/University.

Internet2 Middleware Activities Progress

Internet2 Middleware Activities Progress

Internet2 Middleware Activities Progress Renee Woodten Frost Project Manager, Internet2 Middleware Initiative I2 Middleware Liaison, University of Michigan.

Internet2 Middleware Activities Progress Renee Woodten Frost Project Manager, Internet2 Middleware Initiative I2 Middleware Liaison, University of Michigan.

Internet2 Middleware Initiatives: Early Harvest to Early Adopters and Beyond Renee Woodten Frost Project Manager, Middleware Early Adopters, Internet2.

Internet2 Middleware Initiatives: Early Harvest to Early Adopters and Beyond Renee Woodten Frost Project Manager, Middleware Early Adopters, Internet2.

Internet2 Middleware Initiatives: Early Harvest to Early Adopters and Beyond

Internet2 Middleware Initiatives: Early Harvest to Early Adopters and Beyond

Internet2 Middleware Initiative. Discussion Outline What is Middleware why is it important why is it hard What are the major components of middleware.

Internet2 Middleware Initiative. Discussion Outline What is Middleware why is it important why is it hard What are the major components of middleware.

Security and Privacy Renee Woodten Frost Program Manager, Middleware Initiatives, Internet2 I2 Middleware Liaison, University of Michigan Telemedicine.

Security and Privacy Renee Woodten Frost Program Manager, Middleware Initiatives, Internet2 I2 Middleware Liaison, University of Michigan Telemedicine.

Middleware Activities Update Internet2 Membership, with coordination provided by Internet2 et al presentation by Renee Woodten Frost Internet2 and the.

Middleware Activities Update Internet2 Membership, with coordination provided by Internet2 et al presentation by Renee Woodten Frost Internet2 and the.

The Co-mingled Universe of R&E Networking: the reprise Ken Klingenstein Director, Internet2 Middleware and Security Ken Klingenstein Director, Internet2.

The Co-mingled Universe of R&E Networking: the reprise Ken Klingenstein Director, Internet2 Middleware and Security Ken Klingenstein Director, Internet2.

Internet2 Middleware Activities Progress. Internet2 All staff tutorial Nov.28, 2001 Acknowledgments MACE and the working groups NSF catalytic grant and.

Internet2 Middleware Activities Progress. Internet2 All staff tutorial Nov.28, 2001 Acknowledgments MACE and the working groups NSF catalytic grant and.

Shib in the present and the future Ken Klingenstein Director, Internet2 Middleware and Security.

Shib in the present and the future Ken Klingenstein Director, Internet2 Middleware and Security.

26 November 2015 Middleware Planning and Deployment 101: Setting the Stage Ann West EDUCAUSE/Internet2 27 October 2002 Ann West EDUCAUSE/Internet2 27 October.

26 November 2015 Middleware Planning and Deployment 101: Setting the Stage Ann West EDUCAUSE/Internet2 27 October 2002 Ann West EDUCAUSE/Internet2 27 October.

Middleware: High Technical Bandwidth, High Political Latency Ken Klingenstein, Project Director, Internet2 Middleware Initiative Chief Technologist, University.

Middleware: High Technical Bandwidth, High Political Latency Ken Klingenstein, Project Director, Internet2 Middleware Initiative Chief Technologist, University.

3 September 2015 Federated R US. Agenda Background on Internet2 Middleware and NSF Middleware Initiative The body of work Directories Shibboleth.

3 September 2015 Federated R US. Agenda Background on Internet2 Middleware and NSF Middleware Initiative The body of work Directories Shibboleth.

Middleware Tutorial and Use Renee Woodten Frost Project Manager, Internet2 Middleware Initiative Internet2 Middleware Liaison, University of Michigan ARKNet.

Middleware Tutorial and Use Renee Woodten Frost Project Manager, Internet2 Middleware Initiative Internet2 Middleware Liaison, University of Michigan ARKNet.

Federated Security and the Federal Government Ken Klingenstein Director, Internet2 Middleware and Security.

Federated Security and the Federal Government Ken Klingenstein Director, Internet2 Middleware and Security.

Current Activities in Middleware Ken Klingenstein, Project Director, Internet2 Middleware Initiative Chief Technologist, University of Colorado at Boulder.

Current Activities in Middleware Ken Klingenstein, Project Director, Internet2 Middleware Initiative Chief Technologist, University of Colorado at Boulder.