Computerized global management of maintenance

Transcription

1 Computerized global management of maintenance Linx 7.0 is a program that makes easy and automates the management of the Maintenance department, allows an exhaustive control of all the tasks (Preventive, Corrective, Predictive, New Installations, etc.) and gives information to make good decisions. It is designed to work with Windows systems and in a local network or Intranet/Extranet/Internet environment. It stands out as having a user--friendly interface, being easy to use and needing only a quick, intuition--based learning. At SPI, we design applications to make computers adapt to people s needs, not vice versa. This program has all the necessary modules to manage entirely a Management Department, be it an industrial company, a building or a service company. It is extremely flexible, and never makes the user to put in what they may consider unnecessary data. In no case the program forces, it only suggests. There is no need to appoint a specific person or office worker to manage the program, as every person in the company can contribute to the well--functioning of the program.

2 Example. Linx 7.0 main window and management of Scheduled WOs Example. Linx 7.0 main window and Structure of Actives.

3 Description of functions The program consists of 7 sections: Files This is the section where basic data for the management of the maintenance is stored. The Files are: S Organizing Structure. Section where the structure of the program is defined graphically.there are no pre--determined levels and it is possibletodefineupto99levels of dependency. The program is based on the relationship Father and Sons of the various components. In this section it is possible to define the Cost Centers and the Families of Components, with their respective technical file.they are not required fields and the user can define them entirely. Example. Window to access the Organizational Structure file.

4 S Workers. Section where the details about the human resources assigned to the maintenance are kept. The program lists three categories of workers: those who belong to the firm owning the program, those who belong to External Companies and External Companies. Example. Window to access the Worker file. S Spare Parts. Section where the spare parts to be used are listed. All the data relative to those spare parts is also listed here.warehouses, Suppliers and Categories of Spare parts.the program can create a technical file in order to list the technical characteristics of each spare part. The whole section of spare parts can be managed by means of bar code scanning Example. Window to access the Spare Parts file.

5 S Operations. Section where the maintenance operations for the Scheduled and Non Scheduled WOs are defined. The Causes for the Corrective WOs are also listed here. It is possible to create various modules of Security and Environment, which will be assigned to eitherone of the Scheduled and Non Scheduled Operations. Example. Window to access the Scheduled Operations file. The program allows controlling the stoppage time of the elements. The expected response time and the actual response time can also be controlled. The program can monitor the efficacy of the interventions, manage the resources and apply Safety and Environmental measures to the orders. It can set checklist tables for the Worker. An image is worth a thousand words For this purpose, a system for document managing has been integrated in every section of the program. Such system allows adding any extra file to the program: user s guides of spare parts/machines in digital format. It can also include diagrams and plans, training videos to mend machinery, photographs, etc. All the above -mentioned documents can be printed together with the WO, be it listed under Scheduled or Non Scheduled Operations or Safety modules

6 Maintenance The Scheduled and Non Scheduled WOs are monitored here. The management of the Warehouse (Orders, Stock Checking, Income and Expenditures, etc.) is also executed here. The Maintenance consists of: S Orders. Section where the Scheduled and Non Scheduled WOs are created and managed. The Maintenance and Guarantee Contracts are also created and managed here. This menu allows the monitoring of Breakdown Requests sent by users, the Workers Workload and the Planning of the WOs. Example. Window to access the Scheduled WOs. In Linx 7.0, the whole management of WOs is very visual, with plenty of colors and icons that show clearly the state and the urgency of each WO, the resources assigned to it, etc. One of the most important sections of the program is the communication, or message center. In fact, the program has always been thought of as a tool that allows informing of and following work orders. For such purpose, a powerful messaging system has been incorporated into the WO section. The Scheduled and Non Scheduled Maintenance Operations can be assigned to any of the elements previously defined in the Organizing Structure of the Company. In Linx 7.0, the WOs can be scheduled in terms of time (days) or by applying meters assigned to each element: Piece, Time, Kilometers, etc.

7 The program has a system of colors to identify the state of every order of work: Order of Work in Progress Order of Work that should be carried out Today Order of Work to be carried out in the Future Order of Work that should have been carried out. The program is designed to help the person in charge of the maintenance. Therefore, when a WO is activated, it will suggest the names of the workers who have a lighter workload at that moment. It will also tell the operator how long it took them to carry out the same operation in the past, which Workers are on duty, which ones are on holiday, etc. It is also possible to plan the Scheduled and Non Scheduled WOs by means of a system similar to the Outlook one. Such system allows assigning resources, days, times and knowing the actual workload of each Worker. The program will suggest the resources depending on the scheduled day and time and the workload of each Worker.

8 Once the WO has been carried out, the work order will be Closed. The Operator can, if it is necessary, modify the notes, resources, the time taken to carry the order out, the hours of inactivity, the cost center, include documents (images, documents, etc.). When an OW is Closed, it can no longer be modified. It becomes part of the history and a piece of the statistical data so that it can be looked up later on. Only the Administrator of Linx 7.0 will be able to recover a WO in order to correct it. When Closing the Scheduled and Non Scheduled WOs, the operator will write down the hours worked by each Worker, the cost of the work carried out by External Workshops, etc. in order to monitor the cost of each work order. Knowledge is power In the section Causes for Correction, the program revises the history of each machine and then suggests the probable cause for the Breakdown. It will also show the repairs made in each case. This system enables to shorten the search and the solution to the Corrective orders. It uses the history as a source of knowledge.

9 Workloads. This utility enables the person in charge of the maintenance to see the workload of each Worker (Internal or External), prioritize orders, move WO from a Worker to another, etc. Example. Window to access Workloads. S Orders. Section where the Orders for Spare Parts to Suppliers and the Orders for Servicing to External Workshops are created and managed. Example. Window to access Orders for Spare Parts.

10 S Warehouse. Section where the Entry of Spare Parts and their Exit out of the various warehouses is managed. This section also allows controlling the Inventory and the movement of Spare Parts around the Warehouses. The Entry and Exit of Spare Parts and the Stocks Control is carried out by bar code scanning, as this is the quickest and most reliable way. Example. Window to access Stocks Control. The program allows monitoring and controlling everything related to a single spare part: entry, exit, orders, inventories, minimal stocks, etc. It provides options for multi--storage and multi--location, as the spare parts can be stored in various warehouses. The program can also find out where, in a given warehouse, the spare parts are (shelves, drawers, tool cabinets, etc.) It is possible to list the various companies that supply the same spare part, the last price paid to buy it, the product reference, its usual batch, etc. in the file where the spare part is detailed. In this same file, the user can decide the minimum or critical stock number so that the program can warn them when such number is reached and they can place a new order. No movement in the stock of spare parts can be made without it being recorded by the program. Physical inventories to ascertain the actual number of spare parts can be carried out by the warehouses and places where they are stored. The management of spare parts by means of bar code makes the assignment of WO an easy and quick task to perform.

11 S Parameters. Section where the types of Maintenance, Scheduled and Non Scheduled, are defined.just like all else, in Linx 7.0, this section is totally definable by the user so that they can establish the types of maintenance that best suit their needs. Such types can be: Preventive, Corrective, New installations, Legal, Quality, Improvements, etc. When defining WOs, it is also possible to create and define the various degrees of urgency and which icons show them. Example. Window that defines Types of Maintenance. Example. Window that defines Types of Urgency. Here are also defined the theoretical Budgets for the Elements and Cost Centers and also the management of the Work Calendar: Timetables, bank holidays, etc.

12 Queries This section allows the user to analyze the data generated by the program, and to create lists. The program features an inquiry system in HTML format (Web), which can be accessed from the program itself or through a browser (Internet Explorer, Safari, etc.) Linx 7.0 does not have lists of pre--determined inquiries. However, it does have a report generator to help the user to inquire and then view the chosen fields in the list. Once the inquiry has been made, it is possible to Save it in the Inquiries Repository in order to be retrieved later on. Example. Window to Query of Maintenance.

13 Example. Window to access Statistics of Costs. The program allows the user to know: S General Costs S Costs detailed under Spare Parts/Workers/External Workshops/Maintenance Contracts S Costs for each item S Costs for the Cost Centre S Hours of Inactivity S Cost for the Hours of Inactivity for item or Cost Centre. S Compare between the expected and the actual budgets S Calculate the ratio of efficiency in the interventions S To know the deviations of time, resources and costs S To make statistic lists based on the maintenance indicators:mtbr, MTTR, MTBF, Machine Availability, Hours of Intervention, Number of WOs, etc....and any other data that has been put into Linx. The Inquiry section does not features predefined lists, so the user can create their own lists and analyze data the way they consider best!

14 Statistics S EThis section allows the user to analyze in graphic format the data in the history of the Preventive and Corrective orders. Once a statistic has been created, it canbeexportedinexcelformator saved in graphic format. Example. Window of Statistics of Costs. What Lies Beneath The Statistics section (either in graphic format or through inquiries) allows the user to follow the financial weight of their maintenance in a matter of seconds. It will allow them to find out which machine is the most troublesome, which one is generating more expenses, which one has more hours of inactivity due to Corrective interventions, etc.

15 Users/Profiles The program allows multiple users to be registered. Each user can choose the profile they will have. The program only shows those menus and icons previously created for each profile. The access to the program can be restricted for clients use, web inquiries or users who Apply for Interventions. Example. Window of Profiles. Those who manage the Users section have total control over it. They can remove menus, restrict access, allow the display but not the execution of a command, etc. The managers of the Users section can make the users to access only their assigned WOs and make them to Close the WOs only under the supervision of the person in charge of the maintenance. Example. Window of Users.

16 Users that have the mere task to submit Applications for Intervention can be also defined. This part of the program works with any browser and allows the user to apply for a corrective service to the maintenance department. Also, the user who placed the request can see the status of their application. The communication between the maintenance department and the user who places the request is possible. This enables both parties to follow a WO through an service that reaches out to the people who carry out the WO. The Maintenance Department has the authority to approve or reject an Application for Intervention sent by a user. On the other hand, the Maintenance Department can request the approval of the user who placed the request to carry out the task they had applied for. Time is Money Nowadays the number of requirements for Maintenance Departments is ever increasing. However, there are less resources and the level of specialization is higher. The people in charge of Maintenance are professionals who do their job properly and cannot waste their time with paperwork. Linx 7.0 is easy to implement and needs little time to be managed. It also gives, in real time, the necessary data to the person in charge of the Maintenance so that they can take the best decisions.

17 Settings Here the setting parameters of the program are entered, such as the details of the company, numbers of orders, management of stock, bar code scanner, etc. Utilities S This section features a Library (Management of Documents), Management of s messages, Tools for the Touch Screen, Change of Password and Log off. The program has a very useful tool to ensure that the workers manage well the WOs they have been assigned. This utility requires the use of a touch screen and to configure the terminal as such. The program also includes the management by bar code: Scheduled or Non Scheduled WOs, Orders, Spare Parts, Warehouse, etc. Workers can log in by means of a magnetic card or bar code.

18 Help The program features an on -line help web site that includes all the modules. The help site is easy to navigate. The User can access the help site from any window of the program by pressing the F1 key. Versions of the Program Linx 7.0 is sold in its entirety. There are neither additional modules nor additional users. SPI sells a license to the purchasing company and this decides how many work places it wishes to install. The installation of new clients of the purchasing company has no additional costs. The program has 2 versions: S S Linx 7.0 Single. It is for those companies that work under a single company name, but it gives the opportunity to define the various elements present in such company. Linx 7.0 Multi Company. It is for groups of companies that operate under different names or companies that carry out maintenance work for other businesses. There are 3 versions available: Multi Company 5. To register 5 companies. Multi Company 10. To register 10 companies. Multi Company Full. To register an unlimited number of companies. Technical Data The program is designed to work through a Client /Server system suitable for Windows 9X or higher. Server. The server requirements are defined from the database that the purchaser wants to implement. Linx 7.0 works with SQL Multiuser data bases: Oracle 8.0.X or SQL Server 7/2000/2005/2008, SQL Express, etc. Linx Client. The requirements for the customer are 50 Mb of disk space and 256 Mb of Ram. Web customer or Application for Intervention. The requirements are determined by the chosen browser (Explorer, Safari, etc.) For communication between Server and Customer Linx 7.0, itis used the SOAP protocol, which allows access from an internal LAN or access from Internet/Extranet. Program updates are automatic for both the Server Linx and Customer Linx so that the user does not need to update the versions of each installation.