)
1.Vessel Related messages:
Sl No
|
Document Name
|
Document Type
|
Message movement From – To
|
Message to be integrated and messages to be uploaded to PCS
|
1
|
Vessel Profile
|
VESPRO
|
SA to Port
|
Vessel Master Updation
|
2
|
Voyage Registrations
|
CALINF
|
SA to Port
|
ETA
|
3
|
Allotment of VCN
|
CALINV
|
Port to SA
|
VCN generated by the VPOMS system has to be uploaded to PCS
|
4
|
Berth Management
|
BERMAN
|
SA to Port
|
Berthing Programs of POMS
|
5
|
Berth Allotment / Allocation
|
BERALT
|
Port to SA
|
POMS to PCS
|
6
|
Passengers / Crew List
|
PAXLST
|
SA to Port, Carrier, Customs, Immigration, PHC
|
POMS data repository and generate a report
|
7
|
Stowage Plan
|
STOPLN
|
SA to Port
|
|
8*
|
Bay Plan
|
BATPLIE
|
SA to Port
|
|
9*
|
Stowage Instruction
|
MOVINS
|
SA to Port
|
|
10
|
Dangerous Goods Notification
|
IFTDGN
|
SA to Port
|
POMS data repository and report
|
11
|
Dangerous Goods Notification Acknowledgement
|
DGNACK
|
Port to SA
|
Acknowledge-me to Notification from POMS to PCS
|
12
|
Requisition of Resources
|
RESREQ
|
SA to Port, CFS &
SA to Port
|
Integration with POMS equipment deployment module
|
13
|
Allotment of resources
|
ALORES
|
Port to SA
|
POMS allotment module to PCS
|
14
|
Re-Berthing
|
UNBERT
|
SA to Port
|
Berthing Program of POMS
|
15
|
Vessel Movements
|
VESDEP
|
Port to SA
|
POMS to PCS
|
16
|
Terminal Performance Report
|
TPFREP
|
Port to SA
|
POMS to PCS
|
The above messages are supported with the XML and Text Formats
Vessel Profile:
The Shipping Line/Agent needs to submit the Vessel Profile through the PCS Web and the mandatory documents (PDF) like
Vessel Certificate of Registry
Vessel Tonnage Certificate
International ship Security Certificate
Vessel Safety Management Certificate
P&I Insurance Certificate
Certifications of Class (For Tankers) are to be attached to this Profile.
Once the Agent submits the Vessel Profile, Port Authority verifies the contents of vessels with the certificates attached and approves the Vessel Profile submitted. Port may reject the Vessel Profile in case of non-submission of certificates and Wrong/insufficient details found the Vessel profile. PCS converts the message in the XML format and places the messages in respective outbox of Port.
Port need to download the approved messages to update its Vessel Master maintained in the internal (POMS) system.
Voyage Registration:
The Shipping Line/Agent needs to submit the Voyage Registration after the Vessel Profile is approved by Port Authority. Voyage Registration will act as a notice from a Shipping Agent (SA) to a Port providing information concerning the expected arrival of a vessel and the expected cargo operations Port system downloads the message and integrates with the Port internal application (ETA). Against this request, Port internal system will provide VCN (Vessel Call Number), a unique identification number for the voyage to port.
Allotment of VCN:
On receipt of the Voyage Registration request from the respective Shipping Line/Agent, VPT downloads this message and integrate with the POMS system, which will generate a VCN (Vessel Call Number). The messages generated by the POMS system i.e., CALINV is uploaded to the PCS. PCS in-turn broadcast the same to the respective Line/Agent.
4. Berth Management:
The Shipping Agent submits the Berthing Application with expected arrival schedule Confirming to the ETA details and cargo details. Port downloads this message and integrates with the process of Berthing Program.
5. Berth Allocation:
The downloaded Berthing requests are processed by the internal system and berth is allotted according berthing policies in the Port. The Berth allotment details are uploaded to the PCS (XML format) by the internal system. PCS broadcast the same to the respective Lines/Agents through the PCS web.
6. Passenger/Crew List:
Passenger/Crew List is a submitted by the Line/Agent through the PCS web. The message is downloaded by the Port internal system and maintains a data repository to generate MIS and other reports.
7. Stowage Plan:
Vessel Shipping Lines/Agents submits Stowage plan, which describes containers existing on-board a vessel, and deals with stowing of containers of different types to a location on a container vessel. This message is transmitted to the next Port of call, where the Vessel is expected to visit. This message is intended for use by ship owners, tonnage centers, Terminal Operators and Shipping Lines.
8. Bay Plan:
Bay plan describes containers existing on-board a vessel and deals with stowing of containers of different types to a location on a container vessel. This message is transmitted to the next Port of call, where the Vessel is expected to visit. This message is intended for use by ship owners, tonnage centers, terminal operators, shipping lines, etc.
9. Stowage Instructions:
Stowage instructions sent to the container terminal/ stevedoring operators, this message is used to transmit information about all activities like discharging, shifting, re-stowing and loading.
10. Dangerous Goods Notification:
The shipping Agent declares the dangerous goods / Compressed Gas Cylinders (e.g. carrier's agent, freight forwarder) to the Port (or terminal operator) for performing the checks with respect to the legal requirements on the control of dangerous goods. This messages id downloaded by the internal system and in-turn generates a acknowledgement messages and uploads to the PCS.
11. Dangerous Goods Notification Acknowledgement:
Once the Dangerous goods notification is received, the Port generates a acknowledgement message and uploads to the PCS. PCS in-turn broadcast the same to the respective Agent.
12. Resource Requisition:
Requisition of resources message will be used by Shipping Agent or Stevedores to request port if additional resources like Equipments, Gangs etc are required. Port downloads these messages and integrates with Equipment Deployment modules of POMS application for equipment requests. For Gangs it will integrate with the Gangs allotment / Labour booking system.
13. Allotment of Resources:
After receiving the request for resources, the internal system processes the allotment and allotment details uploaded to the PCS system.
14. UN-BERTHING /SAILING/ SHIFTING / RE-BERTHING:
The Shipping Line/Agents submits this information in PCS portal. The message is used to intimate the Port about the exact departure schedule of vessel and request to issue sailing report. After sailing report from the port, Vessel is moved out of the Port. Port system downloads this messages integrate with the billing modules collects the charges for intermittent services provided and issues Port clearance.
15. Vessel Movement/Vessel Departure:
This message is generated by the Port’s internal application soon after the vessel is departure from the port. The same is uploaded to the PCS and the same will be broadcasted to the respective Agent.
16. Terminal Performance Report:
This Report is generated by the Port’s internal application to transmit information related to the shift wise and cumulative cargo operations carried out related to a vessel. The message is uploaded to PCS and PCS in-turn broadcast to the respective Agent through the PCS portal.
2. Container related messages:
SNo.
|
Message Name
|
Document Type
|
Message Movement From - To
|
Message to be integrated and messages o be uploaded to PCS
|
|
Container Loading and Discharge Order/Adv container List
|
COPARR
|
SA – VCPTL
|
|
|
Container Loading/Discharge Report
|
COARRI
|
VCPTL – SA
|
|
|
Container Stuffing/ Stripping Order
|
COSTOR
|
SA – CFS
|
|
|
Container Load Plan
|
CLPMSG
|
SA – CFS
|
|
|
Container Special Handling Order
|
COHAOR
|
SA – VCTPL
|
|
|
Container stuffing/ De-stuffing confirmation Report
|
COSTCO
|
CFS – SA
|
|
|
Gate Open/Cut-Off Report
|
GECOFR
|
VCPTL – SA
|
|
|
Container/Cargo Gate-in-Gate-Out Report
|
CODECO
|
VCPTL – SA
|
|
|
Equipment Interchange Report
|
ELCREP
|
VCPTL – SA
|
|
|
Empty Container Release Order
|
COPARN
|
SA – CFS
|
|
|
Container Stock Report
|
CODEDOR
|
CFS – SA
|
|
|
Request for Carting Permission
|
CARREQ
|
SA – CFS
|
|
|
Conformation of Carting
|
CARCFN
|
SA-CFS
|
|
|
Job Order
|
JOBORD
|
CFS - VCPTL
|
|
1. CONTAINER LOADING AND DISCHARGE ORDER:
Shipping companies uses this message to inform the port about the containers to be discharged from the vessel or to be loaded onto the vessel. The port can use these details to plan for discharging/loading of containers.
2. CONTAINER LOADING / DISCHARGE REPORT:
A message by which the container terminal reports that the containers specified have been discharged from a vessel (discharged as ordered, over-landed or short-landed), or have been loaded into a vessel.
3. CONTAINER STUFFING / STRIPPING ORDER:
The message is the request of the Shipping /Container Agent to Port/CFS for stuffing of the export cargo/de-stuffing of the import cargo into/from the container. Stuffing / De- Stuffing are generally performed at Shed in CFS Yard/Port Yard.
4. CONTAINER LOAD PLAN:
In export process, Stevedore/Port prepares the message and a detailed plan about the cargo stuffed inside the container. In import process, the message is helpful for de-stuffing of cargo from the container at the port.
5. CONTAINER SPECIAL HANDLING ORDER:
Special handling instructions are provided to port when the vessel carries any over dimensional/ open top/ open Container.
6. CONTAINER STUFFING / STRIPPING CONFIRMATION:
This message is given by port to confirm the stuffing/de-stuffing of specified goods/consignments into/from LCL-containers.
7. GATE OPEN / CUT-OFF REPORT:
Before arriving the vessel in Port, specific hours in advance, Port opens the gate so that the CHA/ Exporter can bring their Container/ Cargo in Port. Similarly Port gives cut off time indicating that the before that time Container / Cargo need to bring to Port. This is done to stream line the loading and un-loading operation on Vessel.
8. CONTAINER GATE-IN/ GATE-OUT REPORT:
A message by which a Port confirms that the containers specified have been delivered or picked up by the inland carrier (road, rail or barge). This message can also be used to report internal terminal container movements (excluding loading and discharging the vessel) and to report the change in status of container(s) without those containers having physically been moved.
EQUIPMENT INTERCHANGE REPORT:
This message is from Port to Shipping Agent/Transporter Indicate the yard position in the port area. This report is issued at the time of receiving of container in Port area and the same is prepared at Port Gate.
10. CONTAINER ANNOUNCEMENT MESSAGE / EMPTY CONTAINER RELEASE ORDER:
Shipping companies uses this message to instruct a container storage yard of the Port/CFS to release one or more empty containers for export packing. According to the instructions of the agent, Port/CFS can plan placing the empty containers at the stuffing point
11. CONTAINER STOCK REPORT:
Container Stock Report can provide details related to Empty Containers, Destination wise pendency, CFS wise List and intimation of non delivery containers.
12. REQUEST FOR CARTING PERMISSION:
CHA/Exporter can ensure the availability of space in docks by asking the intimation request for carting at Port. On the basis of this request Port can ensure the availability of desired location in Port yard.
13. CONFIRMATION OF CARTING:
Port confirms the availability of space for carting of good in Port/Dock by sending a message to CHA/ Exporter.
14. JOB ORDER:
The purpose of this message is to indicate these containers are to be delivered to the CFS. The CFS/Shipping Agent sends the Job Order (container list) and the yard location to the Transporter and directs Transporter to move the containers to the designated CFS
3.Cargo Related Messages:
SNo.
|
Message Name
|
Document Type
|
Message Movement From - To
|
Message to be integrated and messages o be uploaded to PCS
|
1
|
Agent Delivery Order
|
AGDORD
|
SA - Port
|
Integrated with Cargo Storage Module
|
2
|
Mate Receipt
|
MATREC
|
SA - Port
|
-Do-
|
3
|
Application for Landing condition certificate
|
RLOENT
|
CHA - Port
|
-Do-
|
4
|
Confirmation of landing condition certificate
|
GLOENT
|
Port - CHA
|
-Do-
|
1. Bill of Lading/Agent Delivery Order:
This message is filed by the respective Shipping Agent to Port. The bill of lading / Agent Delivery Order is a title of goods. Without Bill of lading Port cannot allow CHA/Importer to even inspect their goods. This message is downloaded by Port and integrates with the Cargo Storage System of Port Operations Management system.
2. Mate Receipt:
Mate receipt is prepared by SA which is endorsed by Master of ship at the time of sailing of Vessel which confirms that the consignment are loaded on Vessel also certified by Customs Boarding officer. This mate receipt is issued for each consignment. The Shipping Agent/Port hand over the Mate Receipt to CHA/Exporter after the payment is received for the services provided (Return of Mate Receipt). This message is downloaded by the Port and integrates with the Draft Survey Quantities in connection with preparation of Cargo Final Bills.
3. Application for landing condition certificate:
The importer / CHA apply for log entry in case the cargo is short landed or excess landed. The CHA requires short or excess landing certificate from Port/CFS/SA for getting benefit in customs liabilities and claiming for insurance. This is messages is downloaded from PCS and integrate with the Cargo documentation module of Port.
4. Confirmation of landing condition certificate:
The port issues necessary certificates against the application made as per message for Application for Log Entry/Short landed/Landing remark. This message is uploaded to PCS to broadcast the same to the respective CHA.
4. Transport related Messages:
SNo.
|
Message Name
|
Document Type
|
Message Movement From - To
|
Message to be integrated and messages o be uploaded to PCS
|
1
|
Inland Waybill/ Rake Transportation memo
|
COPINO
|
Railway/CONCOR to Port; Port to SA
|
ROMS data repository and generate a report
|
2
|
Rail Receipt
|
RAILREC
|
CONCOR to Port and Port to SA
|
POMS data repository and generate a report
|
3
|
Removal Memo from Rake
|
RMLMEM
|
Port to CONCOR/SA
|
Messages has to be generated from ROMS system and uploaded to PCS
|
4
|
Container Pendency List
|
CONTPE
|
Port to CONCOR/SA
|
Messages has to be generated from ROMS system and uploaded to PCS
|
5
|
Train Schedule
|
RAILSC
|
CONCOR to PCS
|
--
|
1. Inland Waybill/Rake Transportation memo:
To provide advance list of wagons / Containers expected at the Port from different ICDs through rail. A message by which an inland carrier notifies the delivery or pick-up of containers. These messages serve to facilitate the inter-modal handling of containers by streamlining the information exchange. This message is used to intimate regarding removal of container from the rake.
2.Rail Receipt:
The messages is to provide advance intimation of the cargo expected in Port via Rail
3.Removal Memo from Rake:
This message contains the placement details of containers on the rake.
4.Container Pendency List:
Pendency of the containers with respective to the destination /ICD Location in the Port.
5.Train Schedule:
This messages filed by the CONCOR to PCS about the train schedule will be made available on PCS for information of the PCS stakeholders.
5.Finance related Messages:
SNo.
|
Message Name
|
Document Type
|
Message Movement From - To
|
Message to be integrated and messages o be uploaded to PCS
|
1
|
Request for assessment of Charges – Containerized Cargo
|
REQCOC
|
SA to Port
|
|
2
|
Request for assessment of Charges - Cargo
|
REQCAC
|
SA /CHA to Port
|
|
3
|
Request for assessment of Charges - Vessel
|
REQVAC
|
SA to Port
|
|
4
|
Request for assessment of Charges - Stevedoring
|
REQSAC
|
SA to Port
|
|
5
|
Request for assessment of Charges - Container
|
REQCTC
|
SA to Port
|
|
6
|
Confirmation of Advanced assessment of Charges
|
CNFASC
|
Port to SA/CHA
|
|
7
|
Payment Status
|
PAYSTS
|
PCS to Port
|
|
8
|
PD Account balance details
|
PDABAL
|
|
|
9
|
Invoice for Vessel/ Containers/ Stevedoring/ Cargo
|
INVOIC
|
Port to SA/CHA
|
|
10
|
Refund Order
|
REFORD
|
Port to Bank
|
|
11
|
Pay order/Refund Advice
|
PAYORD
|
Port to SA
|
|
12
|
Daily Transaction Summary
|
DLYSUM
|
Bank to Port
|
|
13
|
PD Top up
|
TOPUPPD
|
SA to Port
|
|
Reqest for Assessment of Charges -Containerized Cargo
Request for assessment of Charges - Cargo
Request for assessment of Charges - Vessel
Request for assessment of Charges - Stevedoring
Request for assessment of Charges – Container
The above messages are filed by the respective Agencies for assessment of Charges for Containerized Cargo, Cargo, Vessel, Stevedoring and Containers. Port will downloads these messages and integrate with Billing Modules of Cargo, Vessel, Container and Containerized Cargo. The Port internal system computes the charges basing on the parameters provided by the Agencies.
Confirmation of Advanced assessment of Charges:
Once the request is received through the PCS, the Port’s internal system computes the charges for the applied services and generates a Invoice/Bill (advances assessment) and upload the same to PCS.
Payment Status:
Shipping Agents make payment against Port Generated Assessment number ( in case of Confirmation of Assessment of Charges ) or Bill Number (In case of Invoice) or Top up PD Account through e-Payment option. Once bank debits SA A/C and credits Ports A/C, one response URL will be returned to PCS. PCS generates the PAYSTS message with the details received from the Bank response URL. PCS sends the PAYSTS message to Port on-behalf of SA.
PD Account balance details:
Port will send PD Account Balance details to the individual Stakeholder as and when some transaction is executing. In case of Shortfall Intimation Message will be forwarded by the Port informing the stakeholder regarding the shortfall of funds in the PD account of the agent for adjustment against the bill.
Invoice for Vessel/ Containers/ Stevedoring/ Cargo: Port’s internal system generates invoice basing on the request received. The invoice is uploaded to PCS. PCS incorporates the same in the payment gateway to the respective agent to pay the amount against the invoice/bill.
Refund Order:
Port sends this message to the respective bank when they collect excess amount from the Shipping Agents / CHA for the services they have provided. Bank will acknowledge the same message with few additional fields such as Bank Transaction ID, Unique Transaction Reference, Status of transaction after debiting the Port’s account and crediting the Beneficiary A/C
Refund Order/Refund Advice:
After Port receives the REFORD message from the Bank, Port generates the PAYORD message to inform to the agent about the amount they have refunded against a Particular bill number.
Daily Transaction Summary:
This messages is submitted by the Bank to Port and it is used to inform the Port about the details of transaction such as credit/Debit performed on their account on that day.
PD TOP-UP:
This message is generated by PCS when a stakeholder up-top the PD of Port. This message is downloaded by the Port and respective PD account is Top upped by the internal system. The internal system provides Transactions summary report to each and individual PD account holder once in the fifteen days.
6.New Miscellaneous Message:
SNo
|
Message Name
|
Document Type
|
Message Movement From - To
|
Message to be integrated and messages to be uploaded to PCS
|
1
|
Stowage Plan Cargo
|
STCPGO
|
SA to Port
|
Integrated with Vessel Work-done
|
2
|
Pilot Memo
|
PLTMEM
|
SA to Port
|
|
3
|
Pre-Arrival Notification
|
PAISPS
|
SA to Port
|
Data Repository and Reports
|
4
|
MMD Inspection Report
|
MMDINP
|
MMD to Port
|
-Do-
|
5
|
MMD Vessel Detention Order
|
MMDVDO
|
MMD to Port
|
-Do-
|
6
|
MMD Vessel Release Order
|
MMDVRO
|
MMD to Port
|
-Do-
|
7
|
Request for Free Practique
|
REQFPQ
|
SA to PHO
|
|
8
|
Free Practique Permission
|
FREPRQ
|
SA to Port
|
-Do-
|
9
|
Health Declaration for sail out
|
HTLDLR
|
SA to PHO
|
|
10
|
Heal Inspection Certificate
|
INSCER
|
SA to Port
|
-Do-
|
Stowage Plan fo
This message is filed by the Shipping Agent/Lines to inform the Cargo Stowage details of Vessel. Port downloads this message and integrates with the Vessel Working Details (Work-done) Module of POMS.
3. Pre-Arrival Notification:
The Shipping Line/Shipping Agent will file this message after the Voyage is registered. This document is a declaration by the Shipping Line/agent regarding the security details of the vessel as per the ISPS requirement. It is assumed that PAISPS message is filed by the agency only after the VCN is allocated to the vessel by the Port. During the Berthing Application processing, ports shall reject the Berthing application if PAISPS message is not received. Passenger/crew information is not included as that is a separate message. This message shall be processed in combination with Dangerous Cargo Manifest, Passenger/Crew list and Berthing Application. This message is downloaded by the Port and integrates with Vessel information system.
4. MMD Inspection Report, 5. MMD Vessel Detention Order and 6. MMD Vessel Release Order:
The above messages are filed by the MMD when a vessel is inspected, details and released. Port downloads these messages stores in the Data repository for MIS and other reports.
8.Free Practique Permission &Heal Inspection Certificate:
These messages are filed by the Shipping Line/Agent to inform the Port about the 10.Practique Permission and Inspection Certificate. The Port needs to download these messages and integrate with MIS reports required.
7.Regulatory Authority Messages
List of Import Messages:
S.NO
|
Message Description
|
Message Name
|
Message No
|
Message
from – To
|
Integration to
|
1
|
IGM - Vessel Details
|
VESINFO
|
SACHI01
(Part I)
|
SA to Customs
|
|
2
|
IGM – Cargo Manifest
|
CARGO
|
SACHI01
(Part II)
|
|
|
3
|
IGM – Containers
|
Contain
|
SACHI01
(part III)
|
|
|
4
|
IGM Acknowledgement
|
Igm_ack
|
SACHI01A
|
Customs to SA
|
|
5
|
Grant of Entry Inward
|
Entryin
|
CHSAI02
|
Customs to Port
|
IGM Details
|
6
|
IGM on Inward Entry – Vessel
|
Vessinfo
|
CHPOI03
(Part I)
|
Customs to Port
|
IGM entry Details & Import Application
|
7
|
IGM on Inward Entry – Cargo
|
Cargo
|
CHPOI03
(Part II)
|
Customs to Port
|
8
|
IGM on Inward
Entry – Container
|
Contain
|
CHPOI03
(part III)
|
Customs to Port
|
9
|
Request for Cancellation of IGM
|
Reqcanigm
|
SACHI04
|
SA to Customs
|
|
10
|
Cancellation of IGM
|
Canceligm
|
CHPOI08
|
Customs to Port
|
IGM Details
|
11
|
Landing Tally Report
|
Tally
|
POCHI06
|
Port to Customs
|
Import Cargo Receipts
|
12
|
Details of Containers landed and damaged packages
|
Contland
|
POCHI06
|
Port to Customs
|
Import – Container Receipts
|
13
|
Landing/Tally Report – Acknowledgement
|
Tally_ack
|
POCHI06A
|
Customs to Port
|
|
14
|
Excess Landed Cargo
|
Excess
|
POCHI07
|
Port to Customs
|
Cargo Storage
Module
|
15
|
Excess Landed Cargo – Acknowledgment
|
Excess_
ack
|
POCHI07A
|
Customs to Port
|
|
16
|
Location of Cargo
|
Location
|
POCHI08
|
Port to Customs
|
Cargo Storage
Module
|
17
|
Location of Cargo – Acknowledgement
|
Location_ack
|
POCHI08A
|
Customs to Port
|
|
18
|
BE on Submission – Master
|
Be
|
CHPOI09
(Part I)
|
Customs to Port
|
Import Application
|
19
|
BE on submission – Container
|
Be
|
CHPOI09
(Part II)
|
Customs to Port
|
20
|
BE on submission –
Item
|
Be
|
CHPOI09
(Part II)
|
Customs to Port
|
21
|
BE on OOC – Master
|
Ooc
|
CHPOI10
(Part I)
|
Customs to Port
|
|
Sl.No.
|
Message Description
|
Message Name
|
Message No
|
Message
from – To
|
Integration to
|
22
|
BE on OOC – Container
|
Ooccont
|
CHPOI10
(Part II)
|
Customs to Port
|
Import Application
|
23
|
BE on OOC – Items
|
Oocitms
|
CHPOI10
(Part III)
|
Customs to Port
|
24
|
ACP Status of importer
|
Be
|
CHPOI11
|
Customs to Port
|
|
25
|
Request for Transshipment
|
Req_trans
|
SACHI12
|
SA to Customs
|
|
26
|
Transshipment Permit Approval
|
Trans
|
CHPOI13
|
Customs to SA
|
|
27
|
Request for Cargo Movement
|
Cargo_move
|
SACHI14
|
SA to Customs
|
|
28
|
Cargo Movement Approval
|
Move_app
|
CHSAI15
|
Customs to SA
|
|
29
|
Gate Pass
|
Cfs_pass
|
POCHI16
|
Port to Customs
|
Cargo Storage - Deliveries
|
30
|
Consignment arrival at CFS
|
Cfs_arr
|
CFCHI17
|
CFS to Customs
|
|
31
|
Ditention/ Confiscation/ Release Order
|
Dcrord
|
CHPOI31
|
Customs to Port
|
Cargo Storage
|
32
|
Detintion/ Confiscation/ Release of Containers
|
Dcrordcon
|
|
Customs to Port
|
Cargo Storage
|
33
|
Disposal Request
|
Disreq
|
POCHI32
|
Port to Customs
|
Cargo Storage –
Auction Cargo
|
34
|
Disposal Order
|
Disord
|
CHPOI33
|
Customs to Port
|
35
|
Cargo disposal particulars
|
Disposal
|
POCHI34
|
Port to Customs
|
36
|
Console Manifest
|
Conscargo
|
CMCHI21
|
Consol Agent to Customs
|
|
37
|
Consol Manifest – Container Details
|
Conscont
|
CMCHI21_2
(PART II)
|
Consol Agent
To Customs
|
|
38
|
Consol Manifest – Acknowledgement
|
Consack
|
CMCHI21A
|
Customs to
Consol Agent
|
|
|
|
|
|
|
|
List of Export Messages:
Sl.No.
|
Message Description
|
Message Name
|
Message No
|
Message
from – To
|
Integration to
|
1
|
Application for Rotation No.
|
A_rotn_no
|
SACHE01
|
SA to Customs
|
|
2
|
Application for rotation Number – Ack
|
Goods_arrival_ack
|
CHSAE01A
|
Customs to
CONCOR
|
|
3
|
Allotment of Rotation No.
|
rotn_no
|
CHSAE02
|
Customs to Port
|
|
4
|
Application for cancellation of Rotation No.
|
A_can_rtn
|
SACHE03
|
SA to Customs
|
|
5
|
Cancellation of Rotation No.
|
Can_rtn_no
|
CHSAE04
|
Customs to Port
|
|
6
|
Shipping Bill details on submission
|
Sbmaster
|
CHPOE05
|
Customs to Port
|
Export Application
|
7
|
Entry of Goods into Port
|
Goodsreg
|
POCHE06
|
Port to Customs
|
Export Receipts
|
8
|
Cargo arrival – Acknowledgement
|
Goods_arrival_ack
|
CHPOE06A
|
Customs to Port
|
Export Receipts
|
9
|
LEO (let export order)
|
Leo
|
CHPOE07
|
Customs to Port
|
Export Application
|
10
|
Stuffing Report
|
Leo
|
CHPOE08
|
Customs to Port
|
11
|
Details of shutout cargo
|
Shutout
|
CHPOE09
|
Customs to Port
|
Vessel Survey Dtls
|
12
|
Application for Entry Outward prior to loading u/s 39
|
Aoutward
|
SACHE10
|
SA to Customs
|
|
13
|
Entry Outward
|
Eogrant
|
CHPOE11
|
Customs to Port
|
Vessel Voyage
|
14
|
Application for Port clearance u/s 42 prior to sailing
|
Aportclr
|
SACHE12
|
SA to Customs
|
|
15
|
Grant of Port Clearance
|
Portclr
|
CHSAE13
|
Customs to Port
|
Vessel Information
|
16
|
Vessel sailing Report
|
Sailingrpt
|
POCHE14
|
Port to Customs
|
Vessel Movements
|
17
|
Export General Manifest
|
Egm_master
|
SACHE15
|
SA to Customs
|
|
Messages From Customs to Port (Imports) …… 18
Messages from Port to Customs (Imports) ……. 7
Messages from Customs to Port (Exports) ……. 9
Messages from Port to Customs (Exports) ……. 2
The messages in Customs Message Specification version 1.9 which are exchanged between customs and other stakeholder are groups and released as customs messages in accordance with PCS implementation. The above messages are filed by the respective Agents through the Customs. Port downloads/uploads these above messages through the PCS message handling hub and integrates with the Port’s internal application.
Port need to maintain the two modes of integration of PCS messages, one is integration of messages for the messages filed by the respective agencies and another method non integration (in disaster situation, when the PCS messages are failed due any reason) mode. The internal application could be able to capture the data (messages) through the front end screens of POMS application.
The XML Schemas of messages, structures and other details may be down loaded from the PCS web site https://www.Indianportscommunitysystem.com.
Appendix # 1
VISAKHAPATNAM PORT TRUST
AGREEMENT NO: VPT/R&P/2010 – 200 , DATED: ........
ARTICLES OF AGREEMENT
ARTICLES OF AGREEMENT made at Visakhapatnam this _________ day of
__________ 2010 between Visakhapatnam Port Trust, having its registered office at Administrative Building, Visakhapatnam-530035 (hereinafter referred to as the “Employer”), which term or expression unless excluded by or repugnant to the context or meaning thereof, shall be deemed to include its successors and assigns) OF THE ONE PART
AND
M/s_______________________, a Company organised and existing under the laws of ________ (Name of the Country) and having its registered office at _________________ (hereinafter referred to as “Contractor”), which term or expression unless excluded by or repugnant to the context or meaning thereof, shall be deemed to include its successors and permitted assigns), *(In case the Contractor forming Consortium with his associate members) OF THE OTHER PART.
WHEREAS
a) The Employer has decided to implement ERP Solution at Visakhapatnam Port Trust, and
b) The Contractor has declared that the Contractor has proven and specialized knowledge and expertise for implementing ERP Solution viz., supply and installation of ERP Product, hardware extending implementation services and training, User Acceptance Testing, Go-Live & stabilization acceptance tests, Go-live, demonstrating and establishing Performance Guarantee Parameters of the Work, as per the Contract Specification No._______________ and other documents of the Contract, and
c) The Contractor has declared that the Contractor is in a position to disclose, impart, deliver and transfer the requisite design documents, software and requisite tools of those items which are in the scope of the Contractor, to the Employer for the solution design, development and for installation, Start-up and Commissioning, Demonstrating and establishing Performance Guarantee Parameters of the Work with the aim to implement ERP solution as specified in the Contract, and
d) The Contractor has obtained clarifications on technical and commercial aspects, inspected the site and surroundings of Work and has examined and considered all other matters, conditions and things, probable contingencies and generally all matters incidental thereto and ancillary thereof, and
e) The Contractor has agreed to undertake the implementing ERP Solution viz., supply and installation of ERP Product, hardware, extending implementation services, training, User Acceptance Testing, Go-Live & stabilization acceptance tests, Go-live, demonstrating and establishing Performance Guarantee Parameters of the Work, as per the Contract Specification No. _______________ and other documents of the Contract, and the Employer has accepted the Tender of the Contractor as modified and agreed upon, and
f) The Employer has entered into Agreement with the constituted Consortium comprising of its members, M/s …………, M/s ………. M/s …………. And M/s……………….. for implementing the total Scope of Work under the Agreement. Though, the above Consortium members are jointly and severally liable and responsible for fulfilling respective contractual obligations, however, M/s ……….. , as the Leader of the Consortium as well as designated
“Contractor” of the Work shall assume overall responsibility to ensure proper co-ordination amongst the Consortium members and completeness of the Work as a whole in conformity with the provisions of the Agreement
Now it is hereby agreed as follows:
1. In this Contract, words and expressions shall have the same meanings as are respectively assigned to them in the General Conditions of Contract and Special Conditions of Contract hereinafter referred to.
2. The following documents shall be deemed to form and be read and construed as part of this Contract, viz.
NIT (Notice inviting tender)
Instructions to Tenderers
Letter of Acceptance,
Price Schedule,
General Conditions of Contract and Appendices, Forms
Special Conditions of Contract and Annexure, if any
Contract Specification, Other Technical Documents, software, requisite tools and drawings. Other document and correspondences
3. The Commencement of Contract shall be the date of issue of Letter of Acceptance.
4. In consideration of the payments to be made by the Employer to the Contractor as hereinafter mentioned, the Contractor hereby covenants with the Employer to “implement ERP Solution” viz., supply and installation of ERP Product, hardware extending implementation services, training, User Acceptance Testing, Go-Live & stabilization acceptance tests, Go-live, demonstrating and establishing Performance Guarantee Parameters of the Work, as per the Contract Specification No. _______________ and other documents of the Contract
5. Time is the essence of the Contract.
The Go-Live will be completed in nine months from the date of award contract.
The stabilization acceptance shall be completed within six months from Go-Live. The performance guarantee period of twe;ve months will start from the date of stabilization acceptance. The Go-Live/Stabilization of ERP Solution shall be considered as completed in all respects only after fulfilling all relevant acceptance tests as per contractual obligations under the Contract.
6. The Employer hereby covenants to pay the Contractor in consideration of the above Work, the Contract Price in the manner described in the Contract.
7. No amendment to this Contract shall be valid or be of any effect unless the same is agreed to in writing by both the parties hereto and specifically stated to be an amendment to this Contract.
8. All disputes arising out of or in any way connected with this Contract shall be deemed to have arisen in Visakhapatnam. Only the Courts in Visakhapatnam shall have jurisdiction. However, the disputes, if any, shall be settled by Arbitration mentioned in the General Conditions of Contract.
9. The several parts of the Contract have been read and fully understood by us.
IN WITNESS WHEREOF the Employer and the Contractor have caused this Agreement to be duly executed by their duly authorized representatives the day and year first above written.
Signed by the said in the presence of
Signature............... Signature……..
Name…………….. Name…………..
Address…………. (Employer) Address………….
Signed by the said in the presence of
Signature............... Signature……..
Name…………….. Name…………
Address…………. (SI/Consortium Leader) Address………….
Appendix # 2
Mandatory Requirements for ERP Solution
(The Bidders are expected to provide the reference to from/to page numbers where compliance to individual requirements has been described. These pages should ideally be immediately after this form.)
S
N
O
|
PARAMETER
|
REQUIREMENT
DESCRIPTION
|
SUPPORTING
DOCUMENTS
REQUIRED
|
COMPLIED
Y/N
|
REF PAGE NO
|
ERP Product Capability
|
1
|
Widely respected
product
|
The offered ERP product must have been successfully implemented in at least three large organizations in India with at least four modules out of Finance & Costing, MM, Human Resource, and Projects etc. One of the three references must be a public sector undertaking
|
Documentary Evidence clearly indicating the ERP Modules successfully implemented in form of
Customer Testimonials
|
|
|
2
|
Implementation in
port
|
The offered ERP product must be similar to or an improved or updated version which has been successfully implemented in at least one sea port organization with turnover of Rs. 300 crores or more in any of the last three financial years i.e., 2007-08, 2008-09, 2009-10 and these products should be successfully running as of the current year i.e., 2010-11 and the products subsequent to implementation would have been updated or upgraded as required. Wherever fiscal year has been mentioned, for convenience of countries where calendar year is followed, calendar year would be accepted e.g., for the fiscal year 2007-08 calendar year 2007 would be reckoned and so on.
|
The bidder has to establish the credentials
through data, video conference or other means including possible visits to the customer sites, if necessary.
|
|
|
3.
|
Integration
with non-ERP
application
|
The offered ERP product must have been integrated with non- ERP applications in at least one large organization. (Legacy applications viz., Port Operations, Hospital Management System etc.)
|
Documentary evidence in form of Customer
Testimonials
|
|
|
4.
|
India specific
Country Version
|
The offered ERP product must be the Country Specific Version for India with statutory requirements incorporated and should have a localization support in terms of Sales tax, Excise, Income tax etc. specific to India
|
Documentary evidence in form of Customer Testimonials
|
|
|
5.
|
Support services
|
The ERP product vendor must
be capable of providing 24 X 7
support services on functional and technical issues, upgrades, bug fixes etc. in person or through remote arrangements with resolution time commitment of 24 hrs.
|
Self certificate
From company’s
Authorized signatory.
|
|
|
6.
|
Support Period
|
The ERP product vendor should
support the solution for a minimum period of 7 years from the date of supply
|
Please provide Self certificate From company’s authorized
signatory.
|
|
|
7.
|
Local presence
|
The System Integrator must have offices in India
|
Please provide list of offices in India with nature of activities.
|
|
|
8
|
Experience
of the Company
|
The System Integrator must have successfully implemented four out of six modules (Finance, Accounting & Costing, Materials Management, Projects, Assets, Human Resource and Business Intelligence of the offered ERP product for at least four customers in last three years including ongoing projects.
|
Documentary
evidence in form of
Customer Testimonials
|
|
|
9
|
SEI CMMi
Level 3
|
The System Integrator should be SEI CMMi level 3 certified. If ERP product vendor himself takes the role of System Integrator, this requirement is not necessary.
|
Please provide copy / details of the certificate
|
|
|
10
|
ERP Payroll
|
The System Integrator should have implemented ERP payroll in at least one large organization of 4000 or more employees.
|
Documentary
evidence in form of
Customer Testimonials
|
|
|
11
|
Annual turnover
|
Annual turnover of the System Integrator for the last three years should be Rs. 100 crores or more per annum in the last three years in IT services.
|
Please provide audited balance sheets
|
|
|
12
|
System Integrator manpower
|
The System Integrator must have more than 1500 computer professionals working full time in India with the company for at least last 3 years.
|
Please provide documentary evidence
|
|
|
13
|
System Integrator ERP manpower
|
The System Integrator must have more than 300 computer professionals working full time in India with the company with experience in ERP implementation
|
Please provide documentary evidence with projects handled
|
|
|
Appendix # 3: Functional Requirement Specifications
Note: Bidder to fill Column D with a number as indicated below
Provided in the package and fully meets the requirement – 3 marks
Meets with additional procedures/customization available with the package – 2 marks
Meets the requirement with third party software provided – 1 mark
Not available/provided – 0 marks
Give details like the module name, third party name etc of the above in the remarks column
The codes used for priority are:
Priority code
|
Priority
|
Weightage factor
|
C
|
Critical
|
3
|
D
|
Desirable
|
1
|
E
|
Essential
|
2
|
SNO
|
FUNCTIONAL REQUIREMENT
|
PRIORITY
|
AVAILABILITY
|
REMARKS
|
FINANCE
|
1
|
Ability to support "Double Entry System of Accounting" on "Accrual Basis"
|
C
|
|
|
2
|
Ability to maintain and enforce for strict compliance, the Delegation of Powers (DOP) with a facility to update/modify/ delete/ add powers/grades etc.
|
C
|
|
|
3
|
Ability to implement Work-flow based mechanism of put up of proposal, concurrence, re-comment, forward for approval, refer to backward for necessary action, refer to across functions for getting back along with comments/ remarks/ information/ attachments etc., and for approval and feed back.
|
C
|
|
|
4
|
Ability to generate vouchers automatically based on the workflow outcome as defined by the business rules.
|
C
|
|
|
5
|
Ability to maintain Foreign Exchange Rates centrally and apply wherever necessary
|
C
|
|
|
6
|
Ability to upload exchange rates data from excel or any other system to ERP
|
D
|
|
|
7
|
Ability to maintain the Holiday list of VPT and that of Banks/Govt. as applicable to specific branches/ outstation offices and Head Office individually for determining Due Dates on various occasions or any other purpose
|
C
|
|
|
8
|
Ability to integrate the Finance Function with other functions in ERP and other legacy systems retained
|
C
|
|
|
9
|
Ability to implement and maintain unique vendor master across the organisation on line
|
C
|
|
|
10
|
Ability to implement a single vendor code for a single vendor.
|
C
|
|
|
11
|
Ability to through alert where any new vendor code is being updated with a name which resembles any name already existing in the vendor master. For this purpose, the system should be able to convert both the existing name and new name into fully abbreviated or partially abbreviated and compare for detecting duplicates. For example, the existing name is "M/s N.M.D.C. Ltd" and a new vendor code is being tried with a name N.M. Development Corporation Limited. In such case the system should be able to convert both the names into
abbreviations and generate an alert that there exists already a similar party. It should also filter automatically the words like M/s, M / s etc.
|
C
|
|
|
12
|
Ability to generate report of vendor list/particulars where the name of vendor resembles the name string supplied by user or vendor is inactive etc.
|
D
|
|
|
13
|
Ability to maintain multiple addresses against each Vendor wherever necessary
|
C
|
|
|
14
|
Ability to generate vendor codes automatically by the system after satisfying that there is no duplication
|
D
|
|
|
15
|
Ability to maintain vendor attributes in multiple ways like vendor type (eg. SSI, PSU, Private, Manufacturer, Dealer/Distributor, Agent contractor etc.)
|
C
|
|
|
16
|
Ability to maintain vendor status in multiple ways eg Blacklisted etc., and generates alerts where transactions are being entered with specified status vendors.
|
C
|
|
|
17
|
Ability to drilldown the past transactions for any vendor as desired by users
|
C
|
|
|
18
|
Ability to maintain major financial information like turnover, profit for the last three years.
|
C
|
|
|
19
|
Ability to maintain all types of Tax/other legal/Statutory particulars in respect of each vendor, group of vendors as required in the context of Indian Statutory/Tax legislations like TDS, Sales Tax, VAT etc. with a facility to modify the same wherever required.
|
C
|
|
|
|
Ability to generate TDS data and other statutory forms returns and certificates
|
C
|
|
|
20
|
Ability to automatic updating of Tax Laws by the ERP Product vendor as and when law changes.
|
C
|
|
|
21
|
Ability to maintain "Alternative/ Alias/ Short Names" for each vendor
|
D
|
|
|
22
|
Ability to maintain particulars of "Contact Person" if any, like Name, Address, Telephone Number, Fax Number, email address etc.
|
C
|
|
|
23
|
Ability to maintain the Bank particulars/details for each vendor to facilitate for e-payment/cheques payment etc.
|
C
|
|
|
24
|
Ability to maintain and enforce default payment terms like "Immediate", "on 30th day" etc
|
C
|
|
|
25
|
Ability to capture details of manufacturer as well as supplier, where applicable.
|
C
|
|
|
26
|
Ability to merge/demerge vendors wherever such event takes place at vendor level
|
E
|
|
|
27
|
Ability to restrict and control the access to Vendor Master to specific users.
|
C
|
|
|
28
|
Ability to facilitate complete automated bill passing and payment along with necessary accounting thereof as per the business rules of VPT
|
D
|
|
|
29
|
Ability to support Running Account Bills (RA Bills) and Final Bills in respect of PO/AT/Contracts.
|
E
|
|
|
30
|
Ability to extend facility to Vendors on web/internet for uploading invoices and pushing to ERP.
|
C
|
|
|
31
|
Ability to import invoice data into ERP from a non-ERP application.
|
C
|
|
|
32
|
Ability to enter invoices/ Material Receipt numbers individually or in a batch.
|
D
|
|
|
33
|
Ability to register vendor invoices.
|
C
|
|
|
34
|
Ability to track invoices received but referred to other functions/ vendors for clarifications/details
|
C
|
|
|
35
|
Ability to forward reasons/ remarks requiring further clarifications/ details, through e-mail mode/ work-flow mode etc.
|
C
|
|
|
36
|
Ability to avoid duplicate invoice entry supported by necessary checks and alerts wherever necessary
|
C
|
|
|
37
|
Ability to track invoices received not processed/paid
|
E
|
|
|
38
|
Ability to maintain and implement/enforce check-list
for processing vendor invoices
|
E
|
|
|
39
|
Ability to generate automatic alerts for non compliance of PO terms (documents, price, delivery date other conditions of contract)
|
E
|
|
|
40
|
Ability to check invoice values in foreign currency based on contractual terms.
|
C
|
|
|
41
|
Ability to capture details like quantity, quality of the material dispatched by foreign supplier.
|
C
|
|
|
42
|
Ability to automatically link PO, Invoice, Receipt of material/ Services and Vendor Master and ability to retrieve on supply of one information, the other details. E.g. Ability to retrieve vendor details for a given PO number
|
D
|
|
|
43
|
Ability to match invoice to PO, Receipt in the system at line level eliminating need for physical PO
|
C
|
|
|
44
|
Ability to track budget details for each PO/AT/Contract as well as each vendor invoice level.
|
C
|
|
|
45
|
Approval of certain category of invoices like those for hotel bill, car hire, newspaper and periodicals etc based on individual employee's entitlement.
|
E
|
|
|
46
|
Ability to make payments to parties where no contracts/PO exists.
|
E
|
|
|
47
|
Ability to adjust advances and regularise bills submitted by the supplier/contractor/ employee etc.
|
E
|
|
|
48
|
Ability to track AMOUNT given to employees towards imprest/local purchases etc.
|
E
|
|
|
49
|
System based payment approval hierarchy based on amount in line with VPT's Delegation of Power (DOP).
|
E
|
|
|
50
|
Ability to make payments through different modes like e-payments, RTGS, Cheque, Bank Demand Draft, Bank Transfer, LC payment, Cash, Acceptance of Bills payable etc
|
C
|
|
|
51
|
Ability to club multiple invoices on the same vendor in one payment.
|
E
|
|
|
52
|
Ability to prioritize payments based on pre-defined criteria e.g. due date, vendor category etc
|
D
|
|
|
53
|
Ability to compute the Due Date for payment automatically based on the terms of the concerned PO/Vendor Master/ receipt of material as specified by the user after taking into consideration the Holiday list of VPT/ National holidays/ Sundays etc.
|
E
|
|
|
54
|
Ability to create liability where payment are made in installments /percentage of the bill processed and passed, for the balance amount payable and also keep a track of the liability for subsequent discharge as required.
|
E
|
|
|
55
|
Ability to track and allow manual payments including approvals outside the system and subsequent regularization
|
E
|
|
|
56
|
Ability to calculate gain / loss on foreign exchange, in case of LC/foreign currency payments
|
D
|
|
|
57
|
Ability to adjust outstanding advances against vendor invoices and pay/recover the differential amount as the case may be.
|
E
|
|
|
58
|
Ability to indicate/pop-up the existence of unadjusted Advance, while processing payments to vendors or
Processing further advance
|
C
|
|
|
59
|
Ability to generate alerts where advances are lying unadjusted for more than the specified period.
|
E
|
|
|
60
|
Ability to link advances to specific PO/AT/Contract to ensure adjustment of invoices against advance only on matching of vendor invoice to that PO/AT/ Contract as the case may be.
|
E
|
|
|
61
|
Ability to track materials issued on either free-of-cost basis or chargeable basis to contractors and accounts the same as per defined business rules.
|
E
|
|
|
62
|
Ability to make recoveries from contractors for materials issued on free-of-charge basis to the extent consumed in excess of applicable norms as certified by Engineer-in-charge
|
C
|
|
|
63
|
Ability to track material which was issued to contractors on free-of-charge basis and lying with contractor un-consumed for more than specified period/date and to include the same into the inventory valuation
|
E
|
|
|
64
|
Ability to make recoveries from contractors for materials issued on chargeable basis.
|
C
|
|
|
65
|
Ability to generate/print/send by e-mail, the Request letter and application for opening of LC by automatic capturing key terms of PO/AT/Contract into the LC terms.
|
E
|
|
|
66
|
Ability to upload LC applications in banks' portals.
|
E
|
|
|
67
|
Ability to track status of LCs.
|
E
|
|
|
68
|
Ability to track due dates for LC payments and ability to generate payment authorisation letters on the due dates
|
D
|
|
|
69
|
Ability to facilitate issue of request for LC amendments wherever such requisitions are received from supplier/MM Department in terms of PO.
|
D
|
|
|
70
|
Ability to account for LC charges
|
E
|
|
|
71
|
Ability to receive no due certificates and statutory clearances online.
|
D
|
|
|
72
|
Ability to monitor payments made by outstation office and ability to regularize bills on receipt.
|
D
|
|
|
73
|
Ability to permit payments after approval of time and quantity deviation
|
E
|
|
|
74
|
Ability to track payments made BOQ wise for each contract.
|
E
|
|
|
75
|
Ability to withhold necessary amounts where statutory requirements have not been complied with (in case of service bills).
|
E
|
|
|
76
|
Ability to monitor payments against overall contract value.
|
E
|
|
|
77
|
Ability to link payments to completion/installation details.
|
E
|
|
|
78
|
Ability to generate vendor account statement to be sent to the vendors.
|
E
|
|
|
79
|
Ability to maintain data of Bank Guarantees received from vendors/contractors etc., including full particulars about vendor code with a link to vendor master, related PO/AT/Contract reference, Bank name with ability to link with Bank Master, BG date, BG expiry date, BG confirmation date, BG status, BG invocation details etc.
|
E
|
|
|
80
|
Ability to implement approval of PO/Invoice subject to receipt /confirmation of BG.
|
E
|
|
|
81
|
Ability to generate alerts wherever BG is nearing expiry date as per the preset criteria.
|
E
|
|
|
82
|
Ability to place hold on vendor payments in cases like BG receipt/confirmation is pending or BG has expired.
|
E
|
|
|
83
|
Ability to generate request letters for extension/invocation of bank guarantees.
|
E
|
|
|
84
|
Ability to handle EMD received in the form of cheque, BG, DD etc
|
E
|
|
|
85
|
Ability to record collection of EMD from vendors/service providers/ customers against the related PO/AT/Contract and to keep a track of it.
|
C
|
|
|
86
|
Ability to refund/adjust deposits with age-wise analysis.
|
D
|
|
|
87
|
Ability to generate System Alerts on EMDs not returned to unsuccessful bidders.
|
D
|
|
|
88
|
Ability to convert EMD into Security Deposit for successful vendors and to keep link between the EMD and PO/AT/Contract and also vendor master.
|
C
|
|
|
89
|
Ability to handle credits i.e. CENVAT/VAT/ Customs/ Cess etc.
|
E
|
|
|
90
|
Centralized definition of fixed asset categories, description, multiple depreciation rates etc
|
E
|
|
|
91
|
Ability to maintain parent-child relationship across asset classes
|
E
|
|
|
92
|
Ability to support different methods of depreciation like WDV, SLM etc
|
E
|
|
|
93
|
Ability to support depreciation as per IT Act
|
E
|
|
|
94
|
Ability to record fixed assets as either capitalized or work-in-progress
|
E
|
|
|
95
|
Ability to categorize assets based on various parameters like movable, immovable, plant assets etc
|
E
|
|
|
96
|
Ability to maintain parent - child asset relationships
|
E
|
|
|
97
|
Record fixed assets with date placed in service in the past
|
D
|
|
|
98
|
Ability to merge multiple fixed assets into one fixed Asset
|
E
|
|
|
99
|
Provision to rectify errors in recording fixed assets in the same period or in previous periods
|
D
|
|
|
100
|
Ability to record number of units against each fixed assets e.g. chairs - 10 units
|
E
|
|
|
101
|
Ability to generate Fixed Assets schedule in accordance with the Income Tax Act
|
E
|
|
|
102
|
Ability to retire entire or part of an existing fixed asset and update asset register on retirement of assets
|
E
|
|
|
103
|
Ability to record salvage value, sale proceeds, cost of removal etc
|
E
|
|
|
104
|
Ability to identify assets identifying disposal
|
E
|
|
|
105
|
Ability to update relevant details in Asset Register
|
E
|
|
|
106
|
Record the physical location of each fixed asset
|
C
|
|
|
107
|
Record transfer of fixed assets from one location to another or from one employee to another
|
C
|
|
|
108
|
Record insurance details against each fixed assets
|
E
|
|
|
109
|
Record multiple insurance policy details against individual fixed assets
|
E
|
|
|
110
|
System generated alerts / reminders to designated users about insurance premium payable
|
E
|
|
|
111
|
Ability to revalue an existing fixed asset or a group of fixed assets or all fixed assets belonging to a category or all fixed assets in the fixed assets register and ability to account the same as per defined business rules
|
D
|
|
|
112
|
Provision to record manufacturer's serial number
|
D
|
|
|
113
|
Provision to facilitate physical verification of fixed assets by printing fixed assets reports location-wise, employee-wise, category-wise etc
|
E
|
|
|
114
|
Ability to keep track of last physical verification data for each asset record
|
E
|
|
|
115
|
Create accounting automatically for fixed assets addition, depreciation, recategorisation, revaluation, retirement, transfers etc
|
D
|
|
|
116
|
Automatically interface accounting entries to the GL module
|
E
|
|
|
117
|
Facilitate drilldown facility from the GL to individual fixed asset transaction in the fixed asset module
|
C
|
|
|
118
|
System should support multiple depreciation methods including Straight Line Method, Written Down Value method, Unit of Production based method etc
|
E
|
|
|
119
|
Support change of useful life and effective rate of depreciation
|
E
|
|
|
120
|
Support change in depreciation rates
|
E
|
|
|
121
|
Support change in the method of depreciation
|
E
|
|
|
122
|
Ability to maintain multiple depreciation rates vis-à-vis the periods to which they apply and ability to calculate depreciation with retrospective effect wherever required
|
D
|
|
|
123
|
Ability to integrate Fixed Assets Module with Purchasing, Accounts Payable, General Ledger and budget module
|
C
|
|
|
124
|
Ability to generate asset details required for wealth tax purpose
|
D
|
|
|
125
|
Ability to make provisions against losses on retirement of assets in respect of Assets awaiting for disposal
|
D
|
|
|
126
|
Ability to capture expenditure under "Capital Work In Progress", till completion/ commissioning of Asset
|
E
|
|
|
127
|
Ability to transfer from CWIP to respective Asset Account on completion of work
|
E
|
|
|
128
|
Ability to link the insurance spares with the plant units and ability to generate alerts where spares are retained even after the asset has been sold
|
C
|
|
|
129
|
Ability to maintain component wise break up of the capitalised value of assets like original cost, installation cost, allocated amount of indirect expenditure, interest capitalised etc
|
E
|
|
|
130
|
Bank Master Maintenance - Ability to maintain list of approved banks
|
C
|
|
|
131
|
Ability to print Cheques with pre-printed stationary
|
C
|
|
|
132
|
Ability to generate alerts if cash balance exceeds particular amount
|
E
|
|
|
133
|
Ability to generate alerts if cash payment being prepared / authorised exceeds particular limit.
|
D
|
|
|
134
|
Ability to have cash verification
|
E
|
|
|
135
|
Ability to generate stale cheque report
|
E
|
|
|
136
|
Ability to adjust due dates for statutory payments like TDS/PF etc based on declared holidays by bank, VPT etc
|
E
|
|
|
137
|
Ability to reissue void/stale cheques with necessary controls as per defined business rules
|
E
|
|
|
138
|
Ability to handle e-payments/RTGS etc
|
C
|
|
|
139
|
Ability to handle digital signatures and ability to verify the same
|
E
|
|
|
140
|
Ability to account for the direct debits/ credits in the bank accounts in the cash book
|
E
|
|
|
141
|
Ability to verify the bank charges as per the business rules
|
E
|
|
|
142
|
Ability to integrate bank reconciliation system with the payment and collection recording modules to eliminate any duplicate data entry
|
C
|
|
|
143
|
Ability to integrate bank reconciliation system with General Ledger to consider any bank related journal entries such as those for bank transfers etc
|
E
|
|
|
144
|
Ability to load bank statements into system
|
E
|
|
|
145
|
Ability to enter items in bank statements manually
|
E
|
|
|
146
|
Ability to reconcile bank statement with payments, collections, adjustments etc recorded in the system based on the cheque number or such other reference number
|
E
|
|
|
147
|
Ability to generate bank reconciliation statement listing unreconciled transactions
|
C
|
|
|
148
|
Ability to forecast expected date of payment to vendors based on PO raised, expected date of delivery and invoice received from them
|
E
|
|
|
149
|
Ability to track details investments made along with details of amount invested, interest rate applicable, interest due dates, maturity date
|
C
|
|
|
150
|
Ability to support computation of interest due in respect of investments made
|
E
|
|
|
151
|
Ability to support tendering process for investments to determine highest interest rate quoted
|
E
|
|
|
152
|
Ability to upload exchange rates data from excel or any other system to ERP
|
E
|
|
|
153
|
Ability to capture and report costs against each dimension in the chart of account structure
|
E
|
|
|
154
|
Ability to define cost centers across the organization
|
C
|
|
|
155
|
Ability to define various elements of costs for cost sheet preparation
|
E
|
|
|
156
|
Ability to print various allocation schedules prior to the financial closing of the period
|
C
|
|
|
157
|
Ability to rerun cost allocations when the underlying data changes
|
E
|
|
|
158
|
Flexibility to accept new elements /parameters for preparation of cost sheets
|
D
|
|
|
159
|
Ability to support variance analysis between budget and actual across various periods
|
E
|
|
|
160
|
Ability to comply with the requirements of Cost Audit Record Rules
|
E
|
|
|
161
|
Flexibility for importing data from non-ERP system and vice-versa to prepare their budget at the department level, forward it for approval, modification and consolidation at the organization level with appropriate approval hierarchy at each level
|
E
|
|
|
162
|
Ability to maintain Capital as well as Revenue budgets
|
C
|
|
|
163
|
Ability to maintain record of each version of budget during it's preparation phase
|
D
|
|
|
164
|
Ability to maintain original budget, revised budget and latest forecast for each account
|
E
|
|
|
165
|
Ability to automatically generate a budget from previous years actual or budget with a percentage increase or decrease
|
E
|
|
|
166
|
Ability to view budget availability / utilization on a real-time basis
|
E
|
|
|
167
|
Ability to reappropriate budget across various budget heads.
|
C
|
|
|
168
|
Ability to prepare budget based on top-down / bottom-up approach
|
D
|
|
|
169
|
Ability to generate different types of variance reports (like actual vs. budget, actual on year to year and month to month basis etc as well as yield/ usage/ volume/ price reports etc)
|
E
|
|
|
170
|
Ability to compare budgets with figures for previous years on a year to year basis/month to month basis etc
|
C
|
|
|
171
|
Ability to restrict transfer/ reappropriation of budgets between capital and revenue items
|
E
|
|
|
172
|
Ability to allow enhancements to budgets by way of additions (i.e. additional budget requirement)
|
E
|
|
|
173
|
Ability to restore budgets if the allocated/sanctioned amount is left unutilised or on account of dropping/ revision of proposals
|
E
|
|
|
174
|
Ability to link expenditure/income with the respective budgets
|
C
|
|
|
175
|
Ability to do trend analysis over multiple periods
|
C
|
|
|
176
|
Ability to make what if scenario and modeling
|
E
|
|
|
177
|
Ability to summarize important assumptions used in preparation of various budgets (e.g. Price Increase, wage rate, capacity utilisation of each scenario for comparison purpose
|
D
|
|
|
178
|
Ability to facilitate zero based budgeting
|
E
|
|
|
179
|
Ability to prompt percentage exhaustion of the budget under various budgets
|
E
|
|
|
180
|
Ability to give forecasts based on the data available in the system for various elements of income and expenditure, both quantities and values
|
C
|
|
|
181
|
Ability to link expenditure/ income with the respective budgets
|
C
|
|
|
182
|
Ability to make what if scenario and modeling
|
C
|
|
|
183
|
Ability to facilitate budget revisions during the year
|
E
|
|
|
184
|
Ability to integrate with other modules for the required data for preparation of Budgets and variance analysis
|
E
|
|
|
185
|
Ability to record all revenue collected according to revenue heads
|
E
|
|
|
186
|
Ability to generation of report of all revenue collection according to revenue head
|
C
|
|
|
187
|
Ability to generation of forecast for revenue collection according to revenue head
|
E
|
|
|
188
|
Recording all outstanding revenue collection according to revenue head and party
|
E
|
|
|
189
|
Generation of report of all outstanding revenue collection according to revenue head
|
E
|
|
|
190
|
Closing of an accounting period for Financial Reporting.
|
C
|
|
|
191
|
Hard close or a soft close for an accounting period for Financial Reporting
|
D
|
|
|
192
|
Adjustments to closed periods for Financial Reporting.
|
D
|
|
|
193
|
Opening an accounting period for Financial Reporting
|
C
|
|
|
194
|
Standard reports and statements for Financial Reporting
|
C
|
|
|
195
|
Business performance statistics monitoring for Financial Reporting
|
C
|
|
|
196
|
Maintenance of investment register
|
E
|
|
|
197
|
Keeping track of Dates of maturity
|
E
|
|
|
198
|
Planning for optimum investments
|
E
|
|
|
199
|
Maintenance of debts register
|
E
|
|
|
200
|
Keeping track of Dates of payments due
|
C
|
|
|
201
|
Debts service planning
|
D
|
|
|
ESTATE MANAGEMENT
|
1
|
Creation of the allotable space (land parcels) of the port
|
C
|
|
|
2
|
Interface to graphical master land use plan using GIS package
|
C
|
|
|
3
|
Updation of available warehouse, office and land area for rental complete with details and layout plan
|
D
|
|
|
4
|
Application for rental of warehouse, office and land area electronically
|
D
|
|
|
5
|
Processing of the application, send reply or approval to the applicant electronically
|
E
|
|
|
6
|
Receiving application for renewal of Tenancy Agreement and sending reply or approval electronically
|
D
|
|
|
7
|
Viewing the draft Tenancy Agreement electronically
|
E
|
|
|
8
|
Monitoring and collection payment of rented warehouse, office, land etc
|
E
|
|
|
9
|
Generation of alert on overdue rental payment and reminder letter automatically.
|
E
|
|
|
10
|
Generate report on occupancy rate of warehouse, office and land area complete with layout plan.
|
E
|
|
|
11
|
Alerts before lease expiry date and generate reminder letter
|
C
|
|
|
12
|
Renewal of existing leases
|
C
|
|
|
13
|
Allotment of lands on tender or directly
|
C
|
|
|
14
|
Sub-leases
|
E
|
|
|
15
|
Occupation/ vacation
Renewal of existing lease
|
E
|
|
|
16
|
Demand and collection of rent
|
E
|
|
|
17
|
Allotment, occupation, vacation of quarters
|
C
|
|
|
18
|
Recovery of rent & electricity charges
|
C
|
|
|
19
|
Maintaining physical status of the estate – graphically through GIS package
|
E
|
|
|
20
|
Storage & retrieval of legal documents (Document Management System)
|
E
|
|
|
PROJECT MANAGEMENT
|
1
|
Ability to assign employees / resources to individual tasks
|
E
|
|
|
2
|
Ability to define, track and report on budget for each project at the lowest task level
|
E
|
|
|
3
|
Ability to track project expenses at the lowest task level
|
C
|
|
|
4
|
Facility to adjust costs booked to projects
|
E
|
|
|
5
|
Ability to restrict access to specific projects to specific users
|
E
|
|
|
6
|
Ability to restrict access to specific data in each project to specific users
|
E
|
|
|
7
|
Ability to keep project open across multiple accounting period and year
|
C
|
|
|
8
|
Ability to automatically generate alerts in case of deviation between actual project progress and project schedule
|
C
|
|
|
9
|
Ability to monitor the milestone payments to contractors as per the billing schedule
|
E
|
|
|
10
|
Ability to enable project capitalization on completion or in phases
|
D
|
|
|
11
|
Ability to add project created asset to existing fixed asset(s) e.g. extension to existing building, adding child asset to an existing machinery
|
E
|
|
|
12
|
Ability to link multiple projects
|
E
|
|
|
13
|
Ability to link fixed assets assigned to the project from the fixed assets register
|
E
|
|
|
14
|
Ability to capture expenditure as “Capital Work in Progress”(CWIP) till completion/ commissioning of asset
|
E
|
|
|
15
|
Ability to track expenditure with reference to a particular asset for which different job codes exists
|
E
|
|
|
16
|
Ability to track expenditure in respect of each individual asset where a single job code is applicable for all such assets
|
D
|
|
|
17
|
Ability to track materials issued to contractors vis-à-vis actual utilisation
|
D
|
|
|
18
|
Ability to track reasons for any amendment to contracts
|
D
|
|
|
19
|
Ability to furnish analysis of cost over runs
|
E
|
|
|
20
|
Ability to calculate the recoveries on account of LD and Milestone penalties as per the contract
|
E
|
|
|
21
|
Ability to track payment terms for each BOQ and adhere till completion of contract
|
E
|
|
|
22
|
Ability to track advance payment and automatic adjustments of the same while billing and payments to contractors periodically.
|
E
|
|
|
23
|
Ability to link with BG Module and provision to release the value of BG based on the advance settlement
|
E
|
|
|
24
|
Ability to capture tax amounts or rates in the contract and calculate the variations if any on amendments
|
E
|
|
|
25
|
Ability to provide for liability based on work completion certificate issued by Engineer in Charge
|
D
|
|
|
26
|
Ability to create liability for the work done based on the online certification
|
D
|
|
|
27
|
Integration with bill passing module to interface costs being incurred on the project
|
E
|
|
|
28
|
Integration with the fixed asset register to assign fixed assets to the project and to capitalize projects
|
E
|
|
|
29
|
Integration with the General Ledger to interface accounting entries
|
C
|
|
|
30
|
Integration with purchasing module to link requisitions / purchase orders to specific projects and tasks
|
C
|
|
|
31
|
Integration with the HR management module to enable assignment of employees to specific projects
|
E
|
|
|
32
|
Integration with the inventory management module to interface inventory transactions related to projects
|
E
|
|
|
33
|
Integration with MS Project
|
D
|
|
|
34
|
Integration with Mobile Computing to allow job inspections to be carried out in an offline / online mode
|
D
|
|
|
35
|
Ability to generate engineering estimates and budgets for new projects
|
E
|
|
|
36
|
Ability to process and manage tenders for new projects.
|
D
|
|
|
37
|
Ability to analyze bidder responses and document the award process
|
D
|
|
|
38
|
Ability to import awarded tenders into contract manager for tracking purposes
|
D
|
|
|
39
|
Must have the ability to map discounts at the BOQ level
|
D
|
|
|
40
|
Must have the ability to support up to 3 dimensions for each BOQ
|
E
|
|
|
41
|
Must have the ability to assign activities for each BOQ item that can be scheduled
|
D
|
|
|
42
|
Each BOQ item must support the documentation of components during BOQ creation
|
D
|
|
|
43
|
The system must ensure that an estimate is locked prior to tendering the estimate
|
E
|
|
|
44
|
The system must support the creation of estimate addendums
|
D
|
|
|
45
|
Ability to synchronise the work progress captured in the handheld device to the project monitoring system
|
D
|
|
|
Share with your friends: |
