Menu
Sign in Demo

Cross-industry · EPC and system integration

Contract risk in EPC and system integration

EPC contractors and system integrators are responsible for an overall system of their own and bought-in parts: plant, control systems, software, network, operation. Feature of the class: the result only arises from the interplay of several subsystems and suppliers, and responsibility for the interfaces lies with the contractor. This applies to complex IT systems and services as much as to plants.

CLEVER reviews project, licence and service contracts against the seller register of 414 entries. Where CLEVER recognises a licence or service contract, the register shows the entries of that contract type next to the general ones: 16 on licence and software, 20 on services.

Problem · Benefit · Solution

Starting point and solution

Problem
The contractor is responsible for the interplay of several subsystems and suppliers.
Benefit
Main contract and subcontracts reviewed with the same tool, consortium and subcontracting terms per clause; per topic the check whether the subcontract passes on the obligations of the main contract.
Solution in CLEVER
Contract review and risk tableSEEBuy sideENTERPRISE

Contract forms

Contract form
Coverage in the register
EPC and system integration contract
General entries for project contracts, in addition consortium, liability within the consortium, subcontracting and unclear scope.
IT project contract
General entries on acceptance, variations, warranty and liability; in addition warranty period for software, source code escrow, separation of background and foreground IP.
Software licence agreement
Licence metric and indirect access, rights in modifications, open source and SBOM, audit rights with true-up, maintenance fees.
Service and operation contract with SLA
Service level as an obligation of result, service credits as the exclusive remedy, ITIL terms, exit and data return, renewal with price adjustment.
Cloud and SaaS contract from the buyer’s side
Buyer register: 13 entries on software licences, 13 on services and SaaS, among others availability commitment, exit and deletion rules, data processing.

Register topics

Number of entries per topic in the seller and buyer register.

Interfaces, consortium and subcontracting

Consortium with third parties, liability within the consortium, restrictions on subcontracting, flow-down of terms, change of control.

Seller register: 11 entries

Scope and variations

Unclear scope, unilateral changes, pricing mechanism and notice periods for variations, constructive change.

Seller register: 10 entries

Licence and software

Licence metric, modifications, reverse engineering, open source, audit rights, source code escrow, AI in licensed software.

Seller register: 16 entries · Buyer register: 13 entries

Services and service levels

Service levels, service credits, exclusions, remote services, data portability, data processing.

Seller register: 20 entries · Buyer register: 13 entries

Cyber security and data residency

NIS2, Cyber Resilience Act, DORA for ICT services to financial entities, incident notification deadlines, data residency.

Seller register: 17 entries

Intellectual property and data

Assignment and licence, source code escrow, data protection and processing, use of customer data for AI training.

Seller register: 17 entries

Construction contract under German law and public works contracts

Security under section 650f BGB, employer’s security, material price adjustment clause, disruption and construction time, instructions under section 650b BGB, partial acceptance and condition survey, delay penalty in the employer’s terms, design contract, ground conditions in public works contracts.

Seller register: 8 entries · Buyer register: 9 entries
Risk Assessment of a sample contract in CLEVER
Risk Assessment of a sample contract: a finding per clause with its rating, risk as an amount and as a share of the contract value. Invented data.

Features

Package from which the feature is included. Each tier includes the modules of the tier below. Prices

Use cases

Overall system with software

Project contract with licence and service annexes in one case, up to twenty documents with precedence.

Subcontractors and partners

Main contract from the seller’s side, contracts with subcontractors and software partners from the buyer’s side. Customer contract vs supplier contract (main and subcontract) per topic, such as liability cap, warranty, schedule and change procedure: passed on, partly, not passed on or not covered in the supplier contract.

Operation after acceptance

Service and operation contract with service levels: credits, exit and data return rated per clause.

Coverage

Covered are the general entries for project contracts and the contract-type entries on licence and software and on services; on the buyer’s side, on software licences, services and SaaS.

No entries of their own

Distinction

CLEVER assesses the contracts of an overall system clause by clause. Architecture, interface specification and project control stay in the project’s tools; the legal review stays with the legal or contract team.

Effort and coverage

The calculator on the overview works with your own figures: contracts per year, contracts reviewed today, minutes per review and hourly rate. Alongside: experience values from comparable earlier projects.

To the calculator →

Data security and responsibility

The six answers on training, providers, encryption, evidence, misreading and responsibility are on the overview.

To the overview →

Next step

A demonstration on a sample contract from your function, with the contract types you handle most often.

Book a demoStart a trial3 contract reviews free, no payment details

Not legal advice. CLEVER produces draft wording for internal review; your own legal or contract team decides. No legal services within the meaning of the German Legal Services Act (RDG).