Discovery Phase. Mercatus to interview business users and stakeholders to define Customer workflow, which includes o Definition of current roles internally o How users interact and handoff work o Specific data to capture for end deliverables identified in Service Order o What commitments need to be tracked for each entity record to remain compliant o Key reports generated today, data required, frequency of delivery, audience • Mercatus will hold 1-3-hour sessions of guided discussions with each identified Customer user / group, to be confirmed during the Parties’ kick-off. Mercatus assumes approximately five to ten (5-10) meetings to be held overa 1 to 2-week period with Customer directly, with subsequent follow-ups with Customer as needed. • The meetings will be conducted onsite at Customer or virtual per the availability and location of all key Customer resources. The analysis, documentation, and review will be conducted offsite by Mercatus. • Customer Deliverables: o Access to regional teams with committed times for designated focus groups o Access to current systems and tools, including live demonstrations and ability for Mercatus team to view use in a typical “day-in-the-life” setting of Customer and its users o Company and regional organization charts o Current flow diagrams for specified in-scope business process o Examples of outputs of current process today, including regional / company reports or desired consolidated final products • Mercatus Participants – Program Manager and Solutions Architect (as needed)
Discovery Phase. (a) ABX shall provide AZ with reasonable research quantities of each Research Antibody as specified in the applicable Research Program Work Plan, at ABX’s sole cost and expense, in order for AZ to assess such Antibody and perform its activities under the applicable Research Program and exercise its rights under Article 2. Notwithstanding the foregoing, AZ shall have the right to reasonably request additional research quantities of an Antibody, beyond those quantities set forth in the Research Program Work Plan, for the sole purpose of performing activities outside of the Research Programs that are directed towards designating a Candidate Drug, but not for the purpose of furthering any other AZ activities. If AZ reasonably requests additional research quantities of an Antibody for such purpose, then ABX, at AZ’s sole cost and expense, shall be responsible for manufacturing and supplying such additional research quantities for such purpose. ABX, at its sole cost and expense, shall be responsible for such Antibody scale up activities as are necessary to complete the activities set forth in the Research Programs. If AZ requests additional quantities of any Antibodies as permitted under this Section 7.2.1(a) and ABX does not have sufficient uncommitted quantities available, ABX shall, at its sole cost and expense, provide AZ with the cell line for each such Antibody to enable AZ to produce such Antibody for such purposes.
Discovery Phase. In the discovery phase, there is insufficient information for the parties to reach a final contract with in-depth product specifications, final budget and schedule, production milestones, deliverables, etc. SolutionX and Client work together to reach an interim agreement or letter of intent, based on the high-level overview of the concept document. This letter of intent allows the parties to move forward with creating the all-inclusive scope document and to derive from it a final schedule and final budget which will lead to a final contract.
Discovery Phase. The discovery phase is typically a phone or web interview that typically lasts a couple of hours • Interview maintenance and operations managers/supervisors, technicians, operators • Overview of application with key stakeholders • Define workflow and use-cases within the applications • Discuss change management and strategy Data Loading and Configuration Preparing Data is a key component of the service and requires client input, but the consultant will take care of the rest! • Data review of existing data from previous CMMS system or data sets • Map current data into AE setup and format • Configure GIS Map Settings • Review Map Layers • GIS Layer Configuration and Syncing Assets • Determine priority of data load to meet use-cases • Review data in AE and discuss data management Use-case setup and PM training Setup workflow to meet use-cases and begin PM training • Refinements to configuration, workflow and data as needed • Build workflow to meet agreed use-cases • Refine Request/Work Order templates to capture required data • Training on creating and maintaining PMs with application Admins and Supervisors Hands-on User Training User training sessions by user role or function and typically last up to 90 minutes for up to 10-15 users • Train end users – supervisors, technicians and requestors • Hands on training of reactive workflow with Supervisors • Mobile or Desktop training available for most user roles Evaluation At the conclusion of the consulting service, the consultant will forward notes to your project coordinator capturing what was accomplished and any recommended next steps. The project coordinator will schedule a follow-up call within 2 weeks of the consulting service. Ongoing communication until the project is complete will be through your Basecamp project. Post Enablement Support After data is loaded, the account configured, and users are trained the system is ready to roll-out • Support go-live – adjust configuration, provide additional training and data entry support • Review aspects of AE planned for future use • Define follow-up tasks and next steps • Define Post Launch Support point of contact Project Assumptions DSI has made the following general assumptions in this SOW to derive the estimated cost for this project. It is the responsibility of Client to validate these assumptions and responsibilities before signing the Acceptance. Deviations from these assumptions may impact DSI's ability to successfully complete the project. Any changes i...
Discovery Phase. Purpose: Formally gather, document, and agree upon requirements to be met in the solution. Requirements Gathering Xxxxxx will engage State's subject matter and technical experts to discuss the business process in detail and define the requirements. State/Xxxxxx Follow up items may be discussed with the subject matter or technical experts to close any gaps in fully understanding the captured requirements. State/Xxxxxx Requirements Documentation Compose formal documentation containing the use cases and associated requirements of the business using Xxxxxx’x standard requirements document format. Xxxxxx and/or State Requirements Validation Review and red line (if applicable) the proposed requirements document. State Review the updates and determine if there is an impact on the Project Plan and scope of the solution. State/Xxxxxx Introduce the Project Change Control Process for deviations, which impacts estimated work effort. State/Xxxxxx Make appropriate updates to the proposed requirements document. Xxxxxx and/or State Validate the finalized RD. Upon sign-off by State, the RD replaces any previous form of scope or solution estimate, and becomes the then current project scope. The RD will be subject to review and re-estimation of the timeline, pricing, and work effort involved, and, based on such review and re-estimation, Xxxxxx will determine whether the Project Change Control Process set forth in this SOW Exhibit must be followed. State State Test Case Development Develops tests cases based on agreed upon business process and functionality requirements defined in the RD. State Each test case should minimally include ID number, functional area, prerequisite or dependency, a description, testing steps, expected outcome, pass/fail and tester comments. State Develop/modify test cases throughout the duration of the project. State Periodic review of the test case development progress with State’s assigned test case writer and Xxxxxx’x Project Manager. State/Xxxxxx Implementation Phase Purpose: Xxxxxx designs, develops and functionally tests the Software solution. Solution Design Conduct brainstorming sessions to design the solution based on the RD. Xxxxxx and/or State Create Solution Design Document that outlines and defines important details about the solution based upon the business requirements documented in the approved Requirements Document. Xxxxxx and/or State Prototype Review Provide a walkthrough of the solution to State. Xxxxxx Evaluate the solution and p...
Discovery Phase. The Discovery Phase is completed when the Assessment Meeting is held. It is expected that the Assessment Meeting will be conducted two (2) weeks after the Introductory Meeting is held (five weeks after the license agreement is executed). The objective of this phase is to compile a complete, documented reference base to be used to define, configure and setup your QMACS(TM) system for optimal performance in your business environment. Incomplete or inaccurate information may result in a faulty or failed project. QCSI DataCenter has the following responsibilities during the Discovery Phase: Review Discovery Documents Conduct Assessment Meetings ASSESSMENT MEETINGS The Assessment Meetings include a Technical Assessment and a Business Assessment. QCSI DataCenter staff will chair each of these meetings and full participation from the IMPACT Action Team is required. These meetings will be conducted at your facility and will be held after all discovery documents are completed and have been reviewed by your DataCenter IMPACT team members. Be sure that all discovery documents are delivered to your DataCenter team at least five (5) working days before the Assessment meeting. The TECHNICAL ASSESSMENT MEETING is chaired by the DataCenter Technical Analyst assigned to your IMPACT project. Your assigned DataCenter IMPACT Database Analyst and Systems and Network Analyst will participate. This meeting should be preceded by a tour of your organization with special emphasis on your workstations. Approximately four (4) hours are required to complete this portion of the discovery process at your facility. The BUSINESS ASSESSMENT MEETING is chaired by the DataCenter Implementation Team Leader assigned to your DataCenter IMPACT project. Your IMPACT Project Manager and Professionals must participate. This meeting is dependent upon completion of the Business Analysis Questionnaire. If this document is not complete, and has been reviewed by the DataCenter Implementation Team Leader prior to the Business Assessment, this meeting will be rescheduled. This meeting should be preceded by a tour of your organization with special emphasis on the departments that will be using QMACS(TM). Your DataCenter IMPACT consultants will want to observe the following processes: Enrollment of a new member Addition of a provider or contract 12 (c)Quality Care Solutions, Inc. 02/03/99 26 Addition of a new benefit plan Changes to member, provider, contracts or benefit plan information Issuing and changing...
Discovery Phase. 7 1. This Agreement shall govern all documents and electronically stored information 8 (“ESI”), the information contained therein, and all other information produced or disclosed 9 during the Proceeding whether revealed in a document, deposition, other testimony, discovery 10 response or otherwise, by any party, including any non-party, in this Proceeding (the “Producing 11 Party”) to any other party, including any non-party, when same is designated with the procedures 12 set forth herein. This Agreement is binding upon the parties to the Proceeding, including their 13 respective corporate parents, subsidiaries, and affiliates, as well as their respective attorneys, 14 agents, representatives, officers, and employees and others as set forth in this Agreement. This 15 Agreement is also binding on and applies to all non-parties who either produce or receive 16 documents or information in connection with this Proceeding.
Discovery Phase. A. Development of Design Criteria. TREKK will develop a design criteria memo.
Discovery Phase. At the commencement of the contract, Caissa will begin a discovery phase with DCPS. The discovery phase will include evaluating or determining the following: • Enrollment • Micro-commitment forms • Priority Targets • Community and District Research • Tracking Method • Goals Based on conversations with Xxxxx County Public Schools, the Discovery Process has already begun.
Discovery Phase. Defining the User Journey and key elements of the Register website There has already been a considerable amount of work undertaken on the Discovery phase because of the work done already on similar community benefits registers in Scotland and Wales. We have sought feedback on the Scottish Register and have started to develop a User journey for both the wind developer and community side of the Register (Appendices X, Y and Z). In line with the agile development approach, however, there should be a short discovery phase (2-5 days) to look at: User needs from a community and Fund Administrator perspective; User needs from a wind developers perspective (some work has already been undertaken on this); the Welsh register and what features we may like to incorporate into the English Register; developing the right questions and format for obtaining responses on community engagement; whether we need to have an extra proforma to gather responses on community engagement (developer form on community benefits, a community form on community benefits and community responses on engagement) under the same wind farm record; developing word-based proforma for stakeholders to complete if do not have access to a computer (work has already begun on this, Appendix Z). consider how to clearly distinguish between developments that were operational prior to the Renewables UK voluntary standard for community benefits of £5,000 per MW of installed capacity in June 2013. in conjunction with DECC, the best way of interacting with Xxx.xx and hosting the website, including whether we can have an area on the website with Best Practice Guides for Community Engagement and Community Benefits and the Evidence Toolkit ‘Common Concerns about Wind’ that are being developed by DECC; consider how information on community benefits can be submitted annually to the register by both communities and wind developers and how previous years records can be stored but remain accessible on the register, whilst also reducing the amount of duplicate information collected each year i.e allow those completing the register to use the data from the previous year and amend; consider how the Register can provide information retrospectively – i.e. wind farm X provided Z amount of Community Benefits in 2013. Date stamps for each time the status/CB amount gets updated; automatically aggregate the CB value paid over the years – i.e. on Page 2 of Appendix Z ‘Total Community Benefit Value provided since first payment’ the...
