SLIM / Product
Protocols
Methods live in Word files, binders and people’s heads, and they change quietly. SLIM keeps every protocol versioned and step by step, and every notebook entry records exactly the version that was used.
The problem
Somebody tweaks a temperature, saves over the file, and the old version is gone. Months later the results do not match, and nobody can say what changed.
Five copies of the same method on three drives, all slightly different.
The reagents and instrument a step needs are hidden in a paragraph, so preparing is guesswork.
A method changes, and past experiments now describe something that was never run.
Try it yourself
Add steps, pick inputs from the inventory and the instrument each step needs, reorder them, then publish a version and watch the history build up.
A live demo running in your browser. Nothing you type is saved or sent anywhere.
How SLIM handles it
Solves: materials buried in prose
Not a paragraph with the materials hidden in it. Each step names what it consumes, the instrument it runs on and what it produces, and the inputs can be real items from your inventory.
55 °C for 5 min, then hold at 10 °C and add NT buffer immediately.
12 cycles for 1 ng input. Each halving of input adds a cycle.
Solves: _final_v2 copies and silent edits
Publishing creates a version. Edits wait as a draft until they are right. Every version is kept, shows how many entries were written against it, and can still be used long after it was replaced.
Solves: “which version did you run?”
Publish a run straight from the protocol into the notebook. The version you used is written into the entry as editable text, so the entry records what you really did, deviations included.
What changes for your lab
Keep exploring
Every part of SLIM links to the others. Here is what connects to protocols.
Send us a spreadsheet before the call. We build your inventory from it, show you around it live, and you keep it whether you continue or not.