02 / Digital

We show our own digital products by stating the stage each one is at.

Digital is where Asopel develops its own products: applications, software products, and ambitious digital projects. Because it is a showcase domain, the claim discipline here is the strictest on the site. Every item says what it is and what it is not today.

Method: systems engineering

What we develop

The common thread is moving fragmented information and fragile flows onto a surface people can use with confidence. Products come out of that need, not the other way round.

Web applications and internal tools
Data flows, integrations, and automation
Decision-support and monitoring interfaces
Reusable system components

How we develop it

An interface alone is not a product. The data model, the failure states, and the maintenance responsibility behind it are part of the design. The method layer is systems engineering.

Source and responsibility map
A data model with explicit states
Accessible interfaces and measurable failure states
Reproducible setup and automated checks

When an idea becomes a product

The maturity labels are not decoration; they are a commitment. An item moves up a label only when specific conditions hold.

Live: usable and maintained for the stated purpose
Prototype: a working experiment, not a supported product
Internal: used by Asopel, not offered for general use
Direction: the problem is defined, the solution is not validated

What exists today

This list is short because it contains only what genuinely exists. New items are added when they work and can be shown.

FIG. 01

Bilingual site infrastructure

The content model, route structure, and release controls of the site you are reading. One typed content source feeds both languages, and the pre-release checks run automatically.

Maturity: Live

The problem it solves: A company telling the same truth consistently in more than one language.
What is in it: Two languages fed by one content model
Automated build, type, and content checks
Identity and asset validation before release
What it is not today: Not a product offered for general use; it is Asopel’s own working infrastructure.

FIG. 02

Synthetic operations system

An interactive prototype showing how an operational system can be observed, without using any real customer’s data. It runs in the browser and sends nothing out.

Maturity: Prototype

The problem it solves: Seeing scattered events and constraints in one flow you can decide from.
What is in it: Domain-neutral synthetic data
Deterministic state transitions
Runs in the browser, with no server
What it is not today: Not a production service or a product you can buy. It can be examined in the lab.

Open the operations system

FIG. 03

Scroll-world experiment

A scroll-driven narrative experiment. Its images are abstract product renders: no place, no interior, no person, no text. A motionless alternative always exists.

Maturity: Prototype

The problem it solves: Cases where text alone is not enough to explain a system.
What is in it: An abstract visual language with no location
A full alternative without scroll or motion
Human-reviewed media
What it is not today: Not a product or a service for sale; a clearly labelled experiment.

See the experiment in the lab

FIG. 04

Evidence workspace

An internal method and toolset that keeps source, assumption, test, and limitation notes in the same working flow.

Maturity: Internal

The problem it solves: Keeping assumptions, sources, and limitations visible throughout a technical study.
What is in it: Source and date records
Assumption and limitation notes
Repeatable checklists
What it is not today: An internal working method, not a standalone software product.

FIG. 05

Repeatable operations systems

A solution direction that could be adapted to different organisations, not yet turned into a product. The problem class is defined; the solution is not validated.

Maturity: Direction

The problem it solves: Not solving similar data and workflow problems from scratch every time.
What is in it: A defined problem class
Explained through a synthetic demo
A validation plan through paid feasibility
What it is not today: Not a product that is sold, supported, or priced. No market or customer-outcome claim.

Let’s test a digital product idea together.

Describe your product idea