Asset Design & Compatible Units
Asset Design Basics: Standards, Plants and Classes
Configure the foundational reference data for IFS/Asset Design: standards (a uniform set of classes, class relations, technical attributes and object ID numbering schemes), plants that own the objects, and the design object/design part classes. This basic data is the starting point for any Asset Design implementation and governs how design objects and parts are structured, numbered and related throughout the engineering lifecycle.
Design Object Definition and Technical Specification
Register design objects - the focal point of a design that represents a function with requirements data to satisfy a process (e.g. a pump moving feed water with temperature, pressure, capacity and material requirements). Objects inherit technical attributes from their class template and become the hub for relations to other Asset Design information such as parent objects, design parts, documents and projects.
Design Part Definition and Object-Part Allocation
Define design parts (a common, structured set of materials, equipment and components) and allocate them to design objects using design part codes or by directly connecting the part to the object. The parallel design part / design object class structure lets parts that meet design object requirements be related to their object counterparts, and object class properties can be updated with data from related design parts.
Compatible Unit Definition and Estimating
Define compatible units - reusable, standardized units of work used when designing a design object structure, built as a hierarchical structure that contains a set of execution items needed to complete a certain work scope. Compatible unit revisions carry estimates; when released with a project connection the estimates transfer to the project (or planned cost transfers before release if the revision is flagged as an estimating revision), and released revisions generate work order structures and functional design object structures.
Design Object Structures and Plant Design (Asset Engineering)
Build the multidimensional design object structures in IFS/Asset Engineering. The functional structure arranges design objects by logical placement (facility, plant, area, system, sub-system) atop real objects (pumps, motors, tanks) and is the main navigational structure of an Asset Design installation. The plant structure takes form through classes, allowable class relations and object registration, with the plant owning the objects.
Design-to-Maintenance Handover (Equipment Object Creation)
Transition the engineered design into operational maintenance assets. Changing the design status can create equipment objects in IFS/Equipment, and the approved functional structure is used for Mechanical Completion, Commissioning, Handover and Equipment Maintenance. This maintains as-designed, as-built and as-maintained continuity from engineering through commissioning to operations, populating functional and serial equipment objects for PM.
Site Survey & Technical Design
Converts a permitted site into a buildable technical design: physical survey, RF and transmission design, power and structural loading, and the bill of material that construction will consume. In IFS Cloud the survey and design steps run as Project Activities on the site Sub Project, with drawings and design packs held as Documents and the resulting material list driving Purchase Orders and site kitting. Design approval is the gate that authorises material commitment and civils mobilisation.
Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.
Sign in to open it