0% found this document useful (0 votes)
95 views9 pages

Whitepaper - Open Interfaces in A Terminal Automation Platform PDF

Uploaded by

Ganeshmohite
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
95 views9 pages

Whitepaper - Open Interfaces in A Terminal Automation Platform PDF

Uploaded by

Ganeshmohite
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Open interfaces

in a terminal
automation
platform.
AUTHORS

TIMO LEHTO
JARI HÄMÄLÄINEN
HEIMO POUTANEN

September 2017
OPEN INTERFACES IN A TERNIMAL

Open interfaces in a terminal


AUTOMATION PLATFORM

automation platform.
EXECUTIVE SUMMARY.

Across the globe, container terminal automation is advancing rapidly. Automation,


including the insights learned from the data it produces, is almost universally recognised
as the future of improved container handling productivity, safety and business
performance. However, when compared with other fields (such as the automotive
manufacturing or process industries), automation in the container handling business is
still in its relative infancy. This has meant that until recently, most terminal automation
systems have been based on extensive integration of various subsystems and solutions,
rather than conceived as complete end-to-end automation systems such as those in
other industries.
Development of
This white paper argues for a systemic approach in designing a terminal automation
platform. A key feature of this platform is the availability of new, open application standardisation.
interfaces that enable terminal operators to customise their automation deployments,
allowing third-party developers to provide their own offerings that are interoperable HISTORICAL PERSPECTIVE.
with the automation platform. These additional software interfaces, which supplement
the application-independent core software components of the terminal automation In order for terminal automation to develop to the next level in speed of
deployment and operational efficiency – and for operators as well as other
system, significantly extend the capabilities of the existing Kalmar TLS (Terminal Logistics
industry players to be able to reap the benefits of this development – a
System). Previously, TLS has only provided application-specific interfaces for a limited
significantly higher level of standardisation is required.
number of functionalities.

Currently, a major challenge for most terminal automation projects is that


With terminal
When combined with support services and a developer infrastructure, these open
interfaces pave the way for robust and diverse business ecosystems around terminal
many design and implementation questions need to be solved anew operators unsure
automation that provide new opportunities for terminal operators, independent
each time. These questions range from basic connectivity and equipment
functionality to user interfaces for applications and safety guidelines. With
of the exact
developers and automation system providers. Ultimately, terminal operators will have
terminal operators unsure of the exact specifications needed for a terminal specifications
a broader range of capabilities to develop their systems with agility, based on their
individual business processes and needs.
automation deployment, system providers often need to ”reinvent the wheel”
for each customer case.
needed for terminal
automation
As an equipment-agnostic approach, the terminal automation platform also enables a
vast range of new systems and equipment to be connected to the automation solution.
A markedly different situation can be seen in general process automation.
Initially, each manufacturer developed closed systems with unique interfaces
deployment,
Finally, the open interfaces of a terminal automation system enable a holistic view of for their equipment, but over the decades, the industry converged on a set system providers
data from multiple sources, enabling terminal operators to optimise their operations
continuously and with greater ease.
of interfaces that enable seamless connectivity with standardised technology.
This development shifted the competitive focus of automation technology
often need to
providers away from low-level interfaces and towards higher-value ”reinvent the
This paper provides an overview of the new application interfaces that Kalmar is making
available and examines some possibilities by which terminals and developers can utilise
automation systems. Once the connectivity is standardised, diverse industry
players can come together to create robust ecosystems that further develop
wheel” for each
and benefit from these interfaces. the capabilities of their equipment and software applications. customer case.

2 3
INDUSTRY OUTLOOK FOR STANDARDISATION
IN TERMINAL AUTOMATION.
OPEN INTERFACES IN A TERNIMAL

In many ways, the development and gradual adoption of container terminal


automation mirrors the steps taken by process automation in recent decades;
however, some significant differences also exist.
AUTOMATION PLATFORM

Firstly, when compared to existing highly automated major industries, the container
terminal business is significantly smaller. Resultantly, automation will be adopted
at a slower rate, and the development of the entire field does not have the same
”critical mass” as, for example, automotive manufacturing.

Secondly, at least at the time of writing (2H2017), the container shipping industry
lacks a consistent force of industry consortia and/or international regulatory bodies
that would have the expertise, motivation and influence to define a ”top-down”
set of industry standards for terminal automation at the needed level of detail.
Simultaneously, in a highly competitive, volatile industry, port operators and shipping
lines are unlikely to find – at least in the foreseeable future – common ground for

defining these standards together from the customers’ point of view. Terminal automation
As a result of these factors, it is reasonable to expect that container terminal platform: What and why?
automation will progress through a de-facto standardisation effort of established
automation system providers defining the required interfaces and selectively
Despite the continuous advances in terminal automation over the last
opening them for wider utilisation. The opening up of a set of field-proven, robust
few years, container handling is still a relatively new industry to embrace
interfaces with their associated support tools creates common ground on which
automation. Industries such as car manufacturing began automating their
solutions can be built, customised and expanded, and connected with manual or
operations several decades ago, and have thus been able to develop a
automated equipment from any manufacturer. The Kalmar terminal automation
significantly wider perspective on how to deploy large-scale automation
platform interfaces described in this paper are intended as the first step in this
systems.
direction.
Until recently,
By contrast, until recently, container terminal automation has primarily
been conceived as an ”add-on” to an equipment investment, instead of
container
a comprehensive end-to-end solution. Automation solutions have been terminal
assembled as one-off projects that have required extensive integration of
diverse systems and solutions, often from several vendors.
automation
has primarily
At the same time, as terminal automation advances, the focus in industry
deployments is shifting from a limited number of new greenfield sites to
been
automating hundreds of existing container terminals. These brownfield conceived as
projects require that the automation system can interface with diverse
existing fleets and processes at widely differing levels of automation. To
an ”add-on” to
reap the full benefit of terminal automation and to fully utilise their existing an equipment
equipment and software, terminal operators need the ability to flexibly
customise their solutions, possibly with the help of third-party developers.
investment.
As seen in other, more highly automated industries, successful large-scale
container terminal automation will require a balanced combination of two
things: firstly, an approach that treats terminal automation as a complete
integrated system, and, secondly, open application interfaces that enable
collaboration as well as the creation of ecosystems to further develop the
capabilities of the automation platform.

4 5

In the context of this white paper, an open terminal automation platform
Definition of an open terminal
OPEN INTERFACES IN A TERNIMAL

refers to additional software interfaces that extend the application-

automation platform. independent core software components of a terminal automation


system. This significantly broadens the capabilities of the existing Kalmar
TLS (Terminal Logistics System), which has formerly only provided
AUTOMATION PLATFORM

application-specific interfaces for a limited number of functionalities,


KALMAR TLS IS A PROVEN most notably for integration with the Terminal Operating System (TOS)
ARCHITECTURE FOR and equipment control systems. Previously, these existing interfaces
TERMINAL AUTOMATION.
TOS

have only been available to selected customers and have been The added
TOS
integration
dependent on in-house development by Kalmar. capabilites
3rd party ECS
integration For terminal operators, the added capabilities that open interfaces that open
AGV

CHE
ASC
bring to Kalmar TLS can streamline decision-making by integrating all interfaces
data sources as well as control and monitoring functions into a single,
AutoTT
Automation STS
Gate operations
integration
vendor-independent solution. bring to
Remote monitoring
Integration
and control Kalmar TLS
With the addition of new interfaces that enable direct access to the
AutoRTG
capabilities
Application
communication
AutoRMG

application-independent automation platform core (and thus basic can streamline


History data
management system functionality), the concept of the Kalmar TLS is extended with decision-
additional capabilities for partners and developers to customise and
AutoEquipment
Visualisation AutoStrad

augment customers’ terminal automation solutions. This aids and making.


speeds the development of new applications, opening up a wider
er
T

mi range of potential suppliers and partners that can work with terminal
nal t em
L o g is ti c s S y s automation.

KALMAR TLS GETS STRONGER WITH


AN OPEN AUTOMATION PLATFORM OFFERING.
Key functionalities
TOS and features.
Remote monitoring
and control TOS The concept of an integrated terminal automation platform with open
integration
interfaces benefits all parties throughout the industry. Existing and
3rd party ECS
Integration Historical data integration new users (terminal operators) will be able to customise and augment
capabilities management ASC

AGV their solutions with the required functionality. At the same time, open
CHE
Automation Gate operations interfaces enable smooth and consistent integration of third-party
Automated STS
integration
3rd party CHEs AutoTT
Remote monitoring equipment into the original automation system. Technology development
Extension and control
to visualisation Integration partners may integrate their products with the automation platform in
Connecting new capabilities order to extend the capabilities of the system as well as creating new
native applications
Application AutoRMG

History data communication markets for their own software and hardware products.
AutoRTG

management

AutoEquipment Visualisation AutoStrad The terminal automation platform also provides a holistic view of data
from multiple sources, allowing terminal operators to optimise their
er operations with greater ease.
T

mi
nal t em
L o g is ti c s S y s

6 7
INTEGRATION CAPABILITIES.
OPEN INTERFACES IN A TERNIMAL

DAQ 3rd Party key


DAQ IPC key

These keys enable connecting devices (such as PLCs, sensors etc.) to the Kalmar
AUTOMATION PLATFORM

Integration automation platform through common interfaces based on standard protocols


capabilities(Multi-CAN, Iso-on-TCP, Hostlink, Linux SHM, etc.). Alternately, the DAQ IPC
key enables the creation of custom interface protocols that can be added to the
framework when needed.

EIS Platform key


EIS Communication key

Connecting to Historical data Remote monitoring Automated


Similar to an enterprise service bus, these keys extend the functionalities of the
Extension to visualisation Integration capabilities
native applications management and control 3rd party CHEs
system by enabling custom bundles for additional services or custom interfaces.
Kalmar, for example, uses this to connect different TOS providers to Kalmar
digital solutions.
Figure: System architecture of the
Automation Platform.

A terminal automation platform encompasses several types of system elements. HISTORICAL DATA MANAGEMENT.
These include ‘core components’ that provide access to automation platform History Data Service key
data as well as tools for presenting data; ‘digital services’ that enable creating Kalmar Cloud Interface key
new value from available data; and ‘controllers’ that handle the integration with
equipment and automation hardware. Open interfaces enable direct access The History Data Service key enables the storing and access of data from any
to these elements, facilitating the creation of new and customised solutions in Historical data
connected digital solution in a clustered database. Stored data can include e.g.
multiple application areas.
management time-series, events, alarms or user activities. The GUI Framework and GUI Creator
keys offer ready-made widgets that can be used to visualise the data or build
In the context of this document, a key refers to an open interface or framework custom reporting solutions.
with its attendant documentation and developer toolkit. The keys are accompanied
by a partner ecosystem as well as licensing and support models for both The Kalmar Cloud is used to store, process and visualise data, which can then
developers and customers. be accessed by cloud applications through the Kalmar Cloud Interface key. The
access includes the customer’s proprietary data stored in the Cloud as well as
EXTENSIONS TO VISUALISATION. processed data provided by Kalmar.

GUI Framework key


GUI Creator key AUTOMATED 3RD PARTY CONTAINER HANDLING EQUIPMENT.
CSP Interface key
These keys define the access to the information of the fleet management solutions On-Board Safety key
Extension (for example Kalmar Fleetview). Users and developers can build their own user Motion Controller key
to visualisation interfaces utilising ready-made FleetView drag and drop widgets from Kalmar’s
widget library, or they can use open APIs to create custom widgets when needed. AutomatedThese keys are used to optimise and control equipment fleets. Options are
The framework also supports localisation and stylesheets. 3rd party CHEs
available for different operation types, ranging from automated stacking cranes
to automated RTGs, automated straddle or shuttle carriers and beyond. The
CONNECTING NEW NATIVE APPLICATIONS. Kalmar Control System Platform (CSP) includes driver modules for Kalmar
vehicle controllers but these can be replaced with custom modules to match any
Application Communication key
equipment interface.

The Application Communication key is a library that enables the easy creation of
Vehicle controllers extend the capabilities of manual equipment and prepare it for
custom applications. This API enables easy publishing and subscription of data
automation. An open interface for motion controllers enables different brands of
Connecting new between other components and applications in the system.

native applications
8 9
equipment as well as custom vehicle controllers to be connected to the automation necessary adjustments to their control room operational products
system. Vehicle controllers integrate container handling equipment with the terminal either as in-house work or with the aid of partners.
infrastructure, providing a set of gantry control, horizontal drive and positioning
OPEN INTERFACES IN A TERNIMAL

technologies that are fully supported right out of the box. Solution: Extension to visualisation keys.

The customer can build new dashboards and reports utilising the
REMOTE MONITORING AND CONTROL. data provided by the Kalmar automation system.
AUTOMATION PLATFORM

RCC Interface key


Video Camera Interface key
RC Remote I/O key
Requirement: Terminal wants to automate step-by-step a fleet of Kalmar

Remote monitoring
Remote monitoring keys make it possible to combine multiple video streams
and 3rd party cranes.

and controltousage
create views that are uniquely suited to the individual requirements of each
scenario. An open interface provides easy control of camera connections
As the first, most basic step towards terminal automation,
remote control and monitoring provide immediate productivity
and disconnections, and enables container handling equipment or terminal gains by enabling a single operator to control multiple machines
infrastructure to be fitted for example with standard analogue cameras or AXIS IP without having to physically move from one machine to another.
cameras without any proprietary hardware. Occupational safety and ergonomics are improved significantly
by bringing machine operators from the container yard into the
The RC Remote I/O key provides a failsafe connection between the container comfort of a remote control centre.
handling equipment and TLS remote control consoles. Connections and
disconnections are controlled with an open interface, and any container handling Solutions: Automated 3rd party container handling equipment keys,
equipment can be remotely operated either through a Profinet or physical I/O Extension to visualisation keys, Remote monitoring and
interface. control keys.

The customer can start with a solution based on the Kalmar


automation system and Kalmar equipment, but can later
can complement the solution with third-party equipment, while

s retaining full flexibility for equipment vendor choice. Remote

s”. Use case examples for control functionality can also be implemented for third-party
equipment as part of the Kalmar automation system. Additionally,

open interfaces. the terminal can enhance the Kalmar automation system with
new user interfaces and customised visualisation tools that cover
the third-party equipment.
Open interfaces enable a wide range of new possibilities for terminal operators
to customise their automation deployments, gain enhanced access to their
For example, a terminal can start with a Kalmar AutoRTG and
operational data and develop the system according to their business processes. A
expand the automation deployment later to include a third-party
key benefit of open interfaces is that they facilitate a joint ecosystem that benefits
remote-controlled STS crane. Or a straddle carrier terminal
all parties in the value chain. Technology developers can create and market their
can start with a fleet of Kalmar AutoStrads and expand later to
own products that are interoperable with the terminal automation system; terminal
automating existing straddle carriers from other manufacturers.
operators can add new equipment or features to their systems with minimal
business risk; and the automation system provider can offer new, advanced
capabilities that utilise third-party solutions.

Some examples of potential user cases include the following:


Requirement: Terminal needs completely new technical application as
part of their automation solution.
Requirement: Terminal operator wants to customise the look and feel of
their applications.
Open interfaces also enable the creation of completely new
Brownfield terminals have existing, tightly defined business and applications for terminal automation. Essentially any manual
administrative processes that any new automation deployment or automated process or data source can be visualised and
must accommodate. If the requirements of the process change, connected into the terminal automation system. Even if the goal
open interfaces allow terminal operators to carry out the

10 11
is not to fully automate the terminal equipment, standardised
controller interfaces enable any machine to be remotely
controlled through a single control desk and connected to
OPEN INTERFACES IN A TERNIMAL

Kalmar TLS software.

A natural way to utilise the open interfaces of the Kalmar terminal


AUTOMATION PLATFORM

automation system is for technology partners to deliver enhanced


sensor capabilities for the system. For example, machine
vision enables a host of possibilities for improving the safety
and performance of automated and semi-automated container
handling equipment, but requires highly specialised technology.

Solutions: New application development keys, Remote monitoring


and control keys, Integration capabilities keys.

With the new open interfaces, technology and software


providers can develop and sell their Kalmar integrated products
to container terminal operators. These could include, for
example, solutions for laser scanners, anti-truck lifting, truck
alignment, access control systems, target or load position
measurement, busbar electric power distribution solutions or
new connectivity solutions. Open interfaces enable technology
from other manufacturers to be easily integrated into the Kalmar
architecture.

Key enablers.
In order to be usable, the open interfaces of a terminal automation
system require a full Software Development Kit (SDK) as well as some
The basic
degree of support from the provider of the system. In addition to the structure of the
actual open API definitions, the SDK will need to include, at a minimum,
developer documentation, tools and support. The application interfaces,
licensing model
together with their support and documentation, constitute the keys for the Kalmar
that enable access to the Kalmar automation platform. To summarise,
the keys are licensable modules consisting of an open interface with its
automation
attendant SDK, documentation and support. platform SDK is
The basic structure of the licensing model for the Kalmar automation
that it is free to
platform SDK is that it is free to try for partners, with various licensing try for partners.
options for development and production use. The license structure can
be based on either usage volumes or fleet sizes.

Additionally, a support structure will be in place, ranging from forum


access to an issue/ticket service. Optional services can include
training modules, technical consultancy, help desk access or a Kalmar
verification service that enables independent developers to have their
applications certified by Kalmar for function and interoperability.

12 13
Risks and opportunities. AUTHORS

Any opening up of previously proprietary interfaces always involves some degree


OPEN INTERFACES IN A TERNIMAL

of risk for the party sharing the technology. Competition could increase; new
players may enter the market to challenge industry leaders; or clients may choose
to accomplish in-house what previously would have been delegated to a system
AUTOMATION PLATFORM

provider.

However, it is Kalmar’s firm belief that in terminal automation, shared and


standardised interfaces are an absolute necessity for the development of the TIMO LEHTO JARI HÄMÄLÄINEN HEIMO POUTANEN
entire industry, and that the benefits of progressively opening these interfaces Director, Software and Automation, (Dr Tech.), Director, Terminal Product Manager, TLS platform,
greatly outweigh the potential risks. Not even the largest industry leaders have all Kalmar, has been working on terminal Automation, Kalmar, has a Kalmar, has over 30 years experience
the possible expertise in-house, and open interfaces enable a vastly expanded automation for over 10 years. He has background in telecommunications in developing and delivering
collaborative landscape for the benefit of terminal operators, independent been designing and implementing and the software industry, with automation solutions for different
developers and automation system providers alike. software products for most of the over 300 patents in 40 global industry sectors. He has experience
Kalmar fully automated solutions. patent families helping smartphone with process industry automation
In his current role he is leading the users in their daily business and in pulp and paper mills, graphics
Kalmar software development teams pleasure. He has been working 5 industry and nuclear power plants
in Tampere, Sydney and San Jose. years at Kalmar, leading offering and mobile equipment automation
and service concept development. in the mining and construction
He is currently leading product sector. For the last two years he has
management of Kalmar software been responsible for the product
and automation development, as management of Kalmar’s TLS
well as the simulations lab and test (Terminal Logistic Systems) platform.
yard automation operations. He is
also project director for the Kalmar
AutoRTG product development.

ABOUT THE COMPANY


Kalmar, part of Cargotec, offers the widest range of cargo
handling solutions and services to ports, terminals, distribution
centres and to heavy industry. Kalmar is the industry forerunner
in terminal automation and in energy efficient container
handling, with one in four container movements around
the globe being handled by a Kalmar solution. Through
its extensive product portfolio, global service network and
ability to enable a seamless integration of different terminal
processes, Kalmar improves the efficiency of every move.

CONTACT
www.kalmarglobal.com
[email protected]

KEEP IN TOUCH WITH US

14 15
Published
Published by Kalmar,
by Kalmar, partpart of Cargotec.
of Cargotec. Copyright
Copyright Cargotec.
Cargotec. All rights
All rights reserved.
reserved.

You might also like