Professional Documents
Culture Documents
Use Case - SP1 - Multicustomer - Support
Use Case - SP1 - Multicustomer - Support
For additional detail on the overall customer value proposition for the Service Provider add-on,
see the included set of quick overview slides. Also see the ‘Billing for Managed Assets’ use case
for additional detail on how multi-customer support is used in the billing process.
Customer Role
UID/login name = lrussell
PW = lrussell
First name = Larry
Last name = Russell
Maximo Security Group = MAXEVERYONE, SPCUSTOMER
Start Center = All Users, Customer
1
a. Customers(SP) – is used to define and manage the list of customer being
serviced by the service provider.
b. Customer Agreements(SP) – is used to define and manage pricing and
billing schedules that the customer and service provider have agreed to.
c. Customer Billing(SP) – is used by the service provider to create a bill for
services provided to the customer.
d. Bill Review(SP) – is used by the customer to review/dispute/approve the
bill created and submitted by the service provider.
e. Sales Order(SP) – is used by the service provide to record fees that should
be billed to the customer.
4. Open the Customers application. You can see there are 2 customer records. (UIG,
WGB)
2
b. Look at Assets(SP), filter on all assets associated to customers by selected all
customers in the filter (You can see there are 45 total asset records
w/customer). Note that because ivanit is a Service Provider, he will see all
assets for his customers and all assets which don't yet have a customer
defined.
3
7. What’s important about this customer tag on each record is not only its use as a quick
identifier but it’s also used by the product security framework to control privileges or
permission of customer data.
8. Continue into the next steps of the use case by reviewing the People(SP) record for
ivanit, the logged in user.
10. Open the record and review the Customer Access tab. You can see that IVANIT has
access 2 customers, UIG and WGB.
11. In contrast look at People(SP) record for the UIG customer contact, Larry Russell.
You can see on his record he has limited access to only UIG data.
12. So when we’re logged in as ivanit I pointed out there were 2 customers total in the
system and we looked at assets there were 45 total assets for different customers. If I
now log out and back in as lrussell, the customer for UIG.
13. Log in as lrussell
a. First you’ll see that since Larry is a customer he has a very limited set of actions
available in his start center.
4
b. Review the Assets result set and jump to the assets app and search all
records. You can see Larry only has access to the 30 records for UIG and
has no indication that the other customer asset records even exist in the
system.
14. The Asset(SP) apps is just one simple example, keep in mind that as part of the
Service Provider add-on many of the business objects available are extended to
include this additional customer relationship. I believe all together there are about
40 business objects extended, so all the ticketing and work order applications,
assets and location apps, a few of the platform apps like classifications, domains,
escalations and of course all the Service Provider apps such as customer
agreements and billing, all have the customer attribute so the data can easily be
segmented.
15. Again the value prop with this functionality is the ability of the service provider to
manage multiple customers in a single instance and reducing total cost of
ownership by only having to manage and maintain 1 system for all there
customers.