| Sr. No. | Trading Partner Management Services | Description |
| 1 | Core Business Process Template or Integration Activities |
| 1.1 | Business Process Template Development | The orchestration of a new end-to-end flow from source to target application. It includes ingestion of source data, trading partner setup and propagation through Cleo Integration Cloud before delivering to the target application. Data transformation happens as a part of this business process where the source data is transformed into the target format based on the business rules contained within a ruleset. This also facilitates error handling and process visibility for the end user. Example: Processing of an inbound Purchase Order or EDI 850 from a trading partner into an ERP like Oracle JD Edwards EnterpriseOne. |
| 2 | Trading Partner Management Services |
| 2.1 | New Trading Partner Onboarding (Includes Connection, unique ruleset and associated activities) |
| 2.1.1 | Network (X12) | Onboarding a new trading partner when all business process templates required for this trading partner, are already created. |
| 2.1.2 | Non-Network (Non-X12 - all others) | Onboarding a new trading partner when all business process templates required for this trading partner, are already created. |
| 2.2 | Existing Trading Partner Configuration Change Fee |
| 2.2.1 | Deployment of Base Configuration (Unique Ruleset) | Deployment of Base Configuration (Unique Ruleset), per unique map, or Unique Map development refers to data transformation from a source format to a target format based on business rules that are unique to a trading partner. A unique map needs to be developed when the Business Process Template already exist, however the Ruleset needs to be modified, the process Route requires modification and additional testing is required. Example: A Business Process Template might already exist for Purchase Orders (EDI 850) but now you want to receive orders from a new trading partner that has its own data specifications to be used. In this case, Cleo can clone the EDI 850 Business Process Template and modify it with reduced effort to accommodate the new trading partner’s specifications. The effort to develop Unique Maps is substantially less than creating a Business Process Template. It includes time for Unit Testing the configuration to validate proper operation. |
| 2.2.2 | Changes to an existing Deployment (Unique Ruleset Change) | Changes to an existing Deployment (Unique Ruleset Change) - or a change to a Unique Map, which effectively is a unique map development refers to data transformation from a source format to a target format based on business rules that are unique to a trading partner. A unique map needs to be developed when the Business Process Template already exist, however the Ruleset needs to be modified, the process Route requires modification and additional testing is required. Example: A Business Process Template might already exist for Purchase Orders (EDI 850) but now you want to receive orders from a new trading partner that has its own data specifications to be used. In this case, Cleo can clone the EDI 850 Business Process Template and modify it with reduced effort to accommodate the new trading partner’s specifications. The effort to develop Unique Maps is substantially less than creating a Business Process Template. It includes time for Unit Testing the configuration to validate proper operation. |
| 2.2.3 | Deployment of Same Base Configuration (Ruleset Reuse) | Deployment of Same Base Configuration (Ruleset Reuse) or Unique Map reuse refers to reusing a Unique Map containing data transformation rules across multiple trading partners. In this case, only the trading partner setup is modified and all the trading partners use the same data transformation Unique Map. Example: Supplier receives orders from one Trading Partner with multiple divisions resulting in one set of maps with multiple ISA IDs. In this instance, the Unique Map is reused. |
| 2.2.4 | Trading Partner Connectivity Setup (New Connection) | Establishing a new connection involves working with the trading partner to gather technical details about the connection, setting up the connection and troubleshooting in case of any issues within data movement. CIC Data Movement refers to creation of connections with different trading partners over a variety of protocols like AS2, SFTP, FTP(s) and data movement to the trading partners through these protocols. A new connection is required in case of a new trading partner on-boarding where a data movement channel does not exist between CIC and the trading partner or if an existing trading partner decides to stand up a new data movement server or change the protocol of communication. Non standard integration like API are not included. While VAN connection setup is included in this scope, Customers may require separate VAN contract/subscription. |
| 2.2.5 | Change to Existing Connection | Changes to an existing connection involve changes to URL/ports, user ID and passwords, PGP keys to sustain the connections in production environment. |
| 2.2.6 | New Partner Mailbox | CIC provides the capability for trading partners or customers to connect and upload or download files using AS2, FTP(s), and SFTP protocols. Users can drop and retrieve files from the inbox/outbox allowing you to support doing business with any trading partner regardless of their integration capability. |
| 2.2.7 | Trading Partner Certificate Management | Partner certificate management (for up to 4 hours) |
| 2.2.8 | Trading Partner EDI Certification per transaction | Trading Partner EDI Certification / Testing (add on) for 1 trading partner connection per transaction |
| 2.2.9 | Cross Reference Table additions / deletions, per unique map | Cross Reference Table additions / deletions for up to 1 cross reference table (modifying existing tables only). Creating new reference table will require a SOW. |
| 3 | Miscellaneous Activities |
| 3.1 | Supplier Enablement Campaign Management | Trading partner communication & tracking. This is in addition to the connection setup when the customer needs Cleo assistance with trading partner communication, certification etc. |
| 3.2 | Self Service Portal Certification Testing per transaction | Validation of individual transactions to ensure they meet predefined requirements using transaction validation where each transaction type (e.g., Orders, Invoice, payments, form submissions, service requests) is tested to confirm correct processing and functional testing. Ensures that each transaction follows the intended workflow without errors or unexpected behavior. |
| 3.3 | Minimal changes task (existing contracts) | A Minimal Changes Task is to perform quick adjustments to Business Process where only the minimalistic necessary modifications are made to achieve a specific goal instead of redesigning the entire process. |
Comments
0 comments
Please sign in to leave a comment.