Most manufacturers are flying blind the moment a product leaves the dock
Most companies lose sight of their assets the second the invoice is paid. This is a massive failure of Asset Lifecycle Management. For a company like SMAY, sustainability cannot be a buzzword. It has to be a data-driven reality. If you don't know where your equipment is, how it is performing, or when it needs to be reclaimed, you don't have a circular economy. You have a linear waste stream disguised as a business.
The transition to a circular model requires a radical shift in how we treat the Functional Object. In IFS Cloud, this object is the digital anchor. It must be born during the Sales Quotation, not created as an afterthought when the first service call comes in. Waiting until the maintenance phase to track an asset is a technical debt you will never pay off.
{semanticux}
The Sales Quotation: Where the digital twin is born
The mistake most consultants make is treating a quotation as a simple financial document. In a professional ALM setup, the Sales Quotation is the first heartbeat of the asset. This is where the configuration begins. By defining the functional requirements and the expected installation environment at this stage, you ensure that the data flows without friction into the project and service phases.
When SMAY issues a quote, the system should already be preparing the placeholders for the physical hardware. This creates a link between the customer's need and the long-term maintenance reality. If you skip this, you are manually rebuilding data structures six months down the line. It is inefficient and expensive.
Functional Objects are not just Serial Parts
There is a massive confusion between a physical piece of hardware and its function in a system. A Serial Part is what you ship. A Functional Object is the role that part plays in the building. You might replace the physical fan three times over twenty years, but the functional requirement for air extraction remains the same.
By tracking the Functional Object, you maintain the history of the position, not just the metal. This distinction allows for a true circular economy. You can pull a serial part back for refurbishment, wipe its history, and insert a new one without losing the operational data of the facility. This is the difference between a mess of spreadsheets and a structured Asset Lifecycle Management strategy.
Closing the loop with Service Contracts
A circular economy fails if there is no mechanism to bring the asset back. This is where Service Contracts come in. In IFS Cloud, the contract should be tied to the Functional Object from day one. This ensures that maintenance is proactive. You aren't just fixing things when they break; you are managing a fleet of assets that will eventually be harvested for parts or refurbished for a second life.
If your service team doesn't have immediate access to the configuration created during the Sales Quotation, they are working in the dark. They will waste time identifying parts that should have been linked to the object years ago. This lack of transparency kills the profit margin on service and makes sustainability impossible.
Stop breaking the system with custom code
Engineers love to write custom scripts to link quotes to objects. Stop. IFS Cloud provides the architecture to do this through configuration. Using CRIMS for basic data flow is a sign of a weak architect. You should be using Workflow and Business Process Automation to move data from the quote to the asset structure.
Every time you write custom PL/SQL to handle asset creation, you make the 25R1 or 25R2 upgrade more difficult. The goal is a Clean Core. Use the standard OData APIs if you need to push data from external CRM systems into IFS. This keeps the integration stable and ensures that your circular economy data survives the next five years of system updates.
Strategy is worthless without technical discipline
Circular economy is not a marketing story you tell shareholders. It is a technical discipline. If your IFS Cloud environment is cluttered with disconnected quotes and orphaned serial parts, you are failing. Start at the quotation. Build the Functional Object immediately. Link the Service Contract before the product leaves the factory.
The tools are already in the system. The only thing missing is the willingness to follow the architecture instead of fighting it. Those who master the Functional Object will own the lifecycle. Those who don't will be buried under the cost of their own waste.
