# Presentation: 355056

## I-MANAGE Design Overview

**Basic design principles**
**Building Integrated Systems Using COTS**
**Relational Database Technology**
**What It Means to Us**

## I-MANAGE Design Overview

_**One hand gives**_
**Provides extensive functionality based on the needs of many different users**
**System designed with integration in mind**
**Usually comes with built-in reporting, query tools**
**Add new modules as our requirements dictate**
**Incorporates best practices**
**Maintained and enhanced by vendor who specializes in software development**
- They stay abreast of new technologies
- We focus on core business

_**One hand takes away**_
**Generic functionality not specifically tailored to our needs**
**Requires specialists to deploy system**
**Must rely on vendor to maintain**
**Can’t customize without losing major benefit of system**
**Forces consistency across organizational groups**
**Will force change in business processes**
- Some business activities may actually take longer
- Must retrain staff

**I-MANAGE** **Basic Design Principles**

## I-MANAGE Design Overview

**In general, “design” of commercial off-the-shelf (COTS) or government off-the-shelf (GOTS) software involves:**
- Installing the software with user-defined settings to tailor the applications to your technical environment.
- Once installed, selecting from a wide range of user-defined configuration settings which tailor the application to your business environment.
- Organizations typically optimize this process by using systems integrators skilled in the selected software package, working together with subject matter experts from within the organization.
**However, even with the significant flexibility of COTS / GOTS applications, it is still necessary to analyze, design, and implement modified business practices to gain the most benefit from the new systems. **

**I-MANAGE** **Basic Design Principles**

## I-MANAGE Design Overview

**Proposed solutions must align with DOE’s Enterprise Architecture.**
**To the greatest extent possible, data should be physically stored in one location, accessible through the relational database architecture.**
**COTS / GOTS software will not be “customized”, where customization involves modifications to the baseline software as installed.**
_***Never***_ alter the underlying database structure.
- The general rule is to re-engineer business processes to align with software.

**I-MANAGE** **Basic Design Principles**

## I-MANAGE Design Overview

**I-MANAGE Program Management must deliver an *****enterprise***** solution.**
- This provides important benefits to the organization:
- Elimination of redundant systems, and associated development and maintenance costs.
- Eliminates multiple data feeds and interfaces.
- Enables a common repository for corporate information.
- Provides consistent, accurate reporting using approved data.
- Allows standard business processes, policies, and procedures across the organization.
- Clearly, this is the direction of the President, and OMB.
- Provides the best way to coordinate business processes within an integrated suite of software applications.

**I-MANAGE** **Basic Design Principles**

## I-MANAGE Design Overview

**What are the tradeoffs?**
- Over time, DOE Program Offices and Operations, Field, and Regional Offices have developed custom systems designed for their specific needs.
- Developed in response to real problems.
- Built upon a variety of hardware and software platforms.
- In many cases, these systems provide a combination of mission specific data processing capabilities combined with overlapping enterprise data processing functionality.
- Merging these systems with the I-MANAGE Program suite of integrated systems will require these organizations to relinquish some of their autonomy.
- In some cases, they will end up with a better solution, but in some cases, they may not.
- This will reduce their development and maintenance requirements, but will require that they align business practices with the new applications.

**I-MANAGE** **Basic Design Principles**

## I-MANAGE Design Overview

**How will these determinations be made?**
- We will take a structured approach based on an enterprise architectural model:
- Identify systems that may possess overlapping functionality.
- Analyze the systems to define mission specific business processes vs. enterprise business processes.
- Develop a conceptual systems model that clearly identifies each group of processes.
- Work with the owning organization to establish the costs / benefits of the system.
- Develop alternative solutions that entail:
- Elimination of the legacy system, and transfer of business processes to a system within the I-MANAGE suite of applications.
- Annexation of the enterprise business processes by I-MANAGE, and integrating / interfacing the mission specific business processes in the legacy system.
- Seek approval of the recommended alternative through the appropriate levels as previously identified.

**I-MANAGE** **Basic Design Principles**

## I-MANAGE Design Overview

**I-MANAGE** **Basic Design Principles**

**Mission specific business applications for DOE Program Offices and Operations, Field, and Regional Offices**

**Strategic Planning**

**Field Budget Call**

**Corporate Review Budget**

**President’s Budget**

**OMB Budget / Passback**

**Congressional Budget**

**Commitments, Obligations**

**Appropriation / Cont. Resolution**

**Budget Distribution**

**Costs, Outlays**

**Financial Reporting**

- I-MANAGE Standard Budget System

- STARS, Data Warehouse

**I-MANAGE** **Integrated Performance Management & Reporting**

- Enterprise Business Processes

- Mission Specific Business Processes

## I-MANAGE Design Overview

**I-MANAGE Design Overview**

**General**
**Ledger**

**STARS Oracle Federal Financials V11i**

**Sub-Ledgers**

**Purchasing**

**Accounts **
**Payable**

**Accounts **
**Receivable**

**Fixed**
**Assets**

**Building Integrated Systems Using COTS**

- Oracle Federal Financials is a “modular” COTS system.  For example, the General Ledger module receives journal entries from the sub-ledger modules, purchasing, accounts payable, accounts receivable, and fixed assets.
- Each of the individual modules is comprised of :
- Tables, i.e. data storage entities made up of columns and rows
- Indexes, i.e. tables with pointers to individual rows (or records) within a separate table
- Forms, i.e. online data entry screens
- Reports
- Packages, i.e. units of program code that perform specific processes and may be called from multiple forms or reports
- Triggers, i.e. units of program code that automatically execute before a row (or record) is added, updated, or deleted
- Workflows, i.e. automated, sequenced business rules based on standard business processes

## I-MANAGE Design Overview

**I-MANAGE Design Overview**

**General**
**Ledger**

**STARS Oracle Federal Financials V11i**

**Sub-Ledgers**

**Purchasing**

**Accounts **
**Payable**

**Accounts **
**Receivable**

**Fixed**
**Assets**

**Building Integrated Systems Using COTS**

- Oracle Federal Financials provide “open” pathways into the software that allow other applications to tightly integrate (real time / near real time duplex data exchange), or loosely integrate through an interface (normally data flows in one direction on a scheduled basis).

**Other COTS **
**Applications**
**(e.g. PeopleSoft)**

**Other Proprietary **
**Applications**

**Additional**
**Modules**

- Purchase and install New Oracle modules, or other software vendor products that have been certified by Oracle.

- Best approach:  open pathways are available through Application Programming Interfaces (APIs).
- In some cases, it is necessary to build direct integration with other Oracle based  or ODBC compliant database applications.

## I-MANAGE Design Overview

**I-MANAGE Design Overview**

**General**
**Ledger**

**STARS Oracle Federal Financials V11i**

**Sub-Ledgers**

**Purchasing**

**Accounts **
**Payable**

**Accounts **
**Receivable**

**Fixed**
**Assets**

**Developing “Bolt-On” Functionality**
- When the Department of Energy selected Oracle Federal Financials to replace their core financial systems, they also purchased the Oracle Developer’s Workbench. This Integrated Development Environment (IDE) allows trained technical programming staff to analyze, model, design, develop, and test software applications that may be tightly integrated with the core Oracle Federal Financial Applications.
- This provides practically unlimited flexibility for an organization to address specific gaps in the COTS software suite based on a careful decision process that considers the immediate and long term costs of development, deployment, and maintenance.
- Oracle has documented development standards that provide specific guidance in the design, development, and administration of applications intended for integration with Oracle’s e-Business Software.  By following these standards, organizations can control the cost of maintaining these applications when it is necessary to apply software patches, upgrades, new releases, or even new versions of the Oracle e-Business Software.

**Building Integrated Systems Using COTS**

## I-MANAGE Design Overview

**Relational Database Technology**

**Leveraging Oracle’s Relational Database Management System (RDMBS)**
- Oracle applications reside on Oracle’s RDBMS architecture.  Simply put, this data storage architecture was originally designed by Dr. E.F. Codd from IBM, based upon mathematical principals.  A relational database is made up of individual tables which consist of columns (fields) and rows (individual records within the table).  An individual row is identified through a unique value or values in the primary “key” field.

- Primary
- Key

- Table, with column definitions

## I-MANAGE Design Overview

**Leveraging Oracle’s Relational Database Management System (RDMBS)**
- Relational databases are just that.  Relationships between tables are explicitly defined to the relational database management system, and this allows trained users to insert, select, update, or delete data from the tables using these relationships.  The “language” used to issue these commands to the system is called “Structured Query Language” or SQL.  The “query” below provides customer / order data.

- One (customer) to many (orders) relationship

- SELECT DISTINCTROW Orders.CustomerID, Orders.OrderID, Orders.OrderDate,
- FROM Customers INNER JOIN Orders ON Customers.CustomerID = Orders.CustomerID;

**I-MANAGE Design Overview**

## I-MANAGE Design Overview

**Leveraging Oracle’s Relational Database Management System (RDMBS)**
- Why is this important?  Because, with this technology, we can easily link a set of relational tables that contain performance data with our Oracle Federal Financial Application tables to link budget execution and performance data.  Assuming our I-MANAGE Standard Budget System software is built upon an ANSI compliant relational database platform, we have the ability to link budget formulation, budget execution, and performance data in a single, seamless, integrated solution!

**Budget**
**Data**

**Performance**
**Data**

**Accounting**
**Data**

- RDBMS Architecture

**I-MANAGE Design Overview**

## We need to select the proper balance between enterprise business objects, program / mission business objects.
Our proposed direction is to leverage additional COTS / GOTS applications and modules to the greatest extent possible, however, we may have to develop some functionality on our own.
When individual solutions are selected or developed, they must fit within the Enterprise Architecture, and integrate with the installed base of applications.

**Budget**
**Data**

**Performance**
**Data**

**Accounting**
**Data**

- RDBMS Architecture

**I-MANAGE Design Overview**

**We need to select the proper balance between enterprise business objects, program / mission business objects.**
**Our proposed direction is to leverage additional COTS / GOTS applications and modules to the greatest extent possible, however, we may have to develop some functionality on our own.**
**When individual solutions are selected or developed, they must fit within the Enterprise Architecture, and integrate with the installed base of applications.**