Post on 17-Dec-2015
Unclassified 1
Enterprise Data Management and NIEM “Positive Impacts on Information Sharing”
December 2010
Unclassified 2
Agenda
• Introductions and Level Set• Enterprise Data Management and NIEM at DHS• How EDM and NIEM support agency EA and
Segment Architecture Processes• Break• How EDM and NIEM align with Information
Sharing Environment • EDM Best Practices and the Data Management
Working Group – How Data SMEs Collaborate• Roundtable
Unclassified 3
You are not alone in this world
• Who is here – data architects and SMEs, data managers, and interested parties
• Nuggets from Forrester Report“What is less understood by Mission areas than business
and data architecture – technical and application architectures are the focus of most EA programs”
• Insights from Gartner report“Data Management will fail to yield expected results unless
organizations adopt rigorous data governance and improved data integration planning”
Unclassified 4
So why does Enterprise Data Management matter?
•Critical
data questions you may be
interested
in:
•Who manages this data?
•Where is it stored?•Who can access this data?
•How accurate is it?•How recent is it?•How trustworthy is it?•How is this data related to other data elements in the enterprise—i.e., what is the associated context?
Enterprise Data Management is critical to the data architecture component of EA Frameworks and drives improved understanding and trust of data sources
Unclassified 5
So let’s talk about Enterprise Data Management and NIEM at DHS
Unclassified 6
DHS Enterprise Data Management Office
Enterprise Data Management (EDM) MISSION
Promoting collaboration to achieve efficient management of
Data and
Information
Find -Understand -Access -Trust -Use -Share -
In support of the
DHS Mission
all data collected, created, used, maintained, shared, stored and disposed by DHS.
Fostering innovation and elevating best practices to strengthen and enable the Homeland Security community to:
Unclassified 7
Enterprise Data Management Core Values
• Excellence – providing knowledge, trust and
expertise
• Collaboration – working together we can make a
difference
• Customer Service – voice of the Customer is
the most important
• Recognition – give credit for good work and ensuring best
practices are elevated
• Team Building – the community is only as strong as our weakest
link
Unclassified 8
What DHS Enterprise Data Management is
Enables effective enterprise data management, information sharing, and data reuse across agencies. It utilizes the FEA Data Reference Model (DRM) Framework
The DHS DRM is a framework for the visualization, discovery and reuse of enterprise data architecture assets
Provides guidance to Components
Allows for bi-directional alignment of artifacts
Unclassified 9
Enterprise Data Management Concept of Operations (ConOps)
• Establishes what it means to
“operationalize” the DHS Enterprise Data Management (EDM) and DRM - to enable
information discovery, sharing, exchange, and
reuse across DHS
• Describes Governance, Architecture,
Information Sharing, and Performance
Measurement practice areas
• Identifies the general types of resources
required to be obtained through the
budget cycle or redirected
• Sets the scope and provides a high-level roadmap for DHS and
its Components to mature data
management practices to attain a target state
in which data and information sharing
and reuse are enabled via the EDM framework
Unclassified 10
DHS Enterprise Data Management Roadmap
EDM Concept of Operations Roadmap 10/01/2009
Information Sharing Goals
Data Quality & Data Governance
ConOpsv 2.0ConOps v1.3
ConOps v1.1
EA Information Repository (Requirements & Development)
Data Management Tenets
Introduce Stewardship
Model
Identify standard
processes
Refine Stewardship roles & responsibilities
NIEM & IEPDDevelopment
SELC Touchpoints
Alignment with Touchpoints
Modeling, Methodologies &
Alignments
Reporting & Taxonomy
Requirements
Information Exchange & ISAA
Requirements
Modeling Standards and Tools
Data Stewardship Framework
Value & Performance
ConOpsv2.1
Shared Data Lifecycle
Investment & Performance Reviews & Dashboards
Functional Area LDMs & Trusted Data Sources
Data Management Summits & SMC Data Workshops
Data Asset Catalog Requirements
DMP Template
Performance Management Framework HLS ECDM Requirements
Business Reference Model Requirements
HLS Systems Requirements
Completed In Progress FY10 Future
Unclassified 11
So how are you doing your information sharing and getting everyone to talk in
the same terms?
Unclassified 12
NIEM Overview
In addition to providing guidance and support for all aspects of data management and information sharing within the DHS mission, …
Since September 2008, the Enterprise Data Management Office has been serving as the lead Program Management Office of the National Information Exchange Model (NIEM) program for the U.S. Government and its State, Local, tribal and private sector partners.
“Common Language” for Information Exchange
Components of NIEM data model Repeatable, reusable process for business users to document information exchange requirements
Unclassified 13
DHS and NIEMInformation Sharing
• DHS Adoption has gone from 0% to 40% of major IT programs, forecasted to be 60% by FY11
• NIEM projects are in development with over 90% of Components
• Measurement of Adoption and Project progress tracked on the CIO Enterprise Data Management Scorecard
– FY08 thru FY10: 30 NIEM projects completed
– FY11: 40-50 NIEM Projects projected
• Mandated within the HLS Enterprise Architecture for Common or Shared [SOA] Services on the Enterprise Bus
• Mandated by PM ISE’s implementation of Common Terrorism Information Sharing Standards (CTISS)
• Mandated by OMB for cross agency sharing and supported by HHS, USDA and Treasury
• DOJ and DHS grant language for State and Locals includes NIEM conformance
• Several Fusion Center RFP’s have been released requiring NIEM conformance
Component Project Name
CBP
• Federal Motor Carrier Safety Administration• Enforcement (EID) to Seized Assets and
Catalog System (SEACATS) Sharing• US Census – Entry Summary• US Census – Business Partner• NCIC/NLETS queries• Border Patrol Tracking System• Blue Force Tracking (SBI P.25)• U.S. Passport Query Interface
USCIS • Person Centric Query• Verification
FEMA• Exercise Scheduling• Improvement Plan
US-VISIT • US IDENT to CJIS IAFIS
S&T • Hospital Availability Exchange
DHS• Core Biographic Elements for Screening and
Immigration• Terrorist Watch Listing (TWPDES 1.2b)
ICE• Law Enforcement Info Sharing Services (LEISS
v1.0 & LEISS v2.0)• Removable Alien Query (RAQ)
DNDO • Radiological / Nuclear Detection
Unclassified 14
Improving Information Sharing through the use of data models • The Logical
Data Model (LDM) is the source for identifying what data types are
available for sharing
within an organization or mission
area.• By
incorporating data entities
from the logical data model into the information
exchange model,
exchange modelers can
assure stakeholders
that exchange elements are in fact available
and being derived from
common source.
• If a new information exchange
requirement develops then the LDM must be
updated to support the new requirement
• The Information Sharing landscape
provides a complete picture of a component’s data environment
Unclassified 15
Logical Data Model and NIEM Exchange Model Integration
Unclassified 16
How EDM and NIEM fit in DHS EA and Segment Development Processes?
Unclassified 17
DHS Enterprise Architecture
• DHS Segment
Architectures
• Benefits Administrati
on • Domain Awareness
• Law Enforcemen
t
• Incident Managemen
t
•Screening
•Securing
• Enterprise Mission Services
• Enterprise Business Services
• Enterprise Information
Technology (IT) Services
The Functional Areas serve as the underlying structure, and neutral lens, for planning and assessing performance of DHS resources and capital investments.
Unclassified 18
DHS Segments Information Landscape
DHS Logical Data Model
DHS ConceptualData Model
Incident Management
Law Enforcement
Domain Awareness
Securing
Immigration Management
Screening
Function Area logical data models
Unclassified 19
EDM Support to DHS Segment Architecture Development
• Data Architecture Templates and planning documents
• Data and information sharing artifacts in System Engineering Life Cycle (SDLC)
•Data and information sharing artifacts in Segment Architecture planning processes
•Data management wording in ITAR (acquisition) and SOW language
DHS Data management plays a significant role in identifying the architectural influences that data and information play in developing solutions that meet mission needs. So how did we do that?
Unclassified 20
Support to DHS Enterprise Architecture Development
• EDMO drives the information definition and management support required by Enterprise Architecture frameworks to meet mission needs
– Identifying information sources, information exchanges, and data services for the information sharing environment
– Driving data source and information exchange reuse for new
investments by mandating inclusion in the EA Information Repository
– Support to Investment Programs by reviewing their data architecture plans and providing feedback where appropriate and needed
Unclassified 21
Support to DHS SOA Deployment
• EDMO drives the use of NIEM for service development– This includes required use of
NIEM for information exchange definitions
– Promoting common exchange definition and reuse to reduce development and maintenance costs
• NIEM has traditionally been about the definition of the payload but EDMO has been a leader in looking at the message header and package requirements from a data perspective. Common header development is moving forward as seen in the timeline
New strategy: “Interoperable Component ESBs”Original strategy: “One DHS ESB”
JAN 06 JAN 07 JAN 08 JAN 09
Sep 05DHS Team 5
Standards & MethodsFocus Group
initiates SOA guidance
Oct 07DHS NIEM Blue Team
People ScreeningMessage Header WG
harmonization ofDHS screening headers
Mar 08DHS NIEM Blue Team
People ScreeningMessage Header WG
publishes Screening MessageHeader Guidance Report
Jun 08DHS NIEM Blue
Team and S2AWGNIEM and SOA experts
join to develop fullheader framework
Jan 05Original
DHS Team 5defines the need for
SOA at DHS
May 06DHS SOA
Tactical Focus Groupinitiates SOA
technical framework
Mar 07DHS EAB & EACOE
approve SOATechnical Framework v1.0
into the HLS EA
Jan 06DHS Team 5 CIOs
approve DHS Team 5SOA Guidance
Oct 09DHS SOA Enterprise
Message HeaderFramework Team
piloting of cross-ESBinteroperability and audit-ability
Jan 09DHS SOA Enterprise
Message HeaderFramework Team
review alpha-verstion ofthe header framework
Unclassified 22
EA Information Repository (EAIR) and Data Reference Model Support
• A centralized repository that
enables the search, discovery, and reuse
of Enterprise Architecture assets used by DHS and its
component organizations
•It supports DHS alignment to the
Federal Enterprise
Architecture (FEA) Reference
Models
• Metadata for each data asset and
information exchange gives both business
and technology users the information they require to determine
if this is a reuse candidate
Unclassified 23
DHS Information Sharing Environment (ISE)
Unclassified 24
EDM Best Practices and the Data Management Working Groups –
How DHS Data SMEs Collaborate
Unclassified 25
EDM Waves of Change
Unclassified 26
Waves of Data Management Change
Data Management Maturity is a fundamental change in how organizations address their vision and management of information – going from reactive to optimized
The wave concept has been around for some time and is based on the idea that each new wave builds on the momentum generated by the previous wave
Unclassified 27
Implementing Data Management Maturity
• Collaborative Working Groups - DMWG / NIEM Blue Team
• DHS Best Practices– Data Management and Information Sharing Documents
and Guidance– EDM Balanced Scorecard – Data Management Summits– Mission Specific Data Workshops– Data Management Office guidance for setting up and
operating with the Program or Component
• DM subject matter expert participation
Unclassified 28
Collaborative Working Groups
•EDMO Leader
ship
• NIEM Blue Team is
composed of information exchange
subject matter experts from
each organization
• Data Management
Working Group is composed of
data subject matter experts
from each organization
from with DHS
•DMWG Focus Teams drive best practice development and subject
matter guidance
Unclassified 29
Data Management Guidance Documents
•Information Exchange Package Documentation
• Data Modeling Methodology Guidance
•Data Stewardship Framework
•Data Management Plan
• Performance Management Framework
•Information Flow Modeling Guidelines
Unclassified 30
Support to DHS Enterprise Architecture Deployment
•LDM and NIEM integration•LDM development•Information Flows
• EA Planning
•Data Standards & Processes•Metadata development•Master Reference Data
• Data Governance
& Stewardship
•LDM and NIEM integration•Access agreements•Information exchange documentation
•Information
Sharing
Unclassified 31
Improving Information Sharing through the use of Mission Specific Data Workshops
• Data workshop
s with mission
area subject matter
experts, i.e.
Enforcement
Officers, Intelligen
ce Analysts
•Goal is to identify
their information needs
and sources of data
necessary for
supporting their mission efforts
• Utilized use
cases to documen
t the processe
s each used for gatherin
g information and making
decisions
•Generated information flows to
assist each
group in recognizin
g what informatio
n was available and what was not
being used by each
area
• Utilized EA Information Repository to identify what data
sources are available to
answer their
questions which
become new
information sharing
opportunities
Unclassified 32
DHS EDM Scorecard
DHS Enterprise Data Management Scorecard
PerformanceMeasuresGovernanceInformation
SharingData
Architecture
• Data Asset Catalog• % of Component
Systems mapped to Data Assets
• # of Data Assets Captured Score
• # of Component CDMs and LDMs mapped to Program Investments
• Component Taxonomy /Vocabulary Developed
• NIEM IEPDs in Pipeline
• NIEM IEPD Completion Score
• NIEM Adoption Score• NIEM Domain
Stewardship • Data Quality Plans • Authoritative Data
Source Identification and validation
• Data Management Plans mapped to Program Investments
• Stewardship Groups established (tactical, operational, strategic)
• Data Standards Established and Used
• Business Cases Developed
• Business Case with Metrics Developed
• % of Performance Metrics captured at Component Level
• PM Adoption Score
Wrap up Discussion
• EDM and NIEM have a proven track record at DHS for improving information sharing collaboration
Unclassified 33
• What else can we answer to aid your individual efforts at improving information sharing through EDM and NIEM?
• How can NIEM help your efforts?
The End
Unclassified 34