GEORGIA PORTS AUTHORITY
Request for Proposal
To Provide an
Automated Terminal Asset Management System
3/8/2016
Automated Terminal Asset Management System RFP
Page 1 of 110
TABLE OF CONTENTS
1.0
PROJECT OVERVIEW
1.1
Executive Summary
1.2
Terminology and Abbreviations
1.3
Third-Party Contacts
1.4
RFP Timetable
1.5
Vision
1.6
Design Concerns
1.7
ATAMS Management
2.0
PORT OPERATIONS OVERVIEW AND OPERATIONAL REQUIREMENTS
2.1
Terminal Description
2.2
Physical Layout
2.3
Network Description
2.4
Container Terminal Operations
2.5
Port Operations Requirements Document
2.6
Equipment Mounting Locations
2.7
Post Installation Testing and Commissioning
2.8
Maintenance Plan
2.9
Logistic Supportability
2.10 Research and Design / Future Capabilities
3.0
PROPOSED WIRELESS LOCAL AREA NETWORK
4.0
PROPOSED OPTICAL CHARACTER RECOGNITION SYSTEM
5.0
PROPOSED RADIO FREQUENCY IDENTIFICATION SYSTEM
6.0
PROPOSED POSITION DETECTION SYSTEM
7.0
REQUEST FOR PROPOSAL PROCEDURES
7.1
Release of Request For Proposal
7.2
Notice of Intent to Propose
7.3
Pre-proposal Conference
7.4
Contact for Inquiries
7.5
Last Date to Submit Written Questions
7.6
Proposal Due Date, Time, and Location
7.7
Bid Bond
7.8
Bid Opening
7.9
Contract Award
7.10 Base Bid, Options, and Marginal Costs
7.11 Proposal Format
7.12 Proposal Content
7.12.1
Cover Page
7.12.2
Table of Contents
7.12.3
Cover Letter
7.12.4
Executive Summary
3/8/2016
Automated Terminal Asset Management System RFP
Page 3 of 110
7.13
7.14
8.0
7.12.5
Firm Background, Principal Officers, and Prior Experience
7.12.6
System Functional & Technical Description
7.12.7
Operational Requirements
7.12.8
Questionnaire Responses
7.12.9
Commissioning
7.12.10 GPA Support Requirements
7.12.11 Training
7.12.12 Cost Proposal
7.12.13 Proposed Schedule
7.12.14 Site References
7.12.15 Concluding Remarks
Proposal Evaluation
7.13.1
Evaluation Criteria
7.13.2
Evaluation Weights
7.13.3
Evaluation Rating
Final Offers
GENERAL TERMS AND CONDITIONS
APPENDIX
TABLE A: TERMINAL INFRASTRUCTURE
FIGURE 1: EXISTING SITE PLAN
FIGURE 2: FUTURE SITE PLAN
FIGURE 3: EXISTING TRUCK PROCESS
FIGURE 4: CONCEPTUAL FUTURE TRUCK PROCESS
TABLE B: EXISITNG DATA FLOW LINK DESCRIPTIONS
TABLE C: FUTURE DATA FLOW LINK DESCRIPTIONS
FIGURE 5: EXISTING DATA FLOW
FIGURE 6: CONCEPTUAL FUTURE DATA FLOW
DRAWING LEGEND
TABLE D: NETWORK NODES
3/8/2016
Automated Terminal Asset Management System RFP
Page 4 of 110
1.0 PROJECT OVERVIEW
1.1
Executive Summary
In the past 12 months, the Port of Savannah has handled more than 16 million tons of
cargo, or 1.76 million Twenty Foot Equivalent Unit (TEU) steel ocean shipping
containers, a growth rate of over 15% per year for several years creating an
expectation of doubling the number of TEU’s handled over the next five years. To stay
ahead of the growth curve, the Georgia Ports Authority (GPA) is prepared to invest in
systems that can increase the efficiency of the port. For over two years, GPA has
researched and observed automated gate and container tracking systems at ports
around the world to determine the best existing technology and vendors that can
create, integrate and maintain a semi-automated equipment and container tracking
system at the GPA Garden City Terminal (GCT). By providing this system, GPA
expects that employees at the port will be able to reliably and efficiently boost their
production to ensure the Port of Savannah maintains a competitive edge and remains
attractive to shippers.
GPA’s approach to the development of this system is to request proposals from
bidders that have an existing system that is already known to work in other ports.
Although GPA wishes to use the most technologically and competitively advanced
systems; there is no desire to be on the “bleeding” edge of technology. Any integration
or operational difficulties that temporarily interfere with port operations will be very
costly. Therefore, proposed systems that have the best chance of selection are those
that are proven in other terminals around the world. Furthermore, by purchasing “offthe-shelf” systems, GPA will not design the system; rather, GPA looks to the selected
vendors to provide designs that exceed the stated operational requirements.
GPA will not rule out proposals on newer or different technologies without a thorough
review. GPA recognizes that existing systems are still not as accurate and reliable as
is desired. Thus, GPA welcomes proposals from bidders whose systems may not be
described here or that may not be currently located in another port; but may provide
solutions that are otherwise superior to the system being described. Thus, bidders
should review the operational systems in existence and the operational
intent/requirements being issued as a part of this Request for Proposal (RFP) to
ensure their proposed systems provide the overall system functionality necessary to
support the Port of Savannah.
The system being sought and described in this RFP and referred to as the
Automated Terminal Asset Management System (ATAMS) is comprised of four
different subsystems:
 A Wireless Local Area Network (WLAN),
 An Optical Character Recognition (OCR) system,
 A Radio Frequency Identification (RFID) system, and
 A Position Detection System (PDS).
A separate RFP is being released for each subsystem; however, bidders that
provide multiple subsystems and bidders who want to make joint proposals are
encouraged to do so, so long as the combined proposal is in the best interest of
3/8/2016
Automated Terminal Asset Management System RFP
Page 5 of 110
the GPA. Ultimately, GPA will select a team of vendors who will work together to
finalize a complete system design prior to integration.
In short, GPA wishes to know and track the exact location and utilization of their
assets and cargo. Over the next three to five years, GPA expects to put a system
in place that will identify and track containers throughout their 1,400 plus acre
terminal whether they come by truck, by rail or by sea. Simultaneously, GPA will
be adding substantially to their Container Handling Equipment (CHE).
All project subsystems will be completed in phases as loosely described in this
RFP; however, the team of selected vendors will define the completion schedule.
The systems GPA chooses to buy will be selected in part on the following
attributes:
1. Lifetime cost,
2. Predicted reliability,
3. Demonstrated technology,
4. Maintainability,
5. Safety attributes,
6. Ease of operation,
7. Capabilities to grow, upgrade, or modify as requirements change.
These systems are expected to work on site for many years to come; therefore,
GPA must find vendors with whom they can forge good working relationships
such as those GPA already has with Navis and LA King. Any system incapable
of integrating with Navis and LA King will not be considered. Contact information
for Navis and LA King can be found in section 1.3 - 3rd Party Contacts.
In conclusion, GPA is seeking qualified vendors to provide systems that help
move containers faster and more efficiently, providing the Port of Savannah with
continued room for growth and improved competitiveness.
1.2
Terminology and Abbreviations
The following terms and abbreviations are used throughout this document.
ATAMS:
Bidder:
BIT:
Bomb Cart:
CAS:
CHE:
Contractor:
EIR:
Field Clerk:
3/8/2016
Automated Terminal Asset Management System
An entity responding to an RFP (may be a contractor or supplier).
Built-In Test is a diagnostic test built into a subsystem or component
that can provide real time monitoring or run manually on demand.
Flatbed with a bolster on the side to move containers quickly
Collision Avoidance System
Container Handling Equipment (RTG, UTR, Top Loader, etc.)
An entity providing, or capable of providing, labor and materials to
GPA, and may or may not have a written contract directly with GPA
Equipment Interchange Receipt
Personnel who man the canopies (Inspection Clerks) verify container
ID, truck ID, chassis ID, GenSet ID, inspect containers for empty,
inspect containers and chassis for damage, and make inputs
Automated Terminal Asset Management System RFP
Page 6 of 110
regarding the above into handheld NAVIS units. Inventory Clerks also
carry handheld devices and do physical inventories of the wheeled
parking areas.
GCT:
Garden City Terminal
GenSet
Generator Set - a diesel or gas-powered electric generator used to
power the refrigerated containers.
GPA:
Georgia Ports Authority
ICTF:
Intermodal Container Transfer Facility
Jockey Truck: Truck used to move wheeled containers or bomb carts (also called
UTR’s).
LA King:
Vendor that manages equipment used to collect data at the gates
Navis:
Software and database system that manages container position and
shipping information. It is also the name of the company that
produced the Navis software, including Express and SPARCS.
OCR:
Optical Character Recognition - The machine recognition of printed
characters.
OOG:
Out of Gauge. This is used to identify an oversized container or
conditions where the cargo is larger than the container and protrudes
in some manner, usually through an opening in the top.
PDS:
Position Detection System – the subsystem that tracks CHE
movement and reports container information as they are being
handled by CHE’s.
PORD:
Port Operations Requirements Document
POV:
Privately Owned Vehicle
QoS:
Quality of Service
RFID:
Radio Frequency Identification
RFP:
Request for Proposal
RDT:
Radio Data Terminal
ROI:
Return on Investment
RTG:
Rubber-Tired Gantry crane is an off road overhead cargo container
crane with the lifting mechanism mounted on a crossbeam supported
on vertical legs which run on rubber tires.
RTK:
“Real Time Kinematic” style Differential Global Positioning System
SPARCS:
Navis’ Terminal and Vessel Planning System
SST:
Smart and Secure Trade Lanes
Subcontractor: An entity that provides labor and materials to GPA, but whose
contract is with a vendor or bidder depending on reference.
Subsystem:
One of several parts to ATAMS, including WLAN, RFID, OCR, PDS,
Navis and LA King, or other systems that may be added
Supplier:
An entity that provides only materials, not labor, to either a vendor,
bidder, or directly to GPA depending on reference.
TCO
Total Cost of Ownership. For purposes of this document, TCO is
defined as the sum total of all cost relating to specific technology over
a 10-year period.
TOS:
Terminal Operating System. The software that manages the flow of
containers through the terminal.
TEU:
A standard "Twenty Foot Equivalent Unit" steel ocean-shipping
container
3/8/2016
Automated Terminal Asset Management System RFP
Page 7 of 110
Top Loader:
Total System:
Transaction:
Turnkey:
UTR:
VACIS:
Vendor:
VLAN:
WEP:
WLAN:
An off road truck-like cargo container handler that uses an overhead
telescopic boom to lift empty or loaded cargo containers by grabbing
the top of the containers (also called a “top pick” or “top handler”).
ATAMS
A delivery or a receivable. A truck that delivers and then receives a
container has made two transactions.
A project in which a separate entity is responsible for setting up a
plant or equipment and putting it into operations. It can include
contractual actions at least through the system, subsystem, or
equipment installation phase and may include follow-on contractual
actions, such as testing, training, logistical and operational support.
Utility Tractor Rig also known as a jockey truck, yard truck, yard
tractor, yard hustler or prime mover. It is an off road mobile utility
vehicle used to carry cargo containers with or without chassis.
Vehicle And Cargo Inspection System
An entity that has been selected by GPA to provide a subsystem (or
partial subsystem) as described in an RFP, and has a written
contract directly with GPA.
Virtual Local Area Network. A logical, not physical, group of devices,
defined by software. VLAN’s allow network administrators to
resegment their networks without physically rearranging the devices
or network connections.
Wired Equivalent Privacy and it is a security protocol for Wi-Fi
networks.
Wireless Local Area Network
1.3 Third-Party Contacts
L. A. King Company
3306 Lime Ave.
Long Beach, CA 90807
Phone: (562) 424-0979
Web: www.lakingco.com
Navis LLC
1000 Broadway, Suite 150
Oakland, CA 94607
Phone: (510) 267-5000
Web: www.navis.com
Contact: Mr. Andy Clason
1.4 RFP Timetable
Event
Issue RFP’s
Pre-proposal Conference Registration
Pre-proposal Conference
Submission of Written Questions Due
Responses to Questions
3/8/2016
Date
16 January 2005
27 January 2006
3 February 2006
10 February 2006
20 February 2006
Automated Terminal Asset Management System RFP
Page 8 of 110
Proposals Due
Notice of Intent
6 March 2006
21 April 2006
1.5 Vision
As noted in paragraph 1.1 - Executive Summary above, this project consists of four
subsystems that comprise the total vision of the complete system. For the system to
work properly, all four subsystems must be working simultaneously. The description
below is a very high level description of the entire system and how it works according
to the GPA vision. GPA is releasing RFP’s for the four functional subsystems so
described. GPA wishes to encourage potential vendors with subsystems that may
perform better than those described below to submit proposals as well. The
description below is intended to provide a big picture of the overall system operation
so vendors of these systems and those with competing systems can understand the
system requirements and extrapolate subsystem requirements.
When a truck comes through the gate, GPA expects RFID to automatically identify the
truck, which has been properly tagged. Once the truck is in the gate, the OCR system
can be used to identify the chassis, the container, and the GenSet, if applicable. This
information can all be compared to the pre-advised database on Navis Web Access.
About this same time, the trucker’s credentials are checked. If all the information
obtained correlates to the pre-advise data, the mission ticket(s) prints out and the
truck moves forward to the canopy where the final inspection is completed. Here, the
RFID system verifies which truck is in which lane. Once the inspection is completed,
the equipment interchange receipt (EIR) prints and the truck moves into the terminal.
When loading or unloading the container, the rubber tire gantry (RTG) or top loader,
which is fitted with a PDS, marks the location where a container is picked up or placed
and at that point the data correlation between the truck and the container is broken on
an inbound move, and is made on an outbound move. Upon exiting the gate, the
truck is again verified through RFID and OCR to ensure the proper container and
proper chassis is departing with the correct truck.
Internal repositioning moves are handled with a PDS system on all the cranes and on
all of the bomb carts that move the containers around the terminal. Bomb carts that
are dedicated solely to positioning containers to and from the Intermodal Container
Transfer Facility (ICTF) may require RFID and OCR verification as they go through
Gate 7.
Aside from the over-the-road trucks that enter the gate daily, there are a number of
jockey trucks that interact with other CHE’s to move containers for stack grooming,
wheeled operations, ship transactions, etc. Most of the jockey trucks interact with
cranes at both ends of their runs. For example, a jockey truck gets a container from an
RTG and takes it to a quay crane. Thus, at both ends of his run, a crane with PDS
equipment has updated Navis on the location of the container. All the jockey truck
needs is an RFID tag to identify which jockey truck is under the crane. Conversely,
some jockey trucks handle wheeled containers. In those situations, at one or both
ends of the run, there is no PDS information to be sent to Navis because there is no
PDS-equipped crane involved. Therefore, those jockey trucks require a mounted PDS
3/8/2016
Automated Terminal Asset Management System RFP
Page 9 of 110
system to send Navis container position information. The table below identifies the
CHE's that require PDS equipment and those that only require RFID tags according to
the conceptual plan.
To have PDS Installed
Quay Cranes
15
Top-picks
104
Side-Picks
26
RTG's
86
UTR
180
To only have RFID Tags Installed
60
Thus the system, through association, has identified the trucker, the truck, the chassis,
the container, and the GenSet and through association has tracked where the
container has been moved. The internal moves were tracked as well using a PDS
system or RFID system on the bomb carts.
The WLAN subsystem is provided as a means of communication with remote RFID
readers, PDS transmissions, and possibly OCR transmissions as well. Also included
are handheld devices under the canopy and other equipment throughout the terminal.
1.6 Design Concerns
Having observed similar systems in other locations, there are a number of potential
design flaws in the system just described and potential bidders’ comments where their
system or combination of systems may provide resolution to these potential issues will
have a strong impact on the selection of vendors. The concerns listed below are in no
particular order:
1.6.1
Accuracy. When the trucks come through the OCR and RFID gates, the
percent of trucks read properly is of great concern. If there are a significant
number of no-reads or misreads; more trucks, rather than fewer trucks, could
end up being sent to the trouble gate or requiring manual gate clerk attention.
This outcome would be devastating to the progress/efficiency of the Ports. In
fact, it is a goal that less than 1/10 of 1% of all the trucks entering the gates or
exiting the gates should have trouble that has to be resolved manually.
1.6.2
Top Lifter. Another concern is the ability of top lifters to read the RFID tag of
trucks. Without an adequate solution for the handoff to be automatic, the need
for manual entry inside the top lift has not been eliminated.
1.6.3
Automatic Handoff. Assuming that RFID readers are adequately placed on
an RTG so that trucks that roll underneath are properly identified; how will the
system correlate and handoff the data relating to/from a particular truck? In
other words, if the system receives an RFID signal from the truck that has
come near the RFID reader, is there potential for that last known truck with a
3/8/2016
Automated Terminal Asset Management System RFP
Page 10 of 110
positive identification to be a truck that goes by or does not stop at the crane;
whereby, the system assumes the incorrect truck is under the RTG.
1.7 ATAMS Management
This RFP has been written by the Maritime Logistics Innovation Center (MLIC) based
in Savannah, Georgia in conjunction with and on behalf of GPA. MLIC will also assist
GPA in the management of the ATAMS project over the next several years. MLIC is a
unique partnership of private industry, academia and federal and state authorities
such as GPA working together to develop, apply and promote new technologies,
identify unique applications for existing technology, and create best practices for safe,
efficient and secure supply-chains. The overall mission of MLIC is to promote creative
technology development and commercialization while providing an environment for
new venture creation and entrepreneurial outreach in a specific, regionally targeted
industrial area. The advancement of automation technology at port terminals in
projects such as this one is a significant undertaking where MLIC can lead, promote,
and perform research and development necessary to develop ever more accurate and
efficient logistic systems. Companies that support maritime logistics are invited to be
a part of MLIC and help drive its future. Contact Page Siplon for more information.
Mr. Page Siplon
Director
Maritime Logistics Innovation Center
190 Technology Circle, Suite 173
Savannah, GA 31407
Phone: (912) 966-7867
Fax: (912) 963-2549
Web: www.georgiainnovation.org
3/8/2016
Automated Terminal Asset Management System RFP
Page 11 of 110
2.0 PORT OPERATIONS OVERVIEW AND OPERATIONAL REQUIREMENTS
2.1
Terminal Description
The Garden City Terminal is the largest single terminal container port in the world,
sitting on approximately 1,400 acres. Well into a two-year project, GPA is changing
the stack positions throughout the terminal. Previously, the stack positions ran
perpendicular to the river and were wide enough to accommodate top lifts. Over the
course of this project, the container stacks are being modified to run parallel to the
river to provide more efficient container movement. Furthermore, the active stacks
are being placed closer together and being serviced totally by RTG’s.
GPA is currently midway through this transition. Figures 1 and 2 (see Appendix) show
the present terminal layout and the future terminal layout respectively. In general, the
container stacks are five-high with RTG capability to go 1-over-5. In other words, the
RTG can raise one container high enough to go over the top of a stack of 5-high to
place the container in another row. Empty stacks are stacked as high as 7 containers
high by side picks and are stacked contiguously rather than in columns of five.
2.2
Physical Layout
2.2.1 Terminal Diagrams. Figures 1 and 2 denote major items in the site plans.
Table A: Key Terminal Infrastructure correlates to Figure 1: Existing Site Plan
and Figure 2: Future Site Plan. This table identifies the gates, the container
stack areas and the access roadways and comparing the two figures reveals
the changes that are being made on site to improve efficiency and density.
2.2.2
2.3
Network Description
2.3.1 Data Flow Descriptions. Table B: Existing Data Flow Link Descriptions and
Table C: Future Data Flow Link Descriptions correlate to and describe the
data links found in the network diagrams shown in Figure 5: Existing Data
Flow and Figure 6: Future Data Flow. The existing network nodes shown here
can be used in the system designs described in this RFP. Figure 6 will be
modified accordingly once vendors are selected and an overall design is
finalized.
2.3.2
2.4
Truck Process Flowcharts. The flowcharts in Figure 3: Existing Truck Process
and Figure 4: Conceptual Future Truck Process describe the movement of
trucks through the truck gates currently (Figure 3) and in the future (Figure 4).
Figure 4 is conceptually based on fielding the system described in this
document and may be modified depending on the vendors and systems
ultimately chosen in the RFP process.
Network Nodes. Table D: Network Nodes is a list of network nodes where
data systems currently can hook into the network.
Container Terminal Operations
The container terminal is generally open to truckers Monday through Friday 0700 until
1800. All other hours are spent grooming the stacks and pre-positioning containers in
other parts of the terminal for shipment over rail, ship or truck.
3/8/2016
Automated Terminal Asset Management System RFP
Page 13 of 110
GPA has three truck interchange gates - gate 3, 4 and 6. Gate 3 has 2 approach lanes
that widen to 10 pedestal lanes. After leaving the pedestals, the truckers then move
into one of 13 lanes for inspection. Of the 13 lanes, 6 lanes are inbound only, 4 are
outbound only, and the remaining 3 can be switched depending on traffic conditions.
Approximately 1,700 transactions move through gate 3 daily on average.
Gate 4 has multiple approach lanes that widens to 13 pedestal lanes. After leaving
the pedestal, the truckers then move into one of 15 lanes for inspection. Of the 15
lanes, 8 can be used for inbound traffic only, 4 can be used for outbound traffic only,
and the remaining 3 can be used for either inbound or outbound traffic. An average of
2,800 Transactions move through gate 4 daily.
The entrance to the Rapid Dispatch Area at gate 6 has 2 inbound lanes that expand to
3 inbound lanes after the pedestal. There are 3 outbound lanes that narrow to 2
outbound lanes at the exit to the highway. An average of 700 Transactions move
through gate 6 daily. The Rapid Dispatch area is a wheeled operation.
2.5
Port Operations Requirements Document (PORD)
This document identifies total system level operational requirements that are a part of
the automated container tracking system that is being fielded. Operational tests will
be conducted against these requirements as well as certain technical requirements.
Specific nomenclature is used in this section to define and delineate requirements
from goals or actions.

The words “shall” or “requires” indicates a GPA requirement. If the requirement
applies to a bidder’s particular subsystem(s), the bidder’s proposal must indicate
whether or not the requirement can be met by the proposed system.

The word “should” indicates a GPA desire or goal. If the goal applies to a bidder’s
particular subsystem(s), the bidder’s proposal must indicate whether or not the
goal can be met by the proposed system.

The word “will” indicates that GPA will take action or consideration regarding the
matter.

Precise Location (or Location Precision) is defined as having no ambiguity as to
the location of a container in a three-dimensional stack, on a truck chassis, or
position on a rail car including the rail car location. Furthermore, any equipment
that moves to a particular location (however identified in 3 dimensions) shall find
the container in that location without error or confusion with nearby locations or
containers. Location precision is not based on being within a certain distance or
radius from a lat/long; although, that may be an underlying requirement imposed
by the bidder on his own subsystem to ensure locations are precise in accordance
with the GPA definition.
Accurate Location (or Location Accuracy) is defined as a 2-dimensional fixed
position within 1 meter of the actual location for a CHE or rail car at rest. For a

3/8/2016
Automated Terminal Asset Management System RFP
Page 14 of 110
CHE in motion, an accurate location is a reported position within 5 meters of the
actual location and a direction of travel within ±20 degrees of actual direction.

Container Move Accuracy is defined as recording the following information
regarding container movement: the correct identity of the CHE and road trucks
involved, and the starting location and ending location of the moved container such
that recorded locations comply with the definition of a Precise Location or gate of
entrance/exit.

Efficiency in Moves is defined as the average number of times a container is
moved from the time it enters the container terminal until the time it leaves the
container terminal. Efficiency in Moves can be measured over any length of time
such as a day, a week, a month, etc.

Crane Efficiency is defined as the number of containers added or removed from a
stack or train in a given period of time, less time spent waiting on a bomb cart to
arrive or movement instructions to be sent by Navis.

CHE Efficiency is defined as the total number of truck, rail and ship transactions
divided by the total number of container moves completed during the same time
period.

System Load Efficiency is defined as the average number of containers loaded or
unloaded per hour by a given resource.

System Down Time is defined as all times when the system is not meeting the
operational requirements set forth in section 2.5 and those operational criteria for
which the bidders agree to meet in sections 3-6 (and ultimately included in the
contract); or as any system or subsystem malfunction that prevents the system or
any subsystem from automatically collecting, recording or displaying real-time data
while the terminal operates at the capacities and flow rates defined in section 2.5.
In other words, an OCR camera out of action that does not prevent the gate from
operating at normal flows does not constitute system downtime; however, if an
adequate number of CHE’s cannot operate because the PDS system is broken
and the movement of containers is impacted, ATAMS is considered down.

Gate Throughput is defined as the number of trucks moving through a gate divided
by the number of open lanes divided by the length of time (in hours). Thus 1000
trucks entering a gate with 10 lanes over a four-hour period is a throughput of 25
trucks per lane per hour. Trouble referrals caused by faulty pre-advise data (wrong
data entered by trucking company) or failure of the trucker to obtain credentials are
not included in the calculation of Gate Throughput.
2.5.1
3/8/2016
Increase Container Throughput. ATAMS shall increase container throughput
per day per acre without increasing gate capacity. The ultimate objective is to
move more containers through the terminal with existing assets and
personnel. There is no attempt to reduce manpower; instead, GPA will provide
Automated Terminal Asset Management System RFP
Page 15 of 110
systems that allow existing personnel to process more containers per day.
Also, GPA will not add more truck gates or lanes. System approaches that
help GPA accomplish this objective will be considered. Approaches that do
not help GPA meet this goal will not be considered. Due to the division of
labor at GPA, return on investment (ROI) is not a meaningful measurement.
GPA seeks the best container throughput at the best price.
2.5.1.1
Increase Container Throughput via Trucks. The vast majority of
containers arriving or departing from the terminal over land do so
on trucks. Increasing the throughput at the terminal will incur a
similar increase in truck traffic. Moving trucks through the gates
more efficiently will only marginally aid in the overall efficiency of
the port if systems inside the gates do not work more efficiently
as well; therefore, ATAMS shall reduce truck turn times from 50
minutes to 30 minutes for a 2-way move.
2.5.1.1.1 More Trucks. The number of truck transactions has been
steadily increasing for years. GPA recently signed two additional
large-scale retailers who will be transporting more goods
through the GCT, which will require more trucks to enter the
terminal each day.
2.5.1.1.2 Improve efficiency and throughput at Truck Gates. GPA will use
automated systems to improve Gate Throughput. ATAMS shall
meet a Gate Throughput of at least 40.
2.5.1.1.3 Reduce data entry requirements. GPA requires automated
systems that reduce data entry. GPA will retain the ability to
manually operate the terminal gates for use as a backup system
in the event of an emergency or to augment the automated
system as necessary. ATAMS shall correctly automatically
identify and record all required data for 95% of all containers,
80% of all chassis and 60% of all GenSets. At no time shall less
than 70% of all trucks pass through the gates without the need
for gate clerk interaction. (Exception: in this phase of ATAMS,
the inspection clerks will remain under the canopies.)
2.5.1.1.3.1
Minimize data entry errors. By using automated
systems, the opportunities for data entry error should be
minimized. Data that is automatically entered will be wrong
only if the container, chassis, truck or GenSet was
misidentified. By definition, data entry errors can only occur
with human intervention. Therefore, the greater percentage
of automatically identified containers, etc., the fewer data
entry errors that can occur. Vendors with proven higher
percentages of automatically identified trucks, chassis and
containers will be considered more credible.
3/8/2016
Automated Terminal Asset Management System RFP
Page 16 of 110
2.5.1.1.3.2
Auto ID container number. ATAMS shall automatically
identify containers of all sizes including 20, 40, 45, 48, 53,
and 20/20 foot containers that follow ISO 6346 standard
formats including the check digit verification. ATAMS shall
correctly identify the container number on 95% of all
containers
2.5.1.1.3.3
Auto ID chassis number. ATAMS shall correctly
identify the chassis number on 80% of all chassis.
2.5.1.1.3.4
Auto ID Truck. ATAMS shall automatically identify
trucks using RFID or some other means of identifying the
trucks entering and departing gates and while moving
throughout the terminal. ATAMS shall correctly automatically
identify 99.9% of all trucks passing each location where
ATAMS equipment is located. Thus, ATAMS has multiple
opportunities to read each truck during a single trip through
the terminal. Trucks not equipped with the proper equipment
to be read by ATAMS are not counted in the calculations.
Trucks that have the proper equipment; but, the equipment is
not working, are included in the calculations. For example, a
truck with a bad tag may be misread at the gate, the canopy,
the CHE, the outgoing gate, etc. and thus adding multiple
bad reads to the calculation.
2.5.1.1.3.5
Auto ID GenSet. ATAMS shall correctly automatically
identify the GenSet number on 50% of all chassis undermounted GenSets and 75% of all container nose-mounted
GenSets. Identification shall be made without installing any
equipment on the generator sets.
2.5.1.1.4 Auto ID Container Seal. Container Seal identification is not a
part of this project; however, bidders that can verify seals are
unbroken and/or auto ID container seals will be considered.
GPA will not specify a particular seal as part of this project;
therefore, seal monitoring products should be able to verify
seals of all types. ATAMS should correctly identify the seal on
99.9% of all containers.
2.5.1.1.5 Auto Verify Empty Containers. Automatically verifying empty
containers is not a part of this project; however, bidders that can
verify that containers are empty will be favorably considered.
ATAMS should correctly automatically verify that 99.9% of all
empty containers are empty. ATAMS shall not allow any false
positives (identify a full container as an empty container).
2.5.1.1.6 Auto Inspect Chassis and Containers for Damage. Remote
inspections are not a part of this project; however, bidders that
3/8/2016
Automated Terminal Asset Management System RFP
Page 17 of 110
can remotely or automatically inspect and report on container
and chassis damage will be considered. ATAMS should allow
all containers to be inspected remotely with out manual
intervention.
2.5.1.1.7 Keep Driver in Truck When Possible. ATAMS should keep
truckers in their trucks to minimize turn times. ATAMS shall
ensure 99% of all truck drivers do not have to get out of the cab
of their truck unless opening doors for an inspection.
2.5.1.1.8 Fewer Gate Troubles. ATAMS should improve efficiency by
reducing the number of trucks that are referred to the trouble
gates. System solutions that aid in this goal will be considered.
Subsystem solutions that increase gate troubles may be
penalized.
2.5.1.1.9 Improved Pre-advise. GPA requires all shippers to pre-advise
their shipments using Navis Web Access before entering the
terminal. This data will be available to ATAMS to aid in
processing.
2.5.1.1.10 Ensure Credentialing Completed Before Driver gets to Gate.
GPA is making efforts to get all trucks and truck drivers properly
credentialed before making their way to the entrance gates.
ATAMS system approaches should help GPA in this endeavor.
2.5.1.1.11 Reduce Lost Time at Intermodal Gates. ATAMS shall process a
jockey truck in less than 30 seconds at gate 7.
2.5.1.1.12 Track Chassis. GPA currently identifies chassis as they move
through the gates but does not track chassis as they move
through the terminal. ATAMS should track all assets throughout
the container terminal and/or provide status information in realtime.
2.5.1.1.13 Track GenSets. GPA currently identifies GenSets as they move
through the gates but does not track GenSets as they move
through the terminal. ATAMS should track all assets throughout
the container terminal and/or provide status information in realtime.
2.5.1.2
3/8/2016
Increase Container Throughput via Ships. Almost all containers
will have an associated ship transaction; thus, increasing the
throughput at the terminal will incur a similar increase in ship
transactions. GPA forecasts that ships with more than 5,000
TEU’s will dock at GCT within the next two years; up from the
2,500 TEU ships that are common now. GPA is also experiencing
an increase in the number of ships that call.
Automated Terminal Asset Management System RFP
Page 18 of 110
2.5.1.2.1 Larger Cranes. GPA has already begun installing larger postPanamax cranes and raising the existing cranes to
accommodate post-Panamax ships.
2.5.1.2.2 More Dock Space. GPA is already seeing an increase in the
number of ships and is adding more dock space to the terminal.
2.5.1.2.3 Deeper Channel. Dredging operations are in the planning stage
now to accommodate the larger ships.
2.5.1.2.4 More Quay Cranes per Ship. GPA is already underway in
preparations by installing more cranes on the docks. Larger
ships may allow additional cranes for faster unloading.
2.5.1.2.5 Improve Efficiency on Docks. ATAMS shall increase the quay
crane system load efficiency by 10% over current rates. The
current rates shall be measured by the vendor prior to
commencing installation of ATAMS.
2.5.1.2.6 Faster Cranes. By providing accurate load data and container
position data, the system can help increase the speed the crane
operates. ATAMS shall increase quay crane efficiency by 10%
as a result of better position data. GPA currently averages
approximately 40 moves per hour per crane.
2.5.1.2.7 Automatically ID containers. ATAMS should automatically and
accurately identify 99.9% of all containers and correlate them to
move plans as the crane picks up each container. Note: This
requirement is not part of the base plan but is included as an
option and is planned for eventual inclusion into ATAMS.
2.5.1.2.8 Automatically ID CHE / Jockey Trucks. During 99.9% of all
handoffs between a CHE and quay crane, GPA requires the
crane, the CHE and the container to be automatically identified
and associated without manual intervention.
2.5.1.3
Increase Container Throughput via Rail. Increasing the
throughput at the terminal will incur a similar increase in rail
traffic, even though the majority of containers are not carried by
rail. ATAMS shall reduce the time it takes to transfer containers
from the ICTF to and from the terminal.
2.5.1.3.1 More Trains. GPA forecasts increased rail activity as growth in
container transport increases. Any automated rail container
tracking system purchased as part of ATAMS shall be capable of
continued growth in the number of trains.
3/8/2016
Automated Terminal Asset Management System RFP
Page 19 of 110
2.5.1.3.2 More Tracks. GPA forecasts the number of tracks at ICTF to at
least double in coming years to accommodate additional trains.
Any automated rail container tracking system purchased as part
of ATAMS shall be capable of continued growth in the number of
tracks at ICTF.
2.5.1.3.3 More Trains per Track per Day. GPA forecasts the number of
trains per day to increase per given amount of track, requiring
faster turn times.
2.5.1.3.4 Improve Efficiency and Throughput at ICTF. ATAMS shall
increase monthly CHE efficiency at ICTF by 10% over current
rates. The current rates shall be measured by the vendor prior
to commencing installation of ATAMS.
2.5.1.3.5 Automate Rail Booking. Currently, rail cars and associated
containers are manually located. GPA will automate this activity
as rail activity increases. ATAMS shall identify and Precisely
Locate all rail cars in the ICTF as well as all containers and
associated positions on the rail cars.
2.5.1.3.6 Faster Loading / Unloading Rail Cars. ATAMS should allow rail
cars to be loaded and unloaded faster due to savings by
automatically tracking container positions and rail car positions
and feeding that information through Navis to the CHE
operators and by not requiring the operators to manually enter
the data. ATAMS should increase ICTF System Load Efficiency
by 25%.
2.5.1.3.7 Automatically ID Container at ICTF. ATAMS shall accurately
identify 99.8% of all rail cars and 95% of all containers. ATAMS
should accurately identify 99.9% of all rail cars and 99.5% of all
containers.
2.5.1.3.8 Automatically ID Container positions. ATAMS shall Accurately
Locate 99.9% of all rail containers.
2.5.1.3.9 Automatically ID rail car locations. ATAMS shall Accurately
Locate 99.9% of all rail cars.
2.5.1.3.10 Faster moves between railcars and terminal. GPA requires an
increase in Crane Efficiency of loading and unloading rail cars
onto bomb carts that move between the terminal and the ICTF.
2.5.1.4
3/8/2016
Improve Container Management. Without associated changes in
the terminal, gate improvements will only create bottlenecks
inside the terminal, possibly causing greater disruption to
operations. Several initiatives are underway at GCT including, but
Automated Terminal Asset Management System RFP
Page 20 of 110
not limited to, increasing the density of the stacks, changing the
orientation of the stacks to improve ship loading/unloading
efficiency, and adding CHE’s. Additionally, ATAMS shall automate
container tracking within the terminal to speed container handling,
reduce manual data entries, and improve CHE utilization and
efficiency.
2.5.1.4.1 More CHE. More quay cranes, RTG’s, top lifts, bombcarts, etc.
will allow more containers to be transported through the
terminal.
2.5.1.4.2 Shift more Operations to RTG’s. GPA plans to increase the
number of RTG’s to 90 over the next ten years as well as a
sufficient number of jockey trucks to move the containers
expeditiously.
2.5.1.4.3 Improve Container Handling Efficiency. Currently, GPA makes
about 5,500 transactions (delivery or receivable) per day on
average. That number is expected to rise 15% – 20% per year
for the next several years. ATAMS shall enable GPA to process
11,000 transactions per day by 2010.
2.5.1.4.4 Improve Utilization of CHE’s. ATAMS shall increase CHE
utilization by reducing CHE downtime and by providing reports
to operations staff to help evaluate the effective utilization of
CHE’s.
2.5.1.4.4.1
Hold Operators Accountable. ATAMS shall monitor
CHE’s and identify when a CHE is improperly used or
damaged, such as backing into a light pole. Whenever any
such event happens, the CHE ID, location and time/date
must be passed and recorded. Furthermore, instantaneous
reports such as emails and pager notifications shall be
programmable.
2.5.1.4.4.2
Automatically Report Damages. Whenever any such
event, based on shock or other method occurs, immediate
reports and notifications shall be sent. These notifications
shall be programmable and modifiable by GPA.
2.5.1.4.4.3
Mark Time / Date Damage Occurred. Any such report
or notification must report the exact date and time, within 5
seconds.
2.5.1.4.4.4
Mark Location Where Damage Occurred. Any such
report or notification shall identify the precise position that
can be correlated on a map. ATAMS should mark the
incident on a terminal map (printable) that includes all
3/8/2016
Automated Terminal Asset Management System RFP
Page 21 of 110
permanent structures at GCT such as poles, buildings, etc.
as well as the location of mobile equipment nearby. The map
shall be modifiable as changes on site are made.
2.5.1.4.4.5
Automatically ID Operator. Any such report or
notification shall automatically identify the operator of the
CHE. All CHE’s shall not be operable without first identifying
the operator to the System.
2.5.1.4.4.6
Auto ID CHE. GPA requires that CHE’s be
automatically identified by the PDS or RFID.
2.5.1.4.4.7
Increase Stack CHE Efficiency. ATAMS shall
increase RTG Crane Efficiency by 15% over current rates.
The current rates shall be measured prior to commencing
installation of ATAMS.
2.5.1.4.4.8
Automatic Data Entry at CHE. ATAMS should keep
CHE operators moving containers without stopping to do
data entry. ATAMS shall automatically track and report
Precise Locations and handoffs on container movements
without operator intervention on 97% of containers handled.
2.5.1.4.4.9
Minimize CHE Movement Between / During Moves.
By more timely identification of the location and timing of an
incoming truck, CHE’s efficiency should be improved by
properly anticipating the order of truck arrival at the stacks.
ATAMS should provide an overall system capability that
reduces CHE movement and container movement.
2.5.1.4.5 Eliminate Lost / Misplaced Containers. GPA requires Accurate
Location data in real time for all containers at rest. For all
containers not at rest, ATAMS shall identify the equipment in
possession of the container as well as the source and
destination planned for the container.
2.5.1.4.6 Known Truck Locations. ATAMS shall track all CHE’s in real time
that operate solely in the terminal to within 5 meters. Trucks that
operate between the terminal and the ICTF shall be located at a
minimum when they move through gate 7 and when a CHE
loads or unloads a container to/from the truck.
2.5.1.4.7 Improve Inventory Accuracy. ATAMS shall maintain a Precise
Location on all containers (at rest). ATAMS shall maintain
Accurate Location data on 99.9% of all CHE’s on site. If blind
spots occur or wireless service is momentarily disrupted in the
terminal preventing the ability to automatically transfer data; the
3/8/2016
Automated Terminal Asset Management System RFP
Page 22 of 110
data shall be saved and retransmitted as soon as the CHE is
communicating again.
2.5.1.4.8 Container Moves. ATAMS shall maintain a Container Move
Accuracy of 100%.
2.5.1.4.9 No Stopping Between Tasks. Keeping the trucks moving without
delays is critical to reducing turn times. Although not a part of
this project, systems that aid this endeavor or can aid this
endeavor on future GPA projects will be favorably considered.
2.5.1.4.10 Better Traffic Routing. GPA is not seeking routing solutions as
part of this project; however, systems that aid this endeavor or
can aid this endeavor on future GPA projects will be favorably
considered.
2.5.1.4.11 Enable CHE’s to Move to Precise Location Faster. ATAMS shall
ensure Precise Locations for all containers are maintained at all
times in Navis SPARCS. Furthermore, ATAMS shall utilize preadvise data and container location data to increase Efficiency in
Moves by 20%.
2.5.1.4.12 Pre-plan Moves. ATAMS shall utilize pre-advise data and
container location data to increase Efficiency in Moves by preplanning container moves.
2.5.1.5
Minimize Initial Installation and Life Cycle Costs. GPA will
evaluate the initial and 10-year life cycle costs of the subsystems
and will make purchase decisions based on the perceived overall
value (price vs. performance).
2.5.1.5.1 Replacements. GPA requires a realistic estimate of the number
and type of replacements that will be required as well as the
number of spares that must be kept on site for quick turn-around
when items fail. GPA will not pay for equipment and services
due to failures that exceed the estimates outlined in the
proposals by more than 15%. Furthermore, GPA will not pay
extra for any failures that require expedited services or shipping
due to failures that exceed the number of spares recommended
in the proposals.
2.5.1.5.2 Maintenance. GPA requires a realistic estimate of preventative
and emergency maintenance costs. Penalties may be imposed
if actual maintenance costs exceed estimated costs in the
proposal by more than 20%.
3/8/2016
Automated Terminal Asset Management System RFP
Page 23 of 110
2.5.1.5.3 Fees. All overhead and profit charges shall be reported in the
proposals as actual numbers, not as percentages or based on
time.
2.5.1.5.4 Initial installation. Installation costs are critical, as GPA has
limited funding for these projects. However, 10-year life cycle
costs based on growth of 15% per year in containers handled,
total tonnage, and equipment inventories will be more important
that initial costs.
2.5.1.6
Improve Security. Security of data, equipment and cargo must be
maintained throughout installation period and implementation of
automated systems shall prevent unauthorized users from
gaining access.
2.5.1.7
Improve Safety. The safety and well being of GPA personnel is
paramount and shall be addressed in the design, maintenance
procedures and operations of any equipment fielded for port
operations.
2.5.1.8
No Service Failures. GPA cannot afford failures that disrupt
terminal operations; therefore, ATAMS shall ensure scheduled
and unscheduled maintenance does not interfere with terminal
operations. Furthermore, proposed ATAMS solutions shall be
evaluated for redundancy and single mode failures.
2.5.1.9
System Reliability. Reliability of the system is critical to Port
operations. ATAMS shall be operational 24-hours each and every
day of the year. Any system fielded shall meet the following
stringent reliability requirements.
2.5.1.9.1 Total Annual Downtime. ATAMS shall not be down more than
100 hours in any 12-month period, including time spent for
scheduled shutdowns for maintenance or upgrades.
2.5.1.9.2 Total Monthly Downtime. ATAMS shall not be down more than
12 hours in any one month, including time spent for scheduled
shutdowns for maintenance or upgrades.
2.5.1.9.3 Total Weekly Downtime. The system cannot be down more than
4 hours in any week, including time spent for scheduled
shutdowns for maintenance and upgrades.
2.5.1.9.4 Total Daily Downtime. The system cannot be down more than 1
hour in any 24-hour period, including time spent for scheduled
shutdowns for maintenance or upgrades.
3/8/2016
Automated Terminal Asset Management System RFP
Page 24 of 110
2.5.1.9.5 Backups. All data shall be recorded to multiple locations such
that no data is lost in the event of a power or transmission
failure. Furthermore, all transmissions shall be saved and
repeated until the receiver acknowledges receipt of the
transmission. Data shall be backed up or capability to back up
the data shall be given to GPA Information Technology operators
to ensure in the event of a total failure, the existing data can be
recovered with a loss of no more than 10 minutes of data.
2.5.1.9.6 Single Point Failures. Single point failures should be identified
and eliminated if at all possible. All single point failures shall be
identified in the proposal.
2.5.1.9.7 Power Failure. ATAMS shall be capable of operation for at least
1 hour without interruption in the event of a complete power
failure.
2.5.1.9.8 Environment. All systems shall work in any conceivable
environment such as during electrical and thunderstorms, high
winds (up to 75 knots), heavy rain up to 6” per hour, 99%
humidity, temperatures from 0 to 110 degrees Fahrenheit, hail,
sleet and snow.
2.5.1.9.9 Grounding. All ATAMS equipment shall be properly grounded to
within 5 Ohms verified by a grounding resistance test.
Resistance tests are invalid if done within 72 hours of rainfall on
site.
2.5.1.10
System Implementation. ATAMS shall be installed and tested
before full-scale turn-on. ATAMS shall be installed by subsystem
in phases to be determined after proposal selections. Each phase
shall be tested before moving on to the next phase. In general,
ATAMS shall be installed at gate 3, followed by gate 4 and 6,
other gates as required, then inside the terminal.
2.5.1.10.1 Turnkey installations. In as much as possible, GPA is seeking
off-the-shelf turnkey solutions. However, any resources (such as
power, fiber cabling, towers, etc.) the vendor requires from GPA
to complete their installations must be outlined in detail in their
proposal. Bidders assume the responsibility to install and/or pay
for any infrastructure not properly identified in their proposal.
2.5.1.10.2 Minimize customization. As the complexity of systems
increases, GPA wishes to reduce customized software as much
as possible. ATAMS should not require customized software
solutions. All customized software shall be identified in the
proposal.
3/8/2016
Automated Terminal Asset Management System RFP
Page 25 of 110
2.5.1.10.3 Data Integration. GPA requires data integration to be seamless
and work without error with existing systems. Standardized data
types, such as Extensible Markup Language (XML), are strongly
encouraged.
2.5.1.11
Navis. GPA requires that all systems integrate with Navis
(SPARCS, Express, etc.) as required to provide the total system
solution. Stand-alone solutions are not acceptable.
2.5.1.12
As-built Drawings. As-built drawings and complete documentation
shall be delivered within 30 days upon project completion. Final
payment will not be made until As-built Drawings are provided.
2.5.1.13
Operations Manuals. Operations manuals with step-by-step
instructions regarding equipment operations shall be delivered
prior to personnel training. Manuals shall include system design
layouts, software documentation and details of system operation
as well as individual equipment operation procedures and
troubleshooting techniques. Final payment will not be made until
operations manuals are provided.
2.5.1.14
Maintenance Manuals. Manuals detailing procedures for
preventative maintenance and repair/replacement at the system
level down to the unit levels shall be provided prior to
maintenance training. Final payment will not be made until
maintenance manuals are provided.
2.5.1.15
Improve Back Office Efficiency. An increase in container
operations also demands an increase in back office support.
ATAMS shall provide real-time, periodic and on-demand reporting
that ensures support systems can enhance operations.
2.5.1.15.1 Production and Accountability Tools. ATAMS shall provide tools
(reports, notifications, etc.) to monitor production and allow GPA
to hold drivers accountable. On-screen digital maps and graphic
images/tools are examples of desirable features that can be
used to monitor equipment and containers within the terminal.
Saved data shall allow GPA to replay given events or time
periods within the previous 12 months without searching
archives.
2.5.1.15.2 Inventory Reporting. ATAMS shall have the capability to
generate reports regarding inventory. Standard inventory reports
shall be available as well as reports that can be created from
scratch or modified by the GPA analyst.
3/8/2016
Automated Terminal Asset Management System RFP
Page 26 of 110
2.5.1.15.3 Record of Movements. Movements of all equipment and
containers shall be recorded with time/date and operator.
Reports and real-time operations should be observable on
desktop workstations.
2.5.1.15.4 Container Reports. ATAMS shall track and report the amount of
time containers spend on site. Reports shall be modifiable and
shall include, at a minimum, the date/time a container entered
the terminal, the method of entry, the date/time a container
departed the terminal, the method of exit, the total time on site,
the number of times the container was moved while on site, and
all related data such as shipping company, CHE operators,
shipping instructions, etc.
2.5.1.15.5 Damage Assessment. ATAMS shall track and report on
damages to CHE’s, containers, and chassis as reported on
handheld devices and through automated shock event detection
devices. Reports should include information regarding the type,
location and extent of damages.
2.5.1.15.6 Report Productivity. ATAMS shall provide reports on demand
that detail and summarize CHE and driver productivity and
activity during any time period within the previous 365 days.
2.6
2.5.1.16
Prepare for Future. GPA will continue to add to and modify
ATAMS as technology and requirements change. GPA will
evaluate proposing companies as well as proposal designs to
select entities as well as products that will likely support
operations for years and continue to enhance systems for
accuracy and efficiency.
2.5.1.17
Building Block. This system and each subsystem will be a
fundamental building block for future terminal automation
projects. RFP’s will be compared to determine the ease of
expansion and integration with other subsystems.
2.5.1.18
Open System Architecture. In the greatest extent possible, GPA
requires the use of industry standard equipment and software.
Proprietary based systems are strongly discouraged. Where
proprietary systems are used, the ability to transmit data in
industry standard open system formats is strongly encouraged.
Equipment Mounting Locations
Equipment can be mounted on existing buildings and poles to reduce costs. Proposals
requiring equipment to not be mounted on existing structures shall include the cost of
adding infrastructure or shall include enough information to allow GPA to determine
the costs to provide the necessary infrastructure. Note: the light poles in the terminal
have power only in times of darkness.
3/8/2016
Automated Terminal Asset Management System RFP
Page 27 of 110
2.7
2.8
Post Installation Testing and Commissioning
Proposals shall include a thorough commissioning program description which includes
a description of unit and end to end testing that will be performed as part of the
commissioning process. Perhaps the most important part of the project,
commissioning will be accomplished in two stages: a subsystem commissioning and a
total system commissioning. Bidders shall include minimum acceptable test criteria,
coverage analysis and interference testing as well as test procedures that describe
how unit and end-to-end testing will be completed without disturbing ongoing
operations.
2.7.1
Subsystem Commissioning. The subsystem commissioning shall consist of
two parts: unit testing and end-to-end testing. Unit testing will be completed
as the subsystem is being installed. Results will be forthcoming and
modifications made to correct deficiencies prior to completion of the entire
subsystem. Once each component is tested and is deemed to meet the
design requirements for proper operation, a complete end-to-end subsystem
test will be performed in varying conditions as described in the test plan
provided as part of the proposal.
2.7.2
Total System Commissioning. Once ATAMS (all subsystems) is completed, a
thorough end-to-end test will be performed to ensure the overall system
performs as required including the communications between each of the
subsystems involved. All subsystem vendors shall be present for the test to
ensure their subsystem works properly and to make any necessary
modifications if the overall system fails as a result. Bidders shall identify their
level of support during this test, methods to verify their subsystem in the event
of a failure between subsystems, and recommended test procedures to
follow. The vendors that are selected to provide the various subsystems will
write a test plan together with GPA during the final design analysis
Maintenance Plan
For each subsystem proposed, the vendor shall develop a complete
maintenance plan that provides for routine preventative maintenance as well
as emergency service. The plan shall identify what maintenance GPA shall
complete and what portions should be completed by others. Furthermore, the
plan shall identify what items are maintained on site and which components
are repaired off site. For maintenance that is subcontracted, the plan shall
identify the response times for on-site maintenance and repair. These can
vary by component if necessary and shall be developed to ensure the
reliability criteria identified in section 2.5.1.9 is met at all times. Finally, any
service that is provided on-line shall be identified as well. In the proposal, the
maintenance plan shall be developed well enough to provide the selection
team with enough information to understand the philosophy behind the
maintenance plan; who shall accomplish the work; and what annual costs are
expected over a ten-year period. After selection, the chosen vendors shall
complete the maintenance plan and provide training to ensure GPA can
3/8/2016
Automated Terminal Asset Management System RFP
Page 28 of 110
monitor and administer the maintenance as well as complete any
maintenance that is best completed by GPA personnel.
2.9
Logistic Supportability
Since many components in use today are manufactured in foreign countries,
GPA wishes to ensure the systems fielded are logistically supportable.
Bidders shall make estimates and include the cost of such in the appropriate
cost estimates. Proposals shall include a description of the efforts made to
reduce the number of spare parts, the costs thereof, or any action taken to
ensure GPA has the parts needed, when they need them.
2.9.1
Number of Spare Parts. Proposals shall include the number of spare parts of
each type of equipment proposed that should be kept on hand to maintain the
specified level of reliability.
2.9.2
Equipment Obsolescence. Proposals shall provide information regarding how
often the manufacturers make their product obsolete or replace their existing
product line.
2.9.3
Replenishment Time. Bidders shall provide a guaranteed maximum
replenishment time from order placement for replacement parts.
2.9.4
Parts Programs. Bidders shall describe any discounted spare parts programs
offered or other methods to enable GPA to attain the best life cycle cost for all
proposed equipment.
2.10 Research and Development / Future Capabilities
GPA takes this selection process seriously because the vendors chosen will
likely be a part of the GPA team for many years or decades to come.
Likewise, the chosen vendors will heavily influence the future of GPA
systems. It is imperative that GPA understands the direction bidders are
headed, their philosophies regarding industry research and application, and
specifically, who will be the best, long-term influence on GPA. Bidders should
provide as much detail as possible to provide GPA with a level of comfort
necessary to select the bidder’s product. Bidders may mark sections in their
proposals confidential to ensure trade secrets are not revealed outside GPA.
2.10.1 Applicable Research and Development. Bidders should describe research
and development (R&D) efforts their company is undertaking, projects their
company is working on, etc. that may be applicable or eventually enhance the
system GPA is fielding.
2.10.2 General Research and Development. Bidders should describe the R&D their
company undertakes annually and how product improvements or new
features that result from R&D are brought to customers such as GPA.
3/8/2016
Automated Terminal Asset Management System RFP
Page 29 of 110
3.0 PROPOSED WIRELESS LOCAL AREA NETWORK
The objective of this RFP is to procure a WLAN as described below. This WLAN shall
be the cornerstone for ATAMS as described in this document and will be used for data
communications between existing and future mobile data collection devices and host
business applications. Currently, as described, there is an existing, but limited, 802.11
wireless system on site. Existing narrow band equipment is expected to be replaced
over time with 802.11 equipment. The proposed WLAN will be required to facilitate
this transition as well as support the wireless container tracking system that is being
fielded as part of the overall ATAMS project.
Most bidders in the ATAMS project will propose devices that communicate over
802.11; however, there is the possibility that some bidders may propose systems that
are not 802.11 compatible. For the purpose of this RFP, GPA expects to field a
complete 802.11 system. However, bidders planning to propose non-802.11 systems
on subsequent RFP's within the ATAMS project should ensure that both a WLAN that
meets the limited needs of the current 802.11 equipment and a WLAN that
accommodates the proposed non-802.11 system are provided.
GPA is seeking a qualified vendor that will be responsible for the complete subsystem
proposed. The details provided in the RFP are the minimum project requirements.
The selected vendor shall provide a “turnkey” system. The omission of specific
reference to any software, hardware, training, materials, or labor necessary for such a
complete system shall not be interpreted as relieving the selected vendor from
furnishing such software, hardware, training materials, or labor under the proposal
quoted project price.
The WLAN should completely cover the existing GPA Garden City Terminal and
James D. Mason Inter-modal Facility. Existing and future site plans are included in
Figures 1 and 2 in the appendix. The proposal should include an option to add WLAN
capability to the areas marked FUTURE DEVELOPMENT in Figure 1.
The WLAN shall be capable of delivering wireless data communications services to
GPA authorized devices, as they occupy or roam throughout the Terminal and Intermodal Facility. WLAN service shall be provided to areas under canopies; however,
building interiors are not included in this RFP.
The selected vendor will be required to complete a high level Radio Frequency (RF)
site analysis for each proposed antenna location prior to purchasing any equipment.
The vendor will determine what signals are present in the area that are strong enough
to cause interference with the new WLAN. All findings shall be documented and
presented to GPA. Bidders must define and list the tasks required to complete the site
analysis in the RFP response. Site analyses completed within six (6) months prior to
release of this RFP will be acceptable at no cost to GPA.
The selected vendor will complete a final WLAN design to be approved by GPA staff
after the site analysis has been completed. Bidders shall propose the tasks needed to
complete the final design and provide a cost estimate for the recommended system
and the reasons why they chose the system to support the proposed project.
3/8/2016
Automated Terminal Asset Management System RFP
Page 31 of 110
The selected vendor will participate as a team member with GPA, NAVIS, LA King and
other subsystem vendors during the ATAMS installation process. During the process,
the selected vendor’s WLAN design may be modified. Bidders that do not wish to be
a team member should not submit a proposal.
3.1
System Description
GPA is seeking off the shelf equipment. Rather than define very specific criteria, GPA
will evaluate proposals based on the quality of the products and how well the product
design meets the needs for GPA. Therefore, the following questions are designed to
provide a method for evaluation. Each bidder has the opportunity to define other
criteria by which they may be judged and discussion regarding the superior attributes
of the proposed system is encouraged. Please respond as completely as possible to
the following questions. Do not respond by saying, "see attachment, addendum or
literature".
The evaluation team will consist of technical experts, operational personnel and
general managers. Bidders are encouraged to provide technical details regarding
system functionality to support detailed design evaluation as well as general laymen
definitions and explanations that easily define high-level concepts. Drawings, charts,
white papers and other graphical references (video clips, animations, screen shots,
etc.) are highly encouraged.
3.1.1
3/8/2016
General Description
Provide a detailed description of the proposed subsystem including a site
plan, a system design, an operating description, performance expectations,
and any operating characteristics that may be useful in the evaluation of the
subsystem. Then answer the following questions, even if redundant to the
system description.
3.1.1.1
Site Drawing. Provide a site drawing that identifies the location of
all remote equipment and antennas provided as part of the
proposed design including access points, wireless bridges and
controllers / switches.
3.1.1.2
Network Diagram. Provide a detailed network drawing that
represents all equipment in the response to this RFP, as well as
the connection to the existing LAN.
3.1.1.3
Technology. What WLAN technology is used and why was this
technology chosen to implement at GPA?
3.1.1.4
Equipment Label. What is the manufacturer's name, as well as
the model name, version number, and age of current version for
each type of equipment proposed and where will it be installed?
3.1.1.5
Software Version. What is the software level proposed for each
type of equipment?
Automated Terminal Asset Management System RFP
Page 32 of 110
3/8/2016
3.1.1.6
Network Interconnection. How does the system connect to the
local area network? Please provide specifics regarding
infrastructure required including any wireless backhaul included.
3.1.1.7
Equipment Performance Specifications. What are the
performance specifications for each piece of equipment
proposed? Include details that may provide an advantage over
other WLAN products.
3.1.1.8
Standards. What standards compliance such as the Institute of
Electrical and Electronics Engineers (IEEE) and Underwriters
Laboratories (UL) does the subsystem and components meet?
3.1.1.9
Permits. What Federal Communications Commission (FCC)
permits are required to operate the WLAN?
3.1.1.10
Location. Can the WLAN provide location information using
triangulation and/or time-of-arrival data? If so, to what accuracy
can this be done? Is this included in the proposal or is it an extra
charge to do so?
3.1.1.11
Multi-path. How does the WLAN overcome multi-path given
expected signal reflections in a container terminal environment?
3.1.1.12
Concurrent Connections. How many concurrent data connections
can each access point handle? This discussion should include
information regarding the client association database and the rate
at which the access point can associate and authenticate signals.
3.1.1.13
Quality of Service Priorities. How many Quality of Service (QoS)
priorities are available? What attributes can be used to classify
traffic flows?
3.1.1.14
Protocols. What networking protocols are supported?
3.1.1.15
Distance and Range. What is the maximum distance in feet from
the access point where data rates of 54 Mbps and 11 Mbps can
be achieved?
3.1.1.16
Equipment Amounts. How many of the following items will be
required to implement the proposed subsystem: access points,
wireless bridges, controllers / switches?
3.1.1.17
Bandwidth. Do the access points support 802.11a,b/g? (Specify
all that apply to this system)
3.1.1.18
QoS Support. Does the system support QoS for data, voice and
video?
Automated Terminal Asset Management System RFP
Page 33 of 110
3.1.2
3/8/2016
3.1.1.19
Single Channel Transmissions. Can voice and data be
transmitted on the same channel?
3.1.1.20
Concurrent Users. How many concurrent users can be supported
on each access point assuming each user is using the connection
for Internet access?
3.1.1.21
Total System Users. How many concurrent data users can the
entire system support?
3.1.1.22
Range. What is the access point’s typical range as measured in
feet from the access point to the wireless device?
3.1.1.23
Data Rates. Assuming there are 30 concurrent data users
connected to a single access point using WiFi Protected Access
(WPA), what is the maximum data transfer rate that can be
obtained?
3.1.1.24
Special Features. Please state any special or proprietary features
regarding the proposed system that separates it from other bidder
offerings.
Operations and System Management
In this section, bidders shall discuss in detail the capabilities of the proposed
systems and describe the operations methodology.
3.1.2.1
Operator Interface. What data entry or operator interface is
required to operate the system?
3.1.2.2
Calibration. How is the WLAN calibrated? How does the WLAN
equipment know when its accuracy is not up to standard? Is an
alert generated when this occurs?
3.1.2.3
Equipment Mounting. If any equipment shall be mounted to
mobile equipment, describe the mounting process? What
amount of time is required per vehicle? What design
considerations have been given to reduce vehicle-mounting time?
3.1.2.4
Reporting Events. List all events or actions that will generate a
message to the network operating system.
3.1.2.5
Reporting Functions. What reporting functions are available from
the proposed subsystem? Please provide screen shots of any
significant monitoring, reporting or management tools.
3.1.2.6
Network Availability. Describe what software and hardware will be
needed in the office systems to view subsystem status or review
reports on local desktop computers.
Automated Terminal Asset Management System RFP
Page 34 of 110
3/8/2016
3.1.2.7
Reporting Tools. Does the proposed system easily integrate with
standard office reporting tools such as Excel or other report
generation tools?
3.1.2.8
Report Generation. Are the reports generated from a central
management system or through the network operating system?
3.1.2.9
Remote Status Check. Can transmitter, receiver and other
remote equipment status and availability be checked remotely?
3.1.2.10
Special Operations Tools. What special tools are required to
operate the subsystem?
3.1.2.11
Alert Capabilities. Can the proposed system send email, pager or
other notification of failures or potential network attacks?
3.1.2.12
Report Generation. Are the reports generated from a central
management interface or from each individual access point?
3.1.2.13
Managed Access. Does the proposed solution use configurable,
managed access points or “dumb” access points with a WLAN
switch for management and control?
3.1.2.14
Channel Management. Will the access points require channel
management and detailed RF site surveys for implementation?
3.1.2.15
Power Over Ethernet. Can the access points be powered via
power over Ethernet? If not, what are the power requirements?
3.1.2.16
Management. Are the access points managed from a central
location or are they managed individually?
3.1.2.17
Channel Assignment. Is channel assignment on each access
point an automatic or manual process?
3.1.2.18
Shutdown. Can the access points be shutdown via a Graphical
User Interface (GUI)?
3.1.2.19
Shutdown Location. Can all access points be shutdown from a
single management screen or is it necessary to visit a separate
screen for each access point?
3.1.2.20
QoS Limits. Does the proposed solution provide over the air QoS
for uplink and downlink traffic and can it detect traffic types to
apply QoS policies by application?
3.1.2.21
Hand-off. Describe the hand-off process from access point to
access point as mobile clients roam. Is there a delay while the
hand-off takes place? If there is a delay, how long will it be? Is
the client forced to re-associate and obtain a new Internet
Automated Terminal Asset Management System RFP
Page 35 of 110
Protocol (IP) address or does it retain the same address? Where
is the association taking place: at the domain controller or some
WLAN controller?
3/8/2016
3.1.2.22
Connectivity Limits. The GPA operates over 400 vehicles within
the coverage site. Describe the system’s capability of
maintaining connectivity at speeds up to 40 mph.
3.1.2.23
Seamless Roaming. If the system provides seamless roaming,
please provide a brief technical description of how this is
accomplished.
3.1.2.24
Virtual Private Network (VPN) Roaming. If the system provides
seamless roaming, can it maintain these connections even if a
user is connected using a VPN or IPSec tunnel?
3.1.2.25
Bandwidth Limits. Can the system be configured to limit the
amount of bandwidth available for each Virtual Local Area
Network (VLAN)?
3.1.2.26
VLAN Volume. How many VLAN’s are supported per access
point?
3.1.2.27
VLAN Controller. If applicable, how many VLAN’s are supported
per controller?
3.1.2.28
VLAN Shutdown. Can an entire VLAN be shutdown from a single
management screen so that all access points will disallow
connections to this VLAN?
3.1.2.29
Upgrades. Is the access point capable of being upgraded to
future standards such as 802.11n via firmware/software updates
or will the access point need to be replaced when future
standards are ratified?
3.1.2.30
Voice Over IP (VOIP) Capability. Will the proposed system have
voice or VOIP capability in the future? Will the proposed system
provide this capability today?
3.1.2.31
Concurrent VOIP. How many concurrent VOIP users can each
access point handle?
3.1.2.32
Total VOIP Volume. How many concurrent VOIP calls can the
entire system support?
3.1.2.33
Video Streaming. Will the proposed system be capable of
streaming live video feeds in the future? Will the proposed
system provide this capability today?
Automated Terminal Asset Management System RFP
Page 36 of 110
3.1.3
3/8/2016
3.1.2.34
Expand Coverage. What is required to expand coverage into a
new operating area?
3.1.2.35
Battery Life. If the proposed subsystem includes battery operated
equipment (where the battery is the primary source of power),
what is the average battery life of the device? What procedures
are generally used to monitor replacement?
Security, Survivability and Susceptibility
In this section, bidders shall discuss the proposed system’s vulnerabilities to
outside occurrence, both manmade and natural. Furthermore, the bidder
should provide details regarding any system design or other actions taken to
increase the subsystem’s resistance to outside threats.
3.1.3.1
Painting. Can the outdoor components of the system be painted
for safety or visibility?
3.1.3.2
Outdoor Conditions. The outdoor installed equipment must be
designed for outdoor use. Equipment will be subjected to high
winds (including hurricane force winds), rain, sun, heat and cold.
Is the proposed system designed for continuous outdoor use?
What weather ratings does the equipment carry? Describe the
conditions under which the system will continue to operate
without degradation.
3.1.3.3
Temperature & Humidity. What are the minimum and maximum
temperature and humidity ratings for each device proposed?
3.1.3.4
Wind Ratings. What is the wind survivability rating for each
access point and any other outdoor installed equipment
3.1.3.5
Cell Phone Interference. Will the operation of a cell phone tower
located in the terminal interfere with the subsystem?
3.1.3.6
Shock Tolerance. For vehicle-mounted equipment, how much
shock can the devices withstand and continue to operate
normally?
3.1.3.7
Electrical Interference. How is the subsystem protected from
electrical interference?
3.1.3.8
Spoofing. What steps have been taken in the system design,
hardware or software, to prevent spoofing or service denial
attacks?
3.1.3.9
Authentication Standards. What authentication standards are
supported with the proposed WLAN?
Automated Terminal Asset Management System RFP
Page 37 of 110
3.1.4
3.1.5
3.1.3.10
Encryption Standards. What encryption standards are supported
with the proposed WLAN?
3.1.3.11
Rogue Access. What actions can the system take if it detects a
rogue access point?
3.1.3.12
Rogue Detection. Can the access points be used as rogue
detection devices as well as access points? If so, can this
feature be scheduled to occur at predetermined or scheduled
times?
3.1.3.13
Intrusion Detection. Does the proposed system employ any
intrusion detection or protection mechanisms?
3.1.3.14
RADIUS. What integrated server does the proposed subsystem
support, such as RADIUS?
Reliability
Bidders shall provide evidence that the proposed subsystem is reliable under
the conditions expected to be encountered in Savannah, Georgia. Actual
data from other installations is preferred. Where actual data cannot be
obtained, simulations, tests or manufacturers’ data can be used instead,
albeit at a lower degree of confidence.
3.1.4.1
Mean Time Between Failure (MTBF). What is the MTBF for each
type of equipment proposed?
3.1.4.2
Fault Detection. How are component level faults detected and
reported?
3.1.4.3
Single Point Failures. Identify all single point failures in the
proposed design and indicate what can be done, and the cost for
such, to eliminate the single point failure.
3.1.4.4
Component Failures. On the bidder’s currently installed systems,
what subsystem component fails most frequently? How often
does the component fail? Describe the conditions under which
the component is most likely to fail.
Maintainability
GPA is not prepared to field a system that increases maintenance costs
significantly or one that cannot be maintained. Bidders shall demonstrate a
practical knowledge of maintenance regarding the subsystems proposed.
Again, actual data is preferred.
3.1.5.1
3/8/2016
Periodic Upgrades. Does the WLAN subsystem require periodic
code or firmware upgrades? If so, how are these upgrades
deployed? How often does the manufacturer release the
upgrades?
Automated Terminal Asset Management System RFP
Page 38 of 110
3.1.5.2
Remote Configuration Upgrades. Can the on-board system
configuration be updated remotely from the host?
3.1.5.3
Remote Software Upgrades. Can the remote equipment firmware
/ software be updated remotely from the host?
3.1.5.4
Scheduled Shutdowns. Can the access points be pre-scheduled
to shutdown? If so, how far in advance can the schedule be
setup?
3.1.5.5
Single Channel. Will the access points be able to run on a single
channel?
3.1.5.6
Support Tools. Does the subsystem offer any IT support tools to
facilitate troubleshooting or problem resolution?
3.1.5.7
Diagnostics. What diagnostic features are available? Does the
subsystem have Built-in-Test (BIT)?
3.1.5.8
Mean Time to Repair or Replace (MTRR). What is the MTRR for
each type of equipment included in the subsystem design?
3.1.5.9
Hardware Support. How long from the date of acceptance by
GPA will the manufacturer provide hardware support for each
device in the proposed subsystem?
3.1.5.10
Software Support. How long from the date of acceptance by GPA
will the manufacturer provide software or firmware support for
each device in the proposed subsystem?
3.1.5.11
Manufacturer Warranty Period. What is the manufacturers’
warranty period for each type of equipment proposed?
3.1.5.12
Subsystem Warranty Period. What is the warranty period for the
entire subsystem following acceptance by GPA?
3.1.5.13
Support Levels. What levels of service / support contracts are
available for the system?
3.1.5.14
Maintenance Tools. What special tools are required to maintain
the system?
3.1.5.15
Equipment Sizes. What is the physical size (in inches) and weight
(in pounds) for each type of equipment in the proposed system?
3.1.6
Logistic Supportability
In this section, bidders should respond to section 2.9.
3.1.7
Research and Development / Future Capabilities
In this section, bidders should respond to section 2.10.
3/8/2016
Automated Terminal Asset Management System RFP
Page 39 of 110
3/8/2016
Automated Terminal Asset Management System RFP
Page 40 of 110
4.0 PROPOSED OPTICAL CHARACER RECOGNITION SYSTEM
The objective of this RFP is to procure an OCR system that can automatically identify
the below listed equipment and correlate the results with data supplied by other
subsystems such as RFID, NAVIS, PDS and others at truck entry and exit gates 3, 4
and 6. The system will have access to the truck transaction table in NAVIS that allows
comparison of the recognized image to containers and chassis expected to enter the
terminal gates. The functionality required of the system includes reading the following
identification markings even while vehicles are in motion:

Container Number, Size Code, and International Maritime Organization (IMO)
Label

Chassis Number

GenSet Number for container nose-mounted and chassis under-mounted
GenSets
The OCR portals are a significant part of ATAMS as described in this document. GPA
is seeking a qualified vendor who will be responsible for the complete subsystem
proposed. The proposal must address any required infrastructure such as a
mounting system, cameras, illumination, canopies, detection systems, and back office
equipment. The proposal shall also include options described in section 7.10.
The details provided in this RFP are the minimum project requirements. The selected
vendor shall provide a “turnkey” system. The omission of specific reference to any
software, hardware, training, materials, or labor necessary for such a complete system
shall not be interpreted as relieving the selected vendor from furnishing such software,
hardware, training materials, or labor under the proposal quoted project price.
Bidders are required to complete a site plan analysis to determine the location and
number of OCR gates required to screen the trucks in a timely manner and maintain
the required reliability and identification accuracy rates. All findings shall be
documented and presented in their proposal.
The selected vendor will participate as a team member with GPA, NAVIS, LA King
and other subsystem vendors to review the total system and finalize the ATAMS
design. During this process, the selected vendor’s OCR subsystem design may be
modified. Bidders that do not wish to be a team member should not submit a
proposal.
4.1
System Description
GPA is seeking off the shelf equipment. Rather than designing to very specific
criteria, GPA will evaluate proposals based on the quality of the products and how well
the product design meets the needs for GPA. Therefore, the following questions are
designed to provide a method for evaluation. Each bidder has the opportunity to
define other criteria by which they may be judged and discussion regarding the
superior attributes of the proposed system is encouraged. Please respond as
3/8/2016
Automated Terminal Asset Management System RFP
Page 41 of 110
completely as possible to the following questions. Do not respond by saying: "see
attachment, addendum or literature".
The evaluation team will consist of technical experts, operational personnel and
general managers. Bidders are encouraged to provide technical details regarding
system functionality to support detailed design evaluation as well as general laymen
definitions and explanations that easily define high-level concepts. Drawings, charts,
white papers and other graphical references (video clips, animations, screen shots,
etc.) are highly encouraged.
4.1.1
3/8/2016
General Description
Provide a detailed description of the proposed subsystem including a site
plan, a system design, an operating description, performance expectations,
and any operating characteristics that may be useful in the evaluation of the
subsystem. Then answer the following questions, even if redundant to the
system description.
4.1.1.1
Site Drawing. Provide a site drawing that identifies where the
OCR gates shall be placed. Indicate truck turning radius, speeds,
speed bumps or other methods used to sequence vehicles and
provide an optimal OCR read. Also, identify the dimensions of
the lanes and number of gates needed.
4.1.1.2
Network Design. Provide a detailed network drawing that
represents all equipment in the response to this RFP, as well as
the connection to the existing Local Area Network (LAN).
4.1.1.3
Equipment Label. What is the manufacturer's name, as well as
the model name, version number, and age of current version for
each type of equipment proposed and where will it be installed?
4.1.1.4
Operating System. What is the operating system of the OCR
server?
4.1.1.5
Software Version. What is the software level proposed for each
type of equipment?
4.1.1.6
Equipment Performance Specifications. What are the
performance specifications for each piece of equipment
proposed? Include details that may provide an advantage over
other OCR products.
4.1.1.7
Sun Spots. How does the proposed design deal with the effects
of bright sun or darkness on the camera system, such as glare
from the container?
4.1.1.8
Illumination. Is any illumination used? If so, what kind?
Automated Terminal Asset Management System RFP
Page 42 of 110
3/8/2016
4.1.1.9
Integration. Does your design integrate with NAVIS and/or LA
King? Please describe the method of integration.
4.1.1.10
Standards. What standards compliance such as IEEE or UL does
the system and components meet?
4.1.1.11
Technology. What camera technology is used and why was the
technology chosen to implement at GPA?
4.1.1.12
Number of Cameras. How many cameras will be required on
each lane to implement the proposed system?
4.1.1.13
Cameras. Describe the views and purpose of each cameral in an
OCR portal.
4.1.1.14
Existing Cameras. Can existing GPA cameras be used as part of
the OCR system?
4.1.1.15
Belly Camera. Does the system include a belly camera? Can the
system inspect the undercarriage and dolly legs with a belly
camera?
4.1.1.16
Auto Focus. Does the camera system automatically tilt, zoom and
focus to the desired part of the container, chassis or GenSet for a
manual read when an automatic read is incomplete?
4.1.1.17
Flat Tires. Can the system detect flat tires on the truck or
chassis?
4.1.1.18
Read Time. How many trucks can be processed in one OCR lane
per hour?
4.1.1.19
ID Requirements. Define the physical ID requirements (format,
font, contrast, etc.) to meet the required read accuracy rate.
4.1.1.20
Read Accuracy Rate. What is the proposed system’s read
accuracy rate by type of item being read (container, chassis,
GenSet, etc.)? Does this accuracy change when the truck
transaction data is available? If so, provide accuracy rates with
and without the truck transaction data.
4.1.1.21
Container Length Measurement. Are container lengths
automatically measured by the system? If so, describe how this
works and to what accuracy?
4.1.1.22
Misread Correction. Is the proposed system capable of
completing a misread (correctly) using truck transaction data? If
so, how is this accomplished?
Automated Terminal Asset Management System RFP
Page 43 of 110
4.1.2
3/8/2016
4.1.1.23
OCR Trigger. How does the proposed system recognize that a
truck / container has arrived at the gate for an OCR read?
4.1.1.24
Special Features. Please state any special or proprietary features
regarding the proposed system that separates it from other bidder
offerings.
Operations and System Management
In this section, bidders shall discuss in detail the capabilities of the proposed
systems and describe the operations methodology.
4.1.2.1
Truck Speed. What is the maximum speed a truck can travel and
allow the proposed system to get an accurate read?
4.1.2.2
Processing Time. How long does it take the proposed system to
get a complete scan, process the OCR and transfer that data to
NAVIS/LA King? Be specific regarding each step.
4.1.2.3
Truck Spacing. How much time must pass from the time one
truck completes its pass through the OCR portal until the next
truck can start through the portal?
4.1.2.4
Reporting Events. List all events or actions that will generate an
OCR message to the Terminal Operating System (TOS).
4.1.2.5
TOS Integration. Describe the integration between the OCR
system and the TOS? Discuss what information is being passed
and in which direction, what format is used, etc.
4.1.2.6
Reporting Functions. What reporting functions are available from
the proposed subsystem? Please provide screen shots of any
significant monitoring, reporting or management tools.
4.1.2.7
Report Generation. Are the reports generated from a central
management system or through NAVIS or some other data
system?
4.1.2.8
Control. Can the subsystem be controlled over the network? At
any workstation?
4.1.2.9
Operator Interface. What data entry or operator interface is
required to operate the system?
4.1.2.10
Network Operations. Describe what software and hardware will
be needed in the office systems to view OCR activities or review
reports on local desktop computers.
Automated Terminal Asset Management System RFP
Page 44 of 110
3/8/2016
4.1.2.11
Reporting Tools. Does your system integrate easily with standard
office reporting tools such as Excel or other report generation
tools?
4.1.2.12
Data Storage. How is the data stored? Does the data include
actual images? Answers should include various levels of data
including active data, archived data, etc.
4.1.2.13
Data Storage. Are the pictures and evaluations stored in a usable
file for future reference?
4.1.2.14
Image Playback. Is there any capability to playback images? If
so, what software is required?
4.1.2.15
Image Resolution. What is the resolution of the images captured?
4.1.2.16
Image Size. How large (in MB) are the image files?
4.1.2.17
Special Operations Tools. What special tools are required to
operate the system?
4.1.2.18
Alert Capabilities. Can the proposed subsystem send email,
pager or other notification of failures or alerts?
4.1.2.19
Battery Life. If the proposed system includes battery operated
equipment (where the battery is the primary source of power),
what is the average battery life of the device? What procedures
are generally used to monitor replacement?
4.1.2.20
Calibration. How is the OCR subsystem calibrated? How does
the PDS know when its accuracy is not up to standard? Is an
alert generated when this occurs?
4.1.2.21
Temporary TOS Loss. Does the OCR subsystem capture all
container move information regardless of whether it has a current
connection to the TOS / Server?
4.1.2.22
Minimum Availability. What is the minimum availability of the
subsystem?
4.1.2.23
Equipment Mounting. Describe the equipment mounting in
vehicles? What amount of time is required per vehicle? What
design considerations have been given to reduce vehiclemounting time and to allow for the connection and integration of
additional subsystems such as monitoring equipment?
4.1.2.24
Data Transfer. Provide the steps and the amount of time per step
required to transfer data from an end user to the TOS.
Automated Terminal Asset Management System RFP
Page 45 of 110
4.1.3
4.1.4
3/8/2016
Security, Survivability and Susceptibility
In this section, bidders shall discuss the proposed system’s vulnerabilities to
outside occurrence, both manmade and natural. Furthermore, the bidder
should provide details regarding any system design or other actions taken to
increase the subsystem’s resistance to outside threats.
4.1.3.1
Painting. Can the outdoor components of the system be painted
for safety or visibility?
4.1.3.2
Outdoor Conditions. The outdoor installed equipment must be
designed for outdoor use. Equipment will be subjected to high
winds (including hurricane force winds), rain, sun, heat and cold.
Is the proposed system designed for continuous outdoor use?
What weather ratings does the equipment carry? Describe the
conditions under which the system will continue to operate
without degradation.
4.1.3.3
Temperature & Humidity. What are the minimum and maximum
temperature and humidity ratings for each device proposed?
4.1.3.4
Cell Phone Interference. Will the operation of a cell phone tower
located in the terminal interfere with the subsystem?
4.1.3.5
Shock Tolerance. How much shock can the devices withstand
and continue to operate normally?
Reliability
Bidders shall provide evidence that the proposed subsystem is reliable under
the conditions expected to be encountered in Savannah, Georgia. Actual
data from other installations is preferred. Where actual data cannot be
obtained, simulations, tests or manufacturers’ data can be used instead,
albeit at a lower degree of confidence.
4.1.4.1
Mean Time Between Failure (MTBF). What is the MTBF for each
type of equipment proposed?
4.1.4.2
Fault Detection. How are component level faults detected and
reported?
4.1.4.3
Single Point Failures. Identify all single point failures in the
proposed design and indicate what can be done, and the cost for
such, to eliminate the single point failure.
4.1.4.4
Component Failures. On the bidder’s currently installed systems,
what subsystem component fails most frequently? How often
does the component fail? Describe the conditions under which
the component is most likely to fail.
Automated Terminal Asset Management System RFP
Page 46 of 110
4.1.5
3/8/2016
Maintainability
GPA is not prepared to field a system that increases maintenance costs
significantly or one that cannot be maintained. Bidders shall demonstrate a
practical knowledge of maintenance regarding the subsystems proposed.
Again, actual data is preferred.
4.1.5.1
Periodic Upgrades. Does the camera system require periodic
code or firmware upgrades? If so, how are these upgrades
deployed? How often does the manufacturer release the
upgrades?
4.1.5.2
Remote Configuration Upgrades. Can the on-board system
configuration be updated remotely from the host?
4.1.5.3
Support Tools. Does the system offer any IT support tools to
facilitate troubleshooting or problem resolution?
4.1.5.4
Diagnostics. What diagnostic features are available? Does the
system have Build-in-Test (BIT)?
4.1.5.5
Subsystem Warranty Period. What is the warranty period for the
subsystem following acceptance by GPA?
4.1.5.6
Hardware Support. How long from the date of acceptance by
GPA will the manufacturer provide hardware support for each
device in the proposed subsystem?
4.1.5.7
Software Support. How long from the date of acceptance by GPA
will the manufacturer provide software or firmware support for
each device in the proposed subsystem?
4.1.5.8
Mean Time to Repair or Replace (MTRR). What is the MTRR for
each type of equipment included in the subsystem design?
4.1.5.9
Manufacturer Warranty Period. What is the warranty period for
each type of equipment proposed?
4.1.5.10
Subsystem Warranty Period. What is the warranty period for the
entire subsystem following acceptance by GPA?
4.1.5.11
Support Levels. What levels of service / support contracts are
available for the system?
4.1.5.12
Maintenance Tools. What special tools are required to maintain
the system?
4.1.5.13
Equipment Sizes. What is the physical size (in inches) and weight
(in pounds) for each type of equipment in the proposed system?
Automated Terminal Asset Management System RFP
Page 47 of 110
4.1.6
Logistic Supportability
In this section, bidders should respond to section 2.9.
4.1.7
Research and Development / Future Capabilities
In this section, bidders should respond to section 2.10.
3/8/2016
Automated Terminal Asset Management System RFP
Page 48 of 110
5.0 PROPOSED RADIO FREQUENCY IDENTIFICATION SYSTEM
The objective of this RFP is to procure an RFID system that can automatically identify
trucks and correlate the results with data supplied by other subsystems such as OCR,
NAVIS, PDS and others at truck entry and exit gates 3, 4 and 6, and at the cranes,
RTG’s and top lifters.
The RFID readers are a significant part of ATAMS as described in this document.
GPA is seeking a qualified vendor who will be responsible for the complete subsystem
proposed. The proposal must address any required infrastructure such as a mounting
system, readers/antennas, tags, canopies, detection systems, and back office
equipment. The proposal shall also include options described in section 7.10, if the
bidder is capable.
The details provided in this RFP are the minimum project requirements. The selected
vendor shall provide a “turnkey” system. The omission of specific reference to any
software, hardware, training, materials, or labor necessary for such a complete system
shall not be interpreted as relieving the selected vendor from furnishing such software,
hardware, training materials, or labor under the proposal quoted project price.
Bidders are required to complete a site plan analysis to determine the location and
number of RFID readers required to screen the trucks in a timely manner and maintain
the required reliability and identification accuracy rates. All findings shall be
documented and presented in the bidder’s proposal.
The selected vendor will participate as a team member with GPA, NAVIS, LA King
and other subsystem vendors to review the total system and finalize the ATAMS
design. During this process, the selected vendor’s RFID subsystem design may be
modified. Bidders that do not wish to be a team member should not submit a proposal.
5.1
System Description
GPA is seeking off the shelf equipment. Rather than designing to very specific
criteria, GPA will evaluate proposals based on the quality of the products and how well
the product design meets the needs for GPA. Therefore, the following questions are
designed to provide a method for evaluation. Each bidder has the opportunity to
define other criteria by which they may be judged and discussion regarding the
superior attributes of the proposed system is encouraged. Please respond as
completely as possible to the following questions. Do not respond by saying: "see
attachment, addendum or literature".
The evaluation team will consist of technical experts, operational personnel and
general managers. Bidders are encouraged to provide technical details regarding
system functionality to support detailed design evaluation as well as general laymen
definitions and explanations that easily define high-level concepts. Drawings, charts,
white papers and other graphical references (video clips, animations, screen shots,
etc.) are highly encouraged.
5.1.1
3/8/2016
General Description
Automated Terminal Asset Management System RFP
Page 49 of 110
Provide a detailed description of the proposed subsystem including a site
plan, a system design, an operating description, performance expectations,
and any operating characteristics that may be useful in the evaluation of the
subsystem. Then answer the following questions, even if redundant to the
system description.
3/8/2016
5.1.1.1
Site Drawing. Provide a site drawing that identifies where the
RFID readers shall be placed. Indicate truck turning radius,
speeds, speed bumps or other methods used to sequence
vehicles and provide an optimal RFID read.
5.1.1.2
Network Design. Provide a detailed network drawing that
represents all equipment in the response to this RFP, as well as
the connection to the existing LAN.
5.1.1.3
Equipment Label. What is the manufacturer's name, as well as
the model name, version number, and age of current version for
each type of equipment proposed and where will it be installed?
5.1.1.4
Operating System. What is the operating system of the RFID
server?
5.1.1.5
Software Version. What is the software level proposed for each
type of equipment?
5.1.1.6
Equipment Performance Specifications. What are the
performance specifications for each piece of equipment
proposed? Include details that may provide an advantage over
other RFID products.
5.1.1.7
Integration. Does the proposed design integrate with NAVIS
and/or LA King? Please describe the method of integration.
5.1.1.8
Standards. What standards compliance such as IEEE and UL
does the subsystem and components meet?
5.1.1.9
Air Interface Protocol. Is the air interface protocol a proprietary or
open standards system?
5.1.1.10
Technology. What RFID technology is used and why was this
technology chosen to implement at GPA?
5.1.1.11
Tags. Does your design use active or passive tags? If active tags
are used, how do you propose replacing the battery on trucks and
how often must the batteries be replaced?
5.1.1.12
Tag Frequency. At what frequency do the tags and readers
operate? Are these proprietary frequencies or unrestricted
frequencies?
Automated Terminal Asset Management System RFP
Page 50 of 110
3/8/2016
5.1.1.13
Tag Life. How long will the RFID tag last before it must be
replaced?
5.1.1.14
Information. What information is stored on the tags and read by
the RFID reader? Can this information be modified?
5.1.1.15
Re-writable Tags. Is the tag re-writable on the fly? In other words
can GPA reprogram a tag as a truck goes through a gate? Is
there a need for this in the system design?
5.1.1.16
Data Retention. How long can the tag retain stored data?
5.1.1.17
Transfer Rate. What is the data transfer rate on the tags? How
long does it take a reader to read and properly identigy the tags?
5.1.1.18
Processing Time. How many trucks can be processed in one
RFID lane per hour?
5.1.1.19
Read Accuracy Rate. What is the proposed system’s read
accuracy rate? Does this accuracy change when the truck
transaction data is available? If so, provide accuracy rates with
and without the truck transaction data.
5.1.1.20
Good Read Rate. What percentage of tags are read and read
properly the first time (on a truck moving through the gate)?
5.1.1.21
Bad Read Rate. What percentage of tags is read improperly?
What percentage of tags is not read at all?
5.1.1.22
Checksum. What form of checksum is used to verify the data
received from an RFID tag?
5.1.1.23
Null Spot. How does the system reduce the effects of the null
spot?
5.1.1.24
Antenna Orientation. How has the orientation of the antennas
been optimized to maximize the performance of the RFID
system?
5.1.1.25
Concentrator. Does the proposed design use some form of
concentrator? If so, how does this affect the operation of the
RFID subsystem?
5.1.1.26
Tag Authentication. Is there any method of authentication used
when reading tags?
Automated Terminal Asset Management System RFP
Page 51 of 110
5.1.2
3/8/2016
5.1.1.27
Arrival Notice. How does the proposed system recognize that a
truck has arrived at the gate for an RFID read?
5.1.1.28
Always On. Are the readers always on or do proximity sensors
turn them on?
5.1.1.29
Special Features. Please state any special or proprietary features
regarding the proposed system that separates it from other bidder
offerings.
Operations and System Management
In this section, bidders shall discuss in detail the capabilities of the proposed
systems and describe the operations methodology.
5.1.2.1
Tag in Motion. Can the readers ID a tag while a truck is in
motion? What is the maximum speed at which a truck can travel
and still be identified?
5.1.2.2
Read Range. At what distance (read range) can the tag be read
by the proposed readers?
5.1.2.3
Lane Selection. How can it be verified that the tag that is read
from a truck in a particular lane is actually in that lane and not in
another lane?
5.1.2.4
Tag Interference. Will tags from other sources interfere with GPA
tag readers?
5.1.2.5
Multiple Tags. Can trucks have multiple tags and can the reader
distinguish between the different tags?
5.1.2.6
Tag Commissioning. How are the tags commissioned when given
to truckers?
5.1.2.7
Tag Mount. Where must the tag be mounted on the truck? Can
tags be on the inside of the windshield? What are the restrictions
regarding how the tags can be mounted to the vehicle?
5.1.2.8
Operator Interface. What data entry or operator interface is
required to operate the system?
5.1.2.9
Location Algorithms. Can the RFID system be used to locate
vehicles using methods such as triangulation or signal strength?
5.1.2.10
Read Time. How long does it take the system to get a complete
scan, process the RFID read and transfer that data to NAVIS/LA
King? Be specific regarding each step.
Automated Terminal Asset Management System RFP
Page 52 of 110
3/8/2016
5.1.2.11
Reporting Events. List all actions that will generate an RFID
message to the TOS.
5.1.2.12
TOS Integration. Describe the integration between the RFID
system and the TOS? Discuss what information is being passed
and in what direction, what format is used, etc.
5.1.2.13
Reporting Functions. What reporting functions are available from
the proposed subsystem? Please provide screen shots of any
significant monitoring, reporting or management tools.
5.1.2.14
Report Generation. Are the reports generated from a central
management system or through NAVIS or some other data
system?
5.1.2.15
Control. Can the subsystem be controlled over the network? At
any station?
5.1.2.16
Network Systems. Describe what software and hardware will be
needed in the office systems to view RFID activities or review
reports on local desktop computers.
5.1.2.17
Reporting Tools. Does the proposed system integrate easily with
standard office reporting tools such as Excel or other report
generation tools?
5.1.2.18
Data Storage. How is the data stored and what is the retrieval
process? Answer should include various levels of data such as
archive data, active data, etc.
5.1.2.19
Calibration. How is the RFID subsystem calibrated? How does
the RFID subsystem know when its accuracy is not up to
standard? Is an alert generated when this occurs?
5.1.2.20
Special Operations Tools. What special tools are required to
operate the proposed system?
5.1.2.21
Minimum Availability. What is the minimum availability of the
subsystem?
5.1.2.22
Temporary TOS Loss. Does the RFID subsystem capture all Tag
ID information regardless of whether it has a current connection
to the TOS / Server?
5.1.2.23
Equipment Mounting. Describe the procedure for mounting
equipment in vehicles? How much time is required per vehicle
for equipment mounting? What design considerations have been
given to reduce vehicle-mounting time and to allow for the
Automated Terminal Asset Management System RFP
Page 53 of 110
connection and integration of additional subsystems such as
monitoring equipment?
5.1.3
5.1.4
3/8/2016
5.1.2.24
Data Transfer. Provide the steps and the amount of time per step
required to transfer data from an end user to the TOS.
5.1.2.25
Alert Capabilities. Can the proposed subsystem send email,
pager or other notification of failures or alerts?
5.1.2.26
Battery Life. If the proposed system includes operated equipment
(where the battery is the primary source of power), what is the
average battery life of the device? What procedures are
generally used to monitor replacement?
Security, Survivability and Susceptibility
In this section, bidders shall discuss the proposed system’s vulnerabilities to
outside occurrence, both manmade and natural. Furthermore, the bidder
should provide details regarding any system design or other actions taken to
increase the subsystem’s resistance to outside threats.
5.1.3.1
Painting. Can the outdoor components of the system be painted
for safety or visibility?
5.1.3.2
Outdoor Conditions. The outdoor installed equipment must be
designed for outdoor use. Equipment will be subjected to high
winds (including hurricane force winds), rain, sun, heat and cold.
Is the proposed system designed for continuous outdoor use?
What weather ratings does the equipment carry? Describe the
conditions under which the system will continue to operate
without degradation.
5.1.3.3
Temperature & Humidity. What are the minimum and maximum
temperature and humidity ratings for each device proposed?
5.1.3.4
Shock Tolerance. How much shock can the mobile equipment
mounted devices withstand and continue to operate normally?
5.1.3.5
Cell Phone Interference. Will the operation of a cell phone tower
located in the terminal interfere with the subsystem?
5.1.3.6
Spoofing. Can a reader be spoofed or can a reader be prevented
from reading a tag? What functionality is designed into the
system to prevent this from occurring?
Reliability
Bidders shall provide evidence that the proposed subsystem is reliable under
the conditions expected to be encountered in Savannah, Georgia. Actual
data from other installations is preferred. Where actual data cannot be
Automated Terminal Asset Management System RFP
Page 54 of 110
obtained, simulations, tests or manufacturers’ data can be used instead,
albeit at a lower degree of confidence.
5.1.5
3/8/2016
5.1.4.1
Mean Time Between Failure (MTBF). What is the MTBF for each
type of equipment proposed?
5.1.4.2
Fault Detection. How are component level faults detected and
reported?
5.1.4.3
Single Point Failures. Identify all single point failures in the
proposed design and indicate what can be done, and the cost for
such, to eliminate the single point failure.
5.1.4.4
Component Failures. On the bidder’s currently installed systems,
what system component fails most frequently? How often does
the component fail? Describe the conditions under which the
component is most likely to fail.
Maintainability
GPA is not prepared to field a system that increases maintenance costs
significantly or one that cannot be maintained. Bidders shall demonstrate a
practical knowledge of maintenance regarding the subsystems proposed.
Again, actual data is preferred.
5.1.5.1
Obsolescence. Since the RFID industry is rapidly changing and
standards are still being resolved, what design characteristics will
prevent the proposed system from being obsolete within a few
years? What guarantees do you have that the tags or readers in
use will still be available in a few years?
5.1.5.2
Periodic Upgrades. Does the RFID system require periodic code
or firmware upgrades? If so, how are these upgrades deployed?
How often does the manufacturer release the upgrades?
5.1.5.3
Remote Configuration Upgrades. Can the on-board system
configuration be updated remotely from the host?
5.1.5.4
Support Tools. Does the system offer any IT support tools to
facilitate troubleshooting or problem resolution?
5.1.5.5
Mean Time to Repair or Replace (MTRR). What is the MTRR for
each type of equipment included in the subsystem design?
5.1.5.6
Diagnostics. What diagnostic features are available? Does the
system have Built-in-Test (BIT)?
5.1.5.7
Hardware Support. How long from the date of acceptance by
GPA will the manufacturer provide hardware support for each
device in the proposed subsystem?
Automated Terminal Asset Management System RFP
Page 55 of 110
5.1.5.8
Software Support. How long from the date of acceptance by GPA
will the manufacturer provide software or firmware support for the
proposed subsystem?
5.1.5.9
Manufacturer Warranty Period. What is the warranty period for
each type of equipment proposed?
5.1.5.10
Subsystem Warranty Period. What is the warranty period for the
subsystem following acceptance by GPA?
5.1.5.11
Support Levels. What levels of service / support contracts are
available for the system?
5.1.5.12
Maintenance Tools. What special tools are required to maintain
the system?
5.1.5.13
Equipment Sizes. What is the physical size (in inches) and weight
(in pounds) for each type of equipment in the proposed system?
5.1.6
Logistic Supportability
In this section, bidders should respond to section 2.9.
5.1.7
Research and Development / Future Capabilities
In this section, bidders should respond to section 2.10.
3/8/2016
Automated Terminal Asset Management System RFP
Page 56 of 110
6.0 PROPOSED POSITION DETECTION SYSTEM
The objective of this RFP is to procure a PDS that can track mobile GPA equipment
and vehicles, maintain accurate container locations, monitor vehicle/equipment
performance and provide reporting mechanisms to evaluate the efficiency of the
equipment and container transactions. Data from other sources such as OCR,
NAVIS, and RFID shall be used along with PDS data to maintain an accurate, realtime picture of container terminal operations.
The PDS is a significant part of ATAMS as described in this document. GPA is
seeking a qualified vendor who will be responsible for the complete subsystem
proposed. The proposal must address any required infrastructure such as a mounting
system, vehicle mounted equipment, antennas, and back office equipment. The
proposal shall also include options, if the vendor is capable, for equipment shock
monitoring, monitoring additional CHE’s, and other options the vendor may want to
propose.
The details provided in the RFP are the minimum project requirements. The selected
vendor shall provide a “turnkey” system. The omission of specific reference to any
software, hardware, training, materials, or labor necessary for such a complete system
shall not be interpreted as relieving the selected vendor from furnishing such software,
hardware, training materials, or labor under the proposal quoted project price.
The selected vendor will participate as a team member with GPA, NAVIS, LA King
and other subsystem vendors to review the Total System and finalize the ATAMS
design. During this process, the selected vendor’s PDS subsystem design may be
modified. Bidders that do not wish to be a team member should not submit a
proposal.
6.1
System Description
GPA is seeking off the shelf equipment. Rather than designing to very specific
criteria, GPA will evaluate proposals based on the quality of the products and how well
the product design meets the needs for GPA. Therefore, the following questions are
designed to provide a method for evaluation. Each bidder has the opportunity to
define other criteria by which they may be judged and discussion regarding the
superior attributes of the proposed system is encouraged. Please respond as
completely as possible to the following questions. Do not respond by saying: "see
attachment, addendum or literature".
The evaluation team will consist of technical experts, operational personnel and
general managers. Bidders are encouraged to provide technical details regarding
system functionality to support detailed design evaluation as well as general laymen
definitions and explanations that easily define high-level concepts. Drawings, charts,
white papers and other graphical references (video clips, animations, screen shots,
etc.) are highly encouraged.
6.1.1
3/8/2016
General Description
Provide a detailed description of the proposed subsystem including a site
plan, a system design, an operating description, performance expectations,
Automated Terminal Asset Management System RFP
Page 57 of 110
and any operating characteristics that may be useful in the evaluation of the
subsystem. Then answer the following questions, even if redundant to the
above system description.
3/8/2016
6.1.1.1
Site Drawing. Provide a site drawing that identifies the location of
any remote equipment provided as part of the proposed design.
6.1.1.2
Network Design. Provide a detailed network drawing that
represents all equipment in the response to this RFP, as well as
the connection to the existing LAN.
6.1.1.3
Equipment Label. What is the manufacturer's name, as well as
the model name, version number, and age of current version for
each type of equipment proposed and where will it be installed?
6.1.1.4
Operating System. What is the operating system of the PDS
server?
6.1.1.5
Software Version. What is the software level proposed for each
type of equipment?
6.1.1.6
Network Protocol. How does the system communicate over a
local area network? Please provide specifics regarding
infrastructure required and wireless communication
considerations.
6.1.1.7
Equipment Performance Specifications. What are the
performance specifications for each piece of equipment
proposed? Include details that may provide an advantage over
other PDS products.
6.1.1.8
Integration. Does the proposed design integrate with NAVIS
and/or LA King? Please describe the method of integration.
6.1.1.9
Standards. What standards compliance such as IEEE and UL
does the subsystem and components meet?
6.1.1.10
Technology. What position detection technology is used and why
was this technology chosen to implement at GPA?
6.1.1.11
Differential Global Positioning System (DGPS) Type. If the
proposed PDS uses DGPS, what type of DGPS (Satellite, Real
Time Kinematic) is used? What redundancy provision is made to
ensure the continued provision of differential correction?
6.1.1.12
RF System. What RF system does the proposed PDS use?
Automated Terminal Asset Management System RFP
Page 58 of 110
6.1.2
3/8/2016
6.1.1.13
Location Accuracy. What is the location accuracy of the offered
PDS? Provide data from existing installations to support any
conclusions if possible.
6.1.1.14
Satellites Required. How many satellites in view are required for
achieving the stated levels of accuracy using DGPS?
6.1.1.15
Multi-path. How does the PDS overcome multi-path given
expected signal reflections in a container terminal environment?
6.1.1.16
Signal Blockages. Will crane shadows and similar signal
blockages affect the operation of the PDS? If so, how is this
issue being addressed?
6.1.1.17
Warm-up. What is the warm-up period between powering on the
proposed PDS and operation within given parameters?
6.1.1.18
Auto Steering. Does the bidding company offer an auto steering
system? Please describe all capabilities.
6.1.1.19
Collision Avoidance System (CAS). Does the bidding company
offer a CAS system? Please describe all capabilities.
6.1.1.20
Waypoints. Does the proposed system have the ability to define
reportable waypoints?
6.1.1.21
Special Features. Please state any special or proprietary features
regarding the proposed system that separates it from other bidder
offerings.
Operations and System Management
In this section, bidders shall discuss in detail the capabilities of the proposed
systems and describe the operations methodology.
6.1.2.1
Tolerance. Within what tolerance can the proposed system track
the location of mobile equipment?
6.1.2.2
Simultaneous Operations. How many mobile equipment handlers
can be tracked simultaneously in real-time?
6.1.2.3
Position Indication. Does the proposed system provide an
indication of the CHE’s current position to the driver?
6.1.2.4
TOS Update Frequency. How often will the subsystem send CHE
location updates to the TOS?
6.1.2.5
Position Reports. How often is vehicle position reported as it
changes? At what other times are vehicle positions reported,
Automated Terminal Asset Management System RFP
Page 59 of 110
such as entry or exit of a container row, at roadway intersections,
at refueling stations, etc.?
3/8/2016
6.1.2.6
Operator Interface. What data entry or operator interface is
required to operate the proposed system?
6.1.2.7
CHE Startup. Does the proposed system allow for a keyless
start/stop of CHE’s based on the operator’s identity?
6.1.2.8
Shutdown Events. In the event of a significant shock or other
alarm based on predetermined threshold levels, can the CHE be
shut down?
6.1.2.9
Alarms. In the event of a significant shock or other alarm based
on predetermined threshold levels, can the system make a visual
and/or audible alarm to alert the driver?
6.1.2.10
Shock Evaluation. Can the system measure impacts and stresses
affecting the spreader or frame and evaluate the initial shock gforce and the energy transfer to determine whether damage was
likely to have occurred from the event?
6.1.2.11
Container Inventory. How will the system provide an automatic
inventory of containers in both a stacked (stationary) and
wheeled (mobile) terminal environment? If a separate inventory
is kept apart from NAVIS, in the event of a discrepancy between
databases, how is the inventory reconciled?
6.1.2.12
Site Mapping System. Does the mapping of the X-Y coordinate to
a yard slot occur on-board the CHE, or does the PDS provide
coordinates to the TOS allowing mapping to be performed within
the TOS itself?
6.1.2.13
Terminal Mapping. Are terminal maps developed using a full yard
survey or is the map developed using CHE provided information?
When terminal changes occur, are new surveys required?
6.1.2.14
Survey Translation. Assuming the yard map is generated from a
physical survey, how is the survey carried out, and how are the
coordinates translated into a PDS compatible yard map?
6.1.2.15
Calibration. How is the PDS calibrated? How does the PDS
know when its accuracy is not up to standard? Is an alert
generated when this occurs?
6.1.2.16
Vessel Operations Container ID. How would the system identify
containers upon vessel load and discharge?
Automated Terminal Asset Management System RFP
Page 60 of 110
3/8/2016
6.1.2.17
Container Status ID. How does the PDS determine that a
container has been lifted or dropped?
6.1.2.18
Container Handoff. How is container handoff between equipment
handlers achieved and tracked?
6.1.2.19
Connectivity Limits. The GPA operates over 400 vehicles within
the coverage site. Describe the system’s capability of
maintaining connectivity at speeds up to 40 mph.
6.1.2.20
Container Size. Does the PDS report the size of the container
being handled?
6.1.2.21
Simultaneous Transactions. How many position or status change
transactions can be tracked simultaneously?
6.1.2.22
Temporary TOS Loss. Does the PDS capture all container move
information regardless of whether it has a current connection to
the TOS / Server?
6.1.2.23
Minimum Availability. What is the minimum availability of the
subsystem?
6.1.2.24
Equipment Mounting. Describe the equipment mounting in
vehicles? What amount of time is required per vehicle? What
design considerations have been given to reduce vehiclemounting time and to allow for the connection and integration of
additional subsystems such as monitoring equipment?
6.1.2.25
Data Transfer. Provide the steps and the amount of time per step
required to transfer data from an end user to the TOS.
6.1.2.26
Time Differential. What is the time differential between actual
container operations and a PDS report being received by the
TOS? Does this vary by activity, number of operations ongoing,
(CHE’s in operations), etc.?
6.1.2.27
Reporting Events. List all events or actions that will generate a
PDS message to the TOS.
6.1.2.28
PDS to TOS Integration. Describe all integration between the
PDS and the TOS. Discuss what information is being passed
and in which direction, what format is used, etc.
6.1.2.29
Transaction History. What levels (details) of transaction history
are available for each item tracked in the system?
Automated Terminal Asset Management System RFP
Page 61 of 110
3/8/2016
6.1.2.30
Displays. What types of operator displays are available for realtime viewing of equipment and inventory? Please provide
description and screenshot.
6.1.2.31
Display Updates. How are the operator displays referenced in the
previous question modified when GPA reconfigures container
stacking areas?
6.1.2.32
Reporting Functions. What reporting functions are available from
the proposed subsystem? Provide screen shots of any significant
monitoring, reporting or management tools.
6.1.2.33
Driver Productivity. Describe how the system reports driver
productivity and performs driver and vehicle monitoring and
longer-term trend analysis.
6.1.2.34
CHE Monitoring. List all items that can be monitored and reported
on by the subsystem such as: fuel usage, tire pressure, usage
hours, engine hours (idle and running), twist lock operation count,
distance traveled, battery charge, engine state indicators, fifth
wheel operations, container presence, etc.
6.1.2.35
Control. Can the subsystem be controlled over the network? At
any workstation?
6.1.2.36
Network Systems. Describe what software and hardware will be
needed in the office systems to view container activities or review
reports on local desktop computers.
6.1.2.37
Reporting Tools. Does your system easily integrate with standard
office reporting tools such as Excel or other report generation
tools?
6.1.2.38
Report Generation. Are the reports generated from a central
management system, through NAVIS, or some other data
system?
6.1.2.39
Graphical Depictions. Does the system have the capability to plot
historical and real-time locations of vehicles and reportable
events on a graphical depiction of the terminal?
6.1.2.40
Remote Status Check. Can vehicle status and availability be
checked remotely from the host?
6.1.2.41
Data Storage. How is data stored and what is the retrieval
process? Answer should include various levels of data such as
active data, archived data, etc.
Automated Terminal Asset Management System RFP
Page 62 of 110
6.1.3
3/8/2016
6.1.2.42
Data Handling on CHE’s. In the event of a radio network or power
outage, what is the capacity for storage of container move
information? How is this data retrieved when services are
restored?
6.1.2.43
Special Operations Tools. What special tools are required to
operate the system?
6.1.2.44
Alert Capabilities. Can the proposed subsystem send email,
pager or other notification of failures or alerts?
6.1.2.45
Battery Life. If you have battery operated equipment (where the
battery is the primary source of power), what is the average
battery life of the device? What procedures are generally used to
monitor replacement? (This does not apply to CHE batteries.)
Security, Survivability and Susceptibility
In this section, bidders shall discuss the proposed system’s vulnerabilities to
outside occurrence, both manmade and natural. Furthermore, the bidder
should provide details regarding any system design or other actions taken to
increase the subsystem’s resistance to outside threats.
6.1.3.1
Painting. Can the outdoor components of the system be painted
for safety or visibility?
6.1.3.2
Outdoor Conditions. The outdoor installed equipment must be
designed for outdoor use. Equipment will be subjected to high
winds (including hurricane force winds), rain, sun, heat and cold.
Is the proposed system designed for continuous outdoor use?
What weather ratings does the equipment carry? Describe the
conditions under which the system will continue to operate
without degradation.
6.1.3.3
Temperature & Humidity. What are the minimum and maximum
temperature and humidity ratings for each device proposed?
6.1.3.4
Cell Phone Interference. Will the operation of a cell phone tower
located in the terminal interfere with the subsystem?
6.1.3.5
Shock Tolerance. How much shock can the devices withstand
and continue to operate normally?
6.1.3.6
Electrical Interference. How are onboard systems protected from
electrical interference? In particular, discuss electrical
interference relative to the DGPS differential correction signal?
6.1.3.7
Spoofing. What steps have been taken in the system design,
hardware or software, to prevent spoofing or service denial
attacks?
Automated Terminal Asset Management System RFP
Page 63 of 110
6.1.4
6.1.5
3/8/2016
Reliability
Bidders shall provide evidence that the proposed subsystem is reliable under
the conditions expected to be encountered in Savannah, Georgia. Actual
data from other installations is preferred. Where actual data cannot be
obtained, simulations, tests or manufacturers’ data can be used instead,
albeit at a lower degree of confidence.
6.1.4.1
Mean Time Between Failure (MTBF). What is the MTBF for each
type of equipment proposed?
6.1.4.2
Fault Detection. How are component level faults detected and
reported?
6.1.4.3
Single Point Failures. Identify all single point failures in the
proposed design and indicate what can be done, and the cost for
such, to eliminate the single point failure.
6.1.4.4
Component Failures. On the bidder’s currently installed systems,
what system component fails most frequently? How often does
the component fail? Describe the conditions under which the
component is most likely to fail.
Maintainability
GPA is not prepared to field a system that increases maintenance costs
significantly or one that cannot be maintained. Bidders shall demonstrate a
practical knowledge of maintenance regarding the subsystems proposed.
Again, actual data is preferred.
6.1.5.1
Periodic Upgrades. Does the PDS system require periodic code
or firmware upgrades? If so, how are these upgrades deployed?
How often does the manufacturer release the upgrades?
6.1.5.2
Remote Configuration Upgrades. Can the on-board system
configuration be updated remotely from the host?
6.1.5.3
Remote Software Upgrades. Can the on-board system firmware /
software be updated remotely from the host?
6.1.5.4
Support Tools. Does the system offer any IT support tools to
facilitate troubleshooting or problem resolution?
6.1.5.5
Diagnostics. What diagnostic features are available? Does the
system have Built-in-Test (BIT)?
6.1.5.6
Mean Time to Repair or Replace (MTRR). What is the MTRR for
each type of equipment included in the subsystem design?
Automated Terminal Asset Management System RFP
Page 64 of 110
6.1.5.7
Hardware Support. How long from the date of acceptance by
GPA will the manufacturer provide hardware support for the
proposed product?
6.1.5.8
Software Support. How long from the date of acceptance by GPA
will the manufacturer provide software or firmware support for the
proposed product?
6.1.5.9
Manufacturer Warranty Period. What is the manufacturers’
warranty period for each type of equipment proposed?
6.1.5.10
Subsystem Warranty Period. What is the warranty period for the
proposed subsystem following acceptance by GPA?
6.1.5.11
Support Levels. What levels of service / support contracts are
available for the system?
6.1.5.12
Maintenance Tools. What special tools are required to maintain
the system?
6.1.5.13
Equipment Sizes. What is the physical size (in inches) and weight
(in pounds) for each type of equipment in the proposed System?
6.1.6
Logistic Supportability
In this section, bidders should respond to section 2.9.
6.1.7
Research and Development / Future Capabilities
In this section, bidders should respond to section 2.10.
3/8/2016
Automated Terminal Asset Management System RFP
Page 65 of 110
7.0 REQUEST FOR PROPOSAL PROCEDURES
7.1
Release of Request for Proposal
This RFP is being issued to firms deemed to be potentially qualified to act as Contractor to
GPA for the acquisition, design, implementation, commissioning, and maintenance support of
the proposed ATAMS.
7.2
Notice of Intent to Propose
A Notice of intent to Propose and registration for the optional Pre-Proposal Conference is
required by 27 January 2006. The Notice of Intent to Propose and complete contact
information should be sent by fax, mail, or e-mail to:
Mr. Scott H. Rasplicka
IT Department
Georgia Ports Authority
P.O. Box 2406
Savannah, GA 31402
Fax: (912) 964-3815
E-mail: srasplicka@gaports.com
7.3
Pre-Proposal Conference
An optional Pre-Proposal Conference will be held on 3 February 2006 Eastern Standard
Time at the following location:
Georgia Ports Authority
Garden City Terminal
GPA Administration Building Board Room
Main Street
Garden City, GA 31408
The purpose of this Conference is to discuss the requirements and objectives of this RFP.
GPA staff and representatives will attempt to answer all questions submitted prior to and
during the conference. A summary of all questions and answers, as well as a list of
attendees, will be made available in form of an addendum and will be forwarded to all
companies that filed a notice of intent to propose in accordance with paragraph 4.2.
Tours of the GPA facilities will be conducted immediately following the Pre-Proposal
Conference.
7.4
Contact for Inquiries
Any questions regarding this RFP should be submitted in writing to the GPA’s sole contact
person at:
Mr. Bill Sutton
General Manager of Management Information Systems
P.O. Box 2406
Savannah, GA 31402
Phone: (912) 963-6907
3/8/2016
Automated Terminal Asset Management System RFP
Page 66 of 110
Fax: (902) 964-3815
E-mail: bsutton@gaports.com
The contact person above is the only individual that can be contacted about the project by
Bidders before proposals are submitted. The contact MUST be in writing by letter, fax, or email. The department contact cannot vary the terms of the RFP.
7.5
Last Date to Submit Written Questions
All questions regarding this RFP must be received at GPA by 10 February 2006. Inquiries
received after that date and time will not be considered. All questions and GPA responses
will be made available to all bidders in the form of an addendum and will be forwarded to all
companies that file a notice of intent to propose in accordance with paragraph 4.2.
Responses to questions will be provided no later than 20 February 2006.
7.6
Proposal Due Date, Time, and Location
GPA must receive responses to this RFP no later than 1700 EST, 6 March 2006. Proposals
should be submitted to:
Mr. Bill Sutton
General Manager of Management Information Systems
Garden City Terminal
GPA Administration Building
Main Street
Garden City, GA 31408
The proposals will not be opened publicly. Any proposals received after the time stipulated
will not be considered. Proposals must be responsive to all aspects of this RFP.
7.7
Bid Bond
A bid bond and a payment and performance guarantee must be included as separate line
items in the cost details.
7.7.1
A Bid Bond or check in the amount of 10% of the value of the proposal will be
required from each bidder. The Bid Bond will guarantee the bidder’s bid including
their ability to obtain a payment and performance bond, which will be required prior
to executing a contact.
7.7.2
A payment and performance bond will be required prior to issuance of a contract.
The cost for said bond shall be factored into the proposal.
7.8
Bid Opening
The opening of bids will be closed. Discussions with vendors concerning the status of their
proposal will not be made until a contract with one of the vendors is signed. GPA reserves
the right to have discussions with vendors regarding their proposal if needed to aid in the
selection process.
7.9
Contract Award
3/8/2016
Automated Terminal Asset Management System RFP
Page 67 of 110
Proposals must remain open and valid for up to 90 days from the proposal due date, unless
the time for awarding the contract is extended by mutual consent of GPA and bidder. All
proposals submitted will become the property of the GPA and will not be returned.
7.10 Base Bid, Options and Marginal Costs
All bidders shall submit a bid on the base document and then for each option as outlined in
the following subsections. Bidders may also submit as many additional options as desired.
Each bidder must respond to every option with a $0 bid, an additive bid or a deductive bid.
For bidders that want to submit a bid on only a small subsystem, the base bid may be $0. If
an alternative technology is proposed in lieu of the technologies identified in the following
paragraph, then the bid is treated as a base bid and all appropriate questions from sections
3, 4, 5, and/or 6 must be answered as well as a response for each of the options.
7.10.1 Base Bid. The base bid shall be based on designing and installing the following
items in accordance with the PORD:




A WLAN throughout the GCT and ICTF.
An OCR system for entry and exit at gates 3, 4, 6 and 7 that identifies containers,
chassis and GenSets.
An RFID system with readers for entry and exit at gates (pedestals and
canopies) 3, 4, 6 and 7, and on all cranes (RTG's, lifts and quay cranes, etc.).
Include in the base cost 7,500 RFID tags for trucks.
A PDS with tracking components mounted on all cranes (RTG's, lifts and quay
cranes, etc.) and all UTR's used for wheeled operations (see paragraph 1.5).
7.10.2 Options. The following fourteen options must be included in the proposal even if they
are all $0. Each option must be singularly inclusive. In other words, if option 5
requires the components in option 2 to work: the components in option 2 must be
included in option 5. Do not assume that proposal evaluators will know to add option
2 and option 5 to determine the total cost of option 5. Each option must stand-alone.
Additional options offered by the bidder shall be identified in contiguous order
starting with Optional. Systems or subsystems being proposed that are not identified
in this RFP shall be listed as an unsolicited option following the standard options
listed below. For each option offered, the bidder shall provide a thorough description
and general operating characteristics while keeping the detail and responses
consistent with the level of detail provided in the responses to the overall RFP.
7.10.2.1
Option 1. Install PDS tracking components on all UTR's. Define a PDS
waypoint at gate 7. Delete the RFID and OCR capability at gate 7.
7.10.2.2
Option 2. Provide a subsystem to automatically inspect container seals
for evidence of tampering.
7.10.2.3
Option 3. Provide a subsystem to automatically inspect container seals
for evidence of tampering and automatically record the container seal
number.
7.10.2.4
Option 4. Provide a subsystem (or additional OCR capability) to
automatically verify empty containers.
7.10.2.5
Option 5. Provide a subsystem (or additional OCR capability) to
automatically or remotely inspect chassis and containers for damage.
3/8/2016
Automated Terminal Asset Management System RFP
Page 68 of 110
7.10.2.6
7.10.2.7
7.10.2.8
7.10.2.9
7.10.2.10
7.10.2.11
7.10.2.12
7.10.2.13
Indicate whether the inspection system can identify tires that are flat or
low on air as well.
Option 6. Provide a rail portal at the ICTF to automatically identify and
locate rail cars and chassis.
Option 7. Provide a CAS for each RTG.
Option 8. Provide a CHE monitoring system to detect, locate, identify
and report potential damage to mobile equipment. Sub-divide this option
as necessary to fully explain the cost to add monitoring to different
equipment types with different capabilities.
Option 9. Provide an OCR system on quay cranes to automatically
identify containers as the crane handles them. Indicate whether or not
the proposed crane mounted OCR system can capture re-handles in a
stack or onboard ship.
Option 10. Provide an inventory subsystem to automatically identify and
record the exact location of wheeled containers in the Rapid Dispatch
Terminal.
Option 11. Provide a PDS subsystem that can be used to track over-theroad trucks while they are in the terminal.
Option 12. Provide an RFID subsystem that can be used to track overthe-road trucks throughout the terminal to always know the latest
location of a truck within a specified distance. Use 1/4 mile for this
design and discuss the cost differences of changing the location range.
Option 13. This should be used as the first unsolicited option offered by
the bidder.
7.10.3 Marginal Cost. As container volume at GPA grows, GPA will be purchasing
numerous RTG's and other equipment. Once ATAMS is in place, additional ATAMS
subsystem components must be added to the cost of purchasing new CHE's. To aid
GPA is estimating the added cost of bringing new equipment on-line, bidders shall
provide a marginal price per unit estimate for proposed CHE mounted subsystem
equipment. The quote should include the cost of installation. Also indicate at what
point, if any, additional infrastructure may be needed. For example, 40 CHE units
are purchased as part of this contract and over time 10 more are added. But at 50
total units, an additional radio server is needed.
7.11 Proposal Format
Proposals shall be typewritten, using 12-point font, on standard 8.5” x 11” paper, with
material on one side only. Foldouts containing charts, spreadsheets, and oversized exhibits
are permissible as long as they are packaged with the proposal. The proposal must be
placed in a three-ring binder with tabs separating the major sections in accordance with the
table of contents listed below. The pages in the proposal must be numbered consecutively
within each section, showing proposal section number and page number.
7.11.1 Tabs
The proposal must be submitted using the following table of contents format:
Cover Page
Table of Contents
Tab 1 Cover Letter
3/8/2016
Automated Terminal Asset Management System RFP
Page 69 of 110
Tab 2
Tab 3
Tab 4
Tab 5
Tab 6
Tab 7
Tab 8
Tab 9
Tab 10
Tab 11
Tab 12
Tab 13
Executive Summary
Firm Background, Principal Officers, and Prior Experience
System Functional & Technical Description
Operational Requirements
Questionnaire Responses
GPA Support Requirements (Bidder supplied infrastructure)
Commissioning
Training
Cost Proposal
Proposed Schedule
Site References
Concluding Remarks
Eight (8) copies of the proposal must be submitted in addition to one original, marked
“Original”.
Proposals must also be provided in electronic format, including all figures, handouts, and
attachments. Bidders must provide ten (10) CD-ROMs of the entire proposal package.
Acceptable formats for electronic files include Microsoft Word, Microsoft Excel, Microsoft
Project, Microsoft PowerPoint, and Adobe Acrobat (PDF). Any non-standard formats, such
as Picture Viewer, must include viewing software on the CD-ROM that allows viewing on a
standard Pentium-based computer.
Submittals that are not in compliance with the format requirements will be downgraded
accordingly.
7.12 Proposal Content
Proposals shall be submitted in accordance with the format defined in this section.
Proposals not submitted in this format may be deemed as unresponsive.
7.12.1 Cover Page
The Cover Page must include the RFP number, title, and the complete vendor
name, mailing address, and web address. Include the name, telephone number,
and e-mail address of the person that GPA should contact regarding the proposal.
7.12.2 Table of Contents
The Table of Contents shall include an index of the proposal contents, figures, and
attachments.
7.12.3 Tab 1: Cover Letter
Proposals must include a cover letter signed by a vendor representative
authorized to make contractual obligations and should include the bidder’s
corporate seal.
Proposals must confirm that the organization will comply with all the provisions of
this RFP, and include a statement describing any potential conflict of interest. Any
3/8/2016
Automated Terminal Asset Management System RFP
Page 70 of 110
exceptions to the GPA’s general terms and conditions should also be discussed in
the statement.
7.12.4 Tab 2: Executive Summary
The proposal must include an executive summary of two (2) pages or less that shall
include a statement of approach to the work, understanding of the project goals and
objectives, and demonstrated understanding of the project’s potential problems and
special concerns.
7.12.5 Tab 3: Firm Background, Principal Officers, and Prior Experience
This section should state the full name and address of the bidder’s organization and
identify the parent company if the bidder is a subsidiary. Specify the branch office or
other subordinate element, which will perform or assist in performing this work.
Indicate whether the bidder operates as a corporation, partnership, or individual.
Include the State in which the bidder is incorporated and/or licensed to operate, the
date of incorporation or licensing.
Provide a brief history of the company, including number of employees and a list of
locations, and explanation of the company’s corporate vision.
In the event that a consortium, joint venture, or team submits a proposal, it shall not
be considered responsive unless it is established that all contractual responsibilities
rest solely with one Contractor or legal entity, which shall not be a subsidiary or
affiliate with limited resources. Each proposal shall indicate the entity responsible
for execution on behalf of the team.
Provide a listing of the principle officers of the company or companies responding.
Also provide a listing and resumes of key employees, such as the project manager,
who will lead the project team, to include name, title, job function, and length of
experience with the bidding organization. Include information regarding similar
projects on which they have worked and the capacity in which they have worked on
the referenced projects. Identify the level of authority each person listed will have
regarding the project.
Address the company’s financial situation. Indicate if the company is involved in any
pending litigation or claims and any material liens or judgments against the
company. Acknowledge if the company or any of its subsidiaries have filed for
bankruptcy. Financial statements, background credit reports, and other material
should be used to support the bidder’s assertions.
7.12.6 Tab 4: System Functional & Technical Description
This section shall be used by the bidder to describe the functionality of the proposed
system outlining in detail the system features, options, and/or alternatives as well as
the technical aspects and operation of the proposed system.
7.12.7 Tab 5: Operational Requirements
In this section, responders should identify each operational requirement from section
2.5 and determine whether the requirement is applicable to their subsystem and if
3/8/2016
Automated Terminal Asset Management System RFP
Page 71 of 110
so, whether their subsystem design will meet the requirement. If their design will
meet the requirement, expected results should be identified. If the design will not
meet the requirement, responders should describe the conditions under which the
requirement cannot be met and why.
If the requirement applies to two or more subsystems, the bidder should identify
what part of the requirement applies to them and how well they can meet their part.
Further description of any design criteria for the other subsystem to help meet the
overall requirement should be mentioned to ensure proper selection of vendors for
the other subsystem. In other words, every effort will be made by GPA to marry
vendors and subsystem designs that can work together to meet the overall
requirements.
7.12.8 Tab 6: Questionnaire Responses
This section will be used to record responses to questions in section 3, 4, 5 and/or 6.
The bidder must repeat the question prior to their complete and free form response.
Note that these questions do not imply requirements. Requirements are identified in
section 2.0. These questions are merely a gauge by which the evaluation team can
compare responses and ensure similar information is provided by all responders
resulting in an “apples-to-apples” comparison.
7.12.9 Tab 7: Commissioning
This section will be used to outline the testing and commissioning plans as
described in section 2.7 Post Installation Testing and Commissioning.
7.12.10 Tab 8: GPA Support Requirements
In the appendices, information related to existing GPA infrastructure has been
provided to lay the foundation for adding additional subsystems. Additional
infrastructure will be needed for each subsystem to be added. However, in many
cases, the infrastructure needed may already exist nearby. For example, if power or
data is needed, look for a nearby building. If just power is needed, look for utility
poles. If data is needed near the perimeter, dark fiber may be available without
significant effort.
In this section of the proposal, define any infrastructure requirements that GPA must
provide to support the bidder’s subsystem such as power, new towers, buildings,
etc. Provide all the information necessary for GPA to determine the cost to provide
the necessary infrastructure. Be as specific as possible. For example, 120V, 10
Amp circuit at this location or 1 GB Ethernet access to the network at this location,
etc. Any estimates, or even an alternative proposal may be given to help GPA
evaluate the cost of providing the infrastructure. If bidders prefer to supply their own
infrastructure, include data regarding intended tie-ins to existing data and power
systems in this section. All costs associated with bidder-supplied infrastructure
should be included under Tab 10 of the proposal.
7.12.11 Tab 9: Training
Employee training is critical to the smooth operation of ATAMS, as the complexity of
the GPA IT systems will grow significantly. In this section, bidders shall describe the
3/8/2016
Automated Terminal Asset Management System RFP
Page 72 of 110
training programs recommended and offered in their proposal. All aspects of training
should be discussed from hands-on to classroom training. Include descriptions of the
amount of time, materials, and locations as well as why different programs are
necessary, mandatory or optional. Also segregate initial from follow-on training and
on-site from off-site training. At a minimum, included the following training categories
(others may be substituted or combined if they fit better with technology):





Administrator Training. Describe the training program for the system
administrators.
Trainer Training. Describe train-the-trainer programs.
Maintenance Training. Describe maintenance training programs.
Security Training. Describe training programs related to security.
User Training. Describe training to be provided for subsystem users/operators as
applicable.
7.12.12 Tab 10: Cost Proposal
The cost proposal shall provide enough detail for GPA to understand all associated
cost drivers. Through this understanding, further questions and design
considerations may be requested in subsequent final offers or negotiations with
selected bidders in an attempt to keep costs within budget. Furthermore, an
understanding of the budget will help in the evaluation of long term costs including
the purchase of spare parts, maintenance, etc. The cost proposal shall be submitted
with the first pages as excel spreadsheets identifying the following line-item costs:
A.
B.
C.
D.
E.
F.
G.
H.
I.
J.
K.
L.
Design and Engineering
Hardware
Software
Navis/LA King Integration
GPA Support Requirements
Installation
Training and Support
Warranty
Miscellaneous
Overhead
Profit
TOTAL PROPOSED COST
M.
N.
Options (each listed individually)
Marginal Cost
O.
Ten Year Cost Projections
On subsequent pages, additional details regarding these costs shall be provided as
described below. Any portions of the project that will be subcontracted should be
identified under the appropriate sections along with the costs associated with the
subcontractors.
3/8/2016
Automated Terminal Asset Management System RFP
Page 73 of 110
7.12.12.1
Design and Engineering. Describe the costs associated with designing
the system including any engineering support required to participate in
post award meetings to help define a final total system design, and
provide engineering installation and test support.
7.12.12.2
Hardware Cost. Include the Description, Model Number, Unit Bid Price,
and Total Bid Price for each component of the proposed system.
Indicate whether equipment is required or optional.
7.12.12.3
Software Cost. Describe individual software components and describe
the source of the cost as vendor written, purchased or licensed. Indicate
if license fees are annual or one-time fees. Also identify what additional
software costs can be expected over the next ten years including
additional licensing, periodic upgrades, patches, etc.
7.12.12.4
Navis/LA King Integration. Describe any cost being charged by Navis or
LA King to support integration of the proposed subsystem with the TOS,
excluding any software license fees that will be paid by GPA. Navis and
LA King will identify what fees to support your subsystem shall be paid
by the vendor and what fees shall be paid by GPA in accordance with
existing GPA license agreements.
7.12.12.5
GPA Support Requirements and Bidder Supplied Infrastructure. Bidders
that choose to supply their own infrastructure should detail infrastructure
requirements and their associated costs in accordance with section
7.12.10.
7.12.12.6
Installation. Describe the costs to install the system on GPA facilities
and break the costs down further into field equipment installation, office
equipment, testing and other divisions as applicable.
7.12.12.7
Training and Support. Indicate the number of days, location, and cost of
each training class proposed such as administrator, operations,
maintenance, train-the-trainer, etc. Note the class size limits if
applicable. Include the cost of training materials, travel, etc. in your
estimates.
7.12.12.8
Warranty. Identify the cost for providing a full warranty in accordance
with the RFP requirements. Identify any cost drivers, such as a
particular unit with potentially high failure rates, travel expenses, etc.
7.12.12.9
Miscellaneous. This line item shall include initial consumable supply
cost to test the system and be ready for go-live as well as other items
that do not fit in other sections.
7.12.12.10 Overhead. Identify the cost for this contract that is related to home office
overhead. Identify any cost drivers that may have better solutions with
an appropriate contract to help lower overall costs.
3/8/2016
Automated Terminal Asset Management System RFP
Page 74 of 110
7.12.12.11 Profit. Indicate the profit needed to submit to this contract. Identify any
risks or other factors that adversely affect profit potential.
7.12.12.12 Options. List all options and marginal costs as defined by GPA in
section 7.10 and all unsolicited options that may be pertinent to ATAMS
now or in the future. These options may or may not be purchased now;
but at the very least will allow the evaluation team to have a better
understanding of the bidders' capabilities and the costs involved in
future additions. Option prices must be all-inclusive, and in most cases,
will not be taken unless GPA accepts the main proposal and GPA
chooses to include the option in the contract. In some cases, a standalone option may be purchased separately.
7.12.12.13 Ten-year Cost Projections. Identify all annual costs for maintenance,
software and hardware updates, and consumable supplies, along with
projected price increases, for the ten (10) year period immediately
following system acceptance. Ideally, projections will be developed
using data from previous implementations. Any relative differences
between the proposed GPA system and any actual implementation that
projections are based on should be highlighted. At a minimum, include
the following in the annual cost projections:





Indicate maintenance cost for each component of the proposed
system. List any parts that are likely to be replaced. Include required
labor hours and hourly rates.
Indicate maintenance cost for each software module of the proposed
system.
Indicated all costs associated with receiving new releases and
software enhancements. Include any consulting resource costs
required to implement upgrades.
Indicate consumable supply costs for the system. List the item and
estimated quantity to be consumed annually.
Indicate which components may be maintained by a third party.
7.12.12.14 Considerations. In all the above costs and cost details, ensure the
following considerations have been made. These can be included under
miscellaneous if there is not a more appropriate location. If the
miscellaneous line item is used, subsequent details shall be provided to
identify the costs included in this section.

3/8/2016
All operating system software, utility software, interface software,
installation services, training, manuals, publications, supplies, and
maintenance items shall be priced individually and as a total for the
system.
Automated Terminal Asset Management System RFP
Page 75 of 110

Estimated costs for travel expenses for site preparation, installation,
and training should be included as a separate line item under each
appropriate category.

In the event that the bidder is submitting more than one proposal to
GPA for ATAMS, the bidder should indicate any discount that GPA
will receive if more than one proposal is accepted.
7.12.12.15 The bidder shall also outline a schedule of required progress payments
together with specific system deliverables against which these payments
are to be made, if any. The schedule of progress payments will include
a 15% Final Payment based upon the acceptance of the total system by
GPA.
7.12.13 Tab 11: Proposed Schedule
This section shall begin with a description of the bidder’s approach to project
management and how the bidder will manage the installation of the proposed
subsystem.
A detailed schedule for the installation of the subsystem shall be provided in the
form of a chart or equivalent display. Bidder’s can assume that a contract notice to
proceed will be provided by GPA on June 1, 2006. Include in the schedule all key
operations including, but not limited to, engineering and design, key component
installations, subsystem integrations, system commissioning, training, etc. Tasks
shall be clearly identified as to whether they are the responsibility of the bidder or the
GPA. Any site preparation and utility infrastructure requirements to be completed by
GPA must be included on the schedule.
Finally, describe the three worst problems the bidder has faced on similar projects,
how the issue were resolved, the effects on the schedule, and how to avoid similar
issues in the future.
7.12.14 Tab 12: Site References
This section shall be used by the bidder to list a minimum of three (3) reference
sites. At least one of the reference sites should be a comparable system where the
system is operational. The bidder should include the following minimum information
for each system referenced:







Company Name and Address
Contact Individual, Title, and Phone Number
System Description
Major differences between the installed system and the proposed system
System Hardware and Software configuration
List functional modules installed
Date of system installation
7.12.15 Tab 13: Concluding Remarks
3/8/2016
Automated Terminal Asset Management System RFP
Page 76 of 110
This section shall contain any bidder elaboration regarding software philosophy,
hardware architecture, or additional information that the bidder believes will provide
a clear understanding of the proposed system and/or the bidder’s capabilities.
7.13 Proposal Evaluation
7.13.1 Evaluation Criteria. Proposal evaluation includes, but is not limited to:
A. Total Cost of Ownership (TCO) Over 10 Years. GPA will consider each proposal
based on the predicted TCO over a ten-year period.
B. Meets Requirements. Each proposal will be evaluated on how well the
requirements of this RFP are met.
C. Added Value. Each proposal will be evaluated on perceived added value the
bidder can offer to GPA not otherwise contemplated in this RFP.
D. Technical Approach. The details of the proposed technology will be compared to
other existing or pending technologies to evaluate how GPA benefits from the
proposed technology, e.g. superior life cycle analysis, upgradeability, early
obsolescence issues, etc.
E. Project Management. The experience of the Bidder in overall project
management for projects of similar scope and size will be evaluated. Training
and certification in project management will also be considered.
F. References. The results of interviews with reference sites will be weighed into the
proposal evaluation.
G. Prior Performance in a Sea Port Environment. The success of the bidder in
similar projects in a seaport environment will be considered.
H. Commissioning, Support, Training, and Documentation. The bidder’s responses
to section 7.12.10 detailing what they will offer in this area will be evaluated.
I. Maintenance Plan. The bidder’s maintenance plan shall be evaluated on labor
intensity and ease (skills involved as well as the ease of administration). Bidders
who receive higher ratings in this category are those who demonstrate a proven
track record of maintaining systems once installed, whose plans appear complete
and realistic, and whose maintenance practices can be done with the fewest
number of people with lower level skill sets.
J. Contractor Organization and Financial Viability. GPA must ensure the bidder is
capable of completing the job once selected. Organizations that are strong
financially with good product lines and have a good management team in place
will receive higher ratings in this category. It is important to GPA that the
vendors stay in business and are capable of supporting GPA for many years to
come with ongoing research and development, constantly improving and
3/8/2016
Automated Terminal Asset Management System RFP
Page 77 of 110
developing new product lines to help keep GPA in the lead with productivity and
(low) cost.
7.13.2 Evaluation Weights. There are a number of considerations the evaluation team will
be using to choose vendors for ATAMS. The table below may help provide insight as
to the relative importance of some of these criteria.
Criteria
A
Total Cost of Ownership Over 10 Years
B
Meets Requirements
C
Added Value
D
Technical Approach
E
Project Management
F
References
G
Prior Performance in a Sea Port Environment
H
Commissioning, Support, Training, and Documentation
I
Maintenance Plan
J
Contractor Organization and Financial Viability
* If initial costs are within budget
Weight
15%*
30%
5%
10%
5%
5%
10%
10%
5%
5%
7.13.3 Evaluation Rating. Criteria shall be evaluated in accordance with the following table
and the weights assigned to each criteria:
Rating
10 Excellent
9
8
Very
Good
Good
7
6
Average
5
4
3
2
1
0
Poor
Very
Poor
Exceeds the requirements of the criterion significantly and in
very beneficial ways / very desirable
Exceeds the requirements of the criterion in ways which are
beneficial to our needs
Exceeds the requirements of the criterion but in a manner which
is not particularly beneficial to our needs
Fully meets the requirements of the criterion
Adequately meets most of the requirements of the criterion;
May be lacking in some areas that are not critical
Barely meets most of the requirements of the criterion to the
minimum acceptable level; May be lacking in some of the areas
that are not critical
Addresses most, but not all of the requirements of the criterion
to the minimum acceptable level; Lacking in critical area
Poor to very poor
Minimally addresses some, but not all, of the requirements of
the criterion; Lacking in critical areas
Very poor to unsatisfactory
Does not satisfy the requirements of the criterion in any manner
GPA reserves the right to reject any and all proposals, waive any formalities, and/or divide
any project into sub-projects.
3/8/2016
Automated Terminal Asset Management System RFP
Page 78 of 110
7.14 Final Offers
Depending on the quantity and quality of the proposals received, GPA may request Best and
Final Offers and/or oral presentations. In each subsequent stage, GPA will only invite those
bidders who are under consideration following the previous round of evaluation. During
subsequent stages, if deemed necessary by GPA, additional questions, requirements, data,
cost details, etc. may be required as part of the follow-on bid package.
3/8/2016
Automated Terminal Asset Management System RFP
Page 79 of 110
8.0 GENERAL TERMS AND CONDITIONS
8.1
SPECIFICATIONS: The specifications in this request are the minimum acceptable. When specific
manufacturer and model numbers are used, they are to establish a design, type of construction, quality,
functional capability and/or performance level desired. When alternates are bid/proposed, they must be
identified by manufacturer, stock number, and such other information necessary to establish equivalency.
GPA shall be the sole judge of equivalency. Bidders/bidders are cautioned to avoid bidding alternates to
the specifications that may result in rejection of their bid/proposal.
8.2
DEVIATIONS AND EXCEPTIONS: Deviations and exceptions from original text, terms, conditions, or
specifications shall be described fully, on the bidder's/bidder's letterhead, signed, and attached to the
request. In the absence of such statement, the bid/proposal shall be accepted as in strict compliance
with all terms, conditions, and specifications and the bidders/bidders shall be held liable.
8.3
QUALITY: Unless otherwise indicated in the request, all material shall be first quality. Items that are
used, demonstrators, obsolete, seconds, or which have been discontinued are unacceptable without prior
written approval by GPA.
8.4
QUANTITIES: The quantities shown on this request are based on estimated needs. The GPA reserves
the right to increase or decrease quantities to meet actual needs.
8.5
DELIVERY:
specified.
8.6
PRICING AND DISCOUNT:
Deliveries shall be F.O.B. destination freight prepaid and included unless otherwise
8.6.1 Unit prices shown on the bid/proposal or contract shall be the price per unit of sale (e.g., gal., cs.,
doz., ea.) as stated on the request or contract. For any given item, the quantity multiplied by the
unit price shall establish the extended price; the unit price shall govern in the bid/proposal
evaluation and contract administration.
8.6.2 Prices established in continuing agreements and term contracts may be lowered due to general
market conditions, but prices shall not be subject to increase for ninety (90) calendar days from the
date of award. Any increase proposed shall be submitted to the contracting agency thirty (30)
calendar days before the proposed effective date of the price increase, and shall be limited to fully
documented cost increases to the contractor, which are demonstrated to be industry-wide. The
conditions under which price increases may be granted shall be expressed in bid/proposal
documents and contracts or agreements.
8.6.3 In determination of award, discounts for early payment will only be considered when all other conditions are equal and when payment terms allow at least fifteen (15) days, providing the discount
terms are deemed favorable. All payment terms must allow the option of net thirty (30).
8.7
ACCEPTANCE-REJECTION: GPA reserves the right to accept or reject any or all bids/proposals, to
waive any technicality in any bid/proposal submitted, and to accept any part of a bid/proposal as deemed
to be in the best interests of GPA.
Bids/proposals MUST be date and time stamped by the soliciting purchasing office on or before the date
and time that the bid/proposal is due. Bids/proposals date and time stamped in another office will be
rejected. Receipt of a bid/proposal by the mail system does not constitute receipt of a bid/proposal by
the purchasing office.
8.8
METHOD OF AWARD: Award shall be made to the bidder that provides a reasonably priced,
responsive bid package deemed to be in the best long-term interest of GPA.
8.9
ORDERING: Purchase orders or releases via purchasing cards shall be placed directly to the contractor
by an authorized agency. No other purchase orders are authorized.
3/8/2016
Automated Terminal Asset Management System RFP
Page 81 of 110
8.10 PAYMENT TERMS AND INVOICING: GPA normally will pay properly submitted vendor invoices within
thirty (30) days of receipt providing goods and/or services have been delivered, installed (if required),
and accepted as specified.
Invoices presented for payment must be submitted in accordance with instructions contained on the
purchase order including reference to purchase order number and submittal to the correct address for
processing.
A good faith dispute creates an exception to prompt payment.
8.11 TAXES: GPA as a State Authority is exempt from all sales taxes and all taxes should be removed from
all costs included in the bid package.
8.12 GUARANTEED DELIVERY: Failure of the contractor to adhere to delivery schedules as specified or to
promptly replace rejected materials shall render the contractor liable for all costs in excess of the
contract price when alternate procurement is necessary. Excess costs shall include the administrative
costs.
8.13 ENTIRE AGREEMENT: These Standard Terms and Conditions shall apply to any contract or order
awarded as a result of this request except where special requirements are stated elsewhere in the
request; in such cases, the special requirements shall apply. Further, the written contract and/or order
with referenced parts and attachments shall constitute the entire agreement and no other terms and
conditions in any document, acceptance, or acknowledgment shall be effective or binding unless
expressly agreed to in writing by the contracting authority.
8.14 APPLICABLE LAW AND COMPLIANCE: This contract shall be governed under the laws of the State of
Georgia. The contractor shall at all times comply with and observe all federal and state laws, local laws,
ordinances, and regulations which are in effect during the period of this contract and which in any
manner affect the work or its conduct. GPA also reserves the right to cancel this contract with any
federally debarred contractor or a contractor that is presently identified on the list of parties excluded
from federal procurement and non-procurement contracts.
8.15 ANTITRUST ASSIGNMENT: The contractor and GPA recognize that in actual economic practice,
overcharges resulting from antitrust violations are in fact usually borne by GPA (purchaser). Therefore,
the contractor hereby assigns to GPA any and all claims for such overcharges as to goods, materials or
services purchased in connection with this contract.
8.15 ASSIGNMENT: No right or duty in whole or in part of the contractor under this contract may be assigned
or delegated without the prior written consent of GPA.
8.16 NONDISCRIMINATION / AFFIRMATIVE ACTION: In connection with the performance of work under
this contract, the contractor agrees not to discriminate against any employee or applicant for employment
because of age, race, religion, color, handicap, sex, physical condition, developmental disability. This
provision shall include, but not be limited to, the following: employment, upgrading, demotion or transfer;
recruitment or recruitment advertising; layoff or termination; rates of pay or other forms of compensation;
and selection for training, including apprenticeship. Except with respect to sexual orientation, the
contractor further agrees to take affirmative action to ensure equal employment opportunities.
8.16.1 The contractor agrees to post in conspicuous places, available for employees and applicants for
employment, a notice to be provided by the contracting state agency that sets forth the provisions
of the State of Georgia’s nondiscrimination law.
8.16.2 Failure to comply with the conditions of this clause may result in the contractor's becoming
declared an "ineligible" contractor, termination of the contract, or withholding of payment.
8.17 PATENT INFRINGEMENT: The contractor selling to GPA the articles described herein guarantees the
articles were manufactured or produced in accordance with applicable federal labor laws. Further, that
the sale or use of the articles described herein will not infringe any United States patent. The contractor
3/8/2016
Automated Terminal Asset Management System RFP
Page 82 of 110
covenants that it will at its own expense defend every suit which shall be brought against GPA (provided
that such contractor is promptly notified of such suit, and all papers therein are delivered to it) for any
alleged infringement of any patent by reason of the sale or use of such articles, and agrees that it will
pay all costs, damages, and profits recoverable in any such suit.
8.18 SAFETY REQUIREMENTS: All materials, equipment, and supplies provided to GPA must comply fully
with all applicable standards.
8.19 WARRANTY: Unless otherwise specifically stated by the bidder, equipment purchased as a result of this
request shall be warranted against defects by the bidder for one (1) year from date of system acceptance
by GPA. The equipment manufacturer's standard warranty shall apply as a minimum and must be
honored by the contractor.
8.20 INSURANCE REQUIREMENTS: The Vendor shall provide certificates of insurance in a form acceptable to
the Georgia Ports Authority (GPA), which affirms the Vendor has purchased the insurance described below.
Such insurance shall be provided by an insurer or insurers licensed to transact insurance in the State of
Georgia. Such coverage shall be maintained over the Contract period.
8.20.1 Workers' Compensation and Employer's Liability insurance covering employees of the Vendor and
employees of contractors or subcontractors. Such insurance shall cover the Vendor's full statutory
liability for workers' compensation benefits under the laws of Georgia (or any other state if such
liability arises in another state from work performed under the Contract Documents). Such
insurance shall be provided in accordance with all applicable federal and state laws. The limits of
employer's liability coverage shall be not less than $100,000 for each accident and $500,000
aggregate for disease. Such limits may be provided by a single policy or by a combination of
primary and excess policies.
8.20.2 Automobile Liability insurance coverage for "any" automobiles owned, rented, leased, borrowed, or
otherwise used by the Vendor and its contractors and subcontractors. Limits of automobile liability
coverage shall be not less than $1,000,000 combined single limit for bodily injury and property
damage arising from one occurrence or, if the policy provides separate limits for bodily injury and
property damage, not less than $1,000,000 for bodily injury and $1,000,000 for property damage.
Such limits may be provided by a single policy or by a combination of primary and excess policies.
The policy or policies shall provide coverage at least as broad as that provided by the most recent
edition of the Business Automobile Insurance Policy promulgated by the Insurance Services Office
(ISO).
8.20.3 Commercial General Liability insurance providing the following coverages or their equivalents:
.1
.2
.3
.4
Premises and Operations, including bodily injury and property damage coverage;
Products and Completed Operations;
Broad Form Property Damage;
Contractual Liability, including liability assumed by the Vendor under Paragraph 5.27 and
other insurable indemnification or hold harmless provisions of the Contract;
.5 Personal and Advertising Injury Liability; and
.6 X, C, and U coverage.
8.20.4 Limits of Commercial General Liability insurance coverage shall be not less than $3,000,000
combined single limit for bodily injury, personal injury and property damage arising from one
occurrence or, if separate limits are provided, not less than $3,000,000 for bodily injury, $3,000,000
for personal/advertising injury, and $3,000,000 for property damage. Such limits may be provided
by a single policy or by a combination of primary and excess policies. The policy or policies shall
provide coverage at least as broad as that provided by the Commercial General Liability policy
promulgated by the Insurance Services Office (ISO) and be written on an occurrence basis only.
Coverages shall be maintained continuously from the commencement of work until the date of final
payment. However, Products and Completed Operations coverage, with the Georgia Ports
Authority named as an additional insured, shall be continued for three years following final
3/8/2016
Automated Terminal Asset Management System RFP
Page 83 of 110
payment. The policy or policies shall be endorsed to name the Georgia Ports Authority as an
additional insured. A fully executed endorsement providing additional insured status to the
Georgia Ports Authority shall be attached to and made a part of each policy, and a copy of
each executed endorsement shall accompany each certificate of insurance filed with the
Georgia Ports Authority.
8.20.5 Vendor shall provide evidence of Professional Errors and Omissions Liability insurance. The
policy limit for professional liability insurance shall be at least $3,000,000 arising from each claim
and $3,000,000 in the aggregate. If such insurance is provided on a claims-made basis, the
contractor shall maintain the insurance for at least three years following the completion of the
work. The definition of Professional Services shall include but not be limited to the evaluation,
selection, installation and all other services related to wireless local area network systems.
8.20.6 If boat, barge, ship or other watercraft is employed in performance of work, the Workers'
Compensation and Employer's Liability policy shall be endorsed to include maritime liability
coverage for obligations and liabilities arising from the Jones Act and General Maritime Law and
the United States Longshore and Harborworkers Act. The Vendor shall also provide (a)
Protection and Indemnity Insurance, including Jones Act coverage and wreck removal coverage,
and (b) Hull coverage with running down clause covering such watercraft. The policy limit for
Protection and Indemnity Coverage shall be $1,000,000 for each accident. The policy limit for
the Hull Coverage shall equal the value of the insured watercraft.
8.20.7 Each workers’ compensation and liability insurance policy shall include a waiver of subrogation as
follows: All workers’ compensation and third-party liability insurance policies shall contain a waiver
of subrogation rights against the GPA and its employees and agents, with respect to claims or
losses insured by policy. A fully executed endorsement providing a waiver of subrogation in
favor of the GPA as required for each policy shall be attached to and made a part of each
policy, and a copy of each executed endorsement shall accompany each certificate of
insurance filed with the GPA.
8.20.8 Certificates of insurance shall be provided to the GPA and not later than the date GPA-Vendor
Agreement bearing the Vendor's signature is delivered to the GPA. Such certificates shall be in a
form acceptable to the GPA, and shall show the policies with all required coverages and
endorsements. All required endorsements shall be fully executed and shall accompany
each certificate of insurance filed with the GPA.
8.20.9 The certificate(s) of insurance shall contain a provision whereby the insurer(s) issuing coverage
is required to notify GPA Risk Management Department at least 30 days in advance of any
cancellation or non-renewal of insurance noted on the certificate.
8.21 PROPERTY INSURANCE:
8.21.1 The GPA shall purchase and maintain property insurance to cover the property in the course of
construction. Such insurance shall provide coverage solely for the project or the portion of project
that includes construction. The units of insurance shall be in the amount of the initial Contract Sum
as well as subsequent modifications thereto up to a maximum of $20,000,000 for any one loss
subject to the policy terms and conditions and the following exceptions:
1. $10,000,000 limit for a loss from flood or earthquake;
2. $1,000,000 limit for temporary storage;
3. $1,000,000 limit for covered property in transit.
Such insurance shall cover property employed in construction while at the project site and
property of the GPA, including materials and supplies that will become a permanent part of the
construction, used in a part of or incidental to the construction operations while the property is
located in the U.S. (excluding Hawaii) or Canada. This property insurance shall not include
coverage for Vendor's equipment, including but not limited to mobile equipment, tools, and/or
toolboxes. This property insurance shall not include coverage for loss or damages caused by or
resulting from the rebuilding or refurbishment of cranes unless the project is specifically
scheduled for coverage. Such property insurance shall be maintained, unless otherwise provided
in the Contract Documents or otherwise agreed to in writing by all persons and entities who are
3/8/2016
Automated Terminal Asset Management System RFP
Page 84 of 110
beneficiaries of such insurance, until final payment has been made as provided in Paragraph 9.10
or until no person or entity other than the GPA has insurable interest in the property covered by
the insurance provided for by this Paragraph 11.2, whichever is earlier.
8.21.1.1 Property insurance shall be underwritten on a replacement cost basis in a "special" policy
format and shall insure against the perils of fire and extended coverage including (but not
limited to), without duplication of coverage, theft, vandalism, malicious mischief, and
collapse. Coverage for other perils shall not be provided unless otherwise stated in the
Contract Documents.
8.21.1.2 If the GPA does not intend to purchase such property insurance required by the Contract
and with all of the coverages in the amount described above, the GPA shall so inform the
Vendor in writing prior to commencement of the work. The Vendor may then effect
insurance, which will protect the interests of the Vendor, Subcontractors and Subsubcontractors in the work, and by appropriate Change Order the cost thereof shall be
charged to the GPA. If the Vendor is damaged by the failure or neglect of the GPA to
purchase or maintain insurance as described above, without so notifying the Vendor, then
the GPA shall bear all reasonable costs properly attributable thereto.
8.21.2 If the Vendor requests in writing that insurance for risks other than those described herein or for
other special hazards be included in the property insurance policy, the GPA shall, if possible,
include such insurance, and the cost thereof shall be charged to the Vendor by appropriate
Change Order.
8.21.3 A loss insured under GPA's property insurance shall be settled by the GPA as fiduciary and made
payable to the GPA as fiduciary for the insureds, as their interests may appear, subject to
requirements of any applicable mortgagee clause and of Subparagraph 11.2.4. The Vendor shall
pay Subcontractors their just shares of insurance proceeds received by the Vendor, and by
appropriate agreements, written where legally required for validity, shall require Subcontractors to
make payments to their Sub-subcontractors in similar manner.
8.21.4 The GPA as fiduciary shall have power to negotiate a settlement for a property loss with insurers
on behalf of the Vendor and any Subcontractor.
8.22 CANCELLATION: GPA reserves the right to cancel any contract in whole or in part without penalty due
to non-appropriation of funds or for failure of the contractor to comply with terms, conditions, and
specifications of this contract.
8.23 PUBLIC RECORDS ACCESS: It is the intention of the state to maintain an open and public process in
the solicitation, submission, review, and approval of procurement activities.
Bid/proposal openings are public unless otherwise specified. Records may not be available for public
inspection prior to issuance of the notice of intent to award or the award of the contract.
8.24 PROPRIETARY INFORMATION: Any restrictions on the use of data contained within a request, must
be clearly stated in the bid/proposal itself. Proprietary information submitted in response to a request will
be handled in accordance with applicable GPA procurement regulations and the Georgia public records
law. Proprietary restrictions normally are not accepted. However, when accepted, it is the vendor's
responsibility to defend the determination in the event of an appeal or litigation.
8.24.1 Data contained in a bid/proposal, all documentation provided therein, and innovations developed
as a result of the contracted commodities or services cannot be copyrighted or patented. All data,
documentation, and innovations become the property of GPA.
8.25 RECYCLED MATERIALS: GPA is required to purchase products incorporating recycled materials
whenever technically and economically feasible. Bidders are encouraged to bid products with recycled
content which meet specifications.
3/8/2016
Automated Terminal Asset Management System RFP
Page 85 of 110
8.26 MATERIAL SAFETY DATA SHEET: If any item(s) on an order(s) resulting from this award(s) is a
hazardous chemical, as defined under 29CFR 1910.1200, provide one (1) copy of a Material Safety Data
Sheet for each item with the shipped container(s) and one (1) copy with the invoice(s).
8.27 PROMOTIONAL ADVERTISING / NEWS RELEASES: Reference to or use of GPA, any of its
departments, agencies or other subunits, or any state official or employee for commercial promotion is
prohibited. News releases pertaining to this procurement shall not be made without prior approval of
GPA. Release of broadcast e-mails pertaining to this procurement shall not be made without prior
written authorization of the contracting agency.
8.28 IMDEMNIFICATION AND HOLD HARMLESS: Vendor shall indemnify, protect, save and hold harmless
GPA, its members, directors, officers, employees and agents, against any expense, loss or liability paid,
suffered or incurred, including any environmental fines and/or penalties, as a result of any breach by
Vendor, Vendor's agents, servants, employees, patrons, contractors or subcontractors, visitors or
licensees of any covenant or condition of this Agreement or as the result of Vendor's use or occupancy
of GPA property or the carelessness, negligence or improper conduct of Vendor, Vendor's agents,
servants, employees, patrons, contractors or subcontractors, suppliers, visitors or licensees. Such
indemnification shall be to the extent caused in whole or in part by negligent acts or omissions by
Vendor, its agents, servants, employees, patrons, contractors, subcontractors, suppliers, visitors or
licensees. Vendor agrees to defend GPA from any legal or equitable actions brought against GPA based
on this Agreement and pay all expenses and attorneys fees in connection therewith. Indemnity herein
arising out of any violation by Vendor of any environmental rule, regulation or law of any state and/or
federal agency in force now or enacted in the future shall survive the initial term and any renewal option
period set forth herein. All Vendors’ indemnity obligations herein shall be covered by a policy or policies
of insurance. Nothing herein shall be construed as requiring Vendor or any other person, firm or
corporation to indemnify against any portion or percentage of such claim or loss, if any, caused by the
negligence of GPA, its members, directors, officers, employees and agents.
3/8/2016
Automated Terminal Asset Management System RFP
Page 86 of 110
APPENDIX
3/8/2016
Automated Terminal Asset Management System RFP
Page 87 of 110
TABLE A: KEY TERMINAL INFRASTRUCTURE
The items identified here correlate to labeled items or areas on Figures 1 and 2.
ID
1
2
3
4
5
6
7
Description
Gate 1
Gate 2
Gate 3
Gate 4
Gate 5
Gate 6
Gate 7
8
Personnel Gate
A
B
C
D
E
ICTF
Warehouses
GPA Admin Building
Rapid Dispatch
Pedestals
F
Canopy
G
Gate 4 Gatehouse
H
Gate 3 Control Room
I
J
Tank
Perimeter
K
L
Cold Storage
Maintenance & Port
Police
General Cargo Admin
Office
Customs Warehouse
Warehouses
Rae’s Hall
GPA Maintenance
Facilities
Rail Office
Annex 1
Credentialing Center
Leased Office Facilities
M
N
O
P
Q
R
S
T
U
3/8/2016
Notes
POV Gate
POV Gate – No Access by GPA
Truck Gate
Truck Gate
POV Gate
Truck Gate to Rapid Dispatch
Intermodal Gate between Terminal and
ICTF
Man Trap
Rail Yard
Rented by 3rd Party
Main Administration Building
Wheeled Operations
1st Stop for Truckers, includes scales and
credential checks
2nd Stop for Truckers, includes visual
inspections
Includes “kitchen” for processing as well as
LA King server room
Includes fiber connection to Gate 4
Operations
Large tank to be dismantled in 2008
This is the area within which the WLAN
shall be ubiquitous
Leased to 3rd Party
Includes VACIS
Operated by GPA
Redundant LAN Switch
GPA Administration
Leased to 3rd party
Automated Terminal Asset Management System RFP
Page 89 of 110
FIGURE 1: EXISTING SITE PLAN
3/8/2016
Automated Terminal Asset Management System RFP
Page 91 of 110
FIGURE 2: FUTURE SITE PLAN
3/8/2016
Automated Terminal Asset Management System RFP
Page 93 of 110
FIGURE 3: EXISTING TRUCK PROCESS
Incoming
Truck
LA KING
Pedestal
Print Mission
Ticket(s)
YES
Is All Required Data
Satisfactory?
NO
Is Trouble
Resolved?
Trouble Gate
NO
YES
NO
Is Container or
Chassis Damaged?
Canopy
Inspection
YES
Is Truck
Bobtail?
Same Shipper for Both Missions
Wheeled
Operation
Print EIR
Drop
Container
Dismount
Chassis &
Container
Special
Circumstances*
Drop
Chassis
Mount
Chassis &
Container
1-Way Mission (Bobtail Out)
Pick Up
New
Container
1-Way Mission (Bobtail Out)
Pick Up
New
Chassis
NO
Does Truck Pass
Exit Inspection?
Inspection Clerk
makes Report
NO
Standard
Operation
Truck
Returns to
Terminal to
Complete
Mission
YES
Exit Inspection
YES
Print EIR
Truck
Exits
Terminal



3/8/2016
Automated Terminal Asset Management System RFP
*Examples:
Bundled Chassis
Personal Trailer
Non-container Load
Page 94 of 110
FIGURE 4: CONCEPTUAL FUTURE TRUCK PROCESS
Incoming
Truck
LA KING
Pedestal
Portal
Did OCR link
truck to mission?
Manual Entry Required by
Kitchen Clerk
NO
YES
Print Mission
Ticket(s)
YES
Is All Required Data
Satisfactory?
NO
NO
Is Truck
Bobtail?
Canopy
Inspection
YES
Is Trouble
Resolved?
Trouble Gate
YES
NO
Standard
Operation
NO
YES
Inspection Clerk
Makes Report
Print EIR
Wheeled
Operation
Drop
Container
Dismount
Chassis &
Container
Drop
Chassis
Mount
Chassis &
Container
Pick Up
New
Container
Truck
Returns to
Terminal to
Complete
Mission
Special
Circumstances*
1-Way Mission (Bobtail Out)
Pick Up
New
Chassis
1-Way Mission (Bobtail Out)
Same Shipper for Both Missions
Is Container or
Chassis Damaged?
Exit Portal
NO
Manual Entry Required by
Inspection Clerk



Did OCR link
truck to mission?
*Examples:
Bundled Chassis
Personal Trailer
Non-container Load
YES
NO
3/8/2016
Does Truck Pass
Exit Inspection?
YES
Print EIR
Automated Terminal Asset Management System RFP
Truck
Exits
Terminal
Page 95 of 110
TABLE B: EXISTING DATA FLOW LINK DESCRIPTIONS
Link
Type
From
To
1
WAN
Internet
Computer
2
Cat-5
LA King
Subsystem
Navis Server
Navis Server
LA King
Subsystem
LA King
Subsystem
Kitchen Clerks
Kitchen Clerks
LA King
Subsystem
Trouble Gate
Kitchen Clerks
Kitchen Clerks
Trouble Gate
3
4
Cat-5
Phone
Cable
5
6
3/8/2016
Cat-5
Cat-5
LA King
Subsystem
Data Sent
Navis Server
Truck License Number
Trucking Company
Container Number
Container Owner (line)
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
Bundled Chassis
Bundled Flatracks
Booking Number
Bkg Status/ Empty or Full
Booking Owner (line)
OOG
Hazardous
Booking/EDO Number
Truck Weight
Lane Number
Notes
2
1
1
1
2
2
2
2
2
2
1
1
1
1
1
2
1
1
Print Mission Ticket (file)
Print EIR (file)
Truck Present
Credential Accepted
Analog Video Signal from Camera
Analog Voice Signal from Pedestal Microphone
Camera Control Signal
Voice from Kitchen Microphone
NEXT Queue
Lane Selection
Analog Audio Signal from Phone
Analog Video Signal from Security Camera
Analog Video Signal from Document Camera
Analog Audio Signal from Clerk Microphone
Print Mission Ticket
Trouble Gate
Trouble Gate
LA King
Subsystem
AMAG
Navis
Credential Accepted/Rejected
Document Camera Video
Automated Terminal Asset Management System RFP
Page 96 of 110
7
Cat-5
LA King
Subsystem
Pedestal
1st Pedestal
LA King
Subsystem
Print Mission Ticket (file)
Camera Control Signals
Voice to Speaker
Analog Video Signal from Camera
Analog Voice Signal from Pedestal Microphone
Weight from Scale
Truck Present
8
Cat-5
Pedestal
AMAG
Credential ID
9
Cat-5
LA King
Subsystem
Canopy
Print EIR (file)
10
Cat-5
Navis Server
Shared file for
SAP
11
Cat-5
Navis Server
Teklogix Server
Job Number
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Lane
Bundle (yes/no)
Print EIR
Location
Teklogix Server
Navis Server
Commit
Truck License number
Container Number
Container Location
Trucking Company
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Lane
Bundle (yes/no)
3/8/2016
Container ID
Date/time Container Received
Date/time Container Delivered
Automated Terminal Asset Management System RFP
Page 97 of 110
Data Complete – Print EIR
12
13
14
15
3/8/2016
NBDL
NBDL
NBDL
902
MHz
Teklogix Server
CHE (Vehicle
Mounted)
CHE (Vehicle
Mounted)
Teklogix Server
Teklogix Server
Field Inventory
(Handheld)
Field Inventory
(Handheld)
Teklogix Server
Teklogix Server
Vessel Ops
(Handheld)
Vessel Ops
(Handheld)
Teklogix Server
Teklogix Server
Gate Clerk
(Gates 4 & 6
Handheld)
Gate Clerk
(Gates 4 & 6
Handheld)
Teklogix Server
Container Location
Truck License Number
Container Number
Container Location
Truck License Number
Container Number
Commit
Container Location
Container Number
Container Location
Container Number
Container Location
Container Number
Container Location
Container Number
Commit
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Bundle (yes/no)
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
Automated Terminal Asset Management System RFP
Page 98 of 110
PIN Number
Selection
Lane
Bundle (yes/no)
Commit
16
802.11
17
3/8/2016
Cat-5
Navis Server
Gate Clerk
(Gate 3
Handheld)
Gate Clerk
(Gate 3
Handheld)
Navis Server
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Lane
Bundle (yes/no)
Commit
Kitchen Clerks
Navis/Express
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Booking Number
Booking Status/Empty or Full
Booking
OOG
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Bundle (yes/no)
Automated Terminal Asset Management System RFP
Page 99 of 110
Container GenSet Number
PIN Number
Selection
Bundled Chassis
Bundled Flatracks
18
Cat-5
Trouble Gate
AMAG
Analog Video Signal from Security Camera
Analog Video Signal from Document Camera
Notes:
1. Data required when applicable.
2. Data not required.
3/8/2016
Automated Terminal Asset Management System RFP
Page 100 of 110
TABLE C: FUTURE DATA FLOW LINK DESCRIPTIONS
Link
Type
From
To
1
WAN
Internet Computer
2
Cat-5
3
4
5
Cat-5
Phone
Cable
Cat-5
3/8/2016
Data Sent
Notes
Navis Server
Truck License Number
Trucking Company
Container Number
Container Owner (line)
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
Bundled Chassis
Bundled Flatracks
Booking Number
Bkg Status/ Empty or Full
Booking Owner (line)
OOG
Hazardous
Booking/EDO Number
2
1
1
1
2
2
2
2
2
2
1
1
1
1
1
2
1
1
LA King Subsystem
Navis Server
Truck Weight
Lane Number
Truck ID
Chassis Number
Container Number
GenSet Number
Container Size
Navis Server
LA King Subsystem
LA King Subsystem
Kitchen Clerks
Kitchen Clerks
LA King Subsystem
Trouble Gate
Kitchen Clerks
Kitchen Clerks
Trouble Gate
LA King Subsystem
Trouble Gate
Trouble Gate
LA King Subsystem
Print Mission Ticket (file)
Print EIR (file)
Truck Present
Credential Accepted
Analog Video Signal from Camera
Analog Voice Signal from Pedestal
Microphone
Camera Control Signal
Voice from Kitchen Microphone
NEXT Queue
Lane Selection
Analog Audio Signal from Phone
Analog Video Signal from Security
Camera
Analog Video Signal from
Document Camera
Analog Audio Signal from Clerk
Microphone
Print Mission Ticket
Document Camera Video
Automated Terminal Asset Management System RFP
Page 101 of 110
6
Cat-5
AMAG
Navis
7
Cat-5
LA King Subsystem
Pedestal
Pedestal
LA King Subsystem
Credential Accepted/Rejected
Print Mission Ticket (file)
Camera Control Signals
Voice to Speaker
Analog Video Signal from Camera
Analog Voice Signal from Pedestal
Microphone
Weight from Scale
Truck Present
8
Cat-5
Pedestal
AMAG
Credential ID
9
Cat-5
LA King Subsystem
Canopy
Print EIR (file)
Light Signal
Canopy
LA King Subsystem
Bar Code
Container ID
Date/time Container Received
Date/time Container Delivered
10
Cat-5
Navis Server
Shared file for SAP
11
Cat-5
Navis Server
Teklogix Server
Job Number
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Lane
Bundle (yes/no)
Print EIR
Location
Teklogix Server
Navis Server
Commit
Truck License number
Container Number
Container Location
Trucking Company
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Lane
3/8/2016
Automated Terminal Asset Management System RFP
Page 102 of 110
Bundle (yes/no)
Data Complete – Print EIR
12
13
NBDL
802.11
14
15
802.11
3/8/2016
Teklogix Server
CHE (Vehicle Mounted)
Container Location
Truck License Number
Container Number
CHE (Vehicle
Mounted)
Teklogix Server
Container Location
Truck License Number
Container Number
Commit
Navis
CHE (Vehicle Mounted)
Container Location
Truck License Number
Container Number
CHE (Vehicle
Mounted)
Navis
Container Location
Truck License Number
Container Number
Commit
Navis
Field Inventory
(Handheld)
Field Inventory
(Handheld)
Navis
Navis
Gate Clerks
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Selection
Bundle (yes/no)
Gate Clerks
Navis
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Container GenSet Number
PIN Number
Container Location
Container Number
Container Location
Container Number
Automated Terminal Asset Management System RFP
Page 103 of 110
Selection
Lane
Bundle (yes/no)
Commit
16
802.11
Navis
Vessel Ops (Handheld)
Container Location
Container Number
Vessel Ops
(Handheld)
Navis
Container Location
Container Number
Commit
17
Cat-5
Kitchen Clerks
Navis/Express
18
Cat-5
Trouble Gate
AMAG
19
802.11
Quay Crane
RFID Server
20
Cat-5
RFID Server
LA King Subsystem
21
Cat-5
or
802.11
Canopy
RFID Server
Truck ID
22
Cat-5
or
802.11
Portal
RFID Server
Truck ID
23
Cat-5
or
Coax
Portal
OCR Server
Video Signal
Truck Present
3/8/2016
Truck License Number
Trucking Company
Container Number
Container ISO Code
Container Size Type Height
Chassis Number
Chassis Owner
Chassis Size Type
Chassis GenSet Number
Booking Number
Booking Status/Empty or Full
Booking
OOG
Container GenSet Number
PIN Number
Selection
Bundled Chassis
Bundled Flatracks
Analog Video Signal from Security
Camera
Analog Video Signal from
Document Camera
CHE ID
Truck ID
Location
Date/Time
Automated Terminal Asset Management System RFP
Page 104 of 110
24
Cat-5
or
802.11
Rail Server
Navis
25
Coax
or Cat5
Rail OCR Gate
Rail Server
26
Cat-5
PDS Server
Navis
Navis
PDS Server
Container ID
Rail Car ID
Rail Car Position
Container Position
Date/Time
Video Data
Rail Car Presence by Lane
RFID Data
Truck/CHE Position
Weight status change
5th Wheel status change
Twist Lock status change
Date/Time
Shock or Rapid Deceleration
Report Query
Status Query
27
802.11
Quay Crane
OCR Server
Container OCR Video
Container Present
28
802.11
Quay Crane
PDS Server
Crane Position
Twist Lock status change
Date/Time
29
Cat-5
OCR Server
LA King Subsystem
30
802.11
CHE (Vehicle
Mounted)
PDS Server
PDS Server
CHE (Vehicle Mounted)
CHE (Vehicle
Mounted)
RFID Server
31
802.11
Location
Date/time
Container Number
Chassis ID
GenSet ID
Container Size
Truck/CHE Position
Weight status change
5th Wheel status change
Twist Lock status change
Date/Time
Shock or Rapid Deceleration
Report Query
Status Query
Truck ID
Notes:
1. Data required when applicable.
2. Data not required.
3/8/2016
Automated Terminal Asset Management System RFP
Page 105 of 110
FIGURE 5: EXISTING DATA FLOW
SAP
10
Data
File
1
Web Access
NAVIS
EXPRESS
SPARCS
Trouble Gate
Printer
Security Camera
Document Camera
Phone
Handheld
Ship Load Plan
Gate Lane Table
Container Yard Plan
5
Gate 3
Clerk
16
11
CHE
Vehicle
Mounted
Equipment
6
2
18
17
4
Kitchen Clerks
3
LA King Consol
LA KING
Subsystem
12
AMAG
TEKLOGIX
Server
Credential Table
BDU
15
7
13
9
Field
Inventory
Canopy
Printer
Pedestal
Magnetic Card Reader
Camera
Speaker
Scale
Printer
Microphone
3/8/2016
Gates 4
& 6 Clerk
Handheld
8
Automated Terminal Asset Management System RFP
Handheld
14
Vessel
Ops
Handheld
Page 106 of 110
FIGURE 6: CONCEPTUAL FUTURE DATA FLOW
Rail
Server
SAP
Trouble Gate
Data
File
18
Magnetic Card Reader
Document Camera
Security Camera
Printer
Phone
Web Access
5
24
1
Field
Inventory
Rail Yard
OCR
Position Loops
RFID
25
Vessel
Ops
16
Handheld
10
Handheld
4
NAVIS
EXPRESS
SPARCS
17
Kitchen Clerks
Ship Load Plan
Gate Lane Table
Container Yard Plan
3
LA King Consol
2
14
15
Gate
Clerks
Handheld
13
26
6
Canopy
Printer
Barcode Reader
RFID Reader
Speaker or Light
9
CHE
AMAG
LA KING
Subsystem
Credential Table
BDU
Vehicle
Mounted
Equipment
7
30
20
11
TEKLOGIX
Server
8
21
P
o
r
t
a
l
23
22
3/8/2016
PDS
Server
29
OCR
Server
RFID
Server
Pedestal
Magnetic Card Reader
Camera
Speaker
Scale
Printer
Microphone
27
28
Quay Crane
OCR
RFID
19
12
CHE
Vehicle
Mounted
Equipment
31
Automated Terminal Asset Management System RFP
Page 107 of 110
DRAWING LEGEND
Automatic Function
Requires Manual Data Input
Mobile Equipment Requiring Some Manual Input
Truck Activity
Decision
Printer or Something Being Printed
Flat Data File
3/8/2016
Automated Terminal Asset Management System RFP
Page 108 of 110
TABLE D: NETWORK NODES
Location
Gate 3 Control Room
Gate 3 Canopy
Node
Cisco 3500 Series Switch
10/100 Linksys switch**
Description
Redundant Gigabit backbone
Connected to Cisco 3500 10/00 port
Connection speed
10/100 access
10/100 access
Container Port Bldg Control
Room
Gate 4 Gatehouse
Cisco 3500 Series Switch
10/100 Linksys switch
Redundant Gigabit backbone
Connected to Cisco 3500 10/00 port via fiber transceivers
10/100 access
10/100 access
Gate 6 Booth 4
Gate 4 Canopy
Cisco 3500 Series Switch
10/100 Linksys switch**
Redundant Gigabit backbone
Connected to Cisco 3500 10/00 port
10/100 access
10/100 access
Maintenance Storeroom
Cisco 3500 Series Switch
10/100 access
Cal Cartage
11Mbps non-root bridge**
Redundant Gigabit backbone
Wireless bridge with the root on a Cisco 3500 10/100 & non-root
10/100
Maintenance Autoshop
CB3 Cold Storage
WH24
10base2 hub
10/100 Linksys switch
10/100 Linksys switch**
Connected to Cisco 3500
Connected to Cisco 3500 10/00 port via fiber transceivers
Dark fiber available
Field Office
Cisco 3500 Series Switch
Redundant Gigabit backbone
10/100 access
GCT Admin Bldg
Gate 5 Gatehouse
Gate 7 Gatehouse
Cisco 3500 Series Switch
10/100 Linksys switch
10/100 Linksys switch
10/100 access
10/100 access
10/100 access
CB7 pole
FIP at HWY 25 & 307
FIP at Hwy 25 and Grange Rd
11Mbps non-root bridge**
10/100 Linksys switch**
10/100 Linksys switch**
Redundant Gigabit backbone
Connected to Cisco 3500 10/00 port via fiber transceivers
Connected to Cisco 3500 10/00 port via fiber transceivers
Wireless bridge with the root on a Cisco 3500 10/100 & non-root
10/100
Dark fiber available
Dark fiber available
Annex 2 - Credentialing Center
Cisco 3500 Series Switch
Redundant Gigabit backbone
10/100 access
WH83A Dock Office
WH83A
Cisco 3500 Series Switch
10base2 hub
Redundant Gigabit backbone
Connected to Cisco 3500
10/100 access
10Mbps half-duplex
3/8/2016
Automated Terminal Asset Management System RFP
Page 109 of 110
10/100 access*
10Mbps half-duplex
access
10/100 access
10/100 access*
access
Annex 1 - ATT&T Building
Cisco 3500 Series Switch
Redundant Gigabit backbone
10/100 access
Raes Hall
Cisco 3500 Series Switch
10/100 access
Ceres
11Mbps non-root bridge**
CFS
Gate 1 Gatehouse
Gate 3 Gatehouse
Raes Hall Water Tower
11Mbps non-root bridge
10/100 Linksys switch
10/100 Linksys switch
10/100 Linksys switch
Redundant Gigabit backbone
Wireless bridge with the root on a Cisco 3500 10/100 & non-root
10/100
Wireless bridge with the root on a Cisco 3500 10/100 & non-root
10/100
Connected to Cisco 3500 10/00 port via fiber transceivers
Connected to Cisco 3500 10/00 port via fiber transceivers
Connected to Cisco 3500 10/00 port via fiber transceivers
Container Port Trailer
Cisco 3500 Series Switch
Redundant Gigabit backbone
10/100 access
ICTF Bldg
ICTF road
Cisco 3500 Series Switch
10/100 Linksys switch**
Redundant Gigabit backbone
Connected to Cisco 3500 10/00 port via fiber transceivers
10/100 access
10/100 access
* 11Mbps wireless link in the middle
** lit fiber or avail.cable, switch still needed
3/8/2016
Automated Terminal Asset Management System RFP
Page 110 of 110
10/100 access*
10/100 access*
10/100 access
10/100 access
10/100 access