• Initial Design
  • Relevant Flows
  • Data Requirements
  • Efforts



Architecture

Overall Infrastructure as initially designed by Christian Hoell




Integration Layer Architecture (Light Blue components are required incremental features for this project)


Features Missing:

  1. (Possible Req.) Dynamic Routing by Business Entity.
  2. Custom RSP+ Authentication
  3. ODIS Polling Tasks
  4. Oppotunities API services
    1. Quotes, Contracts, Lead, Cases



Integration Flows


  1. As a DSW User i can create a BP to RSP.
  2. As an RSP "user" I can create/update a BP to DSW.
  3. As a DSW User i can create a Vehicle to RSP.
  4. As an RSP "user" I can create/update a Vehicle to DSW.
  5. As a DSW User, I can monitor the updated Quotes in the "Opportunities" gridlist
    1. pull periodical and automated updates, based on last modified timestamp
  6. As a DSW User, I can monitor the updated (RSP) FS Contracts in the "Opportunities" gridlist
    1. pull periodical and automated updates, based on last modified timestamp)
  7. As a DSW User, I can monitor the updated (RSP) Cases in the "Opportunities" gridlist
    1. pull periodical and automated updates, based on last modified timestamp)




Analysis is pending and is not included for the following flows:

Estimated Efforts

(Integration Team / ODIS Efforts)

The scope of these estimations are limited to the implementation of the nexeccasry infrastructure to connect to RSP/Formel 1 (ie. up to the consumption of the services) and it does not include any potential business logic  implications within the DSW Core Logic or any UI/Gridlist changes.



  1. Custom Authentication: ~1-2PD  (ODIS)
  2. Polling Tasks: ~30-37PD 
    1. Includes RSP Get Implementations: 10-12PD  (ODIS)
    2. RSP to ODIS Transformation Layer:  20-25PD  (ODIS)
  3. Opportunity API: ~19-29PD 
    1. FSContracts: 3-5PD (IL) 
    2. Lead: 2-3PD (IL)
    3. Opportunity:  3-5PD (IL)
    4. Quotes: 2-3PD (IL)
    5. Cases: 4-5PD (IL)
    6. Contracts: 3-4PD (IL)
    7. FS Contracts: 2-3PD (IL)



Miscellaneous

POSTMAN Collections

rsp-crm-vehicle_3.0.1_UAT.ymlrsp-crm-status_1.0.1_UAT.ymlrsp-crm-privacy-consent_2.0.0_UAT.ymlrsp-crm-customer-data_4.0.1_UAT.ymlrsp-crm-async_4.1.0_UAT.yml


  • No labels

1 Comment

  1. Questions: 

    • If an update for a BP/Vehicle is sent to RSP. By when an update to the Mormel 1 DMS is expected?
    • Why are BPs needed to be polled from DMS (how does DMS Create new BPs) since RSP will be the master BP system. 
      • What is in the end of the day the Master System per BP, Vehicles Christian Hoell



You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.