BEA_Statistical_Modernization_Support_PWS_DRAFT_1.pdf

U.S. DEPARTMENT OF COMMERCE

BUREAU OF ECONOMIC ANALYSIS

PERFORMANCE WORK STATEMENT

FOR

BEA STATISTICAL MODERNIZATION

SUPPORT

BEA STATISTICAL MODERNIZATION SUPPORT

1. Overview

This is a non-personal services contract. The Government will not exercise any supervision or control over the contract’s service providers performing the services herein. Such contract’s service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government as defined in this Performance Work Statement (PWS). The Contractor shall perform to the standards in this Contract.

2. Background

The Bureau of Economic Analysis (BEA) is an agency of the Department of Commerce.

BEA produces economic accounts statistics that enable government and business decision-makers, researchers, and the American public to follow and understand the performance of the nation's economy. To do this, BEA collects source data, conducts research and analysis, develops and implements estimation methodologies, and disseminates statistics to the public.

BEA is one of the world's leading statistical agencies. Although it is a relatively small agency, BEA produces some of the most closely watched economic statistics that influence the decisions made by government officials, businesspeople, households, and individuals. BEA's economic statistics, which provide a comprehensive, up-to-date picture of the U.S. economy, are key ingredients in critical decisions affecting monetary policy, tax and budget projections, and business investment plans. The cornerstone of BEA's statistics is the national income and product accounts (NIPAs), which feature the estimates of gross domestic product (GDP) and related measures.

The GDP was recognized by the Department of Commerce as its greatest achievement of the 20th century and has been ranked as one of the three most influential measures that affect U.S. financial markets. Since the NIPAs were first developed in the aftermath of the Great Depression, BEA has developed and extended its estimates to cover a wide range of economic activities.

Today, BEA prepares national, regional, industry, and international accounts that present essential information on such key issues as economic growth, regional economic development, interindustry relationships, and the nation's position in the world economy.

3. Objective

BEA’s modernization program continues to enable the Bureau to move resources from back-office functions to developing and disseminating new and updated statistics. The purpose of this agreement is to support BEA’s Office of the Chief Information Officer (OCIO) in the ongoing development, enhancement, operation, and maintenance of the Bureau’s statistical systems.

4. Requirement

BEA maintains a portfolio of estimation processing subsystems that form the technological foundation for the timely, accurate, and comprehensive release of BEA’s economic statistics. The BEA Estimation IT System (BEA-EITS) is made up of these highly integrated and interdependent subsystems. The BEA-EITS supports the production of 15,000 time series each month and hundreds of thousands of other data produced quarterly and annually.

BEA’s Statistical Production Modernization program supports the generation of some of the nation’s most important economic indicators. The program supports efficient processing of millions of time series of economic data on a monthly, quarterly, annual, and benchmark (3+ years) schedule. To successfully support these processing demands, BEA has developed a “OneBEA” database architecture that support the Bureau’s mission drivers of timeliness, accuracy, and comprehensiveness of its statistical releases. Features of BEA’s OneBEA architecture include:

Metadata driven database Systems In BEA’s OneBEA architecture, the business functionality of each statistical system is not programmed into the system’s code but is instead represented by configuration/control data, called metadata. Metadata is combined with the regular data at run-time to achieve desired results.

Graph Data Structures In BEA’s OneBEA architecture, computational efficiency is achieved by using graph data structures (more specifically, weighted directed acyclic graphs - wDAGs) in a relational database environment.

Several core databases have been deployed with this common architecture and several additional are under development. Existing databases using this architecture and operating in a production environment currently calculate key economic statistics for the United States including Gross Domestic Product (GDP), Personal Income and Outlays, GDP by Industry, Input-Output Statistics, GDP by State, among numerous other statistical series. These systems and subsystems must operate efficiently, predictably, and reliably; upgrades to these systems must be implemented with adherence to the bureau’s stringent release schedule with minimal downtime.

The Contractor shall provide full Software Development Life Cycle (SDLC) support for the BEA–EITS, its subsystems, and underlying IT architecture components. The Contractor shall have demonstrated expertise and experience to support current applications and developing new applications which adhere to the OneBEA architecture, which include:

• Creation of database objects within SQL Server databases.

• Creation of database table objects within SQL Server databases that comply with third normal form

(3NF) database normalization.

• Development and storage of business logic within exogenous metadata external to backend database objects and calculation engines.

4.1 Requisite Functional Experience

The Contractor shall provide evidence that demonstrates expertise and experience in the following areas that are required to support BEA’s modernization program:

• Proven experience developing complex econometric calculations (i.e., multi-dimensional aggregation, primary and secondary suppression, chain-type price indexes, etc.) in SQL utilizing multi-dimensional tree and graph processing.

• Proven experience developing metadata-driven systems in relational database management systems. The calculation engine code must operate over taxonomies, graph relationships, and formulas provided via an exogenous metadata file. The metadata file must be maintained in a format easily read and modified by non-technical analysts.

• Proven experience developing high-performance SQL-based systems that process (i.e., perform the calculations described above) very large datasets (i.e., from 100’s of gigabytes to N terabytes in size) in minutes if not seconds.

• Proven experience Applications that support the production of some of the nation’s most critical economic statistics, must be able to leverage efficiencies and easily respond to changes in available source data, modifications to tree and graph structures, and produce new review and analysis tables without significant modifications to the underlying source code.

• Proven experience and expertise recognizing commonalities in statistical methodologies across program area processes to leverage existing components of the BEA portfolio across multiple applications.

• Proven experience and expertise with survey data processing. One of the major applications that reside within the BEA Estimation IT System processes base level source data (surveys). The application supports vital statistics on Direct Foreign Investment across multiple surveys and unites processing of multiple surveys under one technical umbrella.

• Proven experience incorporating multidimensional drill down capability in the database applications that enables audits from source data to output.

• Proven experience maintaining within the database the history of database content and configuration management data that maintains an audit of code/schema changes.

• Proven experience incorporating system monitoring solutions that maintain command and control capabilities within a database application.

4.2 Requisite Technical Capabilities

The Contractor shall provide evidence that demonstrates expertise and experience in the following technical components of the OneBEA architecture:

• Database Management Systems o Microsoft SQL Server versions 2019, 2022, 2025

• Data Modeling Tools o Erwin data modeling software

• Markup Languages o Hypertext Markup Language (HTML) o Markdown

• Programming Languages o Structured Query Language (SQL) o Python o R

• Software Development Tools o SQL Server Management Studio o Visual Studio Code

• Source Code Management Tools o Azure DevOps o Git

• Text-Based Data Formats o Comma Separated Values (CSV) o extensible Markup Language (XML) o Java Script Notation Language (JSON) o Yet Another Markup Language (YAML)

BEA has utilized several contractors over the last 15 to 20 years to provide the types of application development services and support described in this Performance Work Statement (PWS). Based on the successes and failures of these prior contractual engagements, BEA has determined that due to the unique nature of developing and supporting applications that process economic accounts and socio-economic statistics, the Contractor proposal must demonstrate significant prior specialized experience providing technical support to an agency within the federal statistical systems which utilize graph data structures.

5. Tasks

5.1 Lead database development activities for the Bureau’s statistical systems. This includes guiding the development process through the phases of the BEA Software Development Life Cycle (SDLC).

5.2 Develop Database schemas and code that incorporate the technical standards of the OneBEA architecture (described above).

5.3 Develop statistical production applications using the OneBEA architecture (described above).

5.3.1 Complete database development, modernization, and enhancement (DME) activities for the Bureau’s centralized statistical systems as identified in the deliverable tables below.

5.3.2 Maintain and enhance current production statistical systems developed in accordance with the OneBEA architecture (as described above).

5.3.3 Maintain and enhance current shared production statistical system components developed in accordance with the OneBEA architecture (described above).

5.4 Enhance SQL based software code implemented into BEA centralized statistical systems that produce the following outcomes:

5.4.1 Enables users to select multiple dimensional data over a desired series of time.

5.4.2 Generates and store business logic into SQL database tables for interaction with the data services application system.

5.4.3 Manages the creation, authorization, registration, execution, and monitoring, of data services that facilitate the querying, processing, and transformation of data to upstream client applications in data formats that include:

5.4.3.1 Comma-separated values (CSV)

5.4.3.2 Extensible Markup Language (XML)

5.4.3.3 JavaScript Object Notation (JSON)

5.5 Develop secure gateways to support querying and data transfers from existing Microsoft SQL server based statistical systems for R, Python, and other off-the-shelf software products.

5.6 Provide SQL training to BEA Economists, Statisticians, and IT Specialists through a curriculum of classical SQL and specialized courses. These courses shall cover the following areas:

5.6.1 SQL programming styles

5.6.2 SQL advanced declarative techniques

5.6.3 SQL Tree and graph algorithms

5.6.4 Common utilities within the OneBEA architecture.

5.6.5 Maintenance of SQL based software code implemented within centralized statistical systems in the OneBEA architecture.

5.7 Assist in the migration of statistical systems to the latest versions of Relational Database

Management Software (RDBMS) through software feature evaluation and testing.

5.8 Develop and maintain documentation for all activities identified in tasks 5.1 through 5.7.

6. Contract Type

The projects to be undertaken under this contract vary significantly in scope, complexity, and duration therefore this contract shall be a Labor Hours effort. BEA estimates the annual level of effort (LOE) as identified in the chart below.

Labor Category Hours Subject Matter Expert Level 1 2,000

Subject Matter Expert Level 2 2,000

Application Engineer Level 1 2,000

Application Engineer Level 1 2,000

Technical Writer/Editor Level III 1,000

Application Programmer Level III 2,000

Application Programmer Level III 2,000

Project Manager Level I 600

Total 13,600

7. Period of Performance

The total period of performance with all options exercised shall be one one-year base period and one one-year optional period from the date of award.

8. Place of Performance

The primary place of contract performance will be at the Bureau of Economic Analysis, 4600 Silver Hill Rd, Suitland, MD 20746. The Contractor must follow the BEA on-site reporting requirements.

Remote/telework may be authorized in writing by the COR on a case-by-case basis.

9. Hours of Operation

Under this contract, the Contractor is responsible for conducting business, Monday through Friday during normal business hours except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closing.

Other tours of duty may be arranged as directed by the BEA Contracting Officer’s Representative (COR) in writing. The Contractor may be required to perform activities such as critical upgrades outside normal operating hours to minimize disruption of BEA’s estimates production.

FEDERAL HOLIDAYS

Listed below are recognized Government holidays.

New Year’s Day Labor Day Martin Luther King Jr. Birthday Columbus Day

President’s Day Veteran’s Day Memorial Day Thanksgiving Day

Independence Day Christmas Day

Juneteenth National Independence Day Any other day designated by Federal Statute and/or Executive Order

Unless otherwise authorized by the COR, observance of holidays by Government personnel shall not otherwise be a reason for an extension to the period of performance, delivery schedule, or entitlement of payment by the Government to the Contractor. In the event the Contractor’s personnel (including subcontractor) work during the holiday, they may be compensated for the work in accordance with the Contractor’s operational/employee/business procedures; however, no form of holiday or other premium compensation will be paid by the Government, either as an additional direct or indirect cost, over the payments authorized in this contract.

When the Government grants excused absence to its employees (example: office closing due to inclement weather), onsite Contractor personnel may be dismissed by the Contractor at its discretion. However, such a dismissal will not be an excuse to change any service or delivery requirements under this contract.

10. Productive Direct Labor Hours

The Contractor can only charge the Government for “Productive Direct Labor Hours”. “Productive Direct Labor Hours” are defined as those hours expended by Contractor personnel in performing work under this contract. Productive Direct Labor Hours do not include sick leave, vacation, Government or Contractor holidays, jury duty, military leave, or any other kind of Government administrative leave occasioned by closures or disruptions due to acts of God (i.e. hurricanes, snowstorms, tornadoes, etc.)

Presidential funerals or any other events.

11. Payment for Unauthorized Work

No payments will be made for any unauthorized supplies or services or for any unauthorized changes to the work specified herein. This includes any services performed by the Contractor of their own will or at the request of an individual other than a duly appointed Contracting Officer. Only a duly appointed Contracting Officer is authorized to change the specifications, terms, and conditions of this contract.

12. Contractor Personnel

The Contractor will be responsible for managing and overseeing the activities of all Contractor personnel, as well as subcontractor efforts used in performing this contract. The Contractor's management responsibilities must include all activities necessary to ensure timely and effective support, performed in accordance with the requirements contained in the Performance Work Statement and tasks. Resumes submitted for employees assigned to perform under this Performance Work Statement must contain documented and demonstrated experience directly applicable and of sufficient variety and sufficient duration demonstrating that the employee is able to effectively and efficiently perform the functions assigned.

13. Project Manager

The Contractor must provide a Project Manager to oversee the Contractor’s overall effort and to facilitate Government-Contractor communications. The Project Manager will be the Contractor’s primary technical and managerial interface with the Contracting Officer (CO) and the Contracting

Officer’s Representative (COR) located at Bureau of Economic Analysis, 4600 Silver Hill Rd, Suitland, MD.

The name of this person, and an alternate or alternates, who shall act for the Project Manager when he/she is absent, must be provided in writing to the CO and COR. The Project Manager or alternate will have full authority to act for the Contractor on all contract matters relating to daily operations.

The Project Manager or alternate must be available during normal duty hours, as specified herein, and to meet with Government personnel within 24 hours to discuss problems.

The Contractor's Project Manager will meet with the CO/COR as necessary to maintain satisfactory performance and to resolve other issues pertaining to Government/Contractor procedures. The Project Manager or alternate must be available during normal duty hours to meet with Government personnel within 24 hours of a request by the CO or COR. At these meetings, a mutual effort will be made to resolve any identified problems. Written minutes of these meetings shall be prepared by the Contractor, signed by the Contractor's designated representative, and furnished to the Government within two (2) workdays of the meeting.

14. Personnel Requirements

The Contractor shall assign to this contract the following key personnel.

Subject Matter Expert Application Engineer Application Programmer

The Contractor must obtain the consent of the Contracting Officer prior to making key personnel substitutions. Replacements for key personnel must possess qualifications equal to or exceeding the qualifications of the personnel being replaced unless an exception is approved by the Contracting Officer.

Requests for changes in key personnel must be submitted to the Contracting Officer at least 30 working days prior to making any permanent substitutions. The request should contain a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. The Contracting Officer will notify the contractor within 10 working days after receipt of all required information of the decision on substitutions. The contract will be modified to reflect any approved changes.

14.1 Key Personnel Definition

Certain skilled experienced professional and/or technical personnel are essential for accomplishing the work to be performed. These individuals are defined as "Key Personnel" and are those persons whose resumes were submitted and marked by the Contractor as "Key Personnel.” Substitutions shall only be accepted if in compliance with “Substitution of Key Personnel" provision identified below.

14.2 Substitution of Key Personnel

Whenever possible, all Contractor requests for approval of substitutions hereunder shall be submitted in writing to the COR least (30) calendar days in advance of the effective date and shall provide a detailed explanation of the circumstances necessitating the proposed substitution, a complete resume for the proposed substitute, and any other information requested by COR necessary to approve or disapprove the proposed substitution. The COR will evaluate such requests and promptly notify the Contractor of approval or disapproval in writing.

15. Deliverables

Deliverables outside of the deliverables mentioned in this section will be provided on an as-needed basis and determined by the COR. All deliverables shall be written in clear and precise language that follows structured writing/coding techniques to the maximum extent practicable.

15.1 Project Plan

The Contractor shall prepare a Project Plan in Microsoft Word format, to the COR in writing. The project plan shall describe the technical approach, organizational resources, and management controls to be employed to meet the cost, performance, and schedule requirements for each project under this contract. The Project Plan shall detail the key activities and milestones, distance learning technology, allocation of staff and other resources necessary for successful completion of this effort.

The Contractor will not proceed on any activity until the Project Plan applicable has been approved by the COR in writing. The Contractor shall request to the COR in writing prior approval on any change to the project plan after COR approval has been given.

15.2 Weekly Status Report

The Contractor shall document efforts performed in completing each task in a detailed Weekly Status Report due each week to be submitted in PDF to the BEA COR and BEA Task Manager. The Status Report shall include, at a minimum:

o Contract Name:

o Contract Period of Performance:

o Reporting Period:

o BEA COR:

o BEA Task Manager:

o Contractor Project Manager:

o Contractor Summary of Accomplishments, Activities and Key Meetings for the week: This section should have a detailed breakout for each individual contractor billed to the contract with each person reporting the following.

Contractor Name Contractor Labor Category Contractor Hours Billed by Project for the week.

15.3 Monthly Status Report

15.3.1 Reporting Requirements

Earned Value Management: The Contractor and all subcontractors shall use program management methods and earned value reporting that meet best business practice guidelines provided in the Electronic Industries Alliance standard, “ANSI/EIA-748, Earned Value Management Systems.” The

ANSI/EIA-748, Earned Value Management Systems standard is available from Global Engineering Documents and may be purchased either online at http://global.ihs.com/ or by phone at 1-800-854- 7179.

The Contractor shall document efforts performed in completing each task in a detailed Monthly Status Report due on or before the 10th of each month. The Status Report shall include, at a minimum:

• Progress for the period: Summary, by task, of work accomplished during the reporting period and percent complete followed by a detailed progress report of significant findings, activities, and accomplishments during the reporting period.

• Activities planned for the next reporting period: Planned activities, as well as the status of any/all deliverables, including actual and planned delivery date(s).

• Problems encountered: Identification of any problems, issues or delays and recommendations as to their resolution, and any corrective action taken to correct identified problems.

• Strategy revisions: Recommended changes to include any lessons learned.

• Contract Details: Contract number and reporting period

• Summary of Work: Summary of work accomplished during the reporting period and percentage complete. Additionally, a detailed progress report of findings shall be included, providing activities and accomplishments during the reporting period.

• Summary of Planned Work: Summary of planned activities for the next reporting period, as well as the status of work products, including planned delivery dates (actual or estimated).

• Strategy revisions: Provide change recommendations, to include any lessons learned.

• Expenditure Plan and Status: Provides COR-approved expenditure plan and actuals, indicates current funding level, and highlights the expected date at which 75% of funds will be expended. Any deviations greater than 5% must be explained. The expenditure plan, once approved by the COR, cannot be changed without justification and COR approval.

• Invoice Status: Provides a summary listing of invoices. The listing shall include invoice #, date, period of performance, amount, and payment status.

http://global.ihs.com/

15.4 Deliverable Table

As BEA prioritizes this contract’s requirements, the deadlines identified below may change. The BEA COR will notify the contractor at least 30 days in writing if BEA issues a change to any of the deadlines in the following charts.

Overall Contract Deliverable Table

Milestone/Deliverable Responsibility Deadline Contract Kick Off Government/Contractor Within 14 days of Contract Award

Final Quality Assurance Plan Contractor Within 30 days of Kick Off

Transition-In Plan in MS Word Contractor Draft submitted no later than seven (7) calendar days after award.

Final submitted no later than 30 calendar days after award.

Transition-Out Plan in MS Word Contractor Draft submitted no later 90 calendar days before the end of the Contract period of performance.

Final – submitted no later than 45 calendar days before the end of the Contract period of performance.

Project Plan for each Project Contractor Mutual agreement BEA and the Contractor

Weekly Status Report Contractor Mutual agreement BEA and the Contractor Monthly Status Report Contractor By the 10th day of the month.

Final Report for each Project Contactor Mutual agreement BEA and the Contractor

Development, Modernization, and Enhancement (DME) Deliverable Table

National Directorate

Milestone/Deliverable Responsibility Deadline

Complete development of the balancing automation framework

Contractor Base Period of the contract

Complete translation of industry satellite modules to operate in the Industry Estimation Processing (IEP) environment.

Contractor Base Period of the contract

Complete update of benchmark only capabilities in the IEP environment in preparation for the 2028 comprehensive update.

Contractor

Base Period of the contract

Develop estimate profile framework in the IEP environment in preparation for the 2028 comprehensive update.

Option Period 1 of the contract

Implement decentralized ownership/centralized execution Python-to- SQL database bridging framework.

Option Period 1 of the contract

International Directorate Deliverable Table

Milestone/Deliverable Responsibility Deadline

Automate the transfer of the Direct Investment Division’s (DID) publication data from the Universe Aggregation (UA) system to BEA’s iTable application.

Contractor Base Period of the contract

Update functionality of DID’s Survey Processing System (SPS) to allow survey editors to change forms for reported documents without manual entry.

Contractor Base Period of the contract

Automate the transfer of the Balance of Payment Division’s (BPD) publication data from the OneBEA Data Platform (OBDP) to BEA’s iTable application.

Contractor Base Period of the contract

Add functionality to the Sustainability Framework and the Model Of Operations for Statistical Estimation (MOOSE) to support contextual documentation generation, role and skill management, workflow analysis, and equivalent-task tracking.

Contractor Base Period of the contract

Update OBDP to support more compact metadata to specify non-orthogonal multi-dimensional aggregation.

Contractor Base Period of the contract

Update SPS to allow survey data to move across periods.

Contractor Option Period 1 of the contract

Update the SPS, UA, and Universe Estimation (UE) systems to incorporate data checks, including outlier detection.

Contractor Option Period 1 of the contract

Incorporate the stacked charts and data explorer modules from the Regional Directorate’s Geographical Regional Integrated Development System (GRIDS) system to provide hierarchical drilldown and charting functionality in OBDP.

Contractor Option Period 1 of the contract

Update the Current Account Services Branch (CASB) Utility to operate on additional dimensional sets for use more generally in the International Accounts.

Contractor Option Period 1 of the contract

Regional Directorate Deliverable Table

Milestone/Deliverable Responsibility Deadline

Update the OneBEA Data Platform (OBDP) application for subnational data processing

Contractor Base Period of the contract

Incorporate the Research and Development (R&D) satellite account and Income Distribution account into the Geographical Regional Integrated Development System’s (GRIDS) editing, review, and publication modules.

Contractor Base Period of the contract

Migrate functionality within the Regional Income Processing System (RIPS+) application to GRIDS.

Contractor Base Period of the contract

Update the Public Table module within the GRIDS and RIPS+ systems.

Contractor Base Period of the contract

Migrate functionality within the Regional Income Processing System (RIPS+) application to GRIDS.

Contractor Option Period 1 of the contract

OneBEA Deliverable Table

Milestone/Deliverable Responsibility Deadline

Update the Python to SQL Bridge library (PythonDBSrv) to allow backend data services to be discoverable.

Contractor Base Period of the contract

Develop data backend services to provide details on the content of metadata in centralized systems.

Contractor Base Period of the contract

Implement an AI Readiness data tagging framework for BEA published datasets.

Contractor Option Period 1 of the contract

Implement the current version of the Python to SQL Bridge library as an internal Application Programming Interface (API) application.

Contractor Option Period 1 of the contract

Incorporate back-end SQL interface with Azure DevOps/Pipelines to support automated code deployment, configuration management, and regression testing for modernized SQL systems.

Contractor Option Period 1 of the contract

Office of the Chief Information Officer Deliverable Table

Milestone/Deliverable Responsibility Deadline

Complete user guide and technical documentation of National statistical systems.

Contractor Base Period of the contract

Develop backend data services to support the conversion of the underlying technology of the user interface of the SPS application from ColdFusion to Microsoft .Net.

Contractor Option Year 1 of the contract

Support the evaluation of latest version of SQL Server for use on BEA centralized systems.

Contractor Option Year 1 of the contract

16. Contractor Personnel Security Management Requirements for BEA Spaces at the Suitland Federal Center (SFC), Facility ID 1822

16.1 Administrative

Personnel

• All contract personnel selected to perform on this effort are subject to Government suitability.

In no case will the contractor submit personnel as part of an initial response, when it is not the true intent for that individual to perform on the subsequent award of this requirement. The contractor shall strive to maintain the same team throughout the period of performance on this contract. The contractor shall keep its workforce trained, proficient and knowledgeable about industry/Government best practices and methodologies. The contractor shall provide resumes of all potential candidates to the Government Contracting Officer Representative (COR) in advance of any personnel decisions. The Government will retain the right of refusal for any person determined incapable of performing analytical duties in accordance with Contract requirements.

Key Personnel

• All personnel assigned to this contract will be considered key personnel. The contractor must submit resumes of all qualified, proposed candidates to the COR for review. The contractor must receive written approval from the COR prior to assigning personnel to this contract.

Training

• The Contractor, as required by the Government, shall complete the required training and certifications to maintain physical/logical access to BEA spaces.

Codes and Regulations

• The Contractor will comply with Government facility codes, security regulations and COR directives, as well as applicable safety policies/procedures.

16.2 General Qualifications

Personal Identity Verification (PIV) of Contractor Personnel

• Employment Eligibility Verification (E-Verify) - The Contractor shall use the E-Verify System administered by the Department of Homeland Security, U.S. Citizenship and Immigration Services to verify that all new contractor hires and existing employees directly performing work under Federal contracts are authorized to work in the United States according to Federal Acquisition Regulation (FAR) Subpart 22.18.

• The Position Designation Level for this contract will be Low/Moderate/High Risk as determined by COR using the Office of Personnel Management’s (OPM) Position Description Tool (PDT), with no National Security Sensitivity; see Attachment 1, IT Compliance in Acquisition Checklist v3.4.

The minimum investigation required for Contractor personnel shall be Tier 1 – Low Risk;

however, a Tier 2 – Moderate Risk or Tier 4 – High Risk may be justified. Contract employees will process through the BEA Security for required investigative actions.

• The contract employees must present RealID Act compliant credentials and shall process for PIV issuance through BEA Security. Processing procedures meet standards detailed in the Office of Management and Budget (OMB) guidance M-05-24 and Federal Information Processing Standards Publication (FIPS PUB) Number 201.

• The Contractor may be required to have access to live data and/or sensitive information and resources during performance of this contract. Authorized access to such information and will require signature and acceptance of a Nondisclosure Agreement (NDA), see Exhibit 2.

• The Contractor shall provide security information 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.

• The results of these investigations shall be provided to the ordering activity Federal Government COR upon request and provide proper protection and privacy of individual’s information.

16.3 Contractor U.S. Citizenship Requirements

• Contractors are hereby placed on notice that work on some orders, especially those requiring site visits to some U.S. Government locations or work on some Government Furnished Property, may require Contractor personnel to have U.S. citizenship and provide proof of that citizenship. This shall be provided at no cost to the Government.

16.4 Identification Requirements

• All Contractor personnel shall be clearly identified by display of a valid badge provided by the Government. As determined by the COR, the badge may serve as a card to allow access to controlled areas. Contractor personnel must return promptly to the COR any badge upon request of the Government, termination of employment with the Contractor, expiration of the badge, or expiration of the contract. The Contractor shall bear the cost of any lost or damaged badge. The cost shall be the amount generally charged by the Government to other personnel at the time when the loss is reported

16.5 Standards of Conduct

• The Contractor and all contract personnel shall follow all Federal and Department Rules of Conduct. Firearms, smoking, alcoholic beverages, illegal drugs, fighting, horseplay, and cursing on Department property by Contractor personnel are not allowed; shall not be tolerated; and could result in the individual or individuals being expelled from the site indefinitely.

16.6 Security

Privacy or Security Safeguards

• The Contractor shall be responsible for properly protecting all information used, gathered, or developed as a result of work under this contract. The Contractor shall also protect all Government data, equipment, etc. by treating the information as sensitive. It is anticipated that this information will be gathered, created and stored within the primary work location. If Contractor personnel must receive and remove any information from the primary work area, they must receive COR and BEA Security approval before removal and must protect it to the same extent they would their proprietary data and/or company trade secrets. The use of any information that is subject to the Privacy Act will be utilized in full accordance with all rules of conduct as applicable to Privacy Act Information.

• The Contractor shall not publish or disclose in any manner, without the COR's written consent, the details of any safeguards either designed or developed by the Contractor under this contract or otherwise provided by the Government.

• 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 property and data, the Contractor shall afford the Government access to the Contractor's facilities, installations, technical capabilities, operations, documentation, records and databases.

16.7 Confidentiality and Nondisclosure

• All documents produced for this project are the property of the U.S. Government and cannot be reproduced or retained by the Contractor. All appropriate project documentation will be given to the Department during and at the end of this task order. The Contractor shall not release any information without the written consent of the Contracting Officer. Any request for information relating to the task order presented to the Contractor must be submitted to the Contracting Officer for approval by the customer agency for a response.

• The Contractor is subject to the following provision relating to the protection and nondisclosure of proprietary and other confidential business information:

• Confidential information, as used in this clause means (1) information or data of a personal nature, proprietary about an individual or (2) information or data submitted by or pertaining to an institution or organization, provided that such information in (1) and (2) does not include information which is, or which becomes, public or information which becomes known to the Contractor on a non-confidential basis from a third party source.

• If it is established that information to be utilized under this Contract is subject to the Privacy Act, the Contractor will follow the rules and procedures of disclosure set forth in the Privacy Act of 1974, 5 U.S.C. 522a, and implementing regulations and policies, with respect to systems of records determined to be subject to the Privacy Act.

• Whenever the Contractor is uncertain regarding the proper handling of material under the Contract, or if the material in question is subject to the Privacy Act or is confidential information subject to the provisions of this clause, the Contractor shall obtain a written determination from the COR and BEA Security prior to any release, disclosure, dissemination, or publication. Notwithstanding the above, information which is required to be disclosed by law or legal process shall not be included as confidential information.

• Contractor employees must also comply with all Department policies, rules, regulations and standard operating procedures. The Contractor is bound by all NDAs signed by its employees. In the event that a contractor employee violates any of the terms of the NDA, the Contractor will be considered in breach of contract.

This could result in a termination for default.

17. Transition Planning

17.1 Transition-In Plan

The contractor shall develop a Transition-In Plan that describes the Contractor’s process for transitioning from the incumbent without disruption of operational activities. The plan shall include a schedule of milestones and events for the elements listed in this section below. The contractor shall identify all necessary activities to facilitate the transition of services to the contractor and provide expected completion dates of those activities. The contractor shall maintain responsibility for the transition of all activities identified in this contract. All transition-in activities shall be completed within 90 days after the kickoff meeting. At a minimum, the following activities shall be included as part of the Transition-in Plan:

• Inventory and transfer of all Government Furnished Equipment and Property (GFE/GFP).

• Inventory of software tools used by the contractor.

• Transfer of current modernization project activities.

• Transfer of all application code for modernized systems and other application responsibilities.

• Staff transition timing (e.g., contract identified labor categories for contract staff, contract staff start dates).

• Transfer of technical documentation for all modernized systems and components.

• Transfer of Operations and Maintenance (O&M) processes and procedures of modernized systems.

• Transfer of user guide documentation for all modernized systems and components.

• Coordination of knowledge transfer sessions with the incumbent Contractor.

• Coordination and communication with Government representatives.

• Risks and risk mitigation strategies associated with the change in Contractors.

• Knowledge transfer of configurable data, including usernames and passwords and application settings.

• Transition phases and plans for the new Contractor to become acclimated to government tools, methodologies, and business processes.

• List of any other Government and/or Contractor held information that may be needed by the

Contractor to ensure a successful transition.

The Transition-in Plan shall be approved by the BEA COR.

17.2 Transition-out Plan

The contractor shall provide a final Transition-Out Plan as well as the support necessary to coordinate the transfer of all activities during the 90 calendar-day transition out period. The Transition-Out Plan shall include and/or address the following elements:

• Transfer of all Government Furnished Equipment/Property (GFE/GFP), inventory, peripherals, software, and licenses.

• Transfer of all documentation, both archived and currently in progress

• Briefing on all in-progress and project activities.

• Transfer of current project activities.

• Risks and risk mitigation strategies associated with the change in Contractors.

Attachments

Quality Assurance Surveillance Plan (QASP)

Task Applicability Performance Standard Surveillance

Method Monitoring Performed

Lead database development activities

PWS Section 5, Task 5.1

The development activities follow BEA Software Development Lifecycle (SDLC) phases.

Requirements for development activities are gathered and documented.

Developed software code contains comments.

Testing of software code is documented by the Contractor and program area points of contact.

Deployment of software contains changelog to describe the nature of code updates.

100 percent inspection

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA system owners, and/or the COR.

Develop database schema and code.

PWS Section 5, Task 5.2

Modernized database systems are implemented using technical standards of the OneBEA architecture.

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA system owners, and/or the COR.

Develop statistical production applications

Task 5.3

BEA Statistical system are implemented using the OneBEA architecture to collect, process, and prepare economic estimate data for dissemination.

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA system owners, and/or the COR.

Enhance SQL based software code implemented into BEA centralized statistical systems

Task 5.4

Software code returns multi-dimensional data from databases.

Software code converts data retrieved from databases in human readable data formats.

100 percent inspection

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA system owners, and/or the COR.

Develop secure gateways for statistical systems

Task 5.5

Software code facilitates data transfers from production statistical systems.

Software code facilitates the retrieval and display of data from statistical systems web-based application user interfaces.

The TWG is formed by the date specified.

All TWG meetings outlined in the PWS are held at an appropriate time to get the specified feedback.

100 percent inspection

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA

Memoranda are accurate, comprehensive, clear, well-organized, and error-free.

Provide SQL Training

Task 5.6

Training sessions are conducted by the Contractor and with BEA Economists, statisticians, and IT specialists attending.

Training classes and training are appropriate for the members of BEA partaking in the training sessions.

100 percent inspection

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA system owners, and/or the COR.

Documentation support for PWS tasks

Task 5.8

Documentation of all PWS activities is comprehensive, clear, well organized, and error free.

100 percent inspection

Approval or rejection is completed electronically by BEA business analysts, BEA technical points of contact, BEA