ModelMart

Industry-leading Model Management

Group Modeling Issues

Manually sharing models Hinders individual productivityLimits development coordinationDoes not provide a means to implement

standards

ModelMart Positioning

ModelMart is the first multi-user modeling environment with real-world features that make coordinated large-scale modeling possible.

Key Roles in Enterprise Modeling

The Modeler The Development Manager The Standards Administrator

Just don’t Bug Me

Key Roles and Requirements

The ModelerThe Modeler

NeedsNeeds•Continued productivity•Minimal Obstacles•Integration with existing workflow

ModelMart Provides

Uninterrupted workflow Impact analysis

See affect of proposed changeProceed with update or not

Complete integration with ERwin and BPwin

ModelMart is Seamlessly IntegratedUsing a ModelMart Server...Using a ModelMart Server...

...Is as easy as working locally on your PC...Is as easy as working locally on your PC

The Change Manager……Before updating the shared modelsBefore updating the shared models

View the Impact of ChangesView the Impact of Changes

The Change Manager

Movie

Toggle Off unwanted updates !Toggle Off unwanted updates !

The Model Integration Hub

The ManagerThe Manager needs services needs services for automated group for automated group interactioninteraction•Security•Project Organization•Team Collaboration•Versioning

Key Roles and Requirements

My My hands hands

are full!are full!

Comprehensive Security

Integrated with network and database security Access Control by:

User Profile Group Profile Library Model Sub-model

Project Organization

Library Management Sub-Modeling used when:

Security requires access restricted to only part of a model

Model grow so large as to be unwieldyA single model crosses project boundaries

(the enterprise model)

Automated Collaboration

Concurrent model access Optional model locking Re-integration of off-line changes Model merging Cross-model reporting

Intelligent Conflict Resolution

•ModelMart clearly identifies properties that modelers in conflict are updating within the same time period. Details of the conflict along with user information provides a basis for resolving the conflict.

Versioning & Archiving

Performance conscious versioningOnly delta objects kept

An archive rolls up all the delta version in a full model archiveAuto Archive option

Report on differences Restore to current model

The Standards Administrator The Standards Administrator Needs:Needs:•Reuse mechanisms•Standard security•Meta data extension capability•Reporting and navigation

Key Roles and Requirements

MM Standards Implementation

Standard objects Sub-model security on models Combination of ModelMart sharing mechanisms

with specific standardization capabilities of client tools, such as ERwin’s Independent Attributes and Macro Language, provide powerful naming standards mechanism

User-Defined Properties support custom extensions

“There’s no substitute for defining and sticking with corporate standards, and metadata repositories, such as ModelMart … and forthcoming products based on Microsoft’s global repository specification all smooth the path to corporate-wide data definitions standards.

Buying into E-CommercePC Week

Feb. 2, 1998

Corporate-wide Standards

Who Buys ModelMart?

Existing ERwin and BPwin customers ERwin and BPwin prospects working on large

projects Groups of 5 or more modelers

working in tandem

Sales Differentiators

Intelligent, controlled updatingvs. dynamic updating

Supports working in offline mode

Low TCO

Jasmine Integration

The Virtual RepositoryJasmine TNDInfrastructure

BusinessProcesses

Information Applications ManageModels

Common Services

Common Import & Export

Common UI & APIs

ADvisor TND

•ModelMart Persistence•R/OEE•Harvest

•Jasmine DB•Other System Files•Publication Repository