EHF CV

This specification describes the EHF CV. The document is part of Norwegian Agency for Public and Financial Management (DFØ) standardization work related to electronic commerce.

1. Introduction

Curriculum Vitaes (CV’s) are created in different ways and with different layouts both in procurement processes and other processes where CV’s are used. Contracting Authorities and Economic Operators must relate to different formats when describing skills and competences. This often leads to poor information quality and ambiguity which makes the evaluation of providers and candidates difficult and time consuming.

The purpose of this EHF-CV specification is to define and describe a common format for the Curriculum Vitae (CV) messages to be used in a procurement process. This includes both the tender process in Pre Award and the follow-up of contract information in Post Award.

Europass CV is a specification to be used by employees and job-seekers to register CV-information in a structured way. Europass CV also includes an XML-format which can be used to store and exchange information. EHF-CV is aligned with Europass CV to a certain extent. But since the scope for EHF-CV is to support the procurement process and Europass CV is directed towards job-seeking, they will have different information requirements. As part of the alignment we have used official codelists in EHF-CV when it has been assessed as appropriate.

1.1. Benefits

The main benefit with a standardized CV for both Contracting Authorities and Economic Operators is time saved when processing CV-information. A standardized CV will also enhance the procurement process by ensuring good quality of CV-information.

Benefits for Contracting Authoritites:

A standardized CV can save time and money through easier and faster specification of requirements and criteria
Content can be reused in CV-requests
Parts of the CV-process can be automated and AI may also be used in the process

Benefits for Economic Operators:

A standardized CV can save time and money through easier and faster specification of skills and competences
Content can be reused in CV’s
Parts of the CV-process can be automated and AI may also be used in the process

2. Parties and roles

The table below gives the definitions of the parties and roles involved in the EHF-CV process.

Business partners	Definition
Contracting Authority	The Contracting Authority (CA) is the organization within the government that is responsible for procurement, as well as the individual within that organization who has been delegated this responsibility. Examples of CA roles: Sender of CV-request and Receiver of CV.
Economic Operator	The Economic Operator (EO) is a business or other organisation which supplies goods, works or services within the context of market operations. Examples of EO roles: Sender of CV and Receiver of CV-request.

Business partners

Definition

Contracting Authority

The Contracting Authority (CA) is the organization within the government that is responsible for procurement, as well as the individual within that organization who has been delegated this responsibility.

Examples of CA roles: Sender of CV-request and Receiver of CV.

Economic Operator

The Economic Operator (EO) is a business or other organisation which supplies goods, works or services within the context of market operations.

Examples of EO roles: Sender of CV and Receiver of CV-request.

Role/actor	Definition
Sender of CV-request (cv-req:SenderParty)	The role is carried out by the Contracting authority.
Receiver of CV-request (cv-req:ReceiverParty)	The role is carried out by the Economic operator.
Sender of CV (cv:SenderParty)	The role is carried out by the Economic operator.
Receiver of CV (cv:ReceiverParty)	The role is carried out by the Contracting authority.

Role/actor

Definition

Sender of CV-request (cv-req:SenderParty)

The role is carried out by the Contracting authority.

Receiver of CV-request (cv-req:ReceiverParty)

The role is carried out by the Economic operator.

Sender of CV (cv:SenderParty)

The role is carried out by the Economic operator.

Receiver of CV (cv:ReceiverParty)

The role is carried out by the Contracting authority.

The diagram below shows the roles in the EHF-CV process.

3. Process and Use cases

3.1. EHF-CV in Pre-Award

The following diagram illustrates the use of EHF-CV in a tender process in Pre-Award.

Figure 1. Process diagram

3.1.1. Use case - Tender process

This use case describes a tender process where a Contracting Authority needs several IT-developers to develop the company’s IT-system.

Description

The Contracting Authority needs a developer to develop a web portal and specify criterias to be met. The Economic Operator provides a summary of the candidate’s experiences, academic background, skills, personal skills, language skills, references, interest, and personal information.

Parties involved

Contracting Authority
Economic Operator

Assumptions

The Contracting Authority is able to prepare and send an EHF-CV Request
The Economic Operator is able to receive an EHF-CV Request and to prepare and send an EHF-CV
The Contracting Authority is able to receive an EHF-CV

Flow

The Contracting Authority creates a CV request document with all the necessary requirements and criteria.
The Contracting Authority sends an EHF-CV Request to the Economic Operators.
The Economic Operator colletcs CV-information for the relevant candidates based on the requirements.
The Economic Operator creates an EHF-CV and sends it to the Contracting Authority.
The Contracting Authority receives the EHF-CV.

Result

The Contracting Authority rates EHF-CV’s from several Economic Operators and choose the best candidate based on the requested requirements.

3.2. EHF-CV in Post-Award

The following diagram illustrates the use of EHF-CV in a contract follow-up process in Post-Award.

Figure 2. Process diagram

3.2.1. Use case - Update of CV’s

This use case describes the update of CV-information after the contract is awarded.

Description

The Economic Operator provides an update of the candidate’s skills or experiences. As an example this could be a new certification or a renewal of a certification. The update can be done regulary based on agreements in the contract or when a change has occured that affects the CV.

Parties involved

Contracting Authority
Economic Operator

Assumptions

The Economic Operator is able to prepare and send an EHF-CV
The Contracting Authority is able to receive an EHF-CV

Flow

The Economic Operator creates an EHF-CV with updated CV-information and sends it to the Contracting Authority.
The Contracting Authority receives the EHF-CV with updated information and stores it as part of the contract.

Result

The relevant CV’s are updated based on an EHF-CV sent from the Economic Operator to the Contracting Authority.

4. Descriptions of message content

4.1. Header Information

Information provided in the header of CV and CV request. Issue Time is optional, all other elements are mandatory.

Example of header information in the CV request

<cv-req:CustomizationID>urn:fdc:anskaffelser.no:2019:ehf:cvrequest:1</cv-req:CustomizationID>(1)
<cv-req:ProfileID>urn:fdc:anskaffelser.no:2019:ehf-cv:1</cv-req:ProfileID>(2)
<cv-req:ID>1</cv-req:ID>(3)
<cv-req:RoleDescription>Developer</cv-req:RoleDescription>(4)
<cv-req:IssueDate>2024-02-02</cv-req:IssueDate>(5)
<cv-req:IssueTime>08:30:00</cv-req:IssueTime>(6)

1	CustomizationID identifies the transaction used in the Peppol network.
2	ProfileID identifies the profile used in the Peppol network.
3	ID is a unique identification of the message. UUID or similar.
4	Role description is the role or job title that the CV is requested for.
5	Issue date is the date when the CV-request was sent.
6	Issue time is the time when the CV-request was sent.

Example of a description of header information in a CV

<cv:CustomizationID>urn:fdc:anskaffelser.no:2019:ehf:cv:1</cv:CustomizationID>(1)
<cv:ProfileID>urn:fdc:anskaffelser.no:2019:ehf-cv:1</cv:ProfileID>(2)
<cv:ID>4b2fd73e-f9c8-4465-8e63-4c5edae48057</cv:ID>(3)
<cv:RoleDescription>Developer</cv:RoleDescription>(4)
<cv:IssueDate>2024-02-02</cv:IssueDate>(5)
<cv:IssueTime>08:30:00</cv:IssueTime>(6)

1	CustomizationID identifies the transaction used in the Peppol network.
2	ProfileID identifies the profile used in the Peppol network.
3	ID is a unique identification of the message. UUID or similar.
4	Role description is the role or job title that the CV is submitted for.
5	Issue date is the date when the CV was sent.
6	Issue time is the time when the CV was sent.

4.2. Parties

The following parties/roles may be specified in EHF CV:

4.2.1. Sender (SenderParty)

Sender is the sender of CV-request or CV.

Example of sender in CV-request:

<cv-req:SenderParty>
  <cv-req:Party>
  <cv-req:EndpointID schemeID="0192">987654325</cv-req:EndpointID>(1)
  <cv-req:PartyName>
    <cv-req:Name>Digitaliseringsdirektoratet</cv-req:Name>
  </cv-req:PartyName>
  <cv-req:Contact>
    <cv-req:Name>Ola Nordmann</cv-req:Name>
    <cv-req:Telephone>22224444</cv-req:Telephone>
    <cv-req:ElectronicMail>ola.nordmann@direktorat.no</cv-req:ElectronicMail>
  </cv-req:Contact>
  </cv-req:Party>
</cv-req:SenderParty>

1	schemeID according to codelist Electronic address identifier (EAID)

4.2.2. Receiver (ReceiverParty)

Receiver is the receiver of CV-request or CV.

Example of receiver in CV-request:

<cv-req:ReceiverParty>
  <cv-req:Party>
  <cv-req:EndpointID schemeID="0192">987654325</cv-req:EndpointID>(1)
  <cv-req:PartyName>
    <cv-req:Name>X company</cv-req:Name>
  </cv-req:PartyName>
  <cv-req:Contact>
    <cv-req:Name>John Johnsen</cv-req:Name>
    <cv-req:Telephone>99998888</cv-req:Telephone>
    <cv-req:ElectronicMail>john.johnsen@x.com</cv-req:ElectronicMail>
  </cv-req:Contact>
  </cv-req:Party>
</cv-req:ReceiverParty>

1	schemeID according to codelist Electronic address identifier (EAID)

4.3. Police certificate

Information about a Police certifiate can be specified in CV request and CV. The type of certificate must be according to legal types in the code list Police certificate.

4.3.1. Information specific to CV request

A Contracting Authority can specify the requirement for a Police certificate of a certain type. The Contracting Authority can request that the Police certificate must be valid to a specific date (cv-req:ValidTo).

Example of the request for Police certificate in the CV request

<cv-req:PoliceCertificate>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Type>Begrenset</cv-req:Type>(3)
  <cv-req:ValidTo>2024-12-31</cv-req:ValidTo>(4)
</cv-req:PoliceCertificate>

1	Police certificate identifier.
2	Certificate requirement - indicates whether a candidate needs to fulfill the requirement. According to codelist Requirement code
3	Certificate type according to code list Police certificate
4	The date that the Police certificate must be valid to.

4.3.2. Information specific to CV

Based on the requirement, the Economic Operator must document the candidate’s Police certificate and validity date.

Example of a description of Police certificate in CV as a response to the request in CV request

<cv:PoliceCertificate>
  <cv:ID>1</cv:ID>(1)
  <cv:Type>Ordinær</cv:Type>(2)
  <cv:ValidTo>2025-12-31</cv:ValidTo>(3)
  <cv:Documentation>
    <cv:EmbeddedDocumentBinaryObject mimeCode="application/pdf">YXBwcm92ZWQgZm9vdGJhbGwgcmVmZXJlZSBpbiBub3J3YXk=</cv:EmbeddedDocumentBinaryObject>(4)
  </cv:Documentation>
</cv:PoliceCertificate>

1	Police certificate identifier.
2	Certificate type according to code list Police certificate
3	The date that the Police certificate is valid to.
4	The Police certificate as an embedded attachment.

4.4. Education

Education may be specified in CV request and CV to state the requirements and the level of education of the relevant candidates.

4.4.1. Information specific to CV request

A Contracting Authority can state both an educational requirement and an alternative requirement for the candidate. The alternative requirement is optional, but it might be relevant to accept other educations in some cases. The alternative requirements include the same information elements as the original requirement.

All educations need to be identified uniquely to ensure that the education can be referenced in the CV.

The element cv-req:Requirement shall be used to differentiate between educations that should and must be present. The Economic Operators will only provide qualified candidates to make it easier to do the rating.

Example of the requested education in the CV request

<cv-req:Education>
  <cv-req:ID>2</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Title>Master</cv-req:Title>(3)
  <cv-req:EducationDegree>7</cv-req:EducationDegree>(4)
</cv-req:Education>

1	Education identifier
2	Education requirement - indicate whether a candidate needs to fulfill the educational requirement. According to codelist Requirement code
3	Education title in freetext
4	Education degree according to codelist Education degree

Example of the requested education in the CV request with alternative requirements

<cv-req:Education>
  <cv-req:ID>2</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:Title>Master</cv-req:Title>(3)
  <cv-req:EducationDegree>7</cv-req:EducationDegree>(4)
  <cv-req:AlternativeEducation>(5)
    <cv-req:ID>3</cv-req:ID>
    <cv-req:Requirement>must</cv-req:Requirement>
    <cv-req:Title>bachelor</cv-req:Title>
    <cv-req:EducationDegree>6</cv-req:EducationDegree>
  </cv-req:AlternativeEducation>
</cv-req:Education>

1	Education identifier
2	Education requirement - indicate whether a candidate needs to fulfill the educational requirement. According to codelist Requirement code
3	Education title in freetext
4	Education degree according to codelist Education degree
5	Alternative education requirements

In some cases the Contracting Authorities may accept relevant experiences as a compensation for an education degree. They will then state the type of experience and minimum years of experience. The following example illustrates that. In addition, there is also possible to have alternative educations.

Example of the requested education in the CV request with relevant experience

<cv-req:Education>
  <cv-req:ID>3</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:Title>master</cv-req:Title>(3)
  <cv-req:RelevantExperience>
    <cv-req:Type>3120127</cv-req:Type>(4)
    <cv-req:MinYear>5</cv-req:MinYear>(5)
  </cv-req:RelevantExperience>
</cv-req:Education>

1	Education identifier
2	Education requirement - indicate whether a candidate needs to fulfill the educational requirement. According to codelist Requirement code
3	Education title in freetext
4	Relevant experience type according to codelist Classification of Occupations (Styrk98)
5	Minimum year of relevant experience

4.4.2. Information specific to CV

Based on the educational requirement, the Economic Operator needs to document the candidate’s education.

Example of a description of education in CV as a response to requested education in CV request

<cv:Education>
  <cv:ID>1</cv:ID>(1)
  <cv:Title>Bachelor</cv:Title>(2)
  <cv:EducationDegree>6</cv:EducationDegree>(3)
  <cv:Period>(4)
    <cv:StartDate>2018-08-01</cv:StartDate>
    <cv:EndDate>2021-06-30</cv:EndDate>
  </cv:Period>
  <cv:Documentation>
    <cv:EmbeddedDocumentBinaryObject mimeCode="application/pdf">YmFjaGVsb3IgbnVyc2U=</cv:EmbeddedDocumentBinaryObject>(5)
    <cv:ExternalReference>
      <cv:URI>https://www.vitnemalsportalen.no</cv:URI>(6)
    </cv:ExternalReference>
  </cv:Documentation>
  <cv:Contact>(7)
    <cv:Name>Ola Nordmann</cv:Name>
    <cv:Role>1120131</cv:Role>
    <cv:Telephone>2310114</cv:Telephone>
    <cv:ElectronicMail>ola.nordmann@x.no</cv:ElectronicMail>
  </cv:Contact>
</cv:Education>

1	Education identifier
2	Education name in freetext
3	Education degree according to code list Education degree
4	Education period
5	Embedded document as binary object with `mimeCode`. Use Base64.
6	URI to education document, typically `vitnemalsportalen` in Norway
7	Contact information related to candidate’s education

4.5. Course

The course information group is used to state relevant courses that the candidate has taken. This information is not mandatory, but might be relevant for some assignments.

4.5.1. Information specific to CV request

A Contracting Authority can state a course requirement (main requirement) and an alternative requirement in the CV request. The alternative requirement is optional, but in some cases other similar courses can be accepted. As an example the Contracting Authority can accept other versions of the specific course. Note that the alternative requirements include the same information elements as the original requirement.

All courses need to be identified uniquely to ensure that the course can be referenced in the CV. The element cv-req:Requirement shall be used to differentiate between courses that should and must be present. The Economic Operators will only provide qualified candidates, and this makes it easier to do the rating.

In course requirement, the Contracting Authority can specify which period (cv-req:Period) the candidate must finish the course. This can be a date in the future.

Example of the requested course in the CV request

<cv-req:Course>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Title>macroeconomic</cv-req:Title>(3)
  <cv-req:Period>(4)
    <cv-req:StartDate>2020-01-10</cv-req:StartDate>
    <cv-req:EndDate>2020-05-05</cv-req:EndDate>
  </cv-req:Period>
</cv-req:Course>

1	Course identifier
2	Course requirement - indicate whether a candidate needs to fulfill the course requirement. According to codelist Requirement code
3	Course title
4	Period

Example of the requested course in the CV request with alternative requirement

<cv-req:Course>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:Title>HMS security airport</cv-req:Title>(3)
  <cv-req:VersionID>2.0</cv-req:VersionID>(4)
  <cv-req:Period>(5)
    <cv-req:StartDate>2020-01-10</cv-req:StartDate>
    <cv-req:EndDate>2020-05-05</cv-req:EndDate>
  </cv-req:Period>
  <cv-req:AlternativeCourse>(6)
    <cv-req:ID>1</cv-req:ID>
    <cv-req:Requirement>should</cv-req:Requirement>
    <cv-req:Title>HMS security airport</cv-req:Title>
    <cv-req:VersionID>1.0</cv-req:VersionID>
    <cv-req:Period>
      <cv-req:StartDate>2019-01-10</cv-req:StartDate>
      <cv-req:EndDate>2020-05-05</cv-req:EndDate>
    </cv-req:Period>
  </cv-req:AlternativeCourse>
</cv-req:Course>

1	Course identifier
2	Course requirement - indicate whether a candidate needs to fulfill the course requirement. According to codelist Requirement code
3	Course title
4	Course version
5	Period
6	Alternative course requirement

4.5.2. Information specific to CV

Based on the course requirement, the Economic Operator needs to document the candidate’s courses.

It is possible to state information about the supplier of the course. This might be relevant for some Contracting Authorities, since different suppliers may offer the same course with different content.

Example of a description of course in CV as a response to requested course in CV request

<cv:Course>
  <cv:ID>1</cv:ID>(1)
  <cv:Title>python</cv:Title>(2)
  <cv:Period>(3)
    <cv:StartDate>2019-01-10</cv:StartDate>
    <cv:EndDate>2020-05-05</cv:EndDate>
  </cv:Period>
  <cv:SupplierParty>(4)
    <cv:Party>
    <cv:EndpointID schemeID="0192">123456785</cv:EndpointID>(5)
    <cv:PartyName>
      <cv:Name>X company</cv:Name>(6)
    </cv:PartyName>
    <cv:PostalAddress>
      <cv:Country>
        <cv:IdentificationCode>ES</cv:IdentificationCode>(7)
      </cv:Country>
    </cv:PostalAddress>
    <cv:Contact>
      <cv:ElectronicMail>ola.nordmann@xcompany.no</cv:ElectronicMail>(8)
    </cv:Contact>
      </cv:Party>
  </cv:SupplierParty>
  <cv:Documentation>
    <cv:EmbeddedDocumentBinaryObject mimeCode="application/pdf">cHl0aG9uIGNvdXJzZSB4eXo=</cv:EmbeddedDocumentBinaryObject>(9)
    <cv:ExternalReference>
      <cv:URI>https://www.kurssportalen.no/</cv:URI>(10)
    </cv:ExternalReference>
  </cv:Documentation>
</cv:Course>

1	Course identifier
2	Course title
3	Course period
4	Information about the supplier of the course
5	The supplier’s organisation number. schemeID according to codelist Electronic address identifier (EAID)
6	The legal name of supplier
7	The country where the supplier is registered - expressed as country code from the codelist
8	Contact information of supplier expressed as email address
9	Embedded document as binary object with `mimeCode`. Use Base64.
10	URI to course document

4.6. Certification

The certification information group is used to state relevant certifications that the candidate has taken. If a certification requirement is stated, the candidate must have passed the specified exam/test.

4.6.1. Information specific to CV request

A Contracting Authority can state a certification requirement (main requirement) and an alternative requirement in the CV request. The alternative requirement is optional, but in some cases other similar certifications can be accepted. Note that the alternative requirements include the same information elements as the original requirement.

All certifications need to be identified uniquely to ensure that the certification can be referenced in the CV. The element cv-req:Requirement shall be used to differentiate between courses that should and must be present.

The Contracting Authority can request that the certification must be valid to a specific date (cv-req:ValidTo).

Example of the requested certification for candidate in the CV request

<cv-req:Certification>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Title>archimate</cv-req:Title>(3)
  <cv-req:VersionID>3.0</cv-req:VersionID>(4)
  <cv-req:ValidTo>2025-05-05</cv-req:ValidTo>(5)
</cv-req:Certification>

1	Certification identifier.
2	Certification requirement - indicate whether a candidate needs to fulfill the certification requirement. According to codelist Requirement code
3	Certification title
4	A date the certification is valid to.

Example of the requested certification in the CV request with alternative requirement

<cv-req:Certification>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:Title>Organization leader</cv-req:Title>(3)
  <cv-req:VersionID>3.0</cv-req:VersionID>(4)
  <cv-req:ValidTo>2020-12-01</cv-req:ValidTo>(5)
  <cv-req:AlternativeCertification>(6)
    <cv-req:ID>1</cv-req:ID>
    <cv-req:Requirement>should</cv-req:Requirement>
    <cv-req:Title>Organization leader</cv-req:Title>
    <cv-req:VersionID>2.0</cv-req:VersionID>
    <cv-req:ValidTo>2020-12-01</cv-req:ValidTo>
  </cv-req:AlternativeCertification>
</cv-req:Certification>

1	Certification identifier.
2	Certification requirement - indicate whether a candidate needs to fulfill the certification requirement. According to codelist Requirement code
3	Certification title
4	Certification version.
5	A date the certification must be valid to.
6	Alternative certification requirement.

4.6.2. Information specific to CV

Based on the certification requirement, the Economic Operator needs to document the candidate’s certification.

It is possible to state information about the supplier/issuer of the certification. This might be relevant for some Contracting Authorities, since different suppliers may offer the same certification with different content.

Example of a description of certification in CV as a response to a requested certification in CV request

<cv:Certification>
  <cv:ID>1</cv:ID>(1)
  <cv:Title>archimate</cv:Title>(2)
  <cv:VersionID>3.0</cv:VersionID>(3)
  <cv:ValidTo>2020-05-05</cv:ValidTo>(4)
  <cv:SupplierParty>(5)
    <cv:Party>
    <cv:EndpointID schemeID="0192">123456785</cv:EndpointID>(6)
    <cv:PartyName>
      <cv:Name>U company</cv:Name>(7)
    </cv:PartyName>
    <cv:PostalAddress>
      <cv:Country>
        <cv:IdentificationCode>NO</cv:IdentificationCode>(8)
      </cv:Country>
    </cv:PostalAddress>
    <cv:Contact>
      <cv:ElectronicMail>company@u.no</cv:ElectronicMail>(9)
    </cv:Contact>
    </cv:Party>
  </cv:SupplierParty>
  <cv:Documentation>
    <cv:EmbeddedDocumentBinaryObject mimeCode="application/pdf">YXJjaGltYXRlIGNlcnRpZmljYXRpb24=</cv:EmbeddedDocumentBinaryObject>(10)
    <cv:ExternalReference>
      <cv:URI>https://www.sertifiseringsportalen.no/</cv:URI>(11)
    </cv:ExternalReference>
  </cv:Documentation>
</cv:Certification>

1	Certification identifier.
2	Certification title
3	Certification version.
4	A date certification is valid to.
5	Information about the supplier/issuer of the certification.
6	The suppliers organisation number. schemeID according to codelist Electronic address identifier (EAID)
7	The legal name of the supplier.
8	The country where the supplier is registered - expressed as country code from the codelist.
9	Contact information for the supplier expressed as email address.
10	Embedded document as binary object with `mimeCode`. Use Base64.
11	URI to certification document.

4.7. Language skills

Language skills may be specified in CV request and CV. For certain assignments the language skill may be of great importance.

4.7.1. Information specific to CV request

A Contracting Authority can state both a specific language requirement and an alternative requirement. The alternative requirement is optional, but should be used if an alternative language is accepted. As an example some Norwegian entities use Norwegian as primarily work language but may accept Swedish and Danish. There is also possible to require several languages, for example Norwegian and English. Note that the alternative requirements include the same information elements as the original requirement.

All language skills need to be identified uniquely, to ensure that the language skill can be referenced in the CV. The element cv-req:Requirement shall be used to differentiate between languages skills that should and must be present.

Oral skill and written skill may be provided for each language skill requirement. The skill levels are based on EU global standard. Note that the skill level is a minimum requirement. For example, the Contracting Authority wants a candidate with a B1 oral skill level. A candidate with an oral skill level of C1 is above that level and therefore qualified. Also note that if Scandinavian is set to true, this will overrule the skill requirements between no, sv and da.

Example of the requested language skill in the CV request

<cv-req:LanguageSkills>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Language>no</cv-req:Language>(3)
  <cv-req:Scandinavian>true</cv-req:Scandinavian>(4)
  <cv-req:OralSkill>B1</cv-req:OralSkill>(5)
  <cv-req:WrittenSkill>B1</cv-req:WrittenSkill>(6)
</cv-req:LanguageSkills>

1	Language skill identifier
2	Language skill requirement - indicate whether a candidate needs to fulfill the language requirement. According to codelist Requirement code
3	A specific language according to codelist ISO639 Language code
4	Set to true if the language is no, sv or da
5	Oral skill
6	Written skill

Example of the requested language skill in the CV request with alternative requirements

<cv-req:LanguageSkills>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:Language>no</cv-req:Language>(3)
  <cv-req:Scandinavian>true</cv-req:Scandinavian>(4)
  <cv-req:OralSkill>B1</cv-req:OralSkill>(5)
  <cv-req:WrittenSkill>B1</cv-req:WrittenSkill>(6)
  <cv-req:AlternativeLanguageSkill>(7)
    <cv-req:ID>1</cv-req:ID>
    <cv-req:Requirement>should</cv-req:Requirement>
    <cv-req:Language>en</cv-req:Language>
    <cv-req:OralSkill>A1</cv-req:OralSkill>
    <cv-req:WrittenSkill>A1</cv-req:WrittenSkill>
  </cv-req:AlternativeLanguageSkill>
</cv-req:LanguageSkills>

1	Language skill identifier
2	Language skill requirement - indicate whether a candidate needs to fulfill the language requirement. According to codelist Requirement code
3	A specific language according to codelist ISO639 Language code
4	Set to true if the language is no, sv or da
5	Oral skill according to codelist Language level
6	Written skill according to codelist Language level
7	Alternative language skill requirements

4.7.2. Information specific to CV

Based on the language skill requirements, the Economic Operator needs to document the candidate’s language skills. Oral skill and written skill should be provided for each language. The skill levels must be defined according to the EU global standard codelist.

Example of a description of language skill in CV as a response to requested language skill in CV request

<cv:LanguageSkills>
  <cv:ID>1</cv:ID>(1)
  <cv:Language>no</cv:Language>(2)
  <cv:Scandinavian>true</cv:Scandinavian>(3)
  <cv:OralSkill>C1</cv:OralSkill>(4)
  <cv:WrittenSkill>C1</cv:WrittenSkill>(5)
  <cv:Contact>(6)
    <cv:Name>Ola Nordmann</cv:Name>
    <cv:Role>1210102</cv:Role>
    <cv:Telephone>22221111</cv:Telephone>
    <cv:ElectronicMail>ola.nordmann@bbb.no</cv:ElectronicMail>
  </cv:Contact>
</cv:LanguageSkills>

1	Language skill identifier
2	A specific language according to codelist ISO639 Language code
3	Set to true if the language is no, sv or da
4	Oral skill according to codelist Language level
5	Written skill according to codelist Language level
6	Contact information related to candidate’s language skill

4.8. Project Experience

Project experience describes specific projects that the candidate has been a part of. Note that this is not the same as work experience.

4.8.1. Information specific to CV request

A Contracting Authority can specify a request for a project experience in several ways. For each project experience, there must be an experience type. In some cases it may be relevant to request project experience related to a specific industry, workplace (country) or sector.

The total years of experience can be specified in element cv-req:RequiredTotalExperience. It is also possible to specify a minimum number of years (cv-req:MinimumYearsExperience) and a maximum number of years (cv-req:MaximumYearsExperience). The candidate must fulfill the minimum requirement. Another option is to have either minimum or maximum years of project excperience.

In the CV request, the Contracting Authority can state the requested period for a project experience using element cv-req:Period. This implies that the candidate can only refer to project experience from this period. As an example a Contracting Authority may request information about project experience from the last five years.

The description of experience needs to be provided in element cv-req:ExperienceDescription, where the candidate’s role must be specified in element cv-req:Role. It is also possible to describe the project activities and candidate’s project position percent (e.g. must have worked 100% with the project).

The project value can be stated in element cv-req:ExperienceValue, where the Contracting Authority can specify the candidate’s project participation (normally months), the size of project and the total value of the project.

Example of the requested project experience in the CV request

<cv-req:ProjectExperience>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:ExperienceType>1141101</cv-req:ExperienceType>(3)
  <cv-req:IndustryType>01110</cv-req:IndustryType>(4)
  <cv-req:Workplace>AI</cv-req:Workplace>(5)
  <cv-req:JobSector>private</cv-req:JobSector>(6)
  <cv-req:RequiredTotalExperience>(7)
    <cv-req:MinimumYearsExperience>2</cv-req:MinimumYearsExperience>
    <cv-req:MaximumYearsExperience>5</cv-req:MaximumYearsExperience>
  </cv-req:RequiredTotalExperience>
  <cv-req:Period>(8)
    <cv-req:StartDate>2020-01-19</cv-req:StartDate>
    <cv-req:EndDate>2020-10-02</cv-req:EndDate>
  </cv-req:Period>
  <cv-req:ExperienceDescription>
    <cv-req:PositionPercent>100</cv-req:PositionPercent>(9)
    <cv-req:Role>1210178</cv-req:Role>(10)
    <cv-req:Activities>Must have done financial analysis by using R.</cv-req:Activities>(11)
  </cv-req:ExperienceDescription>
  <cv-req:ExperienceValue>
    <cv-req:ProjectParticipation unitCode="MON">5</cv-req:ProjectParticipation>(12)
    <cv-req:ProjectSize unitCode="MON">5</cv-req:ProjectSize>(13)
    <cv-req:ProjectValue currencyID="NOK">100</cv-req:ProjectValue>(14)
  </cv-req:ExperienceValue>
</cv-req:ProjectExperience>

1	Project experience identifier
2	Project experience requirement - indicate whether a candidate needs to fulfill the project requirement. According to codelist Requirement code
3	Type of project experience according to codelist Classification of Occupations (Styrk98)
4	Type of industry according to codelist Classification of standard industrial classification (NACE)
5	Workplace according to codelist ISO 3166-1:Alpha2 Country codes
6	Job sector (private, public or other)
7	Total year of experience
8	Period for the experience
9	Candidate’s position percent
10	Role in project according to codelist Classification of Occupations (Styrk98)
11	Description of project activities
12	Project participation including unit of measure
13	Total Project size including unit of measure
14	Project value in money. Currency according to code list ISO 4217 Currency codes

Example of the requested project experience in the CV request with alternative requirement

<cv-req:ProjectExperience>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:ExperienceType>2130111</cv-req:ExperienceType>(3)
  <cv-req:IndustryType>63120</cv-req:IndustryType>(4)
  <cv-req:Workplace>CA</cv-req:Workplace>(5)
  <cv-req:JobSector>private</cv-req:JobSector>(6)
  <cv-req:RequiredTotalExperience>(7)
    <cv-req:MinimumYearsExperience>2</cv-req:MinimumYearsExperience>
    <cv-req:MaximumYearsExperience>6</cv-req:MaximumYearsExperience>
  </cv-req:RequiredTotalExperience>
  <cv-req:Period>(8)
    <cv-req:StartDate>2000-01-19</cv-req:StartDate>
    <cv-req:EndDate>2020-10-02</cv-req:EndDate>
  </cv-req:Period>
  <cv-req:ExperienceDescription>
    <cv-req:PositionPercent>100</cv-req:PositionPercent>(9)
    <cv-req:Role>2130110</cv-req:Role>(10)
    <cv-req:Activities>Must coordinate comapnies web-portal.</cv-req:Activities>(11)
  </cv-req:ExperienceDescription>
  <cv-req:ExperienceValue>
    <cv-req:ProjectParticipation unitCode="MON">5</cv-req:ProjectParticipation>(12)
    <cv-req:ProjectSize unitCode="MON">20</cv-req:ProjectSize>(13)
    <cv-req:ProjectValue currencyID="NOK">1500000</cv-req:ProjectValue>(14)
  </cv-req:ExperienceValue>
  <cv-req:AlternativeProjectExperience>(15)
    <cv-req:ID>1</cv-req:ID>
    <cv-req:Requirement>should</cv-req:Requirement>
    <cv-req:ExperienceType>2130111</cv-req:ExperienceType>
    <cv-req:IndustryType>63120</cv-req:IndustryType>
    <cv-req:Workplace>AI</cv-req:Workplace>
    <cv-req:JobSector>private</cv-req:JobSector>
    <cv-req:RequiredTotalExperience>
      <cv-req:MinimumYearsExperience>2</cv-req:MinimumYearsExperience>
      <cv-req:MaximumYearsExperience>6</cv-req:MaximumYearsExperience>
    </cv-req:RequiredTotalExperience>
    <cv-req:Period>
      <cv-req:StartDate>2000-01-19</cv-req:StartDate>
      <cv-req:EndDate>2020-10-02</cv-req:EndDate>
    </cv-req:Period>
    <cv-req:ExperienceDescription>
      <cv-req:PositionPercent>100</cv-req:PositionPercent>
      <cv-req:Role>2130114</cv-req:Role>
      <cv-req:Activities>Developing IT-system.</cv-req:Activities>
    </cv-req:ExperienceDescription>
    <cv-req:ExperienceValue>
      <cv-req:ProjectParticipation unitCode="MON">5</cv-req:ProjectParticipation>
      <cv-req:ProjectSize unitCode="MON">15</cv-req:ProjectSize>
      <cv-req:ProjectValue currencyID="NOK">1500000</cv-req:ProjectValue>
    </cv-req:ExperienceValue>
  </cv-req:AlternativeProjectExperience>
</cv-req:ProjectExperience>

1	Project experience identifier
2	Project experience requirement - indicate whether a candidate needs to fulfill the project requirement. According to codelist Requirement code
3	Type of project experience according to codelist Classification of Occupations (Styrk98)
4	Type of industry according to codelist Classification of standard industrial classification (NACE)
5	Workplace according to code list ISO 3166-1:Alpha2 Country codes
6	Job sector (private, public or other)
7	Total year of experience
8	Period for the experience
9	Candidate’s position percent
10	Role in project according to codelist Classification of Occupations (Styrk98)
11	Description of project activities
12	Project participation including unit of measure
13	Total Project size including unit of measure
14	Project value in money. Currency according to code list ISO 4217 Currency codes
15	Alternative project experience

4.8.2. Information specific to CV

Based on the project experience requirement from CV request, the Economic Operator must document the candidate’s project experience.

Example of a description of project experience in CV as a response to requested project experience in CV request

<cv:ProjectExperience>
  <cv:ID>1</cv:ID>(1)
  <cv:ExperienceType>2130111</cv:ExperienceType>(2)
  <cv:IndustryType>07290</cv:IndustryType>(3)
  <cv:Workplace>AI</cv:Workplace>(4)
  <cv:JobSector>private</cv:JobSector>(5)
  <cv:Company>(6)
    <cv:PartyIdentification>
      <cv:ID schemeID="0192">123456785</cv:ID>
    </cv:PartyIdentification>
    <cv:PartyName>
      <cv:Name>AZ company</cv:Name>
    </cv:PartyName>
  </cv:Company>
  <cv:Period>(7)
    <cv:StartDate>2005-01-01</cv:StartDate>
    <cv:EndDate>2018-12-01</cv:EndDate>
  </cv:Period>
  <cv:ExperienceDescription>
    <cv:PositionPercent>100</cv:PositionPercent>(8)
    <cv:Role>2130111</cv:Role>(9)
    <cv:Activities>Developing web portal for X company.</cv:Activities>(10)
  </cv:ExperienceDescription>
  <cv:ExperienceValue>
    <cv:ProjectParticipation unitCode="MON">5</cv:ProjectParticipation>(11)
    <cv:ProjectSize unitCode="MON">20</cv:ProjectSize>(12)
    <cv:ProjectValue currencyID="NOK">1500000</cv:ProjectValue>(13)
  </cv:ExperienceValue>
  <cv:Contact>(14)
    <cv:Name>Ola Nordmann</cv:Name>
    <cv:Role>2130121</cv:Role>
    <cv:Telephone>22221111</cv:Telephone>
    <cv:ElectronicMail>ola.nordmann@x-company.no</cv:ElectronicMail>
  </cv:Contact>
</cv:ProjectExperience>

1	Project experience identifier
2	Type of project experience according to codelist Classification of Occupations (Styrk98)
3	Type of industry according to codelist Classification of standard industrial classification (NACE)
4	Workplace according to code list ISO 3166-1:Alpha2 Country codes
5	Job sector (private, public or other)
6	Company information
7	Period for the experience
8	Position percent in the project
9	Role in project according to codelist Classification of Occupations (Styrk98)
10	Description of project activities
11	Project participation including unit of measure
12	Total Project size including unit of measure
13	Project value in money. Currency according to code list ISO 4217 Currency codes
14	Project contact person

4.9. Work Experience

Work experience contains information about a candidate’s employment history. This is not the same as project experience.

4.9.1. Information specific to CV request

A Contracting Authority can specify a request for a work experience in several ways. For each work experience a position level can be stated, i.e. employee, middle level manager or manager to illustrate the type of experience a candidate needs for the assignment.

It is also possible to request a work experience specific to a industry or workplace. The job sector can be specified for each work experience in element cv-req:JobSector, e.g. "private".

The minimum total experience can be specified in element cv-req:MinimumYearsExperience. This implies that the candidate must fulfill this requirement and it can be used to differentiate a junior from a senior candidate.

In the CV request, the Contracting Authority can state the requested period for a work experience in element cv-req:Period. This implies that the candidate can only refer to work experience from this period, for example work experience from the last seven years.

The description of experience is provided in element cv-req:WorkExperienceDescription, where the candidate’s position percent must be specified in element cv-req:PositionPercent (e.g. must have worked 100%, full-time, with the assignment). The candidate’s role (cv-req:Role) and the activities performed (cv-req:Activities) may also be described.

Example of the requested work experience in the CV request

<cv-req:WorkExperience>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:PositionLevel>employee</cv-req:PositionLevel>(3)
  <cv-req:IndustryType>01230</cv-req:IndustryType>(4)
  <cv-req:Workplace>AI</cv-req:Workplace>(5)
  <cv-req:JobSector>private</cv-req:JobSector>(6)
  <cv-req:MinimumYearsExperience>5</cv-req:MinimumYearsExperience>(7)
  <cv-req:Period>(8)
    <cv-req:StartDate>2020-01-19</cv-req:StartDate>
    <cv-req:EndDate>2020-10-02</cv-req:EndDate>
  </cv-req:Period>
  <cv-req:WorkExperienceDescription>
    <cv-req:PositionPercent>100</cv-req:PositionPercent>(9)
    <cv-req:Role>1234106</cv-req:Role>(10)
    <cv-req:Activities>Must have done mathemathical analysis by using Python.</cv-req:Activities>(11)
  </cv-req:WorkExperienceDescription>
</cv-req:WorkExperience>

1	Work experience identifier
2	Work experience requirement - indicate whether a candidate needs to fulfill the work experience requirement. According to codelist Requirement code
3	Position level according to codelist Position level
4	Type of industry according to codelist Classification of standard industrial classification (NACE)
5	Workplace according to codelist ISO 3166-1:Alpha2 Country codes
6	Job sector (private, public or other)
7	Minimum total years of experience
8	Period
9	Position percent
10	Role in work experience according to code list Classification of Occupations (Styrk98)
11	Description of work activities

Example of the requested work experience in the CV request with alternative requirement

<cv-req:WorkExperience>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>should</cv-req:Requirement>(2)
  <cv-req:PositionLevel>employee</cv-req:PositionLevel>(3)
  <cv-req:IndustryType>71200</cv-req:IndustryType>(4)
  <cv-req:Workplace>AI</cv-req:Workplace>(5)
  <cv-req:JobSector>private</cv-req:JobSector>(6)
  <cv-req:MinimumYearsExperience>5</cv-req:MinimumYearsExperience>(7)
  <cv-req:Period>(8)
    <cv-req:StartDate>2010-01-19</cv-req:StartDate>
    <cv-req:EndDate>2020-10-02</cv-req:EndDate>
  </cv-req:Period>
  <cv-req:WorkExperienceDescription>
    <cv-req:PositionPercent>100</cv-req:PositionPercent>(9)
    <cv-req:Role>2130161</cv-req:Role>(10)
    <cv-req:Activities>Must have done mathemathical analysis by using Python.</cv-req:Activities>(11)
  </cv-req:WorkExperienceDescription>
  <cv-req:AlternativeWorkExperience>(12)
    <cv-req:ID>1</cv-req:ID>
    <cv-req:Requirement>should</cv-req:Requirement>
    <cv-req:PositionLevel>MiddleLevelManager</cv-req:PositionLevel>
    <cv-req:IndustryType>72190</cv-req:IndustryType>
    <cv-req:Workplace>AI</cv-req:Workplace>
    <cv-req:JobSector>private</cv-req:JobSector>
    <cv-req:MinimumYearsExperience>5</cv-req:MinimumYearsExperience>
    <cv-req:Period>
      <cv-req:StartDate>2010-01-19</cv-req:StartDate>
      <cv-req:EndDate>2020-10-02</cv-req:EndDate>
    </cv-req:Period>
    <cv-req:WorkExperienceDescription>
      <cv-req:PositionPercent>100</cv-req:PositionPercent>
      <cv-req:Role>2130161</cv-req:Role>
      <cv-req:Activities>Must have done mathemathical analysis by using Python.</cv-req:Activities>
    </cv-req:WorkExperienceDescription>
  </cv-req:AlternativeWorkExperience>
</cv-req:WorkExperience>

1	Work experience identifier
2	Work experience requirement - indicate whether a candidate needs to fulfill the work experience requirement. According to codelist Requirement code
3	Position level according to codelist Position level
4	Type of industry according to codelist Classification of standard industrial classification (NACE)
5	Workplace according to codelist ISO 3166-1:Alpha2 Country codes
6	Job sector (private, public or other)
7	Minimum total years of experience
8	Period
9	Position percent
10	Role in work experience according to code list Classification of Occupations (Styrk98)
11	Description of work activities
12	Alternative work experience

4.9.2. Information specific to CV

Based on the work experience requirement, the Economic Operator needs to document the candidate’s work experience.

Example of a description of work in CV as a response to requested work experience in CV request

<cv:WorkExperience>
  <cv:ID>1</cv:ID>(1)
  <cv:PositionLevel>employee</cv:PositionLevel>(2)
  <cv:IndustryType>72110</cv:IndustryType>(3)
  <cv:Workplace>CF</cv:Workplace>(4)
  <cv:JobSector>private</cv:JobSector>(5)
  <cv:Company>(6)
    <cv:PartyIdentification>
      <cv:ID schemeID="0192">123456785</cv:ID>
    </cv:PartyIdentification>
    <cv:PartyName>
      <cv:Name>X company</cv:Name>
    </cv:PartyName>
  </cv:Company>
  <cv:Period>(7)
    <cv:StartDate>2013-05-05</cv:StartDate>
    <cv:EndDate>2017-08-01</cv:EndDate>
  </cv:Period>
  <cv:WorkExperienceDescription>
    <cv:PositionPercent>100</cv:PositionPercent>(8)
    <cv:Role>2130163</cv:Role>(9)
    <cv:Activities>Testing and developing IT-systems in X company.</cv:Activities>(10)
  </cv:WorkExperienceDescription>
  <cv:Contact>(11)
    <cv:Name>Ola Nordmann</cv:Name>
    <cv:Role>1222169</cv:Role>
    <cv:Telephone>22221111</cv:Telephone>
    <cv:ElectronicMail>ola.nordmann@x.no</cv:ElectronicMail>
  </cv:Contact>
</cv:WorkExperience>

1	Work experience identifier
2	Position level according to codelist Position level
3	Type of industry according to codelist Classification of standard industrial classification (NACE)
4	Workplace according to codelist ISO 3166-1:Alpha2 Country codes
5	Job sector (private, public or other)
6	Information about company where experience was gained. The company identifier has schemeID according to codelist Electronic address identifier (EAID)
7	Period for experience
8	Position percent
9	Role in work experience according to code list Classification of Occupations (Styrk98)
10	Description of work activities
11	Contact information in relevant company

4.10. Skills

Skills contains information about candidate’s abilities related to the specific work.

4.10.1. Information specific to CV request

A Contracting Authority can specify a skill requirement and an alternative requirement in the CV request. The alternative requirement is optional, but may be used when different skills can be accepted.

The element cv-req:Requirement shall be used to differentiate between skills that should and must be present.

A description of the relevant skill is provided in cv-req:Type, ref. examples in chapter below.

The Contracting Authority can specify details about the skill practice directly on cv-req:Skills: the last practiced date (cv-req:LastPractice), the skill practice length (cv-req:MinimumLengthPractice - minimum requirement, normally stated as months) and whether the candidate must provide a reference person (cv-req:SkillsReference set to true).

Example of the requested skill in the CV request

<cv-req:Skills>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Type>matlab</cv-req:Type>(3)
  <cv-req:LastPractice>2019-02-02</cv-req:LastPractice>(4)
  <cv-req:MinimumLengthPractice>12</cv-req:MinimumLengthPractice>(5)
  <cv-req:SkillsReference>true</cv-req:SkillsReference>(6)
</cv-req:Skills>

1	Skill identifier
2	Skill requirement - indicate whether a candidate needs to fulfill the skill requirement. According to codelist Requirement code
3	Type of skill
4	Last practice date
5	Length of practice
6	Skills reference to specify the need for a reference person (true or false)

Example of the requested skill in the CV request with alternative requirement

<cv-req:Skills>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Type>java</cv-req:Type>(3)
  <cv-req:LastPractice>2020-03-03</cv-req:LastPractice>(4)
  <cv-req:MinimumLengthPractice unitCode="MON">5</cv-req:MinimumLengthPractice>(5)
  <cv-req:SkillsReference>true</cv-req:SkillsReference>(6)
  <cv-req:AlternativeSkills>(7)
    <cv-req:ID>1</cv-req:ID>
    <cv-req:Requirement>must</cv-req:Requirement>
    <cv-req:Type>java</cv-req:Type>
    <cv-req:VersionID>8</cv-req:VersionID>
    <cv-req:LastPractice>2020-03-03</cv-req:LastPractice>
    <cv-req:MinimumLengthPractice>5</cv-req:MinimumLengthPractice>
    <cv-req:SkillsReference>true</cv-req:SkillsReference>
  </cv-req:AlternativeSkills>
</cv-req:Skills>

1	Skill identifier
2	Skill requirement - indicate whether a candidate needs to fulfill the skill requirement. According to codelist Requirement code
3	Type of skill
4	Last practice date
5	Length of practice
6	Skills reference to specify the need for a reference/contact person (true or false)
7	Alternative skill requirement

4.10.2. Information specific to CV

Based on the skill requirement, the Economic Operator must document the candidate’s skill. The element cv:Contact is used to provide contact information to a reference person.

Example of a description of skill in CV as a response to requested skill in CV request

  <cv:Skills>
    <cv:ID>1</cv:ID>(1)
    <cv:Type>java</cv:Type>(2)
<!--    <cv:VersionID>11</cv:VersionID>-->
    <cv:LastPractice>2020-05-05</cv:LastPractice>(3)
    <cv:MinimumLengthPractice unitCode="MON">5</cv:MinimumLengthPractice>(4)
    <cv:Contact>(5)
      <cv:Name>Ola Nordmann</cv:Name>
      <cv:Role>1223122</cv:Role>
      <cv:Telephone>22221111</cv:Telephone>
      <cv:ElectronicMail>ola.nordmann@x.no</cv:ElectronicMail>
    </cv:Contact>
  </cv:Skills>

1	Skill identifier
2	Type of skill
3	Last practice date
4	Minimum length of practice
5	Contact information to reference person

4.11. Clearance

Jobs within certain departments of the government or private sectors may require that employees have a security clearance.

4.11.1. Information specific to CV request

A Contracting Authority can state a clearance requirement if a person shall work with information graded Confidential or higher.

The element cv-req:Requirement shall be used to state if the clerarance should or must be present.

Contracting Authorities must specify the level of clearance (cv-req:Level) by using codelist clearance level. Note that the clearance level is a minimum requirement, which means candidate with higher level of clearance is qualified.

The Contracting Authority may specify an expiration date (cv-req:ExpirationDate), which defines the time period the clearance needs to be active.

Example of the requested clearance in the CV request

<cv-req:Clearance>
  <cv-req:ID>1</cv-req:ID>(1)
  <cv-req:Requirement>must</cv-req:Requirement>(2)
  <cv-req:Level>CONFIDENTIAL</cv-req:Level>(3)
  <cv-req:ExpirationDate>2030-05-05</cv-req:ExpirationDate>(4)
</cv-req:Clearance>

1	Clearance identifier
2	Clearance requirement - indicate whether a candidate needs to fulfill the clearance requirement. According to codelist Requirement code (chapter 5.5).
3	Clearance level according to codelist Clearance level
4	Expiration date

4.11.2. Information specific to CV

Based on the clearance requirement, the Economic Operator needs to document the candidate’s clearance. The documentation of clearance can be stated as URI (cv:ExternalReference/cv:URI) or embedded document (cv:EmbeddedDocumentBinaryObject).

Example of a description of clearance in CV as a response to requested clearance in CV request

<cv:Clearance>
  <cv:ID>1</cv:ID>(1)
  <cv:Level>CONFIDENTIAL</cv:Level>(2)
  <cv:ExpirationDate>2025-08-08</cv:ExpirationDate>(3)
  <cv:Documentation>
    <cv:EmbeddedDocumentBinaryObject mimeCode="application/pdf">Y2xlYXJhbmNlIGRvY3VtZW50YXRpb24=</cv:EmbeddedDocumentBinaryObject>(4)
    <cv:ExternalReference>
      <cv:URI>https://www.politiet.no/</cv:URI>(5)
    </cv:ExternalReference>
  </cv:Documentation>
</cv:Clearance>

1	Clearance identifier
2	Clearance level according to codelist Clearance level
3	Clearance expiration date
4	Embedded document as binary object with `mimeCode`. Use Base64.
5	URI to clearance documentation

4.12. Personal Information

Personal details about the applicant. Is only used in CV and not in CV request.

Example of a description of personal information in a CV

<cv:PersonalInformation>
  <cv:ID>1</cv:ID>(1)
  <cv:Name>Ola Nordmann</cv:Name>(2)
  <cv:PostalAddress>(3)
    <cv:StreetName>Oslobukta 20</cv:StreetName>
    <cv:AdditionalStreetName>2. building</cv:AdditionalStreetName>
    <cv:CityName>Oslo</cv:CityName>
    <cv:PostalZone>0342</cv:PostalZone>
    <cv:CountryCode>NO</cv:CountryCode>
  </cv:PostalAddress>
  <cv:Contact>(4)
    <cv:Telephone>98989898</cv:Telephone>
    <cv:ElectronicMail>ola.nordmann@xxx.no</cv:ElectronicMail>
  </cv:Contact>
</cv:PersonalInformation>

1	Personal information identifier
2	Personal name
3	Postal address
4	Contact information

4.13. Additional Information

May be used for additional information about the applicant, not provided in other information groups in. Only used in CV, not in CV request.

Give a short title of additional information in element cv:Title and describe the information in element cv:Description. Documentation of the information can be stated as a URI (cv:ExternalReference/cv:URI) and/or embedded document (cv:EmbeddedDocumentBinaryObject).

Example of a description of additional information in a CV

<cv:AdditionalInformation>
  <cv:ID>1</cv:ID>(1)
  <cv:Title>Chairman</cv:Title>(2)
  <cv:Description>Chairman of the lawyers association for five years</cv:Description>(3)
  <cv:Documentation>
    <cv:EmbeddedDocumentBinaryObject mimeCode="application/pdf">YXBwcm92ZWQgZm9vdGJhbGwgcmVmZXJlZSBpbiBub3J3YXk=</cv:EmbeddedDocumentBinaryObject>(4)
    <cv:ExternalReference>
      <cv:URI>https://www.advokatforeningen.no/</cv:URI>(5)
    </cv:ExternalReference>
  </cv:Documentation>
</cv:AdditionalInformation>

1	Identifier
2	Title
3	Description
4	Embedded document as binary object with `mimeCode`. Use Base64.
5	URI to additional information

Appendix A: Profiles and messages

All messages contains ProfileID and CustomizationID. ProfileID identifies what business process a given message is part of, and CustomizationID identifies the kind of message and the rules applied.

Profiles are connected to one business process, and may contain multiple document types. Valid document instances shall contain corresponding ProfileID and CustomizationID.

CustomizationID is a string without spaces. The list below contains spaces in CustomizationID to make them easier to read. Make sure to remove any spaces before use.

A.1. Customization and Profile identifiers

In the table below you will find the values to be used as the specification identifier and the business process type for this profile

Type Element cv:CustomizationID / cv-req:CustomizationID Element cv:ProfileID / cv-req:ProfileID

Type	Element `cv:CustomizationID` / `cv-req:CustomizationID`	Element `cv:ProfileID` / `cv-req:ProfileID`
EHF CV Request	urn:fdc:anskaffelser.no:2019:ehf:cvrequest:1	urn:fdc:anskaffelser.no:2019:ehf-cv:1
EHF CV	urn:fdc:anskaffelser.no:2019:ehf:cv:1	urn:fdc:anskaffelser.no:2019:ehf-cv:1

EHF CV Request

urn:fdc:anskaffelser.no:2019:ehf:cvrequest:1

urn:fdc:anskaffelser.no:2019:ehf-cv:1

EHF CV

urn:fdc:anskaffelser.no:2019:ehf:cv:1

urn:fdc:anskaffelser.no:2019:ehf-cv:1

Appendix B: Semantic datatypes

Semantic data types are used to bridge the gap between the semantic concepts expressed by the information elements and the technical implementation. The semantic data types define the allowed value domain for the content, and any additional information components (attributes) needed in order to ensure its precise interpretation.

B.1. Primitive types

Semantic data type content may be of the following primitive types. These primitive types were taken from {ISO15000}, Annex A.

Primitive type	Definition
Binary	A set of finite-length sequences of binary digits.
Date	Time point representing a calendar day on a time scale consisting of an origin and a succession of calendar {ISO8601}.
Time	Time point representing a time of day on a time scale consisting of an origin and a succession of instants {ISO8601}.
Decimal	A subset of the real numbers, which can be represented by decimal numerals.
String	A finite sequence of characters.

Primitive type

Definition

Binary

A set of finite-length sequences of binary digits.

Date

Time point representing a calendar day on a time scale consisting of an origin and a succession of calendar {ISO8601}.

Time

Time point representing a time of day on a time scale consisting of an origin and a succession of instants {ISO8601}.

Decimal

A subset of the real numbers, which can be represented by decimal numerals.

String

A finite sequence of characters.

B.2. Semantic data types

The different semantic data types are described in the tables below, where various features such as attributes, format, and decimals as well as the basic type are defined for each semantic data type. They are based on {ISO15000}.

When used in an instance document, each data element will contain data. In the below tables this is identified as the “content”. Whenever a business term is used this term shall always have content and therefore the content is always mandatory.

B.2.1. Percentage

Percentages are given as fractions of a hundred (per cent) e.g. the value 34,78 % in percentage terms is given as 34,78.

No restriction on number of decimals for percentages.

Component	Use	Primitive Type	Example
Content	Mandatory	Decimal	34.7812

Component

Use

Primitive Type

Example

Content

Mandatory

Decimal

34.7812

B.2.2. Quantity

Quantities are used to state a number of units such as for items. The code for the Unit of Measure is defined as a separate business term.

No restriction on number of decimals for quantities.

Component	Use	Primitive Type	Example
Content	Mandatory	Decimal	10000.1234

Component

Use

Primitive Type

Example

Content

Mandatory

Decimal

10000.1234

B.2.3. Amount

An amount states a numerical monetary value. The currency of the amount is defined as a separate business term.

Amount is floating up to two fraction digits.

Component	Use	Primitive Type	Example
Content	Mandatory	Decimal	10000.25

Component

Use

Primitive Type

Example

Content

Mandatory

Decimal

10000.25

B.2.4. Numeric

Numeric values state a plain number with no associated unit of measure or currency. Numeric is different from Quantity in that no unit of measure is given, and different from Percentage in that the value is not a fraction of a hundred.

In EHF CV, Numeric is used for counts such as a number of years of experience.

No restriction on number of decimals for numeric values.

Component	Use	Primitive Type	Example
Content	Mandatory	Decimal	5

Component

Use

Primitive Type

Example

Content

Mandatory

Decimal

B.2.5. Code

Codes are used to specify allowed values in elements as well as for lists of options. Code is different from Identifier in that allowed values have standardized meanings that can be known by the recipient.

Codes shall be entered exactly as shown in the selected code list

Component	Use	Primitive Type	Example
Content	Mandatory	String	Abc123

Component

Use

Primitive Type

Example

Content

Mandatory

String

Abc123

B.2.6. Identifier

Identifiers (IDs) are keys that are issued by the sender or recipient of a document or by a third party.

The use of the attributes is specified for each information element.

Component

Use

Primitive Type

Example

Content

Mandatory

String

abc:123-DEF

Scheme identifier

Conditional

String

GLN

Scheme version identifier

Conditional

String

1.0

B.2.7. Date

Dates shall be in accordance to the “Calendar date complete representation” as specified by {ISO8601}, format YYYY-MM-DD.

Dates shall not include timezone information.

Table 1. EN 16931_ Date. Type
Component	Use	Primitive Type	Example
Content	Mandatory	Date	2017-12-01

B.2.8. Time

Times shall be in accordance to the “Complete representation, local time of day” as specified by {ISO8601}, format HH:MM:SS.

Times shall not include timezone information.

Component

Use

Primitive Type

Example

Content

Mandatory

Time

10:30:00

B.2.9. Document Reference

Document Reference Types are identifiers that were assigned to a document or document line.

Table 2. Document Reference. Type
Component	Use	Primitive Type	Example
Content	Mandatory	String	abc:123-DEF

B.2.10. Text

Text is the actual wording of anything written or printed. Line breaks in the text may be present, and any line breaks should be preserved and respected by the receiver’s system

Component

Use

Primitive Type

Example

Content

Mandatory

String

5% allowance when paid within 30 days

B.2.11. Binary objects

Binary objects can be used to describe files which are transmitted together with the business document. Attachments shall be transmitted together with the business document. The binary object has two supplementary components: a Mime Code, which specifies the Mime type of the attachment and a Filename that is provided by (or on behalf of) the sender of the business document.

Component

Use

Primitive Type

Example

Content

Mandatory

Binary

QmFzZTY0IGNvbnRlbnQgZXhhbXBsZQ==

Mime Code

Mandatory

String

image/jpeg

Filename

Mandatory

String

drawing5.jpg

B.2.12. Indicator

Indicators are used to specify the two allowed values, true or false. All elements of datatype Indicator, must have either true or false as their value.

Component

Use

Primitive Type

Example

Content

Mandatory

String

true