S150042_IROC_SOO_Draft_09152015.docx

U.S. Forest Service AG-024B-S-15-0042 IROC Statement of Objectives

Agile Development of the Interagency Resource Ordering Capability (IROC) Statement of Objectives (SOO)

AG-024B-S-15-0042

U.S. Forest Service Version: September 15, 2015

Table of Contents

1.0 INTRODUCTION

The Resource Ordering and Status System (ROSS) has been in use since 2003. ROSS will be retired and replaced with a new web-based system, the Interagency Resource Ordering Capability (IROC), which will transform how the U.S. Forest Service and the interagency wildland fire community order, track and manage resources to fight wildland fires and respond to all-hazard incidents. Through this Statement of Objectives (SOO), the U.S. Forest Service seeks information technology (IT) expert services to develop and maintain the IROC.

2.0 BACKGROUND

Established in 1905, the U.S. Forest Service (FS) has the responsibility for stewardship of more than 193 million acres of the nation’s forests and grasslands; for developing and communicating scientific knowledge through research and development that leads to informed natural resource decision making; for delivering technical assistance through state and private forestry programs; and for sharing knowledge and experience with others in the global community through international forestry. Performing this mission requires effective collection, organization, analysis, and delivery of many different types of information. The Forest Service currently has a workforce whose size varies by season with a maximum of approximately 42,000 employees distributed among:

a. Nine National Forest System (NFS) Regions (Regions);

b. Five Research and Development Stations (Stations) and the Forest Products Lab;

c. The Northeastern Area State and Private Forestry;

d. The International Institute of Tropical Forestry;

e. National headquarters in Washington, D.C. (the Washington Office (WO)); and

f. Forest Service managed Job Corps Centers

The National Interagency Fire Center (NIFC) is located in Boise, Idaho, and manages interagency preparations for and responses to wildland fires and all-hazard incidents. The Interagency Fire Community includes the Forest Service, Department of the Interior (DOI), Bureau of Land Management (BLM), National Park Service (NPS), Bureau of Indian Affairs (BIA), US Fish and Wildlife Service (USFWS), State Forestry Agencies (all 50 states), and Municipal Agencies.

The Resource Ordering and Status System (ROSS) is an application to mobilize and deploy a multitude of resources, including qualified individuals, teams, aircraft, equipment and supplies in place to fight wildland fires and respond to all-hazard incidents. FS is the managing agency for ROSS. The application is used to ensure that the limited number of resources available are deployed to where they are needed most to protect people and property. It is also used to support the basic needs of the first responders and support personnel at an incident location by processing orders and replenishing everything from supplies to sanitation and catering. ROSS continues to be the main tool for placing and tracking orders of resources and supplies.

As mentioned in the introduction, ROSS has been in use since 2003. It is currently a software package that must be downloaded to individual computers rather than a modern, web-based tool. ROSS is currently in steady state maintenance and is not undergoing further design efforts. The U.S. Forest Service and the interagency fire community have agreed that ROSS should be replaced by a newly developed Interagency Resource Ordering Capability (IROC).

3.0 IT ENVIRONMENT

IROC may be hosted by the Contractor as part of a turn-key solution. However, the following section includes information on available Forest Service hosting. As this is a Statement of Objectives (SOO) and not a Statement of Work (SOW), the Forest Service is open to innovative approaches that offer the best value to the Government.

Legacy ROSS is hosted on the National Enterprise Support System (NESS) computer server hardware, as are the Development, Practice, and Training application configurations. System administration for all NESS computer server hardware is performed through a separate contract. NESS is hosted at the USDA National Information Technology Center (NITC) located in Kansas City, Missouri and at an alternate operating site at the National Earth Resources Observation and Science (EROS) Center located in Sioux Falls, South Dakota. It is not expected that on-site support will be required at these or other locations.

NESS provides consistent 24x7 architecture, interoperability, compatibility, and integration across organizational, agency and department boundaries for the hosted applications in the production environment. NESS uses VMware virtual machines, shared storage capabilities and consolidated database services to support ROSS. NESS facilitates management of computing resources, including: hardware acquisition, software and OS licensing. NESS provides the development site for the ROSS Contractor to develop, test and conduct quality control on changes prior to release.

NESS provides a representative to work with the ROSS team, advising in planning and coordinating activities such as application patching and upgrades. The NESS representative attends application meetings and Change Control Boards (CCBs). The NESS System Analysts (SA) assists ROSS in implementation activities when changes to the server, operating system, or middleware are required. The NESS SAs provide oversight in all system and operating system changes through the NESS Project Change Request (PCR) and CCB process.

The NESS team is responsible for the steady state operation of the infrastructure, servers, operating systems, database, and middleware. The NESS team provides the standards and versions that applications need to maintain to ensure a steady state enterprise environment.

NESS has a 99% up-time production metric and historically has had an average of eight hours of down-time annually.

Integrated Data Exchange

In 2012, the Forest Service and the Department of the Interior signed a Memorandum of Understanding (MOU) to create an inter-departmental process for managing Wildland Fire Information and Technology (WFIT). WFIT’s governance model ensures end users are driving solutions and services, that solutions are interoperable and interconnected and that the end user experience is simplified. For more on WFIT, visit: http://www.forestsandrangelands.gov/WFIT/library.shtml.

WFIT authorized the Integrated Reporting of Wildland-Fire Information (iRWin), middleware that facilitates data exchange capabilities between existing agency applications is used to manage incidents related to wildland fire. ROSS is currently integrated into iRWin, and the IROC must also integrate with iRWin. Once an application’s data is integrated into the iRWin data exchange platform, applications are required to incorporate iRWin O&M releases. iRWin issues one major release annually, usually occurring in March. Occasionally, iRWin will apply a service pack for minor bug fixes.

The contractor shall propose standardized Application Program Interface (API) formats for connecting to other systems (qualification, supply, CAD, etc.). The government shall have three weeks to provide comments.

Operations and Maintenance

Sustainment operations and maintenance will be provided in the option years by the selected development contractor.

High Fire Season

High fire season is defined as April 1st through October 31st. While fires occur throughout the U.S. all year, this period is historically the peak of the fire season and when fire-fighting activities impact all aspects of Forest Service and Interagency operations and workload. As such, all releases and changes shall be planned, and approved by the CO or COR, to minimize impact on fire season workload.

Access Portal

The NESS Application Portal (NAP) (https://nap.nwcg.gov/NAP/) serves as the access point for ROSS, and will serve as the access point for the IROC.

Data Integration

The IROC will include a support data management tool (SDMT) capability to administer primarily static information that is consumed by the IROC including but not limited to catalogs of supplies and equipment, agreements, contracts, compacts, and organizational information.

The IROC and/or SDMT must connect with multiple federal and state and local applications to pull and push data. Applications include:

Federal Government Managed Applications eISuite http://eisuite.nwcg.gov A web browser enabled I-Suite application for use at the Incident Command Post (ICP) and in agency offices to manage emergency incidents and planned events. eISuite serves as the “HR” system at an incident.

Incident Qualification and Certification System (IQCS) http://iqcsweb.nwcg.gov An interagency information system that tracks training and certifications for federal emergency responders.

Virtual Incident Procurement (VIPR) http://www.fs.fed.us/business/incident/vipr.php A web-based Forest Service application designed to administer preseason Incident Blanket Purchase Agreements. VIPR has the functionality to solicit, award, and manage preseason I-BPAs, and was implemented nationwide in January of 2009.

State and Local Managed Applications

Incident Qualification System (IQS) http://www.vdatasys.com Application that allows the user to track incident qualifications, experience, tasks books and fitness levels for individuals within various organizational levels. Used by state and local partners.

Other

Standard Functional Specifications for “Law Enforcement Computer Aided Dispatch (CAD) Systems”.

https://it.ojp.gov/documents/LEITSC_Law_Enforcement_CAD_Systems.pdf CAD standards established by the Law Enforcement Information Sharing Program

4.0 REQUIREMENT ARTIFACTS

The table below contains the artifacts associated with this project. They shall serve as a roadmap for this contract. During the agile sprints, additional requirements may become apparent (requirements in the table are estimated to be 80% complete). The Contracting Officer must approve any reduction in requirements captured in the documents of the table below. All artifacts, except for the Charter, shall be kept up-to-date by the Contractor throughout the life of the contract.

The story board personas show the high level functions that are conducted by users and the system. Alternate story boards may be identified as the project moves into design cycles.

The business process models contain the “happy paths” of resource ordering. Alternate paths may be identified as the project moves into design cycles.

The IROC solution requirements specification (requirements traceability matrix format) is an in-depth analysis of stakeholder needs for IROC gathered during discovery. This shall serve as a roadmap and its elements shall be continuously updated. It shall also be used to develop test plans.

The story board personas show the high level functions that are conducted by users and the system to manage support data. Alternate story boards may be identified as the project moves into design cycles.

The business process models contain the “happy paths” of resource ordering. Alternate paths may be identified as the project moves into design cycles.

The SDMT solution requirements specification (requirements traceability matrix format) is an in-depth analysis of stakeholder needs for support data associated with IROC gathered during discovery. This shall serve as a roadmap and its elements shall be continuously updated. It shall also be used to develop test plans.

The reports mock-up focuses on data and historical information about reports which will help to define what information the end user needs.

The interactive mock-ups includes an interactive interface and gives a general look / feel of what type of user experience is desired.

*Note: RDMT is synonymous with SDMT The logical data model provides a graphical representation of the data requirements.

The data dictionary defines data elements and establishes the relationship(s) between data.

5.0 OUTCOMES

High-Level Outcome:

Develop an IROC, which will replace the current ROSS application. The IROC will:

1. Meet defined leadership and business/end user needs to ensure the application fully supports the fire community’s resource ordering and management needs.

2. Be intuitive and easy to use and navigate through such that training and help desk needs are nearly non-existent.

3. Facilitate accurate resource reference and transactional data through a data management tool that integrates with a host of applications and systems to ingest and push data, minimizes the need for data reentry in the IROC, creates data stewardship and maximizes reporting and data subscription capabilities.

4. Maximize off-the-shelf software to minimize O&M and DME efforts.

5.1. Project Management

a) The highest quality contract project management support is provided to FS to ensure delivery of a timely, high quality, cost effective project that meets FS goals and objectives.

b) Communication from the Contractor ensures that the Forest Service COR has accurate and up-to-date information on project status, progress and challenges.

c) Communication and change management expertise are highly effective, professional, well-articulated to support end users in embracing IROC.

5.2. Validation

a) Existing documentation is leveraged to validate desired IROC capabilities.

b) IROC required functionality and logic is defined through additional user stories/storyboards that meets end user needs and requirements.

5.3. Backlog/Sprint Structure

a) A thorough backlog/sprint structure serves as the conceptual architecture and release schedule for development of the IROC.

b) The backlog/sprint structure leads to the efficient and effective development of the IROC within the constraints identified in Section 7.0, Constraints.

5.4. Migration Plan

a) Successful, detailed migration planning ensures that end users are fully supported throughout the agile development of the IROC with minimal disruption to the end users.

b) Historical data from the current ROSS application is migrated into the IROC.

5.5. Sprints

a) Fully functional, tested software packages are developed, that when integrated with other software packages will be useable software releases that meet user stories/storyboard requirements.

5.6. Releases

a) Software is released in accordance with the sprint cycle and migration plan that meets or exceeds the Contractor’s proposed performance measures.

b) A fully functioning IROC meets all user stories/storyboard requirements and is accepted by the end user community per user acceptance testing and surveys.

c) Superior system functionality is maintained after launch through corrections of errors and bugs in accordance with the Contractor’s proposed performance measures.

5.7. Training

a) Users and other stakeholders understand how to use IROC through system usability training. It is expected that the majority of these services will be provided remotely (e.g. Recorded Videos, GoToMeeting, LiveMeeting etc.). topics will include: new releases, account management; data entry; system administration; and individual workflow and operational processes. Please note that training videos will be used for system documentation as providing documentation in this format is much more cost effective and effective then preparing voluminous paper based documentation.

b) End users can expertly use IROC through various modes of available training, including role-based training.

c) Forest Service helpdesk teams have requisite knowledge to resolve end user issues.

d) All training is compatible with the Learning Management System (LMS) standards for easy dissemination within the existing LMS.

5.8. Transition

a) The Government or the subsequent O&M contractor have all applicable information, deliverables, access and lessons learned through a cooperative and collaborative transition period for a seamless transition.

6.0 OPTIONAL OUTCOMES

6.1. Turn-key hosting of IROC is provided in a FedRAMP compliant hosting center.

6.2. Operations and Maintenance (O&M) Support

a) IROC production is fully functional, up-to-date and available 24x7x365 to meet the needs of end users.

b) IROC practice and training instances are fully functional, up-to-date and available 18x7x365.

c) IROC training materials are maintained and updated as necessary.

7.0 CONSTRAINTS

The IROC must:

· Meet NIST and FS IT Security requirements, including receiving an Authority to Operate (ATO).

Meet and be compatible with NESS infrastructure requirements. The General Support System (GSS) for the application, Fire National Enterprise Support System (Fire NESS) will collaborate with the Next Generation team to ensure that needs for hardware, software, and connectivity are met in a completely and timely manner.

· Comply with Section 508 accessibility requirements. The Contractor must provide a completed Voluntary Product Accessibility Template (VPAT) that demonstrates compliance with 508 accessibility requirements with each release of the solution.

· Support up to 2,000 users for core IROC capabilities and support up to 10,000 users for status updates and regular use.

· Integrate and/or push/pull data with the applications and systems mentioned in Section 3.0 of this SOO.

· Be compatible with Apple and Android mobile devices.

· Be properly accessible on multiple browsers, including at a minimum, the Forest Service specific Internet Explorer, general Internet Explorer, Firefox, Chrome and Safari.

· Have appropriately timed releases to avoid major changes during high fire season.

· Be fully operational by the end of year two of the contract. Fully functional means that all agreed upon functionality is completed so that end users are able to properly use IROC without issue.

Requirements Constraints

A data management capability must be developed within three months of contract award to maintain consistent data, for use by data stewards of support catalogs, compacts, agreements, contracts and organizational hierarchy information to clearly identify the authoritative data and always seek to incorporate the true source of data in all decision-making functions. The organizational hierarchy information shall be migrated over from the OIS system.

Provide specific APIs for categories of data Formats for Resource Reference Data will adhere to NWCG Standards; all standards should be in place within two months of the IROC contract award. The IROC will need to be able to “subscribe” to the reference data from the data management capability, and be able to obtain historical copies of the information for reporting purposes.

IROC must continue to support Altaris CAD with a repository feature.

IROC must adhere to the Standard Functional Specifications for “Law Enforcement Computer Aided Dispatch (CAD) Systems”.

IROC will provide reporting capabilities to legacy data and integrate with the existing database.

General

· The Contractor must include a cover letter with all deliverables, which may contain the company logo and name. All other deliverables including but not limited to code, artifacts and filenames shall be void of any company identification.

8.0 INSPECTION AND ACCEPTANCE

The Government will perform Inspection and Quality Assurance in accordance with the contract Quality Assurance Surveillance Plan (QASP). The Government has the right to perform periodic surveillance of the Contractor to ensure that the Contractor’s work products and Quality Control processes are in compliance with the contract requirements. The Government and the Contractor will coordinate Government surveillance in a manner that will not unduly delay or disrupt the Contractor’s performance of the contract.

9.0 PERIOD OF PERFORMANCE

The base period of performance shall extend for one year from the date of award. Option periods may be exercised at the discretion of the Government. The Government may extend the term of this contract by written notice to the Contractor, in accordance with the option terms and conditions in the contract.

10.0 PLACE OF PERFORMANCE

Contractor shall perform the services at its facilities. It is preferred, but not required, that that the Contractor have a presence in Boise, Idaho to increase interaction with the Forest Service and minimize travel costs.

11.0 TRAVEL

The majority of meetings will occur virtually via teleconference or videoconference. Some meetings will require in-person attendance. If a meeting must be in-person, the Contractor shall receive advance approval from the COR. All travel costs shall comply with the Federal Travel Regulation. Travel to Boise, Idaho is expected as part of this project. Travel shall be part of the firm fixed price proposed by the Offeror and will not be reimbursed separately. The Offeror must specify the number of trips, duration of each trip and number of travelers in its proposal.

12.0 GOVERNMENT FURNISHED PROPERTY (GFP)/ GOVERNMENT FURNISHED INFORMATION (GFI)

The Government will provide two laptop computers to ensure access to Forest Service software and systems. LincPass access will be provided to the primary users of those laptops.

The Government will provide access (in accordance with established Government Security Regulations and Agency Policy) to hosting and development environments. Access to these environments will be through a VPN connection. These environments are located at the NESS and EROS.

The Government will provide information collected through its exploration of ROSS replacement options, including feedback from stakeholders, storyboards and functional requirements developed to date.

13.0 CONTRACTOR FURNISHED PROPERTY

The Contractor shall provide all personnel, equipment, tools, materials, supervision, facilities, connectivity, and non-personal services necessary to meet the objectives defined in this SOO except as specified above.

14.0 KEY PERSONNEL

The Contractor shall employ and maintain personnel in the management and key staff positions who meet the minimum requirements for each of the skill levels to which they are assigned, and shall be capable of performing the functions described in a competent and professional manner.

Project Manager: The Contractor shall designate a Project Manager (PM) as the single point of contact (POC) for management of the Contractor’s efforts. The PM shall be the single Contractor representative responsible for all issues, concerns, or problems. The PM shall readily respond to questions, concerns, and comments. The PM shall proactively alert the Government to potential contractual issues.

In addition to the Project Manager, the Contractor shall also designate as key personnel:

Usability Specialist Scrum Master

The Contractor agrees that no Key Personnel substitutions or additions will be made unless necessitated by compelling reasons including, but not limited to, illness, death, maternity leave, or termination of employment. In such event, the Contractor must promptly provide the information required below to the CO and COR for approval prior to any substitution or addition of Key Personnel. Proposed substituted Key Personnel must have qualifications that meet, or exceed the qualifications of the persons replaced, and be an approved replacement by the Government. Whenever possible, fully compliant requests for substitutions or additions must be submitted, in writing to the CO and COR for approval at least fifteen business days in advance of the proposed change. The CO will notify the Contractor within fifteen business days after receipt of all required information of the decision on substitutions or additions. All disapprovals will require re-submission of another substitution or addition within fifteen days by the Contractor.

Request for Key Personnel changes must provide a detailed explanation of the circumstances necessitating the proposed substitutions or additions, a complete resume for the person to be substituted or added, and any other information requested by the COR.

Noncompliance with the provisions of this clause will be considered a material breach of the terms and conditions of the contract for which the Government may seek any and all appropriate remedies, to include termination for default.

15.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

Forest Service COR: To be named at time of award.

The COR is responsible for the technical direction of the contract work. In no event, however, will any understanding, agreements, modification, change order, or other matter deviating from the terms of this contract be effective or binding upon the Government unless formalized by proper contractual document executed by the Contracting Officer prior to completion of the contract.

The Contracting Officer shall be informed as soon as possible of any actions or inactions by the contractor or the Government which may affect the price, required delivery or completion times stated in the contract, so that identified desired changes and outside influences on the contract may be modified as necessary. Whenever, in the opinion of the contractor, the COR requests efforts outside the scope of the contract, the contractor shall advise the COR. If the COR persists and there still exists a disagreement as to proper contractual coverage, the Contracting Officer should be notified immediately, preferable in writing if time permits. Proceeding with work without proper contractual coverage could result in non-payment.

A copy of the COR delegation letter shall be provided to the Contractor after award.

16.0 SECTION 508 - ACCESSIBILITY OF ELECTRONIC AND INFORMATION TECHNOLOGY

(a) This SOO is subject to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) as amended by the workforce Investment Act of 1998 (P.L. 105-220). Specifically, subsection 508(a)(1) requires that when the Federal Government procures Electronic and Information Technology (EIT), the EIT must allow Federal employees and individuals of the public with disabilities comparable access to and use of information and data that is provided to Federal employees and individuals of the public without disabilities.

(b) The EIT accessibility standards at 36 CFR Part 1194 were developed by the Architectural and Transportation Barriers Compliance Board ("Access Board") and apply to contracts and task/delivery orders, awarded under indefinite quantity contracts on or after June 25, 2001.

(c) Each Electronic and Information Technology (EIT) product or service furnished under this contract shall comply with the Electronic and Information Technology Accessibility Standards (36 CFR 1194), as specified in the contract, as a minimum. If the Contracting Officer determines any furnished product or service is not in compliance with the contract, the Contracting Officer will promptly inform the Contractor in writing. The Contractor shall, without charge to the Government, repair or replace the non-compliant products or services within the period of time to be specified by the Government in writing. If such repair or replacement is not completed within the time specified, the Government shall have the following recourses:

1. Cancellation of the contract, delivery or task order, purchase or line item without termination liabilities; or

2. In the case of custom Electronic and Information Technology (EIT) being developed by a contractor for the Government, the Government shall have the right to have any necessary changes made or repairs performed by itself or by another firm for the noncompliant EIT, with the contractor liable for reimbursement to the Government for any expenses incurred thereby.

(d) The contractor must ensure that all EIT products that are less than fully compliant with the accessibility standards are provided pursuant to extensive market research and Are the most current compliant products or services available to satisfy the contract requirements.

(e) For every EIT product or service accepted under this contact by the Government that does not comply with 36 CFR 1194, the contractor shall, at the discretion of the Government, make every effort to replace or upgrade it with a compliant equivalent product or service, if commercially available and cost neutral, on either a contract specified refresh cycle for the product or service, or on a contract effective option/renewal date; whichever shall occur first.

Section 508 Compliance for Communications The IROC contractor shall comply with the standards, policies, and procedures below.

Rehabilitation Act, Section 508 Accessibility Standards

1. 29 U.S.C. 794d (Rehabilitation Act as amended)

2. 36 CFR 1194 (508 Standards)

3. www.access-board.gov/sec508/508standards.htm (508 standards)

4. FAR 39.2 (Section 508)

5. USDA Standards, policies and procedures (Section 508) In addition, all contract deliverables are subject to these 508 standards as applicable.

Regardless of format, all Web content or communications materials produced, including text, audio or video - must conform to applicable Section 508 standards to allow federal employees and members of the public with disabilities to access information that is comparable to information provided to persons without disabilities. All contractors (including subcontractors) or consultants responsible for preparing or posting content must comply with applicable Section 508 accessibility standards, and where applicable, those set forth in the referenced policy or standards documents above. Remediation of any materials that do not comply with the applicable provisions of 36 CFR Part 1194 as set forth in the SOO shall be the responsibility of the contractor or consultant.

The following Section 508 provisions apply to the content or communications material identified in this SOO:

36 CFR Part 1194.21 a - l 36 CFR Part 1194.22 a - p 36 CFR Part 1194.31 a - f 36 CFR Part 1194.41 a – c The contractor shall provide a completed Section 508 Product Assessment Template and the contractor shall state exactly how proposed EIT deliverable(s) meet or does not meet the applicable standards.

The following Section 508 provisions apply for software development material identified in this SOO:

For software development, software applications, and operating systems the Contractor/Developer/Vendor shall comply with the standards, policies, and procedures below:

Rehabilitation Act, Section 508, Accessibility Standards

(1) 29 U.S.C. 794d (Rehabilitation Act as amended)

(2) 36 CFR 1194 (508 Standards)

(3) www.access-board.gov/sec508/508standards.htm (508 Standards)

(4) FAR 39.2 (Section 508)

(5) USDA Standards, policies and procedures (Section 508)

For web-based applications (intranet, internet information and applications, 16 rules), the Contractor shall comply with the standards, policies, and procedures below:

Rehabilitation Act, Section 508, Accessibility Standards

(1) 29 U.S.C. 794d (Rehabilitation Act as amended)

(2) 36 CFR 1194 (508 Standards) 36 CFR Part 1194.22 (a – p) 36 CFR Part 1194.31 (a – f) 36 CFR Part 1194.41 (a – c)

(3) www.access-board.gov/sec508/508standards.htm (508 Standards)

(4) FAR 39.2 (Section 508)

(5) USDA Standards, policies and procedures (Section 508)

For Telecommunication products the Contractor shall comply with the standards, policies, and procedures below:

Rehabilitation Act, Section 508, Accessibility Standards

(1) 29 U.S.C. 794d (Rehabilitation Act as amended)

(2) 36 CFR 1194 (508 Standards) 36 CFR Part 1194.23 (a – k) 36 CFR Part 1194.31 (a – f) 36 CFR Part 1194.41 (a – c)

(3) www.access-board.gov/sec508/508standards.htm (508 Standards)

(4) FAR 39.2 (Section 508)

(5) USDA Standards, policies and procedures (Section 508)

For video and multimedia applications (including training), the Contractor shall comply with the standards, policies, and procedures below:

Rehabilitation Act, Section 508, Accessibility Standards

(1) 29 U.S.C. 794d (Rehabilitation Act as amended)

(2) 36 CFR 1194 (508 Standards) 36 CFR Part 1194.24 (a – e) 36 CFR Part 1194.31 (a – f) 36 CFR Part 1194.41 (a – c)

(3) www.access-board.gov/sec508/508standards.htm (508 Standards)

(4) FAR 39.2 (Section 508)

(5) USDA Standards, policies and procedures (Section 508)

For self contained, closed products, the Contractor shall comply with the standards, policies, and procedures below:

Rehabilitation Act, Section 508, Accessibility Standards

(1) 29 U.S.C. 794d (Rehabilitation Act as amended)

(2) 36 CFR 1194 (508 Standards) 36 CFR Part 1194.25 (a – j) 36 CFR Part 1194.31 (a – f) 36 CFR Part 1194.41 (a – c)

(3) www.access-board.gov/sec508/508standards.htm (508 Standards)

(4) FAR 39.2 (Section 508)

(5) USDA Standards, policies and procedures (Section 508)

For Desktop and portable computers, the Contractor shall comply with the standards, policies, and procedures below:

Rehabilitation Act, Section 508, Accessibility Standards

(1) 29 U.S.C. 794d (Rehabilitation Act as amended)

(2) 36 CFR 1194 (508 Standards) 36 CFR Part 1194.26(a – d) 36 CFR Part 1194.31 (a – f) 36 CFR Part 1194.41 (a – c)

(3) www.access-board.gov/sec508/508standards.htm (508 Standards)

(4) FAR 39.2 (Section 508)

(5) USDA Standards, policies and procedures (Section 508)

All Electronic Information Technology that is subject to the 36 CFR 1194 standards will have a Section 508 acceptance test and Section 508 will be validated upon acceptance.

All maintenance for Electronic Information Technology that requires upgrades, modifications, installations and purchases will adhere to the Section 508 Standards and 36 CFR 1194.

8 | Page