Abstract Maintenance of large equipment is very common in most industrial companies.

Based on a survey, liquefied petroleum gas (LPG) companies are one in the top-ten list users of Computerized Maintenance Management System (CMMS). Maintenance of an asset and the underlying processes is termed as maintenance management system (MMS). MMS includes preventive, corrective, repair, and emergency maintenance procedures that use forms such as work orders, service reports, asset/equipment listings, and preventive maintenance checklists. MMS is used by these companies in order to gain historical track of their equipments, repairs, breakdowns, and most importantly, aid them in decision making. Several LPG companies here in the Philippines are using manual maintenance management systems mostly composed of papers and some spreadsheet editors. To address problems regarding the slow process and inconsistency of reports, the researchers proposed to develop a computerized maintenance management system (CMMS) for LPG companies. The CMMS will transform the manual MMS of LPG companies but will still retain the business logic of the company. Also, the CMMS will be more flexible and will able to resolve potential problems and risks through its implementation. The system will be implemented using the flexibility of the Drupal content management systems (CMS) application programming interface (API).

Keywords: maintenance, maintenance management system, content management system, application programming interface, computerized maintenance management system
1

Chapter 1

RESEARCH DESCRIPTION

1.1 Background of the Study

Computerized maintenance management systems (CMMS) are increasingly being used to manage and control plant and equipment maintenance in modern manufacturing and construction services industries. It is a software package that maintains a database of information about the organizations maintenance operations. The information is intended to help maintenance workers do their jobs more effectively and to help management make decisions. Examples are the calculation of the cost of the machine breakdown and allocation of resources (Computerized Maintenance Management System, 2010).

The principles of CMMS are also applied to hospital equipment maintenance where critical breakdowns could lead to life threatening situations. In recent years, private companies have come to recognize the value of these systems as a maintenance performance and improvement tool. It is becoming more attractive as more maintenance personnel have become computer literate and price of hardware have dropped significantly. Since then, it has been widely used in different industrial companies all over the world; a survey shown in appendix D on CMMS implementation by Plant Maintenance Resource Center between May and July 2004 shows the different sectors of industry all over the world that uses CMMS. The Manufacturing-Petroleum Refining Chemicals and Associated Products, which got 15 out of 74 responses is the leading user of CMMS.

With the rapid change in technology, CMMS aims to improve all aspects of business operations. As reported in A.T. Kearneys and Industry Weeks survey (2004) of 558 companies that are currently using a computerized maintenance management system, companies reported an average of: 28.3% increase in maintenance productivity, 20.1% reduction in equipment downtime 19.4% savings in lower material costs, and 17.8%
2

reduction in inventory and 14.5 months average payback time. Also, benefits of CMMS include elimination of paperwork and manual tracking activities enabling the maintenance staff to become more productive.

Today, there are numerous CMMS available in the market; in fact appendix D shows the most commonly used CMMS in a workplace. The survey was conducted on CMMS implementation by Plant Maintenance Resource Center between May and July 2004. The top 5 most commonly used CMMS are Maximo, MP, MIMS, PMS and Mainsaver, respectively.

The Western Port Alliance Company in Victoria, a home to one of the worlds most technologically advanced steel processing facilities integrates CMMS as one strategy on their way to top. It provides budgeting statistics and provides analysis tools for maintenance performance of the company (Cameron, 2004).

Here in the Philippines, there are various companies that are using CMMS. BTC which stands for Bollozos Trucking Corporation and was founded in 1996 uses CMMS to meet the need for consistent and reliable cargo transportation. The company exclusively hauled the transport of Philippines Shells fuel from respective depots to gasoline stations in Mindanao (Adlaon, et. al., 2007).

1.1.1 Narrative Listing of the Existing System The LPG company has been using manual maintenance management system. In the existing system, there are three major activities being involved. These are (1) work order, (2) preventive maintenance, and (3) corrective / breakdown maintenance.

When there is a request for equipment troubleshooting in department X, corrective/breakdown maintenance will take place. First, a staff goes to the personnel in charge to fill up the work order form. After that, document
3

monitoring and tracking for approval takes place. The form will be submitted to the engineering and services division maintenance supervisor for evaluation and approval. Once approved, the supervisor will call the maintenance engineer for the division of tasks. The maintenance engineer will then assign workers or assistants for the request. After assigning workers for each task, the job will now commence.

The actual job starts after the maintenance engineer makes a decision. The assigned workers or assistants give their service report to the maintenance engineer after they perform the task and it will be relayed to the manager. Finally, the work order will be placed into a shelf. Figure 1.1 shows the complete flow of a corrective/breakdown maintenance which specifically starts from an end user.

Figure 1.1 Corrective/Breakdown Maintenance Flow Chart

During preventive maintenance, Maintenance Engineers fill up a work order form so that maintenance assistants can start the activity. A preventive maintenance checklist will be manually filled up by maintenance assistants on a specific plant equipment/asset. After that, assistants will inform the maintenance engineer for a successful activity. These checklists will be placed into a file after a preventive maintenance is done successfully.

Figure 1.2 Preventive Maintenance Flow Chart

At the end of each month, all data that are in the shelf or file will be encoded to a computer through a spreadsheet editor; the final reports are now in spreadsheet documents. When there is a meeting involving plant maintenance, they would rely on the information in the spreadsheet editor for decision making.

1.1.2 Issues and Problems

There are some issues and problems that arise with the manual maintenance management system of the LPG Company. Problems include the delay in monitoring and tracking of documents for approval, issues regarding the historical information of assets, and also its report generation.

In the actual working environment, it is very difficult for managers to monitor and control overall maintenance. This is because no computerized system is implemented at the company to assist in monitoring the breakdown time and to have best maintenance practices. Normally, during maintenance, the maintenance department will usually engage with the manual maintenance operation by typical paper-based system, each piece of asset will have a history card or file that is piled or placed on a drawer. Accordingly, the company cannot monitor equipments status (e.g. equipment X downtime, equipment X repair cost per month, etc). When data are piled in a table during a pending work order approval or pending consolidation of papers, there are chances that data will be lost, and chances that lost papers are to be issued or produced again. This only means that a certain maintenance process will go back to where data is to be collected or it can possibly go back from the start of the process.

During report generation, there are problems regarding the manual input of data into a particular spreadsheet editor. The process of transferring or encoding will take more time and will also lead to data discrepancy, possible manipulation, and miscalculations. Also, monthly generation of information is slow, aside from manual input; analysts will provide an explanation out of the consolidated data in order for the top management to have deep understanding about the trends whether its for the maintenance, equipment inventory and work orders which are essential for the companys decision making.

Another problem regarding data consolidation is data redundancy. Since individual employees involved in the maintenance process will make reports, there is a
6

possibility of data redundancy because employees can make reports in there individual computers or from another computer. As an end result, data are saved in different storage media resulting to a more difficult data consolidation. This problem mainly focuses to the issue that centralization of database is not applied in the company.

Figure 1.3 shows the four Ms (Man, Machine, Methodology, and Materials) in problem solving which is a concept from total quality management which involves breaking down of problems into small, manageable chunks. It is popularly called as a fishbone diagram.

Figure 1.3 Fishbone Diagram of the Existing Maintenance Management Process

1.2 Statement of the Problem

The LPG Companys existing maintenance management system is done manually, resulting to slow retrieval of information and inconsistency of reports. This problem can be addressed through developing a computerized maintenance management system.

1.3 Research Objectives 1.3.1 General Objective The main objective is to develop a computerized maintenance management system using the Drupal content management system that will facilitate in the LPG Companys maintenance procedures.

1.3.2 Specific Objectives

1.3.2.1 to examine the existing system of the LPG Company. 1.3.2.2 to model the maintenance procedures using applicable modeling tools. 1.3.2.3 to design a database for the LPG Companys maintenance procedure. 1.3.2.4 to identify the advantages and disadvantages of using Drupal content management system in software development. 1.3.2.5 to implement the system using Drupal content management system. 1.3.2.6 to test and evaluate the system functionalities.

1.3

Scope and Limitation of the Research

The development of the research will cover the basic functions of a maintenance management system of an LPG Company which includes creating a maintenance work order, computerized approval of work orders, preventive maintenance procedures such as performing a preventive maintenance checklist, corrective or breakdown maintenance procedure, which primarily includes creation of service reports, and report generation

such as generating list of service reports, list of assets/equipment, preventive maintenance checklists, and list of work orders. These functions will be developed using Drupal CMS (content management systems) API (application programming Interface). The system will primarily focus on Drupals API for the database, forms, and functions. It will only use the CMSs capability and advantage in modifying the user interface and other related functions such as permission handling, content management, and data visualization. Also, the system will incorporate a database that is appropriate with the business process of the LPG Company.

The development of the system will not include functions from other computerized maintenance management systems such as generation of maintenance budget, balancing of workloads, and computation of depreciation and book value. Furthermore, the scope does not compromise the inventory of spare parts, purchase ordering system and inventory system.

1.4

Significance of the Research

The accomplishment of this study lessens the delay of the existing maintenance management procedures of LPG companies. Instead of manual work order approvals and report generation through spreadsheet editors, the process will become computerized and generated reports will be captured and understood directly by analysts after one maintenance procedure has been done. This will help the analysts to make decisions in a small period of time. The system will help prevent safety problems, yield longer asset life with fewer breakdowns, and improve labor productivity that will also result to lower operating costs. Furthermore, the development of the system using Drupal CMS and its API will contribute to the information technology field by exploring more on online and at the same time, open source applications specifically content management systems. Lastly, it serves as a basis for future researchers who want to track the same field of study.

Chapter 2

REVIEW OF RELATED LITERATURE

2.1 Maintenance Management

Maintenance management is an orderly and systematic approach to planning, organizing, monitoring and evaluating maintenance activities and their costs. A good maintenance management system coupled with knowledgeable and capable maintenance staff can prevent health and safety problems and environmental damage; yield longer asset life with fewer breakdowns; and result in lower operating costs and a higher quality of life (DPSI, 2004).

2.1.1 Types of Maintenance

Maintenance is the work performed on an asset such as a road, building, utility or piece of equipment to preserve it in as near to its original condition as is practical and to realize its normal life expectancy (DPSI, 2004). In general, maintenance can be classified into the following categories:

(a) routine: ongoing maintenance activities such as cleaning washrooms, grading roads and mowing lawns, which are required because of continuing use of the facilities (b) preventive: periodic adjustment, lubrication and inspection of mechanical or other equipment to ensure continuing working condition (c) emergency: unexpected breakdowns of assets or equipment. These are unpredictable or reactive type of maintenance and are more difficult to schedule than the above three categories (d) repair: restoring an asset by replacing a part that is broken or damaged, or reconditioning that part to its original or acceptable working condition
10

2.1.2 Building Blocks of a Maintenance Process

The key components that determine a maintenance process are the following: (a) preparation of an asset inventory: Identifying the physical features (e.g., area, material, etc.) of all assets (e.g., schools, roads, etc.) which require maintenance. A sample of asset inventory is shown in Appendix D. (b) identification maintenance activity and tasks: Defining the type of maintenance task (activity) to be performed on each asset and what work should be done under each activity; (c) identification the frequency of the task - determining how often the activities should be performed (frequency of service); this is important particularly in preventive type of maintenance. Emergency or reactive type of repairs is unpredictable, but with good preventive maintenance, the frequency of emergency situations occurring may be reduced. (d) estimation the time required to complete the task: Indicating how long each task should take to complete. (e) preparation and issuance a work order - identifying what, when, where and by whom maintenance work is to be done, figure 2.1 shows a work order sample (f) tracking of costs - determining the costs for all maintenance activities by calculating labor hours, material, equipment, and contracting costs. See figure 2.2 for sample of annual maintenance budget

2.1.3 Task Statement / Frequency / Task Times A task statement is a detailed list of the generic maintenance tasks to be performed for a particular type of asset in conducting preventive or routine maintenance. Frequency refers to how often the maintenance tasks are performed, for example, daily, weekly or every five years. To prepare a set of tasks applicable to a particular asset, one should review the physical features of an asset and/or the manufacturers operation and maintenance manual to determine the maintenance tasks, task times and frequencies required (DPSI, 2004).
11

2.1.4 Work Schedule The work schedule lists all maintenance work to be done for the whole year for each asset. It can be used to identify work load peaks and valleys, i.e., where load balancing overtime and/or part-time help is needed. It also serves as a basis for preparing and issuing scheduled work orders and for preparing the maintenance budget (DPSI, 2004).

2.1.5 Work Orders Work Order is scheduling jobs, assigning personnel, reserving materials, recording costs, and tracking relevant information such as the cause of the problem (if any), downtime involved (if any), and recommendations for future action (DPSI, 2004). Figure 2.1 Sample of Work Order

12

2.1.6 Balancing Work Load Work load balancing may reduce the extreme demands of personnel and provide a more even work load, leading to better use of human resources, reduced administrative paper work and improved efficiency. (DPSI, 2004).

2.1.7 Maintenance Budget A maintenance budget is a cost projection based on the costs of labor, equipment, material and other items (such as contracts) required to do all work identified in the Work Schedule.

2.2 Computerized Maintenance Management System A CMMS consists of hardware solution and a software package that allows an organization to manage the maintenance of equipment and facilities. It is intended to help maintenance workers do their jobs more effectively and to help management make informed decisions, possibly leading to better allocation of resources (Smith, 2007).

2.2.1 CMMS Benefits Its not surprising that the top two business issues the CMMS addresses are improvement of asset performance and labor productivity (table 2.1). After all, 56% of respondents stated that there are more than 30 maintenance employees in their organization, implying a relatively asset-intensive environment. Furthermore, about 70% of respondents have a maintenance-related job title such as maintenance manager (40%) or reliability engineer (10%). Maintenance departments have historically focused on assets as the area of greatest improvement potential (Smith, 2007).

13

Table 2.1 CMMS Benefits

2.3 Review of Related Projects 2.3.1 EIMUMS The Equipment Inventory and Maintenance and Usage Monitoring System (EIMUMS) is a Web-based system of Mindanao Sanitarium Hospital (MSH). The system has a window-based desktop interface that allows the administrator (MSH property accountant) to keep necessary information of all equipments in the hospital and records its maintenance activity. Moreover, it manipulates the data electronically and creates various reports like equipment lists, maintenance history, etc. The main feature of the system is the ability to automatically compute the equipment depreciation and book value given the life span and the purchasing date and cost (Demecillo et. al 2004).

2.3.2 RMS Bollozos Trucking Corporation The repair management system of Bollozos Trucking Corporation provides advancement in the basic transaction of the manual system in the company. Reports like outstanding worker order report, maintenance work report, vehicle repair history report, and repair history report are automatically generated by the system (Adlaon, et. al., 2007).

14

2.4 Review of Related Systems 2.4.1 Talon Resource Maintenance System

RMS is a system accessed through a Web browser that offers maintenance personnel unprecedented tools for managing discrepancies, work orders, events, corrective actions, parts, kits, assemblies, warranty checking, tool management, technician certifications, and shipping and receiving. RMSs automatic alert on event due time is the systems most outstanding feature. It eliminates the possibility of forgetting mandatory or planned maintenance events (Talon RMS Brochure, 2009).

2.4.2 ERIC MMS

ERIC MMS addresses the range of equipment and asset maintenance activities- from machine and component part information to preventive/predictive maintenance scheduling. Planning and ordering for services and parts is also automated by the system, taking into consideration order and deployment lead times. The systems most prominent feature is the predictive maintenance where the system can issue potential problems and generates work orders when readings exceed tolerance levels. The system predicts maintenance based on user-defined equipment (min/max limits), statistical measures, regular reading, trending (Jupiter Systems Inc., 2009).

2.5 Drupal Drupal is open-source software distributed under the GPL ("GNU General Public License") and is maintained and developed by a community of thousands of users and developers. It is a Web-based content management system. Text and pointers to other kinds of content are stored in a database, dynamically retrieved and composed, and presented to a user in response to a request sent via a web-browser (Drupal, 2010).
15

2.5.1 Drupal as Content Management System A content management system (CMS) is a tool that enables a variety of technical and non technical staff to create, edit, manage and finally publish a variety of content, while being constrained by a centralized set of rules, process and workflows that ensures coherent, validated electronic content (Enterprise Content Management, 2008).

2.5.2 Modules Modules are functional plug-ins that are either part of the Drupal core or contributed items that have been created by members of the Drupal community. 2.5.2.1 Core Module These modules are required to run Drupal:
y

Block This controls the boxes that are displayed around the main content.

y y

Filter This handles the filtering of content in preparation for display. Node This allows content to be submitted to the site and displayed on pages.

y y y

System This handles general site configuration for administrators. User This manages the user registration and login system. Watchdog This logs and records system event.

2.5.2.2 Contributed Module These modules are contributed by developers of Drupal modules. These are all tested and used on drupal.org:
y y y

Image This allows uploading, resizing and viewing of images. Simplenews This sends newsletters to subscribed e-mail addresses. Google Analytics This adds Google Analytics click tracking for marketing purposes.
16

y y y

Views - This creates customized lists and queries. Views exporter This allows exporting multiple views at once. Views UI This gives an administrative interface to views.

Figure 2.5.2.2.1 Featured Modules in Drupal

2.5.3 Drupal as Content Management Framework It has an API for managing content, user sessions, and forms. Essentially, it is a part of a proof of concept of what the framework can do. One of the main features of its API is its database abstraction. Drupal is built on top of a database abstraction layer that allows users to use Drupal with MySQL and PostgreSQL. Other SQL databases can be supported by writing a supporting database backend containing fourteen functions and creating a matching SQL database scheme (Drupal, 2010). Other features of API that are part of Drupal include the following:

17

Figure 2.5.3.1 Main Features of Drupal API

2.5.3 Who uses Drupal? The following are companies using Drupal: y y y y y y y Ubuntu Linux Sony Music Box Warner Bros. Adobe Sun Microsystems IBM Yahoo

18

2.5.4 Why do they use Drupal? Drupal is used for the following reasons: y Free Software- Savings in software costs (licenses and lifecycle costs). It means no upfront cost that makes it an attractive option y Features- It is loaded with various features. The caching feature eliminates database queries that results to increased performance and reduced servers load. y Control- You can customize the functionality of Drupal according to your needs. Basically, you can turn off the stuff you dont like and turn on the stuff you need. y Extensibility- The hook system allows you to inject at any point and alter the way that Drupal works. For example, change the way users log in. y Maturity- Drupal has been around for over 7 years. Even though it is now in its 7th version, there already has been 12 releases of Drupal. y Security- There is a dedicated security team not only for the Drupal Core itself but also to handle contributed modules. The team focused on educational developers. 2.5.5 Drupal Feedback

IBM, as one of the users of Drupal, compared Drupal to other five softwares and came up with Drupal as on top (Drupal, 2010). Figure 2.5 Feedback of Drupal in IBM

19

2.6 Summary As shown in table 2.6.1, almost all CMMS have the same features such as tracking equipment history, report generation and preventive maintenance management. The proposed system will apply all the major functions in a CMMS that are also features of the related systems as shown in the table above. From the common features, the proponents derived other features that will mostly help in the betterment of the system. These features are the paperless approval management, system and user security and data visualization that will give support in the companys decision making. The system and user security along with the flexibility of functions and its procedures are achieved through developing the system using a CMS. From the CMS itself, features currently stated are already embedded from its source code, and can be upgraded through its framework or API. Table 2.6.1 Summary of the Related Systems
(proposed Feature EIMUMS RMS Bollozos Trucking Corporation Talcon Resource Maintenance System ERIC MMS system)

Tracking Equipment History  Report Generation Equipment Depreciation Management Automatic Work Order Generation ( Preventive Maintenance Management) Automatic Alerts Generation or Warnings of the Major Maintenance Events (Ex. expiration of warranty) Inventory Management Ordering, Shipping and Receiving Management Paperless Record Keeping Corrective Maintenance Management  Paperless Approval Management System and User Security Data Visualization ( Charts or Graphs)                          

      

20

Chapter 3

RESEARCH METHODOLOGY

All projects can be managed better when segmented into a hierarchy of steps. The proponents will use prototyping as a methodology for the development and implementation of the system. Figure 3.1 Prototyping Model

Data Gathering

System Analysis and Design

System Prototype

Testing and Evaluation

System Deployment

A prototype will be used to simulate only a few aspects of the features of the overall system, it can also be completely different from the eventual implementation (Software prototyping, 2010).

21

3.1 Phase 1 - Data Gathering and Analysis

In this phase, all pertinent information which regards to the existing system and the maintenance management process in general will be gathered and analyzed. The steps of this phase include consultations, interviews, gathering of requirements and gathering of materials and resources. These steps will give us an idea on the complete flow of the existing system and better understand the underlying information behind each process. The proponents will first conduct gathering of general information about the maintenance management and its processes. From the obtained general idea, the proponents will engage in performing consultations and interviews about the project. An interview with the LPG Company personnel is conducted in order to obtain specific knowledge of what is there way in performing the maintenance management process. The data gathering results to an analysis that the existing system of the LPG Company is done manually.

3.2 Phase 2 System Analysis and Design

The data gathered and the knowledge that has been extracted from the analysis of the previous phase would give us an understanding on what we should create. All data that has been gathered would be thoroughly analyzed in this phase. The analysis would be done through the use of modeling diagrams. Modeling diagram shows how the system functions as data are inputted and the output are displayed. The initial design analysis and models will be the basis for the implementation of a prototype. From a span of time, the prototype will be changing while the design is also on the phase of its improvement.

3.2.1 UML (Unified Modeling Language) UML is a standardized general-purpose modeling language in the field of software engineering. These include a set of graphic notation techniques to create visual models of software-intensive systems. UML combines techniques from data modeling, business modeling, object modeling, and component modeling. It
22

can be used with all processes, throughout the software development lifecycle, and across different implementation technologies.

3.2.1.1 ERD (Entity Relationship Diagram)

The ERD is an abstract and conceptual representation of data. It is a modeling method used to produce a type of conceptual schema or semantic data model of the system, often a relational database, and its requirements in a topdown manner. ERD is composed of physical objects or events called entities, relationship which captures two or more related entities, and attributes.

3.2.1.2 Use Case Diagram

The use case diagram is the building block to which system is designed and built. Each use case in a use case diagram depicts one specific scenario in the system. Each use case is also associated with only one role that users have in the system. An overall use case diagram includes a use case, an actor which represents a role that the user can play, an association which links an actor with the use case with which it interacts, and boundary which defines the scope of the system.

3.2.2 System Architectural Design System Architecture is a formal description of a system, organized in a way that supports reasoning about the structural properties of the system. It defines the system components or building blocks and provides a plan for the overall implementation and deployment of the system. Also, it represents the systems mapping functionality onto hardware and software components, a mapping of the software architecture onto the hardware architecture, and human interaction with these components.
23

3.2.2.1 Client Server System Architecture

The architectural design of the system involves several users from the company which leads to an interconnectivity between the client and the server. Each client can work and can generate their own requests providing that they are connected with powerful machines such as servers.

The database functionalities of client-server system architecture are divided into two which is the back-end and the front-end. Back-end manages access structures such as query evaluations, optimization, concurrency control and recovery. The front-end consists of tools such as forms, reports, and graphical user interfaces. The interface between the front-end and the back-end is through SQL or through an API.

Figure 3.2 Initial System Architectural Design

CMMS Server

Client

Client

Client

...

Client

3.3 Phase 3 Implementation

In this phase, the models or designs being created in the previous phase are utilized through its physical realization which is the implementation of the system. There are many types of implementation that is applicable such as implementing from scratch,
24

using new technologies, or to implement through the use of a framework. The system would be implemented through the use of a framework which is embedded from the Drupal Content Management System (CMS) which is its Application Programming Interface (API). The implementation using the API will make the system flexible in such a way that it can easily be added with functionalities that are essentially required. It is also flexible in terms of its database since the database abstraction is included in the CMSs API.

3.4 Phase 4 Testing and Evaluation

Testing and Evaluation is done in every system implementation. This phase is recommended in order to meet system and user requirements and to test if the system serves its purpose correctly. One of the things that are to be tested in this phase is the functionality of the system from the users point of view. It is done through some testing and evaluation methods and procedures.

3.4.1 Testing and Evaluation Methods

There are several methods in testing and evaluating systems but it differs in what the method would actually evaluate.

3.4.1.2 End User Survey

End user surveys are widely used in the field of software development. This is to evaluate if there are defects in the system and also to evaluate if users are confident in using the system. End user surveys prevent systems from continuously produced with defects since from the information gathered from the survey, developers will have time to fix such defects. A User Survey Form is shown in Appendix D.
25

3.4.1.2.1 Likert Scale

Likert Scale is a psychometric scale commonly used in questionnaires, and is almost widely used in survey research which often termed as rating scale. When taking the scale, respondents specify their level of agreement to every statement in the questionnaire. Table 3.2 Sample Likert Scale 1 2 3 4 5 Strongly Disagree Disagree Neither Agree nor Disagree Agree Strongly Agree

3.5 Phase 5 Deployment

In this phase, it shows us how the system will be used or operated after the implementation and what should be done in order to achieve good implementation. After testing and evaluation, a plan would be established to ensure quality deployment of the system. It must also be ensured that there are hardware requirements and specifications that are set in order to achieve good running system based on the facts available from the testing and evaluation. If all of the said requirements are complied, the system is now ready for deployment.

26

Chapter 4

CALENDAR OF ACTIVITIES 4.1 Gantt Chart

Activities Data Gathering System Analysis and Design Implementation Testing and Evaluation Deployment

July August September October November w1 w2 w3 w4 w1 w2 w3 w4 w1 w2 w3 w4 w1 w2 w3 w4 w1 w2 w3

* * * * * * * * * * * * * * * * * * * * * * * * * *

4.2 Milestones and Deliverables

Date
07/09/2010 07/16/2010

Activity
Data Gathering Data Gathering Articles

Deliverables

Background of the Study Review of Related Literatures Narrative Listings of Existing System

07/23/2010

Data Gathering

Issues and Problems Statement of the Problem

07/27/2010

Data Gathering

Objectives of the Research Scope and Limitations of the Research Significance of the Research

07/31/2010

Data Gathering

Research Methodology Gantt Chart Milestones and Deliverables

08/14/2010

System Analysis and Design

Data Analysis

27

08/17/2010

System Analysis and Design

System Architectural Design Entity Relationship Diagram Use Case Diagram

08/25/2010

System Analysis and Design

Activity and Sequence Diagrams Other UML Diagrams Initial Prototype

09/14/2010 10/21/2010 10/22/2010

Implementation Implementation Testing and Evaluation

Initial Implementation Final Implementation Testing and Evaluation of System Functions Use Case Testing

10/23/2010 11/10/2010 11/25/2010

Testing and Evaluation Testing and Evaluation Deployment

End User Testing End User Survey Finalization of Surveys Deployment of the System

28

Appendix A. Bibliography

Adlaon et. al, Repair Management Systems of Bollozos Trucking Corporation, MSU-IIT: Iligan City, 2007 Cameron. Western Port Alliance 2004 Yearly Report, Western Port Alliance Company Victoria: Australia, 2004 Demecillo et. al, Equipment Inventory and Maintenance and Usage Monitoring System, MSU-IIT: Iligan City, 2004 DPSI, Operations and Maintenance Best Practices Guide, North Carolina: Greensboro, 2004 (Drupal,2010) Drupal [Online]: http://www/drupal.org (Enterprise Content Management, 2008) Enterprise Content Management [Online]: http://www.contentmanager.eu.com/history.htm Jupiter Systems Inc, Enterprise Resource Information and Control System, Makati City: Philippines, 2009 Rosenblum, Robert. Computerized Maintenance Management System, 2010 Kearney, A.T., Industry Week Survey, Industry Week, 2005 White et. al, Software Prototyping, 2010 Schenk, H.G., CMMS Implementation, Plant Maintenance Resource Center Cambridge: University Press, 2004 Smith et.al, National Energy Consultation, Cambridge: University Press 2007 Talon Resource Maintenance Systems Brochure, Talon Company, Dallas, 2009
29

Appendix B. Resource Person Rez A. Cabrera Systems Analyst Iligan City Plant Petronas Energy Philippines Incorporated Matab-ang, Dalipuga, Iligan City rezcabrera@petronas.com.ph

30

Appendix C. Definition of Terms

Maintenance- work performed on an asset such as a piece of equipment to preserve it in as near to its original condition as is practical and to realize its normal life expectancy Maintenance Management - orderly and systematic approach to planning, organizing,
monitoring and evaluating maintenance activities and their costs

Content Management System - tool that enables a variety of technical and non technical staff to create, edit, manage and finally publish a variety of content, while being constrained by a centralized set of rules, process and workflows that ensures coherent, validated electronic content Application Programming Interface (API) - interface implemented by a software program that enables it to interact with other software. It facilitates interaction between different software programs similar to the way the user interface facilitates interaction between humans and computers Computerized Maintenance Management System (CMMS) - consists of hardware solution and a software package that allows an organization to manage the maintenance of equipment and facilities. It is intended to help maintenance workers do their jobs more effectively and to help management make informed decisions, possibly leading to better allocation of resources Drupal free and open source content management system (CMS) written in PHP and distributed under the GNU General Public License. Work order- scheduling jobs, assigning personnel, reserving materials, recording costs, and tracking relevant information such as the cause of the problem (if any), downtime involved (if any), and recommendations for future action Preventive Maintenance a schedule of planned maintenance actions aimed at the prevention of breakdowns and failures. It is designed to preserve and enhance equipment reliability by replacing worn components before they actually fail Corrective Maintenance activities performed after a fault or problem emerges, with the goal of restoring operability to the equipment Modules functional plug-ins that are either part of the Drupal core or contributed items that have been created by members of the Drupal community Data Visualization graphical presentation of multidimensional data so that viewers can understand the underlying structure and relationships hidden in the data

31

Equipment Downtime refer to periods when equipment is unavailable Routine Maintenance ongoing maintenance activities such as cleaning washrooms, grading roads and mowing lawns, which are required because of continuing use of the facilities Emergency Maintenance unexpected breakdowns of assets or equipment. These are unpredictable or reactive type of maintenance Repair Maintenance restoring an asset by replacing a part that is broken or damaged, or reconditioning that part to its original or acceptable working condition Machine Breakdown - breaking down, wearing out, or sudden loss of ability to function efficiently, as of a machine

32

Appendix D. Forms

Work Order Form

WORK ORDER REQUESTING DEPARTMENT: CLASSIFICATION: WORK ORDER NO.

ORIGINATOR:

APPROVED BY:

DATE REQUIRED:

WORK ORDER RECEIVED:

DESCRIPTION OF WORK:

SCHEDULING: START DATE:

END

MAINTENANCE:

OPERATION:

ACCEPTANCE: ENDORSED FOR ACCEPTANCE MAINTENANCE:

DATE:

REMARKS:

ACCEPTED DATE:

33

Preventive Maintenance Checklist Form

PREVENTIVE MAINTENANCE CHECKLIST

PLANT EQUIPMENT EQUIPMENT CODE DATE / TIME JOB STARTED DATE / TIME JOB COMPLETED DATE OF NEXT INSPECTION : : : : : : FREQUENCY : REV NO: DATE ISSUED: PAGE: WEEK NO.:

NOTE :

ITEMS TO CHECK

OK

REMARKS

NAME Job Carried Out By :

SIGNATURE

Certified by :

34

Asset Inventory Sample

35

User Survey Form

36

Appendix E. Surveys CMMS Brand Survey

37

Sectors Using CMMS

38

Appendix F. Personal Vitae

Florisa Mae D. Tiongson

1464 Purok 13, Nabunturan Compostela Valley Province Philippines, 8106 Mobile No.: +63917-249-5798 Email: cjamaila@yahoo.com

WORK EXPERIENCE

Globe Telecom Inc. Iligan Business Center Hp# 0917-6888288 Fax# 063 492-2293

March 2010 July 2010

  

Order Management Troubleshoot malfunctioning computers, printers and other devices Assist in Administrative work

PROJECT EXPERIENCE

MSU-IIT Integrated Developmental School Enrolment and Student Management System

Department of Public Works and Highways Official Website- Iligan Chapter

39

EDUCATION

Mindanao State University Iligan Institute of Technology School Year 2005 2010 Bonifacio Avenue, Tibanga, Iligan City, Lanao del Norte, Philippines Bachelor of Science in Information Technology System Major in Management Information

Nabunturan National Comprehensive High School 2001-2005 Poblacion, Nabunturan Compostela Valley Province High School / Secondary Education Diploma

Nabunturan Central Elementary School 2000 Poblacion, Nabunturan Compostela Valley Province Elementary / Primary Education Diploma

TRAININGS/SEMINARS ATTENDED y y y y y y Object Oriented Technology Seminar (2010) March 2010 MSU-IIT IT Research Study and Symposium (2010) January 2010 MSU-IIT Annual Software Free Day Symposium (2009) July 2009 MSU-IIT Regional Quality Circles Convention (2009) August 2009 MSU-IIT Regional Quality Circles Convention (2007) June 2007 Cagayan De Oro city Student Cooperative Orientation Seminar (2006) September 2006 MSU-IIT

40

SKILLS y y y y y y y y y y fluency in English background in Accounting background in Management polished Leadership skills and good in Communication with people deep understanding of Technology with focus on delivering Business Solution Design Document and User Documentation proficient in MS Word, Excel and PowerPoint comprehensive technical knowledge in HTML, DHTML, CSS to design interactive Web User Interfaces Proficient working with Joomla! and Dreamweaver familiar with implementation strategies using C and Java

AFFILIATIONS/MEMBERSHIP y Junior Information Technology Society (JITS), MSU-IIT Member, S.Y. 2007-2010

PERSONAL INFORMATION

Nick Name Age Gender Legal Status Religion Date of Birth Place of Birth Citizenship Languages Spoken

: Risa : 22 years old : Female : Single : Roman Catholic : March 11, 1988 : Nabunturan Comval : Filipino : English, Tagalog, Cebuano

41

ERNEST OLIVER C. CASANES

Blk. 4, Lot 12, Zone 8, Abegail Subd., Del Carmen, Iligan City Lanao del Norte, Philippines, 9200 Mobile No.: +63916-865-7130 Email: ecasanesodesk@gmail.com

WORK EXPERIENCE Petronas Energy Philippines Inc. Matab-ang, Dalipuga, Iligan City Engineering Services Division (Trainee) April 2010 May 2010 y y y Assisted on solving Information Technology related problems for the company Created the source code for PEPI Maintenance Management System Assisted in deploying the PEPI Maintenance Management System Management Information Systems Department

PROJECT EXPERIENCE y Integrated Developmental School Enrollment and Student Management System (IDSESMS) y God s Will Consultancy Services Website

42

EDUCATION Mindanao State University Iligan Institute of Technology School Year 2007 2011 Bonifacio Avenue, Tibanga, Iligan City, Lanao del Norte, Philippines Bachelor of Science in Information Technology Development Major in Business Software

Iligan City East High School Regional Science High School 2003-2007 Sta. Filomena, Iligan City High School / Secondary Education Diploma

Iligan City East Central School 2003 Tambo, Iligan City Elementary / Primary Education Diploma

TRAININGS/SEMINARS ATTENDED y y y Object Oriented Technology Seminar (2010) IT Research Study and Symposium (2010) Regional Quality Circles Convention (2008) IC. March 2010 MSU-IIT January 2010 MSU-IIT June 2007 Elena Tower Inn,

43

SKILLS y y y y y y y y y Programming knowledge (e.g. Java, Python) Web programming using PHP/Javascript Web design using HTML/CSS Web development using open source CMS (content management system) (e.g. Joomla, Wordpress, Drupal) Database design and management in PostgreSQL and MySQL Knowledge in multimedia development tools and Microsoft Office Software Proficient in Adobe Dreamweaver Basic networking technical skills Computer hardware and software troubleshooting

AFFILIATIONS/MEMBERSHIP

Junior Information Technology Society (JITS), MSU-IIT Member, S.Y. 2007-2011

PERSONAL INFORMATION

Nick Name Age Gender Legal Status Religion Date of Birth Place of Birth Citizenship Languages Spoken

: Ernest or Oliver : 20 years old : Male : Single : Roman Catholic : September 14, 1990 : Iligan City : Filipino : English, Tagalog, Cebuano

44

KEVIN AGUSTIN T. BONGCAWEL

Block 20 Lot 15, Pineapple Country Homes 1, Damilag, Manolo Fortich, Bukidnon, Philippines, 8705 Mobile No.: +63906-139-1091 Email: bongcawelkat@gmail.com "Happiness is only real when it is shared. WORK EXPERIENCE Petronas Energy Philippines Incorporated (On Job Trainee) Dalipuga, Iligan City April June 2010 y Developed a system for the company in aiding them with their maintenance process. y Worked with System analyst and Network Technicians in troubleshooting their problems. PROJECT EXPERIENCE y Institute Online Palakasan Monitoring System (IPMS) y MSU SASE Online Application y Zammi Shirts & Prints E-Commerce Website

EDUCATION Mindanao State University Iligan Institute of Technology School Year 2007 Present Bonifacio Avenue, Tibanga, Iligan City, Lanao del Norte, Philippines Bachelor of Science in Information Technology Major in Business Software Development Holy Cross High School 2003-2007 Camp Phillips, Manolo Fortich, Bukidnon High School / Secondary Education Diploma Our Lady of Lourdes Elementary School 1995 Camp Phillips, Manolo Fortich, Bukidnon Elementary / Primary Education Diploma
45

TRAININGS/SEMINARS ATTENDED
y y

Productivity Improvement Circles National Convention The Design Patterns Seminar 2010 MSU- IIT

2008 Pearlmont Hotel

SKILLS
y y y y y y y y

Web programming using PHP/Javascript Web design using HTML/CSS Database design and management in PostgreSQL/MYSQL Knowledge in multimedia development tools and Microsoft Office Software Proficient in Adobe Photoshop, Dreamweaver. Basic networking technical skills Computer hardware and software troubleshooting Knowledge in Drupal Content Management System

AFFILIATIONS/MEMBERSHIP
y

Junior Information Technology Society (JITS), MSU-IIT Member, S.Y. 2007-2010

PERSONAL INFORMATION

Nick Name Age Gender Legal Status Religion Date of Birth Place of Birth Citizenship

: Kimboy : 19 years old : Male : Single : Roman Catholic : August 22, 1986 : Camp Phillips, Bukidnon : Filipino

Languages Spoken : English, Tagalog, Cebuano

46