1 NETWORK PLANNING TASK FORCE November 15, 2004 FALL FY 2005 MEETINGS “STRATEGIC DISCUSSIONS”

1

NETWORK PLANNING TASK FORCE

November 15, 2004

FALL FY 2005 MEETINGS

“STRATEGIC DISCUSSIONS”

2

MEETING SCHEDULE – FY ‘05

■ Summer Focus Groups■ July 19■ August 2■ August 16

■ Fall Meetings■ September 20 Operational Briefing (Non-financial)■ October 18 Strategic Discussions (Security)■ November 01 Operational Discussions ■ November 15 Strategic Discussions ■ November 29 Financial Discussions■ December 6 Consensus/Prioritization/Rate Setting

3

NPTF FALL ’05 MEMBERS

■ Mary Alice Annecharico / Rod MacNeil, SOM

■ Robin Beck, ISC■ Chris Bradie/Dave Carrol, Business

Services■ Cathy DiBonaventura, School of Design■ Geoff Filinuk, ISC■ Bonnie Gibson, Office of Provost■ Roy Heinz / John Keane/ Grover McKenzie ,

Library■ John Irwin, GSE■ Marilyn Jost, ISC■ Deke Kassabian / Melissa Muth, ISC■ Doug Berger/ Manuel Pena, Housing and

Conference Services■ Mike Weaver, Budget Mgmt. Analysis■ Dominic Pasqualino, OAC

■ Kayann McDonnell, Law■ Donna Milici, Nursing■ Dave Millar, ISC■ Michael Palladino, ISC (Chair)■ Dan Shapiro, Dental■ Mary Spada, VPUL■ Marilyn Spicer, College Houses■ Steve Stines / Jeff Linso, Div. of Finance■ Andrew Selden*, PCBI■ Ira Winston / Helen Anderson, SEAS, SAS,

School of Design■ Mark Aseltine/ Mike Lazenka, ISC■ Eric Snyder*, Vet School■ Brian Doherty*/John Yates*, SAS■ Richard Cardona*, Annenberg■ David Seidell, Wharton■ James Kaylor, CCEB

* New Members in FY’05

4

Today’s Agenda

■ PennKey (Mark Aseltine)■ PennCommunity Staff (Jeanne Curtis)■ PennCommunity Hardware (Ray Davis)■ Security (Dave Millar)

5

PennKey - Goal

■ Effectively support PennKeys/passwords.■ Provide a single point of contact for PennKey

questions in support of the range of services that rely on PennKey, particularly during the summer.

■ Respond to requests for creation of new PennKeys in cases where showing up in person is not possible. Includes requests in support of visitors and VIPs.

6

PennKey - Challenge

■ Balance increasing demand for services with the need to provide cost effective services.

■ Fund additional staffing to maintain services at the desired levels given increasing demand.

7

PennKey - Context / Drivers

IT Staff on Campus

450

500

550

600

650

700

750

FY2000 FY2001 FY2002 FY2003 FY2004

Year

Nu

mb

er

of

IT S

taff

8

PennKey - Context / Drivers

Provider Desk Volume

0

2000

4000

6000

8000

10000

12000

FY2000 FY2001 FY2002 FY2003 FY2004

Year

Nu

mb

er

of

Co

nta

cts

Provider Desk

9

PennKey - Context: PennKey Support Analysis Team

■ Cross-ISC team that looked for ways to improve PennKey Support.

■ Text/apps simplified and streamlined.■ Enter PIN once in clear text (vs twice masked). PINs

generated lower case, etc.■ “PIN” becomes “PennKey Setup Code”■ Satellite PennKey locations.■ Etc.

10

PennKey – Context Outcome

■ Even with the improvements brought by these efforts, the volume of support calls is up this year as use of PennKey continues to increase.

■ PennKey “Steady State” Requests:■ Jan-Oct 2003: 1821■ Jan-Oct 2004: 2402 (+32%)

11

PennKey - Current funding model

■ One-time money was allocated to support the effort associated with the transition to PennKey. It was not clear at that point what level of ongoing support would be needed to support PennKey in “steady state”.

12

PennKey – Funding Requested

■ Support for PennKey Use■ ISC Staffing/Cost: .5 FTE / $40K■ Alternatives: No good alternative.

■ Funding Alternatives■ Schools by student headcount■ Stakeholders – Admissions, VPUL, Business

Services, other?■ Central Service Fee

13

PennKey – Funding Requested (Continued)

■ Support for PennKey Creation■ ISC Staffing/Cost: .3 FTE / $30K■ Alternatives: Pursue strategies to lower these costs:

■ Automate setup to the extent possible.■ Distribute guest PennKey responsibility.

Funding Alternatives■ Schools/centers by headcount■ Central Service Fee

14

PennCommunity (Staff)

■ Goal■ Current status■ Value add for additional funding■ Funding requested

15

PennCommunity – Goal

■ Provide a timely common base of data about people in Penn’s Community.

■ Data is drawn from student and employee systems of record.■ Direct entry is enabled for constituencies not available in electronic form.

■ Data serves as a basis for authentication to University services.

■ Provide support for access and use of PennCommunity data.

■ Resolve data conflicts.

16

PennCommunity – Current Status

Transition to Steady State■ To support the implementation of PennKey and shakeout to

steady state ISC has used one-time money to supplement previous support levels.

■ Introduction of PennKey/PennID use into systems:

■ Penn-InTouch, U@Penn, Blackboard, PennNames, school/center applications, etc.

■ Steady State transition will be complete this fiscal year■ New extracts for Payroll and Students

17

PennCommunity – Value Add

Ongoing SupportAdditional continuing support since implementation of PennKey■ Training and daily support of PennKey administrators – increase from

3 central to all schools & centers■ Daily troubleshooting for integrated systems

■ SRS, Payroll, Websec, PennNames, PennKey■ Maintain PennCommunity website■ Establish secure access to data ■ Provide query support and consulting for developers and

administrators■ Developing flow documentation

18

PennCommunity – Funding Requested

■ Additional funding request for half an FTE $50,000

19

PennCommunity (Hardware)

■ Goal■ Current status■ Value add for additional funding■ Funding requested

20

Penn Community - Goal

■ Purchase and install the hardware and

software necessary to provide remote hot failover capability for Penn Community server.

21

Penn Community - Current Status

■ Primary and standby servers are located in 3401 Walnut St.

■ Both servers are attached to ESS disk array■ Remote mirroring at Sungard (business

continuity)■ Manual failover in 15-60 minutes■ Schedule maintenance outages

22

Penn Community – Applications Affected

■ Advisor-In-Touch■ Application■ BEN Deposits■ BEN Reports■ Business Objects■ Classlists■ Directory Services■ Express App■ Facilities Center ■ Gradadmn

■ IRQDB■ Online Giving/Campaign■ PC Photo■ PennAES■ Penncard Forms ■ PennERA■ Pennkey registration■ Penn Online Recom■ Penn’s Way■ Websec

23

Penn Community - Value Add

■ Standby server at remote location■ Three copies of data■ Instantaneous failover capability■ Eliminate maintenance outages

24

Penn Community - Architecture

3401 Walnut StreetSunGard, 401 North Broad

Primary Server Standby Server

ESS Disk Array Remote ESS Disk Array

PPRC Link

PennCommunityCurrent Configuration

PennCommunityHot Failover ConfigurationPrimary Server Hot Failover server

ESS Disk Array

Remote ESSDisk Array

SAN disk withconcurrent database

3401 Walnut StreetRemote Location

SunGard, 401 North Broad

PPRC Link

Fiber Channel switches

Fiber Channel switch

ReservedRS/6000

ReservedRS/6000

Fiber Channel switches

Single mode fiber links from3401 Walnut to remote location

25

Penn Community - Funding Requested

One-time OngoingFAStT600 $21,000 $650Oracle RAC $45,000 $4,400HACMP/XD $27,000 $4,050Staff $20,000 $20,000*Network Fiber Links *

Total $113,000 $29,100

* With the “always available” Penn Community NES staff dollars are saved. This saving offsets costs for the fiber links

26

Security

Goals■ Identify our most serious risks and take the

necessary steps to manage them.■ Continue to provide a reliable network, free from

disruption due to security incidents.■ Minimize the incidence of costly system

compromises■ Achieve an appropriate balance of security vs.

ease of use.

27

Security

Goals■ Maintain an ongoing program of end user education and

awareness to ensure that end users take the steps necessary to ensure computer security, and that they avoid the practices that undermine security.

■ Maintain an ongoing program of LSP awareness, training and education to ensure that they are aware of their obligations under an evolving set of security policies.

■ Provide supporting services and tools to better enable LSPs to compliy with evolving policy.

28

Security

Current status/activities■ Manage and resolve approx. 2000 reports of compromised

systems and approx. 500 reports of copyright infringement annually.

■ Campus-wide security scans to identify both compromised and vulnerable systems.

■ Campus-wide distribution of “A Guide to Information Security” brochure.

■ Extensive end user and LSP education, awareness and training.

■ Actively working with LSPs to implement patch management programs in preparation for 1/1/05 patch management policy deadline.