Standards Structure
- Devishree Nath (Unlicensed)
- Martin Eland
Standards Structure
Standards will each have the content detailed in the table below.
ID | Each Standard has a unique identifier composed of one letter followed by a number. The letter "S" indicates a Standard. The number is arbitrary and does not have any additional meaning such as priority, sequence or inter-relationships. This allows for the identification of Standards in a consistent manner. |
Version | Each Standard has a version number. Each Standard can change independently and its version number will change accordingly. Version numbers are subject to change depending on the nature of the change (e.g. major, minor, patch). There is no relationship between the version numbers of different Standards. |
Type | Categorises as a Standard and, where applicable defines the type of Standard:
|
Status | Each Standard will have one of five statuses:
|
Effective Date | Those Standards that are mandated under the Catalogue Agreement will have an Effective Date by which Suppliers must comply with the Standard.  Suppliers will need to have achieved compliance against all Effective Standards (see Status above) in order to onboard on to the Catalogue. There may be other Standards that Suppliers need to achieve compliance with as part of the Framework Agreement in order to be awarded a place on a Framework. |
Structure of Standards
Requirement ID | Each requirement within a Standard will have a unique ID so it can be recognised during compliance |
Requirement Text | The description of each requirement within a Standard that will be used to determine compliance of a Solution with the Standard |
Requirement Level | Each requirement within a Standard will have a level as defined in RFC 2119.1 |
Â