Automated Dispensing and Delivery System Project Charter

This project charter details the implementation of an automated delivery system (Omnicell) in pharmacy management. It outlines the project's purpose, objectives, scope, timeline, budget, and team organization. The charter also addresses key assumptions, constraints, quality control measures, and communication strategies for successful project execution.

TABLE OF CONTENTS
Document Control..................................................................................................................................... 3
Purpose of this document........................................................................................................................ 4
1. PROJECT OVERVIEW........................................................................................................................... 4
1.1 Project Purpose/Justification:...............................................................................................4
1.2 Project objectives:................................................................................................................4
1.3 Project Scope and Solution Plan.........................................................................................4
1.3.1 Solution Overview.........................................................................................................4
1.3.2 Project Scope................................................................................................................4
1.3.3 Project Deliverables......................................................................................................4
2. PROJECT DETAILS............................................................................................................................... 5
2.1 Timeline & Milestones..........................................................................................................5
2.2 Project Cost Estimate & Budget...........................................................................................5
2.3 Key Assumptions.................................................................................................................5
2.4 Constraints...........................................................................................................................5
2.5 Quality Control:....................................................................................................................5
2.6 Project Success Measures..................................................................................................5
2.7 Project Progress Tracking....................................................................................................5
2.8 Project Communications......................................................................................................5
2.9 Document Management.......................................................................................................5
3. PROJECT TEAM ORGANIZATION, ROLES & RESPONSIBILITIES....................................................5
3.1 Project Delivery Approach & Team Strategy.......................................................................6
3.2 Project Roles and Responsibilities.......................................................................................6
4. Approvals............................................................................................................................................... 6
4.1 Assigned Project Manager (PM):.........................................................................................6
4.2 Name and Authority of the Sponsor:....................................................................................6
Appendix.................................................................................................................................................... 7

Document Control
Document Name, Location, Owner
Name AUTOMATED DISPENSING AND DELIVERY SYSTEM
(OmniCell Implementation) - Charter
Version History and Status
Version Date Revision Description (Author)
Page 2 of 9

Purpose of this document
The purpose of this project charter is to document the business needs, current understanding of
the needs and the new product, service, or result that it is intended to satisfy the entity.
1. PROJECT OVERVIEW
1.1 Project Purpose/Justification:
To implement automated delivery system (Omnicell implementation) in pharmacy management
1.2 Project objectives:
 To evaluate role of delivery system in pharmacy
 To access impact of automation on delivery system.
1.3 Project Scope and Solution Plan
1.3.1 Solution Overview
<A brief overview of the solution to be delivered>
It was analysed that delivery system was very ineffective. therefore, in order to make the overall
delivery system automated, a project was initiated. this was done to increase speed of delivery and
maintaining smooth flow of operation. moreover, it will be useful for reducing waiting time and cost. the
automation will enable in effective storing of data and information. furthermore, once implemented it
can be used for lifetime.
1.3.2 Project Scope
 Business Process Architecture
o <description of the business architecture for the project>
this project will help in modifying overall method and procedure of delivering
pharmacy equipment’s to people. also, it will set time limit of analysing data and
generating results. with this, operation will be performed in smooth way.
 Application Architecture
o <description of the application architecture for the project>
the project will be based on an application which include server, operating
system, database and software. in application data will flow from bottom to
top. it will be designed in such a way that it is easy for business to make
changes in its software and hardware components.
 Information Architecture
o <description of the information architecture for the project>
Page 3 of 9

the flow of information will be through client server architecture. it will use
HTTP protocol to send and receive data. also, information will flow from
bottom to top.
 Technical Architecture
o <description of the technical architecture for the project>
the technical architecture of project will consist of many tools and
equipment’s. there will be centralised server, database, software, etc. the
overall structure will be designed and based on client server protocol.
 Security Architecture
o <description of the security architecture for the project>
there will be high security devices and software installed. it will include anti
virus at both server and client end. it will be licensed software and purchased
from JHAH.
 Change Management Approach
o <description of the organizational change management approach for the project>
the change management approach followed by organisation will be McKinsey
7 S model. it will help in successful implementation of project.
1.3.3 Project Deliverables
<A brief overview of project deliverables, reference the deliverable>
this project will help in modifying overall delivery system. this will result in generating better
outcomes and increasing efficiency of pharmacy.
2. PROJECT DETAILS
2.1 Timeline & Milestones
<An overview of the overall projects timeline >
Page 4 of 9

2.2 Project Cost Estimate & Budget
<An overview of the project’s overall budget, including detailed information about the expenses
and costs>
in order to complete overall project, it requires high investment. the budget required for this is
described below :-
Requirement Cost
CPU $450
Storage devices $750
Network equipment’s $550
Database $1500
OS $1000
Omnicell software $1200
Human resource $350
Total expenses $5800
Page 5 of 9

2.3 Key Assumptions
<List of all the assumptions that should be taken into consideration for the project>
there are some assumptions which that must be considered. these are as follows :-
 business needs must be analysed properly so that system is designed accordingly. it must be
done thoroughly by taking review of stakeholders.
 the system must be tested before implementation so that its efficiency is analysed. also, it will
help in finding out any errors.
2.4 Constraints
<List any known constraints that may introduce risk to the project>
 the increase in time due to lack of resources can result in incompletion of project in given
time period. this will lead to rise in costs in future
 update in technology can impact in negative way on overall project quality. it will lead to
change in software or hardware components resulting in rise in expenses.
 the improper configuration of tools and equipment’s may lead to ineffective
implementation and reducing project efficiency.
2.5 Quality Control:
<List all required quality specs>
the quality of project will be measured by testing configuration with software and hardware
components installed. also, their efficiency will be tested and measured. moreover, policies will
be formed to ensure quality. thus, it will enable in maintaining quality control of project.
2.6 Project Success Measures
<An overview of the criteria that will define success or failure of the project>
Measuring the goals with set standards. if goals are attained then project is successful
otherwise it is failure. another way to measure success is finding out increase or decrease in
sales or profits of business.
2.7 Project Progress Tracking
<A description of how project progress will be tracked, in alignment with the project status
reporting process>
it is important to track progress of project. this will be done by setting standards in each stage
and then after completion of stage, goals will be measured. project manager will observe each
activity and take feedback of members to track progress of project. besides this, members will
have to develop report after each stage. by reviewing report manager will track status of project.
2.8 Project Communications
<A description of how the project team will communicate (both ‘upstream’ and ‘downstream’
communications)>
there will be a proper communication network established so that team members can
communicate with each other in effective way. for upstream they will communicate via e mails.
also, they will coordinate with project manager regarding this. for downstream members will
communicate via an app.
Page 6 of 9

2.9 Document Management
<A description of how project documents are to be stored, including naming conventions,
storage, folder structure, version control, and retention policy>
the documents will be stored in a server in segregated way. each document will have a different name
convention. folder will be structured as below :-
Project (name)
project (stage)
project (task)
project (date)
Version control of files will be version 1.
the files will be retained in electronica way in every 3 month.
3. PROJECT TEAM ORGANIZATION, ROLES & RESPONSIBILITIES
<Include the project team organization chart with all project roles, sponsors, and SMEs. Include
any necessary detail to articulate the roles involved in the project.>
3.1 Project Delivery Approach & Team Strategy
<A description of how the project will be staffed and delivered>
Page 7 of 9

In this waterfall model approach will be followed to accomplish project. the plan will be executed
by developing strategy and assigning roles to members.
3.2 Project Roles and Responsibilities
<A description of each project role; reference the Role Description template>
Roles Responsibilities Assigned
Person
Unit/ Team
IT Project
Manager
 to plan the activities and organise them in systematic
way.
 to conduct IT audit to determine business needs.
TBD
Business Project
Manager
 working with clients, vendors, staff to manage overall
project.
 to develop plan and strategies by coordinating with IT
project manager.
Clinical
Engineering
Project Manager
 To ensure that positive outcomes are generated by
using technology.
 to manage devices and integrating systems.
 to develop strategies to minimise negative results and
improving systems.
Customer  to ensure their needs are satisfied. TBD
Performing
Organization
 to support and assist project manager in
implementation of project.
 to provide necessary resources to perform activities.
TBD
Sponsor  to ensure that project deliverables met business
objectives.
 to minimise risks associated and ensuring project is
under control.
 to approve project initiatives
 to resolve conflicts that occurs between management
and members
TBD
PMO  to set deadline of project along with its size and
resources required.
 to lay down project methodology by using different
types of tools and equipment’s.
 to develop protocols, method and procedure of overall
project.
TBD
4. Approvals
Project Manager sign off:
Page 8 of 9

Name: Title Signature: Date:
PMO sign off:
Name: Title Signature: Date:
Project Sponsor Sign off:
Name: Title Signature: Date:
Appendix
<Additional detail as necessary>
Page 9 of 9