Update on the University of Waterloo's IST Enterprise Architecture (EA) Group.

1. Progress IST-EA:
Role, Responsibilities, and Activities
Colin Bell
Nov 5, 2015

2. Outline
• Enterprise Architecture (EA) Group Basics
– Mission
– Responsibilities
– Director Accountabilities
– Structure
– Required Competencies
– Services
• Subsection Roadmaps
• Activities and Progress

3. Enterprise Architecture (EA):
Mission
The mandate of this group is to develop the
enterprise architecture strategy, framework and
program for the university that addresses both
current and future information management
and information technology needs.
https://uwaterloo.ca/information-systems-technology/about/organizational-structure/enterprise-architecture-ea

4. Enterprise Architecture (EA):
Responsibilities
• Integration Development
– (e.g., web, mobile, other)
• Strategic Innovations
• Information Management
• Usability
• Enterprise Architecture
https://uwaterloo.ca/information-systems-technology/about/organizational-structure/enterprise-architecture-ea

5. Enterprise Architecture (EA):
Director Accountabilities
• Establish direction and priorities for EA section.
• Effective utilization of EA section resources.
• EA strategy, framework, and models.
– Business, Information, Technical, and Solution Architectures
– Whole University (Faculty and Academic Support Areas)
– Advise other IST sections and broader Community
• Provides Thought Leadership
• Architecture Governance
• Communicates Standards
• Stakeholder Management
– Faculties and Academic Support Areas
http://www.hr.uwaterloo.ca/.jd/00001462.html

6. Enterprise Architecture (EA)
Logical + Organizational Structure
EA
Colin Bell
Architecture
Practice
Business and
Information
Sarah Vela
Strategic
Maher
Shinouda
EIM:
Information
Management
EDM: Data
Management
John Kemp
(Cognos)
ECM: Content
Management
Gina Reichard
(OnBase)

7. Enterprise Architecture (EA)
Required Competencies
1. Robust EA Section Portfolio
– Architecture Practice and EIM Practice must have
visions/roadmaps, be moving along them.
2. Strong Relationships with Collaborators
3. Efficient and Effective Governance
4. Continually Grow Staff Capabilities
5. Maintain a Focus on Service Orientation

8. Enterprise Architecture (EA)
Section Development Roadmaps
• Architecture Practice(ARCH)
– Starting from first principles. New approach with new
team and new ideas on campus. No starting point.
• Enterprise InformationManagement(EIM)
– Enterprise Data Management (EDM)
• Move from ‘Cognos’ focused team to tool agnostic, EDM
team. Data Driven; work with IAP and Information Stewards
to empower Data Driven Decision making on campus.
– Enterprise Content Management (ECM)
• Move from ‘OnBase’team to tool agnostic, ECM team.
Digitalization; work with University Records Manager and
AIGC to establish standards and implement in technology.

9. Enterprise Architecture (EA)
Services
• ArchitecturePractice Consulting
– Architectural ‘fire-fighting’ / urgent problems
– Procurement Support
– Archeological Digs (diagramming, documenting)
• EDM Consulting+ Implementation
– Semantic + Data Modeling / Schemas
– Database Performance
– Data Warehousing + BI toolset Implementation Services
• ECM Consulting + Implementation
– University Records Management Technology Standards
– OnBase Implementation Services

10. ARCHITECTURE PRACTICE
(IST-EA-ARCH)
Roadmap + Scope

11. Enterprise Architecture (EA)
Architecture Practice Roadmap
Stage 1
•(#50) Planning and Building EA Foundation @ Waterloo
•Foundational Research. Identify Stakeholders and Working DomainArchitects
•“Foundational” Architecture -> Fire Fighting
Stage 2
•(#51) Establish Framework and Working Model (Tools, Methodologies, Processes)
•Current State Architecture with Future State Directions
•“Operational” Architecture (Project by Project) -> IST Architecture
Stage 3
•(#52,#86) Develop / Refine EA Product and Practices
•Living “Current State,” Adapting “Future State,” w/ Roadmaps
•Kaizen “Tactical” Architecture (Unit) -> “Strategic” Architecture (Waterloo)
Fall 2015
2017
2018

12. Enterprise Architecture (EA)
Architecture Practice Scope

13. ENTERPRISE DATA MANAGEMENT
(IST-EA-EIM-EDM)
Roadmap + Scope

14. Enterprise Data Management (EDM)
Roadmap
Stage 1
• (#42) Cognos On-Going Platform & Project Work
• Continue and complete migrations (Lib, Fin, RO, GSO, HR).
• Production Cognos and Data Warehousing for Waterloo Users
Stage 2
• (#44) Enterprise Data Management Development
• Develop API creation capability.
• Experiment with Microsoft Business Intelligence
Stage 3
• (#45) Towards Enterprise Data Management Practice
• Get all source data into common warehousing. Support long-term analytics.
• Improve APIs, reporting, security, and reduce overall number of copies of data at rest.

15. Enterprise Data Management (EDM)
Scope
http://edmcouncil.orghttp://dama.org

16. ENTERPRISE CONTENT MANAGEMENT
(IST-EA-EIM-ECM)
Roadmap

17. Enterprise Content Management
(ECM) Roadmap
Stage 1
• (#46) OnBase On-Going Platform & Project Work
• Maintenance of OnBase. Upgrades and required system changes.
• Improvements for existing customers (RO, GSO) and new customers.
Stage 2
• (#48) Enterprise Content Management Development
• ImproveIntegration and Interfaces w/ SSO + ERP system improvements.
• Explore Integration / Connection to other Content Systems (Sharepoint,WCMS)
Stage 3
• (#49) Towards Enterprise Content Management Practice
• Clarify Information GovernancePractices at AIGC. Build ECM Working Group.
• Establish global standards and procedures with University Records Manager.

18. Enterprise Content Management
(ECM) Scope
http://edrm.nethttp://dama.org