Skip to main content
Question

How to track software versions in installed base (objects)

  • November 24, 2025
  • 1 reply
  • 10 views
N
Do Gooder (Customer)
Forum|alt.badge.img+1

In IFS Cloud, Functional Objects are used to build the physical/site structure, and Serial Objects represent instantiated parts with a serial number (e.g., each machine is a Serial Object belonging to a Functional Object/site).

What is the recommended or reference method in IFS Cloud to:

  1. Capture and maintain the software version for each machine (each Serial Object)?

  2. Track software products installed at a site that do not have a serial number and therefore cannot be represented as Serial Objects?

Out of the box, I see several possible mechanisms, but I’m unsure which one is considered best practice for software/version tracking:

  • Technical Classes / Characteristics

  • Test Points / Parameters

  • Documents (DMS)

  • Service Notes

  • Installed Base Object Structure
    (but software is not serialized → would need to be a Functional Object, which cannot be placed under a Serial Object)

What is the usual or recommended approach to model machine firmware/software versions and site-level software in IFS Cloud?

 

Cheers

1 reply

Indika99
Do Gooder (Employee)
Forum|alt.badge.img+3
  • Indika99
  • Do Gooder (Employee)
  • November 25, 2025

Hi ​@nheine,

✅ Recommended Approach in IFS Cloud:

  1. For Machines (Serial Objects) – Software/Firmware Version Tracking

    • Use Characteristics on the Serial Object to store software version details. Characteristics allow you to define custom attributes (e.g., “Firmware Version”, “Software Build”) and maintain them per Serial Object.
    • This is considered best practice because Characteristics are designed for technical attributes and can be updated as versions change.

  2. For Site-Level Software (Non-Serialized)

    • Represent these as Functional Objects in the Installed Base structure.
    • Apply Characteristics to these Functional Objects for version information.
    • Alternatively, if the software is more like a product or license, you can use Installed Base Product records linked to the Functional Object.

  3. Why Not Test Points or Service Notes?

    • Test Points/Parameters are intended for operational measurements (e.g., temperature, pressure), not static version data.
    • Service Notes are for maintenance history, not configuration tracking.
    • Documents (DMS) can store manuals or release notes but are not ideal for structured version control.

  4. Installed Base Object Structure

    • Software that is not serialized should not be forced under a Serial Object. Instead, model it as a Functional Object at the site level or under the relevant system node.

Best Practice Summary

  • Characteristics are the primary mechanism for version tracking in IFS Cloud.
  • Use Functional Objects for non-serialized software and Serial Objects for machines.
  • Combine with Documents for supporting files (release notes, installation guides).

Hope this is helpful.

Terms & ConditionsCookie settingsAccessibility statement