Purpose of Perfomance Management

Document Sample
Purpose of Perfomance Management Powered By Docstoc
					                                              Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

            STATE OF WASHINGTON                                                                                           CONTRACTOR’S DIS ITPS MASTER
            DEPARTMENT OF LICENSING                                               AGENCY WORK ORDER NO.                          CONTRACT NO.
            ITPS WORK ORDER
                                                                                             XXXX                                   T08-MST-XXX

SECTION 1: PURPOSE
The purpose of this Work Order is to provide DOL with information technology services in Technical Service Category(s) Client Server, Web & N-Tier
Application Development. XXXXX, a corporation licensed to conduct business in the state of Washington, herein after referred to as the “Contractor”, shall
furnish the necessary personnel, equipment, material and/or services and otherwise do all things necessary for or incidental to the performance of work set forth
in the Statement of Work.
SECTION 2: STATEMENT OF WORK
The purpose of this Work Order is to re-design and re-write eight Department of Licensing (DOL) legacy computer applications that are at risk of failure due
to increasing incompatibility with DOL‟s computer infrastructure and complexity to modify. This project will eliminate the risk by (1) applying current
software architecture principles and contemporary programming languages to the re-write of the applications; and (2) giving DOL Information Services (IS)
developers hands-on experience working with contractors who have expert skills in applying the .net 3.5+ tools and contemporary software design “best
practices”. The Contractor shall furnish four employee(s) at the skill level and hourly rate as shown in Compensation, Section 3, to perform and complete
the following tasks and/or deliverables.
This is a fixed-bid, deliverables-based contract where payments to the Contractor are allowed only after DOL acceptance of the deliverables listed in the
Budget Table.
Due to the nature of the project the Contractor will be expected to provide services on-site, at a DOL-provided office space, in Olympia, Washington. It is
anticipated that the nature of the project will require work to be performed during hours that are compatible with other project team members in order to
maximize team effectiveness and project success. Due to the security requirements of DOL networks, the agency does not allow any devices to be
connected to the network and therefore will provide a PC and any necessary applications (Microsoft Office 2007 Application Suite, including Outlook,
Project, Visio) that the Contractor is to use for work performance.
The staff must be available for the entire project, please see Assignment of Staff.
The following Deliverables/Tasks are required minimums for the project. Contractor is responsible for the preparation of all Deliverables/Tasks. Documents
will be delivered in electronic format using Microsoft Office 2007 and will follow a template conforming to DOL documentation standards, if available. The
following outlines these Deliverables/Tasks:

The contractor(s) will serve as software designers, programmers and teacher-coaches throughout this engagement with responsibility for the re-design and re-
programming of each application. Initial estimates indicate four contract Programmer-Analysts are needed to finish the work before the June 30, 2011 end-of-
biennium deadline. Each of the four contractors will work on one of the four concurrent work paths of the application migration, but need to be consistent in
their approach, recommendations and mentoring of DOL IS staff. There will be one AL for assigned to each concurrent work path. The work paths will be
referred to by the primary application of that path as follows: (1) Revenue In Progress (RIP) application, (2) Revenue Validation (“RevVal” for the five
remaining Revenue applications (RevVal, Cash Mgmt., Actg.Code Maintenance, Actg. Period Maintenance and Miscellaneous Revenue Receiving Reporting),
(3) WSP Gateway, and (4) Driver and Plate Search.

A DOL Application Lead (AL) and one contractor will work together throughout design and programming, with the AL doing 25% of the work, applying 25% of
their work-week to the project, and the contractor doing 75% of the work.

DOL follows a formal code check-out/check-in and code promotion process that the contractor will need to follow. (See Software Maintenance Process under
“Software Deliverables – Additional Requirement”.)

Because DOL only deploys applications to the Production environment on the 2 nd Sunday of each month, the final deployment must be ready and approved for
deployment by the cut-off dates two weeks before the June 2011 “Release Sunday”. DOL strongly prefers that the last deployment under this contract be done in
May 2011 and any change from that target needs to be communicated clearly and repeatedly as soon as a risk of not being able to meet that deployment date is
detected.

During the first few days of the contract engagement, the contractor will be asked to read the Project Charter and related documents describing the migration
objectives, approach and required deliverables. DOL and the contractor(s) will then meet to both answer any open questions or needed clarifications, and to
entertain suggestions from the contractor. DOL is under no obligation to accept recommendations from the contractor, but the contractors are being hired as
experts, so DOL will likely accept at least some of the contractor‟s suggestions. Additional meetings to discuss opportunities to do things better can be called by
either DOL or the contractor. In decision making, DOL has the final say that shall not be protested by the contractor.

The contractor is to create the general and daily work plan for creation of the Detailed Design and for the Programming work. The contractor is responsible for
completing work on or ahead of schedule; realizing work must be done in collaboration with DOL IS staff who will not be able to participate more than 25% of
their work hours.

Technical Knowledge Transfer: The contractor is to ensure each AL he or she works with learns (a) the features of .net 3.5+, VB.net, ASP.net, Visual Studio and
web service design and construction under the Windows Communication Framework (WCF) needed to produce easy-to-maintain code to contemporary best
practices and standards, (b) how to apply contemporary design and architectural principles that produce what other developers and contractors will see as
intuitive and correctly implemented examples for the given languages, and (c) have mastered the technical concepts and thought processes needed to do this
work again without the coaching and mentoring from the contractor. The result must be to accomplish the application migration work and ensure the AL gains a
thorough understanding of the thought processes needed to achieve the software architectural principles, application of best practices and use of the
 File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                   Page 1 of 15                                               Dated: March 11, 2010
                                               Performance-Based Contracting Example
                                                  This is an example only and not required for agency use.

            STATE OF WASHINGTON                                                                                            CONTRACTOR’S DIS ITPS MASTER
            DEPARTMENT OF LICENSING                                                AGENCY WORK ORDER NO.                          CONTRACT NO.
            ITPS WORK ORDER
                                                                                             XXXX                                    T08-MST-XXX
contemporary tool capabilities and languages to most efficiently do the work and produce easily-maintainable software. -- DOL may test their staff‟s knowledge
and skills before and after the contractor‟s coaching, training and mentoring.

Positive Working Relationship: The contractor and DOL IS staff (the AL and those providing support services such as Configuration Management, Infrastructure
Support and Architectural support) must maintain good working relationships, positive attitude and a positive collaborative, helpful style while working together.
All participants are to help each other, learn and accomplish the project mission. The contractor has a special responsibility for facilitating the day-to-day work
with the AL, so must play a key role in fostering positive problem solving.

Escalate Problems: The contractor and DOL staff is strongly encouraged to escalate problems quickly, first to the Project Manger and then to the Deputy CIO.

Status Reporting: The contractor is responsible for weekly written status reports that update the remaining effort and expected delivery dates for work in
progress, expected final delivery dates, and log the technical knowledge transferred to DOL IS staff.

Reporting Unit Testing Results is part of Programming: During the programming phase of each application, the contractor is responsible for leading Unit Testing
of code prior to delivery of that code to DOL. The contractor is to provide the Unit Test results with each code delivery to show the code behaves as specified in
the Functional Specs and Detailed Design.

Deliverable Acceptance Signoff: The contractor is responsible for scheduling and leading formal peer-review/signoff for the design documents and formal code
reviews for each code delivery.

Repair of Defects: During DOL‟s testing of delivered code, it is the contractor‟s responsibility to find and fix the cause of defects reported by the DOL tester(s).
The AL is to assist in this process when possible. Testers will report all defects into the project‟s SharePoint site along with the steps to reproduce the defect
when that is available. The contractor is to record what caused and was required to fix each defect.

Advise on Migration Approach: If the contractor is aware of possible improvements in the way DOL is proceeding with the application re-write, that fact is to be
brought forward first to the Project Manager, and then with the PM‟s approval, to the technical teams working on the project. If the recommendation is approved
by DOL, the contractor is to support DOL making that change.
Understand each Application to be migrated – Responsible for reading and understanding documentation about each application provided to the contractor by
DOL. For each application to be migrated, the documentation will include an Architect Specification and a Functional Specification document(s). Additional
older (and possibly out-of-date) documentation may also be available, but consideration of such information should be done with full understanding that it has
not been validated to be correct. DOL has attempted to make available to the vendor accurate and complete information, but should the contractor discover that
certain needed information is not available in the documents, the AL and the contractor are to either find or create the information needed to complete the
Detailed Design document. Any information created in this circumstance should be approved by the DOL Business Liaison if it affects the user or business
rules.
Plan and coordinate Design Work – During the creation and documentation of the Detailed Design (Programming Specifications) for each application, the
contractor is responsible for (a) Understanding each Application to be migrated, (b) Understanding the content and organization of DOL‟s Detailed Design
documents, (c) applying their own knowledge and experience, to plan what needs to be included in each document while also meeting the needs of the DOL
Project Manager, (d) collaborate with the AL on a daily basis to divide responsibility for the work products between the AL and themselves, (e) integrate the
work products into a single, complete document, (f) schedule at least one peer review of the finished draft document, and (g) get DOL sign-off of the document
from both the AL and the associated IS Manager. Appendix B outlines the information content of the Functional Specification, Architectural Specification and
Detailed Design documents.

Plan and coordinate Programming Work – Before and during programming (application re-write) the contractor is responsible for: (a) breaking down the
application into components to be programmed and sequencing that work for efficient coding and testing; (b) developing unit tests for each component or group
of components that will be delivered to DOL; (c) planning and leading code reviews for each code delivery, (d) getting DOL signoff (written acceptance) of the
code by both the AL and the associated IS Manager; .(e) finding and fixing defects in the application discovered and documented during testing by DOL.

Follow the Project‟s Guiding Principles - The Guiding Principles of this project were listed in the Work Request and are contained in Appendix A. These
principles are to be followed.

Content of the Detailed Design documents – Appendix B lists the content and organization of the desired Detailed Design document deliverables. The
Contractor is to either follow this map of the deliverable‟s content, or negotiate modifications to the map with the DOL project team. The DOL Project Manager
will have final approval of acceptance of any proposed change to the content or organization of this deliverable.


Document Deliverables – Additional Requirements:
      Documents are to be created primarily in Microsoft Word, however where appropriate Excel and Visio may be used.
      All documents are to be stored in the BSM Project SharePoint site document repository as specified by the Project Manager.
 File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                   Page 2 of 15                                                Dated: March 11, 2010
                                             Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

           STATE OF WASHINGTON                                                                                        CONTRACTOR’S DIS ITPS MASTER
           DEPARTMENT OF LICENSING                                              AGENCY WORK ORDER NO.                        CONTRACT NO.
           ITPS WORK ORDER
                                                                                          XXXX                                  T08-MST-XXX

     New folders are not to be created for document storage without prior approval by the Project Manager.
     The Contractor is responsible for scheduling and leading (with assistance of the DOL Application Lead) all document reviews and collecting the
      deliverable sign-off documents (which must be in writing, but may be in the form of emails). Deliverable sign-off sheets are to be emailed or hand-
      delivered to the DOL Project Manager when approved by the appropriate DOL staff. Electronic copies of sign-off sheets will be stored into the Project‟s
      SharePoint site.

Software Deliverables- Additional Requirements:
     Deliverable Reviews and Signoff: The Contractor is responsible for scheduling and leading (with assistance of the DOL Application Lead) all code
      walk-through/reviews and collecting the deliverable sign-off documents (which must be in writing, but may be in the form of emails). Note: Each
      completed Software Deliverable is to match the Architecture Principles, Architecture Specification and Detailed Design document, except where a
      formal written change has been approved and signed by the Project Manager. Conformance is to be part of each code review and is required prior to
      acceptance and approval by DOL technical staff.
     Compliance with Specification and Design: When the document or code reviews surface the need to make changes, the contractor is responsible for
      making those changes unless the change is significantly different from the functionality or software design described in the Architectural or Detailed
      Design, in which case the Change Management process will apply.
      The Contractor is to integrate approved code changes and additions into DOL‟s applications; support testing; trouble shoot the source of defects; fix
      defects; and manage code versions required by DOL‟s configuration management processes and code repository. Defects shall be logged in the project
      SharePoint site along with the status and the corrective actions taken to repair defects.
     Development Standards: DOL‟s development standards, software architecture, and configuration management processes shall be followed for all
      Software Deliverables. DOL maintains three code environments: Development (DEV), Quality Assurance (QA) and Production. All code development
      and unit testing shall be completed in the “DEV” environment before being migrated to “QA”. All unit tests are to be documented and “peer reviewed”
      by the associated DOL Application Lead (AL). All requests to the DOL Configuration Management Group or to DOL Network Services for code
      movement/promotion to a different environment shall be made through the AL responsible for the application. Contractor will assist the AL prepare
      technical instructions, and scripts where appropriate, to migrating and merging code modifications into each code environment. All code will be stored
      and managed within DOL‟s Team Foundation Server (TFS) environment and must not be maintained off-site.
     Software Migration Process: All of the following steps must be completed by the contractor in sequence with the testing tasks identified as DOL
      responsibilities before code may be migrated to the “QA” or “Production” environments and to obtain final acceptance for the software deliverables:

         DEV TO QA:
         o Code Development
         o Develop and executed unit test scripts (functional specification)
         o DOL Testing:
                    DOL: Create Test Data (Use script if necessary)
                    DOL: Peer Review Test Scripts and Test Data
                    DOL: Execute Test Scripts and Document Results
                    DOL: Peer Review Test Results
         o Code Review
         o Defect Resolution (and Re-test by DOL)
         o Integration and Regression Testing

         QA TO Production:
         o Code Development
         o Repeat unit tests (functional specification)
                    DOL: Repeat Functional and End-to-end (integrated) testing with all interfaces
         o Defect resolution, re-test, and document results
         o Peer Review Test Results
         o Develop implementation script(s)
         o Support implementation

    Change Management: A formal change request document is required when DOL requests changes from that described in the approved Detailed Design or
       Functional Specification documents. The Contractor must submit a written quote for work requested in a Change Request. The quote must be accepted
       in writing before the Contractor may proceed with the change. Note: A 10% contingency factor was included in the vendor‟s bid (See Budget Table
       Item 13) to cover the possibility of one or more change requests. The Contractor may also propose changes, following the change management process,
       but there is no assumed approval of these proposals. The Vendor shall not begin any additional work without prior written authorization from DOL's
       Contract Manager. All change requests are to be forwarded to the DOL Contract Manager, DOL Project Director and the DOL Project Executive
       Sponsor for review and approval. Work on any change requests is not to be initiated until a formal written approval from DOL is received. The
       Contractor can‟t assume to receive any of the contingency money without written approval of submitted change requests.

 File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                  Page 3 of 15                                            Dated: March 11, 2010
                                              Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

           STATE OF WASHINGTON                                                                                            CONTRACTOR’S DIS ITPS MASTER
           DEPARTMENT OF LICENSING                                                AGENCY WORK ORDER NO.                          CONTRACT NO.
           ITPS WORK ORDER
                                                                                            XXXX                                    T08-MST-XXX

     Acceptance Criteria: The Contractor is responsible for getting signoff for each software deliverable from DOL business and Information Services (IS)
      staff identified by the DOL Project Manager. Required signoffs are:
        a. Signoff of code reviews is DOL‟s acknowledgement the programming is clear, has sufficient comments to guide those responsible for future
             software maintenance and the new code is consistent with the code into which the changes and additions are being inserted.
        b. Signoff acknowledging delivery of new or corrected code from the Contractor. To gain this signoff the code must be placed into DOL‟s Team
             Foundation Server-based configuration management process and the Contractor must provide to the DOL Project Manager documentation of the
             Contractor‟s unit tests to show code is not being delivered with known bugs and that sufficient testing was performed by the Contractor prior to
             the hand-off to reasonably ensure the application will compile and meet the functional requirements in the Architecture Specification, Detailed
             Design and Functional Specification documents.
        c. Signoff representing DOL‟s acknowledgement that all defects found during QA testing and User Acceptance have been fixed and the modified
             application does not produce any performance problems during stress/load testing.


 Performance Deliverables:
     Contractor Performance: DOL places three Performance Deliverables on Document and Software Deliverables to ensure that the Contractor remains a fully-
     engaged and collaborative partner through achievement of the project‟s successful implementation. These are enforced by a Payment Holdback. Contractor
     invoices are to itemize the amount due for each accepted deliverable, minus a holdback of twenty percent (20%) of the value of each deliverable. DOL
     reserves the right to not pay for each of the Performance Deliverables until the conditions below are satisfied and is not obligated to pay the Contractor the
     whole amount of the holdback. No payment can be made for work performed or deliverables provided to DOL after June 30, 2011.
    1. Deliverable: Deployment Complete
        Outcome: The Contractor has completed all Document and Software deliverables and they have been accepted by DOL. All approved change requests
        have been completed and tested. All DOL testing (functional, end-to-end, performance/stress, user acceptance, and operational readiness) has been
        successfully completed and only bugs authorized to be in the deployed code remain. The application has been successfully deployed and has remained
        in production use for three (3) consecutive business days. The Project Sponsor and/or the Project Manager sign an acknowledgement that these
        conditions have been satisfied.
    2. Deliverable: Deployed Application Stability
        Outcome: The application has been in production use by all intended users for at least ten (10) consecutive business days. There have been no aborts
        and no critical or showstopper bugs and no data corruption for at least six (6) consecutive business days. Users are not negatively impacted by
        application performance that slows their workflow. The Project Sponsor and/or the Project Manager sign an acknowledgement that these conditions
        have been satisfied.
    3. Deliverable: End of Warranty Support.
        Outcome: The Contractor is required to retain staff with expert knowledge and hands-on experience with this project‟s software to be available to DOL
        for one-hour response within standard 8 a.m. to 5 p.m. business hours, to fix defects found in the application both prior to production deployment and
        post-deployment. This post-deployment “Warranty Period” will be in effect for 30 calendar days past the date of the application‟s activation into
        production use, or through June 30, 2011 (whichever is first). During the Warranty Period, defects in the code are to be repaired with the high degree
        of urgency on the Contractor‟s part, appropriate to a problem that is impacting state-wide customer service and legislative mandates. If the defect is
        not included in the Detailed Design documents or implemented Change Requests and represents a change or addition in the implemented features, it
        will be submitted as a change request and may be billed at the Contractor‟s hourly rate with prior DOL approval. Upon completion of the Warranty
        Period, the Project Sponsor and/or the Project Manager sign an acknowledgement that that Contractor services and bug fixes initiated during the
        Warranty Period have been completed and were provided to DOL‟s satisfaction.

Deliverables are subject to review and approval by DOL prior to payment.
The Contractor will allow no less than five (5) working days for DOL staff to peer review and comment on draft versions of final document deliverables
defined in this Work Order. (See also Contractor Assumption #10.) Acceptance by DOL must be in writing.

Review and Acceptance of Software Deliverables is to be as described above under „Software Deliverables – Additional Requirements‟. (See also
Contractor Assumption #14.)

 DOL shall provide the Contractor with all reasonable assistance required by Contractor to verify the existence of and correct a reported Deliverable
 nonconformity
Compliance with DOL Standards
The Contractor is expected to comply with all appropriate DOL process standards (Requirements Development and Management, Project Management
Methodology, configuration management, Solutions Delivery Lifecycle, etc.) and division policies (ethics, Internet / email usage, security, harassment). Failure
to comply on a continuing basis will result in contract termination. The DOL shall supply a copy of all such policies to the awarded Contractor.

The Contractor shall not begin any additional work without prior written authorization from DOL's Contract Manager. Such additions may be approved verbally
by DOL's Contract Manager, but shall be documented in writing to the Contractor. Any such addition is not binding upon the DOL until so documented. The
Contractor shall be responsible for submitting a description of additional deliverables, which address purpose and goals. Each description shall include such
information as is necessary for DOL to determine the exact nature of all expenditures (e.g., tasks, timeline, staff assignments, communication strategy,

 File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                   Page 4 of 15                                              Dated: March 11, 2010
                                              Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

           STATE OF WASHINGTON                                                                                           CONTRACTOR’S DIS ITPS MASTER
           DEPARTMENT OF LICENSING                                               AGENCY WORK ORDER NO.                          CONTRACT NO.
           ITPS WORK ORDER
                                                                                            XXXX                                    T08-MST-XXX
deliverables, change control, etc.) Each additional deliverable shall initially be submitted for approval to DOL's Contract Manager in outline form for discussion
of the scope, analytic methods, and organization.

CONTRACTOR ASSUMPTIONS:

General:
  1. All XXXXX‟s resources are committed to the project streams on a full-time basis to completion of the deliverables and potentially less than full-time
      during the period of testing by DOL.
  2. Each stream of work will be completed by a single XXXXX resource and one or more DOL IS staff.
  3. Credit Card processing through the current provider (CyberSource) will remain the same. Contractor will use and modify as necessary the existing DOL
      CyberSource wrapper components for RIP credit card processing.
  4. Database migration to SQL Server 2005 will be performed prior to start of work and tested successfully using the current applications deployed.
  5. 25% of one DOL staff person will be allocated to each of the four work streams throughout the duration of the engagement.
  6. DOL logging and error handling solution standard is completely implemented and related service specification documents are provided.
  7. No new business functionality will be implemented other than that specifically identified in the Work Request and associated documentation.
  8. Additional requirements identified during the Detailed Design phase beyond those stated in the Work Request and associated documentation, if any, will
      be identified to and reviewed by DOL. Upon DOL‟s approval of such additional requirements, the work will be incorporated via a Change Request.
  9. XXXXX assumes timely response to XXXXX requirements for DOL support in the areas of database administration, testing, and architecture review of
      deliverables.
  10. DOL will review and provide written feedback on document deliverables within five (5) business days. One draft version of the written deliverables will
       be produced for review, DOL feedback incorporated, and a final version published. At that point, DOL will accept the document if all DOL feedback
       was accurately incorporated. The document deliverable review and acceptance process will not be repeated for any deliverable non-conformity. Review
       of software deliverables by DOL will repeat until DOL acceptance is achieved.
  11. All technical environments (dev, test, prod, etc.) support the technologies requested in the Work Request and will be in place before development begins.
  12. Clustering and Load Balancing infrastructure is the responsibility of DOL staff. XXXXX resources will develop the applications to be load balance aware
       and configurable.
  13. Ovis Probe configuration and scripting will be developed by DOL staff. Contractor and DOL will identify functions to monitor and confirm that probes
       are working correctly.
  14. Time is of the essence in completing the User Acceptance Testing (UAT) process for each work stream. DOL and XXXXX Systems will work diligently
       to perform tasks necessary to complete UAT.
  15. All applicable and available DOL standards documents that are to be used on the project will be gathered prior to and presented to the teams at the start of
       the engagements. XXXXX Systems‟ consultants will work collaboratively with DOL IS staff to understand the applicable standards during the course of
       the engagement.
  16. Core development tools will initially use Visual Studio 2008, leveraging Framework 3.5 and Microsoft SQL Server 2005. Contractor is expected to
       migrate solutions to Visual Studio 2010 and Framework 4.0 when DOL adopts that technology. Contractor and DOL will migrate SSIS packages to SQL
       Server 2008 when DOL adopts that technology. DOL will be responsible for all database migrations to SQL Server 2008. DOL has not set dates for
       these technology upgrades.
  17. Deliverable #13 (“10% Contingency”) was calculated on the development estimates only.
  RIP Application:
  18. User Interface of the replacement system is estimated based on a standard ASP.NET implementation. WinForms and RIA services were not factored into
       the estimates as these were considered nice but not essential.
  19. The Payment Discrepancy Detail screen has some moderate functionality and processing that will be included in the work being done. The documentation
       provided did not appear to have this detail provided.
  20. Batch Export Control screen and its functionality will not be incorporated in the new replacement system.
  21. Undo Reconciliation navigation will be included in a new logic location for the replacement system.
  22. Reports are already developed and in place in SQL Server Reporting Services; only linking to the reports is in scope of the work.
  23. Although not specifically referenced within the RIP Functional Specs or the Revenue Solution Architecture documents provided during the RFP process,
       the provided source code shows MSMQ is used within this application. Choices about the inclusion or replacement of MSMQ within the other
 File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                  Page 5 of 15                                               Dated: March 11, 2010
                                             Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

           STATE OF WASHINGTON                                                                                           CONTRACTOR’S DIS ITPS MASTER
           DEPARTMENT OF LICENSING                                               AGENCY WORK ORDER NO.                          CONTRACT NO.
           ITPS WORK ORDER
                                                                                            XXXX                                   T08-MST-XXX
       applications of this project should be addressed in the same way within RIP.
  WSP Application:
  24. WSP Access Switch does not need any modifications per the specification.
  25. Databases are already stable and do not need any major modifications.
  26. Estimation is based on the WSP Solution Architecture and WSP Functional Specification provided during RFP process. Any changes to the functional
       specification document will be handled under Change Control. As stated in the architecture documents, DOL expects that the WSP Solution Architecture
       document will change as DOL and the Contractor establish the final architecture.
  27. DOL common Internet Help application is available to be consumed in all environments (PROD, UAT, DEV).
  DAPS Application:
  28. DAPS is a standalone application. Codes/modules/services are designed to be reused within the application and will not provide interface or services to
       other applications unless otherwise specified in the technical document.
  29. Estimation is based on the DAPS Solution Architecture, Web Application Functional Specifications, Vehicle Record Load Functional Specification, and
       Driver Record Load Functional Specifications provided during RFP process. Any changes to the functional specification document will be handled under
       Change Control. As stated in the architecture documents, DOL expects that the DAPS Solution Architecture document will change as DOL and the
       Contractor establish the final architecture.
  30. DOL common Internet Help application is available to be consumed in all environments (PROD, UAT, DEV).
  31. SecureAccess and Transact Washington Web Services are available to be consumed in the Production and UAT environments. There is no support for
       these services in the development environment. A security bypass is needed in the development environment.
  32. SQL Server Integration Services (SSIS) will be the technology used for those jobs that are ETL in nature.
  33. User Interface of the replacement system is estimated based on a standard ASP.NET implementation. WinForms and RIA services were not factored into
       the estimates as these were considered nice but not essential.
  34. Estimates included for ETL batch processes are using SSIS as the tool. Refinement to the estimates will be made initially when starting the analysis to
       determine if the time would be the same to implement a real-time SQL Service broker mechanism.

WORK PERIOD OF PERFORMANCE START DATE                        March 15, 2010           END DATE                        June 30, 2011

SECTION 3: COMPENSATION: The Contractor agrees that DOL shall NOT be responsible for any additional costs or expenses incurred by Contractor in the
performance of work described in this Agreement, which include but are not limited to travel, lodging, meals, and other miscellaneous expenses otherwise
incurred by the Contractor. DOL shall pay up to but not to exceed 80% of the maximum cost of each deliverable. The remaining amount due shall be payable
upon completion of the work and acceptance of the final deliverable by DOL. Compensation for a deliverable shall be up to but shall not exceed the budgeted
cost for a deliverable regardless of hours worked or other expenses related to a deliverable. Contingency will only be used for approved Change Requests that
have been submitted to the DOL Contract Manager and approved in writing. Any variance shall be justified to DOL's Contract Manager who shall have
discretion to approve/ disapprove compensation for such variance.
                                      Check the appropriate Box and fill in the number of Workstations assigned, if applicable
           Compensation for work (see table below) associated with this Project will
       be based on completion or percentage completion of deliverables. DOL shall                        Individual                      Hourly Rate
       pay up to but not to exceed 80% of the maximum cost of each deliverable. The      XXXXX                                        $120.00
       remaining amount due shall be payable upon completion of the work and             XXXXX                                        $120.00
       acceptance of the final deliverable by DOL.                                       XXXXX                                        $120.00
           Some deliverables (see table on right) associated with this Project cannot    XXXXX                                        $120.00
       be clearly defined in advance. The selected vendor will be compensated based
       on hourly rate(s) for work actually performed.
          Yes No The Contractor is assigned          workstation(s) and assessed a
       workstation fee of $108.00 per month for each workstation.




 File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                  Page 6 of 15                                              Dated: March 11, 2010
                                           Performance-Based Contracting Example
                                               This is an example only and not required for agency use.



                                                                                                     Projected                                Not to
           Deliverable                                                Skill     Primary
                                      Functional Specs                                               Duration (#of   Est.       Staff         Exceed
           Description                                                Level     Experience Needed
                                                                                                     Wks)            Hours                    Cost


       DOCUMENT
       DELIVERABLES:

1      Weekly Status Reports          Prepare weekly (or as
                                      requested) status reports
                                      using an Excel or Word
                                                                      Senior    MS Office 2007                         170
                                      template provided by the                                            35                        All              $20,000
                                      DOL Project Manager
                                      (PM).
2      Collaborative Work Plans       Establish at the beginning of
                                      work on the Detailed
                                      Design document and the
                                      Programming a written                                                                       XXXXX
                                      work breakdown with time                                             3
                                                                      Expert    MS Office 2007                         100
                                      estimates and assignment of                                                                 XXXXX              $12,000
                                      the work between the
                                      contractor and DOL AL.
                                      Include tasks required of
                                      others during this activity.
3      Migration Wrap-up Reports      Document (one per
                                      application migrated)
                                      summarizing decisions
                                      made during preparation of
                                      the detailed design and
                                                                                                           1                        All
                                      programming along with the      Expert    MS Office 2007                         125
                                                                                                                                                     $15,000
                                      lessons learned and
                                      suggestions for the process
                                      changes for use when
                                      migrating other
                                      applications.
4      Defect Cause & Correction      For each defect logged into
                                      the project SharePoint site,
                                      the contractor will record
                                      with that entry the cause of    Expert    SharePoint                 3           190
                                                                                                                                    All              $23,000
                                      the defect and the corrective
                                      action(s) that were required
                                      to fix the defect.
5      Detailed Design Document –     In collaboration with the
       RIP application                Application Lead, develop a
                                      work plan for creating the                MS Office 2007
                                      Detailed Design document                  VB.6, VB.net,
                                                                      Expert                                           275
                                      and then create, refine and               ASP.net, .net 3.5+         8                      XXXXX              $33,000
                                      submit the document for                   Framework,
                                      review and approval.

6      Detailed Design Document –     Same as for RIP
       RevVal (RevVal, Revenue
                                                                                MS Office 2007
       Cash, Acct.Code Maint, Acct.
                                                                                VB.6, VB.net,              6
       Period Status) &                                               Expert                                           205
                                                                                ASP.net, .net 3.5+                                XXXXX              $24,500
       Misc.Rev.Recd.Rpt
                                                                                Framework,
       applications

7      Detailed Design Document –     Same as for RIP
                                                                                MS Office 2007
       WSP Gateway application
                                                                                VB.6, VB.net,
                                      See Functional                  Expert                               7           220        XXXXX              $26,500
                                                                                ASP.net, .net 3.5+
                                      Specifications:
                                                                                Framework,
8      Detailed Design Document –     Same as for RIP                           MS Office 2007
       DAPS application                                                         VB.6, VB.net,
                                                                      Expert                               8           260        XXXXX              $31,000
                                                                                ASP.net, .net 3.5+
                                                                                Framework,

       SOFTWARE
       DELIVERABLES:

9      Reprogrammed – RIP              Write/modify code to          Expert    MS Office 2007            20           640        XXXXX              $77,000

File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                   Page 7 of 15                                           Dated: March 11, 2010
                                              Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

       application                          approved Architectural                 VB.6, VB.net,
                                            Specifications, and                    ASP.net, .net 3.5+
                                            Detailed Design                        Framework, Visual
                                            documents, produced as                 Studio
                                            a document deliverable
                                            of this project...
                                          Unit test each code
                                            delivery and provide a
                                            report of the test results
                                            to the Project Manager
                                            with the delivery.
                                          Correct defects identified
                                            during all test phases.
                                          An Ovis Probe script
                                            must be provided for
                                            monitoring performance
                                            of each application
10     Reprogrammed - RevVal             Same as for RIP                           MS Office 2007
       (RevVal, Revenue Cash,                                                      VB.6, VB.net,
       Acct.Code Maint, Acct. Period                                     Expert    ASP.net, .net 3.5+    20    625          XXXXX              $75,000
       Status) & Misc.Rev.Recd.Rpt                                                 Framework, Visual
       applications                                                                Studio
11                                                                                 MS Office 2007
                                         Same as for RIP                           VB.6, VB.net,
       Re-Program – WSP Gateway
                                                                         Expert    ASP.net, .net 3.5+    17    535          XXXXX              $64,000
       application
                                                                                   Framework, Visual
                                                                                   Studio
12                                                                                 MS Office 2007
                                         Same as for RIP                           VB.6, VB.net,
       Re-Program – DAPS
                                                                         Expert    ASP.net, .net 3.5+    17    540          XXXXX              $65,000
       application
                                                                                   Framework, Visual
                                                                                   Studio
13     Change Requests – Vendor
       will include a 10%
       contingency in the bid to cover   See Deliverables – Change                 VB 6.0, VB.net,       N/A                  All
                                                                         Expert                                240
       the event that a “change          Management Section                        SQL, COBOL.net                                              $29,000
       request(s)” is required (based
       on time and materials).

                                                                             Total Duration/Hours/Cost         4,125                       $495,000




File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                      Page 8 of 15                                  Dated: March 11, 2010
                                             Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.




  SECTION 4: SPECIAL TERMS & CONDITIONS

  1    Protection of Purchasers Confidential Information: The final sentence of section 18.5 of the Master Contract shall be replaced with the following : If
       data compromise and/or identity theft occurs and is found to be the result of Contractor‟s acts or omissions, Contractor shall assume complete
       responsibility for notification of affected parties, and be liable only for the direct costs incurred by DOL in responding to or recovering from the breach.
  2    Save Harmless: Section 36 of the Master Contract shall be amended by adding the following language to the end of the provision as a new sentence: The
       Contractor‟s liability for any and all claims related to this Work Order shall be limited to direct damages suffered by the D OL under this work order, and in
       aggregate will not exceed the total fees actually paid to the Contractor under this Work Order.
  3    Termination for Default: Section 51.2 of the Master Contract shall be amended by adding the following language to the end of the provision as a new
       sentence: Notwithstanding the foregoing, in no event shall Contractor‟s liability under this Work Order exceed the total value of this Work Order o r the
       affected Work Product or Services under this Work Order.
  4    Safeguarding of Confidential Information: The Contractor shall not use or disclose Confidential Information in any manner that would constitute a
       violation of federal law or applicable provisions of Washington State law. The Contractor agrees to comply with all federal and state laws and regulations,
       as currently enacted or revised, regarding data security and electronic data interchange of Confidential Information. The Contractor shall prote ct Personal
       Information collected, used, or acquired in connection with this Contract, against unauthorized use, disclosure, modifi cation or loss. The Contractor shall
       ensure its directors, officers, employees, Subcontractors or agents use it solely for the purposes of accomplishing the servi ces set forth in this Contract.
       The Contractor and its Subcontractors agree not to release, divulge, publish, transfer, sell or otherwise make it known to unauthorized persons without the
       express written consent of DOL or as otherwise authorized by law. The Contractor agrees to implement physical, electronic, a nd managerial policies,
       procedures, and safeguards to prevent unauthorized access, use, or disclosure. The Contractor shall make the Confidential Information av ailable to amend
       as directed by DOL and incorporate any amendments into all the copies maintained by the Contractor or its Subcont ractors. The Contractor shall certify its
       return or destruction upon expiration or termination of this Contract‟s retention requirements and the Contractor shall retai n no copies. If the Contractor
       and DOL mutually determine that return or destruction is not feasible, the Contractor shall not use the Confidential Information in a manner other than
       those permitted or authorized by state and federal laws. DOL reserves the rights to monitor, audit, or investigate the use of confidential information
       collected, used or acquired by the Contractor through this Contract. The monitoring, auditing, or investigating may include, but is n ot limited to, “salting”
       by DOL. Salting is the act of introducing data containing unique but false information that can be used l ater to identify inappropriate disclosure of data.
       The Contractor shall notify DOL in writing within 5 working days of becoming aware of any unauthorized access, use or disclos ure. The Contractor agrees
       to indemnify and hold harmless DOL for any damages related to unauthorized use or disclosure by the Contractor, its officers, directors, and employees,
       Subcontractors or agents. Any breach of this clause may result in termination of the Contract and the demand for return of al l Confidential Information.
  5    Insurance: The Contractor shall provide insurance coverage as set out in this section. The intent of the required insurance is to prote ct the State should
       there be any claims, suits, actions, costs, damages or expenses arising from acts or omissions of the C ontractor or Subcontractor, or agents of either, while
       performing under the terms of this Contract.
       The Contractor shall provide insurance coverage which the Contractor shall maintain in full force and effect during the term of this Contract as follows:
               Professional Liability, Errors and Omissions Insurance: The Contractor shall maintain Professional Liability or Errors and Omissions Insurance. The
               Contractor shall maintain minimum limits of no less than $1,000,000 per occurrence to cover all program activities by the Contractor and licensed staff
               employed or under contract to the Contractor.
  6    Confidentiality: The use or disclosure by any party of any information concerning DOL for any purpose not directly connected with the administ ration of
       DOL's or the Contractor's responsibilities with respect to services provided under this Work Order is prohibited except by prior written consent of DOL.
       The Contractor shall maintain as confidential all information concerning the Contractor's study findings and recomm endations, as well as the business of
       DOL, its financial affairs, relations with its clientele and its employees, and any other information which may be specifical ly classified as confidential by
       DOL in writing to the Contractor. To the extent consistent with Washington State law, DOL shall maintain all information which the Contractor specifies
       in writing as confidential. The Contractor shall have an appropriate contract with its employees to this effect .
  7    DISPUTES: The parties agree that time is of the essence in resolving disputes. During the dispute resolution period the parties agree that:
       If the subject of the dispute is the payment due the Contractor, the Contractor will continue performance and DOL will pay th e amount that it in good faith
       believes to be due and payable. If the subject of the dispute is not the payment due, the Contractor will continue performance of w ork under the Contract
       that is not affected by the dispute. Dispute Steps:
        When a bona fide dispute concerning a question of fact arises between DOL and the Contractor and it cannot be resolved, either party may request a
              dispute hearing with DOL's Contracts Office. The request for a dispute hearing must:
                    o be in writing;
                    o state the disputed issues;
                    o state the relative positions of the parties;
                    o state the Contractor's name, address, and DOL Contract Number; and
                    o be mailed to the Contracts Office and the other party's Contract Manager within 3 working days after the parties agree that t hey cannot resolve
                          the dispute.
         The responding party shall have 5 working days to respond in writing to the requesting party's statement. This response will be sent to both the Con tracts
          Office and the requesting party.
         The Contracts Office shall review the written statements of the parties and reply in writin g to both parties within 10 working days. The Contracts Office
          may extend this period if necessary by notifying the parties.
         The decision of DOL's Contracts Office shall be final and conclusive unless, within 5 working days from the date the Contractor signed the Certified Mail
          Return Receipt, the Contractor requests a dispute panel. This request must be in writing to DOL's Contracts Office.
         If a dispute panel is requested, DOL and the Contractor shall each appoint a member to the dispute panel within 5 w orking days. DOL and the Contractor
          shall jointly appoint a third member to the dispute panel within the next 5 working days.
         The dispute panel shall review the written descriptions of the dispute, gather additional information as needed, and make a decision on the dispute within
          180 business days with the majority prevailing. The parties agree that the decision of the dispute panel shall be final and binding.
  8    Site Security: While on DOL premises, Contractor, its agents, employees or subcontractors sha ll conform in all respects with physical, fire or other
       security regulations. DOL will provide copies of related policies, regulations, etc., as required.
  9    Changes to the Work Order: Any communications that either Project Manager determines to address more than day-to-day concerns, but do not modify
       the terms of this Work Order, shall be documented by a written, numbered Memo of Understanding (MOU). Changes to the Work Order, which extend the
       end date, increase the maximum compensation, or involve a change in the scope of work, require an Amendment to the Work Order. Amendments must be
       in writing, signed by DOL and the Contractor.


File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                     Page 9 of 15                                                  Dated: March 11, 2010
                                               Performance-Based Contracting Example
                                                   This is an example only and not required for agency use.

  10   Funding Contingency: In the event funding from state, federal, or other sources is withdraw, reduced, or limited in any way a fter the effective date of this
       Work Order and prior to normal completion, DOL may terminate this Work Order without advance notice subject to renegotiation under those new funding
       limitations and conditions.
  11   Billing Procedures: DOL will pay the Contractor within 30 calendar days of receipt of properly executed invoice vouchers. Requests for payment under
       this Work Order shall be submitted by the Contractor on State Invoice Voucher (Form A -19), or similar. Invoices shall include such information as is
       necessary for DOL to determine the date and exact nature of all expenditures. Each voucher will clearly reference the Work Order number and pe rcent of
       the cost of each deliverable, which the Contactor would pay to any subcontractors, if any, to accomplish t he tasks and to produce the deliverables under the
       Work Order. Vouchers shall be submitted to DOL‟s Project Manager.
       No payment in advance or in anticipation of services or supplies under this Work Order shall be made by DOL. Claims for payment submitted by the
       Contractor to DOL for costs due and payable under this Work Order that were incurred prior to the expiration date shall be pa id to the Contractor, if
       received by DOL within 90 days after the expiration date.
       Timely payment. Payment by DOL will be considered timely if a check or warrant is postmarked within 30 days of receipt of either of the following,
       whichever is later: Receipt of properly executed invoice vouchers; or acceptance of deliverables by DOL.
  12   Workstation Fee: If the Contractor is assigned a workstation onsite at a DOL location, DOL will charge the Contractor a workstation fee of $108 per month to
       cover costs for each workstation assigned. This amount shall be invoiced by the Contractor on a monthly basis as a credit against invoiced charges to DOL. If the
       Contractor has performed no billable work during a month, the Contractor shall pay DOL the workstation fee, or with approval of DOL‟s Project Manager, arrange
       for an alternate payment method.
       First & Last Month Charge: DOL will prorate the workstation fee charged for the first and last month of use as follows: $108 per workstation multiplied by the
       number of days of use. The result of this will be divided by the number of days in the month; this will equal the prorated charge for that month.
       Workstation Termination: DOL shall have the right to unilaterally terminate the Contractor‟s workstation assignment at anytime and with five (5) working days
       advance written notice.
       Multiple Work Orders and/or Workstations: If the Contractor has more than one open Work Order and/or assigned workstations, the parties shall determine and
       document in Memos, to which Work Order(s) the workstation fee will be assigned. When a Work Order with a workstation fee is complete and the Contractor
       wishes to continue use of the workstation for another Work Order, the parties shall document in a Memo to which Work Order the workstation fee shall be invoiced.
       Failure to Pay: If the Contractor fails to credit or pay a monthly workstation fee to DOL, the parties specifically agree that DOL‟s Project Manager for the Work
       Order shall have the right to deduct the workstation fee from the invoiced amount and authorize the corrected invoice for payment or take other action deemed
       appropriate.
  13   Independent Status of Contractor: In the performance of this Work Order, the parties will be acting in their individual, corporate or governmental capacities and not
       as agents, employees, partners, joint venturers, or associates of one another. The parties intend that an independent contractor relationship will be created by this
       Work Order. The employees or agents of one party shall not be deemed or construed to be the employees or agents of the other party for any purpose whatsoever.
       Contractor shall not make any claim of right, privilege or benefit which would accrue to an employee under chapter 41.06 RCW or Title 51 RCW for any work
       conducted under this Contract or any Work Order.
  14   Assignment of Staff: The Vendor staff identified in the response to the Work Request will work for at least the approximate number of hours described. DOL may
       at their sole discretion, without cause, and at any time during the term of the Work Order, require immediate replacement of a Vendor‟s employee(s). Unless
       authorized in writing in advance by DOL‟s Work Order Manager, subcontracting or substituting proposed Vendor staff/employees with other staff/employees will
       not be allowed. The DOL Contract Manager shall have the sole discretion to accept or reject such proposal. As a condition to accepting Contractor‟s proposal for
       personnel changes, DOL may require Contractor to compensate DOL for any training and administrative costs incurred by DOL in association with such
       replacement. Such compensation will be in the form of a credit against Contractor‟s monthly invoice charges to DOL by Contractor (a) not billing DOL for hours
       worked during the first ten (10) Business Days replacement personnel begin work, if the method of compensation agreed to in the Work Order is by hourly rates
       (time and material); or (b) crediting DOL an amount not to exceed $5,000 per person replaced, if the method of compensation agreed to in the Work Order is by
       deliverables (fixed cost). If DOL does not accept Contractor‟s proposed change and Contractor is unable to provide acceptable personnel to Purchaser within ten (10)
       Business Days after the originally assigned personnel have left, then DOL may terminate the Work Order.
       DOL may assign other vendors and/or DOL staff to work with the Vendor. The Vendor shall work collaboratively and share knowledge and expertise with DOL to
       ensure a successful and timely completion. Vendor shall not supervise DOL employees. The Statement of Work is not intended to completely describe all work the
       Vendor would need to complete the deliverables. The Vendor shall control the manner and means and otherwise do all things necessary for or incidental to the
       performance of work set forth in the Statement of Work.
  15   Performance Monitoring Report: Impacts and outcomes achieved as a result of the delivery of services may be measured and evaluated by DOL in a
       Performance Monitoring Report form. DOL may evaluate Contractor performance at Work Order completion and at least once a year. An annual
       evaluation will be conducted during the sixty-day period following the Work Order anniversary date, except DOL can establish, a date, which better
       accommodates DOL‟s particular needs. The evaluation will cover the period ending with an established due date. DOL may utilize the standardized form
       and/or supplement the process with special performance factors peculiar to the specific contractual needs. Each evaluation shall include an as sessment of
       the Contractor‟s efforts toward achieving DOL‟s objectives. The form is designed to aid DOL in referrals, clarify Contractor‟s duties and DOL
       expectations, and inform Contractors of their performance strengths and weaknesses.
  16   Order of Precedence: The items listed below are incorporated by reference herein. In the event of an inconsistency in this Work Order, or conflic t with
       the Contractor‟s ITPS Master Contract with the Department of Information Services, unless otherwise provided herein, the inconsistency shall be resolved by
       giving precedence in the following order:
       1.   Applicable Federal and Washington State Statutes and Regulations;
       2.   Terms & Conditions as contained in this Work Order;
       3.   Statement of Work, Section 2 of this Work Order
       4.   DOL‟s Work Request WRXXXX dated January 28, 2010;
       5.   Contractor‟s proposal (response to Work Request), dated February 15, 2010;
       6.   Contractor‟s ITPS Master Contract #T08-MST-XXX with the Department of Information Services;
       7.   Any other provisions of the Work Order incorporated by reference or otherwise.




File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                       Page 10 of 15                                                    Dated: March 11, 2010
                                                  Performance-Based Contracting Example
                                                      This is an example only and not required for agency use.

                                                                                 APPENDIX A
                                                Business Software Maintenance (BSM) Project: Guiding Principles
     1. Application migration shall be performed as quickly and efficiently as possible, allowing that neither learning by DOL Application Leads (AL) or quality of the work
         products should be sacrificed.
     2. The business features of each application are to remain essentially as-is. Unused features may be dropped and a few minimum-impact features may be added if
          authorized by the CIO.
     3. Because this is a technology change to the applications, not a business process re-engineering, there is an expectation that the standard DOL procedures for adding or
          modifying application features can and should be simplified. The goal is to speed the requirements and design process. Where possible required business logic and
          application navigation information should be extracted from the code (with the help of the AL), rather than through interviews with business users.
     4. The two requirements of this project are to: (1) eliminate the risk of infrastructure incompatibility by re-writing the applications in contemporary languages to
          contemporary architectural standards, and (2) make each application much easier and quicker to maintain while increasing creation and use of reusable code
          (services). Key to achieving this goal is suggestions and guidance from the expert contract Programmer-Analyst. The advice is to include architectural policies and
          best practices, application of tools and methods within the .net 3.5+ framework, and efficient and effective use of constructs within the VB.net and ASP.net
          languages. Advice may also include, but not be limited to, use of object oriented design, appropriate data and data access service design and inclusion of service
          oriented architectural principles.
     5. Training of DOL IS staff comes from hands-on experience in use of the latest technologies and tools to do the application upgrades, guided and mentored by contractors
          with expert-level skills and experience with these technologies. (Both the contractor and DOL IS staff will work side-by-side to prepare the detailed design
          (programming specification) document, then program the new version of the application. Each AL will be paired with a contract expert to maximize collaborative
          learning and completion of work. It is desired that DOL staff leave this project with the ability to repeat the technology upgrade process for the many remaining DOL
          legacy applications.
     6. During this project, every opportunity should be taken to create and adopt improved ways of application design and development and processes for legacy application
         migration. These improved methods will be applied again as DOL migrates other legacy applications in its software portfolio. Ideas should be documented, but
         formal methods improvements work should not take priority over or divert significant effort from the migration task itself.
     7. The applications are to be architected into at least three layers (tiers): Presentation, Business Logic, and Data Access.
     8. New (Washington State Information Services Board) computer application security practices shall be implemented whenever possible.
     9. Very few of the existing database tables can be restructured because they are used by applications other than the ones being re-designed and re-written, however re-
         designed to object-oriented and 3rd-Normal structures should be considered when practical.
     10. Data Access services are to be created to isolate the application from the design of the underlying database(s). The view of the data to the application should make the
          application easier to modify while preserving sub-second access and update times for online and web-based user interface.
     11. Where appropriate, data management logic currently implemented as database stored procedures or triggers should be replaced by logic in the data access service.
     12. The DOL Architecture Group is in the process of planning DOL‟s transition to software development based on Service Oriented Architecture (SOA) principles. We are
           also actively engaged with the Washington State Dept. of Information Services in creating Statewide standards and policies to guild effective sharing and reuse of
           services. When there is no negative risk to the project‟s on-schedule delivery of the re-written application, new standards and procedures that are developed by DOL
           or the State-level groups should be incorporated into this project‟s deliverables.
     13. Some effort should be placed on identifying reusable services within the applications being migrated, and building new services as the applications are being re-
           designed and re-written.
     14. Application response time and performance under load can‟t be degraded by the migration changes. Likewise batch jobs must continue to complete within their
          existing time windows.
     15. Although we consider it unlikely that an automated migration tool with the features listed below exists, DOL will consider suggestions from the Contractor about use of
           automated tools to migrate the applications from their current “old” languages, IF the automated migration also:
                a. separates the application into Presentation, Business Logic and Data Access layers;
                b. Suggests database structure or data access services and code structures / services that provide code and data structures that are easier and quicker to modify
                     and maintain with less knowledge about the application specifics;
                c. Provides the DOL ALs the opportunity to learn and apply the new architecture and capabilities of Visual Studio, the .net3.5+ framework, VB.net and
                     ASP.net.
     16. Programming is to be done using VB.net, ASP.net and SQL 2005+ under the Windows .net 3.5+ Framework, compiled with “strict” and “explicit” turned on, and may
           not be deployed with “debug” mode active.
     17. Applications must operate under Internet Explorer 7 and 8.
     18. Batch jobs run under the TIDAL batch scheduler.
     19. Client side execution of the applications must run under Windows (Vista and Windows 7)
     20. The applications must operate on load-balanced servers and clustered Storage Area Networks (SANs). DOL load balancing does not guarantee sessions remain with a
           single server.
     21. Visual Studio 2008 or later provides the development integration environment.
     22. All code is to be managed per DOL‟s Configuration Management and Code Promotion Procedures including formal Check-out/ Check-in to Team Foundation Server
           (TFS) against DOL‟s standard folder structure. All software will be compiled using the TFS Build Server.
     23. Feature changes and additions may be made to the application by other projects while work is underway on this project. The AL has responsibility for bringing details
           of those changes to the contractor as soon as possible and then collaborate with the contractor to include the changes into the migrated version, using TFS Branch &
File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                          Page 11 of 15                                                      Dated: March 11, 2010
                                             Performance-Based Contracting Example
                                                 This is an example only and not required for agency use.

        Merge where appropriate. Most such changes are small and should be included in the normal scope of work. However, if significant extra effort results, it may
        require creation of a formal change request.




File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                     Page 12 of 15                                                    Dated: March 11, 2010
                                               Performance-Based Contracting Example
                                                  This is an example only and not required for agency use.

                                                                          APPENDIX B
                                                              Map of Detailed Design document Content


    DETAILED DESIGN (Programming Specification) (one per application)
      1. Introduction to Application                                                        4. Web Services
               a. Overview of Programming Plan                                                     a. Name, Purpose, existing/new
               b. Delivery of Business Functions                                                   b. Page Reference
               c. Security Implementation                                                          c. Code Behind
               d. Software Architecture                                                            d. IPO Service URLs
               e. Diagrams                                                                         e. TFS Source Code Location
                        i. Business Workflow                                                       f. Guidelines for Developers to use/consume this service
                       ii. Software Component flow                                                 g. Request Objects (Input Parameters)
                      iii. Dataflow                                                                h. Response Objects (Results)
                                                                                                   i. Functions & Descriptions
      2. System Requirements                                                                       j. Stored Procedures
              a. Development Environments & Tools                                                  k. Testing Considerations
              b. Production Environment Requirements
              c. Client Side Requirements                                                   5. Screens
              d. Server Systems Requirements                                                        a. Common features & standards
              e. Constraints from Load Balancers                                                    b. Name & Description
              f. System-Network Architecture                                                               i. Purpose
              g. Backup / Recovery                                                                        ii. Page Reference
              h. Performance Metrics                                                                    iii. Code Behind
              i. Ovis Probe (operational monitoring)                                                     iv. Data Sources
              j. Scalability Constraints                                                                  v. Form Controls & Links
              k. Parameters Referenced in .ini & .cfg files                                              vi. Initialization
              l. Error Logs                                                                             vii. Input Validation
                                                                                                       viii. Called Functions
      3. Program Components                                                                              ix. Stored Procedures
              f. Name, Purpose,                                                                     c. Testing Considerations
              g. Type of Component & Software Layer(s)
              h. Programming Language                                                       6. Reports
              i. Global & Common Variables                                                         a. Common features & standards
              j. Parameters referenced via .ini or .cfg files                                      b. Name & Description
              k. Accuracy & Validity Checks                                                                i. Purpose
              l. Timing & Performance metrics                                                             ii. Page Reference
              m. Concurrent Usage – Database Locking                                                    iii. Code Behind
              n. Scalability                                                                             iv. Frequency
              o. Support Software Environment / Components                                                v. Input Parameters/Data Source(s)
              p. Interfaces                                                                              vi. Report Fields & Columns
                      Message Transfer Mechanism                                                       vii. Sort Order & Grouping
                      Message content                                                                 viii. Sample Report Layout
                      Message Timing                                                              c. Testing Considerations
                      Message Transfer Confirmation                                        7. Batch Processing
              q. Internal & Temporary Storage                                                       a. Name, Purpose
              r. User Access & Data Security                                                        b. Page Reference
              s. Design Details                                                                     c. Code Behind
                      Inputs                                                                       d. TIDAL Configuration
                      Outputs                                                                             i. Job Name
                      Logic / Algorithms                                                                 ii. Command & Command Parameters
                      Use of shared services and common components.                                     iii. Schedule (calendaring)
              t. Testing Considerations                                                             e. Environment Configuration
                                                                                                    f. Functions (Name, details)
                                                                                                    g. Stored Procedures
                                                                                                    h. Testing Considerations




File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                     Page 13 of 15                                             Dated: March 11, 2010
                                          Performance-Based Contracting Example
                                             This is an example only and not required for agency use.



  IN WITNESS WHEREOF, the parties have executed this Work Order.
  By signing below AGENCY and the Contractor acknowledge that this Work Order is issued under the provisions of the State of Washington Department
  of Information Services Information Technology Professional Services Master Contract Program. The services authorized are within the scope of
  services set forth in the Purpose of the Master Contract between DIS and the Contractor. All rights and obligations of the parties are subject to and
  governed by the Master Contract including any subsequent modifications incorporated herein. The persons signing below warrant that they have the
  authority to execute this Work Order.
  CONTRACTOR
                          XXXXX XXXXX, Inc.                                      AGENCY                               DEPARTMENT OF LICENSING
  NAME
                        XXXXX Street NE, Ste XXX
  ADDRESS                                                                                                             1125 WASHINGTON ST
                        Olympia, WA 98501                                         ADDRESS
                                                                                                                      Olympia, WA 98504
  E-MAIL                XXXXX@XXXXX.com
  PHONE                 360) XXX-XXXX
  FAX                   360) XXX-XXXX                                                                                 JERRY ANDERSON, SIGNATURE
                                                                                  AAG APPROVAL
                                                                                                                      ON FILE


     (Signature)     (Date)                                                       AUTHORIZED SIGNATURE                DATE
  PRINT NAME
                                                                                                                      Assistant Director
  TITLE
  FEDERAL ID
                                                                               PRINT NAME                        TITLE
  CERTIFICATE OF INSURANCE REQUIRED        YES     NO
                                  Agency’s Work Order Manager and the Contractor’s Work Order Manager
         are responsible for and shall be the contact person for all communications/billings regarding performance of this Work Order.
  CONTRACTOR WORK ORDER                                                        AGENCY WORK ORDER
                                XXXXX                                                                      XXXXX
  MANAGER                                                                      MANAGER
                                XXXXX Street NE, Ste XXX                                                   405 Black Lake Blvd, SW
  ADDRESS                                                                      ADDRESS
                                Olympia, WA 98501                                                          Olympia, WA 98502
  TELEPHONE NUMBER              (360) XXX-XXXX                                 TELEPHONE NUMBER            (360) XXX-XXXX
  E-MAIL                        XXXXX@XXXXX.com                                E-MAIL                      XXXXX@dol.wa.gov




File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc              Page 14 of 15                                            Dated: March 11, 2010
                                                DOL PERFORMANCE MONITORING REPORT

PERFORMANCE MONITORING REPORT                                                    DIS CONTRACT NUMBER                DOL WORK ORDER NO.
STATE OF WASHINGTON
DEPARTMENT OF LICENSING (DOL)

DOL‟s Contract Manager may complete a                    Annual                                      CONTRACTOR’S NAME
Performance Monitoring Report at least                   Deliverable
annually and/or at the end of each project and/or
deliverable.                                             Final

PREPARED BY                                                                                         CONTRACTOR CONTACT
DATE PREPARED
PHONE NO.                                                                                     PERIOD OF PERFORMANCE MEASURED
E-MAIL                                                                  START DATE                             END DATE
SECTION 1 - RATINGS                                                                                                        RATING
Please rate your experience by placing an “ ” in the appropriate column                                         N/A    1    2        3
1 (Did Not Meet Expectation), 2 (Met Expectation), 3 (Exceeded Expectation), or N/A (Not Applicable)
1. Performed statement of work/technical specification requirements to agency expectation
2. Performed technical work using approved standards, tools and methods
3. Contractor‟s overall expertise and use of effective project management skills
4. Performed work within project schedule
5. Performed work within project budget
6. Performed work in compliance with agency policies and procedures.
7. Demonstrated professional communications
8. Provided accurate and properly constituted invoicing
9. Provided timely response and resolution to any problem or issue
10. Overall satisfaction with the quality of contract work and conduct of the contractor
                                                                                                                   YES        NO
11. Did Contractor complete all work (projects, deliverables, etc.) specified in the Contract/ Work Order?
12. Would you hire this Contractor again?
13. Would you recommend this Contractor?
SECTION 2 - DOL’S NARRATIVE (Provide a brief description of the work performed)
It is the purpose of this Work Order to (e.g., provide, obtain, etc.)

1.) THE CONTRACTOR WAS VERY GOOD IN THE FOLLOWING AREAS/SKILLS:


2.) THE CONTRACTOR NEEDS IMPROVEMENT IN THE FOLLOWING AREAS/SKILLS:


3.) PLEASE ELABORATE ON ANY AREAS IN SECTION 1 ABOVE WITH A RATING OF “1”:


4.) ADDITIONAL COMMENTS, IF ANY ON OVERALL PERFORMANCE OR OTHER APPLICABLE ISSUES:

                                                        (Attach additional sheets if necessary)
                                                      SECTION 3 - CONTRACTOR’S COMMENTS
                          Brief comments/suggestions from the Contractor for DOL‟s Contract Manager or DOL management?




                                                           (Attach additional sheets if necessary)




     File Name: a13e7394-5d92-4313-8fe1-c7e3e968b368.doc                   Page 15 of 15                                   Dated: March 11, 2010

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:7
posted:8/1/2011
language:English
pages:15
Description: Purpose of Perfomance Management document sample