For ECL2.0, in combination with its own services / solutions, NTT Com will promote the collaboration of the business with the partners that provide ECL2.0 services to end-user clients.
For the collaboration partners, NTT Com is planning to collaborate with businesses that are deploying the following services.
  • System Integrator to be considered for SI projects, including the procurement of the system infrastructure by the cloud environment, consulting businesses.

  • Entrusted End-user customers’ systems, managed services business, which is providing management services.

  • Utilizing the ECL2.0 as the foundation of its own services, SaaS vendors that are considering the sales of services.

  • Agencies that would like to do the sales mediation for the ECL2.0 service.

Here, we will explain the mechanism to realize collaboration with these operators and the functions to support this.


Please refer to Partner Tutorials ( ) on how to use partner function.

Business Model

In the ECL2.0, two forms of collaboration models are offered as follow.

Reseller Model

Collaboration Form

Partner companies will purchase the ECL2.0 services from NTTCom. The system development and application’s provision, operation and monitoring of the management services, etc are provided with a unique added value by the partner. Resell to the end users a new service/solution that includes ECL2.0 resources.
Services provided by the partners to end-user clients, and the offerings , conditions, fee, etc are determined by the partner.
In this model, System Integrator and managed service providers, SaaS partners will use it.


Contract Form

In this case of the Use contract for ECL2.0, it is generated between NTT Com and partners. Between the partners and the end-user, depending of the partner, there is an own agreement.
In this document, the contract between NTT Com and partner is called parent contract. The contract between the partners and end-user clients is called child contract.
As a parent contract, it is needed to get signed a resale agreement to resell normal ECL2.0 Use contract and ECL2.0.
Sub contracts have terms and conditions, etc. that are determined by the partners. It is between the partners and end-user clients. NTTCom does not intervening directly in this contract.
NTTCom will charge the usage fee of ECL2.0 to the partners on the basis of the parent contract. End-user clients will be charged by the partners.
Partners can create multiple child contract under a single parent contract. In this model, the management function to effectively manage this child Agreements is provided (described later).


Agency Model

Collaboration Form

Partner companies become Agency and introduce about the use of ECL2.0 services to the end-users. If the end-user starts using the ECL2.0 services, NTT Com will pay a fee to the partner company.
For the end-user customers, NTTCom will provide the usual direct sales as well as ECL2.0 service.
In this model, it is assumed to be for sale brokers of IT products, System Integrator and consulting businesses.


Contract Form

The agreement related to the use of ECL2.0 is a direct contract between NTTCom and the end user. The content and the terms and conditions of service that is provided to the end-user has no difference with other user from another NTTCom’s Sales Partner.
An agency agreement with partner companies is engaged separately.



In the distributor business model, all the provision of services to end-user customers is carried out by partners. NTTCom will provide the services to partners.
In the agency model, partners will be asked to implement the proposal of ECL2.0 services to end-user customers, but since the conclusion of the contract will correspond to NTTCom, then as well as general users, NTTCom will make the appropriate end-user management.

(Versus End-user)

Distributor Model

Agency Model

Sales Activity






Contract Management






Accepting applications / opening






Inquiries (Tier1)



Inquiry to NTTCom (escalation)


Conditions of Reseller model

In order to use the reseller model described in the previous chapter, it is necessary to conclude a resale partner agreement of Enterprise Cloud 2.0 service.n this chapter, we will explain the terms and conditions for resale program based on this resale partner agreement.
This model provides cloud infrastructure and various functions and tools for resellers to develop their own cloud service business.


When reselling ECL 2.0, reseller partners may become telecommunications carriers. In the case of using a Japanese region, it may be necessary to notify the Ministry of Internal Affairs and Communications by a telecommunications carrier (Article 16 of the Telecommunications Business Act). For details, please refer to the Ministry of Internal Affairs <> _ homepage. In addition, you may need a telecommunications carrier license etc. in each country of the ECL 2.0 region that you use, so please contact the supervisory authorities of each country as necessary. This notice is for promoting caution about regulation and not for the purpose of legal advice. NTT Communications and its affiliates can not give legal advice.


In this model, the menu that the Reseller can resell to the end user is shown below.







Baremetal Server


Virtual Server


Image Storage





Block Storage






Logical Network


Internet Connectivity



・As of July 1, 2017, we will stop new sales of Firewall (Brocade 5600 vRouter) .
As a successor service, please use Network-based Security menu Managed Firewall .
・Furthermore, customers currently using Firewall (Brocade 5600 vRouter) can continue to use it.
As for details, please refer to Firewall(Brocade 5600 vRouter) .

Load Ballancer


Colocation Inter-Connectivity

Specific conditions in collocation interconnectivity are as follows in the bottom of this table.


Enterprise Cloud 1.0 Inter-Connectivity

The contract name of the connection destination for ECL1.0 must be the same with the partner name.


Enterprise Cloud 2.0 Inter-Connectivity


Amazon Web Services Inter-Connectivity


<Dedicated Hypervisor>




Guest image








Network-based Security


Host-based Security





  SQL Server


  Windows Server Remote Desktop Services SAL








Monitoring Logs


<Platform Service>

  Cloud Foundry



Resale may not be possible in some cases. In that case we will contact you individually from our company.

  WebRTC Platform SkyWay

  Power Systems


  Hybrid Cloud with Microsoft Azure


  Hybrid Cloud with GCP



Rancher(Docker Container Management)

  Global Sever Load Balance

Resale may not be possible in some cases. In that case we will contact you individually from our company.


Specific condition in Colocation Interconnectivity
The Colocation rack to which the ECL2.0 Service connects by Colocation Interconnectivity shall be provided by NTT Communications to the ECL2.0 Reseller. A Colocation Service Agreement must be concluded beforehand.
If management of equipment within the colocation or colocation is performed by the end user, the partner operator agrees to the following matters, and also consents to the end user in advance.
  • If there is a colocation connection application or a failure report, open work / test by a NTTCom consignee employee (hereinafter referred to as “NTTCom employee etc.”) based on the instruction of NTTCom in the colocation rack, and failure occurs It is assumed that the partner company and the end user have agreed that the separation, recovery examination, etc. (hereinafter referred to as “in-rack work”) will be performed.

  • The NTT Communications Service Desk of Colocation Services may take the direct contact to the end user as Work_within_Racks or its related works requires.

  • In the work in the rack or related work, NTTCom employees etc. respond to the end user with NTTCom name.

  • Direct interaction between NTTCom employees or colocation service service desks and end users is limited to the duration of the opening work and repair work. All other services are handled through the window of the partner company, and end users can not contact NTTCom. When working in the rack, the partner company will contact NTTCom workers after obtaining the presence or absence of the end user, the end user representative name, contact information, attendance date and time, meeting place, etc.


Points to remember when resale

In the reseller model, there are some points to remember about the following menu, please check.



VPN Connectivity

Because the “Multi-Cloud Connect (Enterprise Cloud 2.0 connection)” that is an option menu of NTT Com’s VPN Service “Arcstar Universal One” is provided, it is necessary a separately contract with Arcstar Universal One. Please check the term and conditions, etc of Arcstar Universal One.

Datacenter Inter-Connectivity

Because the conection features for NTT Com’s VPN Service “Arcstar Universal One - Network between Data Centers” is provided, it is necessary a separately contract with Arcstar Universal One - Network between Data Centers. Please check the term and conditions, etc of Arcstar Universal One.

Managed options

NTT Com”s managed services is provided as “Global Management One”. It is necessary to do a contract separately for Global Management One. Please check the Terms and Conditions of the Global Management One.


ECL2.0 Resellers shall be compliant to the software licenses in reselling ECL2.0 including the OS, middleware and application licenses provided by ECL2.0 Service, or in running the software developed or procured by ECL2.0 Resellers on ECL2.0 Service.

Provided functions

In the Distributor model, partners are able to create more than one child contract under one parent contract, and provides a variety of management functions for managing this child contract efficiently.
For Partners that use distributor model, the following features are offered. Each function can be operated from GUI and from the API.

Configuration of the child contract

The configuration of the child contract in Distributor model, is described below.
Partners own the parent contract, can create multiple child contracts under the parent contract. By paying out this child contract to end-user customers, end-user clients are available to use ECL2.0.
Partners in the parent contract, can also create a tenant to use itself. End-user customers can create a tenant under each child contract, and can use it as same as the ECL2.0 services in the case of direct sales from the normal NTTCom.
Of course, depending on the type of business of the partner, it is assumed that the end user will not release the authority of the portal GUI or API of the subcontract, such as being provided with the right to use the application on ECL 2.0 resources.


In the next, the child contract management features will introduce the features for managing this child contract efficiently.

Child contract management features

In the child contract management features, it provides the following features:



Contract Management

Creation, search, reference, change, abolition of child contract

Billing Management

Specify the child contract and confirm the fee of the child contract

Tenant Management

Specify the child contract and it is possible to manage the child contract of the tenant (create and delete).
In addition, you can also set the access rights to the tenant. For tenants belonging to the child contract, it is also possible to manage the access rights of the parent contract user.

User Management

Specify the child contract, manage the users affiliated to the child contract (Create / Delete)

Contract group management

For tenants belonging to the child contract, it is also possible to manage the access rights of the parent contract user.

Please refer to `Partner Tutorials <>_ on how to use partner function.

Two Factor Authentication

Partner and Enduser can also select Two Factor Authentication (TFA) when logging in to the portal.

Two Factor Authentication(TFA) is an optional secondary authentication step in addition to the standard user Login and Password authentication. It uses a token, i.e. a mobile phone running an RFC 6238 Time-Based One-Time Password Algorithm (TOTP), as a key.

Suitable smartphone client app for TFA include the following:

  • Google Authenticator (iPhone, Android)

Service Documents

The following NTT Communications standard sales documents are available for ECL2.0 Resellers.



How to refer


proposal tools

Please contact your sales representative.


Our standard Pumphlet

Please contact your sales representative.

Terms and Conditions

Enterprise Cloud Service specific 2.0 Terms and Conditions

Please contact your sales representative.


The documents will be provided in either Japanese or English and can not be specified by the partner company. In addition, we do not customize according to your individual request. Among the provided documents, there may be a description of the service menu that is not provided by the resale provision model because of our sales activities.

Subscriptions Methods

Please contact to the NTT Com’s Sales representative.


Billing for the end-user

In the Distributor Model, the price for the end-user is decided by the partner as one of the components of the partner service. It is billed by the partners.


Distributor Model

(In case of NTTCom direct sales)

Billing source



Fee for End-user

Determined by the partners

Determined by NTTCom

Billing for the Partner

In the reseller model, NTTCom charges partners a total of the ECL 2.0 usage fee for the partner and the end user usage fee.

Operation and Maintenance


In the case of the Distributor Model, the primary corresponding point of contact for the end-user support, it will be set up at the partners.


Distributor Model

(In case of NTTCom direct sales)


Provided by the partners. Support content is determined by the partners.

Offered by NTTCom


NTT Com provides the same support as the direct sales, and provides the support for providing function of the partners.


Also in the case of resale business operator models, please be aware that NTT Com may directly deal with end users if it is unavoidable in an emergency.
In order to do this, you may be asked to present the end user’s name and contact information to the partner company.

Notification settings management

In ECL 2.0, we will perform the following e-mail notification regarding the service.

Email notification category

Contract delegate user
Non-contract user
Notification content
Notice / Release Information
Announcement concerning notice of new menu / function addition etc., specification change etc.
○ (Unchangeable)
Notification on Failures
*For users other than the contract delegate user, we will notify you if you have access rights to the corresponding tenant
Notification on Maintenance
*For users other than the contract delegate user, we will notify you if you have access rights to the corresponding tenant

  • Users can select mails themselves to receive from the above initial state (you can check out mails you do not want to receive)

  • However, the contract representative user can not change the reception of the failure notification

  • An administrative user with user administration authority can manipulate the reception selection of other users

Separately from the above, we may send notification e-mails about contracts and fees to the contact person in charge of the parent contract (person-in-charge e-mail address entered on the online sign-up screen of ECL 2.0 new application).


The partner can also set up not to receive e-mails for child contracts to be managed. If you specify a category that you do not want to receive, the mail selection for that category will not be displayed on the user’s screen of child subscription.

About failure / maintenance notification

In case of outage / maintenance related to tenants belonging to a resellers’ own contract, a notification mail is sent to the Admin User of the contract , and the User who has access permission to the tenant.

In the case of outage / maintenance related to tenants belonging to a sub-contract, a notification mail is sent(CC) to the Admin User of the Resellers’ contract, too. As shown in the figure below.



For each menu, the respectively defined SLA is applied as same as the normal direct sales.