USC-8_PWS_Contingency_Annex_DRAFT_Dec_2014.pdf

USC-8 Contingency AnnexContingency Annex

USC-8 CONTINGENCY ANNEX

Formatted: Right

A. CONTINGENCY ANNEX

A.1. Preamble – Scope / Declaration of Exigency Area

A.1.1. The provisions of Tthis annex shall apply to any and all geographic areas designated by the Commanding General (CG) of SDDC as Exigency Areas. These provisions shall supersede any conflicting terms or conditions of this contract and shall take precedence over same. All other terms and conditions of this contract not in conflict with this section shall also apply to Exigency Areas.

A.1.2. The SDDC CG may designate any geographic area as an Exigency Area, which may include any geographic area in which contingency operations are being conducted and any geographic area that is used as a primary staging area for such operations. Areas designated as “Exigency” will remain so until such designation is rescinded by SDDC CG. The Contracting Officer shall notify the Contractor in writing of each Exigency Area determination or rescission. The notification shall include geographic area of exigency and effective date of exigency at a minimum.

A.1.3. The first part of this annex applies to all Exigency Areas, regardless of location. The remaining parts apply only to specific Exigency Areas, and are organized by COCOM. Provisions of this contract that are specific to a geographic area and are intended to apply to such an area in both ordinary and Exigency conditions will not appear in the Exigency Annex. For example, a provision that is intended to apply to Afghanistan even in the event that its status as an Exigency area is rescinded will not appear in the Exigency Annex.

A.1.4. The provisions of tThis annex shall apply to cargoequipment booked under the contract to areas designated as Exigency Areas. The Exigency Areas designations shall apply prospectively to cargoequipment with a vessel sail date on or after SDDC’s declaration of an Exigency Area.

A.1.5. If there is a conflict between the main part of the Exigency Annex, and the COCOM-specific portion of the Annex, the COCOM-specific portion shall prevail.

B. APPLICABLE TO ALL EXIGENCY AREAS

“B.10” Mandatory Acceptance of Bookings, Government-Furnished Containers

In the case of urgent and compelling circumstances or in the interest of National Defense or Security, bookings to contingency areas must be accepted, as indicated by the Contracting Officer or Ordering Booking Officer. Should the bookings consist of Government-Furnished containers (GFC), the contractor shall provide the same level of service to the carriage of cargo in GFC that is provided to the carriage of cargo in the Contractor’s container. If a single vessel carries more than 200 GFCs, a surcharge of 5% of the ocean charge shall apply to containers beyond the first 200 containers.

B.21. Leasing of Containers

B.21.1. In the case of urgent and compelling circumstances or in the interest of National Defense or Security, the Contracting Officer may require, and the contractor must furnish, 20 or 40-foot dry cargo containers and chassis for use in connection with land and ocean transportation of Government cargo.

Requirement to lease containers will be conveyed to the contractor during the booking process. Containers may also be converted to a lease in lieu of purchase under paragraph 3.G.9 for containers required for storage and deemed not practical to immediately return and where the Contracting Officer does not desire to purchase them. Under these circumstances, the Government will require full support of contractors, but acknowledges their satisfactory compliance with this requirement with leasing of at least 50 FEUs to include chassis for any one voyage. Unless otherwise agreed, the Government will return containers and other equipment leased by the Government to the place where such equipment was originally received from the contractor or at the seaport of debarkation of the country where the container was shipped to

Formatted: Right or any other location within a theater of operations as mutually agreed upon by the carrier and the Contracting Officer.

B.21.2. The Contractor will be paid at the equipment lease rate of $9/day for dry containers, and $15/day for reefer containers. The contractor must be paid at the equipment leasing rates set forth below for equipment leased under this provision. The contractor must be paid for each 24-hour calendar day or part thereof for the period between the time the equipment is received or ordered from the contractor, whichever is later, until the time the equipment is returned to the contractor.

B.21.3. The Government will return containers/equipment in the same condition as received.

B.32. Container Detention

Free time for the purposes of calculating container detention shall be 40 days for Dry containers and 35 days for Reefer containers, commencing at 0001 on the first calendar day after the container is discharged from the vessel at the Port of Debarkation, with the exception of cargo entering Afghanistan from countries other than Pakistan, as detailed in the CENTCOM section of this Annex. Free time/detention will run during any staging or authorized US Government caused delay in accordance with Attach 1.

B.43. Container Pick Up/Return

B.43.1. The U.S. Government and the Contractor agree that it is in their mutual best interests to facilitate the prompt return and pickup of empty containers at the original point of delivery. To achieve this goal, the Contractor will use commercially reasonable efforts to position trucks at FOBs to evacuate empty containers within 7 calendar days after receiving notice from the U.S. Government that the container is available at the original point of delivery. In addition, the US Government will use reasonable efforts to load empty containers onto trucks that the Contractor positions to evacuate empties, including trucks that have delivered loaded containers at the FOB as well as trucks dispatched to pick up empties.

B.43.2. To manage and monitor progress towards achieving prompt return and pickup of empty containers, the U.S. Government and the Contractor will exchange weekly reports in mutually agreed formats. Among other things, the reports may identify loaded containers delivered, loaded export containers picked up, empty containers notifications, empty containers picked up, and trucks leaving FOBs without loaded or empty containers.

B.43.3. At regular intervals as may be mutually agreed upon, the U.S. Government and the Contractor will meet to review and discuss empty return and pickup performance. Corrective action plans will be jointly developed to address any significant deficiencies in the Contractor’s performance in positioning trucks to pick up empty containers or the U.S. Government’s performance in loading empty containers on the Contractor’s trucks.

B.43.4. At locations where the U.S. Government has automated system capability to report that containers are empty and request their pickup, the dates documented by the system will be the official date/time of notification unless the Contractor has been provided earlier written notice from the U.S. Government.

Contractor personnel will obtain passwords as needed to access these systems. In order to assist with container accountability, as requested by the Contractor, the US Government will provide a regular, weekly report showing all loaded containers delivered and empty containers picked up from specific installations.

B.43.5. The Contractor will report pickup of empty containers in accordance with Attachment 1 for EDI shipment status reporting. Additional written reports may be required upon Government request.

B.43.6. The Contractor will notify the U.S. Government of its pick up of empty reefer containers from the consignee’s location if such pick up occurs without the genset being attached to the reefer. Notification will be made to the cognizant SDDC Battalion and COR within three calendar days from the time the reefer is picked up without its genset, or via a weekly report as mutually agreed upon.

Formatted: Plain Text, Adjust space between Latin and Asian text, Adjust space between Asian text and numbers

Formatted: Right

B.54. Call Forward Cargo

Contractor will provide a dispatch plan to cognizant COR and SDDC Battalion if unable to dispatch all called forward cargo within 5 calendar days of the call forward.

B.65. Staging

B.65.1. Billing will cease upon generation of the HR EDI code or 5 calendar days after receipt of the call forward message even if cargo has not dispatched from staging location, whichever occurs first.

B.65.2. The Contractor may submit a constructive staging request to the cognizant COR via the D-RAP if cargo is not in-gated within 72 hours of arrival at base gate. If an authorization is not approved or denied by the SDDC COR in the D-RAP within 2 business days, the HG transaction will be auto-generated and distributed. The Contractor must submit supporting documentation with the constructive staging request submitted via the D-RAP. The COR may void the constructive staging authorization if supporting documentation showing adequate justification is not provided.

B.76. Carrier Holding Yards

B.76.1. Contractors will provide detailed information of all carrier holding yard locations (including latitude/longitude) that will be used to store U.S. Government cargo to cognizant COR and SDDC Battalion.

B.76.2. Contractors will provide standard commercial security service at carriers’ holding yards.

B.76.3. Contractors will provide a Daily Carrier Holding Yard Report to cognizant SDDC Battalion as advised by COR on cargo that is stored in carriers’ holding yards until cargo is dispatched for onward movement.

B.76.4. Carrier Holding Yard Report format: The Contractor shall provide report in a separate Excel spreadsheet. Columns will include: type/description of cargo, TCN, container number (if applicable), PCFN, booking number, origin/destination, POE/POD, shipper DoDAAC, receiver DoDAAC, vessel discharge date, date cargo moved from port to carrier holding yard location, date cargo arrived at carrier holding yard location, date cargo departed carrier holding yard location whether it’s moving to another carrier holding yard location or final destination.

B.76.5. For invoicing purposes, carrier holding yard rates will only apply to import/export cargo when a Staging Request has been received from the cognizant COR or when the cargo is constructively staged in accordance with the Staging Section.

B.76.6. Contractor will not bill carrier holding yard fees concurrently with driver wait time fees.

B.76.7. Lift-Off fees shall apply when the cargo is lifted off a truck for storage into the carrier holding yard upon written staging request by the cognizant COR.

B.76.8. Lift-On fees shall apply when cargo is lifted on to a truck to commence dispatch to final destination when on-carriage from carrier holding yard has been requested by COR or cognizant SDDC Battalion.

B.87. Driver Wait Time

B.87.1. Free time shall start when the driver is in line outside the final destination waiting to deliver cargo and Contractor provides notice by submitting an "AV" EDI transaction that the cargo is locally available for immediate delivery but is delayed by the US Government.

B.87.2. The receiver shall have free time for the day that driver arrived in line outside final destination.

Starting at 0001 on the day following arrival in line, the Contractor shall be paid waiting time at $100 per day.

B.87.2.1. Driver wait time shall end when:

1. The cargo is removed from the container or conveyance and the Contractor submits an X1 EDI transaction in accordance with Attachment 1; or

2. The cargo is removed from the container or conveyance and an HG EDI transaction for staging start has been auto-generated by the D-RAP in accordance with Attachment 1.

B.87.3. Driver wait time applies only to charges incurred when the driver is physically in line outside the final destination waiting to deliver cargo. For all other situations, the contractor may submit a request for an equitable adjustment.

B.87.4. Shipments delivered with evidence of tampering or loss shall be investigated by base security;

drivers may be detained for questioning by base security. If investigation determines no tampering occurred, applicable wait time rates will be paid. If the investigation determines that tampering/pilferage has occurred, wait time will not be payable.

B.87.5. Invoices for driver wait time will be submitted in accordance with Attachment 6.

B.87.6. Invoices for driver wait time shall also be permitted on a case-by-case basis for stoppages in transit if a compensable delay is approved in advance by the COR through the DRAP process.

B.98. Daily Intransit Visibility (ITV) Reports

B.98.1. Inland ITV Reports are required for cargo moving to any exigency area, and is included in the linehaul rate. Should these reports not be required for a particular contingency, the contractor will be advised by the Contracting Officer.

B.98.1.1. The Contractor shall report each shipment daily by providing event reports or location information as set forth below.

B.98.2. Reporting method/format. The Contractor shall report via the Contractor ITV Entry Tool (CIET), for import and export routes available in CIET, or via separate Excel spreadsheets for new routes not yet available in CIET.

B.98.2.1. Reportable events shall include the dates for the following events: vessel arrival, cargo discharge, cleared by customs, out-gate from port of debarkation, arrival at consignee (import cargo), requested pickup (export cargo), origin departure, in-gate, vessel lift, vessel sail (export cargo) and transit of Contractor waypoints (import and export).

B.98.2.2. The following information must also be included: IBS TCN, container number with prefix (if applicable), PCFN, booking number, type/description of cargo, Enhanced ITV tag number (when ordered), origin and final destination, POE and POD, shipper Department Of Defense Activity Address Code (DODAAC), consignee DODAAC, current truck number and border crossing date, and each applicable event.

B.98.2.3. Contractor shall provide exception information (location, remarks, and dates) providing shipment status for the previous 24 hours or shipment information that had not been included previously.

Exception information is required only when there is no event report for the prior day. Remarks can be used to advise of cargo exception information but would not replace notifications otherwise required per the contract. When inputting exception information in CIET, the Contractor shall use the remarks block which can be updated as a single shipment record or as part of a grouping of shipment records. Completed

Formatted: Right shipments may be deleted 30 days after delivery when being reported using the excel spreadsheet reporting method.

B.98.3. Spreadsheet reports shall be provided by email attachments to a distribution list provided by the cognizant COR.

B.109. Standard Security

B.109.1. Security at Sea for SRC I and II shipments

B.9.1.1. Upon demonstrating a need to know to the plan owner, in accordance with 49 CFR 1520, ocean carriers transporting classified/sensitive and SRC I and II shipments, as defined in the Defense Transportation Regulation through high risk waters will provide a copy of the ship's vessel security plan (VSP) with Piracy Annex to SDDC-G2. Plans will be provided by email attachments to distribution as provided by SDDC-G2. VSPs will be copied to SDDC-G2 after the plan is approved by the USCG Marine Safety Center.

B.110. Inland Transit Security

B.110.1. The Contractor shall be responsible for the safe delivery of all cargo booked under this contract and shall employ security methods that can normally be expected to minimize pilferage and banditry.

Contractor shall be responsible for all damage to and loss of cargo while in the physical custody of the Contractor, his agents or assigns, including but not limited to losses caused by pilferage, or theft.

B.110.2. The Contractor shall report to the cognizant BDE and SDDC HQ any loss of cargo, breach of sealed containers, or hijacking of cargo within 48 hours3 days of when the Contractor becomes aware of the event. If the Contractor fails to report such loss, breach, or hijacking, the US Government may exclude the Contractor from consideration for future bookings as detailed at Section 5 above.

B.110.3. The Contractor shall include the cost of Standard Inland Transit Security in its basic linehaul rates.

B.11. Enhanced In-Transit Visibility (ITV) and Cargo Security

B.11.1. Enhanced Security Services

Enhanced Security Services include measures above and beyond the Standard Security measures required by B.9. These services include two separately priced accessorials: Enhanced ITV Services (described in paragraph B.11.2.1 below) and Enhanced Physical Security (described in paragraph B.11.2.2 below). These added security services are intended to eliminate pilferage and prevent banditry; to provide the time and location where losses occur, to assist law enforcement in the prosecution of offenders and recovery of goods and to guide future route selection decisions. These accessorial services shall be limited to Pakistan Ground Lines of Communication overland linehaul services to and from Afghanistan via sea ports in Pakistan.

B.11.2. When ordered by the US Government or its authorized booking agents as a contracted Accessorial Service, the Contractor shall provide Enhanced ITV Services as detailed below:

1. Automated Location Reporting, to include:

a. Position Calculation via GPS every 15 minutes with data queued for later transmission;

b. Communication from cargo via satellite shall include devices capable of transmitting position reports every 30 minutes with no interruption in service for the entire transit from origin to POE;

Formatted: Right

c. Reporting Frequencies shall include multiple options ranging from 30 minutes to six hours. Transmission must include all queued position reports.

d. Communication to Government must be automated via interface with IRRIS and iSDDC.

e. Transponders: Attached to Cargo (vice conveyance)

2. Intrusion Detection (Containers Only), to include:

a. Electronic or Automated Detection of intrusion or tampering;

b. Communication from device to transponder;

c. Automated communication to government via approved interface immediately upon detection of intrusion;

d. Archived record of events to include time and location; and

e. Installation and arming of devices

3. Position/Status Data Reporting, to include:

a. Position/Status reports that shall feed into IRRIS and iSDDC using secure FTP XML, web service, or other format acceptable to IRRIS and iSDDC. Data transmitted to IRRIS and iSDDC must include:

Device identifier, Shipment identifier (Container number or TCN) Date/time in ZULU format, Location information in decimal latitude/longitude format Status/event codes to report when intrusion is detected and (optional) any other shipment events or status.

b. Status code definitions and test data provided to the IRRIS PMO upon contract award and two weeks prior to any scheduled movement for subsequent code changes.

c. Functional Points of Contact for the IRRIS PMO are Ms. Karen Timmons at 618-220- 5116 and Mr. Phil Krueger at 618-220-5216 for review of alternate feed formats, coordination of system interfaces and testing.

d. Functional Points of Contact for the iSDDC PMO are Mr. Christopher Heiby at 618- 220-5632 and Ms. Tina Woodbury at 618-220-5673 for review of alternate feed formats, coordination of system interfaces and testing.

This accessorial shall be applicable when ordered and may be used for Unit Cargo Moves, Sustainment Cargo Moves, or Retrograde Cargo Moves.

B.11.3. When ordered by the US Government or its authorized booking agents as a contracted Accessorial Service, the Contractor shall provide Enhanced Physical Security as detailed below:

1. Convoy Movement Security planning and execution;

2. Secure enroute checkpoints to include cargo inspection and daily reporting of checkpoint activity;

3. Contractor provided special security devices, bolts, seals and/or procedures used to detect and reduce pilferage (Containers Only);

4. Back-up truck and driver capability to recover from truck or driver disability;

5. Truck operations that incorporate:

a. Route planning to avoid reported threats;

b. Waypoint ETAs and status checks for overdue trucks;

c. Continuous contact with drivers and escorts;

d. Secure facilities for overnight rest; and

Formatted: Right

e. Immediate response to driver disability, equipment damage or breakdown.

1. Upon indication of deviation from planned route, unplanned delays in movement, loss of contact, pilferage, attack, security breech, or any other indication that the cargo has been compromised, the Contractor shall immediately notify the cognizant SDDC Group Operations Center of same and provide detailed information to include:

Time and location of incident;

Details of the incident;

Container numbers or breakbulk TCNs involved;

Proposed corrective action;

Impact to delivery schedule; and Follow-on report within 24 hours with reports continuing every 24 hours until the cargo is recovered or the customer suspends the reporting.

Screened Personnel to include drivers, escorts, and checkpoint and tracking personnel.

B. APPLICABLE TO EXIGENCY AREAS WITHIN CENTCOM

B.132. Free Time

For cargo containers consigned to Afghanistan via any border crossing except Pakistan, free time of 35 days for dry containers and 30 days for reefer containers shall commence at 0001 the first calendar day after outgate/departure from Afghanistan border crossing.

B.143. Outer Routing Accessorials

When ordered by the Ordering Officer, the Contractor shall deliver cargo to the final destination via the routing named in the Accessorial. Outer Routing Accessorial is ordered in addition to the linehaul and covers all additional costs for the alternate routing (i.e., additional fuel, linehaul, security, ITV, travel time etc.).

B.143.1. Chaman – shall be ordered when cargo destined for/from provinces in Afghanistan with a normal routing thru Torkham is being re-routed via Chaman. (Example: Torkham normal routing for cargo destined to Faryab, Jawzjan, Balkh, Sari Pul, Samangan, Bayman, Parwan, Kapisa, Panjshir, Nuristan, Konar, Nangarhar, Paktya, Ghazni, Paktika, Kundz, Baghlan, Wardak, Kabul, Logar, Khowst, Takhar, Badgkhshan, Laghman).

B.143.2. Torkham – shall be ordered when cargo destined for/from provinces in Afghanistan with a normal routing thru Chaman is being re-routed via Torkham. (Example: Chaman normal routing for cargo destined to Badghis, Heart, Ghor, Farah, Nimroz, Helmand, Kandahar, Oruzgan, Day Kundi, Zabul).

B.143.3. KKT – shall be ordered when cargo destined for Afghanistan or originating in Afghanistan via the NDN transits thru Kazakhstan, Kyrgzyzstan, Tajikistan to/from Afghanistan.

B.143.4. KUT – shall be ordered when cargo destined for Afghanistan via the NDN transits thru Kazakhstan, Uzbekistan, Tajikistan to/from Afghanistan.

B.12. Enhanced In-Transit Visibility (ITV) and Cargo Security

B.12.1. Enhanced Security Services

Enhanced Security Services include measures above and beyond the Standard Security measures required by B.9. These services include two separately priced accessorials: Enhanced ITV Services (described in paragraph B.11.2.1 below) and Enhanced Physical Security (described in paragraph B.11.2.2 below). These added security services are intended to eliminate pilferage and prevent banditry; to provide the time and location where losses occur, to assist law enforcement in the prosecution of offenders and recovery of goods and to guide future route selection decisions. These accessorial services shall be limited to Pakistan Ground Lines of Communication overland linehaul services to and from Afghanistan via sea ports in Pakistan.

B.12.2. When ordered by the US Government or its authorized booking agents as a contracted Accessorial Service, the Contractor shall provide Enhanced ITV Services as detailed below:

1. Automated Location Reporting, to include:

a. Position Calculation via GPS every 15 minutes with data queued for later transmission;

b. Communication from cargo via satellite shall include devices capable of transmitting position reports every 30 minutes with no interruption in service for the entire transit from origin to POE;

Formatted: Right

c. Reporting Frequencies shall include multiple options ranging from 30 minutes to six hours. Transmission must include all queued position reports.

d. Communication to Government must be automated via interface with IRRIS and iSDDC.

e. Transponders: Attached to Cargo (vice conveyance)

2. Intrusion Detection (Containers Only), to include:

a. Electronic or Automated Detection of intrusion or tampering;

b. Communication from device to transponder;

c. Automated communication to government via approved interface immediately upon detection of intrusion;

d. Archived record of events to include time and location; and

e. Installation and arming of devices

3. Position/Status Data Reporting, to include:

a. Position/Status reports that shall feed into IRRIS and iSDDC using secure FTP XML, web service, or other format acceptable to IRRIS and iSDDC. Data transmitted to IRRIS and iSDDC must include:

Device identifier, Shipment identifier (Container number or TCN) Date/time in ZULU format, Location information in decimal latitude/longitude format Status/event codes to report when intrusion is detected and (optional) any other shipment events or status.

b. Status code definitions and test data provided to the IRRIS PMO upon contract award and two weeks prior to any scheduled movement for subsequent code changes.

c. Functional Points of Contact for the IRRIS PMO are Ms. Karen Timmons at 618-220- 5116 and Mr. Phil Krueger at 618-220-5216 for review of alternate feed formats, coordination of system interfaces and testing.

d. Functional Points of Contact for the iSDDC PMO are Mr. Christopher Heiby at 618- 220-5632 and Ms. Tina Woodbury at 618-220-5673 for review of alternate feed formats, coordination of system interfaces and testing.

This accessorial shall be applicable when ordered and may be used for Unit Cargo Moves, Sustainment Cargo Moves, or Retrograde Cargo Moves.

B.11.3. When ordered by the US Government or its authorized booking agents as a contracted Accessorial Service, the Contractor shall provide Enhanced Physical Security as detailed below:

1. Convoy Movement Security planning and execution;

2. Secure enroute checkpoints to include cargo inspection and daily reporting of checkpoint activity;

3. Contractor provided special security devices, bolts, seals and/or procedures used to detect and reduce pilferage (Containers Only);

4. Back-up truck and driver capability to recover from truck or driver disability;

5. Truck operations that incorporate:

a. Route planning to avoid reported threats;

b. Waypoint ETAs and status checks for overdue trucks;

c. Continuous contact with drivers and escorts;

d. Secure facilities for overnight rest; and

e. Immediate response to driver disability, equipment damage or breakdown.

6. Upon indication of deviation from planned route, unplanned delays in movement, loss of contact, pilferage, attack, security breech, or any other indication that the cargo has been

Formatted: Right compromised, the Contractor shall immediately notify the cognizant SDDC Group Operations Center of same and provide detailed information to include:

Time and location of incident;

Details of the incident;

Container numbers or breakbulk TCNs involved;

Proposed corrective action;

Impact to delivery schedule; and Follow-on report within 24 hours with reports continuing every 24 hours until the cargo is recovered or the customer suspends the reporting.

Screened Personnel to include drivers, escorts, and checkpoint and tracking personnel.

B.12 Sanitization of Containers

This service will only be ordered for cargo exiting Afghanistan via Uzbekistan. procedures apply to both the containers/flatracks as well as any cargo stuffed inside the containers/on the flatracks. The procedures are written for containerized/flatrack cargo but apply to breakbulk cargo as well.

B.12.1 Inspection and preparation of containers – Inspection of containers and territory around them is done to analyze the contamination by rodents and insects. Containers are cleared from trash and rubbish.

B.12.2 Disinfestation – this procedure is carried out by setting bait traps (stations) in the bottom of each container (1 unit per container). Bait station is filled by poisoned grains which are made of low-toxic, anticoagulant for human drug and non-dry glue for catching rodents. This work is carried out immediately after the inspection because if it is done before, rodents might temporarily leave the area, which will prevent effective poisoning and catching of the rodents. Disinfestation of 1 container takes approximately 5-10 minutes. Since disinfected containers are sealed after the procedure, used/full bait stations are removed from containers prior to sealing.

B.12.3 Disinsection – carried out, preferably one day after the disinfestation. This is done by using atomizing and aerosol spraying insecticide for all available surfaces of the container, including the gaps between the goods on the shelves. Spraying is conducted from the bottom – to clean the bottom, side walls, and spaces to the upper side, cleaning the space available at the top. On the availability of modern equipment (sprayers), time spent on a single container is 25-40 minutes (including preparation of the insecticides, filling a spray and spraying itself). Approximate time to process one container is 10-15 minutes using 3 specialists.

B.12.4 Disinfection – after exposure of a container to the disinsection process for at least 2-3 hours, it is ready for disinfection. The purpose of disinfection is to destruct potential pathogenic microorganisms in the container as well as to destruct microorganisms that develop after the possible death of rodents and insects (as a result of disinfestation and disinsection). In this regard, it is performed after these 2 procedures. The disinfection technique is the same as disinsection with the only difference that when spraying the insecticide, the larger area is sprayed out. Processing time per container for disinfection is 30- 50 minutes using 1 specialist and 15-20 minutes using 3 specialists.

B.12.5 After the above procedures are complete, bait stations are inspected and removed from the containers (as an option, unused/empty traps can be left to protect cargo in the future from rodents). This procedure takes 5-10 minutes per container.

Note: Timings above are set for TEUs; FEUs will take approximately twice as long. Two to three hours between disinsection and disinfection is standard regardless of container size.

B.12.6 Sanitation of closed sealed containers – the technique and timing for closed containers is mostly the same as for flatracks. The main differences are:

Formatted: Normal

Formatted: Right

1. Disinfestation and disinfection are carried out on the walls and surfaces of the containers, both outside and inside;

2. Disinsection and disinfection are carried out on open surfaces and all the available space in the container (aerosol sprays easily penetrate into the open surface);

3. Exposure between the procedures and processing of external and internal walls and surfaces of containers depend on providing access by the customer.

C. APPLICABLE TO EXIGENCY AREAS WITHIN AFRICOM

(blank)

D. APPLICABLE TO EXIGENCY AREAS WITHIN EUCOM

(blank)

E. APPLICABLE TO EXIGENCY AREAS WITHIN PACOM

(blank)

F. APPLICABLE TO EXIGENCY AREAS WITHIN NORTHCOM

G. APPLICABLE TO EXIGENCY AREAS WITHIN SOUTHCOM

END OF CONTINGENCY ANNEX

Formatted: Normal

Formatted: Font color: Auto