AMOS Business Suite Basics Peter van Mossevelde [April 14 th 2005] AMOS Maintenance & Purchase.

AMOS Business Suite Basics

Peter van Mossevelde [April 14th 2005]

AMOS Maintenance & Purchase

AMOS Maintenance & Purchase 2

Introduction

• Maintenance

• Stock Control

• Purchase

• Budget


Introduction

General

When setting up the Maintenance (and Stock) part of the database

part of the AMOS Business Suite, the most important guideline

available is the database specification.


Introduction

General

• Addresses (QA Grades and Product Types)

• Currency Codes and Rates

• Base Currency

• Templates (Enhanced)

• Locations


Introduction

Maintenance

• Components and Functions

• Rounds

• Counters

• Requisition Work

• CBM

• Work Orders


Introduction

Maintenance

• Permits to Work

• Work Planning

• Workload Analysis

• Projects

• Component Transfer


Introduction

Maintenance

• Report Work

• Maintenance Log

• History


Introduction

Stock

• Stock (& Stock Classes)

• Stock Wanted

• In & Out of Stock

• Inventory (Stock Control)

• Transfer Documents

• Stock Transactions


Introduction

Stock

• Hand Terminal

• Stock Analysis

• Stock Optimizer


Introduction

Purchase

• Purchase Forms

• Purchase Contracts

• Transport Documents

• e-Business


Introduction

Budget

• Budget Codes & Budget

• Budget Hierarchy


Introduction

AMOS M&P according to the license file:

• Maintenance

• Stock Control

• Purchase

• CBM

• Budget

• Hand Terminal

• eBusiness

• Planning Module

• Accounting

• Stock Optimizer


Introduction

MaterialsManagement(Purchasing)

ComponentRegister

MaintenanceManagement

InventoryManagement


Maintenance

Primary things to consider with implementation:

• Components

or

• Component Types, Components & Functions

• Naming conventions

• Coding system

• Component Classes


Maintenance


Maintenance

Set up periodical and/or counter based maintenance:

• Components (Types and Functions)

• Job Classes, Job Descriptions

• Disciplines & employees

• Counter Types / Counters

• Maintenance Criteria, Types, Classes and Causes


Maintenance

Work Orders are triggered by:

Frequency

Counters

Rounds

User (Requisition Work)

Condition Based

Project

Periodic jobs

StandardJob Descriptions

Lubrication jobsInspections Overhauls

Visualinspection

Level check


...

Free FormatJob Descriptions

Shore side JobsModifications Defects

Requisition work

Maintenance


Periodic Jobs Requisitioned jobs

Work Order

Manually orderedAutomatically ordered

Maintenance


Periodic Jobs

Work Order

Manually ordered

Requisitioned jobs

Automatically ordered

Reservationof spares, toolsand personnel

Time Line/Planning

Maintenance


Periodic Jobs

Work Order

Workcarried out

Manually ordered

Job Sheets issued

History

Requisitioned jobs

Automatically ordered

Reservationof materials, tools

and personnel

Reporting back

Time Line/Planning

Maintenance


Maintenance

Options:

-Required Parts

-Required Disciplines

-Counters

-Related Jobs


Maintenance

Work Order backlog

Requested Planned Issued Completed Controlled Filed

Postponed Pending Cancelled


Maintenance

Work Order backlog

• Requested

• Planned

• Issued

• Completed

• Controlled

• Filed

• Postponed

• Pending

• Cancelled


Maintenance

Parameters influencing the flow:

• Default ‘Work Order Status’

The above available for Periodic, Requisition, Round and

CBM Work Orders with values Requested, Planned or

Issued.

• ‘Auto-File Completed Work Order’

• ‘Auto-File Controlled Work Order’

The above available for Periodic, Requisition, Round and

CBM Work Orders.


Maintenance


• ‘Auto-Filter WO By Discipline’


Maintenance

Access Control influencing the flow:

• ‘Work Order Issuing’ – whether a user has the access

to issue a Work Order.

• ‘Work Orders Cancellation’ – whether a user has the

access to cancel a Work Order.

• Job Class access. Defining the Job Classes groups

have access to results in users only being able to

report work on Work Orders which are based on a Job

with a Job Class they have access to.


Maintenance

Work Planning


Maintenance

Permits to Work

• Define the Permits to Work

• Attach them to the Job Descriptions

Permit to Work is issued (Change Status of Permit to Work)

to a user with privileges to acknowledge it. User opens the

Permit to Work to acknowledge it. Work Order can then be

reported against.


Maintenance

Workload Analysis

• Employee availability

• Required Discipline


Maintenance

Projects

Grouping work orders into Projects and Sections


Maintenance

Historical data

• Maintenance Log

• History

• Counter Log

• Functions Performed


Maintenance

Component Transfer

-Database must be set-up to use Component Types

-Sharing of following registers need to be set the same (ABS 8.1)

Address Job ClassComponent Class Job DescriptionComponent Type LayoutCounter Type Maintenance CauseDiscipline Maintenance ClassEmployee Maintenance CriteriaImage Reference Maintenance TypeImage Reference / HotspotsImage Reference LinksImage Source


Stock Control

ReservationReservation

Stock

UsedUsedRequisitions &

Purchasing

Requisitions & Purchasing

SoldScrapped

SoldScrapped


Stock Control


• Coding & Naming Convention

• Stock Types

• Stock Classes

• Average or Last Purchase price

• Locations

• Minimum and Maximum Stock Levels

• Perishable items

• Units of Measurement & Factors


Stock Control

Calculate Stock Wanted quantity


Perishable Stock

Don’t register the QTY’s in stock directly when dealing with

Perishable Stock.

Make sure they are registered through the in/out of stock or

inventory functionality to make sure the Expiry Dates are

correctly registered.


Factors


Stock Transfer

Office

Unsubmitted

Submitted Approved

In Transit

Received

Pending

Transferred

Donating

installation

Recipient

installation


Purchase


• One form for all types

• Order Priority

• Delivery and Payment Terms

• Delivery Locations (Contracts)

• Purchase Unit & Factors

• Quality Check

• Approval


POQUERY

Purchase

POQUERY

Stock Wanted

SPRSPR


PO

Purchase

PO

Deliveries

Transport

document


Purchase

Three types of forms:

• Requisition Form

• Query Form

• Purchase Order

Five different statuses:

• Active

• Parked

• Filed

• Split

• Cancelled


Purchase

Access Control influencing the flow:

• Specific Access Control (Registers) to forms of each

type/status combination.

• Specific Access Control (Functions) to convert forms

to each type/status combination.


• ‘Form Status after Query select’

• ‘Form Type after Query select’


Purchase

Approval Parameters

• ‘Level of Approval’

• ‘Lock Approved Purchase Orders’

Approval Access Control

• ‘Forms Approval Purchase Orders’


Purchase

1. Ignore – all forms listed regardless of approval status.

2. Awaiting approval – forms are listed if they are not

approved.

3. Awaiting my approval – forms are only listed if the user

has the right to approve that type of form. If approval

limits are in use i.e. defined, PO’s are only listed if their

estimate (converted to base currency) is within the

curent users approval range e.g. 10,001 to 20,000 (i.e.

the user has an approval limit of 20,000 and there’s one

level before up to 10,000).


Purchase

4. I can approve – forms are only listed if the user has the

right to approve that type of form. If approval limits are

in use, purchase orders should only be listed if their

estimate (converted to base currency) is not greater

than the current users approval limit.

5. Approved – lists all forms already approved.


Purchase

Contracts

• One contract per vendor at any given time.

• Delivery Locations register to be populated.

• Vendor and agreed price to be registered in the Multi

Vendors section for the Stock Item – to ease setup

suggest e-Business.

• Register all Stock Types against the contract or

alternatively use Stock Classes (simpler if suitably

divided).


Purchase

e-Business:

• Define e-Business Format(s)

• Define e-Business Portal(s) – Including export/import

folder.

• Setup the Address – Employee – User loop to retrieve

direct contact details.

• Define suppliers as Portal suppliers (Portal ID to be

supplied by Portal Partner).

• Install and configure Portal Partner software to use

above export and import folders.


Purchase

The e-Business solution supports the following electronic

trading formats:

• Request for Quote (RFQ) – from client to supplier.

• Quotations (QT) – from supplier to client.

• Purchase Order (PO) – from client to supplier.

• Purchase Order Confirmation (POC) – from supplier

to client.


Budget

The budget module allows the users to keep track of the

different expenditures within the system. There are three

budget classes:

• Purchase for PO expenditures,

• Stock for Inventory tracking and

• Maintenance for Resource and Miscellaneous

Expenses tracking.


Budget

Steps to implement budgets

• Define the Budget Codes.

• Set the correct ‘Start of Financial Year’.

• Create Budgets for all three classes.

Optional:

• Define the Budget Hierarchy tree.

• Link Budgets to the Hierarchy tree through the Budget

Codes window.

• Define any Defaults (component, compjob, function).


Budget & Base Currency

Budget is per definition in the Base Currency. However it is

possible to register a different base currency at

installation level should this be required.

The Base Currency defined at the global level defines the

Base Currency used to define the global currency rates

- one currency rate table applies throughout the entire

organization, but individual sites can operate in local

Base Currencies (but still having the same global Base

Currency defined).


Budget & Base Currency

AMOS Business Suite Basics Peter van Mossevelde [April 14 th 2005] AMOS Maintenance & Purchase.

Documents

Transcript of AMOS Business Suite Basics Peter van Mossevelde [April 14 th 2005] AMOS Maintenance & Purchase.