Attachment 1 - Performance Work Statement (PWS).pdf
PDF 2 MB Posted
- Attached to
- 100 MFDs for Italy revised to 182 MFDs Federal contract opportunity
- Solicitation number
- SP7000-21-Q-1020
- Issued by
- Defense Logistics Agency
About this file
This is a performance work statement for a solicitation issued by the Defense Logistics Agency seeking quotes for the lease of 182 multifunction devices for locations in Italy. The performance work statement outlines the required technical specifications for the devices, including capabilities for copying, printing, scanning, and faxing. It specifies volume bands for monthly impressions and minimum speeds. It also addresses requirements for delivery and installation, training, maintenance with a 95% uptime guarantee, relocation services, technical refreshment, removal at the end of the contract term, and reporting. The document specifies compliance requirements for network security including DISA STIG and NIAP certification and outlines testing to be conducted by DLA. Quotes are due based on the delivery schedule in Attachment 2, with award planned for early 2023.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SP7000-21-Q-1020-006.pdf | ||
| SP7000-21-Q-1020-005.pdf | ||
| SP7000-21-Q-1020-004.pdf | ||
| SP7000-21-Q-1020-003.pdf | ||
| SP7000-21-Q-1020-002.pdf | ||
| Attachment 1 - PWS 1020-001.pdf | ||
| Attachment 2 - Delivery Schedule 1020-001.pdf | ||
| Attachment 6 - 20 Percent Quantity Increase 1020-001.pdf | ||
| SP7000-21-Q-1020-001.pdf | ||
| Attachment 3 - CLIN Structure 1020-001.xlsx | XLSX spreadsheet | |
| Attachment 8 - Submission Checklist 1020-001.pdf | ||
| Attachment 2 - Delivery Schedule.pdf | ||
| Attachment 4 - Performance Work Statement Compliance Form.docx | DOCX document | |
| Attachment 5 - Full Text Provisions (Vendor COMPLETION Required).docx | DOCX document | |
| Attachment 3 - CLIN Structure.xlsx | XLSX spreadsheet | |
| SP7000-21-Q-1020.pdf | ||
| Attachment 6 - 20 Percent Quantity Increase.pdf | ||
| Attachment 7 - Question and Comment Form.xlsx | XLSX spreadsheet |
Show all 18
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
I. OVERVIEW
| A. The | Defense | Logistics | Agency | (DLA) | seeks | to | enter | into | a | contract | for | ONE | HUNDRED | (100) |
| Multifunctional | Devices | for | up | to | 60 | month | lease | of | Multifunctional | Devices | (MFDs), | accessories | and | |
| office | document | devices | (hereafter | collectively | referred | to | as | “devices”) | within | OUTSIDE | THE | |||
| CONTIGUOUS | UNITED | STATES | (OCONUS) | – | ITALY. Specific | details | are | found | in | sections | II | and | III. |
| B. The | services | associated | with | the | leased | devices | sought | are | delivery | and | installation | (section | IV), | end‐ |
| user | training | (section | V), | full | service | maintenance, | including | all | consumable | supplies | (excluding | |||
| paper)(section | VI), | relocation | (section | VII), | technical | refresh | (section | VIII), | removal | (section | IX), | |||
| reports | (section | X), | network | functionality | (section | XII), | and | network | security | (section | XIII). |
II. DEVICES AND CONFIGURATIONS
A. All devices shall meet the following requirements:
1. Simplex/duplex copying, printing, and scanning.
2. Automatic Document Feeder with a 30 page minimum capacity and duplexing.
3. Basic inline finishing functions which include stacking, collating, and multi‐position stapling.
4. Operate using at least 30% recycled 20 lb. paper.
| 5. Free‐standing | with | casters/wheels | (or | cabinets | provided | as | needed). | No | devices | shall | be |
| configured | for | table‐top | use. |
6. Copy resolution of at least 600 x 600 DPI.
7. Print resolution of at least 1,200 x 1,200 DPI.
8. Support current desktop and server operating systems.
9. A minimum of 1 Gigabyte of document management memory.
| 10. Print | drivers | shall | be | capable | of | Page | Description | Language | (PDL) | to | support | Adobe | PS3, | PCL5E |
| and | PCL6. |
| 11. Delivered | with | up‐to‐date | software/firmware | and | drivers, | with | 32‐bit | and | 64‐bit | architecture | ||
| driver | support. | Provide | all | subsequent | updates | along | with | installation | instructions | to | DLA. |
| 12. Operate | using | 220 | volts | (V)/50 | hertz | (Hz) | alternating | current | (AC) | electrical | current. | No | external | |||
| transformers | shall | be | used | as | an | exception. | The | contractor | shall | also | identify | the | power | plug | type |
required.
| 13. Equipped | with | an | external | surge | protector | to | protect | all | electronic | components. | The | external | surge |
| protector | shall | be | provided | in | addition | to | any | internal | surge | protectors. | External | surge | protectors |
| shall | have | a | minimum | five | (5) | year | manufacturer’s | warranty | that | covers: |
a. Replacement of the surge protector if it fails, at no cost to the Government.
| b. Repair | or | replacement | of | any | device | provided | through | this | PWS | damaged | by | a | power | surge |
| when | properly | connected | to | the | Contractor‐provided | surge | protector. |
14. Include a printed operator’s manual, in English, for each device.
15. Default to:
a. Automatically go into sleep mode after 20 minutes of inactivity
b. Automatically go into hibernation after an hour of inactivity.
SP7000-21-Q-1020 Attachment 1 - Performance Work Statement (PWS)
c. Print duplex (2‐sided).
d. Print in gray scale on both monochrome and color MFDs
e. “Draft” quality printing rather than “high” quality printing
f. Display all information in English.
B. Devices shall meet the following security requirements:
1. Devices with hard drives shall have an encryption or overwrite Security Kit.
| 2. Only | CLASSIFIED | designated | devices | shall | be | placed | on | the Secret | Internet | Protocol | Router | ||||||
| Network | (SIPRNet). | All | CLASSIFIED | designated | devices | shall | include | an | option | for | a | removable | |||||
| hard | drive. | A | removable | hard | drive | is | a | hard | drive | the | end‐user | may | easily | remove, | and | reinsert | |
| into | the | device | on | a | recurring | basis. | All | devices | with | removable | hard | drives | shall | have | a | locking | |
| mechanism | to | secure | the | hard | drive. |
| 3. All | Universal | Serial | Bus | (USB) | ports/memory | card | slots | on | the | devices | shall | be | disabled | when | |
| delivered | except: | the | printer | port | used | to | connect | the | device | to | a | single | computer; | Common | Access |
| Card | (CAC) | readers; | and | any | USB | ports | needed | for | servicing/maintaining | equipment. | Additionally, | ||||
| unused | ports, | protocols | and | services | on | each | device | shall | be | able | to | be | enabled/disabled | by | the |
| local | IT | administrator. |
| 4. All | devices | shall | have | a | secure | scanning | functionality | that | complies | with | Federal | Information | |||||||
| Processing | Standard | (FIPS) | 140‐2 | (will | be | replaced | by | 140‐3 | FY22) | encryption | with | routing | and | full | |||||
| integration | to | standard | network | infrastructure | destinations, | which | include: | Scan‐to‐Email, | Scan‐to‐ | ||||||||||
| Folder, | Scan‐to‐Network, | Scan‐to‐Server | and | Scan‐to‐PC. | Scanned | documents | shall | be | made | ||||||||||
| available | as | a | TIFF, | JPEG | and | as | a | file | format. | The | default | scan | resolution | shall | be | 300 | x | 300 | |
| DPI. | The | default | scan | output | file | type | shall | be | PDF. | Devices | shall | have | Optical | Character | |||||
| Recognition | (OCR) | in | order | to | process | and | produce | text‐searchable | documents | to | the | scan | |||||||
| destination. | Note: | Full | integration | does | not | mean | scanning | to | proprietary | back‐end | content, | ||||||||
| document | or | records | management | systems | to | support | customized | indexing | or | metadata |
requirements.
| 5. All | Non‐Classified | Internet | Protocol | Router | (NIPR) | devices, | volume | bands | 1‐5, | shall | have | analog | fax | |
| only. | Note: | The | analog | fax | function | shall | be | configured | to | separate/isolate | the | fax | controller | from |
| the | network | controller. | SIPR | devices | shall | NOT | have | fax | capability. |
6. All devices shall have:
| a. | CAC/Personal | Identity | Verification | (PIV) | enablement | in | order | to | secure | the | device | from | |
| unauthorized | use | and | shall | have | a | “Secure | Print” | feature | that | allows | end‐users | to | use |
| authentication | credentials | (ex. | ID, | Login) | and | password | identification | (PIN) | to | release | jobs | ||
| on | the | device. |
| b. | Capability | of | integration | with | on‐demand | solution | (e.g., | equivalent | to | “Follow | Me,” | “Follow | |||
| You,” | “Push” | or | “Pull” | printing) | that | shall | allow | end‐users | to | release | output | on | any | device | |
| on | the | network. |
| C | Contractors | shall | provide | original | equipment | manufacturer | (OEM) | specification | sheets, | to | include | |
| proposed | configurations, | for | each | device | with | proposal | to | the | Contracting | Officer. |
III. SPECIFICATIONS:
| A. | In | addition | to | the | features/capabilities/configurations | set | forth | in | section | II | (outlined | above), | the | ||
| Contractor | shall | provide | all | devices | in | accordance | with | the | chart | below: |
Quantity Volume Band
NIPR/
SIPR
Estimated Monthly
Impressions
| Min. | Speed | |
| (PPM) | Paper | Capacity |
Mono Color Mono/Color
7 VB‐1NM NIPR 5,000 N/A 25
| One | (1) | Bypass | Tray | [100 | Sheet | Minimum] | ‐ | Up | to | 11" | x | 17" |
| Two | (2) | Adjustable | Paper | Trays | [500 | Sheet | Minimum/Tray] | ‐ | Up | to | 11" | x |
17"
3 VB‐1SC SIPR 3,000 2,000 25
| One | (1) | Bypass | Tray | [100 | Sheet | Minimum] | ‐ | Up | to | 11" | x | 17" |
| Two | (2) | Adjustable | Paper | Trays | [500 | Sheet | Minimum/Tray] | ‐ | Up | to | 11" | x |
17"
14 VB‐1NC NIPR 3,000 2,000 25
| One | (1) | Bypass | Tray | [100 | Sheet | Minimum] | ‐ | Up | to | 11" | x | 17" |
| Two | (2) | Adjustable | Paper | Trays | [500 | Sheet | Minimum/Tray] | ‐ | Up | to | 11" | x |
17"
23 VB‐2NM NIPR 10,000 N/A 35
| One | (1) | Bypass | Tray | [100 | Sheet | Minimum] | ‐ | Up | to | 11" | x | 17" |
| Two | (2) | Adjustable | Paper | Trays | [500 | Sheet | Minimum/Tray] | ‐ | Up | to | 11" | x |
17"
10 VB‐2SC SIPR 5,000 5,000 35
| One | (1) | Bypass | Tray | [100 | Sheet | Minimum] | ‐ | Up | to | 11" | x | 17" |
| Two | (2) | Adjustable | Paper | Trays | [500 | Sheet | Minimum/Tray] | ‐ | Up | to | 11" | x |
17"
43 VB‐2NC NIPR 5,000 5,000 35
| One | (1) | Bypass | Tray | [100 | Sheet | Minimum] | ‐ | Up | to | 11" | x | 17" |
| Two | (2) | Adjustable | Paper | Trays | [500 | Sheet | Minimum/Tray] | ‐ | Up | to | 11" | x |
17"
IV. DELIVERY AND INSTALLATION
A. Delivery and Installation of Ordered Devices:
| 1. Delivery | and | Installation | of | ordered | devices | shall | be | in | accordance | with | (IAW) | the | timeframes |
| outlined | in | the | chart | below: |
| Amount | of | Devices |
| Per | Contracting | Action |
| Maximum | Number | of | Calendar | Days |
| to | Complete | Delivery | and | Installation |
Up to 100 30 days after receipt of contract
101 ‐ 200 45 days after receipt of contract
201 – 500 60 days after receipt of contract
More than 500 90 day after receipt of contract
| 2. | Installation | shall | be | defined | as | device | is | fully | operational | as | ordered, | to | include | network | ||||||
| connectivity | and | scanning, | if | required. | The | Contractor | shall | provide | onsite | technical | and | system | ||||||||
| analyst | support | and | appropriate | digital | cards/products | to | successfully | connect | devices | to | DLA | |||||||||
| customers’ | networks. |
| 3. | Upon | completion | of | device | delivery, | the | Contractor | shall | obtain | customer | signature | and | date | on | ||||
| each | bill | of | lading | (BOL) | or | packing | slip, | and | provide | this | proof | of | delivery | to | the | designated | DLA | |
| POC | within | ten | (10) | business | days | after | delivery. | The | Contractor | shall | also | provide | the | |||||
| Installation | Report | (Appendix | #1) | or | a | modified | delivery | schedule | with | serial | numbers | added | to | the | ||||
| designated | DLA | Point | of | Contact | (DLA | POC) | within | ten | (10) | business | days | after | delivery | and | ||||
| installation | have | been | completed. |
| 4. | If | a | device | cannot | be | delivered | and | installed | within | the | delivery | time | that | is | given, | the | Contractor |
| shall | notify | the | issuing | Contracting | Officer | as | soon | as | the | delay | is | realized, | of | the | expected | delivery | |
| date | for | the | ordered | device(s). |
| 5. | Regardless | of | installation | date, | all | devices, | including | replacement | devices, | shall | maintain | a | co‐ |
| terminus | Period | of | Performance | (PoP). |
| 6. | Upon | installation, | the | Contractor | shall | affix | on | each | device | a | sticker | with | the | following | information: |
| manufacturer’s | name, | model | number, | device | serial | number | and | toll‐free | telephone | number(s) | to | ||||
| place | service | maintenance | calls | and | order | consumable | supplies. | Additionally, | the | Contractor | shall |
add the PoP end date to DLA EMS sticker and affix to device. (DLA shall provide the DLA EMS stickers.)
7. The Contractor shall provide English‐speaking personnel at the toll‐free number(s) provided.
B. Options to Order Additional Quantities of Devices:
| 1. As | options, | the | Contractor | shall, | at | the | same | unit | price, | provide | up | to | twenty | percent | (20%) | more | ||
| co‐terminus | leased | devices | than | set | forth | at | each | CLIN | of | a | delivery | order; | provided | that | DLA | |||
| exercises | and | issues | its | options, | if | at | all, | prior | to | the | end | of | the | 24th | month | following | the | effective |
| date | of | the | contract. |
V. TRAINING
A. The Contractor shall provide either on‐site or online training, in English, as specified in the contract, to end‐users.
| B. The | Contractor | shall | coordinate | directly | with | each | command’s | POC | listed | on | the | contract | to | establish |
| the | training | schedule. |
C. Training shall include the following:
1. How to operate the basic function keys of the device.
2. How to operate special features including duplexing, enlargements, reductions, and multiple job queues.
3. Diagnosis and resolution of basic device malfunctions, including paper jams.
4. Location and procedures for installing consumables such as paper, toner, staples, etc.
| D. For | on‐site | training, | the | Contractor | shall | submit | a | Summary | of | On‐Site | Training | Report | (Microsoft | Excel | |
| format), | listing | device | serial | number, | personnel | trained | and | date | training | was | completed, | to | the | ||
| designated | DLA | POC | within | five | (5) | business | days | of | training | completion. | Initial | invoice | payment | shall | |
| not | be | released | until | this | report | is | received. |
| E. For | online | training, | the | Contractor | shall | provide | each | POC | listed | on | the | delivery | schedule | with | ||||
| manufacturer‐approved | training | that, | at | a | minimum, | covers | all | items | listed | in | paragraph | V.C. | The | link | ||||
| shall | be | accessible | by | DLA | and | its | customers | via | http | or | https. | The | Contractor | shall | submit | a | Summary | |
| of | Online | Training | Report | (Microsoft | Excel | format), | listing | device | serial | number, | personnel | trained, | ||||||
| addresses | training | link | was | sent | and | date | training | link | was | sent, | to | the | designated | DLA | POC | |||
| within | five | (5) | business | days | of | to | personnel. | Initial | invoice | payment | shall | not | be | released | until | |||
| this | report | is | received. |
| F. | In | addition | to | either | on‐site | or | online | training, | the | Contractor | shall | provide | a | quick | reference | desk | ||
| guide | (single | sheet, | 8.5” | x | 11” | paper | size, | laminated, | full | color | and | able | to | be | easily | stowed | away | with |
| the | device). | The | contractor | shall | also | provide | a | CD‐ROM/DVD | and/or | web‐based | training | (URL | printed | |||||
| on | a | sticker | to | be | placed | on | the | front | of | the | device) | to | serve | as | follow‐up | training. |
VI. MAINTENANCE
A. Service
| 1. The | Contractor | shall | maintain | each | device | at | a | minimum | 95% | monthly | available | rate. | Maintaining |
| the | devices | includes: |
a. Preventive maintenance
b. Service calls
c. Repairs
d. Troubleshooting
e. Connectivity
f. All associated labor and travel
| 2. If | a | malfunction | cannot | be | corrected | during | the | initial | service | call, | the | Contractor | shall | resolve | all |
| issues | no | later | than | ten | (10) | calendar | days | from | date | of | initial | service | call. |
| 3. | The | Contractor | shall | provide | English | speaking | service | technician | support | Monday | through | Friday | ||
| from | 8:00 | a.m. | – | 4:30 | p.m. | local | time, | with | the | exception | of | Federal | holidays. |
| 4. | The | Contractor | shall | respond | to | work | stoppage | situations | within | two | (2) | business | hours | of | a | |||
| service | call. | Work | stoppage | is | defined | as | a | required | function | of | the | device | (printing, | copying, | ||||
| scanning | or | faxing) | is | non‐operational. | A | telephone | call | (unless | it | results | in | solving | the | problem) | ||||
| shall | not | be | deemed | an | acceptable | service | response. | The | service | technician | shall | call | the | end‐user | ||||
| within | an | hour | to | discuss | the | service | problem | and | time | of | arrival. | It | is | estimated | that | 10% | of | |
| service | calls | shall | be | classified | as | “work | stoppage” | across | the | total | device | population | on | a | yearly |
basis.
| 5. | The | Contractor | shall | respond | to | non‐work | stoppage | situations | within | four | (4) | business | hours | of | |||
| a | service | call. | Non‐Work | stoppage | is | defined | as | a | required | function | of | the | device | (printing, | copying, | ||
| scanning | or | faxing) | is | degraded. | A | telephone | call | (unless | it | results | in | solving | the | problem) | shall | not | |
| be | deemed | an | acceptable | service | response. | The | service | technician | shall | call | the | end‐user | within | an | |||
| hour | to | discuss | the | service | problem | and | time | of | arrival. |
| 6. | In | the | case | of | devices | cleared | for | CLASSIFIED | material, | the | Contractor’s | repair | technicians | shall | ||
| have | a | Department | of | Defense | (DoD) | security | clearance | equal | to | or | higher | than | the | classification | of | |
| the | device | and | be | able | to | provide | verification | when | requested. |
| 7. | The | Contractor | shall | be | responsible | for | all | damages | due | to | normal | wear | and | tear | and | loss | or |
| damage | caused | by | the | Contractor | or | its | agents. |
| 8. | If | a | device | is | determined | to | be | non‐repairable, | to | include | damaged | devices, | the | Contractor | shall |
| inform | the | designated | DLA | POC | within | two | (2) | business | days | of | making | this | determination. | The | |
| Contractor | shall | deliver | and | install | a | comparable | replacement | device | within | fifteen | (15) | calendar | |||
| days | from | written | notification | from | the | Contracting | Officer. |
B. Consumable Supplies
| 1. The | Contractor | shall | provide | all | consumable | supplies | (including | staples) | necessary | for | the |
| operation | of | the | devices. | Paper | is | excluded | as | a | consumable | supply. |
| 2. The | Contractor | shall | deliver | all | required | consumable | supplies | to | the | designated | locations | listed | on | ||
| the | delivery | schedule | identified | on | the | contract, | within | three | (3) | business | days | after | receipt | of | a |
| request | for | supplies. |
VII. DEVICE RELOCATION
A. For device relocations, the Contractor shall:
| 1. Provide | device | relocation | services, | within | a | 50‐mile | radius, | for | 100% | of | the | total | number | of | devices | |
| ordered, | for | each | year | of | the | specified | period | of | performance. | (For | example, | if | there | are | 100 | |
| devices | ordered, | the | Contractor | shall | provide | relocations | for | up | to | 100 | devices | per | year. | This | could | |
| be | relocating | the | same | device | 100 | times, | relocating | 100 | different | devices | one | time | each | or | any |
| other | combination | thereof | each | year.) | The | device | relocations | shall | not | require | rigging | or | special | ||
| handling. | Devices | shall | not | be | relocated | without | written | approval | from | the | designated | DLA | POC | ||
| and | shall | be | completed | within | thirty | (30) | calendar | days | after | receipt | of | the | written | request. |
| 2. Include | the | following: | Breakdown | and | packing | of | equipment, | shipping, | uncrating, | re‐installation |
| and | end‐user | training. |
3. Be responsible for any and all repairs that may be required following any relocation performed.
| 4. Upon | completion, | obtain | customer | signature | on | the | Removal/Relocation | Report | contained | within | ||
| Appendix | #2 | and | the | MFD | Hard | Drive | Removal | Record | (Appendix | #3) | if | applicable. |
VIII. TECHNICAL REFRESH
| A. In | the | event | the | Contractor | is | no | longer | able | to | provide | the | products | proposed, | the | Contractor | may, |
| only | after | written | approval | by | the | Contracting | Officer, | remove | the | products | from | the | contract | and | ||
| provide | replacement | products | which | shall | meet | or | exceed | the | Volume | Band | requirements | as | listed | in | ||
| this | PWS, | at | the | contract | price. |
| 1. | Replacement | devices | shall | be | newer | technology | than | the | models | they | are | replacing. | If | the | ||
| Contractor | submits | new | models | for | testing, | the | devices | shall | be | “in | production” | and | not | near | “end | |
| of | life.” |
| 2. | Prior | to | delivery, | if | replacement | devices | have | not | been | previously | tested | by | DLA, | they | shall | be | |
| tested | as | outlined | in | section | XV. |
IX. DEVICE REMOVAL
A. For device removal, the Contractor shall:
| 1. Remove | all | devices | and | associated | supplies | within | thirty | (30) | calendar | days | of | contract | expiration |
| or | receipt | of | a | modification | signed | by | the | Contracting | Officer. |
2. Notify the issuing Contracting Officer as soon as any delay in device removal is realized.
| 3. Prior | to | device | removal, | remove | all | hard | drives | and | surrender | them | to | DLA | (or | its | assignee). | Upon |
| completion | of | the | hard | drive | removal, | the | Contractor | shall | obtain | the | required | signatures | on | both | ||
| the | Removal/Relocation | Report | (Appendix | #2) | and | the | MFD | Hard | Drive | Removal | Record | (Appendix | ||||
| #3). | After | the | hard | drive | has | been | removed, | ALL | classification | stickers | shall | be | removed | prior | ||
| to | device | removal/disposal. |
| 4. The | Government | reserves | the | right | to | withhold | final | payment | if | all | devices | are | not | removed | from |
| the | premises | within | thirty | (30) | calendar | days | of | contract | expiration | or | termination. |
| 5. 5. | Be | subject | to | payment | of | all | disposal | fees | incurred | by | the | Government | for | any | devices | not | removed |
| within | thirty | (30) | calendar | days | of | termination | or | expiration. | After | this | time | period, | the | devices | |||
| will | be | considered | abandoned. |
X. REPORTS
A. The Contractor shall provide the following reports:
1. Installation Report, as referenced in section IV.A.3.
2. Summary of On‐Site Training Report, as referenced in section V.D.
| 3. Device | Listing | Report | (Microsoft | Excel | format) | shall | be | submitted | via | Wide | Area | Work | Flow | ||||
| (WAWF) | to | the | DLA | POC | with | the | monthly | invoice. | The | report | shall | contain | an | accurate | listing | of | |
| all | devices | under | contract | (model, | serial | number, | location). |
4. Removal/Relocation Report, as applicable, as referenced in section VII.A.6 and IX.A.
| B. Upon | request, | the | Contractor | shall | provide | the | following | reports | within | 5 | business | days, | at | no | cost | to |
| the | Government: |
1. Usage Report (Appendix #4) shall be submitted to the DLA POC.
| 2. Response | Time | Report | shall | be | submitted | to | the | DLA | POC | and | the | Contracting | Officer. | This | report | |||
| shall | identify | the | technician’s | response | time, | defined | as | the | time | between | when | the | service | call | is | |||
| placed | and | when | the | technician | arrives | onsite | to | repair | the | equipment. | If | the | issue | is | able | to | be | |
| resolved | on | the | phone, | the | response | time | shall | be | defined | as | the | time | the | service | call | was | placed | |
| and | when | the | issue | was | resolved | over | the | phone. |
| 3. Device | Downtime | Report | shall | be | submitted | to | the | DLA | POC. | This | report | shall | identify | the | time | the | |
| equipment | was | inoperable/non‐functional. | Downtime | is | defined | as | the | time | the | service | call | is | |||||
| placed | notifying | the | Contractor’s | representative | that | the | equipment | is | inoperable/non‐functional | ||||||||
| or | when | the | technician | begins | service | on | the | equipment | if | the | device | is | operable/functional | upon | |||
| arrival. | In | addition, | the | report | shall | include | information | relative | to | the | frequency | of | service | calls, | |||
| production | volume | between | service | calls, | types | of | repairs, | as | well | as | parts | required. |
| 4. Device | Uptime | Report | shall | be | submitted | to | the | DLA | POC | and | the | Contracting | Officer. | This | report | |
| shall | identify | the | time | the | equipment | was | operable | and | available | and | will | be | used | to | verify | the |
| required | minimum | 95% | monthly | available | rate, | as | outlined | in | section | VI.A.1. |
XI. INVOICING
| A. | All | invoices | shall | be | submitted | with | the | Device | Listing | Report | via | Wide | Area | Work | Flow | (WAWF) | |
| and | shall | be | submitted | in | United | States | Dollars. | The | following | website | provides | additional | |||||
| information | regarding | WAWF | including | information | for | “vendors | getting | started” | with | the | system: | ||||||
| https://wawf.eb.mil/xhtml/unauth/help/help.xhtml. |
B. For devices that are relocated or removed, invoices shall include the Removal/Relocation Report
| (Appendix | #2) | and | the | Hard | Drive | Removal | Record | (Appendix | #3) | and | the | BOL. | Invoices | submitted |
| without | the | applicable | reports | shall | not | be | paid. |
XII. NETWORK FUNCTIONALITY
| A. DoD | policy | prohibits | the | publication | of | network | configuration | information; | therefore, | DoD | |||
| installations | shall | not | fill | out | pre‐installation | site | surveys. | The | required | information | shall | be | |
| provided | at | time | of | installation. |
| B. The | Contractor | shall | provide | devices | that | shall | operate | on | and | coexist | on | a | network | supporting | all | of |
| the | following: |
1. Internet Protocol Version 4 (IPv4),
2. Internet Protocol Version 6 (IPv6),
3. A hybrid of IPv4 and IPv6.
C. Support shall be provided for network configurations based on agency hardware/software.
XIII. NETWORK SECURITY
| A. The | Contractor | shall | provide | devices | that | can | be | configured | to | comply | with | the | current | Defense |
| Information | Systems | Agency | (DISA) | Security | Technical | Implementation | Guide | (STIG) | titled | |||||
| Multifunction | Device | and | Network | Printer | STIG | (latest | version | and | release), | available | at: |
https://cyber.mil/.
| B. Contractors | shall | monitor | industry | standard | vulnerability | sites | (e.g. | http://nvd.nist.gov/, | |||||||||
| https://www.us‐cert.gov/ncas/alerts, | http://oval.mitre.org/) | and | take | appropriate | actions | if | their | ||||||||||
| equipment | is | subject | to | a | known | vulnerability. | When | vulnerabilities | are | identified | by | the | Contractor, | ||||
| DLA | or | its | customers, | the | Contractor | shall | provide | remediation | for | distribution | to | all | installed | ||||
| equipment | in | accordance | with | USCYBERCOM | TASKORD | regulations | unless | a | different | time | period | is | |||||
| directed | by | USCYBERCOM | via | DLA. | The | TASKORD | is | For | Official | Use | Only. | The | following | is | authorized | ||
| to | be | quoted | from | the | TASKORD | for | reference: |
| 1. | Assured | Compliance | Assessment | Solution | (ACAS) | assigns | severity | scores | of | critical, | high, | medium |
| and | low | to | plug‐in | findings. |
| a. Critical | findings | reflect | discovery | of | a | common | vulnerability | and | exposure | (CVE) | that | poses | |
| significant | risk | to | the | confidentiality, | integrity, | and | availability | of | DODIN | Networks. | Actions | to | |
| mitigate | or | remediate | critical | vulnerabilities | shall | be | initiated | upon | discover | with | the | goal | of |
| mitigation/remediation | within | seven | (7) | calendar | days. |
| b. Findings | with | a | severity | score | of | high | shall | be | addressed | in | the | same | manner | as | vulnerabilities |
| addressed | via | Information | Assurance | Vulnerability | Alert | (IAVA) | directives | and | mitigated | or | |||||
| remediated | within | twenty‐one | (21) | calendar | days | of | discovery. |
| c. Findings | with | severity | scores | of | medium | and | low | shall | be | addressed | in | accordance | with | local |
| Approving | Official | (AO), | Information | System | Security | Manager | (ISSM), | or | Information | System | ||||
| Security | Officer | (ISSO) | guidance | until | further | notice. |
| d. In | all | instances, | DoD | components | shall | consider | exposure | to | threat, | mission | impact, | sensitivity |
| of | data, | and | current | mitigating | security | controls | when | prioritizing | implementation | of | fix |
actions.
| C. | In | the | event | remediation | cannot | be | achieved | within | the | mandated | timeline, | the | Contractor | shall |
| provide | a | Plan | of | Action | and | Milestones | and | receive | approval | thereof | by | the | Customer’s | agency |
| Authorizing | Official | or | designee | for | risk | acceptance. |
| D. | All | devices | shall | be | International | Organization | for | Standardization | (ISO)/International | Electrotechnical | |
| Commission | (IEC) | 15408 | (Common | Criteria) | certified | IAW | CNSSP‐11 | using | the | National | Information |
| Assurance | Partnership | (NIAP) | approved | criteria | or | equivalent. |
| 1. | A | device | shall | be | acceptable | if | it | is | included | on | either | the | NIAP | CCEVS | Product | Compliant | List |
| (https://www.niap‐ccevs.org/Product/) | or | Common | Criteria | Portal | Certified | Products | list |
(http://www.commoncriteriaportal.org/products/).
| 2. | All | devices | shall | have | current | ISO/IEC | 15408 | certification | and | recertification, | if | applicable, | before | |
| the | Contractor | can | schedule | lab | time. | See | section | XIV. | Guidance | for | Common | Criteria | Maintenance | |
| and | Reevaluation | is | available | at: | https://www.niap‐ |
ccevs.org/documents_and_guidance/ccevs/scheme‐pub‐6.pdf
| E. | All | devices | shall | be | capable | of | obtaining | accreditation | through | the | Risk | Management | Framework | (RMF) | ||
| for | DoD | Information | Technology | (IT). | As | part | of | this, | the | Contractor | agrees | to | provide | all | requested | |
| information | and | work | in | good | faith | with | DLA | so | the | DLA | customers | can | expeditiously | obtain | RMF | |
| accreditation | prior | to | device | delivery | and | installation. | The | Contractor | shall | also | provide | devices | for | |||
| vulnerability | and | STIG | testing | to | DLA | or | customer’s | site. | The | Contractor | further | agrees | that | if | the | |
| proposed | device(s) | does | not | obtain | RMF | accreditation, | the | contractor | shall | remove | the | device(s). | ||||
| Information | regarding | RMF | is | found | in | Risk | Management | Framework | (RMF) | for | DoD | Information | ||||
| Technology | (IT) | Instruction | 8510.1 | dated | 12 | March | 2014: | |||||||||
| http://www.dtic.mil/whs/directives/corres/pdf/851001_2014.pdf. | In | order | to | maintain | RMF | and | ||||||||||
| STIG | compliance, | devices | are | required | to | be | delivered | with | the | most | up‐to‐date | firmware, | as | outlined | in | |
| section | II.A.11. |
| F. | The | Contractor | shall | supply | a | SMARTCARD | Public | Key | Infrastructure | (PKI) | Solution | which | is | compliant | ||
| with | DODI | 8520.03 | and | NIST | FIPS | 201 | (PIV) | standards. | The | contractor | shall | provide | card | readers | that | |
| shall | read | and | process | all | approved | CAC | and | PIV | cards. | The | Contractor | shall | maintain | compliance | with | |
| DoD‐wide | SMARTCARD | and | DoD | PKI | standards, | and | support | all | approved | physical | cards | during | the | full | ||
| lease | period. |
| G. | The | contractor | shall | provide | a | SMARTCARD | PKI | Solution | with | SIPRNet | token | capability, | which | is | ||
| compliant | with | DoD | requirements | for | PK‐enabling | and | interoperability | as | set | forth | in | DODI | 8520.02. | |||
| The | Contractor | shall | provide | card | readers | that | shall | read | and | process | all | approved | SIPRNet | token | ||
| cards. | The | Contractor | shall | provide | device | support | systems | that | incorporate | the | use | of | PKI | for | ||
| encryption | of | information | in | transit | or | at | rest. | The | Contractor | shall | provide | devices | that | are | compatible | |
| with | 3.3 | volt | SafeNet | SC650 | token | and | that | are | compatible | with | the | 90Meter | Middleware | solution | for | |
| CAC, | known | as | CAC | Smart | Card | Manager‐90. | The | Contractor | shall | maintain | compliance | with | DoD | wide | ||
| SIPR | and | DoD | PKI | standards, | and | support | all | approved | physical | cards | and | firmware | during | the | full | |
| lease | period. | For | current | DODI | instructions | go | to: |
http://www.dtic.mil/whs/directives/corres/ins1.html.
| H. | The | Contractor | shall | ensure | that | CAC/SIPR | token | authentication | is | available | for | scanning, | printing | and |
| copying | and | shall | be: |
1. Capable of digitally signing emails using the senders DoD PKI Certificate(s).
2. Capable of encrypting emails using the receivers DoD PKI Certificate(s).
3. Capable of scan to file on networked devices.
4. In compliance with Homeland Security Presidential Directive‐12 (HSOP‐12).
I. The Contractor shall produce certificates of compliance, if requested.
XIV. TESTING
| A. All | devices | proposed | in | response | to | the | contract | shall | be | tested | for | compliance | with | Network | Security |
| as | defined | in | section | XIII | after | award. |
| B. The | estimated | time | for | testing | is | twenty | (20) | business | days. | Testing | and | approval | shall | be | performed | |
| by | the | DLA | Information | Operations | EMS | Division | in | conjunction | with | the | Contractor’s | assistance. | The | |||
| Contractor | shall | provide | onsite | engineering | assistance | and | other | support | necessary | to | configure, | setup, | ||||
| and | test | the | equipment | as | needed. |
| 1. DLA | tests | devices | to | meet | DoD | RMF | and | STIG | Compliance. | If | all | devices | pass | the | preliminary | ||
| testing | process, | DLA | shall | submit | a | compliance | memorandum | to | the | Contractor | informing | them | |||||
| that | the | devices | have | passed | the | preliminary | testing | process. | In | some | cases, | prior | to | being | added | to | |
| the | DLA | customer’s | network, | additional | certification | procedures | and | testing | shall | be | required | prior | |||||
| to | risk | acceptance. | If | required | by | DLA, | the | Contractor | shall | deliver | test | devices | to | the | DLA | customer | |
| prior | to | proceeding | with | installation. | DLA | shall | exercise | due | diligence | to | assist | with | technical | ||||
| mitigation | and | resolve | any | questions | and/or | concerns | raised | by | that | agency | during | the | testing | ||||
| review | process. |
| 2. If | the | devices | do | not | pass | any | of | the | testing | procedures | for | any | reason, | DLA | shall | not | proceed | with |
| installation | of | said | devices | at | the | customer | locations | and | DLA | shall | terminate | the | contract. |
C. A device shall not be tested if it cannot be assigned to one of the Volume Bands as outlined in section V.
| D. The | devices | shall | be | delivered | with | all | required | accessories, | software, | firmware, | etc. | Output | paper | |
| handling | accessories | are | not | tested | and | shall | not | be | delivered | to | the | lab. |
E. Approved devices previously submitted to DLA for testing are not required to be re‐tested.
| F. The | Contractor | shall | deliver | the | devices | for | each | Volume | Band | series, | under | each | Functional | Area, | to | ||
| DLA | Information | Operations | J67E | located | at | 430 | Mifflin | Avenue, | Building | 430, | New | Cumberland, | PA | ||||
| 17071, | for | testing, | at | no | cost | to | the | government. | Delivery | coordination | shall | take | place | within | five | (5) | |
| business | days | of | contract | award. |
| G. The | Contractor | shall | resolve | non‐compliance | issues | as | quickly | as | possible. | If | the | issues | cannot | be | |||
| resolved | within | fourteen | (14) | calendar | days, | the | test | shall | be | suspended. | After | the | non‐compliance | ||||
| issues | are | resolved | by | the | Contractor, | the | suspended | session | shall | be | scheduled | when | lab | time | is | next | |
| available. | If | requested | by | DLA, | the | Contractor | shall | remove | their | devices | from | the | lab | to | avoid | delaying | |
| the | next | scheduled | test. |
| H. For | all | devices | tested | and | placed | on | the | DLA | contract, | the | Contractor | shall | collaborate | with | the | DLA |
| Configuration | Manager | to | develop | the | testing | results | package. | The | Contractor | shall | develop | the | device | |||
| Implementation | Guide. | The | Implementation | Guide | shall | provide | step‐by‐step | instructions | and | |||||||
| screenshots | to | configure | the | devices | in | accordance | with | the | testing | results. | Government | acceptance | of | |||
| the | Implementation | Guide | is | at | the | discretion | of | the | DLA | EMS | Division. |
| I. The | security | requirements | set | forth | in | this | PWS | are | minimum | device | specifications | and | have | been | |
| identified | as | the | basic | requirements | common | across | Government | agencies. | These | are | the | minimum | |||
| security | requirements | applicable | to | all | devices | awarded | under | this | contract. | Each | ordering | activity | may | ||
| have | its | own | hardware/software | acceptance | processes. | All | devices | shall | be | subject | to | ordering | activity | ||
| hardware/software | evaluation | processes. | If | the | device | fails | a | security | evaluation, | the | Contractor | may | |||
| select | a | different | technology | or | mitigate | the | failed | controls | to | fulfill | this | requirement. | The | Contractor | |
| shall | be | available | to | meet | with | the | information | technology | (IT) | and | security | personnel | at | a | mutually |
| convenient | time | during | the | evaluation | process, | and | shall | identify | a | mutually | acceptable | solution. | The | ||
| Contractor | shall | provide | the | necessary | equipment | or | expertise | to | complete | security | testing | and | |||
| integration | into | the | existing | environment. | The | customer | agency | may | require | the | Contractor | to | ship | ||
| devices | to | a | specific | location | for | testing | at | time | of | award. |
| J. If, | during | the | life | of | the | contract, | a | requirement | in | section | XII | and | XIII | is | changed, | updated | or | revised, |
| the | Contractor | shall | comply | with | the | most | current | version | of | the | requirement. |
| K. The | Contractor | shall | remove | all | hardware | from | the | DLA | test | lab | within | ten | (10) | calendar | days | upon |
| notification | of | test | completion. |
XV. SUPPLY CHAIN RISK MANAGEMENT
| A. As | part | of | its | quote, | the | Contractor | shall | provide | written | documentation | demonstrating | how | the | |||
| integrity | and | security | of | all | equipment, | components | thereof, | repair | parts | and | consumables | it | will | |||
| provide | and/or | use | in | performing | this | contract | will | meet | the | standards | set | forth | in | National | Institute | of |
| Standards | and | Technology | (NIST) | Special | Publication | 800‐61. | This | documentation | shall | clearly | ||||||
| demonstrate | how | the | Contractor | is | taking | effective | measures | to | mitigate | the | risks | of | foreign | |||
| intelligence | services, | terrorist | groups, | or | others | from | inserting | unwanted | functionality | into | the | supplies | ||||
| and/or | services | DLA | receives | through | this | contract. | Additionally, | this | documentation | shall | provide | |||||
| specific | details | of | what— |
1. Policies the Contractor has in place to prevent both (a) the use of counterfeit or altered equipment, components thereof, consumables and parts and (b) their introduction into the Contractor’s supply chain;
2. Security procedures the Contractor uses to track the chain of custody of equipment, components thereof, consumables and parts, to include while this material is in storage and in transit; and
| 3. Steps | the | Contractor | takes | to | ensure | the | integrity | and | authenticity | of | new, | refurbished | or |
| remanufactured | equipment, | components | thereof, | repair | parts | and | consumables | to | prevent | ||||
| tampering | so | they | will | perform | according | to | specifications | without | additional | unwanted |
functionality.
B. The Contractor shall continuously meet the standards of NIST Special Publication 800‐61 while taking
| effective | measures | to | mitigate | the | risks | of | foreign | intelligence | services, | terrorist | groups, | or | others | from |
| inserting | unwanted | functionality | into | the | supplies | and/or | services | provided | through | this | contract. | |||
| Upon | request, | the | Contractor | shall | provide | written | documentation | meeting | all | requirements | set | forth | ||
| in | part | A, | above. |
XVI. ENTERPRISE MANAGEMENT TOOL
| A. The | Contractor | shall | provide | an | Enterprise | Management | Tool | that | manages | devices. | The | |
| management/monitoring | software | tool | shall | reside | within | the | customers’ | network | in | order | to | monitor, |
| manage | and | generate | usage | to | facilitate | continued | fleet | optimization | reports. |
| B. The | Enterprise | Management | Tool | shall | use | SNMP | V3. | The | management | tool | shall | monitor | meter | reads, | |
| volume, | usage, | supply | levels, | and | issue | notifications/alerts | about | device | status. | The | notifications/alerts | ||||
| shall | notify | designated | personnel | when | to | order | consumables | and | request | maintenance/repair |
services.
XVII. INSTALLATION SECURITY REQUIREMENTS
| A. The | Contractor | shall | comply | with | all | rules | and | regulations | to | obtain | Government | installation | access | in |
| order | to | meet | all | response | times | identified | within | the | PWS. |
| B. The | Contractor | shall | comply | with | Government | base | access | requirements | as | set | forth | in | the | base/ |
| command | regulations. |
| C. The | Contractor | shall | be | responsible | for | any | and | all | fees | associated | with | the | application | process | and/or |
| enrollment | to | access | any | installation | or | facility.. |
| D. For | devices | cleared | for | CLASSIFIED | material, | the | Contractor’s | repair | technicians | shall | have | a | DoD | ||
| security | clearance | equal | to | or | higher | than | the | classification | of | the | device | and | shall | provide | verification |
| when | requested. |
XVIII. GENERAL CONDITIONS
| A. The | Contractor | shall | assign | a | single | point | of | contact | (POC) | to | coordinate | with | the | Contracting | Officer | in | ||
| all | aspects | of | this | contract | within | three | (3) | business | days | of | receipt | of | the | award. | The | Contractor | shall | |
| provide | its | assigned | POC’s | name, | title, | business | address, | phone | number | and | address | to | the | |||||
| Contracting | Officer. |
| B. The | Contractor | shall | comply | with | the | Health | Insurance | Portability | and | Accountability | Act | (HIPAA) |
| when | installing | devices | at | Government | medical | sites. |
| C. The | Contractor | shall | comply | with | the | Section | 508 | accessibility | requirements. | By | submission | of | its | offer, | ||
| the | Contractor | affirms | that | its | Electronic | Information | Technology | (EIT) | supplies | and | services | are | ||||
| accessible | as | outlined | in | the | law, | the | standard, | and | FAR | Subpart | 39.2. | The | Contractor | shall | complete | the |
| Voluntary | Product | Accessible | Template | (VPAT®) | document | (Appendix | #5) | with | their | proposal. |
XIX. APPENDICES
A. Appendix #1: Installation Report
B. Appendix #2: Removal/Relocation Report
C. Appendix #3: Hard Drive Removal Record
D. Appendix #4: Usage Report
E. Appendix #5: VPAT® Template
Appendix #1 INSTALLATION REPORT
Activity Name Customer Address
Customer POC Phone # Customer POC Email
Contract #
CLIN# Manufacturer Model # Serial # Install
Date
Building
Number
Floor Number/ Room Number
Continue on the back, if needed. Note: A Delivery Schedule or Spreadsheet can be used as an attachment to this install report.
Customer Accepting Receipt of Device (Print): Customer Signature
CLIN# Manufacturer Model # Serial # Install
Date Building Number
Floor Number/ Room Number
(Page 2 – Appendix #1)
Appendix #2 REMOVAL/RELOCATION REPORT
Activity Name Customer Address
Customer POC Phone # Customer POC Email
Contract #
CLIN# Manufacturer Model # Serial # Date Building# / Floor # / Room #
Continue on the back, if needed. Note: A Delivery Schedule or Spreadsheet can be used as an attachment to this install report.
*HARD DRIVE REMOVAL (SIGNATURES REQUIRED)*
Customer Approving Removal of Device (Print Name):
Must be the EMS DLA Information Operations POC, or designated representative.
Customer Signature
Information Assurance Manager (IT) Receipt of HD (Print
Name):
Information Assurance Manager (IT)
Signature
Contractor Technician (Print Name): Technician Signature
CLIN# Manufacturer Model # Serial # Date Building# / Floor # / Room #
(Page 2 ‐ Appendix #2)
Appendix #3 Equipment Management Solutions Hard Drive Removal Record
Form log number
FY ‐ SEQ#
DLADCSVC ‐ ‐
Contract number
Customer (Agency/Command)
Drive manufacturer and model
Hard drive serial number
MFD serial number
Date removed
Printed name of technician removing hard drive
Signature of technician removing hard drive
Drive classification ☐ Classified (up to Secret) ☐ Unclassified (CUI)
Hard drive disposition
☐ Retained by customer ☐ Shipped to DLA Information Operations ☐ Shipped to NSA
Printed name of EMS Division representative accepting drive for DLA Information Operations or customer accepting drive
Signature of EMS Division representative accepting drive for DLA information Operations or customer accepting drive
Printed name/title of person sanitizing hard drive
Signature of person sanitizing hard drive
Date destroyed
Printed name/title verification after Degaussing and Crushing
Signature for verification after degaussing and crushing
Degausser/crusher location ☐ DSI HD‐1T (Phil) ☐ EM/Garner Model TS‐1 (NOR)
☐ SEM Model 0101(Phil) ☐ SEM Model 0101(NOR)
Post‐Sanitization destination (recycling center)
Contact phone number to degausser operator and verification personnel
Appendix #4 USAGE REPORT
Monochrome Color
Contract
Model
Serial #
Install Date
(MM/DD/YYYY)
Beginning
Meter
Ending
Usage
Beginning
Ending
Usage
Was Meter
Read
Estimated?
(Yes/No)
Appendix #5
[Company] Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Name of Product/Version:
Report Date:
Product Description:
Contact Information:
Notes:
Evaluation Methods Used:
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included | In | Report | ||||||||
| Web | Content | Accessibility | Guidelines | 2.0 | Level | A | (Yes | / | No | ) |
| Level | AA | (Yes | / | No | ) |
| Level | AAA | (Yes | / | No | ) |
| Web | Content | Accessibility | Guidelines | 2.1 | Level | A | (Yes | / | No | ) | |
| Level | AA | (Yes | / | No | ) | ||||||
| Level | AAA | (Yes | / | No | ) |
| Revised | Section | 508 | standards | published | January | 18, | 2017 | and | corrected |
| January | 22, | 2018 |
(Yes / No )
| EN | 301 | 549 | Accessibility | requirements | suitable | for | public | procurement | of | ICT |
| products | and | services | in | Europe, | ‐ | V3.1.1 | (2019‐11) |
(Yes / No )
Terms
The terms used in the Conformance Level information are defined as follows:
| Supports: | The | functionality | of | the | product | has | at | least | one | method | that | meets | the | criterion | without | known |
| defects | or | meets | with | equivalent | facilitation. |
| Partially | Supports: | Some | functionality | of | the | product | does | not | meet | the | criterion. | ||||||
| Does | Not | Support: | The | majority | of | product | functionality | does | not | meet | the | criterion. | |||||
| Not | Applicable: | The | criterion | is | not | relevant | to | the | product. | ||||||||
| Not | Evaluated: | The | product | has | not | been | evaluated | against | the | criterion. | This | can | be | used | only | in | WCAG |
2.0 Level AAA.
Revised Section 508 Report Notes:
Chapter 3: Functional Performance Criteria (FPC) Notes:
Criteria Conformance Level Remarks and Explanations
| 302.1 | Without | Vision. | |||||||||
| Where | a | visual | mode | of | operation | is | provided, | ICT | shall | provide | at |
| least | one | mode | of | operation | that | does | not | require | user | vision. |
| 302.2 | With | Limited | Vision. | |||||||||
| Where | a | visual | mode | of | operation | is | provided, | ICT | shall | provide | at | least |
| one | mode | of | operation | that | enables | users | to | make | use | of | limited | vision. |
| 302.3 | Without | Perception | of | Color. | Where | a | visual | mode | of | operation | is |
| provided, | ICT | shall | provide | at | least | one | visual | mode | of | operation | that |
| does | not | require | user | perception | of | color. |
| 302.4 | Without | Hearing. | |||||||||
| Where | an | audible | mode | of | operation | is | provided, | ICT | shall | provide | at |
| least | one | mode | of | operation | that | does | not | require | user | hearing. |
| 302.5 | With | Limited | Hearing. | |||||||||
| Where | an | audible | mode | of | operation | is | provided, | ICT | shall | provide | at | |
| least | one | mode | of | operation | that | enables | users | to | make | use | of | limited |
hearing.
| 302.6 | Without | Speech. | |||||||||
| Where | speech | is | used | for | input, | control, | or | operation, | ICT | shall | |
| provide | at | least | one | mode | of | operation | that | does | not | require | user |
speech.
| 302.7 | With | Limited | Manipulation. | Where | a | manual | mode | of | operation | |||
| is | provided, | ICT | shall | provide | at | least | one | mode | of | operation | that | does |
| not | require | fine | motor | control | or | simultaneous | manual | operations. |
| 302.8 | With | Limited | Reach | and | Strength. | ||||||
| Where | a | manual | mode | of | operation | is | provided, | ICT | shall | provide | at |
| least | one | mode | of | operation | that | is | operable | with | limited | reach | and |
| limited | strength. |
| 302.8 | With | Limited | Reach | and | Strength. | ||||||
| Where | a | manual | mode | of | operation | is | provided, | ICT | shall | provide | at |
| least | one | mode | of | operation | that | is | operable | with | limited | reach | and |
| limited | strength. |
| 302.9 | With | Limited | Language, | Cognitive, | and | Learning | Abilities. | ICT | |
| shall | provide | features | making | its | use | by | individuals | with | limited |
| cognitive, | language, | and | learning | abilities | simpler | and | easier. |
Chapter 4: Hardware Notes:
Criteria Conformance Level Remarks and Explanations
| 402.1 | General. | (Closed | Functionality | ) | |||||
| ICT | with | closed | functionality | shall | be | operable | without | requiring | the |
| user | to | attach | or | install | assistive | technology | other | than | personal |
| headsets | or | other | audio | couplers, | and | shall | conform | to | 402. |
Heading cell – no response required Heading cell – no response required
| 402.2.1 | Information | Displayed | On‐Screen. | ||||||
| Speech | output | shall | be | provided | for | all | information | displayed | on‐ |
screen.
| 402.2.2 | Transactional | Outputs. | ||||||
| Where | transactional | outputs | are | provided, | the | speech | output | shall |
| audibly | provide | all | information | necessary | to | verify | a | transaction. |
| 402.2.3 | Speech | Delivery | Type | and | Coordination. | ||||||
| Speech | output | shall | be | delivered | through | a | mechanism | that | is | readily | |
| available | to | all | users, | including, | but | not | limited | to, | an | industry | standard |
| connector | or | a | telephone | handset. | Speech | shall | be | recorded | or | digitized | |
| human, | or | synthesized. | Speech | output | shall | be | coordinated | with |
Criteria Conformance Level Remarks and Explanations
| information | displayed | on | the | screen. | |||||
| 402.2.4 | User | Control. | |||||||
| Speech | output | for | any | single | function | shall | be | automatically | |
| interrupted | when | a | transaction | is | selected. | Speech | output | shall | be |
| capable | of | being | repeated | and | paused. |
| 402.2.5 | Braille | Instructions. | |||||||||
| Where | speech | output | is | required | by | 402.2, | braille | instructions | for | ||
| initiating | the | speech | mode | of | operation | shall | be | provided. | Braille | shall | |
| be | contracted | and | shall | conform | to | 36 | CFR | part | 1191, | Appendix | D, |
| Section | 703.3.1. |
| 402.3.1 | Private | Listening. | |||||||||
| Where | ICT | provides | private | listening, | it | shall | provide | a | mode | of | |
| operation | for | controlling | the | volume. | Where | ICT | delivers | output | by | an | |
| audio | transducer | typically | held | up | to | the | ear, | a | means | for | effective |
| magnetic | wireless | coupling | to | hearing | technologies | shall | be | provided. |
| 402.3.2 | Non‐private | Listening. | |||||||||||
| Where | ICT | provides | non‐private | listening, | incremental | volume | control | ||||||
| shall | be | provided | with | output | amplification | up | to | a | level | of | at | least | 65 |
| dB. | A | function | shall | be | provided | to | automatically | reset | the | volume | to | ||
| the | default | level | after | every | use. |
| 402.4 | Characters | on | Display | Screens. | |||||||||
| At | least | one | mode | of | characters | displayed | on | the | screen | shall | be | in | a |
| sans | serif | font. | Where | ICT | does | not | provide | a | screen | enlargement | |||
| feature, | characters | shall | be | 3/16 | inch | (4.8 | mm) | high | minimum | based | |||
| on | the | uppercase | letter | “I”. | Characters | shall | contrast | with | their | ||||
| background | with | either | light | characters | on | a | dark | background | or | dark | |||
| characters | on | a | light | background. |
| 402.5 | Characters | on | Variable | Message | Signs. | ||||
| Characters | on | variable | message | signs | shall | conform | to | section | 703.7 |
| Variable | Message | Signs | of | ICC | A117.1:2009. |
| 403.1 | Biometrics | |||||||||
| Where | provided, | biometrics | shall | not | be | the | only | means | for | user |
| identification | or | control. |
| 404.1 | Preservation | of | Information | Provided | for | Accessibility | |||
| ICT | that | transmits | or | converts | information | or | communication | shall | not |
| remove | non‐proprietary | information | provided | for | accessibility | or | shall | ||
| restore | it | upon | delivery. |
| 405.1 | Privacy. | ||||||||||||
| The | same | degree | of | privacy | of | input | and | output | shall | be | provided | to | all |
| individuals. | When | speech | output | required | by | 402.2 | is | enabled, | the | ||||
| screen | shall | not | blank | automatically. |
| 406.1 | Standard | Connections | ||||||||
| Where | data | connections | used | for | input | and | output | are | provided, | at |
| least | one | of | each | type | of | connection | shall | conform | to | industry |
| standard | non‐proprietary | formats. |
| 407.2 | Contrast. | |||||||||
| Where | provided, | keys | and | controls | shall | contrast | visually | from | ||
| background | surfaces. | Characters | and | symbols | shall | contrast | visually | |||
| from | background | surfaces | with | either | light | characters | or | symbols | on | a |
| dark | background | or | dark | characters | or | symbols | on | a | light | background. |
| 407.3.1 | Tactilely | Discernible. | |||||||
| Input | controls | shall | be | operable | by | touch | and | tactilely | discernible |
| without | activation. |
| 407.3.2 | Alphabetic | Keys. | ||||||||
| Where | provided, | individual | alphabetic | keys | shall | be | arranged | in | a | |
| QWERTY‐based | keyboard | layout | and | the | ‘‘F’’ | and | ‘‘J’’ | keys | shall | be |
| tactilely | distinct | from | the | other | keys. |
| 407.3.3 | Numeric | Keys. | ||||||||
| Where | provided, | numeric | keys | shall | be | arranged | in | a | 12‐key | ascending |
| or | descending | keypad | layout. | The | number | five | key | shall | be | tactilely |
| distinct | from | the | other | keys. | Where | the | ICT | provides | an | alphabetic |
| overlay | on | numeric | keys, | the | ||||||
| relationships | between | letters | and | digits | shall | conform | to | ITU?T | ||
| Recommendation | E.161 |
| 407.4 | Key | Repeat. | ||||||||||
| Where | a | keyboard | with | key | repeat | is | provided, | the | delay | before | the | |
| key | repeat | feature | is | activated | shall | be | fixed | at, | or | adjustable | to, | 2 |
| seconds | minimum. |
Criteria Conformance Level Remarks and Explanations
| 407.5 | Timed | Response. | |||||||||||
| Where | a | timed | response | is | required, | the | user | shall | be | alerted | visually, | as | |
| well | as | by | touch | or | sound, | and | shall | be | given | the | opportunity | to | indicate |
| that | more | time | is | needed. |
| 407.6 | Operation. | (General） | ||||||||||
| At | least | one | mode | of | operation | shall | be | operable | with | one | hand | and |
| shall | not | require | tight | grasping, | pinching, | or | twisting | of | the | wrist. | The | |
| force | required | to | activate | operable | parts | shall | be | 5 | pounds | (22.2 | N) |
maximum.
| 407.7 | Tickets, | Fare | Cards, | and | Keycards. | ||||||
| Where | tickets, | fare | cards, | or | keycards | are | provided, | they | shall | have | an |
| orientation | that | is | tactilely | discernible | if | orientation | is | important | to | ||
| further | use | of | the | ticket, | fare | card, | or | keycard. |
| 407.8.1 | Vertical | Reference | Plane. | |||||||||
| Operable | parts | shall | be | positioned | for | a | side | reach | or | a | forward | reach |
| determined | with | respect | to | a | vertical | reference | plane. | The | vertical | |||
| reference | plane | shall | be | located | in | conformance | to | 407.8.2 | or | 407.8.3. |
| 407.8.1.1 | Vertical | Plane | for | Side | Reach. | Where | a | side | reach | is |
| provided, | the | vertical | reference | plane | shall | be | 48 | inches | (1220 | mm) |
| long | minimum. |
| 407.8.1.2 | Vertical | Plane | for | Forward | Reach. | Where | a | forward | reach | is | |
| provided, | the | vertical | reference | plane | shall | be | 30 | inches | (760 | mm) | long |
minimum.
| 407.8.2 | Side | Reach. | ||||||||||||
| Operable | parts | of | ICT | providing | a | side | reach | shall | conform | to | 407.8.2.1 | |||
| or | 407.8.2.2. | The | vertical | reference | plane | shall | be | centered | on | the | ||||
| operable | part | and | placed | at | the | leading | edge | of | the | maximum | protrusion | |||
| of | the | ICT | within | the | length | of | the | vertical | reference | plane. | Where | a | ||
| side | reach | requires | a | reach | over | a | portion | of | the | ICT, | the | height | of | that |
| portion | of | the | ICT | shall | be | 34 | inches | (865 | mm) | maximum. |
| 407.8.2.1 | Unobstructed | Side | Reach. | |||||||||
| Where | the | operable | part | is | located | 10 | inches | (255 | mm) | or | less | beyond |
| the | vertical | reference | plane, | the | operable | part | shall | be | 48 | inches | (1220 | |
| mm) | high | maximum | and | 15 | inches | (380 | mm) | high | minimum | above | the |
floor.
| 407.8.2.2 | Obstructed | Side | Reach. | |||||||||
| Where | the | operable | part | is | located | more | than | 10 | inches | (255 | mm), | but |
| not | more | than | 24 | inches | (610 | mm), | beyond | the | vertical | reference | plane, | |
| the | height | of | the | operable | part | shall | be | 46 | inches | (1170 | mm) | high |
| maximum | and | 15 | inches | (380 | mm) | high | minimum | above | the | floor. | The | |
| operable | part | shall | not | be | located | more | than | 24 | inches | (610 | mm) | beyond |
| the | vertical | reference | plane. |
| 407.8.3 Forward | Reach. | |||||||||||||
| Operable | parts | of | ICT | providing | a | forward | reach | shall | conform | to | ||||
| 407.8.3.1 or | 407.8.3.2. | The | vertical | reference | plane | shall | be | centered, | ||||||
| and | intersect | with, | the | operable | part. | Where | a | forward | reach | allows | a | |||
| reach | over | a | portion | of | the | ICT, | the | height | of | that | portion | of | the | ICT |
| shall | be | 34 | inches | (865 | mm) | maximum. |
| 407.8.3.1 | Unobstructed | forward | reach. | |||||||||
| Where | the | operable | part | is | located | at | the | leading | edge | of | the | maximum |
| protrusion | within | the | length | of | the | vertical | reference | plane | of | the | ICT, | the |
| operable | part | shall | be | 48 | inches | (1220 | mm) | high | maximum | and | 15 | |
| inches | (380 | mm) | high | minimum | above | the | floor. |
| 407.8.3.2 | Obstructed | Forward | Reach. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .