InnerWeb
Skip to main content

Supplier answer to the SOW: how to read requirements met in part and variants

The answer to 19 functional requirements marks 18 as met and 1 as partially met, with a device variant. Is that enough for admission? It depends on what that one requirement is and how the variant is written. Below is the method the buyer uses to read such an answer.

18 of 19
functional requirements met in the sample answer
Source: karta
5 m / 10 m
required accuracy inside and outside
Source: karta

Start with the requirements, not with the count of met ones

A result of 18 out of 19 looks good, but the number does not say which requirement was judged partial. Requirements carry different weight: partial compliance with a supporting requirement is different from partial compliance with a core requirement. Before you assess the answer, mark in the SOW which requirements are conditions of admission and which are scored.

In the example discussed, the required accuracies are 5 m inside buildings and 10 m on the outdoor site. These are measurable requirements, so the supplier cannot answer in general terms: each of them is recorded with the measurement method and conditions.

How to read the partially met status

A partial status makes sense only if the supplier describes three things: what exactly is met, what is missing and how the gap will be closed. In the answer discussed the gap concerned a device, and the supplier gave a variant. The buyer checks whether the variant is realistic: whether it has a price, a date and an impact on the other requirements.

Ask three questions: is the variant within the offer price, does it change the accuracy or the range, and does it require the buyer's consent to change the scope? Record the answers in the assessment minutes, not in informal correspondence.

Status of 19 functional requirements

Status of 19 functional requirementsDonut chart: 18 requirements met and 1 partially met with a variant.Met: 18 pcs (94.7%)Partially met: 1 pcs (5.3%)19pcsMet18 pcs (94.7%)Partially met1 pcs (5.3%)
Source: Answer to the functional requirements of a location system (example)

Criteria for accepting a variant

A variant can be accepted if it meets the SOW requirement in full, and differs in the way the result is achieved, not in the result itself. If the variant changes the result, for example lowers accuracy below the threshold, the offer does not meet the requirement and must be assessed as non-compliant.

Use a simple test: after accepting the variant, do all 19 requirements still hold in the sense of the SOW? If yes, the offer may be admitted with a note on the variant in the contract. If not, the buyer requests clarifications or rejects the offer under the tender rules.

  • The variant is described in the offer with its price and date.
  • The required accuracy of 5 m inside and 10 m outside is maintained.
  • The variant does not change the conditions of integration with the plant's systems.
  • The variant note goes into the contract or an annex.

Answer in the same numbering and an equivalent environment

A good practice is to expect the answer in the SOW numbering, which makes offers easier to compare. In another tender the IT security department of a buyer asked 12 questions about the reporting system and expected answers in the same numbering, together with a demonstration environment equivalent to production.

An environment equivalent to production lets you verify the declarations in the answer, not only read them. If the answer contains a partial status, show it during the demo and record the result in the minutes.

Security requirements in the answer

If the SOW or the IT supplier rules contain security requirements, the answer should confirm them explicitly. For example, the requirements of a large platform for IT suppliers include 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 and TLS 1.0 and 1.1, and audits from the last 12 months.

A general assurance is not enough in the assessment: ask for evidence, for example an audit report, a vulnerability management policy or a scan result.

Video

Frequently asked questions

Does 18 out of 19 mean admission?

Not automatically. Admission depends on whether the requirement not fully met is a condition of entry, and whether the variant is realistic and written into the offer.

How do I tell a variant from a change of scope?

A variant changes the way the result is achieved, and the result stays compliant with the SOW. A change of scope lowers the result or adds cost, so it requires the buyer's consent.

Which evidence to request for security requirements?

An audit report from the last 12 months, the vulnerability management policy and a scan result for the requirements indicated.

Sources

We will prepare the answer in SOW numbering

Send us the SOW and we will answer point by point, with a description of the variants, the evidence and an environment to verify.

Let's talk