This document outlines how WorkSafe BC adopted CA ERwin Data Modeler and CA ERwin Model Manager to build and manage their enterprise data models. They faced challenges like standards adoption, new tool learning curves, and change management. They built infrastructure like standards, templates, and procedures. They then built their enterprise data model by merging existing models and resolving conflicts. For model management, they implemented processes for checking models in and out, using the model manager. This centralized their metadata and allowed for faster development and data consistency across projects.

1. A Practical Guide to Enterprise Data
Modeling and Model Management
Using ERwin
Tuesday, September 15, 2010 at 2pm ET

2. abstract
Are you getting the most out of your data models? Are your data
models spread out all over the place? Do you reuse or reinvent
when you build your data models?
If these are troublesome questions for you and your organization
then you may need a practical solution to address them.
During this session. See how WorkSafe BC, adopted a simple
straight forward approach to building and managing Enterprise
Data Models using CA ERwin Data Modeler and CA ERwin Model
Manager, that turned potential chaos, into value for the
organization.
PAGE 2

3. biography
• Garry Gramm
Enterprise Information Architect, WorkSafe BC
• ERwin Data Modeler user since Version 1.2. Was part of the beta
team for ERwin AOS - as ModelMart/ Model Manager was called in
the beginning under Logic Works, and have been on most CA ERwin
Data Modeler beta programs ever since.
• Currently a member of the CA ERwin Data Modeler Global User
Community board and a contributor to ERwin and InfoAdvisors
discussion forums.
PAGE 3

4. Topics
• Why CA ERwin Data Modeler
• Challenges
• Building infrastructure
• Building enterprise models
• Model management
PAGE 4

5. Why CA ERwin Data Modeler
• Wanted to replace legacy DM tool
• ERwin 3.x Provided Increased Functionality
– Logical data modeling
– Physical data base design
– Implementation of standards
• Needed to support future needs & objectives
PAGE 5

6. Challenges
• Standards & retro fitting
• New Tool = Learning curve
• Management commitment
• Architecture or not
• “Attitudes” - How to manage them
– People Issues
– Methodology requirements
– New approaches challenge validity
– Upgrade resistance
PAGE 6

7. Where are we?
Background
Why CA ERwin Data Modeler
Challenges
• Building infrastructure
• Building enterprise models
• Model management
PAGE 7

8. Building the Infrastructure
• Published Standards
– Naming, Classwords
– Data Definition, Diagramming
• Templates
– Standards, Patterns, Translation
• Procedures
– Modeling, check out/in, MM Maintenance
PAGE 8

9. Building the EDM
• Locate and gather all existing ERwin data models
• Merged by DBMS Type
• Reconciled conflicts
• DBMS specific Enterprise Data Models (EDM)
PAGE 9

10. Are we there yet?
Background
Why CA ERwin Data Modeler
Challenges
Building infrastructure
Building enterprise models
• Model management
PAGE 10

11. Model Management
• Check out
• Check in
• CA ERwin Model Manager
PAGE 11

12. Check Out Process
• Project team - checkout request
• Model Management - processes request
PAGE 12

13. Checkout Process Activities
• Project team
– Required entities
– New entities
– Validate new entity / table names
• Model management team
– Process checkout request
– Challenge new entities
– Create project model
PAGE 13

14. Checkout Tips
• Subject Area (SA) as small as possible
• Sync custom SA
• Specify minimal info on derive type selection
• Keep same named SAs
PAGE 14

15. Modeling Hints & Tips
Project Team
– Review before you build.
• Requirements
• Modeling semantics
• Standards compliance
Model Management Team
– Snoop around while project is ongoing
• Look at naming and metadata
• Gentle reminders
PAGE 15

16. Are we There Yet?
Nope - Not Yet!
PAGE 16

17. Check in Process
• Monitor WIP libraries
• Change Management Notification
• Verify updated project model
• Check in the model
• Close WIP library
• Update Spreadsheets
PAGE 17

18. Check In Activities
Project Team
– Model compliance
– Sync project model
Model Management Team
– Sync project model
– Merge project model
– Visually verify merged model
– Sync merged model
PAGE 18

19. Check-in Tips
• Sync project model
• Use same named SAs
• Use Complete Compare (CC) for the check in
• Use saved ‘type selection’ option sets
• Determine reconciliation strategy
• Have printed diagram handy
PAGE 19

20. Managing Model Manager
Steps to tune and increase MM performance
– Add MM server to SAN
– Partition data file groups
– Transaction logs on separate drives
– Re-index mart regularly
– Remove CA ERwin Data Modeler history
– Keep the mart lean
PAGE 20

21. Our Environment
Public Mart
Production
Read only
Libraries Admin Mart
DB2 SQLS
Project
Libraries
(WIP)
User Updatable
Copy
Archive
PAGE 21

22. Example of the ADMIN MART
PAGE 22

23. Summary
Background
Why CA ERwin Data Modeler
Challenges
Building infrastructure
Building enterprise models
Model management
PAGE 23

24. Benefits
• Faster development cycles
– Unified disparate models
– Re-use
– Rapid impact analysis
– What if scenarios
• Data consistency
• Single central source for metadata
• Metadata is easily shared
• Secure managed environment
PAGE 24

25. Are We There yet?
Yup – we’re done!
Thank you all for sharing your valuable time for this session.
I hope you found it useful and worthwhile.
If you have any other questions later on you can contact me
personally at :
Garry.Gramm@worksafebc.com
You can also find me on:
LinkedIn, ERwin.com, & InfoAdvisors.com discussion groups.
PAGE 25

26. Questions?
PAGE 26