5.3 DTM Use Case Realization

Operation:

Adjust SetValue

Brief Description:

Enables the actor to adjust the SetValues of a device (e.g. positioner, controllers).

Realizes Use Case(s):

Adjust SetValue

Invocation:

The Adjust-SetValue-Operation is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtAdjustSetValue

Operation:

Archive View

Brief Description:

A DTM may provide an archive for historical data. This realization element is for viewing the archived data

Realizes Use Case(s):

Archive

Invocation:

The Archive View is called directly by the Frame Application

Application ID:

-- not supported --

Operation:

Asset Management

Brief Description:

The contents of the Asset Management have not been defined yet.

Realizes Use Case(s):

Asset Management

Invocation:

The Asset-Management-Operation is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtAssetManagement

Operation:

Audit Trail

Brief Description:

The Audit Trail Operation (see bulk-audit-trail) is used for the realization of a device-specific control and documentation of changes in the device parameters.

Realizes Use Case(s):

Device-Specific Audit Trail

Invocation:

Is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtAuditTrail

Operation:

Bus Master Configuration

Brief Description:

GUI for configuration of the bus master.

Realizes Use Case(s):

Bus Master Configuration

Invocation:

Is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtManagement

Operation:

Calibration

Brief Description:

Calibration procedures to adjust the input for e.g. pressure transmitters or the current for the output.

Realizes Use Case(s):

Online Functions

Invocation:

Is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtCalibration

Operation:

Configuration

Brief Description:

The configuration operation lets a user define the structure of complex devices. Configuration is used online and offline.

Realizes Use Case(s):

Configuration

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtConfiguration

Operation:

Create Instance

Brief Description:

This operation generates the data set a DTM requires for the management of a device and feeds it with preset data.

Realizes Use Case(s):

Create Instance

Invocation:

is called directly by the Frame Application

Application ID:

-- not supported --

Operation:

Delete Instance

Brief Description:

Deletes the data

Realizes Use Case(s):

Delete Instance

Invocation:

is called directly by the Frame Application

Application ID:

-- not supported --

Operation:

Diagnosis

Brief Description:

This operation realizes all diagnostic methods a DTM provides for a device check.

Realizes Use Case(s):

Online Status

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtDiagnosis

Operation:

Download

Brief Description:

The Download Operation writes the current parameterization to the field device.

Realizes Use Case(s):

Download

Invocation:

is called directly by the Frame Application

Application ID:

-- not supported --

Operation:

Force

Brief Description:

This operation allows the user to modify the device and change his parameters within a defined time limit. On termination of this operation at the least the device is reset to its original state.

This operation realizes for example the simulation of sensor output values.

Realizes Use Case(s):

Simulation

Invocation:

Is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtForce

Operation:

Identify

Brief Description:

Displays identification of a device instance information e.g. address, TAG, Fieldbus-Rev., DD-Rev., Firmware. These information is protocol dependant. It also may contain device type specific information. Further information may be provided: references to documentation, area to add comments to the device instance.

Realizes Use Case(s):

Parameter Set Online View

Invocation:

The Identify is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtIdentify

Operation:

Install/Uninstall/Update

Brief Description:

The installation and deinstallation of the DTM-Software forms part of the DTM-Operation. Its software-technical realization will however be carried out outside the proper DTM-Module by suitable installation software.

The installation of DTM-Software does not necessarily also signify the notification in the Frame Application.

Realizes Use Case(s):

Install DTM, Deinstall DTM, Update DTM

Invocation:

Can be started directly by the Frame Application or by the surface of the operating system.

Application ID:

-- not supported --

Operation:

Load Data Set

Brief Description:

DTM loads data from a storage with a compatible data set format. Additional check for data compatibility must be done by the DTM.

Realizes Use Case(s):

Upgrade

Invocation:

is called directly by the Frame Application

Application ID:

-- not supported --

Operation:

Login

Brief Description:

When an operation with OEM-specific functions is started by an actor of the "OEM Service" user level, free accessibility to those functions can be enabled by another password inquiry.

This password inquiry is realized by operation "Login".

As in most cases OEM-specific functions only have an effect on online connected devices, it is possible to verify the password through the device and in addition make the device-internal functionality accessible.

This type of login is active during the entire session.

Realizes Use Case(s):

DTM-Specific Login

Invocation:

is called during other operations, when an "OEM Service" actor accesses operations with OEM-specific function elements.

Application ID:

-- not supported --

Operation:

Main Operation

Brief Description:

Entry point for a combination of different functions of a DTM (e.g. combination of parametrization, configuration, diagnosis, measured values).

Realizes Use Case(s):

Invocation:

The Main Operation is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtMainOperation

Operation:

Network Management

Brief Description:

Function of a Communication-DTM to manage the network information

Realizes Use Case(s):

Network Management

Invocation:

The Network Management is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtNetworkManagement

Operation:

Observe

Brief Description:

This operation includes all software elements which support the observation of a device without affecting the functions or the parameter set. The realization of an "Online Trend" can be named as an example of such an operation.

Realizes Use Case(s):

Online Trend

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtObserve

Operation:

Offline Compare

Brief Description:

The Compare-Operation implements the comparison of offline (persistent, transient, projected, default) parameters of two instances.

The Compare GUI of a DTM is switched (or extended) to Offline Compare using the IDtmDiagnosis::Compare() function

Realizes Use Case(s):

Persistent Data Comparison

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtOfflineCompare

Operation:

Offline Parameterize

Brief Description:

This operation enables editing of the instance persistent data set.

Realizes Use Case(s):

Offline Parameterization

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtOfflineParameterize

Operation:

Online Compare

Brief Description:

The Compare-Operation implements the comparison of offline (persistent, transient, projected, default) parameters with online parameters of the device.

A DTM may also permit a comparison with standard configurations or previously exported configurations of other devices through access to intrinsic databases.

Realizes Use Case(s):

Device-/Persistent Data Comparison

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtOnlineCompare

Operation:

Online Parameterization

Brief Description:

This operation enables the editing of parameters directly on the device. When this operation starts, the current parameterization of the device is read out and made available to the user for editing. Modified parameters are immediately entered into the device on successful completion of the plausibility check of the data set.

The edit function is disabled for actor "Operator" in order to realize the "Parameter Set Online View" Use Case.

Realizes Use Case(s):

Online Parameterization, Online Functions, Parameter Set Online View

Invocation:

is called directly by the Frame Application

Application ID:

FDTApplicationIdSchema:fdtOnlineParameterize

Operation:

Parameter Access

Brief Description:

DTM provides read and write access via SingleDataAccess interfaces

Realizes Use Case(s):

Replacement

Invocation:

is only called indirectly via other operations

Application ID:

-- not supported --

Operation:

Plausibility Check

Brief Description:

Operation "Plausibility Check" conducts a consistency check for all parameters of the device. Only offline data is contained in the consistency check.

This operation works as partial realization of other operations of the DTM

Realizes Use Case(s):

Plausibility Check

Invocation:

is only called indirectly via other operations

Application ID:

-- not supported --

Operation:

Print

Brief Description:

Print Operation stands for an action in which a report is created for current view following the generation of a printout. The report generation is an essential part of all operations during which data is edited or produced. The print operation therefore contributes to the part realization of almost all operations also implying a direct call of the GUI Operations.

Realizes Use Case(s):

The print operation participates in the realization of several operations of the DTM.

Every application context a DTM supports with a GUI, should also support printing.

Invocation:

If necessary, it should be possible to start the Print Operation from the DTM�s GUI. In this case the Print Operation is directly called by the DTM.

The Frame Application starts the Print Operation of the DTM directly for the realization of the Use Cases "Report Generation". In this case the Frame Application invokes the documentation interface of the DTM.

Application ID:

-- not supported --

Operation:

Scan

Brief Description:

A channel provides a list of available devices.

Operation:

Upload

Brief Description:

Loads the current configuration from the device to the device instance data set of the DTM

Realizes Use Case(s):

Upload

Invocation:

is called directly by the Frame Application

Application ID:

-- not supported --