CRM; Client Configuration Development and Implementation Sample Clauses

CRM; Client Configuration Development and Implementation. CRM implementation will be led using an agile development approach including the following deliverables: Initial Requirements Demonstration of the Client Configuration; and discussion of Client needs and business environment to support the general usage and end-user experience; will include accounts, functions, Call types, products, customer profile maintenance, etc. Alpha Review First iteration of the Client configuration based on requirements gathered in the Initial Requirements session. Detailed demonstration of the Client Configuration for more in-depth review of Client requirements. Configuration Requirements Document (“CRD”) After the Alpha Review, inVentiv will provide the Client with a draft CRD document which summarizes all end-user system requirements taken from both the Initial Requirements and Alpha Review sessions. The CRD will form a basis for the final Client Configuration specifications, risk assessment, testing, training, and validation (if applicable). [ * ] = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 24b-2 of the Securities Exchange Act of 1934, as amended. Beta Review The final phase of the Client requirements will be a Beta Review, which will allow for any changes to the Client Configuration system requirements for final testing and production readiness. CRD Sign-Off Any changes or additions to the Client Configuration requirements during the Beta Review will be incorporated into the final CRD and submitted to the Client after the Beta Review session for final approval and signature.
Sample 1
AutoNDA by SimpleDocs
CRM; Client Configuration Development and Implementation. CRM implementation will be led using an agile development approach including the following deliverables: Initial Requirements Demonstration of the Client Configuration; and discussion of Client needs and business environment to support the general usage and end-user experience; will include accounts, functions, Call types, products, customer profile maintenance, etc. Alpha Review First iteration of the Client configuration based on requirements gathered in the Initial Requirements session. Detailed demonstration of the Client Configuration for more in-depth review of Client requirements. Configuration Requirements Document (“CRD”) After the Alpha Review, Syneos Health will provide the Client with a draft CRD document which summarizes all end-user system requirements taken from both the Initial Requirements and Alpha Review sessions. The CRD will form a basis for the final Client Configuration specifications, risk assessment, testing, training, and validation (if applicable). Beta Review The final phase of the Client requirements will be a Beta Review, which will allow for any changes to the Client Configuration system requirements for final testing and production readiness.
Sample 1

Related to CRM; Client Configuration Development and Implementation

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Investment Analysis and Implementation In carrying out its obligations under Section 1 hereof, the Advisor shall: (a) supervise all aspects of the operations of the Funds; (b) obtain and evaluate pertinent information about significant developments and economic, statistical and financial data, domestic, foreign or otherwise, whether affecting the economy generally or the Funds, and whether concerning the individual issuers whose securities are included in the assets of the Funds or the activities in which such issuers engage, or with respect to securities which the Advisor considers desirable for inclusion in the Funds' assets; (c) determine which issuers and securities shall be represented in the Funds' investment portfolios and regularly report thereon to the Board of Trustees; (d) formulate and implement continuing programs for the purchases and sales of the securities of such issuers and regularly report thereon to the Board of Trustees; and (e) take, on behalf of the Trust and the Funds, all actions which appear to the Trust and the Funds necessary to carry into effect such purchase and sale programs and supervisory functions as aforesaid, including but not limited to the placing of orders for the purchase and sale of securities for the Funds.

  • Curriculum Development This includes the analysis and coordination of textual materials; constant review of current literature in the field, some of which are selected for the college library collection, the preparation of selective, descriptive materials such as outlines and syllabi; conferring with other faculty and administration on curricular problems; and, the attendance and participation in inter and intra-college conferences and advisory committees.

  • Project Implementation The Borrower shall:

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Training Program It is agreed that there shall be an Apprenticeship Training Program, the provisions of which are set forth in Exhibit "D", which is attached hereto and forms part of this Agreement.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Development Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!