ManagementPlanReplacementV03

catm.002.001.03

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
%% ManagementPlanReplacementV03 recursion level 0 with max 0
ManagementPlanReplacementV03 *-- "1..1" Header4 : Header
ManagementPlanReplacementV03 *-- "1..1" ManagementPlan3 : ManagementPlan
ManagementPlanReplacementV03 *-- "1..1" ContentInformationType9 : 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
%% Header4 recursion level 0 with max 1
class Header4{
    DownloadTransfer IsoTrueFalseIndicator
    FormatVersion IsoMax6Text
    ExchangeIdentification IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header4 *-- "1..1" GenericIdentification35 : InitiatingParty
Header4 *-- "0..1" GenericIdentification35 : RecipientParty
%% GenericIdentification35 recursion level 1 with max 1
class GenericIdentification35{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    ShortName IsoMax35Text
}
%% GenericIdentification35 recursion level 1 with max 1
class GenericIdentification35{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    ShortName IsoMax35Text
}
  

Header4 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
%% ManagementPlan3 recursion level 0 with max 1
ManagementPlan3 *-- "0..1" GenericIdentification35 : POIIdentification
ManagementPlan3 *-- "1..1" GenericIdentification35 : TerminalManagerIdentification
ManagementPlan3 *-- "1..0" TerminalManagementDataSet10 : DataSet
%% GenericIdentification35 recursion level 1 with max 1
class GenericIdentification35{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    ShortName IsoMax35Text
}
%% GenericIdentification35 recursion level 1 with max 1
class GenericIdentification35{
    Identification IsoMax35Text
    Type PartyType5Code
    Issuer PartyType6Code
    ShortName IsoMax35Text
}
%% TerminalManagementDataSet10 recursion level 1 with max 1
class TerminalManagementDataSet10{
    SequenceCounter IsoMax9NumericText
}
TerminalManagementDataSet10 *-- "1..1" DataSetIdentification3 : Identification
TerminalManagementDataSet10 *-- "0..1" ManagementPlanContent3 : Content
  

ManagementPlan3 members

SecurityTrailer building block

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

classDiagram
   direction tb
%% ContentInformationType9 recursion level 0 with max 1
class ContentInformationType9{
    ContentType ContentType1Code
}
ContentInformationType9 *-- "0..1" EnvelopedData3 : EnvelopedData
ContentInformationType9 *-- "0..1" AuthenticatedData3 : AuthenticatedData
ContentInformationType9 *-- "0..1" SignedData3 : SignedData
ContentInformationType9 *-- "0..1" DigestedData3 : DigestedData
%% EnvelopedData3 recursion level 1 with max 1
class EnvelopedData3{
    Version IsoNumber
}
EnvelopedData3 *-- "1..0" IRecipient3Choice : Recipient
EnvelopedData3 *-- "1..1" EncryptedContent2 : EncryptedContent
%% AuthenticatedData3 recursion level 1 with max 1
class AuthenticatedData3{
    Version IsoNumber
    MAC IsoMax35Binary
}
AuthenticatedData3 *-- "1..0" IRecipient3Choice : Recipient
AuthenticatedData3 *-- "1..1" AlgorithmIdentification10 : MACAlgorithm
AuthenticatedData3 *-- "1..1" EncapsulatedContent2 : EncapsulatedContent
%% SignedData3 recursion level 1 with max 1
class SignedData3{
    Version IsoNumber
    Certificate IsoMax3000Binary
}
SignedData3 *-- "1..0" AlgorithmIdentification5 : DigestAlgorithm
SignedData3 *-- "1..1" EncapsulatedContent2 : EncapsulatedContent
SignedData3 *-- "1..0" Signer2 : Signer
%% DigestedData3 recursion level 1 with max 1
class DigestedData3{
    Version IsoNumber
    Digest IsoMax140Text
}
DigestedData3 *-- "1..0" AlgorithmIdentification5 : DigestAlgorithm
DigestedData3 *-- "1..1" EncapsulatedContent2 : EncapsulatedContent
  

ContentInformationType9 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ManagementPlanReplacementV03 --|> IOuterRecord : Implements
    ManagementPlanReplacementV03Document --|> IOuterDocument~ManagementPlanReplacementV03~ : Implements
    class IOuterDocument~ManagementPlanReplacementV03~ {
        ManagementPlanReplacementV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ManagementPlanReplacementV03Document *-- ManagementPlanReplacementV03 : 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.03">
    <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="_sO3hwTWBEeODSIIQsYYKhw"
  nextVersions="_nKPkEWpNEeSR-ZWLvO-1dg"
  previousVersion="_R27DMQvfEeK9Xewg3qiFQA"
  name="ManagementPlanReplacementV03"
  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="_sZSCADWBEeODSIIQsYYKhw"
    type="purpose" />
  <messageBuildingBlock
    xmi:id="_sO3hwzWBEeODSIIQsYYKhw"
    nextVersions="_nKPkFWpNEeSR-ZWLvO-1dg"
    previousVersion="_R27DMwvfEeK9Xewg3qiFQA"
    name="Header"
    definition="Set of characteristics related to the transfer of the management plan."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_K8wSNn1DEeCF8NjrBemJWQ_469587146" />
  <messageBuildingBlock
    xmi:id="_sO3hxTWBEeODSIIQsYYKhw"
    nextVersions="_nKPkF2pNEeSR-ZWLvO-1dg"
    previousVersion="_R27DNwvfEeK9Xewg3qiFQA"
    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="_XO2EkTWBEeODSIIQsYYKhw" />
  <messageBuildingBlock
    xmi:id="_sO3hxzWBEeODSIIQsYYKhw"
    nextVersions="_nKPkGWpNEeSR-ZWLvO-1dg"
    previousVersion="_R27DOwvfEeK9Xewg3qiFQA"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC or a digital signature."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyTrlr"
    complexType="_ZSh2oTScEeOnFuyVSIQZKg" />
  <messageDefinitionIdentifier
    businessArea="catm"
    messageFunctionality="002"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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