Attachment 2 Performance Work Statement.pdf

Performance Work Statement Defense Finance and Account Service

Congressional Reporting

1.0 INTRODUCTION: The Defense Finance and Accounting Service (DFAS) requires a web-based tool that will allow the Legislative Affairs team to fulfill key job functions and report congressional news, legislative actions, follow congressional hearings, and perform research on a wide range of congressional and legislative subjects.

2.0 SCOPE OF WORK: The contractor shall provide on-line legislative Congressional reporting, research, tracking, and analysis services for three users. System access shall be available 24 hours a day, seven days a week, including weekends and holidays. The contractor shall provide virtual training and telephone technical support, as needed.

3.0 PERIOD OF PERFORMANCE: The anticipated period of performance is a one-year base period with four additional one-year option periods.

4.0 SYSTEM ACCESS: DFAS users must be able to access the system using DFAS computers connected through the DFAS network (hardwired or VPN). System access shall not require a reduction of the DFAS security posture to operate. System access shall be available through a web browser executable in a Windows NT PC-based operating environment. The preferred system access is Internet portal based utilizing HTTPS over the standard TCP port 443. Use of other ports must be coordinated with the Government to obtain IT approval prior to completion of an agreement. Port solutions determined as not meeting the DFAS security/cybersecurity requirements will be determined unacceptable. System access shall not require software to be loaded on Government computers, collect/store personally identifiable information, or require the use or acceptance of persistent cookies or cross-site scripting.

5.0 GENERAL REQUIREMENTS: Legislative services must include the ability to download the full text of information available in PDF as well as text file format. Services shall include, at a minimum, the following:

(1) A system to track and maintain engagements and interactions with members and staff of

Congress.

(2) Full text of all versions of bills in the current legislative session with ability to search by word or phrase, bill numbers, chamber, bill version date, date bill introduced, stage in legislative process, and date items added.

(4) Ability to review bills by scanning from a predetermined watch/alert list, which provides updates on news articles, floor votes, new text versions and amendments and other key pieces of information, related to the bill.

(5) Full text of all bills before Congress, and additional information to include highlights, prospects for passage, major bill actions, news analysis and schedule information.

(6) Provide reports to include all aspects of all completed and upcoming House floor activity on legislation in the current legislative session, which includes: (a) list of amendments expected to be offered that day on House floor, (b) summary of key legislation which includes background information on issue prior to floor debate, (c) summary of changes agreed to on House floor and (d) changes made in conference summarized and published prior to release of conference report.

(7) Full Text of Executive Orders.

(8) Complete transcripts of DoD-related congressional hearings (full committee and subcommittee) including all HAC/SAC/HASC/SASC – Defense hearings, to include individual testimony/statements (from previous 18 months) – all of which to be posted no more than one-three days succeeding the event. Additionally, the Government may request that the Contractor provide transcripts of other identified hearings of interest.

(9) Customized reports on key current and past legislative actions.

(10) Ability to conduct text searches by key word, subject, bill number; and ability to link to other data sources and related news documents for analysis to be provided in single result.

(11) Full text of Committee and Conference Reports from current and previous legislative sessions. Full text version must be searchable by Congress number, word or phrase, bill numbers, personal word and bill list, Committees, Chamber, and report numbers.

(12) Transcripts of press conferences and other news media coverage focusing on Congress, the

White House, Pentagon and State Departments, including interviews with key government officials on various media outlets.

(13) Customized Email alerts provided on latest legislative actions and newly posted news stories, transcripts and schedules.

(14) Ability to access full text of key government and congressional documents, to include

Congressional Research Service, Government Accountability Office and Congressional Budget Office reports, OMB memorandums, letters between the Congress and Executive Branch agencies, executive orders, and other government and congressional documents with the ability to request them by e-mail.

(15) A schedule listing current and future committee hearings, including coverage of other events, such as the White House, federal departments and agencies, leading policy groups that are updated throughout the day. These event listings must include descriptions of attendees, times, witnesses and locations and updates available via e-mail, desktop and mobile device.

(16) Contact information for Congressional offices and staff members.

6.0 SECTION 508 REQUIREMENTS: Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use information and communication technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public who have disabilities must have access to, and use of, information and data that is comparable to people without disabilities. The following 508 standards apply to requirement and will ensure the services provided will support DFAS’s ability to comply with the Section 508 law:

• E205.1 General Electronic content shall comply with E205.

• E205.2 Public Facing Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

• E205.3 Agency Official Communication Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:

- A. An emergency notification;

- B. An initial or final decision adjudicating an administrative claim or proceeding;

- C. An internal or external program or policy announcement;

- D. A notice of benefits, program eligibility, employment opportunity, or personnel action;

- E. A formal acknowledgement of receipt;

- F. A survey questionnaire;

- G. A template or form;

- H. Educational or training materials; or

- I. Intranet content designed as a Web page.

• E205.4 Accessibility Standard (WCAG 2.0) - Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (Incorporated by reference, see 702.10.1).

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

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

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

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

• 503.1 General Applications shall conform to 503.

• 503.2 User Preferences Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

• Exception from E503.2 User Preferences: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

• 503.3 Alternative User Interfaces. Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

• 503.4 User Controls for Captions and Audio Description Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

• 503.4.1 Caption Controls Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

• 503.4.2 Audio Description Controls. Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

• 504.2 Content Creation or Editing Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

• 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion. Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

• 504.2.2 PDF Export. Authoring tools capable of exporting PDF files that conform to ISO 32000- 1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).

• 504.3 Prompts. Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.

• 504.4 Templates. Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG

2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

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

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

7.0 Contracting Officer Representative (COR): The COR will act as the on-site technical point of contact for the Government. They will monitor performance of services. The COR’s authority is limited to technical issues and they are not authorized to make contractual decisions. The authority to resolve monetary issues and contractual interpretation is the responsibility of the Contracting Officer.

The Contracting Officer Representative (COR) for this order is listed below.

Mannewell Darby DFAS-Mark Center Site Support Office 4800 Mark Center Dr.

Alexandria, VA 22350 Email: Mannewell.a.darby.civ@mail.mil

The COR is subject to change. The contractor will be notified in writing of any changes.

mailto:Mannewell.a.darby.civ@mail.mil