Enterprise Architecture

CIO Council Update

Jan. 26, 2015 | Monday | 3:00 p.m. | Smith Center 561

v. 1.3
Agenda

• The Enterprise Architecture Vision

• Enterprise Architecture Governance

• EA Program Approach

• Key Terminology

• Interoperation: Current State of Identity and SIS Data

• Interoperation: Domains and Plan

• Interoperation: Vision and Proposed Guiding Principles

2
The Enterprise Architecture Vision

Our Vision for Enterprise Architecture

Provide a technology framework and a set of standards to enable acquisition, development,
and deployment of IT services that maximize interoperation, minimize duplication, and simplify
the IT environment across all of Harvard.

Strategic Objectives Guiding Principles Key Performance Indicators

• Deliver an enterprise architecture
framework that drives technology
and development standards
across Harvard
• Provide common approaches for
integration across enterprise
applications, processes, and data
• Align and rationalize technology
decisions and investments
• Identify redundant or conflicting
processes and data across
organizations
• Ensure that EA provides active
direction and delivers value to the
organization
• Counter complexity with common
solutions
• Enable sharing of data across
organizations
• Preference for open-source,
COTS, and programmatic
interfaces — both in what we
obtain and what is produced
• Encourage, define, and ultimately
provide best-practice solutions
• Evolve framework and solutions
with advances in technology
• Decrease in project delivery
timeframes to production
• Increase in the number of
integrated applications using
programmatic interfaces
• Increase in the number of funded
projects that conform to an EA
Checklist
• Decrease in ad-hoc data sharing
• Increase in automated data
exchange
• Increase in the number of known
authoritative data sources
• Decrease in the number of copies
of data

3
Enterprise Architecture Governance

Enterprise Architecture Executive Committee

IT executives who ensure that the vision and plan are addressed by the working group. Also provides
consistent direction and problem-solving approaches for the working group and the EA program at large.
Meets monthly.
Co-Chairs: Anne Margulies and Stephen Gallagher
Members: Scott Bradner, Ben Gaucherin, Stephen Ervin, Gabriele Fariello, Praneeth Machettira,
Pratike Patel, Jason Shaffner, Jason Snyder, Jim Waldo, Bob Wittstein

Enterprise Architecture Working Group

• Technical members of HUIT, Harvard Schools, and other IT departments that

meet on a regular basis
• Defines the Enterprise Architecture framework for review by Steering Committee
• Defines sub-groups to detail layers
• Builds and reviews other EA components as per vision
• Publishes a monthly report on enterprise architecture progress, issues, and direction for the organization
Chair: Jason Snyder
Members: Scott Bradner, Bill Brickman, Dan Kaplan, Arnold Paul, Robert Piscitello, Jon Saperia,
Raoul Sevier, Michael Thomas

4
EA Program Approach

Re-Evaluate: Identify Places Where EA Can Make an Impact

Layers Communication & Education

Security Advisories,
Requirements Methodologies, Architects
and Needs and Principles
User Experience

Applications and Software Components UX Consultation

Interoperation
Enterprise
Enterprise Patterns and
Architecture
Technology Reference
Implementation Architecture Ad-Hoc Consultation
Assessment Data
Plan

Middleware
ITCRB and PRC Reviews
Infrastructure and IaaS
Technology
Trends and Outreach and
Best Practices Networking Training Evaluate Skills &
Organizational Needs

5
Key Terminology: Layers
Layers Definition
User End-user look-and-feel and navigation
eXperience style of an application or service.
Applications, Algorithms and code that provide
services, technical or business value.
SaaS
Interoperation Exchanges of information and
provisioning of business transactions
between different applications and
services.
Data Information represented in formats
managed by apps and services.
Middleware Common business or technical services
that are implemented separately from
applications and services.
Infrastructure Hardware and virtualized platforms that
operate applications, services, and their
components.
Networks Communications tech to join
infrastructures in disparate locations.
Security Use of resources by authorized
individuals and computing services to
information, business functions, and
computing services.
Examples
Appearance of the Harvard brand, color schemes, use of
„breadcrumbs‟, position and appearance of navigation bars.
Large-scale apps such as SIS, small apps such as Electronic
Submission Tracking and Reporting (ESTR), services such as
Informatica for data transfers, and Software-as-a-Service solutions
such as Office365.
Information exchanges include transfers of student registration from
SIS to central directories, or transfer of account balance values from
financial to CRM systems. One remote service is IAM‟s Authentication
service.
Structured data include student records and general ledger financial
data; unstructured data include e-books, wiki content, and most of the
information available on the Internet.
Database technologies are the most common example of middleware,
but this layer can also include reporting „engines‟, rules „engines‟,
application servers, data transfer applications, and other common
shared services.
Servers, associated storage components, operating systems, and
other computing devices are common examples, as well as cloud-
based infrastructures of Platform-as-a-Service and Infrastructure-as-a-
Service.
Wired and wireless communications supported by devices such as
routers, switches, and naming services.
Mechanisms include door locks, user IDs/passwords, and intrusion
detection/prevention tools. These are supported by apps/services to
manage user and systemic authentication, authorization, and access
to functionality and data.
6
Key Terminology: Processes

Processes Definition Examples

Principles Foundational elements to drive decision- Principles can be applied at many levels, from guiding principles that
making and alignment. characterize strategic, enterprise-wide systemic behavior, to principles
that help explain detailed technical behaviors of applications and
services.
Methodologie Methodologies divide IT work into phases Waterfall, prototyping, iterative, and incremental development; spiral
s for better planning and management, and development; rapid application development; extreme programming;
determine methods or “best practices” to Agile.
be applied to specific cases. May include
specific deliverables/artifacts.
Advisories Recommendations offered as a guides to Security notifications of newly discovered vulnerabilities with
specific actions or practices. recommendations for patching systems or changing passwords; and
announcements of changes to the features, forms, or functions of
applications.
Patterns Generic models or descriptions from Reusable approaches for connecting applications to databases,
which specific implementations can be establishing user security within an application, or implementing user
based or derived. experience in a solution.
Reference A template solution that defines an Business reference architectures include Insurance Application
Architectures architecture for a particular domain using Architecture (insurance),and HL7 V2.5 (health records). One technical
multiple patterns and a vocabulary that reference architecture is Java Enterprise Edition for IT systems
promotes commonality. construction.
Outreach Elevating awareness of programs and Broadly-focused outreach at Harvard includes ABCD meetings on a
initiatives to affected populations. wide range of IT topics; more narrowly focused are Big Group
meetings on specialist topics such as IT skills upgrades.
Training Acquiring knowledge and skills as a IT techniques training could include database design, software coding
result of teaching on specific in node.js, and process modeling with BPMN. Vendor tool training
competencies, with a goal of improving could include Oracle Financials, PeopleSoft, and Informatica ETL.
productivity and performance.
7
Interoperation: Current State of Identity Data
Representative Cross-University Directory Data Flows
School Financial HKS HLS Multiple HBS Sources
Aid Offices

School Person Type

Data
Address Data
Degree Data
Bio Data Multiple HBS
University Financial HBS Person Type
Locations
Aid Liaison Office Address Data
Degree Data Name
Bio Data Person
SIS Data Addresses
Address Data Department Codes
Degree Data CAADS Email Addresses GMAS
Bio Data Employee Class Codes
Employment Status (and others - e.g, Library
SIS + Harvard Positions Campus Services, HUHS)
Job Codes
Name, DOB, last 4 of SSN, People
UUID, HUID, Gender PeopleSoft Location
Codes
IAM Phones
Campus Solutions
Name, DOB, last 4 of SSN
Name Type Athletic
Name Prefix
First Name Membership
FAS Phone Name Middle Name
Last Name
Name Suffix Data Format
15 years service (T/ F)
(from secondar y DB) XML IAM Format
Name
DCE Person XML HBS Format
XML PeopleSoft New Hire Schema

Address, Person, Name, Email PeopleSoft Input XML

Email Address, Directory Listing
Address, Directory Listing Data, Data, Name, Person DB View
Job, Role, Employee Job Code Address
Department Code Human Input
Address Pipe Delimited
Person
Name Oracle Datapump File
Email Address PeopleSoft Employee File Fixed Length Field Text File
Directory Listing Data
Job FindPerson/ JSON
Role Employee Job Code
Role Employee Department Code Address
Aspire Oracle Financial Transfer Protocol/ Creation Method
Person Online forms/ PeopleSoft Proprietary
Name & Procurement
Email Address FAS SFTP HTTP Post
Directory Listing
SPH Data
Job
SQL query and SQLLOAD
Web service
RESTful FindPerson (JSON) service
Version 1.5 - January 23, 2014

8
Interoperation: Current State of SIS Data
SIS Current Production Data Flows
HLS HLS Harvard Harvard
(Graduate (JD) HSPH Divinity School College GSAS
Programs)

ESCI

New Admit Bio

HUID Data
Assignment
Harvard School
of Dental Name
Address
Medicine Bio Data
Academic Progress

New Admit Bio

HBS Data
(MBA) SIS/ Name, DOB, last 4 of SSN
Find Person
Campus Solutions Name, DOB, last 4 of SSN, Service
UUID, HUID, Gender
HUID
HBS Assignment
(Doctoral) Name
Address
CAADS
Degree Data (CPP) (Monthly Feed)
HMS
Data Format
JSON -
Bio Data, (FindPerson)
HUID Payroll Workforce,
New Admit Bio Assignment Data Dept, Job, XML SIS Standard Admission
Data Location XSD
Tab Delimited Admission
Data
Fixed Length Field Text File

Pipe Delimited

GSD GSE HKS PeopleSoft PeopleSoft HR PeopleSoft HR to SIS XML

Payroll
PeopleSoft Payroll to SIS XML

Transfer Protocol/ Creation Method

SOAP/ XML
SFTP Into SIS
SFTP from SIS
Web REST/ JSON FindPerson service
Version 1.3 - January 22, 2015 - Jon Saperia

9
Interoperation: Domains

Modular Approach to Data/ Architectural

Service Integration Principles
Data Warehouse
Design Patterns, etc.
Information Bus Operations
Documentation
Other Resources Technologies for API’s
Operations (5) Integration Change Management
Training Enterprise
Operational Educational (e.g.,
Outreach support - Engineering Architecture (1) eduPerson)
Engineers on Loan Standards
Other de facto/de jure
Organizational standards
Structure and
Service and Selection and
Approaches (4) System/Technology
Data Acquisition Guidelines
Master Data Acquisition
Integration Exception Processes
Management Data Controls
Data Warehouse
Data Governance
Information Bus
Ad hoc analysis
Data Controls and Data Marts
Routine Analyses Analyses (3)
Software and Data Maintenance and
Metrics/Time Variance/Series Data Analyses/Tools Systems Management
and Cross Subject Correlation Engineering (2)
Example code/
Snapshot Operational
libraries
Detail/Audit
Automated
instrumentation
Jon Saperia - 1/7/2015 - Version 1.0

10
Interoperation: Establishing a Domain Work Plan (DRAFT)
FY15 FY16 FY17
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

Propose and Ratify Arch Outreach Activities

Architecture

Define Arch Principles & Methodologies Develop and Deliver Advisories

Document and Publish Architecture Refine Patterns & Reference Arch

Patterns, Reference Architecture

Deploy Prototype
Integration Services
Pilot Services with Selected
Feeds

Inventory Current Feeds & Apps Scale Integration Services Planned Upgrades
Engineering

Interoperation Services

Select Feeds and Integrate with Services

Pilot Services with Selected Integrate Existing School

Feeds Capabilities with EA
Outsource School Integration to
EA

Application Adaptors

Establish InterOp Working

Group
Organization

Train Core Team and Establish

Formalize Integration Services Group
Methodology
Develop Outreach
Provide Cross-Team Coordination
Materials

Management , Staf ng, Skills

Establish Master Data

Standards
Governance

Develop KPIs

Review Operational Metrics

Strategic & Tactical Measurement

Operate InterOp Services

Operations

Operations Management: Measure Service QOS and Data Quality

Deliver Operational Training and Support

Methodologies, Ops Mgmt , Training

KEY: EA Team App Teams Schools Planned

11
Interoperation: Proposed Vision and Guiding Principles

Our Vision for Interoperation in the Enterprise Architecture

Provide a framework and a set of standards to enable acquisition, development, and
deployment of integration services that maximize information sharing, minimize duplication,
and simplify the IT environment across all of Harvard.

Proposed Guiding Principles

• Similar data exchanged between applications have standard definitions and formats
• Publish event-driven data once, as soon as applications have it available
• Allow subscribers to data to specify the frequency of delivery
• Web services or APIs that perform business services are implemented once
• Interoperation improvements will displace, not break, current implementations
• Focus one organization with deep skills for continued development operation of
Interoperation solutions
• Leverage existing successes

12
Questions or comments?
Thank you!