832573199 PWS - DRAFT.docx

PERFORMANCE WORK STATEMENT (PWS)

Award

Tracking Number:

1. Contracting Officer’s Representative (COR).

a. Primary COR. See DITCO Additional Text G1 - Points of Contact

b. Alternate COR. See DITCO Additional Text G1 - Points of Contact

c. Property Administrator See DITCO Additional Text G1 - Points of Contact

2. Contract or Task Order Title. Security System Maintenance

3. Background. The Defense Information Systems Agency (DISA), through the Defense Information Technology Contracting Organization (DITCO), requires 24/7 on-call support services and preventative maintenance (PM) for an existing Johnson Controls CCURE 9000 security access system, badging stations, a Bosch Intrusion Detection System (IDS), and a Milestone video system. These systems are installed at the DITCO facility located at Scott Air Force Base to meet Department of Defense (DoD) Manual 5200.01, Volume 1.

4. Objectives: The objective is to provide 24/7 on-call maintenance and routine PM for the currently installed Johnson Controls Incorporated CCURE 9000 Security Access System, badging stations, Bosch IDS, and Milestone XProtect Video Management System (including all currently connected cameras), as well as sound masking. This maintenance will maintain the security integrity of the DITCO facility in accordance with DOD Manual 5200.01, Volume 1.

5. Scope. The scope of this PWS includes 24/7 on-call maintenance and routine PM for the currently installed Johnson Controls Incorporated CCURE 9000 Security Access System, badging stations, Bosch IDS, and Milestone XProtect Video Management System (including all currently connected cameras), and the sound masking system.

6. Performance Requirements. The contractor shall supply all parts, labor, materials, equipment, tools, consumables, supervision, and other resources necessary to accomplish all tasks in accordance with the manufacturer’s recommended requirements and the tasks outlined below.

6.1 Task 1. Routine/Preventative Maintenance. All materials listed within PWS attachment 1, Presently Installed System Equipment List, shall be included as a part of PM. Collectively referred within this document as “Security System”. Provide report on all maintenance performed. The report must contain at a minimum the date, time, tasks performed, software configuration changes, parts replaced, issues identified with cost estimates if hardware replacement is required,system backup completion date. Contractors performing maintenance on-site will be accessing CUI standalone information system in performance of their duties. Investigation and training requirements are listed in Section 11.

6.1.1 The contractor shall perform PM each month to include labor to perform scheduled repairs and preventative maintenance on the system’s hardware and software. PM will be scheduled and performed monthly.

6.1.2 The contractor shall provide central call center (24x7) to monitor two emergency exit doors and monitor secure room during non-duty hours to include the weekends and holidays and receive trouble calls and guarantee a 24-hour (or less) scheduled on-site response to trouble calls from the Government.

6.1.3 The PM shall include alarm and error checking, testing of readers, door functionality, light replacements, battery checks, restoration of software, data backups, and performance of any other routine maintenance as needed to keep the Security System in good working order. All potential repairs found while performing preventative maintenance shall be brought to the attention of the COR. The COR will approve the repair and determine if the repair is classified as emergency or routine. If determined as an emergency, the contractor will complete the work within 24 hrs. If determined as routine maintenance, the contractor will complete the work within 7 days.

6.1.4 The contractor shall procure and maintain the Security System software and access to technical support, software updates, and licensing for all systems if applicable..

6.1.5 The contractor shall maintain, update, troubleshoot, or replace the currently installed Security System equipment as required or requested by the Government.

6.1.6 The contractor shall maintain a stock of 100 or be able to acquire HID cards within 7 days with a unique facility code which is compatible with the currently installed Security System. Government will program cards with personnel information.

6.1.7 The contractor shall provide generalized technical guidance on upgrades/upkeep of the Security System to include possible modifications to any component of the Security System when required or when requested by the Government. Providing justifications and cost estimates to the COR for evaluation/approval prior to execution.

6.1.8 Create a monthly backup of the Ccure 9000 access system database to an external secondary storage media (USB or external hard drive). The secondary storage media shall be labeled in accordance with DOD Manual 5200.01 Vol. 2 and provided to the COR once prepared for storage until the next backup.

Constraints: Work schedule 5x8, T-1 Security Clearance, Ccure, Milestone XProtect, and Bosch certification, 2 years’ experience.

Deliverables:

6.2 Task 2. Unscheduled Maintenance. The contractor shall provide 24 hours a day, 7 days a week unscheduled, on call, maintenance and repair of the existing Security system to include all the hardware, firmware and software associated with the existing system. Unscheduled maintenance requests will be submitted by the government through the contractor call center. When work is performed repairs or replacements must be the same or equal to size and performance of the equipment and products being replaced. See materials listed within PWS attachment 1, Presently Installed System Equipment List, to provide guidance on what parts might require replacement. Repairs/replacements will be approved by the COR prior to installation.

6.2.1 The contractor shall provide a central call center to receive trouble calls and guarantee a 24-hour (or less) scheduled response time to trouble calls from the Government.

6.2.2 The contractor shall maintain bench stock of 1 or more commonly required S-300 and CK720 parts in stock and/or have the ability to acquire less commonly required parts within 32 hours (or less) as needed to successfully maintain the current Security System. Note: Ccure 9000 parts are only available from the manufacturer, Johnson Controls and the current system is a conglomerate of both type parts. The successful bidder will require an account with the manufacturer to obtain authentic Ccure 9000 parts.

6.2.3 The contractor shall provide generalized technical guidance on possible upgrades and the required upkeep of the Security System. To include modification, unscheduled maintenance, configuration changes, and end of life to any component of the Security System when required or when requested by the Government. Providing justifications and cost estimates to the COR for evaluation/approval prior to execution.

Deliverables:

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR.

7. Performance Standards.

Minimum Acceptable:

Problems or rework are resolved within 30 days.

Calculation:

Routine inspection of deliverable products and services by Government COR.

8. Incentives. Not Applicable (N/A)

9. Place of Performance.

Mission Location: DISA DITCO Scott Air Force, Illinois.

Place of Performance: Government Site, Bldg. 3600, 2300 East Drive, Scott AFB, IL 62225. the Contractor shall ensure that work is completed effectively, and that mission needs and requirements are met, without degradation of services. Also, the contractor may be required to account for the physical location of their personnel should this information be requested by the COR.

10. Period of Performance. One-year base period with four one-year option periods.

Recognized Federal Holidays: The contractor is not required to perform services on Federal Holidays (as specified on the U.S. Office of Personnel Management website), unless otherwise specified by the COR.

11. Security Requirements. The work will be UNCLASSIFIED. The following security requirements shall apply to this effort.

The contractor shall coordinate visits with site Point of Contract (POC)s providing at least a 72-hour notice (or according to each site security requirements) prior to any site access. Contractor personnel without security clearances performing any task under this PWS must be escorted by cleared Defense Information Systems Agency (DISA) personnel (civilian, military, or contractor).

References:

a. DISA End User Access Agreement, 11 February 2021

b. DISA Policy Letter, Unauthorized Connections to Network Devices, 11 September 2013

c. DISA Instruction 240-110-8, Information Security

d. DISA Instruction 240-110-36, Personnel Security

e. DISA Instruction 240-110-38, Industrial Security

f. DISA Instruction 240-110-43, Insider Threat Program

g. DISA Instruction 630-230-19, Cybersecurity

h. DoD Manual 5200.01, Vol 1-2 Information Security Program, 24 February 2012

i. DoD Manual 5200.02, Procedures for the DoD Personnel Security Program, 3 April 2017

j. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

k. 32 CFR Part 117, “National Industrial Security Program Operating Manual (NISPOM)”, 24 February 2021

l. Security Executive Agent Directive 4, National Security Adjudicative Guidelines, 8 June 2017

m. DoDM 5400.07, Freedom of Information Act Program

n. DoDI 5230.24, “Distribution Statements for DoD Technical Information,” January 10, 2023

o. DoD Instruction 8510.01, “Risk Management Framework for DoD Systems,” July 19, 2022

11.1 Background Investigation. All personnel performing on or supporting a DISA contract/order in any way shall be U.S. citizens. The personnel security requirements for this contract/order cover the individuals supporting the Task Areas delineated in the table below. Contractor personnel must possess the interim or final background investigation eligibility delineated in the table below when performance starts.

PWS Task / Subtask

11.2 Investigation Requirements. This contract shall cover unclassified environments, but the DITCO data is considered controlled; therefore, the DITCO facility is a limited-access facility. Unless the contractor possesses a final Secret clearance, contractor personnel will be required to sign in at front lobby and be issued a badge to be escorted. All personnel requiring routine unescorted access under this contract/order shall undergo a favorably adjudicated Tier 1 (T1) investigation as a minimum requirement. Enrollment into Continuous Evaluation current within 5 years and reflected in Defense Information System for Security (DISS), would meet the requirement for a current Periodic Reinvestigation (PR). DISA HQ Fort Meade Security Industrial Security, J16, (301) 225-4039 to obtain a favorable T-1 which is submitted with the SF 85 for the background investigation for Public Trust in a non –sensitive access for a no-escort badge in Bldg. 3600 non-open storage area. This badge must be displayed while working in the building. Contractor personnel will be required to obtain a base pass to enter Scott AFB. A background check of contractor personnel may be required, and conducted by, the US Government as a condition for access to the base and/or to DITCO building 3600. Unfavorable results of the background check will result in denial of access to Scott AFB and to DITCO building 3600. Any violation of security by contractor personnel could result in termination of this contract. Drivers must have a valid driver’s license and be able to show current proof of insurance and vehicle registration upon request. Contractor personnel must be a US citizen.

11.2.1 The contractor is required to have personnel with an interim or final background investigation T1 (as specified in the table located in section 11.2) at contract start date. If contractor personnel are replaced during performance of the contract, replacement personnel should also have interim or final background investigation Tier 1 (T1).

11.3 Visit Authorization. Visit requests shall be processed and verified through the DISS to Security Management Office (SMO) DKADAL. DISS visits for contracts/orders are identified as “Other” or “TAD/TDY” and will include the Contract/Order Number of the contract/order in the Additional Information section. Contractors that do not have access to DISS may submit visit authorizations by e-mail in a password protected .pdf to the COR/ACOR specified in PWS/SOW Section 1.0.

*Prior coordination with the DISA COR should be made via email to ensure the Visit Authorization Letter (VAL)/ Visit Authorization Request (VAR)/ Visit Termination Notification (VTN) process is agreed upon and properly secure.

11.3.1 VAR Package. VARs must be received via email and require pre-approval from the assigned DISA COR five business days in advance of the report date. The VAL/VAR/VTN should be sent via email to the appropriate COR. The VAL/VAR/VTN should be sent using in a locked “Zip” file in one e-mail and then followed up by another e-mail with the password to unlock the Zipped file, because it contains sensitive information covered by the Privacy Act.

Documents to include in the VAR Package:

1. Inter-office Memorandum (IOM)

2. DISS verification of Visit Authorization by Security Manager (if available)

3. (Optional: see NOTE below) Contractor VAL signed by the Contractor Facility Security Officer (FSO) or Program Manager.

NOTE: If DISS is not available, the VAL must contain the following information on the company letterhead

· Company name, address, telephone number, facility security clearance

· CAGE CODE (if available)

· Contract/Order Number

· Name, SSN, date and place of birth, and citizenship of the employee intending to visit, email address, and phone number

· Certification of personnel background investigation authorizations required for the visit (type of investigation & date and adjudication date & agency)

· Name of COR/Alt COR

· Dates or period the VAL is to be valid (i.e., Start date / End date)

11.3.2 VTN Package. The Contractor FSO or PM will forward a VTN letter to the DISA COR identified in the PWS/TO/Sub for all employees leaving the contract/task order/subcontract.

11.3.2.1 In addition, the DISA CORs and security managers shall inform the DISA Security Office when contractor personnel are removed for cause from a contract supporting DISA. This step is being added to prevent contractor personnel removed for security related issues from returning to DISA without appropriate vetting. This step will also provide security with pertinent information to make an informed decision regarding potential contractor employees’ access to secure facilities and sensitive information. “For Cause” is information regarding an individual that falls into one or more of the actions or incidents that are within one of the 13 adjudicative guidelines as cited in the Security Executive Agent Directive (SEAD) 4:

a. Allegiance to the United States

b. Foreign Influence

c. Foreign Preference

d. Sexual Behavior

e. Personal Conduct

f. Financial Considerations

g. Alcohol Consumption

h. Drug Involvement and Substance Misuse

i. Psychological Conditions

j. Criminal Conduct

k. Handling Protected Information

l. Outside Activities

m. Use of Information Technology Other actions:

• Incidents involving violence in the workplace or harassment.

• Misuse of time.

• Inspector General or General Counsel related inquiries.

• Failure to comply with security policies and procedures.

• Other reasons that prompted removal of a contractor.

The VTN must contain the following information on company letterhead

· Company name, address, telephone number, facility security clearance

· CAGE CODE (if available)

· Contract/Order Number

· Name, SSN, date and place of birth, and citizenship of the employee, email address, phone number

· Date contractor CAC was collected

· Name of COR/Alt COR

· Termination Date

· Reason for Termination: <insert reason from the 13 adjudicative guidelines, other actions, or type “No longer working on contract”>

*Any VAL/VAR submitted without the above information will be denied. *

11.4 Security Contacts. DISA Security Personnel can be contacted for Industrial or Personnel Security related issues at (301) 225-4039 or via mail at:

Defense Information Systems Agency

Defense Information Systems Agency

ATTN: J-16, Industrial Security

ATTN: J-16, Personnel Security

Command Building

Command Building

6910 Cooper Ave.

6910 Cooper Ave.

Fort Meade, MD 20755-7088

Fort Meade, MD 20755-7088

For Center or Directorate-specific security related matters, contact the Directorate or Center Security Manager at:

Name: Jessica Mathis Phone Number: 618-418-6735 E-mail: Jessica.a.mathis2.civ@mail.mil

11.5 Information Security and other miscellaneous requirements.

11.5.1 Contractor personnel shall comply with all local security requirements including entry and exit control for personnel and property at the Government facility.

11.5.2 Contractor employees shall be required to comply with all Government security regulations and requirements. Initial and periodic safety and security training and briefings will be provided by Government security personnel. Failure to comply with Government security regulations and requirements shall require the company to provide the Government with a written remediation/corrective action plan; furthermore, failure to comply with such requirements can be cause for removal and the contractor will not be able to provide service on this contract/order.

11.5.3. Contractor employees with an incident report in DISS who have had their access to classified suspended will not be permitted to fill positions requiring access to classified information on a DISA contract/order.

11.5.4 The Contractor shall not divulge any information, classified or unclassified, about DoD files, data processing activities or functions, user identifications, passwords, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor shall observe and comply with the security provisions in effect at the DoD facility. Identification shall be worn and displayed as required.

11.5.5 The authority for the contractor personnel to regain access must be granted by DISA Chief of Security.

11.5.5.1 DISA retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the Government.

11.5.5.2 DISA retains the right to revoke contractor personnel access to DISA facilities and networks, who violates one or more Security Personnel Adjudicative guidelines, harassment or violence in the workplace while assigned to a contract clearly conflict with the interest of the Government.

11.5.5.3 If contractor employee is accused of violating state or federal laws and/or Government professional conduct policies or regulations, then the Government may require that such contractor employee be removed from Government premises and/or that such contractor employee be removed from supporting this contract, pending the duration and outcome of a Government investigation if the Contracting Officer finds that the conduct or violation alleged has the potential to negatively interfere with contract performance or operations at a Government facility. Only the Contracting Officer can make such a request on behalf of the Government. Removal of contractor employee shall not negatively impact contract performance.

11.5.6 Contractor personnel will generate or handle documents that contain Controlled Unclassified Information (CUI) at the Government and/or contractor facility. Contractor personnel will generate or handle documents that contain Proprietary, Contract Sensitive, or similarly designated information at the Government and/or contractor facility. Contractor personnel will have access to, generate, and handle UNCLASSIFIED at the Government and/or contractor location as listed in the place of performance section of this document. All contractor deliverables shall be marked in accordance with DoDM 5200.01, Vol. 1, DoD Information Security Program: Overview, Classification, and Declassification; DoDM 5200.01, Vol. 2, DoD Information Security Program: Marking of Information; DoDI 5200.48, Controlled Unclassified Information (CUI) and DoDM 5400.07, Freedom of Information Act Program, unless otherwise directed by the Government. The contractor shall comply with the provisions of the DoD Industrial Security Manual for handling classified material and producing deliverables. The contractor shall comply with DISA Instruction 630-230-19, Cybersecurity.

11.5.7 The Contractor shall afford the Government access to the contractor’s facilities, installations, operations, documentation, databases and personnel used in performance of the contract/order. Access shall be provided to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of data or to the function of information technology systems operated on behalf of DISA or DoD, and to preserve evidence of computer crime.

12. Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI). N/A

13. Other Pertinent Information or Special Considerations. The contractor is responsible for notifying the COR prior to contract award of any barriers to complete the contract according to the performance requirements listed under line item 7. Site visits are required before any proposal is accepted by the Government. Site visits are arranged by calling the COR at 618-418-6735. All Structural/Electrical work must be performed In Accordance With (IAW) Base, Local, State, Industry, and Federal regulations/National Electric Codes (NEC). The Government is not responsible for any tools/equipment/supplies left unattended in the facility at any time. No tax can be charged to the US Government.

The contractor shall provide technician(s)s with certifications applicable to hardware/software to be maintained. Microsoft, Ccure 9000, Milestone Video, CCTV cameras, and Bosch Intrusion Detection System.

a. Identification of Possible Follow-on Work. None.

b. Identification of Potential Conflicts of Interest (COI). None.

c. Identification of Non-Disclosure Requirements. The contractor shall obtain and maintain Non-Disclosure Agreements (NDA) for each employee assigned to the contract. Initial NDAs shall be signed within one week of the contract award, and NDAs shall be kept current through the entirety of the period of performance as employee turnover occurs. The contractor shall ensure that all employees assigned to the contract have executed NDAs on file as of the date of the Monthly NDA Status Report, which shall include names and NDA status of all current employees assigned to the contract.

[Use Non-Disclosure Agreement for DISA located HERE]

Deliverable:

*Standard Distribution: 1 copy of the transmittal letter with the deliverable to the Primary COR.

d. Packaging, Packing and Shipping Instructions. None.

e. Inspection and Acceptance Criteria. N/A

f. Property Accountability. N/A

g. Transitioning. N/A

h. Supply Chain Risk Management (SCRM). N/A

13. Section 508 Accessibility Standards.

Accessibility Requirements Tool ICT Accessibility Requirements Statement per Section 508 of the Rehabilitation Act Solicitation Development Security Equipment

E206 Hardware E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E208 Support Documentation and Services E208.1 General. Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E301 General E301.1 Scope. The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

E302 Functional Performance Criteria

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.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.

401 General

401.1 Scope. The requirements of Chapter 4 shall apply to ICT that is hardware where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

Exception from E401.1 Scope: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.

402 Closed Functionality

402.1 General. 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.

402.2 Speech-Output Enabled. ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.

Exceptions from E402.2:

1. Variable message signs conforming to 402.5 shall not be required to be speech-output enabled.

2. Speech output shall not be required where ICT display screens only provide status indicators and those indicators conform to 409.

3. Where speech output cannot be supported due to constraints in available memory or processor capability, ICT shall be permitted to conform to 409 in lieu of 402.2.

4. Audible tones shall be permitted instead of speech output where the content of user input is not displayed as entered for security purposes, including, but not limited to, asterisks representing personal identification numbers.

5. Speech output shall not be required for: the machine location; date and time of transaction; customer account number; and the machine identifier or label.

6. Speech output shall not be required for advertisements and other similar information unless they convey information that can be used for the transaction being conducted.

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 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.

Exception from E402.2.5 Braille Instructions: Devices for personal use shall not be required to conform to 402.2.5.

402.3 Volume. ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.

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 (incorporated by reference, see 702.6.1).

403 Biometrics

403.1 General. Where provided, biometrics shall not be the only means for user identification or control.

Exception from E403.1 General: Where at least two biometric options that use different biological characteristics are provided, ICT shall be permitted to use biometrics as the only means for user identification or control.

404 Preservation of Information Provided for Accessibility

404.1 General. ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.

405 Privacy

405.1 General. 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 Standard Connections

406.1 General. 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 Operable Parts

407.1 General. Where provided, operable parts used in the normal operation of ICT shall conform to 407.

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 Input Controls. At least one input control conforming to 407.3 shall be provided for each function.

Exception from E407.3 Input Controls: Devices for personal use with input controls that are audibly discernable without activation and operable by touch shall not be required to conform to 407.3.

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 (incorporated by reference, see 702.7.1).

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.

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. 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 Reach Height and Depth. At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type.

1. 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.

0. 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.

0. 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.

1. 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.

1. 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.

1. 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.

1. 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.

2. 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.

2. 407.8.3.2 Obstructed Forward Reach. Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).

2. 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach. The height of the operable part shall conform to Table 407.8.3.2.1.

2. 407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach. Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

408 Display Screens

408.1 General. Where provided, display screens shall conform to 408.

408.2 Visibility. Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed.

408.3 Flashing. Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.

Exception from E408.3 Flashing: Flashes that do not exceed the general flash and red flash thresholds defined in WCAG 2.0 (incorporated by reference, see 702.10.1) are not required to conform to 408.3.

409 Status Indicators

409.1 General. Where provided, status indicators shall be discernible visually and by touch or sound.

410 Color Coding

410.1 General. Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

411 Audible Signals

411.1 General. Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response 412 ICT with Two-Way Voice Communication

412.1 General. ICT that provides two-way voice communication shall conform to 412.

412.2 Volume Gain. ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.

Exception from E412.2 Volume Gain: ICT conforming to 412.2 shall not be required to conform to 402.3.

412.2.1 Volume Gain for Wireline Telephones. Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.

412.2.2 Volume Gain for Non-Wireline ICT. A method for increasing volume shall be provided for non-wireline ICT.

412.3 Interference Reduction and Magnetic Coupling. Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.

1. 412.3.1 Wireless Handsets. ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).

1. 412.3.2 Wireline Handsets. ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1).

412.4 Digital Encoding of Speech. ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1).

412.5 Real-Time Text Functionality. [Reserved].

412.6 Caller ID. Where provided, caller identification and similar telecommunications functions shall be visible and audible.

412.7 Video Communication. Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.

413 Closed Caption Processing Technologies

413.1 General. Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.

1. 413.1.1 Decoding and Display of Closed Captions. Players and displays shall decode closed caption data and support display of captions.

1. 413.1.2 Pass-Through of Closed Caption Data. Cabling and ancillary equipment shall pass through caption data.

414 Audio Description Processing Technologies

414.1 General. Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.

1. 414.1.1 Digital Television Tuners. Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard.

1. 414.1.2 Other ICT. ICT other than digital television tuners shall provide audio description processing.

415 User Controls for Captions and Audio Descriptions

415.1 General. Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.

Exception from E415.1 General: Devices for personal use shall not be required to conform to 415.1 provided that captions and audio descriptions can be enabled through system-wide platform settings.

1. 415.1.1 Caption Controls. Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.

1. 415.1.2 Audio Description Controls. Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.

503 Applications

503.1 General. Applications shall conform to 503.

602 Support Documentation

602.1 General. Documentation that supports the use of ICT shall conform to 602.

602.2 Accessibility and Compatibility Features. Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

602.3 Electronic Support Documentation. Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

602.4 Alternate Formats for Non-Electronic Support Documentation. Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

603 Support Services

603.1 General. ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

603.2 Information on Accessibility and Compatibility Features. ICT support services shall include information on the accessibility and compatibility features required by 602.2.

603.3 Accommodation of Communication Needs. Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

CCTV equipment E206 Hardware E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E207 Software E207.1 General. Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5 Exception from E207.1 General: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.

E207.2 WCAG Conformance. User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

Exceptions from E207.2 WCAG Conformance:

1. Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.

1. Non-web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.

1. Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

E207.3 Complete Process for Non-Web Software Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.

E208 Support Documentation and Services E208.1 General. Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E301 General E301.1 Scope. The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

E302 Functional Performance Criteria

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.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.

401 General

401.1 Scope. The requirements of Chapter 4 shall apply to ICT that is hardware where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

Exception from E401.1 Scope: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.

402 Closed Functionality

402.1 General. 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.

402.2 Speech-Output Enabled.