River Logiceode docs

Describe your business

Tell RIA about your business in a new model's conversation, attach your data or a design document, answer what RIA asks, and settle what to optimize.

Where: Models→+ New→the message box

You describe your business to RIA in your own words, in the conversation that makes the model (New model). RIA writes what you say into the model's record, asks about what's missing, and builds the model when nothing is left to ask.

Say what the model is for

Put in your first message what you know. RIA asks about the rest, so it doesn't need to be complete:

  • the decision you want to make, such as how many of each product to make each week
  • the time the plan covers, and how it's divided (one week, 13 weeks, months)
  • what you make or sell, where, and for whom: products, sites, lines, suppliers, customers
  • your figures, with their units: prices, costs, capacities, demand
  • the limits that must not break, such as "the oven can run at most 60 hours a week"
  • what to optimize, such as weekly profit or total cost

For example:

Harbor Point Bakery is a small neighbourhood bakery with one oven. Each week we bake two products: sourdough loaves and croissants. A sourdough loaf uses 0.5 kg of flour and 0.25 oven hours. A croissant uses 0.1 kg of flour and 0.1 oven hours. Flour costs 1.20 per kg. We can sell at most 100 loaves and 300 croissants a week. We plan one week at a time and want to know how many of each to bake.

Write as much as you like. The record keeps what you said: What you told us, under What this model will do (Read what the model will do), and each place RIA changed, assumed, left out or asked about your words is listed there.

Attach your data

Above the message box:

  • Select datasets opens Your datasets, the datasets you've imported. Pick one and it sits above the box with its name; its × leaves it out again. Add another dataset picks one more. The datasets go with your next message; sent alone, they read "My datasets: name."
  • Upload picks a file from your computer. You can also drop a file on the message box.
FileWhat happens
.xlsx or .csvAdded to Datasets (Uploading, then Added) and picked for your next message
.pdf or .docxKept with the conversation as a design document; see below
.tsv, .txt, .md, .json or .tabIts text goes into your next message
.xlsRefused: "Save this workbook as .xlsx (Excel's current format) and drop it here again."
Anything elseRefused: "Use an Excel workbook, CSV or text file, PDF, or Word document."

With a workbook attached, RIA reads it and asks only about what its sheets leave out; see Start from a workbook. Once the model holds its data, the controls fold into one line, Data: and the dataset's name, with · Add or change to open them again.

A model reads one dataset. With more than one attached, the build stops and says "Only one dataset can be read into a model today, and this model has 2 attached:" and their names. Keep one of them in the conversation, or import the files together so they become one dataset (Import data).

Attach a design document

Drop a .pdf or .docx on the message box, or pick it with Upload. It shows Parsing doc…, then a chip with the file's name, its format and its length in characters (· truncated when it's longer than eode reads). The document stays with the conversation, and RIA reads it on every turn.

Add a note in "Add context for the design doc (optional)…" and send, or send with the box empty. Build model on the chip starts building a model from the document and what you've said, without waiting for RIA's questions. The × removes the document from the conversation.

Answer RIA's questions

RIA asks in the conversation, usually one question at a time; from a workbook it can ask several at once. Its possible answers are numbered, the one it proposes marked. While a question is open the message box reads "Answer RIA, or say what to change about" and the model's name. A message that is only the question is marked RIA IS ASKING · reply below.

  • Reply with a number. Type the number of your answer and send it. With several questions, give one number for each, in order, such as 1, 1, 1.
  • Click an answer. Where the answers end RIA's message, each is also a button under it. A click sends it as your reply.
  • Type your own. Say what's true in your words and send it. You can ask RIA a question back instead; it answers in the conversation.

Some questions come as a card in the conversation instead:

  • Your figures: a grid of the numbers RIA needs. Fill in the cells and click Done.
  • Your objective: what to optimize; see below.

While a card waits, the message box is off until you answer or dismiss it; see RIA's proposals. Everything waiting on you is also listed under Needs you on the record, each with Go to the chat (Answer what needs you).

When nothing is left to ask, RIA builds the model and solves the Base. A build can still stop to ask what it needs; it asks in the same conversation.

Settle what to optimize

At the Objective step, RIA proposes what the plan should push in a Your objective card: Maximize or Minimize, what, and in which unit, with the terms it adds up. When the model already has one, the card shows it after "Today's objective:".

  • Accept this objective: the card reads Accepted as the objective.
  • Type what you'd rather have in "Or say what you would rather have" and click Reply. The card reads You replied: and your words, and RIA takes it from there.
  • Dismiss closes the card without an answer. The record keeps the objective open until you ask RIA to propose it again.

Once it's settled, the record's Objective row shows it (Read what the model will do).

Change what you said

Tell RIA in the conversation, in your own words. The record lists each change under Since your last message, tagged Changed with what it was and what it is now.

  • Before the build, the change goes into the record, and RIA takes it into the steps still to come.
  • After the build, a change that needs the model built again comes as a change order card for you to preview and apply (Work a change order). The model is built again only when you say so. A question about the model changes nothing.

Every turn and what it changed stays in the record's History (Read the history).

Limits

  • A spreadsheet uploaded from the message box can be up to 100 MB; a text file put into a message, up to 1,000 KB.
  • One dataset per model.
  • A design document can be up to 10 MB; its text is read up to 200,000 characters. A conversation holds up to 5 documents and 500,000 characters; past that, the oldest is dropped.

On this page