Beruflich Dokumente
Kultur Dokumente
VERSION UPDATED
TABLE OF CONTENTS
INTRODUCTION ................................
.....................................................................................................................
..................... 4
Purpose of a Requirements Analysis .................................................................................. .................. 4
Audience ................................
..............................................................................................................................
.............................. 4
Stakeholder Identification................................
................................................................................................
..................................... 4
Purpose of BRD ................................
...................................................................................................................
................... 5
Business Goal ................................
......................................................................................................................
...................... 5
Benefits of BRD ................................
...................................................................................................................
................... 5
APPENDIX A: REQUIREMENTS
ENTS ANALYSIS APPROV
APPROVAL .................................................
................. 15
1 INTRODUCTION
1.2 AUDIENCE
The audience for this document includes:
includes:-
1. NBCL Management
2. Maintenance Department.
3. ICST-NBCL
4. ESS- Service Provider [i.e., developers who may participate in the requirements at later stage for
Implementation of ERP Module]
The main purpose of the BRD is to Implement ERP for PLANT MAINTENANCE & to incorporate all
current process in System.
2. BUSINESS OVERVIEW
1. Annual Maintenance (Through OEM) OEM)- In this process a service person will come to analyze the
equipments & will submit a report to Management with complete details of service need to be done
(Spare part details, Time to resolve problem, Cost for resolving issue's). Maintenance team will send this
reports to Management and after required approvals maintenance team will make Purchase request for
spare parts if it is not available in Stores. After receiving Spare parts ,OEM person will come and resolve
the issue.
2. Preventive Maintenance- In this type of maintenance maintenance time /Date is fixed. Team will plan
accordingly.
3. Predictive Maintenance- In this type of maintenance ,team have to plan as per to working condition of
machines.
4. Break Down Maintenance- This is a situation where team have to give support (Maintenance ) on
immediately.
All the above maintenance process are captured in manual sheets and then goes to management for
preparing different reports. Only if OEM service person is comi
coming
ng for service then only a service PO is
being raised. Rest all are in manual sheets.
MAINTENANCE
PREVENTIVE
MAINTENANCE
Spare part
availability
PREDECTIVE check at store
MAINTENANCE
STORE
BREAK DOWN
MAINTENANCE
If No If
Yes
ANNUAL
MAINTENANCE
PURCHASE
REQUEST
PO
MATERIAL SERVICE PO TO
REVEIVED / GRN OEM
SERVICE PO
WORK ORDER CLOSE
Work Order In
Process
In
Annual Maintenance process
WORK ORDER
service PO need to close after CLOSE
Work Order close.
Whenever there will be some maintenance required , Maintenance team will have to create an Issue Log
in system. This may be Annual maintenance / Preventive Maintenance / Predective Maintenance /
Breakdown Maintenance. This is a sample format to log problem details with Machine.
Abbreviations
CANCELLING THE EXISTING ISSUE LOG FROM SYSTEM / EDITING DETAILS FROM SAVED LOG DATA
There may be some scenario where modification required on loged data or cancelling the log , user need
to login from their id & can make changes as per to requirement ( Approval Required-
Required Management -
Mandatory).
atory). To make any changes department have to take approval from Management ( Auto alert to
Supervisor login / request for change ) through ERP Only . This process will capture all history of making
Plan , Editing , Cancelling & Closing details.
After Making Maintenance Log for Machines , User need to make JO ( Job order) where they will
allocate the work in actual. User need to fill all details of Shift / Machine / Spare Part Required Qty to
complete the Order.
*Once the JO is assigned to a supervisor through Work Order, System will show JO status as WIP &
Once Work order is completed , system will show JO status as Completed.
In this form User can request for materials required for Maintenance process.. Material will be received &
after Maintenance / Repairing the balance materials will be issued back to warehouse. For all Spare parts
user need to select codes for the same
same.
Abbreviations
Here user need to allocate the work to respective supervisor along with the shift / Time required to
complete the JO. All spare parts will be handed over to supervisor to complete this work.
After completing
leting Work Order , User need to change the status of WO to Close. This format will also be
used for closing Work Order in system. When User will close the WO , the linked JO will be closed and
all will be recorded in Machine Repair Logs. One can see in re
reports - All history of the machines like No .
of time it has been repaired / Day Wise / Supervisor Allocated / Time taken to repair / Type of
maintenance etc.
Over All Equipment Efficiency Report
There will be a report to calculate OEE (Over all Equipment efficiency ) during a shift.
The table below contains hypothetical shift data, to be used for a complete OEE calculation, starting with
the calculation of the OEE Factors of Availability, Performance and Quality.. Note that the same units
of measurement (in this case minutes and Bottles)) are consistently used throughout the calculations.
Example-
Calculation steps-
As per to above example , system will calculate Planned Production Time, Good Bottles,
Bottles Operating Time,
Availability & finally Quality. Below formula defined for each steps.
Result-
The undersigned acknowledge that they have reviewed this requirements analysis document and agree
with its information. Changes to this version will be coordinated with, and approved by, the undersigned,
or their designated representatives.
Signature: Date:
Print Name:
Title:
Role:
Signature: Date:
Print Name:
Title:
Role:
Signature: Date:
Print Name:
Title:
Role: