A1.DF32 · IFS Cloud Inventory (Part Ownership)

Government Furnished Equipment Custody & Accountability

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.

44 details worked out · license requiredDefense & Aerospace Sustainment variantMaster

Execution steps

6 steps

Sign in

The sequence somebody actually follows in IFS Cloud, step by step, written for a person doing the work rather than for a diagram.

Data requirements

12 requirements

Sign in

Every entity this process needs, mapped to its IFS object, marked mandatory or optional, with the source system it comes from. This is the list a data migration is built from.

Configuration decisions

5 decisions

Sign in

The choices this process forces you to make in IFS, named up front. Finding these in week nine of a program is what makes week nine expensive.

KPIs

4 measures

Sign in

What this process is measured on, so the reporting requirement is known before the process is configured rather than after go-live.

Integration points

5 integrations

Sign in

Where this process has to talk to something outside IFS, and what crosses the boundary.

Workshop questions

6 questions

Sign in

The questions to ask the business about this process, written before the workshop. This is the difference between a design session and a discussion.

Prerequisites

3 prerequisites

Sign in

What has to be true before this process can run at all: master data, other processes, setup completed elsewhere.

Industry variants

3 variants

Sign in

How this process differs by industry: the parts a utility does differently from a manufacturer, already worked out rather than discovered.

Process diagram

1 BPMN diagram

Sign in

A real BPMN diagram, editable in the platform, not a picture of one. It is the same diagram your team will annotate in the workshop.

Sources

1 citation

Sign in

Where this came from. Every process traces back to IFS documentation and release notes, so a claim about how IFS behaves can be checked rather than believed.

Every process in the library looks like this.

44 details are already worked out for this one process. A license opens them, and the other 619 processes with them.