Wallace

• Describe it

  Tell Wallace what the system is.

  Describe a system OPPI does not have built in. Wallace researches how to connect it and writes a briefing. You approve the briefing, and OPPI reads that source on a schedule from then on.

• The cold units

  Sensors on the walk-in, read through Wallace.

  In the kitchen, Wallace is how the sensors on each fridge, freezer and the walk-in reach OPPI. Their readings log by themselves, and one out of range opens a corrective action.

• The odd one out

  The system only your group uses.

  Groups run software nobody else does. Wallace connects OPPI to it through what that system already offers, an MCP server, a REST API or an upload, so the kitchen's numbers are not split across two screens.

1. 01

   Describe it

   Tell Wallace what the system is, in plain words.

2. 02

   Approve the briefing

   Wallace researches how to connect it and writes up a briefing. You approve it.

3. 03

   Read on a schedule

   OPPI reads that source on a schedule, from a cold unit's sensor to a group system.

• Fridges and freezerTemperature loggingEvery unit on the round. Every reading kept.

Questions.

Does Wallace replace my other systems?

No. It connects OPPI to them. You describe the system, approve the briefing, and OPPI reads from it on a schedule while the other system keeps doing its job.

Do I have to write code to connect something?

No. You describe the system in plain words. Wallace researches how to connect it and hands you a briefing to approve.

What can Wallace read from?

A source that offers an MCP server, a REST API or an upload. Once you approve the briefing, OPPI reads it on a schedule.