Description
STATEMENT OF OBJECTIVES, DELIVERABLES AND CONSTRAINTS The United States Coast Guard ("Client") and [Company Name] ("Company") agree that the following describes the specific objectives, deliverables and constraints for specific Software Upgrade tasks as generally contracted for between the Parties. 1. Statement of Work for Additional Consulting Services. Subject to the terms, conditions and assumptions contained herein, [Company] will provide and Client will pay for the following additional Consulting Services: 1.1. Additional Functionality. All efforts, functionality and documentation described in Section 1.1 are not subject to the MarkView product support terms and conditions. 1.1.1. Enhanced MarkView Authentication. The following section covers the tasks [Company] will perform to implement enhanced MarkView Authentication. 1.1.1.1. MarkView Password Web Application. [Company] shall configure a MarkView Password Web Application that will allow the Client user base to set their password in accordance to the requirements listed below. The Client user base will not be able to save or update a password that does not meet the requirements listed below and will receive one of the following three (3) messages. • "Password should be at least eight (8) characters in length and contain a combination of alphabetic, numeric and special characters." • "Password cannot be the same as the previous 8 passwords used." • "Password cannot be the same as your User ID." The above messages will be stored as a MarkView Preference which may be updated by the Client's MarkView Administrator. 1.1.1.1.1. Require MarkView Passwords To Be At Least Eight (8) Characters. [Company] shall configure the MarkView solution such that the MarkView Password must contain at least eight (8) characters. 1.1.1.1.2. Require MarkView Passwords To Contain An Alphabetic, Numeric, and Special Character. [Company] shall configure the MarkView solution such that the MarkView Password must contain at least one (1) alphabetic character, one (1) numeric character, and one (1) special character. The specific format required is "Regular Expression" and will be stored as a MarkView Preference which may be updated by the Client's MarkView Administrator. The initial format will be: " ( ? ! ^ [ 0 - 9 ] * $) (? ! ^ [ a - z A - Z 0 - 9 ] { 8, 40 } ) $ ‘ ) " 1.1.1.1.3. Require MarkView Password Uniqueness Across Eight (8) Passwords. [Company] shall configure the MarkView solution such that the current MarkView Password is not one of the same as one (1) of the previous eight (8) passwords. 1.1.1.1.4. Require MarkView Password Uniqueness From User ID. [Company] shall configure the MarkView solution such that the MarkView Password is not the same as the User ID. 1.1.1.1.5. Require Encrypted MarkView Password. The MarkView solution will store the MarkView Password in the MarkView Database schema in an encrypted format. 1.1.1.2. Lock MarkView User Account Upon Three (3) Failed Login Attempts. [Company] shall configure the MarkView solution such that a user account will be locked out for a minimum of twenty (20) minutes upon three (3) failed login attempts. The number of failed login attempts as well as the lock out period will be stored as MarkView Preferences which may be updated by the Client's MarkView Administrator. 1.1.1.3. Require Password Change Upon Initial MarkView Login. [Company] shall configure the MarkView solution such that a user will be required to change their password upon their initial login to MarkView. 1.1.1.4. Require Password Change Every Ninety (90) Days. [Company] shall configure the MarkView solution such that a user will be required to change their password every ninety (90) days. The change password timeframe will be stored as a MarkView Preference which may be updated by the Client's MarkView Administrator. 1.2. Installation. [Company] shall remotely support Client's installation of the Enhanced MarkView Authentication functionality in a single Oracle Applications Release 11i, MarkView 7.0.1 development environment for up to two (2) hours. Efforts beyond these two (2) hours must be purchased separately. 1.3. Client Testing Support. [Company] shall remotely support Client's testing for up to sixteen (16) hours. These sixteen (16) must be utilized within two (2) contiguous business weeks of the conclusion of the initial installation described in Section 1.2. Efforts beyond these sixteen (16) hours must be purchased separately. 1.4. Migration Support. [Company] shall remotely support Client's migration of the Enhanced MarkView Authentication functionality for one (1) additional environment (Development to Test) for up to one (1) hour. Efforts beyond this one (1) hour must be purchased separately. This Migration Support will be performed within the Client Testing Support timeframe defined in Section 1.3 above. 1.5. "Go-Live" Migration Support. [Company] shall remotely support Client's migration of the Enhanced MarkView Authentication functionality from a non-production environment to a production environment for up to one (1) hour. Efforts beyond this one (1) hour must be purchased separately. [Company] shall provide this "Go-Live" Migration Support immediately following the Client Testing Support defined in Section 1.3. 1.6. "Go-Live" Support. [Company] shall remotely support Client's initial transition of the Enhanced MarkView Authentication functionality from a test environment to an initial rollout in a production environment ("Go-Live") for up to six (6) hours across two (2) contiguous business weeks (immediately following the "Go-Live" Migration Support defined in Section 1.5 above). 2. Project Schedule. This project's scope and pricing is based upon the following estimated time ranges (elapsed time) for each of the major phases and milestones of the project. It is assumed that the project phases and associated time ranges will be delivered by [Company] in a contiguous fashion. Client and [Company] will maintain joint responsibility for maintaining this timeframe. Material variances to this project schedule may result in additional charges to be handled under a separate Statement of Objectives, Deliverables and Constraints. Estimated Time Ranges for Project Estimated Range in Weeks Kickoff Meeting Start of Project Analysis, Design 1 week System Configuration 2 weeks Installation into Initial Development Environment at Client Location 1 day Client Testing Support and Migration Support 2 weeks Go-Live Migration Support and Go-Live Support 2 weeks 3. Assumptions. [Company] has relied on the assumptions contained in this Statement of Objectives, Deliverables, and Constraints to establish the project schedule and to commit to the pricing described herein. Any failure of, or alteration to, any assumption may result in an increase to the price charged and/or a change to the project schedule or staffing. Client agrees to make commercially reasonable efforts to ensure assumptions occur as indicated or Client agrees to negotiate a change request or separate Statement of Objectives, Deliverables, and Constraints to account for the impact on [Company] of the failure of, or alteration to, an assumption. 3.1. The above Enhanced MarkView Authentication functionality is provided for the MarkView Password only. 3.2. The MarkView Password Web Application will be built upon the MarkView 7.0.1 solution. 3.3. All of the functionality contained herein will be implemented simultaneously as part of a single project. If any of the above functionality is implemented separately or later, a separate Statement of Objectives, Deliverables and Constraints will be required and additional fees may apply. 3.4. All work under this statement of work is expected to be performed during regular business hours (8:00 a.m. - 5:00 p.m. EST). 3.5. Client will perform regression, integration, and scenario-specific testing of the solution following installation and following any future migrations by Client. 3.6. All software/materials will be provided in the English language unless otherwise specified. 3.7. Client will make the necessary technical resources available to [Company] to prepare for installation, for the installation itself, for the train the trainer session, and for the go-live process. These resources include: Oracle Applications, Oracle DBA, Network Administration, Desktop Support, and Internal Help Desk. If suitable resources are not available at times specified in the [Company] project plan, additional billing for reasonable efforts may be incurred. 3.8. One Client resource, along with a designated backup resource, is responsible as the point of contact for all support calls and enhancements requests that go to [Company]. 4. Pricing and Payment. 4.1. Consulting Services. The fee for the Consulting Services described herein is US $##,### (Dollar Amount), exclusive of expenses. [Company] will invoice Client for this amount pursuant to the following schedule of payment milestones ("Milestones"). Payment will be made by Client within thirty (30) days of the invoice date. Milestone Amount Upon Execution of this Amendment US $[ ] Upon Install into Initial Development Environment US $[ ] Upon Install into Production Environment or Two Months After Install Into Initial Development Environment, Whichever Comes First US $[ ] 4.2. Expenses. In addition to the above, Client will be charged for reasonable direct expenses and ancillary costs incurred by [Company]. These include, but are not limited to, such things as shipping costs, taxes, travel expenses, hotel expenses, per diem expenses, etc. [Company] will bill all expenses at the end of each month for expenses incurred during the month. Payment of expenses shall be made within thirty (30) days of receipt of each invoice. Any failure by [Company] to submit monthly bills does not excuse payment for amounts due upon Client's ultimate receipt of said invoice. There are no expected expenses for the work described in this Statement of Objectives, Deliverables and Constraints IN WITNESS WHEREOF, the Parties hereto have caused this STATEMENT OF OBJECTIVES, DELIVERABLES AND CONSTRAINTS to be executed by their duly authorized representatives as of the Effective Date first set forth above. Executed by Client: Executed by [Company]: Signature: Signature: Name: Name: Title: Title: