RFP_DOL-OPS-16-R-00036_W_SOW_Clauses_Provisions.pdf

DOL-OPS-16-R-00036

PRICING SCHEDULE

**Please complete enclosed Excel Spreadsheet

Office of Public Affairs Division of Enterprise Communications

Web Support Statement of Work

U.S. DEPARTMENT OF LABOR

OFFICE OF PUBLIC AFFAIRS

DIVISION OF ENTERPRISE COMMUNICATIONS

STATEMEMT OF WORK

WEB SUPPORT SERVICES

DATED: MAY 23, 2016

Table of Contents 1 Overview

1.1 Background

1.2 Objective

2 Scope

3 Requirements and Tasks

3.1 Detailed Requirements

3.1.1 General

3.1.2 Information Technology Governance

3.1.3 Content Management

3.1.4 Technical Services/Application Development

3.1.5 Quality Management

3.1.6 Security

3.1.7 Project & Program Management

3.1.8 Change, Configuration and Release Management

3.2 Specialized Experience Requirements

3.2.1 Information Technology Governance

3.2.2 Content Management

3.2.3 Technical Services/Application Development

3.2.4 Quality Management

3.2.5 Security

3.2.6 Project & Program Management

3.2.7 Change, Configuration and Release Management

3.3 Additional Requirements

3.3.1 Reporting

3.3.2 Onsite Monitoring

3.3.3 Transition Period

4 Government Furnished Information/Government Furnished Equipment

5 Work Location (200 Constitution Ave. NW, Washington, DC 20210)

6 Deliverables and Delivery Schedule

7 Period of Performance

8 Administrative Concerns

8.1 Hours of Work

9 Non-Personal Services

10 Post Award Administration

11 Deliverables

11.1 Preservation, Packaging, Packing and Marking

11.2 Place of Inspection and Acceptance

11.3 Scope of Inspection and Acception

11.4 Timing of Acceptance

11.5 Basis of Acceptance

11.6 Initial Deliverables

11.7 Non-Conforming Products or Services

12 Access to Government Electronic Mail

13 Invoice Submission

14 Invoicing Instructions

15 Travel

16 Travel Regulations

17 Contracting Officer’s Representative (COR) 18 Organizational Conflict of Interest

19 Non-Disclosure Requirements

20 Security Considerations

21 Transfer of Hardware/Software Maintenance Agreements to Follow-On Contractors

22 Privacy Act

23 Contract Closeout 24 Past Performance Information

25 Data Rights

26 Approach and Methodology

27 Work Stoppages Due to Government Shutdown or Other Unavailability

28 Telework Policy

29 Reporting and Communications APPENDIX A – Secretary’s Order 2-2005

APPENDIX B – Sample Layout/Field Requirements for Weekly Reports

APPENDIX C – Staff Qualifications Key Staff Other Staff Qualifications

APPENDIX D – Technical Standards Web Application Development

Applications Developed by DEC Application Integration Support for Applications Developed by Supported DOL Agencies

Mobile Application Development Source Code Control Web Content Editing/Publishing/Monitoring Information Security Desktop Software and Management Project Management Service Desk Accessibility Evaluation Tools Other

APPENDIX E – Performance Metrics Standards

1 Overview The Contractor shall support a multi-year effort in the areas of Web and mobile application development; Web and content management; quality management; change configuration and release management; support of content and applications in an existing cloud-hosting environment; enterprise and IT governance; technology support services including infrastructure support services; and Web content management that includes written and graphical content.

The Contractor shall be required to furnish and maintain all necessary services, qualified personnel, material, equipment and facilities not otherwise provided by the Government, to meet the requirements described in this Statement of Work (SOW).

1.1 Background

The Office of Public Affairs’ (OPA) Division of Enterprise Communications (DEC) was created by Secretary’s Order 2-2005, “Delegation of Authority and Assignment of Responsibility for DOL Enterprise Communications Initiative.” This Order calls for the centralization of enterprise communications services to ensure a more effective and cost efficient method of providing consistent and accurate information to the public.

DEC has an overarching policy role within the Department, developing policies that affect all DOL websites. DEC has direct responsibility for the content and applications hosted on DOL.gov, and performs content management operations for several smaller agencies hosted on DOL.gov. DEC has direct responsibility for the content and applications hosted on LaborNet, the primary intranet for DOL. DEC is responsible for building Web and mobile applications to support OPA and other agencies’ requirements. To support these activities, DEC maintains a quality assurance function to test all applications, a security team to test applications and ensure DEC compliance with security requirements and a governance function to ensure DEC compliance with OMB and DOL reporting requirements. These separate functions are distributed across four teams led by federal employees and supported by contract staff: content, governance (security, capital planning, enterprise architecture), quality assurance (application testing and accessibility assurance) and technical (application development and infrastructure support).

The DEC Director and the federal managers are responsible for the administration and management of all projects and ensure the delivery of timely, accurate and authoritative information through Internet and intranet services.

Currently, contracted services provide on-site help to support delivery of electronic services and information to DOL customers and employees.

Because of the diversity of OPA and Departmental requirements, the Contractor must support and be available to address and discuss overall OPA DEC functions and services and attend meetings, during the base hours of operation, which are 8:30 a.m. to 5:30 p.m. Monday through Friday, Eastern Time. In rare instances, the Contractor will, upon request, make available the essential staff to perform requested functions or services outside the base hours. When requested, the Contractor will maintain on-call staff for work, as needed, on weekends and federal holidays. The Contractor will fulfill staffing requests with the understanding that OPA operates in a dynamic media and technology environment and that Departmental operations are not limited to the East Coast and take into account other time zones.

1.2 Objective

The Division of Enterprise Communications’ (DEC) objective is to provide useful, usable, accessible and secure websites, Web applications and mobile applications for the public and DOL employees using current and proven technologies while exploring innovative strategies and capabilities to improve these services across the Department of Labor.

DEC accomplishes these tasks in accordance with:

• all federal laws, regulations and policies;

• DOL standards and policies;

• the DOL Systems Development Life Cycle Methodology (SDLCM) processes (the approved DOL project life cycle); and

• Kanban agile project management processes for planning, implementing and executing all projects.

DEC provides:

• direct content management support for DOL.gov and LaborNet;

• direct website management support for several agencies hosted on DOL.gov;

• general support, maintenance and management for a single content and application development environment for DOL.gov and LaborNet;

• application development for OPA and other agency development projects;

• Federal Information Security Management Act (FISMA) and National Institute of Standards and

Technology (NIST) security compliance and risk assessment; and

• ongoing consultation with DOL agencies and components on policy development, compliance enforcement and Web best practices.

The Contractor will use industry best practices for information technology project management; Web and mobile application development; Web content management; quality management; change, configuration and release management; management of applications and websites in an existing cloud environment; enterprise and IT governance technology support services including infrastructure support services and security; and prescribed rules of conduct concerning government information dissemination.

The Contractor shall have practical experience in understanding and support of the FISMA regulations, within the context of the software development process. The Contractor shall efficiently capture, use and report performance information as used commonly in industry to assess the status of projects or as needed to meet Capital Planning requirements. All activities shall comply with standards that sustain internal and external scrutiny, including those of the DOL Office of the Inspector General (OIG). All staff with project management responsibilities shall be Project Management Professional (PMP) certified and have experience managing agile software development projects.

The Government will supply all hardware and software needed for the performance of the tasks in this Statement of Work.

2 Scope The scope of this effort includes services necessary to provide a full range of website content maintenance activities and application design, development and maintenance support. Primarily, but not exclusively, services provided will focus on applications supporting agency interaction with public but may include other administrative applications as well.

All services provided and products delivered must comply with Government security, Section 508 and architecture requirements.

Specifically, the scope of services required includes:

• Manage Internet and intranet website content editing and publishing;

• Measure, track, document and report website effectiveness;

• Improve the consistency, accuracy and timeliness of information across communication channels between

DOL and the public;

• Ensure usability, accessibility and quality assurance for all DOL websites, Web applications and public-facing mobile applications;

• Manage website architecture;

• Support social/digital media activities;

• Support email subscription services as users of the DOL-supplied email subscription service, obtained separately from this contract;

• Manage websites and applications in an existing cloud environment;

• Manage website security, including Web application firewalls, incident response, security compliance and testing, Personally Identifiable Information (PII) and information asset protection, certification and accreditation and additional security services, as required;

• Manage capital planning requirements for the Office of Public Affairs;

• Manage configuration, change and release management;

• Manage Web applications (both off the shelf and onsite created) and website development;

• Provide input for business process reengineering;

• Support the migration of content from the existing DOL.gov to a Drupal-hosted DOL.gov, obtained separately from this contract;

• Manage projects in accordance with Departmental Systems Development Life Cycle (SDLC) requirements;

and

• Respond to all OMB and Departmental requirements within requested timeframes.

Any contract resulting from this Statement of Work (SOW) may be modified at any time to accommodate increases or decreases in the number of end users supported, the number of systems requiring support and legislative changes that affect agency system and/or data requirements.

3 Requirements and Tasks The U.S. Department of Labor (DOL), Office of Public Affairs, Division of Enterprise Communications (OPA DEC) Contractor will provide Web application, content management and enterprise technology support services including infrastructure support services. Onsite services will include project management, Web content management, quality assurance, desktop support to OPA personnel, Web and mobile application management and Web governance (security, change management, release management and capital planning) services.

Web application management shall consist of designing, developing, implementing and managing Web application activities. Mobile application management shall consist of designing, developing, implementing and managing native mobile application activities across the various platforms supported by OPA DEC. Enterprise Web content management support services shall include performing research, creating and revising content and website file management operations. Enterprise technology support services shall include strategic business planning, custom software development and configuration/customization of commercial off-the-shelf (COTS) products, including open source, project management, project life cycle management, application maintenance and support, configuration management, technical documentation, general information systems engineering, technical assistance, security policy management, product development, quality assurance, accessibility, usability, customer service and support and infrastructure support.

3.1 Detailed Requirements

The contractor must be able to adapt to and use emerging technologies related to Web operational support. In order to support the agency mission, projects and system requirements, the Government requires sophisticated information technology systems support and website management services. The following section of the SOW describes the requirements and tasks that shall be accomplished to meet these requirements.

Examples, where provided, are illustrative and are not intended to describe the full array of tasks that might exist within a requirement.

3.1.1 General

The Contractor will:

• Organize, motivate, direct and manage a talented team of mixed skills and responsibilities to maximize a high quality experience for customers, both within DOL and in the public.

• Ensure access to a wide talent pool of Web technology specialists.

• Facilitate meetings.

Example: The Contractor would develop appropriate agendas, make meeting arrangements, facilitate meetings and provide meeting minutes for a variety of topics including project status updates, Web governance meetings with agencies and other types of meetings that will support the ongoing operations of OPA DEC.

• Customer service. All Contractors may have contact with other parts of OPA or with representatives of other agencies in the course of their duties. OPA values service and professionalism and all contact with

OPA and other agencies will be conducted in accordance with these principles. All staff will perform consistent follow-up and display professional behaviors which result in excellent customer service skills during all written and verbal communications.

• Develop or Revise Standard Operating Procedures (SOP), as needed, for all components of the OPA DEC support operations.

Example: The processes, procedures and service levels for daily service desk support will be documented into a comprehensive document (SOP), which will include a workflow and describe how the service desk will support the end user and report to OPA DEC management

3.1.2 Information Technology Governance

The Contractor will:

• Demonstrate the ability to work efficiently within the DOL Enterprise Architecture (EA) governance model and provide enterprise services portfolio management to drive enterprise architecture implementation.

Example: Work with OPA DEC management to determine EA planning and submit all appropriate EA reporting to the appropriate DOL offices.

• Document Program Management and Capital Planning and Investment regulatory compliance requirements, including Control Exhibit 300, Exhibit 53s and Control Reviews.

Example: Contractor staff would work with OPA DEC managers, National Contact Center managers and other team members to gather the information needed for proper reporting and ensure that all reporting is successfully completed and submitted in accordance with established deadlines.

• Assist in developing and monitoring Memoranda of Understanding (MOU) and Service Level Agreements

(SLA).

Example: The Office of the Assistant Secretary for Administration and Management (OASAM) Office of the Chief Information Officer (OCIO) is responsible for the production servers that host OPA DEC websites and applications. The Contractor might be asked to monitor an SLA with OASAM OCIO for their services. Additionally, OPA DEC might establish an MOU or SLA with an agency for which they provide services. The Contractor might be asked to assist in developing the MOU or SLA terms, as appropriate and monitor OPA DEC’s compliance with that MOU or SLA.

3.1.3 Content Management

The Contractor will:

• Provide content management services and support functions. The contractor will maintain existing content for DOL.gov and LaborNet (the DOL intranet) and, on occasion, develop new microsites, typically of 10 Web pages or less. The team is not responsible for writing original content, just editing HTML and CSS and publishing content created by others to the websites.

Example: Until all Web content is moved to a Web Content Management System, pages on the DOL.gov or LaborNet websites must be coded in HTML using an HTML editing package, checked for adherence to the requested changes and copied to a production server. These requests could come from OPA DEC managers, from representatives of agencies for which OPA DEC manages content, or be necessary due to broken link reports. The Contractor will also provide support for migration of files and data into the Drupal Web content management system.

• Provide monthly Web usage statistics and activity reports on the Department’s websites, as requested.

Example: Using a Government supplied tool such as Google Analytics, provide metrics information (including custom reports), as requested and scheduled, manage a user base of DOL agency Web content managers to ensure they have access to current Web metrics reports and demonstrate expertise with additional Google Analytics features such as the Tag Manager.

• Upload, publish and/or caption videos for the website and for various social/digital media platforms. The contractor will not be required to create these videos.

Example: A different division within OPA supplies an electronic version of a video that needs to be posted on DOL.gov. The Contractor would encode that video to a Web-ready format, prepare HTML files to display the video, create captions for the video from supplied transcripts or by creating a transcript (for videos of 1-5 minutes only), time those captions to the video using an existing process, associate the caption file with the video in the HTML and publish everything to a production server. Alternatively, the video would be uploaded to the department’s YouTube channel.

• Create still and motion graphics.

Example: Using requirements from OPA or an agency customer, develop a still image or motion graphic that could be embedded in a website, shared via social media or used in a presentation.

• Conduct training or deskside coaching on developed applications and implemented solutions.

Example: OPA DEC is using Google Analytics. The Contractor will conduct deskside coaching to agency customers on how to use the DOL Google Analytics implementation and/or provide desk aids or manuals with instructions.

• Assist with social media channel management and the implementation of new social media channels.

Typically, the contractor will not publish to social media channels, only assist with setting up new ones.

Example: In rare circumstances, under the direction of OPA, assist in creating content for or publishing information to the various social media channels managed by OPA.

3.1.4 Technical Services/Application Development

• Develop and manage Web applications utilizing the Department’s Systems Development Life Cycle (SDLC) applied, as appropriate, to Kanban and following DEC's technical standards (see Appendix D). The contractor will provide bug fixes and other improvements to existing applications and, as directed, create new applications.

Example: Build a custom application that is an events management platform, allowing users to add events and develop custom registration pages for these events. Reporting would include a list of registered participants. The entire process would follow DOL SDLC processes and meet all DOL SDLC documentation requirements.

• Perform code reviews for quality, standards compliance and security.

Example: Perform manual code reviews in addition to automated scans of application code developed by OPA DEC staff as well as code written by other agencies and hosted by OPA

DEC.

• Manage search engine platforms via an enterprise search solution or equivalent.

Example: The Contractor would input search result boosting information into an existing search solution and ensure that search results are relevant. Additionally, the Contractor would manage the server used to host the search application.

• Manage Multi-platform Database Management System (DBMS) (SQL, Oracle, MySQL, etc.) Design and Administration services.

• Manage application capacity and the ability to proactively plan and scope requirements to enable scalable solutions that maximize the economies of scale and investments.

• Provide expertise in emerging technologies to keep DOL Web services relevant.

Example: The Contractor performs research and development activities on new technologies and briefs OPA DEC managers on the applicability of the technology to OPA DEC’s needs, makes presentations, provides reports and makes a recommendation on implementation.

• Develop and support native mobile applications on multiple platforms while adhering to DEC's technical standards.

Example: The Contractor develops a timesheet mobile application using native tools that can be used by workers to track their hours for multiple employers. The app would provide information on when overtime is due and how to seek help if wages weren’t properly paid. The application would be made available for iOS and Android devices.

• Manage a service desk. The contractor will provide service desk support during the stated business hours.

In rare instances (for example, an emergency or an unexpected teleworking situation), service desk work could be performed remotely.

Example: OPA staff members enter helpdesk requests through DEC's helpdesk ticketing system (JIRA Service Desk). Examples of requests include installing a desktop for a new employee, notification that a production application isn’t working properly, or setting up a test environment for a COTS product undergoing evaluation. OPA DEC supplies desktop support, including hardware installation and inventory, for all OPA staff.

3.1.5 Quality Management

• Provide Section508/accessibility testing and quality assurance services.

Example: The Contractor performs full quality assurance testing on a Web application built by OPA DEC, develops the test plan and test use cases, performs functional testing and provides detailed bug reports. Additionally, the Contractor performs website content reviews and corrections to ensure that all content is current and functional (e.g. no 404 errors).

• Use WCAG 2.0 AA and the DHS Section 508 Compliance Application Test Process and OPA accessibility standards and guidelines to complete accessibility reviews on websites and Web applications as part of the development process. Ad hoc reviews are completed, as requested, to assess accessibility, to make recommendations on coding and design fixes and to provide bug reports.

• Update a knowledgebase site such as the internal wiki with quality management-related information.

• Conduct a variety of accessibility compliance training such as how to use Compliance Sheriff, how to create an accessible document, how to create an accessible website, etc.

• Be able to use assistive technologies to test the Section 508 Compliance for websites and Web applications.

The assistive technologies currently used are Jaws, Dragon Naturally Speaking and Zoomtext.

• Understand iOS Human Interface Guidelines and Android Design Guidelines, used as our mobile testing guidelines, when testing iOS mobile applications and Android applications.

3.1.6 Security

• Have deep knowledge of NIST security requirements.

• Advise on security best practices and make recommendations on ways to strengthen our security program.

• Perform periodic testing and evaluation of the effectiveness of information security policies, procedures, practices and security controls to be performed with a frequency depending on risk, but no less than annually.

• Develop a deep understanding of DOL-specific security polices within 45 days after the contract begins, as validated by the Information Security Officer.

• Develop, implement and manage NIST-compliant security documents, including but not limited to disaster recovery plans, contingency plans and tests, system security plans and all related documents.

• Provide software security services.

Examples: Web Application Vulnerability Assessments, Source Code Analysis, Independent Verification and Validation (IV&V), Penetration Testing, Code Reviews and Architectural Risk Analysis (ARA), Threat Modeling, etc.

• Provide expert analysis of new federal guidance and/or changes to the security environment as it impacts security documentation.

3.1.7 Project & Program Management

• Demonstrate the ability to multitask with various, competing projects using the Kanban agile project management methodology and the approved DOL Systems Development Life Cycle Methodology (SDLCM) processes or, if directed by DEC, Project Management Institute (PMI) project management processes. See http://www.pmi.org/PMBOK-Guide-and-Standards.aspx for information on PMI processes and standards.

Example: Develop a grants data application that allows the public to search for detailed grant information. The Contractor shall gather all requirements, develop all required documentation, manage all stakeholder involvement, develop the application, perform accessibility and quality assurance testing on the application, use change management and release management processes to prepare the application package for deployment, obtain deployment permission from OPA DEC managers, deliver the application package to the implementation authority, document lessons learned and close out the project. Status on the project, from beginning to end, would be provided to OPA DEC managers and the project would be managed using accepted Project Management Institute (PMI) processes and within JIRA (provided by DEC).

• Report the levels and types of activities and the agencies supported on a weekly basis.

Example: The Contractor provides weekly status updates on completed tasks and tasks in progress, noting any issues that may impede progress on a task.

• Provide labor and operations cost projections and actuals on a monthly basis.

3.1.8 Change, Configuration and Release Management

The Contractor will:

• Apply configuration, change and release management practices. These processes have been defined and are currently in use.

http://www.pmi.org/PMBOK-Guide-and-Standards.aspx

Example: OPA DEC manages the desktop equipment for the entire OPA staff. The Contractor would be responsible for inventorying the Government-supplied hardware that is distributed to the OPA staff and for tracking it via configuration management processes. Additionally, the configuration management process would track software versions and installations. Change management processes would be used to track changes to software or COTS products developed or managed by OPA DEC as a service to the agencies OPA DEC supports. Release management processes would ensure that all applications being moved into the production environment are properly managed and coordinated.

3.2 Specialized Experience Requirements

3.2.1 Information Technology Governance

In the area of IT governance, the Contractor will manage the following activities:

a. Web and enterprise communication governance framework implementation and management;

b. Baseline management, performance management and strategic planning;

c. Managing OMB Capital Planning and Investment Control (CPIC) requirements;

d. Exhibit 300 A&B, Exhibit 53 and IT dashboard submission requirements for the federal agencies; and

e. Using enterprise architecture methodology and EA information as decision making tools for enterprise-wide implementations.

Note: Financial information is segregated in a way that no conflict of interest is introduced that would preclude the vendor from competing for future contracts.

3.2.2 Content Management

In the area of content management, the Contractor will manage the following activities:

a. HTML, CSS and JQUERY coding;

b. Management of content in a Web Content Management System (e.g. Drupal); and

c. Still and motion graphics creation and editing.

Although not currently needed, the vendor may be asked to manage the following activities on future tasking:

a. Content research and creation; and

b. Content proofreading and editing.

Content research may include looking at what OPA has done with similar content before, how others publish similar content or how provided content may fit into the existing website. It could also include finding related information for provided content. For example, the vendor might be provided with a list of books and would be asked to provide the related authors and other information about those books to help build a Web page.

Content proofreading and editing is needed to the extent of providing quality assurance activities on content that OPA has developed for a website.

3.2.3 Technical Services/Application Development

In the area of technical services/application development, the Contractor will manage the following activities:

a. Web application development and maintenance;

b. Development of mobile applications for multiple mobile operating systems;

c. Using various application, database and networking technologies including .Net, PHP, Ruby, Swift, MySQL, SQL Server, Git, MS Windows, Mac OS X, etc. (see Appendix D);

d. Management and support of a development network and server infrastructure, consisting of Windows and

Red Hat Linux, including virtualization, SANs and remote access. The development environment already exists within the DOL infrastructure and is expected to remain the same;

e. Researching and proposing technology updates; and

f. Management and support of Windows and OS X desktops in an Active Directory environment.

Note: Although the development work for the Drupal web content management system is currently being performed under another contract, there may be a need for Drupal development work in the future.

3.2.4 Quality Management

In the area of quality management, the Contractor shall manage the following activities:

a. Review and management of Section 508/ accessibility methodologies for the Web as well as training in the application of specific techniques for Section 508/accessibility;

b. Applying Web and mobile application usability standards and testing;

c. Web application, mobile application and website testing, to include developing all relevant test use cases and bug tracking reports; and

d. Process and product quality assurance auditing of Web applications.

3.2.5 Security

The Office of Management and Budget (OMB) Circular A-130, Management of Federal Information Resources, requires federal agencies to plan for security, ensure that appropriate officials are assigned security responsibility and authorize processing prior to operations and periodically thereafter.

Using the Cyber Security Assessment Management (CSAM) tool, the contractor will develop, implement and maintain a security plan that ensures the confidentiality, integrity and availability of information and systems for the duration of this contract. The security plan will contain, at a minimum, the information outlined in NIST Special Publication 800-18, Guide for Developing Security Plans for Information Technology Systems and NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach. Additional work may be required at the discretion of agency designated approving authority (DAA) in accordance with agency policies or directives as specified in statements of work. Other security deliverables include but are not limited to:

• Privacy Impact Assessment (PIA)

• Risk Assessment (RA)

• System Security Plan (SSP)

• Security Training Plan

• Contingency Plan (CP)

• Security Self Assessment (SSA). Any unmitigated weaknesses identified should be included in a Security

Plan of Actions and Milestones (POA&M).

• System Test and Evaluation Plan (ST&E)

• Certification & Accreditation (C&A)

• Disaster Recovery Plan

These documents already exist and are updated as circumstances change, when OCIO requires updates and are reviewed and/or revised at least annually.

The Contractor shall coordinate the submission of certification and accreditation (C&A) documents with DOL and correct any deficiencies identified in the C&A process until full accreditation and authority to operate (ATO) from DOL is obtained. All required ATOs are in place but OPA DEC may have approximately one renewal per year.

3.2.6 Project & Program Management

In the area of project and program management, the Contractor will manage the following activities:

a. DOL System Development Lifecycle Management practices;

b. Agile/modular development methodologies and

c. Meeting planning, meeting facilitation, communication plans, lessons learned, stakeholder outreach and project documentation.

The Contractor shall implement procedures for communicating to the Contracting Officer and/or designated key personnel any issues that impact Contractor performance under this contract. Such procedure shall include an escalation process defining various stages of issue severity and the notification level appropriate to each.

3.2.7 Change, Configuration and Release Management

In the area of change and configuration management, the Contractor shall manage the following activities:

a. Using sound change management process implementation and monitoring principles;

b. Implementing and maintaining change, configuration and release management; and

c. Implementing and monitoring a configuration management database (CMDB).

3.3 Additional Requirements

3.3.1 Reporting

In addition to those reports required by the other terms of this contract and other documentation required as part of development projects and normal operations and maintenance projects, the Contractor will prepare and submit the following reports:

3.3.1.1 Weekly Performance Reports

Contractor will prepare written interim reports to monitor the performance and progress of all projects and tasks in which the Contractor is involved. This report is due in 7 calendar days from the end of each work week. For example, the report for the week ending January 7 (a Friday) will be due on January 14 (the following Friday). The report will be submitted electronically using a format compatible with the Department of Labor’s productivity software. See Appendix B.

3.3.1.2 Final Report

The final report will include a summation of activities performed during the entire contract period of performance.

This report will be in sufficient detail to describe comprehensively the results achieved. Copies of all manuscripts prepared or published by the Contractor must be included in the Final Report. The Contractor will submit, with the final report, two copies of a Summary of Salient Results achieved during the performance of the contract. The report may be submitted electronically using a format compatible with the Department of Labor’s productivity software or in hardcopy form.

3.3.2 Onsite Monitoring

The Department will conduct random onsite monitoring of all Contractor facilities associated with this Contract.

Although the Government anticipates that all work will be done at the government site, if the contractor makes space available for contractor work (e.g. for teleworking), the government can conduct on-site monitoring to note safety issues, adequate space for staff and other workplace issues at any time.

3.3.3 Transition Period

Transition will be immediate.

4 Government Furnished Information/Government Furnished Equipment The Government will make available all equipment necessary to complete the tasks under this contract when work is performed at the Government worksite. The Government will not supply equipment for work performed elsewhere.

5 Work Location (200 Constitution Ave. NW, Washington, DC 20210) All work under this contract will be performed at the Government worksite unless specifically authorized by mutual agreement of the CO, COR and the Contractor. Telework arrangements, if any, will be in accordance with Department of Labor policies and by mutual agreement of the COR and the Contractor. No work may be performed outside the United States. If the vendor has space available that can be used during unusual circumstances (e.g.

building closures) to allow contractors to continue to work at no added expense to the government, that is acceptable with prior approval of the government.

6 Deliverables and Delivery Schedule Deliverables will be as described in 3.3.1 Reporting. All reports will be delivered electronically using the current, approved office automation formats (e.g. Microsoft Word for word processing documents, Microsoft Excel for spreadsheets, etc.).

7 Period of Performance The timeframe covered by this scope will be five years: Base Year followed by four (4) subsequent 12-month Option periods from contract award.

8 Administrative Concerns

8.1 Hours of Work

Normal labor coverage will be from 8:30 a.m. to 5:30 p.m., Monday through Friday, Eastern Time. The Contractor will maintain a flexible staffing arrangement that permits the assignment of work for completion during hours outside normal business hours, in recognition of the requests for support and services that may be made by the OPA agency head or by other representatives of the Secretary of Labor. Weekend and Federal holiday on-call coverage may be required for systems or other support. Extra staffing may be necessary depending on general workload, emergency tasking, server backups, hardware and software installation and other maintenance issues. Actual work volumes may be greater than or less than anticipated. To the best of its ability, DEC will notify the Contractor of any known, or anticipated, impact to work volumes.

9 Non-Personal Services As stated in the Federal Register, Volume 57, No. 190, page 45096, dated September 30, 1992, Policy Letter on Inherently Governmental Functions, no personal services shall be performed under this contract. All work requirements shall flow only from the Project Officer to the Contractor's Senior Project Manager. No Contractor employee shall be directly supervised by the Government. The applicable employee supervisor shall give all individual employee assignments and daily work direction. If the Contractor believes any Government action or communication has been given that would create a personal services relationship between the Government and any Contractor employee, the Contractor shall promptly notify the Contracting Officer of this communication or action.

The Contractor shall not perform any inherently governmental actions under this contract. No Contractor employee shall hold him or herself out to be a Government employee, agent, or representative. No Contractor employee shall state orally or in writing at any time that he or she is acting on behalf of the Government. In all communications with third parties in connection with this contract, Contractor employees shall identify themselves as Contractor employees and specify the name of the company for which they work. In all communications with other Government contractors in connection with this contract, the Contractor employee shall state that he/she has no authority to, in any way, change the contract and that if the other contractor believes this communication to be a direction to change their contract, they should notify the Contracting Officer for that contract and not carry out the direction until a clarification has been issued by the Contracting Officer.

The Contractor shall insure that all of its employees working on this contract are informed of the substance of this article. Nothing in this article shall limit the Government’s rights in any way under the other provisions of the contract, including those related to the Government’s right to inspect and accept the services to be performed under this contract. The substance of this article shall be included in all subcontracts at any tier.

10 Post Award Administration The Contractor’s performance shall be evaluated in accordance with the contractor’s adherence to the requirements stated in the SOW. At a minimum, the Contractor’s performance shall be evaluated on an annual basis and at task completion.

11 Deliverables

11.1 Preservation, Packaging, Packing and Marking

The contractor shall deliver all electronic versions by submission to the COR.

Identified below are the required electronic formats, whose versions must be compatible with Microsoft 2010 versions.

• Text: Microsoft Word

• Spreadsheets: Microsoft Excel

• Briefings: Microsoft PowerPoint

• Drawings: Microsoft Visio

• Schedules: Microsoft Project

11.2 Place of Inspection and Acceptance

(For all CLINs) Inspection and acceptance of all work performance, reports and other deliverables under this contract shall be performed by the DOL Contracting Officer’s Representative (COR).

11.3 Scope of Inspection and Acception

All deliverables will be inspected for content, completeness, accuracy and conformance to the SOW by the COR.

Inspection may include validation of information or software through the use of automated tools and/or testing of the deliverables, as specified in the Statement of work. The scope and nature of this testing must be negotiated prior to Statement of Work award and will be sufficiently comprehensive to ensure the completeness, quality and adequacy of all deliverables.

11.4 Timing of Acceptance

The Government requires a period not to exceed fifteen (15) work days after receipt of final deliverable items for inspection and acceptance or rejection.

11.5 Basis of Acceptance

(For all CLINs) The basis for inspection/acceptance shall be compliance with the requirements set forth in the Statement of work, the contractor’s proposal and other terms and conditions of the contract including the Government Quality Assurance Surveillance Plan (QASP)/Quality Control Plan (QCP). Deliverable items rejected shall be corrected in accordance with the applicable clauses.

Reports, documents and narrative type deliverables will be accepted when all discrepancies, errors or other deficiencies identified in writing by the Government have been corrected.

If the draft deliverable is adequate, the Government may accept the draft and provide comments for incorporation into the final version.

All of the Government's comments to deliverables must either be incorporated in the succeeding version of the deliverable or the contractor must demonstrate to the Government's satisfaction why such comments should not be incorporated.

If the Government finds that a draft or final deliverable contains spelling errors, grammatical errors, improper format, or otherwise does not conform to the requirements stated within SOW, the document may be immediately rejected without further review and returned to the contractor for correction and resubmission.

11.6 Initial Deliverables

(For all CLINs) The Government will provide written acceptance, comments and/or change requests, if any, within ten (10) work days from receipt by the Government of the initial deliverable.

Upon receipt of the Government comments, the contractor shall have ten (10) work days to incorporate the Government's comments and/or change requests and to resubmit the deliverable in its final form.

The Government shall provide written notification of acceptance or rejection of all final deliverables within fifteen

(15) work days. All notifications of rejection will be accompanied with an explanation of the specific deficiencies causing the rejection.

11.7 Non-Conforming Products or Services

Non-conforming products or services will be rejected. Deficiencies will be corrected, by the contractor, within ten

(10) work days of the rejection notice. If the deficiencies cannot be corrected within ten (10) work days, the contractor will immediately notify the Government of the reason for the delay and provide a proposed corrective action plan within ten (10) work days.

12 Access to Government Electronic Mail All Contractor staff that have access to and use of the Government electronic mail (e-mail) must identify themselves as contractors on all outgoing e-mail messages, including those that are sent in reply or are forwarded to another user. To best comply with this requirement, the contractor staff shall set up an e-mail signature ("Auto Signature") or an electronic business card ("V-card") on each contractor employee's computer system and/or Personal Digital Assistant (PDA) that will automatically display "Contractor" in the signature area of all e-mails sent.

13 Invoice Submission For all invoices, the contractor shall provide invoice backup data, including a summary of all work completed. The contractor shall use electronic system to submit invoices.

14 Invoicing Instructions A monthly invoice for each statement of work shall be submitted not later than 5 work days after acceptance by the Government of the product, service and/or cost item. A separate invoice for each statement of work shall be submitted on official company letterhead with detailed costs for each of the following categories:

• Total labor charges

• Total invoice amount

• Prompt payment discount offered (if applicable)

For Labor Hour tasks, the amount invoiced shall include labor charges for actual hours worked and other actual expenses based upon contract rates and conditions, not to exceed the limits specified in the statement of work and that have been accepted by the Government.

For other direct costs (none are expected) such as equipment, travel, per diem, subcontractor labor, etc., invoices shall reflect the contractor's actual expense for the item, plus General and Administrative costs (G&A) These charges shall not exceed limits specified in the statement of work. No charges will be paid by the Government, which are not specifically detailed in the individual statement of work and specifically approved in the underlying contract.

15 Travel No travel is anticipated under this contract.

16 Travel Regulations Not applicable.

17 Contracting Officer’s Representative (COR)

a. A Contracting Officer’s Representative (COR) may be appointed to assist the Contracting Officer in administration of this statement of work.

b. When the appointment of a COR is deemed necessary, the Contracting Officer will issue the formal Letter of Appointment defining the scope and limitations of the authority of the designated COR. A copy of the COR appointment letter will be maintained in the contract file.

c. In no event is the COR authorized to direct any action which:

a) Exceeds the scope or limitations specified in the Letter of Appointment; or

b) Constitutes a change to the Statement of Work (SOW) or any other term or condition of the contract/statement of work. Such changes may be authorized only upon written notification by the contracting officer.

18 Organizational Conflict of Interest If the contractor is currently providing support or anticipates providing support to the U.S. Department of Labor that creates or represents an actual or potential organizational conflict of interest (OCI), the contractor shall immediately disclose this actual or potential OCI in accordance with FAR Part 9.5. The contractor is also required to complete and sign an Organizational Conflict of Interest Statement in which the contractor (and any subcontractors, consultants or teaming partners) agree to disclose information concerning the actual or potential conflict with any proposal for any solicitation relating to any work in the statement of work. All actual or potential OCI situations shall be handled in accordance with FAR Subpart 9.5.

19 Non-Disclosure Requirements All contractor personnel (to include subcontractors, teaming partners and consultants) who will be personally and substantially involved in the performance of the statement of work issued which requires the contractor to act on behalf of, or provide advice with respect to any phase of an agency procurement, as defined in FAR 3.104-4, shall execute and submit an “Employee/Contractor Non-Disclosure Agreement” Form. This is required prior to the commencement of any work on such statement of work and whenever replacement personnel are proposed under an ongoing statement of work. Any information obtained or provided in the performance of this statement of work is only to be used in the performance of the statement of work.

20 Security Considerations No access to classified documents is required.

21 Transfer of Hardware/Software Maintenance Agreements to Follow-On Contractors The contractor shall ensure that all hardware/software agreements entered into under this contract are transferable to the Government and/or to other contractors at the discretion of the Government.

22 Privacy Act Work on this project may require that personnel have access to Privacy Information. Personnel shall adhere to the Privacy act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

23 Contract Closeout The contractor shall submit a final invoice within forty-five (45) calendar days after the end of the Performance Period. After the final invoice has been paid the contractor shall furnish a completed and signed Release of Claims to the Contracting Officer. This release of claims is due within fifteen (15) calendar days of final payment.

24 Past Performance Information In accordance with FAR 42.15 Contractor Performance Information, past performance evaluations shall be prepared for each contract that exceeds the simplified acquisition threshold. For severable contracts, interim evaluations will be required prior to exercising any option periods. For non-severable contracts, evaluations must be collected, coordinated and reported upon completion of the contract.