The MISCOMP Project

The 12th DOE Office Information Technology Conference - July 1995


The Computing Division...

DRUIDS - Equipment and Services management

Financials - Budget and planning, reconciliation, tracking

Document Management - access, storage, link to transactions

Client/Vendor Agreements - contracts, MOU's, etc.

Software management - licences and support

Building and Space - planning, graphics+database

Environment Safety and Health - all tracking issues

Administrative activities not covered elsewhere

Issues in building a New Information System
Objectives of MISCOMP...

Plan for everything to change sometime in the future:

--technology - platforms, tools

--database systems

--functionality required

--views of the data

--services and functions performed/supported

--types of data used to support our tasks

Objectives of MISCOMP...

Build a (logically) central repository of data

Use it to support/automate "business" processes

Get data to people's desktop

--at the appropriate summary level

--with suitable user interface

--from their viewpoint

Stages and Key events related to MISCOMP


Old Information System Model

buy "functional packages" e.g. "Receiving", "Inventory", "Human resources"

--loosely couple them

--re-enter data

no data dictionary or data standards across packages

--possibly export/translate/import data

stick with each package for 10+ years

--freeze technology

New Information System Model...

define data standards, data dictionary, data model

provide a (logical) central repository of data

buy or build as many applications as needed

--each dealing with certain objects and services - interfaced to "views" of the central repository data

New Information System Model...

use parts-assembly principles to build or bind applications

--client/server, re-usable code, layers isolating client from the database

--information hiding/views

keep the architecture - change out everything else over 10 years

For the New Information System Model...

have to understand very well...

--what objects/data are used/by whom/for what/the business

--how they relate to others view of the world

--how all the objects/data are interrelated

--how the division's objects/data are related to labwide data

For the New Information System Model...

also have to understand how to use the current technology...

Analysis & Architecture

The Big Picture
A Multi-Faceted Approach

Architecture & Implementation

Layered Architecture (concepts)
Layered Architecture (specifics)

Conceptual Modeling as the key to architectural design

With a well-designed layered architecture we can support the models and achieve the following in our implementation:




--Incremental development

--Iterative development


Prototyping as a way of understanding requirements...


Current Status...

Equipment Database - Operational

--Hardware (Fixed Assets)


--Hardware/Software Maintenance Contracts

Network Services

--Name Server Table Generation - Final Checkout

--Node Requests - Final Checkout

Current Status...

DRUIDS - In Development

--C++ Object Server

--XVT Platform Independent GUI

--Persistence I/F to Oracle from C++

--Deployment of First Request / Job Tracking this Summer

Current Status...

Document Management - In Procurement

Help Desk - Integration of Purchased Product underway

--Action Request from Remedy

Additional Desktop Query Tools (GQL) under evaluation


Significant Improvements to Ways of Doing Business - some examples...

HW Maintenance Contract

--Time to Prepare Info for Vendor and Verify Vendor Response

--Was: >2 FTE Months

--Now: <2 FTE Weeks


--Was: >4 FTE weeks

--Now: <4 FTE days


Significant Dollar Savings

--$300K/year explicitly identified...

--And increasing...


Significant Adaptation to Changing Technology...

--Forms 3

--Forms 4


While maintaining same underlying conceptual model of actors, provisions, claims, and requests.


With MISCOMP, the Fermilab Computing Division has been able to:

--Handle an increasingly complex business and

--Do it better..