Download NYC Enterprise Architecture

Anthony Insolia
Director, Enterprise Architecture
NYC EA
CTO Office
City of New York Department of
Information Technology and
Telecommunications
City of New York Enterprise Architecture (Internal Use Only)
1
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
NYC EA is a
repository of
information used
for planning
This planning information is gathered from
other existing operational data sources to
establish “line of sight” between technology
products and business goals and objectives and
to facilitate costing and informed decision
making
City of New York Enterprise Architecture (Internal Use Only)
2
Operational Data
Planning
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
NYC EA Framework is a set of standards
for planning data
The NEAF is a set of specifications for collecting and
organizing information using three foundational
frameworks and five industry-standard methods.
NYC EAF
Three Proven
Frameworks
Five Industry
Standard
Methods
3
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
APPLYING EA:
Idea
Architecting a house
or a business, the
process is:
Blueprints / Plans
(paper)
The Owner wants
$
$
(Portfolio Gap / Issue Identified)
$
Architecture
Repository
The Business Analyst /
Architect specifies
(Scoping / needs analysis)
(Translates ideas into plans)
Blueprints / Plans
(electronic)
OMB approves,
The ACCO bids
ACCO bids
(Procurement)
The Systems Integrator /
Engineer designs
Activity-Based Costing
City of New York Enterprise Architecture (Internal Use Only)
The Builder builds
4
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
How is it really done?
Programs like ECTP do it with architecture activities,
tasks, work products, deliverables, methods, and roles
embedded in the program lifecycle and collected via
plans based on a standard set of program phases and
milestones to enable governance.
City of New York Enterprise Architecture (Internal Use Only)
5
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
The NEAF treats the City
portfolio as a collection of
capabilities delivered by
programs that embed
architecture activities
designed to gather
information required to make
investment decisions.
The NYC EAF is also the
basis for the creation of
reference models that are like
zoning maps and ordinances
for the development of
capabilities.
The information is stored in
the NYC EA and passed on
from mayor to mayor: the City
doesn’t skip a beat.
City of New York Enterprise Architecture (Internal Use Only)
6
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
DOITT is applying the NEAF in
gathering and recording
information about Foundational IT
initiatives
– NEA Reference Models (BRM, TRM)
– Service Management
– Emergency Communications (911)
– Emergency Notifications
– Identity and Access Management
– others
7
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
“Service Management” (ITIL) Capability
• Assuring that the IT investments are aligned with the goals
and objectives
• The estimated cost of “Service Management” capability is
understood before and investment decision is made
• That capability/service/system/application information is
preserved so as to avoid rediscovery costs
Service
Management
OMB
Blueprints
$
“Baseline”
Solicitation
NEAF
Content
and
information
Standards
City of New York Enterprise Architecture (Internal Use Only)
Service
Management
OMB
Blueprints
$
“To-Be”
8
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
NYC Enterprise Architecture
Public Safety Access Center (PSAC)
• Information required for business continuity and operations
is recorded in the early stages of the program via
“architecture” activities and tasks
• Service Desk based on Gartner “Liaison Model” to include
the use of Blueprints by the Service Desk during problem
determination
PSAC 1&2
PSAC I
OMB
Blueprints
“Baseline”
$
Blueprints
Solicitation
NEAF
Content
and
information
Standards
City of New York Enterprise Architecture (Internal Use Only)
PSAC 1&2
Blueprints
“As-Is”
9
OMB
“To-Be”
$
Transition Plan
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
DOF/DOITT EA PARTNERSHIP
NYC ENTERPRISE ARCHITECTURE
AN AGENCY VIEW
Jane Landon Deputy Commissioner & CIO
New York City Department of Finance
10
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
Capability 1 Goals,
Objectives,
Strategies
An Agency
View of the
Enterprise
Architecture
Framework
Planner's View of the Capability
What
How
List of Defined List of Services
concepts and
and Processes
data as well as associated with
their
the Capability
authoritative
sources
A
Owner's View
What
Data Attributes
and
relationships
between the
classes of data
Where
Who
When
Why
List of
geographic
regions in
which the
Capability
operates and
serves
List of
Communities of
Interest,
Agencies,
Programs, and
Governance
Bodies
Capability
Maturity Plans
with dates for
achiving a
maturity level,
goals, and
objectives
List of Goals,
Objectives,
Material
Weaknesses,
Gaps, State
and Federal
Laws, City Laws
Who
When
Why
Organization
charts, mission
statements and
a mapping of
roles to
organizations
that require
them
Scheduling
factors and
timelines for
addressing
requirements,
gaps, and
findings.
Business
Events
Functional and
non-functional
requirements
aligned to goals
and objectives
and Services
that comprise
the capability
Who
DODAF based
organization
structures, role
assignments,
and staffing
plans
When
Business
events
embedded in
process models
as triggers and
outcomes of
processes
Why
Business rules
embedded in
the context of
processes
of the Capbility
How
Where
Process
Relationships
information
among
flows and a
locations,
mapping of
informationprocesses to
exchange
affilated roles, requirements,
applications,
and mapping to
policies, and
information
training
exchanges
Designer/Eng
ineer's View
of the
Capability
What
How
IDEF1X based BPMN based
Data Models
Process Models
and a mapping
of processes to
Services
B
Where
DODAF based
models of
Physical
locations in
which systems
reside and
network
connections
11
C
NYC ENTERPRISE ARCHITECTURE
REPOSITORY
Enterprise Elements &
Inter-agency Shared Services
DEPARTMENT of FINANCE
ARCHITECTURE REPOSITORY
Capabilities Specific to DOF
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
Example 1
DOF NOTICING
CAPABILITY
Planner's View of the
Capability
What
How
Where
Provide flexibable SOA, Statement of
Varibable
automated
value, late notices, DOITT data center
noticing service.
rebate etc.
Maiframe Unix and
Data-Property Info,
ProcessesWindows platforms
Owner Name
property tax,
effected
(ACRIS)
assessment,
collections etc
A
Who
DOF Divisions,
OMB,
Governance
DOF Functional
and Leadership
Governance
Councils. DOITT
software impl
When
Why
Time Need Install Stakeholders view.
on DOITT
Inability to support
Mainframe 6/08.
current tech.
SOA 1/09. Other Flexibility to design
148 converted by and adapt Notices
6/10
without IT
programing.
A
B
Owner's View of the Capability
What
How
Where
Who
Detail Varible data Detail per Notice Example property DOF DIVISIONS
Input per Notice on timing inputs put owner name from impacted by each
and notice output
ACRIS for SOA,
Notice type and
variable and
address of property family, DOF project
processes
unless specific
implementation
mailing address is and migration IT
requested.
resources
Designer/
Engineer's View of
the Capability
What
DOF Data Models
for property, corp,
city registry,
parking, records,
payments,
collections
When
Project approval
and funding.
Project planning,
resourcing and
cost plans
estimates.
Why
Business View.
Skills of required
for current
technology.
Need for Business
participation in
Notice design
/modifications
B
Capabilities Specific to DOF
C
How
DOF Business
Process Models,
process event
cycles and a
mapping of
processes to
Notice Service
Where
Who
DOF models of
Assigned time
Phys locations
specific detailed
Example: ACRIS
DOF based
systems resides
organization
Metrotech,
structures, role
leverages DOF and assignments, and
CITY networks
staffing plans
12
When
Why
DOF Business
Detail on each
events embedded
DOF Notice
in process models
Business rules
as triggers and
embedded in the
outcomes of a
context of that
specific notice NOTICE processes
DEPARTMENT of FINANCE
ARCHITECTURE REPOSITORY
C
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017
Agency Service Graduation to Citywide Shared
Service
Example 2
Credit Card
NYC Wide
Payment Service
Capability
A
Planner's View of the Capability
What
How
Where
Who
Provide credit card
Clearly defined
Service to be
Mayors office of
payment service for all association and bank
implemented on
operations,
city revenue collections. requirements and input Enterprise Service Bus consolidated billing,
out put schemas
to allow discovery and
payment, and
required as part of
utilization at agency
collections city
service documentation
level.
evaluation and
and implementation
implementation
design
Governance board.
Owner's View of the Capability
What
How
Where
Who
Detail data Input and Detail per specifications Example: Parking
All agencies that
out put data for
on timing inputs put and ticket paid on the WEB,
currently accept
accepting credit card output variable and for by phone, in person at payments. on the web
business processes. a business center with by phone or in business
Credit Card industry
a credit card.
center and future needs
Business Process
Internet connectivity
as they evolve.
Models aligned with
IVR connectivity, call
banking partner
center systems
example Global
connectivity, all
payments. Leveraging business center cashier
Associations schema
function connectivity
definitions and
parking violations
standards.
connectivity and
integration defined
Designer/
Engineer's View of the
Capability
What
How
Where
Who
Discovery of service
Detail schema and
Enterprise architecture City wide
and review of service in inputs puts and outputs and Enterprise service organization
NEAF Architecture
integrations to
bus connectivity.
structures, role
repository
administration systems
Agency by agency assignments, and
or SaaS site.
administrative system staffing plans for
(s) that need
utilization of service.
connection to service Sample role project
plans provided in
NEAF
B
13
When
By 11/09
When
Project approval and
funding.
Architectural review
and approval.
Project planning,
resourcing and cost
plans estimates.
Why
Stakeholders view.
Need to provide
payment vehicle
options to constituents .
Scale and financial
complexity
consolidation and cost
saving
Why
Business View. Must
make service reuseable by multiagencies. Must have
clearly defined
boundaries, easy to
understand, leverage
and integrate into
multiple and diverse
systems designs and
agency processes.
Must be visible for
agency IT discovery
and use.
C
When
Agency by agency
Business events that
trigger payment
embedded in process
models as triggers and
outcomes of a specific
credit card payment
service variables
Why
Detail on each
Business rules
embedded in the
context of a payment
processes
NYC Enterprise Architecture Repository
Enterprise Elements &
Inter-agency Shared Service
A
B
C
DEPARTMENT of FINANCE
ARCHITECTURE REPOSITORY
Capabilities Specific to DOF
Prepared by Dept. of Information Technology & Telecommunications, July 8, 2017