Frequently asked questions - FAQ
Security, GDPR, licenses, releases—explained in a nutshell.
General information
What is omis?
omis is a cloud-based operator platform that bundles maintenance, malfunctions, statutory inspection data, documents, analyses, and partner communication for network filling stations in a single interface.
Who is omis suitable for?
For operators of networked filling stations who want to reduce downtime, increase transparency, and reduce administration and lifecycle costs.
How long does the introduction take?
Implementation usually takes around eight weeks, divided into phases for data transfer, configuration, testing, and training. omis can reduce this to as little as four weeks, provided that the necessary data is made available in the required format.
Is omis mobile-friendly?
Yes. omis is web-based, responsive, and runs on smartphones, tablets, and desktops in a browser.
Which languages does omis support?
Currently: DE, EN, IT, FR, SK, RO, BG, SR, PL, DK, NO. Other languages available on request.
Do I need an app or special software?
No. A modern browser is sufficient; updates are performed automatically in the cloud.
Can we start without complete data?
Yes. You can start with core processes and gradually expand master data.
Are there any import options?
Yes, structured imports (e.g., Excel/CSV) for objects, devices, users, checks.
What is the licensing situation?
We have four basic products: omis BASIC, omis PRO, omis INFINITY, and omis ENTERPRISE—you can find all the information you need on the products. Users can be added flexibly (no rigid user licensing). The price depends on the number of stations in the gas station network.
What roles are there in the project?
Typical: Project management by operator, key users, omis consulting/support; clear responsibilities for each phase.
Security, Data Protection & Compliance
How does omis protect our data?
With encryption (transport/resting), role-based permissions, audit trails, regular backups, and penetration tests.
Where is the data stored?
Primarily on our own cloud server in Switzerland. Other options available on request.
Who owns the data?
You. Exports are possible at any time.
Does omis support GDPR compliance?
Yes. Order processing, data minimization, defined deletion concepts, and audit-proof evidence are all part of the solution.
Is there source code escrow?
Yes, for additional operational reliability.
Are changes traceable?
Yes. Audit trails log relevant actions with timestamps and user assignments.
How is access controlled?
About client, role, and location concepts based on the least privilege principle.
Are there business continuity/disaster recovery plans?
Yes. Regular backups, restart processes, and defined responsibilities.
IoT, Integrations & Technology
How does omis connect to our systems?
Via standardized interfaces (e.g., REST) to ERP/DMS/BI as well as device/manufacturer APIs.
Which devices can be connected?
Typical examples include car washes, gas pumps, fuel dispensers, price displays, level/leakage/temperature sensors, refrigerators, and coffee machines.
What happens during device events?
Events and measured values can automatically trigger tickets, workflows, and notifications and be incorporated into analyses.
Is there an API?
Yes. For exports, integrations, and automated workflows.
Which browsers are supported?
Current versions of popular browsers (Chrome, Edge, Firefox, Safari).
Operational work (malfunctions, maintenance, test data)
How is the fault handling process carried out?
Recording via web/smartphone, automatic ticket creation, assignment to service providers/teams, processing with SLAs/escalations, completion with documentation.
Can messages be generated automatically?
Yes, for example, through IoT signals or defined events (weather, vandalism, material fatigue).
Are priority and urgency supported?
Yes. Custom workflows, priorities, SLA tracking, and escalation rules.
What evidence can be attached?
Photos, documents, comments, checklists; complete status and processing history.
Can we digitally map legal audits?
Yes. Deadline monitoring, checklists, responsibilities, reminders, and audit-proof logs.
How do I plan maintenance?
From maintenance schedules, periodic measures, and resource/deployment planning to service reports and approvals.
Can spare parts and cost centers be stored?
Yes. For transparency regarding material usage and costs per process/location.
How can we find test certificates?
In document management, structured by location/asset/process, immediately accessible according to authorization.
Does omis support the processing of insurance claims?
Yes. From damage assessment to receipts/deadlines to communication with insurers and partners.
Is there an inquiry and order tool?
Yes. Request for quotation, comparison, approvals, SLA/budget checks, and documented commissioning.
Master data & documents
What master data is maintained?
Equipment/machinery with manufacturer, model, serial number, year of manufacture, location, warranty/guarantee, inspection intervals, responsibilities, and much more.
How are documents managed?
Centralized and audit-proof, with versioning, audit trails, PDF/CSV export, and targeted approvals (authorities/partners).
Who controls access rights?
You define user and group rights down to the document type level.
Analyses & Decisions
What key figures does omis provide?
MTTA/MTTR, downtime, SLA rate, root cause/frequency analyses, costs per ticket/location, trends, and benchmarks.
Do we recognize conspicuous locations or device types?
Yes. Comparison views and filters show clusters, outliers, and potential for improvement.
Does omis help with "repair vs. replacement"?
Yes. History and cost development per asset support economic decisions.
How can I export/report data?
Ad hoc exports (PDF/CSV) and scheduled reports are possible.
Operation, scaling, and support
How does omis scale in growing networks?
Locations, users, and partners can be added at any time; multilingual interfaces support international teams.
What support channels are available?
Help portal with documentation/FAQs, ticket support, training. Emergencies via hotline outside business hours.
How often are updates released?
Our software is usually updated every 6 weeks . This means that the software gets better and better and includes more features. At no additional cost.
Is the software available during these regular updates?
As a rule, updates require only short downtimes, if any. If this is the case, we schedule them during the night (according to UTC +2).
Is there a roadmap?
Yes, thematically – without strict deadlines (focus on quality, security, UX, integrations, test data & audits). We deliberately do not specify concrete deadlines; the quality of implementation is important to us.
Does omis offer training courses?
Yes. Compact training courses for technicians, dispatchers, and service providers; documentation is available.
Products & Cost-effectiveness
What packages are available?
omis Basic, omis Pro, omis Infinity – price available upon request, and omis ENTERPRISE also available upon request.
What is the pricing logic?
The price depends on the number of stations in the gas station network.
What effects are realistic?
Reduced administration costs, higher system availability, better decision-making capabilities thanks to data and standards.
Can we cancel if necessary and take our data with us?
Yes. Exports are possible at any time; you retain data sovereignty.
Community & Events
Is there any exchange with other operators?
Yes. Community formats and the omis user summit with best practices, insights, and networking.
When is the next omis user summit taking place?
October 8–9, 2025, in Geinberg; details/agenda can be found in the community section.