FOSS IQX™ for Network and IT Managers
For the network & IT manager

Instrument networks
you can actually govern

Adding an analyser becomes a configuration change, not a project.

Illustration of the FOSS IQX™ Device Management user interface

Trusted by producers worldwide

FrieslandCampina
Nutreco
Trouw Nutrition
Betagro
APC
Malt Products
BrightPet
Mar-Jac
What gets in the way

The parts of the job that eat the day

A separate stack per instrument

Every analyser arrives with its own client software, its own driver and its own support path.

Access managed twice

Instrument sign-in sits outside the directory you already run, so it is maintained by hand.

Data in unmanaged places

Results on local machines and shared drives, outside your retention and backup policy.

What changes

Where you sit in the flow

Adding an analyser or a site becomes a configuration change rather than a rollout.

For IT

One platform to govern, not a fleet of clients

Instruments connect to a cloud platform with central role management and managed retention. Adding a site or an analyser is a configuration change rather than a rollout.

  • Central role-based access across sites
  • Managed data retention rather than local files
  • Cloud-based, so nothing to install per machine
See what you use

Both products are open to your role. Here is what each one does with your day.

FOSS IQX™ Device Management

FOSS instrumentConnected once, governedcentrallyAccessYouFleet viewIT teamRetentionAuditorsDevice Management

FOSS IQX™ Supplier Quality

Supplier recordsOne place, governedcentrallyAccess controlYouRetentionIT teamAudit trailQA teamSupplier Quality
In practice

Adding a site without a project

A new analyser arrives at a plant that already runs others. It joins the existing network as a configuration change rather than a rollout, so there is no client software to package and no per-machine install to schedule.

Access follows roles rather than individual instrument logins. When somebody moves team or leaves, that is one change in one place instead of a list of systems to work through.

Retention is set once against your policy rather than depending on what happens to sit on a workstation in a laboratory.

What that means
  • New instruments are configuration, not deployment
  • One access model instead of one per analyser
  • Retention governed rather than assumed
What you use

The parts you will actually open

Network and IT managers spend most of their time in these.

FOSS IQX™ Device Management

Network


Instrument networks and site structure.

FOSS IQX™ Device Management

Roles and resources


Access managed centrally per role.

FOSS IQX™ Device Management

Data storage


Retention configured to your policy.

FOSS IQX™ Device Management

Instrument settings


Configuration managed without a site visit.

FOSS IQX™ Device Management

Instrument software


Version state across the fleet.

FOSS IQX™ Device Management

Model authorization


Control which calibrations are live.

FOSS IQX™ Device Management

SSO (add-on)


Sign in through your own identity provider.

FOSS IQX™ Device Management

API (add-on)


Move data between FOSS IQX™ and your own systems.

SSO and API are optional add-ons. A specialist can confirm what applies to your environment.

Which product

Two products, one thing to govern

Both run on the same software under the same access model, so adopting the second is a configuration rather than a new platform.

Quality, lab and network managers

FOSS IQX™ Device Management


One platform to govern rather than a client application per analyser, with central roles, retention and connectivity.

  • Full fleet control remotely
  • Decide centrally in minutes, execute locally in seconds
  • Alerted to actions in minutes
Requires at least one FOSS solution on site
Explore FOSS IQX™ Device Management Download the brochure
Quality, QA and procurement

FOSS IQX™ Supplier Quality


Supplier records under the same access model, without standing up a second system for procurement.

  • Increase visibility across your suppliers
  • Strengthen trust and relationships with your suppliers
  • Improve your supply chain resilience
No FOSS instrument required
Explore FOSS IQX™ Supplier Quality Download the brochure
Customer story

Somebody who runs it already

The recording, 2:04 to 2:55

JW
Jason WhittierLab Manager

United Wisconsin Grain Producers

Friesland, Wisconsin

Two instrumentsboth reporting into the same place
One systeminstead of one package per analyzer
Any locationthe plant, home, or a phone
I can go on from home, from my phone, from anywhere I have an internet connection.

Both instruments are connected to IQX™ – so rather than having one software package for this instrument and another for that one, it’s all one web-based system. I can go on from home, from my phone, from anywhere I have an internet connection.

Common questions

What IT asks before it signs anything off

Where is the data held?
FOSS IQX™ is cloud-based, and a Private Cloud add-on provides a dedicated environment rather than shared infrastructure. Hosting specifics are best confirmed directly, and a specialist can provide them in writing.
Can we use our own identity provider?
Yes, through the SSO add-on, so people sign in with the credentials they already have rather than a separate FOSS IQX™ account.
Can it feed our other systems?
Yes, through the API add-on, which moves data between FOSS IQX™ and your own systems without manual exports.
What does it need from our network?
It is cloud-based, so instruments connect outward rather than requiring inbound access. A specialist can go through the specifics with your team before anything is committed.
How are roles structured?
Access is defined by role rather than per instrument, and applied across sites. With the SSO add-on it follows the directory you already run.
Can we get data out if we stop using it?
Yes. The API add-on exists partly for that reason, and a specialist can confirm the export options for your configuration in writing.
Ready when you are

Bring instrument infrastructure under one roof

Let’s talk