BUSINESS

Cloud Service

Service features

User-oriented, request-based self-service

Due to the job specificity of the contact center application, prior consulting, offline negotiation, and contracts are subject to prior consulting; after signing a contract, the SaaS Manager of Buttle Information Systems assigns programs for each customer. Then, the customer uses our consulting application service.

Process
  • Connecting to the service portal page
  • Check of and application for service details and quote
  • Consulting and contracting after check by Manager
  • Service use check and contracting
  • Creation of service configuration account
  • Cloud service use
Online
  • 01
    Cloud service
    portal

    Connect to the service portal page.

    Each package is introduced, and the price policies are checked.

    Consult on call infrastructure and legacy I/F handling.

  • 02
    Application for
    cloud service

    Fill out the form to apply for the service according to the price policy and send the form to the manager.

    After the manager checks the form, consulting and contracting are carried out. During this process, requirements and negotiations are underway.

  • 03
    Program
    assignment

    After the contract confirmation, the manager adds a user account and assigns programs of the customer based on the contract details.

    If call infrastructure and legacy I/F handling need to be developed additionally, additional development will commence.

  • 04
    SaaS service
    use

    Customers use the service according to their requested packages and functions.

Multi tenancy
Multi tenancy
Service measurements
Service measurements
Comparison of features by account management
If you move the screen left and right, you can check the table in detail
Category Creation of separate account per customer Customer infrastructure is built in the master account
Infrastructure cost

Because the billing per account is separate, detailed billing can be checked for each infrastructure service

Billing per customer is difficult
(e.g., Network traffic billing is difficult to separate)
Rights management

Strong in account-related security because only the authorized customer uses the service

If the customer wants to access the infrastructure, the rights should be separated by customers

Requires complicated rights separation task

Scalability

Infrastructure should be newly built for each customer

Scalable because the entire VPC bandwidth can be used in a single account

Existing infrastructure can be used (VPC, subnet, etc.), but the scalability is low because multiple customer infrastructure is built in a single account

Monitoring

Because only the customer uses the service, detailed service use is enabled

Some services are impossible to check
(For network services, it is difficult to separate)

Application example

When isolated business workload management is needed, or the development life cycle is different for each account

When a budget request needs to be made separately for each account

When an account needs to be paid with a single payment method

Or when a discount of reservation instances is maximized

processing