In the middle of 2023, the World Customs Organization released a new major version of its Data Model. GEFEG.FX users of the WCO Data Model version 4.0.0 can now access the new version publication.

What is new in v4.0.0? Regulatory data requirements due to new or amended legislation submitted as change requests by Customs authorities and WCO Data Model implementers have been added and/or modified.

Furthermore, this major version release addresses pending critical cosmetic and breaking correctional activities since the last major version to improve the efficiency and usage of the WCO Data Model.

The involvement of Customs authorities globally supports an important objective of the WCO Data Model: Requirements of national and regional legislations or guidelines for implementation are considered and incorporated into the WCO Data Model. There are changes in the Information Packages (BIP), i.e. two of the major BIPs have been merged to create a new Additional Information Package (AIP). Please note that this type of change, amongst others, makes this release version non-backwards compatible with previous versions.

Customs authorities around the globe further strive for effectiveness and efficiency

It is an important objective for the WCO to provide and further develop its global standard for seamless cross-border transactions for all Customs administrations worldwide.

What are the benefits of the WCO Data Model, which is intended to be the basis for information exchange of cross-border regulatory processes in a global supply chain?

• The Data Model opens the possibility for Customs authorities to achieve interoperability and collaboration in Single Window and other implementations.
• Data flow and integration of business data for Customs procedures are simplified and harmonized.
• The main components of the WCO Data Model consist of “Base Information Packages” and “Additional Information Packages”.

Information Packages compile information submitted by trading parties on one side and processed by Customs authorities for typical Customs processes and procedures on the other side. Customs processes cover Single Window, or other implementations, including those at the virtual border. This includes, for example, declaration of goods movement, licenses, permits, certificates, or other types of regulatory cross-border trade documents.

Delivery of the WCO Data Model in a structured and reusable format in GEFEG.FX

In cooperation with the World Customs Organization, GEFEG has been delivering the WCO Data Model with GEFEG.FX software since the early 2010s. Thus, new possibilities for joint development work and user-specific usage of the WCO Data Model opened up for Customs authorities, governmental organizations, traders and other parties involved in cross-border regulatory processes. For users, the reuse of the WCO Data Model is simplified and streamlined with GEFEG.FX. A ready-to-use WCO Data Model compliant XML schema export also contributes to this.

Easy and effective use of the WCO Data Model

Many users of the WCO Data Model packages in GEFEG.FX have been impressed by the simple and efficient methods for reusing the WCO Data Model to plan and implement their country and/or regional specific Customs data requirements based on legislation. With each new release, it is important for users to determine if their existing implementations need to be modified to incorporate the latest WCO definitions of objects and Customs procedures to ensure compliance with the Data Model.

In this release, changes have been applied as submitted by member administrations plus corrective changes from WCO intersessional development work approved and maintained by the WCO Data Model Project Team and incorporated into GEFEG.FX by the GEFEG Implementation Support Team.

Join the WCO DM 4.0.0 Webinar

GEFEG invites all interested users of the WCO Data Model to join our webinar on the deliverables and changes in the latest published version 4.0.0 of the WCO Data Model with GEFEG.FX. The webinar will also address the potential impact of the new version and its implementations by business and technical implementers. In addition, GEFEG will present the “How-to” documents delivered with the new release to assist all users in applying all the typical steps when implementing the new version of the WCO Data Model. In the 15-minute question and answer session, participants will have the opportunity to express wishes, questions and comments.

GEFEG.FX – New in the 2023-Q3 Update

With the new GEFEG.FX GEFEG.FX Quartarly Release 2023-Q3, the following new or further developed functionalities are available for use.

New data packages in GEFEG.FX

• UN/EDIFACT
  • UN/EDIFACT D.22B
  • UN/EDIFACT D.22A
  • UNECE / ISO code lists update
  • UN Locode 2022-2

• ISO 20022
  • Model & schema 2023-07
  • External code lists 2023-07
  • Models and schemas 2023-03-21
  • Code lists update

• GS1 eCom standards
  • GS1 Semantic Data Dictionary (SDD): Despatch Advice
  • GS1 XML 3.5.1
  • GS1 Application Guidelines 9.3
  • GS1 XML update for code lists and example values
  • GS1 XML enriched with codes, as of 3.0

Using JSON schema for EDI: Advanced integration with the new GEFEG.FX JSON Editor

Times change and this is usually accompanied by new requirements. This naturally also affects the electronic exchange of business data, and here in particular new technical exchange formats as a supplement to the classic EDI and XML formats. For some time now, GEFEG.FX’s range of services has been enriched by its own API Editor.

With the new release, a JSON editor is now also available and offers a powerful way to design, customise and reuse customer specific data structures in JSON format.

For more information, see the following article: Now ready for use for GEFEG.FX users: The JSON Editor

UN/EDIFACT syntax versions consolidated!

With the publication of the UN/EDIFACT Syntax Verison 3 Part 11, users of the UN/EDIFACT standard will be able to use selected fields of syntax version 4 in syntax version 3, among others. This new syntax is implemented in GEFEG.FX as of the D.22A release.

Users now have the possibility to choose between the following syntaxes:

• Syntax 3,
• Syntax 4 and
• Syntax 3 Part 11

In short, the new syntax allows compatibility between the previous syntaxes.

We would be happy to discuss what this means for your EDIFACT based guides and whether there is a need for action in a non-binding meeting. Get in touch with us!

New functions require new data format versions

What would software be without constant further developments, functional enhancements, bug fixes and, in the case of GEFEG.FX, new data modules? Of course, this is a purely rhetorical question, because we are constantly implementing new customer requirements or expanding existing functions.
Sometimes you as a user will be prompted by a pop-up to update the data format version in your GEFEG.FX version due to an innovation: If possible, always save your GEFEG.FX Guides in a current data format version immediately in order to be able to use the newly provided functions and improvements.

You can read the current data format version of your GEFEG.FX object in the GEFEG.FX information area.

The next practical case will follow with the next release. With regard to EDI guides and EDI standards in particular, the following applies: With the next 2023-Q4 release, these will only be able to be processed with the data format version from 2019-Q3. GEFEG recommends that you update the data format version of your files before the next release upgrade so that you can continue to work seamlessly with your EDI guides.

Please also note the following information:

Regardless of the specific situation of the 2023-Q4 Release, we would like to point out, in connection with the data format version that all GEFEG.FX users within an organization should use the same GEFEG.FX release version to avoid compatibility problems. Under certain circumstances, it could otherwise happen that GEFEG.FX objects saved with a newer GEFEG.FX version cannot be opened with older GEFEG.FX versions.

Over the last 30 years, a number of standards for electronic data exchange between business partners have been created in order to standardise it, often with the aim of adapting it to the business processes of an industry. These standards, which are now well established, have contributed significantly to the fact that companies today save costs by using standardised data exchange formats. After this successful innovation push through B2B standards in electronic data exchange, the search continues for new, innovative and more efficient solutions to further optimise data exchange.

GS1 has taken the next step with the development and publication of the “GS1 Semantic Data Dictionary” (SDD). The semantic data model was developed to define all business-relevant data needed for the exchange of EDI messages in the supply chain, such as purchase order, order confirmation, invoice and other messages. Unlike syntaxes such as UN/EDIFACT, XML Schema, X12, the message structure does not matter: GS1 SDDs focus on the semantic content of the business processes. This creates a comprehensive, higher-level data model that acts as a dictionary and library.

How does the GS1 SDD model benefit users?

Generally speaking, any number of subsets can be derived from the GS1 SDD model and/or the subsets for the supply chain processes. Users leverage the GS1 SDD data model to develop data models tailored to their own use case, containing only the information that the user actually needs. Irrespective of the technical aspects of data exchange, this further improves harmonisation, maintainability, consistency and interoperability of the data. In GEFEG.FX, these subsets can be created as model guides and used with the usual range of functions such as documentation, structural adjustments, mapping options.
Based on the data model, users can develop their APIs or, in the next step, they can link the user-specific data model with a logical mapping to the data formats of the eBusiness standards used, e.g. GS1 EANCOM® or GS1 XML.
Another advantage for users: In case of future updates of the data model, changes can be transferred to the already linked data formats with little effort. Users can manage their interfaces with business partners even more efficiently.

GS1 SDD as a new data module in the GEFEG Distribution

With great commitment, GEFEG has participated in the development process of the GS1 SDD and contributed to the release of this data model. As of now, we offer the GS1 SDD data model as an additional data module in the distribution of GEFEG.FX. The data package also contains the model subsets of the Orders, Invoice and Order Response processes. In addition, it contains detailed mappings for supply chain messages to the GS1 EANCOM®, GS1 XML and SCRDM CII data formats of the same name.

The new data package allows you to easily integrate the GS1 SDD into your existing message formats using the included mappings and to communicate smoothly between different data formats.

Should you require further information or support, we will be happy to assist you. We look forward to introducing you to the advantages of the new GEFEG.FX data package and assisting you with the implementation.

Roman Strand, Senior Manager Master Data + Data Exchange at GS1 Germany, on the success and future of EANCOM® and the GS1 application recommendations based on EANCOM®.

Roman Strand has been working for GS1 Germany for more than 20 years and is, among other things, the head of the national EDI/eCommerce specialist group. In this interview, he explains the role of the EANCOM® standard and why the GS1 specification with the associated application recommendations will continue to determine the business of mass data exchange in the future.

Hello Mr Strand, you have been working for GS1 Germany for over 20 years. What were the major focal points of your work during this period?

I work all the time at GS1 in the national and international standardisation department. In the early years I was the apprentice under Norbert Horst, who helped develop the EANCOM® standard in Germany. During this time I learned a lot and also started working with GEFEG.FX. I have remained loyal to this department and the topic of national and international standardisation to this day. In various committees, I drive the further development of our standards together with our partners from the business community. In addition, I work as a trainer and conduct EDI training courses in which our customers are trained to become certified EDI managers, among other things.

Which topics did you deal with a lot last year?

Next to the further development and maintenance of our EANCOM® and XML standards, we deal with the current digitalisation topics and check to what extent new innovations could be relevant for our work at GS1. Furthermore, we had our big anniversary celebration last year, because EANCOM® is now more than 30 years on the market and our application recommendations have been around for more than 20 years.

Why was the EANCOM® standard developed and what function does it fulfil?

The EANCOM® standard was developed before my time at GS1. There is the mother standard EDIFACT, which is much too big and complex. The great achievement of the EANCOM® standard is to reduce this complexity of the mother standard to those elements that are important for our customers. Approximately 220 EDIFACT messages became 50 EANCOM® messages, which were then further adapted to industry-specific EANCOM® application recommendations. The leaner a standard is, the more economically and efficiently it can be implemented. This simplification made the widespread use of the standard by many companies possible in the first place. We also translated the English-language standard almost completely into German. This was another great simplification for the German community.

How were you personally involved in the development of the EANCOM® standard?

The development of the EANCOM® standard is mainly driven by our customers from trade, industry and other sectors. They pass on their requirements to GS1, which are then processed in the EDI/eCommerce specialist group. The decisions of the expert group are then implemented by me, among others, as a representative of GS1.

How can I imagine the role of GS1 in this process?

There are many published standards on the market for electronic data exchange between companies. But behind very few of them is a reliable organisation that is continuously committed to the further development of its standard. With us, clients can be confident that implementing the standard is a future-proof investment. If, for example, there is a legal change that also has to be taken into account in the standard, we adapt the standard.
Furthermore, we are responsible for the documentation and specification of the EANCOM® standard. Again, our focus is on simplification. Among other things, we ensure that as many codes as possible are used from code lists instead of free-text fields. Because with free-text fields, automated data processing is often associated with errors.

You use GEFEG.FX for data modelling and documentation of the EANCOM® standard. For what reasons do you rely on the software for these work steps?

I have been working with GEFEG.FX for many years now and it took me a while before I could really use the software to its full extent. In the foreground you have your specification and in the background you have the standard, which is linked to the corresponding code lists. This means that as a user, when developing my own specification, I cannot do anything in the foreground that is not already stored in the underlying standard. As soon as there is a deviation from the standard, GEFEG.FX reports an error message and ensures that there is no erroneous deviation. For me, this control function is the main advantage of GEFEG.FX as a standard tool. Otherwise, a comma could always be quickly forgotten or some other small syntactical error overlooked.
With the standard running in the background, validations or checks can be carried out conveniently. In addition, documentation can be created quickly at the touch of a button using the various output options. Thanks to these functions, you don’t have to start all over again and save a lot of time in many work steps.

How do you assess the future development of the EANCOM® standard?

For me, EANCOM® is Classic EDI, which is considered old-fashioned by many workers in innovative companies. However, in my opinion, this classic EDI offers many advantages. It is a defined structure that works in the mass data exchange business and will continue to work in the future. I once said to my colleague who has been working in EDI at GS1 as long as I have: “Until we retire, we don’t have to worry about EANCOM® being shut down.”
Because the business is still going and the demand remains high. There have been and continue to be new technologies that are supposed to replace classic EDI. When I started at GS1, there was a lot of hype about XML. The same happened years later with blockchain technology and today with APIs. All three technologies were seen as replacements for classic EDI, but in the end they are all just additions that offer supporting possibilities in the EDI area. Mass data exchange will continue to be regulated by classic EDI and therefore I assume that the future of the EANCOM® standard is also secured.

Are there any challenges or difficulties that need to be considered in the further development of the standard?

The problem of a global standard is its complexity. Over the years, new information has been added to the standard. For example, every relevant change in the law led to new additions without anything ever being deleted, even if no one has used it for 20 years.
We should therefore work more towards lean EANCOM® standards, in which only the information that is absolutely necessary is stored. After all, this reduction of complexity is one of the central strengths of GS1 standards. We achieve this above all by developing application recommendations in which the underlying standard is specified even further for a specific application. This leads to less information needed and fewer potential sources of error.

We are nearing the end of our conversation. Is there anything else important beyond the EANCOM® standard that you would like to talk about?

Yes, we are currently working on a semantic data model and are thus building a new content basis that contains all relevant information that is to be exchanged electronically. GEFEG is also involved in this development process. With the data model, our customers have the possibility to freely decide which syntax form they use for their data formats for electronic data exchange This fundamental work will therefore help users to be more independent of a specific syntax in the future and to be able to decide freely whether an XML, EANCOM® or even an API should be used for data exchange.

Mr Strand, thank you for this interview.

Digitalisation project for finished vehicles logistics successfully completed

GEFEG supports the development of new messages with technical know-how

The ECG – Association of European Vehicle Logistics in cooperation with the automotive organizations Odette International and the German Association of the Automotive Industry (VDA) have successfully completed a project to develop recommended messages for the logistics of finished vehicles. Coordinated EDIFACT and XML messages were completed as a new message set covering digital communication across all outbound logistics processes.

More efficient communication and reduced process costs

“The recommended standard EDIFACT and XML messages will allow vehicle manufacturers (OEMs) and Finished Vehicle Logistics Service Providers (LSPs) to communicate with each other in a more efficient way. They will also avoid a proliferation of many different message types across the finished vehicle supply chain, significantly reducing IT development costs for individual companies.” (Quote from Standardisation of FVL digital messages)

The standard consists of a process description for all process stages in outbound vehicle logistics. In addition, EDI experts have developed EDIFACT and also XML messages with the aim of offering alternative electronic communication solutions. For each standard message format at least one sample message was published.

Experts from the automotive industry and vehicle logistics involved in the project

Many OEMs from the Automotive Industry and Logistic Service Providers were involved in the creation of the new standard, so that a large number of different requirements where considered. The joint recommendation “Digitilisation of Finished Vehicle Logistics Process Description” is available as a free download for all interested parties.

EDIFACT and XML messages for finished vehicle logistics available in GEFEG.FX

GEFEG supported the project especially in the technical implementation of EDIFACT and XML messages with the GEFEG.FX software. In coordination with Odette International and the VDA, GEFEG is able to deliver the newly developed messages as a supplement to the automotive standards.

The World Customs Organisation has published the latest version of its data model at the end of 2021. GEFEG.FX users can now obtain the latest version 3.11 of the WCO data model via an update of the GEFEG distribution.

What is new in version 3.11?

Data requirements due to new or amended legislation submitted as amendments by customs authorities and WCO data model implementers have been added and/or amended.

In this release there are 5 new Compositions, 5 new Attributes, 8 new Classes and 3 new Codelists approved and maintained by the WCO Data Model Projects Team and provided by the GEFEG Implementation Support Team in GEFEG.FX. Learn more about the details in our webinar.

The involvement of customs authorities worldwide supports an important goal of the WCO data model

Data requirements of national and regional legislations or implementation guidelines are taken into account and incorporated into the latest WCO data model, which in turn takes into account feedback and input from customs authorities around the world. This version is backwards compatible with previous versions as it does not include or remove any new information packages or business processes. Extensive changes are expected in the next major version of the WCO data model, which is currently scheduled for release in mid-2023.

Improve the effectiveness and efficiency of customs authorities around the world

It is an important goal of the WCO to provide and further develop its global standard to enable seamless cross-border transactions for all customs administrations worldwide.

How do you benefit from using the WCO data model as a basis for the information exchange of cross-border regulatory processes in a global supply chain?

• The WCO data model opens the possibility to achieve interoperability and cooperation in Single Window and other implementations by customs authorities.

• Simplified and harmonised data flow and integration of business data for customs procedures

• The “Base Information Packages” are central components of the WCO data model. These information packages compile information for typical customs processes and procedures in single window implementations or at the virtual border. This is information that has to be submitted by the trading parties and processed by the customs authorities. These include, for example, declarations of goods movements, licences, permits, certificates or other types of documents for cross-border trade.

Output of the WCO data model in a structured and reusable format in GEFEG.FX

In cooperation with the World Customs Organization, GEFEG has been providing the WCO data model with the GEFEG.FX software since the beginning of 2010. This opens up new opportunities for customs authorities, governmental organisations, traders and others involved in cross-border regulatory processes for joint development work and user-specific use of the WCO data model. For users, GEFEG.FX simplifies and streamlines the reuse of the WCO data model, whether for national customs implementations or for use by government partner agencies. A ready-to-use XML schema export also contributes to this goal.

Easy and effective use of the WCO data model

Many users of the WCO data model packages in GEFEG.FX are impressed by the simple and efficient methods of reusing the WCO data model to plan and implement their country and/or region-specific customs data requirements based on legislation. With each new release, it is important for users to determine whether their existing implementations need to be modified to incorporate the latest WCO definitions of objects and customs procedures to ensure consistency with the data model. If a migration to the latest version of the WCO data model is required, this can easily be carried out in GEFEG.FX.

Join the WCO Data Model 3.11 Webinar

GEFEG invites all interested users of the WCO data model and all other interested parties to join our webinar on the new features and changes in the latest version 3.11 of the WCO data model with GEFEG.FX. The webinar will also address the potential impact of the new version and its implementations by business and technical implementers. In addition, GEFEG will present the “how-to” documents that are updated and delivered with each new version to help all users to perform all typical steps when implementing the new version of the WCO data model. During the 15-minute question and answer session, participants have the opportunity to ask questions, express wishes and make comments.

The latest EU Customs Data Model Version 6 went live on 2 July 2021. European Customs authorities and other interested parties now have an updated data model at their fingertips in search of information about the UCC Legal Annexes data requirements.

What is the EU Customs Data Model?

The European Union Customs Data Model (EUCDM) is the model for Customs trans-European systems such as NCTS, AES, ICS and for Member States national customs clearance systems. It provides a technical instrument that models and delivers the data requirements as laid down in European Union (EU) Customs legislation UCC.

What has been changed between the previous EUCDM and the newest EUCDM version 6.0?

The EU Customs Data Model version 6.0 publication has been amended by the newly structured, revised and harmonised UCC Legal Annex B. The new EUCDM version transforms the provisions of the legal text of the relevant Commission Delegating and Implementing Regulations (EU) into customs data requirements. In addition, the amended UCC Legal Annex B introduces additional Customs reporting procedures as required by the new EU customs advance cargo information system facilitating free flow of trade through enhanced customs security processes (ICS2).

In contrast to the previous EUCDM HTML publications, the modernised EUCDM 6.0 brings about many improvements in the usability and presentation of Customs data requirements. This includes for example dropdown menus for navigating various Customs procedures as defined and required by the EU legislation.

Also two new useful sections have been added i.e.:

• Archive referencing the previous html publications of EUCDM as of version 3.0.

• Future EUCDM: Projection into the future providing non-binding information regarding possible future EUCDM related developments and implementations.

This change is good, but how to handle it?

EUCDM 6.0 provides you with a “Read Me” page to assist observers, users and implementers of EUCDM utilize the EUCDM publication. The “Read Me” menu item under “Introduction” section of the publication outlines information and details on the semantic content, usage and functions of this publication.

Further information:

Learn more about implementing the EUCDM in our free webinar on How to implement my customs requirements? Hands on customising of EUCDM with GEFEG.FX

The OpenAPI Initiative has just released version OpenAPI 3.1. On 17 February 2021, Ron Ratovsky from SmartBear and Darrel Miller from Microsoft presented the new version. This article deals with the question of what OpenAPI 3.1 brings with it that is new and what this means for existing implementations.

If you would like to know more about the OpenAPI specification standard itself, you are welcome to visit the official website or read the article “With OpenAPI, this is what your future looks like: A world without business documents. Think model-First with GEFEG.FX“.

The essential changes of OpenAPI 3.1

Support of webhooks

From my personal point of view, the most significant difference is the support of webhooks in APIs. Since the topic is new to many, I have written another small article on the topic “Still no catch on webhooks? Create your flexible APIs now with OpenAPI 3.1 and GEFEG.FX“. There you will also find an example. Webhooks are an essential factor for the success of WordPress. It is this technology that makes it possible to write applications efficiently and to extend them easily and in a standardised way via plug-ins. The OpenAPI initiative has also regarded webhooks as so essential that they are a new document type in OpenAPI. An OpenAPI specification now has three basic root elements: Paths, Components and Webhooks.

So now there can be a valid API specification that exclusively defines webhooks. At first glance, this may seem strange. But this can be something very useful. Applications are API-enabled more quickly, especially if they have a fixed process flow. It also means that existing APIs of applications like WordPress can now be specified cleanly.

When specifying a webhook, the path (endpoint) that is executed in the foreign API is defined. In contrast to a callback, a webhook is an active action in the foreign API. Write me in the comments what you think of the new webhooks.

While testing the webhooks, the need quickly arose to also make paths reusable, which leads to the next change.

Global path definitions

With version OpenAPI 3.1, paths can now also be specified under the components. Similar to the parameters, a globally available name can now be assigned to a path. This is an essential step towards standardisation and better governance of API implementations.

Referenced objects with overwritten description

Particularly when defining global objects or global data structures, one often comes to the situation that in the concrete application of the structure, the business term changes.

Here is a simple example: Let’s say we have defined a generic schema object with which we can map an address consisting of street, post office box, postcode, city and country. And now we want to use this address in different places. Even an organisation can have more than one address. From a purely postal point of view, an organisation in Germany can have a home address, a P.O. box address or a major customer address. If logistical considerations are then added, information on gates, branches or the like can be added, for example.

OpenAPI 3.1 now allows the summary and description to be overwritten when referencing a schema object. This means that these different forms of the address can now be clearly described.

What OpenAPI 3.1 cannot do, but the solution with GEFEG.FX

OpenAPI 3.1 only supports overwriting the verbal description of a reference. In particular, however, repetitions or (restrictive) changes to the referenced structure are not possible.

GEFEG.FX can do that. In the above example, it is not possible to distinguish between the structure of a home address, a P.O. box address and a major customer address. . In OpenAPI 3.1, this would require three different schema objects or the use of a OneOf structure. With GEFEG.FX, however, it can be defined directly at the reference that the major customer address, for example, consists only of postcode, city and country.

Support for roles and claims security

With version 3.1, roles are supported throughout the specification of security requirements. This simplifies rights management considerably. For example, it is now easy to define that write or delete operations require a different role than read access.

Description and summary

In addition to the description, there is now also a short summaryfor describing the objects of an API. The main difference is that the description supports Markdown formatting and is thus ideally suited for detailed descriptions for the developer. The summary on the other hand, does not support this. It serves as short information on the function of the object. Ideally, it can be used by code generation tools that generate source code directly from the OpenAPI 3.1 specification. The summary could be included in the source code as a comment, for example.

Full JSON schema support

The OpenAPI 3.0.x version forms both a subset of JSON Schema and a superset of JSON Schema. This has now been fixed. OpenAPI 3.1 is now fully compatible with JSON Schema.

Fewer format specifications for data types

OpenAPI 3.0.x defined a whole range of supported format specifications for data types. This changed with the OpenAPI 3.1 version. Some format specifications went beyond the JSON schema specification or repeated format specifications already defined there.

By approximating the JSON schema, only those formats are now specified that extend the JSON schema. At the same time, the specification of a format as a restriction of the data type has been removed. The specification of a format is now more of an annotation than a restriction. The check is therefore to be carried out by the respective application.

More changes with OpenAPI 3.1

In addition, there are a few more changes in OpenAPI 3.1, which I would like to summarise here:

• Multipart/form data support for parameters
• A path parameter must also be defined. This is actually logical, but was not explicitly required until now.
• All HTTP methods support request bodies. This also applies to DELETE, GET, POST.
• Responses are now optional. If a specification is developed in a “design-first” approach, it can make sense to specify it at a later stage. Especially in a collaborative environment, valid specifications can be exchanged that do not require fancy values for responses, as these may not yet be finally defined.
• When specifying media types, the contentEncoding can now also be specified.

I have linked the complete presentation of the OpenAPI 3.1 format below.

What does this mean for implementation?

When I look at the changes compared to the previous version, I can understand why the OpenAPI Initiative thought for a long time about whether it should be called OpenAPI 3.1 or rather OpenAPI 4.0.

On the other hand, most innovations are compatible. An API with a specification based on version 3.0.x still works. Only downward compatibility is no longer necessarily guaranteed. It is clear that the previous version did not yet know webhooks and global paths. But there would also be problems if the now optional responses were omitted. Such a specification would not have been a valid document in the previous version. But this constellation should occur in very few cases.

At the end of 2020, the World Customs Organization released a new version of its Data Model. GEFEG.FX users of the WCO Data Model version 3.10 can now access the new version. What is new in 3.10? Requirements due to new or amended legislation submitted as change requests by customs authorities and WCO Data Model users have been added or have been modified.

The involvement of customs authorities from around the world supports an important objective of the data model: Requirements of national and regional legislations or guidelines for implementation are considered and incorporated in the WCO Data Model. There is no new information package in this version, so that the new version is backward compatible. Extensive changes are expected in the next major version of the WCO Data Model. As it currently stands, this major version is expected to be released towards the end of 2022.

Effectiveness and efficiency of customs authorities around the globe will be improved

It is an important objective for the WCO Data Model to create and further develop a global standard for seamless crossborder transactions for all customs administrations worldwide. What are the benefits of the data model, which is intended to be the basis for information exchange of crossborder processes in a global world?

The data model opens the possibility to achieve interoperability and collaboration in single window and other implementations by customs authorities. Data flow and integration of business data for customs procedures should be simplified and harmonized. The main components of the WCO data model consist of “Base Information Packages.” These information packages compile information that is submitted by economic parties and processed by customs for typical customs processes and procedures in single window implementations or at the virtual border. This includes, for example, declarations, licenses, permits, certificates, or other types of regulatory cross-border trade documents.

Delivery of the WCO Data Model in a structured, reusable format in GEFEG.FX

In cooperation with the World Customs Organization, GEFEG has been delivering the WCO Data Model with GEFEG.FX software since the early 2010s. Thus, new possibilities for joint development work and user-specific use of the WCO Data Model opened up for Customs authorities, governmental organizations, traders and other parties involved in cross-border processes. For users, the reuse of the WCO data model is simplified and streamlined with GEFEG.FX. A ready-to-use XML schema export also contributes to this.

Easy and effective use of the WCO Data Model

Many users of the WCO data model packages in GEFEG.FX have been impressed by the simple and efficient methods for reusing the WCO data model and planning their country-specific policies. With each new release, it is important for users to determine if their existing implementations need to be modified to incorporate the latest WCO definitions of objects and customs procedures to ensure compliance with the Data Model. In this release, there are 11 new Compositions, 2 new Attributes, 3 new Classes, and 1 new Code List that are being maintained and approved by the WCO’s Data Model Project Team and applied in GEFEG.FX by GEFEG’s Implementation Support Team.

The EU Customs Data Model (EUCDM) is the new data and interface model for trans-European customs systems and for Member States’ national customs clearance systems. Its overall objective is to be the single and true source of information for modelling data requirements. It provides a technical tool that models the data requirements laid down in EU customs legislation. Thus, it sets the guideline for the technical developments of the various IT systems used for data processing by customs in the EU.

The EUCDM in machine-readable format

GEFEG is the only company to offer the EUCDM in the machine-readable GEFEG.FX format for application.

The unique GEFEG.FX software makes it easy for Member States and the private sector to adapt the EUCDM to national requirements and their own business through reuse and customisation.

Alignment of the EUCDM with own data structures

In doing so, GEFEG.FX supports both the overview of the structures of the EUCDM and the own data structures in-house. It enables easy mapping and thus supports data harmonisation between these structures.

This is done with the innovative and unique methods developed by GEFEG for using and building messaging standards.

The core of these methods is the development of so-called guidelines to define data structures and interfaces based on available message standards. Furthermore, it supports the creation of publications.

EUCDM governance and data quality assurance

Governance is a particularly important issue in cross-border data exchange. GEFEG.FX supports compliance with governance and ensures data quality. Implementations can be validated against the specifications of the customs data model as early as the development phase.

But this support is not limited to the customs data model. Data harmonisation also works with own interfaces based on other standards in this environment. This makes it possible to improve the value chain and the interaction of upstream and downstream partners.

Cost savings and efficiency gains

The increased complexity means that companies often no longer know the data structures of their systems. They do not know what happens when a field is changed in the application or how to get the information they need. In a European or even international context with many national requirements, the challenge becomes even greater. Alignment with the EUCDM leads to significant cost savings here:

The impact of legislative changes on the overall “customs” system becomes transparent.

Examples of publications in the customs environment

Examples of publications created with GEFEG.FX in the customs environment are:

• The European Customs Data Model (EUCDM) itself
• The CITES data model, which is based on the data model of the World Customs Organisation (WCO) (from p. 34)
• The interface to the Customs Management System (ECMS) of the Dutch Customs

More than 6 offers from GEFEG around the EUCDM

The methods and software systems developed by GEFEG are used by both customs administrations and the private sector, such as logistics companies.

GEFEG’s offers on the EUCDM include:

• GEFEG.FX to define the interfaces based on the EUCDM and to harmonise your data structures and interfaces against the EUCDM (and other standards).
• GEFEG.FX.Cloud: GEFEG.FX in the Amazon Workspace Cloud with application of GEFEG.FX in the web browser in any operating system without installation
• GEFEG.Portal as a cloud solution for community building and on-boarding support, e.g. for validation of data, publication of interfaces as well as sharing of information and collaboration.
• GEFEG.Packages with more than 30 other data packages, including the WCO data model, EDIFACT, UN/CEFACT CCTS, GS1, UBL etc. for the development of guidelines and data harmonisation
• GEFEG.Support with workshops and support (not only) for EUCDM and WCO data model implementers who want to customise predefined EUCDM datasets, create guidelines or perform data harmonisation
• GEFEG.API as the latest and worldwide unique component of the GEFEG product family. It allows the creation of APIs based on message standards. In this case, based on the schemas of the EUCDM, but also on any other schemas. This ensures that your API is compliant with a desired message standard.

With our offer, all kinds of digitisation projects can be carried out in the EUCDM environment: Integration projects, API projects and even AI projects can be carried out in a time- and cost-saving manner, as knowledge and complete control over all data are guaranteed at all times.

Of course, this also applies to all projects beyond the EUCDM that are based on the WCO data model or other standards. When will you start your GEFEG project?