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
Contract forms
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 entriesScope and variations
Unclear scope, unilateral changes, pricing mechanism and notice periods for variations, constructive change.
Seller register: 10 entriesLicence 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 entriesServices and service levels
Service levels, service credits, exclusions, remote services, data portability, data processing.
Seller register: 20 entries · Buyer register: 13 entriesCyber security and data residency
NIS2, Cyber Resilience Act, DORA for ICT services to financial entities, incident notification deadlines, data residency.
Seller register: 17 entriesIntellectual property and data
Assignment and licence, source code escrow, data protection and processing, use of customer data for AI training.
Seller register: 17 entriesConstruction 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
Features
- Contract review and risk table SEEA finding per clause with a traffic light, a rating and rationale, checked against the reference register.
- Counter-proposal SEEAn insertable counter-proposal per finding, in the language of the contract.
- Protection checklist SEEA rule check for missing must-have clauses, such as a liability cap or jurisdiction.
- Materiality in contract currency SEEAmount per clause: minimum, likely, maximum. Only with a recorded contract value; without it a dash appears, not a zero.
- Multi-document and precedence TEAMUp to twenty documents per contract, such as main agreement and annexes, with precedence.
- Risk reduction TEAMA proposed action per finding: what can be done to reduce the risk.
- Versions and second review TEAMSeveral versions and assessment runs of a contract, each dated.
- Delta analysis BUSINESSTwo versions of the same contract, compared clause by clause: what changed since the previous round.
- Buy side ENTERPRISEContracts in which your own company buys, with a register of its own of 124 entries.
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
- EVB-IT and other model contracts of German public IT procurement: no entries of their own.
- Agile delivery models, requirements and functional specifications: 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.
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).