49
Best Practices for Meeting State Data Management Objectives How ER/Studio Helps Texas Agencies Achieve Strategic Plan Goals

Best Practices for Meeting State Data Management Objectives

Embed Size (px)

Citation preview

Page 1: Best Practices for Meeting State Data Management Objectives

Best Practices for Meeting

State Data Management

Objectives

How ER/Studio Helps

Texas Agencies Achieve

Strategic Plan Goals

Page 2: Best Practices for Meeting State Data Management Objectives

2

Agenda

• Data Management Defined

• State Strategic Plan Overview

• Planning for Data Management

• Enterprise Planning and Collaboration

• Overview

Page 3: Best Practices for Meeting State Data Management Objectives

3

Data Management Defined

• According to Data Management Association

• “The development and execution of architectures, policies,

practices, and procedures that properly manage the full lifecycle

needs of an enterprise”

Page 4: Best Practices for Meeting State Data Management Objectives

4

State Strategic Plan - Background

• Why is Data Management important?

• Emphasis from State CIO Karen Robinson that state agencies plan for data management growth and institute best practices

• State Strategic Plan Background

• Texas DIR developed Top 10 priorities that will affect all technology decisions

• IT’s role to deliver quality services to residents continues to grow

• How to best prioritize agency and statewide technology investments

Source: http://publishingext.dir.texas.gov/portal/internal/resources/DocumentLibrary/2014-2018%20State%20Strategic%20Plan%20for%20Information%20Resources%20Management.pdf

Page 5: Best Practices for Meeting State Data Management Objectives

5

State Strategic Plan - Background

• There are several current practices in the Texas

Government that support best practices and sound

data management:

• Agencies are required to develop controls to ensure

confidentiality, integrity and availability of data

• Agencies implement internal data governance structures to

guide agency-wide policies

• The Texas Legislature requires agencies to develop a standard

format for data sets for public accessibility, as well as to develop

a Records Management Program

Source : http://publishingext.dir.texas.gov/portal/internal/resources/DocumentLibrary/2014-2018%20State%20Strategic%20Plan%20for%20Information%20Resources%20Management.pdf

Page 6: Best Practices for Meeting State Data Management Objectives

6

Planning for Data Management

• Key Areas Addressed by ER/Studio

• Eliminate data silos

• Reduce costs through data reuse & standardization

• Protect confidential info

• Decrease likelihood of security incidents due to improper data

classification

• Ensure compliance with data record management policy

Page 7: Best Practices for Meeting State Data Management Objectives

7

Eliminate Data Silos

• Why is this important?

• Increase intra-agency cooperation & trust

• Improves transparency, data quality and accountability,

allows data to be shared

Page 8: Best Practices for Meeting State Data Management Objectives

8

Data Reuse and Standardization

• Why is this important?

• Reduces costs and time by not having to start from

scratch

• Standardization helps ensure compliance and avoid

fines

Page 9: Best Practices for Meeting State Data Management Objectives

9

Protect Confidential Info/Reduce Risk of

Improper Data Classification

• Why is this important?

• Ensures regulatory compliance and reduces risks of fines

• Safeguards against security incidents

Page 10: Best Practices for Meeting State Data Management Objectives

10

Record Management Compliance

• Why is this important?

• Ensures regulatory compliance

• Ease of data request management

• Promotes data stewardship in complex environments

Page 11: Best Practices for Meeting State Data Management Objectives

11

Enterprise Planning and Collaboration

• Key Areas Addressed by ER/Studio

• Reviewing and aligning IT governance across all organizations

• Using project management to facilitate cross-division

collaboration

• Aligning objectives and outcomes with strategic goals

• Implementing online collaboration tools

Page 12: Best Practices for Meeting State Data Management Objectives

12

Enterprise Planning and Collaboration

• Why is this important?

• Working together allows the state to better manage

expenditures and operate more effectively

• Collaboration affects the degree to which the state maximizes

return on IT investments ($$$!!)

Page 13: Best Practices for Meeting State Data Management Objectives

13

How does ER/Studio Help?

Page 14: Best Practices for Meeting State Data Management Objectives

14

Planning for Data Management

• Key Areas Addressed by ER/Studio

• Eliminate data silos

• Reduce costs through data reuse & standardization

• Protect confidential info

• Decrease likelihood of security incidents due to improper data

classification

• Ensure compliance with data record management policy

Page 15: Best Practices for Meeting State Data Management Objectives

151515

ER/Studio Enterprise Team Edition

Page 16: Best Practices for Meeting State Data Management Objectives

16

Eliminate Data Silos

• How does ER/Studio help?

– Inventory existing databases to determine: 1. What common data exists between silos

2. What data should be shared across the organization

– Connect users w/ subject matter experts (SMEs)

– Team Server collaboration

Page 17: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Complex Data Environments

Evolution:

• 38 years of construction

• 147 builders

• No Blueprints

• No Planning

Result:

• 7 stories

• 65 doors to blank walls

• 13 staircases abandoned

• 24 skylights in floors

• 160 rooms, 950 doors

• 47 fireplaces, 17 chimneys

• Miles of hallways

• Secret passages in walls

• 10,000 window panes (all bathrooms are fitted with windows)

Ad-hoc architecture and lack of strategy

17

Page 18: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Complex Data Landscape

18

• Comprised of:

– Proliferation of disparate systems

– Mismatched departmental solutions

– Many database platforms

– Big Data platforms

– ERP, SaaS

– Obsolete legacy systems

• Compounded by:

– Poor decommissioning strategy

– Point-to-point interfaces

– Data warehouse, data marts, ETL …

Page 19: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Eliminate Data Silos:Inventory existing databases

• What type of data do you posses and where can it be found.

• Map your data landscape using data models as the foundation.

– Each model represents a different database system

– Link like data elements together for traceability

19

Page 20: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Eliminate Data Silos: Inventory existing databases

• Reverse Engineer & MetaWizard

– The ability to create a data model by connecting to an existing data store

• Native connector

– Relational

– Big data

• ODBC

• Can also be SQL script rather than direct connection

• Other models and metadata repositories

– Vital to map & analyze complex data landscapes

20

Page 21: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Eliminate Data Silos:Inventory existing databases

• Native Big Data Support

– MongoDB• Diagramming

• Reverse & Forward Engineering (JSON, BSON)

• MongoDB certification for 2.x and 3.0

– Hadoop Hive• Forward & Reverse Engineer DDL

• Certified for Hortonworks Data Platform (HDP) 2.1

21

Page 22: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Eliminate Data Silos:Inventory existing data types

• What about ERP & SaaS?

– Difficult to comprehend • Cryptic table and column names

• Internal data dictionaries

• Thousands of tables

• Often don’t implement referential integrity in the database

– Safyr – Technology Partnership

22

Page 23: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Eliminate Data Silos:Connect with SMEs

• Collaborate with SMEs using ER/Studio Team Server

– Break down barriers of SME silos • Organizations suffer from SME silos as well as data silos

23

Page 24: Best Practices for Meeting State Data Management Objectives

24

Data Reuse and Standardization

• How does ER/Studio help?

– Define, apply, and enforce naming standards across database systems

– Eliminate data redundancies and errors with data domains

– Document databases with the entire organization in mind

– Create a catalog of existing databases that can be easily accessed and reused

• Team Server exposes the catalog and makes it easily searchable

• Users may make comments and start discussions

Page 25: Best Practices for Meeting State Data Management Objectives

25

Data Reuse and Standardization: Define/apply/enforce naming standards

• Typical use case– Logical -> physical

• Entity name -> table name

• Attribute name -> column name

• Landscape Mapping– Physical -> logical

– Table name -> entity name

– Column Name -> attribute name

Page 26: Best Practices for Meeting State Data Management Objectives

26

Data Reuse and Standardization: Eliminate data redundancies and errors

Page 27: Best Practices for Meeting State Data Management Objectives

27

Data Reuse and Standardization: Document databases with the entire organization in mind

• Data that is not understood will not be reused

• Consider the different user types that may need to

leverage this documentation.

• Create various layers of abstraction

Page 28: Best Practices for Meeting State Data Management Objectives

28

Data Reuse and Standardization: Create an easy-to-access catalogue of databases

Page 29: Best Practices for Meeting State Data Management Objectives

29

Protect Confidential Info/Reduce Risk of

Improper Data Classification

• How does ER/Studio help?

– Document sensitive data for regulatory compliance• PII, highly confidential, security impact, etc.

– Increase awareness of sensitive data by using ER/Studio

Team Server alerts

– Ensure sensitive data is available only to privileged users

Page 30: Best Practices for Meeting State Data Management Objectives

30

Protect confidential information:Document sensitive data

• Include security tags along side of tables and columns

so auditors and other users know where this data lies

and how to use it.

Privacy Level Security tag

Page 31: Best Practices for Meeting State Data Management Objectives

31

Protect confidential information:Increase awareness of sensitive data

Page 32: Best Practices for Meeting State Data Management Objectives

32

Record Management Compliance

• How does ER/Studio help?

– Use of data domains to ensure that data is being properly stored

– Classify data so that it can be properly managed

• Master, reference, transactional, etc.

– Include data lineage in your landscape map for data traceability

Page 33: Best Practices for Meeting State Data Management Objectives

33

Record Management Compliance: Properly classify data

Page 34: Best Practices for Meeting State Data Management Objectives

34

Record Management Compliance: Include data lineage in your landscape map

Page 35: Best Practices for Meeting State Data Management Objectives

35

Enterprise Planning and Collaboration

• How does ER/Studio help?

• Using data modeling to define data standards within and across

agencies = promotion of higher data quality

• Naming standards, domain standards, data classifications, etc.

• Team Server – “business-driven data architecture” = uniting

business and IT

Page 36: Best Practices for Meeting State Data Management Objectives

36

ER/Studio Team Server Overview

Page 37: Best Practices for Meeting State Data Management Objectives

37

What is ER/Studio Team Server?

Team Server is a web environment that delivers a new class of capabilities extending the reach of enterprise data across departments and throughout the organization.

Simple, secure unlimited access is now available to:

• Provide a “self-service” view and navigation of the technical structure in enterprise data.

• Enable cross-departmental collaboration and full traceability of all changes and discussions.

• Manage a single source of business definitions in enterprise glossaries.

• Integrate key business terms and definitions with technical content for greater comprehension.

ER/STUDIO TEAM SERVER PROMOTES BUSINESS DRIVEN ARCHITETURE

Page 38: Best Practices for Meeting State Data Management Objectives

38

Life Without Team Server

• Issues connecting teams and departments with data content:

– Discussions around data management

• Written / Printed Documents

• Loose notes

• Whiteboard sessions

• Email

– Content flow and Storage

• Overwhelming options for storage and sharing of critical documentation

– Enterprise Content Management Platform (SharePoint)

– Spreadsheet Workbooks

– Local Files

– Network Files

– Public Information…

– “Silo” effect resulting in a poor understanding of the data landscape

• Tribal-knowledge

• Redundant work

• Lost Time

Page 39: Best Practices for Meeting State Data Management Objectives

39

Before Team Server

Page 40: Best Practices for Meeting State Data Management Objectives

40

After Team Server

Page 41: Best Practices for Meeting State Data Management Objectives

41

Environment Overview

Tap into the ability to collaborate, define relationships, and

track changes around business terms, technical structure,

and deployment information.

– Business Glossaries and Terms• Custom fields and content

• Insightful business perspective related to technical content

– Technical Structure • Simple way to search and view technical metadata and structure.

– Deployment Information • Store all data sources and show relationships to model diagrams.

Page 42: Best Practices for Meeting State Data Management Objectives

42

Business Definitions

Quickly find relevant information based

on business meaning

» Leverage business glossaries and terms with:

– Custom fields and content Definition

Department

Abbreviation

Data Steward…

» Create insightful business perspective related to technical content

Page 43: Best Practices for Meeting State Data Management Objectives

43

Structural Metadata & Security Compliance

Improve productivity and accuracy in

data analytics, application, BI and ETL development

» Technical Structure

– Simple way to search and view

technical metadata and structure. Column name

Data type

Business rule

Data model name…

Page 44: Best Practices for Meeting State Data Management Objectives

44

Deployment Metadata & Syndication for All

Navigate straight to the source of information assets.

Provide relevant metadata inline with workflows.

» Deployment Information

– Store all data sources and show relationships to model diagrams. Data Source Name

Application Name

Data Source Type

Data Source Server Name

Page 45: Best Practices for Meeting State Data Management Objectives

45

Collaboration for Better Data and Metadata

Communication between team members in departments ranging from data modelers, developers, analysts, and business stakeholders is critical for creating and maintaining a strong data management system.

Page 46: Best Practices for Meeting State Data Management Objectives

46

Integrate Terms & Policies with External Applications

Deploy business definitions to external URL’s and REST API functional applications.

Stay compliant with sensitive data

alerts while using other Embarcadero

products. Team Server

Page 47: Best Practices for Meeting State Data Management Objectives

47

Centralized Business & Technical Reporting

Page 48: Best Practices for Meeting State Data Management Objectives

48

Q&A

Page 49: Best Practices for Meeting State Data Management Objectives

EMBARCADERO TECHNOLOGIES

Thank you!

• Learn more about the ER/Studio product family: http://www.embarcadero.com/data-modeling

• Trial Downloads: http://www.embarcadero.com/downloads

• To arrange a demo, please contact Embarcadero Sales: [email protected], (888) 233-2224

49