For small and newly established terminals confronted with huge investments, finding a TOS geared to their requirements and, in particular, their budget is a struggle. Based in Rotterdam, Copas B.V. designs its software and TOS products with the needs of smaller terminals in mind. Esoware B.V. distributes Copas’ software for terminals from its office in Rotterdam, managed by Mr. Frans Jol, who has extensive experience in the terminal business.
Copas is headed by former senior management of Europe’s biggest container terminal, with over 40 years experience in port and terminal operations, supported by 16 dedicated analysts and software developers. They understand the need of any terminal, small or large, to be able to use a comprehensive set of functions, from graphical planning systems to advanced EDI-systems. To date, the affordable Copas TOS software has been successfully installed on more than 14 ‘wet’ and ‘dry’ terminals throughout Europe and the UK, and modules have also been installed in Holland and Sharjah, UAE.
Esoware B.V.’s integrated container control system for terminals is STEP2, which was developed using modern tools, like Java, and uses SQL-compatible database situations such as MS SQLserver, Oracle or Open Source Databases as a database tool, which ensures safe and reliable storage of valuable data. Using a VPNconnection, Esoware staff can assist customers with the necessary system management or support tasks. Management reports can be made using a standard report generator.
The YARD Planning & Viewer software, a module of the STEP2 container control system, has also been developed using advanced Java techniques. YARD communicates with the STEP2 database to obtain container data in real-time. YARD shows the current status of the container yard, and all containers therein. Certain containers – from a certain vessel or for a certain destination, etc. – can be identified, and their exact location pinpointed in the yard. YARD automatically determines the optimal location in which to place newly arrived containers, and can then communicate this planned location to the reachstacker driver via the RFnet module.
