Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
p
ITAG, version 2.0We need resource commitments!
February 2013 - ITLC
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pFor ITAG V.2 to Succeed…Appointment is based on Member Role Profile• Has the requisite skills, knowledge and abilities
Members commit to the necessary level of effort• ~10-25% FTE (4-10 hours/week, minimum)
Uses Project and Service Management methodologies• Track and communicate status all requests• Members rotate PM duties and work within the EA Team PM
Framework
Collaborates and partners with UCOP Shared Services• Enterprise Architecture Team
Governance/Oversight provided by ITLC• Selection and prioritization of engagements in the ITAG Workplan• Resolution of issues that cannot be resolved by ITAG and EA Team
February 2013 - ITLC2
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pITAG version 2.0Goals for 2013 and Beyond• Reconstitute our Charter, Membership, and Workplan• Establish clear governance and process framework(s)
o Partner with UC Shared Services Enterprise Architecture (EA) Teamo Common vocabulary and multi-directional communicationo Standardization and reuse of solutions
• Engage in system-wide effortso Provide decision support with campus perspectiveo Balance localizations against system-wide interoperability
February 2013 - ITLC3
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pWhat We Do (Our Value Add)Represent unmet needs at our respective locations• Business and technology needs/gaps • Inventory of existing campus architectures
Review and assess candidate solutions against campus readiness• Gap analysis, assessment and/or preparation of proposals• Research and recommend a solution(s)
Liaison for Campus implementation and adoption• UC EA Body of Knowledge Subject Matter Expertise• Curators of local Principles, Standards and Reference Architectures• Solution selection, feedback and issue resolution
Provide guidance and consultation• Implementation Planning• Campus Objectives for Service Agreements• Advocacy and Marketing Campaign(s)
February 2013 - ITLC4
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
p
By Request from• ITLC• EA Team• ITAG and UCTrust member(s)• External workgroups (ITPS, CTG, EALT, TAS, Other)
In Consultation with• EA Team• External workgroups• Campus IT Communities
Informed by• ITLC strategic priorities• Campus business requirements and CIO guidance• EA Body of Knowledge
How We Function
February 2013 - ITLC5
ITLC
EA Team
ITAGUCTrust
External
Campus IT Communities
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pWho We AreLocal resource to/forUC Shared Services Enterprise Architecture• Partners with EA Team• Advocates of system-wide
architecture and infrastructure• Champions for campus
implementations of system-wide systems
Efforts prioritized by ITLC• Members interact with their
respective CIO (periodic and regular status updates)
February 2013 - ITLC6
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
p
Our Wiki and Email List• https://spaces.ais.ucla.edu/display/ucitag/Home• [email protected]
v2.0 Documentation• Charter• Member Role Profile• Workplan
Additional Information
February 2013 - ITLC8
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pExpectations of Membership
https://spaces.ais.ucla.edu/display/ucitag/ITAG+Member+Role+Profile
February 2013 - ITLC9
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
p
Month 1 2 3 4 5 6 7 8 9 10 11 12
Integrate with ITLC, EA & Other Teams
A Timeline (DRAFT)
EAA Framework
ITAG Work Intake Methodology
Repository (Tool)
F2F
F2F
Campus Inventories
ITLC ITLC
SOA Reference Architecture for UCPath
MDM Education (for ITAG members)
Campus Integrations
Integrate into Ticketing System
Very drafty. This needs to reflect the workplan confirmed by ITLC and Jerome's team,
and bounded by ITAG capacity for each effort.
Standards, Principles, Reference Architectures
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
ITAGTelecon
EA/SOA "introduction" to locationsEA/SOA marketing campaigns Localization of EA artifacts
February 2013 - ITLC10
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pOur Definition
Enterprise Architecture (EA) is a practice designed to achieve alignment of people, process and technology in support of UC
mission, vision and strategy.
Value Add Across UC:• Consistency and interoperability of technology, data and process
• Shortened delivery timelines, improved quality, reduced redundancy, and increased reuse
• Supports UC’s overarching business and technology strategy
February 2013 - ITLC11
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pThe EA Body of Knowledge (EA-BoK)UC EA-BoK• Repository of documentation (people, process, technology)• Architectural assets are made available to each location• Enables consistency and interoperability of technology deployments
UC Shared Services EA Team• Primary Curator of the Repository• Establishes and maintains the body of knowledge• Ensures the EA-BoK is available and accessible across the UC system
IT Architecture Group• Facilitates local consultation and feedback• Enables local adoption and integration• Participates in maturation (continuous improvement)
February 2013 - ITLC12
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pBenefit Statements
We can only realize the full value of UC Enterprise Architecture by establishing a collaborative working model
for EA functions across the system.
When Architectural assets are managed and subsequently utilized across UC, consistency, interoperability, and reuse
will be achieved.
February 2013 - ITLC13
Info
rmatio
n Tech
no
log
y Arch
itecture G
rou
pSome Interesting Statistics
Source:Enterprise Architecture Survey Results from the January 2010 DDJ State of the IT Union Survey
http://www.ambysoft.com/surveys/stateOfITUnion201001.html
February 2013 - ITLC14