This topic deals with two uses of a generic model:
The first one applies to functional design based on process activities (e.g. PUMPING) and the related funtional units.
The second one applies to human activities (e.g. PUMP SIZING) and the related organization of resources.
Below is the generic functional resource model that applies to all use cases.
The Functional Specification, defining an instance of ClassOfFunctionalObject in a Role, may include a mathematical definition of its transfer function, as are being used in process simulator software.
Examples of a population of the various objects in above diagram for all use cases are given in the table below.
1) This does not mean that everything has to be modeled in such detail. But if required this is the way to go, partially or entirely.
2) The relationship between an object and its definition may also be implemented differently, such as with the template RepresentationOfClassOfIndividualOnDocument.
WBS - OBS
The same diagram as above (actually two of them interconnected) is shown with the annotation where the Work Breakdown and the Organization Breakdown are.
The first diagram is shown below again, but this time indicating which templates are to be used.
The code listed here is for PUMPING as listed in the table, thereby using the templates as indicated above.
It is possible for companies to create a library of standard resource models. Obviously these are adaptable.
For a sequal see the topic "From Design to Reality".