This document provides a case study on using CA ERwin Data Modeler (CA ERwin DM) and CA ERwin Model Manager (CA ERwin MM) across insurance industries. It discusses why these tools were chosen over other options, how strategic business elements like vision and goals impact data modeling. Key elements of the tools like opportunities/threats and capabilities are examined. The document also includes practical demonstrations of using the tools, including reverse engineering, comparing models, and integrating the tools. Appendices provide a SWOT analysis and sample data model.
Effective capture of metadata using ca e rwin data modeler 09232010ERwin Modeling
CA ERwin Data Modeler provides flexible features to effectively capture metadata in data warehouse environments. This includes data sources, transformation rules, and data movement rules. It uses a customer dimension example to demonstrate capturing source tables from various sources, defining transformation templates, and attaching data movement rules to tables. Other options like importing metadata definitions from Excel allow business stakeholders to define and import column metadata. Effective metadata capture helps communicate requirements, identify issues, and understand the data model.
The document discusses CA ERwin, a data modeling tool that can be used to visualize data across different platforms through conceptual, logical, and physical data models in order to effectively manage increasingly complex data environments with multiple databases and applications. CA ERwin provides a centralized repository for storing metadata from multiple data sources and supports communication between business and technical stakeholders through intuitive reports and high-level conceptual models.
Cust experience a practical guide 09152010ERwin Modeling
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.
CA ERwin Data Modeler End User PresentationCA RMDM Latam
CA ERwin is a suite of data modeling products that allows users to model databases across multiple platforms from a single graphical representation. It reduces costs and improves database performance by standardizing database design. The latest release, ERwin 7.3, features enhancements such as ODBC-based metadata access, a SQL query tool, and template customizations. ERwin helps users manage growing database demands with fewer resources through its ability to support multiple database platforms from a single data model.
Generating Code with Oracle SQL Developer Data ModelerRob van den Berg
This presentation discusses code generation capabilities in Oracle SQL Developer Data Modeler. Key features that support code generation include logical and relational modeling, domains, naming standards, and transformation scripts. The presenter demonstrates how to generate various types of code like entity rules, triggers, and packages by writing custom transformation scripts to query the model object and output code to files. Well-designed models can be transformed into maintainable application code automatically.
Oracle Sql Developer Data Modeler 3 3 new featuresPhilip Stoyanov
This document discusses new features in Oracle SQL Developer Data Modeler version 3.3/4.0, including enhanced search functionality, improved handling of logical and relational models including surrogate keys and subtyping, and support for identity columns in Oracle Database. Key new features include global and model-level searching, setting common properties on search results, custom reports on search results, improved mapping of relationships and attributes to relational models, and configuration options for implementing entity hierarchies and generating dependent constraints.
The document provides an agenda and overview for a presentation on data access layer patterns and options. It discusses considerations for keeping data entities consistent or managing differences between objects and schemas. It also covers common patterns for each approach, including row and table data gateways, active record, domain models, data mappers, repositories, and unit of work. The presentation will assess data access technologies and discuss additional challenges like domain model responsibilities. Attendees can contact the presenter with any other questions.
The document discusses relational databases and how they organize data into tables that can be accessed and reassembled in different ways without reorganizing the tables, it also covers how PeopleSoft uses a 3-tier architecture called PeopleSoft Internet Architecture (PIA) consisting of a web browser, web server, application server and database server to deliver pure internet applications to users. PIA provides advantages over traditional client/server architectures like thin clients, improved performance, and the ability to scale more easily to meet increasing user demands.
Effective capture of metadata using ca e rwin data modeler 09232010ERwin Modeling
CA ERwin Data Modeler provides flexible features to effectively capture metadata in data warehouse environments. This includes data sources, transformation rules, and data movement rules. It uses a customer dimension example to demonstrate capturing source tables from various sources, defining transformation templates, and attaching data movement rules to tables. Other options like importing metadata definitions from Excel allow business stakeholders to define and import column metadata. Effective metadata capture helps communicate requirements, identify issues, and understand the data model.
The document discusses CA ERwin, a data modeling tool that can be used to visualize data across different platforms through conceptual, logical, and physical data models in order to effectively manage increasingly complex data environments with multiple databases and applications. CA ERwin provides a centralized repository for storing metadata from multiple data sources and supports communication between business and technical stakeholders through intuitive reports and high-level conceptual models.
Cust experience a practical guide 09152010ERwin Modeling
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.
CA ERwin Data Modeler End User PresentationCA RMDM Latam
CA ERwin is a suite of data modeling products that allows users to model databases across multiple platforms from a single graphical representation. It reduces costs and improves database performance by standardizing database design. The latest release, ERwin 7.3, features enhancements such as ODBC-based metadata access, a SQL query tool, and template customizations. ERwin helps users manage growing database demands with fewer resources through its ability to support multiple database platforms from a single data model.
Generating Code with Oracle SQL Developer Data ModelerRob van den Berg
This presentation discusses code generation capabilities in Oracle SQL Developer Data Modeler. Key features that support code generation include logical and relational modeling, domains, naming standards, and transformation scripts. The presenter demonstrates how to generate various types of code like entity rules, triggers, and packages by writing custom transformation scripts to query the model object and output code to files. Well-designed models can be transformed into maintainable application code automatically.
Oracle Sql Developer Data Modeler 3 3 new featuresPhilip Stoyanov
This document discusses new features in Oracle SQL Developer Data Modeler version 3.3/4.0, including enhanced search functionality, improved handling of logical and relational models including surrogate keys and subtyping, and support for identity columns in Oracle Database. Key new features include global and model-level searching, setting common properties on search results, custom reports on search results, improved mapping of relationships and attributes to relational models, and configuration options for implementing entity hierarchies and generating dependent constraints.
The document provides an agenda and overview for a presentation on data access layer patterns and options. It discusses considerations for keeping data entities consistent or managing differences between objects and schemas. It also covers common patterns for each approach, including row and table data gateways, active record, domain models, data mappers, repositories, and unit of work. The presentation will assess data access technologies and discuss additional challenges like domain model responsibilities. Attendees can contact the presenter with any other questions.
The document discusses relational databases and how they organize data into tables that can be accessed and reassembled in different ways without reorganizing the tables, it also covers how PeopleSoft uses a 3-tier architecture called PeopleSoft Internet Architecture (PIA) consisting of a web browser, web server, application server and database server to deliver pure internet applications to users. PIA provides advantages over traditional client/server architectures like thin clients, improved performance, and the ability to scale more easily to meet increasing user demands.
Generating XML schemas from a Logical Data Model (EDW 2011)George McGeachie
I gave this 30 minute presentation in April 2011 at Enterprise Data World in Chicago, United States.
I also have a copy of the script (also PowerPoint) I used for the PowerDesigner demonstration.
This document provides an overview of OData, including:
- OData is a standard API for accessing data in a RESTful manner that allows for querying and interoperability.
- OData addresses limitations of REST by standardizing resource naming, paging support, querying, and status codes.
- The document demonstrates OData resource identification, operations, representations, query parameters, and tools/libraries, concluding with a link to a GitHub demo.
Structuring An ABAP Report In An Optimal WayBlackvard
Spaghetti code? Do you want to get rid of it now? Are your ABAP reports not structured well enough? Join Blackvard's CEO Lukas Dietzsch in this complimentary webinar as he demonstrates how to structure SAP ABAP reports in an optimal way, using several new development tools now available in Eclipse.
The document outlines a PHP training course covering introductory and advanced PHP topics over 1-2 months. It includes introductions to PHP basics like variables, data types, operators, and control structures. It also covers arrays, functions, object-oriented programming, databases, frameworks like CodeIgniter and CakePHP, and content management systems like Joomla. The training is offered by Resistive Technosource Pvt. Ltd. and includes both conceptual and hands-on components.
The document provides a summary of Lessly Raja's professional experience as a Senior Software Engineer with over 6 years of experience in .NET development. It includes details of his education, technical skills in languages like C#, ASP.NET, and frameworks like .NET and SQL Server. It also summarizes some of his past projects including work on a lawson project at Steria involving LightSwitch, a loan origination system called Catapult at ISGN Technologies, and other projects involving mortgage applications and funeral home accounts.
Migrating from CA AllFusionTM ERwin® Data Modeler to Embarcadero ER/StudioMichael Findling
This is a step-by-step guide to migrating from CA AllFusionTM ERwin Data Modeler to Embarcadero ER/Studio - the next-generation data modeling solutions. Embarcadero Technologies is the leading provider of database tools and developer software.
1. Aburar Yaseen has over 11 years of experience in the IT industry as a software engineer and data analyst.
2. He has extensive experience developing reports and dashboards using tools like Tableau, Crystal Reports, and SQL.
3. Some of the projects he has worked on include data analytics for companies in various industries like manufacturing, logistics, banking, insurance, consumer goods, and sports/entertainment.
Raymond Cochrane has over 20 years of experience developing and administering SQL Server databases and business intelligence systems. He has extensive experience with SQL Server, SSIS, SSAS, and SSRS. He has worked on projects involving data warehousing, ETL, reporting, and analytics for clients in various industries including banking, insurance, healthcare, and retail. His technical skills include SQL, SSIS, SSAS, SSRS, and working with dimensional data models.
pentagon space is training institute in Bangalore and it is located at Vijaynagar, near metro station hosahalli. Our python full stack developer course includes syllabus HTML5 , CSS3 Bootstrap, JavaScript , Postgre SQL, Vue Js and Django.
Piyush Mittal has over 5 years of experience as a software developer. He received his MS in Computer Science from Northeastern University and his Bachelor's in Information Technology from UPTU, India. Currently, he works as a Software Developer for Staples.com where he has designed and implemented features like automatic re-stocking and email notifications. Previously, he had internships at Amazon developing web applications for resellers and at Accenture testing ETL processes. He is proficient in languages like Java, Ruby, and frameworks like Spring and Hibernate.
People soft application-designer-practice-8.43cesarvii
This document discusses PeopleSoft Application Designer and the steps to create a PeopleSoft application. It describes Application Designer as a tool for developing web-enabled PeopleSoft applications. It then outlines the 9 simple steps to create an application, which include creating field, record, page, component, and menu definitions and assigning security. The document also provides details on creating components and field definitions, including field types, formats, and properties.
This document describes four primary models for developing Java applications on the AS/400: HTTP servlets, transaction serving, Domino agents, and distributed objects. It compares these models to the traditional interactive job structure and discusses how each handles system services like transactions and security. The models provide different levels of services, with distributed objects eventually providing the most complete environment similar to traditional models.
The document provides an overview of SQL (Structured Query Language) including its purpose, benefits, and key components. It describes the SQL environment and data types, as well as the main SQL statements used for database definition (DDL), data manipulation (DML), and control (DCL). Examples are given for common statements like CREATE TABLE, SELECT, INSERT, UPDATE, DELETE, and how to define views, integrity controls, indexes and more.
The document discusses reporting tools for Oracle Applications 11i, focusing on Oracle Reports 6i. It describes the key considerations in selecting a reporting tool and provides an overview of Oracle Reports 6i. Specifically, it covers the differences between character and bitmap reports in Oracle Reports 6i, and how to build reports for Oracle Applications 11i using Oracle Reports 6i. It also provides details on building reports, including using the data model, layout model, parameters, triggers, and the built-in SRW package.
This document provides an overview of Informatica Designer, which is used to create mappings and transformations to move and transform data between sources and targets. It describes the key components and tools in Designer including the navigator, workspace, status bar, and output windows. It also covers how to work with sources, targets, transformations, mappings, and mapplets. Additionally, it discusses tasks like debugging mappings, viewing dependencies, and using the designer tools.
OData - An Introduction and Examples
Agenda:
Why We Need OData
A Basic Introduction to OData
Structure of an OData Service
OData Operations
OData Query Language
This document provides a summary of Nagendra Kumar Busetti's work experience and qualifications. He has over 7 years of experience as a data modeler working with tools like Erwin and databases like Oracle, SQL Server, and DB2. Currently he works for TCS as a data modeler on projects for clients like Toys "R" Us, where he is responsible for logical and physical database design, maintaining metadata, and providing support to applications. Previously he worked for iGATE as a senior system engineer, where he performed similar data modeling duties for clients such as MetLife Insurance. He has a B.Tech degree from 2011 and is proficient with programming languages like SQL and T-SQL.
Sneak peak ca e rwin data modeler r8 preview09222010ERwin Modeling
This document provides an overview of new features and enhancements in the upcoming CA ERwin Data Modeler r8 release. Key highlights include a state-of-the-art visualization with dynamic and customizable user interface, productivity-enhancing workflows, support for additional databases, and improvements to modeling tools, editors, and licensing. The goal is to provide the leading data modeling solution while balancing usability, productivity, and database currency.
This document discusses different data models used in database management systems including record-based, relational, network, hierarchical, and entity-relationship models. It provides details on each model such as how data is organized. A record-based model uses fixed-length records and fields. The relational model organizes data into tables with rows and columns. The network model links entities through multiple paths in a graph structure. The hierarchical model arranges data in a tree structure. Finally, the entity-relationship model views the real world as entities and relationships between entities.
This document discusses using high-level data modeling to facilitate communication between business and IT stakeholders. It provides examples of high-level data models and discusses best practices for building high-level models, including getting input from all relevant parties, choosing an intuitive notation, and using the model to achieve consensus on key business concepts and definitions. The document also describes how modeling tools from CA like ERwin can help manage technical data sources from multiple systems and databases, and share information with various audiences.
Generating XML schemas from a Logical Data Model (EDW 2011)George McGeachie
I gave this 30 minute presentation in April 2011 at Enterprise Data World in Chicago, United States.
I also have a copy of the script (also PowerPoint) I used for the PowerDesigner demonstration.
This document provides an overview of OData, including:
- OData is a standard API for accessing data in a RESTful manner that allows for querying and interoperability.
- OData addresses limitations of REST by standardizing resource naming, paging support, querying, and status codes.
- The document demonstrates OData resource identification, operations, representations, query parameters, and tools/libraries, concluding with a link to a GitHub demo.
Structuring An ABAP Report In An Optimal WayBlackvard
Spaghetti code? Do you want to get rid of it now? Are your ABAP reports not structured well enough? Join Blackvard's CEO Lukas Dietzsch in this complimentary webinar as he demonstrates how to structure SAP ABAP reports in an optimal way, using several new development tools now available in Eclipse.
The document outlines a PHP training course covering introductory and advanced PHP topics over 1-2 months. It includes introductions to PHP basics like variables, data types, operators, and control structures. It also covers arrays, functions, object-oriented programming, databases, frameworks like CodeIgniter and CakePHP, and content management systems like Joomla. The training is offered by Resistive Technosource Pvt. Ltd. and includes both conceptual and hands-on components.
The document provides a summary of Lessly Raja's professional experience as a Senior Software Engineer with over 6 years of experience in .NET development. It includes details of his education, technical skills in languages like C#, ASP.NET, and frameworks like .NET and SQL Server. It also summarizes some of his past projects including work on a lawson project at Steria involving LightSwitch, a loan origination system called Catapult at ISGN Technologies, and other projects involving mortgage applications and funeral home accounts.
Migrating from CA AllFusionTM ERwin® Data Modeler to Embarcadero ER/StudioMichael Findling
This is a step-by-step guide to migrating from CA AllFusionTM ERwin Data Modeler to Embarcadero ER/Studio - the next-generation data modeling solutions. Embarcadero Technologies is the leading provider of database tools and developer software.
1. Aburar Yaseen has over 11 years of experience in the IT industry as a software engineer and data analyst.
2. He has extensive experience developing reports and dashboards using tools like Tableau, Crystal Reports, and SQL.
3. Some of the projects he has worked on include data analytics for companies in various industries like manufacturing, logistics, banking, insurance, consumer goods, and sports/entertainment.
Raymond Cochrane has over 20 years of experience developing and administering SQL Server databases and business intelligence systems. He has extensive experience with SQL Server, SSIS, SSAS, and SSRS. He has worked on projects involving data warehousing, ETL, reporting, and analytics for clients in various industries including banking, insurance, healthcare, and retail. His technical skills include SQL, SSIS, SSAS, SSRS, and working with dimensional data models.
pentagon space is training institute in Bangalore and it is located at Vijaynagar, near metro station hosahalli. Our python full stack developer course includes syllabus HTML5 , CSS3 Bootstrap, JavaScript , Postgre SQL, Vue Js and Django.
Piyush Mittal has over 5 years of experience as a software developer. He received his MS in Computer Science from Northeastern University and his Bachelor's in Information Technology from UPTU, India. Currently, he works as a Software Developer for Staples.com where he has designed and implemented features like automatic re-stocking and email notifications. Previously, he had internships at Amazon developing web applications for resellers and at Accenture testing ETL processes. He is proficient in languages like Java, Ruby, and frameworks like Spring and Hibernate.
People soft application-designer-practice-8.43cesarvii
This document discusses PeopleSoft Application Designer and the steps to create a PeopleSoft application. It describes Application Designer as a tool for developing web-enabled PeopleSoft applications. It then outlines the 9 simple steps to create an application, which include creating field, record, page, component, and menu definitions and assigning security. The document also provides details on creating components and field definitions, including field types, formats, and properties.
This document describes four primary models for developing Java applications on the AS/400: HTTP servlets, transaction serving, Domino agents, and distributed objects. It compares these models to the traditional interactive job structure and discusses how each handles system services like transactions and security. The models provide different levels of services, with distributed objects eventually providing the most complete environment similar to traditional models.
The document provides an overview of SQL (Structured Query Language) including its purpose, benefits, and key components. It describes the SQL environment and data types, as well as the main SQL statements used for database definition (DDL), data manipulation (DML), and control (DCL). Examples are given for common statements like CREATE TABLE, SELECT, INSERT, UPDATE, DELETE, and how to define views, integrity controls, indexes and more.
The document discusses reporting tools for Oracle Applications 11i, focusing on Oracle Reports 6i. It describes the key considerations in selecting a reporting tool and provides an overview of Oracle Reports 6i. Specifically, it covers the differences between character and bitmap reports in Oracle Reports 6i, and how to build reports for Oracle Applications 11i using Oracle Reports 6i. It also provides details on building reports, including using the data model, layout model, parameters, triggers, and the built-in SRW package.
This document provides an overview of Informatica Designer, which is used to create mappings and transformations to move and transform data between sources and targets. It describes the key components and tools in Designer including the navigator, workspace, status bar, and output windows. It also covers how to work with sources, targets, transformations, mappings, and mapplets. Additionally, it discusses tasks like debugging mappings, viewing dependencies, and using the designer tools.
OData - An Introduction and Examples
Agenda:
Why We Need OData
A Basic Introduction to OData
Structure of an OData Service
OData Operations
OData Query Language
This document provides a summary of Nagendra Kumar Busetti's work experience and qualifications. He has over 7 years of experience as a data modeler working with tools like Erwin and databases like Oracle, SQL Server, and DB2. Currently he works for TCS as a data modeler on projects for clients like Toys "R" Us, where he is responsible for logical and physical database design, maintaining metadata, and providing support to applications. Previously he worked for iGATE as a senior system engineer, where he performed similar data modeling duties for clients such as MetLife Insurance. He has a B.Tech degree from 2011 and is proficient with programming languages like SQL and T-SQL.
Sneak peak ca e rwin data modeler r8 preview09222010ERwin Modeling
This document provides an overview of new features and enhancements in the upcoming CA ERwin Data Modeler r8 release. Key highlights include a state-of-the-art visualization with dynamic and customizable user interface, productivity-enhancing workflows, support for additional databases, and improvements to modeling tools, editors, and licensing. The goal is to provide the leading data modeling solution while balancing usability, productivity, and database currency.
This document discusses different data models used in database management systems including record-based, relational, network, hierarchical, and entity-relationship models. It provides details on each model such as how data is organized. A record-based model uses fixed-length records and fields. The relational model organizes data into tables with rows and columns. The network model links entities through multiple paths in a graph structure. The hierarchical model arranges data in a tree structure. Finally, the entity-relationship model views the real world as entities and relationships between entities.
This document discusses using high-level data modeling to facilitate communication between business and IT stakeholders. It provides examples of high-level data models and discusses best practices for building high-level models, including getting input from all relevant parties, choosing an intuitive notation, and using the model to achieve consensus on key business concepts and definitions. The document also describes how modeling tools from CA like ERwin can help manage technical data sources from multiple systems and databases, and share information with various audiences.
This certificate of achievement certifies that Ernesto Arce completed 3 days of training totaling 24 hours in ERwin Data Modeling. He has met all requirements and completed all exercises to receive this certification, which was issued on October 26, 2016.
Integrating data process a roundtrip modeling using e rwin data modeler_erwin...ERwin Modeling
This document discusses integrating data and process modeling using ERwin Data Modeler and ERwin Process Modeler. It provides an overview of the modeling tools and a 4 step process for mapping process models to data models. The steps include: 1) Mapping entities to process arrows, 2) Mapping attributes to entities, 3) Identifying process actions on entities, and 4) Identifying process actions on attributes. Rules for allowable actions on entities and attributes based on their usage in the process model are also defined.
This document provides a comprehensive analysis comparing the data modeling capabilities of Sybase PowerDesigner 16.0 InformationArchitect and CA ERwin Data Modeler r8.1 Standard Edition. It examines how each tool supports key data modeling activities like creating different types of data models (conceptual, logical, physical), impact analysis across model levels, and model integration. The analysis finds that while both tools allow creating different model types and linking models, PowerDesigner provides more robust, integrated support through dedicated model types and built-in impact/lineage analysis. It concludes PowerDesigner better enables managing relationships across complex data modeling projects.
The document discusses how to create enterprise data standards using CA ERwin Data Modeling. It describes leveraging naming standards, domains, user defined properties, and data type standards to promote consistency and reuse. The presentation also demonstrates sharing standards using CA ERwin Model Manager and reporting standards to stakeholders using various reporting options like Crystal Reports. Live demo examples are provided of implementing standards in CA ERwin Data Modeling.
Using ca e rwin modeling to asure data 09162010ERwin Modeling
Data profiling analyzes data content to infer metadata and increase the accuracy of data assets and models. It can help with data quality assessments, master data management, and reducing risks in data warehousing projects. The presentation provided examples of how profiling was used to uncover issues, validate models and requirements, standardize values, and reduce development times for various organizations.
CA ERwin Modeling provides data modeling solutions to help reduce costs and increase ROI. Their next release, r8, will include improved visualization, customization, and productivity features. r8 is focused on balancing usability improvements and database support to increase user satisfaction and ROI. The data modeling market is seeing new players and a diversification in how solutions are used, with CA ERwin striving to scale their products to meet new requirements.
Data models can facilitate communication between designers, programmers, and users. A well-developed data model can improve understanding of an organization. Data models are a communication tool that represent different types of relationships in a database. Common data models include hierarchical, network, relational, entity-relationship, and object-oriented models. Each model has advantages like conceptual simplicity and flexibility as well as disadvantages like complexity and implementation limitations.
Paper published as speaker CA World 2010 at Las Vegas, USA.
Speaker & Author: Rasananda Behera Insurance Industry Expert on Enterprise Architecture [Business, Data & Applications] Management.
Mastering your data with ca e rwin dm 09082010ERwin Modeling
This document discusses using data modeling to build the foundations for strong data quality. It outlines a process with six steps: [1] defining metadata standards, [2] encouraging collaboration, [3] organizing models and data, [4] enforcing standards, [5] changing organizational culture, and [6] creating a "to be" target state. The key points are that data quality requires treating data as a valuable asset, establishing good metadata and modeling habits, and ongoing cultural changes rather than a single solution.
This document discusses different types of data models, including hierarchical, network, relational, and object-oriented models. It focuses on explaining the relational model. The relational model organizes data into tables with rows and columns and handles relationships using keys. It allows for simple and symmetric data retrieval and integrity through mechanisms like normalization. The relational model is well-suited for the database assignment scenario because it supports linking data across multiple tables using primary and foreign keys, and provides query capabilities through SQL.
The document provides an introduction to database management systems (DBMS) and database models. It defines key terms like data, database, DBMS, file system vs DBMS. It describes the evolution of DBMS from 1960 onwards and different database models like hierarchical, network and relational models. It also discusses the roles of different people who work with databases like database designers, administrators, application programmers and end users.
This document discusses different types of data models, including object based models like entity relationship and object oriented models, physical models that describe how data is stored, and record based logical models. It specifically mentions hierarchical, network, and relational models as examples of record based logical data models. The purpose of data models is to represent and make data understandable by specifying rules for database construction, allowed data operations, and integrity.
The document discusses data modeling, which involves creating a conceptual model of the data required for an information system. There are three types of data models - conceptual, logical, and physical. A conceptual data model describes what the system contains, a logical model describes how the system will be implemented regardless of the database, and a physical model describes the implementation using a specific database. Common elements of a data model include entities, attributes, and relationships. Data modeling is used to standardize and communicate an organization's data requirements and establish business rules.
The document summarizes BEA-IT's efforts to develop an integrated customer data integration (CDI) solution. Their first generation solution used ETL tools and a matching engine but did not meet objectives due to issues like lack of data stewardship capabilities and business buy-in. For their second generation solution, BEA-IT plans to take a more pragmatic approach starting with a registry-style CDI focused on point solutions, leveraging SOA, and expanding scope gradually based on early wins. The goals are to load all BEA customer data into a master repository and deliver a search portal while establishing governance processes to maintain data quality.
Microsoft Dynamics CRM and xRM were presented as platforms for managing relationships across various entities through a flexible and customizable application framework. xRM allows building industry-specific or line-of-business applications more quickly and at a lower cost than custom development by providing reusable components, a consistent user experience, and a shared environment and resources. Examples of government and commercial organizations successfully using xRM for tasks, grants, and other relationship management were described.
Case Study: Learn How Expeditors Uses APM as Both a Technology and Process T...CA Technologies
Expeditors implemented CA APM as both a technology and process transformation initiative. They took a three-tiered approach focusing on technology, people, and process. On the technology side, they deployed CA APM across their pre-production and production environments. For people, they defined roles, provided training, and partnered with experts. For process, they incorporated APM into their SDLC and created a maintenance discipline. The implementation helped Expeditors gain visibility, improve performance, and empower teams across the organization.
ARC's Bob Mick Asset Performance Management Presentation @ ARC Industry Forum...ARC Advisory Group
ARC's Bob Mick Asset Performance Management Presentation @ ARC Industry Forum 2010 in Orlando, FL.
Aligning IT Strategies with Asset Performance Management
How do I Start Improving AIM?
You Can Start Small – Build Artifacts for the Long Term
What asset performance do I want to impact?
How do I determine that performance?
What roles influence that performance?
What processes are involved?
What information needed?
Share Information
may be used in is What info is shared?
• Where does it come from?
Local Processes
as well as Cross-
Functional Processes
• Who owns it (create, transform, change …)?
What is required to manage quality?
How can technology help?
Performance Specific Metrics, Roles and Processes
Are a Great Place to Start
The document discusses establishing a strategy for enterprise data quality. It recommends identifying the current data infrastructure, setting up quality control initiatives using tools, and developing plans to improve data quality. Specifically, it suggests identifying roles and responsibilities, choosing a data quality architecture and tools, determining standards, and conducting an initial data quality audit to identify issues and get stakeholder buy-in. The overall goal is to establish a framework and roadmap to improve enterprise-wide data quality.
Software development lifecycle (SDLC) has traditionally been used for in-house systems
or custom-developed software. Capability Maturity Model Integration (CMMI) has been
used specifically in software engineering to demonstrate the maturity of an organization's
software development process. Implementations of packaged enterprise software bring a
unique set of challenges that need to be viewed from the different perspectives of SDLC
and CMMI. This presentation demonstrates how ERP managers can articulate their
development and support process within the context of SDLC and CMMI.
Model Drivers is a data architecture designer. Model DR 'industrialises' business systems providing a congruent data architecture that aggregates and integrates myriad data sources for modernised queries and reporting
The document discusses and compares various productivity tools for product management. It focuses on requirements management tools that can be acquired independently by PMs to improve their own productivity. The document analyzes options like Accompa, Accept, IBM Focal Point, and Ryma FeaturePlan based on factors such as cost, platform, security, and integration capabilities. It provides recommendations on tool selection based on a company's PM framework and capabilities.
Research Report Future CRM Technology 2010 to 2013Ram Srivastava
Research Report, Future, CRM technology, 2010 to 2013,
Marketing, Sales, Customer Service, Field Service Management, Social CRM
Information Infrastructure Management, Analytics – BI, E-Commerce
Web-oriented architecture of CRM systems, Mobile CRM, iTV
SIAM Study - Comparing the Introduction of New IT Services via Simple and Com...Ken Blunt
A Study to Compare the Introduction of typical New IT Services within a Single Tower and Multi-Tower SIAM Model using a mature set of ‘Plan-Build-Run’ project tasks
Conlcusion
The conclusions of this study for the introduction of New IT Services via Simple and Complex SIAM Models are:
Single Tower model is more efficient than a Muti-Tower Model
Due to security issues, more Design project tasks are required for New hosted cloud services than On-premise hosted services
The document discusses application portfolio management (APM) and rationalization. It provides an overview of APM, how it can help manage applications from a strategic perspective, and structure rationalization decision making. It then discusses CA Technologies' perspective on APM, including registering applications, rationalizing based on business/technical fit, evaluating applications based on criteria like cost and risk, and identifying portfolio transformation requirements. The document also includes sections on APM drivers/triggers, features of CA's APM product, how APM relates to their business service intelligence (BSI) product, and a roadmap for the APM product.
The document describes an expanded version of the MDM Framework (MDMF) product called MDMF DPGI. MDMF DPGI includes pyramid structures for data management, business processes, information governance, and infrastructure architecture. Each pyramid contains multiple levels that define domains, concepts, life cycles, processes, models, and the physical implementation. Standard templates collect metadata from each pyramid and store it in an enterprise metadata repository to provide a foundation for business decisions.
1. The document summarizes a presentation given by Jos Leber of T-Mobile Netherlands on their data quality efforts.
2. It describes the steps they took during a project called Phoenix to clean customer data and develop tools to measure data quality.
3. It then outlines the additional steps they took after the project, including developing a data quality monitoring process and a data management maturity model to guide their continued work.
The document describes MDMF DPGI v3.0, an HTML-based product that provides standardized frameworks (pyramids) for data management, business processes, information governance, and infrastructure architecture. Each pyramid contains multiple levels that define aspects like domains, concepts, life cycles, processes, models, and physical implementations. Templates are used to collect and store metadata produced through each pyramid's lifecycles in an enterprise metadata repository. Implementing the pyramids individually or together provides a common way to organize an organization's key information.
The document describes MDMF DPGI v3.0, an HTML-based product that provides standardized frameworks (pyramids) for data management, business processes, information governance, and infrastructure architecture. Each pyramid contains multiple levels that define aspects like domains, concepts, processes, models, and the physical implementation. Templates are used to collect and store metadata produced through each pyramid's lifecycles in an enterprise metadata repository. Implementing the pyramids individually or together provides a standardized way to manage an organization's key information.
S299137 Enterprise Saa S Behind The Operational Scenes Of Oracle Crm On DemandKate Haughton
The document provides an overview of Oracle's CRM On Demand enterprise SaaS solution and disaster recovery services. It discusses the current multi-tenant SaaS solution, roadmap including social CRM and industry specific CRM solutions. It also outlines the disaster recovery options available including standard backup services with daily backups and offsite storage, as well as a single tenant disaster recovery option with a secondary site 700 miles from the primary site and a recovery time objective of 24 hours.
This document provides an overview of requirements management capabilities in Aras PLM. It discusses how requirements management ties into product lifecycle management. The agenda includes a product demonstration of the new grid and HTML editor, as well as details on the data model including new item types and relationships. Requirements can be managed across disciplines and traced throughout the lifecycle. Customization options like methods and reports are also covered.
Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Meanwhile, 94% of enterprises are using some form of XaaS--software, platform, and infrastructure as a service.
This document discusses key management systems and cloud migration. It begins with an overview of encryption at rest using DoDAF and various AWS services like S3, EBS, RDS, and Redshift. It then provides details on the AWS Key Management Service (KMS), how it allows users to create and manage encryption keys to protect data on supported AWS services. KMS ensures keys are securely stored and accessible only by authorized users or services. The document also discusses how database encryption can be implemented using KMS and compares KMS to on-premises key management and CloudHSM. It concludes with topics on identity and access management policies, standards for archiving to Glacier, and server-side encryption options on S3
The document is an invitation for the speaker to present at Cloud Expo, Big Data at Cloud Expo, DevOps at Cloud Expo, or @ThingsExpo from June 6-8, 2017. It outlines the presentation guidelines which include checking in at least 1 hour before their session, preparing a presentation and slides on relevant topics by May 19th, and using the provided audiovisual equipment. The speaker agrees to let SYS-CON copy and distribute their materials and recordings. Cancellation requires 3 weeks notice or May 16th. The speaker and SYS-CON sign agreeing to the details.
This document provides the functional requirement details for a Financial Data Warehouse (FDW) project. It includes sections on document control, an overview of the purpose and intended audience. There are also sections covering assumptions, dependencies, detailed requirements, additional specifications, open questions, and appendices. The detailed requirements section links to documents covering areas like the source to target mappings, logical data models, data dictionaries, validation, error handling, security, and more. The document aims to capture all necessary requirements to design and implement the FDW.
This document provides the functional requirement details for a Financial Data Warehouse (FDW) project. It includes sections on document control, an overview of the purpose and intended audience. There are also sections covering assumptions, dependencies, detailed requirements, additional specifications, open questions, and appendices. The detailed requirements section links to documents covering areas like the source to target mappings, logical data models, data dictionaries, validation, error handling, security, and more. The document aims to capture all necessary requirements to design and implement the FDW.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The requirements definition section further outlines goals, usability requirements, system security, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introducing the project, stating its purpose and objectives, defining requirements, and considering constraints. The document was created by Rasananda Behera on February 11, 2016 as an initial version to standardize how requirement specifications are documented for financial data warehouse projects at CUNA Mutual Group.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introducing the project, stating its purpose and objectives, defining requirements, and considering constraints. The document was created by Rasananda Behera on February 11, 2016 as a version 1.0 template for financial data warehouse specification documents.
This document provides a template for specifying requirements for a financial data warehouse project. The template includes sections for introduction, purpose, project summary, requirements definition, considerations, and a document change log. The project summary section provides an executive overview with objectives, scope, references, and outstanding issues. The requirements definition section outlines goals, usability requirements, security requirements, business questions, data requirements, and design constraints. The purpose is to help define and document the project scope and requirements.
1. case study:
CA ERwin Data Modeler and
CA ERwin Model Manager across insurance
industries
Session Code RM006SN
Focus Area: Data Management
-Rasananda Behera, DTM
2. case study: for CA ERwin Data Modeler (CA ERwin DM) and
CA ERwin Model Manager (CA ERwin MM)
Why CA ERwin® Data Modeler (CA ERwin DM) ?
– Why not tools like Designer2K or Designer 6i or Designer 9i from Oracle CASE
Tools?
– Why not tools like Power Designer?
– Why not free software like DB Visualizer?
– Or any other Tools..
3. case study: for CA ERwin DM and CA ERwin MM
Why Strategy?
– The key elements of business strategy
1. Vision
2. Strategic Goals
3. Objectives
4. Methods
5. Tactics
– How it affects to Data Model and Model Manager?
– Impacts and Efficacy
Mission
Definition
Achievements
Competitive Advantage
– Rivals can easily copy your operational effectiveness, but cannot
copy your strategic positioning.
4. case study: for CA ERwin DM and CA ERwin MM
Other Key Elements:
– Opportunities and Threats
– Implementation
– Capabilities
– Strengths and weakness
– Policies
– Key Decisions
Corporate strategy
Competitive Strategy
5. case study: for CA ERwin DM and CA ERwin MM
AIDA Approach & Key (Dynamic) Strategy
– The Who - Who should an organization target as customers for
data model?
– The What - What products or services should be offered?
– The How - How can this be done in an efficient manner?
AIDA Approach
1. Action
2. Interest
3. Desire
4. Action
6. case study: for CA ERwin DM and CA ERwin MM
Data Models:
1. Very High Level Data Model
2. High Level Data Model
3. Logical Data Model
7. case study: for CA ERwin DM and CA ERwin MM
Many names for High Level Data Model1
1. In a recent survey of data model professionals, the most
popular names for high level:
Conceptual Data Model - 59%
Subject Area Model - 12%
Business Data Model - 10%
Enterprise Data Model - 6%
Other - 13%
1DM review Dec 1st 2008 by Hoberman, Steve
8. 0%
10%
20%
30%
40%
50%
60%
%
HLDM Name
High Level Data Models [HLDM Survey of data
Professionals]
Conceptual[59%]
Subject Area[12%]
Business Data
Model[10%]
Enterprise Data
Model[6%]
Other[13%]
case study: for CA ERwin DM and CA ERwin MM
9. case study: for CA ERwin DM and CA ERwin MM
How Logical Data Model different from HDM and VHDM ?
[With refer to Data Modeling to the Business By Steve Hoberman, Donna Burbank, & Chris Bradley }
VHDM HDM LDM
Define the scope and audience,
context for information
Key business concepts and their
definitions
Represents core business rules data relationships at a
detail level
Relationship optional.
Represent hierarchy
Many-to-many relationship is
okay
Many-to-many relationship resolved by associate entity
Cardinality not shown Cardinality shown Cardinality shown
No attributes shown Attributes are optional and
composite
Attributes are required and are atomic. Primary Keys and
FKs are defined [Codd’s Rules]
Not normalized Not normalized Fully normalized
Subject links to 1:M HDMs Concepts are super type; though
subtypes shown for clarity
Super types broken into many subtypes. Entity names
may be more abstract.
One Pager Should be a ‘one pager’ May be larger than one page
Business Driven Cross functional & senior
management involved.
Multiple smaller groups of specialists and IT folks
involved in LDM process
Information Notation Understood by a business user Formal notation required.
< 20 objects < 100 objects > 100 objects
10. case study: for CA ERwin DM and CA ERwin MM
Traditional versus Hoshin Planning
– Hierarchical [Mainframe IMS dB etc]
– Network database
– Character Based Applications
– Object oriented
– Relational dB
– XML/J2EE/.NET/Web App etc.
11. case study: for CA ERwin DM and CA ERwin MM
SWOT analysis on data model techniques
[Refer Appendix A]
12. case study: for CA ERwin DM and CA ERwin MM
SWOT analysis on data model techniques
– Identifying and assessing core competencies
– Understanding your financial capacity for undertaking a new strategy
– Evaluating management and organizational culture in terms of change-
readiness
– A nine-step method for evaluating strengths and weaknesses
– Looking Inside for Strengths and Weaknesses [Refer Appendix B]
– Actuary
– UPM (Underwriting Reserve Control & Pricing Product Management)
– Claim
– Service
– Policy
13. case study: for ERwin DM and CA ERwin MM
Quality Function Deployment Matrices
– Decreasing Costs
– Increasing Revenues
– Cycle Time reduction
– Rapid Product Enterprise Data Model
– Competitive Satisfaction performance across Sales, Claims &
Service.
– Normalized Raw Weight & Best Practices
– Goal Improvement Ratio on EDW
– Concurrent Engineering A Paradigm Shift
– Develop Collaboration & Teamwork across Sales/Service/Claim
14. case study: for CA ERwin DM and CA ERwin MM
Scenario planning and tools for measuring success
– Enterprise Data Model based on 3 major categories for any Insurance business
1. Policy
2. Claim
3. Service Venn Diagram in Enterprise Data Model
Claim
Service
Policy
Claim System
Oracle & IMS
Service
IMS & SQL
Server
Policy
system
DB2
15. case study: for CA ERwin DM and CA ERwin MM
Complex CA ERwin Model Manager in Insurance Industries:
16. case study: for CA ERwin DM and CA ERwin MM
Tool Integration with CA ERwin Data Modeler and CA ERwin Model
Manager
– Offered Features and platforms
– Management Challenges
– Heterogeneous Database support
– Oracle
– DB2
– SQL Server 2005/2008 etc.
– Reports
– Crystal Report
– Adobe Reader
– HTML
– XML etc
17. case study: for CA ERwin DM and CA ERwin MM
Logical Data Model to Physical with Subtype
EXT_CLAIMREFERRAL
ID
PublicID
Ext_SIUReferral
ID (FK)
18. case study: for CA ERwin DM and CA ERwin MM
Why Reverse Engineer [Practical approach]
19. case study: for CA ERwin DM and CA ERwin MM
DM Reverse Engineer template
1. Physical
2. Logical/physical
20. case study: for CA ERwin DM and CA ERwin MM
Subtypes of abContact
– abPerson
– abCompany(B2B)
1. abInsurer
2. abInsuranceAgency
– abPlace
21. case study: for CA ERwin DM and CA ERwin MM
CA ERwin Data Model Reverse Engineer Contd..
22. case study: for CA ERwin DM and CA ERwin MM
Generate Reports from ERwin Data Modeler
23. case study: for CA ERwin DM and CA ERwin MM
Why Forward engineer?
24. case study: for CA ERwin DM and CA ERwin MM
Complete Compare Vs. Snapshots
25. case study: for CA ERwin DM and CA ERwin MM
Why CA ERwin® Model Manager ?
Why not Perforce p4or Visual Source Safe [VSS] as SCM tool for managing
data models?
Why not any other tools in Market like Designer Oracle CASE Tool, Power
Designer from SYBASE etc.?
Pros & Cons
– Scalable
– Multi-User Environment
– Innovative
– Easy to Use
– Controlled, Quality, and productivity
– Manage Risks
– Improve Service
– Reduce Time and Cost effective
– Object Model Management
26. case study: for CA ERwin DM and CA ERwin MM
Let’s do a Practical Hands On!!
Or
DEMO
27. case study: for CA ERwin DM and CA ERwin MM
CA ERwin Model Manager Connection [Practical approach]
28. case study: for CA ERwin DM and CA ERwin MM
Model Manager Administrator Security
31. case study: for CA ERwin DM and CA ERwin MM
[Appendix A II – sample data model]
has relationship (0:1:M) /
abContact-address-config
has rel /
Is defined as
belongs to /
circle/loop
Contact for a contact /
loop
Provides /
stores
Covered by /
has policy
Is Scheduled for /
Contains Schedule Profile
ATLAS covers /
Is defined as
Scheduled Places as /
Is Stored as
may have multiple vehicle types /
is an array of ABERSProvider
Accepts /
Stores method/criterias(array)
Insured by /
has atleast an Insurer
Insured by /
InsuranceAgencyRel
ABGEICOSpecialPmts has an array /
is defined as an array
has an array to Foreign Key to Provider Payment Info /
is defined as an array
has an array defined as /
is an array
has an array /
is an array
has an array /
is an array
has an array(min 2 madatory) /
is defined as an array entity
ERS Provider has many /
is defined as an array (Belongs to ERS)shall defined as /
shall have atleast one
Insured By /
Is defined as Coverage
Has an array of /
Is defined as
has an array /
Is defined as
has an array /
Is defined as an array(0:1:M)
serves for /
is enrolled /rates
has atleast one /
is defined as
has an array /
Is defines as an array
Tracks the IRS file status /
(0:1:M)
abAddress
ID
AddressLine1
AddressLine2
AddressLine3
AddressType
City
CreateTime
CreateUserID
ext_AddressValidation
ext_CountryCode
ext_POBoxNumber
ext_UnitNumber
ext_UnitType
ext_LocationType
PostalCode
State
UpdateTime
UpdateUserID
ValidUntil
ext_Status
ext_StatusDate
ext_TimeZone
ext_MetroCode
PublicID
abContact
ID
W9Received
CellPhone
CreateTime
CreateUserID
Ex_AdditionalName
Ex_DoNotPay
ext_FCC
ext_Incorporated
ext_TaxIDType
ext_TaxName
ext_WorkCompIndicator
ext_FleetInsuranceIndicator
ext_OnhookCargoLiabilityAmount
ext_ProviderStatus
ext_OnholdReason
EmailAddress1
FaxPhone
FirstName
LastName
MiddleName
Name
HomePhone
PrimaryAddressID (FK)
PrimaryPhone
Prefix
TaxID
UpdateTime
UpdateUserID
WorkPhone
W9ReceivedDate
Suffix
DateOfBirth
OrganizationType
LicenseNumber
LicenseState
TINMatchStatusID (FK)
PublicID
ext_OrganizationType
ext_NotifyInd
abContactAddress
ID
ContactID (FK)
AddressID (FK)
abContactContact
ID
Relationship
SrcABContactID (FK)
PublicID
RelABContactID (FK)
TaxIDType
ID
typecode
name
description
AddressValidationCode
ID
typecode
name
description
State Surcharge
ID
typecode
name
description
UnitType
ID
typecode
name
description
YesNo
ID
typecode
name
description
Ext_OccupationType
ID
abCocntactID (FK)
ext_DescriptionTxt
PublicID
Ext_ProviderServiceRate
ID
ext_ServiceTypeRateCode
ext_ServiceRateAmount
PublicID
Ext_ProviderInsurance
ID
ext_PolicyNumber
ext_PolicyStartDate
ext_PolicyExpireDate
ext_CertificateRecdDate
ext_PolicyAmount
InsuranceAgency
Insurer
PublicID
DoNotPayCode
ID
typecode
name
description
FCCCode
ID
typecode
name
description
NonPrintReasonCode
ID
typecode
name
description
ProviderType
ID
typecode
name
description
OccupationType
ID
typecode
name
description
Ext_DispatchContactType
ID
ext_TypeCode
ext_Description
PublicID
Ext_PolicyCoverage
ID
abContactID (FK)
ext_InsuranceTypeCode
ProviderInsuranceID (FK)
PublicID
Ext_ProviderInsuranceType
ID
ext_InsuranceTypeCode
ext_Description
PublicID
Ext_ERSServiceRateEnrollment
ID1
LOBNetworkID (FK)
ext_ServiceType
ext_ERSRateType
PublicID
Ext_RepairServiceType
ID
ext_RepairServiceType
ext_Description
PublicID
Ext_FacilityServiceType
ID
ext_ServiceTypeCode
ext_Description
PublicID
abtl_contact/Contact Sub Type
Name
Code
Description
Priority
Categories
Internal
Retired
Ext_ServiceType
ID
ext_TypeCode
ext_Description
PublicID
Ext_EquipmentsType
ID
ext_EquipmentType
ext_Description
PublicID
Ext_VehicleType(ccx_vehicleType)
ID
ext_VehicleType
CreateTime
CreateUser
Ext_ProviderPaymentInfo
ID
ext_PreferredPaymentIndicator
ext_AcceptPaymentType
ext_BankRoutingNumber
ext_BankAccountNumber
ext_PrenoteIndicator
ext_OverMileagePaymentType
ext_BankName
abContactID (FK)
ext_AcceptCODType
ext_AcceptCreditCardType
ext_GeicoCreditCardType
PublicID
Ext_CreditCardType
ID
ext_CreditCardType
ext_Description
PublicID
Ext_Franchise
ID
ext_Franchisee Name
ext_FranchiseeType??
Ext_MetroCode
ID
ext_MetroCode
ext_Description
PublicID
Ext_EquipmentType
ID
abContactID (FK)
ext_EquipmentType
ext_EquipmentCount
PublicID
Ext_LocationCovered
ID
abContactID (FK)
ext_LocationCoveredType
ext_LocationCovered
Ext_SchedulablePlace
ext_OfficeLocationCode
ext_NotificationPercentage
ext_VehicleTypesHandled
ext_abContactID
abContactID (FK)
PublicID
Ext_ScheduleProfile
ext_EffDate
ext_TermedDate
ext_SettingType
ext_SettingData
ext_DayOfWeek
abContactID (FK)
State
ID
TypeCode
Description
abContactAddressHist
ID
AddressPublicID
ContactPublicID
RelLoadHistoryID
Deleted
abContactAddressHist
ID
AddressPublicID
ContactPublicID
RelLoadHistoryID
Deleted
Ext_ABProfLicenseType
Code
Description
Name
Ext_ProviderStatus
ID
Code
Description
Name
Ext_ABProfLicenseStatus
ID
Code
Description
Name
abCompany
abContactID (FK)
ext_InactiveEffDate
Ext_ABERSProvider
InsurerRel (FK)
abPerson
abContactID (FK)
abPlace
abContactID (FK)
ContactRel
ID
Code
Name
Desc
ContactBidRel
ID
Code
Name
Desc
Ext_ABERSProviders
abContactID (FK)
ext_LegacyID
ext_DBAName
ext_BusinessStartYearDate
ext_ERSContractType
ext_FranchiseName
ext_PoliceDepartmentName
ext_MotorClubType
ext_TowPoliceDepartmentIndicator
ext_MotorClubIndicator
ext_PriorTIN
ext_ERSZone
ext_HoldEndDate
ext_HoldStartDate
ext_ContractedDate
ext_BackUpWithHoldingIndicator
ext_NoOfEmployees
PrimaryDispatchAddrID
PrimaryREMMITAddrID
PrimaryMailingAddrID
Ext_CoverageLimitType
ID
ext_CoverageLimitType
Name
PublicID
Description
Ext_ZoneRegState
Code
Name
Description
Ext_ERSVehicleInfo
ID
PublicID
ext_ERSVehicleType
ext_ERSVehicleCnt
abContactID (FK)
ext_VehMakeYearDate
ext_VehMakerName
ext_VehTagID
ext_VehModelName
ext_VehRegdState
ext_VehVinNumber
Ext_ABInsurer
abInsurer (FK)
Ext_ABInsuranceAgency
AgencyRel
ID (FK)
Ext_ABGeicoSpecialPmt
ID
ProviderPmtInfoID (FK)
PublicID
Ext_DebitCardPaymentInfo
ID
ProviderPmtInfoID (FK)
ext_DebitCardType
PublicID
Ext_CheckPmtInfo
ID
ProviderPmtInfoID (FK)
ext_PersonalCheckType
PublicID
Ext_CODPmtInfo
ID
PublicID
ProviderPmtInfoID (FK)
ext_AcceptPmtType
Ext_CreditCardPmtInfo
ID
ProviderPmtInfoID (FK)
ext_CreditCardType
PublicID
Ext_BusinessRefInfo
ID
ext_BusinessRefName
ext_BusinessRefFirstName
ext_BusinessRefLastName
ext_BusinessRefMiddleName
abERSProviderID (FK)
abAddressID (FK)
ext_BusinessRefPhone
ext_BusinessRefPrefix
ext_BusinessRefSuffix
PublicID
Ext_StagingAreaInfo
ID
PublicID
ext_StagingAreaCode
abContactID (FK)
Ext_BusinessRelInfo
ID
ext_PoliceDeptName
ext_CityOrCountyName
ext_PoliceDeptPhone
ext_PoliceDeptState
ext_PrecinctName
PublicID
abContactID (FK)
Ext_SchedulablePlace
abContactID (FK)
ext_officeLocationCode
Ext_ERSNoteHistory
ID
ext_NoteText
ext_NoteCategoryType
ext_ConfidentialIndicator
ext_EmailToAddress
ext_NoteGenerateIndicator
abContactID (FK)
PublicID
Ext_LineOfBuisnessType
ID
ext_LineofBuisnessType
Typecode
Name
Description
Ext_NetworkType
ID
Typecode
Name
Description
Ext_LOBNetwork
ID
abContactID (FK)
ext_NetworkGroupType
ext_LineOfBusinessType
ext_ERSRateType
PublicID
Ext_ThresholdInfo
ID
ext_LineItemType
ext_ServiceRate
ERSServiceRateID (FK)
ext_ThresholdQty
ext_ServiceUOMType
ext_RateEffDate
ext_Tier1Rate
ext_Tier2Rate
ext_Tier3Rate
ext_Free
ext_Tier1Limit
ext_Tier2Limit
ext_Tier3Limit
AddressBookUID
ext_RateExpirationDate
Public ID
Ext_ThresholdType
ID
Typecode
Name
Description
Ext_IRSTINMatchFileStatus
ID
ext_RequestFileName
ext_FileRequestDate
ext_RequestTINCount
ext_ReponseFileName
ext_FileResponseDate
ext_ReponseTINCount
ext_TINExceptionCount
ext_ProcessStatusCode
ext_FileRefNumber
PublicID
Ext_TINMatchFileStatus
ID
Ext_RequestFileName
Ext_RequestFileDate
Ext_ResponseFileDate
Ext_RequestTINCount
Ext_ResponseFileName
Ext_ResponseTINCount
Ext_FileRefNumber
Ext_ProcessStatus
PublicID
CPPM - ContactCenter
ATLAS - ContactCenter
ERS Rewrite - ContactCenter
Provider Phase II - ContactCenter
Sub Type Entity - ContactCenter
RETIRED - Entity
IRS TIN Matching - Contact Center
Enterprise data Model across multiple projects on Claims & Policy
Author: Model Manager, Rasa Behera, DTM
Created Date: Jan 10, 2008
Last conversion Date: November 10, 2008
32. case study: for CA ERwin DM and CA ERwin MM
Appendix - B
Strengths
(S)
Weaknes
ses(W)
Opportuni
ties(O)
Threats
(T)
Political effects?
Legislative effects?
Environmental effects?
Competitor intentions - various?
Market demand?
New technologies, services, ideas?
Vital contracts and partners?
Sustaining internal capabilities?
Obstacles faced?
Insurmountable weaknesses?
Loss of key staff?
Sustainable financial backing?
Economy - home, abroad?
Current Trends of IT developments?
SWOT Analysis Template
State what you are assessing here ______________________________________________________
(Many criteria can apply to more than one quadrant. Identify criteria appropriate to your own SWOT situation.)
Advantages of proposition & Capabilities?
Competitive advantages?
Resources, Assets, People?
Experience, knowledge, data?
Marketing - reach, distribution, awareness,
Innovative aspects?
Location and geographical?
Price, value, quality?
Processes, systems, IT, communications?
Management cover, succession?
Advantages of proposition?
Capabilities & Competitive advantages?
Resources, Assets, People with experience,
knowledge, data?
Marketing - reach, distribution, awareness?
Innovative aspects?
Price, value, quality?
Processes, systems, IT, communications?
Management cover, succession, philosophy,
values?