Automated Fuel Systems[1].doc

Maine Department of Transportation

Bid Proposal

For

Maine Department of Transportation

Automated Fuel Management System

SPECIFICATION PURPOSE & INTENT - GENERAL

The attached Specifications require providing all things necessary, or proper for, or incidental to the furnishing and delivery of the bid item (or items) and associated equipment to Fleet Service/MaineD.O.T., Augusta. The aforementioned bid item shall be of heavy-duty design and construction for extreme service or application. All things not expressly mentioned in these Specifications, but involved in carrying out their intent, are required by these Specifications and the vendor shall perform the same as though they were specifically mentioned, described and delineated.

The bid item (or items) and all associated equipment shall be furnished complete and in readiness for use as required by the terms of these Specifications and in strict accordance therewith. The bid item (or items) and all equipment furnished shall be the manufacturer's current or 2007 listed and published stock model, or models which meet or exceed all the applicable requirements of these Specifications. All design, materials and workmanship shall in every respect be in accordance with the best current practices in the industry and all materials used shall be new.

The bid item or items shall be in full compliance with any and all Federal and State of Maine, rules, regulations or codes. Any and all bid or accessory items furnished by the vendor, distributor and/or manufacturer shall be installed in accordance with the highest standards of the industry, full compliance of all applicable Federal and State of Maine rules, regulations or codes and must be completely inspected and serviced prior to delivery.

Fleet Service/MaineD.O.T. reserves the right to expect replacement of any item, component or associated equipment from the vendor, distributor or manufacturer, at no cost to Fleet Service for failure to perform. Fleet Service also reserves the right to require training for operation or maintenance and repair where necessary at no additional cost.

All Warranties and Guarantees are to become effective the date the State of Maine places the bid item (or items) into service.

Since the continuous operation of the bid item (or items) as specified is of the utmost importance and sometimes of an emergency nature, it is necessary that the successful bidder be in a position to render prompt parts and if necessary, service. The successful bidder and subcontractor (if any) must maintain and/or have access to parts inventory within the State of Maine. The parts inventory shall be applicable to the bid item (or items) supplied to the State of Maine and must be of sufficient quantity and variety to offer a level of parts availability of 95% within 48 hours from time of order by MaineD.O.T. Upon award of bid and before delivery of bid item (or items) MaineD.O.T must receive a complete list of parts containing part description, manufacturer's part number etc. for the entire item or items including any or all accessories which are supplied as part of the bid. This does not relieve the bidder from supplying parts manuals or repair manuals as required in the individual specification. The manufacturer’s manual must be supplied at time of bid.

During the term of the manufacturer's warranty Fleet Service reserves the right to perform any and all warranty work "in house" to meet operational needs or demands. Fleet Service will recover all parts and labor cost (labor time as allowed by manufacturer's rate manual Fleet Service standard labor rate at the time of repair) by billing the manufacturer and/or dealer. O.E.M. parts may be supplied at no cost by the manufacturer or dealer and will not be billed by Fleet Service, or may be purchased by Fleet Service on the open market to meet operational demands. Any and all defective parts will be returned to the manufacturer or dealer upon request. Additionally Fleet Service will perform no other paper work other than what is necessary for Fleet Service to track the cost of warranty repair through its own billing system. Manufacturers, dealers or vendors who are selected to any equipment, vehicles or accessories to Fleet Service, must place Fleet Service on a mailing list to provide warranty recalls and/or technical updates or service bulletins to the Fleet Manager’s Office of Fleet Service, 105 Capitol St., Station #26, Augusta, Maine 04333.

Either before or after final acceptance any vehicle or equipment which does not meet these requirements may be rejected in whole or returned for correction at no cost.

Specifications

For Automated Fuel Management System General Description

Furnish an automated fuel management system that will control and record the dispensing of fuel. The system shall provide accurate and real time data while accounting for all the fuel and related products being dispensed. It shall be a stand alone, user oriented, fully automated system able to operate completely unattended 24 hours a day 7 days a week. Access to products shall be restricted to operators and equipment through but not limited to magnetic striped cards, with key pad inputs that will perform a predetermined series of data entry operations. In addition, there shall be provision to enter or retrieve data manually, any and all data that the system is designed to receive, track, or transmit. System shall be of modular design, and incorporating built-in system diagnostics. Must have remote monitoring software that shows real time dispenser status. Must support an unlimited number of employees and units. Must have real time integration with the Maximus Fleet Focus M5 Fleet Maintenance Software.

Item #1 Island Control Unit

The control unit shall be the main access point through which the user will obtain fuel. It will be mounted on the island and shall control the operation of the fuel dispensers. The control unit shall have the following capabilities.

1.1 The control unit shall be operable in temperatures from -40 to 140 degrees Fahrenheit.

1.2 Control unit will work on 110 to 120 AC voltage and will be UL approved and conform to the NEC # 70-2022 and UL1238 specifications and be labeled as so.

1.3 The control unit shall have the capability of controlling a minimum of one pump and a maximum of eight pumps.

1.4 The control unit shall have the ability of handling a minimum of two (2) and a maximum of sixteen (16) hoses and products.

1.5 The control unit will have the capability of reading the product being dispensed down to 1/ 100th of a gallon from each dispenser.

1.6 Will have the ability to enable or disable a pump via the control unit.

1.7 Will contain manual override for each pump in case of a system failure.

1.8 The control unit will incorporate a numbered keypad through which data such as unit ID, odometer reading, employee number, and pump selection can be entered.

1.9 The keypad will be designed for commercial fuel management system and have life expectance of five (5) to eight (8) years.

1.10 The control unit shall contain a sunlight readable display such as LCD (LED will not be acceptable.) This display will be use to inform the user of all information. It must be a minimum of thirty two (32) character alphanumeric display with all messages presented in English.

1.11 Control unit shall be capable of reading cards with Track 1, Track 2, and Track 3 the following data at minimum: location, unit ID, department ID, transaction limit, (measured in gallons) product type, and employee ID.

1.12 The magnetic card reader shall be rated at a minimum of 1,000,000 read cycles.

1.13 In case of communication failure the control unit will be capable of storing a minimum 100,000 transactions.

1.14 Shall have the capability of displaying messages to individual units automatically when flagged for maintenance or PM scheduling.

1.15 Must have the ability to communicate using network connections such as Phone lines, Data Links, Fiber Optics, or Wireless.

1.16 The wireless interface shall be at a minimum 802.11 B /G compliant.

1.17 The wireless system shall be capable of 802.1X authentication using active directory withWEP,WPA1,WPA2 and / or AES encryption.

1.18 Control unit must be able to communicate in real time with the host software at the beginning and end of every transaction. Communications shall include card validation; location, unit ID, department ID, transaction Limit, (measured in gallons) product type, hose used, date, time and employee ID.

1.19 Control unit shall be capable of preloading the validation information to local memory so in the event that communications to the host are down, the island control units will still be operable.

1.20 All Island Control Units shall be of modular design for ease of maintenance and repair.

Item # 2 Fuel Management Software Specifications

The Fuel Management Software (FMS) shall be menu driven and almost entirely automated. It shall direct the operator through the few daily functions. The FMS shall manage all of the database functions of the system, including the storing of transaction, inventory, and key information. All files both data and control shall be easily edited through the program. All software and hardware is subject to all applicable MaineD.O.T and State IT standards; See appendix A at the end of the specifications.

2.1 Must have the ability to support and communicate to an unlimited number of sites in real time.

2.2 Have the capability to sort and manage incoming and out going the data from 100 different departments and 50,000 vehicles.

2.3 Be able to sort the daily transaction listing by date and time, key number, vehicle number, employee number, or personnel data.

2.4 Must have the capable to change, enter, create, or eliminate information pertaining to a card, user, or unit remotely.

2.5 Have the ability to lock out a pump or a complete Island Control Unit remotely.

2.6 Capable of pump time out feature from 0 to 180 seconds, which will remove power from the pump. This can not be activated by the user.

2.7 Capable of allowing different levels of program and access through user permissions.

2.8 Must have the ability to make software modifications or updates for a single unit or multiple units simultaneously over the network from a central controller location in real time.

2.9 Will have the ability to generate reports for each Island Control Unit showing the number of transactions, pump and tank inventory, error messages, and system parameters.

2.10 Generate a daily report showing all the transactions.

2.11 Be able to generate reports for each department’s daily fueling record, to include total of fuel used, and each type of fuel for each department.

2.12 The ability to generate reports on each individual unit’s fuel history with the capability to compile estimated miles per gallon of fuel on said unit.

2.13 Set prices by tank and pump and assign to the quantity of fuel dispensed.

2.14 There shall be a method of receiving and displaying preventive maintenance text messages through the Island Control Unit from Maximus fleet focus 5 based on the unit number passed.

2.15 All informational reports must be printable in RTF (Rich Text Format), HTML, or TEXT and stored in Excel, Word, or PDF format.

2.16 Must be able to automatically retain and reset all system parameters / configurations settings upon resumption of power after a power failure.

2.17 A “missing pulse detector” will be incorporated into the circuit controlling each pump. This detector will remove power from the pump if the pulses indicating fuel floe are not received at regular intervals. The time out must be variable from 1 to 180 seconds in increments of 1 second.

2.18 Must be capable of retaining and modifying site description for each Island Control Unit. The following information must be retained; site address, number of islands, number of pumps per island, and product dispensed from each hose.

2.19 The fuel management software must be able to interface with Maximus Fleet Focus M5 software to create internal product issue transactions. There are two equally acceptable alternatives for achieving this requirement:

2.19.1.1 The fuel management software may be natively integrated with Maximus FleetFocus M5 software’s product management software.

2.19.1.2 The fuel management software may meet the following set of requirements to ensure it can create and deliver a complete file of fuel issue transactions to our current Maximus FleetFocus M5 system’s internal fuel issue interface on demand or batch schedule.

2.19.2 All Fuel Issues will be reported in XML with the fields set forth below.

2.19.2.1 The fuel issue file can reside on a location available to the State network for read or copy.

2.19.2.2 Fuel issue files can be recreated from the fuel management software.

2.19.2.3 The fuel issue file can either be accumulated as a log in real time, or populated by a scheduled batch job, as long as the complete record of fuel issues since the last interface run can be made available in the file format without routine programmer or user intervention.

2.19.2.4 The Fuel Management System must be able to store and pass the FleetFocus-assigned hose and pump identification numbers to FleetFocus.

2.20 If software will not interface directly to Maximus Fleet Focus M5 Fleet Maintenance Software, it must meet these specifications set forth below.

2.21 The path name will be specified in the interface parameters for this file.

2.22 The interface will set to run on a scheduled interval, or can be run on an as needed basis.

2.23 When the interface runs, it will look for the appropriate file, append a date/time stamp to the file name, and move it to an ‘out’ directory.

2.24 Once the interface processes, records will either populate into the appropriate fuel transactions table, or populate into a rejected fuel issues table for follow up processing through the application.

2.25 Prior experience with Maximus software systems would be a plus.

PRICE COMES FROM THE VALUE AT THE TANK WHEN THE INTERFACE IS RUN

Item #3 Fueling Procedure

The following is a general sequence of actions that will occur during each fueling transaction.

3.1 The user inserts magnetic strip card into magnetic strip insertion card reader at the Island Control Unit. At that point card validation must take place through our software system.

3.2 The user will be prompted to enter an employee number using the key pad.

3.3 The user will be prompted to enter other data such as miles, or hours or a code number etc. (These selection must be available for use but are not necessarily intended for initial use.)

3.4 The user then will be show which pumps are available for use and be told to make a selection.

3.5 The system will inform the user to start pumping.

Item # 4 Warranty and Maintenance

4.1 The vendor will warranty the system to free from defects during the warranty period of at least one (1) year. The vendor will assume sole responsibility for the performance of all equipment, materials, labor, software and programs supplied during this period. The vendor must certify that an engineer or electronics technician trained in the operation and repair of the system is employed by the vendor for warranty work during this period.

4.2 Warranty period and maintenance cost, terms and conditions (that apply after the warranty period) must be stated by the vendor and accompany the bid proposal.

4.3 Software support shall be provided through the vendor. Assistance response to emergency calls shall be within eight hours and the number of calls shall be unlimited during the warranty period.

Item #5 Training

5.1 The vendor will supply personnel and materials for training for a period of not less than sixteen hours (16). This training will cover installation, operation, and maintenance of island control units.

5.2 Training will also cover all facets of operation of Software System to include manuals and training guides on the complete system.

5.3 Technical documentation and user documentation shall be supplied for the software to include an entity relationship diagram or file layout diagram for the data stores.

Item # 6 Future Upgrades

6.1 The system must have the capability to upgrade and upgrades will be offered by the system supplier as they become available for a period of five (5) years.

Item # 7 Installation of Automated Fuel Management Island Control Units

General Description

The purposes and intent of this specification is to describe the installation of Island Control Systems for an automated fuel system. These island control systems will be placed in various locations through out the State of Maine. The control unit shall be the main access point through which the user will obtain fuel. It will be mounted on the island and shall control the operation of the fuel dispensers. These control units will control as few as one dispenser or as many as four dispensers. The installation of the control units will conform to all State and Federal laws. Vendor will certify any and all contractors that perform work on any and all installations during the installation process.

Installation

7.1 The units shall be installed in accordance with the manufactures instructions.

7.2 The units shall be installed in such a manner that all markings are readily observable.

7.3 The primary indicating elements must be visible from the position at which the operator of the pump stands.

7.4 The unit shall be securely bolted to the top service island.

7.5 All data wires shall be 18 gage or larger.

7.6 All AC wires shall be 14 gage or larger.

7.7 Mount pedestal to concrete slab in proximity of island light conduit. Use concrete anchors with nuts that can be removed if computer pedestal is moved. Removing the island light pole may prove helpful. Reinstallation of island illumination is required.

7.8 A 120volt 20amp dedicated circuit must be supplied from electrical panel feeding the fuel island. This circuit of three #12 THHN (gas/oil resistant), wires must be run to pedestal. One wire must be colored green for grounding purposes and one wire must be white to be used as a neutral. Existing high voltage conduits may be used if fill requirements are not exceeded. An existing green conductor of adequate size can fulfill the need for a grounding wire in the dedicated circuit.

7.9 A separate conduit (1/2” minimum) for low voltage communication wiring must be run from pedestal to all dispensers on the fuel island. Wires will be connected from the pedestal to the pulser in each dispenser. Number 14 THHN (gas/oil resistant) wires may be used or shielded cable of four 22AWG conductors.

7.10 A high voltage conduit from the pedestal will have to be connected to the dispenser junction box. Existing conduit from dispenser box to island light may be used, if fill requirements are not exceeded.

7.11 Unless otherwise informed, a dedicated conduit (3/4” minimum) must be installed from the pedestal to the building where computer links are found. Communication cables (CAT5 or fiber optics) required for card reader operation must be pulled from computer location in the building to the pedestal.

7.12 High voltage conduit from dispenser to pedestal must have at least four #12 THHN (gas/oil resistant) conductors. One of the wires shall be colored green for grounding purposes. These wires are in addition to any other circuits if existing conduit is used. Green conductor may be shared if an existing circuit has a grounding conductor from the dispenser to the pedestal.

7.13 All conduits will be rigid metal conduit. Each conduit run will be equipped with sealing fittings at all appropriate locations as though a Class I liquid is being dispensed at the fuel island. The use of flex conduits will be allowed if suitable for Class I, Division I locations. All junction boxes and fittings will be suitable for Class I, Division I locations.

7.14 If Card Reader computer link is wireless, then all appropriate antennas and cables will be run according to manufacturer’s specifications on or around the fuel island.

7.15 Pulser types will be unique to each dispenser. They will be installed according to manufacturer’s recommendations.

7.16 All work will be done in a professional manner in accordance with all applicable codes.

Item # 8 General

8.1 MaineD.O.T. reserves the right to add or remove, locations, installations, and or sites listed.

8.2 Proposal submittals are a lump sum, completely installed and tested. Equipment and installation cost are to be provided individually for each site.

8.3 Completion of all installations shall be done no later than 9 months after the awarding of the bid.

8.4 A detailed set of specifications to include all items in the bid list shall be provided with the bid proposal.

8.5 Nine spare parts kits shall be provided. Each spare parts kit shall consist of, at the minimum, a card reader and circuit boards.

8.6 Bid proposal shall include references going back five years for previous work on automated fuel management systems, fuel management software, and the installation of automated fuel management control units.

8.7 Exceptions to specifications shall be listed on a separate paper and submitted with bid proposal.

List of Fuel Station Locations for Installations to Take Place.

Exists

N. Augusta

S. China

Randolph

W. Gardiner

Fairfield

Washington

Montville

Greene

Mercer

Edgecomb

Waldoboro

Knox

Turner

Canaan

Skowhegan

Pittsfield

Canton

Northport

Fairbanks

Rockport

Freeport

Yarmouth

Poland

Danville

Athens

Searsport

Gray

Dixfield

Solon

Plymouth

Avon

Dexter

Carmel

Moscow

S. Paris

Bethel

Standish

Orland

Gorham

Charleston

Kingfield

Guilford

Bridgton

Stratton

Lyman

Alfred

Sedgewick

Milo

West Forks

Shirley

Goldbrook

N. Berwick

Ellsworth

York

S. Berwick

La Grange

W. Enfield

Jackman

Amity

Gouldsboro

Bar Harbor

Aurora

Cherryfield

Rockwood

Medway

Winn

Macwahoc

Topsfield

Springfield

Wesley

Beddington

Jonesboro

Crystal

Whiting

Pembroke

Houlton

Ashland

Mars Hill

Presque Isle

Baileyville

Woodland

Fort Kent

Van Buren

Stockholm

Madawaska

Frenchville

Fort Fairfield

Appendix A

Maine D.O.T. IT Standards

MAINE DEPARTMENT OF TRANSPORTATION

INFORMATION SYSTEMS TECHNOLOGY

STANDARDS

ADOPTED: August 18, 2003

LAST REVISED: November 15, 2005

PREFACE:

The Maine Department of Transportation has adopted these Information Systems Technology Standards in order to more effectively and efficiently provide Information Technology Services to its internal and external systems users. These standards are consistent with those adopted by the State of Maine for all agencies.

These standards will be reviewed and altered as necessary on an annual basis so that the Maine Department of Transportation is adaptive to the information technology currently available.

Change Log:

· Adopted August 18, 2003 by the Maine Department of Transportation Information Systems Steering Committee

· Revised September 19, 2003 to include a draft GPS Standard and revisions to the Accessibility Standards as approved by the State of Maine Information Services Policy Board on September 18, 2003.

· Updated March 8, 2004 to include Handheld (PDAs) software standards and an update to the GPS Standard.

· Updated January 10, 2005 as a yearly update revision.

· Updated November 15, 2006 as a periodic update version

TABLE OF CONTENTS

1.0. SOFTWARE STANDARDS

1.1. Application Development

1.1.1. Application Sign-On

1.1.2. Programming Languages

1.1.3. User Interface / Presentation Layer / Internet Browser

1.1.4. Personal Digital Assistant (PDA)

1.1.5. Source Code Control

1.2. Computer Aided Drafting Design

1.2.1. Drafting/Vector Graphics

1.2.2. 3D Survey & Terrain Modeling & Road Design

1.2.3. Survey Data Collection

1.2.4. Electronic Plans Production & Archiving

1.2.5. Add-on/Add-in Programs and Macros

1.3. Database Standards

1.4. Geographic Referencing and Data Formats

1.5. Reporting Tools

1.6. Recoverability

2.0. HARDWARE STANDARDS

2.1. Server Standards

2.1.1. Configuration

2.1.2. Software

2.2. Client Configuration

2.3. Personal Digital Assistant (PDA)

2.4. Scanner

2.5. Handheld GPS Receiver

3.0. NETWORK STANDARDS

4.0. DOCUMETATION

5.0. STATE COMPLIANCE STANDARDS

5.1. ADA Compliance

5.2. Deployment Certification Policy

1.0. SOFTWARE STANDARDS

1.1. Application Development

Applications must be able to perform on Microsoft IIS server, version 6 or Oracle application server, version 9i or 10g.

1.1.1. Application Sign – On

All applications that use an ID and/or password should use the Windows 2003 (Active Directory) network sign-on ID and password. Exceptions may be made for licensed software if that option cannot be made available.

1.1.2. Programming Languages

This section contains the requirements for the “base” programming language used in the development of the application software. One of the programming languages identified below must be used:

· PL/SQL - Oracle's "procedural extension to Structured Query Language (SQL)." Version 9.2.04 and above

· Java versions:

· 1.5 (Bundled with JDeveloper 10g)

· 1.3 (Bundled with Oracle Application server)

· VB.NET Framework version 1.1 or higher

· Use of XML is preferred for passing data

Extensions to these programming languages such as JavaScript are acceptable.

Licensed software not written in any of these languages may be approved on an exception basis.

1.1.3. User Interface / Presentation Layer / Internet Browser The user interface will be provided for in a WEB-enabled format wherever applicable.

Applications which require no footprint on the client machine are preferred.

Modification or an extension of an existing application will remain consistent with the presentation of the parent application.

1.1.3.1. Intranet

Applications developed using a web-enabled presentation layer for use internal to Maine DOT must be compatible with Microsoft Internet Explorer

1.1.3.2. Internet

An application developed for public use must be both Netscape and MSIE. Compatibility with Netscape version 8.1 and MSIE version 6.0 and higher is required. The web based presentation layer must also be consistent with the official State of Maine Web Site at WWW.Maine.gov, in format and design.

1.1.4. Personal Digital Assistant (PDA)

· Current Microsoft PDA operating system

· Microsoft PDA software wherever available (such as database if required)

· Application will be coded in DOT NET.

· Data will be passed in XML files

· Data synchronization logic will be coded on the server side of the application in the application’s software environment.

· IDE recommended: Visual Studio 2005

1.1.5. Source Code Control

The standard method for code versioning used by Maine Department of Transportation is Microsoft’s Visual Source Safe, version 6.0.

1.2. Computer Aided Drafting Design

1.2.1. Drafting/Vector Graphics

Micro Station, Version 8.1 or later, from Bentley Systems, Inc.

1.2.2. 3D Survey & Terrain Modeling & Road Design

MX 2.6 or later, from Bentley Systems Inc. for processing ground surveys, terrain models, roadway design, and related functions.

1.2.3. Survey Data Collection

SDMS 3.3 or later, an AASHTO-ware product, is our system for electronically collecting data from survey instruments, and for transmitting layout data back to survey instruments.

1.2.4. Electronic Plans Production & Archiving

Digital InterPlot, from Bentley Systems, Inc.

Scanned plan images will also be stored in the Digital Interplot archiving system.

1.2.5. Add-on/Add-in Programs and Macros

Microsoft Visual Basic 6.0, or later, is our platform for in-house or custom development of MX Add-In applications and for stand-alone utility programs to facilitate our CADD system.

We have a number of VB programs now, which we are maintaining and enhancing.

We use the Bentley MX SDK for making VB add-ins for MX.

Micro Station VBA is our primary platform for new macros (add-in programs) for Micro Station.

1.3. Database Standards

For any applications that are used beyond a single work unit or in different buildings an Oracle database will be used to house any necessary data. For applications limited to a single work unit and one building (typically 1 – 12 users) a Microsoft Access database may be substituted for an Oracle 9i or 10g database.

1.4. Geographic Referencing and Data Formats

Applications will be GIS-aware where appropriate. Data that is geographic in nature will be geo-referenced. Data may be referenced with an x,y coordinate, with a Maine DOT linear reference, or with a standard use of feature ids such as geographic names for purposes of joining a tabular database with a spatial dataset(example: official town codes join with town polygons that contain town codes) for mapping or query purposes.

Geo-Reference

· x,y must be either lat, long or UTM Nad83 Zone 19 coordinates

· Maine DOT linear reference will be route/begin milepoint/end milepoint/date or element (link)/ offset/date

· Join item to spatial data - Maine DOT node number, standard town name or town code, PIN, etc.

Data Format/Software

· GIS software must be compatible with ESRI GIS products, ArcGIS 8.3 or above and ArcIMS 9.0 or above.

· Spatial data must be in Oracle Spatial9i or 10g, ESRI SDE version 9.1 or above, or ESRI shape file format.

1.5. Reporting Tools

Oracle Business Intelligence version 10.1 or higher is the preferred reporting tool. Other reporting software may be approved on an exception basis.

1.6. Recoverability

Procedures for daily automatic unattended backups will be provided, where appropriate incremental/differential will be provided. Procedures for full unattended backup and restores will also be provided in case of a large catastrophic disaster.

If more than one server is utilized, documentation will be provided that describes how data synchronization will be maintained.

A Windows GUI is preferred so that the system administrator will be able to point and click to activate specific backup and restore procedures.

Maine DOT currently uses ARCserve version 11.5 but is moving to CommVault 6.1. Applications must be able to use either product for backup.

2.0. HARDWARE STANDARDS

2.1. Server Standards

Any new application coming into Maine DOT must work with the Maine DOT Technical Support group to develop a hardware plan. This plan will take into account present Maine DOT servers and computer room equipment to maximize the utilization of existing resources. Maine DOT discourages single use servers and does not intend to dedicate servers to a single application.

2.1.1. Configuration

An example of an Maine DOT typical server is:

Compaq (HP) rack mount

RAID 1 for OS (36.4 , 15,000 RPM)

RAID 5 for DATA and/or SAN attached to disk farm 4 GB RAM minimum Redundant power supplies

Dual 10/100/1000 NIC card

Smart Array controller

SDLT or LTO tape drive (if needed)

Keyboard, mouse, and monitor on 8 port smart switch.

2.1.2. Software

Windows 2003 server for all servers.

ARCserve version 11.5 and CommVault 6.1 for backups.

2.2. Client Configuration

Any new applications must be developed to run in the following minimum desktop environment:

· CPU: Compaq small form factor P4 1.7 20GB,512MB RAM, CD, Windows XP Pro

· Monitor: Compaq 15 inch flat panel

· CD Burner

Standard configurations of clients include the following applications. Any new applications must co-exist with the following products:

· MS Office Desktop Suite 2000 or higher, Outlook 2000 or higher, MX, Micro Station, McAfee Security Protection, ePO, Adobe Acrobat Reader 5.0, ESRI ArcGIS version 9, and Hummingbird DM Viewer.

2.3. Personal Digital Assistant (PDA)

General use: IPAQ 2210 Handheld Pocket PC 2002 with most current OS

2.4. Scanner

Ricoh IS 330DC full color with duplex capabilities

2.5. Handheld GPS Receiver

· Basemap Software: Detailed base map software of Maine with cities, interstate highways, state highways, public roads, rivers, and lakes.

· Parallel Channels: 12

· WAAS Enabled: Yes

· Accuracy w/ WAAS: Within 5 meters 95% of the time.

· Acquisition times (For WAAS): Warm: < 1 min. Cold: < 15 min

· Update Rate: 1 per second

· Waypoints: Minimum of 500

· Position Format: Minimum of Lat/Lon, UTM

· Map Datums: NAD 83

· Coverage: North America

· Case: Waterproof to IEC 529 IPX7 standards

· Carrying Case: Yes

· Data Output: RS232 (or USB v1.1, v2.0) with NMEA 0183 v2.1 data format

· Data Export: GPS collected data exportable to a format that allows for differential correction and is compatible with, and importable into, ESRI GIS data structures.

· Cables: Vehicle 12-Volt Power Adapter and PC Data Cable

· Antenna: Quad Helix (or equivalent)

3.0. NETWORK STANDARDS

Main Office LAN, 1000MB switched backbone with 100MB switched to desktop.

Division LAN, 100MB switched to desktop.

WAN connections:

Main Office 1000MB

One region Office 1000MB

One Region Office 100MB

One Region Office 20MB Two Region Offices – dual T1

Most remote sites T1

Dial-up for mobile users

VPN’s are also used in some cases

4.0. DOCUMENTATION

System and User documentation will be provided for in a standard format and storage facility. Templates will be made available prior to the start of each development phase listed below. The documentation will consist of the following:

Phase 1: Analysis and design; required prior to beginning of coding

· System Overview:

· What is the purpose of the system?

· What problem is the system solving?

· Data Flow Diagram

· Process Flow Diagram

· Functional Requirements Document (Will be developed by Maine DOT regardless of whether system is COTS (“commercial off the shelf”/licensed), contracted development, or internally developed.)

Phase 2: Programming / Development; required within 2 weeks prior to testing

· Technical Documentation

· Description of System Architecture:

· Database type, version, instance name, schemas

· Server configuration (distributed or not)

· Operating System

· Backup and Recovery Procedures

· Security structure

Phase 3: Implementation; required upon user acceptance

· Entity Relationship Diagram with Data Dictionary

· Source Code (Not applicable to COTS software) – should be well-documented either through internal comment lines, external document, or both. Documentation should include:

Description of module – purpose or function

Tables used

Forms and/or Functions to which it relates

· User Documentation: (delivery at system roll-out) User manuals can be hardcopy or electronic copy; electronic is preferred

Online Help must accompany the system.

· Closed Issue Log and Change Log Electronic documentation must be delivered in MSWord 2000 or higher format.

New applications will be tested “on the network” for performance purposes according to the attached State of Maine Network Performance Standards in Appendix A.

5.0. STATE COMPLIANCE STANDARDS

5.1. ADA Compliance

All applications will meet the State of Maine ADA standards as found at: http://www.maine.gov/oit/accessibility/guidelines.htm Applications should be developed for 800 by 600 screen resolution. Licensed software not using this standard may be approved on an exception basis.

5.2. Deployment Certification Policy

Any system development effort subject to CIO’s Deployment Certification policy process must adhere to testing standards found at: http://www.maine.gov/oit/oitpolicies/DeployCertPolicy10_30_2006.htm.

PAGE

_1199697299.bin