Hazardous Substance Management System (HSMS)

System Technical Architecture Guide (STAG)

4 October 1996

Distribution authorized to U.S. Government agencies and specified contractors only, to, protect technical information from automatic dissemination under the International Exchange Program or by any other means. Requests for this document should be referred to Project Officer, Hazardous Substance Management System (PO HSMS), ATTN: SFAEPS-SB, 9350 Hall Road, Suite 142, Fort Belvoir, Virginia 22060-5226

i

HSMS System Technical Architecture Guide

4 October 1996

Table of Contents

PURPOSE .....................................................................................................................................3 SYSTEM CONFIGURATION......................................................................................................3 DEFINITIONS................................................................................................................................3 ORGANIZATIONAL RESPONSIBILITIES ...............................................................................6 HQDA ACSIM (ODEP) .............................................................................................................6 HQDA ODCSLOG .....................................................................................................................6 U.S. Army Environmental Center..............................................................................................6 Project Manager, Sustaining Base Automation (HSMS Project Officer)................................6 U.S. Army Information System Engineering Command (USAISEC) .......................................7 GENERAL OPERATIONAL CONCEPT...................................................................................7 General........................................................................................................................................7 System Features .........................................................................................................................7 General Operational Concept ....................................................................................................7 Technical Implementation ..........................................................................................................8 TECHNICAL REQUIREMENTS ................................................................................................8 Hardware .....................................................................................................................................8 Data Base Server...................................................................................................................8 Workstation.............................................................................................................................9 Printers ..................................................................................................................................10 Bar Code Equipment.............................................................................................................10 Other Equipment...................................................................................................................10 Software.....................................................................................................................................10 Operating Environment ........................................................................................................10 HSMS Application Software ................................................................................................11

i

HSMS System Technical Architecture Guide

4 October 1996

DATA BASE MANAGEMENT SYSTEM................................................................................11 DATA BASE MANAGEMENT SYSTEM................................................................................11 Utilities. .................................................................................................................................11 Screen Development/Painting ..............................................................................................11 Communications/Infrastructure................................................................................................11 Network Interface Card ...........................................................................................................11 Modem..................................................................................................................................12 24 Port UTP Stackable Hub .................................................................................................12 ORGANIZATIONAL POINTS OF CONTACT........................................................................ 12

ii

HSMS System Technical Architecture Guide

4 October 1996

Hazardous Substance Management System (HSMS) System Technical Architecture Guide

1.

Purpose.

This guide provides an overview of the technical architecture associated with the implementation of the Hazardous Substance Management System (HSMS). It describes the hardware, software, and communications infrastructure associated with a standard implementation of HSMS to achieve an Initial Operational Capability (IOC) at the installation. It will describe the hardware components which will be procured when existing infrastructure is not available. It will also describe the minimum configuration for servers and workstations if an installation desires to use existing hardware. 2.

System Configuration.

HSMS will be implemented at all Army installations in a standard hardware and software configuration. The implementation of HSMS at an installation will be designed to support existing or planned hazardous substances management business practices. However, in order to maintain configuration management for the system, the technical implementation will be changed only in the number of workstations and type of connectivity at an installation rather than in the type of equipment, software or operating environment. 3.

Definitions.

a. Data Base Server. The HSMS DB Server is used to host the HSMS Data Base for an installation. The data base management system which resides of the server will be Informix On-Line Workgroup Server Version 7.1. The data base is accessed through the use of Structured Query Language (SQL) queries developed through the HSMS application software or report writer software. b. Workstation. The HSMS workstation is a fully functional personal computer on which the HSMS application software resides. The workstation also contains the necessary software in order to provide connectivity to the HSMS DB Server and output devices such as printers and bar code equipment. c. Operating Environment. The operating environment defines the operating system which will be used on the DB Server and Workstations for HSMS. The Army standard operating environment will be Windows NT 3.51 Server/Workstation. d. HSMS Data Base. The HSMS Data Base consists of the data elements required to operate HSMS at an installation. It consists of two types of data - Static and Dynamic. The Static data is the data which is collected and describes the constant physical parameters of the installation such as

3

HSMS System Technical Architecture Guide

4 October 1996

storage site locations, users, etc. Dynamic data is data which is used in the day to day operation of HSMS. It is transaction based and captures data on requisitions, receipts and issues of hazardous substances. Static data and Dynamic data will be updated during the operation of HSMS. e. Single Application. The single application is an implementation of HSMS in which a Data Base Server (which may be combined into a single workstation configuration) and one or more workstations have been fielded within the context of a single operational activity. An operational activity is defined to be a single organization which requests, receives, issues and accepts turn-in of a set of hazardous materials. An example of an operational activity if the Directorate of Public Works, the Directorate of Logistics and/or the Director for Community Activities. Additional support activities which may be included in this configuration are the Installation Safety Office, MEDCOM Industrial Hygiene office, Installation Environmental Office, Hazardous Waste Management activity and others as deemed necessary to manage the hazardous materials. f. Multiple Application. The multiple application is an implementation of HSMS in which a Data Base Server and several workstations have been fielded across multiple operational activities. Multiple application implementation will be accomplished by installations as they transition from IOC to FOC. g. Initial Operational Capability (IOC) . IOC is defined a single application of HSMS in which the full range of functions in HSMS (hazardous substance management, pollution prevention and hazardous waste management) with a limited scope in terms of organizations participating and materials managed. IOC is a configuration of hardware, software and business practices defined by the installation which establishes their plan for achieving the management of hazardous materials at some level on the installation (one or more operational activities, one or more hazardous material categories of supply). It is the minimal configuration which is fielded to an installation which allows for management of a subset of all hazardous substances at a level defined by the installation that is achievable and manageable in the short term (3-4 months). h. Full Operational Capability (FOC) . FOC is a configuration of hardware, software and business practices which encompasses all reportable organizations and hazardous materials on an installation. (Also known as “fence to fence” implementation). i. Initial Site Visit. The purpose of the Initial Site Visit is to lay the groundwork for followon functional and technical site visits. During the visit the Garrison Commander and key staff directors (DPW, DOL, DOIM) are provided a briefing on the capabilities and benefits of the HSMS. Initial coordination is conducted with the Installation HSMS POC. At the conclusion of the initial site visit, a checklist of activities to be accomplished prior to the start to the Functional/Technical Site survey will be discussed with installation HSMS points of contact and left for action. It is envisioned that these activities will be accomplished in a 4-6 week period after the conclusion of the initial site visit although the functional/technical questionnaires must be completed and returned to the HSMS Project Officer after the end of the first week following the initial site visit. In cases where the situation warrants, the contractor tasked to support your installation will remain on site after the site visit to assist in data

4

HSMS System Technical Architecture Guide

4 October 1996

collection and development of the operational concept and business practices for hazardous material management. This must be accomplished so that there is sufficient time to review the surveys in preparation for the Functional/Technical Site Survey. The checklist of required items is included in the Site Implementation Plan and at Appendix C to this document. j. Technical Site Survey. The technical site survey is conducted by the HSMS Engineers to identify the technical requirements (hardware, communications infrastructure and other engineering requirements) for the implementation of HSMS at an installation. It is conducted in conjunction of the functional site survey and is a coordinated effort with the Directorate of Information Management. The technical site survey identifies the specific requirements by user and building for HSMS IOC as well as assessing the overall infrastructure at the installation for migration to FOC. k. Functional Site Survey. The functional site survey is conducted by personnel from the functional proponent’s office. The purpose of the functional survey is to identify HSMS users, begin initial preparation for the data collection and data base development of the HSMS DB and work with the installation of the development and implementation of hazardous substance management business practices. l. Site Implementation Visit. During the site integration visit, the hardware and executive software will be installed, the application software and installation data base will be loaded, system interfaces will be initiated and the total system will be integrated and tested. At the conclusion of the integration and testing, functional users will receive user training. Prior to this the System Administrator will have received training through Defense Environmental Security Corporate Information Management Program Management Office (DESCIM PMO) at Norfolk, Virginia. After integration and training, members of the site implementation team will remain on site for a period of time to assist in bringing the system to IOC. m. Hazardous Substance Management Business Practices. These are the operational methodologies implemented at an installation for the management of hazardous substances including procedures for requisitioning, receipt, storage, issue, use and disposal. n. Chief of Installation (COI) . The COI is the government representative of the Project Manager, Sustaining Base Automation (PM SBA). The COI manages all aspects of the installation and integration of HSMS at an installation including leading the technical and functional survey teams, coordinating all aspects of HSMS implementation with the installation HSMS Point of Contact, development and completion of the Memorandum of Agreement and coordination of activities between the installation an all other participating organizations. o. USAEC Project Officer (PO). The USAEC PO is responsible for the overall implementation of HSMS at an installation including coordination of site visits, training and schedules for implementation.

5

HSMS System Technical Architecture Guide

4.

4 October 1996

Organizational Responsibilities.

a. HQDA ACSIM (ODEP) . The HQDA ACSIM serves as the functional proponent for HSMS. Additionally, the ACSIM has been appointed by the Deputy Assistant Secretary of Defense for Environmental Security (DASD(ES)) as the Department of Defense Executive Agent for HSMS. Staff oversight of the HSMS for the ACSIM has been delegated to the ACSIM Director for Environmental Programs (DEP). The DEP is responsible for policy, budget and oversight of the program. b. HQDA ODCSLOG. The HQDA DCSLOG serves as the subject area functional proponent for hazardous materiel management. Staff oversight for the DCSLOG has been assigned to the ODCSLOG Supply and Maintenance Directorate, Supply and Maintenance Policy Division (SMP). ODCSLOG SMP develops logistics policy and business practices related to hazardous material management at Army installations and coordinates with the DEP for establishing and documenting functional business practice changes for installation and materiel management in support of HSMS implementation. c. U.S. Army Environmental Center. USAEC serves as the Army’s Subject Area Functional Proponent for Environmental Security (ES) issues. USAEC plans and executes HSMS initial operational capabilities at the five Phase 1A prototype sites (Schofield Barracks, Pine Bluff Arsenal, Forts Bliss, Knox and Campbell) and supports transition of programmatic/acquisition management for Phase 1B sites, establishes HSMS project teams to coordinate functional assessments and site visits including the development of individual installation functional fielding configurations, develops, coordinates and publishes training plans and procedures for the training of HSMS users and system administrators, coordinates scheduling of training for HSMS functional users and system administrators, identifies functional data requirements for HSMS processing and assists in the development of hazardous management business practices and prepares a strawman approach to used as a starting point for development of installation unique processes. d. Project Manager, Sustaining Base Automation (HSMS Project Officer) . PO HSMS serves as the centralized manager and provides overall direction and guidance for life cycle management of the project including testing, acquisition, fielding and post deployment system support for HSMS as a system. PO HSMS procures, installs, integrates HSMS infrastructure including hardware, communications, networks, data bases and application and executive software, ensures that all required technical and programmatic documentation is developed, reviewed and submitted in accordance with established milestone schedules, coordinates and monitors project schedules and milestones associated procurement, integration, testing, and implementation of HSMS, coordinates with all appropriate organizations in support of the overall program including provision of system engineering and technical assistance, coordinates and transitions the system interface strategy into system interface specifications/interface agreements (SIS/IA) and develops the automated system interface utilities/applications, coordinates and participates in HSMS testing to ensure operational requirements and technical specifications are met, ensures project hardware, software, and communications meet

6

HSMS System Technical Architecture Guide

4 October 1996

appropriate DoD and/or Army architecture requirements, and coordinates and monitors project schedules and milestones. e. U.S. Army Information System Engineering Command (USAISEC) . USAISEC provides system engineering and technical assistance in support of PO HSMS for technical site surveys, site integration and implementation and centralized customer assistance and help desk capability to HSMS users. 5.

General Operational Concept.

a. General. HSMS is used to track and manage hazardous substances at the chemical constituent level from cradle-to-grave or from the time the item is requisitions until is completely utilized or shipped off the installation as hazardous waste. It also is capable of providing the legal reporting requirements to satisfy Executive Order 12856 (Pollution Prevention Act) and the Emergency Planning and Community Right to Know Act (EPCRA), as well as collects data for use in developing Tier I, Tier II and Form R reports. HSMS tracks hazardous substance usage and hazardous waste generated through the use of a set of process algorithms which calculate chemical release based on the way the material is utilized (process). The system tracks hazardous substance that is requisitioned/ordered, received, stored, issued, used, recycled or spilled. b. substances:

System Features.

• • • • • •

HSMS maintains the following information regarding hazardous

Local Material Safety Data Sheets (MSDS) Material chemical constituent information Chemical hazard information Authorized Use List (AUL) for hazardous substances Information about all processes that use hazardous substances or generate hazardous waste Hazardous substance and chemical inventory

c. General Operational Concept. HSMS will be implemented to support the hazardous substance management business practices implemented on an installation. It operates best when implemented under business practices which call for the use of a Hazardous Material Control Center (HMCC) or pharmacy for requisition, receipt, issue, turn-in and disposal of all hazardous substances on an installation. NOTE HSMS supports business practices which have been implemented at Army installations which include centralized control of these materials in a HMCC/Pharmacy concept. HSMS has not been designed as a replacement for these business practices but rather as a support tool to provide an automated management processes to installations.

7

HSMS System Technical Architecture Guide

4 October 1996

The HMCC can either have physical control of all hazardous substances or may be implemented to have virtual control over the materials (Virtual control means that the pharmacy activity does not actually work with the materials but maintains accountability as a supply support activity). Under the concept of fielding of HSMS, a single application implementation will be defined as the Initial Operational Capability (IOC) which will allow for management of a subset of all hazardous substances for a subset of all organizations using or managing these materials. Based on the IOC configuration, the technical site survey will be conducted to determine what sites/users within the installation will receive the system. d. Technical Implementation. HSMS technical implementation has been standardized for all installations. A general technical implementation for HSMS is shown at Figure 1. It should be noted that the only thing that will change between installations is the number of workstations, printers and bar code equipment and the method for connectivity between the workstations and the DB Server. Specifics on the hardware, software and communications components is described in paragraph 6 below. 6.

Technical Requirements.

The hardware, software and communications components for HSMS are described below. These items are the Army standard and will be procured when required to implement HSMS at an installation. Items which include a description of minimum configuration indicate the minimum required configuration for a DB Server or Workstation to be utilized for HSMS when the installation has these items on hand or already ordered. The minimum configuration is defined as that configuration which is required in order to operate HSMS. Appendix B provides a summary of the system components. a.

Hardware.

(1) Data Base Server. Provides for access to the HSMS data base from the HSMS application software which resides on the user workstations. The data base server operates in a Windows NT operating environment and uses Informix On-Line Workgroup Server 7.1 as the data base management system. Table 6-1 provides the minimum configuration for a Server and Table 6-2 provides the standard configuration which is being centrally procured. DB Server Minimal Requirements Processor Intel 486DX266 MHz CPU RAM 64 MB Hard Drive (Free Space) 200 MB Free Space (Minimum for HSMS) Monitor 14” SVGA Communications Xircom multi-port modem card/ Interface Card w/AUI, BNC and RJ-45 CD-ROM Quad (4x) Speed CD-ROM Drive Table 6-1 - Minimum DB Server Configuration

8

HSMS System Technical Architecture Guide

Processor RAM Hard Drive Monitor Communications Tape Back-Up CD-ROM

4 October 1996

Standard Configuration Intel Pentium 120 MHz CPU 64 MB 8 GB (2 x 4GB) 15” SVGA Xircom multi-port modem card/ Interface Card w/AUI, BNC and RJ-45 DAT Tape Back-Up Unit Quad (4x) Speed CD-ROM Drive Table 6-2 - DB Server Standard Configuration

(2) Workstation. Workstations are used by HSMS users to operate the HSMS application software. The workstations access the data base on the data base server using a data base product from Informix called ESQL/C w/I-NET. The workstations are connected to one or more output devices to either print reports (laser printer), bar codes (Bar code printer), or preprinted forms (dot matrix printer). The workstations also include a copy of a report writer software product for doing ad hoc reports (Crystal Reports). The workstations may be connected to the data base server as part of a local area network or through the use of a modem and telephone line. The workstations are all configured to be used in either mode. Table 6-3 provides the minimum configuration for a Workstation and Table 6-4 provides the standard configuration which is being centrally procured. Workstation Minimum Configuration Processor Intel 486DX266 MHz CPU RAM 16 MB Hard Drive (Free Space) 100 MB Free Space (Minimum for HSMS) Monitor 15” SVGA Communications V.34 28.8 Kbps internal modem card/ Microdyne 32-bit PCI network card CD-ROM Dual Speed CD-ROM Drive Table 6-3 - Workstation Minimum Configuration

Processor RAM Hard Drive Monitor Communications

Workstation Standard Configuration Intel Pentium 120 MHz CPU 32 MB IDE 1.2 GB 17” SVGA V.34 28.8 Kbps internal modem card/ Microdyne 32-bit PCI network card

9

HSMS System Technical Architecture Guide

CD-ROM

4 October 1996

Internal Hex (6x) CD-ROM Drive Table 6-4 - Workstation Standard Configuration

(3) Printers. Printers are used for printing standard and ad hoc reports required by HSMS and for printing multi-part transportation documentation (DD Form 1348-1). (a) Minimum/Standard Configuration. The minimum and standard configuration for printers are the same.

Laser Printer Dot Matrix Printer

Printers Laser Printer OPTRA LX+ Lexmark 2381

(4) Bar Code Equipment. Bar code equipment is used by HSMS to produce bar codes for hazardous substance and then to read the bar codes as the material is moved through the installation. (a) Minimum/Standard Configuration. The minimum and standard configuration for bar code equipment are the same.

Bar Code Scanner Bar Code Reader Bar Code Printer

Bar Code Hardware Intermec Bar Code Scanner 1545E Intermec Bar Code Reader 9710E01 Intermec Bar Code Printer 4100B

(5) Other Equipment. These are additional equipment items which may be required in order to fully implement HSMS at your installation. (a) Minimum/Standard Configuration. The minimum and standard configuration for other equipment are the same. Other Equipment Uninterruptable Power Supply 24 Port UTP Stackable Hub Surge Suppressers Intermec Bar Code Media Kit b.

Software (1)

Operating Environment.

10

HSMS System Technical Architecture Guide

(a) (b)

4 October 1996

DB Server - Windows NT Server Version 3.51 Workstation - Windows NT Workstation Version 3.51 DOS 6.22 (Note 1) Windows for Workgroups 3.11 (Note 1)

(2)

HSMS Application Software. HSMS Version 2.1

(3)

Data Base Management System.

(4)

(a)

Informix On-Line Workgroup Server 7.1

(b)

SQL Query Generator. Informix ESQL/C with I-NET

Utilities. (a)

Report Writer. Crystal Reports

(b)

Bar Code Printing. BarTender (Note 1)

(c)

Screen Development/Painting. ViewPoint Pro (SA only)

Note 1 BarTender printer drivers will not operate in a Windows NT environment. Therefore, until the vendor develops printer drivers (December 1996) which allow users to print directly to the Bar Code Printer from the HSMS application software, DOS 6.22 and WFWG 3.11 are included in the standard configuration.

c. Communications/Infrastructure. The communications/infrastructure requirements will be tailored to the requirements of the installation. However, all workstations will contain a modem and a network interface card to provide flexibility to field in any environment. Although a Network Hub and Xircom Multi-Port Modem card are described in the standard configuration, the existing infrastructure on the installation will determine whether they are procured. (1)

Network Interface Card. Microdyne 32-bit PCI Network Card.

11

HSMS System Technical Architecture Guide

4 October 1996

(2) Modem. Internal ISA V.34 (28.8 Kbps) modem. The modem must be 100% Hayes compatible and supported by the Xircom Multi-Port Modem card. (3)

LAN Connectivity. 24 Port UTP Stackable Hub.

7. Organizational Points of Contact. The following listed people can provide additional information of the technical aspects and/or operational concept for HSMS.

Project Manager, Sustaining Base Automation HSMS Project Officer (DSN 656) Mr. Jack Ross (703) 806-4604 [email protected] Support Contractors (Anteon Corp) Mr. Bill Eggers (703) 806-4223 [email protected] U.S. Army Environmental Center (DSN 584) Mr. Stan Childs (410) 671-1226 [email protected] Support Contractors (Dynamac Inc) Mr. Jim Head (804) 526-8951 [email protected] U.S. Army Information Systems Engineering Command (DSN 879) Mr. Kevin Jordan (520) 538-3129 [email protected] Support Contractors (SAIC) Mr. Don Albright (520) 452-6636 [email protected] Mr. Rick Bywater (520) 452-6637 [email protected]

12

HSMS System Technical Architecture Guide

6 August 1996

Appendix A - HSMS Standard Fielding Configuration HSMS Version 2.1 Windows NT 3.5.1 WS ESQL-C w/ I-NET ViewPoint Pro Crystal Reports

Dot Matrix

Bar Code Printer Scanner/Reader

Windows NT 3.5.1 Server Informix On-Line Workgroup Server 7.1

HSMS SA Workstation

HSMS Version 2.1 Windows NT 3.5.1 WS ESQL-C w/ I-NET Crystal Reports

ETHERNET

HSMS Data Base Server

HSMS

HSMSDB

Dot Matrix Printer

XIRCOM

HUB

UPS

HSMS User Workstation (Material Receiving Point) (LAN Connect)

Telephone Connectivity Modem

HSMS Version 2.1 Windows NT 3.5.1 WS ESQL-C w/ I-NET Crystal Reports

Optra Laser Printer

Bar Code Printer 1

HSMS User Workstation (Modem Connect)

HSMS System Technical Architecture Guide

Appendix B - HSMS System Architecture

HSMS System Architecture Hardware Data Base Server Workstation 120 MHz Pentium CPU 120 MHz Pentium CPU 64 MB RAM 32 MB RAM 2 x 4GB Hard Disks (8GB Total) 1.2 GB IDE Hard Disk Single Platter Quad Speed CD-ROM Internal Hex Speed CD-ROM 15” Color SVGA Monitor 17” Color SVGA Monitor Interface Card w/AUI, BNC and RJ-45 Microdyne 32-bit PCI Network Card Xircom Multi-Port Modem Card (As Rqd) Internal ISA V.34 (28.8kbps) Modem Uninterruptable Power Supply (UPS) Surge Suppresser 24 Port UTP Stackable Hub (As Rqd) DAT Tape Backup Unit Other Equipment Printers Laser Printer OPTRA LX+ 24-Pin Dot Matrix Printer

Bar Code Equipment Intermec Bar Code Printer 4100B Intermec Media Kit Intermec Bar Code Scanner 1545E Intermec Bar Code Reader 9710E01 Surge Suppresser Software

Data Base Management Software Informix On-Line Workgroup Server 7.1 ESQL/C with I-Net

Operating System Windows NT Server 3.51 Windows NT Workstation 3.51 MS-DOS 6.22 Windows for Workgroups 3.11 (As Rqd)

Utilities Bar Tender Bar Code Label Software ViewPoint Pro (SA Workstation Only) Crystal Reports Report Generator (As Rqd)

1

HSMS System Technical Architecture Guide

Appendix C - Site Visit Checklist

• • •

•

• • •

Complete Functional/Technical Questionnaires (1 Week After Initial Site Visit). Charter and Form HSMS Implementation Workgroup. Collect and provide to HSMS Functional Analysts: • Hazardous Material Management Plan • Hazardous Waste Management Plan • Pollution Prevention Plan • Installation Environmental Regulations or Supplements • EPCRA Reports (as required) • Tier II Reports (as required) • Installation Master Plan • Other Documentation (as required) Define IOC Operational Concept and Business Practice Model. • Identify and document hazardous material management industrial processes and flow. • Identify IOC Users and Facilities. • Determine locations and number of hazardous material issue points. • Determine hazardous waste collection and storage points. Appoint/Procure HSMS System Administrator/Data Base Administrator. Provide information on availability of a computer lab to conduct functional user training including number and type of workstations, other hardware, and software (operating system and data base management system). Identify issues and concerns.

1