Common use of How to Participate Clause in Contracts

How to Participate. 2.1. In order to participate in FRVT, an Organization must provide the information requested in Section 5 of this Agreement identifying the Responsible Party and the Point of Contact. Organization must also print and sign this Agreement, attach business cards from each of the signing parties, and send it to the location designated in Section 5. Signatures of both the Responsible Party and the Point of Contact are required. 2.1.1. The Responsible Party is an individual with the authority to commit the organization to the terms in this Agreement. 2.1.2. The Point of Contact (POC) is an individual with detailed knowledge of the participating Submission. 2.1.3. In some cases, the Responsible Party and the POC may be the same person. 2.2. Upon receipt of the signed application by the National Institute of Standards and Technology (NIST), the organization will be classified as a “Participant.” NIST must receive this signed application either before or with the algorithm prototypes. Algorithm prototypes (“Submissions”) shall be submitted as pre-compiled software libraries. They may be submitted anytime after February 17, 2017. The application shall be submitted either before or with the first Submission; subsequent Submissions do not require additional applications. 2.3. NIST intends to evaluate all Submissions from all Participants on a first come, first served basis. 2.4. Participant shall provide a submission (“Submission”), conforming to the specifications in the Concept, Evaluation Plan, and API (“Test Plan”) available at xxxxx://xxx.xxxx.xxx/programs-projects/face-recognition-vendor-test-frvt-ongoing A Submission shall include all executable code, validation results, configuration files, documentation, and all other files required by NIST and the Participant to validate and execute the tests specified in the Test Plan. 2.5. The Submission need not be used in a production system or be commercially available. However, the Submission must, at a minimum, be a stable implementation conforming to the Test Plan that NIST has published for FRVT. 2.6. The Submission must be encrypted and signed before transmission to NIST. Instructions for Submission can be found on the FRVT website. Generic encryption instructions can be found in the Image Group’s Encrypting Software for Transmission to NIST document available at xxxxx://xxx.xxxx.xxx/itl/iad/image-group/products-and-services/encrypting-softwaredata-transmission-nist A box for the Participant’s public key fingerprint is included on the Agreement. Submissions that are not signed with the public key fingerprint listed on the Agreement will not be accepted. 2.7. Submissions must be compliant with the Test Plan, NIST test hardware, and NIST test software. Submissions must be delivered to NIST during the submission period given in paragraph 2.2 of this agreement according to the technical specifications given in the Test Plan.

How to Participate. 2.1. In order to participate in FRVTSRSE, an Organization must provide the information requested in Section 5 of this Agreement identifying the Responsible Party and the Point of Contact. Organization must also print and sign this Agreement, attach business cards from each of the signing parties, Agreement and send it to the location designated in Section 5. Signatures of both the Responsible Party and the Point of Contact are required. 2.1.1. The Responsible Party is an individual with the authority to commit the organization Organization to the terms in this Agreement. 2.1.2. The Point of Contact (POC) is an individual with detailed knowledge of the participating Submission. 2.1.3. In some cases, the Responsible Party and the POC may be the same person. 2.2. Upon receipt of the signed application by the National Institute of Standards and Technology (NIST), the organization Organization will be classified as a “Participant.” NIST must receive this signed application either before or with the algorithm prototypes. Algorithm prototypes (“Submissions”) shall be submitted in a containerized form compliant with the NIST test framework as pre-compiled software libraries. They may be submitted anytime after February 17, 2017defined in the Speaker Recognition Sequestered Evaluation Test Plan (“Test Plan”). The application shall be submitted either before or with the first Submission; subsequent Submissions do not require additional applications. 2.3. NIST intends to evaluate all Submissions from all Participants on a first come, first served basis. 2.4. Participant shall provide a submission (“Submission”), conforming to the specifications in the Concept, Evaluation Plan, and API (“Test Plan”) available at xxxxx://xxx.xxxx.xxx/programs-projects/face-recognition-vendor-test-frvt-ongoing . A Submission shall include all executable code, validation results, configuration files, documentation, and all other files required by NIST and the Participant to validate and execute the tests specified in the Test Plan. Datasets that include human data, regardless of whether it is identifiable, should be vetted to ensure they have been appropriately approved or consented for use in research. This should include datasets posted on the internet. 2.5. The Submission need not be used in a production system or be commercially available. However, the Submission must, at a minimum, be a stable implementation conforming to the Test Plan that NIST has published for FRVTSRSE. 2.6. The Submission must be encrypted and signed before transmission to NIST. Instructions for Submission can be found on the FRVT SRSE website. Generic encryption instructions can be found in the Image Group’s Encrypting Software for Transmission to NIST document available at xxxxx://xxx.xxxx.xxx/itl/iad/image-group/products-and-services/encrypting-softwaredata-transmission-nist A box for document. Enter the Participant’s public key fingerprint is included on in the AgreementAgreement below. Submissions that are not signed with the public key fingerprint listed on the Agreement will not be accepted. 2.7. Submissions must be compliant with the Test Plan, NIST test hardware, and NIST test software. Submissions must be delivered to NIST during the submission period given in paragraph 2.2 of this agreement Agreement according to the technical specifications given in the Test Plan. 2.8. To the extent allowable by Federal law, NIST agrees to protect Submissions as business proprietary information by using same degree of care, but no less than a reasonable degree of care, to prevent the unauthorized use, dissemination or publication of the Proprietary Information as NIST uses to protect its own confidential information of a like nature. NIST agrees not to transfer any Submissions to any third party without the prior written permission of the Participant. 2.9. These provisions are consistent with and do not supersede, conflict with, or otherwise alter the employee obligations, rights, or liabilities created by existing statute or Executive order relating to (1) classified information, (2) communications to Congress,

How to Participate. 2.1. In order to participate in FRVTTatt-E, an Organization must provide the information requested in Section 5 of this Agreement identifying the Responsible Party and the Point of Contact. Organization must also print and sign this Agreement, attach business cards from each of the signing parties, and send it to the location designated in Section 5. Signatures of both the Responsible Party and the Point of Contact are required. 2.1.1. The Responsible Party is an individual with the authority to commit the organization to the terms in this Agreement. 2.1.2. The Point of Contact (POC) is an individual with detailed knowledge of the participating Submission. 2.1.30.0.0. In Xx some cases, the Responsible Party and the POC may be the same person. 2.2. Upon receipt of the signed application by the National Institute of Standards and Technology (NIST), the organization will be classified as a “Tentative Evaluation Participant.” NIST must receive this signed application either before or with the algorithm prototypes. Algorithm prototypes (“Submissions”) shall be submitted as pre-compiled software libraries. They may be submitted anytime after February 17during the submission period from December 1, 2016 to September 15, 2017. The application shall is required to be submitted either before or with the first Submissionsoftware library submission; subsequent Submissions submissions do not require additional applications. 2.3. It is the NIST’s desire to select all Tentative Participants as Participants. However, if demand for participation exceeds NIST’s ability to properly evaluate the technology, NIST intends to evaluate all Submissions from all will select Participants on a first come, come - first served basis. 2.4. Participant shall provide a submission (“Submission”), conforming to the specifications as specified in the document Tatt-E: Concept, Evaluation Plan, and API (“Test Plan”) available at xxxxx://xxx.xxxx.xxx/programs-projects/face-recognition-vendor-test-frvt-ongoing xxxxx://xxx.xxxx.xxx/itl/iad/image- group/programsprojects/tattoo/tattoo-recognition-technology-evaluation-tatt-e. A Submission shall include all executable code, validation results, configuration files, documentation, and all other files required by NIST and the Participant to validate and execute the tests specified in the Test Plan. 2.5. The Submission need not be used in a production system or be commercially available. However, the Submission must, at a minimum, be a stable implementation capable of conforming to the Test Plan that NIST has published for FRVT.Tatt-E. 2.6. The Submission must be encrypted and signed before transmission transmitting to NIST. Instructions for Submission can be found on the FRVT Tatt-E website. Generic encryption instructions can be found in the Image Group’s Encrypting Software for Transmission to NIST document available at xxxxx://xxx.xxxx.xxx/itl/iad/image-group/products-and-services/encrypting-softwaredata-transmission-nist xxxxx://xxx.xxxx.xxx/itl/iad/image- group/products-and-services/encrypting-softwaredata-transmission-nist. A box for the Participant’s public key fingerprint is included on the Agreement. Submissions that are not signed with the public key fingerprint listed on the Agreement will not be accepted. 2.7. Submissions must be compliant with the Test Plan, NIST test hardware, and NIST test software. Submissions must be delivered to NIST during the submission period given in paragraph 2.2 of this agreement according to the technical specifications given in the Test Plan.

How to Participate. 2.1. In order to participate in FRVTFRVT MORPH, an Organization must provide the information requested in Section 5 of this Agreement identifying the Responsible Party and the Point of Contact. Organization must also print and sign this Agreement, attach business cards from each of the signing parties, and send it to the location designated in Section 5. Signatures of both the Responsible Party and the Point of Contact are required. 2.1.1. The Responsible Party is an individual with the authority to commit the organization to the terms in this Agreement. 2.1.2. The Point of Contact (POC) is an individual with detailed knowledge of the participating Submission. 2.1.3. In some cases, the Responsible Party and the POC may be the same person. 2.2. Upon receipt of the signed application by the National Institute of Standards and Technology (NIST), the organization will be classified as a “Participant.” NIST must receive this signed application either before or with the algorithm prototypes. Algorithm prototypes (“Submissions”) shall be submitted as pre-compiled software libraries. They may be submitted anytime on or after February 17June 27, 20172018. The application shall be submitted either before or with the first Submission; subsequent Submissions do not require additional applications. 2.3. NIST intends to evaluate all Submissions from all Participants on a first come, first served basis. 2.4. Participant shall provide a submission (“Submission”), conforming to the specifications in the Concept, Evaluation Plan, and API (“Test Plan”) available at xxxxx://xxx.xxxx.xxx/programs-projects/face-recognition-vendor-test-frvt-ongoing xxxxx://xxx.xxxx.xxx/programs-projects/face- recognition-vendor-test-frvt-morph. A Submission shall include all executable code, validation results, configuration files, documentation, and all other files required by NIST and the Participant to validate and execute the tests specified in the Test Plan. 2.5. The Submission need not be used in a production system or be commercially available. However, the Submission must, at a minimum, be a stable implementation conforming to the Test Plan that NIST has published for FRVTFRVT MORPH. 2.6. The Submission must be encrypted and signed before transmission to NIST. Instructions for Submission can be found on the FRVT MORPH website. Generic encryption instructions can be found in the Image Group’s Encrypting Software for Transmission to NIST document available at xxxxx://xxx.xxxx.xxx/itl/iad/image-group/products-and-services/encrypting-softwaredata-transmission-nist A box for the Participant’s public key fingerprint is included on the Agreement. Submissions that are not signed with the public key fingerprint listed on the Agreement will not be accepted. 2.7. Submissions must be compliant with the Test Plan, NIST test hardware, and NIST test software. Submissions must be delivered to NIST during the submission period given in paragraph 2.2 of this agreement according to the technical specifications given in the Test Plan.