InnerWeb
Skip to main content

BHP software supplier risk: a checklist for purchasing and IT

Before signing a contract with a BHP software supplier, purchasing and IT check the SLA, backups, updates, support, data rights and exit rules. Below is a checklist with comments, based on SLA parameters, the architecture model and the security requirements found in tenders.

99.5%
SLA availability in a calendar month
Source: internal card
3-4 days
repair of critical and high vulnerabilities in the platform requirements
Source: internal card

How to use the list

The list serves to compare suppliers by the same criteria. Each point gets a yes, no or partly answer, and for a partly answer add what is missing. Collect answers from every supplier in one template, ideally numbered as in the tender query, because then the comparison takes hours rather than days.

SLA and response to failure

Check the availability rate and response times. In the example SLA contract, system availability is 99.5% per calendar month. For a type A failure the response time is 12 h and repair 8 h from taking up the service; for a type B failure the response is on the next working day.

SLA parameters (availability, response and repair times) are set in the maintenance contract, e.g. 99.5% availability per month. Ask therefore how failure time is counted, who measures it and how breaches are reported. Ask also for a sample monthly availability report and a description of which planned works are excluded from measurement, so you can compare supplier offers on the same terms and avoid a dispute at the first breach. It is worth recording in the contract a contact person on each side and the deadline for handing over the report after the month ends.

Response and repair times for a type A failure

Response and repair times for a type A failureChart: response time 12 hours and repair time 8 hours for a type A failure.02.557.51012.5hResponseResponse: 12 h12RepairRepair: 8 h8
Source: SLA parameters from the sample contract (internal card)

Architecture, backups and data

The architecture model for the IT department has 5 zones, and no inbound ports are opened on the plant network: outbound traffic is limited to HTTPS 443 towards the instance address. Each customer has an isolated instance with its own database and its own mail system. The instance can run in Docker containers on the customer's server, and some environments run on Kubernetes.

Ask about backup frequency, storage location, restore time and whether a restore test is performed. In the on-premise model establish who makes the backup: the customer or the supplier. Also ask about the customer's right to export data in a format that can be loaded outside the supplier's system.

Security and updates

Security requirements for a large IT platform for suppliers include, among others, fixing critical and high vulnerabilities within 3-4 working days, OWASP ASVS level 2, tokens with at least 128 bits of entropy, a ban on RC4, DES, MD5, SHA1, TLS 1.0 and TLS 1.1, and audits from the last 12 months. You can use them as a template in the query.

Check how the supplier announces updates, how it tests them before deployment and whether the plant can influence the date. A good practice is a service window agreed with plant maintenance.

Exit from the contract

Set the exit rules before signing: the period during which data remains available after the contract ends, the export format, deletion of data with confirmation and the cost, if any. A good supplier does not treat these questions as distrust, because it supports the plant's continuity requirements and provides audit evidence.

Checklist

Video

Frequently asked questions

Does a 99.5% SLA mean no interruptions?

No. It means permitted unavailability within a calendar month. Therefore ask about the measurement method and what is excluded from the count.

Where are SLA parameters set?

In the maintenance contract: availability, response and repair times, e.g. 99.5% availability per month.

Where can the instance be placed?

In the EU cloud or on-premise in Docker containers on the customer's server. Some environments run on Kubernetes.

Sources

Let us go through the list with your IT team

We will answer every point in the numbering of your query and attach evidence: SLA parameters, the architecture model and the description of exit.

Let's talk