2 5-01-90 02 mms functional specification r01
Post on 08-Nov-2014
26 Views
Preview:
TRANSCRIPT
Owner
P. T. CENTRAL JAVA POWER
Employer
Project
TANJUNG JATI ‘B’ COAL-FIRED POWER STATION UNIT 3 & 4 2 x 660MW(NET)
Document Title :
MMS FUNCTIONAL SPECIFICATION
Document No. : Owner's Document No. : B-MMS-I-TS-7657 REV 1 TOSHIBA’s Document No. : A7523-E24-SP-002 REV 1
Date Revision Prepared by Reviewed by Issued by TO Purpose Status
SC For Information INF 2010/06/30 0 M.Koishi Y.Fushimi T.Sato
- - -
SC For Information ABT 2011/09/20 1 WC Tan Y.Fushimi M.Takashima
- - -
Submitted By :
LOT 2
AS BUILT
File:
Copyright © 2010 Chiyoda Advanced Solutions Corporation. All Rights Reserved.
The copyrighted works contained in this document should not be copied, reproduced, varied, modified,
distributed, performed and displayed in any form without the written permission of the copyright owner.
1 Issue for AS BUILT K.Y. Y.Y. K.S. Sep.15,‟11
Rev. Revision reason for issue description Revised Checked Approved Date
Revisions
Client :TOSHIBA CORPORATION Approved K.S.
Project :Tanjung Jati „B‟ Coal-Fired Power Station Units 3 & 4 Checked Y.Y.
Job No. :A7523 Prepared K.Y.
Project Doc. No. :A7523-E24-SP-002 Date June 30, 2010
P. T. CENTRAL JAVA POWER
TANJUNG JATI ‘B’ COAL-FIRED POWER STATION
UNITS 3 & 4 2 x 660MW(NET)
Rev 1
B - M M S - I - T S - 7 6 5 7
MMS Functional Specification
AS BUILT
P 1/46
A7523-E24-SP-002R1.doc
1
TABLE OF CONTENTS 1 INTRODUCTION ............................................................................................................................... 2 2 FUNCTIONAL DESCRIPTION ............................................................................................................ 2
2.1 Maximo Modules .......................................................................................................................................... 2 2.2 Assets Module .............................................................................................................................................. 2
2.2.1 Assets Application .................................................................................................................................................. 3
2.2.2 Locations Application ............................................................................................................................................. 4
2.2.3 Meters Application ................................................................................................................................................. 5
2.2.4 Meter Groups Application ....................................................................................................................................... 5
2.2.5 Condition Monitoring Application ........................................................................................................................... 6
2.2.6 Failure Codes Application ....................................................................................................................................... 7 2.3 Planning Module ........................................................................................................................................... 8
2.3.1 Job Plans Application ............................................................................................................................................. 8
2.3.2 Routes Application ................................................................................................................................................. 9 2.4 Safety Sub Module ..................................................................................................................................... 10
2.4.1 Hazards Application ............................................................................................................................................. 10
2.4.2 Precautions Application ........................................................................................................................................ 10
2.4.3 Lock Out / Tag Out Application ............................................................................................................................ 10
2.4.4 Safety Plans Application ....................................................................................................................................... 10 2.5 Preventive Maintenance Module ................................................................................................................. 11
2.5.1 Preventive Maintenance Application ..................................................................................................................... 11
2.5.2 Master PM Application ......................................................................................................................................... 11 2.6 Work Orders Module .................................................................................................................................. 12
2.6.1 Work Oder Tracking Application .......................................................................................................................... 12
2.6.2 Labor Reporting Application ................................................................................................................................. 13
2.6.3 Quick Reporting Application ................................................................................................................................. 13
2.6.4 Activities And Tasks Application ........................................................................................................................... 13
2.6.5 Assignment Manager Application ......................................................................................................................... 14
2.6.6 Service Requests Application ............................................................................................................................... 14 2.7 Self Service Module .................................................................................................................................... 15 2.8 Service Requests Sub Module .................................................................................................................... 15
2.8.1 Create Service Request Application ...................................................................................................................... 15
2.8.2 View Service Request Application ........................................................................................................................ 16 2.9 Desktop Requisition Sub Module ................................................................................................................ 17
2.9.1 Create Requisition Application ............................................................................................................................. 17
2.9.2 View Requisition Application ................................................................................................................................ 17
2.9.3 View Templates Application ................................................................................................................................. 18
2.9.4 View Drafts Application ........................................................................................................................................ 18 2.10 Inventory Module ....................................................................................................................................... 19
2.10.1 Item Master Application ....................................................................................................................................... 19
2.10.2 Service Items Application .................................................................................................................................... 20
2.10.3 Tools Application ................................................................................................................................................. 20
2.10.4 Stocked Tools Application .................................................................................................................................... 20
2.10.5 Inventory Application ........................................................................................................................................... 20
2.10.6 Issue and Transfer Application ............................................................................................................................ 21
P 2/46
A7523-E24-SP-002R1.doc
2
2.10.7 Condition Codes Application ................................................................................................................................ 21
2.10.8 Storerooms Application ........................................................................................................................................ 21 2.11 Purchasing Module ..................................................................................................................................... 22
2.11.1 Purchase Requisitions Application ........................................................................................................................ 22
2.11.2 Purchase Orders Application ................................................................................................................................ 23
2.11.3 Receiving Application ........................................................................................................................................... 24
2.11.4 Invoices Application ............................................................................................................................................. 24
2.11.5 Request for Quotations Application ...................................................................................................................... 25
2.11.6 Companies Application ......................................................................................................................................... 26
2.11.7 Company Master Application................................................................................................................................ 26
2.11.8 Terms and Conditions Application ........................................................................................................................ 26 2.12 Change Module .......................................................................................................................................... 27 2.13 Financial Module ........................................................................................................................................ 27
2.13.1 Currency Codes Application ................................................................................................................................. 27
2.13.2 Exchange Rates Application ................................................................................................................................. 28
2.13.3 Chart of Accounts Application .............................................................................................................................. 28
2.13.4 Cost Management Application .............................................................................................................................. 28 2.14 Resources Sub Module ............................................................................................................................... 29
2.14.1 People Application ............................................................................................................................................... 29
2.14.2 Person Group Application..................................................................................................................................... 30
2.14.3 Crafts Application ................................................................................................................................................ 30
2.14.4 Labor Application ................................................................................................................................................. 31
2.14.5 Qualifications Application ..................................................................................................................................... 31 2.15 Platform Configuration Sub Module ........................................................................................................... 32
2.15.1 Actions Application .............................................................................................................................................. 33
2.15.2 Roles Application ................................................................................................................................................. 33
2.15.3 Communication Templates Application ................................................................................................................ 33
2.15.4 Application Designer Application .......................................................................................................................... 33
2.15.5 Database Configuration Application ..................................................................................................................... 33
2.15.6 Escalations Application ........................................................................................................................................ 33
2.15.7 Cron Task Setup Application ................................................................................................................................ 33
2.15.8 Domains Application ............................................................................................................................................ 33
2.15.9 Logging Application ............................................................................................................................................. 34
2.15.10 System Properties Application .............................................................................................................................. 34
2.15.11 Web Services Application ..................................................................................................................................... 34
2.15.12 Workflow Administrator Application ..................................................................................................................... 34
2.15.13 Workflow Designer Application ............................................................................................................................ 34
2.15.14 E-mail Listener Application ................................................................................................................................... 34
2.15.15 Launch in Context Application .............................................................................................................................. 34
2.15.16 Object Structures Application ............................................................................................................................... 34 2.16 Administration Module ............................................................................................................................... 35
2.16.1 Organizations Application .................................................................................................................................... 35
2.16.2 Classifications Application .................................................................................................................................... 36
2.16.3 Bulletin Board Application .................................................................................................................................... 36
2.16.4 Communication Templates Application ................................................................................................................ 37
2.16.5 Calendars Application .......................................................................................................................................... 37
2.16.6 Sets Application ................................................................................................................................................... 37
P 3/46
A7523-E24-SP-002R1.doc
3
2.16.7 Work View Application ......................................................................................................................................... 38
2.16.8 Conditional Expression Manager Application ........................................................................................................ 38 2.17 Security Module ......................................................................................................................................... 39
2.17.1 Security Groups Application ................................................................................................................................. 39
2.17.2 Users Application ................................................................................................................................................. 39 2.18 Reporting Module ....................................................................................................................................... 40
2.18.1 KPI Manager Application ...................................................................................................................................... 40
2.18.2 Report Administration Application ........................................................................................................................ 40 2.19 External Interface - RFID ........................................................................................................................... 41
2.19.1 Automatic Processing .......................................................................................................................................... 41
2.19.2 Manual Processing ............................................................................................................................................... 41 2.20 External Interface - DCS ............................................................................................................................ 43
P 4/46
A7523-E24-SP-002R1.doc
2
1 INTRODUCTION Purpose of this document is to provide functional details of the Computerized Maintenance
Management System (CMMS) for Tanjung Jati „B‟ Coal-Fired Power Station Units 3&4.
2 FUNCTIONAL DESCRIPTION IBM Maximo Asset Management (hereafter Maximo) is an integrated productivity tool and database
to achieve maximum efficiency in asset management by managing all of asset types on a single software platform.
2.1 MAXIMO MODULES
Maximo is composed of modules that in turn contain applications or sub-applications. The key management modules are:
Asset Management Work Management
Service Management Materials Management
Procurement Management
2.2 ASSETS MODULE The Assets module is used to manage all the assets that have been purchased, and control them
through their entire asset life cycle.
To support maintenance of assets, the Assets module has the following applications:
ASSETS
APPLICATION DESCRIPTION
Assets
Store asset numbers and corresponding information such as parent, location, vendor, up and down status, and maintenance costs for each
asset.
Locations Enter and track locations for assets, and organize these locations into logical
hierarchical systems.
Meters Add or modify meter definitions. Meter definitions include names for the meters as well as sets of attributes that describe the meters.
Meter Groups Define a logical grouping of meters to exist in a meter group. Meter groups
represent a collection of meters that are used together multiple times.
Condition
Monitoring
Define unlimited measurement points for assets, and specify alarm limits and associated work to be performed after reaching those limits. Create and
view measurement-point records to define acceptable meter readings for a characteristic or gauge type of meter on an asset or location.
Failure Codes Build and display failure hierarchies, which help you construct accurate histories of the failures that affect your assets and operating locations.
P 5/46
A7523-E24-SP-002R1.doc
3
2.2.1 ASSETS APPLICATION
Screen of Assets Application
The Assets application is responsible for the creation and maintenance of assets and an asset‟s
related information such as costs, parent, statuses, location, vendor, maintenance, and meters. The Assets application enables the user to be able to create the asset hierarchy and the list of
locations, such as sites, buildings and subassemblies.
Assets application has following tabs:
List, which is where you can search for Assets.
Asset, which is for assets maintenance such as create, update, and delete. Spare Parts, which is to create asset hierarchy and all subparts of it.
Safety, which is for maintenance of safety records of an asset.
Meters, which is to track, insert, consult data related to meter life-to-date of an asset. Specifications, which is to maintenance of specification of an asset related to Classifications
application.
P 6/46
A7523-E24-SP-002R1.doc
4
2.2.2 LOCATIONS APPLICATION
Screen of Locations application
The Locations application generally defines as a place where assets are operated, stored, or repaired. Typically, locations are defined as a means of tracking assets, but may define a location as
any facility (or portion of a facility) for which you want to create a maintenance record.
The Locations application is to add, view, modify, and delete location records for assets, and
organize these locations into logical hierarchical or network systems. Use systems of locations for specifying the location for assets.
Asset records provide the groundwork for gathering and tracking valuable information about the
history of assets, including asset performance at specific sites, and as an asset is moved from
location to location. When you organize your locations into systems, you can quickly find a location and then identify the assets at a specific location.
The followings are common terms of location hierarchies:
Hierarchy is any system of places ranked one above another. Each parent location can have many child locations, but each child location can have only one parent location.
Location is typically a place where assets operate, but includes any building, place, or position that contains assets, or where maintenance work might have to be performed.
Network is any system of interconnected locations. Unlike hierarchies, in a network each
location can have multiple parents and children. Operating location is the place where equipment operates.
Primary system is the default hierarchy of locations. Each site is allowed to have only one primary system. Your primary system must be hierarchical; that is, there must be a single
top-level location that is the parent of all other locations in the system. If assets in different locations are part of an asset hierarchy, their locations must exist in the primary system.
Site is a work location, such as a plant or facility. A site belongs to a single organization.
P 7/46
A7523-E24-SP-002R1.doc
5
System is a grouping of locations, organized into either hierarchical or network relationships. A
hierarchical system could define location relationships of a plant, having a plant site as a parent to plant buildings, which are parents of sub-locations within the building areas.
A network system could define the location relationships of a system of pipes or ducts, where certain locations feed back to others.
2.2.3 METERS APPLICATION
The Meters application is to add or modify meter definitions including the names for the meters and the sets of attributes that describe the meters. You define the meters whose readings you can use
to track the performance of an asset or a location. An asset or location can have multiple meters associated with it.
The following types of meters can be defined: Continuous meters are cumulative and tend to measure consumption or accumulation. They
include meters that track such things as miles, hours, engine starts, pieces produced, or fuel consumed.
Gauge meters show a range of values such as fuel levels, temperature, pressure, noise level or, oil level. Gauge meters can be used to perform condition monitoring on Assets or Locations.
Characteristic meters are observational in nature and have a list of possible values. They are
used to track things such as noise level, vibration level, clarity, or color. Characteristic meters can be used to perform condition monitoring on Assets or Locations.
2.2.4 METER GROUPS APPLICATION The Meter Group application is to define a logical grouping of meters. Meter groups represent a
collection of meters that are used together multiple times.
P 8/46
A7523-E24-SP-002R1.doc
6
2.2.5 CONDITION MONITORING APPLICATION
Screen of Condition Monitoring application
The Condition Monitoring application is to define unlimited measurement points for assets, and to
specify alarm limits and associated work to be performed after reaching those limits. You can also create and view measurement-point records to define acceptable meter readings for a
“characteristic” or “gauge” type of meter on an asset or location. When the meter reading of an asset or location is outside acceptable limits, you can generate
preventive maintenance work orders or a work order with a specific job plan to address the
problem. Each measurement point is unique. You can compare similar measurement points on different
assets or locations using meter readings.
P 9/46
A7523-E24-SP-002R1.doc
7
2.2.6 FAILURE CODES APPLICATION
Screen of Failure Codes application
The Failure Codes application is to build and display failure hierarchies, which help you construct accurate histories of the failures that affect the assets and operating locations.
A failure code is an element of a failure hierarchy. A failure hierarchy consists of Problems, Causes, and Remedies. This hierarchy helps you construct accurate histories of the failures that affect your
assets and operating locations. You can also use failure hierarchies to record the different solutions
to failures. An individual failure code can be used at more than one level of a failure hierarchy.
P 10/46
A7523-E24-SP-002R1.doc
8
2.3 PLANNING MODULE The Planning module is to plan how work should be performed. The Planning module comprises the
following applications and sub-module:
PLANNING
APPLICATION DESCRIPTION
Job Plans Create a detailed description of how a job is to be performed.
Routes List related work assets that are considered “stops” along an inspection or maintenance route.
2.3.1 JOB PLANS APPLICATION
Screen of Job Plans application
The Job Plans application is to create a detailed description of how a job is to be performed.
The job plans can be created using a different template for each type of job, including preventive maintenance, repairs, inspections, and other tasks.
The job plan description can include:
the steps that must be performed to complete the work the number of workers needed to complete the work and the job skills they must have
the supplies and parts that will be needed the services required to complete the work
the tools that must be available to complete the work
After a job plan is created, it can be used to plan worker schedules, inventory stocks, and budgets.
A job plan can be applied to an unlimited number of work records. After you apply a job plan to a work record, its resource estimates and tasks are copied to the work record.
P 11/46
A7523-E24-SP-002R1.doc
9
2.3.2 ROUTES APPLICATION
Screen of Routes application
The Route application is to list related work assets that are considered “stops” along an inspection or maintenance route.
You can apply a route to a work order to create child work orders for each location or asset identifier listed on the route. You can also associate a route with a PM record. When you generate a work
order for the PM, you also generate child work orders for each location or asset identifier listed on
the route.
P 12/46
A7523-E24-SP-002R1.doc
10
2.4 SAFETY SUB MODULE The applications in the Safety sub module (within the Planning module) are to inform workers of
potential dangers in their work environment and to provide information to protect workers from those dangers. The hazards, precautions, and procedures that you define in these applications can
apply to assets, work locations, or both. You associate the records that you create in these
applications with Asset, Location, PM (Preventive Maintenance), and Work Order records.
The Safety sub-module comprises following applications:
Safety
APPLICATION DESCRIPTION
Hazards Define hazards that exist in the workplace and related safety precautions.
Precautions Define safety precautions to prevent hazards in the workplace.
Lock Out/Tag Out Create a detailed description of how to take work assets out of service or how to place them back in service, to ensure a safe work environment.
Safety Plans Create a detailed plan of how to safely service assets or locations.
2.4.1 HAZARDS APPLICATION
The Hazards application is to define hazards that exist in the workplace and related safety
precautions.
2.4.2 PRECAUTIONS APPLICATION
The Precautions application is to define safety precautions to prevent hazards in the workplace. You can associate these safety precautions with workplace hazards in the Hazards application.
2.4.3 LOCK OUT / TAG OUT APPLICATION The Lock out / Tag out application is to create a detailed description of how to take work assets out
of service or how to place them back in service, to ensure a safe work environment.
You create a tag out procedure to eliminate a defined hazard on a specific asset or at a specific location. To create a tag out procedure, you describe the lock out tasks needed to accomplish the
tag out.
2.4.4 SAFETY PLANS APPLICATION
The Safety Plans application is to create a detailed plan of how to safely service assets or locations.
Safety procedures can be either generic safety plans for use on all work assets or locations, or specific to a particular work asset or location.
P 13/46
A7523-E24-SP-002R1.doc
11
2.5 PREVENTIVE MAINTENANCE MODULE The Preventive Maintenance module is to manage the work performed on a regular schedule in
order to keep assets running efficiently. The applications in the Preventive Maintenance module can help you to plan and budget for regular maintenance work by planning the labor, material, service,
and tool needs of your regularly scheduled maintenance and inspection work orders.
The Preventive Maintenance module comprises the following applications:
PREVENTIVE MAINTENANCE
APPLICATION DESCRIPTION
Preventive Maintenance
Create, modify, and view preventive maintenance plans for work assets. PM records are templates for work orders or for other PMs.
Master PM Create and modify master PMs, which are templates for other PM records.
2.5.1 PREVENTIVE MAINTENANCE APPLICATION
Screen of Preventive Maintenance application
The Preventive Maintenance application is to create and modify master PMs, which are templates for other PM records.
On a PM record, you schedule job plans to be performed for preventive maintenance work, and then
the system generates work orders from the PM. You can also group PMs into hierarchies that model your asset hierarchies and generate sequenced
work order hierarchies.
2.5.2 MASTER PM APPLICATION
The Master PM application is to create and modify master PMs, which are templates for other PM (Preventive Maintenance) records.
A master PM does not generate work orders like other PMs. Instead, it is used as a template from
which to generate other PMs, called associated PMs. Associated PMs are managed in the Preventive Maintenance application.
P 14/46
A7523-E24-SP-002R1.doc
12
2.6 WORK ORDERS MODULE A work order is a request for work to be performed. The work orders module is to track the work
that has been performed in the past, and future work that is being planned. The information that is contained on a work order includes the tasks that were performed; the labor hours, services,
materials, and tools required to do the work, the assets worked on, and the locations where the
work was performed.
The Work Orders module comprises the following applications:
WORK ORDERS
APPLICATION DESCRIPTION
Work Order Tracking
Plan, review, and approve work orders for assets and locations.
Labor Reporting Report the type and total number of hours of work that was performed by external contractors or internal employees.
Quick Reporting Report work on open work orders or small jobs.
Activities and
Tasks
Plan, review, and manage activities that can initiate the maintenance process and create a historical record of work being performed.
Assignment
Manager
Dispatch urgent work and schedule labor to planned work requirements.
Service Requests Create, view, and resolve service requests from clients.
2.6.1 WORK ODER TRACKING APPLICATION
Screen of Work Order Tracking application
P 15/46
A7523-E24-SP-002R1.doc
13
The Work Order Tracking application is to create, review, approve, and manage work orders for
work on assets and locations. A work order is a request for work to be performed. Using this application, you can specify the tasks that need to be accomplished, and the labor,
materials, services, and tools needed to complete the work.
2.6.2 LABOR REPORTING APPLICATION
Use to report the type and total number of hours of work that were performed by external contractors or internal employees. You can enter labor information by work order, labor ("timecard"
reporting), ticket, or contract/vendor.
2.6.3 QUICK REPORTING APPLICATION
Screen of Quick Reporting application
Report work on open work orders or small jobs. You can plan, review, and approve work orders (created in other applications) for assets and locations.
When you create a work order, you initiate the maintenance process and create a historical record of the work that is being performed. You can capture this work using Quick Reporting.
2.6.4 ACTIVITIES AND TASKS APPLICATION The Activities and Tasks application is accessible from several different modules.
P 16/46
A7523-E24-SP-002R1.doc
14
2.6.5 ASSIGNMENT MANAGER APPLICATION The Assignment Manager application is to dispatch urgent work and schedule labor to planned work
requirements. You can view work order assignments and their craft, skill level, vendor, contract, and organization
requirements; dispatch labor according to work priority, or view labor and schedule work according
to labor availability.
2.6.6 SERVICE REQUESTS APPLICATION
Screen of Service Requests application
The Service Requests application is to create, view, and resolve service requests from customers.
The purpose of a service request can be to resolve an issue, obtain new service, obtain information, or change a current service.
P 17/46
A7523-E24-SP-002R1.doc
15
2.7 SELF SERVICE MODULE (NOT IN USE IN THIS PROJECT) Self-Service users (with proper permissions) can register themselves in the system and use the
applications in the Self-Service sub-modules (Desktop Requisitions and Service Requests) to create records without the assistance of an administrator or a service desk agent. See each sub-module for
a description of its applications.
2.8 SERVICE REQUESTS SUB MODULE
As a self-service user, you use the applications in the Service Requests sub-module (within the Self Service module) to create and view a service request for equipment repair or configuration, and to
request, and search for information. You can choose a template to best suit your specific request type, and you can view existing
requests and drafts. The resulting requests (tickets) can be viewed and processed by a service desk agent using the Service Request application in the Service Desk module.
The Service Requests sub-module comprises these applications:
SELF SERVICE - Service Request (Sub Module)
APPLICATION DESCRIPTION
Create Service Request
Self-service users use this application to create new service requests.
View Service
Request
Self-service users can view existing service requests.
2.8.1 CREATE SERVICE REQUEST APPLICATION
Screen of Create Service Request application
The Service Request application is to create new service requests for a repair or a change to an
asset. You can request the service for yourself or on behalf of another party. You can attach
documents or Web pages to the request.
P 18/46
A7523-E24-SP-002R1.doc
16
2.8.2 VIEW SERVICE REQUEST APPLICATION The View Service Request application is to view existing service requests.
You can view and print details for a service request and add or view attachments, such as documents or Web pages.
P 19/46
A7523-E24-SP-002R1.doc
17
2.9 DESKTOP REQUISITION SUB MODULE (NOT IN USE IN THIS PROJECT) As a self-service user, you use the applications in the Desktop Requisitions sub-module (within the
Self Service module) to create and view purchase requisitions. You also can use the applications to create template requisitions for repeat orders, create a list of favorite items that you order
frequently; view open, draft, and template requisitions, and check the status of your order.
The Desktop Requisitions sub-module comprises the following applications:
SELF SERVICE – Desktop Requisition (Sub Module)
APPLICATION DESCRIPTION
Create Requisition Self-service users create new purchase requests.
View Requisition Self-service users view purchase requests.
View Templates Administrative users design purchase requests from existing templates.
View Drafts Self-service users can view draft purchase requests.
2.9.1 CREATE REQUISITION APPLICATION
Screen of Create Requisition application
The Create Requisition application is to create and submit a desktop requisition to purchase the items from either an internal source, such as a company storeroom, or from an external vendor.
The desktop requisition will complete using a three-step process.
2.9.2 VIEW REQUISITION APPLICATION
The View Requisition application is to search for, view, and change the status of your existing purchase requisitions.
You can view requisition details, history, and workflow information using the subtabs available in
the application. You can also create a template of the requisition that you can use to simplify the process of creating multiple new requisitions.
P 20/46
A7523-E24-SP-002R1.doc
18
2.9.3 VIEW TEMPLATES APPLICATION The View Templates application is to view a requisition that was saved as a template. A template
requisition is a requisition that you save to use repeatedly in the future, and it typically contains standard shipping and charge information plus line item information. You can edit the requisition
template and use it to create new requisitions.
2.9.4 VIEW DRAFTS APPLICATION
The View Drafts application is to view a requisition that was previously saved as a draft during the
create requisition process.
P 21/46
A7523-E24-SP-002R1.doc
19
2.10 INVENTORY MODULE The applications in the Inventory module are to manage spare parts inventory.
The Inventory module comprises the following applications:
INVENTORY
APPLICATION DESCRIPTION
Item Master Define items that stocked in your Storerooms. You group these items in an item set, which can then be shared by the organizations using that item set.
Service Items Define and manage purchased services.
Tools Manage information about the tools used to perform work. Tools are
typically non-consumable items for which you charge an hourly rate.
Stocked Tools Manage existing tools in Storerooms.
Inventory Enter, display, and update information about each inventory item.
Issues and
Transfers
Issue or transfer items from Storerooms, or return items to Storerooms.
Condition Codes Create and maintain a master list of condition codes for a particular item
set.
Storerooms Add and maintain information about Storeroom locations, as well as view
the items stocked within a Storeroom.
2.10.1 ITEM MASTER APPLICATION
Screen of Item Master application
The Item Master application is to define items that will be stocked in storerooms. You group these
items in an item set, which can then be shared by the organizations using that item set.
P 22/46
A7523-E24-SP-002R1.doc
20
2.10.2 SERVICE ITEMS APPLICATION The Service Items application is to define and manage purchased services by creating service item
records and maintaining a list of vendors that supply the service item.
2.10.3 TOOLS APPLICATION
The Tools application is to manage information about the tools used to perform work. Tools are typically non-consumable items for which you charge an hourly rate for their use. Some examples of
tools include air compressors, nail guns, calibration equipment, and heavy equipment such as
cranes and excavators.
2.10.4 STOCKED TOOLS APPLICATION
The Stocked Tools application is to manage existing tools in storerooms. (To create new tool records, you must use the Tools application.)
2.10.5 INVENTORY APPLICATION
Screen of Inventory application
The Inventory application is to create and manage information about items in inventory (stocked,
non-stocked, and special order) and to know when your stock falls below a specified level so that
you can reorder. You can track item balances, and vendors who supply an item, down to the bin and lot level for each storeroom.
P 23/46
A7523-E24-SP-002R1.doc
21
2.10.6 ISSUE AND TRANSFER APPLICATION
Screen of Issue and Transfer application
The Issue and Transfer application is to issue or transfer items from storerooms, or to return items
to storerooms.
2.10.7 CONDITION CODES APPLICATION
The Condition Codes application is to create and maintain a master list of condition codes for a particular item set.
2.10.8 STOREROOMS APPLICATION The Storerooms application is to add and maintain information about storeroom locations, view
items that are stocked in a storeroom, and define the GL account codes to be associated with a
storeroom.
A storeroom is a location that contains inventory items. Storerooms have general ledger account codes associated with them to help track inventory costs.
P 24/46
A7523-E24-SP-002R1.doc
22
2.11 PURCHASING MODULE The applications in the Purchasing module are to manage the purchasing process, including
obtaining requests for quotations (RFQs), purchasing the materials and services, and then receiving and invoicing them. The applications also help you to maintain information about the companies
from which you purchase, and to integrate legal terms and conditions into the purchasing process.
The Purchasing module comprises the following applications:
PURCHASING
APPLICATION DESCRIPTION
Purchase
Requisitions
Ask the purchasing department to order materials or services.
Purchase Orders Purchase materials or services from an internal supplier or an external
vendor.
Receiving Receive materials into inventory and record the receipt of services.
Invoices Record invoices and match them against purchase orders and receipts for approval.
Request for Quotations
Request and manage vendor quotations.
Companies Manage data about manufacturers, vendors, and other companies that do
business with you.
Company Master Create company master records that belong to a particular company set.
Terms and
Conditions
Create and maintain a library of terms and conditions that can be added to a
purchasing document or contract.
2.11.1 PURCHASE REQUISITIONS APPLICATION
Screen of Purchase Requisition application
The Purchase Requisition application is to ask the purchasing department to order materials and
services. A purchase requisition (PR) is a written request issued internally to a purchasing department to order items or services.
P 25/46
A7523-E24-SP-002R1.doc
23
2.11.2 PURCHASE ORDERS APPLICATION
Screen of Purchase Order application
The Purchase Order application is to purchase materials and services from an external supplier or an
external vendor.
You can create POs in three ways:
Directly from the Purchase Orders application From purchase requisitions (PRs)
From requests for quotations (RFQs)
P 26/46
A7523-E24-SP-002R1.doc
24
2.11.3 RECEIVING APPLICATION
Screen of Receiving application
The Receiving application is to receive materials into inventory and record the receipt of services. When you receive items, the system increases balances in the Inventory application or issues direct
issue items directly to an asset, location, or work order.
2.11.4 INVOICES APPLICATION
Screen of Invoices application
The Invoice application is to record invoices (and debit and credit notes) from vendors and match
them against purchase orders and receipts for approval. An invoice is a bill from a vendor for delivered products or services.
P 27/46
A7523-E24-SP-002R1.doc
25
2.11.5 REQUEST FOR QUOTATIONS APPLICATION
Screen of Request for Quotations application
The Quotations application is to request and manage vendor quotations. A request for quotation
(RFQ) is a request for a price quote that you send out to one or more potential suppliers.
P 28/46
A7523-E24-SP-002R1.doc
26
2.11.6 COMPANIES APPLICATION
Screen of Companies application
The Companies application is to manage data about vendors, manufacturers, and other companies
with whom you do business.
2.11.7 COMPANY MASTER APPLICATION
Screen of Company Master application
The Company Master application is to create company master records that belong to a particular company set.
Company master records contain information pertaining to companies such as the default contact
person, purchasing, e-commerce, and payment details of the company.
2.11.8 TERMS AND CONDITIONS APPLICATION The Terms and Conditions application is to create and maintain a library of terms and conditions
that can be added to a purchasing document or contract. These terms can contain information such
as liability concerns, shipping and handling details, or delivery time expectations.
P 29/46
A7523-E24-SP-002R1.doc
27
2.12 CHANGE MODULE The Change module contains the Activities and Tasks application, which you use to plan, review,
and manage activities and tasks. When you create an activity, you initiate the work process and create a historical record of work being performed.
CHANGE
APPLICATION DESCRIPTION
Activities and
Tasks
Plan, review, and manage activities and tasks. When you create an activity, you initiate the work process and create a historical record of work being
performed.
2.13 FINANCIAL MODULE
The applications in the Financial module are to define and manage currency codes, exchange rates, general ledger accounts and resource codes, and to track project management costs.
The Financial module comprises the following applications:
FINANCIAL
APPLICATION DESCRIPTION
Currency Codes Define currency codes and specify which codes can be used in Maximo Asset Management.
Exchange Rates Set up exchange rates for converting currencies.
Chart of Accounts Establish general ledger account fields with definitions equivalent to those used with the rest of your financial data processing system.
Cost Management Generate project cost information to track the financial resources that are
required to complete a project and manage budgets more effectively.
2.13.1 CURRENCY CODES APPLICATION
Screen of Currency Codes application
The Currency Codes application is to define currency codes and to specify which codes can be used
in the system. A currency code is a short, user-defined value that you create to represent a currency, for example, IDR for the Indonesian Rupiah.
P 30/46
A7523-E24-SP-002R1.doc
28
2.13.2 EXCHANGE RATES APPLICATION
Screen of Exchange Rate application
The Exchange Rate application is to set up exchange rates used for converting currencies.
The application stores exchange rates at the organization level. Therefore, each organization
defines and maintains its own exchange rates.
2.13.3 CHART OF ACCOUNTS APPLICATION
Screen of Chart of Accounts application
The Accounts application is to establish general ledger account fields in the product that are equivalent to the definitions that are used in the rest of your financial data processing system.
2.13.4 COST MANAGEMENT APPLICATION The Cost Management application is to generate project cost information to track the financial
resources required to complete a project and manage budgets more effectively. Use this application in conjunction with an external project costing system.
P 31/46
A7523-E24-SP-002R1.doc
29
2.14 RESOURCES SUB MODULE The applications in the Resources sub-module (within the Administration module) are to create
records about the people in your workforce. The people whom you document can include internal and external workers, and other people whose
names or IDs might be listed on other records.
The Resources sub-module comprises five applications:
RESOURCES
APPLICATION DESCRIPTION
People Maintain records of people.
Person Group Maintain person groups. A person group consists of people who may or may not be workers.
Crafts Define and maintain craft records.
Labor Define and maintain labor records.
Qualifications Create qualifications and certification requirements for qualifications.
2.14.1 PEOPLE APPLICATION
Screen of People application
The People application is to create and maintain records about people. This application stores
personal and official information about individuals, such as users, laborers, asset owners, supervisors, and individuals who receive Workflow notifications.
P 32/46
A7523-E24-SP-002R1.doc
30
2.14.2 PERSON GROUP APPLICATION
Screen of Person Group application
The Person Group application is to create and maintain person groups. A person group consists of people who might or might not be workers.
2.14.3 CRAFTS APPLICATION
Screen of Crafts application
The Crafts application is to define and maintain craft records. The craft code usually reflects the
type of work done by employees and contractors. The Crafts application is also used to define skill levels, standard rates, and premium pay codes for
crafts.
P 33/46
A7523-E24-SP-002R1.doc
31
2.14.4 LABOR APPLICATION
Screen of Labor application
The Labor application is to define and maintain labor records. You can provide personal and work
related information about labors, who could be employees or a contractors.
2.14.5 QUALIFICATIONS APPLICATION
The Qualifications application is to manage the qualifications of the laborers in your workforce, and the certification requirements for each qualification. Using a labor‟s record, you can associate each
labor with a qualification. You can also view the qualifications associated with a particular labor record and renew and change the status of their qualifications.
P 34/46
A7523-E24-SP-002R1.doc
32
2.15 PLATFORM CONFIGURATION SUB MODULE
The applications in the Platform Configuration sub-module (within the System Configuration
module) are to configure many pieces needed in the system to build up.
The Platform Configuration sub-module comprises the following applications:
SYSTEM CONFIGURATION – Platform Configuration
APPLICATION DESCRIPTION
Actions Manage the administrative functions of creating actions and action groups
within Escalations.
Roles Manage roles within Maximo Asset Management.
Communication
Templates
Create and manage generic communication templates that users can leverage to standardize frequently used e-mail communications (also known
as notifications).
Database
Configuration
Create or modify the objects and attributes used by Maximo Asset Management applications.
Application
Designer
Create new applications (clones and custom applications) or tailor the pages
of existing applications.
Escalations
Automatically monitor critical processes across your enterprise. The primary goal of Escalation Management is to ensure that critical tasks are completed
on time, such as those defined in service-level agreements (SLAs).
Cron Task Setup Manage cron tasks. Cron tasks are behind-the-scene jobs set to run automatically and on a fixed schedule.
Domains Maintain lists of defined values that appear in drop-down lists (sometimes
referred to as value lists).
Logging Manage log settings and configure log files.
System Properties Manage system properties and their values used by various product components.
Web Services
Create, modify, and delete Web services. You also can generate schema
and Web Service Description Language (WSDL) files for any Web service that you deploy. External applications can use Web services to query or to
send transactions to the Integration Framework.
Workflow
Administrator
View and modify assignments within the workflow, escalation, and service-level agreement processes.
Workflow Designer Use this graphical application to create a series of decision paths for records to flow through, called workflow process.
E-mail Listener
Receive and process incoming e-mail messages. This application can monitor multiple e-mail accounts to retrieve messages, and it supports
embedded and normal message attachments.
Launch in Context Create and manage launch entries that open, in the same or a different browser session, an application that is external to the system.
Object Structures
Create, view, modify, and manage the processing logic of an object structure. An object structure is the common data layer that the Integration
Framework uses for all outbound and inbound application data processing. An object structure consists of one or more sub-records that develops their
XML content from a particular object.
P 35/46
A7523-E24-SP-002R1.doc
33
2.15.1 ACTIONS APPLICATION The Actions application is to manage the administrative functions of creating actions and action
groups within the workflow, escalation, and service level agreement processes. Actions are scheduled events that occur when a record leaves a Workflow node.
2.15.2 ROLES APPLICATION
The Roles application is to create and manage roles, which define a function or position in a business. A role can represent a job title, such as a “department manager,” or an assigned duty,
such as a watch officer. When a role is used as part of a communication template, escalation,
service level agreement, or workflow process, it can determine the correct individuals to whom the process is routed.
2.15.3 COMMUNICATION TEMPLATES APPLICATION The Communication Templates application is to create and manage generic communication
templates that users can use to standardize frequently used e-mail communications (also known as notifications).
2.15.4 APPLICATION DESIGNER APPLICATION
The Application Designer application is to create new applications (clones and custom applications) and tailor the pages of an existing system application.
2.15.5 DATABASE CONFIGURATION APPLICATION
Use to create or modify the objects and attributes that are in the Maximo database and used by system applications. Maximo database configuration is based on objects. There is a one-to-one
correlation between an object and a table in the database. Behind the scenes, the business object fetches the columns of the corresponding table and presents them to you as attributes of the object.
2.15.6 ESCALATIONS APPLICATION The Escalation application is to automatically monitor the critical processes in your enterprise. The
primary goal of escalation management is to ensure that critical tasks, such as those defined in
service level agreements, are completed on time. You can also use escalations for events such contract expiration, a change in the status of a record (such as for invoices or contracts), or a
change in the owner of a record (such as for service requests, incidents, or problems).
2.15.7 CRON TASK SETUP APPLICATION
The Cron Task Setup application is to manage cron tasks, which are jobs that run (as background tasks) automatically and on a fixed schedule.
2.15.8 DOMAINS APPLICATION The Domains application is to define the values that appear in select value lists in some fields on the
application pages and tabs of the user interface.
P 36/46
A7523-E24-SP-002R1.doc
34
2.15.9 LOGGING APPLICATION
The Logging application is to create and manage log settings and configure the log files that contain informational, warning, or error messages about the system.
2.15.10 SYSTEM PROPERTIES APPLICATION The System Properties application is to manage system properties and their values which are used
by various product components.
2.15.11 WEB SERVICES APPLICATION
The Web Services application is to create, modify, and delete Web services which are used by
external applications to query or to send transactions to the integration framework. You also can generate schema and Web Service Description Language (WSDL) files for any Web service that you
deploy.
2.15.12 WORKFLOW ADMINISTRATOR APPLICATION
The Workflow Administrator application is to view and modify assignments within workflow, escalation, or service level agreement process.
2.15.13 WORKFLOW DESIGNER APPLICATION The Workflow Designer application is to create a series of decision paths for records to flow through,
called a workflow process graphically.
2.15.14 E-MAIL LISTENER APPLICATION
The E-Mail Listener application is to receive and process incoming e-mail messages. This application can monitor multiple e-mail accounts to retrieve messages, and it supports embedded and normal
message attachments.
2.15.15 LAUNCH IN CONTEXT APPLICATION
The Launch in Context application is accessible from several different modules.
2.15.16 OBJECT STRUCTURES APPLICATION
The Object Structures application is accessible from several different modules.
P 37/46
A7523-E24-SP-002R1.doc
35
2.16 ADMINISTRATION MODULE
The applications in the Administration module are for small system administration tasks, such as setting one parameter, and for tasks that you do often, such as creating user groups.
The Administration module comprises the following applications and sub-modules: ADMINISTRATION
APPLICATION DESCRIPTION
Organizations Set up the organizations and sites to be used within Maximo.
Classifications Create classifications and establish classification hierarchies for Items,
Assets, Locations, Work Orders, etc.
Bulletin Board Create, post, and view messages as well as broadcast information to users
of the Maximo system.
Communication
Templates
Create and manage generic communication templates that Maximo users
can leverage to standardize frequently used e-mail communications (also known as notifications).
Calendars Indicate working time for equipment, craft, and labor records for an
organization and its associated sites.
Sets Create a framework for sharing item and company (vendor) data across
multiple organizations.
Work View Make queries available for display in the Result Set portlet of a user‟s Start
Center.
Conditional Expression
Manager
Create and maintain a library of conditions. In other applications, such as Application Designer and Security Groups, you select from predefined
conditions to set up conditional behavior.
2.16.1 ORGANIZATIONS APPLICATION
Screen of Organization application
The Organization application is to set up the organizations and sites to use with the system. You must define at least one organization and one site.
P 38/46
A7523-E24-SP-002R1.doc
36
2.16.2 CLASSIFICATIONS APPLICATION
Screen of Classifications application
The Classifications application is to create classifications and establish classification hierarchies for
many objects such as Items, Assets, Locations, and Work Orders. Classifications and hierarchies help you organize your data and make it easier to find specific information.
2.16.3 BULLETIN BOARD APPLICATION
Screen of Bulletin Board application
The Bulletin Board application (within the Administration module) is to create, post, and view messages and to broadcast information to system users.
P 39/46
A7523-E24-SP-002R1.doc
37
2.16.4 COMMUNICATION TEMPLATES APPLICATION The Communication Templates application is to create and manage generic communication
templates that users can use to standardize frequently used e-mail communications (also known as notifications). You can use these standardized e-mail notifications to increase productivity and
efficiency in the Workflow and Escalation processes.
2.16.5 CALENDARS APPLICATION
Screen of Calendar application
The Calendar application is to indicate working time for equipment, craft, and labor records for an organization and its associated sites.
Calendars application defines data such as holidays, shifts, and work periods, which is used for
scheduling in other areas within the system.
2.16.6 SETS APPLICATION
The Sets application is to create a framework for sharing item and company (vendor) data across multiple organizations. The system stores both item and company master records in sets. These
sets exist above the organization level so that organizations can share the same data.
P 40/46
A7523-E24-SP-002R1.doc
38
2.16.7 WORK VIEW APPLICATION The Work View application is to make queries available for display in the Results Set portlet of a
user‟s Start Center.
2.16.8 CONDITIONAL EXPRESSION MANAGER APPLICATION
The Conditional Expression Manager application is to create and maintain a library of conditions that you, or other users, can select from when using applications, such as Application Designer and
Security Groups, to set up conditional behavior.
P 41/46
A7523-E24-SP-002R1.doc
39
2.17 SECURITY MODULE
The applications in the Security module are to implement and manage security for users and groups.
The Security module comprises the following applications: SECURITY
APPLICATION DESCRIPTION
Security Groups Grant access to sites, applications, and menu options. A user is assigned to
one or more groups to gain access to the system.
Users Add and manage Maximo users.
2.17.1 SECURITY GROUPS APPLICATION
Grant access to sites, applications, and menu options by using security privileges. You set up
security privileges by group. You use the Security Groups application to create groups. Then you can specify group privileges and restrictions for applications and options, as well as other settings.
2.17.2 USERS APPLICATION
Screen of Users application
Use to add users to the system and manage user privileges. You can perform these tasks in the Users application:
Manage user status Manage user sessions
View user security profile
Specify various user defaults, such as default insert site, storeroom, language, and general ledger accounts for purchasing.
Grant users the right to access inactive sites Specify which users can access a screen reader to assist in interacting with the system
Set system-wide security controls and new user default groups Change passwords
Create database users
P 42/46
A7523-E24-SP-002R1.doc
40
2.18 REPORTING MODULE The applications in the Reporting sub-module (within the Administration module) are to create and
view key performance indicators (KPIs), manage reports for users, and to set and view report-based security.
The Reporting sub-module comprises two applications: REPORTING
APPLICATION DESCRIPTION
KPI Manager Create key performance indicators (KPIs) to track critical performance variables over time.
Report
Administration
Create reports, generate and preview request pages, add parameters, display reports as toolbar icons, e-mail reports, or specify a schedule for
running a reports.
2.18.1 KPI MANAGER APPLICATION
Screen of KPI Manager application
The KPI Manager application is to create key performance indicators (KPIs) to track critical performance variables over time.
KPIs can be viewed either in the Start Center or directly with the KPI Manager.
2.18.2 REPORT ADMINISTRATION APPLICATION
The Report Administration application is to create reports, generate and preview request pages, add
report parameters, display reports as toolbar icons, e-mail reports, and specify a schedule for running reports. Also, use to import report design files and libraries into the Maximo Database, and
set or view report security at the group level.
P 43/46
A7523-E24-SP-002R1.doc
41
2.19 EXTERNAL INTERFACE - RFID The interface between Maximo and RFID system is implemented by utilizing Maximo Integration
Framework (MIF). This RFID Interface exports INVENTORY data from Maximo system to a XML file. The file will be stored into the specified folder of the RFID server.
This RFID Interface will export the INVENTORY data by two methods: RFID Interface
PROCESSING DESCRIPTION
Automatic On the updating event of Inventory information, Maximo Interface will publish the data to External Server (RFID Server).
Manual
Using the Maximo External Systems application‟s RFID System, INVENTORY information can be exported to External Server (RFID Server).
Optionally, user can supply condition on which data can be exported.
2.19.1 AUTOMATIC PROCESSING
This Automatic Processing task will be performed upon modifying INVENTORY information. Maximo application notifies the updating event to Publish Channel. Publish Channel store the received data
and updating event into Queue. The Cron Task will create the XML file and stores it into shared folder on the External server (RFID Server). This file contains single data record for each event.
The following transactions are automatically initiated by events in Maximo Inventory application: Create or Update or Delete event of Item Master Information
Issue Transaction Return Transaction
Transfer Transaction
Create or Update event of Receipt Transaction Adjustment Transaction
2.19.2 MANUAL PROCESSING
Screen of External Systems application
P 44/46
A7523-E24-SP-002R1.doc
42
This task can be performed using the Maximo External Systems application's RFID system. Use
Publish Channel to export desired INVENTORY data from Maximo system to a XML file. Upon clicking on Data Export button, Data search conditions dialog box displays and then user has to
enter data export condition. Then Publish Channel will fetch the data as per condition and store it in Queue. The Cron Task will create the XML file and stores it into shared folder of the External (RFID)
server.
You can export the following data using RFID interface:
Adjusted Average cost Adjusted Current balance
Inventory Information Material Information
Inventory Change Information
Issues transactions Stock Tracking
Receipts transactions Returns transactions
Transfers transactions
P 45/46
A7523-E24-SP-002R1.doc
43
2.20 EXTERNAL INTERFACE - DCS
The interface between DCS (EMC) and CMMS system is implemented via Web Services and the
Maximo Integration Framework (MIF). This DCS Interface transfers Meter reading data from OPC to
Maximo. DCS Interface utilizes the open standard OPC to communicate with OPC Servers, currently there are three OPC servers installed; Common, Unit 3 & Unit 4.
User can define schedules for frequency to push OPC data to Maximo.
Matrikon ™ Analysis Host service handles the scheduling and execution of the scheduled analyses. It executes in the background.
Screen of EMC application
Screen of Asset-Meter application
P 46/46
top related