- Prospective partner accesses the Partner Portal to apply to be a Partner
- Partner-Portal collects information from the Partner
- Information is sufficient to establish account and settlements information and support supplier relationship management (Suppliers) or to support customer relationship management (Developers/Resellers)
- Information is validated and assessed for completeness and consistency
- Optionally, when data has been collected, Partner-portal initiates a Credit Check
- Information collected from partner is utilized to set up partner account
- The Partner account remains in a Pending state until the Operator accepts the Partner
- The prospective Partner then provides information about the purpose of the asset they want to contribute: application, web service, API, content.
- For Engaged Party Role - supplier:
- Partner-Care assesses the types of services the Supplier wants to offer and selects an Agreement Template for the appropriate Business Relationship agreements.
- The Agreement Template is also used to set access privileges for the Supplier.
- For Engaged Party Role - Developers:
- The type of APP and the expected use of services will drive the choice of Agreement Template.
- 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.
- For Engaged Party Role Enterprise :
- The Enterprise also has a set of agreements that have to be signed.
- In the case of the Enterprise, who brings together the appropriate Ecosystem, Operator Sales may assist in this process.
- Enter agreement types from B2B2X partnering guide
- The prospective Partner electronically signs the appropriate Business Relationship agreements.
- Partner agreements are retained
- Partner Agreements are stored electronically and accessible to the Operator Supplier Management via the Partner records
- Operator Supplier Management may need to be notified of the agreement signing for review.
- Operator reviews prospective Partner information and Agreements
- Operator reviews Credit Check Results
- Operator Approves Partner
- The partner is now part of the ecosystem
- Partner-self-care notifies Partner of Approval
- Partner accesses Partner-self-care to establish credentials
- Partner ID is generated and sent to Partner
- Credentials are established for the Partner and retained
- Partner is enabled for further processing
- 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)
- 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
- 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.
- If the Partner is an Enterprise, then the credentials enable the enterprise to submit partner names to ecosystem.
- Partner uses credentials to log in and review catalog information.