Project Charter Project Name Project Manager Owner(s) ERPro 6.0 1 Mir Jawad Ali Razvi Project Number Prioritization St. Joseph Healthcare Start Date: 05/01/2016 Scheduled Completion Date: 01/05/2017 1 Mission/ Purpose The reason for this project is to build up a software which gives data management solutions for the new MRx screen/defibrillator and AEDs in the doctor's facility and emergency medical services (EMS) markets. The software, named ERPro 6.0, is the new form of ERPro, which has been utilized as a part of emergency medical services, fire stations, and police headquarters. The new ERPro 6.0 is proposed to work with the new MRx and AEDs and enter the healing center business sector. It will be sold to Seattle neighborhood doctor's facilities and after that healing centers in different districts in the US. Sooner rather than later, the organization is wanting to present the software in Europe and China. SOW This project will yield ERPro 6.0 which gives data administration answers for the new MRx screen defibrillator and AEDs. For this new programming adaptation, we present the accompanying qualities and necessities: 1.GUI will be same with past ERPro variant aside from new elements; 2.The Bluetooth communication highlight will be included; 3.The new information sort augmentations; 4.The improved information investigation functionalities. Item related deliverables include: 1.Market examination. The promoting office breaks down the requirement for the new ERPro 6.0, and gives the prerequisites and details of the new discharge. 2.The waterfall programming advancement model is utilized to build up the application. Every venture part is in charge of culmination of his/her part and submitting to the following part. The required documentations about the product are submitted to the venture administrator. 3.The last programming will be tried and accepted by prerequisites and details. Project Charter 4.The programming will be released.. Objectives The ERPro series programming has been broadly utilized as a part of EMS, fire stations, and police headquarters for MRx screen defibrillator and AEDs and reliably got positive input from customers. The objective of this project is to build up another variant of ERPro, which gives productive information administration arrangements on new MRx and AEDs for customers and enters the healing facility market. Aside from the US advertise, the organization additionally has wanted to dispatch this new form in different dialects and offer it in Europe and China. This project might nearly take after calendar, finished no later than January 5,2017. Project Charter Business Need The old ERPro 5.5.1 may not work viably with the new MRx screen/defibrillator and AEDs. Keeping in mind the end goal to keep giving productive data administration answers for the new MRx and AEDs, the organization needs to respond to changing economic situations and grow new components, for example, importing information from MRx and fare information to other IT frameworks. By acquainting the new ERPro with our customers, we demonstrate to them that we have reliably strived to give items which bring arrangements and improve their works, which convey quality to them. This helps expanding our organization trust in existing markets. Furthermore, the new ERPro can likewise give a chance to demonstrate our mastery in the hospital market. Project Manager and Stakeholders Mir Jawad Ali Razvi will be the project manager and lead this project. Project team members are from the product development team, marketing department, data management group, IT department, quality engineering, software engineering, technical support, customer services, and documentation control group. Milestones Project stage 1 starting ought to be wrapped up by task introduction on June 1,2016. Stage 2 arranging ought to be wrapped up by assignment prioritization and undertaking start-up on July 2, 2016. Stage 3 executing ought to be wrapped up by rivalry of beta testing on November 3, 2016 and application on November 5, 2016. Stage 4 checking and controlling ought to be wrapped by advantage estimation and application finish on November 11,2016. furthermore, stage 5 shutting ought to be and undertaking finish on January 5, 2017. Budget The organization will allot considerable measure of budget for this project. The majority of the expenses for this project will be labor, because the innovation, gear and different necessities are now accessible. Extra spending plan might be essential if external contractors are required, subsequent to our ability is not programming advancement. User Acceptance Criteria/Quality We will likely finish this project toward the beginning of January 2017. The past ERPro forms have gotten great input from our customers, and we trust this new form will do likewise. The organization additionally plans to offer this new form to hospitals, and in view of the underlying deals data from the neighborhood showcase, the organization hopes to discharge it to the across the nation business sector and after that abroad markets, for example, Europe and China. On the off chance that the task costs somewhat more than arranged, Project Charter the organization will even now see it as a win on the off chance that it will be finished on schedule. High-Level Project Assumptions The ERPro 6.0 is the new form of the ERPro programming arrangement. Since thereare past programming forms, the task group is acquainted with the product and comprehends the prerequisites, particulars, and necessities well. Promoting division has directed research and discovered new improvement prerequisites and particulars, for instance, importing information from MRx and trading information to other IT frameworks. The project team will utilize the waterfall programming advancement approach, a successive programming improvement model which the improvement does not move starting with one stage then onto the next until the former stage is finished. By and large, the venture group's nature with the past programming adaptations and the utilization of waterfall procedure are principle qualities for the task. High-Level Project Constraints Time is the main requirement. The undertaking is planned to finish on January 5,2017 however at some stages, there might be difficulties in incorporating new functionalities, so support time remittances in schedule might be expected to keep away from any postponement. Exclusions and Boundaries This software is created upon past rendition and means to offer new features and upgraded data analysis functionalities, yet it doesn't present any new innovation and any new utilization. The product must be utilized just on the MRx screen/defibrillator and AEDs; it is not expected to be utilized on some other gadgets. It should not be utilized as a part of business sectors other than indicated either. Major Risks Despite the fact that this project is to build up a software in light of a current past rendition, there lies a potential danger of characterizing and building up the utilitarian particulars, since the organization's aptitude is on medicinal gadget fabricating however not programming configuration and improvement. Time is the other potential danger, as the group needs to finish particular, advancement, and pilot generation for the product in 8 months. In the event that the necessities are not completely comprehended or change after some time, we may need to look for different methodologies. KEY STAKEHOLDERS Project Manager Authority Level Mir Jawad Ali Razvi is the project manager for this project and shall have authority to select project team members, assign roles and Project Charter Project Core Team Subject Matter Experts (SMEs) responsibilities and determine the final project budget. The core team who will be involved in the project planning and execution will be:Project team members are from the product development team, marketing department, data management group, IT department, quality engineering, software engineering, technical support, customer services, and documentation control group. Consultants: Taher Saif ballu Type Name Project Manager Approval: Customer/Sponsor Approval: APPROVALS Signature Date Project scope statement Project name ERPro 6.0 Project number 1 Project Manager Mir Jawad Ali Razvi Prioritization 1 Owner St.Joseph Healthcare Statement of work- Project description and project product This project will create ERPro 6.0, another form of the ERPro programming arrangement which succeeds ERPro 5.5.1, and give data administration arrangements on the new MRx screen/defibrillator and AEDs for customers in the emergency medical services (EMS), fire station, police headquarters, and hospital markets. This new form of the ERPro will have the accompanying attributes and particulars: 1.The Graphical User Interface (GUI) will be the same with ERPro 5.5.1 aside from new features; 2..New information sort additions; 3.Enhanced information examination functionalities; 4..Bluetooth correspondence will be added.Overall, we will utilize the waterfall programming advancement way to deal with complete this anticipate, and here are the strides we expect to finish the project: *Develop an examination to get abnormal state detail of the application; * Develop meaning of client necessities and needs; * Develop useful and specialized requirements; * Develop prototype; * Validate and confirm the particulars of prototype; * Assemble last product; * Release last product; * Determine intends to gauge the estimation of the application regarding backing and help with the undertakings. The new ERPro 6.0 will demonstrate to our present customers the organization's steady effort to providing significant items to them, which bring arrangements and streamline their works. This helps expanding our organization trust in the current markets. Moreover, the new ERPro 6.0 likewise can expand perceivability of the organization's mastery to potential healing center customers, which should help our arrangement to offer it to the neighborhood doctor's facilities, then across the nation clinics, and in the long run abroad markets, for example, Europe and China. Project Deliverables We should have two arrangements of deliverables for this anticipate: project management related deliverables and product related deliverables. Project management related deliverables might incorporate undertaking sanction, business case, group contract, scope proclamation, WBS, plan, cost standard, status reports, last venture presentation, last venture report, after death, and whatever other supporting records required to deal with the task. Item related deliverables should incorporate business sector examination, client necessities, application determinations, application client interface outline and code, information sort augmentations code, information investigation functionalities code, Bluetooth correspondence, test plan, and project advantage estimation arrangement. Project Objectives We should nearly take after the undertaking cost pattern and timetable; complete it in spending plan and no later than January 5, 2017. We should build up another ERPro 6.0 which gives effective information administration arrangements on new MRx and AEDs for customers against their prerequisites and needs and enters the healing center market, and meets target deals income number. In view of the underlying deals data, we might delineate arrangements to discharge the product to the across the nation market and in the end abroad markets, for example, Europe and China. Project Assumptions Since the ERPro 6.0 depends on ERPro 5.5.1 and there are past ERPro adaptations, the project group is acquainted with the product and comprehends the prerequisites, determinations, and different necessities well. Promoting division has directed research and discovered new improvement requirements and particulars, and the venture group will utilize the waterfall programming advancement technique, which is the procedure utilized for past ERPro advancement ventures. In general, the venture group's nature with the past programming variants and the utilization of the waterfall procedure are fundamental qualities for the project. Project Constraints Time is the main requirement. The task is planned to be finished no later than January 5, 2017; however at some phases amid the advancement procedure, there might be difficulties in incorporating new functionalities, so cradle time stipends in timetable might be expected to dodge any postponement. Exclusions This project is to build up a product upon a past adaptation and plans to offer new elements, for example, information sort increments and improved information investigation functionalities, yet it doesn't present any new innovation and any new utilization. The product must be utilized just on the MRx screen/defibrillator and AEDs; it is not planned to be utilized on whatever other gadgets. It should not be utilized as a part of business sectors other than determined either. Acceptance Criteria This project must be finished no later than January 5, 2017. The past ERPro adaptations have gotten great input from our customers, and we trust this new form will do likewise by giving effective information administration answers for customers, with the new components and functionalities. In the event that the project costs somewhat more than arranged, the undertaking patron will in any case view it as a win on the off chance that it will be finished on calendar. The new ERPro 6.0 should likewise be sold to point of view doctor's facility customers and in the end enter abroad markets of Europe and China. Technical requirements The ERPro 6.0 is to be utilized on the new MRx screen/defibrillator and AEDs. With the vast majority of ERPro 5.5.1's components and functionalities are held and enhanced, the new ERPro 6.0 incorporates new elements and functionalities which meet changing business sector requests. For instance, importing information from MRx and trading information to other IT frameworks, new information sort increases, upgraded information investigation functionalities, and Bluetooth correspondence capacity. Work Breakdown Structure ERPro 6.0 Development Project 1.0 Initiate project 1.1 Assign project manager 1.2 Identify stakeholders 1.3 Prepare project charter 1.4 Prepare business case 2.0 Plan project 2.1 Hold project kickoff meeting 2.2 Prepare team contract 2.3 Prepare scope statement 2.4 Determine Work Breakdown Structure (WBS) 2.5 Prepare project schedule and cost baseline 2.6 Identify, discuss and prioritize tasks 3.0 Execute project 3.1 Discuss market analysis 3.2 Discuss user requirements and needs 3.3 Determine application specifications 3.4 Design user interface 3.5 Develop user interface 3.6 Implement data type additions 3.7 Develop data analysis functionalities 3.8 Implement Bluetooth communication tool 3.9 Develop other minor functionalities 3.10Prepare test plan 3.11Test initial prototype 3.12Test beta version of application 4.0 Monitor and control project 4.1 Prepare status reports 4.2 Prepare benefit measurement plan 4.3 Implement benefit measurement 4.4 Finalize application 5.0 Close project 5.1 Prepare final project report 5.2 Prepare final project presentation 5.3 Prepare postmortem 5.4 Finalize project