Partner portal dashboards for supplier and customers - IBM/intelligence-suite-supply-chain-solutions GitHub Wiki

DRAFT

Overview:

  • Supplier Portal in SCIS will be an additional instance within the customer account
  • Customer will own all supplier portal instances they choose to provision in their account. If they want to enable 10 suppliers, they will provision 10 instances.
  • Customer can assign a supplier admin user to their supplier portal instance (which allows supplier reps to add their own users) or choose to maintain control of users in portal instances -- their choice
  • Each Supplier portal is simply a new "default" instance of SCIS and easily configured (Dashboards, Work Queues, etc) just like customer parent instance
  • The user content in the portal is to be defined by your implementation team -- I expect portals will be a simper UI with fewer dashboards and widgets, and I also assume that each supplier instance will have the same user experience content. (This is configurable of course)
  • Assuming each supplier portal instance uses the same UI content, then setting up a new supplier portal will be as simple as API registering the needed template JSON configurations and data exchange rules
  • Data will be set up to flow (copy) from the customer parent instance to each Supplier portal instance based on easily configurable, API-registered rules
  • (Data can optionally be configured to flow (copy) from the Supplier portal instance to customer parent instance but I will not cover that for now)
  • Usage will be billed as usual -- app points based on data ingested and used across all instances. Assume 2x data usage if all suppliers are onboarded.

Step 1 - Setup and create templates

  1. Create a COS instance for customer (this is a prereq for the whole project anyways)
  2. Gather customer requirements for what specific data they want to share with suppliers
  3. Create Data Import and Data Export rule JSON templates for the desired data set needed for a supplier and save these locally
  4. Gather customer requirements for what features they want on the supplier portals (dashboards, work queues, rules, etc)
  5. Implement these screens in a dev tenant with sample data
  6. Store these Dashboard JSON templates configuration files locally

Step 2 - Onboard a new supplier

(this can all be done by customer admins, but you will want to do initial implementations and write a run book)

  1. Provision a new Supplier Portal (IBM request, 24h now, minutes in future)
  2. API post the Dashboard JSON templates created in step 1
  3. On the customer parent instance, API post the Data Export rule JSON template with the supplier ID in the payload
  4. On the Supplier portal instance, API post the Data Import rule JSON template with the cos instance location from the prior step
  5. Test
  6. Invite supplier users

Sizing

  • Step 1 - Depends on the dashboard content expected. Use the same dev sizing as customer dashboard work. A simple user experience can be developed in a day if the requirements are understood. (Requirements gathering, iteration, and testing will take far longer than actual config of the pages)

  • Step 2 - Several hours. Most time is spent waiting for provisioning, testing, and managing users.