Capabilities

InBase President, Randy Weis, has developed a database architecture pattern
that allows for the versioning of database objects, allowing the application
to maintain and retrieve instances of an object "as of" any given point in
time. This also allows for proactive updates, retroactive updates,
sandbox and hypothetical updates. It also provides the ability to spread
a business transaction across multiple physical units of work, many days,
several tables and numerous rows, yet release/publish them all together in a
small release transaction. This pattern builds upon the bi-temporal
pattern that he previously developed and implemented.

Randy, in collaboration with Dr. Tom Johnston of
Mindful Data, Inc., another
specialist in this space, are publishing a series in
DM-Review, explaining the
various Data History Patterns, leading up to the ultimate pattern.
Check
out the series here, and give us your feedback.

Conceptual Modeling

IBI will work with your team gathering requirements and developing a
Conceptual Data Model. This identifies high level fundamental
entities, and provides a starting point for future design

Logical Design

After capturing detailed requirements, IBI organizes these Entities and
Attributes into an "normalized" Logical data model. Tools, such as
ER-Win are used to help create a ERD (Entity Relationship Diagram). In
addition, Primary Keys and Relationships are defined. This model helps
simply the development, and enables future enhancements

Physical Model

Volumetrics and Access Paths are analyzed, and mapped to critical/high
volume functions to help identify areas of the model that might benefit from
special "denormalization", indexes or other tweaks to improve performance.
Trade-offs are documented and discussed. The physical model updated
accordingly

Physical Database

Database platform and DBMS vendor is determined. The Data
Definition Language (DDL) is created, and standards are defined and applied
to simplify program development, database migration and roll-out. The
database is created

Physical Model

Volumetrics and Access Paths are analyzed, and mapped to critical/high
volume functions to help identify areas of the model that might benefit from
special "denormalization", indexes or other tweaks to improve performance.
Trade-offs are documented and discussed. The physical model updated
accordingly

Performance monitoring and Tuning

The database is monitored for any low hanging fruit that will benefit
from simple tweaks, such as an index or minor SQL adjustment. This is
an on-going process as new requirements are added and data volumes change.
Often, related architectures, such as the Operating Systems, TP Monitors,
Disk Subsystems, and the like, need to me evaluated and tuned, too.

Reference Accounts

Blue Cross Blue Shield

Data Architecture, data modeling and physical databases

GoMedia

Vertical Market on-line Expo

Kemper Insurance

Implemented the IAA (Insurance Application Architecture) data model with
IBM. Troubleshooting of many of their legacy systems. Peoplesoft
tuning.

TransAmerica Commercial Finance (GE Finance)

Worked with IBM in designing and implementing a Floor Plan Financing
system. Within two months of implementing the centralized system, the
company turned profitable, and exceeded profit projections for over 5 years
in a row.