Projects / Industrial reporting

Janus

Production figures with a shared reporting structure.

Janus connects daily production inputs, KPI calculations and reporting across plants. Local teams record the figures, while administrators maintain the equipment and material structure, configure operating rules and manage reporting periods. Historical comparisons and forecasts extend the same platform’s analytical capabilities.

01 / Daily production data

Daily inputs with completion tracking.

Janus: Daily production entry

Daily rows separate production and inventory quantities from operating hours, with units shown in each column. KPI and stoppage tabs share a month selector, completion indicator and overdue-entry notice, so the team can review reporting gaps before preparing the monthly figures.

02 / Monthly reporting

Monthly figures organised by equipment and measurement.

Janus: Monthly reporting

Monthly reporting

The working challenge

A monthly total needs a clear source within the plant. Teams need to know which department, equipment and measurement category a figure belongs to before interpreting it.

The product solution

Category filters and the plant hierarchy organise electrical power, fuels, raw materials, production and quality data. Monthly columns and totals remain beside the selected equipment and measurement.

03 / Plant and material settings

Plant and material settings that define the reporting context.

Janus: Plant setup

Plant setup

Plant configuration connects the equipment hierarchy with production-day boundaries, produced and received materials, and storage capacities. Administrators can define a reporting day that reflects the plant’s operating schedule.

Janus: Material configuration

Material configuration

The material record combines classification, characteristics and reporting categories. Dedicated tabs hold SAP and LIMS codes, recipes and targets, giving teams a structured place to maintain the material’s references and properties.

04 / Reporting periods and versions

Calculation controls and reporting status for each plant.

Janus: Version management

Version management

The working challenge

Reporting administration needs to distinguish the selected version and period from each plant’s current status. A shared overview helps the team see where reporting remains open and where it is closed.

The product solution

Administrators select a version and period, then review open and closed plants. Calculation controls are available for an individual site or all sites, with an overview that also identifies mixed reporting status.

Technology stack

The technology behind Janus.

Plant reporting interfaces, calculation services and the infrastructure used to deliver them.

Reporting workspace

React 18, TypeScript and Material UI form the reporting and administration interface.

  • React 18
  • TypeScript
  • Material UI

Services & messaging

The service stack combines .NET 8 and ASP.NET Core with gRPC, Kafka and RabbitMQ.

  • .NET 8
  • ASP.NET Core
  • gRPC
  • Kafka
  • RabbitMQ

Production data

EF Core provides data access; SQL Server and PostgreSQL are the project’s relational databases.

  • EF Core
  • SQL Server
  • PostgreSQL

Delivery & testing

Docker and Kubernetes support deployment. Jest and Cypress are used for automated tests.

  • Docker
  • Kubernetes
  • Jest
  • Cypress
Your production reporting

Which number takes the longest to reconcile across your plants?

Bring a daily report and the monthly summary it feeds. We will map the input, unit, reporting period and calculation rules before designing the shared workspace.

Plan your reporting platform