Locations The governance of customs processes is done via authorizations/licenses. In these licenses, an important element is the identification of locations that are considered approved for the application of the license. To allow the application of business rules, but also the general requirement of keeping record of the location of products, the proper setup of Locations is essential. Below the some common examples emphasize the principle: The entire Terminal with the address. Although not always relevant from he start, a License could cover for example multiple Terminals, meaning that the setup should be in such a way that the Terminal is linked to a license number, but also has its own identification reference. For example, in the Netherlands there are two Terminals. One in Rotterdam and one in Amsterdam. Both Terminals fall within the scope of the same license with license number X. Each Terminal has its own 'Tax warehouse reference'. The Rotterdam Terminal has Tax warehouse reference Y, belonging to License X and the Amsterdam Terminals has 'Tax warehouse reference Z', while belonging to License X. This setup is also relevant to the registration of Parties, which is described in the Chapter Parties; Jetties at the Terminal. Operationally speaking a Visit will typically berth at a Jetty, hence this information is likely to be available already. A Jetty should be considered a Location where it is possible to apply settings to a Jetty such as 'label' them as belonging to a certain license yes or no; Tanks. Some Member States license tanks instead of the full Terminal for (certain) customs procedure. To keep flexibility and allow for implementation of Measures of Internal Control, Tanks should be considered as Location just like Jetties allowing for allocation to licenses. This would allow the implementation of business rules where not only an Activity is validated if it is allowed under a certain license, but also is the license covers the Location where the Activity takes place. For example, if an Excise warehouse license does not include a Jetty and a User is trying to register an Activity related to Excise controlled goods at the Jetty, the system has the parameters and setup to prompt the User that said Activity is not allowed at the jetty location; Remote locations. Remote locations, such as Buoys (also referred to as Dolphins) or remote jetties not belonging to the Terminal infrastructure wise can be part of a License. The concept of Locations should also cover these type of Locations in terms of settings, where, for example, a Buoy has a registration number and/or address. For example, in case Product is moved under the governance of a license from a Terminal Jetty 1 to a Buoy 12, the record keeping should show the Movement from Jetty 1 to Buoy 12. When the Vessel leaves from Buoy 12 after performing an operation a declaration is likely to require the identification of the Buoy 12 as Place of Dispatch with the listing of address details. Hence, in terms of setup it should be possible to register a Location with an address. Wherever a Location is used in the business process, Location details should be available from the Locations setup.