Processing more signals is not the goal by itself. What matters is whether Copass can keep distinguishing what belongs together, what is irrelevant, and in which operating context an observation matters as the signal base grows.
The current 48-signal test confirms that direction: the architecture remained stable, irrelevant signals continued to be separated, and the machine-specific structure was preserved. For us, that matters more than putting the biggest possible number on a slide.
The next step doubles the signal base to 96. We will test whether the same logic holds at greater scale — without feeding the engine machine-specific special rules or a pre-maintained signal library.
That is where Copass differs from conventional monitoring. Instead of wiring every measurement point individually and evaluating it against a fixed threshold, Copass is designed to place signals in context and build structure that belongs to this specific machine.
The distinction matters: these are internal tests and lab scenarios — not yet a field test in a customer plant. But this is exactly how we build Copass: prove it in the lab, then take it to the real machine.
Not more curves. More structure.