Search Results

3T is a leader in network solutions and logistics / transportation software, 3T's Event software redefines how you optimise the position of your business on a global scale in todays digital world. Top of Page Product line CREATE ORDER ROUTE2 DOCK KIOSK INFORM TRACK MY DELIVERY reCONNECT CONNECT INSIGHTS INCAB The Event product line Add each product to create your required process Start building your Event platform by selecting Create Order or DOCK from below. 2 of the most common products, then add more to replicate your operation processes Get help with building a platform Product line Click on a product to view it Add orders Routing orders Despatch orders Deliver orders Pay for deliveries Report on deliveries CREATE ORDER Add orders [integration] Integrated order receipt View OASIS mini site *OASIS will need IT development. Speak to sales Add orders [manual] Manual entry of orders Get Create Order *Create Order cannot be used until you have add ROUTE to your account ROUTE2 Planning Routing and scheduling Get ROUTE DOCK Bay Management Bay management for inbound and outbound traffic Get DOCK KIOSK Gatehouse control Automated gate control to manage vehicles arriving and departing View Go-Kiosk mini site INFORM Tracking deliveries Central control and visibility of all your deliveries Get INFORM TRACK MY DELIVERY Tracking deliveries [delivery point] Give your customers access to track their own deliveries Included with Event *TMD is activated from the INFORM configuration * TMD can be accessed without a login but deliveries must be tracked with INFORM reCONNECT POD, costs and invoice control Cost control, POD management and invoice reconciliation. Get reCONNECT CONNECT POD, costs and invoice control This is the Carrier portal and in included in all Event products Included with Event *you cannot add to your account, carriers on Event already have this product INSIGHTS Reporting Operational reports and KPI's Included with Event - click for more info *Insights operational reports are included with Event **You can include Qlikview as an addon. Please speak to sales INCAB INCAB mobile Free mobile application for tracking and ePOD Included with Event *ePOD is activated in INFORM configuration **You can use the INCAB DESKTOP to configure how your carriers use INCAB INCAB DESKTOP application Configure how INCAB works for you Get INCAB Desktop

Home / Product Line Our connect API landing page is below, here you can download the swagger, see example json requests and code examples. https://event3tdev.developer.azure-api.net/ Once you are ready to get started please send an email over to servicedesk@3t-europe.com . We will send you back an API key that you can use for testing purposes. Carrier Connect API An API for Carriers to plug into Event This API allows carriers to pull data from Event, update Event with tracking, shipping labels and much more. Retrieve a route from Event In Event each of your routes will have a unique id number, this id can be found in connect. This unique identifier can be used to communicate with Event through our API and pull back route data for a specific route id. Example below. https://event3tdev.azure-api.net/carrierconnect/route/1e11Em49 This will return all the route detail for this route and all the detail for each of the stops on the route. Get all routes by collection date You can also pull all your routes for a given collection date. https://event3tdev.azure-api.net/carrierconnect/routes/2022-09-07 This will return a collection of routes, it will still included all the stop level detail. Get all customers you are connected to in Event If at any time you want to see all of the customers you are connected to in Event, you can call the operation below. https://event3tdev.azure-api.net/carrierconnect/accounts/ No parameter needs to be passed, we will identify who you are by the key you have passed in the request. Update routes and stops in Event The connect API also gives you the ability to send us information and update your routes/stops in Event. For example the below operation can be used to send us back shipping labels, documents and costs. https://event3tdev.azure-api.net/carrierconnect/stops/ Send us tracking updates You can send us back tracking information using the operation below, there is also the option to send us back GPS information so we can track the shipment on route. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Need us to push updates to you? If you need us to push information to you we have got you covered, using the operation below you can register a url for us to send webhook notifications to. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Currently, our recommended best practice for securing Webhooks involves using basic authentication and HTTPS on your endpoint. This will help prevent any altering of any information communicated to you by 3T, prevent any third parties from seeing your webhooks in transit, and will prevent any third parties from masquerading as 3T and sending fraudulent data. 3T performs certificate validation and requires any TLS-enabled (HTTPS) webhook recipients to have a certificate signed by a public trusted certification authority. We do not support sending webhooks to over SSLv2, SSLv3, or any connection using so-called export-grade ciphers. The example response shows the webhooks event you will receive to your endpoint once it is enabled.

JCB US / Canada JCB UK JCB FR JCB CZ JCB NL

Top of Page OASIS v's Event Integration simplified... Home / Learning Centre The Oasis What is The Oasis...? The OASIS is the 3T process for integrating with Event. Order data in and routed data out. What is Event..? Event is the 3T Transport Management Platform. It can receive from you orderline / sku level data, pack and consolidate it to create shipments for routing optimisation through the selection of the optimial equipment type and carrier. It can update these orderlines from triggers sent by you and re-optimise these shipments and routes. It has custom build Packaging, consolidation and both carrier and routing optimisation algorithms What will you need? You will need to be able to send Event accurate, live order information. A new order, when 1st received Any updates to that order already sent to Event [changes to date, quantity, manufacturing estimate etc] To tell Event if it has been cancelled To confirm to Event that it has been despatched [the actual despatch quantity and the POD reference] Where do we start? The integration is an order file. It is also the life cycle of this order as it goes from being a NEW order, through UPDATED [maybe Req Date or quantity] to being despatched [COMPLETE]. The OASIS is made up of several sections: The design of the xml order files Required data fields Optional data fields Custom data fields The send of the xml order files The export of the planned data back from Event Who needs to create the integration? The requirement is to create an OASIS format output that can be imported into Event. This can either be actioned by your internal IT or through a 3rd party comany that can do the translation from your format and process into the Oasis format In the below example, you can see a 3rd party translation company in GREEN. If the integration is direct between Event and your WMS / ERP, the GREEN section would be ignored. Where do i get the specification? This is the specification for designing your integration Inbound order files [NEW, UPDATE, COMPLETE, CANCEL] The OASIS schema 04-01-2021 Sheet 1 = The specification. Design what you want to send.The data fields available, what they mean. Sheet 2 = an example of a NEW xml creation from the schema Sheet 3 = an example of a COMPLETE xml created from the schema Do you have any examples of actu al files? Below are examples of NEW / UPDATE and CANX prefix files using the most popular data fields These are the same with differemt prefixes The COMPLETE file has some different data filelds The OASIS schema NEW / UPDATE / CANX 21-11-2020 .DAF file The OASIS schema COMPLETE 22-11-2020 .DAF file You can use the specification above to map the 'required' data and then decide on what other information you want to provide that means something to you. For example, providing a delivery date for your orders, tell us if the order goes 'on hold' or add 'product' information. Once you have decided on the data to send in addition to the required information, you can build your order xml. Examples of these xml's can also be found above to help you. OASIS integration has 3 levels of complexity: Required data (i.e. source and delivery address) Optional data (i.e. delivery instructions) Custom data (i.e. specific data to you, such as reference numbers) The OASIS process flow NEW To Event From Event Data flow and validation OASIS Send once Send multiple Send multiple API or SFTP NEW order UPDATE order CANCEL order Transport export Routed orders Send once Send once COMPLETE Despatched order Invoice export Optional Send once Example data Unique order number Coll date Del Date Pickup address Destination address Handling unit total Product desctiption ... ... Unique order number Coll date Del Date Pickup address Destination address Handling unit total Product desctiption ... ... UPDATE or CANCEL ROUTE file Carrier name Coll date Del Date Route No Stop No Order numbers Products ... ... Unique order number Coll date Del Date Pickup address Destination address DespatchedHU total Despatched Product ... ... COMPLETE What does Required mean? This is the start of the process. Here we provide you with the data fields that must be included in the build of your Event integration This is the base information we require to make Event work so you can deliver orders to customers What does Optional mean? This is the 2nd part of the process, the Optional data stage. Here we have provided you with the data fields that are most frequently used in enhancing Event integrations. For example you may want to add product information, not just HU level or maybe a collection date or delivery instructions. You have the option to decide... What does Custom mean? The OASIS integration looks to provide you with the most common types of data for your order and in most cases this is enough. But for some customers, they have data types specific to them. For those we have created Custom Fields Custom fields need to be added to the correct section. If you are adding a new item that relates to a product, add it to the product section, if a reference, in the reference section... What does NEW, UPDATE etc actually mean? Order receipt Orderlines from order book integration Address Coll date Del date Booking times Equipment Order numbers Incoterms ... Consolidation [Existing orders] Validation [schema] Can an order be consolidated to an existing order already received? NO YES Find matching orderline and consolidate orderlines on the route Packaging will take all the orderlines provided and calculate the optimal 'package'. Looking at size, stacking, rotation, tilt, to provide a volume. Packaging algorithm Pack the order to calculate the volume. Create a new Stop Check fit on existing route, vehicle size. Recalculate packing and add back to existing route. We use our own global address database and Google servies to validate addresses provided. Address validation Set collection / delivery dates from transit times Auto reoptimise the updated Stop within the day plan Closest together Stops Booking windows Size of Stop Stop instructions Vehicle capacity Best carrier reallocation ... Check plan optimisation Check all ACTVE routes for best Stop placement Can Stop be reoptimised in current ACTIVE day plan? NO YES Equipment carrier Equipment location Best cost Availability Priority ... ... Create new route Update day plan NEW prefix to an order file This is a brand new order that has never been sent to Event. For an order number [which MUST be unique] you will only ever send 1 NEW order file If you send a NEW and then another NEW for the same order number we will ingore the 2nd order file In this case you should have sent an UPDATE after the NEW How does Event know? We use the order number to identify if we have already got it in Event. What if I have different products for the same order number, so multiple new orders for the same order number? Then you will identify them by using the field in the specification to differentiate. 0123456_1 - Product A Required 0123456 Optional 1 0123456_2 - Product B 0123456_3 - Product C UPDATE prefix to an order file This is a change made to an existing NEW. For example, your customer service team update the required delivery date on an order. You will generate and send the same format as the NEW file but with a PREFIX of UPDATE and the new required delivery date. Not just the required delivery date field but the whole order message again. Our process will check the order number, look for the prefix and then identify the update made. Then make this update in Event for the operations team. How does Event deal with these updates in a LIVE environment? In Event we use different status to represent where in the process the order currently sits. We actio the update in different ways based on its current status. COMPLETE prefix to an order file This is a change made to an existing NEW or UPDATE It is specifically sent at the point the order is despatched for delivery [this is usually the despatch team updating what actually left the warehouse] For example, An order is loaded onto a vehicle. The planned quantity is 12 plts but only 10 are ready in time for loading, so despatch will update your system with 10 plts. You create a new order message, prefix COMPLETE and update the DESPATCHED fields with 10. The format is the same as NEW and UPDATE apart from the following fields need to be completed: - you will need to tell HU's us what was despatched for delivery - you can optionally tell us what Product quantity was actually despatched - you will need to tell us the POD reference that your users will search for a POD by. Example 10</ QTY_DELIVERED> and if you are using Products field 2000 What about short deliveries. How do you send the remaining items on the order number? So sometimes not all the product for a delivery is ready at the point of departure. Its goes short. So the COMPLETE order message [from above] will say 12 plts to deliver but only 10 plts were despatched. That means you still have 2 plts to send. In this situation you have 2 options in OASIS: To close the order in your system and to create a new order number for the 2 plts. To use the field to show that it Previous Despatch lets you indicate to OASIS that you want the same order / line number to NOT be ignored [remember, as we already have that combination as a COMPLETE]. By setting the Previous Despatch OASIS will now use order / line / prev destach to check for uniqueness. If that combinatin is unique, allow import. Example for 12plts 0123456 1 Now at point of despatch only 10plts where ready. You have a remaining 2plys that you still want to deliver on the same order / line number combination. 0123456 1 1 CANCEL prefix to an order file This is a change made to an existing NEW or NEW. Not to a COMPLETE. It is the same format, with just a different prefix, 'CANCEL'. This prefix is to be used when an order / line is fully cancelled. If it is cancelled for tomorrow because the customer wants it 6 days later, then its an UPDATE, so update the date If you delete the order in your system, please sent that to Event as a CANCEL. What if the order message fails? Event has an import error function that picks up on failed schema and bad data for correction What file name do I use? The file name will be your agreed Account name and a date/time stamp. The time to seconds. Example: 'ACMEPACKAGING-NEW-11102020234712' 'ACMEPACKAGING-UPDATE-11102020234712' 'ACMEPACKAGING-COMPLETE-11102020234712' 'ACMEPACKAGING-CANCEL-11102020234712' What am I creating? You will use the specification to design your own integration based on the data you want to send. Making sure you have included all the required data fields. You are creating a service to generate and send an xml file from a trigger in your business for: A NEW order is created An order is UPDATED An order is CANCELLED An order is COMPLETED [Despatched] How am I sending it? It will be either ftp or sftp. You can set this up or we can for you It is triggered each time a new order is created, updated, despatched or cancelled. or use our API... You can use our API if you prefer. You will need to subscribe and get an account, then you can follow the documentation to design and test. Go Take me to the developer portal What data can i receive back? When all the routing and scheduling is complete you will want to know how the orders were combined to create routes. We can provide data back to you at 2 different points in the process: At the point a route is accepted by a carrier This will provide data by route on what orders, when, the cost and delivered by who At the point a invoice is created This will provide information on cost additions and final invoice costs The OASIS export schema Transport file 31-01-2022 The OASIS export schema Transport file example 22-01-2022 .TXT file The OASIS .xsd Transport file 31-05-2022 .TXT file The OASIS Transport file example, simple 08-02-2022 .TXT file The OASIS Transport file example multi HU and Stops 08-02-2022 .TXT file The OASIS export schema Invoice file tbc The OASIS export schema Invoice file example tbc A Transport file is sent to you at the point the carrier accepts the route offer What do you do now? Lets get started. Define your operational process to create your integration Use the spreadsheet to get the required data Decide if you need any of the optional data or have custom requirements. Use the xml examples to help build your order message files. When you are ready to test, we can provide an environment for you. We can help check and validate your integration. Send us your OASIS integration spreadsheet Create the xml using the example and send to us for each prefix for an example order Ask us any questions Contact details for OASIS support Email: antony.pratt@3t-europe.com Email: Chad.martin@3t-europe.com Email: Scott.pemberton@3t-europe.com OASIS v's Event How does OASIS affects Event status? Event is controlled by its many different status. These control the stage in the Event process where an order sits and therefore how it is affected by the different prefixes OASIS uses. This will help you understand the impact a late UPDATE will have if a carrier is due to collect it in 20 mins Let's go... How does Event deal with OASIS updates How does OASIS affects Event status? API or SFTP Error handling Format validation To Event Order packing metaheuristics Order consolidation service Carrier selection NEW order Send once To Event From Event Order routing Address validation Default or Custom update rules Default or Custom update rules UPDATE order Send multiple CANCEL order Send once Sent when carrier accepts route NEW, MODIFY, CANCEL Transport export Send multiple Provides the despatched qty Provides Despatch note information COMPLETE Despatched order Invoice export Optional The Event Team

Top of Page Which rate card do i use? Introduction How to build a rate card Rate card validation Self-serve rate card import Uploading rate cards for carriers you connect with To use a non parcel carrier, you will need to add a rate card A rate card simply shows where a carrier will deliver to and how much that delivery will cost... If you are using ROUTE in Event you will need to connect to carriers. To allocate routes to your connected carrier you need a rate card. Carriers in Event have a standard universal rate card or you can arrange and negotiate your own rates. Introduction This guide assumes you have created an account with a carrier, connected to them through Event and now need to upload your negotiated rate card so you can start allocating routes. Connect and allocate Decide on a carrier and create an account [contract] with the carrier (outside of Event) Connect to your chosen carrier through Event* Receive a 'carrier now connected' notification Create a rate card, upload. Start allocating routes to your carrier * A carrier will add themselves to EVENT through being invited. They only need to be invited once and in doing so will create access, login details and a 'connected' presence in the Event ecosystem overall for all current and future Accounts to connect to. You just need to upload a rate card.. Use the rate card template below and follow the instructions here to upload it. * There is not set requirement for naming a rate card upload file. We will add a date time stamp to make sure it is unique Which rate card do i use? Do not change the format of these rate cards! Download, change the date but not the headers or the tab names Which rate card do i use? The rate card templates are simply based on the a tariff in WEIGHT or PALLET based. Are you adding a groupage pallet tariff or one based on weight? hint: FTL is always added as weight. See the examples below to help you quickly create a rate card. If creating an FTL tariff, use the Template 1. This includes EXW. If creating an Groupage PALLET based tariff, use the Template 1 If creating an Groupage WEIGHT based tariff, use the Template 2 Standard plt / weight tariff click to download Template 1 FTL all postcode Rate card template PLT - Day / night / weekend / holiday 19-04-2023 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc This tariff includes where a carrier provides different costs based on the time of day or day of week It is only for the FTL sheet, not for Groupage Column J cannot be used if any of columns O-T are being used. Leave J as = blank Column U can be used with either column J or columns O-T. It can also be used on its own. The daytime setting can be configured in AccountVITALS / Setup Basics / Rate Card Bank holidays can be configured in AccountVITALS / Setup Basics / Holidays The headers for columns O-U will be used to show as the servie in Change Carrier Template 2 Groupage all UK postcode rate card template PLT. Upto 10 plts 12-02-2019 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Template 3 Rate card template weight - Groupage 12-02-2019 - AP Hint: Its important to define if the Groupage tariff is per weight band or pallet. The excel spreed sheet tab defines this Template 4 Rate card template weight bands- Groupage 17-09-2021 - AP This function includes 2 new columns. 'PER' column and 'ROUNDING' column. PER = rate per kg. This can be 1 as std or 100kg ROUNDING = set to round by, e.g. 10 (to mearest 10) The PER calculation example is: 99-250kg line in tariff rate = 39.98 Set PER rate as 100kg Shipped 145kg Set rounding to 10kg (nearest 10kg) so 150kg calculated rate = 39.98 x 1.5 Template 4a Rate card template weight bands with minimum charge 14-09-2022 - AP Template 5 Template 5 Rate card template pallet per lifts - Groupage 17-09-2021 - AP This function is the standard Groupage rate card by pallet. The difference is a configuration to set between per plt or per lift. This Lift configuration will use the stackability from the Stop. If 7 plts and stackable, lifts = 3 lifts The default is per pallet. Groupage rate card by m3 Template 6 GRP rate card by m3 08-05-2021 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Use column F & G for calculating Stop volume (10-15 m3 band = 4.50 x total m3) Use column H & I for calculating Stop volume as a fixed total cost (10-15 m3 band = 180.00 fixed rate) To set the calcuation at PLANNED or DESPATCHED status, use the configuration in Carrier VITALS To speed up creating multi equipment type FTL rate cards... Template 7 FTL x3 equipment types UK postcodes template 12-02-2019 - AP Template 8 FTL x2 equipment types UK postcodes template 12-02-2019 - AP Distance tariff by metric Template 9 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated from a source postcode and by a metric, i.e. per tonne Distance tariff from point A-B Template 10 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated based on the actual distance banding from any location to any location. It is not dependant on any metric, simply a cost per distance by an equipment type Day rate tariff A day rate tariff is a rate that a carrier charges for either a specific amount of time or a set distance. Using the day rate tariff in Event will impact the way in which a rate is calculated in ROUTE2. A user can select a Day Rate carrier, see the rate in Change Carrier. To create a connected Day of trips for a vehicle, the user cn drag a route onto the Day rate route line. The route will be updated with a Trip number automatically Template 11 Day rate tariff for distance or time 25-02-2021 - AP Max distance Max distance = the maximum distance this vehicle can travel in 1 day for the tariff. Either set to 99999 to activate TIME columns or add in the actual max distance. To use only mileage as a calculator, you need to set the time band as 00:00 - 23:59. This will ignore the time. To / From Band Time To / From Band Time =This time is used to determine the starting and ending time of this vehicle. To / From Band Time =This time is used to determine the starting and ending time of this vehicle. to use only the time band as a claculator, you need to set the max mileage as 99999 How does Day Rate tariff work in ROUTE2? Day Rates are basically FLEET routing. A Day Rate is all about getting as many trips per day from the vehicle for a set price. A Day Rate carrier will do as many routes in one day as possible. We call these connected routes 'Trips'. For example: Day Rate carrier vehicle 1, 1st route = Trip 1.1 Day Rate carrier vehicle 1, 2nd route = Trip 1.2 Day Rate carrier vehicle 1, 3rd route = Trip 1.3 Day Rate carrier vehicle 2, 1st route = Trip 2.1 Day Rate carrier vehicle 2, 2nd route = Trip 2.2 To create a Trip you must allocate the route to a carrier that has a Day Rate. To create a multi trip you can drag any Route onto the Trip. To change the Trip sequence you do this in Route Detail for the Trip. To change from a Day Rate carrier you Change Carrier. The cost for a Day Rate is based on the tariff. The tariff will be based on the total distance or total time. If distance, the logic is: The distance for a Trip, double it to create the return leg The distance is fixed for the tariff, so ROUTE2 will not let a user add a trip if the total distance for all trips is greater than the max mileage Example: Tariff = max 300 miles. Trip 1.1 = 100miles return, Trip 1.2 = 100 miles return, Trip 1.3 = 102 miles return, then Trip 1.3 cannot be added as 2 miles over agreement. The time tariff is calculated as the total time for the Trips plus waiting time. Time is a return time. In ROUTE2 we only show 1 way, you will need to double this if Day Rate carrier There is a 45 min waiting / loading / unloading time If time, the logic is: Create a FLEET carrier So you can recognise it in ROUTE2. Now create your rate card. Creating a FLEET route To create a FLEET Route you need to allocate to your Day Rate carrier. The Route will show the 'return trip' icon and a TRIP NUMBER Gant view You can also change view and look at the Gant view Create a FLEET carrier So you can recognise it in ROUTE2. Now create your rate card. 1/12 Parcel tariff by service Template 12 Parcel tariff by weight and service 11-10-2021 - AP Tariff for calculating parcel wieght and service through SLM rules Do I have to create a file per carrier? No. To make it easier you can add all carriers onto 1 file and import or create separately. Decision is yours... What if i want to use a carrier but i have no rate card? You do not need to add a rate card for a carrier to be able to use the carrier in Event. Using Event's 'Spot Rate' function lets you allocate to any carrier at any time How does Spot Rate work? show me How to build a rate card How to build a rate card Groupage, FTL, EXW carriers all need a rate card in Event... This guide will step through how to build a rate card Vitals For a carrier to be available in Event, they must have a rate for the destination. The rate can be 0.00. Use the template provided below. Rate card type A rate card is added based on being a weight based rate card or PLT based. If you are adding a Groupage tariff for weight use the weight card, it PLT use the PLT card. For FTL it is always imported as weight. Upload to Event When complete please e-mail currently to: antony.pratt@3t-europe.com Email header: Rate Card Upload. Environment: QA, LIVE Carrier name Vitals For a carrier to be available in Event, they must have a rate for the destination. The rate can be 0.00. Use the template provided below. 1/19 Rate card validation Rate Card Validation So once you have uploaded a rate card, AMI will validate the contents and notify you of the result. The validation will include format and contents, providing information, where a failure occurs on what the failure is. Initial validation that must be passed to proceed; 1. Correct column headers Validation will fail if the headers are named differently to the template. Validation error message ' Column headers are not named correctly' 2. Correct order of the columns Validation will fail if the columns are not in the correct position. Validation error message ' Columns are not in the required positions' 3. Carrier ID Validation will pass if the carrier ID exists on the Account being uploaded to and will fail if the carrier does not exist in Account receiving upload. Validation error message for notification and storing ' Carrier ID must match the carrier's code in Carrier VITALS' Specific validation 1. Origin country Is required. Format is ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 2. Origin code Is required. Format can be numbers or letters. CV, 01, 850. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV, 11, 98' 3. Destination country Is required. Format ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 4. Destination code Is required. Format c an be numbers or letters . CV 22 6HL , CV 22, CV , 01, 01000, 10000. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV22, 11, 98' 5. FromBand Is required. A number of at least 0. Can be format 1.000000001. Validation error message 'Must add a number in the format 1 ' Example: for FTL this would be 1 6. ToBand Is required. A number of at least 0. Can be format 1.000000001 if Groupage. Validation error message 'Must add a number in the format 2.000000001 ' Example: for FTL this would be 99999 7. Stop rate Is required if Delivery type = FTL. Format must be 0.00. Validation error message ''Rate must be included for FTL and cannot be left empty. It can be 0.00' 8. Equipment Is required. Validate the equipment type against the Account Equipment database and if a match can be found allow, if no match fail validation. Validation error message '[failed equipment name] is not a valid equipment type for this Account. Please use a valid type or update your equipment' 9. SLM rule Not required. Default is blank. This is a specialist rule for RULE ASSIST only. Max characters = 10 Validation error message where not matching rule is found in SLM 'No matching rule found in Route Assist rules' To use this rule, ROUTE ASSIST rules for the carrier must match those in the rate card. To use this function, add the SLM rules to the ROUTE ASSIST column called 'Groupage type' *this rule will lookup ROUTE ASSIST rule, take the associated Groupage Type and when looking up the rate card, will look to match a SLM rule to the Groupage type added. 10. Mode Is required. Must be LAND, AIR or SEA. AMI will default to LAND if not added. If added but not one of the 3... Validation error message 'Mode must equal LAND, SEA or AIR in this format ' 11. Service Is required. Default is Economy. AMI will default to Economy if not added. If added but not Economy, check for match in Account's Service and update. No validation message. 12. Delivery type Is required. Must be '2' for FTL or '4' for Groupage. Validation error message 'Delivery type must be '4' for GROUPAGE or '2' for FTL' 13. Cost Is required. validation just a number. Must be a number in format 0.00, 200.00. Can be 0.00 if no rate is known. Validation error message 'A rate must be included and cannot be left empty. Format is 0.00. It can even be 0.00 ' Notes: As you create rate cards, we advise that you save them and duplicate them as required for new carriers to make it easier and faster to on board new carriers The Event Team designed by humans : built with machines

Chargeable weight For a transport company to sell their free space more efficiently, the industry developed a concept known as Chargeable Weight... Why do carriers not use gross weight or volume when calculating freight costs? Some goods are heavy but take up very limited space, others are really light but take up alot of space in a trailer. How do we calculate Chargeable Weight? We use these calculations: Gross weight Loading meter (Ldm weight) Volumetric weight Chargeable weight = the largest weight from the 3 calculations above Let us assume that we want to ship a consignment that consists of 10 pallets with the following measurements: Dimensions of each pallet [mm]: 1200 x 1000 x 1800 Weight of each package [kgs]: 960 gross weight Step 1: Add the weight factors Each carrier will have a: Volumetric [cbm] factor. For example, 1 m3 = 333 kgs Loading meter [Ldm] factor. For example, 1 pallet space = 1250 kgs Step 2: Calculating the gross weight of the cargo The gross weight of our cargo is 9600 kgs . Step 3 : Calculating the Ldm of the consignment We will multiply the length and width of the consignment and then divide by the width of the trailer. We are using a default of 2.4m. [= 0.5 ldm] Now multiply that figure by the number of pallets. [= 5 ldm] Example of the carriers Loading meter factor = 1250 kgs / ldm LDM weight = Total Ldm of the consignment x road shipment Ldm weight factor Ldm Weight= 5 Ldm x 1250 kgs/ Ldm = 6250 kgs Step 4 : Calculating the volumetric weight of the cargo We will multiply the volume of the consignment with the volumetric weight factor of the carrier to get the volumetric weight. Example of the carriers volumetric weight factor = 333 kgs / cbm Volumetric Weight = Total volume of the consignment x road shipment volumetric weight factor Volumetric Weight= 21,6 cbm x 333 kgs/ cbm = 7192,8 kgs Step 5 : Calculating the chargeable weight of the cargo: We now compare: the gross weight the Loading meter weight the volumetric weight of the consignment and select the biggest amount. This will be your chargeable weight for the given shipment. Stacking of a consignment This is based on the information received through the interfaced orders or by using the stackable function in Create Order. Event will then divide the number of HU's by half to show as stacked. note : Users can select the calculations that they want to use. For example they may only calculate Gross weight and Volumetric weight. Implementing Chargeable Weight How to start calculating This guide will step through getting started with activating Chargeable Weight Chargeable weight You activate chargeable weight by carrier, so select the correct carrier in Carrier Vitals, then their Rate Card tab. Help Use the '?' help to open the Chargeable Weight mini site. Save Save your changes. Chargeable weight You activate chargeable weight by carrier, so select the correct carrier in Carrier Vitals, then their Rate Card tab. 1/8 Now it's active, how do i use it? Once activated for a carrier, you don't need to worry about anything. Event will tell you if you need to know. Selecting a carrier activated with the Chargeable Weight calculation, Event will calculate the cost for you. Don't worry. Simply select stacked if the shipment is stackable and you will only see this if the carrier charges by Chargeable Weight If changing carrier Event will show you the carriers charging mechanism just so you are aware we know and the calculation includes it. Try selecting and deselecting 'stackable' just to see the calculation change! Requirements Ready to activate Chargeable weight for your carriers? Go to Chargeable Weight

Top of Page Requirements Direct-to-Print Labelling The no-hands, web based label solution for fully integrated customers... Are you looking to print parcel labels directly from packing the item? No manual searching or scanning for the HU in Event, just pack and print? The Direct-to-Print application uses the Label Station ID added to the Packing message to trigger the print of the label you have just packed. The application is a windows application It needs to be downloaded onto each Label Station PC Each PC must have a default printer setup Each Label Station must be given a unique name to differentiate it You will need to add this unique Label Station ID to the PACK message you create On receipt of the PACK message, Event will process the request automatically and output the correct label for exactly the PACK sent. Expected performance is approx. 10 seconds per label* note : Direct-to-Print works only per PACK message, it does not allow for consolidation as it creates per HU reference. Ready to activate? Make sure all the requirements have been met... Get Direct-to-Print Implementing Direct-to-Print How to start direct label printing This guide will step through getting started with hands free label generation What is Direct-to-Print? To find information for your users, you can search for it in 3t-event.com... 'How to' guide ...or access it from the activation page in Event itself. Save ...save the status. Direct-to-Print is now LIVE and ready to receive. What is Direct-to-Print? To find information for your users, you can search for it in 3t-event.com... 1/19 Now it's active, how do i use it? Once downloaded, the application will need to be opened each time the PC is switched on by the user. PIN the application fro the Start menu to the Task Bar to make it easier to access. Click on it to start it and minimise it again Start packing and labels will print on the PC default printer There is no need to open Event as the application works without it physically open. Application Open and minimise each shift. ROUTE configuration In ROUTE configuration, you can see if Print-to-Label is active. Application Open and minimise each shift. 1/2 Requirements Requirements to use Direct-to-Print A valid Event account with ROUTE, integrated parcel carriers with valid accounts. A valid interface from your ERP to Event [including the Label Station tag] Ability to download the windows application to each PC on each Label Station .net framework on each PC (https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer ) A default label print for each Label Station PC A package to put the label on... Support process At any point, when the application cannot connect and 'stops listening for labels' we will automatically generate a support ticket to the 3T Service Desk and your Admin account email address. This will be considered a Priority support ticket and acted on with immediate effect. Where a label cannot be returned, an error label will be produced to advise you of the issue If a label has a hazardous code associated we will generate an additional label to advise of this. * Label generation speed is approximate and based on the quality of your internet connection. Tested as below: http://www.speedtest.net Download speed 73.92 Mbps Upload speed 86.70 Mbps Response time 10 ms The Event Team designed by humans : built with machines

Top of Page SAICA Thrapston SAICA Sywell Home / SAICA PACK We provide sustainable recycled paper, corrugated cardboard packaging and flexible packaging manufacturing solutions as well as solutions for waste management and the recovery of waste. We develop attractive packaging for food, beverages, perfumes and detergents that increase the presence of the product on the shelves in compliance with Retail Ready Packaging requirements. Easy to transport and store in all phases of the logsitics chain. SAICA Thrapston SAICA - Thrapston Production Production Thrapston prod.event.customer5@3t-europe.com saitprod01! Production Sywell prod.event.customer6@3t-europe.com saisprod01! Production Corby prod.event.customer7@3t-europe.com saicprod01! QA [interfaced] Account ID: 40007 UAT uat.event.customer14@3t-europe.com saiuat01! UAT wapox22824@edultry.com Sparhawk72 Rate cards Truckwright 100220 QA siaca@mailboxt.net Sparhawk72 016c6f3a-4546-4dc6-8ab4-a7189499db6c KGT 100220 PC Howard 100220 MTS Logistics 100220 Wise Logistics 100220 QA Carrier Truckwright Ltd truckwright@mailboxt.net Sparhawk72 QA Carrier KGT kgtsaica@mailboxt.net Sparhawk72 QA Carrier PC Howard pchoward@mailboxt.net Sparhawk72 SAICA - Sywell - Amazon SAICA Sywell Manual Ordr Entry Account ID: LIVE Account users SAICASywell.SuperUser@3t-europe.com SywellProd12 https://qa.3t-event.com/ QA Account users sywell@inmail92.com Sparhawk72 QA Connect users amazon@inmail92.com Sparhawk72 How to create a manual order Select Create Order Is the collection date correct? We will set to the current date but remember to change if collection is different. Order complete The order has now been released to ROUTE and the planners have been notified of the new order. Select Create Order 1/11

Top of Page The Oasis Integration simplified... What is Application Integration Application integration connects and combines different software applications to create workflows that streamline processes. By integrating two or more applications, businesses can automate mundane tasks that would otherwise require manual entry and management. The primary mechanism for achieving this is through Application Programming Interfaces (APIs), which are rules and protocols allowing different applications to communicate and share information. This helps them save time and money while ensuring accuracy in data processing. What is The Oasis...? The OASIS is the 3T process for integrating with Event. It is a fully documented integration that provides the 3T and the customer the ability to create a workflow of order data received by the customer and to map that data between systems. To create an order for shipment, Event requires at the very least: a unique order number, a source address, a delivery address, a date to deliver a quantity of goods to deliver It also requires information on when an update is made to that delivery This can be in the form of a customer mapping data directly into the Oasis api or the customer providing the mapping from their own data outputs so we can receive and map to OASIS. The above is not always straight forward and depends on the customers technical ability and access to its order data, The preference is for the customer to integrate to OASIS, as they know their data well and OASIS proivides the perfect workflow into Event to get the best from the TMS. What is Event..? Event is the 3T Transport Management Platform. Where you can control the transportation of your product to your customers. So you are creating the ability to put your order data into a format that can be used for: Routing and scheduling Parcel selection and labelling Bay Managment Your carriers Your carrier rates The delivery process The POD and Invoice process Reporting So it is important that this order data is comprehensive enough that your routing and scheduling team have the correct information to be able to create vehicle loads and can fill this accuratly to get the best fit and cost and that you have the required information in the reporting when its all delivered. Why would you want to use this integration? As a TMS, the requirement is to provide the best possible solution for delivering a customer's product. We realised that even though we could and have integrated with many different systems, these systems often had non-standard schemas and integrations were often long, expensive, complicated and problematic to maintain. So we designed a simple, customisable interface that flawlessly integrates with Event. This is a purpose built, self-service, 2-way integration for Event, so it works in perfect harmoney with Events complex functionality. Its SKU level, designed to work with Events complex consolidation, packaging and routing functions It has been designed to follow an order pattern of NEW, UPDATE, CANCEL and COMPLETE information It is maintained and monitored by our own integration team and their purpose-built insights software 24/7 It is fully customisable, making it as simple or as complex as is required and allowing for customers to still provide any non-standard data that is important to their business What will you need? You will need to be able to send Event accurate, live order information from your order system. A new order, when 1st received You will need to be able to identify updates to that order already sent to Event [changes to date, quantity, manufacturing estimate etc] To tell Event if the order has been cancelled To confirm to Event that it has been despatched or packed [the actual despatch quantity and the POD reference if required] [Optional} To receive in return your order data back as routes. Where do i get the specification? Event has 2 integration methods. Where do we start? 1 Parcel You pick, pack and label parcels Primary service is parcel. You may use limited groupage or palletised services You use well known parcel carriers (DHL, FedEx, UPS) This is the important one! How does your business work? Let's go... Welcome to Events Oasis for Parcel... 2 Truckload, part load, groupage You despatch mainly palletised goods or loose load Primary service is NOT parcel You use general haulage carriers Let's go... Welcome to Events Oasis for Freight... Contact details for OASIS support Email: antony.pratt@3t-europe.com Email: chad.martin@3t-europe.com The Event Team

Top of Page Requirements Create a PACKAGE Parcel label integration, but not as we know it! When you only have an order message but no packing message... ...then you need to 'Create a PACK'. The Create PACK application enables the user to create a Packing message to trigger the print of the label you have just packed. What does it actually do? In integration terms, if you are automating your parcel label operation, you require 4 things: 1. An 'ORDER' to tell the parcel carrier what to send and where to send it. 2. A 'PACK' to tell the parcel carrier what size and weight the parcel with the orders in is. 3. A 'RULE' to decide, based on point 1 & 2, which parcel carrier and service to select 4. A 'LABEL' to put on the parcel. Create PACK is a semi manual process that replaces point 2 above, when integration is not possible and as a customer you have no automated way to provide packing information. With 3 pieces of information, you have the information required to send a parcel. How does it work? Activate Direct-to-Print labeling This will automatically print your label on your selected printer when you hit 'print' Scan the parcel barcode The parcel is packed with a barcode of the order No. on it. Simply scan the barcode. This links to the Order message with address, product information etc If the delivery is an export, Create PACK will ask you to add a value for customs. Scan the box type used The parcel carrier will need to know the dimensions of the package. You can store these, create barcodes and simply scan the correct package type Weight and add the weight The actual 'packed' weight is required. Weight it and add. Collect the label from your selected printer. On receipt of the PACK message, Event will process the request automatically and output the correct label for exactly the PACK sent.Expected performance is approx. 10 seconds per label* note : Create PACK is only for customers that can provide an integrated Order file but cannot provide an integrated Packing file Ready to activate? Make sure all the requirements have been met... Get Create PACK Getting started with Create PACK How to use Create PACK This guide will step you through starting out Open Create PACK Open Event and search for Create PACK. Create pack screen The Create PACK screen will open Next label ...and the screen will reset itself. Open Create PACK Open Event and search for Create PACK. 1/14 How to add in a barcode to a Packaging type Open Create Order Open the configuration Add / delete the required packaging types in the HU section. Remember to add a barcode reference. Save How to use barcodes with Create PACK Make sure your packaging types have barcode references associated to them Go to: a free barcode generator website Create a barcode for each packaging type and copy them onto a word document Print out document and tape down in the area you scan Now simply scan the correct barcode to make selecting the correct packaging type easy! Check list Make sure you have all you need setup to start labelling Requirements A valid Event account with ROUTE, integrated parcel carriers with valid accounts. Direct-to-Print activated - .net framework on each PC ( https://www.microsoft.com/en-us/download/details.aspx?id=53344) Note: Changing your default printer after you have downloaded the above application will require a reinstall. A valid interface from your ERP to Event for Order R OUTE ASSIST rules for determining carrier and service selection. (You can simply use select cheapest carrier option) A package to put the label on... Support process At any point, when the application cannot connect and 'stops listening for labels' we will automatically generate a support ticket to the 3T Service Desk and your Admin account email address . - coming soon Q3 2019 This will be considered a Priority support ticket and acted on with immediate effect. Where a label cannot be returned, an error label will be produced to advise you of the issue. - In Route, the package will be set with a status of 'E', the Stop will be updated to red and a notification will be sent to users that subscribe. If a label has a hazardous code associated we will generate an additional label to advise of this. * Label generation speed is approximate and based on the quality of your internet connection. Tested as below: http://www.speedtest.net Download speed 73.92 Mbps Upload speed 86.70 Mbps Response time 10 ms The Event Team designed by humans : built with machines

Top of Page Order Message file Pack Message file Despatch Message file Transport Message file The Oasis Integration simplified... What is The Oasis...? The OASIS is the 3T process for integrating with Event. Order and Packing data in, carrier allocation and labels out What is Event..? Event is the 3T Transport Management Platform. Where you can control the transportation of your product to your customers. So you are creating the ability to put your order data into a format that can be used for: Routing Carrier selection Label creation Costing Reporting What does Event do with the order information? Event has integrations with all the main parcel carriers. Providing a direct link to your account information, services available and tariffs. It will select the best carrier and service option, provide cost visibility, labels and tracking updates. This integration is used for dedicated parcel requirements, where a customer is packing boxes of picked goods that are being delivered through the parcel network, rather than a few parcels in a predominantly bulk freight environment It is different because it uses PACK messages aswell as order messages, as for optimal parcel deliveries we need actual packed weight and dimensions to get the correct service level and cost from your selected carrier How does parcel integration work? You will need to be able to send Event accurate, live order information. In the below order... A new order, when 1st received Sent in advance A PACK message, when orders are packed Send at the time the orders are packed into the packaging ORDER message The order message is the order, date, addresses and products. We require this as the order request. We hold it until it is PACKED PACK message A PACK message is a separate message file. It is the Handling Unit, the box, parcel, jiffy... It includes the dimensions and weight so that the correct carrier, weight and service can be selected. It is created when the user in the warehouse packs the customer order into the required packaging. Once you have sent the PACK message, Event will automatically select the carrier, service level and provide a label to to printed and added to the package. Transport Update (Return) message This is a message we will send to you each time your user physically prints a label for a HU Despatch message This is a message that you will sent to us when you physically despatch a HU or shipment. This can be a combination of HU's. Where do we start? Where do i get the specification? This is the specification for designing your integration Order Message File (OMF) Order Message file The OASIS OMF schema 11-05-2021 .daf file The OASIS OMF xsd 29-04-2021 .daf Sheet 1 = The specification. The format Sheet 2 = an example of a NEW xml creation from the schema Do you have any examples of actu al files? Below are examples of NEW and PACK message files using the most popular data fields These are the same with differemt prefixes The OASIS schema 29-04-2020 .daf file PACK Message File (OMF) Pack Message file The OASIS PACK schema 27-07-2021 .daf file The OASIS PACK xsd. 21-07-2021 Sheet 1 = The specification. The format Sheet 2 = an example of a PACK xml creation from the schema A PACK is only ever for 1 handling unit and can contain 1 or multiple Orders for a customer. Do you have any examples of actu al files? Below are examples of the PACK message files. The OASIS PACK 29-04-2020 .daf file The OASIS PACK - multi lines 29-04-2020 .daf file Despatch Message File Despatch Message file The OASIS Despatch xsd. 16-07-2021 .xsd Do you have any examples of actu al files? Below are examples of the Despatch message files. The OASIS Despatch 16-07-2021 .daf file The Return message will be sent to us when the HU's are despatched RETURN Message File (Transport Update) The OASIS Return schema 11-05-2021 .daf file Transport Message file The OASIS Return xsd. 11-05-2021 Sheet 1 = The specification. The format Sheet 2 = an example of a RETURN xml creation from the schema Do you have any examples of actu al files? Below are examples of the Return message files. The OASIS Return 29-04-2020 .wmt file The Return message will be sent back to you as each label is PRINTED. What does NEW, UPDATE etc actually mean? UPDATE prefix to an order file This is a change made to an existing NEW. For example, your customer service team update the required products on an order. You will generate and send the same format as the NEW file but with a PREFIX of UPDATE and the new products. Not just the required products fields but the whole order message again. Our process will check the order number, look for the prefix and then identify the update made. Then make this update in Event for the operations team. Do you need to build an update process? The majority of our parcel customers donot use the update process, adding NEW orders as required. In most cases the orignal order is replaced by a new order. CANCEL prefix to an order file In this integration the Order Message file (OMF) is not actioned until the items are packed ready to be sent and the PACK message is received. If we donot receive a PACK message for an Order we will simply not action it. So no cancellation messages are required What if the order message fails? Event has an import error function that picks up on failed schema and bad data for correction What file name do I use? The file name will be your agreed Account name and a date/time stamp. The time to seconds. Example: 'ACMEPACKAGING11102020234712' What am I creating? You will use the specification to design your own integration based on the data you want to send. Making sure you have included all the required data fields. You are creating a service to generate and send an xml file from a trigger in your business for: When a NEW order is created When a parcel is physically PACKED How am I sending it? It will be either ftp or sftp. You can set this up or we can for you It is triggered each time a new order is created, or PACK received What do you do now? Lets get started. Define your operational process to create your integration Use the spreadsheet to get the required data Use the xml examples to help build your order message files. When you are ready to test, we can provide an environment for you. We can help check and validate your integration. Send us your OASIS integration spreadsheet Create the xml using the example and send to us for each prefix for an example order Ask us any questions What else do i need to know? For system and PC requirements, label printing information you can visit the below... Let's go... Minimum System requirements... Contact details for OASIS support Email: antony.pratt@3t-europe.com Email: Scott.pemberton@3t-europe.com The Event Team

Top of Page Privacy Policy Security Policy The Event policies Privacy Policy Our Privacy Principles If you read nothing else, please read this: The most fundamental privacy principle 3T Logistics Ltd (“we”, “3T”, “us” and “our”) follow is that by default, anything you add to 3T’s EVENT control Platform is private to your Company. That is, files shared, orders added within a specific EVENT control application requires authentication as a member of that team. 3T is the custodian of data on behalf of the companies that use the EVENT control Platform. We don’t own EVENT user data. EVENT users own their data. They like it that way and so do we. At 3T we believe that more transparency is better than less. We try to make our product easy to use, with settings and options that are easy to find and understand. This is good for privacy, good for the product, and good for 3T customers and users. Privacy goes hand in glove with security and confidentiality. We see these things being the three legs that keep the stool balanced and upright. Each is as important as the other and if one is missing the stool won’t stand. They are all very important to us and we take them very seriously. For the purposes of the applicable data protection laws, legislation and regulations, the data controller is 3T Logistics Ltd. We are registered in England and Wales under company number 03973355 and have our registered office at 5 Smith Way, Grove Park, Enderby, Leicester, LE19 1SX. 2. Information we collect and receive We collect different kinds of information. Some of it is personally identifiable and some is non-identifying or aggregated. Here are the types of information we collect or receive: Information you give us This is information about you that you give us by filling in forms on our site or by corresponding with us by phone, e-mail or otherwise, it includes information you provide when you register to use our site, subscribe to our service and when you report a problem with our site. The information you give us may include your name, address, e-mail address and phone number and financial and credit card information. Any information you add to your profile is visible to other people on your team depending on their level of permission. Log data. When you use EVENT control, our server’s automatically record information, including information that your browser sends whenever you visit a website or your mobile app sends when you’re using it. This log data may include your Internet Protocol address, your browser type and settings, the date and time of your request, information about your browser configuration and plug-ins, language preferences, and cookie data. Log data does not contain message content and is not routinely deleted. Device information. In addition to log data, we may also collect information about the device you’re using EVENT application on, including what type of device it is, what operating system you’re using, device settings, unique device identifiers, and crash data. Whether we collect some or all of this information often depends on what type of device you’re using and its settings. Geo-location information. Precise GPS from mobile devices is collected only with your permission. WiFi and IP addresses received from your browser or device may be used to determine approximate location. 3. Cookies About Cookies When you use or access the EVENT control Platform, we may use small text files containing a string of alphanumeric characters called cookies to improve the overall experience, among other things. A cookie is a piece of data stored on the user's hard drive or browser containing information about the user. Information from cookies alone generally do not provide us with information to personally identify you. 3T may use both session cookies and persistent cookies. A session cookie generally disappears after you close your browser. A persistent cookie remains after you close your browser and may be used by your browser on subsequent visits to the EVENT control Platform or other web sites. Persistent cookies can generally be removed by you. Please review your web browser "Help" file to learn the proper way to modify your cookie settings and to remove cookies. Cookies that we use We use cookies for the following purposes: (a) Authentication – we use cookies to identify you when you visit our website and as you navigate our website. (b) Status – we use cookies to help us to determine if you are logged into our website. (c) Personalisation – we use cookies to store information about your preferences and to personalise the website for you. (d) Security – we use cookies as an element of the security measures used to protect user accounts, including preventing fraudulent use of login credentials, and to protect our website and services generally . Cookies used by our service providers (a) Our service providers use cookies and those cookies may be stored on your computer when you visit our website. (b) We use Google Analytics to analyse the use of our website. Google Analytics gathers information about website use by means of cookies. The information gathered relating to our website is used to create reports about the use of our website. Google’s privacy policy is available at: https:/www.google.com/policies/privacy/. Managing Cookies Most browsers allow you to refuse to accept cookies and to delete cookies.The methods for doing so vary from browser to browser, and from version to version. You can however obtain up to date information about blocking and deleting cookies via these links: (a) https://support.google.com/chrome/answer/95647?hl+en(Chrome) ; (b) https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences (Firefox) ; (c) http://www.opera.com/help/tutorials/security/cookies/(Opera); (d) https://support.microsoft.com/en-gb/help/17442/windows -internet-explorer-delete- manage-cookies (internet Explorer); (e) https://support.apple.com/kb/PH21411 (Safari); and (f) https://privacy.microsoft.com/en-us /windows-10-microsoft-edge-and-privacy (Edge). Blocking all cookies will have a negative impact upon the usability of many websites. If you block cookies, you will not be able to use all the features on our website. 4. How we use your information We use your information for the following Providing the EVENT service. We use information you provide to carry out our obligations arising from any contracts entered into between you and us and to provide you with the information, products and services that you request from us. To authenticate you. Understanding and improving our products. To make the product better we have to understand how users are using it, we call this solo.COMMUNITY. We have a fair bit of data about usage and we intend to use it many different ways to improve our products, including research. This policy is not intended to place any limits on what we do with usage data that is aggregated or de-identified so it is no longer tied to an EVENT user. Investigating and preventing bad stuff from happening. We work hard to keep EVENT secure and to prevent abuse and fraud. Communicating with you Solving your problems and responding to your requests. If you contact us with a problem or question, we will use your information to respond to that request and address your problems or concerns. Email messages. We may send you service and administrative emails. We may also contact you to inform you about changes in our services, or our service offerings. These messages are considered part of the service and you may not opt-out of them. In addition, we sometimes send emails to EVENT users about new product features or other news about EVENT or 3T. You can opt-out of these at any time by contacting us at service.desk@3t-europe.com . Personal data that we process for any purpose or purposes shall not be kept for longer than is necessary for that purpose or those purposes. 5. Disclosure of your Information You agree that we have the right to share your personal information with: Any member of our group, which means our subsidiaries, our ultimate holding company and its subsidiaries, as defined in section 1159 of the UK Companies Act 2006. [HS1] Our payment service providers. We will share transaction data with our payment services providers only to the extent necessary for the purposes of processing your payments, refunding such payments and dealing with complaints and queries relating to such payments and refunds. You can find information about the payment services providers’ privacy policies and practices at [URLs]. 6. Security 3T takes reasonable steps to protect information you provide to us as part of your use of the 3T service from loss, misuse, and unauthorized access or disclosure. When you enter sensitive information (such as sign-in credentials) we encrypt the transmission of that information using secure socket layer technology (SSL). We follow generally accepted standards to protect the personal data submitted to us, both during transmission and once we receive it. However, no electronic or email transmission or digital storage mechanism is ever fully secure or error free. To learn more about current practices and policies regarding security and confidentiality, please see our Security Practices; we keep that document updated as these practices evolve over time. 7. Your Rights If the data you provide to us is personal data you have principal rights under data protection law which include: - the right to access; - the right to reflection; - the right to erasure; - the right to restrict processing; - the right to object to processing; - the right to data portability; - the right to complain to a supervisory authority; and - the right to withdraw consent. You have the right to confirmation as to whether or not we process your personal data and, where we do, access to the personal data, together with certain additional information. That additional information includes details of the purposes of the processing, the categories of personal data concerned and the recipients of the personal data. Providing the rights and freedoms of others are not affected, we will supply to you a copy of your personal data. The first copy will be provided free of charge, but additional copies may be subject to a reasonable fee. You have the right to have any inaccurate personal data about you rectified and, taking into account the purposes of the processing, to have any incomplete personal data about you completed. In some circumstances you have the right to the erasure of your personal data without undue delay. Those circumstances include: the personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed; you withdraw consent to consent-based processing; the processing is for direct marketing purposes; and the personal data have been unlawfully processed. However, there are certain general exclusions of the right to erasure. Those general exclusions include where processing is necessary: for exercising the right of freedom of expression and information; for compliance with a legal obligation; or for the establishment, exercise or defence of legal claims. In some circumstances you have the right to restrict the processing of your personal data. Those circumstances are: you contest the accuracy of the personal data; processing is unlawful but you oppose erasure; we no longer need the personal data for the purposes of our processing, but you require personal data for the establishment, exercise or defence of legal claims; and you have objected to processing, pending the verification of that objection. Where processing has been restricted on this basis, we may continue to store your personal data. However, we will only otherwise process it: with your consent; for the establishment, exercise or defence of legal claims; for the protection of the rights of another natural or legal person; or for reasons of important public interest. If you consider that our processing of your personal information infringes data protection laws, you have a legal right to lodge a complaint with a supervisory authority responsible for data protection. You may do so in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. To the extent that the legal basis for our processing of your personal information is consent, you have the right to withdraw that consent at any time. Withdrawal will not affect the lawfulness of processing before the withdrawal. You may exercise any of your rights in relation to your personal data by written notice to us. 8. Changes to this Privacy Policy We may change this policy from time to time, and if we do we’ll post any changes on this page. If you continue to use EVENT after those changes are in effect, you agree to the revised policy. If the changes are material, we may provide more prominent notice or seek your consent to the new policy. 9. Contacting us You can contact us: (a) by post, using the postal address 3T Logisitcs Ltd Grove Park, 5 Smith Way, Enderby, Leicester LE19 1SX (b) using our website contact form (c) by telephone: +44 (0) 116 240 5940 (d) by email, using service.desk@3t-europe.com Privacy Policy Security Policy Each Owner and each User (as defined in our Terms of Service) using EVENT control applications expect their data to be secure, confidential, and private. We understand how important this is to our customers and work to the best of our abilities to ensure all three expectations are met. Please review the information below regarding our current policies and practices, along with our Privacy Policy and Terms of Service. This is a living document and we will update it as our service evolves and industry practices change. 1. Security As a company, we use the service for nearly all of our communication. Ensuring that the Event service remains secure is vital to protecting our own data. The security of your information is required for our success as a business. Below are some details on our security practices. 2. Encrypted Traffic by Default, in Both Directions Event uses 256-bit AES, supports TLS 1.2 for all of your messages, and uses the ECDHE_RSA Key Exchange Algorithm. We monitor the security community's output closely and work promptly to upgrade the service to respond to new vulnerabilities as they are discovered. 3. External Security Audits We contract with respected, external security firms who perform regular audits of Event to verify that our security practices are sound and to monitor the service in light of new vulnerabilities discovered by the security research community. 4. Secure Physical Location Our servers are located in Microsoft Azures data centers. They've devoted an entire portion of their site to explaining their security measures, which you can find here: https://www.microsoft.com/en-us/trustcenter/compliance/default.aspx 5. Experienced Team Even before EVENT control, we (as 3T) have been providing services on the internet for a long time. We're good at it. Our engineering, quality assurance and technical operations team members are experienced and keep their skills up to date as industry best practices evolve. We’ve coded, tested and administered services running on thousands of physical servers in data centers around the world and we bring the collective wisdom that comes with many decades of secure practice to the operation of the 3T service. 6. Security Features for Team Members & Administrators The highest security risk to any system is usually the behaviour of its users. We want to provide you with the tools you need to protect your own data. For example, we log every time your account is signed in to, noting the device used and location of the connection, and make these access logs available to you. Account administrators can review consolidated access logs for the whole team. We also make it easy for each user to remotely close all Event connections and sign out all devices authenticated with their Event credentials at any time (so if you or one of your teammates lose your phone or laptop, you don't have as much to worry about). We will continue to roll out additional features which afford you more control over the security of your own Event environment. We will also be adding more options for Account administrators to set internal security policies, such as establishing password strength requirements or requiring use of PIN-lock functionality for Event’s mobile apps. 7. Availability We understand that you rely on EVENT control to work. We're committed to making EVENT control a highly-available, ultra-reliable service that you can always count on. We build systems that tolerate the failure of individual computers or whole data centers, keep many copies of your data online for redundancy, practice disaster-recovery measures often, and always have staff on-call to quickly resolve unexpected incidents. 8. Confidentiality We regard the information you share within your EVENT control users as private and confidential. We place strict controls over our employees’ access to internal data and are committed to ensuring that your data is never seen by anyone who should not see it. While the operation of the EVENT control service would not be possible unless there were some technical employees with sufficient system permissions to enable them to access and control software that stores and indexes the content you add to your EVENT control application, this team is kept purposefully small and are prohibited from using these permissions to view customer data unless it is necessary to do so. All of our employees and contractors are bound to our policies regarding customer data and we treat these issues as matters of the highest importance within our company. If, in order to diagnose a problem you are having with the service, we would need to do something that would expose your personal company data to one of our employees in a readable form, we will ask for your consent prior to taking action. Our platform will automatically generate an audit entry of any such access. There are limited circumstances when we ever share customer content without first obtaining permission. These are outlined in our Privacy Policy. Security Policy