Professional Documents
Culture Documents
System Analysis and Design: Pamantasan NG Lungsod NG Maynila
System Analysis and Design: Pamantasan NG Lungsod NG Maynila
Submitted by
Group Techies
Alonzo, Corina L
Diaz, Rudolph D.
Lalu, Kycir Feleo
Sarmiento, Ma. Rufa V.
Valbuena, Joannabelle P.
Villamor, Lara Bonita L.
Introduction
Historical Background
F.J.D. Clemo, a British shipping executive, arrived in The Republic of the Philippines in 1950,
transferred by United States Shipping Lines from their Hong Kong office to Manila. In 1968, he
retired from U.S. Lines and ventured into partnership with Filipino colleagues for the major
purpose of locally representing various foreign shipping concerns.
On 6th July 1973, Aquila Maritime Business Inc. (Aquila), the first of what is now unofficially
called The Aquila Group of Companies, was registered in the Philippines. In 1977 Mr. Frederick
Clemo, best known as Freddie, became a naturalized Filipino citizen and assumed sole
proprietorship of Aquila. With Aquila as the mother company, our organization has been
involved in those days in a wide range of shipping-related activities: air and sea freight
forwarding, N.V.O.C.C., trucking, brokerage, container leasing, and acted as agents in the
Philippines for a number of foreign concerns. As early as 1978 Aquila began handling on an ad
hoc basis personal injury claims for the first of the Protection and Indemnity (P&I) Associations
to approach our organization seeking purely commercial assistance. Within a few years Aquila's
P&I involvement assumed so large a part of daily corporate life that the need for the
incorporation of a separate Company became apparent.
Protection and Indemnity (P&I) is the traditional name for the coverage obtained by Ship owners
and Charterers to protect and indemnify themselves against their legal liabilities to third parties.
Ship owners entering their vessels with a particular P & I Association become members of that
Association; thus, by definition the Associations are called Clubs.
Thus, in June of 1982 Pandiman Philippines, Inc. (an acronym for P-and-I Man(ila), was
registered as Correspondent in the Philippines for the various P&I Associations looking to our
organization for assistance.
It was the late Mr. Clemo who designed the Pandiman logo, which depicts a three-masted vessel
towing to safety a second crippled vessel with a broken mast and collapsed sails, an analogous
interpretation of the P&I mandate. Mr. Clemo died in 1999, passing the management gavel to his
wife, Janet Clemo who, as President, headed the management team for six years, with Andrew
Malpass, ex Master Mariner, as Vice President and Fiona Malca, the second of the three Clemo's
three daughters, as Consultant. In 2005, Capt. Malpass became President and Mrs. Malca
Executive Vice President when Mrs. Clemo, now Chairman, retired from fulltime involvement.
Pandiman is a correspondent in the Philippines for the majority of the P & I Associations (or
clubs) of the International Group. Our sixty-member staff includes teams of crew and cargo
claims handlers well experienced in their respective fields.
Pandiman's daily routine necessitates close liaison with the three government arms most closely
involved with the manning industry of the Philippines, namely the Philippine Overseas
Employment Administration (POEA), the Overseas Workers Welfare Administration (OWWA)
and the National Labor Relations Commission (NLRC)
Pandiman's Crew Claims Division handles all work involved with seafarers. Each handler is
assigned a carefully drawn-up list of specific local manning agencies of which over 300 are
based in Metro Manila area alone. The Division's Liaison Officer is responsible for meeting
repatriates on arrival in the Philippines and escorting them, when necessary, to the medical
facility. Individual handlers often accompany the instructed P&I counsel to different areas
throughout the Philippine archipelago.
Organizational Chart CHAIRMAN OF THE
BOARD
SEC
TREASURY/
EXEC. SEC Exec.Sec. BILLING
SUPERVISOR
BILLING CASHIER
SENIOR CLAIMS EXEC. SENIOR CLAIMS EXEC.
ANALYST II COMMUNICATIONS
MIS STAFF
RECEPTIONIS CLERK I
COMPANY CLAIMS EXEC
T/TEL. TREASURY/
DRIVER ACCTG. CLERK
OPERATOR TREASURY BILLING
CLAIMS HANDLER ASST. COORDINATO COMMUNICATIONS
CLERK/ENCODER R
.JR. CLAIMS CLERK
EXEC ACCTG. CLERK
SENIOR CLAIMS TREASURY BILLING
RECEPTIONIS CLAIMS HANDLER HANDLER CLERK CLERK
COMPANY
T/MAILING DIV. SEC.
DRIVER
CLERK ACCTG. CLERK
CLAIMS
HANDLER CLAIMS HANDLER
LIASON OFFICER
COMPANY PURCHASING
CARPENTER CLAIMS HANDLER
DRIVER RECORDS CLERK
CLAIMS HANDLER
CUSTODIAN
ENCODER
COMPANY
DRIVER CLAIMS HANDLER
BILLING CLERK CLAIMS HANDLER
RECORDS
CLAIMS HANDLER
CUSTODIAN/ENCODER
BILLING
ANALYST I
CLAIMS HANDLER
ENDORSEMENT
CLERK i
ENDORSEMENT
CLERK
Pandiman Philippines Inc.
Treasury & Billing Division Chart
Supervisor,Treasury
Billing
Billing Analyst ii
Treasury/Billing
Treasury Assistant
Coordinator
Billing Clerk
Statement of the Problem
Documents involved:
Workload report about the Seaman/ship cases- Consists of the information about the case
of the Seaman/Ship.
Scenario:
Pandiman's Crew Claims Division handles all work involved with seafarers. The handler
who is assisting the Seaman/Ship, get the information about the seaman. After that he/she
submit it to the Billing and treasury Department. The billing analysts analyze the
workload report and summarize it manually.
Cause:
Long time consumed in processing the billing summary
Impact:
Errors are frequent
Additional payment for the billing analyst
It takes so long to push in making the invoice because of the workload is still in
progress.
Quantifications:
Ship cases:
Oil pollution
Ship arrest
Collision, fire and explosion
Cargo claims
Towage and salvage
Assists Crew Claims Division when instructions from principals require deployment of a
Pandiman staffer to some other area within the Philippines, normally for the purpose of
visiting a repatriated seafarer
Stowaways
Accident to stevedores and passengers
Damage to/by a vessel or to fixed and/or floating objects
Appointment and monitoring of marine surveyors, divers and other experts
Other related work passengers
2. Redundant process in generating the Billing Summary.
Documents involved:
Sales Invoice- Medical Expenses about the seaman/Ship Cargo
Scenario:
After the billing department submitted the billing summary on PNI, PNI verify this
summary first. They often return it because they not satisfied in this summary.
Cause:
Due to repeated summarization through manual process possibilities are questionable
workload report
Impact:
repetition on typing, every time in making the workload
sometimes in encoding the workload there are times there are negligible error that
are inputted due to the length of the workload
Errors Frequent
Quantifications:
Documents involved:
Sales Invoice- Medical Expenses about the seaman/Ship Cargo
Billing Summary- Workload narrative made by the billing analyst
Scenario:
The PNI clubs often return the billing summary because of the frequent errors they
encountered. After that the Pandiman will revise again the billing summary and submit it
to PNI. The PNI clubs verify it again and if errors occur, they will return it back to
Pandiman.
Cause:
Due to the long time of processing of billing summary and errors are always frequent, the
PNI Clubs suggested the Pandiman to change the manual system of Billing and treasury
division to automate one.
Impact:
Quantifications:
Manning agencies of which over 300 are based in Metro Manila area alone
More than 10 clubs all over the world
Scope and Limitation
Scope
The scope of the billing /treasury system is to solve the problems or damages that may occur on
billing and give the most suitable solution to fix the malfunctions and problems. The accuracy
and validity requirements such as mathematical calculation will be considered. It also provide a
description of the capability to be incorporated for adapting the system to changing requirements,
such as anticipated operational changes.
Limitations
The Treasury/billing System will only develop according to the requirements needed by the
company. Other transactions that are outside the billing/treasury are not included in the study.
Chapter II
System Analysis
Main Menu
Start
A X
Y Processin
Is it g of WSS A
WS
N
Processin
Is it Y g of SIHS A
RHS
N
Processin
Is it A
Y g of RC
RC?
Y Processin
Is it A
SM? g of SM
N
X
Workload Report about the Seaman /Ship Cases
Start
Verification by
the Billing
Supervisor
Is it Y Preparation of the
approve Billing Summary by
the Billing Analyst
d? Y
N Verification of
diarized Workload
Forward disapproved
prepared by Crew
Workload Report to
Handler
Preparation of
Preliminary
B corresponding fee
Preparation of the
costing sheet draft
on each case
Submission of
Workload/ Narrative
to Billing Supervisor
Z
Workload Report
Is Y Finalize the File Folder
there Workload/Narrativ
any
N Checking of
Workload/
Encoding of
Sales Invoice
C
Checking of
Sales Invoice
Approval of the
AVP Finance and
Treasurer
Return
Sales Invoice from Hospital/ Ship Expenses
Start
Verification by
the Billing
supervisor
Encoding of
Sales Invoice
Submission of Sales
Invoice to Billing
Supervisor
Checking of
Sales Invoice
Approval of the
AVP Finance and
Treasurer
Return
Verification about the Billing Summary
Start
Verification by
Billing Supervisor
Checking of
Workload Report
and Billing Summary
N Is Y Verification of
there diarized Workload
any prepared by Crew
Preparation of
N Preliminary
Close corresponding fee
deal
E Preparation of the
costing sheet draft
Return on each case
Submission of
Workload/ Narrative
to Billing Supervisor
E
Grid Chart
Not Satisfied 3 4 1 2
in the Cheque
Context Diagram
Data Flow Diagram
Level 1
Level 2 (Process 1)
)
Level 2 (Process 2)
Level 2 (Process 3)
Level 2 (Process 4)
Level 2 (Process 5)
Level 2 (Process 6)
Level 2 (Process 7)
Level 2 (Process 8)
Level 2 (Process 9)
User Requirements
The intended users of the billing/treasury system is someone who has registered and
authorized with the company name PANDIMAN Philippines. The major user can be the billing
analyst or somewhat knowledgeable and familiar in using the system.
The user that interacts directly with the system must computer literate when it comes in
knowing the functions and properties the system must contain.