SMC CORE

This is the basic module that contains the following subparts:

Session Makers

Represent the boundary of SMC and their type can either be “Input” that has the function of “listening” to source folders for input files and importing SWIFT messages from these files onto the SMC database; or “Output” that can channel messages to destination files in folders.

Supported Data Transfer Protocols: Windows Credentials, FTP and VB.Net code based protocol.

Parser Engine

Here the messages are browsed and decoded into their basic blocks (Header, Text & Trailer) and copies of the source files are stored in a backup folder structure. The Text part of the message is also internally organized according to supported Message Type Formats (SMC has license specific messages)

Message Type Formats & Field Formats

These designers allow the user to view/build any message type from swift (ISO 7775 or 15022) Multiple message syntax versions are supported.

Business Structures

This defines the “business” metadata part of imported SWIFT messages. Each business structure reflects the pure business service that the user is offering or working with.

SMC MODULES

USER POLICIES

User policies define access permissions based on user profiles. It also defines reporting and search views available to different user groups, offering custom results based on message ownership and user profiles mapping.

NAME-TO-CODE CONVERTOR

This add-on utility performs the automatic naming conversion from Institution Names to their correspo nding BICs – Bank Identifier Codes (Example Field 58D converted to 58A).

DUPLICATES DETECTOR

SMC is equipped with an optional Duplicates Detector module, which automatically detects possible duplicates within incoming SWIFT messages and as well as allows the user to manually confirm these duplicates.

MONITOR VIEW

This module allows for monitoring results, checking on the status of messages, and showing summary data based on Queries defined by the user and in accordance with data ownership.

MAPPING MODULES

All data collected from the SMC Core Module will be filtered for specific messages types defined in the Mapping Modules. Mapping Modules scan through the text block of the messages and extract the fields that will be monitored, filtered upon and stored in data tables that can be accessed by the user’s legacy system. In addition to these fields, the message is stored in its integrity for reference. The data extraction process is fully configurable. Mapping Modules can be reconfigured by the user to account for any changes that might occur on the original SWIFT message format.

Every Mapping Module provides an extension that will add up to the following :

• Source (e.g. Message-type format)
• Destination (e.g. Business structures)
• Mapping Type (e.g. MessageToBusiness)

SMC’s Mapping Module can handle 6 types of Maps:

• MessageToBusiness
• FileDescriptorToBusiness
• MXToBusiness
• BusinessToMessage
• BusinessToFileDescriptor
• BusinessToMX

Commonly used Message Type Mapping Modules include:

• Payments (ISO 7775 compliant messages)


MT 100, 103
MT 200, 201, 202, 203 and 210

 

• Securities (ISO15022 compliant messages)

Receipt/Delivery Instructions: MT540, MT541, MT542, MT543
Receipt/Delivery Confirmations: MT544, MT545, MT546, MT547