2017_CICO_PWS_v7_15_June_17.docx

Information Technology Services Chief Information Office/Office of Safety and Occupational Health Program

Performance Work Statement (PWS) Check-In/Check-Out Forest Service Hosted Software as a Service (SaaS)

Current Version:

Revised 06/15/17

Version 1.7

Contents

Introduction:

The Forest Service (FS) requires the purchasing of an Electronic Employee Status Board (EESB) solution to confirm the location of field going employee for safety purposes. This solution requires that the EESB be a Software as a Service (SaaS) with all required maintenance and support, within a FS hosted environment. The SaaS based solution will be needed for all field going employees to enter their physical location and status, for routine reporting to their supervisors, for safety purposes. The SaaS solution will continue to be hosted and work with existing FS IT technology and mobile technology.

Background and Objectives:

The FS had identified the need for a standardized check-in/check-out system to ensure employees whereabouts are known during work hours. A team was formed to research the best practices, and to develop the FS specific process for implementing a standard protocol for use nationwide. The team has identified several FS Units that have operational check-in/check-out protocols on their own, utilizing commercially available electronic status board systems. The FS wants to take the next step, and implement a FS wide standardized check-in/check-out SaaS.

Objectives:

The EESB will need to be able to manage and support over 30,000 employees, via an on premise (the FS/USDA Data Center) SaaS solution. Under this Objective, the FS will be responsible for providing the selected contractor with the hosting environment; and the contractor will be responsible for providing the FS customized SaaS solution, including 1) Full lifecycle support for the software; 2) Installation; 3) Setup; 4) Customization; 5) Management Support; 6) Any required Patches; 7) Bug fixes; 8) Enhancements; 9) Updates; and 10) Monitoring. The system will be for use by both employees and volunteers initially, and then could be expanded to include seasonal hires, cooperators, and other field going staff.

Technical Requirements:

The technical requirements are the current requirements for the solution is use, and as currently customized and deployed by numerous FS units.

Safety Requirements:

With the Forest Service’s current decentralized duty station environment, field work assignments, and telework locations, there is a real concern for employee safety. There is a valid safety need to know where employees are physically located during work tours of duty in case of an emergency. Supervisor need to be able to electronically pull up a list of where employees have checked-in status and check-out.

Technical Objectives:

Unique Requirements Customized Specifically for the Forest Service:

· Custom domain name with secure access, customized with the agency’s name and logo.

· Each site includes a regular (office) website for viewing and managing data, and a mobile website for employees using their mobile devices that has been optimized for quick access and ease of use.

· The employee Status Board can be filtered by location, work status, and other FS custom fields. The information displayed on the Status Board has been customized for FS.

· Custom fields specific to FS such as: Township, Section, Vehicle #, SEND Unit #, Range, Repeater, Supervisor status, Supervisor Name, Line/Staff Officer status, Line/Staff Officer Name. This information is displayed on the Status Board for each user.

· Integration with 3rd party applications, such as Find Me Spot and Lighthouse.

· Users, Status Codes, Resources are defined by Agency, Location, Department, as well as active or inactive status. This allows FS to be very specific in how they want to view their information.

· Users who do not update their status at or before the expected Return Time are sent an email and a text alerting them that they are past due, and should update their status. The Supervisor of the user is also notified via text and email that the user has not returned and/or updated their current status.

· Return time field on the Status Board changes to red for any users that go beyond their expected Return Time. The date and return time are highlighted.

· Reservations component: Users can reserve conference rooms, vehicles, or equipment on this page; by calendar view, date range, or list view. Reservations contains its own separate calendar component. Resource Manager level users can add and edit the status of resources and manage reservations as needed.

· Security levels: expanded security levels include: Administrator, User Manager, Resource Manager, User and Resource Manager, Employee, and Guest users. Manager level users can manage resources and/or users at their same Location.

General Primary Requirements:

· Cross browser compatibility (IE, Chrome, Firefox, Safari)

· Mobile compatibility (via smart and SEND devices)

· Status board to include the following attributes at a minimum:

· Name

· Location

· Status

· Return time including countdown ticker

· Comment field

· Status change screen/dropdown will be customizable to meet each units needs and will include the following defaults:

· Status types including: In, Off Duty, Out Field, Out Fire, Out Travel, Teleworking, Unavailable

· Return date and time

· Comment

· Status change screen must be able to be customized (add or remove options) to meet individual unit’s needs

· Users can be grouped into forest, district/office and configurable

· *Some trip specific fields should be made required fields based on the status type selected (for data integrity)

· Some trip specific fields only appear when relevant based on status type

· All status board attributes can be searched

· *Departure Date

· *Starting Point

· *Route of Travel

· *Parking Location

· *Destination

· Upon becoming overdue (optional for all status types) the status color changes to red (or whatever color is decided) and an email or text is sent to a predetermined individual/s

· *A customizable function that requires nightly “audit-OK” of the status board by dispatch or a manager by a certain time for a “group” – or else additional alerts are triggered

· Permission levels with a minimum of user, receptionist, group manager, supervisor/admin, super user

· User can only update/access their own profile and status

· Receptionist can update/access their own profile and the statuses of all users

· Group manager can update/access their own profile and the profiles of individuals within their assigned group

· Supervisor/Admin has the permissions of the group manager and can add new users to their forest

· Super User has the permissions of the group manager and can update/access all forests

· Secure Site (SSL)

· Scalable for enterprise use

· 508 compliant (Further details: 11.0 Section 508 - ACCESSIBILITY OF ELECTRONIC AND INFORMATION TECHNOLOGY)

· Reliable system with high level of availability and disaster recovery

· Capability to define retention period of data in the system.

· Messaging capabilities (email/text)

· Alerts & reminders (email/mobile)

· Status changes can occur via SMS

Secondary Requirements:

· Status board will auto refresh (customizable interval)

· *Set permission level of detail visible to correspond to User Type

· *Undo – change function or recall from archive/backup function in case someone accidentally deletes or prematurely removes user or trip details

· Capability to provide both SaaS and customer hosted solutions, SaaS is preferred option but FS is interested in available options

Desirables:

· Work phone number

· Email

· User import via .csv instead of manual entry

· Capability to integrate with external authentication systems (Interface with USDA e-authentication)

· Capability to perform administrative functions at an enterprise level as well as the sub-organization level

· Broadcast Messages (either marquee or email)

· Configurable to display SEND (Spot Messenger) location data

· Customizable reporting

· *Capability to include ArcGIS online spatial tools Documentation/Reports:

The contractor software will continue to provide customized status and the capability to run employee reports based on usage of employees:

7.1 System Upgrades and Testing:

The contractor will test FS Employee Status Board upgrade SaaS solution to insure that it is functioning correctly with all current IT equipment and infrastructure. The contractor will continue to work with the Government for recommended timeframe for any required downtime to install upgrades with up to a minimum of a 2 week notice.

Location:

Solution will need to be installed and managed within the USDA Forest Service (FS) Virtual Data Center (VDC) by the vendor. FS will be responsible to provide the standard environment while vendor will be responsible to install, configure, deploy and manage the environment following USDA FS release and configuration management standards.

8.1 Hours of Operation:

The contractor is responsible for providing services 24 hours and may be requested; exceptions to include Federal Holidays. The Contractor must at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this statement of work when the Government personnel. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the work force are essential.

Recognized Federal Holidays:

Period of Performance (POP):

The Base period performance is for one year from 07/15/2017 to 7/14/2018.

Anticipated Start Date: 07/15/2017 The contract period shall extend for one (1) year from the date of award. At the option of the Government, the contract may be renewed for four (4) One-Year Option Periods. The contract shall not exceed total of 60 months, if all options are exercised.

POP below:

Base Year: July 15, 2017 through July 14, 2018 (Users quantity: 30,000) Option Year 1: July 15, 2018 through July 14, 2019 (Users quantity: 30,000) Option Year 2: July 15, 2019 through July 14, 2020 (Users quantity: 30,000) Option Year 3: July 15, 2020 through July 14, 2021 (Users quantity: 30,000) Option Year 4: July 15, 2021 through July 14, 2022 (Users quantity: 30,000)

SECURITY

1.1 Security Language

By accepting this contract/agreement, the Contractor/Cooperator and other external organizations (hereafter called Contractor) providing Information Technology (IT) resources or services to the US Forest Service (FS) agrees to comply with the applicable IT security policy as outlined in this document. The Contractor and other external organizations will be responsible for IT security for all systems connected to the FS network or operated by the Contractor and other external organizations for the FS, regardless of location. This clause is applicable to all or any part of the contract that includes IT resources or services in which the Contractor and other external organizations must have physical or electronic access to FS sensitive information that directly support the mission of the FS. The term “information technology,” as used in this clause, means any equipment or interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. This includes both major applications and general support systems as defined by OMB Circular A-130.

The Contractor shall be responsible for properly protecting all information used, gathered, or developed as a result of work under this task. The Contractor shall also protect all unclassified Government data, equipment, etc., by treating information as sensitive business, confidential information, controlling and limiting access to the information, and ensuring the data and equipment are secured within their facility.

The Contractor or other external organization will not publish or disclose in any manner, without the FS Contracting Officer’s written consent, the details of any programs, documentation, data, or safeguards either designed or developed by the Contractor or other external organization under this Contract or otherwise provided by the Government. The Contractor may be required to sign non-disclosure or other appropriate security agreements. A written agreement between the FS and any contractors and other external organizations will be entered into before FS data and information otherwise exempt from public disclosure may be disclosed to the contractors and other external organizations. The Contractor and other external organizations will agree to establish and follow security precautions considered by the FS to be necessary to ensure proper handling of data and information. As may be identified elsewhere in this contract, the Contractor agrees that:

· The draft and final deliverables and all associated working papers and other materials deemed relevant by the COTR that have been generated by the Contractor in the performance of this contract are the property of the U.S. Government and must be submitted to the COTR at the conclusion of the tasks.

· All documents produced for this project are the property of the U.S. Government and cannot be reproduced or retained by the Contractor.

To the extent required to carry out a program of inspection to safeguard against threats and hazards to the security, integrity, and confidentiality of Government data, the Contractor will afford the Government access to the Contractor’s or other external organization’s facilities, installations, technical capabilities, operations, documentation, records, and databases.

The Contractor will cooperate with Federal agencies and their officially credentialed representatives during official inspections or investigations concerning the protection of FS information. Cooperation may include providing relevant documentation showing proof of compliance with federal and agency requirements, and rendering other assistance as deemed necessary.

If new or unanticipated threats or hazards are discovered by either the Government or the Contractor or other external organization, or if existing safeguards have ceased to function, the discoverer will immediately bring the situation to the attention of the other party. The Contractor will report real or suspected incidents or violations immediately upon discovery to the FS Computer Incident Response Team (CIRT), by e-mail, at CIRT@fs.fed.us.

The Contractor shall insert these clauses in all subcontracts when the subcontractor is required to have routine physical access to a federally controlled facility and/or routine access to a federally controlled information system. Failure to comply with said requirements will constitute cause for termination.

The Contractor Agrees To –

(a) Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies—

(i) The systems of records; and

(ii) The design, development, or operation work that the contractor is to perform;

(b) Include the Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a system of records on individuals that is subject to the Act; and

(c) Include this clause, including this paragraph (3), in all subcontracts awarded under this contract that requires the design, development, or operation of such a system of records.

In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a system of records on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a system of records on individuals to accomplish an agency function. For purposes of the Act, when the contract is for the operation of a system of records on individuals to accomplish an agency function, the Contractor is considered to be an employee of the agency.

Definitions of the clause:

(a) “Operation of a system of records,” as used in this clause, means performance of any of the activities associated with maintaining the system of records, including the collection, use, and dissemination of records.

(b) “Record,” as used in this clause, means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and that contains the person’s name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a fingerprint or voiceprint or a photograph.

(c) “System of records on individuals,” as used in this clause, means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual.

The contractors and other external organizations will ensure that the following banner is displayed on all FS systems that contain Privacy Act information operated by the contractors and other external organizations prior to allowing anyone access to the system:

“This system contains information protected under the provisions of the Privacy Act of 1974 (Public Law 93-579). Any privacy information displayed on the screen or printed must be protected from unauthorized disclosure. Employees who violate privacy safeguards may be subject to disciplinary actions, a fine of up to $5,000, or both.”

1.2 CONTRACTORS/COOPERATORS REQUIRE BUILDING ACCESS AND/OR INFORMATION SYSTEM ACCESS IT Security Training: The Contractor and other external organizations will ensure that its employees performing under this contract fulfill all Forest Service requirements for mandatory security awareness and role-based advanced security training in accordance with OMB Circular A-130, FISMA, and NIST requirements, and sign all applicable FS statements of responsibilities.

Background Investigations: All non-government employees with unescorted access to FS facilities, computer systems and/or FS information must have background investigations commensurate with the level of risk and magnitude of loss or harm. The FS will determine the level of background investigation and position classification needed.

Personal Identity Verification of Contractor Personnel: The Contractor shall be responsible for ensuring compliance by its employees with all applicable federal regulations, to include those of GSA, NIST, USDA, FS and HSPD-12. Contractors and their employees are subject to all Federal laws applicable to Government installations and are under the jurisdiction of the Federal Protective Service (FPS). The Contracting Officer Representatives (CORs; also known as Contracting Officer Technical Representatives), or other designated program/project officers, in conjunction with the FS HCM HSPD-12 staff, will assist the Contractor in processing the required Security Background Investigations/Clearances.

(1) The Contractor shall comply with the personal identity verification (PIV) policies and procedures established by U.S. Department of Agriculture (USDA) Directives 3800 series.

(2) Should the results of the PIV process require the exclusion of a Contractor’s employee, the Contracting Officer will notify the Contractor in writing.

(3) The Contractor must appoint a representative to manage this activity and to maintain a list of employees eligible for a USDA PIV ID Badge required for performance of the work.

(4) The responsibility of maintaining a sufficient workforce remains with the Contractor. Employees may be barred by the Government from performance of the work should they be found ineligible or to have lost eligibility for a USDA PIV ID Badge. Failure to maintain a sufficient workforce of employees eligible for a USDA PIV ID Badge may be grounds for termination of the contract.

(5) The Contractor shall insert this clause in all subcontracts when the subcontractor is required to have access to a federally controlled facility or information system.

(6) The PIV Sponsor for this contract is the Contracting Officer Representative (COR), unless otherwise specified in this contract. The PIV Sponsor will be available to receive contractor identity information from * (hours and days) to * (hours and days) at * (office address for registration). The Government shall notify the Contractor if there is a change in the PIV Sponsor, the office address, or the office hours for registration.

(7) At this time, the Government will pay for and process all required security investigations/clearances, except as identified differently within this clause.

(8) The Contractor should be aware of any of its employees possibly having had a background investigation through another government agency. The investigation that was conducted, if verifiable by the FS HSPD-12 staff, and if it was completed within the last 5 years, can be accepted by the Government in lieu of a background check.

(9) The Contractor shall comply with any facility badging requirements for the issuance of building access, badges, etc.:

· Ensure that each of the Contractor’s employees has been issued either a temporary or permanent badge from the Government. A permanent badge will not be issued until the security questionnaire has been completed and favorably reviewed. Temporary or visitor badges will be provided for persons who are identified as having an infrequent or temporary legitimate business need for access to the site. As noted above, periods that exceed 180 days will require a permanent badge. The badge must be worn at all times while in the facility. It must be displayed above the waist. The individual will retain possession of the badge as long as continued admittance to the site is needed.

· Ensure the safekeeping, wearing, and visibility of Government-furnished badges.

· Immediately return all badges and permits to the Government when such need ceases to exist.

(10) The Contractor shall comply with any facility security requirements for access to the facility.

(11) The Contractor shall comply with all applicable rules governing parking at USDA locations.

1.3 ACQUIRING AND/OR IMPLEMENTING SOFTWARE APPLICATIONS

Secure Coding Skills: Contractor certifies that at least one member of each programming team working on any code (including C, Java, .Net, ASP.NET, Visual Basic) to be delivered to the Forest Service has earned the Global Information Assurance Certification for Secured Software Programming or equivalent.

Source code testing, binary code testing, application scanning, and penetration testing: At least one week prior to delivery of any code due under this contract, Contractor will deliver to the COTR the following reports covering all code that will be delivered:

A. Source code testing results showing all potential security flaws identified by at least one of the commercial source code testing tools approved by the Office of the Chief Information Officer of USDA. On the report, the Contractor will highlight all vulnerabilities rated “critical” and “high.” The Contractor must then correct the vulnerabilities, resend the code, and ensure the health of delivered source code.

B. For web applications, web application scanning test results showing all potential security flaws identified by at least one of the commercial web application scanning tools approved by the Office of the Chief Information Officer of USDA. On the report, the Contractor will highlight all vulnerabilities rated “critical” and “high.”

C. For all applications: application penetration results.

Copyright Management and Responsibility: By delivering applications or programming code to the Federal Government, the vendor or Contractor certifies that they have the proper authority to transfer the property and will defend the Government against copyright or other lawsuit resulting from the application or programming delivered.

1.4 ACQUIRING EXTERNAL IT SERVICES (PROCESSING, STORING, OR TRANSMITTING FS DATA ON A NON-FS SYSTEM) The Contractor or other external organizations will develop, provide, implement, and maintain an IT System Security Plan for any system that includes acquisition, transmission or analysis of data owned by FS with significant replacement cost should the Contractor’s and other external organization’s copy be corrupted. This plan will describe the processes and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contract. The plan will describe those parts of the contract to which this clause applies. The Contractor or other external organization’s IT System Security Plan will be compliant with applicable Federal laws that include, but are not limited to: (e.g., the Clinger-Cohen Act of 1996 and the Federal Information Security Management Act of 2002). The IT System Security Plan will meet IT security requirements in accordance with Federal and FS policies and procedures that include, but are not limited to: National Institute of Standards and Technology (NIST) SP 800-53 Guidelines.

The Contractor and other external organizations will ensure that the appropriate security banners are displayed on all FS systems (both public and private) operated by the contractors and other external organizations prior to allowing anyone access to the system.

Section 508 - ACCESSIBILITY OF ELECTRONIC AND INFORMATION TECHNOLOGY

(a) This PWS 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.

1.5 Section 508 Compliance for Communications

The solution shall comply with the standards, policies, and procedures below. In the event of conflicts between the referenced documents and this PWS, the PWS shall take precedence.

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 PWS shall be the responsibility of the contractor or consultant.

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

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 PWS:

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.

IPv6 Requirements Vendor shall provide Supplier Declaration of Conformity SDOC(s) documenting:

1. Any system, hardware, software, firmware or networked component (voice, video or data) developed, procured or acquired in support or performance of this contract shall be capable of transmitting, receiving, processing, forwarding and storing digital information across system boundaries utilizing system packets that are formatted in accordance with commercial standards of Internet Protocol (IP) version 6 (IPv6) as set forth in the USGv6 Profile (NIST Special Publication 500-267) and corresponding declarations of conformance defined in the USGv6 Test Program. In addition, this system shall maintain interoperability with IPv4 systems and provide at least the same level of performance and reliability capabilities of IPv4 products:

1. Specifically, any new IP product or system developed, acquired, or produced must:

1. Interoperate with both IPv6 and IPv4 systems and products, and

1. Have available contractor/vendor IPv6 technical support for development and implementation and fielded product management.

1. As IPv6 evolves, the Contractor commits to upgrading or providing an appropriate migration path for each item developed, delivered or utilized at no additional cost to the Government.

1. The Contractor shall provide technical support for both IPv4 and IPv6.

1. Any system or software must be able to operate on networks supporting IPv4, IPv6 or one that supports both.

1. Any product whose non-compliance is discovered and made known to the Contractor within one year after acceptance shall be upgraded, modified or replaced to bring it into compliance at no additional cost to the Government.

Contracting Officer Representative (COR): The (COR) is identified below:

Roger Garza

The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements to the Contracting Officer, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract or order.

Contractor Manager:

The contractor shall provide a contractor manager or lead who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contractor manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between [Insert the hours, i.e., 8:00 a.m. to 4:30p.m.], Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. (If the effort is for complex services or a large program you may want to consider adding additional requirements for program management duties that the contractor is required to perform to oversee the successful completion of the services work that the contractor must complete. Talk with your contracting officer to discuss when this may be a good idea.)

image1.png