About Resources | |||||
|
| ||||
Working, Non-working and Organizational Resources
Depending on how and where they are used, resources can be classified as working, non-working or organizational.
A working resource defines which resource executes an operation (for example, a robot, worker or conveyor). These are also known as 'who' resources.
A non-working resource defines with what resource an operation is executed (for example, a tool device). These are also known as 'with' resources.
An organizational resource defines a resource where an operation is executed (for example, a station, zone, line or workbench). These are also known as 'where' resources.
Programmable and Non-programmable Resources
A resource is programmable if it can have a logic or behavior in context. A resource is non-programmable if it can have a logic or behavior in reference only.
A robot is programmable. For example, a robot program, which exists in a certain context, can be added to it .
For example, an organizational resource is non-programmable. Its logic is only in reference. It cannot have a logic or behavior in context.
Resource Types
Each resource type has various characteristics (such as capability to aggregate other resources or be aggregated by other resources). A resource can be useful for a specific application or for several applications.
The characteristics of each resource type are discussed below.
Area
An Area is an organizational resource. It can be used by all DELMIA applications.
No logic is allowed for this resource, either in reference or in context. It is a non-programmable resource.
An Area 
can be referenced by a 'where' implement link only.
It can be aggregated by Organizational and Area resources. It can aggregate all types of Resources and Products.
Organizational
An Organizational resource is, as its name suggests, an organizational resource and defines where an operation is executed. It can be used by all DELMIA applications.
All logic must be defined in the reference. No contextual logic is allowed: it is a non-programmable resource.
An Organizational resource 
can be referenced by a 'where' implement link only.
It cannot be aggregated by any other resources. It can aggregate all types of resources and Products.
can be referenced by a 'who' implement link only.
can be referenced by a 'who' implement link only.
can be referenced by a 'who' implement link only.NC Machine
An NC Machine is a working resource.
Logic can be defined either in reference or in context (it is a programmable resource).
An NC Machine 
can be referenced by a 'who' implement link only.
It can be aggregated by NC Machine, Organizational and Area resources. It can aggregate Products and Tool Device, NC Machine, and User Defined resources.
Industrial Machine
An Industrial Machine is a working resource. It can be used by Live Device Behavior Experience to model composed resources with mechanisms.
All logic must be defined in the reference. No contextual logic is allowed: it is a non-programmable resource.
An Industrial Machine 
can be referenced by a 'who' implement link only.
It can be aggregated by Industrial Machine, Organizational and Area resources. It can aggregate Products and Tool Devices and Industrial Machine resources.
Inspect
An Inspect is a working resource.
Logic can be defined either in reference or in context (it is a programmable resource).
An Inspect 
can be referenced by a 'who' implement link only.
It can be aggregated by Organizational and Area resources. It can aggregate Products and Tool Device and User Defined resources.
can be referenced by a 'who' implement link only.Tool Device
A Tool Device is a non-working resource.
All logic must be defined in the reference. No contextual logic is allowed: it is a non-programmable resource.
A Tool Device 
can be referenced by a 'with' implement link only.
It can be aggregated by Tool Device, NC Machine, Inspect, Industrial Machine, Organizational and Area resources. It can aggregate Products, Tool Devices and User Defined resources.
can be referenced by a 'with' implement link only.Control Device
A Control Device is a working resource.
Logic can be defined either in reference or in context (it is a programmable resource).
A Control Device 
can be referenced by a 'who' implement link only.
It can be aggregated by Organizational and Area resources. It can aggregate Products and User Defined resources.
Logic Controller
A Logic Controller is a working resource. It can be used by Smart Device Builder to own the control logic of a system of leaf resources.
All logic must be defined in the reference. No contextual logic is allowed: it is a non-programmable resource.
A Logic Controller 
can be referenced by a 'who' implement link only.
It can be aggregated by Organizational and Area resources. It can aggregate Products only.
Sensor
A Sensor is a non-working resource. It can be used by Smart Device Builder to support scenarios with part detection or machines with sensors.
All logic must be defined in the reference. No contextual logic is allowed: it is a non-programmable resource.
A Sensor 
can be referenced by a 'with' implement link only.
It can be aggregated by Organizational and Area resources. It can aggregate Products only.
User Defined Resource
A User Defined resource is a non-working resource.
Logic can be defined either in reference or in context (it is a programmable resource).
A User Defined resource 
can be referenced by a 'with' implement link only.
It can be aggregated by User Defined, Transport, Storage, Control Device, Tool Device, NC Machine, Inspect, Organizational and Area resources. It can aggregate Products and User Defined resources.
Detection and Correction of Invalid Resource Structures
For various reasons, a resource structure may be invalid with respect to the aggregation rules for resources (for example, after an import from a previous version). It is possible to detect and correct these invalid resource structures using the Resource Structure Check in the West Quadrant of the PLM Compass and the Clone as New Resource command.
For example, consider the case of a tool device that aggregates a product. Prior to the V6R2011, it was possible to transform this product into any other resource type, such as organizational. However, an organizational resource inside a tool device is not a consistent structure.
From V6R2011, when generating a resource from a product, checks ensures that such invalid structures cannot be created.
Resource Structure Check
A Resource Structure Check is available by clicking the West Quadrant of the PLM Compass for Product workshops.
Note: If you have a PPR Context, right-click the Root Resource to be checked and select Open in New Window.
It detects the following resource structure anomalies:
- resource instances that have a type that is inconsistent with its aggregating father
- behavior representations that do not have their relative resources loaded
- contextual behavior representations aggregated under an organizational resource at a level that is too high.
The status of the resource is indicated by a colored square next to the tree object or the color of the object in the 3D view.
Resource Structure Correction
The Clone as New Resource command works for resources that are already in the database.
To correct an invalid resource instance that violates the aggregation rules, it is possible to generate a new resource from the existing one and change the Resource type as well as other attribute modifications.
The command creates a clone of the current resource in the database directly with the correct Resource type. All instances of the current resource are replaced in session by the new one. All other modified attributes on the resource extension are modified in session.
A propagate is necessary to ensure the validity of the resource. This ensures that modified attributes are written on the cloned resource and instance replacements are validated.