Objects that tools retrieve from other authoring tool documents can become the design basis for objects in downstream documents. Objects that become the design basis for other objects can be specific objects that accumulate more data as they move through the lifecycle or can be schematic or logical objects in one application that evolve into more detailed objects downstream.
Design basis is implicitly based on retrieval, which means you do not have to define it. For example, a pump retrieved from a Process Flow Diagrams becomes the design basis for a pump in the Smart P&ID document. When you change common properties for the pump and retrieve the changes into Smart P&ID, tasks to update property values are automatically added to the To Do List. The same process works for logical items that are a design basis for other items, such as a stream in Aspen Basic Engineering that results in multiple pipe runs in Smart P&ID.