Docstoc

State of Oregon Oregon Department of Transportation REQUEST FOR

Document Sample
State of Oregon Oregon Department of Transportation REQUEST FOR Powered By Docstoc
					RFP #730-24226-10




                                   State of Oregon
                    Oregon Department of Transportation
                    REQUEST FOR PROPOSALS (RFP)
                         RFP Number 730-24226-10

                     Software Configuration Management
                            Software and Services

                        Date of Issuance: August 6, 2010
                     Proposals Due Date: September 9, 2010
                      Issuing Office: ODOT Procurement Office
                      Single Point of Contact (SPC): Tara K. Anderson, CPPB, OPBC
                      Address: 455 Airport Road SE, Bldg K
                                Salem, Oregon 97301
                      Phone (voice): (503) 986-2921
                      E-mail: tara.k.anderson@odot.state.or.us




                                                                         Page 1 of 100
                                                                        Table of Contents
                                                                                                 RFP
SECTION 1: PURPOSE AND GENERAL INFORMATION............................................................................................................3
    1.1 INTRODUCTION ................................................................................................................................................................................3
    1.2 SCHEDULE ........................................................................................................................................................................................4
SECTION 2: PROPOSAL .....................................................................................................................................................................5
    2.1 PROPOSAL REQUIREMENTS ..............................................................................................................................................................5
    2.2 AMENDMENTS ..................................................................................................................................................................................5
    2.3 SINGLE POINT OF CONTACT (SPC)...................................................................................................................................................5
SECTION 3: SOLICITATION PROCESS ..........................................................................................................................................6
    3.1 PROCUREMENT AUTHORITY AND METHOD ......................................................................................................................................6
    3.2 ORPIN.............................................................................................................................................................................................6
    3.3 QUESTIONS, MODIFICATIONS AND PROTESTS...................................................................................................................................6
    3.4 SUBMISSION OF PROPOSALS .............................................................................................................................................................8
    3.5 WITHDRAWAL OF PROPOSALS ..........................................................................................................................................................8
    3.6 OPENING OF PROPOSALS ..................................................................................................................................................................8
    3.7 PUBLIC INFORMATION, CONFIDENTIALITY, AND TRADE SECRETS ...................................................................................................8
    3.8 COST OF PREPARING PROPOSALS .....................................................................................................................................................8
    3.9 RESERVATION OF AGENCY RIGHTS ..................................................................................................................................................8
    3.10 PRICE AGREEMENT FORM ..............................................................................................................................................................9
    3.11 NO CONTRACTUAL OBLIGATION ....................................................................................................................................................9
    3.12 OWNERSHIP OF MATERIALS ...........................................................................................................................................................9
SECTION 4: EVALUATION AND AWARD ......................................................................................................................................9
    4.1 EVALUATION PROCESS .....................................................................................................................................................................9
    4.2 EVALUATION OF MINIMUM REQUIREMENTS (PASS/FAIL) ................................................................................................................9
    4.3 SCORING OF PROPOSAL ..................................................................................................................................................................10
    4.4 PRELIMINARY RANKING OF PROPOSALS; DETERMINATION OF COMPETITIVE RANGE ....................................................................11
    4.5 EVALUATION OF PRESENTATIONS/DEMONSTRATIONS ...................................................................................................................11
    4.6 REFERENCES ..................................................................................................................................................................................11
    4.7 FINAL RANKING OF PROPOSALS ...................................................................................................................................................12
    4.8 AWARD NOTIFICATION AND PROCESS ............................................................................................................................................12
ATTACHMENT A SAMPLE PRICE AGREEMENT.......................................................................................................................15
    EXHIBIT A CONFLICT OF INTEREST (COI) DISCLOSURE FORM............................................................................................30
    EXHIBIT B INSURANCE..................................................................................................................................................................31
    EXHIBIT C CERTIFICATION STATEMENT FOR INDEPENDENT CONTRACTOR .................................................................32
    EXHIBIT D AUTHORIZED REPRESENTATIVES TO THE PRICE AGREEMENT..........................................................................................33
    EXHIBIT E SAMPLE FORM.............................................................................................................................................................34
ATTACHMENT B – 1 PROPOSAL FORM .......................................................................................................................................38
    COVER SHEET ......................................................................................................................................................................................38
    CONTRACTOR PERSONNEL AND KEY PERSONS .....................................................................................................................41
    PROPOSER RESPONSES TO SCOPE OF WORK............................................................................................................................47
    CONTRACTOR’S SOFTWARE LICENSE AGREEMENT .............................................................................................................50
    PRODUCTS AND SERVICES WARRANTY ...................................................................................................................................51
    MAINTENANCE & SUPPORT .........................................................................................................................................................52
    TECHNICAL ENVIRONMENT ........................................................................................................................................................53
    FUNCTIONAL REQUIREMENTS ..............................................................................................................................................................54
ATTACHMENT B – 2 PRICING PROPOSAL FORM.....................................................................................................................77
    FINANCIAL BACKGROUND INFORMATION..............................................................................................................................78
ATTACHMENT C DRAFT WOC #1 FOR DMV ..............................................................................................................................79

ATTACHMENT D WOC 1 EXHIBITS 1 - 13 .................................................................................................................................. 100


                                                                                                                                                                Page 2 of 100
Section 1: Purpose and General Information
1.1 Introduction

Overview

This RFP is intended to result in one Price Agreement awarded to one Contractor for Software Configuration Management
software, maintenance and related Services. The current work is to be performed at ODOT’s Driver and Motor Vehicles
(DMV) division. However, other divisions of ODOT may issue a Work Order Contract (WOC) to order software products
and Services. The intent of this solicitation is to provide a Price Agreement that is available to all of ODOT for future use
and incorporates the Contractor’s catalog of services and supplies relating to SCM products. This RFP will focus primarily
on the current need at DMV and result in an ODOT Price Agreement and the first DMV Work Order Contract.


DMV wants to replace its current assortment of SCM tools. These tools are an in-house-developed library-management
system for mainframe components, an open-source product for web components, and a COTS product for client/server
components. These three tools are not integrated, and they use paper-based approval processes. In addition, these
tools provide no automated support for concurrent development, which is becoming increasingly important at DMV.
DMV's applications are highly coupled, and many development projects that have overlapping timeframes also have a
number of programs in common. Coordinating the modification of these programs is vital to the success of DMV's
application development activities.


DMV wants to acquire and implement an SCM solution that will support the development and deployment of DMV's
applications. The SCM solution will consist of one or more SCM products plus the services needed to fully implement the
products and to establish appropriate SCM procedures. The SCM products are expected to be industry-standard, COTS
products. (The purchase of COTS software supports the State Chief Information Officer Council’s actions to optimize
information technology cost and efficiency.) The SCM solution must support and integrate all significant platforms and
architectures that are currently used to execute DMV applications. The SCM solution must also provide the following:


•   Library management functions that support the modification and migration of source components

•   Version control functions that ensure source integrity and prevent accidental source regression

•   Branching and merging capabilities that support concurrent development

•   Impact analysis capabilities that enable determination of the effects of potential changes

•   Simplified recovery functions that enable the restoration of prior source versions

Implementation of the SCM solution will introduce a standardized, automated, and controlled discipline for executing and
managing many aspects of the application development process at DMV. The following are some of the expected
benefits from this implementation:


•   Accelerated application development and improved application quality and reliability

•   Early identification of the potential impacts of application changes

•   Identification and maintenance of source component and system relationships

•   Automation of many SCM-related processes and the reduction of the manual intervention needed to move, promote,
    and recover source components

•   Retirement of DMV's current assortment of SCM tools



                                                                                                   Page 3 of 100
The Oregon State Data Center (SDC) is a stakeholder in this RFP because the SCM product will run on the State
infrastructure at the SDC.

Price Agreement Term.
The Price Agreement is anticipated to start in November 2010 and extends through December 2020. The parties may
agree to extend the term of any WOC by amendment for continuing maintenance and support services for the duration of
the Price Agreement. Additional WOCs may follow to provide products and services for other divisions of ODOT through a
negotiated WOC.

Method of Compensation.
The contract payment method shall be fixed price for the software and any products and either fixed price or a fixed price
and time and materials combination (with fixed due dates) per deliverable for the Services. Licensing and Maintenance
and Support shall be payable annually based on costs negotiated in the Price Agreement. Training costs, if any, will be
negotiated at the time each WOC is initiated.

Ordering Software and Services.
ODOT may choose to purchase software and Services from the resulting Price Agreement using a Work Order Contract
(WOC). All prices negotiated as part of the Price Agreement will be honored by the Contractor in all WOC’s executed from
this price Agreement.

Work Order Contract No.1
After execution of the Price agreement, a WOC will be executed immediately for DMV’s software installation and related
Services. DMV desires the product to be installed and the services to be completed for DMV by June 2011. The current
effort to purchase software and Services for DMV as described in this RFP is estimated to be in the range of $450,000 to
$500,000 and will be defined in a WOC to be executed upon final execution of the Price Agreement. A draft of anticipated
WOC # 1 is attached as Attachment C.


1.2 Schedule

        Event                                                                Due Date
        RFP Release – Date of Issuance                                       August 6, 2010
        Mandatory Pre-Proposal Conference                                    August 17, 2010 by 1:30 PM
        Written Questions Due                                                August 29, 2010
        RFP Protests, Changes, Clarifications Accepted                       August 23, 2010 by 10:00 AM
        Addenda to Answer Pre-Proposal Questions issued on ORPIN             August 27, 2010
        RFP Closing                                                          September 9, 2010 by 2:00 PM
        Opening of Proposals                                                 September 9, 2010 at 2:00 PM
        Competitive Range determined (approx.)                               September 28, 2010
        Presentation/Demonstrations Completed by (approx.)                   October 22, 2010
        Award Notification (approx.)                                         October 26, 2010
        Issuance of Notice of Intent to Award (approx.)                      October 26, 2010
        Award Protests due (approx.)                                         November 2, 2010 by 5:00 PM

A mandatory Pre-Proposal Conference will be held on August 17, 2010 at DMV Headquarters, 1905 Lana Ave NE, Salem
OR, 97314 from 1:30 PM to 3:30 PM. Attendance may be in person or via i-linc.

                Please use this link to join the meeting: http://ilinc.odot.state.or.us/ilinc/join/wmfzc

                If you have never attended a MeetingLinc meeting, click here now:
                http://ilinc.odot.state.or.us/iLinc/docs/help/odot/noob.htm

                Audio for this meeting will be through a telephone conference. Please call (877) 287-0283 when the
                meeting starts. When prompted for the PIN, enter 245497.

The Pre-Proposal Conference is intended to clarify the intent of this RFP and may result in an Addendum to the RFP to
answer the questions submitted to date and asked at the Conference. Only written questions and answers posted on
ORPIN through an Addenda to the RFP are binding to the Agency, verbal discussions at the Conference are not binding
to the Agency. Proposals will not be accepted from proposers who do not attend the mandatory Pre-Proposal
Conference.

                                                                                                       Page 4 of 100
Section 2: Proposal
2.1 Proposal Requirements

Proposal Form with Cover Sheet.
A Proposal Form has been provided to simplify and create consistency in the development of your Proposal. The
Proposer shall sign and submit the Cover Sheet included in the Proposal Form. Proposals shall address the proposal and
submission requirements set forth in the RFP and shall describe how the Software and Services shall be provided.
Proposals that merely offer to provide Software and Services as stated in the RFP shall be considered non-responsive
and shall not be further considered. All Proposals shall be completed using the Proposal Forms included as Attachment
B-1 and B-2. Proposals must be separately submitted in a sealed envelope or box, labeled “Proposal Form to RFP #730-
24226-10” and delivered to the SPC by the date and time specified.

Pricing Form (Attachment B-2)
Attachment B-2 containing all pricing information is to be submitted in a separate sealed envelope labeled RFP # 730-
24226-10, Attachment B-2 – Pricing Form. Pricing information will not be distributed to the Evaluation Committee until
after the Attachment B-1 Proposal Form has been evaluated and scored and the Proposers have been ranked.

For reduced or free or no cost solutions to be considered, a Proposer shall submit with their Pricing Form a license
agreement and/or letters guaranteeing that the Agency has the right to use the solution at no cost to the Agency. For
example if you are wanting to leverage already existing licenses with the State, you will need to submit the license
agreement and a letter guaranteeing that the Agency has the right to use the solution from the existing owner and
manufacture of the solution.

Copies.
Submissions of Attachment B-1 Proposal Form in response to the RFP shall contain 1 original, signed hard copy plus 7
copies and 1 CD containing a scanned pdf version of the signed Attachment B-1 Proposal Form. Attachment B-2 Pricing
Form is to be submitted as one original hard copy and 1 CD containing a scanned pdf version of Attachment B-2 Price
Form in a separate sealed and labeled envelope.


2.2 Amendments

The parties may agree to amend or modify the awarded Price Agreement or a WOC in accordance with OAR 125-246-
0560 or 125-247-0285.

The general circumstances that might require an Amendment to be issued under the Price Agreement or a WOC include
an extension of time and money and additional years of software maintenance and support.

Anticipated Amendments
Anticipated Amendments may also be issued to WOCs that authorize purchases of software and services for other offices
within ODOT. Anticipated Amendments may be issued to add or change deliverables in the Statement of Work of a WOC,
add amounts payable for additional deliverables, extend or change due dates for deliverables, add or delete Key Person
Classifications and purchase related but new software products or maintenance and support services.

Unanticipated Amendments
Except for these Anticipated Amendments, any and all later amendments shall be deemed unanticipated.

Change Orders
Change Orders are written changes to the statement of work to modify existing deliverables, modify estimated due dates
or move fixed costs or portions thereof from one deliverable to another. Change Orders do not increase or decrease the
total not to exceed of the contract and are not used to add deliverables. Change Orders must be in writing (email
acceptable), follow that change order process, and the contract is deemed amended.


2.3 Single Point of Contact (SPC)

All questions, whether about the technical requirements of the RFP, contractual requirements, the procurement process,
or any other aspect of the project or needed services, shall be directed only to the person listed on the first page of the
RFP. The RFP document may be reviewed upon request at the address listed on the first page of the RFP.
                                                                                                   Page 5 of 100
Section 3: Solicitation Process

3.1 Procurement Authority and Method

Agency is conducting the RFP pursuant to its authority under ORS 279A.050. Agency intends to use the Competitive
Sealed Proposals method pursuant to ORS 279B.060 and OAR 125-247-0260. Agency intends to conduct a multistep
Competitive Sealed Proposal method.

FOR THE MULTISTEP SEALED PROPOSALS METHOD UNDER OAR 125-247-0260:
            i. INITIAL EVALUATION
           ii. COMPETITIVE RANGE;
          iii. PRESENTATION/DEMONSTRATION;
          iv.  BEST AND FINAL OFFERS;
           v.  NEGOTIATIONS.



3.2 ORPIN

The RFP, including all Addenda and Attachments, shall be posted on the Oregon Procurement Information Network
System (ORPIN). Agency is not required to mail the RFP, its Addenda or Attachments. Notification of any substantive
clarifications provided in response to any question will be provided and published at the ORPIN web site below. For
complete RFP documentation please go to the ORPIN web site:
http://orpin.oregon.gov/open.dll/welcome and view Agency Opportunity number 730-24226-10.
Proposers without electronic access to ORPIN may obtain access to ORPIN and download copies at the location listed on
the front page of the RFP. Proposers may also order hard copies from the SPC.

Addenda to RFP on ORPIN.
Addenda are incorporated within the RFP and may be viewed and downloaded on ORPIN by registered suppliers.
Proposers should consult ORPIN regularly until Closing to ensure that they have not missed any Addenda
announcements.

Any oral communications shall be considered unofficial and non-binding. Proposers shall rely only on written statements
issued by the SPC.

ORPIN Usage.
Proposers unfamiliar with ORPIN may contact the State Procurement Office (SPO) at the Department of Administrative
Services, 1225 Ferry St. SE - U140, Salem, OR 97301-4285; telephone (503) 378-4642. Proposers may also look for
updates about ORPIN on the SPO website: http://procurement.oregon.gov/.

ORPIN Registration.
Proposers are responsible for ensuring that their registration information is current and correct. Agency accepts no
responsibility for missing or incorrect information contained in the supplier’s registration information in ORPIN.


3.3 Questions, Modifications and Protests

Submittal of Questions and Requests.
Questions, including requests for explanations of the meaning or interpretation of provisions of the RFP, shall be submitted in
writing, arrive by the date and time specified above, and be addressed to the attention of the SPC. Emails are acceptable.

        Note: with the exception of Negotiations of those terms outlined in Section 4.8, this is the Proposer’s only
        opportunity to request any change or protest any requirement of the RFP, including but not limited to the
        solicitation process, proposal requirements or terms and conditions.




                                                                                                    Page 6 of 100
Methods of Seeking Modifications to RFP, Contractual Provisions or Specifications.

                1 Procedure.
                The appropriate means of seeking modifications to provisions of the RFP are through a written (a)
                request for clarification; (b) formal submittal of requests for changes to the RFP, contractual terms or
                specifications; or (c) formal submittal of protests of the RFP, contractual terms or specifications.

                2 Request for Clarification.
                Any Proposer requiring clarification of any provision of the RFP, Price Agreement terms or conditions
                may submit to the SPC a written request for clarification. To be considered, the request shall be
                received by the SPC by the deadline specified or any extension made by subsequent Addenda.

                3 Request for Changes to RFP, Contractual Terms or Specifications.
                Any Proposer may submit to the SPC a written request for changes to the RFP, Price Agreement terms
                or conditions. To be considered, the request for changes shall be received by the SPC by the deadline
                specified above or any extension made by subsequent Addenda to this RFP. The request shall include
                the reason for requested changes, supported by factual documentation, any proposed changes and
                shall contain all other information required by ORS 279B.405 and OAR 125-247-0730.

                4 Protest of RFP, Price Agreement Terms or Conditions.
                Proposers may submit to the SPC a written protest of RFP, Price Agreement terms or conditions. To be
                considered, Protests shall:

                   Identify the Proposer’s name and reference the RFP number;

                   Contain evidence that supports the grounds on which the protest is based and specify the relief sought,
                   including a statement of the proposed changes to the process or RFP provisions, requirements or terms
                   and conditions that the Proposer believes shall remedy the conditions upon which the protest is based;

                   Be signed by the Proposer’s authorized representative;

                   Be submitted to the SPC by the Solicitation Protest due date specified above; and

                   Be delivered or emailed to the SPC at the address specified on the first page of the RFP.

                   Agency shall not consider solicitation protests that do not meet the requirements. Agency shall resolve
                   all solicitation protests in accordance with OAR 125-247-0730. Unless this specific due date is
                   extended by Addenda to the RFP, Agency shall not consider solicitation protests to the originally-issued
                   RFP submitted after the Solicitation Protest due date specified above.

Method of Submitting Requests for Modification of RFP Provisions. Envelopes containing requests for clarification,
      requests for change, and protests shall be marked as follows:

                          Request for Clarification /Change /Protest
                          RFP Number
                          Closing Date

Envelopes shall be received by the SPC by the date and time specified above. This deadline may be extended by
Addendum. No requests for clarification, requests for change or protests regarding the RFP, contractual terms or
specifications shall be considered if received after the date specified in this Section or the date specified in a subsequent
Addendum.

Response to Requests for Clarification or Change and Protests. Agency shall respond to each written request for
clarification, request for change, and protest in accordance with ORS 279B.405. Where appropriate, Agency shall issue
revisions and clarify RFP provisions via Addenda posted on ORPIN. Agency may also informally respond to Proposer
questions. Informal responses, however, do not affect the provisions of the RFP. The RFP, Price Agreement
terms and conditions can only be changed via addenda issued by Agency.




                                                                                                    Page 7 of 100
3.4 Submission of Proposals

All Proposal Forms shall be received by the SPC no later than the closing date and time specified in ORPIN at the
address listed on the front page of the RFP. Proposal Forms may be delivered via U.S. Mail or courier or hand-
delivered. Proposal Forms shall be sent to the attention of the SPC.


3.5 Withdrawal of Proposals

If a Proposer wishes to withdraw a submitted Proposal Form, it shall do so prior to the Closing date and time. The
Proposer shall submit a written request to withdraw, signed by the Proposer, on the Proposer’s letterhead, to the SPC at
the address listed on the front page of the RFP, as required by OAR 125-247-0440(2).


3.6 Opening of Proposals

Proposals shall be opened and the names of all Proposers shall be read at the date and time listed above. Proposals will
not be read aloud (OAR 125-247-0450(2)). Proposals shall be opened at the address of the SPC.


3.7 Public Information, Confidentiality, and Trade Secrets

All Proposals are public information after the Proposals have been opened, and all protests are public information after
the protest period ends. Proposals shall be opened by the SPC at the date and time listed above. Copies of Proposals,
however, shall not be provided until the evaluation process has been completed and a Notice of Intent to Award has been
issued pursuant to OAR 125-247-0630. Copies of public information may be requested by any person. Proposers shall
label any information that it wishes to protect from disclosure to third parties as a trade secret under ORS 192.501(2) with
the following: "This material constitutes a trade secret under ORS 192.501(2) and is not to be disclosed except as
required by law." Agency shall take reasonable measures to hold in confidence all such labeled information, but the
State shall not be liable for release of any information when required by law or court order to do so, whether pursuant to
the Oregon Public Records Law or otherwise and shall also be immune from liability for disclosure or release of
information under the circumstances set out in ORS 646.473(3).


3.8 Cost of Preparing Proposals

All costs incurred in preparing and submitting a Proposal Form in response to the RFP are the responsibility of the
Proposer and shall not be reimbursed by Agency.


3.9 Reservation of Agency Rights

Agency reserves all rights regarding the RFP, including, without limitation, the right to:
   a. Amend, delay or cancel the RFP without liability if Agency finds it is in the best interest of the Agency to do so;
   b. Reject any or all Proposals received upon finding that it is in the best interest of the Agency to do so;
   c. Waive any minor informality or non-conformance with the provisions or procedures of the RFP, and seek
       clarification of any Proposal, if required;
   d. Reject any Proposal that fails substantially to comply with all prescribed RFP procedures and requirements;
   e. Negotiate a Statement of Work based on the Scope of Work and to negotiate separately in any manner necessary
       to serve the best interest of the public;
   f. Amend any Price Agreements or Contracts that are a result of the RFP;
   g. Engage contractor by selection or procurement independent of the RFP process or any Contracts or agreements
       under it to perform the same or similar services; and
   h. To extend any Price Agreement that results from the RFP without an additional RFP process up to a total of 10
       years, pursuant to OAR 125-246-0560.

Although price is a consideration in determining the apparent successful Proposer, the intent of the RFP is to identify a
Proposal from a Proposer that has a level of specialized skill, knowledge and resources to perform the work described in

                                                                                                  Page 8 of 100
the RFP. Qualifications, performance history, expertise, knowledge and the ability to exercise sound professional
judgment are primary considerations in the selection process. Due to the highly technical nature of some of these tasks,
the Proposer with the lowest Price may not necessarily be awarded a Price Agreement. Agency reserves the sole right to
determine the best Proposal.


3.10 Price Agreement Form

The apparent successful Proposer shall be asked to sign a Price Agreement substantially in the Price Agreement form
that is included as Attachment A.


3.11 No Contractual Obligation

Agency is not obligated as a result of the submission of a Proposal Form to enter into a Price Agreement with any
Proposer, and has no financial obligation to any Proposer arising from the RFP.


3.12 Ownership of Materials

        All materials submitted in response to this RFP become the property of OPO. Proposals and supporting materials
        will not be returned to Proposers unless the Proposal is submitted late or the RFP is cancelled.



Section 4: Evaluation and Award

4.1 Evaluation Process

Agency shall conduct an evaluation of the Proposal Forms received in response to the RFP.

Agency shall establish an evaluation committee which may consist of Agency staff, government partners and community
and public partners to review, evaluate and score each Proposal Form.

Any attempt by a Proposer to improperly influence a member of the evaluation committee during the proposal review and
evaluation process shall result in proposal rejection.

Agency shall evaluate and score all Proposals on the completeness, quality, and applicability of their content in
accordance with the following Sections:

                Evaluation of Minimum Requirements (Pass/Fail)
                Attachment B-1 Evaluation of Proposal Forms (Scored)
                Preliminary Ranking of Proposal Forms (based on Evaluation Scores)
                Evaluation of Presentations/Demonstrations (Scored)
                Reference Checks (Scored)
                Final Ranking of Proposals and Intent to Award


4.2 Evaluation of Minimum Requirements (Pass/Fail)

The SPC shall review all Proposals on a pass/fail basis and determine if each Proposal meets the minimum proposal
requirements. Minimum Requirements are that a proposal is received in the format provided as the Proposal Form that
includes a signed Cover Sheet. Proposer’s failure to comply with the instructions or to submit a complete Proposal Form
may result in the Proposal being deemed non-responsive. Only those Proposals determined to be responsive to the
Minimum Requirements shall be considered for further evaluation by the evaluation committee.




                                                                                                  Page 9 of 100
4.3 Scoring of Proposal

The evaluation committee shall score all Proposals using the information provided on the Proposal Form (Attachment B-
1). Points will be distributed among the scoring sections as indicated below and on the Proposal Form and the Form will
be used by the Evaluation team to score actual points awarded. Actual points assigned by each evaluation committee
member shall be added together and divided by the total number of evaluation committee members to compute an
average score for the evaluation. Points determined awarded for the Pricing Form will be added to the Proposal Form
points to determine the ranking of Proposers.

PROPOSAL FORM EVALUATION                                               Possible
                                                                       Points
Contractor Personnel and Key Persons                                    30
Proposer Responses to Scope of Work                                     75
Proposer Response related to Warranty and Support                       50
Technical Environment                                                   35
Functional Requirements                                                210
SUB TOTAL Possible Points from Proposal Form                           400
Pricing Information                                                    200
Presentation/Demonstration                                             300
References (corporate – 25 and Key Person Professional – 75)           100
TOTAL Possible Points                                                  1000
The evaluation committee may request additional clarification from Proposers for any portion of the Proposal Forms. If a
Proposal Form is unclear, Proposer may be asked to provide clarification by the SPC. No new information or
documentation may be submitted, however, and clarifications may not be used to rehabilitate a non-responsive Proposal
Form. Proposers shall remain available during the evaluation period to respond to requests for additional clarification.
Proposers shall submit written signed clarification(s) within 24 hours of request (Monday through Friday, state-observed
holidays and mandatory Furlough Days excluded) following receipt of the request. Failure to provide clarification may
result in a lower score.

Price Scoring
Price Proposals will be scored by the SPC prior to the Evaluation Committee Wrap up meeting. The Evaluation
Committee will not see the Price Proposals until after the Proposal Forms have been evaluated.

The lowest proposed price shall be awarded the maximum number of Price Points available which is 200. Proposals with
higher prices shall be awarded a percentage of the maximum Price Points awarded based on the following formula:

         (L/X)*Y = A
         where:
                  X = Price Proposal being scored
                  L = Lowest Price Proposal among all Proposals
                  A = Awarded points
                  Y = Total Points Possible
If the SPC requests clarification of any pricing information Proposer shall provide the clarification within 24 hours (Monday
through Friday, state-observed holidays and mandatory Furlough Days excluded) or the Proposal Form may be rejected
as non-responsive at the sole discretion of Agency.

Reciprocal Preference. In accordance with OAR 125-246-0310, when evaluating Proposals, Agency shall add a
percentage increase to the Prices of a non-resident Proposer equal to the percentage, if any, of the preference that would
be given to that Proposer in the state in which Proposer resides.




                                                                                                   Page 10 of 100
4.4 Preliminary Ranking of Proposals; Determination of Competitive Range


Agency will rank the Proposals as a result of the initial evaluation of Proposals to determine Proposers in the Competitive
Range. The “Competitive Range” is the three highest ranked Responsive, Responsible Proposers. Agency reserves the
right to increase the number of Proposers in the Competitive Range if Agency evaluation establishes a natural break in
the scores of Proposers indicating that a number of Proposers greater than the initial Competitive Range are closely
competitive or have a reasonable chance of being determined the most Advantageous Proposer. Agency reserves the
right to reduce the Competitive Range to two Responsive and Responsible Proposers, if there is a natural break between
the second and third ranked proposals.

            a. Following its determination of the Competitive Range, Agency will notify every Proposer of its respective
               Competitive Range status in writing (“Notice of Competitive Range”).

            b. Upon its determination and Notice of Competitive Range, Agency will concurrently provide written notice
               to all Proposers in the Competitive Range.


4.5 Evaluation of Presentations/Demonstrations

All points received in the Scoring of Proposals will be added to the Presentation/Demonstration score for those Proposers
in the Competitive Range. The Agency shall score Presentations/Demonstrations based on a script that will be submitted
to Proposers in the Competitive Range along with a notification of the time and date of the Presentations/Demonstrations.
Intended point distribution will be provided to the Competitive Range along with a script for the
Presentation/Demonstrations.

All costs associated with the Presentations/Demonstrations are the responsibility of the Proposer. Due to the potential for
connectivity incompatibility, Proposer shall provide all audio/visual equipment with connectivity necessary for the
Presentations/Demonstrations. Agency will provide a suitable venue. Agency reserves the right to not reschedule any
event due to technical difficulties absent extraordinary conditions.

Each Proposer shall be provided 2 days (a total of 16 hours) to present and demonstrate. If a Proposer is offered a
Presentation/Demonstration, a script will be provided.

Each member of the Evaluation Committee shall award points based on his or her assessment of how well the
Presentations/Demonstration covered the script and how well each Proposer understood the Agency’s needs and
provided the best overall solution. Evaluation points provided by each evaluation committee member shall be added
together and divided by the total number of evaluation committee members to compute an average score for the
presentations/demonstration.


4.6 References

References will be contacted to verify Proposer’s ability to perform the work requested in the RFP. Agency will attempt
to contact each of the three references provided by the Proposer. A maximum of three (3) attempts will be made for each
reference. If these attempts are unsuccessful, the Proposer will not receive points for that reference.

Agency reserves the right to contact references in addition to those provided by the Proposer to investigate any
references whether or not furnished by the Proposer, and to investigate the past performance of any Proposer. Agency
may investigate the qualifications of a Proposer, including but not limited to: successful performance of similar services;
compliance with specifications and contractual obligations; its completion or delivery of services on schedule; and its
lawful payment of suppliers, subcontractors, and workers.

        4.6.1 Corporate References

        Proposers shall provide the names, addresses, telephone numbers, contact information, and project description
        for 3 customers for whom Proposer has provided services to within the last five years, Government references are
        preferred. A mix of public/private sector references would be acceptable. Products and Services equivalent to
        those described in the RFP.

                                                                                                   Page 11 of 100
       4.6.2 Key Person References
       Proposers shall provide the names, addresses, telephone numbers, contact information, and project description for
       3 professional references for each Key Person. Professional references must reference projects for services
       provided within the last five years and Services equivalent to those described in the RFP.


4.7 FINAL Ranking of Proposals

The evaluation committee will determine the final total score based on the Presentation/Demonstrations and the Intent to
Award will be announced.



4.8 Award Notification and Process

       First Selection.
       Following the identification of an apparent successful Proposer, Agency may elect to notify the Proposer and
       request a signed Price Agreement substantially in accordance with the form set forth in Attachment A.

       Successive Selection and Rejection.
       If negotiations are not successful, Agency may terminate negotiations with highest ranked firm and begin
       negotiations with second higher ranked firm. All Proposers shall be notified of the status of their Proposal. If all
       Proposals are rejected, the SPC shall promptly notify all Proposers. No information shall be given to any Proposer
       (or any other individual) relative to their standing with other Proposers during the RFP process.

       Negotiation.

       The Sample Price Agreement (Attachment A) contains the terms and conditions that will govern the Price
       Agreement. The State will also consider for negotiation terms and conditions from the Proposer's software license
       agreements, maintenance contracts, technical support agreements and other similar documents that do not
       materially conflict with this RFP, including the Sample Price Agreement, or which would materially change the
       nature of this solicitation or adversely effect competition (Peripheral Agreements). The State will only consider
       terms and conditions contained in such Peripheral reasonably related to this RFP and which supplement, and are
       not materially in conflict with, the terms and conditions contained in the Sample Price Agreement and this RFP.

       Peripheral Agreements. Proposers shall include any Peripheral Agreements with their Proposals related
       to their Proposals that they seek the State to consider as prescribed in RFP.

       NEGOTIABLE ITEMS: The following Contract terms and conditions may be negotiated by the State and
       the apparent Successful Proposer to the extent they do not conflict with Oregon Revised Statute:

                  Term of Contract (Length of Contract)
                  Extensions
                  Contract price as it is affected by the results of negotiating the Scope of Work/Specifications
                  Schedules
                  Scope of Work of the PA
                  Statement of Work of WOC 1
                  Warranty
                  Key Person(s)
                  Attachment A, Section 5 Compensation
                  Agency will consider for negotiation and inclusion in to the Contract those terms and
               conditions from Proposer’s
                                      a.       Software license agreements;
                                      b.       Software maintenance agreements, including measurable service levels
                                               for support and performance credits;
                                      c.       Technical support agreements.




                                                                                                 Page 12 of 100
Statement of Work, WOC #1:
Upon Notice of Intent to Award, Contractor shall confer with DMV and deliver a Statement of Work, Pricing Form
and Schedule (Plan) to accomplish work that is required in WOC #1 for discussion and approval by DMV. The
Plan must include estimated delivery dates for the future deliverables keeping in mind that DMV desires the
completion of all work to be accomplished by June 30, 2011. The DMV approved Plan will be used by Proposer to
create the first deliverable required by WOC #1.
The deliverable due dates will be mutually agreed upon during DMV approval of the FINAL Project Plan and
schedule which is the first deliverable due under the WOC. The DRAFT Project Plan and schedule must include
at a minimum:
    •   Project schedule including tasks and activities, deliverables, location of task and activities, activity
        duration, resources, sequencing and dependencies;
    •   Project work plan for each deliverable, including a work breakdown structure;
    •   Completion date for each task and deliverable;
    •   Project milestones;
    •   Entrance and exit criteria for specific project phases; and
    •   Project organization including a resource plan that defines roles and responsibilities for the Contractor
        and DMV resources.


Award Protests.
Agency shall notify every Proposer of its selection status. A Proposer who claims to have been adversely
affected or aggrieved by the selection of a competing Proposer may protest the selection by submitting, within
seven calendar days after receiving notice of the selection a written, signed protest by U.S. Mail or courier, or by
hand-delivery or e-mail to the SPC at the address listed on the front page of the RFP. To be adversely affected or
aggrieved, a Proposer shall demonstrate that all higher ranked Proposals were ineligible for selection as per ORS
279B.410(1)(a) and (b). Agency shall not consider a protest submitted after the deadline. Protests shall be
resolved according to Oregon Administrative Rules. Faxed protests shall not be accepted.

Insurance Certification.
The apparent successful Proposer shall provide all required proofs of insurance to Agency within seven calendar
days of the Intent to Award Notice. Failure to present the required documents within the seven calendar-day
period may result in proposal rejection. Proposers are encouraged to consult their insurance agent(s) about the
insurance requirements contained in the RFP prior to proposal submission.



Preference for Oregon Supplies and Services.
If Agency receives Proposals identical in price, fitness, availability and quality and chooses to award a Price
Agreement, Agency shall award the Price Agreement in accordance with the procedures outlined in OAR 125-
246-0300.

 Responsive and Responsible Determinations.

        Responsive.
        To be considered responsive, the Offer shall substantially comply with all requirements of the RFP and all
        prescribed public solicitation procedures. In making such evaluation, Agency may waive minor
        informalities and irregularities. Prior to award of a Price Agreement, Agency intends to evaluate whether
        the apparent successful Proposer meets the applicable standards of responsibility identified in OAR 125-
        247-0500. In doing so, Agency may investigate Proposer and request information in addition to that
        already required in the RFP, when Agency, in its sole discretion, considers it necessary or advisable.

        Responsible.
        Agency reserves the right, pursuant to OAR 125-247-0500, to investigate and evaluate, at any time prior
        to award and execution of the Price Agreement, the apparent successful Proposer's responsibility to
        perform the Price Agreement. Submission of a signed Proposal shall constitute approval for Agency to
        obtain any information Agency deems necessary to conduct the evaluation. Agency shall notify the
        apparent successful Proposer in writing of any other documentation required, which may include but is
        not limited to: recent profit-and-loss history; current balance statements; assets-to-liabilities ratio,
        including number and amount of secured versus unsecured creditor claims; availability of short and long-
        term financing; bonding capacity; credit information; material; equipment; facility and personnel
                                                                                          Page 13 of 100
information; performance record of Contract performance; etc.      Failure to promptly provide this
information shall result in proposal rejection.

Agency may postpone the award of the Price Agreement after announcement of the apparent successful
Proposer in order to complete its investigation and evaluation. Failure of the apparent successful
Proposer to demonstrate Responsibility, as required under OAR 125-247-0500, shall render the Proposer
non-responsible and constitute grounds for offer rejection, as required under ORS 297B.10




                                                                            Page 14 of 100
                                                  Attachment A
                                              Sample Price Agreement
               INFORMATION TECHNOLOGY PRODUCTS AND SERVICES PRICE AGREEMENT
                                 (Software and related Services)

       This Information Technology Products and Services Price Agreement (this “PA”) is entered into on the date of execution by
and between the State of Oregon acting by and through its Department of Transportation (“Agency”), and _________ a
_________________corporation (“Contractor”).



RECITALS

A.      Agency desires to engage a Contractor to provide Products and Services to enable Agency to achieve specific business and
Agency mission objectives defined in this Price Agreement and any fully executed Work Order Contracts. To that end, Agency issued
RFP # 730-24226-10_(defined below) .

B.      Contractor is the successful Proposer to the RFP # 730-24226-10 and Agency desires to engage the Contractor to deliver the
Products and perform the Services.

C.       Contractor desires to deliver the Products to and perform the Services for the Agency as more fully described in a Work Order
Contract.

AGREEMENT

In consideration of the foregoing recitals and the mutual terms and conditions set forth below, Agency and Contractor agree as follows:


1.   DEFINITIONS GOVERNING THIS PA AND ANY WORK ORDER CONTRACT. Additional definitions may be included in an
     individual WOC that are of specific import to that WOC.

“Acceptance” means written confirmation by Agency that Contractor has completed a Deliverable according to the Acceptance Criteria
and accepted for purposes of interim payment. The term is distinct from “Final Acceptance”.

“Acceptance Criteria” means the criteria for accepting Deliverables required by this PA and any WOC, including but not limited to all
specifications and requirements in the Statement of Work, and the Performance Warranties set forth in Article 8.2

”Acceptance Tests" means those tests which are intended to determine compliance of Products and Services with the Acceptance
Criteria of this PA and any WOC.

“Change Order” means a written change agreed to by both parties that makes minimal adjustments to the Statement of Work
Deliverable due dates, fixed costs or Deliverables.

“Agency Intellectual Property” means any intellectual property that is owned by Agency. Agency Intellectual Property includes any
derivative works and compilations of any Agency Intellectual Property.
“Application” means a business system (group of software programs) which aids users in the performance of business tasks, activities,
and functions in support of Agency's mission. Application programs are distinguished from system programs, which control the
computer and run the application programs and utilities.

“Authorized Representative” means a person representing a party to the Contract who is authorized to make commitments and
decisions on behalf of the party regarding the performance of the Contract. Contractor’s Authorized Representative is the person so
identified in Exhibit D. Agency’s Authorized Representative is the person so identified in Exhibit D.

“Change Order” means a form of Contract amendment pursuant to Article 17 that makes changes or modifications to the Statement of
Work within the Scope of this PA or any WOC.

“Confidential Information” is defined in Section 7.1.

“Contract” means the agreement between parties resulting from this Price Agreement including all terms and conditions in this PA, and
all Exhibits attached hereto including a fully executed Work Order Contract Forms



                                                                                                           Page 15 of 100
“Contractor Intellectual Property” means any intellectual property that is owned by Contractor and contained in or necessary for the use,
or optimal use, of the Deliverables. Contractor Intellectual Property includes Documentation, Work Product, and derivative works and
compilations of any Contractor Intellectual Property. Contractor Intellectual Property does not include COTS Software.

“Deliverables” means the Services and all Products that Contractor is required to deliver to Agency under this PA and any WOC,
including Work Product.

“Delivery Schedule” means that attribute of the Statement of Work setting forth the completion date of each Milestone and the delivery
date for each Deliverable.

“Documentation” means all documents, including documents that are Deliverables described in the Statement of Work and includes, but
is not limited to, any and all operator’s and user’s manuals, training materials, guides, commentary, listings, requirements traceability
matrices and other materials for use in conjunction with and for the operation of Products and Services that are to be delivered by
Contractor under the Contract.

“DOJ” means the State of Oregon acting through its Department of Justice.

“Effective Date” means the date on which this PA and any WOC is fully executed and approved in according to applicable laws, rules
and regulations.

“Final Acceptance” is defined in Section 2.3.

“Hardware” means the information technology equipment and related goods identified in Exhibit A, and all related Documentation, that
the Contractor will deliver to Agency pursuant to this Contract


“Intellectual Property Rights” is defined in Section 6.

“Key Persons” means Contractor’s Authorized Representative, the Project Manager and all other Contractor personnel designated as
key persons in each WOC.

“Maximum Not-To-Exceed Compensation” is defined in Section 5.1. and will be specific to any executed WOC.

“Milestone” means a specific group of Tasks or Deliverables identified as a Milestone in the Statement of Work of a WOC.

“Project Manager” means Contractor’s representative who manages the processes and coordinates the Services with Agency’s
Authorized Representative (as identified in each WOC) to ensure delivery of the Product or Service. Contractor’s Project Manager is the
person so identified in each WOC.

“Proposal” means Contractor’s proposal in response to the RFP.

“RFP” means the Request for Proposal # 730-24226-10.

“Products” means the information technology Hardware and Software identified in Exhibit A, and all related Documentation, that the
Contractor will deliver to Agency.

“Products and Services” means the sum total of all Deliverables (excluding ongoing Warranty Maintenance and Support) including
Hardware, Software and Services that Contractor is to deliver to Agency under this Contract for Acceptance Testing.

“Schedule of Deliverables” means that attribute of the SOW that describes each Deliverable, measurable attributes of each Deliverable,
Milestones with identification of the Services activities that are associated with them and a planned completion date for each Milestone
and Deliverable as defined in each WOC.

"Services Retention Amount" is defined in Section 5.3.1

“Services” means all effort to be expended by Contractor as set forth in the Statement of Work and the Maintenance and Support
Agreement for each WOC, including but not limited to delivery, installation, configuration, implementation (collectively “installation”),
warranty, maintenance and support of the Products.

“Software” means an all-inclusive term which refers to any computer programs, routines, or subroutines supplied by the Contractor,
including Operating Software, Programming Aids, Application Programs, and Application Programming Interfaces.

”Software Retention Amount” is defined in Section 5.3.2.

“Statement of Work” means the means a document that describes each Task, Deliverable and Milestone, the measurable attributes of
each Deliverable, identification of the Deliverables and Services that are associated with each Task, and a completion date for each
Milestone and Deliverable, the Payment Schedule for each Deliverable and Milestone, and any other items as agreed by the parties
including Amendments pursuant to section 17.15, all to be included in each WOC.
                                                                                                            Page 16 of 100
“Task” means a segment of the Services to be provided by Contractor under any fully executed WOC.

““Third Party Intellectual Property” means any intellectual property owned by parties other than Agency or Contractor and contained in
or necessary for the use, of the Deliverables. Third Party Intellectual Property includes COTS Software owned by Third Parties, and
derivative works and compilations of any Third Party Intellectual Property.

"Third Party Products” includes Software not published by Contractor or Agency and which are supplied by Contractor to Agency under
this PA and any WOC.

“Warranty Period” means the period that begins on the date the Products are delivered, and ends ____________________.

“Work Product” means every invention, modification, discovery, design, development, customization, configuration, improvement,
process, software program, work of authorship, documentation, formula, datum, technique, know-how, secret, or intellectual property
right whatsoever or any interest therein (whether patentable or not patentable or registerable under copyright or similar statutes or
subject to analogous protection) that is specifically made, conceived, discovered, or reduced to practice by Contractor or Contractor’s
subcontractors or agents (either alone or with others) pursuant to the Contract. Notwithstanding anything in the immediately preceding
sentence to the contrary, Work Product does not include any Agency Intellectual Property, Contractor Intellectual Property or Third
Party Intellectual Property.

“Work Order Contract” (WOC) means the document substantially in the format included in this PA as Exhibit E that includes the
Statement of Work including all Products and Services the Agency is ordering from this Price Agreement and incorporates by reference
all terms and conditions of this Price Agreement. The Price Agreement together with the Work Order Contract (WOC) constitutes the
Contract.

2.   PRODUCTS AND SERVICES.

     2.1. PERFORMANCE AND DELIVERY.

         2.1.1. Contractor shall deliver the Products and provide the Services to Agency according to this PA including the Statement of
                Work contained in any WOC.

         2.1.2. All Products to be supplied by Contractor will be the most recent version at the time of delivery and remain so through
                the Warranty period unless expressly authorized by Agency.

         2.1.3. Contractor shall deliver the Products to the Agency F.O.B. to the destination specified in the WOC according to the
                Delivery Schedule set forth in the WOC. During the period that Products are in transit, and until the time that the
                Products are tendered to enable the Agency to take delivery of the Products, Contractor and its insurers, if any, relieve
                the Agency and the State of Oregon of the responsibility for all risk of loss of, or damage to, the Products. Thereafter, all
                risk of loss of, or damage to, the Products shall be borne by the Agency.

         2.1.4. Contractor shall have all publisher warranties covering the Products transferred to the Agency at time of delivery at no
                additional charge. Contractor shall also furnish to the Agency the details of the third party publisher warranties.

     2.2. If any WOC requires Agency to provide any resources, and Agency fails to provide the requisite quality or quantity of such
          resources, or fails to provide such resources in a timely manner but for a period not to exceed 30 days, Contractor's sole
          remedy shall be an extension of the applicable delivery dates corresponding to the delay caused by Agency's failure. If
          Agency's failure to provide such resources exceeds 30 days and Contractor can show to the reasonable satisfaction of
          Agency, that the Agency's failure has resulted in an unavoidable increase in the cost of the Services required for the
          Statement of Work then Contractor shall be entitled to recover from Agency the reasonable amount of such increased costs.
          Contractor's right to delay applicable delivery dates may be exercised only if Contractor provides Agency with reasonable
          notice of Agency's failure and Contractor uses Commercially Reasonable Efforts to perform notwithstanding Agency's failure
          to perform.

     2.3. REVIEW OF PRODUCTS ANDSERVICES / FINAL ACCEPTANCE

         2.3.1. Contractor shall deliver Deliverables and complete Milestones as set forth in the WOC Statement of Work by no later
                than the date or dates set for delivery in the WOC Statement of Work. Delivery dates, both critical and non-critical, are
                set forth in the WOC Statement of Work and are subject to Agency performing its responsibilities in a timely manner.

         2.3.2. For Deliverables that do not require Acceptance Testing, Contractor shall provide written notice to Agency upon delivery
                of a completed Deliverable to Agency. By no later than (i) 10 days after receipt of such notice, or (ii) the date set forth in
                the Delivery Schedule for Agency’s review, Agency shall determine whether the Deliverable meets Acceptance Criteria
                set forth in the Contract including the Statement of Work. If Agency determines that the Deliverable meets in all material
                respects the Acceptance Criteria, Agency shall within such 10 days issue a written Notice of Acceptance. If the Agency
                determines that a Deliverable does not meet the Acceptance Criteria, the parties shall proceed under section 2.3.4. With
                respect to any Deliverables that are subject to Acceptance Testing by the SOW Agency shall conduct Acceptance
                Testing as set forth in Section 2.3.3. and the SOW.
                                                                                                                Page 17 of 100
         2.3.3. FINAL ACCEPTANCE TESTING. Contractor shall provide written notice to the Agency upon full and complete installation,
                configuration and implementation of the Products and Services as required by the WOC SOW. Within 90 State of Oregon
                business days after receipt of such notice, Agency shall conduct such Acceptance Testing as set forth in the SOW. If the
                Acceptance Tests establish that Products and Services conform in all material respects to the Acceptance Criteria Agency
                shall issue a written notice of Acceptance to Contractor, and “Final Acceptance” shall be deemed to have occurred, If
                the Products and Services fail to meet the Acceptance Criteria, the parties shall proceed under section 2.3.4

         2.3.4. If the Agency determines that a Deliverable or the Products and Service after Acceptance Testing do not meet in all
                material respects the Acceptance Criteria, Agency shall notify Contractor in writing of Agency’s rejection of the
                Deliverable or Products and Services, and describe in reasonable detail in such notice the Agency’s basis for rejection
                of the Products and Services. Upon receipt of notice of non-acceptance, Contractor shall, within a period designated in
                each WOC, modify or improve the Deliverable or Products and Services at Contractor’s sole expense so that the
                Deliverable or Products and Services meets, in all material respects the Acceptance Criteria, and notify the Agency in
                writing that it has completed such modifications or improvements and re-tender the Deliverable or Products and
                Services to Agency. Agency shall thereafter review the modified or improved Deliverable or Products and Services
                within 30-days of receipt of the Contractor's delivery of the Products and Services. Failure of the Products and Services
                to meet in all material respects, the Acceptance Criteria after the second set of Acceptance Tests shall constitute a
                default by Contractor. In the event of such default, Agency may either (i) notify Contractor of such default and instruct
                Contractor to modify or improve the Products and Services as set forth in this section 2.3.3, or (ii) notify Contractor of
                such default and in which case Contractor shall comply with section 2.4

     2.4. REMOVAL/REIMBURSEMENT: If the Products or Services are rejected or acceptance is revoked, at the option of the
          Agency, the Contractor shall refund any Contract payments that have been made with regard to the Products or Services,
          and shall (at Contractor's sole cost and expense) remove the Products within 7 calendar days of receiving notice of rejection
          or revocation of acceptance

     2.5. REMEDIES NOT EXCLUSIVE No provision of this Article 2 precludes Agency from other remedies to which it may be entitled
          upon rejection or revocation of acceptance.

     2.6. Warranty Period/ Post Warranty Maintenance and Support.
         2.6.1. During the Warranty Period, Contractor shall, at no additional charge to Agency, (1) furnish such materials and Services
                as shall be necessary to correct any defects in the Products and Services and maintain the Products in good working
                order according to the Warranties and Acceptance Criteria provided in the PA or any WOC (2) Contractor shall provide
                maintenance and support of the Products and Services consistent with the Contractor’s obligations of Post Warranty
                Maintenance and Support as set forth in the WOC. Notwithstanding the expiration of the Warranty Period, Contractor
                shall be obligated to cure defects discovered during the Warranty Period that prevent the Products and Services from
                meeting the Acceptance Criteria and Warranties of this PA or any WOC.
         2.6.2. Post Warranty Maintenance and Support. Contractor shall provide post Warranty Maintenance and Support of the
                Products in accord with Maintenance and Support Agreement attached hereto or as described in any WOC.

3.   CONTRACTOR’S PERSONNEL.

     3.1. Project Manager. Contractor shall designate one of the Key Persons as Project Manager for the Services. The Project
          Manager shall be familiar with Agency’s business operations and objectives as necessary for the successful completion of the
          WOC. The Project Manager shall participate with Agency in periodic review sessions and shall provide at Agency’s request
          detailed progress reports that identify completed tasks and the status of the remaining Services as set forth in the WOC
          Statement of Work.

     3.2. Contractor’s Employees and Subcontractors. Contractor shall not use subcontractors to perform the Services unless
          specifically authorized to do so by Agency. Contractor represents that any employees assigned to perform the Services, and
          any authorized subcontractors performing the Services shall perform the Services according to the warranties set forth in
          Article 8 of this PA and a WOC.

     3.3. Key Persons. Contractor acknowledges and agrees that Agency selected Contractor, and is entering into a WOC because of
          the special qualifications of Contractor's Key Persons identified in the WOC. Contractor's Key Persons shall not delegate
          performance of their powers and responsibilities they are required to provide under the WOC to another Contractor
          employee(s) without first obtaining the written consent of the Agency. Further, Contractor shall not re-assign or transfer the
          Key Persons to other duties or positions such that the Key Persons are no longer available to provide the Agency with their
          expertise, experience, judgment, and personal attention, without first obtaining the Agency's prior written consent to such re-
          assignment or transfer, which Agency shall not unreasonably withhold or delay. Notwithstanding the foregoing, Contractor
          may replace Key Persons without Agency’s consent in the event any Key Person is no longer available due to death, illness
          or termination of employment with Contractor. In the event Contractor requests that the Agency approve a re-assignment or
          transfer of the Key Persons, or if Contractor must replace a Key Person due to death, illness or termination of employment
          with the Contractor, the Agency shall have the right to interview, review the qualifications of, and approve or disapprove the
          proposed replacement(s) for the Key Person. Any such replacement shall have substantially equivalent or better qualifications

                                                                                                             Page 18 of 100
            than the Key Person being replaced Any replacement personnel approved by Agency shall thereafter be deemed a Key
            Person for purposes of the WOC and the WOC shall be deemed amended to include such Key Person.

4.   TERM. This PA shall be effective on the Effective Date, and shall expire 10 years from execution date. A WOC shall be effective
     on the Effective date as noted in the WOC and shall expire on the expiration of any Warranty period or the expiration date
     described in the WOC whichever is later. Notwithstanding the foregoing, the term for any License Agreement, Maintenance and
     Support Agreements attached to the Price Agreement shall be as specified in those agreements.

5.   COMPENSATION.

     5.1.   Maximum Payment Amount. Notwithstanding any other provision of this PA or any WOC to the contrary, the maximum, not-to-
            exceed compensation that Agency will pay to Contractor is noted in each WOC as the “Maximum Not-To-Exceed
            Compensation”, which includes payment for any allowable expenses for which Contractor may request reimbursement under
            any WOC.

     5.2. Payments.

            5.2.1. Payment for Services. Subject to the requirements of Sections 5.3 and 5.5 Agency shall pay Contractor for each
                   Deliverable delivered pursuant to the WOC Statement of Work and accepted by Agency the price for that Deliverable set
                   forth in the WOC Statement of Work.

            5.2.2. Maintenance / Support Services. Subject to sections 5.5 and 5.6, No later than 30 days prior to the expiration of the
                   Warranty Period, Contractor shall invoice Agency for the annual fees for Maintenance and Support. Thereafter, Contractor
                   shall no later than 30 days from the expiration of any Maintenance or Support period invoice Agency for the next period of
                   Maintenance and Support in accord with the pricing set forth in the WOC.

            5.2.3. Payment for COTS Software. Subject to Sections 5.3 and 5.5, Agency shall pay Contractor for COTS Software delivered
                   under any WOC upon Agency’s acceptance of the COTS Software/Final Acceptance, in the amount set forth in the WOC
                   Statement of Work for the COTS Software.

            5.2.4. Payment for Hardware. Subject to Sections 5.3 and 5.5, Agency shall pay Contractor for Hardware delivered under this
                   Contract upon [Agency’s acceptance of the Hardware /Final Acceptance], in the amount set forth in the Statement of Work
                   for the Hardware.


     5.3.    Retention Amount.

            5.3.1. Retention Amount for Services. Agency shall in all events be permitted to hold back an amount (the "Services Retention
                   Amount") of not more than ten percent (10%) of any amount that is payable by Agency to Contractor, other than amounts
                   attributable to the purchase licenses of COTS Software, if any. Agency shall pay the then accrued Services Retention
                   Amount to Contractor within thirty (30) days following Final Acceptance.

            5.3.2. Retention Amount for Products. Agency shall in all events be permitted to hold back an amount (the “Products Retention
                   Amount”) of not more than ten percent (10%) of any amount payable to Contractor pursuant to Section 5.2 for Products.
                   Agency shall pay the accrued Products Retention Amount for the applicable Product within 30 days of Agency’s Final
                   Acceptance of the Product according to Acceptance Criteria and processes set forth in this PA and any WOC.

     5.4. Expenses. Agency will not pay or reimburse any expenses incurred by Contractor during the completion of the Service except as
          authorized in the WOC Statement Work Any such authorized expenses shall comply with Oregon Travel Policy.

     5.5. Invoices. Agency shall pay Contractor not more than once each month upon Contractor’s submission of detailed invoices that set
          forth the Products and Services accepted by Agency. Such invoices shall comply with the requirements of Sections 5.2, 5.3, and
          5.4 and shall identify the Products Delivered and the Services completed and Accepted by Agency for which Contractor seeks
          compensation and shall itemize and explain all authorized expenses for which reimbursement is claimed. Contractor shall
          request payment only for Deliverables accepted by Agency. The invoices also shall include the total amount invoiced to date by
          Contractor prior to the current invoice. Contractor shall submit invoices to Agency’s Authorized Representative. Agency will have
          the right to review each such invoice for compliance with the requirements of this Section 5.5 and any other relevant provisions
          of this PA and WOC. All payments to Contractor are subject to ORS 293.462

     5.6. Limit on Payments. Contractor shall not submit invoices for, and Agency shall not pay, any amount in excess of the Maximum
          Not-To-Exceed Compensation set forth in a WOC. If this maximum amount is increased by amendment of the WOC, pursuant to
          Section 17.15, the amendment must be fully effective before Contractor performs Services or delivers goods subject to the
          amendment. No payment will be made for any Services performed or Products delivered before the Effective Date of this PA or
          any WOC or after termination of the WOC.

     5.7. Subject to any retention amounts, Authorized Purchaser will compensate Contractor for accepted Products or Services, or both,
          based upon the applicable prices and rates as reflected this Price Agreement, the Products and Prices List. The Products and
          Prices List is comprised of Product and Services line items, maximum hourly rates, guaranteed minimum discounts, and
                                                                                                                Page 19 of 100
            discounted prices. Authorized Purchaser may compensate Contractor on a deliverables based payment schedule. Authorized
            Purchaser may receive discounted hourly rates below the maximum hourly rates. Agency and Contractor may periodically adjust
            prices and rates according to Section 5.8.


     5.8. Price Increases. If allowed by Agency, the billing rates, product costs and maintenance and support costs established in this
          Price Agreement may be amended at the annual anniversary of execution of this Price Agreement. Contractor shall provide new
          proposed rates or costs, justification for the increase or decrease no less than 30 calendar days before the annual anniversary
          date of execution of this Price Agreement. The increase rate shall not exceed 3% or the Portland – Salem, OR-WA Consumer
          Price Index –U (as reported by the Oregon Economic and Community Development Department at
          http://www.econ.state.or.us/cpi.htm) CPI which ever is less.

     5.9    PRICE GUARANTEE. Contractor warrants that it shall use its best efforts to extend best available pricing to the State of
            Oregon for the Products and Services covered by this Agreement, as compared to Contractor’s other customers who provide
            Contractor with comparable potential for business volume for like Products and Services implicated under this Agreement,
            subject to any of Contractor’s pricing obligations under its established state government programs, if any, and to the federal
            government. Contractor will utilize all accessible and applicable business partner programs and pricing mechanisms in order
            to optimize pricing and terms on behalf of the State, including without limitation other pricing methods sanctioned by
            Contractor for the benefit of its state government clients, e.g., the Western States Contracting Alliance (WSCA).

6.   OWNERSHIP AND LICENSE IN PRODUCT OR SERVICES.

     6.1. Contractor retains ownership of all Contractor Intellectual Property that Contractor delivers to Agency pursuant to a WOC.
          Contractor grants Agency a license to Contractor Intellectual Property as set forth in Exhibit G.

     6.2. Work Product. Contractor owns all Work Product. Contractor grants Agency a non-exclusive, irrevocable, royalty-free, world-
          wide license to use, copy, display, distribute, transmit and prepare derivative works of Work Product, and to authorize others
          to do the same on Agency’s behalf.

     6.3. Third Party Intellectual Property. Unless otherwise specified in the WOC that Agency, on its own, will acquire and obtain a
          license to Third Party Intellectual Property, Contractor shall secure on Agency’s behalf, in the name of Agency and subject to
          Agency’s approval, a license to Third Party Intellectual Property sufficient to fulfill the business objectives, requirements and
          specifications identified in the WOC.

     6.4.    Agency Intellectual Property; Data and Background Information. Agency owns all Agency Intellectual Property and Agency
            data and background information provided to Contractor pursuant to this PA and any WOC. Agency grants Contractor a non-
            exclusive, royalty-free, world-wide license to use, copy, display, distribute, transmit and prepare derivative works of Agency
            Intellectual Property and Agency data and background information only to fulfill the purposes of this PA and any WOC.
            Agency’s license to Contractor is limited by the term of the WOC and the confidentiality obligations of this PA.

     6.5. No Rights. Except as expressly set forth in this PA, nothing in this PA or any WOC shall be construed as granting to or
          conferring upon Contractor any right, title, or interest in any intellectual property that is now owned or subsequently owned by
          Agency. Except as expressly set forth in this PA or any WOC, nothing in this PA or any WOC shall be construed as granting
          to or conferring upon Agency any right, title, or interest in any Contractor Intellectual Property that is now owned or
          subsequently owned by Contractor.

     6.6. Competing Services. Subject to the provisions of this Article 6, and Contractor’s obligations with respect to Confidential
          Information, as defined in Article 7 nothing in this Pa or any WOC shall preclude or limit in any way the right of Contractor to:
          (i) provide the services similar to those contemplated in this PA or any WOC, or, consulting or other services of any kind or
          nature whatsoever to any individual or entity as Contractor in its sole discretion deems appropriate, or (ii) develop for
          Contractor or for others, deliverables or other materials that are competitive with those produced as a result of the Services
          provided hereunder, irrespective of their similarity to the Deliverables Each party shall be free to utilize any concepts,
          processes, know-how, techniques, improvements or other methods it may develop during the course of performance under
          this PA or any WOC free of any use restriction or payment obligation to the other.

     6.7. Neither party grants the other the right to use its trademarks, trade names, servicemarks or other designations in any
          promotion or publication without prior written consent. Each party grants only the licenses and rights specified in this PA.

     6.8. SOFTWARE ESCROW

            6.8.1. Within thirty (30) days of execution of this Contract, Contractor shall propose to Agency a mutually agreeable,
                   commercially reasonable arrangement to escrow:

                6.8.1.1. The source code for the Products, including Contractor Intellectual Property and Third Party Intellectual Property
                         in such format that will allow Agency to build and compile useful object code;

                6.8.1.2. Any and all updates, modifications, revisions, and enhancements of the System Software;

                                                                                                                Page 20 of 100
              6.8.1.3. Any and all Documentation pertaining to source code for the Products, including the technical specifications and
                       documents, data conversion guidelines and instructional tools (collectively, all items identified in subsections A
                       through C shall be referred to as “Deposited Programs”).

         6.8.2. Upon the Parties’ acceptance and written approval of such proposed escrow arrangement and its approval by DAS and
                DOJ if required, Contractor and Agency shall promptly execute a three party escrow agreement with the selected
                escrow agent which shall govern the terms of the escrow arrangement. The escrow agreement shall authorize the
                escrow agent to release the Deposited Programs to Agency upon the occurrence of any of the following:

              6.8.2.1. Source code for any or all material part of the Deposited Programs is generally made publicly available by
                       Contractor, with or without additional cost, to other users of comparable software; or

              6.8.2.2. The Contractor's cessation, for any reason, to do business; or

              6.8.2.3. The Contractor discontinues offering maintenance and support services for the Deposited Programs; or

              6.8.2.4. The Contractor institutes or has instituted against it insolvency, receivership or bankruptcy proceedings, or makes
                       an assignment for the benefit of creditors, and same has not been discharged or terminated without any prejudice
                       to Agency’ rights or interests under this Contract within thirty (30) days; or

              6.8.2.5. Any other event or circumstance occurs that demonstrates with reasonable certainty the inability or unwillingness
                       of Contractor to fulfill its obligations to Agency under this Contract, the escrow agreement or any maintenance or
                       support agreement between the parties.

         6.8.3. Agency shall pay the fees of the escrow agent. The copies of the Deposited Programs placed in escrow shall be
                reproduced and maintained on magnetic tape or disk using a commonly accepted data recording protocol. When a
                change is made to the Deposited Programs by or on behalf of the Contractor, during the term of the escrow agreement,
                the revised Deposited Programs, including the change, shall be delivered to the escrow agent not later than sixty (60)
                days after the change is effected by or on behalf of the Contractor. Contractor shall allow Agency to periodically
                examine the escrowed source code for the Deposited Programs to verify it is current and complete;

         6.8.4. Upon receipt of the Deposited Programs by Agency pursuant to the escrow agreement entered into under this Section
                6.8, Agency shall treat the Deposited Programs as confidential information to the fullest extent authorized by the Oregon
                Public Records Law. Notwithstanding such delivery to Agency, the Deposited Programs shall remain the property of
                Contractor or its successor, unless ownership is specifically transferred to Agency by Contractor or its authorized agent.
                Upon release of the Deposited Programs as provided for herein, Agency and its consultants and contractors, shall have
                a perpetual, irrevocable license to use, reproduce, prepare derivative works based on, perform and display the
                Deposited Programs in conjunction with and to update, modify and otherwise support the System.

7.   CONFIDENTIALITY AND NON-DISCLOSURE.

     7.1. CONFIDENTIAL INFORMATION. Contractor acknowledges that it and its employees or agents may, in the course of
          performing their responsibilities under this PA or any WOC, be exposed to or acquire information that is confidential to
          Agency or Agency’s clients. Any and all information of any form obtained by Contractor or its employees or agents in the
          performance of a WOC shall be deemed to be confidential information of Agency (“Confidential Information”). Any reports or
          other documents or items (including software) that result from the use of the Confidential Information by Contractor shall be
          treated with respect to confidentiality in the same manner as the Confidential Information. Confidential Information shall be
          deemed not to include information that (a) is or becomes (other than by disclosure by Contractor) publicly known; (b) is
          furnished by Agency to others without restrictions similar to those imposed by this PA; (c) is rightfully in Contractor’s
          possession without the obligation of nondisclosure prior to the time of its disclosure under this PA; (d) is obtained from a
          source other than Agency without the obligation of confidentiality, (e) is disclosed with the written consent of Agency, or; (f) is
          independently developed by employees, agents or subcontractors of Contractor who can be shown to have had no access to
          the Confidential Information.

     7.2. NON-DISCLOSURE. Contractor agrees to hold Confidential Information in confidence, using at least the same degree of care
          that Contractor uses in maintaining the confidentiality of its own confidential information, and not to copy, reproduce, sell,
          assign, license, market, transfer or otherwise dispose of, give, or disclose Confidential Information to third parties (other than
          its subcontractors, or use Confidential Information for any purposes whatsoever other than the provision of Services to
          Agency hereunder, and to advise each of its employees and agents of their obligations to keep Confidential Information
          confidential. Contractor shall use commercially reasonable efforts to assist Agency in identifying and preventing any
          unauthorized use or disclosure of any Confidential Information. Without limiting the generality of the foregoing, Contractor
          shall advise Agency immediately in the event Contractor learns or has reason to believe that any person who has had access
          to Confidential Information has violated or intends to violate the terms of this PA and any WOC and Contractor will at its
          expense cooperate with Agency in seeking injunctive or other equitable relief in the name of Agency or Contractor against
          any such person. Contractor agrees that, except as directed by Agency, Contractor will not at any time during or after the
          term of this PA disclose, directly or indirectly, any Confidential Information to any person, except according to this PA, and
          that upon termination of this PA or at Agency’s request, Contractor will turn over to Agency all documents, papers, and other
          matter in Contractor's possession that embody Confidential Information. Notwithstanding the foregoing, Contractor may keep
                                                                                                               Page 21 of 100
          one copy of such Confidential Information necessary for quality Assurance, audits and evidence of performance of the
          Services.

     7.3. Identity Theft. In the performance of the PA or WOC, Contractor may have possession or access to documents, records or
          items that contain “Personal Information” as that term is used in ORS 646A.602(11), including Social Security numbers.
          Personal Information is a type of Confidential Information that is highly sensitive and subject to additional protection.
          Therefore, prior to the receipt of, and during the period in which Contractor has possession of or access to, any Personal
          Information, Contractor shall have in place, a formal written information security program that provides safeguards to protect
          Personal Information from loss, theft, and disclosure to unauthorized persons, as required by the Oregon Consumer Identity
          Theft Protection Act, ORS 646A.600-646A.628.

         7.3.1. Contractor shall not breach or permit breach of the security of any Personal Information that is contained in any
                document, record, compilation of information or other item to which Contractor receives access, possession, custody or
                control under this PA or WOC. Contractor shall not disclose, or otherwise permit access of any nature, to any
                unauthorized person, of any such Personal Information. Contractor shall not use, distribute or dispose of any Personal
                Information other than expressly permitted by the Agency, required by applicable law, or required by an order of a
                tribunal having competent jurisdiction.

         7.3.2. Contractor shall promptly report to the Agency, as promptly as possible, any breach of security, use, disclosure, theft,
                loss, or other unauthorized access of any document, record, compilation of information or other item that contains
                Personal Information to which the Contractor receives access, possession, custody or control in the performance of this
                PA or any WOC.

         7.3.3. Contractor shall require its employees and agents to comply with this section.

     7.4. Security Policies / Non Disclosure Agreement Contractor at all times shall comply with Agency’s security policies as made
          available to Contractor. Contractor shall upon Agency’s request provide a written non disclosure agreement and obtain such
          from Contractor’s employees or subcontractors performing Services under this PA or any WOC including the Maintenance
          and Support Agreement included in any WOC.

     7.5. Injunctive Relief. Contractor acknowledges that breach of this Article 7, including disclosure of any Confidential Information,
          will cause irreparable injury to Agency that is inadequately compensable in damages. Accordingly, Agency may seek and
          obtain injunctive relief against the breach or threatened breach of the foregoing undertakings, in addition to any other legal
          remedies that may be available. Contractor acknowledges and agrees that the covenants contained herein are necessary for
          the protection of the legitimate business interests of Agency and are reasonable in scope and content.

     7.6. Publicity. Contractor agrees that news releases and other publicity relating to the subject of this PA or any WOC will be made
          only with the prior written consent of Agency.

8.   CONTRACTOR’S REPRESENTATIONS AND WARRANTIES.

     8.1. GENERAL REPRESENTATIONS AND WARRANTIES. In addition to all other Contractor representations and warranties in
          this PA or any WOC, Contractor also represents and warrants to Agency that:

         8.1.1. Contractor has the power and authority to enter into and perform this PA and any WOC;

         8.1.2. This PA and any WOC, when executed and delivered, will be a valid and binding obligation of Contractor enforceable
                according to its terms;

         8.1.3. Contractor will, at all times during the term of the PA and any WOC, be qualified to do business in the State of Oregon,
                professionally competent and duly licensed to perform the Services;

         8.1.4. Contractor is not in violation of, charged with nor, to the best of Contractor’s knowledge, under any investigation with
                respect to violation of, any provision of any federal, state or local law, ordinance or regulation or any other requirement
                or order of any governmental or regulatory body or court or arbitrator applicable to provision of the Services, and
                Contractor’s provision of the Services shall not violate any such law, ordinance, regulation or order.

         8.1.5. Contractor’s performance under this PA and any WOC to the best of Contractor’s knowledge creates no potential or
                actual conflict of interest, as defined by ORS 244, for either Contractor or any Contractor personnel that will perform the
                Services under a WOC.

         8.1.6. The Contractor Data and Tax Certification in this PA and the Certification Statement For Independent Contractor in the
                form attached hereto as Exhibit C, if applicable, are true and accurate as of the Effective Date, and Contractor will notify
                Agency in writing if any such data or certifications change during the term of this Contract such that the attached Exhibit
                C, if applicable, are no longer true and accurate.

     8.2. CONTRACTOR’S PERFORMANCE WARRANTIES. Contractor represents and warrants to Agency that:

                                                                                                              Page 22 of 100
         8.2.1. Contractor has the skill and knowledge possessed by well-informed members of its trade or profession and Contractor
                will apply that skill and knowledge with care and diligence so Contractor and Contractor’s employees and any authorized
                subcontractors perform the Services described in a WOC according to the highest standards prevalent in the industry or
                business most closely involved in providing the Products or Services that Contractor is providing to Agency pursuant to
                this PA and any WOC.

         8.2.2. Through the expiration of the Warranty Period, all Product and Services delivered by Contractor to Agency shall
                materially conform to the Acceptance Criteria set forth in this PA and any WOC, including the Statement of Work and
                any Documentation provided by Contractor and shall be free from error or defect that materially impairs their use, and
                shall be free from defects in materials, workmanship and design.

         8.2.3. Except as otherwise permitted or provided in this PA or any WOC including as provided in Article 6, all Products or
                Services supplied by Contractor to Agency shall be transferred to Agency free and clear of any and all restrictions on or
                conditions of transfer, modification, licensing, sublicensing, direct or indirect distribution, or assignment, and free and
                clear of any and all liens, claims, mortgages, security interests, liabilities, and encumbrances of any kind.

         8.2.4. Except as otherwise set forth in this PA and any WOC, any subcontractors performing work for Contractor under a WOC
                have assigned all of their rights in the Product or Services to Contractor or Agency and no third party has any right, title
                or interest in any Product or Services supplied to Agency under this PA and any WOC.

         8.2.5. Contractor represent and warrants that it will maintain, operate and enforce, prior to the receipt of, and during the period
                in which Contractor has possession of or access to, any Personal Information, an active and effective information
                security program to preserve the security and confidentiality of all Personal Information that is contained in any
                document, record, compilation of information or other item to which Contractor receives access, possession, custody or
                control.

         8.2.6. The Contractor represents and warrants that, at the time of delivery and installation of the Products provided pursuant to
                this PA or any WOC, those Products shall be free of what are commonly defined as viruses, backdoors, worms,
                spyware, malware and other malicious code that will hamper performance of the software, collect unlawful personally
                identifiable information on users, or prevent the software from performing as required under the terms and conditions of
                this PA and any WOC. Notwithstanding the foregoing, this representation and warranty does not include a disabling
                device that limits, suspends or ends use of the Software expressly permitted by the terms and conditions by the license
                under which it was provided.

     8.3. WARRANTIES EXCLUSIVE; DISCLAIMERS. THE WARRANTIES SET FORTH IN THIS PA ARE EXCLUSIVE AND IN LIEU
          OF ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, AND CONTRACTOR EXPRESSLY DISCLAIMS ALL
          OTHER WARRANTIES, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A
          PARTICULAR PURPOSE. CONTRACTOR DOES NOT WARRANT THAT THE AGENCY’ S USE OF THE PRODUCTS WILL
          BE UNINTERRUPTED OR ERROR FREE.

     8.4. The warranties stated above will not apply to the extent that there has been misuse (including, but not limited to, any use of
          the Products capacity or capability, other than that authorized by Contractor in writing), accident, modification, unsuitable
          physical or operating environment, operation in other than the specified operating environment, improper maintenance by
          Agency or a third party, or failure or damage caused by a product for which Contractor is not responsible

9.   LIMITATION OF LIABILITY.

     9.1. EXCEPT FOR LIABILITY ARISING OUT OF OR RELATED TO (i) SECTION 10.1, (ii) SECTION 10.2, (iii) ARTICLE 7 OR (iv)
          CLAIMS FOR PERSONAL INJURY, INCLUDING DEATH, OR DAMAGE TO REAL PROPERTY OR TANGIBLE PERSONAL
          PROPERTY ARISING FROM THE NEGLIGENCE, RECKLESS CONDUCT OR INTENTIONAL ACTS OF CONTRACTOR,
          ITS OFFICERS, EMPLOYEES OR AGENTS, CONTRACTOR'S LIABILITY FOR DAMAGES TO THE STATE FOR ANY
          CAUSE WHATSOEVER SHALL BE LIMITED TO THE MAXIMUM-NOT-TO-EXCEED AMOUNT OF THE WOC.

     9.2. EXCEPT FOR LIABILITY TO THIRD PERSONS ARISING OUT OF OR RELATED TO (i) SECTION 10.1, (ii) SECTION 10.2,
           (iii) ARTICLE 7 OR (iv) CLAIMS FOR PERSONAL INJURY, INCLUDING DEATH, OR DAMAGE TO REAL PROPERTY OR
           TANGIBLE PERSONAL PROPERTY ARISING FROM THE NEGLIGENCE, RECKLESS CONDUCT OR INTENTIONAL
           ACTS OF CONTRACTOR, ITS OFFICERS, EMPLOYEES OR AGENTS NEITHER PARTY BE LIABLE FOR ANY LOST
           PROFITS, LOST SAVINGS, LOST DATA, PUNITIVE, INDIRECT, EXEMPLARY CONSEQUENTIAL OR INCIDENTAL
           DAMAGES.




                                                                                                              Page 23 of 100
10. INDEMNITIES.

   10.1. GENERAL INDEMNITY. Contractor shall defend, save, hold harmless, and indemnify the State of Oregon and Agency and
         their officers, employees and agents from and against all third party claims, suits, actions, losses, damages, liabilities,
         statutory penalties, costs and expenses for personal injury, including death, damage to real property and damage to tangible
         personal property resulting from, arising out of, or relating to the intentional, reckless or negligent acts or omissions of
         Contractor or its officers, employees, subcontractors, or agents under a WOC; provided that Contractor shall have no
         obligation to indemnify Agency or the State of Oregon from and against any claims, suits, actions, losses, damages, liabilities,
         costs and expenses attributable solely to the acts or omissions of Agency or the State of Oregon, and their officers,
         employees or agents.

   10.2. IP INDEMNITY. In addition to and without limiting the generality of Section 10.1, Contractor expressly agrees to, indemnify,
         defend and hold the State of Oregon and its agencies, subdivisions, officers, directors, employees and agents harmless from
         any and all third party claims, suits, actions, losses, damages, liabilities, costs and expenses of any nature whatsoever
         resulting from, arising out of or relating to any claims that the Product or Services or use thereof infringe or violate any patent,
         copyright, trade secret, trademark, trade dress, mask work, utility design, or other proprietary right (collectively, “Intellectual
         Property Rights”) of any third party. If Contractor believes at any time that the Product or Services infringe a third party’s
         Intellectual Property Rights, Contractor may upon receipt of Agency’s prior written consent, which Agency shall not
         unreasonably withhold, (i) replace an infringing item with a non-infringing item that meets or exceeds the performance and
         functionality of the replaced item; or (ii) obtain for Agency the right to continue to use the infringing item; or (iii) modify the
         infringing item to be non-infringing, provided that, following any replacement or modification made pursuant to the foregoing,
         the Products continue to function in conformance with the Acceptance Criteria set forth in this PA and any WOC. Contractor’s
         failure or inability to accomplish any of the foregoing shall be deemed a material breach of this PA and a WOC, and Agency
         may pursue any rights and remedies available to it under this PA, including termination of the PA or the WOC. Contractor
         shall not be liable under this Article 10.2 for any claim for infringement based solely on the following:

   •   Agency’s modification of the Product or Services other than as set forth in this PA or a WOC, the Product or Services’ or
       System’s specifications;

   •   Use of the Product or Services in a manner other than as contemplated by this PA or any WOC, their specifications, or as
       authorized in writing by Contractor;

   •   Use of the Product or Services in combination, operation, or use of with other products in a manner that does not comply with
       their specifications, not specified by Contractor or of which Contractor has not approved in writing.

   10.3. CONTROL OF DEFENSE AND SETTLEMENT. Contractor’s obligation to indemnify Agency as set forth in Sections 10.1 and
         10.2 is conditioned on Agency providing to Contractor prompt notification of any claim or potential claim of which Agency
         becomes aware that may be the subject of those Sections. Contractor shall have control of the defense and settlement of any
         claim that is subject to Section 10.1 or Section 10.2; however, neither Contractor nor any attorney engaged by Contractor
         shall defend the claim in the name of the State of Oregon or any agency of the State of Oregon, nor purport to act as legal
         representative of the State of Oregon or any of its agencies, without the approval of the Attorney General, nor shall Contractor
         settle any claim on behalf of the State of Oregon without the approval of the Attorney General. The State of Oregon may, at
         its election and expense, assume its own defense and settlement in the event that the State of Oregon determines that
         Contractor is prohibited from defending the State of Oregon, is not adequately defending the State of Oregon’s interests, or
         that an important governmental principle is at issue and the State of Oregon desires to assume its own defense.

   10.4. DAMAGES TO STATE PROPERTY AND EMPLOYEES. Contractor shall be liable for all claims, suits, actions, losses,
         damages, liabilities, costs and expenses for personal injury, including death, damage to real property and damage to tangible
         personal property of the State of Oregon or any of its employees resulting from, arising out of, or relating to the intentional,
         reckless or negligent acts or omissions of Contractor or its officers, employees, subcontractors, or agents under this PA or
         any WOC.

   10.5. Insurance. Contractor shall provide insurance as required by Exhibit B.

11. EVENTS OF DEFAULT.

   11.1. DEFAULT BY CONTRACTOR. Contractor shall be in default under this Pa and any WOC if:

       11.1.1. Contractor institutes or has instituted against it insolvency, receivership or bankruptcy proceedings which are not
             dismissed within 60 days of their commencement, makes an assignment for the benefit of creditors, or ceases doing
             business on a regular basis; or

       11.1.2. Contractor no longer holds a license or certificate that is required for Contractor to perform the Services and
             Contractor has not obtained such license or certificate within thirty (30) business days after delivery of Agency’s notice
             or such longer period as Agency may specify in such notice; or


                                                                                                               Page 24 of 100
        11.1.3. Contractor commits any material breach of any covenant, warranty, obligation or certification under this PA or any
              WOC, fails to perform the Services in conformance with the specifications and warranties provided herein, or clearly
              manifests an intent not to perform future obligations under this PA or any WOC, and such breach or default is not cured,
              or such manifestation of an intent not to perform is not corrected by reasonable written assurances of performance
              within thirty (30) business days after delivery of Agency’s notice or such longer period as Agency may specify in such
              notice.

    11.2. DEFAULT BY AGENCY. Agency shall be in default under this PA or any WOC if:

        11.2.1. Agency fails to pay Contractor any amount pursuant to the terms of the WOC, and Agency fails to cure such failure
              within thirty (30) business days after delivery of Contractor’s notice or such longer period as Contractor may specify in
              such notice; or

        11.2.2. Agency commits any material breach or default of any covenant, warranty, or obligation under this PA or any WOC,
              fails to perform its commitments hereunder within the time specified or any extension thereof, and Agency fails to cure
              such failure within thirty (30) business days after delivery of Contractor’s notice or such longer period as Contractor may
              specify in such notice.

12. REMEDIES FOR DEFAULT.

    12.1. Agency’s Remedies. In the event Contractor is in default under Section 11.1, Agency may, at its option, pursue any or all of
          the remedies available to it under this PA and at law or in equity, which include, without limitation:

        12.1.1. termination of this PA or any WOC under Section 13.2;

        12.1.2. withholding all monies due for Services that Contractor is obligated but has failed to perform within thirty (30) days
              after Agency has notified Contractor of the nature of Contractor’s default;

        12.1.3. with respect to Products and Services for which Agency has paid before Acceptance, returning the Products to
              Contractor for which Agency has paid in exchange for a return of all moneys previously paid for such Products and
              Services, and

        12.1.4. initiation of an action or proceeding for damages, specific performance, declaratory or injunctive relief;

        12.1.5. exercise of its right of setoff.

    12.2 REMEDIES CUMULATIVE. These Agency remedies are cumulative to the extent the remedies are not inconsistent, and
    Agency may pursue any remedy or remedies singly, collectively, successively or in any order whatsoever. If it is determined for
    any reason that Contractor was not in default under Section 11.1, the rights and obligations of the parties shall be the same as if
    this PA or any WOC was terminated pursuant to Section 13.1.

    12.3 CONTRACTOR’S REMEDIES. In the event Agency terminates this PA or any WOC as set forth in Section 13.1, or in the
    event Agency is in default under Section 11.2 and whether or not Contractor elects to exercise its right to terminate the PA or any
    WOC under Section 13.3., Contractor’s sole monetary remedy shall be a claim for (i) any unpaid invoices for Products delivered
    and Services completed and accepted; and, (ii) for incomplete Deliverables an amount calculated by determining the percentage of
    Services completed on each unpaid Deliverable and applying that percentage to the price for the Deliverable set forth in the WOC
    Statement of work, not to exceed amount for the Deliverable set forth in the WOC Statement of Work, and authorized expenses
    incurred. If previous amounts paid to Contractor exceed the amount due to Contractor under this Section 12.3, Contractor shall
    pay any excess to Agency upon written demand.

13. Termination.

    13.1. AGENCY’S RIGHT TO TERMINATE. Agency may, at its sole discretion, terminate this PA or any WOC, as follows:

        13.1.1. Agency may terminate this PA or any WOC for its convenience upon thirty (30) days’ prior written notice to
              Contractor.

        13.1.2. Agency may terminate this PA or any WOC if Agency fails to receive funding, appropriations, limitations or other
              expenditure authority at levels sufficient to pay for Contractor’s Services;

        13.1.3. Agency may terminate this PA or any WOC if Federal or state laws, regulations, or guidelines are modified or
              interpreted in such a way that the performance of the Services under a WOC is prohibited or Agency is prohibited from
              paying for such Services from the planned funding source;

    13.2. AGENCY’S RIGHT TO TERMINATE FOR CAUSE. In addition to any other rights and remedies Agency may have under this
          PA or any WOC, Agency may terminate this PA or any WOC, in whole or in part, immediately upon Contractor’s default under
          Section 11.1.

                                                                                                             Page 25 of 100
    13.3. CONTRACTOR’S RIGHT TO TERMINATE FOR CAUSE. Contractor may terminate this PA or any WOC upon Agency’s
          default under Section 11.2.

    13.4. RETURN OF PROPERTY. Upon termination of this PA or any WOC for any reason whatsoever, Contractor shall immediately
          deliver to Agency all of Agency’s property (including without imitation Agency’s Confidential Information or any Product or
          Services for which Agency has made payment in whole or in part) that are in the possession or under the control of
          Contractor in whatever stage of development and form of recordation such Agency property is expressed or embodied at that
          time. Any property or Product or Service returned or delivered to Agency pursuant to this Section shall be provided without
          the warranties set forth in Article 8.2, unless, with respect to Product or Services, Agency has accepted the Product or
          Service pursuant to Section 2.3.

14. INDEPENDENT CONTRACTOR; TAXES AND WITHHOLDING.

    14.1. INDEPENDENT CONTRACTOR. Contractor shall perform all Services as an independent contractor. Although Agency
          reserves the right to evaluate the quality of the completed performance, Agency cannot and will not control the means or
          manner of Contractor’s performance. Contractor is responsible for determining the appropriate means and manner of
          performing the Services.

    14.2. DECLARATION AND CERTIFICATION. Contractor by execution of this PA and any WOC declares and certifies that (i) its
          performance of the Services creates no potential or actual conflict of interest as defined by ORS Chapter 244, for Contractor
          or any Contractor personnel who will perform Services under this Contract, and (ii) in the event that Contractor or its
          personnel are either employed by or performing services for the federal government, that no rules or regulations of the
          agency for which Contractor or its personnel work or are employed prohibit Contractor or its personnel from providing the
          Services under this PA and any WOC. Contractor also declares and certifies by execution of this PA and any WOC that it is
          not an “officer,” “employee,” or “agent” of Agency, as those terms are used in ORS 30.265.

    14.3. RESPONSIBLE FOR TAXES. Contractor shall be responsible for all federal and state taxes applicable to compensation and
          other payments paid to Contractor under a WOC and, unless Contractor is subject to backup withholding, Agency will not
          withhold from such compensation and payments any amount to cover Contractor’s federal or state tax obligations. Contractor
          is not eligible for any social security, unemployment insurance, or workers’ compensation benefits from compensation or
          payments paid to Contractor under a WOC, except as a self-employed individual.

15. COMPLIANCE APPLICABLE LAW. Contractor shall comply with all federal, state and local laws, regulations, executive orders and
    ordinances applicable to the PA and any WOC. Without limiting the generality of the foregoing, Contractor expressly agrees to
    comply with the following laws, regulations and executive orders to the extent they are applicable to the PA and any WOC: (i)
    Titles VI and VII of the Civil Rights Act of 1964, as amended; (ii) Sections 503 and 504 of the Rehabilitation Act of 1973, as
    amended; (iii) the Americans with Disabilities Act of 1990, as amended; (iv) Executive Order 11246, as amended; (v) the Health
    Insurance Portability and Accountability Act of 1996; (vi) the Age Discrimination in Employment Act of 1967, as amended, and the
    Age Discrimination Act of 1975, as amended; (vii) the Vietnam Era Veterans’ Readjustment Assistance Act of 1974, as amended;
    (viii) ORS Chapter 659, as amended; (ix) all regulations and administrative rules established pursuant to the foregoing laws; and
    (x) all other applicable requirements of federal and state civil rights and rehabilitation statutes, rules and regulations. These laws,
    regulations and executive orders are incorporated by reference herein to the extent that they are applicable to the PA and any
    WOC and required by law to be so incorporated.

16. DISPUTE RESOLUTION.

    16.1. LITIGATION. Any claim, action, suit, or proceeding (collectively, “Claim”) between Agency (or any other agency or
          department of the State of Oregon) and Contractor that arises from or relates to this PA and any WOC shall be brought and
          conducted solely and exclusively within the Circuit Court of Marion County for the State of Oregon; provided, however, if a
          Claim must be brought in a federal forum, then it shall be brought and conducted solely and exclusively within the United
          States District Court for the District of Oregon. In no event shall this section 20.1 be construed as a waiver by the State of
          Oregon of any form of defense or immunity, whether sovereign immunity, governmental immunity, immunity based on the
          eleventh amendment to the Constitution of the United States or otherwise, from any claim or from the jurisdiction of any court.
          CONTRACTOR BY EXECUTION OF THIS CONTRACT HEREBY CONSENTS TO THE IN PERSONAM JURISDICTION OF
          THE COURTS REFERENCED IN THIS SECTION 16.

    16.2. GOVERNING LAW. This PA and any WOCs shall be governed by and construed according to the laws of the State of Oregon
          without regard to principles of conflict of laws.

17. MISCELLANEOUS PROVISIONS.

    17.1. ORDER OF PRECEDENCE. This PA consists of the following documents that are listed in descending order of precedence:
          (a) the terms and conditions of this PA, less its Exhibits; (b) the WOC Form including the Statement of Work, Exhibit E; (c)
          Exhibits A, B, and C. The aforementioned Exhibits are by this reference incorporated in the Contract.

    17.2 RECYCLING. Contract shall, to the maximum extent economically feasible in the performance of the PA and any WOC, use
    recycle paper (as defined in ORS 279A.010(1)(ee)), recycle PETE products (as defined in ORS 279A.010(1)(ff)), and other
    recycled plastic resin products and recycled products (as :”recycled product” is defined in ORS 279A.010(1)(gg).
                                                                                                              Page 26 of 100
17.3 SUBCONTRACTS AND ASSIGNMENT. Contractor shall not enter into any subcontracts for any of the Services required by
this PA or any WOC or assign or transfer any of its interest in this PA or any WOC without Agency’s prior written consent. Any
proposed use of a subcontractor which is located outside the United States or use of subcontract labor or facilities located outside
the United States must be called to the specific attention of Agency. Agency’s consent to any subcontract or assignment shall be
timely and not unreasonably withheld. Agency consent to a subcontract or assignment s shall not relieve Contractor of any of its
duties or obligations under this PA or any WOC. The assignment of this PA or any WOC, in whole or in part to a successor
organization by merger or acquisition does not require the consent of the other. Contractor is also permitted to assign its rights to
payments without obtaining Agency’s consent.

17.4 SUCCESSORS AND ASSIGNS. The provisions of this PA and any WOC shall be binding upon and shall inure to the benefit
of the parties hereto and their respective successors and permitted assigns, if any.

17.5 NO THIRD-PARTY BENEFICIARIES. Agency and Contractor are the only parties to this PA and any WOC and are the only
parties entitled to enforce its terms. Nothing in this PA or any WOC gives, is intended to give, or shall be construed to give or
provide any benefit or right, whether directly, indirectly, or otherwise, to third persons unless such third persons are individually
identified by name herein and expressly described as intended beneficiaries of the terms of this PA and any WOC.

17.6 FUNDS AVAILABLE AND AUTHORIZED. Contractor shall not be compensated for Services performed under any WOC by
any other agency or department of the State of Oregon. Agency believes it has sufficient funds currently available and authorized
for expenditure to finance the costs of the WOC within Agency’s biennial appropriation or limitation. Contractor understands and
agrees that Agency’s payment of amounts under a WOC is contingent on Agency receiving appropriations, limitations, or other
expenditure authority sufficient to allow Agency, in the exercise of its reasonable administrative discretion, to continue to make
payments under the WOC.

17.7. RECORDS MAINTENANCE; ACCESS. Contractor shall maintain all financial records and other records relating to its
performance under this PA and any WOC according to generally accepted accounting principles and in such a manner as to clearly
document Contractor’s performance. Contractor acknowledges and agrees that Agency, the Oregon Secretary of State and the
federal government and their duly authorized representatives shall have reasonable access, at their own cost and expense and
only following reasonable notice to Contractor, to such records, in paper or electronic form, to perform examinations and audits and
make excerpts and transcripts. Contractor shall retain and keep accessible all such records for a minimum of three (3) years, or
such longer period as may be required by applicable law, following termination of this PA and any WOC, or until the conclusion of
any audit, controversy, or litigation arising out of or related to this PA or any WOC, whichever date is later.

17.8. FOREIGN CONTRACTOR. If Contractor is not domiciled in or registered to do business in the State of Oregon, Contractor
shall promptly provide to the Oregon Department of Revenue and the Secretary of State, Corporation Division, all information
required by those agencies relative to this PA. Contractor shall demonstrate its legal capacity to perform the Services under this PA
and any WOC in the State of Oregon before entering into this PA.

17.9. Survival. All rights and obligations shall cease upon termination or expiration of this PA and any WOC, except for the rights
and obligations and declarations set forth in Articles 5, 6I 7, 8, 9, 12, 14 and 16, and Sections 14.3, 17.1, 17.4, 17.5, 17.7, 17.9,
17.12, 17.13, 17.18, 17.19, 17.20 and 17.21.

17.10. TIME IS OF THE ESSENCE. Contractor agrees that time is of the essence under this PA and any WOC for Deliverables or
Milestones as set forth in the WOC Statement of Work.

17.11. FORCE MAJEURE. Neither Agency nor Contractor shall be liable to the other for any failure or delay of performance of any
obligations hereunder when such failure or delay shall have been wholly or principally caused by acts or events beyond its
reasonable control, including without limitation acts of God, acts of civil or military authority, fires, floods, earthquakes or other
natural disasters, war, riots or strikes. Contractor shall, however, make all reasonable efforts to remove or eliminate such a cause
of delay or default and shall, upon the cessation of the cause, diligently pursue performance of its obligations under this PA and
any WOC.

17.12. NOTICES. Except as otherwise expressly provided in this PA, any communications between the parties hereto or notices to
be given hereunder shall be given in writing by personal delivery of, facsimile transmission of, or mailing the same, postage
prepaid, to Contractor at the address or number set forth in any WOC, and to Agency at the address or number set forth in the
WOC, or to such other addresses or numbers as either party may hereafter indicate in a WOC pursuant to this Section 17.12 Any
communication or notice so addressed and mailed shall be deemed to be given five calendar days after mailing. Any
communication or notice delivered by facsimile shall be deemed to be given when the transmitting machine generates receipt of
the transmission. To be effective against Agency, such facsimile transmission must be confirmed by telephone notice to the
Agency Authorized Representative. Any communication or notice by personal delivery shall be deemed to be given when actually
received by the appropriate Authorized Representative.

17.13 SEVERABILITY. The parties agree that if any term or provision of this PA or any WOC is declared by a court of competent
jurisdiction to be illegal or in conflict with any law, the validity of the remaining terms and provisions shall not be affected, and the
rights and obligations of the parties shall be construed and enforced as if this PA or WOC did not contain the particular term or
provision held to be invalid.

                                                                                                           Page 27 of 100
17.14 COUNTERPARTS. This PA or a WOC my be executed in several counterparts, all of which when taken together shall
constitute one contract binding on all parties, notwithstanding that all parties are not signatories to the same counterpart. Each
copy of this PA and any WOC so executed shall constitute an original.

17.15. AMENDMENTS.

17.15.1. Generally. This PA and any WOC may be amended, modified, or supplemented only by a written amendment signed by
Agency and Contractor that has been approved by DAS and DOJ, if required by applicable law. Any amendment that provides for
additional Products or Services may only provide for Products or Services directly related to the general scope of Products and
Services described in the RFP, and no amendment shall be effective until all requisite signatures and approvals are obtained.

17.15.2 Anticipated Amendments. The parties have determined that during the term of the PA or a WOC, the parties may need to
modify selected terms, conditions, price(s) and types of Products and Services under circumstances related to the following
illustrative, although not exhaustive, categories of anticipated amendments:

        17.15.2.1. Amendments required as a result of necessary changes in the State's business process that may restructure a
        State Agency;

        17.15.2.2. Amendments to the PA or any WOC Statement of Work to add Products and Services within the scope of the
        RFP;

        17.15.2.3. Amendments to delete Products and Services from the PA or from any WOC Statement of Work;

        17.15.2.4. Amendments to extend the term of the term of a WOC;

        17.15.2.5. Amendments to change pricing;

17.15.3. Change Control Procedures.

        17.15.3.1. Written Change Requests. Either Agency or Contractor may request a change to the PA or a WOC, including
        all Exhibits hereto, by submitting a written change request describing the change requested. Agency’s and Contractors’
        Authorized Representatives will review the written change request and either mutually approve it for further analysis or
        reject it.

        17.15.3.2. Analysis of Change Requests; Change Orders. The party to whom the written change request has been
        submitted, if it has not been rejected pursuant to Section 17.15.3.1, shall analyze such change request to determine the
        effect that the implementation of the change will have on the WOC Statement of Work. If Contractor requests to make
        changes in its design or implementation of the System to enable the System to meet the requirements of the WOC
        Statement of Work, such changes will be made at no cost to Agency, unless such changes are due to the failure of
        Agency or its agents to perform its or their responsibilities in a timely manner. If any change is approved, the party that
        submitted the request for the change shall prepare a written change order, detailing all modifications to the scope, price,
        Delivery Schedule or other terms (the “Change Order”). A Change Order at a minimum shall contain the following
        information:

             17.15.3.2.1. The date of issuance of the Change Order;

             17.15.3.2.2. A detailed description of the Products obtained or Services to be performed under the Change Order;

             17.15.3.2.3. The particular specification or matter set forth in the applicable WOC Statement of Work which will be
             altered and the precise scope of that alteration;

             17.15.3.2.4. The cost of the Products to be obtained or Services to be performed pursuant to the Change Order; and

             17.15.3.2.5. The cumulative cost of all Change Orders previously issued.

    17.15.4. A Change Order shall alter only that portion of the WOC Statement of Work to which it expressly relates and shall not
    otherwise affect the terms and conditions of this PA or the WOC. Both parties must sign the Change Order to authorize the
    Services described therein and incorporate the changes into the WOC or this PA. No Services shall be performed pursuant to
    the Change Order and no payment shall be made on account of the Change Order until the Change Order is fully executed
    and approved as set forth in Section 17.15.

    17.15.5. Payments. Subject to the foregoing Sections of this PA and performance of the Services, Agency shall pay for
    Services performed pursuant to a Change Order according to the acceptance and payment procedures set forth in this PA and
    the WOC.

17.16. DISCLOSURE OF SOCIAL SECURITY NUMBER. Contractor must provide Contractor’s Social Security number unless
Contractor provides a federal tax identification number. This number is requested pursuant to ORS 305.385, OAR 125-246-

                                                                                                      Page 28 of 100
    0330(2)(d), and OAR 150-305.100. Social Security numbers provided pursuant to this authority will be used for the administration
    of state, federal, and local tax laws.

    17.17. WAIVER. The failure of either party to enforce any provision of this PA or any WOC or the waiver of any violation or
    nonperformance of this Pa or any WOC in one instance shall not constitute a waiver by the party of that or any other provision nor
    shall it be deemed to be a waiver of any subsequent violation or nonperformance. No waiver, consent, modification, or change of
    terms of this PA or any WOC shall bind either party unless in writing and signed by both parties and, with respect to Agency’s
    waiver or consent all necessary State of Oregon approvals have been obtained. Such waiver, consent, modification, or change, if
    made, shall be effective only in the specific instance and for the specific purpose given.

    17.18. HEADINGS. The headings in this PA are included only for convenience and shall not control or affect the meaning or
    construction of this PA.

    17.19. INTEGRATION. This PA including attached Exhibits constitute the entire agreement between the parties on the subject
    matter hereof. There are no understandings, agreements or representations, oral or written, not specified herein regarding this PA.

    17.20. NO PARTNERSHIP. This PA and any WOC is not intended, and shall not be construed, to create a partnership or joint
    venture between Agency and Contractor. Nothing in this PA or any WOC shall be construed to make Agency and Contractor
    partners or joint venture participants.

    17.21. PUBLICITY. Contractor agrees that it will not disclose the form, content or existence of this PA or any WOC or any Product
    or Service in any advertising, press releases or other materials distributed to prospective customers, or otherwise attempt to obtain
    publicity from its association with Agency or the State of Oregon, whether or not such disclosure, publicity or association implies an
    endorsement by Agency or the State of Oregon of Contractor’s services, without the prior written consent of Agency.

CONTRACTOR, BY EXECUTION OF THIS PRICE AGREEMENT AND ANY WORK ORDER CONTRACTS, HEREBY
ACKNOWLEDGES THAT CONTRACTOR HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY
ITS TERMS AND CONDITIONS.

CONTRACTOR: YOU WILL NOT BE PAID FOR SERVICES RENDERED BEFORE NECESSARY AGENCY APPROVALS.

                                          CONTRACTOR DATA AND TAX CERTIFICATION

Certification: By signature on this Contract for Contractor, the undersigned hereby certifies under penalty of perjury that the
undersigned is authorized to act on behalf of Contractor and that Contractor is, to the best of the undersigned’s knowledge, not in
violation of any Oregon Tax Laws. For purposes of this certification, “Oregon Tax Laws” means a state tax imposed by ORS 320.005 to
320.150 (Amusement Device Taxes), 403.200 to 403.250 (Tax For Emergency Communications), 118 (Inheritance Tax), 314 (Income
Tax), 316 (Personal Income Tax), 317 (Corporation Excise Tax), 318 (Corporation Income Tax), 321 (Timber and Forest Land
Taxation) and 323 (Cigarettes And Tobacco Products ) and the elderly rental assistance program under ORS 310.630 to 310.706 and
any local taxes administered by the Department of Revenue under ORS 305.620.


CONTRACTOR:

__________________________________________________ Date:_____________


AGENCY:

__________________________________________________ Date:_____________


Department of Justice (approved as to Legal Sufficiency)

_________________________________________________ Date:______________




                                                                                                             Page 29 of 100
                                        EXHIBIT A
                       CONFLICT OF INTEREST (COI) DISCLOSURE FORM

Please answer all questions below. If uncertain answer “yes.” If the answer to any of the questions below is “yes,” then:
(a) provide all relevant facts that are necessary to make the response complete, accurate, and not misleading; and
(b) identify any actions that must be taken to avoid, neutralize, or mitigate such conflict of interest

(e.g. communications barriers, restraint or restriction upon future contracting activities, or other precaution).
Is any Associate of the firm a former employee of ODOT within the last two years or a family member of a current
employee of ODOT?         ____Yes        __No
Did the Firm, or any Associate of the Firm, participate in preparing any part of any ITB or RFP or any documents or
reports to which any such ITB or RFP refers that have been advertised or will be advertised pertaining to this project?
____Yes          ___ No

Does the Firm, or any Associate of the Firm, have any past, present or currently planned interests which are an Actual or
Potential Organizational Conflict of Interest (as defined in ODOT’s COI Guidelines), with respect to performing the work
for ODOT? ______Yes         _____No
Does the Firm, or any Associate of the Firm, have any individuals with an Actual or Potential Personal Conflict of Interest
(as defined in ODOT’s COI Guidelines), with respect to performing the work for ODOT? _____Yes           _____No
Have subcontractors furnished COI Disclosure Forms separate from the present form? (If yes, attach subcontractor
disclosures.) _____Yes _____No

My signature certifies that as disclosed on or attached to the present form:
the Firm’s disclosures are complete, accurate, and not misleading.
the Firm has received COI Disclosure Form(s) from all sub-Contractors or subcontractors (if any) and the present form
incorporates or has attached any disclosures thereof.
This COI Disclosure Form must be signed in ink by a principal of the Firm to certify that it is correct and includes the
disclosure by its Associates and subcontractors. I hereby certify that I am authorized to sign this COI Disclosure Form as
a Representative for the Firm identified below:


_________________________________________________________________________

Complete Legal Name of Firm


_________________________________________________________________________
Representative’s Signature                                                            Date




Print Name & Title________________________________________________________




                                                                                                      Page 30 of 100
                                                             EXHIBIT B
                                                           INSURANCE.
REQUIRED INSURANCE. Contractor shall obtain at Contractor’s expense the insurance specified prior to performance under this
Price Agreement and shall maintain it in full force and at its own expense throughout the duration of this Price Agreement and all
warranty periods. Contractor shall obtain the following insurance from insurance companies or entities that are authorized to transact
the business of insurance and issue coverage in State and that are acceptable to Agency.

WORKERS COMPENSATION. All employers, including Contractor, that employ subject workers, as defined in ORS 656.027, shall
comply with ORS 656.017 and shall provide workers' compensation insurance coverage for those workers, unless they meet the
requirement for an exemption under ORS 656.126(2). Contractor shall require and ensure that each of its subcontractors complies with
these requirements.

PROFESSIONAL LIABILITY
Contractor shall obtain and maintain at its own expenses for the duration of this Price Agreement Professional Liability Insurance wit h a
combined single limit, or the equivalent, as set forth below. This is to cover damages caused by error, omission or negligent acts
related to the professional services to be provided under this Price Agreement. Full limits can be obtained by the purchase of one
primary policy or a primary and excess policy as needed to provide the full policy limits. Such policy shall include coverage for losses
arising from the breach of information security or cyber liability (including Technology Errors & Omissions, Network Security and Privacy
Liability and Media Liability), whether combined with the Professional Liability policy or placed as a separate policy, but carrying the
same limits of liability. Such coverage shall insure damage caused by error, omission, or negligent acts, including all prior acts without
limitation, related to the professional services to be provided under this Price Agreement. The Policy shall be amended to include
Independent Contractors providing Professional Services on behalf of or at the direction of Contractor. The definition of Contractual
Liability shall be amended to state that liability under a contract of professional services is covered. Further, coverage shall be afforded
for fraudulent acts, misappropriation of trade secrets, internet professional services, computer attacks, personal injury, regulatory
actions, known wrongful acts, contractual liability, privacy policy, and insured versus insured.
$1,000,000 Per occurrence limit for any single claimant; and $3,000,000 Per occurrence limit for any number of claimants

COMMERCIAL GENERAL LIABILITY.
Commercial General Liability Insurance covering bodily injury, death and property damage in a form and with coverages that are satisfactory
to the State. This insurance shall include personal injury liability, products and completed operations. Coverage shall be written on an
occurrence basis. Contractor shall provide proof of insurance of not less than the following amounts as determined by the Agency:

Bodily Injury/Death:
$3,000,000 Per occurrence limit for any single claimant; and      $3,000,000 Per occurrence limit for any number of claimants:

Property Damage:
$3,000,000 Per occurrence limit for any single claimant; and      $3,000,000 Per occurrence limit for any number of claimants

ADDITIONAL INSURED.
The Commercial General Liability insurance required under this Price Agreement shall include the State of Oregon, its officers,
employees and agents as Additional Insureds but only with respect to Contractor's activities to be performed under this Price
Agreement. Coverage shall be primary and non-contributory with any other insurance and self-insurance.

"TAIL" COVERAGE.
If any of the required professional liability insurance is on a "claims made" basis, Contractor shall either maintain either “tail" coverage
or continuous "claims made" liability coverage, provided the effective date of the continuous “claims made” coverage is on or before the
effective date of this Price Agreement, for a minimum of 24 months following the later of (i) Contractor’s completion and Agency’s
acceptance of all Services required under this Price Agreement, or, (ii) The expiration of all warranty periods provided under this Price
Agreement. Notwithstanding the foregoing 24-month requirement, if Contractor elects to maintain “tail” coverage and if the maximum time
period “tail” coverage reasonably available in the marketplace is less than the 24-month period described above, then Contractor shall
maintain “tail” coverage for the maximum time period that “tail” coverage is reasonably available in the marketplace for the coverage required
under this Price Agreement. Contractor shall provide to Agency, upon Agency’s request, certification of the coverage required under this
section.

NOTICE OF CANCELLATION OR CHANGE.
There shall be no cancellation, material change, potential exhaustion of aggregate limits or non-renewal of insurance coverage(s)
without sixty (60) days' written notice from this Contractor or its insurer(s) to Agency. Any failure to comply with the reporting provisions
of this clause shall constitute a material breach of Contract and shall be grounds for immediate termination of this Price Agreement by
Agency.

CERTIFICATE(S) OF INSURANCE.
Contractor shall provide to Agency Certificate(s) of Insurance for all required insurance before delivering any Goods and
performing any Services required under this Price Agreement. The Certificate(s) must specify all entities and individuals
who are endorsed on the policy as Additional Insured (or Loss Payees). Contractor shall pay for all deductibles, self-
insured retention and self-insurance, if any.
                                                                                                                Page 31 of 100
                                   EXHIBIT C
             CERTIFICATION STATEMENT FOR INDEPENDENT CONTRACTOR
                        (Contractor completes if Contractor is not a corporation or is a professional corporation.)

A. CONTRACTOR IS INDEPENDENT CONTRACTOR.
Contractor certifies he/she meets the following standards:

1.   I am registered under ORS chapter 701 to provide labor or services for which such registration is required.

2. I have filed federal and state income tax returns in the name of my business or a business Schedule C as part of the personal
income tax return, for the previous year, or expect to file federal and state income tax returns, for labor or services performed as an
independent contractor in the previous year.

3.   I will furnish the products or equipment necessary for the contracted labor or services.

4.   I have the authority to hire and fire employees who perform the labor or services.

5. I represent to the public that the labor or services are to be provided by my independently established business as four (4) or more
of the following circumstances exist. (Please check four or more of the following:)

A. The labor or services are primarily carried out at a location that is separate from my residence or is primarily carried out in a
specific portion of my residence, which is set aside as the location of the business.
B. Commercial advertising or business cards are purchased for the business, or I have a trade association membership;
C. Telephone listing is used for the business that is separate from the personal residence listing.
D. Labor or services are performed only pursuant to written contracts.
E. Labor or services are performed for two or more different persons within a period of one year.
F. I assume financial responsibility for defective workmanship or for service not provided as evidenced by the ownership of
performance bonds, warranties, errors and omission insurance or liability insurance relating to the labor or services to be provided.

Contractor Signature                                                       Date




                                                                                                              Page 32 of 100
                              EXHIBIT D
           Authorized Representatives to the Price Agreement

           Agency                              Contractor
Name:                               Name:

Title:                              Title:

Address:                            Address:



Phone:                              Phone:

Fax:                                Fax:

Email:                              Email:




                                                            Page 33 of 100
                                                                     EXHIBIT E
                                                                   SAMPLE FORM
                                                  WORK ORDER CONTRACT #__________
                                                       Price Agreement #_______


This Work Order Contract (“WOC”) # ________________ is between the State of Oregon, acting by and
though its Department of Transportation (“Agency”) and __________________ (“Contractor”). This WOC is
placed against State of Oregon Price Agreement #________. The terms and conditions of the Price
Agreement apply to this purchase.

1. PROJECT: _____________________________________________________________________

2. WOC TERM: The WOC is effective upon the Effective date. The WOC expires on __________.

3. COMPENSATION:


4. STATEMENT OF WORK for this WOC is attached and hereby incorporated by this reference.
Certification: The individual signing on behalf of Contractor hereby certifies and swears under penalty of perjury: (a) Contractor is not subject to
backup withholding because (i) Contractor is exempt from backup withholding, (ii) Contractor has not been notified by the IRS that Contractor is
subject to backup withholding as a result of a failure to report all interest or dividends, or (iii) the IRS has notified Contractor that Contractor is no
longer subject to backup withholding; (b) s/he is authorized to act on behalf of Contractor, s/he has authority and knowledge regarding
Contractor’s payment of taxes, and to the best of her/his knowledge, Contractor is not in violation of any Oregon tax laws (including, without
limitation, the following pursuant to OAR 150-305.385(6)-(B): For purposes of this certification, “Oregon tax laws” means the tax laws names is
ORS 305.380 (4), including without limitation the state inheritance tax, gift tax, personal income tax, withholding tax, corporation income and
excise taxes, amusement device tax, timber taxes, cigarette tax, other tobacco tax., 9-1-1 emergency communications tax, the homeowners and
renters property tax relief program and local taxes administered by the Department of Revenue (Multnomah County Business Income Tax, Lane
Transit District Tax, Tri-Metropolitan Transit District Employer Payroll Tax, and Tri-Metropolitan District Self-Employment Tax; (c) Contractor is
an independent contractor as defined in ORS 670.600; and (d) the supplied Contractor data is true and accurate.

CONTRACTOR:
By: ___________________________ Title: __________________ Date: ___________

ODOT: _________________________________________________
By: ___________________________ Title: __________________ Date:___________

DEPARTMENT OF JUSTICE:
Approved By: ___________________________ Title: __________________ Date: ___________
(If required by OAR 137-045-0030 or OAR 137-045-0035)




                                                                                                                                    Page 34 of 100
                                SAMPLE STATEMENT OF WORK

                                                                   Work Order Contract #______
A. INTRODUCTION AND PROJECT OBJECTIVES




B. AUTHORIZED REPRESENTATIVES:

            Agency                                        Contractor
Name:                                        Name:
Address:                                     Address:

Phone:                                       Phone:
Fax:                                         Fax:
Email:                                       Email:

C. PROJECT TEAM: Contractor’s Key Persons.
     Name:


D. PROJECT SPECIFIC ABREVIATIONS, ACRONYMS AND DEFINITIONS.


E. PRODUCTS

F. TASKS AND DELIVERABLES: Contractor shall not start work under this WOC until in receipt of a
written Notice-to-Proceed (NTP) from the Agency.

Sample:
Task #1

      Task #1 Deliverables:

Task #2

      Task #2 Deliverables:

G. PROJECT SPECIFIC PROVISIONS:
Project specific Terms and Conditions are applicable only to this WOC and Project.



H. REVIEW AND ACCEPTANCE CRITERIA:




                                                                               Page 35 of 100
I. SAMPLE DELIVERY AND PAYMENT SCHEDULE

The Agency shall make payments to the Contractor based on the Work delivered and accepted by
the Agency. The attached Gantt chart and Excel Pricing form are examples of delivery and payment
schedules.
ID    WBS         Task Name                                                       Start          Finish
                                                                                                              1st Quarter   2nd Quarter   3rd Quarter   4th Quarter   1st Quarter   2nd Quarter   3rd Quarter   4th Quarter   1st Quarter   2nd Quarte

 1           3 TranInfo Implementation                                           Mon 4/6/09 Wed 11/24/10
 2          3.1      Project Management and Tracking                             Mon 4/6/09 Mon 10/25/10
 3       3.1.1           Status report                                          Mon 4/13/09 Mon 10/25/10
45       3.1.2           Status meeting                                         Mon 4/13/09 Mon 10/25/10
87       3.1.4           Steering Committee Meetings and Plan Update            Wed 4/15/09 Thu 10/21/10
98       3.1.5           Quality Assurance Reviews                               Tue 5/5/09     Thu 8/5/10
105      3.1.6           Project Plan and Initiation                             Mon 4/6/09     Tue 5/5/09
109    3.1.6.4                Update Project Plan                                Mon 4/6/09    Tue 4/28/09
115    3.1.6.5                Prepare Project Initiation Document                Mon 4/6/09     Tue 5/5/09
123         3.2      System Architecture                                         Mon 4/6/09 Tue 11/10/09
124      3.2.1           COTS training                                           Mon 4/6/09    Wed 5/13/09
128      3.2.2           Detailed Requirements                                   Mon 4/6/09     Fri 7/10/09
129    3.2.2.1                Configure scoping workshop system                  Mon 4/6/09     Fri 4/10/09
132    3.2.2.2                Workshops                                         Mon 4/13/09      Fri 5/1/09
135   3.2.2.2.3                   System interfaces workshops                   Mon 4/20/09     Fri 4/24/09
143    3.2.2.3                Detailed requirements document                     Mon 5/4/09    Tue 6/30/09
144   3.2.2.3.1                   First draft detailed requirements document     Mon 5/4/09     Wed 6/3/09
157    3.2.2.4                Stakeholder meeting                                Thu 6/4/09     Tue 6/9/09
162    3.2.2.5                Prioritize reporting requirements                  Thu 6/4/09     Fri 7/10/09
164   3.2.2.5.2                   Reporting prioritization document              Mon 6/8/09     Fri 7/10/09
170      3.2.3           System requirements specification                       Wed 7/1/09     Thu 8/6/09
175      3.2.4           To-Be Work Processes                                    Wed 7/1/09     Fri 7/24/09
180      3.2.5           COTS Data Dictionary                                   Mon 7/27/09     Fri 9/11/09
189      3.2.6           Software Architecture                                  Wed 7/29/09     Fri 8/28/09
196      3.2.7           Data conversion strategy document                       Fri 8/28/09   Tue 10/6/09
204      3.2.8           Technology Infrastructure Document                       Fri 8/7/09    Fri 9/11/09
212      3.2.9           Installation plan                                       Fri 9/11/09   Tue 9/29/09
217     3.2.10           Implementation plan document                            Fri 9/11/09   Tue 9/29/09
223     3.2.11           Reassessment                                           Wed 10/7/09 Tue 11/10/09
228   3.2.11.5                Update project plan                              Mon 10/19/09 Tue 11/10/09
238         3.3      Design and Construction Phase                               Thu 5/7/09     Mon 5/3/10
239      3.3.1           COTS License                                            Thu 5/7/09     Thu 5/7/09
242      3.3.2           Final installation plan                               Mon 10/26/09    Mon 11/2/09
247      3.3.3           Physical database                                      Mon 1/11/10    Mon 1/25/10
250      3.3.4           Test plan                                             Thu 11/12/09 Thu 12/17/09
257      3.3.5           Develop interfaces and extracts                       Thu 11/12/09     Fri 3/26/10
258    3.3.5.1                Document interfaces design                       Thu 11/12/09     Tue 3/2/10
259   3.3.5.1.1                   First draft design document                  Thu 11/12/09 Mon 11/23/09
269    3.3.5.2                Development for interfaces                         Tue 3/2/10     Fri 3/26/10
274      3.3.6           Develop Conversions                                   Tue 11/10/09    Mon 2/22/10
275    3.3.6.1                Data model review                                Tue 11/10/09    Fri 11/13/09
279    3.3.6.3                Design and develop conversion objects             Fri 11/13/09    Wed 1/6/10
284    3.3.6.4                Test conversion                                    Wed 1/6/10    Wed 2/10/10
287   3.3.6.4.3                   Load data into new environment                Mon 1/25/10    Wed 2/10/10
294      3.3.7           Develop Reports                                       Thu 11/12/09    Wed 3/31/10
295    3.3.7.1                Document reports design                          Thu 11/12/09     Wed 3/3/10
302    3.3.7.2                Development for reports                            Wed 3/3/10    Wed 3/31/10
306      3.3.8           Configure and install COTS                               Fri 5/8/09   Thu 5/14/09
309      3.3.9           Test Environment                                      Thu 12/17/09     Tue 1/5/10
314     3.3.10           System testing                                          Tue 1/5/10     Mon 5/3/10
319     3.3.11           Update user training plan                             Thu 11/12/09 Tue 12/22/09
326     3.3.12           Assemble user training materials                       Fri 11/27/09 Wed 1/13/10
333     3.3.13           Prepare TransInfo User Guide                            Wed 1/6/10     Fri 2/19/10
339     3.3.14           Prepare TransInfo Administration Guide                 Wed 1/27/10     Fri 3/12/10
346         3.4      Implementation                                             Tue 11/3/09    Thu 7/29/10
347      3.4.1           UAT user training                                       Mon 5/3/10    Mon 5/17/10
350      3.4.2           User Acceptance Testing                                 Mon 5/3/10    Tue 6/29/10
351    3.4.2.1                Set up test environment                            Mon 5/3/10    Tue 5/11/10
358      3.4.4           Install configured system in production environment    Tue 11/3/09    Thu 7/29/10
359    3.4.4.1                Set up production environment                     Tue 11/3/09     Mon 7/5/10
364      3.4.5           Convert data                                            Mon 5/3/10     Thu 7/29/10
371         3.5      Project Closure                                             Mon 7/5/10 Wed 11/24/10
373      3.5.2           Project completion review                              Thu 7/29/10 Wed 11/24/10
375    3.5.2.2                Project close-out                                Tue 11/23/10 Wed 11/24/10




                                                                                                                                                                                                                                                  Page 36 of 100
                     Pricing Schedule - Cost per Task
  WBS #                           Task                             Cost
3.1     Project Management and Tracking
3.1.1   Status report                                         $   18,141.76
3.1.2   Status meeting                                        $   67,759.48
3.1.4   Steering Committee Meetings and Plan Update           $   32,985.01
3.1.5   Quality Assurance Reviews                             $    9,744.60
3.1.6   Project Plan and Initiation                           $   23,687.78
3.1.7   Kick-off meeting                                      $    4,609.25
3.2     System Architecture
3.2.1   COTS training                                         $ 16,354.27
3.2.2   Detailed Requirements                                 $ 109,269.29
3.2.3   System requirements specification                     $ 7,944.44
3.2.4   To-Be Work Processes                                  $ 15,737.98
3.2.5   COTS Data Dictionary                                  $ 15,813.43
3.2.6   Software Architecture                                 $ 13,452.74
3.2.7   Data conversion strategy document                     $ 26,142.42
3.2.8   Technology Infrastructure Document                    $ 7,906.72
3.2.9   Installation plan                                     $ 4,759.12
3.2.10  Implementation plan document                          $ 5,546.02
3.2.11  Reassessment                                          $ 28,147.76
3.2.12  System Architecture phase complete                    $        -
3.3     Design and Construction Phase
3.3.1   COTS License                                          $        -
3.3.2   Final installation plan                               $ 1,573.80
3.3.3   Physical database                                     $ 17,387.23
3.3.4   Test plan                                             $ 21,521.55
3.3.5   Develop interfaces and extracts                       $ 41,623.88
3.3.6   Develop Conversions                                   $ 72,172.17
3.3.7   Develop Reports                                       $ 51,300.00
3.3.8   Configure and install COTS                            $ 9,836.98
3.3.9   Test Environment                                      $ 2,400.00
3.3.10  System testing                                        $ 103,975.04
3.3.11  Update user training plan                             $ 21,243.71
3.3.12  Assemble user training materials                      $ 30,011.57
3.3.13  Prepare TransInfo User Guide                          $ 24,951.68
3.3.14  Prepare TransInfo Administration Guide                $ 24,258.58
3.3.15  Design and construction phase complete                $        -
3.4     Implementation
3.4.1   UAT user training                                     $    7,118.62
3.4.2   User Acceptance Testing                               $   33,682.22
3.4.3   End user training                                     $   20,980.66
3.4.4   Install configured system in production environment   $    7,328.84
3.4.5   Convert data                                          $   16,624.92
3.4.6   Administrator training                                $   11,089.64
3.4.7   Operations training                                   $    5,732.41
3.5     Project Closure
3.5.1   Monitor operations                                    $ 56,028.18
3.5.2   Project completion review                             $ 10,493.77
3.5.3   COTS support and maintenance                          $        -
TOTAL COST OF ALL TASKS                                       $ 999,337.50




                                                                              Page 37 of 100
                                              Attachment B – 1
                                             PROPOSAL FORM
                                    (To be completed and returned as the “Proposal”)

                                                     Cover Sheet
    Corporation                  Professional Corporation       Partnership                Ltd. Partnership
    Ltd. Liability Company       Ltd. Liability Partnership    Sole Proprietorship          Other ________
Secretary of State Corporations Division Registration No.      ____________________________
Mailing Address              ______________________________                          ________________


Type name of authorized representative
Email address
Telephone                                         Fax
Type name of person(s) authorized to sign Contract

Provide at least three corporate references:
Name of Firm
Project Title
Their Contact Person
Telephone                        email ___________________________________________
Project Manager or Owner_______________________________________________________
Telephone                        email
Project Description: ____________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________

Name of Firm
Project Title
Their Contact Person
Telephone                        email
Project Manager or Owner_______________________________________________________
Telephone                       email
Project Description: ____________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________

Name of Firm
Project Title
Their Contact Person
Telephone                        email
Project Manager or Owner_______________________________________________________
Telephone                       email
Project Description: ____________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________


                                                                                              Page 38 of 100
      Agency has the right to obtain references from any source known to Agency in addition to those above.

Representations, Attestations, and Certifications: The undersigned further acknowledges, attests and certifies
individually and on behalf of the Proposer that:

1.    No attempt has been made or shall be made by the Proposer to induce any other person or organization to submit
      or not submit a Proposal.

2.    Information and prices included in this Proposal shall remain valid for one hundred and twenty (120) days after the
      proposal due date or until a Price Agreement is approved, whichever comes first.

3.    The undersigned recognizes that this is a public document and open to public inspection.

4.    The Proposer acknowledges receipt of all Addenda issued under the RFP.

5.    Proposer does not discriminate in its employment practices with regard to race, creed, age, religious affiliation, sex,
      disability, sexual orientation or national origin, nor has Proposer or will Proposer discriminate against a
      subcontractor in the awarding of a subcontract because the subcontractor is a minority, women or emerging small
      business enterprise certified under ORS 200.055.

6.    Affirmative Action Program: Agency is an equal-employment-opportunity employer and value diversity in its work
      force. Agency requires its Contractors to have an operating policy as an equal employment opportunity employer.
      Firms of 50 people or less do not need to have a formal equal employment opportunity program, but shall have an
      operating policy supporting equal employment opportunity. ________________________ (Name of Firm) has an
      operating policy supporting equal employment opportunity. Firms of 50 people or more shall also have a formal
      equal employment opportunity program.
          Yes    No Does your firm have 50 or more employees?
          Yes    No Does your firm have a formal equal employment opportunity program?
          Yes    No This Proposal has been printed on recycled paper.

7.    The Proposer, acting through its authorized representative, has read and understands all RFP instructions,
      specifications, and terms and conditions contained within the RFP and all Addenda, if any;

8.    The Proposer agrees to and shall comply with, all requirements, specifications and terms and conditions contained
      within the RFP, including all Addenda, if any;

9.    The Proposal submitted is in response to the specific language contained in the RFP, and Proposer has made no
      assumptions based upon either (a) verbal or written statements not contained in the RFP, or (b) any previously-
      issued RFP, if any.

10.   The Proposer agrees that if awarded the Price Agreement, Proposer shall be authorized to do business in the State
      of Oregon at the time of the award;

11.   Agency shall not be liable for any claims or be subject to any defenses asserted by Proposer based upon, resulting
      from, or related to, Proposer's failure to comprehend all requirements of the RFP.

12.   The Agency shall not be liable for any expenses incurred by Proposer in either preparing and submitting its
      Proposal, or in participating in the proposal evaluation/selection or Price Agreement negotiation process, if any.

13.   Recycled Products Certification
      Contractors must use recyclable products to the maximum extent economically feasible in the performance of the
      Contract work set forth in this document.
      Authorized Agencies must use, or require persons with whom they Contract with to use in the performance of the
      Contract work, to the maximum extent economically feasible, recycled paper products as well as other recycled
      plastic resin products. (ORS 279B.270(1)(e)).

      “Recycled paper” means a paper product with not less than fifty percent of its fiber weight consisting of secondary
      waste materials; or twenty-five percent of its fiber weight consisting of post-consumer waste. (ORS
      279A.010(1)(g)).


                                                                                                   Page 39 of 100
      ORS 279A.010 (1) (ii) states: "'Recycled product' means all materials, goods and supplies, not less than 50 percent
      of the total weight of which consists of secondary and post-consumer waste with not less than 10 percent of total
      weight consisting of post-consumer waste. 'Recycled product' also includes any product that could have been
      disposed of as a solid waste, having completed its life cycle as a consumer item, but otherwise is refurbished for
      reuse without substantial alteration of the product's form."

      ORS 279A.010(1)(u) states: "'Post-consumer waste' means a finished material which would normally be disposed of
      as solid waste, having completed its life cycle as a consumer item. 'Post-consumer waste' does not include
      manufacturing waste."

      ORS 279A.010(1)(jj) states: "'Secondary waste materials' means fragments of products or finished products of a
      manufacturing process which has converted a virgin resource into a commodity of real economic value, and
      includes post-consumer waste, but does not include excess virgin resources of the manufacturing process. For
      paper, 'secondary waste materials' does not include fibrous waste generated during the manufacturing process
      such as fibers recovered from waste water or trimmings of paper machine rolls, mill broke, wood slabs, chips,
      sawdust, or other wood residue from a manufacturing process."

      I, the undersigned duly authorized representative of the Proposer, hereby certify that the products, if any, offered in
      this Proposal contain the following minimum percentages:

               a) ____ % (recycled product as defined in ORS 279A.010 (1)(ii)
               b) ____ % (post-consumer waste as defined in ORS 279A.010 (1)(u)
               c) ____ % (secondary waste materials as defined in ORS 279A.010 (1)(jj)

      It is the Proposer's responsibility to provide additional signed copies of the Certification of Compliance for each item
      which contains a different percentage of recycled materials than listed above.

14.   Office of Foreign Assets Control and US Department of State: Proposer and Proposer’s employees and agents
      are not included on:
      a) the list entitled “Specially Designated Nationals and Blocked Persons” maintained by the Office of Foreign Assets
      Control of the United States Department of the Treasury and currently found at
      http://www.treas.gov/offices/enforcement/ofac/sdn/t11sdn.pdf; or
      b) the list entitled “Current List of Designated Foreign Terrorist Organizations of the US Department of State” and
      currently found at http://www.state.gov/s/ct/rls/fs/37191.htm.

15.   The signatory of this Proposal Cover Sheet is a duly authorized representative of the Proposer, has been
      authorized by Proposer to make all representations, attestations, and certifications contained in this Proposal
      document and all Addenda, if any, issued, and to execute this Proposal document on behalf of Proposer.

16.   By signature below, the undersigned Authorized Representative hereby certifies on behalf of Proposer that all
      contents of this Proposal Cover Sheet and the submitted Proposal are truthful, complete and accurate. Failure to
      provide information required by the RFP may ultimately result in rejection of the Proposal.

THIS OFFER SHALL BE SIGNED IN INK BY AN AUTHORIZED REPRESENTATIVE OF THE PROPOSER; ANY
ALTERATIONS OR ERASURES TO THE OFFER SHALL BE INITIALED IN INK BY THE UNDERSIGNED AUTHORIZED
REPRESENTATIVE.

SIGNATURE OF PROPOSER'S DULY AUTHORIZED REPRESENTATIVE FOR ALL SECTIONS:


Authorized Signature: __________________________________________________________

Print Name: __________________________________________________________________

Title: _______________________________________________________________________


Contact Person (Type or Print): ___________________________________________________

Telephone Number: (___) _____________________Fax Number: (___) ___________________


                                                                                                    Page 40 of 100
                       CONTRACTOR PERSONNEL AND KEY PERSONS
                        Points Possible _30_ Points Awarded_______
INSTRUCTIONS: Proposer shall list all proposed personnel including resumes for each and a description of how they are
qualified to perform the work. Only the Personnel qualifications will be assigned scoring points in this section. Use the
below professional reference form for each Key Person you are submitting. The Billing Rate Information is to be included
separately in the Price Information section.


Provide at least three professional references for each Key Person:
Name of Firm
Project Title
Their Contact Person
Telephone                        email ___________________________________________
Project Manager or Owner_______________________________________________________
Telephone                        email
Project Description: ____________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________

Name of Firm
Project Title
Their Contact Person
Telephone                        email
Project Manager or Owner_______________________________________________________
Telephone                       email
Project Description: ____________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________

Name of Firm
Project Title
Their Contact Person
Telephone                        email
Project Manager or Owner_______________________________________________________
Telephone                       email
Project Description: ____________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________




                                                                                                Page 41 of 100
      KEY PERSONS             Resume/reference                          Description of Qualifications
                                 attached?
                                Yes      No
Contractor Project
Manager:




                                   Evaluator Comments:                                            Points          Points
                                                                                                 Possible:       Awarded:




                                      Qualifications of Contractor Key Persons

Contractor Project Manager - responsible for all coordination of work required of Contractor to fulfill the obligations
resulting from this RFP. Contractor Project Manager shall provide input to the DMV Project Manager and support
planning, reporting, risk and issue management in support of the DMV project. Responsible for completing the agreed
project scope on time, within budget. Responsible for facilitating the project by using the project management processes,
organizing the project, and managing the team work activities consistent with the approved work plan. Responsible for
collaborating with and responding to requests from DMV Project Manager in support of the SCM project.
Minimum Requirements: 5-10 years of IT project management experience. Experience should include a minimum of two
successful projects that involved implementing the product being proposed in response to this RFP.



                                                                                                Page 42 of 100
     KEY PERSONS              Resume/reference                           Description of Qualifications
                                 attached?
                                Yes      No
Contractor Technical
Lead




                                   Evaluator Comments:                                             Points          Points
                                                                                                  Possible:       Awarded:




Contractor Technical Lead - provides technical leadership and guidance to Contractor’s technical staff to accomplish
project objectives effectively and efficiently. Coordinates the work of technical resources to facilitate the completion of
assigned tasks. Works with Contractor Project Manager and stakeholders to develop plans and schedules and manages
the work of the technical teams. Responsible for responding to requests from DMV Technical Lead in support of the SCM
project. May facilitate work sessions with DMV Technical Lead to validate requirements and will develop specifications,
design, and other technical deliverables.
Minimum Requirements: 3 - 5 years of IT Technical Lead experience. Experience should include a minimum of two
successful projects that involved implementing the product being proposed in response to this RFP.

                                                                                                 Page 43 of 100
      KEY PERSONS              Resume/reference                          Description of Qualifications
                                  attached?
                                 Yes      No
Systems Engineer :




                                     Evaluator Comments:                                               Points       Points
                                                                                                      Possible:    Awarded:




Systems Engineer - responsible to co-ordinate all aspects product development including validating requirements,
proposing solution design and workflow process changes, configuring the product to meet all requirements, testing,
troubleshooting, and participating in implementation activities. Systems Engineer will be the key technical contact that co-
ordinates across multiple teams within the company from project planning through deployment and is responsible to
implement system features required to meet objectives of the SCM project.
Minimum Requirements: 3 - 5 years of technical analysis, design, and implementation experience. Experience should
include a minimum of two successful projects that involved implementing the product being proposed in response to this
RFP.




                                                                                                  Page 44 of 100
      KEY PERSONS              Resume/reference                          Description of Qualifications
                                  attached?
                                 Yes      No
Implementation Engineer:




                                     Evaluator Comments:                                              Points       Points
                                                                                                     Possible:    Awarded:




Implementation Engineer - responsible to co-ordinate all aspects of the product installation in ODOT DMV LPAR, and
product configuration in test and production environments as required for the project. Will train and support SDC and
DMV staff in initial installation and provide mentoring and training for ongoing operations, support, troubleshooting and
problem solving.
Minimum Requirements: 3 - 5 years of implementation experience which includes a minimum of two successful projects
that involved implementing the product being proposed in response to this RFP.


                                                                                                 Page 45 of 100
      KEY PERSONS              Resume/reference                           Description of Qualifications
                                  attached?
                                 Yes      No
Training Specialist:




                                    Evaluator Comments:                                              Points          Points
                                                                                                    Possible:       Awarded:




Training Specialist – responsible for proposing a training strategy and specific plan to and delivering training to all roles
required to use, support, and maintain the system. Responsible for developing materials to support work process
changes and support transition activities.
Minimum Requirements: 3 - 5 years of technical training experience which includes a minimum of two successful projects
that involved implementing the product being proposed in response to this RFP




                                                                                                   Page 46 of 100
                      PROPOSER RESPONSES TO SCOPE OF WORK
                          Points Possible: 75 Points Awarded
Instructions: Proposer shall respond to the following questions to provide DMV with an understanding of the
project effort and activities to be accomplished, based on Proposer’s experience.

1. Describe your proposed solution and how it will integrate into DMV’s technical environment. Describe any
   areas where your product is not compatible with DMV’s technical infrastructure and describe how you plan
   to mitigate that.
RESPONSE:                                         EVALUATOR COMMENTS:                                   POINTS
                                                                                                        AWARDED




2. Describe how your product will provide software configuration management for applications in DMV’s
   mainframe, client/server, and web platforms.
RESPONSE:                                         EVALUATOR COMMENTS:                                   POINTS
                                                                                                        AWARDED




3. Describe the approach and methodology you are recommending to convert DMV from its current state to a
   fully implemented Software Configuration Management solution supporting the platforms required and
   DMV requirements as outlined in the RFP. Include in your response:
       •   Specific successful experience implementing your SCM solution to support multi-platform
           environments similar to DMV.
       •   How you will begin the engagement with DMV, and how you will analyze, plan, execute, and control
           all activities to deliver a system that meets or exceeds DMV requirements.
       •   Estimated timeframe for the total project, including estimates for each phase of the project.
       •   Estimated DMV staffing requirements by role and length of participation in the project.
       •   Implementation considerations including products, utilities, databases currently in use at DMV that
           would be converted, modified, or eliminated by implementing your solution.
       •   A description of your conversion and implementation strategy and what products you have to
           support this effort.
       •   A description of your methods for validating the conversion of components and testing the product.

RESPONSE:                                         EVALUATOR COMMENTS:                                   POINTS
                                                                                                        AWARDED




                                                                                       Page 47 of 100
4. Describe the software product or products you are recommending as a DMV solution. Include in your
   response the following:
       •   Software product name(s) and version/release/modification level(s) for each
       •   Any prerequisite software or hardware required for implementation and ongoing operations
RESPONSE:                                          EVALUATOR COMMENTS:                                   POINTS
                                                                                                         AWARDED




5. Describe if DMV would be able to perform a proof of solution in a separate environment before full
   implementation. If not, what technical (or other) constraints would prevent it?
RESPONSE:                                          EVALUATOR COMMENTS:                                   POINTS
                                                                                                         AWARDED




6. Describe the estimated DMV staffing level by role required to support your product post implementation.
   Include in your response the following:
       •   Ongoing support/maintenance activities and frequency of each activity
       •   Skill sets required to adequately support the product(s) included in your proposed solution
       •   Considerations DMV needs to be aware of related to support and maintenance of the product(s)
           you propose to meet DMV needs.

RESPONSE:                                          EVALUATOR COMMENTS:                                   POINTS
                                                                                                         AWARDED




7. Describe how you would ensure knowledge transfer, training, coaching, and support to ensure that DMV
   acquires skills and proficiency to fully utilize and support the SCM product and all related components of
   your proposed solution once the project has ended.
RESPONSE:                                          EVALUATOR COMMENTS:                                   POINTS
                                                                                                         AWARDED




                                                                                        Page 48 of 100
8. Describe any other requirements or considerations that DMV needs to be aware of to fully implement your
   SCM solution and to support and maintain the product post implementation.
RESPONSE:                                        EVALUATOR COMMENTS:                                  POINTS
                                                                                                      AWARDED




                                                                                     Page 49 of 100
CONTRACTOR’S SOFTWARE LICENSE AGREEMENT
         (software license to be attached here)




                                                  Page 50 of 100
PROPOSER RESPONSES RELATED TO WARRANTY AND SUPPORT


                           PRODUCTS AND SERVICES WARRANTY

                               Points Possible: 25 Points Awarded

Instructions: Define the product and services warranty period and service levels to be provided in support of an
operational SCM system. Please attach your Standard Warranty documents, if any.
The warranty period will begin at final acceptance and should be provided at no additional charge. Minimal
acceptable warranty period is 90 days. Longer Warranty periods will receive additional points.
The successful Proposer must agree to a warranty period that covers any functional and operational defects
that are not in compliance with the approved design and specifications and DMV’s technology standards at the
time of release.


RESPONSE:                                          EVALUATOR COMMENTS:                                    POINTS
                                                                                                          AWARDED




                                                                                         Page 51 of 100
                                   MAINTENANCE & SUPPORT
                               Points Possible: 25 Points Awarded

                                    Maintenance and Support Agreement
                          (Maintenance and Support Agreement to be attached here)


Instructions: Describe how system maintenance support on a yearly basis following the end of the Warranty
Period will be provided.

ATTACH ANY MAINTENANCE AND SUPPORT AGREEMENT THAT YOU TYPICALLY OFFER A
CUSTOMER.


Maintenance/Support Agreement must cover repairs of any defects in the system and periodic enhancements
to the system including, but not limited to 24 x 7 technical support and be able to respond to requests within 4
hours.

24 x 7 support and be able to respond to problem reports based on severity level. An example of the support
level requirement is provided below:

  Severity 1: Issue represents a problem in the SCM system which includes a complete loss of service, either
  temporary or permanent. No workaround exists. The customer cannot continue essential operations.

  Severity 2: Issue represents a high-impact problem in the customer's SCM system. Essential operations
  are compromised, but a temporary workaround exists which allows for continued operations.

  Severity 3: Issue represents a minor-impact problem in the customer's SCM system. Software programs
  feature failure or may be working differently than documented. Temporary workaround exists which allows
  for continued operations.

  Severity 4: Errors in the documentation have occurred. Contractor shall resolve these problems with the
  next release of the Software programs documentation.

• Provide maintenance agreement period options, such as 1, 3, 5, or 10 years which includes:
   o   Software patches
   o   Software upgrades
   o   Hardware replacement/repair for failed components
   o   Preventive maintenance/upkeep

RESPONSE:                                           EVALUATOR COMMENTS:                                   POINTS
                                                                                                          AWARDED




                                                                                         Page 52 of 100
                                  TECHNICAL ENVIRONMENT
                              Points Possible: 35 Points Awarded

Instructions: Document your understanding of the current DMV technical environment and products used today
to manage source on all DMV platforms. Additionally, describe any differences between DMV requirements
and the Contractor’s solution including, but not limited to:
• Hardware/Software prerequisites (if any), understanding that the product must run on the technology
  platform defined in WOC #1, Statement of Work.
• Configuration requirements;
• Migration requirements for all programs, libraries, databases, utilities, and any other components or
  process that may be impacted;
• Database set-up requirements;
• Process changes required by DMV in order to utilize the SCM solution;
• Changes in Roles and Responsibilities and a description of what and how they should change and related
  transition activities;
• Microfocus mainframe access is used to communicate with the Microfocus Mainframe Express (MFE)
  product which is also used to do mainframe development on the workstation.


RESPONSE:                                         EVALUATOR COMMENTS:                                   POINTS
                                                                                                        AWARDED




                                                                                       Page 53 of 100
                                   Functional Requirements
                             Points Possible: 210 Points Awarded

The required functionality of DMV’s SCM solution is described on the following pages. The requirements
include mandatory and desirable features by groupings such as Source Management, Migration Workflow, and
Administration.

INSTRUCTIONS: Proposers must respond to each requirement with a statement indicating their ability to meet
or exceed the stated requirement whether mandatory or desirable. And if the Proposer can’t meet a
requirement, they must indicate that they cannot meet the requirement by providing a written comment.

Proposer must describe in detail sufficient to allow the Evaluation Committee to award points based on a clear
understanding of the offer.

Circle the items that your solution can meet and describe how your solution meets the item.

Any mandatory or desirable items that are not also accompanied by a description will not be assigned
a score.




                                                                                       Page 54 of 100
RFP #730-24226-10
Source Management
                                                          Ranking:
                                                            “M”       Proposer Responses to include Proposer’s
Req.                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
                  Requirement Description
 #                                                          “D”       section must be addressed to be considered         comments               Points
                                                          Desirable   Responsive:


Check-In/Check-Out
101      Provide the capability to check out software        M
         components from any environment to any
         other environment.
102      Enforce check-in/check-out procedures for           M
         source components.
Concurrent/Parallel Development
103      Provide the capability to support concurrent        M
         development.
Editor
104      Provide the capability to edit, update and          M
         save the software components checked-
         out into the development environments.
105      Have the ability to browse any stored               M
         version of a software component.
106      Store software components in a space                D
         efficient fashion.
Versioning
107      Ability to store one version of the software        M
         component across multiple environments on
         Mainframe or server.
108      The SCM product should support versioning.          M
         Provide a description of how your SCM
         product does versioning.
109      Ability to store multiple versions of the same      D
         software component module in a single
         environment on the Mainframe or server.
Compiling
110      Provide the ability to automatically compile,       M
         link, and bind software components into the
         development environments.
111      Ability to build/compile a Full package.            M
112      Ability to build/compile a Partial package.         D

                                                                                                    Page 55 of 100
                                                      Ranking:
                                                        “M”       Proposer Responses to include Proposer’s
Req.                                                  Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
                Requirement Description
 #                                                      “D”       section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


Packages
113    Provide the ability to assemble/group             M
       software components into one to many
       package(s).
114    Ability to add or remove software                 M
       components from a package in a
       development environment.
115    Provide the capability to merge 2 or more         D
       packages into a single package.
116    Provide the capability to split a single          D
       package into 2 or more packages.
Branching
117    The SCM product will support branching.           M
Merging
118    The SCM product will support merging.             M
119    The SCM product should have the ability to        D
       automatically merge unambiguous logic
       (after the user review).
120    The result of a merge should always be a          D
       copy or temp work space of the originals,
       not overlays.
121    The product should allow the user to review       D
       the impact of a merge before an actual
       merge is done.
Impact Analysis
122    Ability to identify and resolve conflicts         D
       between components and packages.
123    Provide the ability to execute impact             D
       analysis research to determine the impact of
       a change to software components (Cobol,
       includes, DB2, Files, Triggers, etc…) across
       all systems and sub-systems and across all
       platforms (Main Frame, Client Server and
       Web).
124    Provide change impact analysis information        D
       over a selectable range of the software
       components.
                                                                                                    Page 56 of 100
                                                            Ranking:
                                                              “M”       Proposer Responses to include Proposer’s
Req.                                                        Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
                 Requirement Description
 #                                                            “D”       section must be addressed to be considered         comments               Points
                                                            Desirable   Responsive:


Graphical User Interface (GUI)
125    Provide a GUI to initiate mainframe change              D
       functions.
Tracking Changes
126    Automatically capture and track the                     M
       mainframe changes to components. (Cobol,
       Includes, JCL, Files).
127    Automatically capture and track the web                 D
       changes to application components. Sample
       file types - not an exhaustive list: Java
       (*.java, *.jsp, *.jsf); ColdFusion (*.cfc, *.cfm);
       MS Access (*.mdb, *.mde); Web (*.html,
       *.htm, *.txt, *.bmp, *.jpg).
Restoring
128    Provide the ability to restore prior stored             M
       versions of software components.
129    Provide the capability to re-generate any               D
       prior version of a software component and
       its dependencies.
Dependencies
130     The SCM product should allow developers                D
       to define application dependencies.
DB2
131    Automate Plan or Package Binding when                   M
       migrating DB2 components to different
       environments.
132    Synchronize DB2 application components,                 M
       including SQL program source, DBRMs,
       BIND statements, program load modules
       and application plans, and application
       packages.
133    Manage DB2 application components,                      D
       including DB2 Stored Procedures,
       DCLGEN’s, and User Defined Functions
       (UDFs).
134    Provide the ability to assess the impact of a           D
       change to a DB2 component before the
       change is implemented.
                                                                                                          Page 57 of 100
                                                     Ranking:
                                                       “M”       Proposer Responses to include Proposer’s
Req.                                                 Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
               Requirement Description
 #                                                     “D”       section must be addressed to be considered         comments               Points
                                                     Desirable   Responsive:


135    Manage DB2 application components as             D
       they progress through the application
       development life cycle.

Migration Workflow
                                                      Ranking
                                                        “M”      Proposer Responses to include Proposer’s
                                                     Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#            Requirement Description
                                                        “D”      section must be addressed to be considered         comments               Points
                                                     Desirable   Responsive:


Environments
 201     The SCM product should support multiple        M
         test and acceptance environments on
         mainframe, client/server, and web
         platforms.

         Include in your response which platforms
         the product work in and how many
         environments the products will support on
         these platforms.
 202     The SCM product should support multiple        M
         migration paths on mainframe,
         client/server and web platforms.

         Include in your response which platforms
         your product works in and how many
         migration paths the product will support
         on these platforms.
 203      The SCM product should provide the            M
          ability create, modify, and delete
          migration paths.
 204      The SCM product should support                D
          development-mode-based migrations,
          such as project migrations, maintenance
          migrations, and emergency migrations.
          The SCM product should also support
          development-mode-based migration
          paths, which include project paths,
          maintenance paths, and emergency
          paths.
                                                                                                   Page 58 of 100
                                                         Ranking
                                                           “M”      Proposer Responses to include Proposer’s
                                                        Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#             Requirement Description
                                                           “D”      section must be addressed to be considered         comments               Points
                                                        Desirable   Responsive:


 205       The SCM product should support the              D
           use of the product by other IS
           departments within ODOT other than
           DMV. Other IS departments would
           initiate their own effort to configure the
           product in their instance.
 206       The SCM product should support the              D
           creation, modification, and deletion of
           development-mode-based release
           packages, such as packages for project
           migrations, maintenance migrations, and
           emergency migrations.
Components
 207       The SCM product should support                  D
           migration of application documentation
           and test documentation for all
           environments.
Packages
 208       The SCM product should support                  M
           multiple release packages.
           Include in your response how many
           release packages the product will
           support.
 209       The SCM product should support                  M
           multiple components per release
           package.
           Include in your response how many
           components per release package the
           product will support.
 210       The SCM product should support the              M
           creation, modification, and deletion of
           release packages for any platform and
           any site. The SCM product should also
           support the creation, modification, and
           deletion of release packages for multiple
           platforms.




                                                                                                      Page 59 of 100
                                                    Ranking
                                                      “M”      Proposer Responses to include Proposer’s
                                                   Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#         Requirement Description
                                                      “D”      section must be addressed to be considered         comments               Points
                                                   Desirable   Responsive:


211    The SCM product should enable a                D
       release package to be associated with a
       migration path. The package should
       control every migration of this package's
       components along the path. The
       package should not need to be manually
       changed for any migration.
212    The SCM product should enable local            D
       task/activity identifiers (such as the
       Change Request identifier and the
       Request for System Services identifier)
       to be assigned to a release package.
213    The SCM product should enable free-            D
       format text to be added to, modified in,
       or deleted from a release package, with
       the text being used to provide additional
       information about the migration.
214    The SCM product should monitor and             D
       control the concurrent migration of
       multiple release packages.
       Include in your response how many
       release packages the product can
       concurrently migrate.

215    The SCM product should consider                D
       interdependencies between components
       when assigning components to a
       release package, and the SCM product
       should provide warnings if the
       interdependencies are not addressed.
       One such interdependency is a copy
       member that defines a record which is
       written by one program and read by
       another. A change to the data structure
       of the copy member could affect both
       programs and could necessitate them
       both being in the release package.




                                                                                                 Page 60 of 100
                                                      Ranking
                                                        “M”      Proposer Responses to include Proposer’s
                                                     Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#           Requirement Description
                                                        “D”      section must be addressed to be considered         comments               Points
                                                     Desirable   Responsive:


 216     The SCM product should support                 D
         auditing of the components within a
         release package, ensuring that none are
         missing, and the SCM product should
         support auditing of the attributes of the
         components. The auditing could be
         conducted at any time during the life of
         the package, including immediately prior
         to migration. The SCM product should
         support auditing of partial migration
         release packages.
 217     The SCM product should support                 D
         auditing of release packages for any
         platform, as well as auditing of release
         packages for multiple platforms.
Approvals
 218    The SCM product should enable an                M
        approver to be added to, modified in, or
        deleted from a release package at any
        time during the life of the package, until
        migrated to the Production environment.
 219     The SCM product should support the             M
         electronic approval of release packages.
         The approval process could require
         some approvals to be performed in a
         specific order and could allow other
         approvals to be performed in any order.
         The process could also allow certain
         approvals to be performed by any
         member in a group of approvers.
 220     The SCM product should require that all        M
         approvals be obtained prior to the
         release package being migrated.
 221     The SCM product should send an                 M
         electronic notification to selected
         individuals when any approver rejects
         the migration of a release package.
 222     The SCM product should support the             M
         automated approval of migrations.




                                                                                                   Page 61 of 100
                                                         Ranking
                                                           “M”      Proposer Responses to include Proposer’s
                                                        Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#             Requirement Description
                                                           “D”      section must be addressed to be considered         comments               Points
                                                        Desirable   Responsive:


 223        The SCM product should send                    D
            notifications when the approvals are
            past due. The threshold on the timeline
            should be configurable.
 224        The SCM product should support a               D
            "freeze" on changes to a release
            package while the package is being
            approved. The freeze should remain in
            effect until the package is migrated or
            the package is "unfrozen". When either
            condition occurs, all approvals for the
            current migrated of the release package
            are reset.
 225        The SCM product should enable                  D
            approvers to be both manually assigned
            to a release package and automatically
            assigned to a release package based on
            package attributes. Typical package
            attributes include: a.) the components
            contained in the package, b.) the
            application to which a package's
            components belong, or c.) the
            development-mode migration for the
            components (project migration,
            maintenance migration, or emergency
            migration).
Migration
 226        The SCM product should support the             M
            migration of migration-type-based
            release packages. One migration type
            involves moving the source components
            to a source repository and then
            compiling and linking the moved
            programs into the source repository's
            load libraries. Another migration type
            involves moving the source components
            to a source repository and then moving
            the program load modules to the source
            repository's load libraries. The
            difference between these two migration
            types is that the first type re-generates
            the program load modules while the
            second type simply moves them.
                                                                                                      Page 62 of 100
                                                   Ranking
                                                     “M”      Proposer Responses to include Proposer’s
                                                  Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#         Requirement Description
                                                     “D”      section must be addressed to be considered         comments               Points
                                                  Desirable   Responsive:


227    The SCM product should send an                M
       electronic notification to defined
       individuals when a release package is
       successfully or unsuccessfully migrated.
228    The SCM product should support an             M
       online review of the completeness of any
       prior migration.
229    The SCM product should ensure that            M
       load modules and the source
       components that generate the load
       modules are always migrated together in
       cases where the source components are
       moved, rather than compiled.
230    The SCM product should support                M
       migrations to any platform.
231    The SCM product should allow compile-         D
       and-link options to be defined and
       modified for each program as needed.
232    The SCM product should support the            D
       release package either requiring or
       bypassing the re-compiling and re-
       linking of all programs that reference a
       modified Include Member. The
       require/bypass choice should be
       available for each Include Member.
233    The SCM product should be able to             D
       initiate the appropriate DB2 binds
       needed to enable migrated load
       modules to be executed in other
       environments.
234    The SCM product should enable                 D
       installation date-and-time windows to be
       both manually assigned to a release
       package and automatically assigned to a
       release package based on the
       application to which the package's
       components belong (scheduled
       migrations).
235    The SCM product should require                D
       minimal human intervention to affect the
       migration process.



                                                                                                Page 63 of 100
                                                     Ranking
                                                       “M”      Proposer Responses to include Proposer’s
                                                    Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#         Requirement Description
                                                       “D”      section must be addressed to be considered         comments               Points
                                                    Desirable   Responsive:


 236    The SCM product should provide a               D
        standard method for implementing
        migrations and should ensure that like
        items (e.g. Programs, Include Members,
        Jobs, or Control Members) are
        processed the same way.
 237    The SCM product should support                 D
        complex migrations, which could have
        stop/break points and restart/continue
        points and could involve dependencies
        on system changes (e.g. CICS or DB2
        modifications) or on changes to other
        platforms.
 238    The SCM product should support both            D
        immediate and deferred migration on
        final approval, where deferred migration
        is controlled by an automated
        scheduling utility.
 239    The SCM product should enable a                D
        migration to be scheduled to take place
        either at a given date and time or within
        a predefined migration window, which
        can be based on application group.
 240    The SCM product should enable                  D
        independent migrations to be performed
        in sequence and in parallel.
 241    The SCM product should interface with          D
        application scanning tools, such as
        IBM's AppScan, and JCLCHECK.
 242    The SCM product should be able to               D
        interface with CICS to issue commands,
        like new copy. DMV currently uses a
        product (CICS CEMT)from MacKinney
        Systems that is used to issue CICS
        commands via batch.
 243    The SCM product should support                 D
        migrations to multiple platforms.
Program Regeneration




                                                                                                  Page 64 of 100
                                                       Ranking
                                                         “M”      Proposer Responses to include Proposer’s
                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#           Requirement Description
                                                         “D”      section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


 244      The SCM product should be able to              D
          recreate any migration that occurred on
          a prior date and time. The application
          components in the recreated migration
          should be identical to the corresponding
          components in the original migration.
Migration Reversal
 245      The SCM product should support back            M
          out and restore for any migration. This
          process should produce correct results
          and should be fast and simple, requiring
          minimal intervention.
Partial Migration
 246      The SCM product should support the             D
          creation, modification, and deletion of
          release packages for partial migrations.
          A partial migration release package is
          created from another release package
          by selecting one or more components
          from the original package. A partial
          migration package could be created
          from another partial migration package.
          The SCM product should establish a
          relationship between the original
          package and the partial migration
          package, and the SCM product should
          coordinate migrations for the two
          packages. If a partial migration is
          performed prior to an original migration,
          the SCM product should confirm
          whether any components migrated in the
          partial migration need to also be
          migrated in the original migration.
Test JCL Customization




                                                                                                    Page 65 of 100
                                                      Ranking
                                                        “M”      Proposer Responses to include Proposer’s
                                                     Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#          Requirement Description
                                                        “D”      section must be addressed to be considered         comments               Points
                                                     Desirable   Responsive:


 247     The SCM product should automate the            D
         process of identifying appropriate
         changes in production source
         repositories (i.e. typically changes to
         Jobs and Control Members) and
         migrating these changes to the proper
         test source repositories. The migrations
         should be done in parallel once the
         production migration is successful. The
         process should use the JCL conversion
         rules that are specific to our test
         environments.
Microfocus Mainframe Express (MFE) Support
 248     The SCM product should synchronize             D
         the contents of mainframe-based source
         repositories of mainframe components
         with the contents of correlated PC-based
         source repositories of mainframe
         components. The synchronization
         should support functions such as check-
         out and migration.
Miscellaneous Functionality
 249     The SCM product should electronically          M
         notify selected individuals associated
         with an initial source repository when a
         component is checked out to another
         source repository and that component
         affects one or more components in the
         initial source repository. The effect can
         be direct (as when the checked-out
         component is contained in the initial
         library).
 250     The SCM product should record every            M
         relevant change to every component in
         every source repository. The record of
         changes should identify what was
         changed, when it was changed, who
         changed it, and why it was changed.
         The record should contain current status
         information as well as data about all
         check-outs and all migrations.

                                                                                                   Page 66 of 100
                                                       Ranking
                                                         “M”      Proposer Responses to include Proposer’s
                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#          Requirement Description
                                                         “D”      section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


251     The SCM product should enable an                 M
        administrator to override the migration
        path in a release package.
252     The SCM product should record every              M
        relevant characteristic of the migration of
        every component in a release package.
        The recorded data should also contain
        current status information for every
        component in the package.
253     The SCM product should provide a                 M
        means to prevent source component
        updates from being lost when the
        components are being modified by
        multiple development teams working in
        parallel and the components are
        contained in different release packages.
254    The SCM product should allow only a               M
       selected group of individuals to migrate
       release packages.
255     The SCM product should electronically            D
        notify selected individuals associated
        with an initial source repository when a
        component is checked out to another
        source repository and that component
        affects one or more components in the
        initial source repository. The effect can
        be indirect (as when the checked-out
        component is included in or referenced
        by the component in the initial library).
256     The SCM product should record                    D
        environment characteristics (server
        name, port requirement, etc.) by
        application for every migration that
        involves a client server platform.
257     The SCM product should provide a                 D
        browser-based interface.




                                                                                                    Page 67 of 100
Administration
                                                       Ranking
                                                         “M”      Proposer Responses to include Proposer’s
                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#           Requirement Description
                                                         “D”      section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


RACF
 301    RACF and/or Active Directory must be             M
        used to ensure the confidentiality and
        integrity of the SCM files and data bases.
 302    The product should use RACF and/or               M
        Active Directory to assign different access
        levels based on user functions.
 303    Capability to use RACF and/or Active             M
        Directory for identifying, authenticating,
        and authorizing access to the SCM
        system.
 304    Provide the capability to quickly limit or       M
        expand access rights and privileges to
        specific functions within the SCM product.
Roles and Functions
 305    The SCM product should enforce a                 M
        separation of duties, and needs to be
        able to support the following roles and
        functions.
        • Product administration
        • Security
        • Librarians
        • Developers
        • QA
        • Approvers
        The duties in these areas need to be able
        to be executed independently and
        simultaneously as defined in DMV’s
        software life cycle.




                                                                                                    Page 68 of 100
                                                       Ranking
                                                         “M”      Proposer Responses to include Proposer’s
                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#            Requirement Description
                                                         “D”      section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


 306    The SCM product should not severely              D
        limit the number of individuals that might
        support the defined DMV life cycle
        functions.
        Include in your response the limitation (if
        any) for the number of individuals that
        can be assigned to any type of role, i.e.,
        Approver, Librarian, and Developer.
Users
 307    Provide the capability to identify users         D
        who are logged into the system, on real-
        time basis.
 308    Provide the capability to terminate user’s       D
        connection for maintenance or
        emergency purposes.
Source Control
 309    Ensure that the change package unique            D
        identifier cannot be altered or destroyed
        by any users unless the product
        administrators are asked to modify or
        delete it.
Backup and Recovery
 310    Ability to backup components.                    M
 311    The SCM product should be able to                M
        recover from system and SCM-product
        failures, returning quickly to its normal
        operating state and experiencing no loss
        of data.
Job Scheduler
 312    The SCM product should have capability           D
        to communicate to DMV’s job scheduler.
Compiles and Developers Tools
 313    The SCM product will interface with IBM’s        M
        SYSDEBUG, SYSADATA and LANGX
        listing files for the IBM Problem
        Determination Products.

                                                                                                    Page 69 of 100
                                                        Ranking
                                                          “M”      Proposer Responses to include Proposer’s
                                                       Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#            Requirement Description
                                                          “D”      section must be addressed to be considered         comments               Points
                                                       Desirable   Responsive:


 314     Support all language processing facilities       M
         that support the currently defined IBM
         compilers used in the ODOT LPAR.
 315     The SCM product should not force all             M
         programs that share copybook or
         includes to be compiled.
Ticket Tracking Systems
 316     The SCM product should be able to                D
         retrieve information from Alexsys
         database (DMV’s maintenance log).
 317     Capability to retrieve information from the      D
         DMV Remedy database. Remedy is the
         system used for logging and tracking
         customer and end-user problems.
         Remedy is not used for SDLC defect
         tracking or problem management.
Graphical User Interface (GUI)
 318     The SCM product should provide an                D
         Integrated Development Environment
         (IDE) preferably and Eclipse based
         interface. The IDE will be used to do
         software development on the workstation.
Electronic Forms
 319     Should be able to send email notifications       D
         in a format compatible with Microsoft
         Outlook.
Conversion Tools
 320     As part of the installation the vendor will      M
         provide the necessary tools and
         processes to convert from PANVALET
         into the vendor’s desired component
         repositories; if the SCM product uses
         PANVALET as a component, the vendor
         will provide a method to interface to
         ensure the product functions
         appropriately in the DMV environment.



                                                                                                     Page 70 of 100
                                                       Ranking
                                                         “M”      Proposer Responses to include Proposer’s
                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#           Requirement Description
                                                         “D”      section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


 321     Ability to convert current components by        M
         mass conversion (if conversion is
         needed).
 322     Conversion of existing software                 D
         components should not be required in
         order to begin a pilot.
Scalability
 323     The SCM product should have the                 M
         capability of supporting multiple business
         lines within the same mainframe LPAR.
         All data and processes should be able to
         exist individually with no impact on each
         other.
 324     Easily allow for the addition of new            M
         application systems and their
         components (in-house developed and
         purchased) that DMV would like to be
         managed by the SCM product.
 325     The SCM product should provide facilities       D
         that could be used to integrate with
         functionality of new software types and
         development technologies. An example
         would be moving to more of a true SOA
         architecture and build/migration process.
 326     The SCM product should allow DMV’s in-          D
         house built applications to interact with
         the product to add additional functions to
         the product.

Reporting and Auditing
                                                       Ranking
                                                         “M”      Proposer Responses to include Proposer’s
                                                      Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#           Requirement Description
                                                         “D”      section must be addressed to be considered         comments               Points
                                                      Desirable   Responsive:


Reporting
 401     Detailed report on all migrations.              M
         Please provide samples.
                                                                                                    Page 71 of 100
                                                   Ranking
                                                     “M”      Proposer Responses to include Proposer’s
                                                  Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#          Requirement Description
                                                     “D”      section must be addressed to be considered         comments               Points
                                                  Desirable   Responsive:


402    Detailed report on all backouts.              M
       Please provide samples..
403    Provide audit report that lists who, why      M
       and when details on checked out /
       migrated components.
       Please provide samples.
404    Summary and detail reports for                D
       components:
       •   Status
       •   History
       •   Locations
       •   Changes
       •   Counts/for specified period
       Please provide samples.
405    Summary and detail reports for package:       D
       •   Status
       •   History
       •   Changes
       •   Listing of components
       Please provide samples.
406    Summary and detail reports for                D
       environments:
       •   Component listing
       •   Package listing
       Please provide samples.
407    Summary and detail reports for systems:       D
       •   Status
       •   History
       •   Locations
       •   Changes
       •   Counts/ for specified period
       Please provide samples.



                                                                                                Page 72 of 100
                                                          Ranking
                                                            “M”      Proposer Responses to include Proposer’s
                                                         Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#            Requirement Description
                                                            “D”      section must be addressed to be considered         comments               Points
                                                         Desirable   Responsive:


 408     Provide the capability to create                   D
         customized ad-hoc reports on all SCM
         activities, status and structures, and
         being able to save as permanent report.
 409     Any report produced needs to be                    D
         displayed online with printing options.
 410     Provide the ability to tailor reports to suit      D
         internal needs.
Stored Data
 411     DMV should be able to access the                   D
         information stored in the SCM product.
 412     Automatically capture and track the                D
         components that make up all executable
         modules, including the versions of those
         components and the locations from where
         they were included.
Data Compares
 413     Ability to compare 2 components between            D
         libraries or versions.
 414     Ability to compare 2 packages between              D
         libraries.
Scheduling
 415     Capture the JES2 sysout for CA-View.               D
 416     Ability to automate scheduled defined              D
         reports.
Emails
 417     Ability to prepare and send e-mails with           D
         attached SCM reports.
 418     Ability to enable or disable notifications.        D

Online Display
 419     Provide management dashboard for quick             D
         viewing of packages by category/type.




                                                                                                       Page 73 of 100
                                                         Ranking
                                                           “M”      Proposer Responses to include Proposer’s
                                                        Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#            Requirement Description
                                                           “D”      section must be addressed to be considered         comments               Points
                                                        Desirable   Responsive:


 420      On-line display to display the last set of       D
          changes made to a component, when
          they took place, who was responsible for
          them, and why they were made.

Product
                                                         Ranking
                                                           “M”      Proposer Responses to include Proposer’s
                                                        Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#            Requirement Description
                                                           “D”      section must be addressed to be considered         comments               Points
                                                        Desirable   Responsive:


Manuals
 501      Provide Product Implementation Guide.            M
 502      Provide User’s Manual.                           M
 503      Provide Quick Reference Guide.                   D
 504      Provide Glossary of terms.                       D
 505      Provide electronic version of all manuals        D
 506      Vendor will provide the data dictionary for      D
          their product.
Compatibility
 507      The SCM product must be able to                  M
          execute within the current SDC
          mainframe and server hardware and
          software environments and be compatible
          with any future changes to those
          environments during the life of the
          contract.
Software Prerequisites or Dependencies
                                          rd
 508      The vendor must list IBM and 3 party             M
          software that is needed to run their SCM
          product.
Upgrades/Releases
 509      Provide Support for Minor upgrade, Major         M
          Upgrade, Patches, and emergency
          upgrade.
                                                                                                      Page 74 of 100
                                                          Ranking
                                                            “M”      Proposer Responses to include Proposer’s
                                                         Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
 Req#             Requirement Description
                                                            “D”      section must be addressed to be considered         comments               Points
                                                         Desirable   Responsive:


 510       Vendor will provide implementation               M
           planning and assistance.
 511       The vendor will share the product                D
           upgrade information with ODOT for
           example, advance product
           announcements, technical release notes,
           end user release notes.
 512       Vendor will provide Pilot implementation         D
           support.
 513       Installation and implementation provided         D
           by the vendor.
Training
 514       Provide training support for DMV                  M
           personnel; such as:
           •   Mainframe Programmers/Analysts
           •   Web and Client/Server
               Programmers/Analysts
           •   Release Management
               Analysts/Managers
           •   Application Managers
           •   Operations & Production Managers
           •   System Administrators
           •   Database Administrators
           •   All other training required to
               understand, implement, and become
               proficient with product.
 515       Provide electronic copies of training            D
           materials.
Support
 516       Vendor will provide a copy of service level      M
           agreement.
 517       Vendor must provide on-line access to            M
           information about the product that is
           accessible via the Internet. Please
           describe the type of information that
           would be available online about the SCM
           product.
                                                                                                       Page 75 of 100
                                                      Ranking
                                                        “M”      Proposer Responses to include Proposer’s
                                                     Mandatory   ability to meet or exceed this requirement. This   Evaluation committee   Awarded
Req#            Requirement Description
                                                        “D”      section must be addressed to be considered         comments               Points
                                                     Desirable   Responsive:


 518    An established user group organization.         D
 519    Vendor must supply 24 X 7 support.              D
        Please describe the vendor product
        support, including availability of support
        via telephone, fax, Internet, etc.
Help and Documentation
 520    Provide on-line tutorial and help screens.      D




                                                                                                   Page 76 of 100
RFP #730-24226-10

                                  ATTACHMENT B – 2
                               PRICING PROPOSAL FORM
                      (To be provided in a separate sealed envelope)
                           Points Possible: 200 Points Awarded

Instructions: Complete the attached Pricing Form and submit with Attachment B-2.



                                             Pricing Form Final.xls



                               KEY PERSONS                             Inclusive Hourly Billing Rate
                                                                      $
         Contractor Project Manager:

                                                                      $
         Contractor Technical Lead:

                                                                      $
         Systems Engineer :

                                                                      $
         Implementation Engineer:

                                                                      $
         Training Specialist




                          WARRANTY                                           Length of Warranty in
                                                                                   Months:




                                                                                    Page 77 of 100
                              FINANCIAL BACKGROUND INFORMATION

Financial Statement/Fiscal Stability.
Briefly describe Proposer’s experience with, and current strategies for, ensuring that the Proposer conducts business in a
fiscally responsible manner and remains financially solvent through the proposed Contract term. Identify the individuals who
have fiscal responsibilities. Any Proposer that has generated financial statements shall submit copies for the most recent
period. If financial statements have not been generated, then Proposer may submit an audit or fiscal review by a
certified public accountant, or if the Proposer is a “new” business, a copy of a business plan completed within the
last year. This information will be used as part of the Responsibility review, no score will be given. If a proposal firm does
not meet the responsibility requirement the proposal shall be rejected.


RESPONSE:




                                                                                                    Page 78 of 100
RFP #730-24226-10


                                                          ATTACHMENT C
                                                       DRAFT WOC #1 for DMV

The following Work Order Contract is the Draft Work Order Contract # 1 expected to be executed
directly upon execution of the Price Agreement for products and Services for DMV:

                                                         WORK ORDER CONTRACT # 1
                                                        Price Agreement # ___________


This Work Order Contract (“WOC”) # 1 is between the State of Oregon, acting by and though its Department of
Transportation (“Agency”) and __________________ (“Contractor”). This WOC is placed against State of
Oregon Price Agreement #________. The terms and conditions of the Price Agreement apply to this
purchase.

1. PROJECT: Software Configuration Management for Driver and Motor Vehicles Division

2 WOC TERM: The WOC is effective upon the Effective date. The WOC expires on ____________.

3. COMPENSATION:________________


4. STATEMENT OF WORK for this WOC is attached and hereby incorporated by this reference.
Certification: The individual signing on behalf of Contractor hereby certifies and swears under penalty of perjury: (a) Contractor is not subject to
backup withholding because (i) Contractor is exempt from backup withholding, (ii) Contractor has not been notified by the IRS that Contractor is
subject to backup withholding as a result of a failure to report all interest or dividends, or (iii) the IRS has notified Contractor that Contractor is no
longer subject to backup withholding; (b) s/he is authorized to act on behalf of Contractor, s/he has authority and knowledge regarding
Contractor’s payment of taxes, and to the best of her/his knowledge, Contractor is not in violation of any Oregon tax laws (including, without
limitation, the following pursuant to OAR 150-305.385(6)-(B): For purposes of this certification, “Oregon tax laws” means the tax laws names is
ORS 305.380 (4), including without limitation the state inheritance tax, gift tax, personal income tax, withholding tax, corporation income and
excise taxes, amusement device tax, timber taxes, cigarette tax, other tobacco tax., 9-1-1 emergency communications tax, the homeowners and
renters property tax relief program and local taxes administered by the Department of Revenue (Multnomah County Business Income Tax, Lane
Transit District Tax, Tri-Metropolitan Transit District Employer Payroll Tax, and Tri-Metropolitan District Self-Employment Tax; (c) Contractor is
an independent contractor as defined in ORS 670.600; and (d) the supplied Contractor data is true and accurate.

CONTRACTOR:
By: ___________________________ Title: __________________ Date: ___________


ODOT:
By: ___________________________ Title: __________________ Date:___________


DEPARTMENT OF JUSTICE:
Approved By: ___________________________ Title: __________________ Date: ___________
(If required by OAR 137-045-0030 or OAR 137-045-0035)




                                                                                                                                Page 79 of 100
                                          STATEMENT OF WORK

                                                                           Work Order Contract # 1
A. INTRODUCTION AND PROJECT OBJECTIVES
The purpose of this first WOC project is to acquire and implement a Software Configuration Management
(SCM) solution to automate the process of changing and deploying software applications. This project will
introduce a standardized, automated, regulated discipline of managing, tracking, and configuring most aspects
of the application development process for DMV.
Implementation of a SCM solution must automate the application lifecycle, accelerate application development
and improve software quality and reliability.
The solution must support and integrate all platforms and architectures that currently exist to support DMV
business systems.
The product selected must support library management for source control and protection; version control to
prevent code regression; branching and merging capabilities; and must simplify recovery to prior versions of
source.
Other desired benefits resulting from implementation of an SCM solution include improved impact analysis
capabilities to determine potential effects of changes and configuration management to identify and maintain
component and system relationships. The product must automate many processes and reduce manual
intervention to move, promote and restore source code. Additionally, the solution must allow retirement of the
existing internally developed Library Tracking System and other components that will be replaced through
implementation of a SCM solution.
DMV’s objective is to acquire a product and complete implementation and rollout during the 2009-2011
biennium. Project activities include planning, analysis, installation, configuration, migration, work process
changes, testing, training/knowledge transfer and other activities required to ensure mastery of the product
prior to closing the project.

Background
DMV will address the limitations that exist in the current technical environment to be able to continue to modify
systems within state and federally mandated deadlines. Current manual processes and internally developed
library management products increase the time, complexity, and cost of each project and limit the number of
projects that can be active concurrently.
The need for improved processes and automated procedures has been known for many years, and a Software
Configuration Management project has been on the DMV/IS Strategic Plan since 2007.
The Oregon Secretary of State recently conducted an audit of application software controls and practices and
recommended implementation of a formal change management process that provides comprehensive source
code controls.
Quality assurance audits on large technology projects frequently result in a recommendation to implement
source code controls including check-in/check-out, branching, merging, and version management. They also
note that limitations of current products combined with the non-modular design of DMV’s core systems restricts
the number of developers and testers that can be working simultaneously.
DMV has made improvements in code management processes and expanded the technical architecture to
support an increased number of development and testing environments, and manual processes were improved
and standardized. The work that was completed should reduce the complexity of this project since procedural
documentation and architectural changes that would otherwise be part of the project effort were already
completed
Scope
This project will acquire and fully implement a Software Configuration Management solution to satisfy DMV’s
requirements. The proposed solution may consist of a single product or multiple products, but the solution
                                                                                          Page 80 of 100
must be tightly integrated with minimal complexity. Specifically, the product must ensure that mainframe,
client/server and web source can be managed using one integrated solution.

The project will modify work processes and existing procedures to simplify and automate workflow such as
code promotion activities and approvals. The project will also facilitate changes in roles and responsibilities to
support agreed upon SCM procedures.

The project will be accomplished by joint planning and participation between DMV and the selected Contractor.
DMV will provide management and oversight of the work performed by Agency staff to ensure that schedules
are met by the Contractor and that deliverables are received and satisfactory. The joint project team will
conduct planning, analysis, construction/configuration, migration, testing, implementation and all other activities
required to fully and efficiently implement the selected product.

The project will ensure compatibility with DMV systems and technical architecture and will support all
development, test, and production environments on the State of Oregon mainframe (only on the ODOT LPAR),
web, and client/server platforms.

The project will use project management methodologies and IT governance to comply with state standards and
procedures. The selected Contractor shall produce deliverables defined in the SOW.
                                            Technical Environment
DMV’s systems run on multiple platforms. The majority of DMV systems run on a mainframe and fewer are
client/server and web systems. The SCM product must be able to execute within the current SDC hardware
and software environments for the mainframe and servers, and the product must be compatible with any future
upgrades to these environments during the life of the contract. A summary of DMV’s technical environments
follows:

Mainframe:
• DMV systems run on the SDC IBM 2097-504 z10 running 1675 MIPS which represents the entire State
  capacity
• DMV runs on the z10 mainframe running z/OS 1.9 and JES2 on the ODOT LPAR which is one of three
  LPARS on the State mainframe
• The majority of applications are written in COBOL (executing under LE), Assembler, and Easytrieve/Plus
  (embedded in JCL, not compiled).
• CICS Transaction Server (release 3.1) hosts the online applications.
• Application code is stored using Panvalet.
• Mainframe access is through TSO/ISPF and CICS services.
• Microfocus mainframe access is used to communicate with the Microfocus product Mainframe Express
  (MFE) which is also used to do mainframe development on the workstation.
• Application development and maintenance is done through Panvalet on the mainframe.
• Library and compile services on the mainframe are presented via REXX and CLIST routines.
• Online applications use IBM mapping support (BMS) via 3270 green screen presentations.
• Primary data storage: IBM DB2 (Version 8), VSAM, and QSAM files.
• Developers utilize TSO/ISPF utilities and IBM File Manager to work with data.
• DB2 is accessed through IBM File Manager, DB2 mainframe utilities, CA Platinum.
• Testing and debugging products consist of IBM Debug and IBM Fault Analyzer for online and batch.
• Security is managed using RACF.
• Java source runs on UNIX Systems Services Heirarchial File System (UNIX/HFS)
• IBM Application Performance Analyzer is used for performance monitoring.
• Stress testing is done using IBM Workload Simulator.
• Data disguise is done using IBM Optim with Test Data Management.
• Printed forms and other specialized printing is done using PSF.
• Report archiving and viewing uses CA-View.
• JCLCHECK utility is used to check syntax on batch Job Control statements.
                                                                                           Page 81 of 100
•   CA-1 Tape Management System is used to manage tape volumes.
•   Batch job scheduling is handled using CONTROL-M.
•   IBM Omegamon is used to monitor CICS.
•   SIM2000 date simulation product is used to future date mainframe batch and CICS testing.
•   MacKinney “Batch to CICS” is used to initiate CICS commands via batch jobs.

Client/Server and Web:
• Applications are written in Cold Fusion, JavaScript, Active Server Pages (ASP), Java, HTML, and MS
   Access.
• Applications use DB2 Connect to access DB2 on the mainframe.
• Application development and maintenance is done using Macromedia Dream Weaver, Websphere studio,
   and Visual studio.
• Security vulnerabilities are detected by using IBM AppScan.
• Application migration is performed by RepliWeb R-1.

Work Station:
• Workstations currently are on the Microsoft XP Professional SP3 platform. ODOT’s strategy is to upgrade
  to Windows 7 in two years.
• Existing servers are typically on the Windows Server 2003 platform, with newly deployed servers being
  Windows Server 2008R2.
• Attachmate is used for 3270 terminal emulation.
• WebSphere on the mainframe is used by Client Server applications to access mainframe resources.
• DB2 is accessed through a Windows based application called AQT via DB2 Connect.
• Mainframe Application development and maintenance is done through MicroFocus Mainframe Express
  (version 3.1) on workstations.
• Testing and debugging products are provided by the MicroFocus developer’s set.
• MicroFocus Revolve is used for mainframe impact analysis.
                               DMV Source Control Products and Processes
SCM Products
• Web products currently in use are Concurrent Versioning System (CVS) and Visual SourceSafe.
• Web Application migration is done using RepliWeb R-1 Console.
• Library Tracking System (LTS). An internally developed mainframe application is our current mainframe
  SCM system. This product is an ISPF Dialog/REXX based application that supports mainframe source
  migrations.

SCM Environments, Procedures and Workflows (the following are attached as Exhibits at the end of
this RFP)
• Environment regions and libraries,
• Environment chart,
• SCM coordinator Rules and Responsibilities,
• Migration Paths,
• Migration process flow for Projects,
• Migration process flow for Maintenance,
• Migration Procedures for ISPF Modules,
• Migration Procedures for JCL modules,
• Migration Procedures for EGOV applications,
• Migration Procedures for MS Access applications,
• Migration Procedures for Coldfusion applications,
• Application Source Component Counts,
                           Methodology and Project Documents Requirements
Agency IT Delivery Methodology – Agency’s Information Systems sections uses a system development
methodology based upon Fujitsu Consulting’s Macroscope product. Contractor shall use and model
                                                                                      Page 82 of 100
Deliverables based on this methodology as requested by Agency’s Project Manager. The letters and numbers
corresponding to the methodology are in parenthesis following the definition titles, i.e. (P4200). Agency will
provide Contractor with access to the templates on the Agency’s Intranet.
Documentation Standards – The Contractor shall create documents, unless otherwise approved in writing by
Agency’s Project Sponsor using standard Agency office automation products.
Contractor shall use the provided templates as guidelines for Project Deliverables. The templates represent
minimum information required for each deliverable. Final Deliverable contents will be mutually agreed upon in
writing between the Agency and Contractor.
Change Control – The Contractor shall use existing Agency issue and change management processes
including standard formatted documents coordinated through established approval processes. Agency will
provide sample forms, approval process and related information to implement change control.
Reassessment – Contractor and Agency shall reassess Project Scope, schedule, and tasks after completion
of Task 2.2, Functional and Technical Specifications. Contractor shall draft and submit to Agency the updated
Project Scope, schedule and tasks that have been negotiated. If needed, the parties shall prepare and submit
a change order per Appendix a, Price Agreement Section 17.15.3 and amend the WOC pursuant to the Price
Agreement.
                                            Agency Responsibilities
Office Space
Work will be primarily performed at Contractor’s offices and on-site at DMV HQ, Salem, OR. If requested by
Contractor, Agency will provide office space, desk, and chair, phone, and Agency security badges, at an
Agency facility in the Salem area for Contractor staff.

PC and Related Equipment
If requested by Contractor, Agency will provide an available workstation that can access the Agency network.

                                          Contractor Responsibilities
Project Cooperation
Contractor acknowledges that Agency may have separate contract(s) with other entities (i.e., contractors,
consultants or governmental agencies) involved with the project. Contractor shall support Agency's efforts to
create and maintain a cooperative working relationship between and among other entities involved in the
project, and their respective representatives, to further the interests of Agency to result in the project being
successfully completed on time and within budget.

Any Contractor tasks or deliverables which are contingent upon receiving information, resources, assistance,
or cooperation in any way from another entity (other than the Contractor Sub-contractors) as described in this
SOW must be subject to the following guidelines:

     •    At the first indication of non-cooperation, Contractor shall provide written notice to ODOT Contract
          Administrator of the specific acts or inaction indicating non-cooperation and of any deliverables that
          may be delayed due to such lack of cooperation by other entities referenced in the SOW.

     •    ODOT Contract Administrator will contact the non-cooperative entity/s to discuss the matter and
          attempt to correct the problem and expedite items determined to be delaying Contractor/project.

If Contractor has followed the notification process and delinquency or delay of any deliverable is found to be a
result of the failure of other referenced entities to provide information, resources, assistance, or cooperation, as
described in the SOW, Contractor will not be found in breach or default with respect to delinquencies beyond
any reasonable control of Contractor; nor will Contractor be assessed or liable for any damages arising as a
result of such delinquencies. Neither will ODOT be responsible or liable for any damages to Contractor as the
result of such non-cooperation by other entities. ODOT Contract Administrator will negotiate with Contractor in
the best interest of the state, and may revise the delivery schedule to allow for delinquencies beyond any

                                                                                           Page 83 of 100
reasonable control of Contractor. Revised delivery dates beyond the expiration date require an amendment to
the Contract.

Review, Comment and Schedule Overview
   • Contractor shall coordinate with Agency staff as necessary and shall revise draft deliverables to
       incorporate Agency draft review comments.
Contractor shall incorporate comments within 10 business days from receipt by Agency and return the Final to
Agency staff, unless a different timeframe is specified for specific tasks or otherwise agreed to in writing by
Agency.


B. AUTHORIZED REPRESENTATIVES:

               Agency                                                  Contractor
Name:                                                   Name:
Address:                                                Address:

Phone:                                                  Phone:
Fax:                                                    Fax:
Email:                                                  Email:

C. PROJECT TEAM:
                                             Contractor’s Key Persons.
Contractor Project Manager - responsible for all coordination of work required of Contractor to fulfill the obligations
resulting from this RFP. Contractor Project Manager shall provide input to the DMV Project Manager and support
planning, reporting, risk and issue management in support of the DMV project. Responsible for completing the agreed
project scope on time, within budget. Responsible for facilitating the project by using the project management processes,
organizing the project, and managing the team work activities consistent with the approved work plan. Responsible for
collaborating with and responding to requests from DMV Project Manager in support of the SCM project.
Minimum Requirements: 5-10 years of IT project management experience. Experience should include a minimum of two
successful projects that involved implementing the product being proposed in response to this RFP.
Contractor Technical Lead - provides technical leadership and guidance to Contractor’s technical staff to accomplish
project objectives effectively and efficiently. Coordinates the work of technical resources to facilitate the completion of
assigned tasks. Works with Contractor Project Manager and stakeholders to develop plans and schedules and manages
the work of the technical teams. Responsible for responding to requests from DMV Technical Lead in support of the SCM
project. May facilitate work sessions with DMV Technical Lead to validate requirements and will develop specifications,
design, and other technical deliverables.
Minimum Requirements: 3 - 5 years of IT Technical Lead experience. Experience should include a minimum of two
successful projects that involved implementing the product being proposed in response to this RFP.


Systems Engineer - responsible to co-ordinate all aspects product development including validating requirements,
proposing solution design and workflow process changes, configuring the product to meet all requirements, testing,
troubleshooting, and participating in implementation activities. Systems Engineer shall be the key technical contact that
co-ordinates across multiple teams within the company from project planning through deployment and is responsible to
implement system features required to meet objectives of the SCM project.
Minimum Requirements: 3 - 5 years of technical analysis, design, and implementation experience. Experience should
include a minimum of two successful projects that involved implementing the product being proposed in response to this
RFP.

Implementation Engineer - responsible to co-ordinate all aspects of the product installation in ODOT DMV LPAR, and
product configuration in test and production environments as required for the project. Shall train and support SDC and
DMV staff in initial installation and provide mentoring and training for ongoing operations, support, troubleshooting and
problem solving.
Minimum Requirements: 3 - 5 years of implementation experience which includes a minimum of two successful projects
that involved implementing the product being proposed in response to this RFP.
                                                                                                 Page 84 of 100
Training Specialist – responsible for proposing a training strategy and specific plan to and delivering training to all roles
required to use, support, and maintain the system. Responsible for developing materials to support work process
changes and support transition activities.
Minimum Requirements: 3 - 5 years of technical training experience which includes a minimum of two successful projects
that involved implementing the product being proposed in response to this RFP.

                                                  DMV Key Personnel
Executive Sponsor provides the executive leadership, priority and commitment to the project, its goals and objectives.
Helps the project team to remain focused on the established project objectives by protecting the project against out of
scope customer agendas and other intruding external forces and barriers. Ensures that critical decision points are clearly
identified and that decisions are made in a timely manner.

Project Manager is responsible for all coordination between the Agency and Contractor from the time the Contract is
executed until the work is completed and accepted or the Contract is terminated. Works closely with the Executive
Sponsor in the planning and delivery of the project. Is responsible for completing the agreed project scope on time and
within budget. Responsible for facilitating the project by using the project management processes, organizing the project,
and managing the team work activities consistent with the approved work plan.

Technical Lead provides technical leadership and guidance to accomplish project objectives effectively and efficiently.
Coordinates the work of technical resources to facilitate the completion of assigned tasks. Takes direction from the
Project Manager regarding project planning and development activities. Works closely with the Project Manager to
select, plan and coordinate the implementation of technical solutions and to develop plans and schedules and manage the
work of the technical teams. Has primary responsibility for design, technical issue resolution, and conversion and
implementation activities between DMV and selected Contractor’s technical staff. Reviews and approves project
deliverables.

Contract Administrator will be responsible for all functions related to the Contract between the Agency and Contractor
from the time the Contract is executed until the work is completed and accepted or the Contract is terminated.




D. PROJECT SPECIFIC ABREVIATIONS, ACRONYMS AND DEFINITIONS.
Agency or ODOT – Oregon Department of Transportation

Administrator – The person, who sets up the SCM product, creates user login accounts and passwords,
creates groups, sets security, and maintains the SCM product.
Application Dependencies – Application dependency is a mapping on how applications and their underlying
components interact with one another. The components of an application could reside in multiple platforms. As
an example an online DMV application running on a cold fusion server could execute a DB2 stored procedure
running on the mainframe.
Application Development Lifecycle – The various stages in the life of a Configuration Item, Incident,
Problem, Change etc. The Lifecycle defines the Categories for Status and the Status transitions that are
permitted. The Lifecycle of an Application includes Analysis, Design, Code, Test, and Implementation and post
implementation support and decommissioning.
Approval – The agreement that an item is complete and suitable for its intended use.
Approver – The person that does the approval.
Backout – Restore back to the prior versions for all components being backed-out.
Branching – Branching, in revision control and software configuration management, is the duplication of an
object under revision control so that modifications can happen in parallel along multiple branches. The
requirement to be able to do concurrent development at DMV results in a component needing to be
simultaneously changed by several unrelated development activities while the component remains unchanged
in production. DMV uses the term “branching” to name the process of initiating and maintaining an independent
source component in one or more environments.
                                                                                                   Page 85 of 100
Business Hours – Agency’s normal business hours are 8:00 AM PT – 5:00 PM PT, Monday through Friday,
excluding state holidays and mandated Furlough days. Facilities are available 7:30 AM PT to 5:30 PM PT
subject to Agency policy.
Business Days – Unless otherwise provided, all references to “days” in this Statement of Work mean
“Monday to Friday”.
Business Owner – The business manager assuming the costs of the Project and being the recipient of the
solution's benefits. In a delivery context, they represent the organizational unit most affected by the Project.
Business Test Plan (P416D) – A project deliverable that details test specifications for the Business Team's user
acceptance and user simulation testing activities for the project, project component or release and to define the
roles and responsibilities and the individuals assigned to fulfill them.
Change Request (M042S) – Used to document and validate a desired change to the project, especially those
with impacts on scope, budget, timeline and/or other initiatives.
Change Request Log (M046S) – Used to track and report all of the change requests for a given project.
Check In – At DMV, check in is a process by which source components are migrated back into production
environment through development/acceptance test environments or that a specific check out has been
abandoned in a development environment.
Check Out – At DMV, check out is a process by which source components are checked out to modify the
source for a given project, maintenance or an emergency change. The source is usually checked out from
production environment to a development environment.
Communication Plan (M017S) − Deliverable used to define a communication plan for the project
implementation (i.e., communicating results, changes, procedures, etc to stakeholders or the general public).
Component – A single member of a release package; usually a member of a library that was brought into
SCM for modification.
Concurrent development – DMV frequently has source components that are being modified by two (or more)
concurrent projects while at the same time undergoing emergency maintenance. This circumstance results in
four (or more) copies of the same program, each in its own environment. Each copy of the program could
receive a different set of changes, and all copies of the programs must eventually be reconciled / merged.
Contract Administrator – The Agency designee that is responsible for all functions related to the contract
between an agency and a Contractor from the time the contract is awarded until the work is completed and
accepted or the contract is terminated. These functions may include technical oversight, review of work,
progress monitoring, invoice processing, change management, documentation and filing, performance reviews,
and contract closeout.
Conversion Strategy – A Project Deliverable that describes the strategy that will be used to convert the
information, both automated and manual, from current systems to the new system; describes the state of the
current system's information; and describes the conversion rules that will be used to convert existing
information for use in the new system.
Deliverable Expectation – Project Deliverables, their Acceptance Criteria, and their reviewers and approvers.
Detailed Project Plan (M009S) – MS Project plan (baseline template).
DMV – A division of Oregon Department of Transportation known as Driver and Motor Vehicle Services.
Environments – A set of facilities (CICS regions, DB2 Tables, etc.) and files (load libraries, VSAM and QSAM
data files, source libraries, etc.) in which programs and jobs can be created and executed. ENVA and PROD
are two examples of environments at DMV.
Freeze – A point in time in the development process after which the rules for making changes to the source
code or related resources become more strict, or the period during which those rules are applied. A freeze
helps move the project forward towards a release or the end of an iteration by reducing the scale or frequency
of changes, and may be used to help meet a roadmap. The exact rules depend on the type of freeze and the
particular development process in use; for example, they may include only allowing changes which fix bugs, or

                                                                                         Page 86 of 100
allowing changes only after thorough review by other members of the development team. They may also
specify what happens if a change contrary to the rules is required, such as restarting the freeze period.
Fujitsu Macroscope – A comprehensive body of knowledge relevant to organizations and their need for
change. It offers an integrated set of proven processes that help successfully initiate, manage, and implement
change in organizations, with the goal of improving business performance. This “methodology” is used by
Agency, licensed and copyrighted to Agency by Fujitsu, and where appropriate, its Contractors to manage and
deliver information technology projects within the department. The information will be made available to the
Contractor through the Agency’s Project Manager.
Functional Specifications – A Project Deliverable that describes business functions and the requirements for
all functions that the application is to support; it describes the data structures required to support the
application and any data conversion requirements needed to transfer existing data to the new application; and
it describes the software services needed to complete the application and describe the interfaces to other
systems and applications. The functional specification is the basis for all subsequent Project planning, design,
and coding, as well as the foundation for system testing and user documentation.
Functionality – The capabilities or behaviors of a program, part of a program, or system, seen as the
sum of its features. A useful function within a computer application or program.

Furlough Days – means the days state employees are mandated to take off work to comply with the
Governor’s Directive.

Gantt Chart – A horizontal bar chart that can graphically depict the time relationship of tasks,
activities and resources in a project.
Impact Analysis – DMV performs impact analyses that show the system-wide and platform-wide effect of
migrations, ranging from the effect of an individual change in one specific source component through the effect
of all changes in a package. The impact analyses provide information such as: a.) programs affected when
data-names are changed in an include member or copy member, b.) programs affected when a subroutine is
changed, and c.) jobs affected when the record-size of a file is changed, and d.) files affected when an include
member or copy member for a record is changed.
Implementation Plan (P450S) – A Project Deliverable that describes implementation and post-implementation
activities; describes and quantifies resources required to implement the system: and describes and quantifies
resources that will use, operate, support, and maintain the system once implemented.
Implementation Strategy – A Project Deliverable that recommends a specific implementation strategy;
describes the major aspects of the implementation strategy; and, where appropriate, provides the basis for
release-based implementation planning.
Installation Instructions (P800D) – Deliverable used to plan and define the installation activities for the
project.

IDE - An integrated development environment (IDE) also known as integrated design environment or
integrated debugging environment is a software application that provides comprehensive facilities to computer
programmers for software development. An IDE normally consists of
                  - Source code editor
                  - Compiler and/or an interpreter
                  - Debugger
Independent QA Log (P999X) – Deliverable used to track DMV's responses to independent QA Contractor
findings and recommendations. Generally, a separate log is created for each Contractor QA report.
Issue Log (M048S) – Deliverable used to track project issues.
Issue Paper (M046X) – Deliverable used to thoroughly define and analyze an issue, explore possible
resolution options, and recommend a course of action.
Librarian – The person that performs the migration of a package using the SCM product.

                                                                                          Page 87 of 100
Library Tracking System – LTS is an in-house product developed by DMV. LTS provides the capability to
control migration for various projects and maintenance tasks. LTS does not support version control or other
functions like branching and merging to be able to do concurrent development.
Macroscope – is a methodology and process for information technology projects. It is marketed by Fujitsu.
Macroscope is licensed to ODOT and is the Agency standard for managing information technology projects.
The system is made up of document templates, outlines, process, and requirements for each deliverable.
Each deliverable used in the methodology has a reference number associated with it. All deliverables with
reference numbers identified in this statement of work are Macroscope documents.
Merging – DMV frequently merges changes made to a source component or multiple components in one
environment with different changes made to the same source components in other environment. This merging
typically occurs when the components are being changed by a project and are also undergoing periodic
emergency maintenance in production. When the project is migrated to production, the component's project
changes must be merged with the component's production changes. This merging can also occur when
components are being changed by two unrelated projects and one of the projects must incorporate the other
project's changes in order to proceed with development.
Migration – The process of transferring a release package's components from one source repository to
another source repository. Source components (Program source, Include Member source, JCL, Control
Members, etc.) are moved from one repository to another. Executable components (Program load modules,
generated BMS Maps, etc.) can either be moved from one repository to another or re-generated in the "to"
repository (by compiling and linking, assembling and linking, etc.).
Migration Path – An ordered set of source repositories that represent a normal progression of components
through the environments. The progression from the ENVA source repository to the REGI source repository to
the PROD source repository is an example of a migration path.
ODOT – Oregon Department of Transportation.
ODOT IS – the Information Systems branch within ODOT.
P+ Deliverable – a Macroscope deliverable produced according to the methodology and ODOT IS standards.
Package/Release package – DMV uses the term “package” to name the migration description for a set of
components that are migrated from one environment to another at the same time. The package identifies every
component to be migrated as well as the migration path through the environments.
Partial Migration – The process of transferring part of a release package’s components from one source
repository to another source repository.
Procurement Management Plan (M010S) – Deliverable used for planning the procurement related aspects of
a project, including buy vs. build decisions.
Project Completion Report (M060S) – A Project Deliverable that evaluates the Project with regard to its initial
success parameters to provide feedback to the client, stakeholders, and members of the Project team.
Project Performance Meeting – A once every two week meeting between Contractor and Agency’s Project
Manager to discuss Project status.
Project Progress Meeting – A monthly meeting between Contractor Project Manager, Agency’s Project
Manager, and System Owner to review Project issues, progress, and future direction.
Project Proposal (A400D) – Required deliverable used to propose, estimate and schedule an IT project.
Project Status Report (M050S) – A Project Deliverable that describes the status and evolution of
Deliverables, activities, and a timetable of the Project; it facilitates Project control and the associated decision-
making processes.
QA – Quality Assurance
Restore – Move a prior version of a component over the current version.
SCM – Software Configuration Management
SDC – Oregon State Data Center.
                                                                                            Page 88 of 100
SPC – Single Point of Contact
Softcopy Documentation – Electronic copy of the documentation.
Software Architecture (P219S) – Deliverable used to establish the technical foundations of the system, to
partition it into developer subsystems and software components, and to show the associations with the user
requirements and technology infrastructure.
Source Repository – A set of files that is associated with one environment and that contains the source
components from which the environment’s programs and jobs are created. The program source files, include
source files, JCL files, Control Member files, etc., for the ENVA Environment is a source repository.
Stakeholders Needs (P240S) – Project or pre-project deliverable used to document, rank and justify
Stakeholder Needs and their decomposition into High-Level Requirements.
State Procurement Office (SPO) – The State of Oregon acting by and through its Department of
Administrative Services, State Procurement Office.
SOW – Statement of Work
System Architecture – Deliverable used to document the functional architecture of subsystems impacted by
the project.
System Test sign-off – A documented summary of the approach taken during System Test activities as well
as a comprehensive description of the findings identified during a System Test, which includes sign-off by all
participants, including Agency. The document defines the purpose of the System Test, describes the
procedures followed during functional testing and addresses the acceptance criteria. In addition, the document
outlines the results of the System Test by providing the incidents identified during testing and by addressing
the status of each.
Technical Infrastructure (P370D) – Deliverable used to describe the technology infrastructure needed to
support the information system (including its development, tests, and training), to define the impacts on the
existing infrastructure, and to define the distribution of software components on the infrastructure.
Technical Lead – The software engineer in charge of the Project responsible for the underlying architecture
for the software program(s) and for overseeing the work being done by any other software engineers working
on the Project.
Technical Test Plan (P415D) – A Project Deliverable that details test specifications in the form of test cases,
test scripts, and test data requirements.
Test Environment (P740S) – Deliverable used to describe the techniques and products to be used for testing,
and to define the technical environment(s) within which the testing will be conducted.
Test Results (P770D) – A Project Deliverable that documents the results of the system and integration tests.
Test Strategy (P405D) – A Project Deliverable that defines the approach to be used for requirements
management and the unit, integration, and Acceptance Tests.
Traceability Matrix (P900S) – A project deliverable to document the relationships between stakeholder needs
and the corresponding high-level requirements, detailed requirements, and test/use cases after they have been
defined to ensure that what is being built and then tested addresses the needs. Traceability Matrix is generally
created from other source documents (P145S Stakeholder Needs, P899S Detailed Requirements, P416D
Business Test Plan and P415D Tech Test Plan) before construction gets fully underway, but definitely before
testing is conducted.
Technical Training Plan – Deliverable that may be used to create a training plan for technical support
resources.
To Be Process Workflow (P251S) – Deliverable used to define and approve the "To Be" Business
Processes and Work Process for the project, and to provide an audit trail for process changes, deletions and
additions.
User Acceptance Testing (UAT) – The testing of the systems and system interfaces which have been added
or modified for/by the project, project component or release. The primary goal is to ensure that the systems
                                                                                        Page 89 of 100
function as specified in the business needs and requirements.
User Interface specification (P186D) – A Project Deliverable that describes programming interfaces or
communications protocols by defining services that are available through each subsystem; defining the
communication protocol which applies to each subsystem; and defining how proper information exchanges
between subsystems will be achieved.
Verification – The process of determining whether or not the products of a given phase of the system/software
cycle fulfill the requirements established during the preceding phase.
Version – An identified instance of a Configuration Item within a product breakdown structure or configuration
structure for the purpose of tracking and auditing change history. Also used for software Configuration Items to
define a specific identification released in development for drafting, review or modification, test or production.
Version Number – Part of the unique identification used to distinguish a changed version of a component from
the previous version of the component with the same primary identifier.


E. PRODUCTS _(to be determined upon Price Agreement Award)_____________________

F. TASKS AND DELIVERABLES: Contractor shall not start work under this WOC until in receipt of a
written Notice-to-Proceed (NTP) from the Agency.

The Contractor shall perform the following Tasks and provide the following Deliverables to the Agency’s
Project Manager or designee. Contractor shall provide copies of all final Deliverables to the Agency’s Project
Manager or designee.
Note: Contractor may suggest specific deliverables and processes as an alternative if comparable deliverables
exist in their methodology.

TASK 1: PLANNING AND ADMINISTRATION

Contractor shall perform the following activities to ensure that adequate planning and project management are
performed for this project.

Activity 1.1: Develop a Detailed Project Plan and Schedule
Contractor shall confer with DMV and deliver a detailed project plan and schedule (using MS Project) due 15
business days after Notice to Proceed. The project plan and schedule must include fixed delivery dates for
the remaining deliverables. All deliverables must be completed and accepted by Agency by __________.
The deliverable due dates will be mutually agreed upon during DMV approval of project plan and schedule.
The project plan and schedule must include, but not be limited to:
   •   Project schedule including tasks and activities, deliverables, location of task and activities, activity
       duration, resources, sequencing and dependencies;
   •   Project work plan for each deliverable, including a work breakdown structure;
   •   Completion date for each task and deliverable;
   •   Project milestones;
   •   Entrance and exit criteria for specific project phases; and
   •   Project organization including a resource plan that defines roles and responsibilities for the Contractor
       and DMV resources.

Activity 1.2: Develop a Detailed Activities Plan
Contractor shall produce a detailed activities plan to include, but not be limited to, the following project areas:
    • Communications: How communications will be managed between the Contractor and DMV project
        team members and other stakeholders and governance committees.
    • Activities that need to be completed with team members and stakeholders in order to prepare them for
                                                                                           Page 90 of 100
        the implementation of the SCM solution. This section must detail the activities, resources,
        recommended timeframes for completion and any special requirements from either DMV or the
        Contractor to ensure the success of the communication activity. All communication plan activities must
        be reflected in the project schedule, including all tasks, activities, activity duration, sequencing and
        dependencies.
    •   Risk Management: Tasks to ensure that risks are effectively identified, planned for, analyzed,
        communicated and acted upon. The plan must include a preliminary list of risks that the Contractor
        has identified, along with the probability of each risk's occurrence, the potential impact to the project if
        each risk occurs, and a response strategy for each risk.
    •   Quality Assurance: The methodology for maintaining quality of the product as changes are made to
        facilitate the DMV implementation.
    •   Change Control: Specifications for change control procedures to be used during the project.

Activity 1.3: Meeting Attendance

                                                 Kick-off Meeting
Agency and Contractor Key Personnel shall plan and attend a kick-off and planning meeting within two weeks
of the WOC Notice to Proceed issuance. The purpose of this meeting is to introduce team members to one
another, clarify team member roles, review the overall Project Plan, and confirm understanding of detailed
plans for next steps.
Contractor Key Personnel shall include at a minimum Contractor’s Project Manager, Technical Lead and
Training Specialist. The Contractor shall provide the following for this meeting:

• Agenda Items to the Agency Project Manager
• Invite proper contractor staff to attend the meeting
• Provide any necessary presentation materials

                                         Semi-Monthly Status Meetings
Participate in twice monthly project status meetings with DMV project team at a location to be determined by
DMV. Attendance may be in person or via teleconferencing, as agreed to by DMV. These meetings must
follow an agenda developed by the Contractor and agreed to by DMV. The agenda may include, but not be
limited to:
• Review and approval of previous meeting minutes;
• Review of project status by Contractor, DMV, ODOT, and other State stakeholders, with the review
  addressing accomplishments, activities, issues, upcoming activities and resource requirements;
• Outstanding action items, including resolutions;
• Review of project risks and issues including status on outstanding issues and their resolution;
• New action items;
• Contract status and issues, including resolutions;
• Quality Assurance status;
• Date of next meeting; and
• Other business.

                                    Project Related Meetings, as Requested
Contractor shall attend and participate in all project related meetings, as requested by DMV. The Contractor
shall prepare materials or briefings for these meetings as requested by DMV.




                                                                                            Page 91 of 100
Activity 1.4: Provide Written Twice Monthly Status Reports

Contractor shall provide written twice monthly project status reports to DMV SCM Project Manager on the first
and third Tuesday of each month. The status reports must include, but not be limited to, the following:
• Overall completion status of the project in terms of DMV approved project work plan and deliverable
  schedule;
• Accomplishments during the reporting period;
• Problems encountered and their proposed and actual resolutions;
• Tasks and activities to be accomplished during the next reporting period;
• Issues that need to be addressed, including contractual;
• Quality Assurance status;
• Updated MS Project time line showing percentage completed, tasks assigned, completed and remaining;
• Identification of schedule slippage and strategy for resolution;
• Contractor Key Personnel or other staff assigned and their location/schedule;
• DMV and other State resources required for activities during the next time period; and
• Resource allocation percentages including planned versus actual by project milestone.


        PLANNING AND ADMINISTRATION DELIVERABLES
                                                                                          DMV
        DELIVERABLE
                                DESCRIPTION OF DELIVERABLE              ACTIVITY      REVIEW TIME
          NUMBER
                                                                                     (Business Days)
        D1.1                Detailed Project Plan and Schedule            1.1               5
                            (Due 15 business days after Contract
                            award)
        D1.2                Activities Plan                               1.2                 5
        D1.3                Attendance at All Scheduled Meetings          1.3               N/A
        D1.4                Written Project Status Report (P050)          1.4                 5
                            (submitted the first and third Tuesday of
                            each month)




TASK 2: CONFIRMATION OF FUNCTIONAL AND TECHNICAL REQUIREMENTS
Contractor shall confirm system installation requirements, configuration, security authorizations, modifications,
process changes, and activities to retire existing systems, products, and utilities in order to complete the
project.
Contractor shall provide:

Activity 2.1: Functional and Technical Specifications
Attend working sessions with DMV to jointly review and clarify the vision, objectives and functional
requirements for the SCM solution. Contractor shall be on site at DMV for these working sessions in order to
review and discuss DMV requirements and must provide a demonstration copy of the software in order to
demonstrate how the software functions and can be configured to meet DMV’s needs.
The working sessions must include the review of flowcharts, product workflow and DMV workflow and business
rules associated with the implementation of the SCM solution. The Contractor shall confer with DMV to
determine the most effective way to operate during planning, analysis, and system implementation and before

                                                                                          Page 92 of 100
the system is moved to a production state. The goal is to continue to operate simultaneously using both the
existing products and procedures and the new system in order to ensure a smooth transition and minimize
business and operational disruptions.
The Contractor shall document an understanding of the current DMV technical environment and products used
today to manage source on all DMV platforms. The Contractor shall describe in writing any differences
between DMV requirements and the Contractor’s solution including, but not limited to:
• Hardware/Software prerequisites (if any), understanding that the product must run on the technology
  platform defined in WOC1 SOW Technical Environment.
• Configuration requirements;
• Conversion requirements for all programs, libraries, databases, utilities, and any other components or
  process that may be impacted;
• Database set-up requirements;
• Process changes required by DMV in order to utilize the SCM solution;
• Changes in Roles and Responsibilities and a description of what and how they should change and related
  transition activities;
• Activities and methods to retire systems and utilities that must be replaced by the SCM product.
Since the SCM solution will replace existing systems, procedures, and work processes, the Contractor and
DMV will confer and agree on how to implement a solution that supports DMV’s multiple platforms and
successfully integrates and supports all DMV systems.
The Contractor shall confer with DMV to develop new processes and procedures and must support all
transition activities including creation of written documentation, proposing work process changes and
configuring the SCM product to support workflow processes. The contractor shall be responsible for
transition/training Information Systems and Business staff and managers on responsibilities and use of the
SCM product to fulfill those responsibilities.
The Contractor shall confer with DMV to specify the testing and production environments that must be needed
to implement the SCM solution. This specification must include the identification of any additional pieces of
hardware or software that will be acquired by DMV in order for the SCM solution to be fully implemented. The
Contractor shall document all issues that are identified through the working sessions as well as all agreements
reached between the Contractor and DMV.
The development and testing/training environment must be established by the Contractor and reviewed and
agreed by DMV.

Activity 2.2: Create a System Modification/Configuration Plan
Contractor shall develop a system modification/configuration plan and present the plan to DMV. The plan must
be presented in Contractor-lead working sessions that enable the joint revision, scheduling and acceptance of
the plan. The purpose of the plan is to agree to and document the tasks required to implement the SCM
solution to satisfy DMV requirements. Upon completing all the tasks in the plan, the system should be ready
for integration testing and user acceptance testing.
The plan must cover, at a minimum, the following:
• Description of system features/components to be modified or configured;
• Description of future workflows and work processes;
• Description of system installation requirements and configuration activities;
• Description application installation requirements and configuration activities;
• Location (environment/region) where modification/configuration must occur;
• Schedule for modification/configuration activities; and
• Resource requirements.

                                                                                        Page 93 of 100
Activity 2.3: Create a Conversion Strategy and Plan
Contractor shall develop a conversion strategy that describes the overall conversion approach including any
limitations and restrictions that affect the conversion as well as any testing activities to verify the correctness of
the conversion. The Contractor shall also develop a conversion plan that identifies all detailed activities
necessary for completing the conversion.


        CONFIRMATION OF FUNCTIONAL AND TECHNICAL REQUIREMENTS DELIVERABLES
                                                                                                 DMV’s
                                                                                               Estimated
         DELIVERABLE
                                    DESCRIPTION OF DELIVERABLE                   ACTIVITY     REVIEW TIME
           NUMBER
                                                                                               (Business
                                                                                                 Days)
        D2.1                Functional and Technical Specifications                 2.1              15
        D2.2                System Modification/Configuration Plan                  2.2              15
        D2.3                Conversion Strategy and Plan                            2.3              10

TASK 3: PRODUCT INSTALLATION AND CONFIGURATION
The objective of this task is to install and configure the product in the ODOT LPAR specifically for DMV’s
environments.

Activity 3.1: Installation Activities
The Contractor shall be on-site to support the installation of the product into the z/OS LPAR provided by SDC
for use by ODOT DMV. The Contractor shall provide instruction, oversight, and mentoring for State staff
involved in installation activities to ensure a complete, accurate, and supportable product installation.

Activity 3.2: Configure the Solution
The Contractor shall be on-site to support configuration of the product according to the specifications agreed
upon with DMV, as detailed in the Functional and Technical Specification and the System
Modification/Configuration Plan deliverables.

Activity 3.3: Demonstrate the Configured Solution
The Contractor shall plan and conduct walk-through demonstrations of the fully configured SCM solution. The
purpose is to confirm that the solution completely fulfills all requirements, functionality, workflow, processes
and other components approved in Task 2, Functional and Technical Requirements. The demonstrations will
occur in DMV’s test environments. If corrections are required, the Contractor shall make the requested
corrections and conduct additional demonstrations (not to exceed a total of five) at no additional expense until
DMV approves the system ready to enter Acceptance Testing.



        INSTALLATION & CONFIGURATION DELIVERABLES
                                                                                                DMV’S
         DELIVERABLE                                                                          ESTIMATED
                                DESCRIPTION OF DELIVERABLE                  ACTIVITY
           NUMBER                                                                            REVIEW TIME
                                                                                            (Business Days)
        D3.1                Demonstration of Configured Solution             3.1-3.3                10




                                                                                             Page 94 of 100
TASK 4: ACCEPTANCE TESTING
The objective of this task is to fully exercise the solution through various scenarios and to take corrective action
as needed to ensure that the system satisfies all required functionality and requirements. Contractor shall train
an initial team of DMV testers to prepare for user acceptance test activities.

Activity 4.1: Provide Test Plan and Scripts
The Contractor shall provide DMV with a test plan and corresponding test scripts that must enable DMV to test
the entire system. Testing must be done in test environments established by DMV that simulates migration to a
production environment. Testing must exercise all functions of a fully implemented SCM solution and must
exercise all DMV required functionality and processes. The Acceptance Test Plan must include, but not be
limited to:
• Procedures for conducting Acceptance Testing (AT);
• Procedures for documenting results;
• Procedures for reporting defects to the Contractor;
• Method by which AT training must be conducted with each user group (i.e., System Administrators,
  Developers, Manager/Approvers, Business Analyst/Testers);
• Copies of AT training materials by user group; and
• Copies of procedures and other documentation that must be used as part of AT to capture results and
  defects.
• A description of the problem reporting and resolution process including estimated time to resolve issues
  based on problem type and severity.
• Metrics for measuring effectiveness of overall training in order to make improvements in training materials
  prior to delivery of training.


Activity 4.2: Provide Acceptance Test Training
The Contractor shall provide training to designated Users prior to beginning Acceptance Training (AT). AT
training includes, but is not limited to: use of the application to exercise all features to control source code;
support parallel development activities; support test activities; support electronic approvals; and to perform
code migrations based on rules established in the approved requirements document. User groups include, but
are not limited to:
• Mainframe Programmers/Analysts
• Web and Client/Server Programmers/Analysts
• Release Management Analysts
• Application Development Managers
• Operations & Production Managers
• Business Analysts/Testers,
• Librarians;
• System Administrators
• Database Administrators

Activity 4.3: Provide On-Site Support with Acceptance Testing
Testing must be performed by DMV Technical Staff, DMV IS Managers, and DMV Business Users with on-site
involvement and support from the Contractor. Testing must be done in an iterative fashion, performing as
much testing as possible between revisions and then repeating the preparation and testing as needed until all
results are satisfactory to DMV.

Contractor shall provide staff on-site during the Acceptance Test (AT) period.
                                                                                           Page 95 of 100
Should the system require any revisions or changes, or require corrective actions to ensure the SCM solution
is fully functional and production ready, the Contractor shall, at no additional charge, make all necessary
changes, configurations and adjustments until AT is passed or rejected.

        ACCEPTANCE TESTING DELIVERABLES

                                                                                     DMV'S ESTIMATED
        DELIVERABLE
                           DESCRIPTION OF DELIVERABLE                 ACTIVITY         REVIEW TIME
        NUMBER
                                                                                      (Business Days)
        D4.1               Acceptance Test (AT) Plan and Scripts         4.1                  10
        D4.2               Acceptance Test Training                      4.2                  10
        D4.3               Onsite Support During Acceptance              4.3                 N/A
                           Testing
                           DMV Approval/Signoff to move to
                           Production



TASK 5: TRAINING
The objective of this task is to provide DMV resources with the necessary training and materials to effectively
use, maintain and support the SCM product. All training courses and materials must be oriented towards user
groups or roles determined by DMV and include training on all system functions that a given user group or role
will need to know to successfully perform its duties.

All training provided by the Contractor shall be conducted at DMV training facilities and must be hands-on
training to include up to 50 individuals.

Activity 5.1: Provide a Training Plan and Schedule
Contractor shall provide a description of the approach and timeline to deliver training sessions. The sessions
must be arranged by type of training and user groups. The training plan and schedule must include but not be
limited to:
• Session goals;
• User profile and prerequisites;
• System functions and processes covered in the session;
• Examples of practical exercises to be used during the session; and
• Hours required for each session;
• Course outlines and training materials by type of training and user group with time allocations for each topic;
• Metrics for measuring effectiveness of overall training.


Activity 5.2: Provide Systems Installation and Support Training
Contractor shall provide training and mentoring of SDC staff for technical implementation, installation, and
configuration of base programs. This training must occur at the State Data Center and will include up to 3
individuals.

Activity 5.3: Provide System Administrator Training and Mentoring for Knowledge Transfer
Contractor shall provide system administrator training for a maximum of five DMV staff. Contractor shall
provide training guides, course outlines, and any other materials customized to the system administrator role.
Training must cover but not be limited to:

                                                                                         Page 96 of 100
• Setting up new users;
• Adding/changing user passwords and authorities;
• Adding/changing workflow rules;
• Setting up security profiles;
• Procedures for setting up projects/systems/branches; and
• All other tasks that a system administrator will need to perform in order to fully understand how to use
  system functions and perform all required post implementation tasks.

Mentoring includes one-on-one guidance and support to foster an understanding of the product and process
required to support the SCM product.

Activity 5.4: Provide End User Training
Training by end user role type must prepare DMV to operate the system at an enterprise level and across all
functional areas of the system. Training must focus on educating the end user on how operate the system
from the perspective of their role and responsibilities within the system.
Contractor shall provide training guides, course outlines, and other materials customized to the role for
delivering training to the following user groups to include up to 50 individuals:

   •   Mainframe Programmers/Analysts
   •   Web and Client/Server Programmers/Analysts
   •   Release Management Analysts
   •   Application Development Managers
   •   Operations & Production Managers
   •   Business Analysts/Testers
   •   Librarians
   •   Database Administrators
   •   SDC Systems Programmers and Support staff


        TRAINING DELIVERABLES
                                                                                              DMV'S
                                                                                            ESTIMATED
        DELIVERABLE
                           DESCRIPTION OF DELIVERABLE                         ACTIVITY     REVIEW TIME
        NUMBER
                                                                                            (BUSINESS
                                                                                              DAYS)
        D5.1               Training Plan and Schedule                            5.1            10
        D5.2               Systems Installation & Support Training               5.2              N/A
        D5.3               System Administrator Training                         5.3              N/A
        D5.4               End User Training                                     5.4              N/A


TASK 6: DOCUMENTATION
The objective of this task is to provide DMV with documentation and materials that provide a comprehensive
understanding of the system from both a technical and functional perspective.

Activity 6.1: Provide a Complete Set of Documentation


                                                                                          Page 97 of 100
The Contractor shall provide written documentation that details a comprehensive understanding of the system.
Five copies of hardcopy documents must be provided in addition to electronic versions of each document. The
documentation must include, but not be limited to, the following topics:
• User Manuals;
• Product Implementation Manuals
• Technical Reference Manuals
• Glossary of Terms
• System Administration Guide, including:
   - System Control Tables; and
   - System Set-Up Options.
• System Utilities, including Backup and Recovery Utilities;
• System Data Dictionary;
• System Process and Related Entity Diagrams
• Other documentation required to understand, implement, and become proficient with the product


       DOCUMENTATION DELIVERABLES
                                                                                              DMV'S
                                                                                           ESTIMATED
       DELIVERABLE
                               DESCRIPTION OF DELIVERABLE                   ACTIVITY      REVIEW TIME
       NUMBER
                                                                                            (Business
                                                                                              Days)
       D6.1                    Complete Set of System Documentation            6.1             10


TASK 7: PRODUCTION IMPLEMENTATION
The objective of this task is to deploy the system to the production environment. The Contractor shall
complete the following activities.

Activity 7.1: Implementation Strategy and Planning
Contractor shall develop and document an implementation plan that includes, but is not limited to:
• Implementation Activities, Plan and Schedule
• Installation Procedures
• Communication and Contact Information
• Backout Procedures
• Go/No-Go Decision Criteria

Activity 7.2: Implementation Support
The Contractor shall provide on-site support during production implementation and during the first month of
operation in the production environment. On-site availability must include, but is not limited to:
• Troubleshooting and resolving technical issues
• Providing support and assistance to system users
• Identifying common issues and determining if they are related to product implementation or training.
• Resolving all issues to DMV’s satisfaction to gain approval to close out the project.




                                                                                          Page 98 of 100
Activity 7.3: Final Acceptance
Upon completion of project activities, the Contractor shall deliver a written project completion report to the
Agency. The report must describe how all the work defined in the SOW and WOC was delivered and fulfills all
Agency requirements.

       PRODUCTION IMPLEMENTATION DELIVERABLES
                                                                                            DMV’S
                                                                                         ESTIMATED
       DELIVERABLE
                           DESCRIPTION OF DELIVERABLE                     ACTIVITY      REVIEW TIME
       NUMBER
                                                                                          (Business
                                                                                            Days)
       D7.1                Implementation Plan                               7.1             10
       D7.2                Implementation Support                            7.2               N/A
       D7.3                Final Acceptance Report                           7.3               90




TASK 8: SYSTEM WARRANTY
Will be negotiated.


TASK 9: SYSTEM MAINTENANCE AND SUPPORT Agreement
Will be negotiated.

G. PROJECT SPECIFIC PROVISIONS:
Project specific Terms and Conditions are applicable only to this WOC and Project.



H. REVIEW AND ACCEPTANCE CRITERIA:



I. DELIVERY AND PAYMENT SCHEDULE

The Agency will make payments to the Contractor based on the Work delivered and accepted by the
Agency.

                                             (Insert Gantt Chart)




                                                                                       Page 99 of 100
                                                     ATTACHMENT D
                                                    WOC 1 Exhibits 1 - 13
                           DMV Environment Descriptions for Proposer Review
                        (These Exhibits are not to be returned with Proposal Form)



     Exhibit 1 -         Exhibit 2 -    Exhibit 3 - Migration Exhibit 4 - Migration Exhibit 5 - Migration Exhibit 6 - Library Exhibit 7 - Migration
Environment Chart EXEnvironment Regions      paths.pdf        process flow for Projeprocess flow for Main Tracking System.pdf Procedures for ISPF M



Exhibit 8 - Migration Exhibit 9 - Migration Exhibit 10 - Migration Exhibit 11 - Migration Exhibit 12 - SCM      Exhibit 13 -
Procedures for JCL mProcedures for Coldfu   Procedures for EGOV Procedures for MS Accoordinator Roles and  Application Source Co




                                                                                                                      Page 100 of 100

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:26
posted:6/8/2011
language:English
pages:100