Best practice to manage Information Technology System in Factory and Manufacturing Environment
This document specifies the requirements for the design of an ERP Reporting Tool System. This chapter also describes the technical requirements for the whole project. The ERP Reporting Tool on itself is described in the next chapter. Read More
| Comment on ERP Usage related to your work | ||
| 1 | Which ERP module(s) you use currently: | |
| Inventory Control Module | yes/no | |
| Sales Module | yes/no | |
| Purchase Module | yes/no | |
| Manufacturing Module | yes/no | |
| MRP Planning Module | yes/no | |
| Accounting Module | yes/no | |
| 2 | How important of ERP system relative to your daily work | very important / less important / no comment |
| 3 | How important of ERP system affect your dept/whole company business operation | very important / less important / no comment |
| 4 | ERP can provide info to help better management decision-making | strongly agreed / not agreed / no comment |
| 5 | You can logon and use ERP anytime and anywhere, i.e. good system availability to users. | strongly agreed / not agreed / no comment |
| 6 | ERP can provide function to meet nowadays requirement as well as future business operation needs | strongly agreed / not agreed / no comment |
| Pls identify what system function need to be improved_______________________________ | ||
| Comment on Overall System Operation | ||
| 7 | ERP is easy for users to operate, i.e. very User-Friendly. | strongly agreed / not agreed / no comment |
| 8 | ERP response time for performing data update or report generation is acceptable. | strongly agreed / not agreed / no comment |
| 9 | ERP provides a very accurate management information, i.e. good data integrity. | strongly agreed / not agreed / no comment |
| 10 | ERP helps to decrease the workload of users significantly. | strongly agreed / not agreed / no comment |
| If you feel your productivity declined by using ERP, please give up to three reasons you feel this happened:
_______________________________________ |
||
| 11 | ERP user access right application is under well control, i.e. good authorization procedure. | strongly agreed / not agreed / no comment |
| 12 | Users aware their liability on the system usage, especially perform data update function, i.e. system increases users accountability. | |
| 13 | ERP provides sufficient logging report to check user action, i.e. good traceibiltiy function. | strongly agreed / not agreed / no comment |
| 14 | MFG/PRO system is protected from both internal and external hacker, i.e. high system security. | strongly agreed / not agreed / no comment |
| Comment on local/external consultant and training support: | ||
| 15 | Users clearly understand the ERP Helpdesk procedure to ask for support, e.g. who and how to request ERP support, | |
| 16 | Users clearly understand the ERP support organization, i.e. the responsibility of system owners, Dept expert/key users, the first and 2nd line technical support among HK, Shanghai and Shenzhen IT-Depts as well as external vendor consultant support. | |
| 17 | The function of ERP user group committee in Shanghai and Shenzhen factory is well recongized, i.e. each dept respesentatives activity participate the user group committee meeting to improve ERP operation and raise usefull request. | |
| 18 | Training document and operation manual for ERP are adequate and esay assessable. | strongly agreed / not agreed / no comment |
| Pls identify which missing operation document you need:_______ | ||
| 19 | Training or consultant support from your supervisor is adequate | strongly agreed / not agreed / no comment |
| 20 | Training or consultant support within users dept’s expert/key user is adequate | strongly agreed / not agreed / no comment |
| 21 | Training or consultant from IT dept is adequate | strongly agreed / not agreed / no comment |
| 22 | Training or consultant from external vendor consultant is adequate | strongly agreed / not agreed / no comment |
| Comment on Problem Handling | ||
| 23 | Users clearly understand the error handling procedure to solve any ERP error, i.e. who and how to report ERP error. | strongly agreed / not agreed / no comment |
| 24 | Users satisfy the software quality of MFG/PRO in term of mininal program bug and data update error. | strongly agreed / not agreed / no comment |
| 25 | Users satisfy the error handling procedure as well as the response time to error and fix. | strongly agreed / not agreed / no comment |
| 26 | IT Dept and external vendor consultant support are technical enough to solve error. | strongly agreed / not agreed / no comment |
| Comment on further System Development | ||
| 27 | IT Dept and vendor consultant support are technical enough to provide professional advice on system development. | strongly agreed / not agreed / no comment |
| 28 | ERP system is flexibility enough to build/enhance function to meet new requirement. | strongly agreed / not agreed / no comment |
| 29 | Company allocates sufficient internal IT man-power resource on ERP function enhancement | strongly agreed / not agreed / no comment |
| 30 | Company reserves sufficient funding for external vendor on ERP function enhancement | strongly agreed / not agreed / no comment |
| 31 | The development progress on function enhancement by IT Dept is under well control | strongly agreed / not agreed / no comment |
| 32 | The development progress on function enhancement by vendor consultant is under well control | strongly agreed / not agreed / no comment |
| 33 | The project management/monitor on function enhancement by IT Dept is well performed | strongly agreed / not agreed / no comment |
| 34 | Cost of function charge by external consultant is high | strongly agreed / not agreed / no comment |
| 35 | Your Overall rating to ERP System | Excellent / Not Acceptable / no comment |
Company relies extensively on large and complex information systems for its daily operations and value creating processes. Disruption of these systems will have serious negative implications for our business. The purpose of this document is to outline the set of appropriate policies and procedures that is necessary for the management of system disruption scenarios that potentially affect our most critical information systems. This procedure allows us to minimize the impact of disruption to our most critical systems and to restore the systems to full functionality in an efficient and effective way. Read More
The objective of this plan is to provide a guideline to the organization to continue managing the business through MFGPro and to minimize the disturbance to manufacturing operations in the event that the MFGPro system is totally unavailable and cannot be recovered within 48 hours.
The service provided during the disaster recovery is of survival nature, may not extend to every user, and may require end-users to re-enter the backlog transactions at the commencement of the disaster recovery and at re-starting of the normal operation.
The recovery option will be varied in nature depending on the cause of the outage. This may require set-up of LAN server, secondary processing center, etc. Read More
The purpose of the business blueprint document is to present the results, findings and conclusions of the blueprint finalization phase of the SAP project. This document consists of:
SAP poject phase overview:
Setup and Scoping –> Blueprint –> Core System –> Core System –> Implementation
Scoping finalization realization construction Read More
Objective:
To manage change and enhancement activities of IT for ERP System. This procedure clearly identifies the responsibility and accountability of each and every party involved in the process. With the proper checks and balances, it also fosters the quality that is required for business process and automation. Read More
ERP is a multi-function and highly integrated application that supports most of the critical operations within the company. In using such an ERP application, while we can depend on some of the built-in checks and balances embedded in the system, the most important business control and appropriate use of the system lies in the working habit and disciplines of people who use it. This Policy is devised to help ensure such work disciplines are in place among all users as well as all IT staff. Read More
In this document context, ‘MFGPRO ERP System Disaster’ refers to the situation where the total system is unavailable to the users either due to hardware, network, or software problems and recovery is estimated to take more than 48 hours
‘MFGPRO Disaster Recovery’ is to offer a temporary measure/workaround solution to the organization to enable partial delivery of the processing service. Read More
1) Objectives
This document is to describe the methodology employed and process involved in the recovery of the Hyperion system currently operated in the company.This document will be updated and maintained by IT department, and posted in the Hyperion Planning Implementation Database for access by project members as well as the end-users.
2) Applicability
This applies to the following server components of the Hyperion applications.
o Application and Web Server (Application)
o Reports Server (Application)
o Essbase Server (Transaction Data)
o Oracle Server (Application Configuration/Reports Definition Data)
These servers are located in the computer room controlled and managed by IT Department.
3) Responsibility
IT department is responsible for the managed operation of the application, which involves systems installation, systems upgrade, backup, recovery, and technical infrastructure support while the systems owner is responsible for the maintenance of the models/reports built on the application.
Primary Support Secondary Support
IT Department: ….
Application Owner: ….
4) Processes
4.1) Normal Recovery
This refers to the situation where a server is corrupted due to hard disk failure and requires re-built, or alternatively, the database is corrupted and requires recovery. Advanced approval is required from the site IT Manager prior to the recovery is executed.
4.1.1 Application & Web Server (Hy-web) & Reports Server (Hy-rpt)
Essbase (Hy-Ess)
The following is for a complete rebuilt when the hard disk is totally damaged. Should only the database restore is required; the last step is needed to be executed.
Oracle
If a complete rebuilt of the Hyperion instance is required, go to step e directly.
4.2) Disaster Recovery
Disaster recovery refers to a situation where all of the server hardware is completely lost or damaged. Changeover to a temporary application infrastructure is required in order to provide minimal survival services to the user community. It is intended not to cover the entire user community, but 50% only. The fall back period is estimated to be 4-8 weeks prior to the new production hardware is acquired and set-up.
4.2.1 Backup Application Infrastructure
During the fall back period, it is planned to use a single Intel PC as a temporary machine with all products/system components installed which includes web/application, Analyzer, Report, Essbase, and Oracle. The machine should satisfy the following minimum configuration in order not to have significant performance degrade.
– CPU of at least 2GHz,
– At least 4G RAM,
– At least a 100G hard disk
– 10/100M Ethernet Connection
This machine will be located in the IT area at the another Office, and it is controlled, and reserved by IT for such purpose.
4.2.2. Recovery SLA
| Tasks | Estimated Time |
| Backup Equipment available | 2 hours |
| Server recovery | 2 days |
| Re-connect users PC to the backup infrastructure | 1 day * |
| Access & Data Testing | 1 day * |
* Concurrent event
4.2.3 Server Recovery
Procedures to recover servers as follow
4.2.4 Network Connection
4.2.5 Client Recovery
4.2.6 People Organization
During the Disaster Recovery, a project team is set-up comprising of the Application owner, site IT Manager, and the IT support staff. The Application Owner will assume the lead for this process and will co-ordinate and communicate with the user community for any systems arrangement while IT will be responsible to make sure the backup infrastructure is established, data is restored and system connection is normal.
4.2.7 Rehearsal Run
A yearly rehearsal run should be executed to ensure the above stated process is working properly. The results of the rehearsal will be documented and filed for reference.
1) Objectives
This document is to describe the methodology employed and process involved in the backup of the Hyperion system currently operated in the company. This document will be updated and maintained by IT department for access by project members as well as the end-users. Read More