2.0 PROPOSAL REQUIREMENTS

The USPTO anticipates entering into agreements for FY 2000 and beyond. The agreements will have a three-year duration with an option to renew for an additional 2 years.

Offerors interested in proposing several different solutions shall submit separate proposals for each and shall not combine them into one proposal. There are no restrictions on the number of proposals submitted by any Offeror for the RFA.

Proposals shall clearly state the implementation milestones and associated time frames for the proposed solution, for both the Offeror and the USPTO noting the goals in the current USPTO SITP. If the USPTO determines that the proposal cannot be accomplished in a reasonable time then the proposal will be rejected.

2.1 Project Plan

All proposals submitted in response to this RFA shall be submitted in the form of a project plan. The format for and content of the project plan is as follows:

The format for and content of the project plan is as follows:

2.1.1 Introduction

• Briefly describe your understanding of the objectives and scope of the proposed Agreement
• State the proposed duration of your proposal.
• Include Point of Contact (POC) information (name, address, phone number, e-mail address and fax number) for discussion and negotiation of your proposal. The point of contact shall have decision making (commitment) authority for the Offeror.

2.1.2 Description of Solution and Proposed Agreement

• Identify the mechanism, e.g., the software, service, etc. that you plan to use in order to reach that market segment or segments by describing the incentives, discounts, offers, benefits to the market segment or other specific approaches to increase electronic filing volumes.
• Identify the market segment you are trying to reach; describe your solution's impact on the segments (target population) and the electronic filing volume goals. Include the impact, if any, on complicated applications with and without complex work units (CWU) such as mathematical formulas, chemical formulas and the like. Alternative views of the market segments that better fits your conception of the market and/or your existing business are acceptable so long as they are clearly articulated.
• Describe the attention that will be given to this project, the resources that you will allocate, and your plan for managing and implementing the Agreement.
• Provide the business plan that supports the economic viability of the proposal
• Describe the duties and responsibilities of the USPTO in fulfilling the proposed Agreement.
• Describe the duties and responsibilities the Offeror will assume as an industry partner to the USPTO in fulfilling the proposed Agreement.
• Describe the USPTO resource requirements if required. Include the required: type of support, number of personnel, time frames for personnel, and supplies or equipment.
• Include Point of Contact (POC) information (if different from above) for management of the Agreement. Describe the POC's scope of authority and the resources available to the POC for ensuring the performance of the Agreement.
• Describe the milestones and time frames associated with implementation including all deliverables. Clearly delineate the milestones and timeframes associated with each participant, the Offeror and USPTO.
• Describe how the Offeror will track and report the number of unique applicants that use the Offeror's USPTO electronic filing XML product as a result of the marketing campaign.
• Return the Model Electronic Filing Memorandum of Agreement (Attachment 2 to this RFA) with any proposed additional content for negotiation, including dispute resolution and any remedies other than termination for the failure of either party to perform. Offerors are free to describe the respective duties and responsibilities either in the Agreement Requirements section of the project plan or in items 7 and 8 of the Model Electronic Filing Memorandum of Agreement.

2.1.3 Request for Patent Application Information (as applicable)

• Address the appropriate privacy and security safeguards as necessitated by the proposed Agreement.
• Describe the measures taken to guard against unauthorized disclosure in violation of the Patent Law 35 USC 122 when proposing solutions that require or contemplate release of information by the USPTO to other parties.

All of the elements and contents of the project plans may not be selected for inclusion in the resulting Non-Monetary Agreement. The project plan may include some information that the Offeror considers being proprietary and confidential and protected from Disclosure under the Freedom of Information Act (FOIA). Such information should be clearly marked.

2.2 Agreement Deliverables

On the last day of each quarter of the agreement following implementation, the Offeror shall submit a project performance report. This report shall contain narrative describing accomplishments and any difficulties in performance of the agreement, and measurement of the success of the Partner' s efforts including the number of unique customers that actually prepare and electronically file their application, correspondence or payment using the company's software or service. The final project performance report shall be submitted on September 1 of each calendar year during the term of the agreement to the USPTO Point of Contact. This report shall be used as a means to determine whether the Offeror has successfully performed the agreement. This report is subject to inspection/verification and approval by the USPTO and will be used to determine whether any option to extend the Agreement is exercised.