|
Peer-to-Peer
IT bunker at Chemoil
Chemoil recently implemented OBIS 6.0 to address issues such
as lack of data integrity, slow response time and lack of real-time access to
current market information. Priya Jain reports
Chemoil, a marine fuel products supplier, was faced with meeting growing business
demands and dealing with issues such as lack of data integrity, slow response
time and lack of real-time access to current market information. Hence, the
company recently deployed OBIS 6.0.
Earlier in 1994, it had implemented Chemistry, an Oracle-based solution. This
was upgraded in 1999. In 1995, the companys turnover was $1.5 billion.
Presently it is around $4.2 billion. So the number of transactions has increased
and the business has also grown in terms of the number of offices.
With growing business needs, increased complexities, global spread, statutory
regulations and multi-country, multi-currency operations being part and parcel
of the business, Chemoil was forced to look for a fresh solution. It chose Calsofts
Online Bunkering Information System (OBIS) Ver 1.0.
In 2002, it upgraded to OBIS Ver 3.0 and migrated from a two-tier to an n-tier
architecture and brought new business processes under the purview of the system.
In 2005, Chemoil upgraded its systems to OBIS Ver 6.0 from California Software
with the focus to Web-enable critical operations.
| Company |
Chemoil & group companies |
| Solution |
OBIS v6.0 is an end-to-end Supply Chain
Management System for the Bunkering Industry which covers Trading, Operations,
Risk Management and Accounting |
| Year / Time of implementation |
Commenced in March 2005 |
| Aim of the implementation |
Change of Technologymoved from
2-tier architecture to n-tier architecture using Microsoft Technology. The
focus was to Web-enable critical operationsallowing users to access
the system from anywhere / any time. Management reporting gained more importance
and a management dashboard was designed |
| Phases of implementation |
The first phase covered the backlocated
in Chennai. Phase two Web-enabled the system for marketing and trading.
In the third phase the system was rolled out at other group companies and
in the fourth a management dashboard was created |
| Challenges faced |
It was a distributed implementation (across
geographical locations) and co-ordinating user-testing across locations
was a hurdle as was handling change-requests for out-of-scope functionality |
| Major benefits |
End-to-end integration across all functional
departments. Web-enablement giving traders real-time access. Data integrity
across group companies, locations and departments |
Bunker trade
IT implementations are an outcome of business requirements.
To understand the specific requirements of a bunker-trading corporation, lets
take a closer look at its operations. A typical bunker traders day starts
with checking current trade inventory positions and commitments in a spreadsheet.
During the day, the trader enters new trades and sends them to the back-office
for an update of records. Subsequently an e-mail is sent to the operator for
further action and he, in turn, talks to the agents via telephone and confirms
the delivery plan in a spreadsheet. The plan is then manually keyed in and sent
to the terminal operators. On delivery, the Bunker Delivery Note is sent to
the finance department for invoicing.
The terminal operation is a high traffic area where fuel is continuously pumped
in and out of storage tanks by trucks, barges and pipelines. Keeping track of
these movements, collectively and from individual modes of dispatch, results
in an enormous information overload on bunker operators. The entire process
is person-dependent and error-prone due to manual data entry. Global operations
layer their own complexity on to these processes.
A source of concern at the Chemoil group was the non-uniform
representation of data because the associate company had its own style of reporting
and data representation. Some major issues encountered were data integrity,
response time, validity, and real-time access to current market information
and data transfer across locations.

"Earlier pricing used to take two to three days but today it gets
done in
half-an-hour. Now we can key in real-time
information and get access to the current status of inventory and invoices"
- Baburaj Parakkal
Global IT Director, Chemoil
|
Baburaj Parakkal, Global IT Director, Chemoil states, We
were using an isolated trading system to track the trading and risk management
activities. This meant that data had to be culled from various locations. A
forecast based on this data usually was a time-consuming and painstaking effort.
Each group company carried out its transactions in isolation and consolidation
of trades leading to frequent delays in reporting. At the end of the day, employees
were working hard, but the results did not fully justify their efforts.
Chemoil stipulated that any IT solution implemented by it
had to support all of its functions including bunkering trading, cargo operations
and finance management and it had to be simple to operate, and scalable. The
solution had to be online with suitable Web-based interfaces, multi-location
and multi-currency support with workflow automation and alerts.
However, J K Nair, Executive Vice-president and COO, California
Software highlighted some of the challenging aspects of the project; process
automation by linking modules and connecting different users such that each
department can work independently and yet interact with other departments without
loss of confidentiality of information. This need was addressed by building
in comprehensive data level security that ensures confidentiality.
The fuel oil trading business is a volatile, high-volume,
low-margin business. Parakkal explains, The market scenarios keep changing
and hence business processes get dynamic. This places greater emphasis on the
setting up of automated workflow engines that send alerts to the management
and support users in the field (from departments such as retail sales, cargo
operations and claims) with Web-enabled user interfaces that have adequate security
to ensure confidentiality and user defined dynamic reporting across locations.
| Founded in 1981, Chemoil is an integrated physical
supplier of marine fuel products. It purchases fuel oil, diesel oil and
blend components from national oil companies, refineries, major oil producers
among others and delivers marine fuel to a broad base of customers, including
a diverse group of ocean-going ship operators, international container and
tanker fleets, time charter operators, marine fuel traders, and other customers.
It also provides fuelling services through its service centres that operate
in many ports around the world.
The company has physical operations in Los Angeles,
New York, Houston, Singapore, Panama, Amsterdam, Rotterdam and Antwerp,
or the ARA region. In all of these ports, they own or lease terminal capacity
for storage and blending of fuels and barging facilities for the delivery
of marine fuel. It has sales offices in San Francisco, Rotterdam, Monaco
and Singapore. Chemoils back-office in India serves as the hub of
its global operations.
Its business is carried out through nine departments
at eight locations. It buys from oil majors, and supplies fuel oil to
ships at ports. The company hires ships to carry oil to discharge ports
where it has leased or owned oil tanks. From these tanks, Chemoil supplies
to ships coming to those ports using barges. Sometimes it does drop shipments,
supplying the cargo in bulk directly to customers. Often it enters into
joint ventures with partners to share the risk of the cargo.
|

Automatic for the business
| 1992 |
Refinery Management System |
| 1994 |
Chemistry Ver 1.0 |
| 1997 |
Chemistry Ver 2.0 |
| 1999 |
Chemistry Ver 3.05 |
| 2000 |
OBIS Ver 1.0 |
| 2001 |
OBIS Ver 2.0 |
| 2002 |
OBIS Ver 3.0 |
| 2003 |
OBIS Ver 4.0 |
| 2004 |
OBIS Ver 5.0 |
| 2005 |
OBIS Ver 6.0 |
Today, the companys business processes are automated
and integrated including the automation of cargo operations, back-to-back trading,
terminal operations, use of third-party equipment to record terminal operations,
filling in process gaps and ironing out process inadequacy. This is with respect
to information flow in operations and inventory. The other aspects of the project
are facilitating updates to inventory as estimates, as well as actual and verified
movements in a simple manner. Last but not least, the solution generates alerts,
tasks and clarifications to facilitate information flow.
All this automation and integration has reduced the overall
time taken from inquiry to invoicing at Chemoil. OBIS Version 6.0 carries out
the standardisation of the data collected internally and generates reports in
a uniform format while continuing to allow individual users to work with the
format that they are comfortable with.
All front-end modules of OBIS Version 6.0 are Web-enabled
letting traders and operators access information from anywhere. Further, centralised
Web-based modules in OBIS Version 6.0 have eliminated data transfer problems,
ensured data integrity and given operators access to real-time inventory positions
and value. It automatically re-costs the inventory giving an accurate idea of
the cost of various products across tanks and locations at any given point of
time.
The only challenge during the implementation was to get feedback from
multiple locations, handle change requests, synchronise testing and have simultaneous
communication. Since the accounting functionality was done at the back-office
in Chennai, this issue was sorted out, feels Parakkal.
| Period |
Environment |
Modules / Activity |
Change |
| 2000 |
NetWare Windows Oracle
Power Builder |
OBIS Ver 1.0 |
Calsoft migrated the application from
DOS to Windows. At the same time the system was moved onto a relational
database in a two-tier architecture |
| 2001 |
NetWare Windows Oracle
Power Builder |
OBIS Ver 2.0 |
Collections Module was added |
| 2002 |
Windows NT Windows 95/98
Visual Basic DCOM / MTS
n-tier architecture |
OBIS Ver 3.0 |
Migrated from a two-tier to an n-tier
architecture. New business processes were added to the functionality |
| 2003 |
Windows NT Windows 95 / 98
Visual Basic
DCOM / MTS
n-tier architecture
|
OBIS Ver 4.0 |
Added Trading Module |
| 2004 |
Windows NT Windows 95/98
Visual Basic
DCOM / MTS
n-tier architecture |
OBIS Ver 5.0 |
GreatPlains Adaptor added |
| 2005 |
Net environment
SQL Server
Web Access |
OBIS Ver 6.0 |
The focus was to Web-enable critical
operations giving users access from anywhere at any time. Management reporting
gained more importance and a management dashboard was designed. Flexi reporting
came into play |
With the introduction of OBIS Version 6.0, collection and collation of data
became automatic and hence real-time data and timely forecasts are readily available.
Parakkal adds, Earlier pricing used to take two to three days but today
it gets done in half-an-hour. Now we can key in real-time information and get
access to the current status of inventory and invoices. The system analyses
and gives us the provisional profit and loss statement based on the additional
cost involved in selling at a particular port. It also provides multiple purchase
and sales analysis and helps plan our own strategy. Costing is also done in
real-time along with hedging, thus minimising the risk of inventory.
Other than that, consolidation and standardisation of trading and risk management
functionalities across group companies has helped the company leverage capabilities
such as real-time reporting and optimal price realisation. It has also aided
in the implementation of a company-wide risk management policy and build in
natural hedge opportunities across companies against market fluctuations.
| Product |
OBIS v6.0 |
| Desktops running |
Windows 2000 / XP |
| Database |
SQL Server 2000 |
| Servers running |
Windows 2000 |
| Cost of implementation |
$600,000 |
| Number of user licences |
70 |
| Implementation Partner |
None |
|