47QFPA20N0002 - USCO ECS RFI.pdf

REQUEST FOR INFORMATION

# 47QFPA20N0002

For The

UNITED STATES COPYRIGHT OFFICE / COPYRIGHT MODERNIZATION OFFICE

ENTERPRISE COPYRIGHT SYSTEM (ECS)

1.0 DESCRIPTION

The U.S. General Services Administration (GSA) Federal Acquisition Service, Region 9, is releasing this

Request for Information (RFI) on behalf of the United States Copyright Office (USCO), in support of registration, recordation, public record, and licensing capabilities, and is seeking information on how an interested contractor could continue development of USCO capabilities into a web-based, cloud-hosted

Enterprise Copyright System (ECS).

This is follow-on market research to an RFI submitted in 2018. Over the last two years, the ECS has been under development by the Library of Congress’ Office of the Chief Information Officer (OCIO), and requirements have been further refined, as explained in section 2.0 below. Development work to-date has largely focused on functionality related to a web-based recordation system, including related ECS platform services. A limited, public pilot of recordation functionality was released in April 2020.

Additional work has included development efforts directed towards a prototype online public records system, foundational work for a replacement web-based registration system, and the selection of supporting technologies to integrate with the ECS. Industry proposals are sought to allow the USCO and

OCIO to explore strategies that might lead to more cost effective and efficient future development.

Responses to this RFI will enhance Government’s knowledge of market capabilities and potential sources, and assist in the Government’s development of future acquisition strategies. The applicable NAICS code for this RFI is 541512 Computer Systems Design Services; with a small business size standard of $30M in average annual receipts.

The goals of this RFI are to:

i. Determine what risks and issues industry sees in assuming development of the ECS and gather information about how industry would mitigate and address such risks and issues.

ii. Gather insight into the proposed approach to completing development and implementing an

ECS and the length of time it would take an industry partner, given its proposed approach and cost, to finalize development of the ECS.

iii. Gather insight as to industry’s assessment of the remaining total cost to develop, implement, and maintain the ECS.

iv. Evaluate any alternative contract funding strategies that may be proposed by industry if this requirement were to be solicited.

This RFI will be posted on the System for Award Management (SAM) and GSA E-buy to ensure the widest dissemination. Interested parties need not respond to both RFIs as they are largely the same.

Interested respondents are requested to complete the items indicated below, including: Section 3.1

Corporate Description and Section 3.2 Corporate Capabilities and Responses.

This RFI is issued for market research purposes only and is not meant to imply there will be a follow-on solicitation for this requirement issued by the Government. This RFI does not commit the Government to solicit or contract for any supply or service whatsoever. Further, GSA and the USCO are not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future solicitation, if any is issued. A solicitation may be synopsized or released on the System For Award Management Contract Opportunities website or it may be released under an existing contract. An acquisition strategy has yet to be determined by the

Government.

2.0 BACKGROUND

For over a century, the USCO has administered the national copyright registration and recordation programs in accordance with the U.S. copyright law. Certain provisions of the Copyright Act, codified in

Title 17 of the U.S. Code, govern the submission, review, indexing, and legal presumptions pertaining to the act of registering claims to copyright and publicly recording documents relating to copyright ownership.

Registration establishes a claim to copyright with the Copyright Office. A certificate of registration creates a public record of key facts relating to the authorship and owner-ship of the claimed work, including the title of the work, the author of the work, the name and address of the claimant or copyright owner, the year of creation, and information about whether the work is published, has been previously registered, or includes preexisting material, and serves as prima facie evidence of the facts stated in that certificate. Registration of a claim in copyright with the USCO is a prerequisite to initiating a copyright infringement claim for US works and for all works, is a prerequisite for the availability of statutory damages and attorney’s fees. Different types of copyrightable works may be registered, including literary works, musical works, dramatic works, pantomime and choreographic works, pictorial, graphic and sculptural works, motion pictures and other audiovisual works, sound recordings, and architectural works.

Documents of transfers of copyright ownership or otherwise pertaining to a copyright may be voluntarily recorded with the Copyright Office. While recordation is voluntary, the law confers certain legal advantages, including priority between conflicting transfers and “constructive notice” of the facts stated in the recorded document to the public if certain requirements are met. Examples of recorded documents include assignments of copyright title, licenses, terminations of transfers, security interests, bequests, and other instruments relating to the ownership or expiration of copyright interests.

The USCO also administers the statutory licensing provisions of the Copyright Act, collecting licensing filing fees and royalties. On behalf of copyright owners, the USCO receives royalties from cable operators for the retransmission of over-the-air television and radio broadcast stations to subscribers, from satellite carriers for the retransmission of distant over-the-air television broadcast stations for private home viewing, and from importers or manufacturers for distributing products that employ digital audio recording technologies.

In accordance with the Copyright Act, the USCO maintains a variety of records that are available for public inspection, including records relating to registration, recordation, and the Office’s administration of statutory licenses. Members of the public seek out these records to find copyright owners and to obtain copies of registration records, recorded documents, registration deposits, and statements of account filed by remitters. Because many of these records pertain to copyrighted works, it is vital that the USCO provide accurate and timely information in its public record.

The Register of Copyrights initiated several public inquiries regarding how best to modernize its transactional systems and integrate them under one ECS. In general, this means:

i. Developing the next generation of web-based registration and recordation capabilities. (1) Including the development of browser agnostic systems. (2) Including the development of a mobile accessible solution for submissions.

ii. Developing a system for efficient ingestion, processing, and tracking of information submitted as required to administer copyright statutory licenses, including primarily the statements of account required under sections 111 and 119 for cable and satellite companies.

iii. Developing a highly searchable web-based catalog of public records with integrated records of registrations and recorded documents featuring intelligent searching, bulk download capability, and potentially capabilities for external databases/applications to pull in or link to information from the system.

iv. Providing a secure mechanism for deposits to be transferred into the custody of the Library of

Congress collections, including as applicable with all electronic files and assets delivered via direct system-to-system transfers.

v. ECS search, reporting, and administrative views will be implemented across all ECS applications.

Search functionality against the live system for USCO staff will provide broad searches, complex targeted searches, and search result filters on multiple indexes, and cover draft applications, submissions, and correspondences at different stages in the process. Reporting functionality will be primarily implemented outside of ECS in a business intelligence tool that provides correlation with additional external data sources. Finally, administrative views in each of the applications will be oriented around ongoing work streams for both staff and supervisors.

vi. Developing the capability to seamlessly navigate between the multiple ECS services.

vii. Developing platform services that provide for a unified user experience, allow for seamless integration of all financial data and customer relationship data with other systems, and allow for robust reporting across all systems, to facilitate the USCO’s reporting needs and requirements.

viii. Providing robust capabilities for the USCO to seamlessly interact with customers by email, phone, web-based inquiry, and other means to provide up-to-date status, procedural advice, and tracking information on all services.

ix. Providing robust capability to manage, track, and retrieve copyright deposits, submitted in both electronic and physical form, in a seamless solution that includes features like alerts for items beyond retention, full-term retention flagging, chain of custody tracking, etc.

x. A flexible, potentially modular design that can adapt to changing requirements, updated policies/regulations/laws with minimal (or no) disruption of the functions of the ECS.

xi. A system that will enable the performer to regularly manage operations and maintenance (O&M) and continuous development activities for a sustained period (5-10 years).

An online ECS is expected to yield innumerable conveniences and benefits to different user groups and underscore the protections and incentives that are associated with timely and accurate filings. These modernization goals will also yield faster processing by the USCO, improve access to copyright records, and initiate integration of historic and contemporary records and a stable IT environment for the future.

2.1 Enterprise Copyright System Workflows/Desired Functionalities

2.1.1. Registration Workflow/Desired Functionality

Applicants who apply for registrations have varying needs depending on experience level and type of work they seek to register. At this time, we envision three ways to apply for registration:

i. Applicants with little to no copyright registration experience would apply using a dynamic application form with a series of questions that guide the applicant through the process. There would be heavy use of validations along this path and opportunities to access help topics through the use of pop ups, hover text, and links to other USCO sources such as The Compendium of U.S.

Copyright Office Practices, 3d ed. (2017) (available at: https://www.copyright.gov/comp3/ ) and newly revised USCO circulars (available at: https://www.copyright.gov/circs/ ).

ii. “Power applicants” and those familiar with the copyright application process would apply using straightforward electronic registration applications that contain some dynamic logic and validations.

iii. Applicants who would like to bypass traditional application forms altogether would be able to link to the USCO database with APIs, or some other format, wherein the applicant uploads data fields that would automatically populate USCO database fields, some of which would contain validations.

All of the types of existing copyright registration applications need to be incorporated or addressed in this system (e.g., group registration options, supplemental registration, renewal, etc.). As USCO regulations and practices must adapt to changes in the law, the system must be adaptable to changes with minimal need for technical intervention. The business should have the ability to make routine changes rapidly without the need for heavy IT support.

For registration applicants, the USCO envisions that the modernized system will, at a minimum, achieve the following:

• Provide the ability to submit applications and copies of deposited works for users with varying experience levels.

• Provide the ability to make corrections to in-process submissions, subject to USCO administrative practices.

• Provide a status tracker to keep applicants informed of progress as their application moves through the registration process, including examination after the user has submitted their application information along with appropriate filing fee and deposit of the work to be registered

• Provide dashboards and other views to allow applicants to track their current and historical activities.

• Centralize correspondence functions, providing the applicant with a consistent location to view, respond, track, search, and review their correspondences for a particular document submission.

For internal staff, the Copyright Office envisions that the modernized system will, at a minimum, achieve

• Allow internal workflows to include efficient examination and correspondence between Copyright

Office staff and the applicant

• Create dashboard-style capability so that managers, supervisors and staff have the ability to monitor pending applications and throughput across the organization.

• Allow work to be easily sortable into subtypes for efficient routing and handling by subject matter experts.

• Generate an official Certificate of Registration following examination and approval.

• Populate an electronic public record system with relevant data fields.

2.1.2. Recordation Workflow/Desired Functionality

For recordation filers, the USCO envisions that the modernized system will, at a minimum, achieve the following:

• Provide the ability to submit documents and works for users with varying experience levels. This includes both online and paper submission workflows (end-to-end).

• Provide access to all submission workflows covered under the Copyright Office’s Recordation service

• Provide the ability to track submissions within an external user’s team or organization

• Provide the ability to make corrections to current or previous submissions

• Provide a status tracker to keep remitters informed of progress as their document submitted for recordation moves through the examination process.

• Provide dashboards and other views to allow remitters to track their current and historical activities.

• Centralize correspondence functions, providing the remitter with a consistent location to view, respond, track, search, and review their correspondences for a particular document submission.

• Provide access to public record, legal document annotated with the volume and document number, and official Certificate of Recordation that resulted from the recordation service to be recorded.

For internal staff, the Copyright Office envisions that the modernized system will, at a minimum, achieve

• Allow internal workflows to include efficient examination and possible correspondence between USCO staff and the remitter (once the user has submitted their information along with appropriate filing fee and documentation).

• Build views to allow Copyright office staff to effectively carry out the following (actions may vary depending on submission type): package, inspect, ingest data, scan, route, examine, and process online and paper submissions (actions not listed in a specific order).

• Provide LIB and Copyright Office staff an area to add and tag internal facing notes

• Allow work to be easily sortable into subtypes for efficient routing and handling by subject matter

• Generate an official Certificate of Recordation following examination and approval

• Populate electronic public record system with relevant data fields.

2.1.3. Licensing Workflow/Desired Functionality Example

For licensing remitters, the USCO envisions a system which provides a mechanism to efficiently ingest, process, and share filings made with the USCO Licensing Division. The USCO receives royalty payments, which it holds, invests, and distributes to copyright owners. The USCO charges fees for such filings. The USCO accepts three forms for deposit of royalties and filing fees; while the section 111 form is the longest, the USCO also welcomes a simple manner to ingest and process section 119 and DART forms, and to ingest and display additional licensing-related forms for which the Office does not receive royalty payments.

The Licensing system must encompass the following activities:

• A simple method for ingestion and examination of statements of account forms (or data from the forms) from cable, satellite, and digital audio recording transaction licensees,

• Financial and reporting workflow(s), and integration of budgetary and accounting data with the LBFMS.

• Reporting, display and search functionality (internal and external, including to service annual auditing processes).

• Create dashboard-style analytics for managers and staff, including the ability to monitor submitted statements of account across the organization.

• Allow work to be easily sortable into subtypes for efficient routing and handling by subject matter

2.1.4 Public Record Workflow/Desired Functionality Example

The USCO envisions the following capabilities for the modernized Public Record system:

• A public web site that is easy and intuitive to navigate.

• The capability for users to view relationships between records and easily navigate between them, including to facilitate analysis of relationships between copyrighted works and associated files, such as transfers of title.

• The capability for users to save, share, print, export, or download public records

• Support for consistent data structure and metadata for records.

• Support for non-public access to create, update, and edit records.

• The capability for external databases/applications/APIs to be able to pull in or link to information from the system.

• Provide access to a federated or smart searching capability to quickly search and filter through all USCO records, providing meaningful and useful results, and facilitating user research such as ownership and transfers of title.

2.1.5. Enterprise Capabilities

• Provide the ability to seamlessly navigate to across USCO services housed within ECS.

• Provide user accounts that allow access to all services provided by the Office in a single portal.

• Provide for an online payment collection system using either integration with pay.gov, or another, secure system that provides for USCO collections reconciliation requirements with the U.S. Treasury and with the Library of Congress’s Legislative Branch Financial Management System (LBFMS-Momentum).

• Provide for seamless integration of all financial transactions with the LBMFS.

• Provide for robust financial and statistical tracking and reporting across all systems. Financial and statistical tracking and reporting will consider the needs of USCO customers as well as USCO federal reporting responsibilities as part of the Library of Congress.

• Provide for tracking and monitoring of workflows to facilitate required activity cost allocations between the USCO appropriations and to facilitate the appropriateness of the USCO fee structure.

• Access to / integration with a Help Desk system to manage account, access, and other IT related issues to the system

2.2 Current State of ECS

The Enterprise Copyright System (ECS) has been under active design and development for over 2 years.

In its completed state, the ECS is a suite of modern cloud native applications that use a micro-services architecture to create a robust, scalable and maintainable solution.

The ECS technologies can be broken up into three broad categories: 1) Application 2) CI/CD Pipeline and

3) Infrastructure. We are most interested in using the right tools for the problem at hand and not mandating a single set of tools and technologies. That needs to be tempered with the operation overhead of maintaining a large catalog of technologies. We are open to discussions about adding or removing technologies, with the federal Solutions Architect making the final decision.

The application/UX tier is presently made up multiple technologies as follows.

• Java

• Angular

• Python

• Vue

• Keycloak / Centrify / Login.gov (authentication)

The data / search ties:

• Postgres

• Amazon RDS

• Elastic Search

• AWS Redshift

Our CI/CD Pipeline toolset is made up of:

• Jira issue tracking

• GitLab / Gitlab runners

• Jenkins

• Selenium / Zephyr

• Docker

• SonarQube

Infrastructure:

• Terraform

• Cloud Formation

• Kubernetes / AWS ECS / AWS Fargate

Architecturally, ECS will be comprised of the following major application components:

Component Description Status

Recordation web based system Web based system that allows customers to file Recordation records and internal USCO workflows for examination and approval.

Initial limited public release in April 2020; under active development.

Registration web based system Web based system that allows applicants to file Registration records and internal USCO workflows for examination and approval.

Development initiated;

initial public prototype of

Standard Application release anticipated end of calendar year 2020.

Public Record web based system Web based system that allows customers to search for public record contents and internal

USCO workflows to manage those records.

Active Development; initial public release at end of fiscal year 2020.

ECS Licensing Services Services that support the simple ingestion and processing of statements of account and other licensing-related notices.

Development scheduled to be initiated in fall of 2020.

ECS Platform Services A suite of services that are used by the other system components.

Initial version developed as part of the initial

Recordation release; will be adapted and expanded to support required

Registration, Public Record, and Licensing functionalities.

Although some work has been done in all of the major areas of this effort, we expect the majority of the

ECS work will continue over the next few years. The Registration components are the largest, most complex portion of this system, any only foundational work has been done up to this point.

We are treating the entirety of the ECS efforts as a continuous development project, and it will remain under active development as long as it supports the mission of the United States Copyright Office.

In addition, complementary business capabilities are planned for technology integration with the ECS.

Those capabilities include:

1. Data Analytics: The Qlik Sense solution is currently in the process of being implemented within the USCO.

2. Financial Management: the Library of Congress’s Legislative Branch Financial Management

System (LBFMS-Momentum).

3. Contact Center: The technology solution is under evaluation.

4. Warehouse Inventory Management: The technology solution is under evaluation.

Additional capabilities, Office functions, or datasets will also need to connect directly or be integrated with the ECS, such as the Public Information Office contact center.

Lifecycle Processes

The work done for ECS falls under the Libraries Software Development Lifecycle (SDLC), Project

Management Lifecycle (PMLC) and Agile at the Library guidance. All of these processes follow standard

Federal practices and include, but not limited to, Project Roadmaps, Risk Registers, Configuration management Plans, Backlog, User Stories, etc.

Our security practices are integrated into our SDLC and PMLC processes as well, so all code that is developed is scanned during project build time, and the completed system is scanned prior to production deployment.

Product quality is constantly monitored during the development process using SonarQube to determine code smells, accessibility issues as well as static code security analysis.

Product build and deployment should be integrated into a centralized CI/CD pipeline so that all ECS components can be built automatically, tested and then deployed. Each project will have dedicated Dev and Test environments, but the major components will get deployed into a shared Stage and Production

ECS environment for integration testing.

Attached are the Library’s PMLC, SDLC and Agile process documents that potential vendors would need to follow or justify deviation.

2.3 Fee Collection Information

The USCO will consider vendor proposals for alternative funding strategies, including recovery of industry investment in ECS development based on some portion of filing fees collected by the USCO.

The USCO’s current fee schedules can be found at the link below.

https://www.copyright.gov/about/fees.html

Data on registration, recordation, statutory licensing, and other fees collected from fiscal 2008 – fiscal

2018 can be found in the links below.

https://www.copyright.gov/about/fees.html https://www.copyright.gov/reports/annual/2018/ar2018.pdf#page=25 https://www.copyright.gov/reports/annual/2017/ar2017.pdf#page=19 https://www.copyright.gov/reports/annual/2016/ar2016.pdf#page=19 https://www.copyright.gov/reports/annual/2015/ar2015.pdf#page=18 https://www.copyright.gov/reports/annual/2014/ar2014.pdf#page=20 https://www.copyright.gov/reports/annual/2013/ar2013.pdf#page=21 https://www.copyright.gov/reports/annual/2012/ar2012.pdf#page=25 https://www.copyright.gov/reports/annual/2011/ar2011.pdf#page=50 https://www.copyright.gov/reports/annual/2010/ar2010.pdf#page=55 https://www.copyright.gov/reports/annual/2009/ar2009.pdf#page=76 https://www.copyright.gov/reports/annual/2008/ar2008.pdf#page=69

2.4 Security Requirements and Clauses

All ECS systems must adhere to FedRAMP controls for cloud-based SaaS or PaaS systems, internal

Library of Congress information technology (IT) security guidelines for an “authorization to operate”

(ATO), and applicable National Institute of Standards and Technology (NIST) controls incorporated into

Library of Congress IT policies and practices.

3.0 INSTRUCTIONS TO RESPONDENTS

At a minimum, interested respondents are requested to submit the information detailed below. All information submitted shall be UNCLASSIFIED. Responses shall be limited to 25 pages. Please use 10-point or larger font and respond with to this RFI with a capability statement in Microsoft Word compatible format. Proprietary information, if any, should be minimized and MUST BE CLEARLY

MARKED.

The deadline for submission of questions is 11:00 AM Pacific Time on 29 May 2020.

Firms are encouraged to ask questions (prior to responding to the RFI) if additional information or clarification is needed to provide a meaningful response to the Government’s requests. All questions are welcome, especially those that would help to improve the quality of responses and the accuracy of estimated costs and schedules. Questions shall NOT contain proprietary or classified information.

Written responses to this RFI shall be received no later than 11:00 AM Pacific Time on 16 June

2020.

Questions and Responses shall be submitted electronically via e-mail to the following individuals:

matthew.schupbach@gsa.gov (Mr. Matthew Schupbach, Contracting Officer) mark.schimmelbusch@gsa.gov (Mr. Mark Schimmelbusch, Program Manager) ozel.kirkland@gsa.gov (Mr. Ozel Kirkland, Program Manager)

Thank you in advance for any time and effort spent responding to this market research request.

Attachments:

1. PMLC_Directive

2. PMLC Overview_Additional Guidance

3. Draft Agile SDLC Guidance

4. Agile at the Library https://www.copyright.gov/reports/annual/2018/ar2018.pdf#page=25 https://www.copyright.gov/reports/annual/2017/ar2017.pdf#page=19 https://www.copyright.gov/reports/annual/2016/ar2016.pdf#page=19 https://www.copyright.gov/reports/annual/2015/ar2015.pdf#page=18 https://www.copyright.gov/reports/annual/2014/ar2014.pdf#page=20 https://www.copyright.gov/reports/annual/2013/ar2013.pdf#page=21 https://www.copyright.gov/reports/annual/2012/ar2012.pdf#page=25 https://www.copyright.gov/reports/annual/2011/ar2011.pdf#page=50 https://www.copyright.gov/reports/annual/2010/ar2010.pdf#page=55 https://www.copyright.gov/reports/annual/2009/ar2009.pdf#page=76 https://www.copyright.gov/reports/annual/2008/ar2008.pdf#page=69 mailto:matthew.schupbach@gsa.gov mailto:mark.schimmelbusch@gsa.gov mailto:ozel.kirkland@gsa.gov

3.1 Corporate Description. Please fill in the table below.

Name of Company

Name of Business Unit Responding to the

RFI

(if applicable)

DUNS Number

CAGE Code

Corporate Address

NAICS codes supported

Total Number of Full Time Employees

Is your company a small business or a large business under NAICS 541512 with a $30M small business size standard

If applicable, provide socio-economic category of Small Business (e.g.

Woman- Owned, Veteran Owned, Service Disabled Veteran Owned, 8(a), HUBZone etc.)

Would your company be interested in responding to the full scope of the requirement as prime contractor? If not, describe what portion your company is interested in performing.

Is your company a current awardee on a

GSA Federal Supply Schedule 70 or

GSA Alliant 2 contract vehicle? If so, please provide applicable contract numbers.

Single Point of Contact Name (Enter

Name, phone number and email address)

3.2 Corporate Capabilities and Responses. Reponses that address each of the items indicated below are appreciated and may be given the most consideration by the Government.

i. Describe any potential risks or foreseen challenges your company sees in taking over development of the ECS and provide information about your plan to mitigate and address such risks and challenges.

ii. Describe any potential risks or foreseen challenges your company sees in following the

Library’s PMLC, SDLC and Agile Development processes (attached). Provide information about where your company would suggest/request deviations from these processes to mitigate and address such risks and challenges.

iii. Describe your company’s technical capabilities and intended approach to complete development and implementation of the ECS.

iv. Provide the estimated length of time it would take to finalize development and implementation given your company’s intended approach.

v. Provide an estimate of the remaining total cost to develop and implement the ECS, based on your company’s intended approach. Also provide estimated yearly maintenance costs. The estimates shall include all costs, whether or not they are to be funded by the Government or industry. Please break out estimated costs per year of the effort to include pricing for labor and other direct costs. For labor estimate, please describe applicable labor categories and hours, and for software and ODCs please provide a description of each and any associated unit costs. Describe your company’s compensation and/or billing structure for your solution.

vi. Describe any alternative funding strategies that your company would be interested in proposing if this requirement were to be solicited. The Government is seeking creative funding solutions that may include, but are not limited to the following: no-cost contracts, cost-sharing contracts, licensing arrangements, and transaction based models where industry could recover investment based on some portion of filing fees collected by the USCO for a set period of time. Please fully describe the alternative cost sharing or funding arrangement, provide your understanding of how this strategy would work in a resulting Federal contract, and indicate what portion of the proposed estimate, from part iii above, could be funded by such a strategy. The Government is interested in any creative funding strategy, as long as it is viable and your company is actually willing to propose such a strategy.

vii. Provide any feedback regarding pricing options/ contract types that your firm would recommend for completion of development and implementation of the ECS.

viii. Outline any additional information your firm would need, if any, to formulate a technical

ECS strategy.

As stated above, firms are encouraged to ask questions (prior to responding to the RFI) if additional information or clarification is needed to provide a meaningful response to the Government’s requests. All questions are welcome, especially those that would help to improve the quality of responses and the accuracy of estimated costs and schedules.