Equipment & Installed Base

Modeling the physical and functional asset hierarchy in IFS Cloud using Functional Objects and Serial Objects within an Object Structure, supporting multiple relationship views (Function, Location, From, To, Process, Pipe System, Electrical) so maintenance cost and history roll up correctly.

Classifying equipment in IFS Cloud through Object Types / Type Designations, Technical Classes and Technical Attributes (with Technical Class Groups) and Item Classes, so assets carry standardized technical specs and failure-analysis data for consistent maintenance and reporting.

Defining the spare parts associated with equipment objects in IFS Cloud - object spare part lists (cross-referenced to Inventory for balances, prices and suppliers) and reusable multi-level Detached Spare Part Lists (kits) used when planning material for PM actions and work orders.

Tracking customer and supplier warranties for serialized equipment in IFS Cloud - defined on Part/Inventory Part/Sales Part/Supplier or order lines with conditions (duration or usage such as hours/km) and covered cost types, visible on Part Serial and Equipment/Service Objects, and activated on work orders and Service Management requests.

Setting up and recording object measurements (meters/counters) in IFS Cloud via Parameters (Accumulated/Limit/Condition) and Test Point/Parameter lines on equipment objects, feeding Preventive and Condition Based Maintenance, usage-based warranty expiry and analytics, with an ObjectMeasurementService API from 25R1.

Establishes and maintains the virtual representation of every unit the manufacturer has shipped, so that aftermarket service, warranty and contract entitlement all resolve to a single authoritative asset record. In IFS Cloud this means Object Families, Object Subfamilies and Models as installed base basic data, Part Serial records created through inventory and delivery, and Service Objects classified as either Serial or Functional. Getting serialisation and the Model-Part connection right here is the precondition for every downstream warranty, claim and contract process in this theme group.

Establishes the single authoritative register of critical facility assets for a data centre in IFS Cloud, structured as a Functional Object hierarchy from site down to individual UPS module, generator set and switchboard. Serialised plant is registered as Serial or Equipment Objects carrying nameplate, warranty and criticality data, so that PM plans, spares policy, documents and work history all anchor to the same physical asset. Without this register there is no traceable link between the maintenance programme and the electrical one-line the site is certified against.

Establishes and maintains the configuration baseline for serialised platforms in IFS Cloud Fleet and Asset Management, where serial parts configure template structures and those template structures are the basis for the serial structures used to plan, schedule and control a fleet. The link to IFS/PDM Configuration is activated by enabling after-delivery serial tracking on an engineering part, and serial part data carries the vehicle-part flag, life limit, operational parameters and maintenance group. Product model and manufacturer data must be established before serial structures are created, because product model drives the functional breakdown used when faults are reported.

IFS Cloud has a real and well-documented Part Ownership model - Company Owned, Consignment, Supplier Loaned, Supplier Owned, Customer Owned, Company Rental Asset and Supplier Rented - with an owner on the stock record, zero inventory valuation and exclusion from planning for customer-owned stock, controlled transfer-of-ownership paths, and persistent ownership that survives out of inventory for serial-tracked parts and tracked components. Modelling the government customer as the owner of Customer Owned stock is therefore a legitimate way to segregate and track government property. IFS does not, however, implement Government Property accountability as a regulated concept: there is no GFE/GFP property record, no property administrator approval workflow, no loss/damage/destruction report object, and no interface to any government property registry - all of which remain external or manual.

IFS Cloud provides real serialised identity: part serial tracking with a part serial catalog, serial history recording the objects, purchase orders and inventory locations a serial has passed through, and Serial Objects in equipment administration carrying type designation, technical data, warranties, structure position and maintenance history. That is a sound basis for item-level traceability of a serialised deliverable. IFS does not implement unique item identification as a regulatory scheme: no UII construct, enterprise identifier or issuing agency code field was found, no MIL-STD-130 data-matrix content generation, and no interface to any government item registry, so mark content generation and registry submission are a labelling/integration bolt-on and an external filing process.

Customer-funded equipment relocation (without meter): technical study, design/approval, cost confirmation, payment, execution and energization of the relocated equipment.

Meter Removal Sub Process is an electric distribution utility planning process executed across FSM/FSM Connect/FSM Mobile with SAP ISU and GIS integration. It is mapped to IFS Equipment & Installed Base and comprises 11 extracted steps covering request intake, validation, site/technical work and cost/work-order handling. Provenance is the client To-Be draw.io planning flows.

Meter and Equipment Removal is an electric distribution utility planning process executed across FSM/FSM Connect/FSM Mobile with SAP ISU and GIS integration. It is mapped to IFS Equipment & Installed Base and comprises 25 extracted steps covering request intake, validation, site/technical work and cost/work-order handling. Provenance is the client To-Be draw.io planning flows.

Establishes and maintains the single authoritative register of the property estate in IFS Cloud - portfolio, site, building, floor and space - modelled as a Functional Object hierarchy under Enterprise Asset Management. Every space carries a measured area on an agreed measurement basis (IPMS, BOMA or local NIA/GIA convention), a use classification and a capacity, so that occupancy, cost allocation, PPM and lifecycle planning all resolve to the same location key. This is the client-side estate backbone, not the contractor-side asset list.

Matches business demand for space to the supply held in the IFS Cloud property register, allocating floors, zones and workstations to occupying organisations and cost centres. Occupancy and utilisation are then measured against that allocation to drive rebalancing, densification and release decisions. Space is managed as a strategic asset with a cost, not as a fixed given.

Proves that the asset register in IFS Enterprise Asset Management matches the physical estate, and keeps it that way. A verification programme is issued as Work Orders by site, surveyors capture and correct attributes against Functional Object, Serial Object and Equipment Object records, and an independent sample audit scores data quality before sign-off. Corrected data then republishes Maintenance Plan / PM Action coverage and reconciles to the Fixed Asset register.

Covers installing a new gas meter set and exchanging meters at end of life, on periodic change-out, or on AMI upgrade, executed in IFS Cloud as Work Orders against the serialised meter install base. The meter and regulator are handled as Serial Objects mounted on the premise Functional Object so the removed and installed serials, index readings and seal numbers form an auditable chain. The process closes when the exchange is posted to CIS and the removed meter is dispositioned to test or scrap.

Covers the recurring cycle of collecting gas meter reads from AMI, AMR or manual routes, validating them, and converting the failures into field work in IFS Cloud. Readings land as Measurement / Parameter values against the meter Serial Object so consumption history, tamper indications and communication faults sit alongside the maintenance history of the same device. Exceptions that cannot be resolved in the back office become Service Requests or Work Orders scheduled through PSO.

Covers the physical survey of HVAC and building services plant across a site or estate and the construction of a structured, hierarchical asset register that PPM regimes can be built on. Each asset is captured with type, location, condition, criticality and nameplate data, then individually linked to the correct maintenance schedule. Poor asset data at this stage is one of the most common reasons PPM programmes drift out of compliance.

Manages the register of lifting equipment and lifting accessories in a building or service portfolio and the statutory thorough examination regime that keeps each item lawfully usable, from interval derivation through competent-person examination, report capture, defect handling and record retention. Jurisdiction: UK, under the Lifting Operations and Lifting Equipment Regulations 1998 (LOLER), with in-between inspection and maintenance duties arising under PUWER. Covers passenger and goods lifts, hoists, MEWPs, gantry and jib cranes, davits and the accessory population.

Maintains the medical device installed base in IFS Cloud so every device at a customer site is a Service Object carrying its Model, part, serial number and UDI identification. The FDA Device Identifier is held against the model or part record while the object serial number carries the Production Identifier, giving a traceable link from the object structure back to the labeler GUDID entry. Object structures, connected parties and move history keep location, ownership and configuration current for entitlement, recall and field safety corrective action purposes.

Controls the tools, gauges and test instruments that technicians use on medical devices, so that no measurement is ever taken with an out-of-calibration instrument. Each instrument is held in IFS Cloud as its own Serial Object with a calibration maintenance plan, a due date and a traceability record. Instruments that fall due are blocked from issue, and any measurement taken with a later-failed instrument triggers a recall of affected results.

Manages the fiscal measurement asset base and the proving cycle at pipeline receipt and delivery points, terminals and truck racks, with meters, provers and flow computers held in IFS Cloud as Serial and Equipment Objects. Proving is scheduled as PM Actions driven by contract terms, elapsed time and throughput, and each proving Work Order records meter factor and repeatability Measurements against the applicable API MPMS Chapter 4 criteria. Out-of-tolerance results trigger repeat runs, a Fault Report and, where the shift cannot be resolved, removal of the meter from custody transfer service.

Keeps every instrument that a telecom operator relies on for service acceptance or safety decisions - OTDRs, optical power meters, spectrum analysers, RF personal exposure monitors, torque wrenches, anemometers - within a controlled, traceable calibration regime. Covers registration, interval-driven recall, calibration at an accredited laboratory or in-house, recording of as-found results and tolerance judgement, and quarantine plus measurement-impact review when an instrument is found out of tolerance. In IFS Cloud the instruments are managed as serialised objects on a preventive maintenance plan that raises calibration Work Orders.

Runs the controlled exit of legacy network - 3G and copper sunset, post-merger site consolidation, lease exits - from candidate selection through to asset retirement. Covers traffic-free validation and network planning sign-off, the physical strip-out Work Order including reinstatement obligations, recovery and grading of removed serialised equipment into reuse, remanufacture or scrap, compliant disposal with certificates, and retirement of the asset records. In IFS Cloud this closes the loop between Enterprise Asset Management, the spares pool and the fixed-asset register.

Installation of new water meters and planned or reactive exchange of existing meters (age-based replacement programs, failures, upsizing, AMI endpoint retrofits): scheduling, final/initial read capture, serialized meter and register/endpoint recording, AMI communication verification, and read handoff to CIS/billing.

Collection of meter reads via AMI head-end, drive-by AMR, or manual routes; validation of reads against consumption profiles; and management of exceptions (no-reads, tamper flags, continuous-flow/leak alerts, zero consumption) including dispatch of field investigation orders and endpoint remediation so billing runs on actual reads.

Periodic and complaint-driven testing of water meters for registration accuracy per AWWA M6 practice: test program definition by size class and age, bench and in-situ testing at low/intermediate/high flows, recording results against accuracy limits, repair/retire decisions, and fleet accuracy analytics supporting apparent-loss (non-revenue water) reduction.

Establishes the structural backbone of the treatment plant in IFS Cloud EAM: site, treatment train, unit process and equipment position held as a Functional Object hierarchy, with serialised rotating and repairable equipment registered as Serial Objects and buried mains as Linear Assets. Every object is scored for criticality from likelihood of failure and consequence of failure, and that score drives maintenance strategy, work order priority and spare stocking. All downstream PM, CBM, corrective and shutdown processes in the plant inherit this structure.