Attach_0001_ADMC-3_SOW_FINAL_(26July_16).pdf

Army Desktop and Mobile Computing

(ADMC-3)

Statement of Work (SOW)

26 July 2016

Army Desktop and Mobile Computing

(ADMC-3)

Statement of Work (SOW)

1.0 Introduction

The U.S. Army Computer Hardware, Enterprise Software and Solutions (CHESS) in coordination with the Army Contracting Command – Rock Island (ACC-RI), requires contracts to support the Government’s worldwide requirements for commercial-off-the-shelf (COTS) Information Technology (IT) equipment in accordance with the definition under FAR

2.101. These contracts will be awarded to a set of lowest price technically acceptable for the items identified. The suite of awarded contracts shall serve as an overarching procurement vehicle for the Army Consolidated Buy (CB). The contracts shall also allow the DoD to modify or develop new service centric programs in an effort to enhance configuration management of IT and leverage buying power of IT products.

1.1 Scope

This Statement of Work (SOW) defines the requirements for desktop computers, integrated desktop computers, workstations, notebooks, tablets, slates, electronic displays, thin clients, ultra-thin client, printers and multifunction devices and warranty. The ordering period for equipment under this contract will be a five year base period, with 1 five year option period.

The contractor shall provide and warranty IT equipment on a worldwide basis. Equipment provided under this contract shall be new. Used or refurbished equipment is not acceptable.

Both original equipment manufacturer (OEM) and extended warranty shall be provided. In order to keep pace with changes in technology, the Government may issue Engineering Change Requests (ECRs) outlining new requirements. The contractor may also propose new technologies and if approved by the Government will issue an ECR to all contract holders for the addition of items during the normal technology refresh period. As Army policy allows the product scope may include commodity items such as mobile devices with integrated cellular and 802.11 wireless connection, devices with operating systems other than the Army Golden Master (AGM), wearable computing devices, wall mounted displays, and touch screen displays. Paragraph 1.1.1 through 1.1.11 are definitions as developed by the Environmental Protection Agency (EPA) and supersede any commercial or industry use of the terms.

1.1.1 Desktop Computers

A desktop computer is defined by the Environmental Protection Agency (EPA) as a computer whose main unit is designed to be located in a permanent location, often on a desk or on the floor. Desktop computers are not designed for portability and are designed for use with an external display, keyboard, and mouse. Desktop computers are intended for a broad range of home and office applications. Desktop Computers shall also include computer components that directly support the these platforms (e.g., various processors, random access memory (RAM), hard disk drives, solid state drives, optical drives, video cards, mice, keyboards, input devices, network interface controllers, multimedia devices, smart card readers, interface adapter cards and various warranty options). Golden Master (AGM), wearable computing devices, wall mounted displays, and touch screen displays.

1.1.2 Integrated Desktop Computers

The EPA goes on to further define an Integrated Desktop Computers as a desktop computer in which the computing hardware and display are integrated into a single housing, and which is connected to ac mains power through a single cable. Integrated desktop computers come in one of two possible forms: (1) a system where the display and computer are physically combined into a single unit; or (2) a system packaged as a single system where the display is separate but is connected to the main chassis by a dc power cord and both the computer and display are powered from a single power supply. As a subset of desktop computers, Integrated Desktop Computers are typically designed to provide similar functionality as Desktop systems. Integrated computers shall also include computer components that directly support these platforms (e.g., various processors, random access memory (RAM), hard disk drives, solid state drives, optical drives, video cards, mice, keyboards, input devices, network interface controllers, multimedia devices, smart card readers, interface adapter cards and various warranty options).

1.1.3 Workstations

A workstation is defined by the EPA as a high-performance, single-user computer typically used for graphics, CAD, software development, financial and scientific applications among other compute intensive tasks. Workstations covered by this specification

A. are marketed as a workstation;

B. provide mean time between failures (MTBF) of at least 15,000 hours (based on either Bellcore TR-NWT-000332, issue 6, 12/97 or field collected data); and C. support error-correcting code (ECC) and/or buffered memory. In addition, a workstation meets three or more of the following criteria:

a. Provide supplemental power support for high-end graphics (e.g., PCI-E 6-pin 12V supplemental power feed);

b. Wired for greater than x4 PCI-E on the motherboard in addition to the graphics slot(s) and/or PCI-X support;

c. Do not provide support for Uniform Memory Access (UMA) graphics;

d. Provide 5 or more PCI, PCI-E, or PCI-X slots;

e. Provide multi-processor support for 2 or more processors (shall support physically separate processor packages/sockets, i.e., requirement cannot be met with support for a single multi core processor); and/or

f. Qualification by 2 or more Independent Software Vendor (ISV) product certifications; these certifications can be in process, but shall be completed within 3 months of qualification.

Workstations shall also include computer components that directly support these platforms (e.g., various processors, random access memory (RAM), hard disk drives, solid state drives, optical drives, video cards, mice, keyboards, input devices, network interface controllers, multimedia devices, smart card readers, interface adapter cards and various warranty options).

1.1.4 Electronic Display

An electronic displays (also referred to as monitors) is defined by the EPA as a commercially-available product with a display screen and associated electronics, often encased in a single housing, that as its primary function displays visual information from

(1) a computer, workstation or server via one or more inputs (e.g., VGA, DVI, HDMI, IEEE 1394), (2) a USB flash drive, (3) a memory card, or (4) a wireless Internet connection.

Monitors shall also include cables, connectors to attach the display to the computer and various warranty options.

1.1.5 Notebooks

A notebooks is defined by the EPA as a computer designed specifically for portability and to be operated for extended periods of time both with and without a direct connection to an AC mains power source. Notebook computers include an integrated display and are capable of being powered by an integrated battery or other portable power source. In addition, most notebooks use an external power supply and have an integrated keyboard and pointing device. Notebook computers are typically designed to provide similar functionality to desktops, including operation of software similar in functionality as that used in desktops.

Notebooks shall also include computer components that directly support these platforms (e.g., various processors, random access memory (RAM), hard disk drives, solid state drives, optical drives, video cards, docking stations, port replicators, mice, keyboards, input devices, network interface controllers, wireless network interfaces, multimedia devices, smart card readers, interface adapter cards and various warranty options).

1.1.6 Slate

The EPA goes on to further define a computer is a Slate Computing Device if it has all of the following characteristics:

1. either lacking a physical keyboard or with a detachable physical keyboard;

2. relying solely on touchscreen input;

3. having solely a wireless network connection (e.g., Wi-Fi, 3G); and

4. primarily powered from an internal battery (with connection to the mains for charging, not primary powering of the device).

Slates shall also include computer components that directly support the these platforms (e.g., various processors, random access memory (RAM), hard disk drives, solid state drives, optical drives, docking stations, port replicators, mice, keyboards, input devices, network interface controllers, wireless network interfaces, smart card readers, and various warranty options).

1.1.7 Thin Client

The EPA defines a Thin Client as: an independently-powered computer that relies on a connection to remote computing resources (e.g., computer server, remote workstation) to obtain primary functionality. Main computing functions (e.g., program execution, data storage, interaction with other Internet resources) are provided by the remote computing resources. Thin Clients covered by this specification are (1) limited to devices with no rotational storage media integral to the computer and (2) designed for use in a permanent location (e.g. on a desk) and not for portability.

1.1.8 Ultra-Thin Client

The EPA goes on further to define an ultra-thin client as: a computer with lesser local resources than a standard Thin Client that sends raw mouse and keyboard input to a remote computing resource and receives back raw video from the remote computing resource. Ultra-thin clients cannot interface with multiple devices simultaneously nor run windowed remote applications due to the lack of a user-discernible client operating system on the device (i.e., beneath firmware, user inaccessible).

1.1.9 Printer

A printers is defined by the EPA as a product whose primary function is to generate hard-copy output from electronic input. A printer is capable of receiving information from single-user or networked computers, or other input devices (e.g., digital cameras). This definition is intended to cover products that are marketed as printers, and printers that can be field-upgraded to meet the definition of an MFD. Printers shall also include network interface controllers, wireless network interfaces, cables, connectors to attach the printer to the computer and various warranty option.

1.1.10 Multifunction Device (MFD)

A multifunction devices is defined by EPA as a product that performs two or more of the core functions of a Printer, Scanner, Copier, or Fax Machine. An MFD may have a physically integrated form factor, or it may consist of a combination of functionally integrated components. MFD copy functionality is considered to be distinct from single-sheet convenience copying functionality sometimes offered by fax machines. This definition includes products marketed as MFDs, and “multi-function products” (MFPs). Multifunction

Device shall also include network interface controllers, wireless network interfaces, cables and connectors to attach the printer to the computer.

1.2 General Requirements

1.2.1 Operating System Licensing

Vendors are responsible for providing the appropriate Microsoft Windows OEM licenses for each computing device offered to include all desktop computers, all workstations, all notebook computers, all slate computers, and thin client computers. The government will furnish the Army Golden Master (AGM), which is a securely configured operating system and a collection of applications which addresses Army requirements and are covered by an enterprise license.

1.2.2 Army Golden Master (AGM)

The Army Golden Master is a securely configured operating system and a collection of applications which addresses Army requirements and are covered by an enterprise license. There a currently three separate versions of the AGM each supporting either Microsoft Windows 7 SP1 Enterprise 64bit, Microsoft Windows 8.1 Enterprise 64bit, or

Microsoft Windows 10 Enterprise 64bit operating systems. Each AGM also supports the following list of applications:

– Internet Explorer

– Microsoft Office Professional

– Adobe Acrobat Reader

– Microsoft Visio Viewer

– McAfee Anti-Virus client

– ActivIdentity ActivClient

– Microsoft Media Player

– Microsoft System Center Configuration Manager (SCCM) client agent

– Axway Desktop Validator

– SUN JAVA Runtime Environment (J2SE)

– Software to manage TPM (Provided by vendor)

– Driver Package (Provided by vendor in a format easily used for automated image deployment using SCCM)

The AGM is Government Furnished Equipment (GFE) which can only be loaded on Army procured platforms sold through ADMC-3 contract. Non-Army customers and non- ADMC-3 contract procurements are not authorized to use the AGM. Non-Army customers are required to use the Custom Image CLIN to define any applications, drivers, and operating system that is to be loaded on their platforms. The makeup of such loads shall be negotiated on a case by case bases. The Army Custom Image CLIN shall be used by Army users that have requirements for additional applications, drivers, or utilities beyond the standard AGM they wish to have loaded on their procurement. In both Custom Image loads it is the responsibility of the customer to provide the vendor the image, to secure proper licenses for all software within the image, and assure proper execution of the image.

The Department of Defense (DoD) and the Military services are working to establish a single desktop operating system and application suite image that is compliant with the United States Government Configuration Baseline (USGCB) security configuration baseline and aligns with the Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIG). However, the diversity of applications used across the services currently requires the use of service unique images.

The AGM will be provided to ADMC-3 contractors after award. It will be the responsibly of CHESS to provide the latest version of the AGM 60 days before the start of each Consolidated Buy period and vendors are not required to change out AGMs within a Consolidated Buy period should a new version be released.

1.2.3 Consolidated Buy

Three CBs shall be run over the course of a year; CB-1, CB-2 and CB-3 for a duration of four months each. New Army technology requirements, any new functionality not available on the contract that can be determined to be within the general scope of the contract, shall be introduced once every 12 months, starting with CB-4 and every third CB cycle thereafter

(e.g., CB-7, CB-10, CB-13, etc.). Only immediately mandated DoD/Army requirements shall be introduced during other CB cycles. During CB-1 cycle, and every third CB cycle thereafter (e.g., CB-4, CB-7, CB-10, etc.), the complete product offering of the ADMC-3 contract shall be offered. Product offerings during these CB periods shall establish the vendor’s ceiling prices for each product category and will be enforced the remainder of the year (i.e., next two CB periods). Failure to provide the complete offering will prevent contractor from offering any products until a complete product line offering can be secured.

Contractors shall have the opportunity to refresh product offerings, opportunity to update product offerings to reflect the latest innovation(s)/technology and/or address the CB specification requirements, at or below established ceiling prices for the other two CB periods should they choose. However, only approved product changes will be authorized and no product substitutions will be allowed during a CB period. Should an item become unavailable the product will be listed as “No Bid” for the remainder of that CB and a new product will have to be offered before the next CB. The “No Bid” option is available only for CB-2 and CB-3 cycles, each year (e.g., CB-5, CB-6). To assure that customers have sufficient time to exercise vendor bids, CLINs from closed CBs shall be available for 30 days after the CB has closed. After that time the customer must obtain a new bid based on current CB offerings. This process will repeat with every subsequent ordering year through the Period of Performance (POP).

1.2.4 Start-up Period. The contract start-up period is 60 calendar days commencing upon the issuance by the Government of a notice to proceed. The contractor, at the conclusion of the 60 calendar day period, following issuance of the notice to proceed, shall accept orders.

During that period the contractor shall:

1. Secure required personnel;

2. Develop the specific product descriptions for all CLINs beyond the generic nomenclature in the awarded contract;

3. Establish telephonic support;

4. Prepare to support Electronic Commerce/it e-mart, e.g., vendor’s website URL and vendor’s company and POC information.

5. Complete Request for Quote (RFQ) Tutorials provided by Army CHESS.

1.2.5 Delivery

All orders shall be F.O.B. destination with evidence of delivery unless otherwise specified in the individual orders. The following defines the locations for CONUS, Named OCONUS, and Remote OCONUS:

CONUS The 48 contiguous states, Alaska, Hawaii, and the District of Columbia

Named OCONUS Germany, Italy, Japan, Korea, Belgium, Turkey, Spain, Greece, United Kingdom, Netherlands, Puerto Rico, Guam, Okinawa, Solomon Islands, Kwajalein, Bahrain, United Arab Emirates, Kuwait, and Qatar

Remote OCONUS Locations that are not listed under CONUS or Named

OCONUS

Delivery of products to both CONUS and OCONUS locations shall be in accordance with individual Delivery Orders issued. The contractor shall start accepting orders upon the completion of the 60 day startup period. Delivery to the address(es) specified in each delivery order shall be within 30 calendar days for CONUS addresses, 35 calendar days OCONUS, and 45 days remote OCONUS from the date a valid order is received by the contractor, or as otherwise agreed to by the parties. Partial shipments and partial payments are allowed under the ID/IQ contract unless otherwise specified by the Ordering Contracting Officer. Alternate or additional delivery terms or schedules, such as ship-in-place, expedited shipping or shipping to APO addresses, shall be negotiated between the Contractor and the Ordering Contracting Officer. Upon shipment of product(s), the contractor shall e-mail the Contracting Officer or the individual the order will be shipped to (if an e-mail address is provided). The e-mail shall include the delivery order number, when the order was shipped, the tracking number used by the common carrier, and a worldwide web "hot-link" and if possible, a toll free number to the common carrier.

1.2.6 Trade Agreement Act Compliant (TAA)

All product offerings, if sold separately, shall be compliant with TAA as defined in Federal Acquisition Regulation (FAR) Subpart 25.4 except for CLIN items defined as Computer Accessories (CLIN 0008AA through 0008AM). These CLINs are considered supplies which are applicable to FAR Subpart 25.103 relief from TAA compliance.

NOTE: Only items defined as Computer Accessories are considered Supplies.

All component upgrades and additions (e.g., additional hard drives) are to be provided as part of the major end item being offered (e.g., Standard Desktop Computer). Only the major end item, which is comprised of these components, is required to be TAA compliant.

1.2.7 Acceptance

Acceptance is at destination. The contractor is responsible for providing a legible acceptance document (e.g. DD250) within the timeframe determined by the task order.

1.2.8 Warranty

All computers, displays, printers and multifunction devices shall be offered in three CLIN configurations based on the ship to location of the item. All three delivery locations have different pricing options for customers. The warranty service shall reflect the standard warranty service of the item to include installed upgrades in its area of operation (i.e., CONUS/OCONUS is On-Site while Remote OCONUS is mail-back or hot swap).

Relocation of items shall not affect warranty coverage. If at any time during the warranty or extended warranty period, items are relocated (i.e., from CONUS to OCONUS site), an equitable price adjustment for the remainder of the warranty coverage shall be negotiated between the Contractor and the Ordering Contracting Officer utilizing the CLIN prices contained in the Price Matrix. The contractor shall provide for the repair or replacement of equipment including transportation/shipping costs to and from the customer’s site. The government shall not incur additional charges for the warranty support.

Warranty coverage shall only be terminated when equipment is grievously damaged.

Grievous damage would include cracked, crushed, or bent equipment enclosure/contents;

penetration or spillage by foreign objects or liquids; or damage of item by fire or kinetic force that has been incurred after acceptance of delivery. The warranty shall cover all accessories ordered and installed with the original item except consumables (e.g., paper, printer cartridges). The warranty period shall commence upon the receipt of the equipment at the final destination identified on the Delivery Order or 35 days after shipment from the contractor’s facility, whichever is sooner. This also applies to Purchase Cards orders.

Location Type of Warranty Duration

Desktop Computers, Integrated Computers, Workstations, & Thin Clients

CONUS On-Site 3 Years

OCONUS On-Site 3 Years

Remote OCONUS mail-back or hot-swap 3 Years

Electronic Displays

CONUS On-Site 3 Years

OCONUS On-Site 3 Years

Remote OCONUS mail-back or hot-swap 3 Years

Notebooks, and Slates

CONUS On-Site 3 Year

OCONUS On-Site 3 Year

Remote OCONUS mail-back or hot-swap 3 Years

Printers and Multifunction Devices

CONUS On-Site 1 Year

OCONUS On-Site 1 Year

Remote OCONUS mail-back or hot-swap 1 Years

1.2.8.1 Computer and Display Warranty

All computers, displays, associated upgrades, and accessories shall have a minimum warranty of three (3) years. Items requiring service within CONUS and named OCONUS locations shall have on-site service. Remote OCONUS locations shall as a minimum have mail back or hot swap service. Under no circumstances shall vendor retain storage devices in the servicing of platforms. If hot swap warranty service is offered, the contractor shall dispatch the replacement equipment only after the contractor establishes that the equipment to be repaired has been dispatched by the end user to the appropriate location to be repaired. The option to purchase extended warranties in one-year increments shall be offered for all products delivered. Mobile device batteries shall not be considered a consumable and shall be warranted for one year in the event of failure.

1.2.8.2 Printer and Multifunction Device Warranty

Printers and multifunction devices shall provide a minimum one-year or commercial warranty period whichever is greater. Items requiring service within CONUS and named OCONUS locations shall have on-site service. Remote OCONUS locations shall as a minimum have mail back or hot swap service. If hot swap warranty service is offered, the contractor shall dispatch the replacement equipment only after the contractor establishes that the equipment to be repaired has been dispatched by the end user to the appropriate location to be repaired. The option to purchase extended warranties in one- year increments shall be offered for all products delivered.

1.2.9 Time to Repair

Desktop equipment, within CONUS and named OCONUS locations, shall be repaired or replaced and fully operational within two (2) Government working days following notification to the contractor's designated technical support personnel of the need for warranty service.

Portable equipment, within CONUS and named OCONUS locations, for which on-site warranty is being offered shall be repaired or replaced and fully operational within two (2) Government working days following notification to the contractor's designated technical support personnel of the need for warranty service. For Remote OCONUS locations being offered on-site warranty, the equipment shall be repaired or replaced and fully operational within three (3) Government working days following notification to the contractor’s designated technical support personnel of the need for warranty service. For Remote OCONUS locations not being offered on-site warranty, the contractor shall repair or replace and return fully operational equipment to the customer’s possession within five (5) Government working days after it is received at the contractor’s repair facility (mail-back), or within five (5) Government working days after it has been dispatched by the end user to the appropriate location to be repaired (hot-swap). The contractor shall bear all shipping costs and responsibilities of repaired and replaced equipment and software both to and from the customer’s site.

1.2.10 Replacement Parts

When the contractor replaces a defective part during the warranty period, the newly installed part shall become Government property. The defective part shall become the property of the contractor except for the disposition of storage devices (e.g., hard disk drives, solid state drives, etc.) the Government shall retain all drives without additional fees to assure proper disposal of any information contained on the devices. The effective warranty for all replacement items shall be the greater of: (1) the remaining warranty period on the original item; (2) a 90-calendar day warranty; or (3) a specified warranty period of specific items defined in this SOW.

1.2.11 New or Warranted Parts

Only new parts or parts warranted by the OEM as equal to new shall be utilized when repairs are made.

1.2.12 Telephonic Support

The contractor shall provide a toll free number in CONUS for warranty support and any product questions. As a minimum, telephonic support shall be provided in support of all purchased products and shall include Order Processing, Order Tracking Information, and Customer Technical Assistance. The minimum amount of time before call back from the contractor will be within 24 hours. Telephonic support personnel shall speak English fluently. Telephonic support shall also be provided free of charge to users in Named OCONUS and Remote OCONUS locations. Telephonic support shall be available, as a minimum, during the Principle Period of Operation (PPO) on a worldwide basis. The Contractor shall provide a means to receive problem reports from users Outside of Principal Period of Operation (OPPO). The PPO and OPPO time periods are listed in the table below.

Location PPO* OPPO**

CONUS M-F 8am – 5pm local time M-F 5:01 pm – 7:59 am local time Sat–Sun – 24 hours a day

Named OCONUS M-F 8am –5pm local time M-F 5:01 pm – 7:59 am local time Sat–Sun – 24 hours a day

Remote

OCONUS

M-F 8am –5pm local time M-F 5:01 pm – 7:59 am local time Sat–Sun – 24 hours a day

*PPO - excludes U.S. Government Holidays and OCONUS host nation holidays.

**OPPO – includes weekends, U.S. Government and OCONUS host nation holidays.

Recorded answering services are not acceptable to the Government during the PPO but are acceptable during OPPO hours. "Local Time" is the current time associated with the site/location requiring telephonic support.

1.2.13 Customer Technical Assistance

The contractor shall receive product problem reports and assist the customer toward timely resolution of the reported problem. Reports of problems from customers may come via postal mail, e-mail, phone, or fax. The contractor is responsible for hardware related calls for all products that are sold by the contractor under the contract. Telephonic triage is acceptable for the initial warranty call. This call shall be limited to one (1) hour in length. If at the end of one hour of telephone time the contractor determines that additional time will provide a resolution to the problem they may extend the telephone time with the approval of the caller.

1.2.14 Order Processing and Order Tracking

The contractor shall receive Delivery Orders and credit card orders. Orders may be received via phone, fax, E-mail, postal mail, or Government websites (e.g., CHESS IT e-mart). The contractor shall provide customers the status of their delivery order.

1.2.15 Technology Refresh and Product Additions

The Contractor, shall be able to submit a technology refresh of their product offering before the start of each Consolidated Buy. The Technology Refresh shall update product offerings to reflect the latest technology and address the CB specification requirements. At the Government’s release of an “Engineering Change Request” (ECR) the contractor will be requested to submit products for addition to the contract that address the EC requirement and are within the contract scope. All changes shall be within the general scope of the contract and in the best interest of the Government. The decision to accept such offers shall be at the sole and exclusive discretion of the procuring contracting officer and not subject to the “Disputes” clause of this contract.

1.2.16 DoD Enterprise Software Initiative and SmartBUY

The DoD ESI and SmartBUY are two initiatives that establish Enterprise Software Agreements (ESA) for commercial software. In accordance with DFARS PGI 208.74, in situations where the purchase of new commercial software, including preloaded software, is needed to satisfy the requirements of a particular order, requirements shall be fulfilled with software through the DoD ESI or SmartBUY sources. The contractor shall order from the DoD ESI and SmartBUY sources to obtain the software to satisfy the requirement. The contractor is responsible for reviewing available DoD ESI and SmartBUY sources. The listing of commercial software available from DoD ESI sources can be viewed on the website at http://www.esi.mil/. The listing of commercial software available from SmartBUY sources can be viewed on the website at http://www.gsa.gov/portal/content/105119. Also see, SmartBUY Policy, dated 22 Dec 2005, DoD CIO Office, Department of the Defense Support of the SmartBUY initiative; electronic copy can be found at http://www.esi.mil/download.aspx?id=463

1.2.17 Unique Identification

A unique item identifier (UII) is required in accordance with (IAW) DFARS clause 252.211-

7003, Item Identification and Valuation, for: a) any DOD equipment whose acquisition cost is $5,000.00 or greater; and, b) all serially managed items (as identified by the customer).

The contractor is required to enter the UID data IAW DFARS clause 252.211-7003, Item

Identification and Valuation.

1.2.18 Special Asset Tagging

Special asset tags, to include UID tagging requested by Non-DOD customers, shall be provided. Contractors may charge for asset tagging negotiated by the ordering Contracting

Officer, as appropriate.

1.2.19 Radio Frequency Identification (RFID)

RFID tagging shall be IAW DOD Radio Frequency Identification (RFID) Policy, 30 July

2004. RFID tagging is mandatory for deliveries as follows:

A. Major end items (items with an acquisition cost of $5000 or more) delivered to the sites identified at Attachment 3 of the RFID policy; and

B. After 1 January 2007- all shipped cases, pallets, and items with an UID tag.

Contractors may charge for RFID tagging negotiated by the ordering Contracting Officer.

1.2.20 Security

Note: Based on the information available it is estimated that approximately 99% of the orders under the previous (ADMC-2) contracts were unclassified and did not require a DD Form 254.

http://www.esi.mil/ http://www.gsa.gov/portal/content/105119 http://www.esi.mil/download.aspx?id=463

A. Although it is unknown exactly how many orders will be required to have security clearance requirements and the levels of security clearances, the Government may require security clearances from Secret to Top Secret sensitive compartmented information (SCI), for performance of any order under this contract. The specific vendor security clearance will be determined at the delivery order level. A DD Form 254 will be incorporated for individual orders at the delivery order level, as required.

B. The Contractor shall provide sufficient personnel with the required security clearances to perform the work as specified in individual orders. If satisfactory security arrangements cannot be made with the contractor, the required services shall be obtained from other sources. The Contractor’s Facility Security Officer is responsible for submitting the required personnel security clearances IAW DoD 5220.22-M, National Industrial Security Program Operating Manual, February 28, 2006.

C. The level of classified access required shall be indicated in the individual order.

Contractor personnel not requiring a personnel security clearance, but performing

Information Technology (IT) sensitive duties, are subject to investigative and assignment requirements IAW DoD 5200.2R, Personnel Security Program, January

1987, and Change 3, 23 Feb 1996, AR 25-2, Information Assurance, 24 Oct 2007, and affiliated regulations.

D. Security requirements that shall be accomplished by the Contractor will be per the DOD Information Assurance Certification and Accreditation Process (DIACAP) DOD Instruction 8510.01, November 28, 2007. The Contractor shall transmit and deliver any classified material/reports IAW the National Industrial Security Program Operations Manual (NISPOM) and the Industrial Security Regulation (DOD 5220.22- R). Individual system security requirements shall be accomplished as specified in the Task/Delivery Order. When the Delivery Order/Task Order is not for a classified order a DD Form 254 is not required.

1.3 Contract Management

1.3.1 Government Information Technology Conferences

The contractor shall participate in Government IT conferences which are normally held by each Military service annually. The location for each conference varies and will be specified by the Government.

1.3.2 Contract Status Meetings

The contractor shall participate in meetings with the Government to discuss contract status;

this includes issues, concerns, improvements, new products, etc. The meetings will be held by each Military service approximately once each year. Location of the meetings will vary and will be specified by the Government.

1.3.3 Reports

The Contractor shall provide the following reports electronically to each of Military services as detailed in Exhibit A.

– Equipment Failure Report: The contractor shall provide an equipment failure report IAW Exhibit A. This report shall be provided on an as requested basis.

– Monthly Order Transaction Report: The contractor shall provide monthly order transactions (delivery orders or credit card purchases) to the Government for inclusion in its Order Tracking Database and website.

– Monthly Vendor Status Report: The contractor shall provide monthly shipping status to the Government for inclusion in its Order Tracking Database and website.

1.3.4 Worldwide Web

The contractor shall develop a worldwide web home page to house the guidelines and products offered on the contract. The contractor may work with the Government to build a

Business-to-Business Integration relationship between the Government’s website (IT e-mart) and the contractor’s website for the customer’s use in purchasing online. The contractor shall use IT e-mart to respond to customers requesting quotes, configuration assistance, and assistance with shopping for products listed. The time allotted for acknowledging customer requests is two Government working days. The contractor shall send a formal response to the customer within five Government working days. The contractor shall provide a quote to 30% or greater of all RFQs solicited competitively during a one year period through the CHESS IT E-Mart Tool. Quotes must be within contract scope and within the stated requirements set forth in the orders. “No bid” responses must include rationale for not bidding. No bid responses are not included in the 30%. Exceptions to bid quotes (not counted in the 30%) include: (1) Not an authorized reseller; (2) Not enough time provided to respond based on the requirement and the contracting office has denied an extension request; (3) Out of scope, or there exists a more appropriate CHESS contract vehicle; or (4) Unclear requirements that the contracting office has not been able to resolve. Contractor response and response times will be used as a measure of contractor performance.

1.3.5 Promoting the Contract

The contractor shall promote this contract to DoD customers and other eligible users during the life of the contract. The contractor’s goals shall be to:

– Make customers aware of this procurement vehicle;

– Make customers aware of available products;

– Make customers aware of sub-contractor(s) products, including small business participation; and

– Assist customers in creating timely and accurate purchase orders.

1.3.6 Performance Standards

The contractor’s performance will be monitored, measured, and reported in the Past Performance Information Management System (PPIMS). Performance measures will include the contractor’s ability:

– To meet agreed upon dates for scheduled delivery of items, and warranty;

– To prepare, develop, and use comprehensive reports/presentations;

– To provide qualified employees to adequately staff the program;

– To efficiently log and track requests for warranty service and notify the customer as to expected completion time; and

– To respond to the customer’s requests for quotes and configuration assistance within five Government working days.

1.3.7 IT e-mart

It will be mandatory for all customers to submit Request for Quotes (RFQ’s) over $3,000 using the RFQ tool on CHESS IT e-mart or by using a reverse auctioning site, such as FedBid. It is also mandatory that the contractor use the IT e-mart RFQ Tool, if the RFQ is submitted via IT e-mart, to acknowledge customer RFQ’s either by indicating that a quote will be provided or by responding with a no-bid. If the contractor provides a no-bid response, the no-bid response and the rationale for not bidding shall be submitted for each RFQ to the IT e-mart in the location provided for the no-bid responses no later than the RFQ due date. The time allotted for acknowledging customer RFQ’s is two Government working days. The contractor shall send a formal response to the customer within five Government working days regarding its intent to propose a solution unless the quote is due in a shorter timeframe. In the event the contractor receives a request for quote from the customer via email, direct phone call, etc., (with the exception of FedBid) the contractor must direct the customer to place the RFQ using the RFQ Tool on the IT e-mart system.

The PD CHESS Product Leader shall also be notified that the customer has been advised to place the RFQ on IT-emart.

2.0 Constraints

2.1 Federal

Energy Star Program Requirements for Computers, Version 6.1 , 20 Oct 2014 http://www.energystar.gov/sites/default/files/FINAL%20Version%206.1%20Computer%20Pr ogram%20Requirements%20%28Rev%20Oct-2014%29_PTECMAX_Clean_0.pdf

Energy Star Program Requirements for Displays, Version 6.0, 20 Oct 2014 http://www.energystar.gov/sites/default/files/FINAL%20Version%206.0%20Display%20Prog ram%20Requirements%20%28Rev%20Oct-2014%29_0.pdf

Energy Star Program Requirements for Imaging Equipment, Version 2.0, 01 January 2014, http://www.energystar.gov/sites/default/files/FINAL%20Version%202.0%20Imaging%20Equ ipment%20Program%20Requirements%20%28Rev%20Oct-2014%29_0.pdf

Energy Star Program Requirements for Uninterruptible Power Supply, Version 1.0, 1 August 2012 http://www.energystar.gov/sites/default/files/specs//private/ES_UPS_V1_Specification.pdf

Electronic Product Environmental Assessment Tool http://www.epeat.net/about-epeat/

Executive Order 13693 Federal Leadership in Environmental, Energy, and Economic Performance, 19 March 2015. https://www.fedcenter.gov/programs/eo13693/

FAR Federal Acquisition Regulation http://farsite.hill.af.mil/vffara.htm

FIPS PUB 140-2 Security Requirements for Cryptographic Modules, 15 Nov 2001 http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf

FIPS 140-1 and FIPS 140-2 Cryptographic Modules Validation List http://csrc.nist.gov/groups/STM/cmvp/validation.html

FIPS PUB 200 Minimum Security Requirements for Federal Information and Information Systems, March 2006 http://csrc.nist.gov/publications/fips/fips200/FIPS-200-final-march.pdf

FIPS PUB 201-2 Personal Identity Verification (PIV) of Federal Employees and Contractors, August 2013 http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.201-2.pdf

FIPS 201 Approved Products List http://fips201ep.cio.gov/apl.php

OMB Circular A-130 Revised, "Management of Federal Information Resources, Transmittal 4, 28 November 2000 http://www.whitehouse.gov/omb/circulars_a130_a130trans4

OMB Memorandum M-05-22 Transition Planning for Internet Protocol Version 6 (IPv6), 2 August 2005 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-http://www.energystar.gov/sites/default/files/FINAL%20Version%206.1%20Computer%20Program%20Requirements%20%28Rev%20Oct-2014%29_PTECMAX_Clean_0.pdf http://www.energystar.gov/sites/default/files/FINAL%20Version%206.1%20Computer%20Program%20Requirements%20%28Rev%20Oct-2014%29_PTECMAX_Clean_0.pdf http://www.energystar.gov/sites/default/files/FINAL%20Version%206.0%20Display%20Program%20Requirements%20%28Rev%20Oct-2014%29_0.pdf http://www.energystar.gov/sites/default/files/FINAL%20Version%206.0%20Display%20Program%20Requirements%20%28Rev%20Oct-2014%29_0.pdf http://www.energystar.gov/sites/default/files/FINAL%20Version%202.0%20Imaging%20Equipment%20Program%20Requirements%20%28Rev%20Oct-2014%29_0.pdf http://www.energystar.gov/sites/default/files/FINAL%20Version%202.0%20Imaging%20Equipment%20Program%20Requirements%20%28Rev%20Oct-2014%29_0.pdf http://www.energystar.gov/sites/default/files/specs/private/ES_UPS_V1_Specification.pdf http://www.epeat.net/about-epeat/ https://www.fedcenter.gov/programs/eo13693/ http://farsite.hill.af.mil/vffara.htm http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf http://csrc.nist.gov/groups/STM/cmvp/validation.html http://csrc.nist.gov/publications/fips/fips200/FIPS-200-final-march.pdf http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.201-2.pdf http://fips201ep.cio.gov/apl.php http://www.whitehouse.gov/omb/circulars_a130_a130trans4 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-22.pdf

22.pdf

The Contractor shall transmit and deliver any classified material/reports IAW;

National Industrial Security Program Operations Manual (NISPOM) Industrial Security Regulation (DOD 5220.22-M) incorporating Change1,28 March 2013 http://www.dtic.mil/whs/directives/corres/pdf/522022m.pdf

Department of Defense Instruction (DoDI 5220.22) March 18, 2011 http://www.dtic.mil/whs/directives/corres/pdf/522022p.pdf

NIST SP800-147 Basic Input/Output (BIOS) Protection Guidelines, April 2011 http://csrc.nist.gov/publications/nistpubs/800-147/NIST-SP800-147-April2011.pdf

NIST SP 800-153 Guidelines for Securing Wireless Local Area Networks (WLANs), February 2012 http://csrc.nist.gov/publications/nistpubs/800-153/sp800-153.pdf

National Security Telecommunications and Information Systems Security (NSTISSP) Policy No. 11, July 2003 http://www.niap-ccevs.org/cc-scheme/nstissp_11_revised_factsheet.pdf

NIST Special Publication 800-36. October 2003, Subject: Guide to Selecting Information Technology Security Products http://csrc.nist.gov/publications/nistpubs/800-36/NIST-SP800-36.pdf

Security and Privacy Controls for Federal Information Systems and Organizations SP 800- 53 Rev. 4, 30 April 2013, Updated 22 Jan 2015;

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

Section 508; Guide to the Standards for Electronic and Information Technology:

Section B – Technical Standards http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards#subpart_b Software Applications and Operating Systems (1194.21), Web-based Intranet and Internet Information and Applications (1194.22), Telecommunications Products (1194.23), Video and Multimedia Products(1194.24), Self-Contained, Closed Products (1194.25 Desktop and Portable Computers (1194.26)

Title 47, Part 15(47 CFR 15) – Class B Federal Communications Commission – Unintentional Radiators http://www.ecfr.gov/cgi-bin/text-idx?SID=83be207fe7c6e3d41d530ad4dd0268c4&node=47:1.0.1.1.16&rgn=div5

Under Secretary of Defense Memorandum: Subject Policy For Unique Identification (UID) of Tangible Personnel Property Legacy Items in Inventory and Operational Use, Including Government Furnished Property (GFP). 23 Dec 2004, http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-22.pdf http://www.dtic.mil/whs/directives/corres/pdf/522022m.pdf http://www.dtic.mil/whs/directives/corres/pdf/522022p.pdf http://csrc.nist.gov/publications/nistpubs/800-147/NIST-SP800-147-April2011.pdf http://csrc.nist.gov/publications/nistpubs/800-153/sp800-153.pdf http://www.niap-ccevs.org/cc-scheme/nstissp_11_revised_factsheet.pdf http://csrc.nist.gov/publications/nistpubs/800-36/NIST-SP800-36.pdf http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards%23subpart_b http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards%23subpart_b http://www.ecfr.gov/cgi-bin/text-idx?SID=83be207fe7c6e3d41d530ad4dd0268c4&node=47:1.0.1.1.16&rgn=div5 http://www.ecfr.gov/cgi-bin/text-idx?SID=83be207fe7c6e3d41d530ad4dd0268c4&node=47:1.0.1.1.16&rgn=div5 http://www.acq.osd.mil/dpap/Docs/uid/UID%20Policy%20Update%20Legacy%20Items%20 12-23-2004.pdf

Under Secretary of Defense Memorandum: Subject: Radio Frequency Identification (RFID) Policy, 30 July 2004, https://acc.dau.mil/adl/en-US/142796/file/27748/RFIDPolicy07-30- 2004.pdf

CJCSI 3170.01I: Joint Capabilities Integration and Development System, 23 January 2015, https://dap.dau.mil/policy/Documents/2015/CJCSI_3170_01I.pdf

CJCSI 6212.01F Net Ready Key Performance Parameter (NR KPP), 21 March 2012, http://www.dtic.mil/cjcs_directives/cdata/unlimit/6212_01.pdf

Common Criteria http://www.commoncriteriaportal.org/

Department of Defense Architecture Framework (DODAF) Version 2.02. August 2010 http://dodcio.defense.gov/Portals/0/Documents/DODAF/DoDAF_v2-02_web.pdf

Department of Defense Guide to Uniquely Identifying Items (Version 1.4). 16 April 2004, http://www.acq.osd.mil/dpap/Docs/uid/guide_1_4.pdf

Department of Defense Strategy for Implementing the Joint Information Environment, 18 September 2013, http://dodcio.defense.gov/Portals/0/Documents/JIE/2013-09- 13_DoD_Strategy_for_Implmenting_JIE_(NDAA_931)_Final_Document.pdf

Department of Defense Standard Practice - Military Marking For Shipment and Storage (MIL-STD-129R) 18 February 2014, https://www.wbdg.org/ccb/FEDMIL/std129r.pdf

Department of Defense Standard Practice – Test Method Standard Environmental engineering Considerations and Laboratory Tests (MIL-STD-810G) 31 October 2008, http://www.atec.army.mil/publications/Mil-Std-810G/Mil-Std-810G.pdf

Department of Defense Suppliers’ Passive RFID Information Guide http://www.acq.osd.mil/log/sci/.RFID_FAQs.html/DoD_Suppliers_Passive_RFID_Info_Guid e_v15update.pdf

DFARS- Department Federal Acquisition Regulation Supplement -http://farsite.hill.af.mil/VFDFARA.HTM

NOTE: To download the following STIGs, go to the website listed below. The STIGs are listed alphabetically. Click on the name and download the files.

http://iase.disa.mil/stigs/Pages/a-z.aspx (search name and download files)

DISA Application Security and Development STIG Version 3 Rel 10, 23 Jan 2015

DISA Desktop Application General STIG, Version 4, Release 4, 24 October 2014 http://www.acq.osd.mil/dpap/Docs/uid/UID%20Policy%20Update%20Legacy%20Items%2012-23-2004.pdf http://www.acq.osd.mil/dpap/Docs/uid/UID%20Policy%20Update%20Legacy%20Items%2012-23-2004.pdf https://acc.dau.mil/adl/en-US/142796/file/27748/RFIDPolicy07-30-2004.pdf https://acc.dau.mil/adl/en-US/142796/file/27748/RFIDPolicy07-30-2004.pdf https://dap.dau.mil/policy/Documents/2015/CJCSI_3170_01I.pdf http://www.dtic.mil/cjcs_directives/cdata/unlimit/6212_01.pdf http://www.commoncriteriaportal.org/ file:///C:/Users/james.h.johnson/Documents/CHESS/Standards&Policies/~$andards_and_Policies.docx file:///C:/Users/james.h.johnson/Documents/CHESS/Standards&Policies/~$andards_and_Policies.docx http://www.acq.osd.mil/dpap/Docs/uid/guide_1_4.pdf http://dodcio.defense.gov/Portals/0/Documents/JIE/2013-09-13_DoD_Strategy_for_Implmenting_JIE_(NDAA_931)_Final_Document.pdf http://dodcio.defense.gov/Portals/0/Documents/JIE/2013-09-13_DoD_Strategy_for_Implmenting_JIE_(NDAA_931)_Final_Document.pdf https://www.wbdg.org/ccb/FEDMIL/std129r.pdf http://www.atec.army.mil/publications/Mil-Std-810G/Mil-Std-810G.pdf http://www.acq.osd.mil/log/sci/.RFID_FAQs.html/DoD_Suppliers_Passive_RFID_Info_Guide_v15update.pdf http://www.acq.osd.mil/log/sci/.RFID_FAQs.html/DoD_Suppliers_Passive_RFID_Info_Guide_v15update.pdf http://farsite.hill.af.mil/VFDFARA.HTM http://iase.disa.mil/stigs/Pages/a-z.aspx

DISA Multifunction Device and Network Printer STIG Version 2, Release 7, 23 October 2015

DISA Network Firewall STIG Version 8, Rel 19,23 Oct 2015

DISA Network Infrastructure Router L3 Switch STIG- Version 8, Rel 19, 23 Oct 2015

DISA Network L2 Switch STIG, Version 8, Rel 19, 23 Oct 2015

DISA Network Perimeter Router L3 Switch STIG, Version 8 , Rel 21, 23 Oct 2015

DISA Network Policy, Version 8, Rel 18, 3 Sept 2014

DISA Voice and Video over Internet Protocol (VVoIP) STIG, Ver 3, Rel7 23 Oct 2015

DISA Wireless STIG, Version 6 Rel 9, 24 Oct 2014

DISA STIGs for UNIX: The most current version of the applicable UNIX STIG at the time of request for proposal or task order issuance will take precedence.

DISA STIGs for Linux: The most current version of the applicable Linux STIG at the time of request for proposal or task order issuance will take precedence.

DoD CIO Desk Reference - The Clinger-Cohen Act (Chapter 25 of title 40, United States Code) see http://dodcio.defense.gov/Pciodesrefvoloneortals/0/Documents/.pdf

DoD Directive 8000.01,…