FA³ST Service @ HM 2024

If you want to implement reactive Digital Twins in an interoperable and transparent way, then FA³ST Service should be a key component in your IT stack.

FA³ST Service implements the latest version (v3.0) of the asset administration shell (AAS) specification, allowing you to host interoperable and reactive Digital Twins.

• With FA³ST Service your Digital Twins can be connected to your Asset. Deployment at edge-level is a focus of FA³ST Service.
• The API lets you create and modify AAS compliant Digital Twins. But don’t stop there: Use the API to trigger business logic from within your Digital Twins, as well!
• Use Endpoints for HTTPS or OPC UA. Or both at once: in parallel and synchronously.
• Link legacy systems with their existing communication interfaces thanks to the Asset Connection.
• Use the open and expandable architecture to make FA³ST Service fit your individual requirements and application scenarios. Any database systems or other software systems can be connected.
• Be prepared for Data Spaces: The FA³ST Ecosystem can be connected to Eclipse Dataspace Components (EDC) via the EDC-AAS extension software. FA³ST Service itself is in the process of becoming an Eclipse Project.

As FA³ST Service is open-source software with an extension concept, your own application scenario can benefit from the development of third parties, as well! This is boosted by detailed documentation and active development.

FA³ST Service is the central component of an entire collection of tools , which is currently being developed, for the individual phases in the entire life cycle of a digital twin.

Get a hands-on feel for FA³ST Service and how it can help you to digitalise your production.

• Get started right away with our Starter Guide
• Download FA³ST on Github
• We offer our support for questions and problems regarding FA³ST usage.
  

Minimize integration costs by linking legacy systems with FA³ST Service thanks to the Asset Connection.

Easy to learn and flexible:

• No programming knowledge is required to start FA³ST Service and use it effectively.
• Start the service using Docker, from the command line or as embedded library.
• Configure FA³ST Service using environment variables, a configuration file or directly from code.
• For connecting FA³ST Service with existing systems, basic knowledge of the AAS Specification and relevant protocols is required. 

To show how different assets and their respective digital twins can communicate with each other to reach a mutual goal, we have built a demonstrator that implements digital twins using AAS and FA³ST Service.

The FA³ST demonstrator simulates a typical industrial process based on PLC automation. The PLC controls the distribution and measurement of products while providing an OPC UA interface for the Plant AAS. Additionally, there are three types of AAS: Robot, Product and Storage. The AAS Robot is the digital twin of a miniature robot arm that is responsible for sorting out the measured products into storage.

Each asset is connected to FA³ST service via OPC UA and communicates with other assets through FA³ST service events. This way the robot arm gets notified when storage is full and initiates an operation to empty the storage.

Each product receives a digital product passport based on AAS submodel templates. This allows for estimated carbon emissions to be recorded in the product carbon footprint submodel template. The products are tracked with NFC so that end users can access the DPP by scanning the NFC tag.

With our demonstrator, we can show that each asset, including their processes, is represented by an AAS provided through FA³ST service. This kind of interaction, in which AAS communicate directly with each other, allows for flexible and modular production. This is a key step on the way to proactive AAS and autonomous production.

The demonstrator can be seen live and in action at Hanover Fair Hall 15, Booth A06