|
|
| (15 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | [[Category:OpsPdfs]] | + | [[Category:Ops Pdfs Old]] |
| | | | |
| - | == Mantis ==
| + | This is original old spec. Content has been hidden. To view - see history. |
| - | [http://mantis.jaguarfreight.com/mantis/view.php?id=575 575]
| + | |
| - | | + | |
| - | == Business Needs and Requirements ==
| + | |
| - | | + | |
| - | === Definitions ===
| + | |
| - | (wikipedia) International AWBs that contain consolidated cargo are called master air waybills (MAWB). MAWBs have additional papers called house air waybills (HAWB). Each HAWB contains information of each individual shipment (consignee, contents, etc.) within the consolidation. International AWBs that are not consolidated (only one shipment in one bill) are called simple AWBs. A house air waybill can also be created by a freight forwarder. ''When the shipment is booked, the airline issues a MAWB to the forwarder, who in turn issues their own house air waybill to the customer''.
| + | |
| - | | + | |
| - | (export911) The freight forwarder may consolidate the consignments of several independent shippers that are intended for the same airport of destination and dispatch them together under one air waybill (AWB) issued by the carrier, known as master air waybill (MAWB), with a cargo manifest detailing such consignments attached to the MAWB. '''The freight forwarder in turn issues to each shipper its own AWB, known as a house air waybill (HAWB) or freight forwarder's waybill.'''
| + | |
| - | | + | |
| - | In the case of air freight using a house air waybill (HAWB), just like in ocean freight using a house bill of lading (the freight forwarder's bill of lading), it is the freight forwarder's handling agent at destination, not the carrier, who notifies the consignee of the cargo arrival at destination.
| + | |
| - | | + | |
| - | == Technical Specification ==
| + | |
| - | === Summary ===
| + | |
| - | === Template ===
| + | |
| - | ==== Template Top Section ====
| + | |
| - | ==== Template Bottom Section ====
| + | |
| - | === Pdf ===
| + | |
| - | ==== Header ====
| + | |
| - | ==== Top Section ====
| + | |
| - | ==== Bottom Section ====
| + | |
| - | ==== Footer ====
| + | |
| - | === Special case: Groups ===
| + | |
| - | == Additional Figures ==
| + | |
| - | === Figure X ===
| + | |
| - | == History ==
| + | |
| - | | + | |
| - | === Archive ===
| + | |
| - | http://mantis.jaguarfreight.com/wiki/Air_M_MAWBL
| + | |
| - | | + | |
| - | === Several bug fixes and changes requested by Paris office ===
| + | |
| - | * Parent mantis for a group of tasks: http://mantis.jaguarfreight.com/mantis/view.php?id=1093
| + | |
| - | | + | |
| - | * Add office specific airline fields
| + | |
| - | ** http://mantis.jaguarfreight.com/mantis/view.php?id=1602
| + | |
| - | ** see "Airlines Entity with Office fields.JPG" attached to mantis. This is one option. Alternatively we could add "per Office Admin" (Admin > Paris Admin, etc) where each office would maintain its local settings
| + | |
| - | | + | |
| - | * Add new fields: carrier’s headquarter address; carrier's IATA code; carrier’s account number
| + | |
| - | ** http://mantis.jaguarfreight.com/mantis/view.php?id=1603
| + | |
| - | ** add these to template and pdf (top right corner near "AirWayBill")
| + | |
| - | ** mappings as defined in mantis#1602
| + | |
| - | | + | |
| - | * 1) Add JFS PARIS IATA code into the system 2) pull it into MAWB and HAWB automatically
| + | |
| - | ** http://mantis.jaguarfreight.com/mantis/view.php?id=1604
| + | |
| - | ** Add this into Admin > Office Profile OR Admin > Paris Admin
| + | |
| - | ** pull this into "Agent's IATA code" field on template for HAWB / MAWB
| + | |
