Introduction
This document describes the Functional setup of our Terminal Management System (TMS) called ATLAS and its working in conjunction with our Compliance Managements System (CMS). With CMS, we implement processes and measures of internal controls to ensure compliance with the relevant legal requirements and updated systems on the side of the relevant authorities.
CMS is a an autonomous module/system built using the same standards as ATLAS (i.e. Oracle APEX). In the intermediate period, where Tomcat is still in production, CMS will be linked to Tomcat as source system. As Tomcat is phased out gradually, CMS is now also linked to ATLAS as the source system.
CMS will only be used by Terminals that offer Compliance services, such as Customs and Global Trade (CGT) services to their clients. Examples are lodging customs declarations, issuing customs documents such as customs transport documents or origin documents.
All Terminals globally have to deal with compliance requirements, but where the Terminal does not perform actual services in this matter, it merely keeps record of data relevant to the goods we handle. This is covered by the source system and is not in scope of CMS. Think of data around the goods we handle, such as:
- Commodity code;
- Customs status;
- Origin (preferential and non-preferential); and
- Reference numbers / cargo document data, among which customs documents.
With ATLAS in combination with CMS, customs processes are automated as much as possible.