Anda di halaman 1dari 12

P E N G E M B A N G A N S I S T E M I N F O R M A S I B E R B A S I S E N T E R P R I S E R E S O U R C E P L A N N I N G P A D A M O D U L

M A N U F A C T U R I N G M E N G G U N A K A N O D O O
D I P T . U N G G U L J A Y A S E J A H T E R A
K I C K O F M E E T I N G

PREPARED BY :

YANA PUTRI 1106130096

I M P L E M E N TA S I E R P
CONTENTS
Introduction to the project.
Goal Settings
Project Deliverables.
Project Team.
Project Timeline.
Communications Plan.
Key Project Risks.
Technical Contacts & Escalation Process.
Project Closure Terms.
Project Documentation.
INTRODUCTION TO THE PROJECT
PT. Unggul Jaya Sejahtera dalam melakukan pengolahan
datanya hanya menggunakan kertas dan Ms. Excel, sehingga
perpindahan data dan informasi yang diolah oleh Bagian
Produksi tidak terintegrasi dengan Bagian lain dan hal tersebut
menimbulkan beberapa masalah yang terkait dengan
perencanaan manajemen sumber daya produksi. Peneliti
mengusulkan untuk menerapkan sistem ERP menggunakan
metode ASAP untuk untuk mengintegrasikan proses pengolahan
data dan informasi yang mengalir disetiap harinya dari Bagian
Produksi dengan Bagian lain dan begitu juga sebaliknya.
GOAL SETTINGS

Production
Mengurangi berbagai permasalahan yang terkait dengan proses
perencanaan sumber daya produksi dan untuk mengintegrasikan
proses pengolahan data dan informasi yang mengalir disetiap
harinya dari Bagian Produksi dengan Bagian lain dan begitu juga
sebaliknya.
Manfaatnya :

Melancarkan kegiatan operasional.


Menyediakan sistem informasi dan komunikasi antar work
center.
Tercipta alur produksi yang lebih baik.
Tercipta produktifitas yang lebih baik.
Permasalahan yang terdapat didalam proses produksi dapat
dikelola dengan baik sehingga tidak ada lagi
ketidaksesuaian data dalam hal pencatatan.
PROJECT DELIVERABLES
Sistem Informasi berbasis Enterprise Resource Planning pada modul
manufacturing menggunakan odoo di PT. Unggul Jaya Sejahtera
Project Team

Configurati
Project Development Quality on
Manager Analysis SME
Team Assurance Manageme
nt

Richie
Garret
Annis Risk Shen Kimi
Syafiqa Assessment
Yani Putri SME Configurati
Hayati on Lead
Annis Rachel Paul
Yani Putri Syafiqa H
Yana Putri Risk SME
Yana Putri
PROJECT TIMELINE
Today

6 Jul '15 27 Jul '15 17 Aug '15 7 Sep '15 28 Sep '15 19 Oct '15 9 Nov '15 30 Nov '15 21 Dec '15

Analysis
5 Jul - 30 Jul

Design
31 Jul - 20 Aug

Development
21 Aug - 15 Oct

Migration
16 Oct - 29
Oct

Integratio
n
30 Oct - 12
Nov
Testing
13 Nov - 10 Dec

UAT
11 Dec - 17
Dec

Go
Live
24 Dec
COMMUNICATIONS PLAN
Communication Owner Frequen Agenda
Type cy
Scrum Meeting Project Manager Daily Update from everyone on
What was done yesterday?
What is the plan for tomorrow?
What are your obstacles?
Project Team Project Manager Weekly Discuss the project progress.
Meeting Discuss upcoming milestones.
Review the risk and issues log.
Discuss upcoming leave plans.
Any other business.
Project Status Project Manager Weekly Status update on the key project
Report parameters Schedule, Budget, Risks, Issues
and Benefits.
Project Update Project Manager Weekly 60 mins one-on-one meeting with Project
Meeting Sponsor for a full project update.

Project Control Project Sponsor & Monthly Status update on the key project
Meeting Project Manager parameters Schedule, Budget, Risks, Issues
and Benefits. And seek guidance on
decisions required.
Quality Assurance Quality Daily A list of defects count, open/close status
KEY PROJECT RISKS
Risk Risk
No Risk / Issue Owner Possible Mitigation
Category Rating
The project team does not have any None at this stage.
contingency so if any resources take
Human
1 unplanned leave or leaves the IT High
Resources
organisation then the project will suffer.

The project needs the license to be Follow up with finance
procured ASAP for the system setup to department.
Project
2 start. Any delays with the procurement Finance Medium Work with vendor to see if the
Schedule
process will delay the project. setup can be started with a trial
license.
The IT Team does not have the skillset Organise training sessions for IT
to maintain the BRMS Product. Team.
Technical
3 IT Low Organise shadowing session
Risk
with vendor consultants.

TECHNICAL CONTACTS & ESCALATION PROCESS
Project
Control

Project Project
Manager Sponsor
Swapnil Tom
Wale Ternn

Technical Lead Quality Process &


Assurance
Rimi Senha Manager Other
Eric Dake Issues

Technical Quality
Issues Issues
PROJECT CLOSURE TERMS
All the current business rules are migrated to the new BRMS.

Business Users will be able to maintain business rules.

Business Rules changes will not require IT Involvement.

The current manual process for application risk assessment will be abolished.
PROJECT DOCUMENTATION
Document Link

Project Plan <Document Link>

Business Case <Document Link>

Risk Management Plan <Document Link>