When communicating with a meter, an application may demand periodical actions. If these actions are not linked to tariffication (ActivityCalendar or Schedule), use an object of type ActionSchedule.

When handling tariffication structures, you can use an object of type ActivityCalendar. It determines, when to activate specified scripts to perform certain activities in the meter. The activities, simply said, scheduled actions, are operations that are carried out on a specified day, at a specified time. ActivityCalendar can be used together with a more general object type, Schedule, and they can even overlap. If multiple actions are timed to the same moment, the actions determined in the Schedule are executed first, and then the ones determined in the ActivityCalendar. If using object type SpecialDaysTable, with ActivityCalendar, simultaneous actions determined in SpecialDaysTable are executed over the ones determined in ActivityCalendar.

All object types are used.

AssociationLogicalName object type is used with meters that utilize Logical Name associations within a COSEM (Companion Specification for Energy Metering) context. This kind of meters are known as COSEM Logical Devices, each one of them having a unique ID, a logical device name.

AssociationShortName object type is used with meters that utilize Short Name associations within a COSEM (Companion Specification for Energy Metering) context.

To determine auto answering settings (for data transfer between device and modem(s) to answer incoming calls), use AutoAnswer object.

To determine auto connecting settings (for data transfer from the meter to defined destinations), use AutoConnect (previously known as AutoDial) object.

An object of type Clock is used to handle the information of a date (day, month and year) and/or a time (hundredths of a second, seconds, minutes and hours).

An object of type Data typically stores manufacturer specific information of the meter, for example configuration data and logical name.

An object of type DemandRegister stores a value, information of the item, which the value belongs to, the status of the item, and the time of the value. DemandRegister object type enables both current, and last average, it supports both block, and sliding demand calculation, and it also provides resetting the value average, and periodic averages.

To determine the Ethernet settings, use the EthernetSetup object.

When a certain occasion should cause a certain action, use an object of type Event, which the client system can enable. When enabled, and when the specified occasion occures, the event is sent the soonest possible. Information of the time of the occasion, the acknowledgement of the event, and its response time is included.

ExtendedRegister stores a value, and understands the type of the value. Refer to an object of this type by its logical name, using the OBIS identification code.

To determine the GPRS settings, use GprsSetup object.

To determine the HDLC (High-level Data Link Control) settings, use the IecHdlcSetup object.

To determine the Local Port settings, use the IecLocalPortSetup object.

To determine the Twisted Pair settings, use the IecTwistedPairSetup object.

To determine the IP 4 settings, use the Ip4Setup object.

To determine the M-BUS settings, use the MbusSetup object.

To determine modem settings, use ModemConfiguration object.

Default value, no object type is set.

To determine PPP (Point-to-Point Protocol) settings, use the PppSetup object.

ProfileGeneric determines a general way of gathering values from a profile. The data is retrieved either by a period of time, or by an occuring event. When gathering values from a profile, you need to understand the concept of the profile buffer, in which the profile data is stored. The buffer may be sorted by a register, or by a clock, within the profile, or the data can be just piled in it, in order: last in, first out. You can retrieve a part of the buffer, within a certain range of values, or by a range of entry numbers. You can also determine objects, whose values are to be retained. To determine, what to retrieve, and what to retain, you need to assign the objects to the profile. You can use static assignments, as all entries in a buffer are alike (same size, same structure).

Register stores a value, and understands the type of the value. Refer to an object of this type by its logical name, using the OBIS identification code. OBJECT_TYPE_REGISTER.

When handling tariffication structures, you can use RegisterActivation to determine, what objects to enable, when activating a certain activation mask. The objects, assigned to the register, but not determined in the mask, are disabled.

RegisterMonitor allows you to determine scripts to execute, when a register value crosses a specified threshold. To use RegisterMonitor, also ScriptTable needs to be instantiated in the same logical device.

RegisterTable stores identical attributes of objects, in a selected collection of objects. All the objects in the collection need to be of the same type. Also, the value in value groups A to D and F in their logical name (OBIS identification code) needs to be identical. Clause 5 determines the possible values in value group E, as a table, where header = the common part, and each cell = a possible E value, of the OBIS code.

To create a table of setpoints within the logical device, and to connect any / all entries to an analogue control point of the physical device, use RemoteAnalogueControl.

To create an array of switches within the logical device, and to connect any / all entries to a digital relay, to switch on or off any equipment (that is connected to the physical device), use RemoteDigitalControl.

SapAssigment stores information of assignment of the logical devices to their SAP (Service Access Point)s.

To handle time and date driven actions, use Schedule, with an object of type SpecialDaysTable.

To trigger a set of actions with an execute method, use object type ScriptTable. Each table entry (script) includes a unique identifier, and a set of action specifications, which either execute a method, or modify the object attributes, within the logical device. The script can be triggered by other objects (within the same logical device), or from the outside.

To determine the SMTP protocol settings, use the SmtpSetup object.

With SpecialDaysTable you can determine dates to override a preset behaviour, for specific days (data item day_id). SpecialDaysTable works together with objects of Schedule, or Activity Calendar.

StatusMapping object stores status words with mapping. Each bit in the status word is mapped to position(s) in referencing status table.

To determine Internet TCP/UDP protocol settings, use the TcpUdpSetup object.

Use Tunnel, when you need to transfer data of a source by DLMS. All different kinds of sources need to implement a corresponding Tunnel to match the attributes, such as source, destination, QoS (Quality od Service), message length, and EOM (End of Message). Though source and destination addresses come from lower layers, the message should include information of the source and destination, too.

In an object of type UtilityTables each "Table" (ANSI C12.19:1997 table data) is represented as an instance, and identified by its logical name.