Original Notice.

     Expedited rule making-Proposed notice was filed as WSR 06-08-060.

     Title of Rule and Other Identifying Information: The Transportation Innovative Partnerships Act, proposed chapter 468-600 WAC et seq., are being proposed by the transportation commission in response to SHB 1541 enacted by the 2005 legislature. This law will provide a more desirable and effective approach to developing transportation projects in partnership with the private sector; greater flexibility in achieving the transportation project; allows for creative cost and risk sharing between the public and private partners. This law also states that the transportation commission shall be responsible for receiving, reviewing and approving proposals with the technical support of WSDOT.

     Hearing Location(s): Department of Transportation Headquarters Building, Large Commission Board Room, 310 Maple Park Avenue S.E., Olympia, WA 98504, on November 15, 2006, at 1:00 p.m.

     Date of Intended Adoption: November 15, 2006.

     Submit Written Comments to: Jeff Doyle, Director, Public-Private Partnerships, P.O. Box 47395, Olympia, WA 98504-7395, e-mail doylej@wsdot.wa.gov, by November 10, 2006.

     Assistance for Persons with Disabilities: Contact Wendy Harris by November 10, 2006, TTY (800) 833-6388 or (360) 705-7023.

     Purpose of the Proposal and Its Anticipated Effects, Including Any Changes in Existing Rules: The Transportation Innovative Partnership Act became law in June 2005. That law directs the Washington transportation commission to adopt administrative rules for the purpose of implementing and overseeing a public-private partnership program. The purpose of this program is to encourage and facilitate private sector participation in the design, development, construction, financing, operations and maintenance of transportation-related facilities and programs. The private sector is eligible to participate in any or all of these aspects of transportation project delivery. Final approval of any public-private partnership proposal rests with the transportation commission.

     Statutory Authority for Adoption: RCW 47.29.030 empowers the Washington state transportation commission to adopt rules.

     Statute Being Implemented: Chapter 47.29 RCW, Transportation Innovative Partnership Act of 2005.

     Rule is not necessitated by federal law, federal or state court decision.

     Agency Comments or Recommendations, if any, as to Statutory Language, Implementation, Enforcement, and Fiscal Matters: The Washington transportation commission and WSDOT both encourage any comments and suggested improvements to be communicated to Jeff Doyle, either by conversation or written submission. At this present time, no specific funding has been provided to carry out the requirements of chapter 47.29 RCW. The commission and WSDOT both anticipate submitting a request for funding this program to the governor and the legislature in time for the 2007 legislative session, which begins in January 2007. Absent specific funding, the commission and WSDOT must manage the program within their budgetary and resource constraints.

     Name of Proponent: Washington state department of transportation, governmental.

     Name of Agency Personnel Responsible for Drafting and Implementation: Jeff Doyle, 310 Maple Park Avenue S.E., P.O. Box 47316, Olympia, WA 98504, (360) 705-7023; Enforcement: Reema Griffith, P.O. Box 47308, Olympia, WA 98504-7308, (360) 705-7070.

     No small business economic impact statement has been prepared under chapter 19.85 RCW. These proposed rules govern a program that is 100% voluntary in participation by private industry. The rules relate to the process for reviewing, negotiating and approving public-private project agreements. The projects themselves may have impacts, which are subject to usual and customary analysis for impacts (such as environmental impact statements), but these administrative rules are not project-specific.

     A cost-benefit analysis is not required under RCW 34.05.328. The promulgation of these rules is required under chapter 47.29 RCW, there are no fees or cost impacts imposed as a result of these rules. Further rule making will be required to establish application fees for the evaluation of unsolicited proposals.

September 28, 2006

Reema Griffith

Executive Director

Transportation Commission

OTS-9092.1

     The legislature has articulated the policy goals and objectives of the act, found in chapter 47.29 RCW. These rules are intended to prescribe the processes that will be used to implement a successful transportation innovative partnership program in the state of Washington.

[]

     (1) "Commission" means the Washington state transportation commission;

     (2) "Competing proposal" means a written submission to the department that a proposer submits in response to a notice issued by the department under WAC 468-600-320;

     (3) "Department" means the Washington state department of transportation;

     (4) "Eligible project" as defined in RCW 47.29.050 includes:

     (a) Transportation projects, whether capital or operating, where the state's primary purpose for the project is to facilitate the safe transport of people or goods via any mode of travel. However, this does not include projects that are primarily for recreational purposes, such as parks, hiking trails, off-road vehicle trails, etc.; and

     (b) Facilities, structures, operations, properties, vehicles, vessels, or the like that are developed concurrently with an eligible transportation project and that are capable of providing revenues to support financing of an eligible transportation project, or that are public projects that advance public purposes unrelated to transportation;

     (5) "Eligible public works project" means only a project that meets the criteria of either RCW 47.29.060 (3) or (4);

     (6) "Governor" means the governor of the state of Washington;

     (7) "Key persons" means individuals or personnel employed by or affiliated with a proposer or team of proposers, and who, because of that person's responsibilities and participation in a proposed project, the department has formally designated as key to the proposer's ability to successfully develop or deliver the project;

     (8) "Major partner" means, with respect to a limited liability company or joint venture, each firm, business organization or person that has an ownership interest therein in excess of five percent, unless the department has provided an alternate definition that applies only to a specific project or series of projects;

     (9) "Major subcontractor" means any subcontractor designated in the proposal to perform ten percent or more of the scope of work for a proposed project, unless the department has provided an alternate definition that applies only to a specific project or series of projects;

     (10) "Private sector partner" and "private partner" means a person, entity or organization that is not the federal government, a state, or a political subdivision of the state and that proposes to enter into an agreement with the state to participate in any or all portions of the design, development, construction, improvement, expansion, extension, delivery, operation, maintenance or financing of a project eligible under the act;

     (11) "Proposal" means a written submission to the department satisfying the requirements of WAC 468-600-105, 468-600-240 or 468-600-250;

     (12) "Proposer" means a person, business entity, a consortium of business entities or a public sector entity that submit a proposal for review and evaluation under these rules, whether the proposal was solicited or unsolicited by the department;

     (13) "Public facility" means a building, structure, vehicle, vessel or the like where ownership is retained by the public sector and where the facility is available for use by the general public. This does not include any facilities that are owned by the private sector;

     (14) "Public funds" means all moneys derived from a public imposition of taxes, fees, charges and tolls, including those imposed by a private entity for the privilege to use a publicly owned facility;

     (15) "Public-private partnership" and "PPP" mean a nontraditional arrangement between the department and one or more public or private entities for the implementation of an eligible project as defined in subsection (12) of this section;

     (16) "Public project" means a project that is owned by the state or any of its political subdivisions;

     (17) "Secretary" means the secretary of the Washington state department of transportation;

     (18) "State" means the government of the state of Washington, including all agencies, organizations, boards, commissions, elected or appointed officials, who are empowered to act on behalf of the state of Washington;

     (19) "Transportation Innovative Partnership Act" and "act" means the law enacted and codified in chapter 47.29 RCW, and any amendments thereto;

     (20) "Transportation innovative partnership program" and "TIPP" means that portion of the department of transportation responsible for implementing and carrying out the duties prescribed in chapter 47.29 RCW, these rules, and under the powers conferred upon the department to implement the executive branch functions of state government;

     (21) "WSDOT" means the Washington state department of transportation.

[]

     (2) After review and approval by the commission, the department shall publish and make available conflict of interest guidelines and policies that encompass the standards of conduct required by federal and state law, and as further required in these administrative rules. The conflict of interest guidelines and policies may be modified as necessary to meet the particular objectives of individual projects, whether those projects emanate from solicited or unsolicited proposals.

[]

     (2) For those activities not prohibited by subsection (1) of this section, but which attempt to influence decision making in any legislative branch, proposers must fully disclose all lobbying activities undertaken by any of its contractors, officers, employees or agents that are subject to public disclosure under chapter 42.17 RCW or federal law. For lobbying activities subject to chapter 42.17 RCW, copies of all required disclosure forms for the previous two years' reporting cycles must be submitted.

[]

     (2) During the pendency of any solicitation, negotiation or selection of a proposal, no member of the commission may engage in ex parte communications with proponents or opponents with respect to the proposal, unless that person:

     (a) Places on the record the substance of any written or oral ex parte communications concerning the decision of action; and

     (b) Provides that a public announcement of the content of the communication and of the parties' rights to rebut the substance of the communication shall be made at each meeting where action is considered or taken on the subject to which the communication related. This prohibition does not preclude a member of the commission from seeking in a public meeting specific information or data from such parties relative to the decision if both the request and the results are a part of the public record.

[]

     By submitting such a proposal, a proposer thereby waives and relinquishes any right, claim, copyright, proprietary interest or other right in any proposed location, site, route, corridor, rights of way, alignment, or transportation mode or configuration identified in the proposal as being involved in or related to the proposed project, and proposer agrees to indemnify and hold the state harmless against any such claim made by any of its contractors, subcontractors, agents, employees and assigns.

     The waiver and release of rights in this section do not apply to a proposer's rights in any documents, designs and other information and records that constitute "sensitive business, commercial or financial information" as that term is defined and used in WAC 468-600-605.

[]

     (2) The department shall periodically update the information in the registry, and shall review and consider additions or deletions to the registry at least every two years. When considering additional projects for the registry, or removal of the projects on the registry, the department must publish a request for information that seeks comments and suggestions from the public and private sectors.

     (3) At least once every two years, the department must develop a plan for conducting a solicitation of proposals under the TIP program. The purpose of this plan is to:

     (a) Encourage sound programming and budgeting practices, which are the basis for submittals required under chapter 43.88 RCW;

     (b) Ensure that the department does not issue a request for proposals that exceeds the resources available to properly evaluate, select and enter into development agreements;

     (c) Ensure that development of projects under the TIP program would not run contrary to any legislatively enacted direction or express executive policies or directions; and

     (d) Provide potential proposers an anticipated schedule for the solicitation and development of certain projects on the registry.

     In selecting projects for competitive solicitation, the department should endeavor to follow the published plan for soliciting proposals for projects on the registry. However, the department is not required to solicit only those projects contained on the registry, nor is it required to conduct a solicitation for a predetermined number of projects each year or biennium, nor is it required to undertake projects in the exact order of consideration as published in the Register.

[]

[]

     (1) Issuing a request for qualifications, where proposers are ranked and selected based on the qualifications of the major partners, major subcontractors and key persons, which would result in a predevelopment agreement being entered into that authorizes the proposer to fully develop a detailed proposal that would be evaluated pursuant to WAC 468-600-350;

     (2) Issuing a request for proposals that invites the private sector to make proposals to develop eligible projects that are contained in the department's registry of projects under WAC 468-600-100.

     These examples are offered for illustrative purposes only, and should not be construed to limit the scope of the state's discretion or authority to develop proposal and evaluation criteria and processes for any project as long as those criteria and processes comply with the requirements of RCW 47.29.010 et seq.

[]

     (1) General information.

     (a) Notice of any preproposal conference as follows:

     (i) The time, date and location of any preproposal conference;

     (ii) Whether attendance at the conference will be mandatory or voluntary; and

     (iii) A disclaimer that statements made by the department's representatives at the conference are not binding upon the state unless confirmed by written addendum.

     (b) The name and title of the person authorized and designated by the department to receive the proposals and contact person (if different).

     (c) Instructions and information concerning submission requirements including the address of the office to which proposals must be delivered and any other special information, e.g., whether proposals may be submitted by facsimile or electronic data interchange (secured e-mail).

     (d) The time and date of closing after which the department will not accept proposals.

     (e) The form and submission of proposals and any information required therein.

     (f) If the agreement resulting from a solicitation will be a contract for a public work subject to chapter 39.12 RCW or the Davis-Bacon Act (40 U.S.C. section 3141 to 3148), a statement that no proposals will be considered by the state unless the proposal contains a statement by the proposer, as part of its proposal, that proposer agrees to be bound by and will comply with the provisions of chapter 39.12 RCW and 40 U.S.C. section 3141 to 3148.

     (g) Contractor's certification of nondiscrimination in obtaining required subcontractors in accordance with state law.

     (h) How the state will notify proposers of addenda and how the state will make addenda available.

     (2) Project description. A description of the eligible project for which the department is requesting proposals for a public-private partnership in such detail as the department considers appropriate or feasible under the circumstance.

     (3) Evaluation process. A description of the process by which the proposals will be evaluated, including:

     (a) A statement that the commission and/or department may reject any proposal not in compliance with all prescribed procedures and requirements and other applicable laws, and that the state reserves its rights under WAC 468-600-810 through 468-600-820;

     (b) The anticipated solicitation schedule, deadlines, protest process, and evaluation process, if any; and

     (c) Evaluation criteria that the state will use to select a proposal(s) from among those submitted in response to the request for proposals.

     (4) Desired contract terms. The department shall provide an outline or draft term sheet of those contract terms and conditions, including warranties and bonding requirements, that the department considers necessary.

     (5) Federal funds. If federal funds are involved, the federal laws, rules and regulations applicable to the fund requirements shall govern in the event they conflict with a provision required by state law.

[]

     (a) Mail notice of the availability of solicitation documents ("notice") to entities that have expressed an interest in department procurements;

     (b) Place notice on the state of Washington's electronic procurement system; or

     (c) Place notice on the department's and the commission's internet web site.

     (2) Method of publication. The department shall furnish notice for every solicitation for proposals by any method that meets the requirements of RCW. . . . . , including:

     (a) Mail notice of the availability of solicitation documents ("notice") to entities that have expressed an interest in department procurements;

     (b) Place notice on the state of Washington's electronic procurement system;

     (c) Place notice on the department and commission's internet web site;

     (d) Advertising - the department shall publish the advertisement for proposals at least once in at least one newspaper of general circulation in the area where the contract is to be performed, in at least one trade newspaper or publication of general statewide circulation and in as many additional issues and publications as the department may determine to be necessary or desirable to foster and promote competition.

     (3) Publication contents. All advertisements for proposals shall set forth:

     (a) The scheduled closing, that shall not be less than five days after the date of the last publication of the advertisement;

     (b) The date that entities must file applications for prequalification if prequalification is a requirement and the class or classes of work for which entities must be prequalified;

     (c) The nature of the work to be performed or the goods to be purchased;

     (d) The office where any documents related to the solicitation may be reviewed;

     (e) The name, title and address of the department employee authorized to receive proposals; and

     (f) If applicable, that the contract is for a public work subject to chapter 39.12 RCW or the Davis-Bacon Act (40 U.S.C. sections 3141 to 3148).

     (4) Posting advertisement for proposals. The department shall post a copy of each advertisement for proposals at the principal business office of the department. A proposer may obtain a copy of the advertisement for proposals upon request from the transportation innovative partnership program office, or on the internet at www.wsdot.wa.gov.

     (5) Notice to state office of minority and women's business enterprises (OMWBE). The department shall provide timely notice of all solicitations to the state office of minority and women's business enterprises.

[]

[]

     (1) The project must meet the definition of an "eligible project" under WAC 468-600-015(4);

     (2) The project must not be listed in the registry of projects intended for a competitive solicitation, under WAC 468-600-100;

     (3) The project must be included in the Washington transportation plan or otherwise identified by the commission as being a priority need of the state.

[]

     (2) Commencing on the effective date of the order giving priority, the department may undertake expedited processing and consideration of unsolicited proposals (or a particular unsolicited proposal) for transportation projects of the class, category or description contained in the order. The limited resources of the department, in such cases, will require either the postponement of, or delay in, the processing and consideration of unsolicited proposals for projects that are not within a class, category or description that is subject to a priority order.

     (3) By submitting an unsolicited proposal, each proposer thereby waives and relinquishes every claim of right, entitlement or expectation that:

     (a) Its proposal will enjoy the benefit of a priority order; and

     (b) The processing and consideration of its proposal will not be subject to postponement or delay arising out of the department's issuance of an order that gives priority to another proposal or to proposals for different classes, categories or descriptions of projects.

     (4) The department may, by written order, suspend the acceptance and consideration of proposals based on the types, classes, cost ranges, geographic areas of projects, or other factors as determined by the department. The order will specify either the term of the suspension or that the suspension will continue until recalled by a subsequent order of the department.

     (5) Commencing on the effective date of the suspension order, the department will refuse to accept unsolicited proposals or unsolicited proposals for projects of the class, category or description contained in the order, and may, as stated in the order, cease further processing and consideration of any such unsolicited proposals then currently under consideration by the department.

     (6) By submitting an unsolicited proposal, each proposer thereby waives and relinquishes every claim of right, entitlement or expectation that the processing and consideration of its proposal will not be subject to suspension under this rule.

     (7) The state of Washington, the department of transportation, the Washington transportation commission, and their officers and employees, shall have no responsibility or liability of any nature for the preservation, confidentiality or safekeeping of any proposal that is subject to a suspension order under this rule and is submitted to the department while that suspension order is in effect.

[]

     (2) A proposal review fee in the amount prescribed by WAC 468-600-230 must accompany any unsolicited conceptual proposal submitted by a private entity or unit of government.

     (3) The proposer shall submit twenty copies, individually identified, of any unsolicited conceptual proposal in addition to the proposal bearing the signature of the authorized representative. The original proposal, required copies and processing fee shall be delivered to the department.

     (4) The department will consider an unsolicited conceptual proposal only if:

     (a) The proposed project is unique or innovative in comparison with, and is not substantially duplicative of, other transportation system projects included in the state transportation improvement program within the department or, if it is similar to a project in the state transportation improvement program, the proposed project has not been fully funded by the state or any other public entity as of the date the proposal is submitted, or the proposal offers an opportunity to materially advance or accelerate the implementation of the project. Unique or innovative features that may be considered by the department in evaluating such a proposal may include but are not limited to unique or innovative financing, construction, design, schedule or other project components as compared with other projects or as otherwise defined by state rules or regulations; and

     (b) The conceptual phase includes all information required by and is presented in the format set out in WAC 468-600-540. Such information shall include a list of any proprietary information included in the proposal that the proposer considers protected trade secrets or other information exempted from disclosure under either WAC 468-600-605 or RCW 47.29.190.

     (5) The department will not consider an unsolicited proposal for a project involving another state or local government unit of another state unless the department and the appropriate representative of the other state or of the local government unit of the other state have entered into an agreement that permits the acceptance of unsolicited proposals for such a project.

[]

[]

     (1) Selecting a proposal for development into a final agreement based on a unitary proposal instead of a two-step conceptual/detailed proposal process; and

     (2) Proposers are ranked and selected based on the qualifications of the major partners, major subcontractors and key persons, which would result in a predevelopment agreement being entered into that authorizes the proposer to fully develop a detailed proposal that would be evaluated pursuant to WAC 468-600-350.

     (3) Nothing in this section, nor in these WAC rules, shall be construed to allow proposer conduct or participation in a project that would be prohibited under the Federal Highway Administration's Conflict of Interest Guidelines.

     These examples are offered for illustrative purposes only, and should not be construed to limit the scope of the state's discretion or authority to develop proposal and evaluation criteria and processes for any project as long as those criteria and processes comply with the requirements of RCW 47.29.010 et seq.

[]

     (1) TAB 1: Qualifications and experience.

     (a) Identify the legal structure of the private entity or consortium of private entities or of private and public entities (the "team") submitting the proposal. Identify the organizational structure of the team for the project, the team's management approach and how each major partner and major subcontractor identified as being a part of the team as of the date of submission of the proposal fits into the overall team.

     (b) Describe the experience of each private entity involved in the proposed project. Describe the length of time in business, business experience, public sector transportation experience, PPP experience, development experience, design-build experience and other similarly sized engagements of each major partner and major subcontractor. The lead entity must be identified.

     (c) Provide the names, addresses and telephone numbers of persons within the team who may be contacted for further information.

     (d) Include the address, telephone number, and the name of a specific contact person at a public entity for which the private entity or the team or the primary members of the team have completed a development project, public-private partnership project or design-build project.

     (e) Include the resumes for those managerial persons within the team that will likely be associated in a significant way with the project development and implementation.

     (f) Provide financial information regarding the private entity or team and each major partner that includes, if available, the most recent independently audited financial statement of the private entity or team and of each major partner, and which demonstrates their ability to perform the work and project as set forth in the proposal, including ability to obtain appropriate payment and performance bonds.

     (g) Submit executed disclosure forms, prescribed by the department, for the team, each major partner and any major subcontractor.

     (2) TAB 2: Project characteristics.

     (a) Provide a topographical map (1:2,000 or other appropriate scale) depicting the location of the proposed project.

     (b) Provide a description of the eligible project or projects, including all proposed interconnections with other existing transportation facilities or known publicly identified projects.

     (c) Describe the project in sufficient detail so the type and intent of the project, the general location of the project, and the communities that may be affected by the project are clearly identified. Describe the assumptions used in developing the project.

     (d) List the critical factors for the project's success.

     (e) If the proposed project does not conform with the state and regional transportation plans or regional plans, outline the proposer's approach for securing the project's conformity with, or indicate the steps required for, acceptance into such plans.

     (f) When a proposed project is sited, in whole or in part, within the jurisdiction of a metropolitan planning organization or area commission on transportation, identify applicable regional and local approvals required for the project.

     (g) Provide an explanation of how the proposed transportation project would impact local transportation plans of each affected locality.

     (h) Provide a list of public transportation facilities and major apparent public utility facilities that will be crossed or affected by the transportation project and a statement of the proposer's plans to accommodate such facilities.

     (i) Describe the role the proposer anticipates the department will have in the development, construction, operation, maintenance, financing, or any other aspect of the eligible project.

     (3) TAB 3: Project financing.

     (a) Provide a projected budget for the project or scope of work based on proposer's prior experience on other scopes of work and projects or other cost projection factors and information.

     (b) Include a list and discussion of assumptions (e.g., user fees, toll rates and usage of the facility) underlying all major elements of the plan for the project.

     (c) Identify the proposed risk factors relating to the proposed project financing and methods for dealing with these factors.

     (d) Identify any significant local, state or federal resources that the proposer contemplates requesting for the project. Describe the total commitment (financial, services, property, etc.), if any, expected from governmental sources; the timing of any anticipated commitment; and its impact on project delivery.

     (e) Identify any aspect of the financial model for the project that implicates or potentially implicates restrictions on the use of highway-related revenues under Article II, section 40 of the Washington Constitution (commonly known as the Motor Vehicle Trust Fund), and explain how the financial model avoids conflicting with those restrictions.

     (f) Provide a conceptual estimate of the total cost of the transportation project.

     (4) TAB 4: Public support/project benefit/compatibility.

     (a) Identify who will benefit from the project, how they will benefit and how the project will benefit the overall transportation system.

     (b) Identify any anticipated government support or opposition, or general public support or opposition, for the project.

     (c) Explain the strategy and plans that will be carried out to involve and inform the agencies and the public in areas affected by the project.

     (d) Describe the significant social and economic benefits of the project to the community, region or state and identify who will benefit from the project and how they will benefit. Identify any state benefits resulting from the project including the achievement of state transportation policies or other state goals.

     (5) All pages of a conceptual proposal shall be numbered. Each copy of the proposal will be bound or otherwise contained in a single volume where practicable. All documentation submitted with the proposal will be contained in that single volume.

     (6) A conceptual proposal submitted by a private sector partner must be signed by an authorized representative of the private sector partner submitting the unsolicited conceptual proposal.

     (7) The proposer shall include a list of any proprietary information included in the proposal which the proposer considers protected trade secrets or other information exempted from disclosure under WAC 468-600-605.

[]

     (1) TAB 2: Project characteristics.

     (a) Provide a detailed description of the eligible project or projects, including all proposed interconnections with other existing transportation facilities or known publicly identified projects. Describe the project in sufficient detail so the type and intent of the project, the general location of the project, and the communities that may be affected by the project are clearly identified. Describe the assumptions used in developing the project.

     (b) Identify any significant local, state or federal services or practical assistance that the proposer contemplates requesting for the project. In particular, identify and describe any significant services that will need to be performed by the department such as right of way acquisition or operation and maintenance of the completed project.

     (c) Include a preliminary list of all significant federal, state, regional and local permits and approvals required for the project. Identify which, if any, permits or approvals are planned to be obtained by the department.

     (d) List the critical factors for the project's success.

     (e) Identify the proposed preliminary schedule for implementation of the project.

     (f) Describe the assumptions related to ownership, law enforcement and operation of the project and any facility that is part of the project.

     (g) Describe the payment and performance bonds, guarantees, letters of credit and other performance security, if any, that the proposer will provide for the project.

     (h) Identify any public improvements that will be part of the proposed project that will constitute "public works" under RCW 47.29.020(5), the workers on which must be paid in accordance with Washington's prevailing rate of wage law, chapter 39.12 RCW, and any public improvements the workers on which must be paid in accordance with the federal Davis-Bacon Act, 40 U.S.C. sections 3141 to 3148.

     (2) TAB 3: Project financing.

     (a) Identify the form and amount of any private capital contribution and the entities that will make such capital contributions. If other forms of contribution are proposed, describe the nature of the contributions, the fair market value (if applicable), and whether compensation for such contributions will be sought.

     (b) If the proposal would provide for a state-granted franchise to a private concessionaire in exchange for financial consideration, provide the proposer's financial model and all capital costs, operating and maintenance costs (including reconstruction, resurfacing, restoration, and rehabilitation costs), revenues and other data and assumptions that comprise the base case financial model.

     (c) Provide an explanation of how funds for the project will be segregated, accounted for and expended in a manner that ensures that any moneys protected under Article II, section 40 of the Washington Constitution be expended exclusively for the purposes authorized under that provision.

     (d) Identify, to the extent possible, proposed financing team members, including banks, investment banks, equity investors, credit enhancement providers, bond trustees and legal counsel to the same.

     (3) TAB 5: Special deliverables.

     (a) Provide a statement setting out the plan for securing all necessary real property, including proposed timeline for any necessary acquisitions.

     (b) Provide proposed design, construction and completion guarantees and warranties.

     (c) Include traffic studies and/or forecasts and related materials that establish project revenue assumptions, including, if any, user fees or toll rates, and usage of the facility.

     (d) Provide such additional material and information as the department may reasonably request.

     (4) All pages of a proposal shall be numbered. Each copy of the proposal shall be bound or otherwise contained in a single volume where practicable. All documentation submitted with the proposal will be contained in that single volume.

     (5) A proposal submitted by a private sector partner must be signed by an authorized representative of the private sector partner submitting the proposal.

     (6) The proposer shall clearly mark any proprietary information included in the proposal which the proposer considers protected trade secrets or other information exempted from disclosure under RCW 47.29.190 and WAC 468-600-605. Any individual page containing material that the proposer considers proprietary must be stamped "proprietary."

[]

     (2) All proposers must provide all the information required by this rule and by the department. All proposers and key persons must complete and submit the required disclosure form within the deadlines set by the department. All proposers and key persons must provide any documents required in the disclosure process, or other documents as determined by the department, or their proposals may be rejected by the department.

     (3) The department may reject, or require the supplementation of, a proposal if the proposer has not provided all information required in the disclosure form or if any information provided is not accurate, current or truthful. The failure or refusal of any proposer to properly execute, fully complete, or accurately report any information required by the required disclosure shall be sufficient grounds for rejection of the proposal.

     (4) Any change in the status of the proposer, in the identity of any of the key persons, or the addition of any key persons must be reported to the department within thirty days of the known change, and those whose status has changed or who have been added as key persons will be required to submit the required disclosure information. For purposes of this section, a "change in the status of a proposer" means a reorganization of the business structure or corporate structure of the proposer or a major partner, or a change in ownership of the proposer or a major partner amounting to a transfer of over twenty percent of the entity's ownership.

     (5) The burden of satisfying the department's disclosure requirements, both in terms of producing the disclosures and assuring their accuracy and completeness, resides with each proposer.

     (6) Each proposer, by submitting a proposal, thereby accepts all risk of adverse public notice, damages, financial loss, criticism, harm to reputation or embarrassment that may result from any disclosure or publication of any material or information required or requested by the state in connection with the proposer's submission of a proposal. In submitting a proposal, the proposer expressly waives, on behalf of itself, its partners, joint venturers, officers, employees and agents, any claim against the secretary, the state of Washington, the commission, the department and their officers and employees, for any damages that may arise therefrom.

     (7) A public entity that submits a proposal may, prior to submission, request the department to waive the disclosure requirements of this rule with respect to the corporate public entity and its officers. However, if the public entity proposes to enter into or establish a partnership or joint venture with a private sector partner to perform any substantial portion of the proposed project (as opposed to the engagement of only a prime contractor or subcontractors), then disclosure of the private party must be made as if the private party is a proposer, in accordance with this rule.

[]

     (1) Department staff;

     (2) An independent representative of a consulting or contracting firm with no interests in the project, whose firm would be precluded from participating in any part of the project;

     (3) An observer from the state auditor's office or the joint legislative audit and review committee;

     (4) A person appointed by the commission; and

     (5) A financial expert.

[]

     (a) The proposal is complete;

     (b) The proposal is responsive; and

     (c) The proposal meets any additional procedural or process requirements prescribed by the state.

     Solicited proposals certified by the department under this subsection will be forwarded to the evaluation panel under WAC 468-600-305.

     (2) Unsolicited conceptual proposals submitted under WAC 468-600-220 will be reviewed by the evaluation panel, as created and assembled under WAC 468-600-305. The evaluation panel will initially determine whether the conceptual proposal is eligible for evaluation pursuant to WAC 468-600-200 (state's authority to accept unsolicited proposals -- Moratorium); WAC 468-600-210 (Projects eligible for unsolicited proposals) and WAC 468-600-215 (management of unsolicited proposals). If not, the evaluation panel will not proceed further with its evaluation and the department may return the proposal to the proposer. If the conceptual proposal is eligible for evaluation, the evaluation panel will assess:

     (a) Whether the proposal is complete;

     (b) Whether the proposer appears qualified;

     (c) Whether the proposal appears to satisfy the requirements of WAC 468-600-240;

     (d) Whether the project as proposed appears to be technically and financially feasible;

     (e) Whether the project as proposed appears to have the potential of enhancing the state transportation system; and

     (f) Whether the project as proposed appears to be in the public interest.

     (3) The evaluation panel will report the results of its evaluation and its recommendation to the commission. The recommendation will not include sensitive business, commercial or financial information or trade secrets as described in WAC 468-600-605.

[]

[]

     (a) Be published in a newspaper of general circulation and upon such electronic web site providing for general public access as the department may develop for such purpose;

     (b) Be provided to any county, city, metropolitan service district, or transportation district in which the project will be located;

     (c) Be provided to any person or entity that expresses in writing to the department an interest in the subject matter of the unsolicited conceptual proposal and to any member of the legislature whose house or senate district would be affected by such proposal;

     (d) Outline the general nature and scope of the unsolicited conceptual proposal, including the location of the transportation project and the work to be performed on the project; and

     (e) Specify the address to which any competing conceptual proposal must be submitted.

     (2) The department may also elect to deliver such notice directly to any person or entity the department believes may have an interest in submitting a competing conceptual proposal.

     (3) Any entity that elects to submit a competing conceptual proposal for the proposed project shall submit a written letter of intent to do so not later than thirty calendar days after the department's initial publication of notice. Any letter of intent received by the department after the expiration of the thirty-day period shall not be valid and any competing conceptual proposal submitted thereafter by a private or governmental entity that has not submitted a timely letter of intent shall not be considered by the department.

     (4) An entity that has submitted a timely letter of intent must submit its competing conceptual proposal to the department not later than one hundred twenty calendar days after the department's initial publication of notice under subsection (1) of this section, or such other time as the department provides in the notice. The competing conceptual proposal must:

     (a) Be signed by an authorized representative of the proposer;

     (b) Be accompanied by the processing fee for conceptual proposals required under WAC 468-600-230; and

     (c) Include the information and be organized in the manner required of an unsolicited conceptual proposal under WAC 468-600-240.

     (5) Any competing conceptual proposal that is received within the time provided in subsection (4) of this section must be forwarded to the evaluation panel as provided in WAC 468-600-310. The panel must:

     (a) Evaluate the competing conceptual proposal under the criteria specified in WAC 468-600-310; and

     (b) Determine whether the competing proposal(s) differ from the original unsolicited conceptual proposal in such a significant and meaningful manner that they should be treated as an original unsolicited conceptual proposal. If the evaluation panel believes that a proposal submitted as a competing proposal should be treated as an original unsolicited conceptual proposal and that it satisfies the requirements of WAC 468-600-240, the evaluation panel shall forward the proposal to the commission for preliminary review and approval under WAC 468-600-315, and the proposal shall thereafter be processed under these rules in the same manner as an unsolicited conceptual proposal. If the competing conceptual proposal is not to be treated as an original unsolicited conceptual proposal, the competing conceptual proposal will be reviewed by the evaluation panel as provided in WAC 468-600-330 through 468-600-350.

[]

     For unsolicited and competing proposals, the evaluation panel must consider the following factors:

     (1) Qualifications and experience. Has the proposer created a team that is qualified, managed, and structured in a manner that will enable the team to complete the proposed project and perform the proposed scope of work?

     (a) Experience with similar infrastructure projects. Have members of this team previously worked together or in a substantially similar consortium or partnership arrangement constructing, improving operating, maintaining or managing transportation infrastructure? Has the lead firm managed, or any of the member firms worked on, a similar public-private partnership project?

     (b) Demonstration of ability to perform work. Does the team possess the necessary financial, staffing, equipment, and technical resources to successfully complete the project and perform the proposed scope of work? Do the team and/or member firms have competing financial or workforce commitments that may inhibit success and follow-through on this project?

     (c) Leadership structure. Is one firm designated as lead on the project? Does the organization of the team indicate a well thought out approach to managing the project? Is there an agreement/document in place between members?

     (d) Project manager's experience. Is a project manager identified, and does this person work for the principal firm? If not, is there a clear definition of the role and responsibility of the project manager relative to the member firms? Does the project manager have experience leading this type and magnitude of project?

     (e) Management approach. Have the primary functions and responsibilities of the management team been identified? Have the members of the team developed an approach to facilitate communication among the project participants? Has the firm adequately described its approach to communicating with and meeting the expectations of the state?

     (f) Financial condition. Is the financial information submitted on the forms sufficient to determine the firms' capability to fulfill its obligations described in the project proposal, and is that capability demonstrated by the submitted information?

     (g) Project ownership. Does the proposal identify the proposed ownership arrangements for each phase of the project and clearly state assumptions on legal liabilities and responsibilities during each phase of the project?

     (h) Competitive subcontracting. To what extent have adequate procurement policies been adopted by the proposer to ensure opportunities for competitive procurement of work, services, materials and supplies that the proposer will subcontract?

     (2) Project characteristics. Is the proposed project technically feasible?

     (a) Project definition. Is the project described in sufficient detail to determine the type and size of the project, the location, all proposed interconnections with other transportation facilities, the communities that may be affected, and alternatives (e.g., alignments) that may need to be evaluated?

     (b) Proposed project schedule. Is the time frame for project completion clearly outlined? Is the proposed schedule reasonable given the scope and complexity of the project?

     (c) Quality management. Does the proposer present a quality management plan, including quality control and quality assurance processes, that are good industry practice and are likely to result in delivery of a project and services that meet the department's standards and comply with contract requirements?

     (d) Operation. Does the proposer present a reasonable statement setting forth plans for operation of the project or facilities that are included in the project?

     (e) Technology. Is the proposal based on proven technology? What is the degree of technical innovation associated with the proposal? Will the knowledge or technology gained from the project benefit other areas of the state or nation? Does the technology proposed maximize interoperability with relevant local and statewide transportation technology? Can the proposed project upgrade relevant local technology?

     (f) Conforms to laws, regulations, and standards. Is the proposed project consistent with applicable state and federal statutes and regulations, or reasonably anticipated modifications of state or federal statutes, regulations or standards? Does the proposed design meet applicable state and federal standards?

     (g) Federal permits. Is the project outside the purview of federal oversight, or will it require some level of federal involvement due to its location on the National Highway System or Federal Interstate System or because federal permits are required? Does the proposal identify the primary federal permits and agencies that will be involved in review and oversight of the project?

     (h) Meets/exceeds environmental standards. Is the proposed project consistent with applicable state and federal environmental statutes and regulations? Does the proposed design meet applicable state environmental standards? Does the proposal adequately address air quality issues?

     (i) State and local permits. Does the proposal list the required permits and provide a schedule for obtaining them? Are there known or foreseeable negative impacts arising from the project? If so, does the proposal outline a plan to address those negative impacts? Are alternatives to standards or regulations needed to avoid those impacts that cannot be addressed?

     (j) Right of way. Does the proposal set forth a method or plan to secure all property interests required for the transportation project?

     (k) Maintenance. Does the proposer have a plan to maintain any facilities that are part of the proposed transportation project in conformance with department standards? Does the proposal clearly define assumptions or responsibilities during the operational phase including law enforcement, toll collection and maintenance? Under the proposal, will maintenance and operation of any new facilities be consistent with standards applied throughout the highway system and use the same work forces and methods?

     (3) Project financing. Has the proposer provided a financial plan that allows access to the necessary capital to make a substantial contribution of nonstate, private sector, or other innovative financing resources to the financing of the facility or project?

     (a) Financing. Did the proposer demonstrate evidence of its experience, ability and commitment to provide a sufficient private-sector contribution or other innovative financing contribution of funds or resources to the project as well as the ability to obtain the other necessary financing?

     (b) Conformance with RCW 47.29.060. Does the proposed financing plan conform to any requirements of state-issued debt under RCW 47.29.060? If the proposed financing plan is not in conformance, has the proposer committed to seeking any necessary legislative or other state approvals in order to proceed with the financing plan as proposed?

     (c) Financial plan. Does the financial plan demonstrate a reasonable basis for funding project development and operations? Are the assumptions on which the plan is based well defined and reasonable in nature? Are the plan's risk factors identified and dealt with sufficiently? Are the planned sources of funding and financing realistic? Is the proposer willing to place private capital at risk in order to successfully deliver the project? Does the proposer adequately identify sources of nonstate funding that it anticipates including in the project financing, and does the proposer provide adequate assurance of the availability of those funds and the reliability of the funding sources?

     (d) Estimated cost. Is the estimated cost of the project reasonable in relation to the cost of similar projects?

     (e) Life-cycle cost analysis. Does the proposal include an appropriately conducted life-cycle cost estimate of the proposed project and/or facility? How does the life-cycle cost impact the projected rate of return?

     (f) Financial model. If the procurement is for a concession agreement, does the proposal present a sound base case financial model? Are the assumptions in the financial model reasonable and realistic?

     (g) Business objective. Does the proposer clearly articulate its reasons for pursuing this project? Do its assumptions appear reasonable?

     (4) Public support. Has the proposer demonstrated sufficient public support for the proposed project or proposed a reasonable plan for garnering that support?

     (a) Community benefits. Will this project bring a significant transportation and economic benefit to the community, the region, and/or the state? Are there ancillary benefits to the communities because of the project?

     (b) Community support. What is the extent of known support or opposition for the project? Does the project proposal demonstrate an understanding of the national and regional transportation issues and needs, as well as the impacts this project may have on those needs? Is there a demonstrated ability to work with the community? Have affected local jurisdictions expressed support for the project?

     (c) Public involvement strategy. What strategies are proposed to involve local and state elected officials in developing this project? What level of community involvement is contemplated for the project? Has the proposer articulated a clear strategy for informing and educating the public and for obtaining community input throughout the development and life of the project?

     (5) Project compatibility. Is the proposed project compatible with, or can it be made compatible with state and local comprehensive transportation plans?

     (a) Compatibility with the existing transportation system. Does this project propose improvements that are compatible with, or that can be made compatible with, the present and planned transportation system? Does the project provide continuity with existing and planned state and local facilities?

     (b) Fulfills policies and goals. Does the proposed project help achieve performance, safety, mobility or transportation demand management goals? Does the project improve connections among the transportation modes?

     (c) Conformity with local, regional and state transportation plans. Does the project conform with, or can it achieve conformity with, city and county comprehensive plans and regional transportation plans? Does the project conform with, or can it achieve conformity with, plans developed by the commission and any applicable regional transportation plans or local transportation programs? If not, are the steps proposed in the proposal to achieve conformity with such plans adequate and appropriate to provide a high likelihood that the project and the applicable plans can be brought into conformity?

     (d) Economic development. Will the proposed project enhance the state's economic development efforts? Is the project critical to attracting or maintaining competitive industries and businesses to the region, consistent with stated objectives?

[]

     (1) The opinions and interests of units of government encompassing or adjacent to the path of the proposed tollway project in having the tollway installed;

     (2) The potential impact of the proposed tollway project on local environmental, aesthetic and economic conditions and on the economy of the state in general;

     (3) The extent to which funding other than state funding is available for the proposed tollway project and the extent to which resources other than tolls would be required to be established and/or maintained as necessary security to support such a financing;

     (4) The likelihood that the estimated use of the tollway project will provide sufficient revenues to independently finance the costs related to the construction and future maintenance, repair and reconstruction of the tollway project, including the repayment of any loans to be made from moneys in the transportation innovative partnerships account created under RCW 47.29.230 or other accounts;

     (5) With respect to tollway projects, any portion of which will be financed with state funds or department loans or grants:

     (a) The relative importance of the proposed tollway project compared to other proposed tollways; and

     (b) Traffic congestion and economic conditions in the communities that will be affected by competing tollway projects; and

     (6) The effects of tollway implementation on other major highways in the state system and on community and local street traffic.

[]

[]

     (2) After the department's opening and review of proposals, the department may issue or electronically post an addendum to the request for proposals that:

     (a) Requires proposers to address or add physical features or elements, and information or explanations that were not included in their initial proposals; or

     (b) Requires proposers to delete physical features or elements that were included in their initial proposals; or

     (c) Change the method by which the department will send any such addendum that it issues by a method other than electronic posting to all proposers to continue in the proposal process; or

     (d) Any addendum issued will contain a deadline by which the proposers must submit to the department any additions to, modifications of or deletions from their proposals.

[]

     (a) Requiring the proposer to provide additional information or clarification concerning elements or parts of its proposal;

     (b) Requiring the proposer to develop and submit additional information confirming the technical feasibility of the proposed project;

     (c) Requiring the proposer to develop and submit additional information confirming that the proposed project complies with or can be brought into compliance with relevant local and state transportation plans, restrictions on property use, and environmental laws, or that the project and the applicable plans, restrictions and environmental laws can otherwise be brought into conformity;

     (d) Requiring the proposer to commit in writing to the department to undertake good faith efforts to modify or adjust the proposal in specific ways, or to incorporate steps, characteristics or features that the department identifies as necessary or desirable to enhance the feasibility, public acceptance, transportation efficiency, or economy in execution or operation, of the project;

     (e) Otherwise requiring the proposer to develop and present revisions to, or alternatives within, the proposal that will permit the department to obtain best value based on the requirements and evaluation criteria set forth in the notice or request for proposals and based on knowledge obtained by the department by virtue of its review and evaluation of the proposals; and

     (f) Requiring the proposer to enter into an interim agreement, on terms satisfactory to the proposer and the state, under which the proposer will provide services to the department in connection with the development of the proposal or further development of the project, including assistance to the department in obtaining any necessary regulatory approvals.

     (2) The evaluation panel will report its assessments and recommendations to the commission.

[]

     (1) Select one proposal to advance to execution of a contract or development agreement; or

     (2) Select one proposal to advance to negotiations of a contract or development agreement; or

     (3) Select one proposal to advance to execution or negotiations of a contract or development agreement, subject to the proposer's willingness and ability to satisfy specified conditions; or

     (4) Pursuant to WAC 468-600-360, select more than one proposal from which to conduct competitive negotiations; or to continue competitive negotiations for a specified period of time; or

     (5) Reject all proposals. For purposes of this section, competitive negotiations means negotiations authorized under WAC 468-600-360, for the purposes of refining and arriving at a final selection of a proposer. This term does not refer to negotiations for a contract or development agreement as provided in WAC 468-600-710.

[]

     (2) The commission may announce its election to conduct competitive negotiations:

     (a) In any notice issued for solicited proposals under WAC 468-600-105; or

     (b) By written notice, by mail or by electronic means, to the proposers, issued at any time following the state's receipt of proposals under WAC 468-600-220.

     (3) In any communication under subsection (2) of this section, or by notice to the proposers issued by mail or by electronic means at any time after the receipt of proposals, the commission may announce that it will initiate competitive negotiations with all proposers who submitted responsive proposals, or only with proposers who qualify to negotiate because the state has determined that their proposals fall within a competitive range.

     (4) When the commission elects to negotiate only with proposers within a competitive range, then after the evaluation panel's evaluation of proposals in accordance with the criteria set forth in the notice or request for proposals, the commission will determine the proposers in the competitive range.

     (a) For purposes of this subsection (4), the proposers in the competitive range consist of those proposers whose proposals, as determined by the commission in its discretion, have a reasonable chance of being determined the best proposal as the result of the evaluations conducted by the evaluation panel under WAC 468-600-350. In determining which proposals fall within the competitive range, the commission may consider whether its preliminary evaluation of proposals establishes a natural break in the preliminary scores of the proposals that suggests those proposals that are sufficiently competitive to be included in the competitive range.

     (b) The department will provide written notice to all proposers, by mail or by electronic means, of the proposals the commission determines to fall within the competitive range. A proposer whose proposal is not within the competitive range may submit a written protest of the commission's evaluation and determination of the competitive range within fourteen calendar days after the date of the department's notice. A proposer's written protest must state facts and argument that demonstrate how the competitive range determination was flawed or how the commission's determination constituted an abuse of discretion. If the department receives no written protest concerning the proposed selection listing within the fourteen calendar day period, then the department will proceed with negotiations with the proposers whose proposals fell within the competitive range.

     (c) In response to a timely filed protest, the commission will issue a written decision that resolves the issues raised in the protest. The commission will make its written determination available, by mail or by electronic means, to the protesting proposer and to the proposers falling within the competitive range.

     (5) The object of competitive negotiations, which the department may conduct concurrently with more than one proposer or serially, is to maximize the state's ability to obtain best value and to permit proposers to develop revised proposals. Therefore, the negotiations may include, but shall not be limited to:

     (a) Informing proposers of deficiencies in their proposals;

     (b) Notifying proposers of parts of their proposals for which the department would like additional information; and

     (c) Otherwise allowing proposers to develop revised proposals that will permit the state to obtain the best proposal based on the requirements and evaluation criteria set forth in the notice or request for proposals.

     (6) The scope, manner and extent of negotiations with any proposer are subject to the discretion of the department. To prevent the disclosure of proposal information to a proposer's competitors, the department shall conduct negotiations with proposers before the nature of the proposals, information about the proposed project, or proposal information have been made public under WAC 468-600-600. In conducting negotiations, the department:

     (a) Shall treat all proposers fairly and shall not engage in conduct that favors any proposer over another;

     (b) Shall not reveal to another proposer a proposer's unique technology, unique or innovative approaches to project design, management or financing, or any information that would compromise the proposer's intellectual property, trade secrets or sensitive business information; or

     (c) Shall not reveal to another proposer a proposer's price or pricing information, provided, however, that the department may inform a proposer that the department considers a proposer's price or pricing information to be too high or too low.

     (7) The evaluation panel must further evaluate the proposals subjected to the competitive negotiation process, and recommendations to the commission for their action under WAC 468-600-350 (1), (2), (3) or (5).

[]

     (2) For purposes of this rule, a protesting proposer is adversely affected by a selection only if the proposer has submitted a responsive competing proposal and is next-in-line for selection. In other words, the protesting proposer must demonstrate that all higher-scoring proposers are ineligible for selection because either:

     (a) The higher-scoring proposals were not responsive to the requirements stated in the department's solicitation documents; or

     (b) The department committed a substantial violation of a provision in the department's notice requesting competitive negotiation, in these rules, or in chapter 47.29 RCW, or otherwise abused its discretion, in evaluating the revised proposals.

     (3) A proposer's written protest must state facts and argument that demonstrate how the selection process was flawed or how the commission's selection of the apparent successful proposer constituted an abuse of the commission's discretion. If the commission receives no written protest concerning the proposed selection listing within the fourteen-day period, then the selection of the successful proposer automatically shall become effective on the fifteenth calendar day after the department first transmitted or otherwise delivered its written notice of the apparent successful proposer.

     (4) In response to a proposer's timely filed protest that complies with this rule, the commission will issue a written decision that resolves the issues raised in the protest. In considering a timely protest, the commission may request further information from the protesting proposer and from the apparent successful proposer identified in the department's notice issued under subsection (1) of this section. The commission will make its written determination available, by mail or by electronic means, to the protesting proposer and to the apparent successful proposer identified in the department's notice issued under subsection (1) of this section.

[]

     (2) Upon the commission's provisional selection of a proposal subject to satisfaction of conditions, and upon expiration of the protest period, the department shall notify the proposer of the conditions. The proposer shall have a period of time, set forth in the department's notice, but to be at least ten calendar days, from receipt of the department's notification to elect to proceed under specified conditions. If the proposer elects to proceed, the department shall work with the proposer to develop a plan for satisfying the conditions. If the plan entails entry into an interim agreement, the agreement will conform to all relevant requirements of chapter 47.29 RCW and these rules.

     (3) After the commission's selection or provisional selection of a proposal, the department and the proposer may confer on any matter pertinent to refinement of the proposal.

[]

     (2) On the department's receipt of a request pursuant to chapter 42.56 RCW, for the disclosure of records or information that have been submitted to the department by a proposer under the program authorized by chapter 47.29 RCW, the department will notify the proposer of the request and provide the proposer a reasonable opportunity to demonstrate that all or part of the requested records or information are exempt from disclosure under applicable law recognizing the confidentiality of public records and information. In determining whether the information or records are exempt from disclosure, the department will consider the evidence and objections to disclosure presented by the proposer, but as custodian of the records or information, the department must make the initial determination of the records that may be withheld from disclosure.

     (3) An affected proposer who seeks to demonstrate that public records pertaining to it are exempt from disclosure must respond to the department with its evidence and objections within four working days of the department's issuance of notice of the request to the proposer. After considering the proposer's evidence and objections, the department will inform the proposer of its disclosure decision, giving the proposer no fewer than three working days in which to institute appropriate proceedings in its own behalf to protect the proposer's interests in preventing the disclosure or maintaining the confidentiality of the records or information. The proposer shall be exclusively responsible for all costs, expenses and attorney fees incurred in taking any action to prevent the disclosure of information or records under this section. The department shall not make a disclosure of records or information while an action by the proposer to enjoin disclosure thereof is pending.

[]

     (2) A proposer may desire that certain information be considered "trade secret" information for purposes of applying the public records exemption set out in state law. "Trade secret" means information, including a formula, pattern, compilation, program, device, method, technique or process that derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use; and is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. To qualify for that exemption, trade secret information must meet the following criteria:

     (a) Not be the subject of a patent;

     (b) Be known only to a limited number of individuals within an organization;

     (c) Be used in a business that the organization conducts;

     (d) Be of potential or actual commercial value; and

     (e) Be capable of providing the user with a business advantage over competitors not having the information.

     (3) The following procedures shall be followed by the proposer to designate information as trade secret:

     (a) Each individual page of a proposal, plan or progress report that contains trade secret information must be clearly marked trade secret;

     (b) Written substantiation describing what information is considered trade secret and why, must accompany the document. The written substantiation shall address the following:

     (i) Identify which portions of information are claimed trade secret;

     (ii) Identify how long confidential treatment is desired for this information;

     (iii) Identify any pertinent patent information;

     (iv) Describe to what extent the information has been disclosed to others, who knows about the information, and what measures have been taken to guard against undesired disclosure of the information to others;

     (v) Describe the nature of the use of the information in business;

     (vi) Describe why the information is considered to be commercially valuable;

     (vii) Describe how the information provides a business advantage over competitors;

     (viii) If any of the information has been provided to other government agencies, identify which one(s); and

     (ix) Include any other information that supports a claim of trade secret.

     (4) Notwithstanding a proposer's designation of information as constituting "trade secret," and subject to a proposer's opportunity to object to disclosure under WAC 468-600-605, the department may independently assess whether the trade secret exemption applies when responding to a public records request.

[]

     (1) The department must seek to adopt contracting techniques that represent the best practices in use by owners of facilities;

     (2) To the extent permitted by law, protection must be provided for local contractors to participate in any subcontracting opportunities on projects;

     (3) Projects that use tolling technology must maintain standards that are consistent with any standards adopted or widely used by the state;

     (4) Provision must be made for patrolling and law enforcement on state-owned transportation facilities, as approved by the Washington state patrol for facilities within their jurisdiction;

     (5) Any debt to be issued to pay for the construction of a state-owned transportation facility that is secured by public funds must conform to RCW 47.29.060, or if not in conformance, any agreements reached must be conditioned upon obtaining necessary legislative approval of alternative financing provisions;

     (6) The public involvement plan must provide that all forums, workshops, open houses or public meetings be administered and attended by the public sector partner; and

     (7) Any project with a capital cost in excess of three hundred million dollars must establish an advisory committee, consisting of at least five but not more than nine members, who shall be appointed by the commission.

[]

[]

     (1) If public moneys are used to pay any costs of construction of public works that is part of an eligible project, the construction contract shall contain provisions that require payment of workers under the contract in accordance with chapter 39.12 RCW; and

     (2) Any maintenance provisions on a public facility must be provided in a manner consistent with collective bargaining agreements, the Personnel Reform Act, and civil service laws in effect on any portion of the project that constitutes a public facility.

[]

     (1) At what point in the transportation project public and private sector partners will enter the project and which partners will assume responsibility for specific project elements;

     (2) How the partners will share management of the risks of the project;

     (3) How the partners will share the costs of development of the project;

     (4) How the partners will allocate financial responsibility for cost overruns;

     (5) The consequences for nonperformance;

     (6) The incentives for performance;

     (7) The invoicing and payment procedures and schedules to be followed to the extent that the department or state is to pay for the work, and the accounting and auditing standards to be used to evaluate work on the project; and

     (8) An agreement for the construction of a public improvement as part of an eligible project shall provide and be approved for bonding, financial guarantees, deposits or the posting of other security to secure the payment of laborers, subcontractors and suppliers who perform work or provide materials as part of the project. Furthermore, the department shall determine that adequate security exists to address any default or nonperformance by the private sector partner or other contractual claims of the department against the proposer; and

     (9) For projects that revert to public ownership, responsibilities for reconstruction or renovation that bring the facility up to government standards before reversion to the state.

[]

     (2) If the department has reasonable objection to any proposed subcontractor, the department is authorized to require, before the execution of a contract, an apparently successful proposer to submit an acceptable substitute. In such case, the proposer must submit an acceptable substitute, and the contract may, at the department's discretion, be modified to equitably account for any difference in cost necessitated by the substitution. The department will set a maximum time period from the date of the department's written demand for substitution within which to make an acceptable substitution. A proposer's failure to make an acceptable substitution at the end of the time period will constitute sufficient grounds for the department to refuse to execute a contract, without incurring any liability for the refusal. In setting a maximum time period, the department shall consider the scope of the subcontract, availability of other subcontractors, and whether the disapproved subcontractor is identified in the proposal as an equity contributor or source of other financial support to the project relied on by the proposer. Following such identification, the proposer shall be granted an additional maximum time period as determined by the department to conclude negotiations of acceptable terms and conditions with that substitute major subcontractor.

     (3) The department may not require any proposer to engage any subcontractor, supplier, other person or organization against whom the proposer has reasonable objection.

[]

[]

[]

     (1) Conduct a financial analysis that fully discloses all costs and cost estimates, including the costs of any financing, and all estimated project revenues; and

     (2) Compare the department's internal ability to complete the project that documents the advantages of completing the project as a public-private partnership versus solely as a public venture.

     The commission may undertake this analysis at any point in the solicited or unsolicited proposal process.

[]

[]

[]

[]

     (1) Approve the final agreement;

     (2) Reject the final agreement; or

     (3) Return the final agreement to the team for further negotiation on issues the commission specifies.

[]

[]

     (a) Reject any and all proposals at any time;

     (b) Terminate evaluation of any and all proposals at any time;

     (c) Suspend, discontinue and/or terminate comprehensive agreement negotiations with any proposer at any time prior to the actual authorized execution of such agreement by all parties;

     (d) Negotiate with a proposer without being bound by any provision in its proposal;

     (e) Request or obtain additional information about any proposals;

     (f) Issue addenda to and/or cancel any RFQ or RFP;

     (g) In accordance with the rule-making procedures of chapter 34.05 RCW, supplement or withdraw all or any part of these rules;

     (h) Decline to return any and all fees required to be paid by proposers hereunder; and

     (i) Request revisions to proposals.

     (2) Absent express written provisions contained in any solicitation document, order or written policy issued by the department, the department is not liable for, or required to, reimburse the costs incurred by proposers, whether or not selected for negotiations, in developing proposals or in negotiating agreements. Any and all information the department makes available to proposers shall be as a convenience to the proposer and without representation or warranty of any kind.

[]

© Washington State Code Reviser's Office