OIT LOGO
Yellow Separator Line
  Spacer Image
Princeton University Title and Shield
Office of Information Technology Logo
Blue Separator Line


IT Architecture Team Charter

Introduction and Background

This team, sponsored by Betty Leydon and Colin Currie, was formed to document the many architectural standards, conventions, and best practices in use within OIT. The team will also serve to provide leadership and prescribe recommended standards, best practices, and technologies to OIT and its customers.

Goal

The IT Architecture Team will work collaboratively with staff throughout OIT and other campus departments to define and articulate the standards, technologies, processes, interfaces, and best practices that form the University’s IT architecture. The published architecture will document the University’s framework for the efficient and effective integration and cooperation of computing systems and functions and form the basis for future planning. The IT Architecture Team will define a cohesive architectural strategy for the future. The group will form specific technology prescriptions based on the defined strategy. On a yearly or as needed basis, the team will update the published architecture to reflect recent changes as well as review and update the existing published IT strategy documents.

Authority and Commitment

To make recommendations to the OIT Cabinet in the form of IT architecture documents.

Objectives

·        Define and articulate the components of the current IT architecture through the use of sub-teams focusing on the following general areas:     

1.      Standards (e.g., IMAP, LDAP, PKI and Kerberos)
2.      Networking, wired and wireless
3.      Processes (e.g., authentication, authorization, identity management)
4.      Desktop computing infrastructure (e.g., DeSC and SCI)
7.      Portal Strategy
8.      Web access to databases (e.g., Almagest)
9.      Directories (e.g., LDAP and AD)
11.      Middleware (e.g., Shibboleth and the Grid)
12.  Integrated workgroup applications (e.g., e-mail, calendaring)
13.  Workflow management

·        Provide information to the campus about the IT architecture via a centralized Web page.

·        Define a process for the review and updating of the IT architecture documents by the sub-teams on a semi-annual basis.

·        • Provide architectural reviews at the beginning of a project or tool selection and before implementation.

Authority and Commitment

To make recommendations to the OIT Cabinet in the form of IT architecture documents. 

Meeting Logistics

The team meets on the first Thursday of each month.

Team Structure (Membership, Roles and Team Leadership)

·        Betty Leydon: Executive Sponsor

·        Colin Currie: Team Sponsor

·        Debby Becker: Core Member
·        Jon Edwards: Core Member
·        Serge Goldstein: Core Member
·        Dave Herrington: Core Member
·        Robert Knight: Core Member
·        Paul Lynn: Co-Team Leader
·        Dave Morreale: Core Member
·        Peter Olenick: Core Member
·        Anthony Scaturro: Core Member
·        Steve Niedzwieki: Co-Team Leader

Points of Contact

·        Academic Computing Infrastructure:

Serge Goldstein

·        Administrative Distributed Computing Infrastructure:

Paul Lynn

·        Architectural Review Board:

Paul Lynn

·        Desktop Computing Infrastructure:

David Morreale

·        Directories:

Chris Kranz

·        Networking, Wired and Wireless:

Peter Olenick

·        Production Databases:

Debby Becker

·        Web Application Services:

Dave Herrington

·        Documentation/website coordinator:

Jon Edwards

Archiectural Review Board

·        Core Team Members:

Michael Barton
Deborah Becker
Curt Hillegas
Charles Kruger
Paul Lynn, ARB Team Leader
Steven Niedzwiecki
Peter Olenick
Anthony Scaturro

·        Additional Members:

Charles Augustine
Colin Currie






Blue Separator Line
©
IT questions: helpdesk@princeton.edu, Web page comments: webservices@princeton.edu