Project Management Process. This section describes the following project management procedures that will be used to support the delivery of this project: ~ Organization ~ Change Control ~ RAID Management (Risk, Action, Issue, Decision)
Project Management Process. The eClinicalWorks Project Management Process: • Initiate the project with clearly defined goals and objectives • Define the client’s governance structure and project team • Define the eCW Project Team • Define the eClinicalWorks Project Team’s relationship with the client’s designated Project Team and accountabilities for each team’s members • Describe preferred communication approaches between the two teams • Define technical and management strategies and methods to be employed to ensure completion of the project plan in accordance with contract requirements • Understand and document infrastructure requirements • Explore concrete approaches that can be used to promote system acceptance and long-term adoption by users and stakeholders • Define content and workflow needs • Define Interoperability needs • Discuss the development of a communication portal for use by the Project Teams to facilitate timely communication • Plan the launch and obtain user buy-in • Perform site analyses to understand the various workflow requirements • Perform enterprise inventory analysis to determine workstation and peripheral hardware needs based on eCW hardware specifications • Check connectivity • Develop the data migration strategy • Determine and document the interoperability requirements and develop the interoperability plan • Plan for additional assistance, staff augmentation. • Understand and document reporting requirements • Plan the deployment strategy – big bang, phased, hybrid • Support Strategy –Internal Help Desk, eCW Support, eCW’s Account Management model • Deployment – hardware, software, system build • End user training • Go Live – on-site user training, engage eCW Support Resources • Review the execution phase: operational, financial, Meaningful Use, adoption, quality • Measure progress toward goals using eBO reporting • Listen – provider user groups – weekly and/or monthly • Support – provider/user appreciation events • Tracking and trending for Meaningful Use – MAQ Dashboards • User adoption of the technology – KPIs, site assessments, site review for technology optimization
Project Management Process a. Vendor’s Project management process is based upon the premise that the Vendor Delivery Project Executive has overall responsibility and accountability to meet the agreed upon quality, cost, schedule and technical objectives of the Project.
Project Management Process. IBM's Project Management process is based upon the premise that the IBM Account Manager will have overall responsibility and accountability to meet all agreed upon quality, cost, schedule and technical objectives of the project. In addition, each Party will assign an individual to each project to act as its respective representative with responsibility for specific operational roles as described below and further delineated in the Project Plan ("Project Manager"). Based upon the scope of the work and the Deliverables to be provided under a project, a Project Manager may be assigned to oversee multiple Projects. Each project whether included as of the Commencement Date or subsequently added at the request of Certegy, subject to Section 9.6 of the Master Agreement, will have a plan developed (the "Project Plan") and, upon approval by both Parties, the Project Plan will be assigned a sequential number and will be attached to, and become a part of, this Schedule (e.g., Mainframe Project Plan M-1/Title, Mainframe Project Plan M-2/Title, etc.). The terms, and conditions of the Master Agreement and the Transaction Document will apply to each project unless otherwise amended by the applicable Project Plan.
Project Management Process. 2.1 The following procedure will apply in respect of proposed works at the Site:
Project Management Process. 2.1 The Provider Project Executive will have overall responsibility and accountability to meet agreed upon quality, cost, schedule and technical objectives of the Project.
Project Management Process a. A Project is work performed by IBM under the Agreement that spans a specific period of time within the Term of the Agreement and is defined by the achievement of defined target outcomes or objectives. IBM will perform all Projects under a Project Change Request (PCR). Projects will be subject to charges in addition to the charges set forth in the Agreement to the extent that (i) the Project is not a Project specifically within the scope of the Agreement such as the Server Consolidation Project; (ii) the Project consists of New Services; (iii) the Project consists of material changes to the scope of the Services and the Agreement does not set forth a pricing methodology to address such material changes (e.g., Services in excess of the volume of Services provided under the Agreement; and Services on an expedited basis); or (iv) the Project consists of Services for which the parties expressly agree not to use the charging methodology set forth in the Agreement.
