Common Contracts
6 similar Operational Level Agreement contracts
EGI.eu UMD Software provisioning infrastructure OPERATIONAL LEVEL AGREEMENTOperational Level Agreement • May 19th, 2017
EGI.eu UMD Software provisioning infrastructure OPERATIONAL LEVEL AGREEMENTOperational Level Agreement • April 19th, 2016
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
EGI.eu UMD Software provisioning infrastructure OPERATIONAL LEVEL AGREEMENTOperational Level Agreement • April 19th, 2016
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
EGI VO OPERATIONAL LEVEL AGREEMENTOperational Level Agreement • November 24th, 2015
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
EGI.eu UMD Software provisioning infrastructure OPERATIONAL LEVEL AGREEMENTOperational Level Agreement • November 24th, 2015
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
EGI.eu UMD Software provisioning infrastructure OPERATIONAL LEVEL AGREEMENTOperational Level Agreement • November 24th, 2015
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
