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. 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 Preparing Data is a key component of the service and requires client input, but the consultant will take care of the rest! Setup workflow to meet use-cases and begin PM training User training sessions by user role or function and typically last up to 90 minutes for up to 10-15 users After data is loaded, the account configured, and users are trained the system is ready to roll-out
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.
(b) Except as otherwise described in Section 7.2.1(a) and as provided in Sections 7.5, 7.6 and 7.13, ABX, at AZ’s sole cost and expense subject to Section 7.13, shall be responsible for all process development and manufacturing activities (including cell line development and scale up) required to be conducted, prior to the designation of a Candidate Drug, in accordance with the Process Science/Clinical Manufacture Agreement.
Discovery Phase. Purpose: Formally gather, document, and agree upon requirements to be met in the solution. Hyland will engage State's subject matter and technical experts to discuss the business process in detail and define the requirements. State/Hyland Follow up items may be discussed with the subject matter or technical experts to close any gaps in fully understanding the captured requirements. State/Hyland Compose formal documentation containing the use cases and associated requirements of the business using Xxxxxx’x standard requirements document format. Hyland and/or State 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/Hyland Introduce the Project Change Control Process for deviations, which impacts estimated work effort. State/Hyland Make appropriate updates to the proposed requirements document. Hyland 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, Hyland will determine whether the Project Change Control Process set forth in this SOW Exhibit must be followed. State 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/Hyland Implementation Phase Purpose: Hyland designs, develops and functionally tests the Software solution. Conduct brainstorming sessions to design the solution based on the RD. Hyland 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. Hyland and/or State Provide a walkthrough of the solution to State. Hyland Evaluate the solution and provide feedback to Hyland. State Refine documentation based on feedback from prototype review(s) with State in accordance with the Proj...
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.
17 2. A Producing Party may designate as “CONFIDENTIAL” any material the 18 producing party believes in good faith constitutes or discloses information or that qualifies for 19 protection pursuant to the Federal Rules of Civil Procedure, specifically information that is trade 20 secret or other confidential research, development, or commercial information, and materials 21 that are deemed confidential under Federal Drug Administration ("FDA") regulations and Health 22 Insurance Portability and Accountability Act ("HIPAA") statutes and/or regulations.
23 3. Confidential information may be further designated as “HIGHLY 24 CONFIDENTIAL” if the Defendant produces materials that it believes in good faith would, if 25 disclosed, cause substantial economic harm to the competitive position of the entity from which 26 the information was obtained because it relates to research and development material on a new 27 product that has not been approved or cleared by the FDA or a similar regulatory body or reflects 28 a party’s price competitiveness in the market or marketing business strategies of a party 1 concerning a current or new product. The Plaintiff will inform the Producing Party of its intent 2 to disclose such information to any individual who is currently, or who at any time during the 3 pendency of this litigation becomes, a consultant to a competitor of the Producing Party in the 4 pelvic mesh business, or is a consultant to an entity actively investigating entering such business, 5 and Plaintiff will follow the procedures for disclosure of s...
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. Deliverable: Provide web conferencing training, Onsite Meetings, and Remote Reviews as outlined in the agreement. Deliverable: Customer to complete configuration workbooks provided by SunGard. The workbooks are designed to assist SunGard is capturing the Customer’s business processes and requirements. SunGard will use a combination of the workbooks and information gathered during meetings to set up and configure the software.
Discovery Phase. The purpose of the discovery phase is to understand the OSOS and its stakeholders' current state, needs, challenges, and opportunities. In this phase, we will conduct the following activities: • Kick-off meeting: Hold a kick-off meeting with the OSOS project team and key stakeholders to introduce Digitech Labs & Proarch, review the project objectives, scope, timeline, and expectations, confirm roles and responsibilities, and establish communication protocols. • Stakeholder interviews: Conduct interviews with various stakeholders, such as OSOS and WATech staff, customers, partners, vendors, and regulators, to gather their input, perspectives, and feedback on the current and desired state of the OSOS services and processes. • Data collection and analysis: Collect and analyze relevant data and information, such as OSOS strategic plans, policies, procedures, reports, surveys, metrics, performance indicators, systems, technologies, etc., to understand the current situation and identify gaps, issues, and areas for improvement. • Applications in Scope : Through the discussions, workshops and interviews, we will seek to list down the applications, beyond the 5 critical systems, relevant and in scope for this feasibility study.
