Introduction
OMNIS software is built around a structured workflow that links work systems, operating procedures, methods and samples into a single, traceable process. Each configuration step builds on the previous one, ensuring that instruments, parameters and data handling are aligned before a sample is ever run. Understanding how these elements connect, and the order in which they should be created, is essential for reliable results and efficient operation. This article walks through the OMNIS system workflow, explaining how software settings are related and outlining the correct sequence for creating and running a sample from setup to completion.
OMNIS Workflow
Before a sample can be run for the first time, a work system needs to be defined and used in a method. Methods are used in the operating procedure and OPs are used in the sample profiles.
- Create work system.
- Check work system.
- Create operating procedure.
- Create method(s).
- Assign work system to method.
- Build operating procedure from methods and commands.
- Create new sample profile.
- Create new sample list.
- Run sample.
OMNIS Software System Overview
- Hardware - OMNIS instruments are connected and populate instrument inventory.
- Software - Hardware and functional units are reserved in work systems.
- Commands - An assortment of commands are available which are assembled to create a method.
- Methods- Methods are sequences of individual commands.
- Operating Procedure - OPs are sequences of methods and commands.
- Sub-sample - A sample profile links to an OP and number of sub-samples to run.
- Sample - OMNIS focuses on the sample which contains components of all the above-mentioned items.
Additional Support
If you encounter any issues or need additional help, please submit a support ticket through Metrohm Technical Support.
For additional training on any of these topics, explore our available Metrohm Titration Training courses or learn more about our Metrohm Custom Training options.