Appendix J-11 Product Evaluation Template.docx

Appendix J-11

Version <0.1>

DRAFT

Date: <MM/DD/YYYY>

Equipment type: < >

EXECUTIVE SUMMARY

The <Product Name> was evaluated by the DS/TDB/SDE test and evaluation staff. This product is classified as: Generic Equipment[footnoteRef:1], Standardized Equipment[footnoteRef:2], or cleared American access equipment[footnoteRef:3] [1: Generic Equipment is defined as Technical Security COTS Equipment that is compatible with standardized DS systems or equipment suites.] [2: Standardized Equipment is defined as non-generic technical security equipment needed to meet DS installation and maintenance standardization requirements] [3: Cleared American access equipment is defined as proprietary technical security equipment and systems restricted to those that are crucial to the Department's CI posture, and whose use is restricted to cleared Americans.]

Evaluation Results/Recommendation:

The <Product Name> was found to be ACCEPTABLE / UNACCEPTABLE for BETA TESTING / GENERAL FIELD USE / DOMESTIC USE ONLY.

Discuss <Product Name> in terms of how it meets the requirements set to advance in the evaluation cycle - limit to half page or less.

Comments: List comments or reservations.

If reservations are associated with the product's approval, list as follows The reservations associated with the system are as follows:

· Reservations, in bullet format

Include free-form comments on the general quality and usefulness of product documentation.

S-AQMMA-11-R-0186 Appendix J-11 Department of State Supply Chain Management

PUBLICATION HISTORY

This document can be found on the OpenNet at:

https://intranet.ds.state.sbu/DS/C/ST/FSE/TDB/default.aspx Please refer to the TDB website for the latest version.

Corrections, comments, or questions should be sent to:

Table of Contents

Table of Figures

Introduction

Purpose of the Evaluation Use a clear, concise statement. Ex. This evaluation will test the applicability of the <product> to the previously identified system requirements for <this type of technology>.

The purpose of the Evaluation is to achieve the following:

· Define testing strategies for each area and sub-area to include all the functional and quality (non-functional) requirements.

· Identify testing risks.

· Identify required resources and related information.

· Provide visible confirmation to test-effort stakeholders that adequate consideration has been given to governing the test effort.

References

· System Requirements Specification Documents

· Manufacturer literature

· Other

Product Description <Identify the product being tested by name. Give a short description of the product’s purpose and capabilities.> Include photo.

Product standard features

USE BULLET STATEMENTS.

Project Context and Background [Provide a brief description of the background surrounding the project. Include information such as the key problem being solved and the major benefits of the solution.

Note that where this information is defined sufficiently in other documents, you might simply include a reference to those other documents if appropriate; however, it may save readers of this document time and effort if a limited amount of information is duplicated here: so you should use your judgment. As a general rule, this section should only be about one to three paragraphs in length.]

Test Methods and Evaluation

Describe test activities that address system requirements. The intent is to show that the test plan covers all functionality, performance, and other requirements associated with each design element in the system requirements (SRS) document. The granularity of the list should be detailed enough that each requirement is simple and testable.

Procedures

Specify the step-by-step procedures to accomplish the test. Include test setup, initialization steps, and termination. Also include effectiveness criteria or pass criteria for each test procedure.

Data recording

This section describes the method used for recording test results and other information about the testing.

System Requirements / Product Specifications Table A system requirements / product specifications table is used to link the product testing procedures to the requirements recorded in the system requirements specification (SRS) document. It is an essential part of the evaluation documentation for all projects. It should be possible to test the product’s features against each of the system requirements as listed in the table below.

Indicate whether the product’s specifications Meets / Does Not Meet the requirements specification as described in the SRS. Where the requirement does not apply, use N/A.

Refer to the test data, Section 6 as needed; otherwise, refer to manufacturer’s materials or indicate other standards references, (e.g. IEEE standards).

Insert photos as needed.

Requirements / Specifications Table

(Meets / Does Not Meet Requirement)

Size

Weight

Power Consumption

Storage Capacity

Buffer Size

Data and Content Constraints

Hardware Constraints

Software Constraints

Personnel Constraints

Governmental Standards

Industry Standards

International Standards

Purchasing Constraints

Pre-deployment warehousing issues

Shipping

Import/Export Restrictions, Certifications, etc.

Production Environment Constraints

Decommissioning

Regulatory Issues

Hazardous Materials Issues

Controlled/Secure Material Handling

Parts

Ease of maintenance

Downtime (MTTR)

Manufacturer customer support

Operator training

Supervisor training

Maintenance training

Diplomatic Security Training Center (DSTC)

Warranty Timing (start and length)

Warranty Coverage

Warranty stipulations, certifications

Commissioning

Availability during Lifecycle

Parts

Software/Firmware revisions

Updated Training and Serviceability Materials

Transportability during lifetime and transit issues

Disposal

Maintenance and repair

Training

User manuals

DS-Specific Modifications

The following modifications have been made to the standard <Product name> to bring it into accordance with the needs of the Department of State:

· List modifications in bullet format

OR

No modifications were made to the <Product name. The product fits the needs of the Department of State as is.

Include photos / diagrams as needed.

Test Data

Include test data results, either numerical or pass / fail.

Evaluation Results

Evaluation Results/Recommendation:

The Product Name was found to be ACCEPTABLE / UNACCEPTBLE for BETA TESTING / GENERAL FIELD USE / DOMESTIC USE ONLY.

Appendix A Manufacturer Data

Toll Free:

Local Point of Contact or Representative:

Contract Data State Dept. BPA TDB GSA Contract Logistics

CMMS Maximo Item number:

NOTE: If the product is NOT approved, then there is no need for an item number.

Cost GSA DS cost of the <Product name> is $

S-AQMMA-11-R-0186 Appendix J-11 Department of State Supply Chain Management

<Month date, year>

UNCLASSIFIED

ACTION MEMORANDUM FOR DS/ST/FSE, MR. MICHAEL J. BARELA

FROM: DS/FSE/TDB – Warren Garrett

SUBJECT: <Product name> Evaluation Results Decision

Recommendation:

That you authorize DS/FSE/TDB, to move to the next phase of the <product name> evaluation flow, pilot project testing.

Approve_________________ Disapprove_________________

Summary:

The <product name> has been evaluated in the lab and found to be ACCEPTABLE as a(n) <equipment type>, TDB evaluation dated <month date, year>. The system is recommended for pilot project testing by the Technology Development Branch (DS/FSE/TDB) test and evaluation staff in coordination with ESO/ESC staff at the selected test site(s). If chosen to move forward, a pilot project plan document will be generated.

image1.jpeg image2.png image3.png