Navtech Radar AGS800-001 AGS800 Position Sensing Radar User Manual User guide
Navtech Radar Ltd AGS800 Position Sensing Radar User guide
User guide
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 1942001 |
| Application ID | s17bwW75q19OWt2qA//MiA== |
| Document Description | User guide |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 77.26kB (965755 bits) |
| Date Submitted | 2013-04-17 00:00:00 |
| Date Available | 2013-04-17 00:00:00 |
| Creation Date | 2013-03-26 15:29:35 |
| Producing Software | Adobe PDF Library 9.9 |
| Document Lastmod | 2013-03-26 15:31:10 |
| Document Title | User guide |
| Document Creator | Adobe InDesign CS5 (7.0.4) |
| Document Author: | Corporate Text & Design (www.ctxd.com) |
AdvanceGuard Hardware Installation Guide Document version 1.2e Contents 2 Welcome Essential items Parts 4 Creating an installation Mounting a radar sensor Mounting the enclosure and power supply Levelling a sensor Connecting a radar sensor Connecting other items Connecting cameras Connecting trigger inputs and alarm outputs 10 Confirming sensor operation 10 10 11 Preparing your computer Connecting your computer Testing a sensor 15 Appendices 15 16 Appendix 1 - FAQ Appendix 2 - Radio frequency energy statement Hardware Installation Guide Welcome The Navtech Radar AdvanceGuard system provides high integrity detection, tracking and intelligent alarm generation for wide area intrusion detection systems. This guide concentrates on installing the key hardware components: Radar sensors; cameras and external inputs/ outputs. As part of the installation process this guide also covers how to test the radar sensor output and adjust its positioning for optimum performance. For details about the witness application group, please refer to the companion Witness Commissioning Guide. Essential items The following are the essential additional items that you will need to install a radar sensor: • Laptop computer running Radar View software, • Shielded Cat5E patch lead, • Digital level, • 25m² radar target and tripod, 2 off, • 10mm spanner, • Pair of 2 way radios, • An assistant. Radar & camera models may differ from illustrations Power Supply Unit Radar Processing Unit Alarm outputs External inputs Adam 6060 Hardware Installation Guide Parts This page lists the main parts that are commonly used in most radar installations (mount poles are not shown). Note that these images are for illustrative purposes only, as items/casing shapes are subject to change. RPU (Radar Processing Unit) W- Series radar sensor I-Series radar sensor Radar sensor power cable (bare ended at enclosure end) IP-rated equipment enclosure Radar sensor power supply Mil spec shroud for radar sensor data connection Adam 6060 input/output unit Hardware Installation Guide Creating an installation Mounting a radar sensor Mounting the enclosure and power supply Navtech Radar Limited supply a range of radar sensors and mounting posts to suit various installation sites. The two most common posts are: • Standard mount post which provides a height adjustment of between 1.35m to 1.89m (measured beam height for a W200/500/AGS800/1600 sensor) and can optionally be fitted with a CCTV camera arm. • Telescopic mount post which can extend to 4 metres in height and is suitable for the X variant sensor. For the standard mount posts you should aim to initially position the sensor so that its metal collar is at roughly 1.5 metres above ground level so that the post is at the middle of its vertical adjustment range. During commissioning it may be necessary to raise or lower the sensor to clear obstacles or allow for the local terrain. Note: If you are creating your own mount post, you are recommended to include at least 50 centimetres of vertical adjustment built into the post to allow for local topography. The IP-rated equipment enclosure is normally mounted at the base of the radar post and is used to house the radar power supply unit, however, other items may also need to be housed within the enclosure: • If the radar is mounted more than 70 metres from the RPU server then it is recommended that a fibre optic ethernet link is used. In this case a media converter would also need to be housed within the enclosure. • If there is a camera option on the post then the camera power supply unit and a possibly a video encoder will also need to be housed. IMPORTANT: To prevent floating voltage levels on the low output of the radar sensor power supply unit, link the 0v output to earth. IMPORTANT: Note that each radar is supplied with a pressure plug, which is left loose during freight. This plug should be reinserted at install time such that the radar is kept pressurised and maintains its ingress protection. Failure to insert the pressure plug could invalidate the warranty in the event of damage. AC Simplified wiring diagram Hardware Installation Guide Levelling a sensor Due to the very narrow beams (1 or 2 degrees) used by most radar sensors, it is important that each sensor is level in relation to the area that it surveys. Level in this sense may not mean absolutely horizontal. For instance, if the site has a continual slope it may prove beneficial to incline the sensor in line with the slope to ensure that targets are correctly tracked. The exaggerated examples below show how a sensor with an incorrect incline could miss targets which are lower down the slope: To make sensor levelling adjustments The sensor mounting plate allows for a simple yet effective method to fine tune the incline of the sensor. For each of the mounting holes, the bolt is fed from underneath and locked onto the mounting plate with a nut. Two more nuts and washers are then used above and below the sensor plate so that the sensor can be positioned anywhere up or down the bolt thread, as necessary. The horizontal radar sensor misses target B. We recommend that you begin with the sensor completely horizontal and then carefully adjust it to suit the conditions using the method described next. The inclined radar sensor locates both targets. Hardware Installation Guide To adjust the sensor level The recommended procedure to check for the optimum incline is to use two radar targets mounted on tripods. 1 Adjust each target to a height of 1.3 metres above ground level and locate them on opposites sides of the sensor at suitable distances (e.g. 30m or further). Your aim is to ensure that both targets can be clearly seen by the radar sensor. If necessary, carefully adjust the incline of the sensor until they produce similar traces. It may be necessary at this point to raise or lower the radar in addition to changing the incline. 2 Connect a portable computer to the radar sensor and then use the procedure To use SPx RadarView (within the section Testing a sensor) to view the resulting scan: Target A Target B 3 Reposition the targets in new locations and repeat the adjustment procedure until targets in various positions can be seen by the radar sensor. Radar sensor Target response shown in isolation within the SPx RadarView application Hardware Installation Guide Connecting a radar sensor Connections to W and AGS-Series radars On radar sensors with W and AGS-Series enclosures, the connections are made underneath: Each radar sensor requires a power and a data connection. Both are made using military specification connectors to ensure link integrity in the harshest environmental conditions. In the majority of cases, the power and data connections run from the sensor to the enclosure at the base of the mounting pole where the power supply is situated. Supplied with each radar sensor is a power cable with a mil-spec connector for the sensor connection and a bare end at the enclosure connection. A mil spec shroud is also supplied for use with a suitable environmentally protected Ethernet network cable. It is essential that the supplied shroud is correctly used to ensure that the data connection is water tight. IMPORTANT: Failure to correctly fit the shroud can invalidate the warranty on sensors that have been caused to fail through water ingress. Connections to I-Series radars On radar sensors with I-Series enclosures, the connections are made on the side panel: Data connection Power connection Data connection Power connection Hardware Installation Guide Connecting other items Multiple serial links This diagram indicates the two ways to link serial cameras to the RPU. As required, cameras can either use their own dedicated links to the RPU. It is important that each camera is given a unique ID number. The modular nature of the AdvanceGuard system offers considerable opportunity for customisation to suit a wide range of installations. This section discusses the broad approach for connecting third party devices to the AdvanceGuard system. Connecting cameras The AdvanceGuard system communicates with cameras using either direct Ethernet, RS422 serial or VipX (a proprietary Ethernet-based standard), as required. All cameras within an installation are linked to a server system called an RPU (Radar Processing Unit), which is a high specification industrial computer. In certain cases a single RPU will control several radar sensors as well as the cameras. In larger installations there may be separate RPU systems for the radar sensors and cameras. A software component called Cyclops is used on the RPU for the purpose of controlling all of the cameras. Depending on the nature of your installation, there are numerous ways to connect cameras to an RPU. RS422 Line 1 Sentinel ID 0 RPU RS422 Line 2 Controller Basic Ethernet or serial links The diagram shows two cameras connected by their own Ethernet and/or serial links (different connection types can easily be mixed on the same RPU). The operator is provided with the AdvanceGuard Sentinel display which allows manual control of cameras where necessary. Additionally, a standard CCTV camera controller can also be provided and would be fed via the RPU, where its actions are interpreted by the AdvanceGuard system before being directed to the cameras. ID 1 RPU RS422 Cam 1 Cam 1 Controller Ethernet Sentinel Controller ID 3 Adapting existing larger installations When AdvanceGuard is integrated into an existing large installation, it is likely that a matrix will be employed to link multiple cameras to a single CCTV controller. It is also possible that the AdvanceGuard system is not required to control all of the existing cameras. In such situations it is important that the RPU is linked at the correct point. Matrix Sentinel ID 2 Cam 2 Cam 2 RPU Note: For simplicity in these examples, the Sentinel display and CCTV controller are shown connecting directly into the RPU. In reality they would not be connected in this manner. For security reasons, these controls would be connected to their own computer system which would indirectly link them to the RPU via an Ethernet connection. Cam 3 In the diagram only Cam 3 is required to be controlled by AdvanceGuard. The RPU is linked to the existing output for Cam 3 from the matrix and interprets the control signals before sending them to the camera. In this way the CCTV controller can service both the AdvanceGuard and non-AdvanceGuard sections of the installation. Hardware Installation Guide Connecting trigger inputs and alarm outputs Connecting inputs The Adam 6060 unit can accept inputs in either of two ways between the Iso GND. and the opto-isolated inputs D0 to D5: In addition to radars and cameras, the AdvanceGuard system can be integrated with other sensors, such as simple PIR units, and also linked to external alarms. Connections of this type are handled by one or more Advantech Adam 6060 industrial I/O devices which are attached, via Ethernet, to the RPU (Radar Processing Unit) system. Each Adam 6060 unit provides six opto-isolated inputs (labelled DI0 to DI5) and six relay switched dry-contact outputs. Input and output connections are made using the green blocks at each end, as shown below: RL 0+ RL 0RL 1+ RL 1RL 2+ RL 2RL 3+ RL 3RL 4+ RL 4Not used +VS GND Status indicators Dry contact inputs Also called ‘zero-volt’ switching, where the input line is shorted by an external switch to the Isolated GND terminal to signal a change of state. Iso. GND RL 5RL 5+ DI 5 DI 4 DI 3 DI 2 DI 1 DI 0 Vcc Ethernet Iso. GND RL 5RL 5+ DI 5 DI 4 DI 3 DI 2 DI 1 DI 0 Wet contact inputs Each input can also accept a DC voltage to represent a logic state. An input of 0 to 3VDC is taken to represent a logic zero, while a logic 1 is triggered when the input level rises above 10VDC. The input can accept voltages up to 30VDC. Vcc Iso. GND RL 5RL 5+ DI 5 DI 4 DI 3 DI 2 DI 1 DI 0 0~30Vdc Connecting outputs Each of the six outputs are relay driven with an internal contact being made between the + and - terminal pairs of the channels RL0 to RL5. The relay contacts can handle up to 0.5A at 120/240VAC or up to 1A at 30VDC. The Adam 6060 unit requires a power input of 10 to 30VDC which is applied between connections +VS and GND. At 24VDC supply level the unit consumes a maximum of 2W. 120/240Vac or 30Vdc Status indicators There are four status indicators on the top panel. Their functions are as follows: • Status (red) - Flashes when the module is powered on. • Link (green) - On when Ethernet connection is valid. • Speed (red) - On when the Ethernet connection 100Mbps. • COM (green) - Flashes when the Ethernet link is communicating. Addressing Each Adam 6060 unit must use a unique IP address that is within the same subnet as the RPU. LOAD RL 0+ RL 0RL 1+ RL 1RL 2+ RL 2RL 3+ RL 3RL 4+ RL 4Not used +VS GND Hardware Installation Guide Confirming sensor operation In order to test the output of the radar sensor, you will require: • A portable computer running Windows XP, Vista, Windows 7 or later, • The SPx RadarView application, which can be obtained from the ‘tools’ folder on the supplied RPU. • A CAT 5, 5e or 6 network cable (straight or crossover wiring). Connecting your computer Preparing your computer You can connect your computer at any point along the signal link from the radar sensor, either directly into the sensor mounted socket; at the pole mounted enclosure (if the signal link is joined there) or at the far end of the link where it will join the RPU (Radar Processing Unit) system. Note: The sensor can be powered on or off while connecting and disconnecting the network link. The network controller within the radar sensor is autosensing so that you can use either straight through or crossover cables and it will adjust its operation accordingly. IMPORTANT: Ensure that your computer has its IP address set to operate within the same subnet as the radar sensor: • The IP address (e.g. 192.168.0.1) of the radar sensor is preset before leaving Navtech Radar Limited according to client specifications and will be declared on a label attached to the outer casing. • The subnet mask of the radar sensor is often preset to 255.255.255.0 but could also be set wider (such as 255.255.0.0) if requested. • Thus, if the sensor IP address is 192.168.0.1 and the mask is 255.255.255.0, then your computer must use an IP address in the range: 192.168.0.2 to 192.168.0.254. Note: If you are connecting to the radar via an Ethernet switch rather than making a direct link, it is important that no other radar client software is already connected before using radar view. To connect your computer 1 Connect a link cable between your computer and the network port, either on the sensor or elsewhere along the signal path. 2 Ensure that the radar sensor is powered on and is rotating - you can faintly hear the rotor when it is running. 10 Hardware Installation Guide Testing a sensor Once your computer is connected to a sensor, there are four main tests that you can carry out on the radar sensor: • Ping the sensor to check for a basic network response. • Telnet to the sensor to view fundamental configuration settings. • Run a base level diagnostic test. • Use SPx RadarView to view the radar output. To ping a sensor 1 Open the Windows command prompt window (Start > Accessories > Command Prompt). 2 In the window, type ping a.b.c.d where a.b.c.d is the IP address of the radar sensor. After a short while you should see several responses from the sensor: To telnet to a sensor 1 Open the Windows Command Prompt window (Start > Accessories > Command Prompt). 2 In the window, type telnet a.b.c.d where a.b.c.d is the IP address of the radar sensor. After a short while you should see a response from the sensor: This shows that the network interface of the sensor is functioning (and confirms connectivity of any intermediate switching equipment). If you do not receive a response: • Check the power supply to the sensor. • Listen for the rotor spinning. • Double check the network link to the sensor. • Confirm that you can ping intermediate switching equipment. • Check that your computer is configured with an IP address that is within the same subnet as the sensor. The response should show details about various modules within the sensor. 11 Hardware Installation Guide To run the diagnostic test 1 Open the Windows Command Prompt window and telnet to the sensor as discussed in the previous section. 2 Whilst still within the telnet session, type diag 1 After ten seconds, results from the diagnostic will begin to be displayed: Note: The radar sensor will report incorrect temperature readings for the first 100 seconds of its operation after first being powered on. The results will be appended every ten seconds. The various fields are as follows: • Time - Shows the time when the diagnostic test was run. • T - Shows the current temperature reading within the sensor housing. • Min/Max - Shows the recorded minimum and maximum temperatures. • Revs - Shows the rotor revolutions per second. Should be 1.0* • Pkts - Shows the number of packets of IP data sent in the last ten seconds* • Kbits - Shows the size of IP data sent in the last ten seconds. • Idle - N/A. • VCO - Shows the setting of the Voltage Controlled Oscillator - should be A-On. • TCP/IP - Shows the status of the IP connection. *These will only be non zero if a client is connected to the radar (RadarView or witness) To use SPx RadarView The SPx RadarView application consists of two files which must be located in the same folder (any folder) on your computer: SPXRadarView.exe and SPXRadarView.rpi. 1 Run SPXRadarView.exe. You should see a blank main screen: Note: In the lower panel, the Video and Turn indicators will be red to indicate that there is no communication with the sensor. 2 Click the Channel-A menu and select the Source... option. 3 Ensure that the Selection option is set to Network and in the section below, enter the IP Address of the sensor. The Port must be set to 700. Click OK. 12 Hardware Installation Guide 4 Once the IP address and port are correctly set and the application makes contact with the sensor, the Video and Turn indicators should turn green. Shortly after, you should begin to see radar scan information within the main window: 13 Hardware Installation Guide 5 On the left side of the screen, ensure that the Raw option is ticked. 6 Click the button to show the Display Control dialog box: 9 Right click the mouse pointer on the exact middle point of one of the targets to display a popup options box. Click the option ‘Popup Channel-A AScan...’ to display a scan window: Target response The scan window provides live signal strength data concentrating only on the angular direction of the chosen target from the radar sensor. In each of the two graph plots, the x-axis shows the distance from the sensor while the y-axis indicates the returned signal strength. You should see a spike representing your target at the relevant distance. 10 On the top graph, left click on both sides of the spike to create a zoomed view on the lower graph. This will allow you to see small changes in the returned signal strength on the lower graph when levelling the sensor: 7 Ensure that in the Raw Radar section, the Fading option is set to Sweep and the Rate (sweeps) is set to 5. Click OK. 8 Click the button to zoom into the radar view so that you can clearly see the both of your test targets: Define the zoom area here Radar sensor Target A Target B See the zoomed view here 11 Repeat steps 9 and 10 for the other target so that you can view both on screen at the same time. 12 Adjust the radar sensor level (see To adjust the sensor level for details) while checking the scan graphs to ensure the best (highest signal) reponse from both targets. 14 Hardware Installation Guide Appendices Appendix 1 - FAQ What is the power consumption of the radar? • Up to 25 watts at 24VDC. Please see the data sheet for the exact figure. Can the radar sensor be inverted? • Please contact Navtech Radar Ltd to discuss the application. The Industrial series may be inverted, subject to some firmware changes and additional charge. What is the network bandwidth usage? • Up to 25 megabytes per sensor. Please contact Navtech for exact figures for your chosen radar. What is the operating frequency/band width of the radar? • All radars operate within the 76-77GHz band as per ETSI standard EN 301 091-1 V1.3.3 What connectivity does the radar support? • Connection to the radar is via ethernet. Each radar has an RJ45 socket. We recommend cat5 cable to the radar, not to exceed 70m in length. Longer lengths should make use of switches or fibre converters. What output power does the radar emit? • Maximum output power is within the limit of +55dBm EIRP as specified by ETSI standard EN 301 091-1 V1.3.3 What is the ideal mounting height? • The ideal mounting height can vary depending on the specific site, the type of radar and if the beam is angled. The X units have been designed to be mounted at about 4m, this will give a minimum detection range of about 10m and for a man walking upright, with the maximum according to the sensor data sheet. Does the radar interfere with aviation systems? • The radar conforms to ETSI standard EN 301 091-1 V1.3.3. Confirmation of compliance with aviation systems is the responsibility of the systems integrator/end user. What is the beamwidth? • The beamwidth varies per radar sensor. The azimuth beamwidth is either 1 or 2 degrees with the main elevation beamwidth of the radars ranging from 2 to 4 degrees. The X radar in addition has a close range infill beam of approximately 25 degrees. Please see the data sheets for clarification. Is the radar affected by adverse weather conditions? • The radar is unaffected by fog, rain, snow etc. Does witness provide other interfaces? • Witness can interface to multiple ethernet relay units, providing multiples of 6 digital inputs and 6 relay outputs. These I/O lines can be linked to various actions/events within witness. Which cameras does Witness support? • Witness currently supports a selection of cameras, as detailed in the applicable sales literature. Additional cameras can be added (at cost) if they support absolute positioning. At what ambient temperatures can the radar operate? • Please refer to the data sheet for the exact model, but most sensors will operate over -20 to +60 degrees C. Can the radar be used on the move? • Not as an intruder detection device, as the radar has to be static in order to be able to detect movement. It can, however, be used as an obstacle detection device to prevent large plant equipment from having collisions. 15 Hardware Installation Guide Appendix 2 - Radio frequency energy statement FCC compliance statement (United States) This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. The operation of this device is limited to a fixed position at airport locations for foreign object debris detection on runways and for monitoring aircraft as well as service vehicles on taxiways and other airport vehicle service areas that have no public vehicle access. This equipment must be mounted in a fixed location maintaining a minimum separation distance of 46cm from personnel when in general operation. This restriction of operation is specific for use in North America. For use in other regions aligned to the FCC regulations, specific country restrictions should be reviewed. Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. © 2013 Navtech Radar Limited 16 Release 1.2e Documentation by: www.ctxd.com Hardware Installation Guide
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : No Author : Corporate Text & Design (www.ctxd.com) Create Date : 2013:03:26 15:29:35Z Modify Date : 2013:03:26 15:31:10Z Tagged PDF : Yes XMP Toolkit : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26 Instance ID : uuid:dc24e686-2586-4bc5-b3e6-6d58598de3d4 Original Document ID : adobe:docid:indd:b3643674-d060-11df-ab2d-93eff77cbaa1 Document ID : xmp.did:9C3AB44F2C87E211830AD4287F83B195 Rendition Class : proof:pdf Derived From Instance ID : xmp.iid:1983ED382C87E211830AD4287F83B195 Derived From Document ID : xmp.did:23C14CD81C87E211830AD4287F83B195 Derived From Original Document ID: adobe:docid:indd:b3643674-d060-11df-ab2d-93eff77cbaa1 Derived From Rendition Class : default History Action : saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved, saved History Instance ID : xmp.iid:6365059A4AF3DF119DE2A15EAC63500B, xmp.iid:6465059A4AF3DF119DE2A15EAC63500B, xmp.iid:6565059A4AF3DF119DE2A15EAC63500B, xmp.iid:1E9848AB4AF3DF119DE2A15EAC63500B, xmp.iid:5AEC8FD24BF3DF119DE2A15EAC63500B, xmp.iid:63EC8FD24BF3DF119DE2A15EAC63500B, xmp.iid:424D9DA8BCF3DF11A60BD6EA9E18E7B4, xmp.iid:DBB7537DCFF3DF11A60BD6EA9E18E7B4, xmp.iid:FDC5AD6B22F7DF11AECFB8EBBC4B1045, xmp.iid:FE8FB8FE24F7DF11AECFB8EBBC4B1045, xmp.iid:04C0B93A2FF7DF11AECFB8EBBC4B1045, xmp.iid:97AE2D5D2FF7DF11AECFB8EBBC4B1045, xmp.iid:549298892FF7DF11AECFB8EBBC4B1045, xmp.iid:3EF22BE44DF7DF11AECFB8EBBC4B1045, xmp.iid:2CDF1334ADF7DF11A57BB4568EA39418, xmp.iid:BAA53509C0F7DF1196EA8CAC5FC1CD5C, xmp.iid:A0678D9DC8F7DF1196EA8CAC5FC1CD5C, xmp.iid:58C514BCCFF7DF1196EA8CAC5FC1CD5C, xmp.iid:FD4CD3BED0F7DF1196EA8CAC5FC1CD5C, xmp.iid:8BE62976D1F7DF1196EA8CAC5FC1CD5C, xmp.iid:B9DB77DCD9F7DF1196EA8CAC5FC1CD5C, xmp.iid:A7E00445E5F7DF1196EA8CAC5FC1CD5C, xmp.iid:E3D20D8DE7F7DF1196EA8CAC5FC1CD5C, xmp.iid:56799832E9F7DF1196EA8CAC5FC1CD5C, xmp.iid:8F191AEDEAF7DF1196EA8CAC5FC1CD5C, xmp.iid:F25F9162ECF7DF1196EA8CAC5FC1CD5C, xmp.iid:F69D1016EEF7DF1196EA8CAC5FC1CD5C, xmp.iid:355D3CD5F3F7DF1196EA8CAC5FC1CD5C, xmp.iid:7BF788DDF3F7DF1196EA8CAC5FC1CD5C, xmp.iid:5677C37CF5F7DF1196EA8CAC5FC1CD5C, xmp.iid:D321BD88F5F7DF1196EA8CAC5FC1CD5C, xmp.iid:C59897C7BAF8DF11A5EDA97672048163, xmp.iid:7904EAFF41F9DF1195B59640D1978931, xmp.iid:4FAE622645F9DF1195B59640D1978931, xmp.iid:AD4BC9F046F9DF1195B59640D1978931, xmp.iid:17FFDF6048F9DF1195B59640D1978931, xmp.iid:76BC8EC54AF9DF1195B59640D1978931, xmp.iid:C947B3A44BF9DF1195B59640D1978931, xmp.iid:394FC4D34BF9DF1195B59640D1978931, xmp.iid:6E8FD8E44FF9DF1195B59640D1978931, xmp.iid:FCB5CCCD7AF9DF119CADECA8F8581DE8, xmp.iid:B7F782D77AF9DF119CADECA8F8581DE8, xmp.iid:8E2616FD7CF9DF119CADECA8F8581DE8, xmp.iid:C1C2E9E27DF9DF119CADECA8F8581DE8, xmp.iid:A5D5E2BC7EF9DF119CADECA8F8581DE8, xmp.iid:2AFDEDAA7FF9DF119CADECA8F8581DE8, xmp.iid:25B47B6285F9DF119CADECA8F8581DE8, xmp.iid:E68652B386F9DF119CADECA8F8581DE8, xmp.iid:08C47BC589F9DF119CADECA8F8581DE8, xmp.iid:ACBCF8838BF9DF119CADECA8F8581DE8, xmp.iid:CB1019A18BF9DF119CADECA8F8581DE8, xmp.iid:7BD18FE311FADF11B80FD96DE33B738B, xmp.iid:61DEC3D112FADF11B80FD96DE33B738B, xmp.iid:6952EC9527FADF11B80FD96DE33B738B, xmp.iid:786F68102AFADF11B80FD96DE33B738B, xmp.iid:7BBC982835FADF11B80FD96DE33B738B, xmp.iid:F911A8FF35FADF11B80FD96DE33B738B, xmp.iid:0680125C3CFADF11B80FD96DE33B738B, xmp.iid:DBC892543EFADF11B80FD96DE33B738B, xmp.iid:A771446F41FADF11B80FD96DE33B738B, xmp.iid:1F9602EB41FADF11B80FD96DE33B738B, xmp.iid:77ED0A7542FADF11B80FD96DE33B738B, xmp.iid:2B9E03A042FADF11B80FD96DE33B738B, xmp.iid:188EE0C542FADF11B80FD96DE33B738B, xmp.iid:293BA15835FBDF11B15DD4613646058F, xmp.iid:A0BA471939FBDF11B15DD4613646058F, xmp.iid:78D87D7E39FBDF11B15DD4613646058F, xmp.iid:3A0F2E0D47FBDF11B15DD4613646058F, xmp.iid:0D85535947FBDF11B15DD4613646058F, xmp.iid:784A2C6C47FBDF11B15DD4613646058F, xmp.iid:FA0BE3F796FBDF11A766A3D85E92AD67, xmp.iid:787F4C31A5FBDF11A766A3D85E92AD67, xmp.iid:C5277D5EABFBDF11A766A3D85E92AD67, xmp.iid:53B815E4ABFBDF11A766A3D85E92AD67, xmp.iid:FD0F8F4AACFBDF11A766A3D85E92AD67, xmp.iid:84BC91E9ACFBDF11A766A3D85E92AD67, xmp.iid:08683764ADFBDF11A766A3D85E92AD67, xmp.iid:3A2FD4530DFCDF11A766A3D85E92AD67, xmp.iid:3B2357600FFCDF11A766A3D85E92AD67, xmp.iid:CACA4A4E10FCDF11A766A3D85E92AD67, xmp.iid:016AEED211FCDF11A766A3D85E92AD67, xmp.iid:B5691641CFFCDF11B950EF0AE6537629, xmp.iid:522B4C9DD0FCDF11B950EF0AE6537629, xmp.iid:70B9A7C9D3FCDF11B950EF0AE6537629, xmp.iid:AED9B73BD4FCDF11B950EF0AE6537629, xmp.iid:7DECAD11D6FCDF11B950EF0AE6537629, xmp.iid:8B5E4C67D9FCDF11B950EF0AE6537629, xmp.iid:6E252A89D9FCDF11B950EF0AE6537629, xmp.iid:371BE8AED9FCDF11B950EF0AE6537629, xmp.iid:27E06459DAFCDF11B950EF0AE6537629, xmp.iid:6CD6DB98DAFCDF11B950EF0AE6537629, xmp.iid:0397BD291D1FE0118736DEC66BC3C8FE, xmp.iid:98F720BE1E1FE0118736DEC66BC3C8FE, xmp.iid:9A8407E41E1FE0118736DEC66BC3C8FE, xmp.iid:554D8B81201FE0118736DEC66BC3C8FE, xmp.iid:85F11AB2241FE0118736DEC66BC3C8FE, xmp.iid:37DBDD1B251FE0118736DEC66BC3C8FE, xmp.iid:2E8CE42F2F1FE0118736DEC66BC3C8FE, xmp.iid:DD236C9D381FE0118736DEC66BC3C8FE, xmp.iid:3ADBD30F391FE0118736DEC66BC3C8FE, xmp.iid:131045A33A1FE0118736DEC66BC3C8FE, xmp.iid:9F731E37DFF4E011B3A4E740939E5FCE, xmp.iid:A0731E37DFF4E011B3A4E740939E5FCE, xmp.iid:184371CDE6F4E011B3A4E740939E5FCE, xmp.iid:3989744BE7F4E011B3A4E740939E5FCE, xmp.iid:6F4A96DCE8F4E011B3A4E740939E5FCE, xmp.iid:D1FD684EE9F4E011B3A4E740939E5FCE, xmp.iid:30E879C7E9F4E011B3A4E740939E5FCE, xmp.iid:8F92B8097BF9E011AE8EA008EF5FC3E9, xmp.iid:627FF9B07BF9E011AE8EA008EF5FC3E9, xmp.iid:637FF9B07BF9E011AE8EA008EF5FC3E9, xmp.iid:F2F8165181F9E011AE8EA008EF5FC3E9, xmp.iid:21F272D42BFAE011AE8EA008EF5FC3E9, xmp.iid:EFF456FE7E00E111A877E4A435EC005E, xmp.iid:02446D927F00E111A877E4A435EC005E, xmp.iid:15CF69432187E211830AD4287F83B195, xmp.iid:16CF69432187E211830AD4287F83B195, xmp.iid:8BA675F02287E211830AD4287F83B195, xmp.iid:66364CCA2487E211830AD4287F83B195, xmp.iid:A1EF36FC2B87E211830AD4287F83B195, xmp.iid:1883ED382C87E211830AD4287F83B195, xmp.iid:1983ED382C87E211830AD4287F83B195, xmp.iid:9C3AB44F2C87E211830AD4287F83B195, xmp.iid:9D3AB44F2C87E211830AD4287F83B195, xmp.iid:62DE77053887E211830AD4287F83B195, xmp.iid:314849473887E211830AD4287F83B195, xmp.iid:02EEB5115691E2118CCCB63AB1F842A1, xmp.iid:E83C84ED5691E2118CCCB63AB1F842A1 History When : 2010:11:18 19:32:38Z, 2010:11:18 19:32:38Z, 2010:11:18 19:33:07Z, 2010:11:18 19:33:07Z, 2010:11:18 19:41:22Z, 2010:11:18 23:20:54Z, 2010:11:19 09:09:05Z, 2010:11:19 11:23:53Z, 2010:11:23 16:55:05Z, 2010:11:23 17:13:30Z, 2010:11:23 18:26:46Z, 2010:11:23 18:27:44Z, 2010:11:23 18:28:58Z, 2010:11:23 22:33:12Z, 2010:11:24 09:28:31Z, 2010:11:24 11:51:04Z, 2010:11:24 12:44:45Z, 2010:11:24 13:35:43Z, 2010:11:24 13:42:57Z, 2010:11:24 13:48:04Z, 2010:11:24 14:48:12Z, 2010:11:24 16:09:52Z, 2010:11:24 16:26:12Z, 2010:11:24 16:37:59Z, 2010:11:24 16:50:21Z, 2010:11:24 17:00:48Z, 2010:11:24 17:12:58Z, 2010:11:24 17:54:07Z, 2010:11:24 17:54:21Z, 2010:11:24 18:05:57Z, 2010:11:24 18:06:17Z, 2010:11:25 17:38:14Z, 2010:11:26 09:46:10Z, 2010:11:26 10:08:43Z, 2010:11:26 10:21:32Z, 2010:11:26 10:31:50Z, 2010:11:26 10:48:58Z, 2010:11:26 10:55:12Z, 2010:11:26 10:56:31Z, 2010:11:26 11:25:38Z, 2010:11:26 16:32:47Z, 2010:11:26 16:33:04Z, 2010:11:26 16:48:26Z, 2010:11:26 16:54:51Z, 2010:11:26 17:00:57Z, 2010:11:26 17:07:36Z, 2010:11:26 17:48:32Z, 2010:11:26 17:57:57Z, 2010:11:26 18:19:56Z, 2010:11:26 18:32:25Z, 2010:11:26 18:33:14Z, 2010:11:27 10:34:18Z, 2010:11:27 10:40:58Z, 2010:11:27 13:09:37Z, 2010:11:27 13:27:21Z, 2010:11:27 14:46:46Z, 2010:11:27 14:52:47Z, 2010:11:27 15:38:19Z, 2010:11:27 15:52:25Z, 2010:11:27 16:14:39Z, 2010:11:27 16:18:06Z, 2010:11:27 16:21:58Z, 2010:11:27 16:23:10Z, 2010:11:27 16:24:13Z, 2010:11:28 21:20:38Z, 2010:11:28 21:47:30Z, 2010:11:28 21:50:19Z, 2010:11:28 23:27:22Z, 2010:11:28 23:29:30Z, 2010:11:28 23:30:02Z, 2010:11:29 08:59:26Z, 2010:11:29 10:41:15Z, 2010:11:29 11:25:28Z, 2010:11:29 11:29:12Z, 2010:11:29 11:32:04Z, 2010:11:29 11:36:31Z, 2010:11:29 11:39:57Z, 2010:11:29 23:06:41Z, 2010:11:29 23:21:21Z, 2010:11:29 23:28Z, 2010:11:29 23:38:52Z, 2010:11:30 22:14:52Z, 2010:11:30 22:24:36Z, 2010:11:30 22:47:19Z, 2010:11:30 22:50:30Z, 2010:11:30 23:03:39Z, 2010:11:30 23:27:31Z, 2010:11:30 23:28:28Z, 2010:11:30 23:29:31Z, 2010:11:30 23:34:17Z, 2010:11:30 23:36:04Z, 2011:01:13 13:58:13Z, 2011:01:13 14:09:32Z, 2011:01:13 14:10:35Z, 2011:01:13 14:22:09Z, 2011:01:13 14:52:08Z, 2011:01:13 14:55:06Z, 2011:01:13 16:07:14Z, 2011:01:13 17:14:44Z, 2011:01:13 17:17:56Z, 2011:01:13 17:29:12Z, 2011:10:12 15:33:56+01:00, 2011:10:12 15:33:56+01:00, 2011:10:12 16:28:14+01:00, 2011:10:12 16:31:46+01:00, 2011:10:12 16:42:59+01:00, 2011:10:12 16:46:10+01:00, 2011:10:12 16:49:33+01:00, 2011:10:18 12:19:26+01:00, 2011:10:18 12:24:06+01:00, 2011:10:18 12:41:16+01:00, 2011:10:18 13:04:22+01:00, 2011:10:19 09:24:57+01:00, 2011:10:27 10:35:23+01:00, 2011:10:27 10:39:31+01:00, 2013:03:07 12:19:30Z, 2013:03:07 12:19:30Z, 2013:03:07 12:31:30Z, 2013:03:07 12:44:45Z, 2013:03:07 13:36:15Z, 2013:03:07 13:37:57Z, 2013:03:07 13:38:35Z, 2013:03:07 13:38:36Z, 2013:03:07 13:45:45Z, 2013:03:07 15:02:25Z, 2013:03:07 15:04:15Z, 2013:03:20 12:02:42Z, 2013:03:20 12:08:51Z History Software Agent : Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.5, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0, Adobe InDesign 7.0 History Changed : /;/metadata, /metadata, /metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata, /;/metadata Metadata Date : 2013:03:26 15:31:10Z Creator Tool : Adobe InDesign CS5 (7.0.4) Page Image Page Number : 1, 2 Page Image Format : JPEG, JPEG Page Image Width : 256, 256 Page Image Height : 256, 256 Page Image : (Binary data 5078 bytes, use -b option to extract), (Binary data 7582 bytes, use -b option to extract) Doc Change Count : 200 Format : application/pdf Creator : Corporate Text & Design (www.ctxd.com) Producer : Adobe PDF Library 9.9 Trapped : False Page Layout : SinglePage Page Mode : UseOutlines Page Count : 17EXIF Metadata provided by EXIF.tools