Diagram
| Super-types: | abstractSingularDataObject < obj_productFlowModel (by extension) |
|---|---|
| Sub-types: | None |
| Name | obj_productFlowModel |
|---|---|
| Used by (from the same schema document) | Complex Type obj_productFlowModels |
| Abstract | no |
'The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element.'
">'The name of the facility which is represented by this model. The name can be qualified by a naming system. This also defines the kind of facility.'
'The name and type of a facility whose context is relevant to the represented installation.'
'The date and time of the start of validity for this model.'
'The date and time of the termination of validity for this model.'
'The time for which \"currently existing\" data is desired from the network. All connections (and related data) existing at this time (i.e. start and end bracket this value) will will be returned if requested. The existence time is a server query parameter. See the WITSML API Specification appendix on \"Special Handling\" of growing objects for a description of the behavior related to this parameter.'
'The minimum time index contained within the report. The minimum and maximum indexes are server query parameters and will be populated with valid values in a \"get\" result. See the WITSML API Specification appendix on \"Special Handling\" of growing objects for a description of the behavior related to this parameter.'
'The maximum time index contained within the report. The minimum and maximum indexes are server query parameters and will be populated with valid values in a \"get\" result. See the WITSML API Specification appendix on \"Special Handling\" of growing objects for a description of the behavior related to this parameter.'
'Defines the external port in another Product Flow Model to which an external port in this model is connected. An external port should be connected to an external port with the opposite direction. The connected external port must be in another Product Flow Model. These connections should always be defined on a one-to-one basis. For example, if a facility may receive input from multiple other facilities then a separate input port should be defined for each of those facilities. This allows any question about mass balancing to be contained within each individual model. The external port name must match the name of an external port on the network that represents this model.'
'The description of one named network within this model. Each model is self contained but may reference other newtorks for defining internal detail. One of the networks must represent this model.'
'A descriptive remark about the model.'
'A container element that contains elements that are common to all data objects.'
'A container element that can contain custom or user defined data elements.'