Bill of Materials (BOM) for
FEMIS v1.4.7

March 3, 2000


Contents

1.0 Introduction
    1.1 Point of Contact
    1.2 FEMIS Changes at a Glance
    1.3 Further Software and Hardware Information
2.0 Hardware Requirements
    2.1 UNIX Server
    2.2 PC Client Workstation
    2.3 Stand-Alone FEMIS PC Workstation
    2.4 Remote Evacuee Registration Hardware
    2.5 Other Supporting Hardware
3.0 Software Requirements
   3.1 Server Software
   3.2 PC Client Software
   3.3 Stand-Alone FEMIS PC Software
   3.4 Remote Evacuee Registration Software
   3.5 E-mail Standards
   3.6 COTS on CD
4.0 Telecommunications
   4.1 Remote Access Servers
5.0 Computer Networks

1.0 Introduction

This document describes the hardware and software required for the Federal Emergency Management Information System version 1.4.7 (FEMISİ v1.4.7)(a) released by Pacific Northwest National Laboratory (PNNL)(b). Information included in this document about hardware and software requirements is subject to change.

FEMIS is designed for a single Chemical Stockpile Emergency Preparedness Program (CSEPP) site that has multiple Emergency Operations Centers (EOCs). Each EOC has personal computers (PCs) that emergency planners and operations personnel use to do their jobs. These PCs are connected via a local area network (LAN) to servers that provide EOC-wide services. Each EOC is interconnected to other EOCs via a wide area network (WAN).

A UNIX server provides a platform to support the Oracle relational database management system (RDBMS), ARC/INFO geographic information system (GIS) capabilities (optional), basic file management services, the evacuation model (ESIM), the data exchange interface (DEI), and the notification service.

FEMIS is a client/server system where much of the application software is located on the client PC. This client software includes the FEMIS application, government furnished dispersion model, and Commercial-Off-The-Shelf (COTS) software applications, including the ArcView GIS and Microsoft Project (electronic planning).

Several configurations are possible at a CSEPP site. In this document, a site is understood to include several installations of FEMIS, including the depot, surrounding Immediate Response Zone (IRZ) and Protective Action Zone (PAZ) counties, and one or more state EOCs. In general, the main differences between possible configurations are the numbers of PC workstations at an installation, the location of the UNIX server(s), and the WAN links between installations.

FEMIS v1.4.7 can also be operated on an isolated PC workstation and is then referred to as "stand-alone" FEMIS. If a stand-alone installation is desired, please contact Ranata Johnson, (see Section 1.1, Point of Contact) for updated information before purchasing additional software.

FEMIS v1.4.7 also includes a remote evacuee registration capability. This dial-in tool will allow shelters to register evacuees at the shelter location and do a batch update of the information to the FEMIS database. Additional hardware and software required for this capability are described in each section of this document.

The remainder of this section lists PNNL's Point of Contact for this document, software applications and version changes for FEMIS v1.4.7, and a reference section for software and hardware that can be used with FEMIS.

Section 2.0 discusses hardware requirements, including UNIX servers, PC client workstations, stand-alone PC workstations, Remote Evacuee Registration (RER) hardware, and other supporting hardware.

In Section 3.0, the software requirements for the server, PC client, stand-alone FEMIS PC, and RER are described. This section also includes a discussion regarding electronic mail (E-mail) standards and the COTS CD that is available from PNNL.

Section 4.0 discusses telecommunications.

Section 5.0 discusses computer networks.

1.1 Point of Contract

If you have questions or need additional copies of this document, please contact

Ranata L. Johnson
Pacific Northwest National Laboratory
PO Box 999 MSIN K7-28
Richland, WA 99352
Phone: (509) 375-6311 FAX: (509) 375-3641
E-mail: ranata.johnson@pnl.gov

1.2 FEMIS Changes at a Glance

The following table lists software applications and versions that have changed for FEMIS v1.4.7.

COTS Software
 Server Software FEMIS v1.4.6 FEMIS v1.4.7
Oracle v7.3.4 Release v8.1.6
NFS Maestro
or
SUNWpcnfd
or
Samba
v6.1
 
v1.2
 
N/A
v6.2
 
v1.2 (no change)
 
v2.0.6
 PC Client Software
Oracle v2.3.4 Net8 Client v8.1.5 (replaces SQL*Net and TCP/IP Adapter)
NFS Maestro v6.1 v6.2 and
Patch v6.2.0.2
ArcView GIS v3.0a v3.1.1

1.3 Further Software and Hardware Information

The following table lists references for software and hardware that can be used with FEMIS.

Required Software

Software Application Software Company Web Site Address
ArcView GIS ESRI (Environmental Systems Research Institute, Inc.) www.esri.com
NFS Maestro
or
Solstice NFS Client
(SUNWpcnfd)
or
Samba
Hummingbird Communications Ltd.
 
Sun Microsystems, Inc.
 
 
Samba Team (open source project)
www.hummingbird.com
 
www.sun.com
 
 
www.samba.org
Microsoft Project Microsoft Corporation www.microsoft.com
Microsoft Windows NT Microsoft Corporation www.microsoft.com
Oracle Oracle Corporation www.oracle.com
Oracle Net8 Client Oracle Corporation www.oracle.com
Solaris Sun Microsystems, Inc. www.sun.com

Optional Software

Software Application Software Company Web Site Address
ARC/INFO ESRI www.esri.com
Microsoft Office Microsoft Corporation www.microsoft.com

Telecommunications Hardware Suppliers

Hardware Supplier Web Site Address
3Com www.3com.com
3Com US Robotics www.3com.com/carrier/nsd/products/rapd/30403.html
Cabletron Systems www.cabletron.com
Cisco www.cisco.com
MultiTech Systems www.multitech.com
Nortel Networks www.nortelworks.com

2.0 Hardware Requirements

To successfully run FEMIS, the following UNIX server and PC client workstation hardware must be present.

2.1 UNIX Server

Each EOC requires access to a UNIX data server. This server can be either physically present in the EOC or remotely accessed across a WAN link.

In previous versions of the Bill of Materials (BOM), PNNL listed the Sun SPARCserver 1000e, Sun SPARCstation 20 Model 612, and Sun Ultra Enterprise 2 as the three UNIX server options for your CSEPP site. The Sun SPARCserver 1000e and Sun SPARCstation 20 Model 612 servers are no longer available. The Sun Ultra Enterprise 2 is available but is no longer the recommended migration path. For FEMIS v1.4.7, the recommended migration path for these servers is to the Sun Enterprise 450, Sun Enterprise 250, or their associated rack variants.

Because several sites have purchased the SPARCserver 1000e, SPARCstation 20 Model 612, or Sun Ultra Enterprise 2, we have retained Sections 2.1.1 through 2.1.3 to be used as references.

2.1.1 Sun SPARCserver 1000e (for Installations with More Than 15 Users)

Note: The Sun SPARCserver 1000e is no longer available. See Section 2.1.4 for a comparable system that is currently available from Sun.

To ensure an appropriate level of performance, PNNL recommends that the SPARCserver contain multiple central processing units (CPUs).

The SPARCserver 1000e requires Year 2000 (Y2K) enhancements to be compliant. The SPARCserver 1000e requires PROM Version 3.1a or later. If you have a maintenance contract with Sun, call 1-800-USA-4-SUN to order new PROM kits. Per Sun's web site, the part number is 560-1962-07.

The SPARCstorage Array is Y2K compliant.

The following UNIX server configuration will meet FEMIS needs.

Sun SPARCserver 1000e Notes
System Board
2 SPARCserver 1000e system boards with 2 SuperSPARC processors each, no memory
Includes a 14GB 8mm tape drive, cable, and terminator.
Main memory
384MB (4x96)

Standard interfaces
2 10BaseT via twisted-pair
One interface per system board.
Internal disk
2 internal disks (2.1GB formatted)
 
Internal mass storage
1 14GB 8mm tape drive
1 Sun CD drive
 
External mass storage
1 35.7GB SPARCstorage Array Model 112 (no longer available)
1 SBus card
1 fiber cable
Disk storage capacity requirements are a function of the size of the installation database and the number of EOCs supported by the data server. 15x2.01GB will provide ~18GB RAID (Redundant Array of Inexpensive Disks) capacity.
External backup drive
1 16-32GB 4mm DDS-2 Autoloader
1 cable
1 terminator

Console
1 20-in. color monitor with Turbo GX frame buffer
1 cable

2.1.2 Sun Microsystems SPARCStation 20, Model 612 (for Installations with 15 or Fewer Users)

Note: The Sun SPARCstation 20 is no longer available. See Section 2.1.4 for a comparable system that is currently available from Sun.

A lower cost alternative to the SPARCserver 1000e that is adequate to support EOCs with smaller numbers of clients is the SPARCstation 20 Model 612. To ensure an appropriate level of performance, PNNL recommends that this server contain multiple CPUs.

The SPARCstation 20 and the SPARCstorage Array are Y2K compliant.

The following UNIX server configuration will meet FEMIS needs.

SPARCstation 20 Model 612 Notes
System Board
A standard configuration includes 2 SuperSPARC processors
 
Main Memory
192MB (2x96)
 
Standard interfaces
1 10BaseT via twisted-pair
 
Internal disk
1 internal disk (2.1GB formatted)
 
Internal mass storage
1 Sun CD drive
 
External mass storage
1 35.7GB SPARCstorage Array Model 112
1 Sbus card
1 fiber cable
Disk storage capacity requirements are a function of the size of the installation database and the number of EOCs supported by the data server. 15x2.01GB will provide ~18GB RAID capacity.
External backup drive
1 14GB 8mm tape drive
1 16-32GB 4mm DDS-2 Autoloader
1 cable
1 terminator
 
Console
1 20-in. color monitor with Turbo GX frame buffer
1 cable
 

2.1.3 Sun Ultra Enterprise 2

The Sun Ultra Enterprise 2 is available but is no longer the recommended migration path. The configuration for the Sun Ultra Enterprise 2 is listed below.

The Sun Ultra Enterprise 2 and the Sun StorEdge MultiPack are Y2K compliant.

The following UNIX server configuration will meet FEMIS needs.

Sun Ultra Enterprise 2 Notes
Processor
2 UltraSPARC processors
 
CPU modules
2 CPU modules
 
Main memory
256MB (2x128) per CPU
 
Standard interfaces
1 FastEthernet (100BaseT)/10BaseT via twisted-pair
4 SBus expansion slots
 
Internal disk
2 internal disks (3.5-in. x 1-in. disks) (2.1GB formatted)
Optional
1 3.5-in. floppy drive
 
Internal mass storage
1 Sun CD drive
 
External mass storage
1 54.6GB Sun StorEdge MultiPack with 10,000 rpm disk drive (7200rpm disk drive is no longer available)
1 cable kits
Disk storage capacity requirements are a function of the size of the installation database and the number of EOCs supported by the data server. The MultiPack 6x9.1GB will provide ~27GB RAID capacity.

Note: To obtain your RAID configuration, use Sun's Disksuite v4.2 software.

External backup drive
1 14GB 8mm tape drive
1 cable
1 terminator
1 72-144GB 4mm Sun StorEdge FlexiPack DDS-3 Autoloader
1 cable kit
1 fast/wide SCSI adapter
 
Console
1 20-in. color monitor with Turbo GX frame buffer
1 cable
 

2.1.4 Sun Enterprise 250

A migration path from the SPARCstation 20 model 612 and the Enterprise 2 is to the Sun Enterprise 250. The configuration for the Sun Enterprise 250 is listed below.

The Sun Enterprise 250 is Y2K compliant.

The following UNIX server configuration will meet FEMIS needs.

Sun Enterprise 250 Notes
Processor
Large EOC -- 2 UltraSPARC II processors
Small EOC -- 1 UltraSPARC II processor
Two processors can be used in either large or small EOC's for redundancy purposes (recommend 512MB minimum memory for two processors).
Main memory
Large EOC -- 512MB
Small EOC -- 256MB (512MB if dual processors)
Recommend larger memory amounts (512MB to 1.0GB) for systems utilizing more than two processors. These are the minimum values.
Standard interfaces
1 Integral 10/100 Ethernet
2 separate PCI buses supporting 4 slots
3 PCI slots for 32/64 bit 33MHz 5v cards
1 PCI slot for 32/64 bit 33- or 66-MHz 3.3v cards
2 EIA232D/423 serial ports
2 MB/sec Centronics compatible EPP (parallel) port, DB25
1 40MB/sec Ultra SCSI-3 bus for internal disk
1 40-MB/sec fast/wide SCSI-3 bus for external disk
For more details, see Sun's web site (http://www.sun.com/servers/workgroup/250).
Internal mass storage
1 9.1GB disk drive for operating system
5 9.1GB or 18.2GB disk drives for data
1 additional power supply for redundancy
1 32X CD-ROM drive
1 8mm internal tape drive
1 3.5-in. floppy drive

Optional:
1 X6542A SRC/P PCI Intelligent SCSI RAID controller
Note: Hardware Specification Change -- Sun no longer offers this part in its sales line.

Disk storage capacity requirements are a function of the size of the installation database and the number of EOCs supported by the data server.

5x9.1GB will provide ~26GB RAID5 capacity with 1 hot swappable drive.

5x18.2GB will provide ~55GB RAID5 capacity with 1 hot swappable drive.

Note: To obtain your RAID5 configuration, use Sun's Disksuite v4.2 (or later) software.

Note: Hardware RAID5 can now be accomplished with the addition of a SRC/P PCI Intelligent SCSI RAID controller card; however, the Disksuite software must still be used to manage the RAID configuration.

External mass storage
Optional:
Mass storage option (upgrade option for the SPARCstorage array model 112.): Sun StorEdge A1000, tabletop (12x9.1GB 10000rpm) with hardware RAID
Note: StorEdge A1000 requires an additional differential SCSI controller, Part # X6541A.

Note: The StorEdge A1000 disk array is a dual Ultra SCSI (2x40MB/sec) interface. It is not a Fibre Channel interface.

External backup device (archive)
1 72GB 4mm DDS-3 Autoloader
1 cable
1 terminator
DDS-3 Autoloader is capable of handling six 12GB 4mm tapes. Under compression, 6x24GB (144GB) may be achieved.
Console
1 19-in. color monitor, 96KHz, DDC1/2B, MPR-II, TCO'95
1 Integrated PGX graphics card
1 cable
 

2.1.5 Sun Enterprise 450

A migration path from the SPARCserver 1000e and SPARCstation 20 Model 612 is to the Sun Enterprise 450. The configuration for the Sun Enterprise 450 is listed below.

The Sun Enterprise 450 is Y2K compliant.

The following UNIX server configuration will meet FEMIS needs.

Sun Enterprise 250 Notes
Processor
Large EOC: 2 or more (maximum of 4) UltraSPARC II processors
Small EOC: 1 UltraSPARC II processor
Two processors can be used in either large or small EOCs for redundancy purposes. Recommend 512MB as the minimum memory for two processors.
Main memory
Large EOC: 512MB
Small EOC: 256MB (512MB if dual processors)
Recommend larger memory amounts (512MB to 1.0GB) for systems utilizing more than two processors. These are the minimum values.
Standard interfaces
1 Integral 10/100 Ethernet
6 separate PCI buses
3 PCI for 33 or 66MHz 3.3v cards
4 PCI 64 bit 33MHz 5v cards
2 EIA232D/423 serial ports
1 2MB/sec Centronics compatible EPP (parallel) port, DB25
1, 3, or 5 40MB/sec UltraSCSI-3 buses for internal disks (See notes on Internal mass storage)
1 20MB/sec Fast/Wide SCSI-2 bus for CD-ROM and tapes; 8 pin external connector
The PCI connections support combinations of 32/64 bit, 33/66MHz and 3.3v/5v PCI cards. For more details, see Sun's web site (http://www.sun.com/servers/workgroup/450).
Internal mass storage
1 4.2GB disk drive for operating system (no longer available); use 9.1GB disk
10 4.2GB disk drives for data (no longer available) ; use 9.1GB disk
2 8 bay internal storage expansion kit
1 additional power supply
1 32X CD drive (12X is no longer available)
1 8mm internal tape drive
1 3.5-in. floppy drive

Optional:
1 X6542A SRC/P PCI Intelligent SCSI RAID controller
Note: Hardware Specification Change -- Sun no longer offers this part in its sales line.

The internal storage expansion kit and the additional power supply are required to support the 10 data disk drives.

Disk storage capacity requirements are a function of the size of the installation database and the number of EOCs supported by the data server. 10x9.1GB will provide ~55GB RAID5 capacity with 1 hot swappable drive./P>

Note: To obtain your RAID5 configuration, use Sun's Disksuite v4.2 (or later) software./P>

Note: Hardware RAID5 can now be accomplished with the addition of an SRC/P PCI Intelligent SCSI RAID controller car; however, the Disksuite software must still be used to manage the RAID configuration.

External mass storage
Optional:
Mass storage option (upgrade option for the SPARCstorage array model 112.): Sun StorEdge A1000, tabletop (12x9.1GB 10000rpm) with hardware RAID
Note: StorEdge A1000 requires an additional differential SCSI controller, Part # X6541A.

Note: The StorEdge A1000 disk array is a dual Ultra SCSI (2x40MB/sec) interface. It is not a Fibre Channel interface.

External backup device
1 72GB 4mm DDS-3 Autoloader
1 cable
1 terminator
DDS-3 Autoloader is capable of handling six 12GB 4mm tapes. Under compression, 6x24GB (144GB) may be achieved.
Console
1 19-in. color monitor with integrated PGX graphics card
1 cable
 

2.1.6 Maintenance for Solaris Software and Sun Hardware

For Solaris software and Sun hardware, PNNL recommends that sites obtain a Silver Maintenance contract. Each hardware and software item is a line item that is a costed item. The contract should be written to cover the following items: your site's CPU, disk arrays or StorEdge MultiPack, Solstice NFS Client, and disk management software. Equipment, such as CD drive, 8mm tape drives, disks, and monitors are considered as part of the CPU.

2.1.7 Sun Y2K Validation Tools

To validate your Sun products for Y2K compliance, you can download Sun's tool set. SunScan 2000 compares existing Sun hardware, operating systems, and middleware to a list of Sun products that have been tested for Y2K compliance. The product is free. Instructions and software are available at http://www.sun.com/y2000/sunscan. Additional tools and information can be found at http://www.sun.com/y2000/ and http://www.sun.com/y2000/test-tools.html.

2.2 PC Client Workstation

The PC client platform is the Pentium-based PC. The minimal PC configuration describes the lowest level at which FEMIS has been tested and run. The recommended PC configuration describes the configuration to be considered for current procurement. The following table lists minimum and recommended PC configurations.

Minimum PC Configuration Recommended PC Configuration
Intel Pentium microprocessor PC Intel Pentium microprocessor PC
90MHz 350MHz or better
128MB RAM* 128MB RAM or better
1GB hard disk 4GB hard disk or more
Internal CD drive 8X Internal CD drive
1.44MB 3.5-in. internal floppy drive 1.44MB 3.5-in. internal floppy drive
1 parallel and 2 serial ports 1 parallel and 2 serial ports
Ethernet Adapter card or equivalent (10MBps, 10BaseT or Thinnet) Ethernet Adapter card or equivalent (10MBps or better, 10BaseT or better)
17-in. color VGA monitor (SVGA capable) 19-in. color VGA monitor (SVGA capable)
Standard 101 keyboard Standard 101 keyboard
Mouse Mouse
* FEMIS will run on PCs with 64MB of RAM, but performance will be considerably slower when running multiple applications at the same time, such as the GIS, E-mail, web browser, and other applications.

2.3 Stand-Alone FEMIS PC Workstation

The stand-alone FEMIS PC workstation is the Pentium-based PC with a configuration similar to the recommended configuration for a PC client workstation (see Section 2.2, PC Client Workstation).

2.4 Remote Evacuee Registration Hardware

The Remote Evacuee Registration (RER) tool can be installed on the minimal PC configuration (see Section 2.2, PC Client Workstation) or better. A 28.8kbps modem is also required in addition to the minimal PC configuration. For more information, see Section 4.0, Telecommunications.

2.5 Other Supporting Hardware

For FEMIS v1.4.7, PNNL recommends the following supporting hardware.

Supporting Hardware Notes
Network hardware including Nortel Networks, Cabletron, or Cisco routers.
Printer (HP LaserJet, color printer, or other LAN-compatible printer).
Screen projection hardware compatible with a PC client workstation (optional).
Uninterruptable power supply (UPS) of sufficient capacity to operate the EOC system for a length of time acceptable to installation management. Individual EOCs should calculate their power needs based on their existing and planned hardware and may elect to purchase a larger or smaller UPS accordingly.

For example, an EOC with 1 data server and 25 PC clients (including a communications server if used), might have a UPS rated between 40kVA and 50kVA.

3.0 Software Requirements

The following sections discuss the software requirements for FEMIS v1.4.7.

3.1 Server Software

The following table includes information about data server software configuration and maintenance recommendations.

Data Server Software Configuration Maintenance Contract Recommendations Notes
Sun Microsystems Solaris v2.7 See Section 2.16 For recommended patches, see our web site (http://www.pnl.gov/femis/tech/solar27.htm).
Oracle Release v8.1.6 RDBMS with SQLPlus OracleBRONZE Oracle licenses for the server are sold in sets, for example, 1, 8, 12. Purchase the number of licenses to match the number of user PCs that will connect to the server. Only one license per server is required for SQLPlus.
NFS Maestro v6.2
 
or
 
 
 
 
SUNWpcnfd v1.2
 
or
 
Samba v2.0.6
Maintenance for the server is provided with the standard PC maintenance available from the vendor.
 
 
 
 
 
See Section 2.16
 
 
 
Not applicable-public domain, see www.samba.org (Samba Team).
The NFS Maestro daemon hclnfsd process should be running on the FEMIS UNIX server. The source code for hclnfsd is public domain and is distributed with the client product. After the installation of NFS Maestro on the PC, the source files can be found in the utility subdirectory under the directory it where it was installed.
 
Distributed on the Solaris Server Intranet Extension 1.0.
 
 
 
Samba is open source software distributed under the GNU General Public License, Version 2, June 1991.
E-mail application Application dependent Any E-mail application meeting the requirements in Section 3.5, E-mail Standards.
FEMIS Server Application Set Evacuation SIMulation Model, ESIM v2.1f1.3 Not applicable Distributed with FEMIS.
Perl v5.004-04 Not applicable--public domain, see www.perl.org (Larry Wall, author). Distributed with FEMIS and needed to run AutoRecovery and Data Driven Notification.
Apache HTTP Web Server v1.3.12 Not applicable--public domain, see www.apache.org (Apache Group). Distributed with FEMIS and needed to run the AutoRecovery WEB interface.
Network time synchronization protocol v3.4y (Sun v11.7.0) See Section 2.16 Network Time Protocol is distributed with Solaris v2.7 or higher operating systems.
ARC/INFO v7.1.2 or later (optional) Optional Optional

For information about downloading SunScan 2000 (Sun's Y2K compliance tool set), see Section 2.1.6, Sun Year 2000 Validation Tools and Sun's web site (http://www.sun.com/y2000).

3.2 PC Client Software

The following table includes information about PC client software configuration and maintenance recommendations.

PC Client Software Configuration Maintenance Contract Recommendations Notes
Microsoft Windows NT Workstation v4.0 (CD edition) Maintenance contract may be available from PC vendor. The version specified includes documentation. Additional licenses may be obtained without documentation by procuring the Windows NT Workstation License Pack.
Microsoft Windows NT Workstation v4.0 Service Pack 5 N/A The Service Pack addresses security issues for Windows NT v5.0 and can be downloaded from Microsoft's web site (http://support.microsoft.com/support).
Oracle Net8 Client v8.1.5 Maintenance is included as part of the server software maintenance contract. Oracle Net8 Client v8.1.5 is included with the Oracle server license and replaces SQL*Net and TCP/IP Adapter.
ArcView GIS v3.1.1 No additional maintenance contract is available from vendor.
NFS Maestro v6.2
Patch v6.2.0.2
or
 
 
Solstice NFS Client v3.2
Standard maintenance contract by vendor is based on the number of seats (licenses) your site has purchased.
 
 
 
See Section 2.16
Purchase the number of licenses (seats) to match the number of user PCs.

A patch is required for upgrade from v6.2 to v6.2.0.2.

Solstice NFS Client licenses for the PC are sold in sets, for example, 1, 5, 10, or 25. Purchase the number of licenses to match the number of PCs. If purchasing more than one license, you should also purchase one base pack that provides software and documentation.

Microsoft Project 98 and Service Release 1 No additional maintenance contract is available from vendor. Project is not needed for operations. Project is needed for generating/modifying plans in Planning mode.
FEMIS Client Application Set Not applicable The Dispersion Model (D2PC [December 1999]) and the Dose/ Time Model (PARDOS [May 1997]) are part of the FEMIS Client Application Set.
Network time synchronization protocol xntp3 5.90.3 Not applicable-public domain Configured as part of the FEMIS installation.
Network Monitor for Windows vA17 95.03.11 Not applicable--public domain Included in the FEMIS Tools as WS Network Monitor
Oracle ODBC Driver v8.1.5.5 Maintenance is included as part of the server software maintenance contract. The Oracle drivers are available at no cost. In FEMIS v1.4.7, the drivers will be installed as part of the Oracle installation.
E-mail Application Application dependent Any E-mail application meeting the requirements in Section 3.5, E-mail Standards.
Microsoft Office (optional) No additional maintenance contract is available from vendor. Includes Microsoft Excel, PowerPoint, and Word.
Word processor (optional) Application dependent Corel WordPerfect or Microsoft Word

3.3 Stand-Alone FEMIS PC Software

A PC may be configured to run FEMIS as a stand-alone PC. In this configuration, there is no connection to the server database, and no information is exchanged with any other user. The FEMIS application and the Oracle databases are installed on the stand-alone PC. A network connection is only required during the setup when FEMIS files are loaded on the stand-alone PC. Once the setup is complete, the network may be disconnected.

The software required for a stand-alone PC is the same as that listed in Section 3.2, PC Client Software, with the exception of an Oracle product-either Oracle Workgroup Server v8.1.5, which is the RDBMS, or Personal Oracle v8.1.5. Oracle Workgroup Server contains more capability (and is consequently more expensive) than FEMIS requires. If you are purchasing either product, please contact us for the latest information (see Section 1.1, Point of Contact).

Stand-Alone PC Client Software FEMIS v1.4.6 FEMIS v1.4.7
Oracle Workgroup Server
or
Personal Oracle
v7.3.4

 v7.3.4
Oracle Net8 Client v8.1.5 for Microsoft Windows NT
or
Personal Net8 Client v8.1.5

3.4 Remote Evacuee Registration Software

The Remote Evacuee Registration (RER) tool uses all of the software products listed in Section 3.2, PC Client Software, except ArcView GIS, Microsoft Project 98, network time synchronization, and an E-mail application. The following table lists the software for the PC Client and how the RER tool uses it.

Remote Evacuee Registration Software Notes
Microsoft Windows NT Workstation v4.0 (CD edition) The FEMIS RER software runs on a Windows NT environment.
Microsoft Windows NT Workstation v4.0 Service Pack 5 The Service Pack addresses security issues for Windows NT v4.0.
Oracle Net8 Client v8.1.5 The RER attaches to the FEMIS database for a short period of time to download and upload information to support evacuee registration.
NFS Maestro v6.2 and Patch v6.2.0.2
or
Solstice NFS Client v3.2
NFS may be needed to do the initial installation of FEMIS and RER.
FEMIS Client Application Set The FEMIS Client Application Set must be installed to ensure that all of the supporting software is loaded onto the PC. The GIS files do not need to be installed.
Oracle ODBC Driver v8.1.5.5 The Oracle drivers are used to connect to the FEMIS database during download and upload of evacuee information. They are also used during the offline entry of evacuee and tracked person information.

The FEMIS RER tool also requires a PPP (Point to Point Protocol) link, such as the Remote Access Services (RAS) components of Windows NT v4.0. RAS has to be turned on for the PC using RER.

Additionally this tool requires a server software package, such as Solstice PPP to be installed on the FEMIS UNIX server. For more information on the UNIX configuration, see Section 4.0, Telecommunications.

3.5 E-mail Standards

Electronic communication and the exchange of electronic documents for collaborative purposes is an increasingly critical form of communication. In the past, GroupWise v4.1 (a Novell, Inc. product) was the recommended E-mail application for FEMIS. For FEMIS v1.4.7, PNNL does not recommend a specific E-mail application; however an E-mail package is still required.

The E-mail application your site chooses should meet specific standards listed below, which are separated into two categories-required and strongly recommended. An existing system and future trends are also discussed.

3.5.1 Required

ESMTP/SMTP (Extended Simple Mail Transfer Protocol) is capable of sending E-mail messages between multi-user servers.

3.5.2 Strongly Recommended

MIME (Multipurpose Internet Mail Extensions) compatible. MIME is a specification for formatting non-ASCII messages such as graphics, audio, and video so they can be sent over the Internet. In addition, MIME supports messages in character sets other than ASCII.

IMAP4 (Internet Message Access Protocol, version 4) retrieves E-mail messages. IMAP4 is similar to POP3 (Post Office Protocol, version 3) but includes the following additional features:

UUENCODE (Unix-to-Unix encode) is a set of algorithms that converts files into 7-bit ASCII characters suitable for transmitting over the Internet. UUENCODE is used to transfer files between different platforms such as UNIX, Windows, and Macintosh and is very popular for sending E-mail attachments.

LDAP (Lightweight Directory Access Protocol) is a set of protocols for accessing information directories. LDAP is based on the standards contained within the X.500 standard but is significantly simpler. LDAP supports TCP/IP, which is necessary for any type of Internet access. Because it is an open protocol, applications need not worry about the type of server hosting the directory.

3.5.3 Existing System

Several EOCs are using POP3, which allows a workstation to retrieve E-mail that the server is holding for it. Once the E-mail is downloaded, it is deleted from the server.

3.6 COTS on CD

Through an agreement with the COTS providers, PNNL has created a CD with a copy of the appropriate version of the PC client COTS software. The COTS CD allows users to install the COTS software prior to their initial FEMIS installation, and it is available from PNNL. The COTS CD will make the installation of these applications easier. The COTS software can be installed directly on a PC or copied to the server and then installed on each PC from the server.

Before PNNL can ship you a CD, we must have proof of purchase of at least one license for each of the COTS on the CD. The proof of purchase can be a photocopy of each license and must accompany your request for the COTS CD. To request the COTS CD, contact Ranata Johnson (see Section 1.1, Point of Contact).

Note: This agreement does not exempt the site from the responsibility of purchasing the required number of licenses, but it does ensure that the site has the correct versions of COTS software for FEMIS. All versions of the COTS for FEMIS v1.4.7 are available for purchase from vendors.

For FEMIS v1.4.7, the following COTS applications are included on the FEMIS COTS CD:

Note: If you are running an earlier version of FEMIS, do not install the COTS from this CD until your site is ready for the FEMIS v1.4.7 upgrade.

The Oracle PC components needed for the stand-alone PC configuration are not on the FEMIS COTS CD.

4.0 Telecommunications

FEMIS can be used remotely via telecommunication access using commercial telephone lines suitable for modem data transmission. The acceptability of remote access is dependent upon the capacity of the connection and the FEMIS functions being utilized. Ideally, these lines should be 28.8kbps or better. Leased lines with a minimum capacity of 56kbps are preferred for remote login to FEMIS, including shelters and the Joint Information Center (JIC). A 28.8kbps service will provide adequate connectivity if only the Remote Evacuee Registration (RER) tool is used.

A PC dialing in to an EOC via Windows NT Remote Access Service (RAS) and Point to Point Protocol (PPP), a standard Internet protocol, can utilize the full capabilities of FEMIS. Using FEMIS in this configuration will obviously not provide response speeds as fast as when higher data transmission speeds provided by a WAN or LAN are available, and one such connection should never be used for more than a single remote PC.

Options available to establish this communication are discussed below.

4.1 Remote Access Servers

To enable remote dial-in at EOC LANs, sites need a network remote access server capable of PPP operation via V.34 compliant modem of at least 28.8kbps. Popular networking/communication equipment vendors (such as Nortel Networks, Cabletron, and Cisco) can supply the hardware to implement PPP remote dial-in connections. For example, the Cisco 2509 is one model of a remote access server with dial-in access (for more details, see http://www.cisco.com/warp/public/cc/cisco/mkt/access).

Additional dial-up options can also be utilized that are more software based. These include, but are not limited to, Microsoft's NT RAS server option (for NT platforms) or Sun's PPP dial-up software, which is currently bundled with the operating system. Sun also sells an unbundled product called Solstice PPP which offers everything that the bundled operating system software does in addition to more complex scripting, better authentication methods, and synchronous date connectivity.

5.0 Computer Networks

Computer networks used for FEMIS data communication and database administration should be modern computer networks which utilize router equipment that conforms to current industry standards.

FEMIS will perform best when the inter-EOC links are based on T-1 or better communication. Local networks in the EOCs should be based on a 10MB or higher data communication rate.

Under certain situations, where low performance is acceptable, lower data transmission rates can be utilized with the expected longer delay in response of many FEMIS functions.

Better performance can be realized on switched LANS rather than hub-based LANS.


Footnotes:

(a)FEMIS software was copyrighted in 1995 by Battelle.

(b)Pacific Northwest National Laboratory is operated for the U.S. Department of Energy by Battelle under Contract DE-AC06-76RLO 1830.


Acknowledgment and Disclaimer | Acronyms and Definitions | Authors


Last modified: 08/30/2000
Security & Privacy
Pagemaster: Sharon Johnson