[optional: insert company logo] Transport Security Program (tsp) for

Attachment C: List of Sites and Facilities Covered by this TSP [r2.54(1)]

Download 333.77 Kb.

Page	10/10
Date	02.02.2017
Size	333.77 Kb.
	#16088

1 2 3 4 5 6 7 8 9 10

Attachment C: List of Sites and Facilities Covered by this TSP [r2.54(1)]

Listed below are all sites that operate on behalf of the Organisation and all facilities covered by this TSP:

Site/facility name	Address	Suburb/town	State	Postcode

Add rows as required

Under the Regulations, for each facility that is located at a security controlled airport, the RACA must give the airport operator:

the RACA’s contact details, including contact details for the security contact officer; and
details of the procedures to check the identity of persons who are authorised to have access to the facility.

A failure to notify the Secretary in writing within seven (7) days of becoming aware of any changes to the details in these tables may be an offence under the Regulations.

Attachment D: Organisational Structure and Security Management Arrangements [r2.52(1)(a)]

Insert text and/or a diagram clearly articulating your organisational structure and security management arrangements here.

Attachment E: Consultation undertaken as part of the development of this TSP [s16(2)(g)]

The following aviation industry participants contributed to the development of this TSP:

Organisation	Title / Relationship	Consultation Undertaken
e.g. your organisation	e.g. all levels of management and staff supervision	e.g. considered and discussed the various security-related roles and responsibilities within the organisation. e.g. security measures and procedures to be implemented in accordance to this TSP. e.g. reporting responsibilities of staff.
e.g. ABC Airways	e.g. RPT operator	e.g. procedures and requirements for loading cargo.
e.g. XYZ Cargo	e.g. freight operator	e.g. procedures and requirements for loading cargo.
[Other consulted organisations]

Add rows as required

Attachment F: Regular Customer Undertaking [r2.60(b)]

[Optional: Insert customer logo]

[Insert customer’s legal name here] (the customer):

agrees to be placed on the regular customer list of [Organisation’s name].

undertakes to take appropriate security measures to prevent the unauthorised carriage of an explosive or an explosive device;

undertakes that at time of consignment, cargo will:

have secure, undamaged packaging;
appear not to have been tampered with;
be accompanied by documentation that identifies the customer as the consignor of the cargo; and
be presented by a person who can be verified as a representative of the customer;

is aware that cargo will be subject to security and clearing procedures; and

is aware that it is illegal to consign as cargo, without authorisation, an explosive or an explosive device.

Signature :
Title :
Date :	(Chief Executive Officer or authorised representative)

Accompanying Document 1: Details of Sites and Facilities Covered by this TSP [r2.54(2)]

Detailed below are all sites that operate on behalf of the Organisation and all facilities covered by this TSP:

Site/facility name:		Site/facility name or identifying description
Address:		Street address of site/facility
Located on an airport		Yes / No	If yes, is it a security controlled airport				Yes / No
If located on an airport, name of airport and a description of airside and landside operations
This site/facility is located at [airport trading name]. The airside operations at this airport are [location and description]. The landside operations at this airport are [location and description].
Operations conducted at this site/facility include:
handling cargo consolidating cargo examining cargo storing cargo after hours loading cargo onto road vehicles parking cargo transport vehicles after hours loading cargo onto aircraft (CTO operations)
Proportion of cargo handled at this site that is domestic cargo						None / Some / Most / All
Proportion of cargo handled at this site that is international cargo						None / Some / Most / All
Hours of operation
Days	e.g. Mon-Fri			Hours	e.g. 24h
Days	e.g. Sat			Hours	e.g. 0800h – 1200h
Days	e.g. Sun			Hours	e.g. closed

Add additional pages as required

Under the Regulations, for each facility that is located at a security controlled airport, the RACA must give the airport operator:

the RACA’s contact details, including contact details for the security contact officer; and
details of the procedures to check the identity of persons who are authorised to have access to the facility.

A failure to notify the Secretary in writing within seven (7) days of becoming aware of any changes to the details in these tables may be an offence under the Regulations.

Accompanying Document 2: Timetable for implementation of security measures and procedures [r2.55(2)(b)]

Detailed below are security measures and/or procedures yet to be implemented at by the Organisation.

Measure or Procedure not yet implemented	Site(s)	Implementation date (no later than)
e.g. Swipe card access installed to replace the key lock on all entry doors	All sites	DD/MM/YY

Delete this document if all of the measures and procedures referred to in your TSP have been implemented.

Accompanying Document 3: Measures and procedures in the event of a heightened security alert [r2.57]

The Organisation has a number of additional security measures and procedures available for implementation in the event of a heightened security alert. These measures are:

Insert your measures and procedures. For example:

an increase in the number of security personnel / guards;

increased frequency of patrols;

implement 7-day hold on all cargo;

examine 100% of cargo (including cargo from regular customers);

24-hour watches;

hiring commercial flood lights;

request assistance from the relevant law enforcement agency;

changes to parking arrangements in the vicinity of the site or facility and/or inspection of vehicles and changes to the vehicular parking areas;

changes to cargo delivery arrangements; and

increased monitoring or reduction of access points.

All of these measures can be applied almost immediately, and are able to be sustained for an extended period.

Aviation security incident response [r2.57(2)(a)]

Insert your measures and procedures for responding to an aviation security incident. For example:

If an aviation security incident, including a threat or breach of security, is identified by the Organisation or any member of staff, the [specify] and the SCO are to be informed immediately.

The SCO is to inform:

all relevant authorities including the local State / Territory Police and the Australian Federal Police; and

any relevant aviation industry participants facing immediate threat.

The SCO is to ensure:

staff are fully aware of circumstances;

information is passed on; and

evidence is preserved (unless otherwise directed by a relevant authority e.g. for safety reasons).

The SCO is then to:

document or record all information from staff with knowledge of the incident;

provide an analysis of the incident for company action;

be prepared to provide information to assist relevant authorities; and

if requested, consider providing company resources to assist relevant authorities.

All Organisation staff are to:

assist the SCO and the Site/Facility Manager in precautionary/preparatory actions; and

comply with all requests and procedures from relevant emergency authorities.

Reporting aviation security breaches [r2.57(2)(b)]

The Organisation has a range of procedures for reporting aviation security breaches, including threats to aviation security. The nature of the threat and the seriousness of the breach will dictate who will be advised and the appropriate level of escalation.

These procedures are as follows:

Insert your measures and procedures. For example:

the [specify] and the SCO are to be informed immediately;

the SCO is responsible for recording the breach, and for recording and response activities taken;

the Department will be notified of any security breaches on case by case OR monthly basis.

Where appropriate, an aviation security breach that relates to the Organisation will also be reported to:

the Secretary;

the relevant State or Territory [specify] police force;

the Australian Federal Police;

any regulated business that is impacted;

any airport operator that is impacted; and

any aircraft operator that is impacted.

Contact numbers and email addresses for incident reporting are available to all staff via:

our induction training;
our procedures manual; and
are prominently displayed in all offices.

Reports made by phone will be followed up in writing within 24 hours.

Evacuation and emergency management [r2.57(2)(c)]

The following actions apply to a threat to or breach of security including:

a bomb threat;

a failure of critical security equipment;

[specify further as relevant].

Any of these incidents may result in the Organisation doing some or all of the following:

Insert your measures and procedures. For example:

securing and evacuating the affected site/facility;

refusing to receive any further cargo;

[specify further as relevant].

We will also comply with any requests from relevant emergency authorities.

Following any of the incidents referred to above, a full internal investigation and report will be made for review by [specify] and, if required, changes to operating procedures will be implemented and this TSP updated accordingly.

Special security directions [r2.57(2)(d)]

[Specify position/role] is responsible for implementing and ensuring compliance with any special security direction (SSD) issued by the Secretary to the Organisation.

Insert your procedures for responding to an SSD given by the Secretary here. For example:

Upon receipt of an SSD, the [position identified above] will determine the most effective way to implement the SSD in consultation with the Organisation’s senior management.

The Organisation’s senior management will consider which of the various parties who may be affected by the SSD will need to be informed, including:

employees and staff;

consignors;

relevant regulated businesses;

law enforcement agencies; and

local fire and emergency agencies.

The Organisation’s senior management will also determine the most effective method to communicate the SSD to the various parties such as through meetings, telephone calls or emails.

Staff security awareness [r2.57(2)(e)]

In the event of a heightened security alert the Organisation will take the following actions to raise the awareness and alertness of staff to security threats, and their responsibility to report aviation security incidents and breaches:

Insert your measures and procedures. For example:

Inform staff of the heightened security alert.

Remind staff of reporting responsibilities regarding security incidents and breaches.

Provide staff with details of the approved incident report form.

Ensure all staff are made aware of, and have access to, the Organisation’s operational procedure manual / security manual [insert the title of the relevant documentation for your organisation].

Contingency Plans [r2.57(2)(f)]

Select from the options below as appropriate for your operations.

The Organisation does not have additional security contingency plans or procedures related to heightened security alerts.

The Organisation has a number of security contingency plans and procedures related to heightened security alerts. These plans may also be activated upon:

receipt of an SSD;

a threat to security;

a breach of security;

the occurrence of an aviation security incident; or

any time declared by the [specify].

These procedures and plans include, but are not limited to:

Insert your organisation’s contingency plans here. For example:

an increase in security personnel;

requests for assistance from the relevant law enforcement agency;

changes to vehicle access and/or parking arrangements in the vicinity of the site/facility and/or inspection of vehicles;

increased monitoring or reduction of access points; and

other measures subject to assessment of risk.

DELETE THIS PAGE PRIOR TO SUBMISSION

Final checks prior to submission

All purple text should have been replaced or overwritten in black text by the information relevant to your operations.
All red text (except the security classification) should be deleted.
There should be no track changes or comments.
The Table of Contents should be updated (at the Home option on the toolbar, go to the Editing tab, choose Select, then press Select All. This will select the entire document. If you now press the F9 button, section headings and paragraph titles will be updated in the Table of Contents).
Ensure the Document Revision Record is completed.
Remove any passwords or other protection measures.
Ensure that your Statement has been signed and dated by the CEO (or authorised representative).
Ensure your organisation retains identical electronic and hard copies of the document.
Send the completed TSP by email to national.coordinator@infrastructure.gov.au for consideration by the Secretary.

DELETE THIS PAGE PRIOR TO SUBMISSION

Under regulation 2.06 of the Aviation Transport Security Regulations 2005 it is an offence to disclose any information about the content of an aviation industry participant’s TSP without the consent of the participant.

SCT05-06 (May 2016) Sensitive

Directory: security
security -> Security Education Narrative Database Patterns of Professional Education
security -> Tropic Lightning
security -> Here is a basic helloworld asm program in x86 assembly
security -> Computer security involves a number of aspects as follows: *Your computer hardware
security -> Data warehouse use & access rules & access request form
security -> Degreeworks use & access rules
security -> Ccna security Chapter 2 Lab A: Securing the Router for Administrative Access Instructor Version Topology ip addressing Table
security -> Chapter 3 Lab A, Securing Administrative Access Using aaa and radius instructor Version
security -> E-vote 2011 Security Architecture Description eVoting toe V 0
security -> United Nations Peacekeeping Operations and Mandatory hiv testing August 1996

Download 333.77 Kb.

Share with your friends:

1 2 3 4 5 6 7 8 9 10