command header determines the source and destination of a message sequenceId unique command identifier, copied to reply to match between command and reply this identifier is generated automatically by XMLlib. fromModuleId identifies module sending command, copied to toModuleId in reply this identifier is generated automatically by XMLlib. toModuleId identifies module to receive command, copied to fromModuleId in reply this identifier must be supplied by the application. timeStamp time when command was issued, this identifier is generated automatically by XMLlib.
Generic concentrator address, combines the legal possibilities concentratorId casdu decimal address concentratorName as reported from concentrator substationId decimal Id substationName group name (relationship to substationId is configured) broadcast to all concentrators
The elements are mutually exclusive.
Generic equipment address, combines the legal possibilities idType serial number and equipmentType name external application name (relationship Id, Type is configured) broadcast to all equipment within a type
The elements are mutually exclusive.
Generic homeAutomation, combines the legal possibilities id decimal address name group name (relationship Name to Id is configured) broadcast to all equipment
The elements are mutually exclusive.
prevalue, combines the legal possibilities id index, direct actual index actual cumulated index last automatic cumulated
The elements are mutually exclusive.
Generic unit, combines the legal possibilities id decimal address name group name (relationship Name to Id is configured) broadcast to all equipment
The elements are mutually exclusive.
used to address a group of concentrators within a substation
address space is share with casdu. The real casdu address is calculated 65000 + substationId
value comes from list: {'define'|'delete'|'list'|'updateAdd'|'updateRemove'}
Documentation
set type of action for external commands define new item (group, equipment etc.). If the item exist the command is rejected this action will often lead to a message being sent to the equipment in question delete existing item (group, equipment etc.). If the item does not exist or if the item is in use the command is rejected list existing item (group, equipment etc.). If the item does not exist the command is rejected updateAdd elements to existing item (group, equipment etc.). If the item does not exist the command is rejected this action will often lead to a message being sent to the equipment in question updateRemove elements from existing item (group, equipment etc.). If the item does not exist the command is rejected this action will often lead to a message being sent to the equipment in question
value comes from list: {'accepted'|'executing'|'finished'|'issued'|'rejected'|'terminated'}
Documentation
used in all commands: accepted means command is accepted but not yet executed. Status is not mandatory, but modules like e.g. schedulerModule use it, to signal that commands is valid and waiting to be executed. executing means command is passed on for execution. This status is not mandatory, but modules like e.g. commModule use it, to signal that commands are passed to equipment. finished means command executed correctly. This status is mandatory, the actual reply (e.g. load-profile) is available in the database. issued means command issued but not active. Thiss status is mandatory. rejected means the toModule was not allowed to execute command. This status is mandatory, but is handled by XMLlib. terminated means command did not execute correctly. This status is mandatory, the reason will normally be written to the log.
value comes from list: {'G23-410'|'G23-41X'|'G23-510'|'G23-511'|'G23-512'|'G23-51X'|'G23-520'|'G23-530'|'G23-5XX'}
Documentation
equipmentType defines the known equipment in the system G23-410 concentrator G23-41X all concentrators G23-510 meter 3 phase 100 Amp G23-511 meter 3 phase 60 Amp G23-512 meter 1 phase 60 Amp G23-51X all meters G23-520 loadswitch G23-530 meter gateway G23-5XX all meters,loadswitches and meter gateways
value comes from list: {'appl_interface01'|'appl_interface02'|'appl_interface03'|'appl_interface04'|'appl_interface05'|'appl_interface06'|'appl_interface07'|'appl_interface08'|'appl_interface09'|'appl_interface10'|'appl_interface11'|'appl_interface12'|'appl_interface13'|'appl_interface14'|'appl_interface15'|'appl_interface16'|'client_command'|'client_web'|'client_xml'|'module_alarm'|'module_scheduler'|'module_backup'|'module_comm'|'module_command'|'module_config'|'module_database'|'module_monitor'|'module_redundant'|'module_web'}
Documentation
defines the known modules, clients and libraries in the system that can send or receive commands.
remark: the relationship applInterface to real world name (e.g. sap) is defined in the database. appl_interface01-16 is external, converts to/from external application
client_command is external, handles command user interface client_web is external, handles generic user interface client_xml is external, handles xml from user interface
module_alarm is internal, handles alarms to network manager module_backup is internal, handles backup module_command is internal, handles command table module_comm is internal, handles equipment communication module_config is internal, handles binary configurations module_database is internal, handles database module_monitor is internal, monitors modules module_redundant is internal, handles redundant system module_scheduler is internal, schedules commands module_web is external, handles web (apache)
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.
