Business Nerds and Software Carpenters

Biogas plants

Logistics support for biogas plants

Modules in Business Central for biogas plants

Find the right package for your plant

Over the years, Elite IT has built extensive experience in developing our own Business Central solutions for biogas plants.

Differences in the needs of individual plants have led us to develop the following four modules.

Modules

Basis

Basic module

The foundation of the Biomass solution

Essentials

Essentials module

Extended functionality for operations and planning

Premium

Premium module

More advanced
functionality

Ultimate

Ultimate module

The complete package with access to all functionality

Overview of modules

Module

The basic module allows for the creation of suppliers, their tanks, and the associated biomasses, etc.

The module forms the foundation for all data relationships and other modules, enabling a documented link between all supplier deliveries, dry matter analyses, GPS tracking data, and more.

In addition, the module includes functionality for exporting and reporting data to the Danish Agricultural Agency (Naturerhverv) as well as the Waste Register.

The entire solution is built on the proven database technology of Microsoft SQL Server and Microsoft process architecture, ensuring maximum user-friendliness, performance, user-defined access control, data security, and data integrity.

Suppliers, tanks, biomasses, etc.

The analysis process allows for sampling of both raw and degassed biomass, with samples paired to the correct deliveries and quantities. This creates a data foundation for statistics such as fertilizer balance, among others.

It is also possible, through purchase and sales agreements, to generate transport orders, which can then be recorded on the shipments. These agreements can serve as the basis for planning functions.

Formerly known as Navision and Dynamics NAV, now called Dynamics 365 Business Central, is one of the world’s leading financial/ERP solutions from Microsoft.

With several million users worldwide, the system has evolved into the preferred solution for small and medium-sized enterprises. The solution offers full scalability, both in terms of the number of users and future needs for advanced business support solutions.

The Biomass solution is based on the standard NAV modules, including, for example, inventory management (with support for FIFO/FEFO/batch handling and advanced MRP for inventory replenishment), the fixed assets module for maintenance, and the project module for time registration, among other functions.

Experience with:

  • Danvægt
  • Scanvægt
  • Bjerringbrovægt


DriverApp integration with the mentioned scales or other scales via a Moxa box

The module links data from the truck scale with data in the system. Each transport (delivery) is recorded with data from the scale, including weight at entry and exit, time of weighing, and more.
It is also possible to allow manual entry of the weight – generally available for all users and administrators.

Integration with multiple truck scales via DriverApp (specify scale when collecting weight).

Via a portal function, act as a truck scale terminal as an alternative to a permanently installed terminal at the scale.

This module is designed for the staff responsible at the facility, allowing them to weigh drivers more quickly and easily. It includes a list of active transports at the facility, quick lookup of suppliers and tanks, and an information screen showing the status of terminals.

Drivers can enter their phone number and receive a delivery receipt via SMS.

Manual marking of transports to indicate that receiving inspection has been completed.

Post analyses on transports with the option to remove an analysis from a delivery and re-post a different value.

Ability to generate overviews with information pulled from various parts of the system, for example for Excel exports, without needing a license for new reports/screens or similar.

Elite IT’s Cybersecurity Package – EICybSec

In our software solutions, data integration between different systems always plays a major role, and we often work with IT/OT systems that are classified as critical infrastructure. These systems are, to varying degrees, covered by the NIS2 Directive, which is expected to come into effect on July 1, 2025. Therefore, we have already largely prepared our systems and procedures to meet these requirements, and they are an integrated part of our solutions and services. We apply ISO 27001 control measures in our approach to cybersecurity.

Securing API integrations involves implementing robust measures designed to protect data in transit and at rest, authenticate and authorize users, mitigate potential attacks, and maintain system reliability.

Overall, securing API integrations requires an approach that includes encryption, access control, traffic management, and proactive security procedures. By carefully applying these principles, we achieve a high level of security for our APIs. While no guarantees can be made, the above measures address a wide range of security threats and ensure the integrity, confidentiality, and availability of our API-based software solutions.

Below is an overview of the procedures and components included in our solutions:

1. Establish and Maintain Concrete and Relevant Contingency Plans:
These plans ensure preparedness against the attack surface, risks, and potential consequences. They also help prevent over-implementation. It is important to consider the consequences; if they are minor, the item should be given lower priority. Threat landscape and the combination of risk and consequence should determine priority and effort.

2. Use HTTPS for Data Encryption:
Implementing HTTPS instead of HTTP is essential to encrypt data sent between client and server, ensuring sensitive information cannot be easily intercepted by attackers (Man-in-the-Middle). HTTPS uses SSL/TLS protocols, which not only encrypt the data but also authenticate the server’s identity.

3. Authentication and Authorization:
Implementing robust authentication and authorization mechanisms is critical to verify user identities and control access to different parts of the API. OAuth 2.0 and JWTs are popular choices for token-based authentication.

4. Rate Limiting:
Rate limiting is important to protect APIs from brute-force attacks and ensure fair resource usage among consumers. Implement rate limiting based on IP address, API token, or user account to prevent a single user or service from overwhelming the API with requests.

5. Logging:
Logging user access and data usage can reveal patterns of unauthorized access and usage. It can also be used for debugging and performance improvements.

6. API Gateway:
An API gateway acts as a reverse proxy and provides a single entry point for managing API calls. It isolates backend logic and enables centralized security management, such as SSL termination, authentication, and rate limiting.

7. Input Validation:
Validating all input received by your API is a fundamental security measure to protect against various injection attacks. Use allowlists for input validation to ensure only permitted characters are processed.

8. Security Headers:
Security headers are crucial to prevent common web vulnerabilities. Set headers such as Content-Security-Policy (CSP) to prevent XSS attacks by specifying which dynamic resources are allowed to load.

9. Regular Security Audits and Testing:
Regular security audits and automated testing play a critical role in identifying vulnerabilities in your API. Use tools and methods such as static code analysis, dynamic analysis, and penetration testing.

10. Web Application Firewall (WAF):
A WAF acts as a protective barrier for your API, analyzing incoming requests and blocking malicious ones. Configure your WAF with rules specific to your application context.

11. Security Policies and Documentation:
Having clear and comprehensive security policies and documentation is essential to inform developers and users about secure interactions with your API. Document security practices and secure coding guidelines.

12. Security Procedures in Software Development:
Use pull requests for four-eyes approval of commits, and employ software that scans code for vulnerabilities (supply chain attacks are also addressed in our development procedures).

The module enables central administration and planning of transports.
Transport agreements (agreements for fixed deliveries/pick-ups) are created per supplier/tank at the agreed intervals (number of loads, days, and weekly intervals). The system generates a central plan based on this information.
Planning can also be based on fertilizer balances at the supplier (farmer).

The module enables advanced configuration of supplier settlement, including dry matter, fees, transport settlement, and more.

The module enables planned execution of transports to be assigned to individual vehicles, from which the system can register activities and positions for each delivery.

Drivers can create their own transports via the DriverApp. The DriverApp supports offline operation (data is stored locally and synchronized once network coverage is restored).

This module provides extended logging of transport activities.
Routes are logged with distance and duration, and can be displayed via Google Maps. This enables the creation of a statistical basis for transport optimization per vehicle or driver.

Additionally, time spent on farms, unloading, and loading times can be tracked using geofencing. Drivers can start and end their workday and register breaks.

SMS notifications can be sent directly to suppliers and/or the mixer.

Experience:

Lommy via Care4All

SMS / mixer notifications via the CPSMS system (Compaya SMS Gateway)

Weight retrieval from truck scales (requires truck scale integration)

Health status is displayed using color indicators.

Drivers are able to create transports on their tablet.

A summarized overview per supplier/address of the day’s planned transports can be displayed.
Option to select available transports (e.g. buffer trips).

Login via Azure AD.

Option to block a tank from the DriverApp and send a notification to a shared mailbox or selected user.

Prompt in the DriverApp to take samples according to the selected biomass configuration.

Option to adjust the vehicle’s tare weight from the DriverApp.

Option to change tank and/or depot on an existing transport.

Option to record the tank’s GPS coordinates when the vehicle is located at the farmer’s site.

The module provides external access to data via a web browser (Google Chrome).
With two-factor authenticated login, each supplier can obtain a precise overview of all deliveries and follow the analysis results associated with them. In addition, data can be exported to Excel (typically used by the farmer’s consultant). Access is provided to view all transports, including planned transports.

The module allows suppliers (farmers) to book, reschedule, and cancel transports.

The module also includes an administrator access, enabling biogas plant staff to quickly create ad hoc transports in the system.

Suppliers can upload contracts, certificates, and other relevant documents. Documents are automatically stored in a supplier-specific folder structure.

Suppliers can enter budgeted tonnage, kg of nitrogen (N), and kg of phosphorus (P), which among other things form the data basis for reporting to Natur & Erhverv.

File management, including transfer of settlement documents (specifications, invoices, credit notes) – settlement documents are displayed in the supplier portal.

Handling of text layout such as bold, italics, etc., when using text fields.

Creation of multiple depots for digested biomass.
Different fertilizer profiles can be created and are used in the planning of designer manure.

Creation of multiple depots (storage locations) for raw biomass.
Inventory management of various outgoing fractions (digested slurry, separated slurry, biofibers, etc.).

Post analyses on transports with the option to remove an analysis from a delivery and repost a different value.

Import of analysis data from the Eurofins file format.

It is possible to retrieve information registered in the CHR Register using the supplier’s CVR number.

Based on the retrieved data, a warning will be displayed in the biomass role center if there are health issues associated with the supplier.

During the data import, an address table is updated simultaneously. This can be used when creating new tanks, ensuring that the address from the CHR Register is applied to the tanks.

.

.

.

.

.

Specify vehicle capacity in minutes; the planning takes this into account and creates transports up to the defined limit. Optional buffer time can be specified, which may be relevant in cases where outbound trips are made without returning with raw material.

Export of transports to external route optimization

When biomasses are moved from one storage location to another, or from a storage location to a reactor, a proportional allocation of mixed biomasses is performed and registered as individual inventory entries.
For RedCert reporting purposes, the setup can also ensure that these movements can be traced back to the individual deliveries from suppliers.

Incoming and outgoing transports are, upon registration, mirrored to inventory and location management in standard Business Central (BC).
Based on this, it is possible to use standard BC inventory management with the associated benefits, such as MRP runs and financial follow-up on purchases.

Purchase agreements form the basis for consolidation into purchase orders, after which it is possible to handle subsequent purchase invoices in accordance with the agreed pricing.

Transports are automatically linked to the purchase agreement, making it possible to track deliveries against the agreement in terms of quantity and price.
Through integration with standard BC, purchases provide a financial overview and enable validation of incoming purchase invoices against weighed transports.

Basic. Movements with a wheel loader are recorded electronically via wheel loader weighings. Integration is available with load cells from Meldgaard.

Internal inventory movements can be created on a tablet, retrieving actual weighings from the wheel loader. Central ordering/planning of biomass or recipes (multiple biomasses in varying quantities) is supported. Retrieval of actual weighings from the wheel loader requires that data can be obtained electronically and requires the wheel loader app.

Purchase agreements form the basis for consolidation into purchase orders, allowing subsequent purchase invoices to be handled in accordance with the agreed pricing.

Transports are automatically linked to the purchase agreement, making it possible to track deliveries against the agreement in terms of quantity and price.

Through integration with standard Business Central (BC), purchases provide a financial overview and enable verification of incoming purchase invoices against weighed transports.

Advanced module for mass flow reports according to RedCert standards. Configured based on requirements from the RedCert/ISCC consultant or the biogas plant.

Post analyses on transports with the option to remove an analysis from a delivery and repost a different value.

Data retrieval from the analysis scale: Scan the label on the sample and weigh it (first wet, then dry). In the process, the data is linked to the delivery. Requires that the analysis scales can provide weighing data electronically.

.

.

Mobile App (Android/iOS) that receives planned tasks and allows data collection on these tasks.
Login per user.
Registration and planning of maintenance tasks in Business Central.
Time tracking and project management in Business Central.
Clock-in/Clock-out registration.

Basis

Essentials

Premium

Ultimate

If you would like to learn more about our modules for biogas plants, you are always welcome to contact us directly

Klaus Gaarde

Klaus Gaarde

Partner and Head of Consulting, Product Owner for Apps and Mobile Solutions

Carsten Skovbjerg

Carsten Skovbjerg

Managing Director and Co-owner of Elite IT

Karl Therkildsen

Chairman of the Board and Business Developer