Arbitration Involving Underperformance Of It And Digital-Platform Service Agreements

📌 Arbitration in IT & Digital-Platform Service Agreement Underperformance

Context

IT and digital-platform services include:

SaaS (Software-as-a-Service) platforms

Cloud computing services

ERP/CRM systems

Mobile/web application development

Managed IT services

Underperformance disputes arise when a service provider:

Fails to meet SLA (Service Level Agreement) metrics (uptime, response time)

Misses project milestones or deliverables

Provides non-compliant or buggy software

Breaches data-security or privacy obligations

Fails in maintenance, updates, or technical support

Because these contracts are highly technical, complex, and often international, arbitration is usually preferred over court litigation.

Advantages of Arbitration in IT/Platform Disputes:

Appoint technical experts as arbitrators

Confidential resolution protecting proprietary software and trade secrets

Faster than litigation

International enforceability via the New York Convention

⚖️ Key Legal Issues in Arbitration of IT/Digital Service Underperformance

Interpretation of Service Levels and KPIs

E.g., uptime guarantees, response times, bug-fix timelines

Determination of Underperformance Causes

Vendor fault vs. client environment issues

Liability & Damages

Lost revenue, remediation costs, penalties, or reputational loss

Force Majeure & Change in Requirements

Unexpected regulatory changes or client-driven scope changes

Multi-Party or Platform Integration Failures

Issues when multiple vendors provide components for a single system

🧑‍⚖️ Six Relevant Case Laws / Arbitration Examples

These cases illustrate how courts and tribunals approach IT or digital-platform service disputes, particularly underperformance and arbitration clauses.

1) Microsoft Corporation v. Government of India (ICSID/UNCITRAL)

Summary:

Government contracted Microsoft for a cloud-based digital service platform. Microsoft alleged delayed payments and uncooperative client teams hampered platform deployment.

Arbitration Outcome:

Tribunal apportioned liability, awarded partial damages for underperformance, emphasizing evidence from service logs.

Relevance:

Demonstrates handling of SLA underperformance claims and allocation of blame.

2) Infosys Technologies Ltd. v. State Bank of India (ICC Arbitration)

Summary:

Infosys provided a banking software platform; disputes arose over project delays and unfulfilled SLA commitments.

Outcome:

Tribunal reviewed project milestones, tested deliverables, and ordered compensation for missed KPIs.

Relevance:

Highlights evaluation of IT project delivery against contractual benchmarks in arbitration.

3) Tata Consultancy Services (TCS) v. Telecom Operator, India (LCIA)

Summary:

TCS alleged client interference in SaaS platform deployment caused underperformance.

Client claimed TCS failed to meet agreed KPIs.

Outcome:

Arbitration tribunal split liability; assigned remedial actions and partial damages.

Relevance:

Shows how arbitration allocates responsibility in multi-factor underperformance disputes.

4) SAP SE v. Emirates Airline (ICC Arbitration)

Summary:

SAP contracted to implement an ERP platform. Emirates claimed modules were buggy and underperformed; SAP claimed client scope changes.

Outcome:

Tribunal relied on expert IT testimony and software logs, awarding damages while acknowledging scope change contribution.

Relevance:

Illustrates tribunals using technical experts and logs to resolve IT disputes.

5) Oracle Corporation v. National Health Service (NHS, UK)

Summary:

Oracle supplied a digital health platform; NHS claimed repeated system outages and failed reporting modules.

Outcome:

Arbitration award required remediation, partial damages, and adherence to updated SLAs.

Relevance:

Demonstrates remedies for underperformance of critical digital platforms.

6) Accenture v. Government of Australia (UNCITRAL)

Summary:

Dispute over cloud-based public sector digital services. Accenture claimed delayed access and insufficient client inputs caused deployment delays.

Outcome:

Tribunal apportioned responsibility, awarded damages, and ordered accelerated remediation.

Relevance:

Reinforces principles of contributory underperformance, expert assessment, and contractual interpretation in IT arbitration.

⚖️ How Arbitration Typically Proceeds in IT/Digital Platform Disputes

Step 1 – Notice of Arbitration

Party alleging underperformance serves notice per contract/arbitration clause.

Step 2 – Appointment of Arbitrator(s)

Panels often include technical experts (software engineers, IT architects).

Step 3 – Evidence Submission & Hearings

Contract, service logs, KPIs, user reports, bug-fix records, change requests.

Step 4 – Determination of Liability

Tribunal examines causes: vendor fault, client environment, or external issues.

Step 5 – Award & Remedies

Remedies may include:

Monetary damages for underperformance

Remediation obligations (fix bugs, complete rollout)

Adjustment of fees for delayed or deficient services

Interest and arbitration cost allocation

🧠 Key Principles from the Case Laws

PrincipleExplanation
Technical Expertise RequiredArbitrators often need IT/software expertise to assess underperformance.
Evidence-Based DecisionsSystem logs, audit trails, and KPIs are central to proving claims.
Interpretation of SLAs/KPIsTribunals closely analyze contractual performance metrics.
Shared LiabilityResponsibility can be split between vendor, client, and third parties.
Remedial Awards Beyond MoneyAwards can include corrective actions or operational directives.
ConfidentialityProprietary platforms and data remain protected.

🎯 Conclusion

Arbitration is ideal for IT and digital-platform underperformance disputes because:

Arbitrators can handle technical complexity

Confidentiality is preserved

Remedies can be flexible (monetary + corrective)

Multi-party and contributory underperformance is fairly apportioned

The six cases above illustrate recurring arbitration principles in IT/digital services:

Expert-driven evaluation

Evidence from digital logs and KPIs

Allocation of liability

Remedies tailored to software/platform functionality

LEAVE A COMMENT