ManagementPlanReplacementV07

catm.002.001.07

Terminal maintenance actions to be performed by a point of interaction (POI).

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% ManagementPlanReplacementV07 recursion level 0 with max 0
ManagementPlanReplacementV07 *-- "1..1" Header27 : Header
ManagementPlanReplacementV07 *-- "1..1" ManagementPlan7 : ManagementPlan
ManagementPlanReplacementV07 *-- "0..1" ContentInformationType18 : SecurityTrailer
  

Now, we will zero-in one-by-one on each of these building blocks.

Header building block

Set of characteristics related to the transfer of the management plan. Set of characteristics related to the transfer of transactions. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header27 recursion level 0 with max 1
class Header27{
    DownloadTransfer IsoTrueFalseIndicator
    FormatVersion IsoMax6Text
    ExchangeIdentification IsoNumber
    CreationDateTime IsoISODateTime
}
Header27 *-- "1..1" GenericIdentification71 : InitiatingParty
Header27 *-- "0..1" GenericIdentification92 : RecipientParty
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification92 recursion level 1 with max 1
class GenericIdentification92{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
GenericIdentification92 *-- "0..1" NetworkParameters5 : RemoteAccess
  

Header27 members

ManagementPlan building block

Sequence of terminal maintenance actions to be performed by a point of interaction (POI). Sequence of terminal management actions to be performed by a point of interaction (POI). For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ManagementPlan7 recursion level 0 with max 1
ManagementPlan7 *-- "0..1" GenericIdentification71 : POIIdentification
ManagementPlan7 *-- "1..1" GenericIdentification71 : TerminalManagerIdentification
ManagementPlan7 *-- "1..1" TerminalManagementDataSet24 : DataSet
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification71 recursion level 1 with max 1
class GenericIdentification71{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% TerminalManagementDataSet24 recursion level 1 with max 1
class TerminalManagementDataSet24{
    SequenceCounter IsoMax9NumericText
}
TerminalManagementDataSet24 *-- "1..1" DataSetIdentification7 : Identification
TerminalManagementDataSet24 *-- "0..1" ManagementPlanContent7 : Content
  

ManagementPlan7 members

SecurityTrailer building block

Trailer of the message containing a MAC or a digital signature. General cryptographic message syntax (CMS) containing data. protected by a MAC or a digital signature. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContentInformationType18 recursion level 0 with max 1
class ContentInformationType18{
    ContentType ContentType2Code
}
ContentInformationType18 *-- "0..1" AuthenticatedData5 : AuthenticatedData
ContentInformationType18 *-- "0..1" SignedData5 : SignedData
%% AuthenticatedData5 recursion level 1 with max 1
class AuthenticatedData5{
    Version IsoNumber
    MAC IsoMax140Binary
}
AuthenticatedData5 *-- "1..0" IRecipient6Choice : Recipient
AuthenticatedData5 *-- "1..1" AlgorithmIdentification22 : MACAlgorithm
AuthenticatedData5 *-- "1..1" EncapsulatedContent3 : EncapsulatedContent
%% SignedData5 recursion level 1 with max 1
class SignedData5{
    Version IsoNumber
    Certificate IsoMax5000Binary
}
SignedData5 *-- "0..0" AlgorithmIdentification21 : DigestAlgorithm
SignedData5 *-- "0..1" EncapsulatedContent3 : EncapsulatedContent
SignedData5 *-- "0..0" Signer4 : Signer
  

ContentInformationType18 members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the ManagementPlanReplacementV07 implementation follows a specific implementaiton pattern. First of all, ManagementPlanReplacementV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ManagementPlanReplacementV07Document implements IOuterDocument. Because ManagementPlanReplacementV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ManagementPlanReplacementV07.

classDiagram
    class IOuterRecord
    ManagementPlanReplacementV07 --|> IOuterRecord : Implements
    ManagementPlanReplacementV07Document --|> IOuterDocument~ManagementPlanReplacementV07~ : Implements
    class IOuterDocument~ManagementPlanReplacementV07~ {
        ManagementPlanReplacementV07 Message
     }
  

Document wrapper for serialization

The only real purpose ManagementPlanReplacementV07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:catm.002.001.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ManagementPlanReplacementV07.ToDocument() method. The returned ManagementPlanReplacementV07Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    ManagementPlanReplacementV07Document *-- ManagementPlanReplacementV07 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:catm.002.001.07">
    <MgmtPlanRplcmnt>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <MgmtPlan>
            <!-- ManagementPlan inner content -->
        </MgmtPlan>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </MgmtPlanRplcmnt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_1Cj8QdqJEeearpaEPXv9UA"
  nextVersions="_BegL8Q02EeqUVL7sB4m7NA"
  previousVersion="_CzZYcbC8EeamYaqfhG1ZuA"
  name="ManagementPlanReplacementV07"
  definition="Terminal maintenance actions to be performed by a point of interaction (POI)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MgmtPlanRplcmnt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <doclet
    xmi:id="_1Cj8Q9qJEeearpaEPXv9UA"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_1Cj8RdqJEeearpaEPXv9UA"
    nextVersions="_BegL9Q02EeqUVL7sB4m7NA"
    previousVersion="_CzZYdbC8EeamYaqfhG1ZuA"
    name="Header"
    definition="Set of characteristics related to the transfer of the management plan."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_4lU_YY3bEeW32YMP0mBeyw" />
  <messageBuildingBlock
    xmi:id="_1Cj8R9qJEeearpaEPXv9UA"
    nextVersions="_BegL9w02EeqUVL7sB4m7NA"
    previousVersion="_CzZYd7C8EeamYaqfhG1ZuA"
    name="ManagementPlan"
    definition="Sequence of terminal maintenance actions to be performed by a point of interaction (POI)."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MgmtPlan"
    complexType="_shn18dqJEeearpaEPXv9UA" />
  <messageBuildingBlock
    xmi:id="_1Cj8SdqJEeearpaEPXv9UA"
    nextVersions="_BegL-Q02EeqUVL7sB4m7NA"
    previousVersion="_CzZYebC8EeamYaqfhG1ZuA"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="__DJZ4dtZEee9e6xduATmQg" />
  <messageDefinitionIdentifier
    businessArea="catm"
    messageFunctionality="002"
    flavour="001"
    version="07" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.