1prepared by dept. of information technology & telecommunications, january 12, 2016 nyc ea cto...

1 Prepared by Dept. of Information Technology & Telecommunications, April 21, 2023

NYC EANYC EACTO Office

City of New York Department of Information Technology and

TelecommunicationsCity of New York Enterprise Architecture (Internal Use Only)City of New York Enterprise Architecture (Internal Use Only)

Anthony InsoliaDirector, Enterprise Architecture

2 Prepared by Dept. of Information Technology & Telecommunications, April 21, 2023City of New York Enterprise Architecture (Internal Use Only)City of New York Enterprise Architecture (Internal Use Only)

NYC EA is a NYC EA is a repository of repository of information used information used for planningfor planning

This This planning informationplanning information is gathered from is gathered from other existing operational data sources to other existing operational data sources to establish “line of sight” between technology establish “line of sight” between technology products and business goals and objectives and products and business goals and objectives and to facilitate costing and informed decision to facilitate costing and informed decision makingmaking

NYC Enterprise ArchitectureNYC Enterprise Architecture

Planning

Op

era

tion

al D

ata

Components of, Views of

Integrated, Synchronized


Three Proven Frameworks

Five Industry Standard Methods

UM

L

IDEF

ABC

BPM

N

DoD

DoD

AF

FEA

F

Zachm

an


The NEAF is a set of specifications for collecting and organizing information using three foundational frameworks and five industry-standard methods.

NYC EAF

NYC EA Framework is a set of standards NYC EA Framework is a set of standards for planning datafor planning data


(Portfolio Gap / Issue Identified)

(Scoping / needs analysis)(Translates ideas into plans)

(Procurement)

The Owner wants

Idea

OMB approves,ACCO bids

The Business Analyst / Architect specifies

The Builder builds

The Systems Integrator / Engineer designs

Blueprints / Plans(electronic)

APPLYING EA:

Architecting a house or a business, the

process is: Blueprints / Plans(paper)

ArchitectureRepository

City of New York Enterprise Architecture (Internal Use Only)City of New York Enterprise Architecture (Internal Use Only)

The ACCO bids


ABC

Activity-Based Costing


How is it really done?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.



6 Prepared by Dept. of Information Technology & Telecommunications, April 21, 2023City of New York Enterprise Architecture (Internal Use Only)City of New York Enterprise Architecture (Internal Use Only)

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.

NYC Enterprise Architecture 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



Service Management

Blueprints

“Baseline”

Service Management

Blueprints

“To-Be”

AB

C

OMB

$

IV&

V

OMB

$



“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

SolicitationNEAF

Content and

information Standards

Industry

guidance


PSAC 1&2Blueprints

“To-Be”

SolicitationNEAF

Content and

information Standards

PSAC I

Blueprints“Baseline”

PSAC 1&2Blueprints

“As-Is”

AB

C

OMB

$

IV&

VOMB

$



Transition Plan

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


DOF/DOITT EA PARTNERSHIP

NYC ENTERPRISE ARCHITECTURE AN AGENCY VIEW

Jane Landon Deputy Commissioner & CIONew York City Department of Finance


An Agency View of the Enterprise Architecture Framework

DEPARTMENT of FINANCE ARCHITECTURE REPOSITORY

Capabilities Specific to DOF

Planner's View of the CapabilityWhat How Where Who When Why

List of Defined concepts and data as well as their authoritative sources

List of Services and Processes associated with the Capability

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

Owner's View of the Capbility

What How Where Who When Why

Data Attributes and relationships between the classes of data

Process information flows and a mapping of processes to affilated roles, applications, policies, and training

Relationships among locations, information-exchange requirements, and mapping to information exchanges

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

Designer/ Engineer's View of the CapabilityWhat How Where Who When Why

IDEF1X based Data Models

BPMN based Process Models and a mapping of processes to Services

DODAF based models of Physical locations in which systems reside and network connections

DODAF based organization structures, role assignments, and staffing plans

Business events embedded in process models as triggers and outcomes of processes

Business rules embedded in the context of processes

Capability 1 Goals, Objectives, Strategies

A

B

C

NYC ENTERPRISE ARCHITECTURE REPOSITORY

Enterprise Elements &Inter-agency Shared Services


Planner's View of the Capability

What How Where Who When WhyProvide flexibable

automated noticing service.

Data-Property Info, Owner Name

(ACRIS)

SOA, Statement of value, late notices,

rebate etc. Processes-

property tax, assessment,

collections etc

VaribableDOITT data center Maiframe Unix and Windows platforms

effected

DOF Divisions, OMB,

GovernanceDOF Functional and Leadership

Governance Councils. DOITT

software impl

Time Need Install on DOITT

Mainframe 6/08. SOA 1/09. Other 148 converted by

6/10

Stakeholders view. Inability to support

current tech. Flexibility to design and adapt Notices

without IT programing.

Owner's View of the CapabilityWhat How Where Who When Why

Detail Varible data Input per Notice

Detail per Notice on timing inputs put and notice output

variable and processes

Example property owner name from ACRIS for SOA,

address of property unless specific

mailing address is requested.

DOF DIVISIONS impacted by each Notice type and

family, DOF project implementation and migration IT

resources

Project approval and funding.

Project planning, resourcing and

cost plans estimates.

Business View. Skills of required

for current technology.

Need for Business participation in Notice design /modifications

Designer/Engineer's View of

the Capability

What How Where Who When WhyDOF Data Models for property, corp,

city registry, parking, records,

payments, collections

DOF Business Process Models,

process event cycles and a mapping of

processes to Notice Service

DOF models of Phys locations

Example: ACRIS systems resides

Metrotech, leverages DOF and

CITY networks

Assigned time specific detailed

DOF based organization

structures, role assignments, and

staffing plans

DOF Business events embedded in process models

as triggers and outcomes of a specific notice

Detail on each DOF Notice

Business rules embedded in the context of that

NOTICE processes

A

C

Example 1DOF NOTICING

CAPABILITY

A

B

C



B


Planner's View of the CapabilityWhat How Where Who When Why

Provide credit card payment service for all

city revenue collections.

Clearly defined association and bank

requirements and input out put schemas

required as part of service documentation

and implementation design

Service to be implemented on

Enterprise Service Bus to allow discovery and utilization at agency

level.

Mayors office of operations,

consolidated billing, payment, and collections city evaluation and implementation

Governance board.

By 11/09 Stakeholders view. Need to provide payment vehicle

options to constituents .Scale and financial

complexity consolidation and cost

savingOwner's View of the Capability

What How Where Who When WhyDetail data Input and

out put data for accepting credit card

Detail per specifications on timing inputs put and output variable and for business processes. Credit Card industry Business Process

Models aligned with banking partner example Global

payments. Leveraging Associations schema

definitions and standards.

Example: Parkingticket paid on the WEB,by phone, in person at a business center with

a credit card.Internet connectivityIVR connectivity, call

center systems connectivity, all

business center cashier function connectivity

parking violations connectivity and

integration defined

All agencies that currently accept

payments. on the web by phone or in business center and future needs

as they evolve.

Project approval and funding.

Architectural review and approval.

Project planning, resourcing and cost

plans estimates.

Business View. Must make service re-useable by multi-

agencies. 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.

Designer/Engineer's View of the

CapabilityWhat How Where Who When Why

Discovery of service and review of service in

NEAF Architecture repository

Detail schema and inputs puts and outputs

integrations to administration systems

or SaaS site.

Enterprise architecture and Enterprise service

bus connectivity. Agency by agency

administrative system (s) that need

connection to service

City wide organization structures, role assignments, and staffing plans for utilization of service. Sample role project plans provided in NEAF

Agency by agency Business events that

trigger payment embedded in process models as triggers and outcomes of a specific

credit card payment service variables

Detail on each Business rules

embedded in the context of a payment

processes

Example 2Credit Card NYC Wide

Payment Service Capability

A

B



NYC Enterprise Architecture RepositoryEnterprise Elements &

Inter-agency Shared Service

ABC

C

Agency Service Graduation to Citywide Shared Service

1prepared by dept. of information technology & telecommunications, january 12, 2016 nyc ea cto...

Documents