Transport Module Blueprint
Table of Contents
Introduction
The Caribbean Disaster Emergency Management Agency (CDEMA) Is looking to use Sahana Eden as the basis for its Regional Logistics Tool (RLT). The RLT will be built from a set of collected data from the entire region. The Regional Logistics Tool will initially include information on:
- Critical Infrastructure in CDEMA Participating States (seaports, airports, etc.)
- Location and capacity of Public and Private Sector organizations (including assets, equipment and vehicles)
- Location, capacity and supply inventory of Sub Regional Focal Points, including staging areas
- Library of existing MOUs, associated vessels and transport routes in the region.
The proposed transport module will be designed as the repository of this data. The primary purpose of the transport module is to record data about important locations related to logistics and transport. This includes airports, seaports and key land transport locations - such as international border crossings/checkpoints.
CDEMA is currently collecting baseline data on airports, seaports, border crossings, shipping lines and airlines, warehouses and cold storage facilities.
This collection of data will be in constant evolution and over time they may expand their data collection to include:
- Hospitals
- Fuel depots
- Sources of communication
- Preferable roads and routes
- Shelters
- Alternate warehouses
- Military resources, police resources and other institutions
Description
The Transport Module will provide a registry for recording logistics location information, primarily for the following types of facilities:
- Airports
- Seaports
- Land Border Crossings.
- Warehousing (Warehousing may include Cold Storage Facilities and Staging Areas)
These are facilities where goods enter into a country/city and may be stored locally in a warehousing situation, or enter the road/ground transportation network for shipment to its final destination.
The Transport module will need to link these resources to contact information (both persons and to several types of organizations - such as airlines, sealines, ground transportation companies, as well as the owners and operators of the facilities). It will also store information about customs requirements, forms and existing MOUs for transport (all documents).
Requirements
Airport Data
The following data needs to be stored and be viewable about Airport resources:
| Data Element | Description |
|---|---|
| Airport Name | Airport Name |
| Airport Code | Designator, e.g. JFK, EWR, LHR |
| Airport Type | International, Regional, Local, Military |
| Airport Ownership | Public, Private |
| Airport Operator | Link to an ORG record |
| Airport Operation | Status - operational, closed |
| Airport Authority Contact Name | Link to a PR record |
| AIrport Authority Contact Title | Job Title of linked PR record |
| Airport Authority Contact Number | Main Telephone Number of linked PR record |
| Airport Location (lat/long) | Link to Street Address and Location (point on map) |
| Airport Elevation | Feet or Meters above sea level |
| Airport Runway Surface | configurable drop-down list - Asphalt, Concrete, Dirt + Need to allow for multiple runway records per airport |
| Airport Runway Length | Length in Feet or Meter + Need to allow for multiple runway records per airport |
| Airport Runway Direction | Numeric 360 degree heading + Need to allow for multiple runway records per airport |
| Airport Fuel Availability | configurable drop-down list - JetA1, Avgas, other options |
| Airport Fuel Cost | cost per liter/gallon for each type of fuel |
| Airport Restrictions | open paragraph field for listing information |
| Airport ILS | YES/NO |
| Airport Lighting | YES/NO |
| Airport Working Hours | Text Field or more sophisticated option would be to record hours on daily basis (which could differ) |
| Airport Immigration and Customs Capabilities | Paragraph text field |
| Airport Immigration and Customs Information | Link to documents that can be uploaded (customs forms, visa forms, regulations, etc.) |
| Aircraft Maximum Size | Paragraph text field |
| Airport Loading Equipment | Forklifts (#, capacity); Scissors Lifts (#, capacity); Cargo dollies (#); Trucks (#), Laborers for hand loading (#) |
| Airport Security | Paragraph text field for description of perimeter fencing, security guards, security lighting |
| Airport Storage | capacity (m3), covered, uncovered |
| Airport Parking / Tarmac Space | capacity (# of planes, m3) |
| Airport Helipad information | paragraph text field |
| Airline | Link to airline (company or ORG record) that provides service to this airport + can link to multiple records - link table as component tab |
| Trucking Line | Link to Trucking line (company or ORG record) that provides service to this airport + can link to multiple records - link table as component tab |
| Information Source | Link to a PR record - who provided this information |
Seaport Data
The following data needs to be stored and be viewable about Seaport resources:
| Data Element | Description |
|---|---|
| Seaport Name | Seaport Name |
| Seaport Ownership | Public, Private |
| Seaport Operator | Link to an ORG record |
| Seaport Operation | Status - operational, closed |
| Seaport Authority Contact Name | Link to a PR record |
| Seaport Authority Contact Title | Job Title of linked PR record |
| Seaport Authority Contact Number | Main Telephone Number of linked PR record |
| Seaport Location (lat/long) | Link to Street Address and Location (point on map) |
| Seaport Operating Hours | Text Field or more sophisticated option would be to record hours on daily basis (which could differ) |
| Seaport Max Height | in feet or meters |
| Seaport Roll On Roll Off Berth | YES/NO? |
| Seaport Depth | in feet or meters (by high tide, low tide and flood depth) |
| Seaport Cargo Pier Depth | in feet or meters |
| Seaport Oil Terminal Depth | in feet or meters |
| Seaport Dry Dock | YES/NO? |
| Seaport Vessel Max Length | in feet or meters |
| Seaport Repairs | Paragraph text field |
| Seaport Shelter | Paragraph text field |
| Seaport Storage | capacity by type - warehousing, secure storage, customs warehousing |
| Seaport Loading Equipment | Paragraph text field |
| Seaport Cranes | height, span, max load |
| Seaport Tugboats | number, capacity |
| Seaport Barges | number, capacity |
| Seaport Customs Capacity | Paragraph text field |
| Seaport Customs Information | Link to documents that can be uploaded (customs forms, regulations, etc.) |
| Seaport Security | Paragraph text for perimeter fencing, security lighting, security guards |
| Shipping Lines | Link to Shipping Line (company or ORG record) that provides service to this seaport + can link to multiple records |
| Trucking Line | Link to Trucking line (company or ORG record) that provides service to this seaport + can link to multiple records |
| Information Source | Link to PR record of person providing the above information |
Warehousing
The following data needs to be stored and be viewable about Warehousing resources (much of this may already be implemented by existing warehouse information in Eden):
| Data Element | Description |
|---|---|
| Warehouse Name | Name Field |
| Warehouse Type | configurable drop-down - covered, uncovered, staging area |
| Cold Storage Facility | Flag (checkbox) |
| Warehouse Location (lat/long) | Link to Street Address and Location (point on map) |
| Warehouse Contact Person | Link to a PR record |
| Warehouse Telephone | Telephone Number at Warehouse |
| Warehouse Fax | Fax Number at Warehouse |
| Warehouse email | email address for Warehouse |
| Warehouse Size | capacity (m3) |
| Cold Storage Size | Cold storage capacity (m3) |
| Trucking Line | Link to Trucking line (company or ORG record) that provides service to this warehouse + can link to multiple records |
| Information Source | Link to PR record of person providing the above information |
Border Crossings
The following data needs to be stored and be viewable about Border Crossing locations:
| Data Element | Description |
|---|---|
| Name of Border | Name of Border Crossing |
| Border Contact Person | Link to a PR Record with Name, Title, Contact information |
| Border Telephone | Telephone Number at Border Crossing |
| Border Fax | Fax Number at Border Crossing |
| Border email | email address at Border Crossing |
| Border Crossing Immigration and Customs Capacity | Paragraph text field |
| Border Crossing Immigration and Customs Information | Link to documents that can be uploaded (customs forms, visa forms, regulations, etc.) - Facilities are already doc_entities, so docs can be a component tab |
| Trucking Line | Link to Trucking line (company) that provide cross-border shipping at this border crossing + can link to multiple records - link table as component tab |
| Information Source | Link to PR record of person providing the above information |
Transport Line Information
Information on shipping (sea), air (air) and trucking (land) lines (companies) needs to be recorded to the following linked organization types. Airlines, Shipping Lines and Trucking Lines are Organizations, which may have organization contacts, as well as offices, with office contacts, and staff with individual staff contacts. No special changes may be needed to the ORG/OFFICE or HRM registries in order to implement these contact features for Airlines, Shipping Lines or Trucking Lines. There are specific routing, MOU, cost information that are, however, going to be unique to an organization with a type of an Airline, Shipping Line or Trucking Line. The following schema requirements come from how CDEMA is currently collecting information on these types of organizations as a part of their baseline assessment.
Airline
| Data Element | Description |
|---|---|
| Name of Airline | Airline Name |
| Airline Owner | Link to ORG or PR record |
| Airline Contact | Link to PR record |
| Airline Telephone | Airline Telephone |
| Airline Fax | Airline Fax |
| Airline email | Airline email address |
| Airline Offices | Link to Airline Offices (could be multiple) - link table as component tab |
| Airline Airport Service | Link to Airport records (above) that Airline Services - link table as component tab |
| Airline Schedule | Flys from/to information, may include cost and capacity specific to each route - add details to the link table |
| Airline MOUs | Link to documents that can be uploaded documenting agreements and pricing with airlines - make Airline a doc_entity & then docs can be a component tab |
Shipping (Sea) Line
| Data Element | Description |
|---|---|
| Name of Shipping Line | Shipping Line Name |
| Shipping Line Owner | Link to ORG or PR record |
| Shipping Line Contact | Link to PR record |
| Shipping Line Telephone | Shipping Line Telephone |
| Shipping Line Fax | Shipping Line Fax |
| Shipping Line email | Shipping Line email address |
| Shipping Line Home Port | Home Port of the Shipping Line (Link to an OFFICE) [Home Port would be Headquarters Office of the Organization] |
| Shipping Line Offices | Link to Shipping Line Offices (could be multiple) - use link table as component tab |
| Shipping Line Ports of Entry | Ports that Shipping Line provides service to (link to multiple Seaports (above)) - use link table as component tab |
| Shipping Schedule | Ships from/to information, may include cost and capacity specific to each route - add this detail to the link table |
| Shipping Line MOUs | Link to documents that can be uploaded documenting agreements and pricing with Shipping Lines - make Shipping Line a doc_entity & then docs can be a component tab |
Trucking Line
| Data Element | Description |
|---|---|
| Name of Trucking Line | Trucking Line Name |
| Trucking Line Owner | Link to ORG or PR record |
| Trucking Line Contact | Link to PR record |
| Trucking Line Telephone | Trucking Line Telephone |
| Trucking Line Fax | Trucking Line Fax |
| Trucking Line email | Trucking Line email address |
| Trucking Line Offices | Link to Office (could be multiple) - use link table as component tab |
| Trucking Line Locations Serviced | Links to Airports, Seaports, Warehouses and Border Crossings that Trucking Line services (multiple link possible) - use link table of Facilities as component tab |
| Trucking Line MOUs | Link to documents that can be uploaded documenting agreements and pricing with trucking lines - make Trucking Line a doc_entity & then docs can be a component tab |
| Shipping Schedule | Ships from/to information, may include cost and capacity specific to each route |
Use-Cases
<Describe actors and use-cases> <Describe workflows> <Include diagrams where useful>
Design
<Describe a possible design, repeat any design sections for alternative designs> <Include diagrams, screen mockups and wireframes where useful>
Implementation
<Leave open for a list of implementation>
References
<Links to external resources>
