Skip to end of metadata
Go to start of metadata

Date: 3/29/2012, 8:30 to 10:30am 

Location: 118 Wagner Building

Purpose: Review CSI Preliminary Project Planning Reports by AIS and CSS.

Facilitator: IAM
Attending:

Renee Shuey
Richard Dumm
Jimmy Vuccolo
Ed Hayes
Ron Rash
Cheryl Seybold
Walter Kay

Dawn Boyer
Jan Grasser
Carl Seybold
Pete Dawson
Kelly Hartzfeld
Saralee Conkling
Scott Weaver

Kathy Brown
Sue Jones
Kathy Beck
John Williams
Shawn Smith
Barb Howe

Bob Walters
Jeff D'Angelo
Gerry Mihaly
Robyn Wang
Steve Kellogg
Ken Forstmeier

** Note: Ron and Ken were unable to attend.

MEETING SUMMARY

NEXT STEPS - HIGH LEVEL ACTION ITEMS

ACTION ITEM

OBJECTIVE

PARTICIPANTS

DUE DATE

Schedule weekly meetings with IAM and AIT

Develop work breakdown and work estimates for May 1st Report

CPR tech team, AIS/IAP Group, CSS/AIT group

Weekly - now to May 1st

Performance Testing

Performance statistics - necessary to complete May 1st Report.(for batch processing analysis)

CPR tech team, AIS/IAP Group, CSS/AIT group

As needed  - before May 1st

CSI - Project Recommendations Report

A report that will include high level work packages and resource estimates. 
-> Use consistent reporting of work effort in report
-> Include a Total FTE count in all options
-> Include high level description of skill sets required to complete work

IAM, AIS, CSS

May 1st (for review)

Impacts to current projects

Identify what projects/work effort in AIS and CSS that will be impacted by doing the CSI project.

AIS and CSS Sr. Directors

 

Business Process Impacts

Identify the business process impacts and high level work effort that will impact key stakeholders (UAO, Registrar, Grads, Outreach, Hershey, Payroll/Controller, OHR)

AIS and AIT reports

 

Present Report to CIO

Renee, Ken, and Ron present reports to Kevin. 
Determine approach to take on commitment of partner office resources (Present to IAM Governance (top down) or Partner Offices first (bottom up)

Renee

 

Present Recommendations to IAM Governance or Partner office

IAM Report with recommendations presented to IAM Governance or Partner Office

 

 

PRODUCTION READY CPR DELIVERABLE'S

  • CPR Provisioning Penn State ID numbers
  • CPR Provisioning User ID's
  • CPR Provisioning PersonID (cpr unique identifier)
  • IAM onLine (Web application) Provisioning Identity service (User Interfaces and process)              }
  • IAM onLine (web application) Person Maintenance service (User Interfaces and process)               }      See IAM ITS Service Catalog Draft
  • IAM onLine (web application) Administrative Maintenance service (User Interfaces and process)     }
  • CPR will be authoritative source for identity information:
    • Name (all types)
    • Address (all types)
    • Personal Data (Date of Birth, personal email address, gender)
  • Provisioning services to CPR
    • email, auth, and directory
  • Batch Ingestion processes
    • CACTUS imports from student, employee, Hershey, World Campus, and other smaller entities.

NOTE: The work effort defined in AIS Option 1 or Option 2 would need completed to meet the above deliverables.


IAM UPDATE: CPR OPERATIONAL READY KEY DELIVERABLES - 3/31/12

INFRASTRUCTURE

  • 13 Virtual Machines and 5 physical  boxes.
  • Test, acceptance, and production application servers (Tomcat 7.028) and messaging servers  (ActiveMQ 5.5.1) are configured and available.
  • Production Oracle database (11gR2) is configured and primed with data from CACTUS.
  • Production and test DataFlux (matching and address validation) servers are configured.
  • Test, acceptance and production Grouper servers are configured and available.
  • Rules Engine currently used for affiliations.
  • 88 SOAP based web services and associated Unit and Integration Tests.
  • Domestic and International Matching Algorithm’s.
  • Address validation and transformation software in place.
  • IAM onLine – Identity Provisioning services.
  • Automated continuous integration build tool (Jenkins).
  • Source Code version control (Subversion).
  • Two prototype service provisioner's were developed (Authentication and Directory).

MIDDLEWARE

  • Rules Engine currently used for affiliations.
  • 88 SOAP based web services and associated Unit and Integration Tests.
  • Domestic and International Matching Algorithm’s.
  • Address validation and transformation software in place.

USER INTERFACES

  • IAM onLine – Identity Provisioning services.

TOOLSETS

  • Automated continuous integration build tool (Jenkins).
  • Source Code version control (Subversion).

PROTOTYPES

  • Two prototype service provisioners were developed (Authentication and Directory).

AGENDA

Reference Next Steps from last meeting: CSI - CPR Technical Overview - Feb 6 2012

  • IAM Update (10 minutes)
  • AIS Report Review - AIS Architecture and Impact StatementMarch 29.docx
  • CSS Report Review
  • Next Steps
    • Project Organization
      • Project Management Working Group (PM and Team Lead from each area)
      • Identify Decision Makers
      • Meeting Frequency
    • Project Management Plan
      • Project Schedules
      • Communication
      • Risk Plan
      • Issue Resolution Process
      • Guiding Principles
    • Other ?

Meeting Notes

Reference Material

  • No labels