1. Prospective partner accesses the Partner Portal to apply to be a Partner
  2. Partner-Portal collects information from the Partner
  3. Information is sufficient to establish account and settlements information and support supplier relationship management (Suppliers) or to support customer relationship management (Developers/Resellers)
  4. Information is validated and assessed for completeness and consistency
  5. Optionally, when data has been collected, Partner-portal initiates a Credit Check
  6. Information collected from partner is utilized to set up partner account
  7. The Partner account remains in a Pending state until the Operator accepts the Partner
  8. The prospective Partner then provides information about the purpose of the asset they want to contribute: application, web service, API, content.
  9. For Engaged Party Role - supplier:
    1. Partner-Care assesses the types of services the Supplier wants to offer and selects an Agreement Template for the appropriate Business Relationship agreements.
    2. The Agreement Template is also used to set access privileges for the Supplier.
  10. For Engaged Party Role - Developers:
    1. The type of APP and the expected use of services will drive the choice of Agreement Template.
    2. Developers that are sponsored by the Operator must have a special designation that enables them to select special services that apply only to that relationship.
  11. For Engaged Party Role Enterprise :
    1. The Enterprise also has a set of agreements that have to be signed.
    2. In the case of the Enterprise, who brings together the appropriate Ecosystem, Operator Sales may assist in this process.
    3. Enter agreement types from B2B2X partnering guide
  12. The prospective Partner electronically signs the appropriate Business Relationship agreements.
  13. Partner agreements are retained
  14. Partner Agreements are stored electronically and accessible to the Operator Supplier Management via the Partner records
  15. Operator Supplier Management may need to be notified of the agreement signing for review.
  16. Operator reviews prospective Partner information and Agreements
  17. Operator reviews Credit Check Results
  18. Operator Approves Partner
  19. The partner is now part of the ecosystem
  20. Partner-self-care notifies Partner of Approval
  21. Partner accesses Partner-self-care to establish credentials
  22. Partner ID is generated and sent to Partner
  23. Credentials are established for the Partner and retained
  24. Partner is enabled for further processing
  25. If the Partner is a Supplier, then the credentials enable the Supplier to On-Board a Service though the Self-Care capability Or via catalog management API (e.g. stored in catalog with a non-active PLM state)
  26. If the Partner is a Developer, then the credentials enable the Developer to Register an APP through Self-Care or to purchase product offerings through the portal storefront
  27. If the Partner is a Reseller, then the credentials enable access to create a bundled offering or purchase an API with a resulting mash up.
  28. If the Partner is an Enterprise, then the credentials enable the enterprise to submit partner names to ecosystem.
  29. Partner uses credentials to log in and review catalog information.
  • No labels