Oracle Enterprise Asset Management Overview (eAM)

Oracle ebusiness  suite>Oracle Enterprise Assets Management (eAM) eAM Functionality
Work Requests		A Work Request serves a different function than a Work Order; it is a request for maintenance on an asset (Capital or Rebuildable Inventory). eAM enables operations and maintenance staff to report any problems with an asset. A supervisor can approve, request additional information, or reject a Work Request. A Work Request requires approval before it is generated into a Work Order. The Work Requests tab enables you to query existing, and create new Work Requests for an asset.
Work Request Statuses		Open - A Work Request is created in an Open status. Awaiting Work Order - The Work Request status changes from Open to Awaiting Work Order if the individual on the approval route has approved it. If the Auto-Approve Work Request functionality is enabled for the current organization, the status is automatically Awaiting Work Order. On Work Order - After a Work Request is associated with a Work Order, the status changes to On Work Order. Rejected - The individual on the approval route rejected the Work Request. Additional Information - If the Work Request's status is Additional Information, the originator needs to add the requested information. Complete - The Work Request status transitions to Complete when the Work Order associated with the request is completed.
eAM Work Management		The Work Order is the foundation for all maintenance organizations. Work orders define the resources and items that are needed to conduct work. They can automatically generate through the use of Preventive Maintenance Schedules, the issue of an inventoried rebuildable, breach of quality results, or manually generated as a routine Work Order. These
eAM Work Orders		Enterprise Asset Management Work Orders are created for assets and rebuildable inventory items. They are defined manually, or generated automatically based on a scheduled Activity.
Routine Work Orders		Routine Work Orders are normally created by a Planner from the Maintenance Workbench
Preventive Maintenance Work Orders		Enterprise Asset Management enables you to generate Work Orders automatically based on meter readings, runtime intervals, and calendar days. Preventive maintenance Activities reduce the probability of failure or degradation of the assets' physical conditions.Meters are entered to measure any Asset Number that needs to be measured and periodically serviced, based on the measurement.For example, a pipe may start out at 12 millimeters, but when it wears to only four millimeters, it needs to be replaced.Scheduling definitions are defined to create forecasted, scheduled Work Orders, based on meter readings.
Rebuild Work Orders		Rebuild Work Orders are created as child Work Orders.For example, a Work Order was issued for the inspection of a pump. During the pump inspection, you found that the motor, one of the components of the pump, is problematic. You have two options: You can repair and then reinstall this motor (rebuildable item), or you can replace the rebuildable item by issuing a new motor rebuildable item from inventory. If you choose to perform a material issue from inventory, the old motor rebuildable item attaches to the Work Order, automatically creating the child, rebuild Work Order number associated to the parent Work Order. In this case, the Asset Number genealogy would automatically update to identify this new item number.If you choose to repair and then reinstall the problematic motor rebuildable item, you can manually create the child rebuild Work Order for the old motor (rebuildable item).
Easy Work Orders		Easy Work Orders are unplanned Work Orders, and enable you to avoid operation and resource planning. An Activity does not default into the Work Order, based on the Asset Number/Activity association as with planned Work Orders, however, you can add an Activity to an Easy Work Order. These Work Orders are only created in Maintenance User. Work Orders can create at any status, such as Released
eAM Work Order Statuses		Draft status >  then move to  >  Released >  Complete >   and finally Closed
Draft		Infinite resource capacity scheduling of Work Orders at a Draft status may take place. You cannot charge labor, or request material for Work Orders at this status.
Released		After a Work Order is Released, you can execute a Work Order. You can charge labor, request material, and scheduling for this Work Order takes place
Unreleased		You can move an Enterprise Asset Management Work Order in Draft or Released status to Unreleased. Scheduling can take place for these Work Orders  but you cannot charge labor or request material. An Unreleased Work Order cannot be changed to a Draft status.
Pending Scheduling		If the Scheduler is enabled, the Work Order status changes to Pending Scheduling, if a status of Released is chosen. After the Scheduler process finishes running, the status changes back to Released.
Complete		A Complete status for an Enterprise Asset Management Work Order does not require any completed operations. When a Work Order is completed, you can still charge labor. You can uncomplete a Work Order; this transitions it to a Released status.
Complete - No Charges		A Complete - No Charges status for an Enterprise Asset Management Work Order does not require any completed operations. You cannot charge labor at this status. You cannot update associated asset hierarchy, work order hierarchy, material, resource, operation, cost, collection plan results, work request, and attachment information on a Work Order that is at a Complete - No Charges status.
Closed		You cannot charge any accounts after an Enterprise Asset Management Work Order is closed. If a Work Order was at a Released status at the time of closing it, you can unclose the Work Order to bring it back to a Released status. If a Work Order was at a Complete status at the time of closing it, you can unclose the Work Order to bring it back to a Complete status.
On-Hold		Enterprise Asset Management Work Orders at Released and Unreleased statuses can be put on hold. You cannot charge labor or request material for a Work Order at this status.
Cancel		You can cancel an Enterprise Asset Management Work Order at any status in its lifecycle.
Asset Shutdown Statuses		Shutdown of an asset is sometimes necessary to perform a maintenance Activity. You can create new shutdown information associated with an asset, or view existing shutdown history information already recorded to an asset. Shutdown information consists of start and end dates, Work Order numbers requiring maintenance on the asset, and specific operation sequences.
Direct Item Material Requirements		Direct Items represent items with infrequent use or criticality; they are not included in the internal catalog as stocked items. These items are considered as "one off", bought directly from a vendor for a specific Work Order and Operation. These items are delivered directly to the Shop Floor for maintenance Work Order execution. To set up Non-Stock Direct Items, access the Master Item window within Oracle Inventory, and set up the item with the Stockable check box cleared.
Parent-Child Relationship		The Parent-Child Relationship enables a network of Work Orders, which includes one top level Work Order that defines the time line of all its children Work Orders. The start and end dates of the child Work Orders are within the start and end dates of the parent Work Order. The parent Work Order dates are scheduled, while its child Work Orders automatically schedule, as well.
End to Start Dependency		You can create Work Orders with scheduling dependency relationships (including child sibling Work Orders). For example, one Work Order's scheduled start date is dependent on another Work Order's completion. With this relationship, the next Work Order cannot start until the prior Work Order is completed.
Cost Relationship		You can optionally roll a child Work Order's costs into the parent Work Order, for reporting purposes. You can perform cost roll ups on ad hoc Work Orders because the cost roll up is independent of scheduling  elationships. You can base the cost roll up, within a hierarchy, on scheduling relationships, as well. Scheduling relationships are not required to roll up costs within a hierarchy.
Follow-up Work Relationship		You can create a Work Order for a capital Asset Number or Rebuildable Item, while executing work for the asset on another Work Order. For example, a second problem with an asset is discovered while executing a Work Order. A Follow-up Work Order, associated with the original Work Order, is created for the issue.
Preventive Maintenance		eAM generates Work Orders automatically based on meter readings, runtime and/or calendar days. An example of meter-based preventive maintenance is your car's oil changes. Most car manufacturers recommend that you change your engine oil every 3,000 miles or six months, whichever comes first. To set up the above scenario, define your car's odometer as a meter. Next, associate that meter to an asset (your car), using the Asset Meter Association window. After you have associated the meter to the asset, associate the Maintenance Activity (oil change) that should occur, based on the meters you defined. This is performed via Preventive Maintenance Scheduling.
Meters		Meters are defined and associated with Asset Numbers to measure an asset or rebuildable item's usage. Examples include odometers or counters. Meters are used in Preventive Maintenance Scheduling to schedule and generate Preventive Maintenance Work Orders.
Direct Item Procurement for eAM Work Orders		Enterprise Asset Management (eAM) Direct Item Procurement enables you to order items directly to your maintenance organization Purchase requisitions and purchase orders of such items capture the Work Order for which they are required. If the Work Order is project related, then the project and task information is captured in the purchase requisition. You can procure Non-Stock and Description-based Direct Items, without accessing iProcurement, as well. To enable direct item (both supplier catalog and non-catalog items) procurement for eAM Work Orders directly from an eAM Work Order, set the PO: Enable Direct Delivery To Shop Floor profile option to Yes. You can manually create requisitions for Direct Items within iProcurement or Purchasing. If you have Oracle iProcurement installed, you can access supplier catalog items directly from an eAM Work Order. If you create a requisition within iProcurement, the Work Order and operation information generates as you proceed to checkout
eAM Direct Procurement Accounting		For all requisition or purchase order distribution lines with a destination type of Shop Floor (not related to outside processing), the amount (quantity * purchase price * exchange rate) charges to the eAM Work Order Material account.   Receiving entry (Dr:- Receiving Inspection XXX - Cr: -Accounts Payable Accrual - XXX )   Delivery - (Dr. Work Order Material XXX -  Cr. Receiving Inspection - XXX)
Outside Service Processing		Contractor services are defined as work services provided by an organization or person who is not an employee of your company. Contractors are paid for their work based on an agreed upon contract or agreement. For example, a contractor service may be a painting service. It is also important to associate the purchasing transactions, such as the requisition and purchase order, to the Work Order. Item type should be Outside processing , Check the outside processing in eAM resources.
Property Manager Integration		Property Manager can store three-level land or building hierarchies, providing a parent/child location hierarchy. eAM provides a parent/child asset hierarchy. The integration enables locations defined in Property Manager to import into eAM as Asset Numbers. The process also imports the land or building hierarchy, while respecting its current structure.
eAM Project Manufacturing		Create Project --> Associate project to Maintenance WO --> Create Requisition or Purchase Order ----> Update Commitments for projects --> Cost Collection
eAM Quality		eAM integrates with Quality, enabling you to collect quality results on your assets. If an asset is not up to the required standards, a Work Request can automatically generate
eAM Billing		After the setup tasks are complete , you  can bill third parties and customers the work performed, while maintaining an asset or servicing a customer request. Work Order Billing requires completed, billable Work Orders. First, create a Work Order that is associated with billable material, resources, and/or a billable Activity. After the Work Order is released, you can apply material and resources to it. Finally, after the Work Order is completed, the status is changed to Complete - No Charges. The Work Order is ready to bill.
Wireless  Maintenance User Workbench		Maintenance User can log on to a mobile device and view all work that is assigned to him/her. You can view today's Work Orders, overdue work, and Work Orders that you are assigned to you in the future.
Maintenance User		The Maintenance User is a maintenance person who is generally responsible for completing tasks that are assigned on a Work Order. This person reports maintenance problems using Work Requests, troubleshoots on jobs, and works on a team with other maintenance workers.
Maintenance Super User		The Maintenance Super User is generally a Maintenance Planner or Supervisor and is often defined as a "super user". A Maintenance Planner plans and schedules maintenance jobs, manages and balances work loads over time, manages preventive maintenance strategy and scheduling, manages material requirements, monitors availability, and coordinates strategies with other departments, such as Operations, Purchasing, and Inventory.
eAM Stores Issuance		Material issue to Work Orders and returns to Inventory are typical store room functions and are provided by the Stores tab. There are two activities involved in delivering material from stores to a Work Order.First, a Material Issue Request is generated to request the material to a Work Order.This process is automated upon Work Order release, by selecting a check box in the Enterprise Asset Management Parameters
One Step Issue & Two Step Issue		There are two primary methods used to issue material to a Work Order: One Step Issue and Two Step Issue. The One Step Issue method is used to issue one-off or ad hoc material to a work order; this does not involve the prior requesting of material and can execute for both planned and unplanned material. The Two Step Issue method involves two steps. The first step involves the maintenance planner or user requesting material from stores, and the second step involves the stores room person delivering the material to the Work Order
Failure Analysis		Failure Analysis enables you to track an asset failure from the time it is reported until its resolution. Statistics from your collected failure data provide you with information on why an event occurs and causes your asset failure. You can then take the necessary steps to eliminate that event.
Activity Cause Report		Use the Activity Cause Report to report on reasons for your assets' failures, reported by Department, or Asset Number. An Activity Cause is a reason for an asset's failure, for example, Preventive, Normal Wear, Rework, and Breakdown. This information enables you to understand the dynamics that affect an asset's ability to perform.
Department Actual Cost Report		Use the Department Actual Cost Report to determine the actual costs charged to an Owning Department for a specified period of time.
Work Order Cost Report		Use the Work Order Cost Report to determine the costs charged to Work Orders for a specified period of time, and optionally, a Department range.
EAM Weekly Schedule Report		Use the EAM Weekly Schedule Report to display Work Order details, by specific owning department, within your crew's calendar week's starting dates. This report includes details, such as Work Order number, status, work description, start date, operation, department, resources, instance, priority, duration, estimated completion date, and the distribution of hours on a weekly basis.
Load Production Equipment Maintenance Downtime		After establishing, you can view the resource usage (maintenance Work Orders, batches, or FPOs) emanating from production, associated with a maintainable asset. You can also use the Load Production Equipment Maintenance Downtime process to view or purge your maintenance production equipment downtime.
Maintenance Work Order Detail Report		Use the Maintenance Work Order Detail Report to view and analyze all information related to a maintenance work order. You can create a report that displays user-defined values. For example, you can view all unreleased work orders for a specified date
Material Issue Request Pick List Report		Stocked inventory items may be necessary to perform work on maintenance Work Orders. Use the Material Issue Request Pick List Report to display all reserved stock for maintenance Work Orders, so that you can easily retrieve the necessary material.

Oracle Property Overview

Oracle ebusiness  suite>Oracle Financial> Oracle Property

Oracle Property Integration with GL and Payable. 

Process flow.

 

Oracle Applications Implementations Methodology (AIMS)

Oracle Applications Implementations Methodology (AIMS) AIM Methodology : Phase 1 – Project Management (Definition) : This phase start very early in the project, starting of every project happens with a Project plan as well as the resource planning considering the high level requirement of the project. This project plan should be divided into the different phase of the project and then base lined. Any change in the requirement need to be taken as a change request and revised Project plan should be issued for stakeholder’s approval. Project plan Review of Budget Resource allocated Org objectives Key document Produced: Baseline Project Plan (mpp), Latest project Plan (mpp) Key Owners: Stakeholders, Client Project Manager(s), Vendor Project Manger(s) Phase 2 – Requirement Analysis (Operational analysis - As Is Study)  Understand and document the current Organization Structure     Prepare the AS- IS Document which details about the existing business processes  Note down the key areas which are considered as the bottleneck in the existing processes Final Step (which is very important) is to get the sign off on all the requirements which are captured. Key Document produced: Current Financial and Operating Structure (RD10), Business Requirements Scenario (RD50) Phase 3 – Solution Design  This is the phase which is termed as TO BE phase also. In this phase analysis is done on the existing Business practice and decisions are taken for providing the solution to each requirement. Gap analysis is also done for the requirements which can not be met by standard products. After the solution is designed by consultants then it need to taken with client in a walk through meeting (with flow diagram or Vision screenshots). This is mandatory as client need to understand the ‘To Be’ process as well as provide the sign off to Solution design. The areas where client is not satisfied need to be explored and alternate solution need to be designed. Scenario Mapping Conduct CRP Key document produced: Gap Analysis (BR10), Business Requirements mapping (BR30), Application Extension Functional Design (MD50) and Application Extension Technical Design (MD70) Phase 4 – Solution Building ( Development Phase) During this phase the instance is prepared and setup is performed for meeting the solution design. This phase differs from project to project as in some cases huge amount of extensions and interfaces are developed. Those complex projects have this phase divided into different phases of system testing and integration testing. Following key activities performed in this phase Test the standard Business processes and interact with Oracle for standard product issues Technical consultant completes the customization and deploy for testing on the basis of MD070 and MD050 Functional Consultant complete the testing of customization and extensions Implementation team applies the Solution Do all the customization Key document produced: Application Setup (BR100), Unit Test Script (TE20), System Test Script (TE40), System Integration Test Plan (TE120) System Integration Test Script (TE50) Phase 5 – Training and UAT - (Go-Live) This phase is generally divided into two levels Conference Level Pilot: Consultant works with Key users to demonstrate the application and take their feedback User Acceptance Testing: Here Key users as well as End user performs the testing and provide acceptance of application. Key document produced: User Training Manual, User Acceptance Test Report (TE130) Some of the available template documents are: Adoption and Learning AP010 Executive Project Strategy AP010 Invitation Memorandum AP010 Session Planning Checklist AP020 Application Overview Customization AP020 Invitation Memorandum AP020 Project Team Orientation Plan AP020 Session Planning Checklist AP030 Project Team Learning Plan AP040 Project Team Learning Environment AP050 Project Team Learning Events Administration AP060 Business Unit Managers Readiness Plan AP060 High Level Systems Overview Customization AP060 Invitation Memorandum AP060 Session Planning Checklist AP070 Invitation Memorandum AP070 Project Readiness Roadmap AP070 Session Planning Checklist AP080 Communication Campaign AP090 Application to Process Overview Customization AP090 Invitation Memorandum AP090 Managers Readiness Plan AP090 Session Planning Checklist AP100 Business Process Organizational Impact AP110 Human Performance Support Systems AP120 Information Technology Groups Alignment AP130 User Learning Needs Analysis AP140 Learning Plan AP150 User Learningware AP160 User Learning Environment AP170 User Learning Events Administration AP180 Effectiveness Assessment AP180 Invitation Memorandum AP180 Session Planning Checklist BP010 BP020 Define Business and Process Strategy Change Catalog BP030 Data Gathering Requirements BP040 Current Process Model BP050 Leading Practice Review BP060 High Level Process Vision BP070 High Level Process Designs BP080 Future Process Model BP090 Business Procedure Documentation BR010 High Level Gap Analysis BR020 Configured Mapping Environment Architecture and Configuration BR030 Business Requirements Mapping Form BR050 Integration Fit Analysis BR060 Information Model BR080 Business Mapping Test Results BR100Aap Accounts Payable Application Setup BR100Aar Accounts Receivable Application Setup BR100Aas Sales and Marketing Application Setup BR100Abom Bill Of Materials Application Setup BR100Aca Common Applications Application Setup BR100Acas Common Applications System Admin Application Setup BR100Ace Cash Management Applications Setup BR100Acf Common Financials Application Setup BR100Acm Common Manufacturing Application Setup BR100Acn Sales Compensation Application Setup BR100Acrp Capacity Application Setup BR100Acs Service Application Setup BR100Acst Cost Management Application Setup BR100Aeng Engineering Application Setup BR100Afa Fixed Assets Application Setup BR100Afi OPM Financials Application Setup BR100Agl General Ledger Application Setup BR100Ahr Human Resources Application Setup BR100Aic OPM Inventory Application Setup BR100Ainv Inventory Application Setup BR100Alo OPM Logistics Application Setup BR100Amrp Master Scheduling MRP Application Setup BR100Aoe Order Entry Application Setup BR100Apa Project Accounting Application Setup BR100Apd OPM Product Development Application Setup BR100Apo Purchasing Application Setup BR100App OPM Process Planning Application Setup BR100Aqa Quality Application Setup BR100Ascp Supply Chain Planning Application Setup BR100Ass Supplier Scheduling Application Setup BR100Asy OPM Systems Application Setup BR100Awip Work in Process Application Setup Document CM010 Configuration Management Procedures CM020 Document Index CM020 Document Update Notice CM030 Configuration Item Index CM030 Configuration Item Status Record CM040 Release Note CR010 Project Management Plan CR010 Project Start Up Checklist CR020 Control and Reporting Procedures CR040 Risk and Issue Form CR040 Risk and Issue Log CR050 Problem Report Form CR050 Problem Report Log CR060 Change Request Form CR060 Change Request Log CR070 Meeting Minutes CR070 Project Progress Report CR080 Acceptance Certificate CR080 Client Satisfaction Report CR080 End Report CV010 Data Conversion Requirements and Strategy CV020 Conversion Standards CV030 Conversion Environment CV040 Conversion Data Mapping CV050 Manual Conversion Procedures CV060 Conversion Program Designs CV070 Conversion Test Plans CV120 Installed Conversion Programs CV130 Converted and Verified Data DO010 Documentation Requirements and Strategy DO020 Documentation Standards and Procedures DO030 Glossary DO040 Document Environment DO060 User Reference Manual DO070 User Guide DO080 Technical Reference Manual DO090 System Management Guide MD010 Application Extension Strategy MD020 Application Extension Definition And Estimates MD030 Design Standards MD040 Build Standards MD050 Application Extensions Functional Design MD060 Database Extensions Design MD070 Application Extensions Technical Design MD090 Development Environment MD120 Installation Instructions PJM01 Engagement Summary PJM02 Project Memo PJM03 Meeting Agenda PJM04 Rejection Note PJM05 Supplier Assessment Record PJM06 Project Document Generic PJM07 Phase End Report PJM08 Site Visit Report PJM09 Project Management Checklist PJM10 Quality Management Checklist PM010 Transition Strategy PM020 Production Support Infrastructure Design PM030 Transition and Contingency Plan PM040 Installation QA Checklist PM090 System Performance Assessment PM130 Business Direction Recommendations PM140 Technical Direction Recommendations PT010 Performance Testing Strategy PT020 Performance Test Scenarios PT030 Performance Test Transaction Models PT040 Performance Test Scripts PT050 Performance Test Transaction Program Designs PT060 Performance Test Data Design PT070 Performance Test Database Load Program Designs PT110 Performance Test Environment PT120 Performance Test Results PT130 Performance Test Report QM010 Quality Management Procedures QM020 Review Comments List QM020 Review Leader Form QM030 Audit Action Form QM030 Audit Report QM040 Metrics Report QM045 Project Healthcheck Checklist QM050 Quality Report RD010 Current Financial and Operating Structure RD020 Current Business Baseline RD030 Process and Mapping Summary RD040 Business Volumes and Metrics RD050 Business Requirements Scenarios RD060 Audit and Control Requirements RD070 Business Availability Requirements RM010 Resource Management Procedures RM020 Assignment Request RM020 Staffing and Organization Plan RM025 Project Orientation Guide RM030 Staff Training Plan RM040 Physical Resource Plan RM040 Service Level Agreement RM050 Incoming Item Record RM050 Installation Plan and Record RM060 Assignment Terms of Reference RM070 Equipment Fault Record TA010 Architecture Requirements and Strategy TA020 Current Technical Architecture Baseline TA030 Preliminary Conceptual Architecture TA040 Application Architecture TA050 System Availability Strategy TA060 Reporting and Information Access TA080 Application Security Architecture TA090 Application and Database Server Architecture TA100 Architecture Subsystems Proposal TA110 System Capacity Plan TA120 Platform and Network Architecture TA130 Application Deployment Plan TA140 Performance Risk Assessment TA150 System Management Procedures TE010 Testing Requirements and Strategy TE020 Unit Test Script TE030 Link Test Script TE040 System Test Script TE050 Systems Integration Test Script TE060 Testing Environment Setup Log TE110 Test Report for System Test TE120 Test Report for Systems Integration Test TE130 Test Report for Acceptance Test WM010 Work Management Procedures