Skip to main content

Cloud Contracting Models

models that are available in the industry -

 Standard Contract

Standard Contract model contains the most common terms and conditions listed in the agreement. It talks about

• The security and data protection standards followed by the cloud service providers
• Capacity allocation and scalability terms
• Location of the datacentres
• Lock-in period (which talks about how long the client would sign up for)
• Pricing structure and payment terms
• Periodic audits and updates
These are the general terms that would be included in a standard contracting model. This model is also referred to as Click-Through Agreement - as the client just needs to review the contract and sign off with minimal or no changes. Both the client and the service provider know about all the agreement terms prevalent in the industry. Usually, standard contracting model is utilised by the organisation whose cloud requirements are not mission critical or when they do not, intend to move their confidential and core business applications to the cloud.

 Negotiated Contract

As the name indicates, Negotiated Contract talks about specific terms and conditions in the agreement as per the unique requirements of the organisation. Usually, organisations which serve business customers negotiate strict terms and conditions and they would insist the cloud service provider to abide to it. The additional terms that are negotiated include:

  1. • Key Management and Encryption requests
  2. • Specific policies and procedures
  3. • Standard data transmission protocols as per the sector
  4. • API Integration and related set of guidelines
  5. • Contingency measures and action plan
  6. • Administrative roles and responsibilities

Time-bound Contract

This is either a standard contract or a negotiated contract, the whole validity is for a specific period. Say for example, some organisations have internal policies to change vendors every year or once in 3 years etc. This applies for all types of vendors they deal with. This ensures efficiency in services provided and move to the better ones if in case there are issues with existing vendors. This holds true for cloud service providers as well. If the organisation is happy with a specific cloud service provider whom they have trusted their data with, then they would renew it after the time frame in the contract gets over. If they are unhappy or if they found any discrepancies with the existing cloud service provider, then they would change them after a certain period. Some of the multinational corporations are known to levy heavy penalties for their vendors who do not comply with the contracts. The industrial term for such activity is “Contract Deviation”. If the cloud service provider is said to deviate from the contracts, then they might end up paying heavy penalties and in some cases, also face law suits. In such cases, the contract is terminated immediately and the data is moved to other third party service providers.

Comments

Popular posts from this blog

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the ...

Cloud Computing architecture

Cloud computing architecture refers to all components and sub-components that together form the structure of the cloud computing system. This architecture can be divided into three parts for better understanding – front end, back end and middleware. Each part of the cloud architecture has its own set of functionalities and protocols that work together to deliver on-demand services to user-facing hardware as well as software. In general, the architecture is evolved out of large distributed network applications over the last two decades. Hence it supports any system where resources can be pooled and partitioned as required. The general cloud architecture is capable of running multiple software applications running on multiple virtual hardware in multiple locations to efficiently render on-demand services to the users. The users could be using these software applications from their desktop or laptop or mobile or tablets. Usually, whatever the user is looking at – through t...

connection oriented

connection-oriented:- connection-oriented  describes a means of transmitting data in which the devices at the end points use a preliminary  protocol  to establish an end-to-end connection before any data is sent. Connection-oriented protocol service is sometimes called a "reliable" network service, because it guarantees that data will arrive in the proper sequence. Transmission Control Protocol ( TCP ) is a connection-oriented protocol. For connection-oriented communications, each end point must be able to transmit so that it can communicate. The alternative to connection-oriented transmission is the  connection-less  approach, in which data is sent from one end point to another without prior arrangement. Connection-less protocols are usually described as  stateless  because the end points have no protocol-defined way to remember where they are in a "conversation" of message exchanges. Because they can keep track of a conversation, connection-or...

tag