You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Standards/scs-0007-v2-certification-integrators.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,21 +7,21 @@ replaces:
7
7
- scs-0007-v1-certification-integrators.md
8
8
track: Global
9
9
description: |
10
-
SCS-0007 defines the process and rules on how SCS integrators are certified.
10
+
SCS-0007 defines the process and rules on how to become certified as SCS Integrator.
11
11
---
12
12
13
13
## Introduction
14
14
15
-
The purpose of this document is to describe a concept for how an implementation partner can obtain certification as SCS Integrator. In essence, this certificate is intended to express that an organization has sufficient technical knowledge and experience to provide technical support to companies using SCS.
16
-
This certification is demanding by design, and it may take some time for a company aspiring to become an SCS integrator to reach the requirements. For this scenario, a lesser variant of the certificate, called SCS Incubator, is also defined.
15
+
The purpose of this document is to describe a concept for how an implementation partner (also referred to as an applicant) can obtain certification as SCS Integrator. In essence, this certificate is intended to express that an applicant has sufficient technical knowledge and experience to provide technical support to other organizations using SCS.
16
+
By design, this certification demands to reach a certain score based on a predefined scoring system. As it may take some time for an aspiring applicant to become an SCS Integrator, a lesser variant of the certificate, called SCS Incubator, is also defined which can be achieved with a lower score.
17
17
18
18
## Motivation
19
19
20
-
As an implementation partner, I want to obtain a certificate as _Certified SCS IaaS Integrator_ or _Certified SCS KaaS Integrator_ in order to prove sufficient technical knowledge and experience to provide technical support for SCS.
20
+
As an implementation partner, I want to become certified as SCS Integrator in order to prove sufficient technical knowledge and experience to provide technical support for SCS.
21
21
22
22
## Regulations
23
23
24
-
The certificates are awarded for the period of one year.
24
+
The certificates are awarded for a period of one year based on the predefined scoring system below.
25
25
The certification is done either by the Forum SCS-Standards or an attestation body nominated by the forum.
26
26
27
27
### Certificates
@@ -31,24 +31,26 @@ The certification is done either by the Forum SCS-Standards or an attestation bo
31
31
- Certified SCS IaaS Incubator: aspiring SCS IaaS (Infrastructure as a Service) implementation partner
32
32
- Certified SCS KaaS Incubator: aspiring SCS KaaS (Kubernetes as a Service) implementation partner
33
33
34
-
### Criteria
34
+
### General expectations
35
35
36
-
<!-- Criteria for certification, proof of experience in setting up, operating and supporting SCS-compliant environments.-->
36
+
The general expectation for certification is to provide proof of experience in setting up, operating and supporting SCS-compliant environments.
37
37
38
38
SCS is an open source community project with the goal of enabling digital sovereignty. As such, the commitment and support of this mission SHOULD be recognized and promoted beyond technical competence.
39
39
40
-
The implementation partner SHOULD work towards ensuring that digital sovereignty is implemented in accordance with the SCS definition (Standards and [Mission Statement](https://docs.scs.community/community/mission-statement)). This is expressed in a way that, in addition to the technology used to build environments (not necessarily only SCS environments), knowledge and experience in SCS standards compliance (SCS-compatible IaaS and KaaS) is also available and that environments built by this implementation partner have already been configured in accordance with the standards and are listed on the SCS compliance list.
40
+
The applicant SHOULD work towards ensuring that digital sovereignty is implemented in accordance with the SCS definition (Standards and [Mission Statement](https://docs.scs.community/community/mission-statement)). This is expressed in a way that, in addition to the technology used to build environments (not necessarily only SCS environments), knowledge and experience in SCS standards compliance (SCS-compatible IaaS and KaaS) is also available and that environments built by the applicant have already been configured in accordance with the standards and are listed on the SCS compliance list.
41
41
42
-
The implementation partner SHOULD work towards ensuring that the cloud environments it sets up and/or manages are also officially visible as SCS clouds, thereby strengthening the SCS brand.
42
+
The applicant SHOULD work towards ensuring that the cloud environments it sets up and/or manages are also officially visible as SCS clouds, thereby strengthening the SCS brand.
43
43
44
-
The implementation partner MUST achieve at least FOUR points (for Integrator) or TWO points (for Incubator) according to the following system:
44
+
### Scoring system
45
45
46
-
- two points for each SCS-compliant environment of a third party successfully brought into production in the last 12 months;
46
+
The applicant MUST achieve a total of at least FOUR points to become SCS Integrator or at least TWO points to qualify as SCS Incubator according to the following scoring system:
47
+
48
+
- two points for each SCS-compliant environment of a third party successfully brought into production by the applicant in the last 12 months;
47
49
- two points for each SCS-compliant environment of a third party actively being managed by the applicant for the last 12 months, one point for 6 months;
48
50
- two points for each SCS-compliant public-cloud environment with at least two regions or at least three availability zones being operated by the applicant for the last 12 months, one point for 6 months.
49
51
50
52
Here, an SCS-compliant environment is one that qualifies for [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_Certified SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas), depending on the desired certification.
51
53
52
54
### Attestation
53
55
54
-
The audit for the certification of an implementation partner is carried out by a person appointed by the Forum SCS-Standards. The person will assess and, if necessary, obtain evidence from the implementation partner to be certified as to whether and to what extent the criteria have been met.
56
+
The audit for the certification of an applicant is carried out by the Forum SCS-Standards or an attestation body. It will assess and, if necessary, obtain evidence from the applicant to be able to estimate which score will be achieved in total and how.
0 commit comments