The Net is the Automation.
We bring people, systems and devices together.
NettedAutomation GmbH
Information & Communication Systems (NAICS)

back - menue - contact - search
news - solutions - standardization - seminars - marketing support
question & answers - discussion forum - glossary - links - about us

-> home > standardization > iso > tc 184 > sc5 > working group 2 > mms revision 2000

MMS Revision (ISO/IEC 9506 : 2000)

2000 Edition  MMS 2000 Edition Service Models


The official publication of the MMS version 2000 has some syntax errors. Therefore NEMA has removed the syntax from their website. We expect a new MMS version in a few months.
More details can be found in the pdf document:

Information on
Industrial automation systems --
Manufacturing Message Specification
ISO 9506; first edition 2000-08-15

MMS Evaluation Kit CD ROM for the fastest possible start to learn about
MMS technology (more details).

The Manufacturing Message Specification (MMS) is an application layer standard designed to support messaging communications to and from intelligent electronic devices (IED) in an distributed system environment.

ISO/IEC 9506 defines the Manufacturing Message Specification within the OSI application layer in terms of

  • an abstract model defining the interaction between users of the service;
  • the externally visible functionality of implementations conforming to ISO/IEC 9506, in the form of procedural requirements associated with the execution of service requests;
  • the primitive actions and events of the service;
  • the parameter data associated with each primitive action and event;
  • the relationship between, and the valid sequences of, these actions and events

2000 Edition

This is the second edition of ISO/IEC 9506-1. It differs from the first edition in the following ways:

a) The informal object modelling used in ISO/IEC 9506-1 has been replaced by the use of the object modelling techniques present in ASN.1, ISO/IEC 8824-2. Hence, this part of ISO/IEC 9506 defines an ASN.1 module, MMS-Object-Module-1, that contains the object models on which the service procedures are based.

b) The material in ISO/IEC TR 13345 that specifies subsets of protocol for MMS has been used in this part of ISO/IEC 9506 to specify options within the object models.

c) All the material of Amendments 1 and 2 have been incorporated into the document, as well as the Technical Corrigenda.

d) The services and protocol present in the Companion Standards already published, ISO/IEC 9506-3, ISO/IEC 9506-4, and ISO/IEC 9506-6, have been incorporated into the base standard, and new parameter CBBs have been added to the Initiate procedure to indicate their presence. The concept of Companion Standard has been simplified to a document that make explicit the relationship between the abstract models in MMS and the requirements of the application field that is the subject of the Companion Standard.

 As a result of this incorporation, the need for separate abstract syntaxes for each of the Companion Standards has been removed. All Companion Standards can now operate in the single abstract syntax of the base standard, although using other abstract syntaxes remains a possibility for backward compatibility.

e) The communication requirements of MMS have been generalized so that MMS is described with respect to an abstract set of services needed for its support.  The relation between this abstract set of services and the services provided by the suite of OSI communication protocols is specified in an annex.  This opens the possibility of having MMS operating correctly over alternate communication systems (such as reduced stack implementations) as long as the equivalent of these abstract services are provided.

f) The restrictions on the characters that can be used as an Identifier have been relaxed to allow an Identifier to begin with a numeric character, and by extension, to consist solely of numeric characters.

g) Many (but not all) occurrences of VisibleString have been replaced by a new production MMSString that provides the option of using an extended latin alphabet, suitable for western Europe, and an option to use an arbitrary string of characters taken from ISO 10646 or from elsewhere.

h) A new service, ReconfigureProgramInvocation, has been introduced into the clause on Program Invocation management. This service provides a technique of dynamically changing the constituent Domains of a running Program Invocation.

i) A new field was added to the object model of the Named Variable and Named Type. This field may be used to describe the semantics associated with the Named Variable or Named Type. The field is either predefined or has its value established as the name of the Named Type used to construct it in the DefineNamedVariable or DefineNamedType service. This field can be reported with the GetVariableAccessAttributes or GetNamedTypeAttributes service if a new parameter CBB has been negotiated.

j) The material of the document has been reorganized to provide shorter clauses.

k) The Scattered Access and the Real Data type have been removed from the base document and placed in informative annexes.

l) In accordance with the recommendations in ISO/IEC 8824-1, all occurrences of EXTERNAL in the protocol have been replaced with CHOICE { EXTERNAL, EMBEDDED PDV }.

MMS 2000 Edition Service Models:

7 The Virtual Manufacturing Device (VMD)

8 Environment And General Management services
  8.2 Initiate service
  8.3 Conclude service
  8.4 Abort service
  8.5 Cancel service
  8.6 Reject service

9 Conditioned service response
  9.3 DefineAccessControlList service
  9.4 GetAccessControlListAttributes service
  9.5 ReportAccessControlledObjects service
  9.6 DeleteAccessControlList service
  9.7 ChangeAccessControl service

10 VMD Support Services
  10.3 Status service
  10.4 UnsolicitedStatus service
  10.5 GetNameList service
  10.6 Identify service
  10.7 Rename service
  10.8 GetCapabilityList service
  10.9 VMDStop service
  10.10 VMDReset service

11 Domain Management Services
  11.2 InitiateDownloadSequence service
  11.3 DownloadSegment service
  11.4 TerminateDownloadSequence service
  11.5 InitiateUploadSequence service
  11.6 UploadSegment service
  11.7 TerminateUploadSequence service
  11.8 RequestDomainDownload service
  11.9 RequestDomainUpload service
  11.10 LoadDomainContent service
  11.11 StoreDomainContent service
  11.12 DeleteDomain service
  11.13 GetDomainAttributes service

12 Program Invocation Management Services
  12.2 CreateProgramInvocation service
  12.3 DeleteProgramInvocation service
  12.4 Start service
  12.5 Stop service
  12.6 Resume service
  12.7 Reset service
  12.8 Kill service
  12.9 GetProgramInvocationAttributes service
  12.10 Select service
  12.11 AlterProgramInvocationAttributes service
  12.12 ReconfigureProgramInvocation service

13 Unit Control
  13.2 Control Element
  13.3 InitiateUnitControlLoad service
  13.4 UnitControlLoadSegment service
  13.5 UnitControlUpload service
  13.6 StartUnitControl service
  13.7 StopUnitControl service
  13.8 CreateUnitControl service
  13.9 AddToUnitControl service
  13.10 RemoveFromUnitControl service
  13.11 GetUnitControlAttributes service
  13.12 LoadUnitControlFromFile service
  13.13 StoreUnitControlToFile service
  13.14 DeleteUnitControl service

14 Variable Access Services
  14.6 Read service
  14.7 Write service
  14.8 InformationReport service
  14.9 GetVariableAccessAttributes service
  14.10 DefineNamedVariable service
  14.11 DeleteVariableAccess service
  14.12 DefineNamedVariableList service
  14.13 GetNamedVariableListAttributes service
  14.14 DeleteNamedVariableList service
  14.15 DefineNamedType service
  14.16 GetNamedTypeAttributes service
  14.17 DeleteNamedType service
  14.18 Conformance
  14.19 Guidance To Implementors

15 Data Exchange Management Services
  15.2 ExchangeData service
  15.3 GetDataExchangeAttributes service

16 Semaphore Management Services
  16.2 TakeControl service
  16.3 RelinquishControl service
  16.4 DefineSemaphore service
  16.5 DeleteSemaphore service
  16.6 ReportSemaphoreStatus service
  16.7 ReportPoolSemaphoreStatus service
  16.8 ReportSemaphoreEntryStatus service
  16.9 AttachToSemaphore Modifier
  16.10 Conformance

17 Operator Communication services
  17.2 Input service
  17.3 Output service

18 Event Management services
  18.2 TriggerEvent service
  18.3 EventNotification service
  18.4 AcknowledgeEventNotification service
  18.5 GetAlarmSummary service
  18.6 GetAlarmEnrollmentSummary service
  18.7 Attach To Event Condition Modifier
  18.8 Conformance Requirements Unique to Event Management

19 Event Condition services
  19.2 DefineEventCondition service
  19.3 DeleteEventCondition service
  19.4 GetEventConditionAttributes service
  19.5 ReportEventConditionStatus service
  19.6 AlterEventConditionMonitoring service

20 Event Action services
  20.2 DefineEventAction service
  20.3 DeleteEventAction service
  20.4 GetEventActionAttributes service
  20.5 ReportEventActionStatus service

21 Event Enrollment services
  21.2 DefineEventEnrollment service 339
  21.3 DeleteEventEnrollment service
  21.4 GetEventEnrollmentAttributes service
  21.5 ReportEventEnrollmentStatus service
  21.6 AlterEventEnrollment service

22 Event Condition List services
  22.2 DefineEventConditionList service
  22.3 DeleteEventConditionList service
  22.4 AddEventConditionListReference service
  22.5 RemoveEventConditionListReference service
  22.6 GetEventConditionListAttributes service
  22.7 ReportEventConditionListStatus service
  22.8 AlterEventConditionListMonitoring service

23 Journal Management services
  23.2 ReadJournal service
  23.3 WriteJournal service
  23.4 InitializeJournal service
  23.5 ReportJournalStatus service
  23.6 CreateJournal service
  23.7 DeleteJournal service


The Net is the Automation.
© 2000-2002 NettedAutomation
composed by JohnBlack '01

back - menue - contact - search
news - solutions - standardization - seminars - marketing support
question & answers - discussion forum - glossary - links - about us