The elements of a concrete simple physical process derived from the core process model. SensorML is an OGC Standard. Copyright (c) 2019 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . A PhysicalComponent is a physical process that will not be further divided into smaller components. The method describes (as an algorithm or text) how the process takes the input and, based on the parameter values, generates output values. A physical process where the spatial and temporal state of the process is relevant. sml:AbstractPhysicalProcess References the physical component or system (e.g. platform) to which to which this component or system is attached. A spatial reference frame of the physical component itself; this reference frame is absolute and defines the relationship of the reference frame to the physical body of the component; position of the component relates this reference frame to some external reference frame. Note that units are specified in the position so they are not specified as part of the SpatialFrame. Supports local time reference frames such as "time past mission start". Note that units are handled in timePosition so they are not specified in the TemporalFrame. Provides positional information relating the component's spatial reference frame to an external spatial reference frame. Positional information can be given by location, by full body state, by a time-tagged trajectory, or by a measuring or computational process. Provides Time positions typically reference a local time frame to an external time frame. For example, a timer-start-time might be given relative to an "absolute" GPS time. A general temporal frame such as a mission start time or timer start time. The origin should just describe context of the start of time (e.g. start of local timer). A general spatial Cartesian Reference Frame where the axes and origin will be defined textually relative to a physical component. A textual description of the origin of the reference frame relative to the physical device (e.g. "the origin is at the point of attachment of the sensor to the platform"). Axis with name attribute and a textual description of the relationship of the axis to the physical device; the order of the axes listed determines their relationship according to the right-handed rule (e.g. axis 1 cross axis 2 = axis 3). A choice of elements for defining spatial state (e.g. location, orientation, linear/angular velocity and linear/angular acceleration. Provides positional information in textual form (e.g. "located on the intake line before the catalytic converter"); shall only be used when a more precise location is unknown or irrelevant. Provides static location only using a gml:Point element. Provides a static location using a swe:Vector. Provides location and orientation as a DataRecord consisting of one or two Vector elements. Provides time-tagged dynamic state information that can include, for instance, location, orientation, velocity, acceleration, angular velocity, angular acceleration; shall be a DataArray consisting of a DataRecord element of multiple Vector fields. Provides for positional information to be provided by a process; example processes could include a physical sensor such as a GPS, a computational process such as an orbital propagation model, a specific web service such as a SOS, or any process who's output provides positional information.