|
Vehicle
|
Vehicle |
[An equipment for transporting shipments. The vehice also moves from origin to the target of the transportation activity. Examples are trucks or forklifts.] |
|
Equipment
|
Equipment |
[An object needed to perform an activity, and when used is in continuous control of the agent involved in the activity. Equipment cannot execute activities by themselves.
Examples: Vehices, cranes, and tools such as hammers and drills.] |
|
NonConformanceIssue
|
NonConformanceIssue |
[Issue that is about an entity that does not conform to its specification] |
|
ProductIssue
|
ProductIssue |
[Issue related to the product (e.g., a building or some of its components or systems)] |
|
OperationalCost
|
OperationalCost |
[The operational costs for the Energy System] |
|
LifeCycleCost
|
LifeCycleCost |
[Lifecycle Cost Parameters for the Energy Systems] |
|
StakeholderRole
|
StakeholderRole |
|
|
Role
|
Role |
[Role is equivalent to the BFO class 'role' (http://purl.obolibrary.org/obo/BFO_0000023)] |
|
DeliveryTeam
|
DeliveryTeam |
[Lead appointed party and their appointed parties (ISO 19650-1, def. 3.2.6).
Note 1: A delivery team can be any size, from one person carrying out all the necessary functions through to complex, multi-layered task teams. The size and structure of each delivery team are in response to the scale and complexity of the asset management or project delivery activities.
Note 2: Multiple delivery teams can be appointed simultaneously and/or sequentially in connection with a single asset or project, in response to the scale and complexity of the asset management or project delivery activities.
Note 3: A delivery team can consist of multiple task teams from within the lead appointed party’s organization and any appointed parties.
Note 4: A delivery team can be assembled by the appointing party rather than the lead appointed party. (ISO 19650-1, def. 3.2.6)] |
|
Team
|
Team |
[A set of persons working together for some purpose] |
|
SameValues
|
SameValues |
[A constraint for all involved Properties must have a same value] |
|
ElementaryConstraint
|
ElementaryConstraint |
[Constraint that does not have other more simple constraints as its parts.] |
|
Labeling
|
Labeling |
[Labeling is a generic mechanism to associate entities with any number of labels that are unique within a given category. The purpose is to enable the representation of connections to existing systems, databases or classification schemes.] |
|
Quality
|
Quality |
[Quality is equivalent to the BFO class 'quality' (http://purl.obolibrary.org/obo/BFO_0000019)] |
|
EvaluationCriteria
|
EvaluationCriteria |
[Evaluation Criteria is a definition of a benchmark, standard, or yardstick against which accomplishment, conformance, performance, and suitability of an individual, alternative, activity, product, or plan is measured.] |
|
InformationContentEntity
|
InformationContentEntity |
[Identifiable information content. Examples are a BIM model, a drawing, a specification, an image, a message, and an issue. Separate from physical information carriers. Note that the instances of this concept represent particular identifiable contents (such as a version of a architectural model or a master plan), not the physical carrier of that content (such as a database, a file in a cloud storage, or a bunch of paper). There can be several different carriers for the same information content entity] |
|
ResourceCost
|
ResourceCost |
|
|
CostProperty
|
CostProperty |
|
|
Load
|
Load |
|
|
Device
|
Device |
[An object that performs a function, requiring at most only intermittent control by a user (an agent).
Examples: Sensor, actuator, dishwasher, heater.] |
