Akcelik & Associates Pty Ltd

PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA

[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SIDRA TRIP
USER GUIDE
Restricted document
for use under SIDRA TRIP
software licence only

November 2011
 Quality Management System
Certificate # QEC27492

INNOVATION AWARD
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SIDRA TRIP
USER GUIDE
SECTION 1 - INTRODUCTION

Restricted document
for use under SIDRA TRIP
software licence only

November 2011
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

© AKCELIK & ASSOCIATES PTY LTD 2000 - 2011

All Rights Reserved.
No part of this document may be copied, reproduced, used to prepare derivative works by modifying,
disassembling, decomposing, rearranging or any other means, stored in a retrieval system or
transmitted in any form or by any means: electronic, electrostatic, magnetic tape, mechanical,
photocopying, recording or otherwise, without the prior and written permission of Akcelik &
Associates Pty Ltd.
The information provided in this document is CONFIDENTIAL and must not be used for any
commercial purposes or in any way that infringes on the intellectual property or other rights of Akcelik
& Associates Pty Ltd.
Readers should apply their own judgement and skills when using the information contained in this
document. Although the information contained in this document is considered accurate, no warranties
or guarantees thereto are given. Whilst the authors have made every effort to ensure that the
information in this document is correct at the time of publication, Akcelik & Associates Pty Ltd, save
for any statutory liability which cannot be excluded, excludes all liability for loss or damage (whether
arising under contract, tort, statute or otherwise) suffered by any person relying upon the information
contained in the document. Any such statutory liability is reduced to the full extent lawful.
Any product, trade or manufacturer name(s) appear in this document only because they are considered
essential for the purposes of this document, and Akcelik and Associates Pty Ltd does not endorse,
market, support, represent or accept any liability for any product or manufacturer appearing in this
report unless it is so specified.

Any examples given in User Guides, training manuals and similar documents for SIDRA SOLUTIONS
software products, or any templates included in SIDRA SOLUTIONS products, have been prepared for
the purpose of demonstrating software features or providing a basis for user input, and do not
necessarily represent the best design practice.

SIDRA SOLUTIONS software products are professional tools for the purpose of capacity, level of
service, operating performance and travel quality analysis of road traffic. They are not safety design or
evaluation tools. We recommend the use of appropriate safety analysis and audit tools for this
purpose.

ACKNOWLEDGEMENTS
Akcelik & Associates Pty Ltd acknowledges the contributions by numerous users from many countries
around the world through their valuable comments towards the development of SIDRA SOLUTIONS
software products.

IMPORTANT

User Guides and training manuals for SIDRA SOLUTIONS software products are RESTRICTED
DOCUMENTS for use under software licence only. These documents may not be placed in any public
library, may not be rented, loaned or distributed by any means. They are under the COPYRIGHT of
Akcelik and Associates Pty Ltd and may only be reproduced with written permission.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

We thank you for choosing SIDRA TRIP,

and hope it will meet your expectations.
The following is a general outline of this User Guide.

Part 1 - INTRODUCTION
Includes REFERENCES applicable for all sections of the Guide.

Part 2 - GETTING STARTED

Installing, Activating and Using SIDRA TRIP.

Part 3 - INPUT
Preparing Input Data for SIDRA TRIP.

Part 4 - OUTPUT
Interpreting SIDRA TRIP Output.

CONTACT US

Email
For general enquiries, sales information and training workshops:
[email protected]
For technical support enquiries for users with current COVER:
[email protected]

Phone
International +61 3 9857 4943
Australia 03 9857 4943

Fax
International +61 3 9857 7462
Australia 03 9857 7462

Postal Address
Akcelik and Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104, AUSTRALIA
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

TECHNICAL SUPPORT

CONDITIONS
Technical support is provided for the latest version of SIDRA TRIP only, and you need to have valid
COVER. A reasonable amount of technical support is provided to registered users under the
COVER agreement. This includes assistance to make the software operate on your computer
system, and investigation of example files that fail to run or produce unexpected results. It does not
include assistance in the normal use of the software such as coding of input from an intersection
plan. SIDRA SOLUTIONS training courses that cover these topics are offered from time to time.

BEFORE CONTACTING AKCELIK AND ASSOCIATES

Before contacting Akcelik and Associates, refer to the Troubleshooting section in Part 2 of this
User Guide (or the same topic in the Help system). The Troubleshooting section contains many
answers to common problems. Also refer to the Technical Advice page of the Support section of
www.sidrasolutions.com, which is frequently updated with answers to user questions. If you are
unable to find an answer to your problem using these resources, please use the process described
below to contact Akcelik & Associates.

PROCESS FOR CONTACTING AKCELIK AND ASSOCIATES

To expedite support services, we prefer electronic communications via EMAIL. Use the following
EMAIL address to ensure that your message is replied to as promptly as possible:
[email protected]
When you send an EMAIL message:
 ensure that you have valid COVER,
 provide your Customer ID and Licence Type which can be found in the SIDRA TRIP
Licence Configuration dialog which you can access using Start - All Programs - SIDRA
SOLUTIONS - SIDRA TRIP 1.1 Tools - Licence Configuration,
 include your phone number and organisational details in your EMAIL message,
 describe your problem succinctly, and include any error messages reported by the program,
and
 if it is a problem with input and output, attach the Profile (aam) file in a zipped folder, or if it is
a computer system problem, give details of your computer.

Quality Management System Certificate # QEC27492

 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

ABOUT THE SIDRA SOLUTIONS WEBSITE

Our Website
www.sidrasolutions.com
The SIDRA SOLUTIONS website is full of essential information about SIDRA SOLUTIONS
software products. Utilise this information for most efficient use of your SIDRA TRIP software.

Subscribe to SIDRA NEWS

www.sidrasolutions.com/Company/SIDRA_News
If you are not already a list member, sign up to SIDRA NEWS to stay informed with our regular
email alerts that give you the latest information on important product releases and updates, training
workshops and other events. To subscribe, use the web address above. To unsubscribe, use the
unsubscribe link at the bottom of any SIDRA NEWS email.

YouTube Channel
www.youtube.com/SidraSolutions
We are creating tutorial videos for SIDRA TRIP, SIDRA INTERSECTION and other SIDRA
SOLUTIONS software. Visit our SIDRA SOLUTIONS YouTube channel and subscribe to keep up
to date with the latest video posts.

eLearning
www.sidrasolutions.com/eLearning/INTERSECTION
The eLearning page for SIDRA TRIP includes links to tutorial videos, getting started documents,
installation instructions and more.

SIDRA FORUMS for Traffic & Transport Engineering

www.sidrasolutions.com/forums
Join SIDRA FORUMS, get involved, and communicate with the SIDRA team and other like-minded
traffic and transport engineers around the world. To register, visit the FORUMS page.

Twitter
@sidrasolutions
Follow Rahmi on Twitter to keep in touch with what is happening at SIDRA SOLUTIONS.

Articles
www.sidrasolutions.com/Resources/Articles
Download and read the latest papers, reports and presentations as well as reprints of older but
important papers and reports relevant to SIDRA SOLUTIONS software products.

continued >>>
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

ABOUT THE SIDRA SOLUTIONS WEBSITE - continued

Support
www.sidrasolutions.com/Support
Information about sales support, product support including licensing information and licence setup
instructions, latest technical advice and software updates.

Software Updates
www.sidrasolutions.com/Support/Software_Updates
To find information about the latest software updates, visit the Software Updates page under the
Support section.

Store
www.sidrasolutions.com/Store
For purchasing new licenses, upgrade licences and COVER renewal.

Contact Us
www.sidrasolutions.com/Company/Contact_Us
Information about contacting us as well as lists of our representatives and resellers around the
world.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SIDRA SOLUTIONS SOFTWARE

LICENCE AGREEMENT
THIS IS A LEGAL AGREEMENT BETWEEN YOU AND AKCELIK & ASSOCIATES PTY LTD
(TRADING AS SIDRA SOLUTIONS). BY INSTALLING, COPYING OR OTHERWISE USING
THIS SOFTWARE, YOU ARE AGREEING TO BECOME BOUND BY THE TERMS OF THIS
LICENCE AGREEMENT.

This agreement is between Akcelik & Associates Pty Ltd (A&A) of Suite 5, 22 Horne St, Elsternwick, Victoria
3185, Australia (trading as SIDRA SOLUTIONS), and the company, organisation or the person hereinafter
referred to as the Licensee, for the use of SIDRA SOLUTIONS computer software package, or packages, as
applicable, hereinafter referred to as the Software.
This licence agreement covers the following SIDRA SOLUTIONS software packages which are fully owned by
A&A:
(i) SIDRA INTERSECTION, SIDRA TRIP and INPUT COMPARISON supplied upon payment of a licence
fee,
(ii) Trial Versions of SIDRA INTERSECTION and SIDRA TRIP supplied free of charge, and
(iii) SIDRA UTILITIES (OUTPUT COMPARISON and VARIABLE RUN programs, and Excel applications
VOLUMES and ANNUAL SUMS) supplied free of charge.

CONDITIONS
LICENCE AGREEMENT
1. This Agreement is the complete and exclusive statement of agreement between A&A and the Licensee,
and no other commitment or understanding exists outside this document. This agreement may be
modified only by a written agreement signed by both parties.
2. A&A agrees to furnish to the Licensee, the Software upon receipt of payment of licence fees, or free of
charge, as applicable. Distribution of the Software will be via direct download from A&A eCommerce
website, or via CD or other media selected by A&A.
3. By installing, copying or otherwise using the Software, the Licensee agrees to become bound by the
terms of this licence agreement.
4. This licence agreement cancels and replaces all prior licence agreements for all earlier versions of the
Software.
5. The agreement applies to all licence and product types for the use of the Software and all related
material including the user guides, training material and other supplementary material.
6. The rights granted to the Licensee under this Agreement are non-exclusive and non-transferable. The
software licence cannot be passed on, rented or leased, to another organisation.
7. All registration details such as the Customer ID, User ID, Licence ID, Password, Serial Number, User
Key, Product Key, Machine Key, Unlock Code and Registration Code for the licensed use of the
Software are confidential, and must not be given to any third party.
8. Licensee will nominate a Licence Contact for communication with A&A for licence management
purposes. A&A will supply the Software licence details and the eCommerce account and login
information for the Software licence management to the Licence Contact only. The Licence Contact
agrees to receive notices from A&A via email and other means from time to time. These will include
notices about COVER renewal and new version release.
9. A&A will observe the confidentiality of the information supplied by the Licensee for the licence purchase
and registration purposes. A&A may pass some of this information to its Representatives as relevant,
who will observe the confidentiality of such information under contract to A&A.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

USE OF LICENCE - GENERAL

10. The Licensee agrees that the Software shall only be used for the Licensee's own purposes and limited to
those purposes set out in this Agreement.
11. The Licensee agrees that it is the responsibility of the Licensee to understand fully the limitations of and
assumptions underlying the Software and not to make use of the Software without the assistance of
personnel with appropriate expertise.
12. Software programs and Excel applications which are part of the SIDRA UTILITIES group of products
offered by A&A free of charge are also subject to the conditions of this agreement. These products
require the use of a licensed copy of the SIDRA INTERSECTION software, or other software as
applicable.
13. A licensed copy of the Software is required where it is being accessed via its Application Programming
Interface through software linking provided in another vendor's product.
14. The Trial Version of the Software may not be used for any purpose other than evaluating the Software
towards licence purchase.

USE OF LICENCE – SOFTWARE PROVIDED UPON PAYMENT OF LICENCE FEE

15. The following conditions apply to the use of SIDRA SOLUTIONS software provided upon payment of a
licence fee. The conditions are stated in general terms and they apply to the use of individual software
packages as relevant.
a) This licence agreement is applicable to Professional and Educational licences for the Software.
SINGLE (Per Computer) FLOATING (Network), LIMITED and ENTERPRISE (UNLIMITED)
licence products are available for purchase depending on the particular software package.
b) The Educational licence is applicable to recognised educational institutions, and is subject to
various restrictions. Under the Educational licence, the Licensee will not use or attempt to use the
Software in any way for commercial gain or profit including any research carried out under contract
for commercial gain. The Professional licence must be obtained for use of the Software for any
professional (non-educational) purposes. Upgrade from Educational licence to Professional
Licence is not available.
c) All licence products are treated individually from a pricing and licence management perspective.
Each SINGLE computer licence, FLOATING licence pack, LIMITED licence pack and
ENTERPRISE (UNLIMITED) licence has an individual price, Licence ID and COVER expiry date
associated with it.
d) Where applicable, the Licensee can buy any number of SINGLE and FLOATING licence products
at different times, and may use any combination of SINGLE and FLOATING licences in any site
(office) of the Licensee's organisation in the country for which the licence is issued.
e) Licenses are not directly associated with specific sites (offices) of the Licensee's organisation. The
Licensee may therefore redeploy the licences between sites (offices) of the licensed organisation.
However, in the case of multi-national organisations, the Licensee agrees to use the Software only
in the offices (sites) of the organisation in the country for which the licence is issued. Purchase of
additional licences or a special agreement is required for use of the Software in additional countries
where the Licensee's organisation has offices.
f) The Licensee is expressly prohibited to transfer licences to other organisations.
g) For licence management purposes, three "version status" levels which determine the licence
purchase and COVER renewal conditions for the Licensee are designated as Current Version,
Previous Version and Old Version (all versions older than the Previous Version).
h) As soon as a new major version of the Software is released, it becomes the Current Version with
the following consequences:
i. COVER renewal is available for the Current Version only (therefore “valid COVER” is
associated with the Current Version only),
ii. for Previous Version licences, purchase of an upgrade licence and COVER is needed, and
iii. for Old Version licences, purchase of a new licence and COVER is needed.
i) The licences with valid COVER at the time of the release of a new major version (which becomes the
new Current Version) will be replaced with a free upgrade licence to the new Current Version.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

j) The SINGLE licence allows installing and using the software on one computer of the Licensee.
Once a SINGLE licence has been installed and activated on a computer, it cannot be simultaneously
activated on another. The software activation procedures will prevent a SINGLE licence version of
the Software from being used on more than one computer. To be able to use the Software
simultaneously on more than one computer, further SINGLE Licences are required.
k) A SINGLE licence can be deactivated and subsequently moved to another computer of the
Licensee. Generally this process will require an internet connection. If a licence cannot be
deactivated, for example because a computer was damaged or became inoperable, the Licensee
would then need to contact A&A by email to have the licence reactivated on another computer. A
service fee may be applicable for such cases.
l) The Licensee can buy any number of SINGLE licence products at different times, and may use any
combination of those licences in any site (office) of the Licensee's organisation in the country for
which the licence is issued. Each license is managed individually, has its own COVER associated
with it, and is not directly associated with specific sites (offices) of the Licensee's organisation. The
Licensee may therefore redeploy the licences between sites (offices) of the licensed organisation.
m) The FLOATING (Network) licence will allow a number of simultaneous users (computers) to access
the software. It will not allow more than the licensed number of users to access a licence
simultaneously. Under the FLOATING (Network) licence, the software cannot be used on a
computer that is not connected to the Licensee's network. The SINGLE licence is needed for such
computers.
n) The FLOATING (Network) licence requires installing a Licence Manager program on a server,
installing the Software on any number of individual computers that are connected to the Licensee's
computer network, and providing a permanent internet connection to the server for the purpose of
initial setting up of the FLOATING (Network) licence and for any subsequent changes to the
licence.
o) The FLOATING (Network) licence requires a Licence Server and needs to access a shared
(common) network folder on the server during the time that the Software is in use. The Licence
Server must be accessible to all computers running the Software in order to obtain a licence. The
Licence Manager software supplied to the Licensee by A&A will need to be installed on the server
machine. The shared network folder on the server is for licence control only. The Software will
reside on the individual user computers.
p) The FLOATING (Network) licence can be used within a single site (office) or over a number of sites
(offices) at different locations of the Licensee's organisation in the country for which the licence is
issued. The Licensee may wish to set up the common network folder on a server at a central
location to serve several sites (offices) of the licensed organisation. The use of the Software in this
manner is dependent on the reliability of the Licensee's inter-office links and A&A do not have any
responsibility for this operation.
q) The LIMITED licence allows the Licensee to install and use the Software on a specified number of
computers, including laptop computers, within the Licensee's organisation in the country for which the
licence is issued. The allocated maximum number of computer licences can be used in all offices of
the licensed organisation in a flexible way.
r) The ENTERPRISE (UNLIMITED) licence allows the Licensee unlimited use of the Software in the
offices (sites) of the Licensee's organisation in the country for which the licence is issued. This
licence allows the Software to be installed on any number of individual computers, including laptops,
without need to keep a track of how many computers, or which computers, the software is installed
on. For licensing purposes, there is no networking requirement, no need to access the internet, and
no network traffic required. Only one licence is issued to the Licensee's organisation and the
software can be installed on individual computers using the same licence. No deactivation-
reactivation is needed to uninstall and reinstall the licence on individual computers.
s) This licence agreement does not allow licence upsizing or downsizing. A&A may offer a licence
replacement service to help the Licensee with licence management that may be needed from time to
time. This service will be offered at A&A's discretion and at an hourly service charge rate subject to a
minimum fee. The licence replacement process may involve cancelling some of the Licensee's
existing licences, and any new licence and COVER costs are additional to the service charge.
t) In the case of an outsourced office (service provision on an on-going basis under contract), the
organisation providing the service or the organisation receiving the service is required to have a valid
licence for the use of the Software.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

u) A representative of A&A appointed under agreement (hereinafter referred to as the Representative)

may use the Software for its own purposes, including commercial applications, as well as for
marketing the Software on behalf of A&A, in accordance with the terms of the AGREEMENT for
APPOINTMENT OF REPRESENTATIVE. Outside this, the Software will not be copied, modified or
used by the Representative in any way. The Representative is subject to all terms and conditions of
this user licence.

MAINTENANCE - GENERAL
16. A&A will not maintain software other than the Current Version.
17. The Licensee acknowledges and agrees that the A&A is not in a position to provide any support or
maintenance services that are not expressly provided under this agreement.

MAINTENANCE – SOFTWARE PROVIDED UPON PAYMENT OF LICENCE FEE

18. The following conditions apply to provision of maintenance services for the Software provided upon
payment of a licence fee.
a) Unless different arrangements are made during purchase, this licence agreement provides a 12-
month COVER (support subscription) starting from the purchase date of the software.
b) The COVER renewal period is 12 months from the expiry date of the current COVER in the case of
COVER renewal before expiry, or from the COVER renewal date in the case of COVER renewal
after expiry. COVER renewal is available for the Current Version only.
c) Technical support will be provided for the Current Version under valid COVER only.
d) The COVER is associated with the particular software licence purchased, i.e. it applies per licence,
and there are no upgrades or downgrades of COVER.
e) COVER benefits include free upgrades to new versions released during the COVER period,
notification regarding minor updates to the Software that become available, a reasonable amount of
technical support limited to making the Software operate on the Licensee's computer system, and
investigation of project files that fail to run or produce unexpected results. The COVER does not
include assistance in the normal use of the Software such as coding of the input.

COPYRIGHT
19. The Software is protected by copyright laws and international treaties, and other intellectual property
laws and treaties.
20. All title, copyrights and intellectual property in and to the Software including but not limited to all program
codes, concepts, intellectual ideas, methods, formulas, algorithms, data, text, images, photographs,
audio, video, animations, graphics and applets incorporated into the Software and its associated
materials, including but not limited to user guides, training material and other supplementary material,
and any copies of the Software and its associated materials, remain the property of A&A.
21. The Licensee shall treat as confidential information relating in any way to the Software and will not
redistribute, translate to another language, publish or copy, wholly or in part, the Software and its
associated materials, without previous written consent from A&A.
22. The Licensee is not permitted to alter, revise, amend, reverse engineer, decompile or disassemble the
Software in any way.
23. The Licensee shall not remove the full or abbreviated names and associated brand images of SIDRA
SOLUTIONS, SIDRA INTERSECTION, SIDRA NETWORK, SIDRA TRIP, INPUT COMPARISON,
SIDRA UTILITIES, OUTPUT COMPARISON, VARIABLE RUN, VOLUMES, ANNUAL SUMS, SIDRA,
aaSIDRA, Akcelik & Associates and A&A from the Software or its output.
24. Any reference to the Software in any published material shall include a reference to SIDRA
SOLUTIONS, SIDRA INTERSECTION, SIDRA NETWORK, SIDRA TRIP, INPUT COMPARISON,
SIDRA UTILITIES, OUTPUT COMPARISON, VARIABLE RUN, VOLUMES, ANNUAL SUMS, SIDRA,
aaSIDRA, Akcelik & Associates and A&A as appropriate.
25. Where the Software uses other software of a proprietary nature, then it is the Licensee's responsibility to
arrange from the owners of that software the appropriate licence for its use on their computer, and that
the use of such proprietary software by A&A in the Software does not constitute release of that
proprietary software.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SOFTWARE DOCUMENTATION AND OTHER RELATED MATERIAL

26. All Software documentation and other related material including the user guides, training material and
other supplementary material are RESTRICTED for use under the Software licence only. They may not
be placed in any public library, may not be rented, loaned or distributed by any means. No part of
Software documentation and other related material may be copied, reproduced, used to prepare
derivative works by modifying, disassembling, decomposing, rearranging or any other means, stored in a
retrieval system or transmitted in any form or by any means: electronic, electrostatic, magnetic tape,
mechanical, photocopying, recording or otherwise, without the prior and written permission of A&A.
27. The information provided in Software documentation and other related material are CONFIDENTIAL and
must not be used for any commercial purposes or in any way that infringes on the intellectual property or
other rights of A&A.
28. Where applicable, an electronic copy of the Software User Guide may be installed or supplied with the
Software. The Software User Guide is only for use by those who have a valid software licence for the
Current Version of the Software.

RESELLING
29. Reselling the Software is strictly prohibited unless a RESELLER AGREEMENT is signed with Akcelik
and Associates Pty Ltd.

WARRANTY, INDEMNIFICATION and LIMITED LIABILITY

30. To the fullest extent permitted by law and except as expressly provided in this Agreement, all conditions
and warranties relating to the Software and associated materials, either express or implied, are
excluded. Any implied warranties are limited to 60 days from the date of dispatch to the Licensee.
31. It is the Licensee's responsibility to arrange for the correct execution of the Software on the Licensee's
computer, and the release of the Software by A&A does not imply that it is suitable for execution on the
Licensee's computer.
32. A&A warrants any media on which the Software is furnished to be free from defects in materials and
workmanship under normal use for a period of sixty (60) days from the date of dispatch to the Licensee.
The entire liability of A&A and the Licensee's exclusive remedy shall be the replacement of any media
not meeting the preceding limited warranty provided that the Licensee gives notice of the defect to A&A
and returns the defective media to A&A within the 60-day warranty period.
33. Except as provided above, the Software and documentation are provided "as is" without warranty of any
kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability
and fitness for a particular purpose. A&A does not warrant that the functions contained in the Software
will meet the Licensee's requirements or that the operation of the Software will be uninterrupted or error
free. The entire risk as to the quality and performance of the product is with the Licensee.
34. The Software is supplied for the purpose of capacity, level of service, operating performance and travel
quality analysis of road traffic. The Software is not intended to be used in the area of traffic safety design
or evaluation.
35. A&A shall not be under any liability to the Licensee in respect of any loss or damage (including any lost
profits, lost savings or other incidental or consequential loss or damages arising out of the use or inability
to use the Software) however caused incurred or which may arise directly or indirectly in respect of the
Software or from the failure or omission on the part of A&A to comply with its obligations under this
Agreement.
36. A&A shall not be responsible in any way for errors arising out of the use of the Software itself, improper
use of documented features, use of undocumented features, misapplication, or any other reason, and
the Licensee further agrees to indemnify A&A and its officers against any claims, proceedings or
liabilities caused by any such errors.
37. Where errors are found in the Current Version of the Software or its associated documentation, A&A
may, at its discretion, correct such errors and make the corrected software and documentation available
to the Licensee.
38. A&A reserves the right to charge a fee for any upgrades at its own discretion.
39. For the Software provided upon payment of a licence fee, A&A's entire liability will be, at A&A's choice,
either return of the licence fee paid or replacement of the software.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

TERMINATION
40. This agreement will continue in perpetuity, and will apply to any future updates of the program supplied
to the Licensee free of charge, or on payment of appropriate upgrade or new licence fees, unless
replaced by a new agreement, or terminated according to other clauses of this agreement.
41. A&A reserves the right to terminate this licence agreement if the Licensee is found to have breached any
of the conditions of the agreement by giving two weeks notice in writing to the Licensee.
42. Upon the termination of this Agreement for any reason, the Licensee shall, if requested, supply a
statement in writing certifying that all copies of the software have been deleted.

GOVERNING LAW
43. This agreement is governed by the laws in force in the State of Victoria, Australia. A&A and the
Licensee hereto agree irrevocably to submit to the jurisdiction of the courts of the State of Victoria,
Australia.

End of Licence Agreement

SIDRA TRIP User Guide

CONTENTS
page
1. INTRODUCTION ............................................................................................................... 1.1
1.1 What is SIDRA TRIP? .......................................................................................................... 1.1
1.2 About SIDRA TRIP ............................................................................................................... 1.1
1.3 What Can SIDRA TRIP Do? ................................................................................................. 1.2
1.4 System Requirements .......................................................................................................... 1.3
REFERENCES ............................................................................................................................... 1.3

2. GETTING STARTED ......................................................................................................... 2.1

2.1 INSTALLING SIDRA TRIP .................................................................................................... 2.1
2.1.1 Software Installation ................................................................................................ 2.1
2.1.2 Uninstalling ............................................................................................................. 2.1
2.1.3 Your Account .......................................................................................................... 2.1
2.1.4 Downloading ........................................................................................................... 2.2
2.1.5 Trial Mode .............................................................................................................. 2.2
2.1.6 SIDRA TRIP User Guide ......................................................................................... 2.2
2.1.7 Example Files ......................................................................................................... 2.2
2.1.8 Defaults and Options .............................................................................................. 2.2
2.2 LICENCE ACTIVATION ....................................................................................................... 2.3
2.2.1 SINGLE Licence ..................................................................................................... 2.4
2.2.2 ENTERPRISE Licence ............................................................................................ 2.9
2.3 USING SIDRA TRIP ............................................................................................................ 2.10
2.3.1 Starting SIDRA TRIP ............................................................................................. 2.10
2.3.2 SIDRA TRIP User Interface .................................................................................... 2.10
2.3.3 User Guide ............................................................................................................ 2.15
2.3.4 Help System .......................................................................................................... 2.16
2.4 DEFAULTS AND OPTIONS ................................................................................................ 2.17
2.4.1 Defaults.................................................................................................................. 2.17
2.4.2 Vehicle Classes ..................................................................................................... 2.21
2.4.3 Parameter Values for Default Vehicles ................................................................... 2.22
2.4.4 Options ................................................................................................................. 2.24
2.5 TROUBLESHOOTING ........................................................................................................ 2.27
2.5.1 Installation ............................................................................................................. 2.27
2.5.2 Starting SIDRA TRIP ............................................................................................. 2.28
2.5.3 Input Problems ...................................................................................................... 2.28
2.5.4 Processing, Defaults and Options ........................................................................... 2.28
2.5.5 Output Problems .................................................................................................... 2.29

Continued >>
 Akcelik & Associates Pty Ltd

3. INPUT ............................................................................................................................... 3.1

3.1 GENERAL ASPECTS OF SIDRA TRIP INPUT ...................................................................... 3.1
3.2 GENERAL SETTINGS .......................................................................................................... 3.4
3.3 TRIP DATA USING TRAVEL DATA METHOD ...................................................................... 3.6
3.3.1 Importing Trip Data ................................................................................................. 3.6
3.3.2 Conversion of Units Used in Data File ...................................................................... 3.9
3.3.3 Source Data File Formats ...................................................................................... 3.10
3.3.4 Parameters in the Trip Data Dialog ........................................................................ 3.14
3.4 TRIP DATA USING EVENT DATA METHOD ...................................................................... 3.18
3.4.1 Specifying Event Data .......................................................................................... 3.18
3.4.2 Initial and Final Speeds ........................................................................................ 3.20
3.4.3 Event Type ........................................................................................................... 3.20
3.4.4 Event markers ...................................................................................................... 3.20
3.4.5 Loops ................................................................................................................... 3.22
3.5 SPEED SETTINGS ............................................................................................................ 3.23
3.6 NOISE SETTINGS ............................................................................................................. 3.24
3.7 COST & LOS PARAMETERS ............................................................................................. 3.26
3.8 VEHICLES ......................................................................................................................... 3.29
3.8.1 Fuel Consumption and Emission Parameters ......................................................... 3.30
3.8.2 Fuel Consumption Model........................................................................................ 3.32
3.8.3 Model for Emission Rates (CO, HC, NO x) .............................................................. 3.33
3.8.4 Model for Carbon Dioxide Emission (CO2) .............................................................. 3.33
3.8.5 Fuel and Emission Model Calibration ..................................................................... 3.33
3.9 DRIVERS .......................................................................................................................... 3.36
3.10 DIAGNOSTICS ................................................................................................................. 3.37

4. OUTPUT ........................................................................................................................... 4.1

4.1 INTRODUCTION .................................................................................................................. 4.1
4.2 TEXT OUTPUT, GRAPHS, ANIMATION ............................................................................... 4.1
4.2.1 Text Output ............................................................................................................. 4.2
4.2.2 Graphs ................................................................................................................... 4.6
4.2.3 Animation ............................................................................................................... 4.8
4.3 PRINTING, COPYING and SAVING OUTPUT ..................................................................... 4.10
4.4 OUTPUT STATISTICS ....................................................................................................... 4.12
4.4.1 Trip Assessment ................................................................................................... 4.13
4.4.2 Speed ................................................................................................................... 4.22
4.4.3 Cost (Operating or User) ....................................................................................... 4.25
4.4.4 Fuel Consumption ................................................................................................. 4.26
4.4.5 Emissions (CO2, CO, HC, NOx) .............................................................................. 4.27
4.4.6 Noise .................................................................................................................... 4.28
SIDRA TRIP User Guide

ABOUT THIS GUIDE

This guide contains information and step-by-step procedures for users of the SIDRA TRIP software.
It provides information on how to install, register and run SIDRA TRIP, how to prepare input data,
how to inspect text output and graphs, and how to interpret SIDRA TRIP output.

INTRODUCTION: Overview of the SIDRA TRIP software; information about what SIDRA TRIP
does and how it works; computer system requirements and references.

GETTING STARTED: Step-by-step instructions for installing and registering SIDRA TRIP,
information about using the software, information on defaults and options, the help system, and
various troubleshooting hints.

INPUT: Detailed information on SIDRA TRIP input data and how to specify data in input dialogs.
OUTPUT: Information about the SIDRA TRIP output system; output tables, viewing and printing
text and graphical output (Trip Statistics, Event Statistics, Sums, Graphs), and detailed information
about SIDRA TRIP output statistics.

File Management in SIDRA TRIP

All file management functions are performed through the SIDRA TRIP File menu. The Profile file
(extension aam) contains the input data and various model parameters pertaining to a particular
case. See Section 2.

Viewing and Printing Text and Graphical Output

Text output and graphical displays (Trip Statistics, Event Statistics, Sums, Diagnostics, Graphs) as
well as the Input Report can be viewed by double-clicking the corresponding node in the Profile
tree. For information about printing and copying pictures and text, refer to Section 4.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
Akcelik & Associates Pty Ltd
SIDRA TRIP User Guide 1.1

1. INTRODUCTION

1.1 WHAT IS SIDRA TRIP?

SIDRA TRIP is a single-trip microsimulation model for realistic assessment of road traffic
conditions using in-traffic vehicle data or user-defined drive cycles. It employs an instantaneous
speed and acceleration model to determine various trip characteristics for assessing travel level of
service, performance (delay, speed, travel time), operating cost, user cost, fuel consumption,
vehicle emissions and noise in real-life road networks. SIDRA TRIP uses a power-based vehicle
model to estimate fuel consumption and emissions of Carbon Dioxide (CO2), Carbon Monoxide
(CO), Hydrocarbons (HC) and Nitrogen Oxides (NOx).
SIDRA TRIP is ideally suited to comparison of traffic and travel conditions before and after
introduction of traffic management schemes, intersection and road improvements, residential street
traffic calming schemes, and so on, without need for time-consuming and costly network data
preparation work. It can also be used for assessing intelligent transport system applications, driver
training programs, and vehicle characteristics.
SIDRA TRIP allows analysis of trips of any length as well as selected sections of a trip in a flexible
way. It can use trip data collected by an instrumented vehicle, for example, using a GPS data
logger. SIDRA TRIP can also be used for trip assessment using drive-cycle data based on speed-
change information specified by the user. Simulation can be performed using default (passenger
car, light vehicle, heavy vehicle) or customised (user-specified) vehicles. Different driver
characteristics can be specified for all vehicle types.
See the References listed at the end of this user guide for more detailed technical information
about the methodology employed in SIDRA TRIP.

1.2 ABOUT SIDRA TRIP

The SIDRA TRIP software is supplied under the terms of a software licence agreement. For
further information, visit www.sidrasolutions.com or send an email to [email protected].
SIDRA TRIP has been developed, and is fully owned by, Akcelik & Associates Pty Ltd. It is an
evolution of an earlier development version of the software called aaMotion whose development
started in 2002. This is the first commercial release of SIDRA TRIP. The software will be
developed further in response to feedback from practising traffic engineers and planners.

Author Programmers Advisers

Rahmi Akçelik Harry Cai Mark Besley
Tristan McLeay Darren Thompson
Bhaskar Ashish Edward Chung
Adnan Bader
Arvid Aakre
David Crafti

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
1.2 Akcelik & Associates Pty Ltd

1.3 WHAT CAN SIDRA TRIP DO?

You can use SIDRA TRIP to:
 compare traffic and travel conditions before and after introduction of traffic management
schemes, intersection and road improvements, residential street traffic calming schemes,
and so on, without need for time-consuming and costly network data preparation work;
 assess intelligent transport system applications, driver training programs and vehicle
characteristics;
 analyse trips of any length as well as selected sections of a trip in a flexible way;
 analyse standard drive cycles used in vehicle fuel consumption and emission testing;
 estimate noise levels (dBA) generated during the trip using three different models: ASJ
2003 (Japanese) Model, SonRoad (Swiss) Model, and RLS-90 (German) Model;
 determine vehicle operating and user costs including toll cost;
 simulate light and heavy vehicle movements using default or customised vehicle and driver
characteristics.

In using SIDRA TRIP, you can:

 use Metric or US Customary units;
 prepare data and inspect output with ease;
 make use of diagnostic messages given by the program to avoid use of unreliable data;
 import trip data collected by an instrumented vehicle, e.g. using output from a GPS data
logger, in a variety of formats:
o CSV (comma-separated values),
o Text (tab-separated),
o NMEA Text,
o GPS Exchange,
o Track
o and Garmin Database;
 define trips simply by specifying initial and final speeds to represent vehicle idling, cruise,
acceleration and deceleration manoeuvres with markers representing traffic events;
 simulate detector loop actuation;
 create your own vehicle and driver types using appropriate parameters describing vehicle
and driver characteristics;
 calibrate the parameters of the operating and user cost models for your local conditions
allowing for factors such as the value of time and resource cost of fuel;
 obtain output including trip statistics, sums of statistics for a given number of trips, and
detailed statistics per drive cycle element;
 save the HTML-based text output as separate files suitable for viewing with web browsers;
 you can also save simulation data in csv, txt or xml format;

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INTRODUCTION 1.3

 animate the movement of a vehicle as defined in the trip profile with dynamic graphs
linked to the vehicle movement;
 animate driving on the left-hand and right-hand side of the road;
 use your own default settings for a large number of input, output and model parameters
using Tools - Defaults;
 control the text and graph displays, as well as various input, model and animation settings
using Tools - Options.

1.4 COMPUTER SYSTEM REQUIREMENTS

Computer system requirements for SIDRA TRIP 1.1 are given below.

SIDRA TRIP

Memory 1 GB RAM or higher

Display 1024x768 or higher resolution monitor

Operating system Windows 7, Windows Vista, Windows XP with Service Pack (SP) 2.
32-bit and 64-bit versions supported
Other SIDRA TRIP will install .NET Framework 2.0 if not already present. This is a
prerequisite for installation of the software.
SIDRA TRIP requires a PDF viewer for reading the User Guide. SIDRA TRIP
will not install this (a reminder message will be given during installation).
Additional Internet connection for activation of software licence.

REFERENCES

 Available for download from www.sidrasolutions.com/Resources/Articles

AKCELIK & ASSOCIATES (2011). SIDRA INTERSECTION User Guide (for Version 5.1).
Akcelik and Associates Pty Ltd, Melbourne, Australia. [Restricted document - available under
SIDRA INTERSECTION licence only.]
AKÇELIK, R. (1980). Objectives in traffic system management. Key paper presented at the joint
SAE/ARRB Seminar and Workshop 'Can Traffic Management Reduce Vehicle Fuel Consumption
and Affect Vehicle Design Requirements?', Melbourne. Reprinted in Society of Automotive
Engineers - Australasia, 41(6), pp 284-301.
AKÇELIK, R. (1981a). Fuel efficiency and other objectives in traffic system management. Traffic
Engineering and Control, 22(2), pp 54-65.
 AKÇELIK, R. (1981b). Traffic Signals: Capacity and Timing Analysis. Research Report
ARR No. 123. ARRB Transport Research Ltd, Vermont South, Australia. (6th reprint: 1995).
AKÇELIK, R. (1982). Derivation and Calibration of Fuel Consumption Models. Australian Road
Research Board. Internal Report AIR 367-3.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
1.4 Akcelik & Associates Pty Ltd

AKÇELIK, R. (1982). Limitations on the objective of energy efficiency in urban traffic

management. Proc. XIX International FISITA Congress, Melbourne, Vol. 2, Paper 82081.
 AKÇELIK, R. (Ed.) (1983a). Progress in Fuel Consumption Modelling for Urban Traffic
Management. Research Report ARR No. 124. ARRB Transport Research Ltd, Vermont South,
Australia.
AKÇELIK, R. (1983b). Formulae for predicting fuel consumption of cars. Traffic Engineering
and Control 24(3), pp 115-118.
AKÇELIK, R. (1985). An interpretation of the parameters in the simple average travel speed
model of fuel consumption. Australian Road Research 15(1), pp 46-49.
AKÇELIK, R. (1986). Discussion on the paper 'Estimating fuel consumption from engine size' by
T.N. Lam. Journal of Transportation Engineering, 113(1), pp 101-106.
AKÇELIK, R. (1986). Models for estimation of car fuel consumption in urban traffic. ITE
Journal, 56(7), pp 29-32.
AKÇELIK, R. (1989). Efficiency and drag in the power-based model of fuel consumption.
Transportation Research 23B(5), pp 373-385.
 AKÇELIK, R. (1991). Travel time functions for transport planning purposes: Davidson's
function, its time-dependent form and an alternative travel time function. Australian Road
Research 21 (3), pp 49–59.
AKÇELIK, R. (1996). Relating flow, density, speed and travel time models for uninterrupted and
interrupted traffic. Traffic Engineering and Control 37(9), pp 511-516.
AKÇELIK, R. (1999). A Travel Time Model and Traffic Quality Index. Technical Note. ARRB
Transport Research Ltd, Vermont South, Australia.
 AKÇELIK, R. (2002a). Speed-Flow Models for Uninterrupted Traffic Facilities. Technical
Report. Akcelik and Associates Pty Ltd, Melbourne, Australia.
AKÇELIK, R. (2002b). HCM 2000 speed-flow relationships for freeways and multilane highways.
Institute of Transportation Engineers Australia and New Zealand Section, 2002 International
Conference, Melbourne, 12-13 September 2002.
 AKÇELIK, R. (2003). Speed-Flow and Bunching Relationships for Uninterrupted Flows.
Paper presented at the 25th Conference of Australian Institutes of Transport Research (CAITR
2003), University of South Australia, Adelaide, Australia, 3-5 December 2003.
AKÇELIK, R. (2006a). Speed-Flow and Bunching Models for Uninterrupted Flows.
Transportation Research Board 5th International Symposium on Highway Capacity and Quality of
Service, Yokohama, Japan, 25-29 July 2006.
 AKÇELIK, R. (2006b). Operating cost, fuel consumption and pollutant emission savings at a
roundabout with metering signals. ARRB 22nd Conference, Canberra, Australia.
AKÇELIK, R. (2006c). Operating cost, fuel consumption and pollutant emission savings at a
roundabout with metering signals. Seventh International Congress on Advances in Civil
Engineering (ACE 2006), Istanbul, Turkey.
AKÇELIK, R. and BAYLEY, C. (1982). Derivation of fuel consumption models. Joint
SAE/ARRB 2nd Conf. 'Traffic Energy and Emissions', Melbourne.
AKÇELIK, R., BAYLEY, C., BOWYER, D.P. and BIGGS, D.C. (1983). A hierarchy of vehicle
fuel consumption models. Traffic Engineering Control, 24(10), pp 491-495.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INTRODUCTION 1.5

 AKÇELIK, R. and BESLEY, M. (2001a). Microsimulation and analytical methods for

modelling urban traffic. Paper presented at the Conference on Advance Modeling Techniques and
Quality of Service in Highway Capacity Analysis, Truckee, California, USA, July 2001.
 AKÇELIK, R. and BESLEY M. (2001b). Acceleration and deceleration models. Paper
presented at the 23rd Conference of Australian Institutes of Transport Research (CAITR 2001),
Monash University, Melbourne, Australia, 10-12 December 2001.
 AKÇELIK, R. and BESLEY, M. (2003). Operating cost, fuel consumption, and emission
models in aaSIDRA and aaMotion. Paper presented at the 25th Conference of Australian Institutes
of Transport Research (CAITR 2003), University of South Australia, Adelaide, Australia..
AKÇELIK, R. and BIGGS, D.C. (1985). A discussion on the paper on fuel consumption modelling
by Post et al. Transportation Research 19B(6), pp 529-533.
 AKÇELIK, R. and BIGGS, D.C. (1987). Acceleration profile models for vehicles in road
traffic. Transportation Science, 21 (1), pp 36-54.
AKÇELIK, R., BIGGS, D.C. and LAY, M.G. (1983). Modelling Acceleration Profiles. Australian
Road Research Board. Internal Report AIR 390-3.
AKÇELIK, R. and RICHARDSON, A.J. (1981). Fuel Consumption Models and Data Needs For
the Design and Evaluation of Urban Traffic Systems. Australian Road Research Board. Internal
Report AIR 367-2.
AKÇELIK, R. RICHARDSON, A.J. and WATSON, H.C. (1982). Relation between two fuel
consumption models. Joint SAE/ARRB 2nd Conf. 'Traffic Energy and Emissions', Melbourne.
AUSTROADS (2005). Modelling, Measuring and Mitigating Road Traffic Noise. Research
Report AP-R277/05. Austroads, Inc., Sydney, Australia.
BIGGS, D.C. (1988). ARFCOM – Models for Estimating Light to Heavy Vehicle Fuel
Consumption. Research Report ARR No. 152. ARRB Transport Research Ltd, Vermont South,
Australia.
BIGGS, D.C. and AKÇELIK, R. (1983). Procedures for On-Road Acceleration, Deceleration and
Steady-Speed Tests. Australian Road Research Board. Internal Report AIR 390-2.
BIGGS, D.C. and AKÇELIK, R. (1984). Validation of a Power-Based Model of Car Fuel
Consumption. Australian Road Research Board. Internal Report AIR 390-4.
BIGGS, D.C. and AKÇELIK, R. (1985a). Further Work on Modelling Car Fuel Consumption.
Australian Road Research Board. Internal Report AIR 390-10.
BIGGS, D.C. and AKÇELIK, R. (1985b). Further work on modelling car fuel consumption.
Australian Road Research 15(1), pp 46-49.
BIGGS, D.C. and AKÇELIK, R. (1986a). An energy-related model of instantaneous fuel
consumption. Traffic Engineering and Control, 27(6), pp 320-325.
BIGGS, D.C. and AKÇELIK, R. (1986b). Estimation of car fuel consumption in urban traffic.
Proc. 13th ARRB Conf. 13(7), pp 123-132.
BIGGS, D.C., AKÇELIK, R. and BOWYER, D.P. (1984). The Effects of Driver Behaviour And
Vehicle Characteristics on Fuel Consumption: An Application of the Power Model. Australian
Road Research Board. Internal Report AIR 390-7.
 BOWYER, D.P., AKÇELIK, R. and BIGGS, D.C. (1985). Guide to Fuel Consumption Analysis
for Urban Traffic Management. Special Report SR No. 32. ARRB Transport Research Ltd,
Vermont South, Australia. (Previously published as AIR 390-9).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
1.6 Akcelik & Associates Pty Ltd

BOWYER, D.P., AKÇELIK, R. and BIGGS, D.C. (1986). Fuel consumption analyses for urban
traffic management. ITE Journal, 56(12), pp 31-34.
BOWYER, D.P., AKÇELIK, R., BAYLEY, C. and BIGGS, D.C. (1982). An Audit of Energy
Savings from Traffic Management: Stage 1 Report. Australian Road Research Board. Internal
Report AIR 390-1.
BOWYER, D.P., AKÇELIK, R., BIGGS, D.C. and BAYLEY, C. (1984). Fuel Consumption
Savings from Urban Traffic Management: Final Report from a Scientific Audit. Australian Road
Research Board. Internal Report 390-8. (Also in: Australian Road Research 14(12), pp 95-96).
DREW, D.R. (1968). Traffic Flow Theory and Control. McGraw-Hill, New York.
GUNATILLAKE, T., CAIRNEY, P. and AKÇELIK, R. (2000). Traffic Management Performance
- Development of the Traffic Frustration Index. AUSTROADS Project Report AP-R160.
Association of Australian State Road and Transport Authorities, Sydney, Australia.
HOLYOAKE, P.A. (1985). Models for the Effect of Driving and Environmental Conditions on Car
Fuel Consumption and Emissions. Report T76/85. Department of Mechanical and Industrial
Engineering, The University of Melbourne, Parkville, Victoria, Australia.
HOMBURGER, W. S., et al. (2001). Fundamentals of Traffic Engineering. 15th Edition. Institute
of Transportation Studies, University of California, Berkeley. USA.
LUK, J.Y.K. and AKÇELIK, R. (1983). Predicting Area Traffic Control Performance with
Transyt/8 and an Elemental Model of Fuel Consumption. Proc. 12th ARRB Conf. 12(4), pp 87-
101. (Also: Internal Report AIR 388-1).
MUSTAFA, M.A.S and VOUGIAS, S. (1993). Analysis of pollutant emissions and concentrations
at urban intersections. ITE Compendium of Technical Papers, 63rd Annual Meeting of the Inst. of
Transportation Engineers, pp 234-238.
REDINGTON, T. (2001). Modern roundabouts, global warming and emissions reductions: Status
of research and opportunities for North America. Paper presented at the Canadian Transportation
Research Forum, 36th Annual Conference, Vancouver, British Columbia, Canada.
TAYLOR, M.P. and YOUNG, T. (1996). Developing a set of fuel consumption and emissions
models for use in traffic network modelling. Proceedings of the 13th International Symp. on
Transportation and Traffic Theory. (Ed. J-B. Lesort). Pergamon, Elsevier Science, Oxford 1996,
pp289-314.
TRANSFUND NEW ZEALAND (1997). Project Evaluation Manual. TRANSFUND New
Zealand Manual No. PFM2. Wellington, New Zealand.
TRB (2000). Highway Capacity Manual. Transportation Research Board, National Research
Council, Washington, D.C., U.S.A. [“HCM 2000”].
TRB (2010). Highway Capacity Manual. Transportation Research Board, National Research
Council, Washington, DC, USA. ["HCM 2010"]

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SIDRA TRIP
USER GUIDE
SECTION 2 - GETTING STARTED

Restricted document
for use under SIDRA TRIP
software licence only

September 2011
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

© AKCELIK & ASSOCIATES PTY LTD 2000 - 2011

All Rights Reserved.
No part of this document may be copied, reproduced, used to prepare derivative works by modifying,
disassembling, decomposing, rearranging or any other means, stored in a retrieval system or
transmitted in any form or by any means: electronic, electrostatic, magnetic tape, mechanical,
photocopying, recording or otherwise, without the prior and written permission of Akcelik &
Associates Pty Ltd.
The information provided in this document is CONFIDENTIAL and must not be used for any
commercial purposes or in any way that infringes on the intellectual property or other rights of Akcelik
& Associates Pty Ltd.
Readers should apply their own judgement and skills when using the information contained in this
document. Although the information contained in this document is considered accurate, no warranties
or guarantees thereto are given. Whilst the authors have made every effort to ensure that the
information in this document is correct at the time of publication, Akcelik & Associates Pty Ltd, save
for any statutory liability which cannot be excluded, excludes all liability for loss or damage (whether
arising under contract, tort, statute or otherwise) suffered by any person relying upon the information
contained in the document. Any such statutory liability is reduced to the full extent lawful.
Any product, trade or manufacturer name(s) appear in this document only because they are considered
essential for the purposes of this document, and Akcelik and Associates Pty Ltd does not endorse,
market, support, represent or accept any liability for any product or manufacturer appearing in this
report unless it is so specified.

Any examples given in User Guides, training manuals and similar documents for SIDRA SOLUTIONS
software products, or any templates included in SIDRA SOLUTIONS products, have been prepared for
the purpose of demonstrating software features or providing a basis for user input, and do not
necessarily represent the best design practice.

SIDRA SOLUTIONS software products are professional tools for the purpose of capacity, level of
service, operating performance and travel quality analysis of road traffic. They are not safety design or
evaluation tools. We recommend the use of appropriate safety analysis and audit tools for this
purpose.

ACKNOWLEDGEMENTS
Akcelik & Associates Pty Ltd acknowledges the contributions by numerous users from many countries
around the world through their valuable comments towards the development of SIDRA SOLUTIONS
software products.

IMPORTANT

User Guides and training manuals for SIDRA SOLUTIONS software products are RESTRICTED
DOCUMENTS for use under software licence only. These documents may not be placed in any public
library, may not be rented, loaned or distributed by any means. They are under the COPYRIGHT of
Akcelik and Associates Pty Ltd and may only be reproduced with written permission.
SIDRA TRIP User Guide 2.1

2. GETTING STARTED

2.1 INSTALLING SIDRA TRIP

2.1.1 Software Installation

Installation of SIDRA TRIP is a straightforward process using the setup file downloaded from the
SIDRASOLUTIONS website. Before installing SIDRA TRIP, please ensure that the following
conditions are met:
 you are logged in with administrator rights on the computer, and
 the computer meets the system requirements (see the introduction section of this User
Guide).
To install SIDRA TRIP 1.1:
 Run SIDRATRIP11Setup.exe to install.
 After the SIDRA TRIP Installation program is loaded, a series of dialog boxes will appear.
Follow the instructions. Supply directory information if required. Click the Next button to
proceed to the next dialog.
The setup program will install:
 Microsoft .NET Framework Version 2.0 if it is not present on your computer,
 the SIDRA TRIP system files in a folder under C:\Program Files\SIDRA SOLUTIONS
(C:\Program Files (x86)\SIDRA SOLUTIONS on 64-bit systems), or in another location
that you can choose.
When installation has been completed successfully, a SIDRA TRIP icon will be installed on your
desktop. Also, a new program named SIDRA TRIP 1.1 will be created under the SIDRA
SOLUTIONS folder in Start - All Programs.
To run SIDRA TRIP, simply double-click the desktop icon.

2.1.2 Uninstalling
In the case of a SINGLE licence, deactivate the licence before uninstalling the software for use on
another computer. Uninstalling the software will not automatically deactivate the licence.
See Section 2.2.1 for information on activating and deactivating a SINGLE licence.
To uninstall SIDRA TRIP software, use one of the following options depending on your Windows
version:
 Windows XP: Use Control Panel - Add or Remove Programs, select
SIDRA TRIP from the program list, and click the Remove button.
 Windows 7 and Vista: Use Control Panel - Programs and Features, select
SIDRA TRIP from the program list, and click the Uninstall button.

2.1.3 Your Account

SIDRA TRIP is distributed via the SIDRASOLUTIONS eCommerce website which incorporates
the software licence management system. Customers are allocated user ACCOUNTS on the
eCommerce website. By logging into your Account homepage using your email and password,
you can download software, and use the ONLINE STORE to renew COVER and purchase new or
upgrade licences.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.2 Akcelik & Associates Pty Ltd

Account and login information is given to one "Licence Contact" only within an organisation.
You must liaise with this person in your organisation in regard to licensing matters and access to
the eCommerce website.

2.1.4 Downloading
You can download the SIDRA TRIP setup program from the SIDRA SOLUTIONS website:
 After you sign up for a Free Software Trial, you will be sent an email with the download
link for downloading the setup program.
 After your purchase has been processed, the Licence Contact will be sent an email with
the download link for downloading the setup program.
 You can also download the setup program from your online account any time after
purchase.

2.1.5 Trial Mode

If you do not activate SIDRA TRIP following installation, it will operate in Trial Mode for a
limited number of days. In Trial Mode, the program is fully functional. However, the software
output produced in this mode will indicate that the software is an "Unregistered Trial Version".
The number of days remaining in Trial Mode will be shown in the Licence Configuration dialog
(see Figure 2.1 in Section 2.2).
The Trial Mode period will not be reset if you uninstall and reinstall the software. You will need to
purchase a licence to continue to use the software.
Refer to Section 2.2 for detailed information on licence activation.

2.1.6 SIDRA TRIP User Guide

The SIDRA TRIP User Guide is installed with the software for direct access from the SIDRA TRIP
menu (Help - User Guide). Refer to Section 2.3.3 for detailed information.
A number of documents of interest to SIDRA TRIP, including various articles providing detailed
information related to the analysis methodology used in SIDRA TRIP, can be downloaded from the
SIDRA SOLUTIONS website (under Resources - Articles).

2.1.7 Example Files

Various examples of SIDRA TRIP profiles and sample source data files are provided with the
software. The examples are provided in two separate folders (Metric Examples and US Units
Examples) which will be installed on your computer. These can be accessed via Start - All
Programs - SIDRA SOLUTIONS - SIDRA TRIP 1.1 Tools - Examples.
We recommend that you make use of these examples for learning about the software.

2.1.8 Defaults and Options

The initial settings for SIDRA TRIP are:
 Current Default System = Metric Units, and
 Drive Rule = Left.
US users may wish to set:
 Current Default System = US Customary Units (use Tools - Defaults), and
 Drive Rule = Right (use Tools - Options - Animation).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.3

2.2 LICENCE ACTIVATION

Information about activating a SINGLE Licence and setting up an ENTERPRISE licence is given
in this section.
At the time of licence purchase, a Customer ID, Licence ID(s) and Password will be allocated by
the eCommerce system to the person who purchases the licence. These details will be required to
activate the software. This information should be kept safely for future use.
When you start SIDRA TRIP, the Licence Configuration dialog will appear with a message about
the unlicensed state of the software (Figure 2.1). You can also access this dialog via Start - All
Programs - SIDRA SOLUTIONS - SIDRA TRIP 1.1 Tools - Licence Configuration.
In the Licence Configuration dialog, use the options available for Online Activation, Offline
Activation and Deactivation of a SINGLE computer licence (Section 2.2.1), or for setting up an
ENTERPRISE licence (Section 2.2.2).

Figure 2.1 - Unlicensed state of the software when you start SIDRA TRIP

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.4 Akcelik & Associates Pty Ltd

2.2.1 SINGLE Licence

In the Licence Configuration dialog, use the Fixed Licence File option for activating or
deactivating a SINGLE licence (Figure 2.2).

Online Activation of SINGLE Computer Licences

You need to activate each SINGLE computer licence using the Licence ID and Password issued to
you (Figure 2.2):
 Run the unlicensed software, or use Start - All Programs - SIDRA SOLUTIONS -
SIDRA TRIP 1.1 Tools - Licence Configuration to access the Licence Configuration
dialog.
 In the Licence Configuration dialog, select the Fixed Licence File option (radio button).
 Click Activate Licence Online.
 In the Activate Licence Online dialog, enter your Licence ID and Password, and click
Activate. Wait for the processing to be completed and a message given.
 If you get the message “Activation Succeeded”, click OK to start using the software in a
licensed state (non-Trial mode). In this state:
o your Company Name, Customer ID and Licence Type will appear in the Licence
Configuration dialog, and will be displayed in software output reports, and
o your Licence ID, Company Name and Licence Type will appear in the Help -
About dialog.

Choose the Fixed Licence File option

and click Activate Licence Online

Enter Licence ID
and Password

xxxxx
x
xxxxx
x

Figure 2.2 - Licence Configuration dialog and online activation of SINGLE computer licences

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.5

You may get the message “Activation Failed” with a message related to the problem.
A Web Service Error Number may also be given indicating a problem. Refer to the Online
Licence Activation Failure section below about possible causes of failure.

Online Licence Activation Failure

Online licence activation may fail for a number of reasons resulting in a failure message. The
reasons for failure include the following:
 You have Internet access problems.
 You did not enter your correct Licence ID and Password.
 The licence has already been activated.
 The licence was blacklisted.
These are explained below.
Internet access problems
If the software may not be able to connect to the activation server, you will receive the response
"The remote name could not be resolved: 'secure.sidrasolutions.com'". Internet access
problems may occur because:
 you do not have an Internet connection, or
 you have an Internet connection but you have a firewall or network administration
policies that prevent the sending or receiving of the activation information over the
Internet.
You should first check that your Internet connection is working. For example, open a web
browser and see if you can look at web pages. If your Internet connection is not working, you
should fix it and then try activating the software again.
If your Internet connection appears to be working, but activation still fails, contact your network
administrator or IT Department and ask them if there is a problem of Internet access restriction.
If you get a message about "Proxy Authentication Required", or any problem/enquiry
mentioning "Proxy settings" or "Proxy Server", this message is being generated by your network
and simply reported by SIDRA INTERSECTION. The error indicates that the internet
communication required by the SIDRA licensing is being blocked by your proxy server. You need
to get your IT department to allow the software to communicate to our activation server as follows:
 Our licensing system runs on the following domain (ssl):
secure.sidrasolutions.com (66.29.201.230).
 Our update system runs on our normal website domain:
sidrasolutions.com (66.29.201.229).
 The XML Activation web service address is
https://secure.sidrasolutions.com/solo/webservices/XmlActivationService.asmx
(this Web Service is used for activation and deactivation).
 Standard port numbers are used in both cases and proxy settings are obtained from Internet
Explorer.
Licence ID or Password incorrect
The message "Invalid License ID or Invalid License ID/Password combination" will appear.
Check your Account homepage on the SIDRASOLUTIONS website for the correct Licence ID
and Password.
If you use a valid Licence ID and Password from a different SIDRA INTERSECTION version, or
from a different SIDRA SOLUTIONS product, you will get a message like: "SIDRA

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.6 Akcelik & Associates Pty Ltd

INTERSECTION cannot be activated using the Licence ID that you have entered. The
Licence ID corresponds to a different SIDRA INTERSECTION version or a different
product." Check your Account homepage on the SIDRASOLUTIONS website for the Licence ID
and Password that correspond to the current SIDRA INTERSECTION version.
The licence has already been activated
Error message "Activation Failed - The web service returned an error. Web Service Error
Number 5013." may be given when activation has failed because:
(i) the licence specified has already been activated, or
(ii) the software could not receive a response from our activation server.
In relation to case (i), if you have more than one licence, please check that you specified the correct
Licence ID (one that is not activated). If your intention is to move a previously activated licence
from another computer, you will need to deactivate it on the other computer before you can activate
it on this computer.
In case (ii), an online activation may appear to have failed on your computer due to the response
from our activation server having been blocked by your firewall or network settings. If the
activation information was received correctly and processed by our activation server, the activation
status will appear as "activated" in the SIDRASOLUTIONS licensing system despite the response
being blocked at your end. If you subsequently change firewall settings to allow the response
through and attempt an Online Activation or if you attempt an Offline Activation you will get an
activation failure message indicating that the software is already activated. In this case, you should
contact us by email to [email protected] for help with resetting your licence activation
status.
Licence blacklisted
The Licence ID that you entered may have been cancelled. Please check the most recent
information provided to you for your current licence details.
If none of the above reasons apply
If you are still unable to activate the software automatically after ensuring that none of the above
reasons for failure of online licence activation applies, you will need to carry out an Offline
Activation as described in the section below.

Offline Activation of SINGLE Computer Licences

Offline Activation is NOT the preferred method. The simple Online Activation using the
Internet is the preferred method, and you should attempt to resolve your Internet access problems
before using the Offline Activation method.
When you have to use the Offline Activation method, you need to use the software and the
SIDRASOLUTIONS web page at the same time (Figure 2.3). You can open the web page on a
different computer if the computer you are wishing to activate does not have Internet access.
The steps in the offline activation process are as follows:
1. Use the Software:
 Run the software.
 In the Licence Configuration dialog, select the Fixed Licence File option (radio
button).
 Click Activate Licence Offline.
 In the Activate Licence Offline dialog, note the two codes.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.7

Software

Website

xxxxx
x
xxxxx 1. Note the two
x codes and enter
xxxxx
in the web page
x
xxxxx dialog.
x
xxxxx
x

xxxxx
4. Click
xxxxxx
x
xxxxx Activate xxxxxx
x

3. Enter the Licence ID and 2. If successful, a Licence ID

the Registration Code as and a Registration Code will
displayed on the web page. be displayed.
Complete the Registration
Details section.

xxxxxx
xxxxxx
xxxxxx
xxxxxx
xxxxxx

Figure 2.3 - Offline Activation of SINGLE Computer Licences

2. Use the Website:

 Login to your Account homepage using your email and password.
 In the relevant product section in your Account homepage, click on the link provided for
use when you cannot achieve Online Activation.
 On the web page, enter the two codes from the software Activate Licence Offline
dialog and click Submit.
 If the codes have been entered correctly, and the licence has not already been activated, a
Licence ID and a Registration Code will be displayed on the web page.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.8 Akcelik & Associates Pty Ltd

3. Use the Software:

 In the software Activate Licence Offline dialog:
o enter the Licence ID and the Registration Code as displayed on the webpage, and
o complete other Registration Details.
 When all details are entered, click Activate.
 If you get the message “Activation Succeeded”, click OK to start using the software in
a licensed state (non-Trial mode).
Offline activation may fail for a number of reasons. Refer to the Online Licence Activation
Failure section above about possible causes of failure.

Moving Your Single Licence from One Computer to Another

If you used the Online Activation method to activate your SINGLE Computer licence on your
computer, it is very easy to transfer your SINGLE Licence from one computer to another computer
in your organisation. Follow the steps given below:
 Before uninstalling the software, use the Online Deactivation method to deactivate your
licence on the computer the software is installed on.
 Download and install SIDRA INTERSECTION on your new computer (Section 2.1).
 Activate your licence on your new computer using the Online Activation method.
If you uninstall after an Online Activation or Offline Activation and delete the licence file and do a
subsequent installation on the same computer, the software will be in an unlicensed state and you
will not be able to do a subsequent Online Activation or Offline Activation with this licence ID
since, in the SIDRASOLUTIONS licensing system, it will still be tied to the computer where the
Offline Activation was carried out.
If you used the Offline Activation method to activate your SINGLE Computer licence on your
computer, you will need to use the Offline Licence Transfer method (Section 1.3.6).
If you need licensing support, contact us by email to [email protected].

Online Deactivation of SINGLE Computer Licences

If you used the Online Activation method to activate your licence on your computer, deactivation
is simple. To deactivate your SINGLE computer licence:
 Use Start - All Programs - SIDRA SOLUTIONS - SIDRA TRIP 1.1 Tools - Licence
Configuration to access the Licence Configuration dialog.
 In the Licence Configuration dialog, select the Fixed Licence File option (radio button).
 Click Deactivate Licence Online.
When you get a message that deactivation has succeeded, click OK.
If you want to move your licence to another computer, you should first deactivate the licence using
Deactivate Licence Online facility as described above. If you uninstall the software without first
deactivating it:
 the licence will stay in an activated state;
 if you reinstall the software on the same computer, it will appear to be activated already;
 you will not be able to activate the licence on another computer.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.9

Offline Licence Transfer for SINGLE Computer Licences

If you used the Offline Activation method to activate your SINGLE Computer licence on your
computer:
 you cannot use the Online Deactivation method to deactivate a licence activated using the
Offline Activation method, and you will not be able to deactivate the licence by uninstalling
the software; and
 when you uninstall after an Offline Activation, the licence file will stay in place and a
subsequent installation on the same computer will reuse the same licence file and it will
appear activated.
If your intention is to move your licence to another computer, and the licence was activated
using the Offline Activation method, you will need to use the Offline Licence Transfer method.
Follow the steps given below:
 Use Start - All Programs - SIDRA SOLUTIONS - SIDRA TRIP 1.1 Tools - Licence
Configuration to access the Licence Configuration dialog.
 In the Licence Configuration dialog, select the Fixed Licence File option (radio button).
 Click Offline Licence Transfer.
 An Offline Licence Transfer dialog will appear. Follow the steps.
If you need licensing support, contact us by email to [email protected].

2.2.2 ENTERPRISE Licence

The ENTERPRISE Licence allows unlimited use of SIDRA TRIP within the licensed organisation.
Only one licence is issued to the licensed organisation and the software can be installed on
individual computers using the same licence. No deactivation-reactivation is needed to uninstall
and reinstall the licence on individual computers.

Setting up Licensing on Individual Computers

Instructions regarding deployment via a “Silent" installation are provided with the software licence.
Alternatively, the software can be installed on individual computers and licensed as follows (note
that Administrative rights will be necessary for this process):
 On the local machine where the software has been installed, save the ENTERPRISE
Licence file to the folder:
o (Vista and Windows 7) “C:\ProgramData\SIDRA SOLUTIONS\Licenses\”
o (Windows XP) “C:\Documents and Settings\All Users\Application Data\SIDRA
SOLUTIONS\Licenses\”
 Run the unlicensed software, or use Start - All Programs - SIDRA SOLUTIONS -
SIDRA TRIP 1.1 Tools - Licence Configuration to access the Licence Configuration
dialog.
 In the Licence Configuration dialog, select the Custom License File option (radio button)
and click the Browse button.
 Browse to and select the licence file saved as indicated above.
 The software should now be in a licensed state (non-Trial mode). In this state:
o your Company Name, Customer ID and Licence Type will appear in the Licence
Configuration dialog, and will be displayed in software output reports, and
o your Licence ID, Company Name and Licence Type will appear in the Help -
About dialog.
 Click OK to close the Licence Configuration dialog.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.10 Akcelik & Associates Pty Ltd

2.3 USING SIDRA TRIP

2.3.1 Starting SIDRA TRIP
To start SIDRA TRIP, double-click the SIDRA TRIP icon on your desktop. If the Trial Dialog
appears, this indicates that your copy of SIDRA TRIP is not registered. You can use SIDRA TRIP
in Trial Mode temporarily. To do this click Try in the Trial Dialog. You should register SIDRA
TRIP without delay unless you are using a Trial Version as explained in Section 2.2.
When SIDRA TRIP is run for the first time, you may wish to use Tools - Options - Settings to set
the Drive Rule (driving on the right-hand side or left-hand side of the road) and Units (Metric, US
Customary). The Drive Rule setting will affect the animation only.
You can double-click the name of the data file that contains the trip profile (extension aam) to start
SIDRA TRIP using file association. If you start SIDRA TRIP in this way, SIDRA TRIP will start
and will automatically open the data file you double-clicked. You should start SIDRA TRIP using
this method only by selecting a single file. You can open any further files within SIDRA TRIP.
See Section 2.3.2 for further information on SIDRA TRIP file association.

2.3.2 SIDRA TRIP User Interface

The main window of SIDRA TRIP contains the Title Bar, the Main Menu, the Toolbar, the
Animation Pane, the Profile Tree Pane, the Display Pane and a Status Bar (Figure 2.9). These are
explained below.

Title Bar
The Title Bar has the name SIDRA TRIP. The selected (maximised) window name will also be
displayed in the title bar.

Main Menu
The SIDRA TRIP Main Menu consists of File, Edit, View, Animate, Tools, Window, and Help
menus. Some commonly used menu items can also be invoked by use of shortcut keys (Ctrl+N for
New, Ctrl+P for Print, etc).
All menu items are sensitive to the context of the currently selected object. This means that certain
menu options will not be available if they are not applicable to the currently selected object.
Most File menu options apply to the Profile (aam) file. The menu contains the following options:
 New: create a new Profile;
 Open: open an existing Profile;
 Save: save the current Profile;
 Save As: create a new Profile by making a copy of the current Profile;
 Save Sim Data As: save the detailed step-by-step simulation data for the current Profile in
csv, txt or xml format;
 Save Trip Data As: save the trip data for the current Profile in csv or txt format;
 Close (close the current Profile)
 Save Output As: save the selected text output in html format or xml format;
 Save Graph As: save the selected graph in emf picture format;

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.11

 Print: print the contents of the selected output (text or graph) window;
 Print Preview: view the print image of the contents of the selected output (text or graph)
window;
 Recent Profiles: a list of most recently used files is shown (click the desired file to open);
 Exit: exit SIDRA TRIP (you can also press Alt+F4 to exit SIDRA TRIP).
The Edit menu options operate on the current output window. The Edit menu contains the
following options:
 Cut: cuts the selection to the clipboard;
 Copy: copies the selection to the clipboard;
 Paste: pastes the clipboard contents;
 Select All: selects all contents of current window;
 Find: prompts for a text string and finds the next or previous occurrence of it in the current
text output window.

Title bar Main Menu Toolbar (buttons)

Text
Output

Graphs

Move to Speed
resize Display
Animation pane
areas

Status bar

Profile
Tree Display
Pane Pane

Animation
Pane

Figure 2.9 - SIDRA TRIP user interface

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.12 Akcelik & Associates Pty Ltd

Note that Cut and Paste will be blocked in the Edit menu since the contents of an output window
cannot be changed.
The View menu contains the options Speedometer (show or hide the Speedometer display),
Powermeter (show or hide the Powermeter display), and Animation Pane (show or hide the
Animation Pane). These view options have a toggle action (show or hide). The program
remembers the status of these view options.
The Animate menu contains the options Play (run animation), Pause (stop animation temporarily),
and Reset (stop animation and reset to the start of trip). Animation speed can be changed by using
the Time Factor button in the toolbar.
The Tools menu contains the options Defaults (to change various settings for input and model
parameters), and Options (to set options for Drive Rule, Units, Displays & Output Settings, Graphs
and Animation options). See Section 2.4 for detailed discussion on Defaults and Options.
The Window menu contains the standard Windows options to allow you to arrange the open
windows in the display pane, and a list of currently open windows that allows you to select a
desired window.
The Help menu gives access to the Help system, the User Guide, the SIDRA SOLUTIONS website
(requires internet connection), and also has an About option that gives basic information (version
number, licence type, etc.).

Toolbar
The Toolbar buttons allow quick access to some frequently used commands (click once). The
toolbar buttons (except the Time Factor Scale) have automatic pop-up descriptions.
The toolbar buttons (as displayed from left to right) and their actions are as follows:
 New Profile: create a new Profile (same action as File - New);
 Open Profile: open an existing Profile (same action as File - Open);
 Save Profile: save the current Profile (same action as File - Save);
 Print (same action as File - Print);
 View Speedometer: view or hide (toggle) the Speedometer display (same action as View -
Speedometer);
 View Powermeter: view or hide (toggle) the Powermeter display (same action as View -
Powermeter);
 Animation Pane: view or hide (toggle) the Animation Pane (same action as View -
Animation Pane);
 Play: run animation (same action as Animate - Play);
 Pause: stop animation temporarily (same action as Animate - Pause);
 Reset: stop animation and reset to the start of trip (same action as Animate - Reset);
 Help: access to the Help system, the User Guide, etc. (same action as Help - Contents);
 Time Factor Scale: click and drag the pointer in the range 1 (real-time) to 10 (very fast) to
modify the animation speed.

Animation Pane
The Animation Pane presents a simple animation of vehicle movement in accordance with the trip
profile specified. This pane can be hidden or displayed (toggle action) by clicking the Animation
Pane button on the toolbar or using View - Animation Pane.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.13

Profile Tree Pane

The Profile Tree on the left-hand side of the screen displays the current Profile as a node with
various child nodes (or sub-nodes) structured in a hierarchical manner (Figure 2.9). The main
nodes are:
 Input
o Edit Profile
o Input Report
o Diagnostics (if applicable)
 Output
o Trip Statistics
o Sums
o Event Statistics
o Graphs.
The Graphs node contains sub-nodes corresponding to different groups of Graphs, and each group
has sub-nodes corresponding to different graphs (see Figure 2.9).
Double-clicking a node in the tree representing a group will open or close the set of sub-nodes in
the group (similar to clicking the + or - symbol next to the node name). Double-clicking a node at
the lowest level in the hierarchy will display (open) the corresponding item in an input dialog or
output window in the Display Pane.
You can change the size of the visible area of the Profile Tree Pane by clicking and dragging the
vertical line separating the Profile Tree Pane and the Display Pane.
If the relevant information does not exist, the node(s) representing the input dialog or output
display will not appear in the Profile tree. For example, the Event Statistics output node will not
exist when the trip profile is created using the Travel Data method.
If any errors are found in processing, output nodes will not be present in the Profile tree (see
Section 2.5).

Display Pane
The Display Pane contains all open output windows. These may be the input (Edit Profile) dialog,
Input Report window, the Trip Statistics, Sums and Event Statistics text output windows, and
windows displaying Graphs. Windows are opened in the Display Pane by double-clicking the
corresponding nodes in the Profile tree. You can arrange open windows using the Window menu
options.
You can maximise the visible area of the displays in the Display Pane by reducing the size of the
visible area of the Profile Tree Pane by clicking and dragging the vertical line separating the Profile
Tree and Display Panes.
The Speedometer and Powermeter displays can be placed anywhere on the screen.

Status Bar
The Status Bar appears at the bottom of the SIDRA TRIP window. The Status Bar shows the
vehicle type and the type of vehicle manoeuvre during animation.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.14 Akcelik & Associates Pty Ltd

Opening an Existing Profile

To open an existing Profile, click the Open button on the toolbar, or select File - Open from the
menu. An Open dialog box will appear where you can select the desired file. This dialog shows
Files of type: SIDRA TRIP Files and lists the Profile (.aam) files. When you select a file and click
OK, the Profile will be opened in the Profile Tree Pane, and text output windows will be opened in
the Display Pane (according to the output display options selected). Only one Profile can be
opened at a time.
An easy way of opening a Profile is to select it from the Recent Profiles list under the File menu.

Closing a Profile
To close a Profile select File - Close from the menu, or right-click on the Profile name in the
Profile Tree and select Close Profile.
Closing all windows in the display pane will not close a Profile. To close any graph or text output
window in the display pane, click the "X" box at the top right-hand corner of the window, or select
Window - Close from the menu.
To close all windows in the display pane, select Window - Close All.

SIDRA TRIP File Extensions and Associations

The Windows operating system associates file types with programs so that users may conveniently
double-click a file and start the associated program. This association is based on the three-letter
filename extension. For this purpose, SIDRA TRIP uses the .aam file extension. You should open
only a single file using this method. SIDRA TRIP will list SIDRA TRIP Profile (.aam) files when
you select File - Open.
After installing SIDRA TRIP, all files on your computer with the .aam extension will be associated
with SIDRA TRIP regardless of whether they were created by SIDRA TRIP or by another
program. These files will be labelled as "SIDRA Trip Profile" files and have SIDRA TRIP icons
associated with them.
The file association process is not related to the file content in any way. SIDRA TRIP will
probably give you an error message if you are trying to open a file with an .aam extension created
by another program. File associations can be changed or removed using standard methods in
Windows.

Backup Files
Each time a Profile (.aam) file is opened, a backup file is created. The backup file has the name of
the original file (including the .aam extension) with the further extension .bak added and is saved
in the same folder as the original file. For example, if you open the file MyProfile.aam, the backup
file will be named MyProfile.aam.bak and will be created in the same folder as MyProfile.aam.
The backup file will overwrite any existing backup file that had been created when the Profile was
opened at a previous time (multiple backup files are not created). The backup file will not be
created if any errors are detected during the process of opening the file in order to prevent the
possible overwriting of a "good" backup file.
The backup file is created only at the time the Profile is opened and it is not updated when the
Profile is subsequently saved (unless the Profile is closed and then re-opened). It therefore contains
an exact copy of the Profile (.aam) file as it was at the time that it was last opened. The backup file
can be used to restore the previous version of the Profile (.aam) file in cases where mistakes have
been made during editing, or if there have been any software problems that have damaged the file.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.15

If the program is not able to create the backup file for any reason, you will receive the warning
message "Failed to write backup file" followed by the name of the backup file and the reason for
the problem. Although this will not prevent you from editing and processing the Profile, you will
not have a backup file in this situation and the cause of the problem should be investigated. The
most likely cause of this problem is rights or permission issues, particularly if your files are stored
on a network.
If you wish to use the backup file to replace an unwanted Profile (.aam) file, you should rename
or delete the unwanted file and then use the Windows Rename function to remove the .bak
extension from the backup file. SIDRA TRIP cannot open the backup files directly (the software
can only open Profile (.aam) files.

Processing
SIDRA TRIP input data processing, simulation and computations are carried out, and text output
and graphs are generated automatically (appearing as nodes in the Profile tree) when the changes
made in the Edit Profile dialog are accepted by clicking the OK button. The contents of output
windows open in the Display Pane are updated automatically.

Printing Text and Graphs

In SIDRA TRIP, printing text output and graphs is easy using the Print function directly, or using
the Windows clipboard facility for capturing displays or text and pasting into a word processing
(e.g. MS Word) or graphics (e.g. MS Paint) file. Refer to Sections 4.2 and 4.3 for detailed
information.

2.3.3 User Guide

The SIDRA TRIP User Guide is installed with the software. It is accessible using
Help - User Guide in the menu.
The User Guide is in Adobe Acrobat (PDF) format. Adobe Reader is required to read the User
Guide. If you do not have Adobe Reader installed on your computer, you will need to install it.
The software licence permits printing of the User Guide for the licensee's own use only. The User
Guide is a restricted document for use under the SIDRA SOLUTIONS software licence only.
Printed copies of the guide may not be placed in any public library, may not be rented, loaned,
distributed or reproduced by any means.
Some or all sections of a printed User Guide will become outdated with the release of each version
of the software. The electronic copy installed with the software is always the most up-to-date
version of the User Guide.
The SIDRA TRIP User Guide consists of the following sections:
 Section 1 - Introduction
 Section 2 - Getting Started
 Section 3 - Input
 Section 4 - Output.
Use the facilities of the Adobe Reader window including bookmarks and Search function to find
the information you are looking for.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.16 Akcelik & Associates Pty Ltd

2.3.4 Help System

SIDRA TRIP contains comprehensive help facilities. The Help menu gives access to Help -
Contents, Help - Index, Help - Search, the User Guide, the SIDRA SOLUTIONS website
(requires internet connection), and has an About option that gives basic information about the
software (Version, Serial Number, Organisation, and Licence type).
Help - Contents will access the Contents page of the help, Help - Index will access the Help
Index, and Help - Search will allow you to search for any string within the help file). The ? button
on the toolbar is equivalent to Help - Contents in the Help menu.
Press F1 for context-sensitive help on most topics in SIDRA TRIP. Most dialog boxes in SIDRA
TRIP also include a What's This button. This button is on the right-hand end of the title bar, just
left of the close button and is labelled with a question mark. If you click this button, the mouse
cursor will change to a question mark and pointer. Point to an item in the dialog box and click.
Help relevant to the selected item will be opened.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.17

2.4 DEFAULTS AND OPTIONS

2.4.1 Defaults

SIDRA TRIP has an extensive defaults system that covers a large number of input and model
parameters (see Figures 2.10a to 2.10g). A Reset function is available to reinstate the standard
default values instead of user-specified default values. The current defaults will be used as input
parameters in a Profile created using File - New.
When you use Tools - Defaults, the nodes displaying various settings will be seen in the Defaults
Tree Pane on the left-hand side of the Defaults dialog (Figure 2.10a). To open a display, click the
node in the Defaults Tree Pane. The default values of settings for the selected node will be seen on
the right-hand side of the dialog. The name of the Defaults dialog box (top left corner) will appear
with the name of the selected node in brackets, e.g. as Defaults (Travel Profile Settings).
Select one of the two defaults sets, namely Metric Units or US Customary Units as the Current
Defaults System using the drop-down list (Figure 2.10a). The values of parameters displayed on
the right-hand side of the defaults dialog will vary according to the selected units.
The simulation will be performed and output will be generated using the units in accordance with
the Current Defaults System. However, trip data to be imported can be in different units, which
can be specified as Data Source Units in the Defaults (Travel Profile Settings) dialog
(Figure 2.10a).

Select Metric or US Customary Units

Click the node for the

corresponding settings Select units used in the
to be displayed source data file for
importing data
(irrespective of the Units
selected for the Current
Defaults System)
Defaults
Tree Pane
Click to reinstate
standard defaults

Figure 2.10a - Defaults (Travel Profile Settings) dialog

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.18 Akcelik & Associates Pty Ltd

Driving on the left-hand or right-hand side of the road is an animation feature (Section 2.4.2) and
has no effect on defaults settings.
The standard default sets in the Defaults (Vehicles) and Defaults (Drivers) dialogs cannot be
edited (they are blocked). They need to be cloned before editing under the User nodes (see
Figures 2.10f and 2.10g). All other parameters can be edited. Data range checks are carried out
during editing.
When a Profile which contains user-specified Vehicles or Drivers is opened using File - Open, the
program will offer to import them into the defaults system. The settings for Drivers are relevant to
the Event Data method (driver characteristics for Travel data method are reflected by the imported
data).
Maximum Power, Maximum Grade, Maximum Speed and Maximum Acceleration parameters
specified for Vehicles (Figure 2.10f) are used for checking reliability of data. If simulation data
violates these maximum values, messages about data problems will be gives in a Diagnostics
dialog, as well as the Event Statistics output in the case of the Event Data method (see
Section 3.10).
All values in the Fuel Consumption and Emission Parameters group for Vehicles (Figure 2.10f)
are always in Metric Units even when the Current Defaults System is US Customary Units (see
Section 2.4.3).

Select Time or
Distance

Figure 2.10b - Defaults (Event Profile Settings) dialog

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.19

Click to specify
the Desired
Speed

Check / Uncheck and

enter values to
modify the Speed
Groups

Figure 2.10c - Defaults (Speed Settings) dialog

Specify Flow
Rate for Average
Equivalent Noise
Level (LeqT)
calculation

Figure 2.10d - Defaults (Noise Settings) dialog

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.20 Akcelik & Associates Pty Ltd

Cost Unit is set

according to
the Windows
regional
settings. It can
be changed in
the Cost & LOS
Parameters
input dialog.

Select
Operating Cost
or User Cost

Figure 2.10e - Defaults (Cost & LOS Parameters) dialog

Maximum values
used for
Diagnostics

Fuel Consumption and

Emission Parameters
given in this group are
always in Metric Units
(even when the Current
Defaults System is US
Customary Units)

Figure 2.10f - Defaults (Vehicles) dialog (for "My Car" in this example)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.21

Specify Adjustment
Factors to modify
acceleration and
deceleration rates

Figure 2.10g - Defaults (Drivers) dialog for Event Data method (for "My Driver" in this
example)

2.4.2 Vehicle Classes

SIDRA TRIP provides three classes of default vehicles, namely Passenger Car, Light Vehicle
and Heavy Vehicle. Although the Light Vehicle class incorporates Passenger Cars, SIDRA TRIP
includes a separate Passenger Car class in order to allow more specific treatment, and also allow
the distinction required by the ASJ 2003 (Japanese) Noise model used by the program
(Section 3.5).
Definition of a Heavy Vehicle in SIDRA TRIP is consistent with the definition used in the SIDRA
INTERSECTION software, and is based on Akçelik (1981b, Section 5). According to this, a
Heavy Vehicle is defined as any vehicle with more than two axles or with dual tyres on the rear
axle (based on Akçelik 1981b, Section 5). Thus, buses, trucks, semi-trailers (articulated vehicles),
cars towing trailers or caravans, tractors and other slow-moving vehicles are classified as Heavy
Vehicles. All other vehicles are defined as Light Vehicles (cars, vans, small trucks).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.22 Akcelik & Associates Pty Ltd

2.4.3 Parameter Values for Default Vehicles

A summary of default vehicle parameters Mass, Maximum Power, and Length are given in
Table 2.1.
The three default vehicle classes used in SIDRA TRIP can be considered to be representative
vehicles, whose parameters are based on a more detailed analysis of several vehicle types as seen in
Tables 2.2a and 2.2b.
Tables 2.2a and 2.2b include parameters used for the fuel consumption model used in SIDRA
TRIP. The same model is used with different parameters for estimating fuel consumption and
emissions of Carbon Monoxide (CO), Hydrocarbons (HC) and Nitrogen Oxides (NOx). Carbon
Dioxide (CO2) is estimated directly from fuel consumption by applying a CO2 factor to the fuel
consumption rate.
The model is explained in detail and the full set of default parameters is given in Section 3.8.
Fuel consumption and emission model parameters (Figure 2.10f) are specified in Metric Units even
when the Current Defaults System is US Customary Units (Section 2.4.1).

Table 2.1
Summary of default vehicle parameters Mass, Maximum Power and Vehicle Length

Passenger Car Light Vehicle Heavy Vehicle

Mass
Metric (kg) 1250 1400 11000
US Customary (lb) 2750 3100 24000
Maximum Power
Metric (kW) 80 85 130
US Customary (hp) 110 115 175
Vehicle Length
Metric (m) 4.5 5.0 11.0
US Customary (ft) * 16 18 38

* Larger than the equivalent metric value

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.23

Table 2.2a
Data used for deriving default vehicle parameters used in SIDRA TRIP

Percentage Idling fuel Maximum Power to

Fuel type Loaded
Vehicle Class of Vehicle cons. engine Weight Ratio
(% Diesel) mass, M (kg)
Kilometres (mL/h) power (kW) (PWR)
Passenger Car
Small car 30% 1 900 1100 64 58.2
Medium car 40% 2 1296 1250 80 64.0
Large car 30% 2 1728 1500 110 73.3
Combined 100% 2 1307 1280 84 65.8
Selected 2 1300 1250 80 64.0
Light Vehicle
Passenger car 90% 1.7 1307 1280 84 65.8
Van 8% 13 1728 2000 70 35.0
Light rigid 2% 34 1332 2700 75 27.8
Combined 100% 3 1341 1366 83 60.7
Selected 3 1350 1400 85 60.7
Heavy Vehicle
Light/Medium rigid 60% 48 1620 5500 90 16.4
Medium rigid 15% 87 1800 10000 120 12.0
Medium/heavy truck 15% 98 2340 16000 170 10.6
Heavy truck 5% 100 2520 28000 260 9.3
Heavy articulated 5% 100 2520 38000 300 7.9
Combined 100% 67 1980 10500 126 12.0
Selected 70 2000 11000 130 11.8

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.24 Akcelik & Associates Pty Ltd

Table 2.2b
Data used for deriving default vehicle parameters used in SIDRA TRIP

Tyre Aero. drag

Rolling res. Frontal Fuel cons. Fuel cons.
No. of diameter coefficient
Vehicle Class factor for area parameter parameter
tyres (m) (with wind
tyre type (m 2) A B
factor 1.2)
Passenger Car
Small car 4 0.65 1.00 1.8 0.50 18 0.00460
Medium car 4 0.65 1.00 2.0 0.53 20 0.00520
Large car 4 0.65 1.00 2.2 0.55 22 0.00580
Combined 4 0.65 1.00 2.0 0.53 20 0.00520
Selected 4 0.65 1.00 2.0 0.53 20 0.00500
Light Vehicles
Passenger car 4 0.65 1.00 2.0 0.53 20 0.00520
Van 4 0.65 1.05 2.6 0.62 27 0.00760
Light rigid 4 0.80 1.25 4.0 0.66 35 0.01170
Combined 4 0.65 1.01 2.1 0.54 21 0.00550
Selected 4 0.65 1.00 2.1 0.54 21 0.00550

Heavy Vehicles
Light/Medium rigid 6 0.80 1.20 5.0 0.70 64 0.01540
Medium rigid 6 1.00 1.15 6.0 0.72 86 0.01860
Medium/heavy truck 10 1.00 1.10 6.5 0.77 135 0.02170
Heavy truck 18 1.00 1.05 7.0 0.82 229 0.02540
Heavy articulated 22 1.00 1.05 8.0 0.86 303 0.03070
Combined 8 0.88 1.16 5.6 0.73 98 0.01809
Selected 8 0.90 1.15 5.6 0.73 100 0.01800

2.4.4 Options
You can use Tools - Options to set your preferences. This will open the Options dialog
(Figures 2.11a to 2.11c) which includes several tabs to specify the following options:
 Settings (Figure 2.11a)
o Import new Vehicles and Drivers in Profiles: (for user-specified Vehicles and
Drivers found when opening a Profile);
o Calculate Grade Data from Altitude Data if available during Import: Never,
If Grade Data not given, Always;
o Time Zone Adjustment: No Time Zone Adjustment, Adjust to Current Time
Zone, Adjust to Specified Time Zone (specify a value if the Specified Time
Zone option is selected);
o Noise Models: ASJ 2003 (Japanese), SonRoad (Swiss), RLS-90 (German).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.25

 Output (Figure 2.11b)

o Default Text Output (options for opening Trip Statistics, Sums and Event
Statistics output windows automatically);
o Graphs (options to plot graphs before animation, specify a Maximum Metric Fuel
Economy (L/100km) value for the largest value to be displayed in the Fuel
Economy graph, specify various options for Noise graphs, and check boxes to
select the graphs to be included in the Profile Tree);
 Animation (Figure 2.11c)
o Drive Rule (Left or Right to indicate which side of the road the vehicle uses);
o Smoothness (Low, Medium or High to determine the smoothness of vehicle
movement, which is related to the animation frames per second);
o Scale (Very Small, Small, Normal, Large or Very Large to determine the
distance shown in one frame of animation, which also affects the vehicle size
shown).

The Drive Rule will affect the animation only.

In the Output tab, the current graph settings are indicated by check boxes (graphs which are
checked will be listed in the Profile Tree).
The parameter Maximum Metric Fuel Economy (L/100km) is relevant when Metric units are in
use, and it sets the largest value displayed in the Fuel Economy graph.

Click the tab for the

corresponding settings
to be displayed

Select the Time

Zone Adjustment
method and
specify a value
if the Specified
Time Zone option
is selected

Check if output
wanted

Figure 2.11a - Options dialog - Settings tab selected

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.26 Akcelik & Associates Pty Ltd

Check if
output
wanted

Figure 2.11b - Options dialog - Output tab selected

Select Drive Rule

(for vehicle to use the left-
hand or right-hand side of
the road)

Figure 2.11c - Options dialog - Animation tab selected

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.27

2.5 TROUBLESHOOTING
Common questions and problems that may be encountered while using SIDRA TRIP are described
in this section. Problem descriptions and solutions are organised into a number of categories.
If you are having problems using SIDRA TRIP, firstly see if your problem is described below. If
so, a possible remedy will be suggested. If the suggestion does not work, or you have a problem
that is not described, please apply for support. See the Technical Support page at the start of the
User Guide.

2.5.1 Installation
Error message during installation (or during registration) such as "You must have
Administrative Privileges to install SIDRA TRIP" or "The system administrator has set policies
to prevent this installation".
You must be logged in as Administrator or as a user with administrative privileges to install
SIDRA TRIP. You must also have administrative privileges to perform the registration
process. If you do not have this access to your computer, you must contact your IT
department and ask them to perform the installation.

Windows 95, 98, NT, ME

SIDRA TRIP is not supported under Windows 95, 98, NT and ME. If you are running one
of these versions of Windows, you will not be able to install SIDRA TRIP on your computer.
Changing File Association for SIDRA TRIP Data Files
After installing SIDRA TRIP, all files on your computer with the .aam extension will be
associated with SIDRA TRIP regardless of whether they were created by SIDRA TRIP or by
another program. They will be labelled as "SIDRA TRIP Profile" files and have SIDRA
TRIP icons associated with them. When you double-click one of these files, SIDRA TRIP
will start and open the Profile (and not a program that may have been associated with these
files previously).
If you need to use another program to open a file with the .aam extension, you should still be
able to start the program that uses these files, and open the files using the File - Open
command in that program's menu.
If you do not wish the .aam extension to be associated with SIDRA TRIP, you should follow
one of the three options listed below.
1. You could reinstall another program that uses .aam files. The latest program that is
installed sets its own associations so this would override those set by SIDRA TRIP.
2. Right-click on the .aam file you wish to open. Select "Open With". Choose the
program you wish to be associated with these files, check the box that says "Always use
the selected program ...". Then click OK.
3. From a "My Computer" or "Explorer" window, select Tools - Folder Options - File
Types. Select .aam files from the list, click the Change option and reset the association
to the desired program.
The .aam extension has been chosen by Akcelik and Associates as one that is unlikely to be
used by other programs and we do not believe that this would be a common problem.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.28 Akcelik & Associates Pty Ltd

2.5.2 Starting SIDRA TRIP

Registration
A Trial Dialog will appear when you start SIDRA TRIP if you have not registered it yet.
You must click Register and enter your Serial Number and Customer ID (User ID). See
Section 2.2 for detailed information about the registration process.

2.5.3 Input Problems

Input Data Checking and Program Errors
SIDRA TRIP input dialogs perform various error checks including data range checks. When
a Profile is processed, many more detailed checks of the input data are made before any
computations are performed, and messages are given to the user about any errors found.
If an error occurs that cannot be resolved, you should report the problem by supplying the
Profile (aam) file together with any relevant information to describe the problem succinctly.
Before reporting the problem, refer to the Technical Support page at the start of the User
Guide, or visit the website www.sidrasolutions.com for the procedure to follow.

2.5.4 Processing, Defaults and Options

SIDRA TRIP Takes a Long Time to Process a Profile
When you accept the data changes in the Edit Profile dialog by clicking the OK button, the
SIDRA TRIP simulation runs and information in all open windows is refreshed to show
updated results from the latest run. This process may take a long time if the trip profile
contains a very large number of data points.
The screen is empty (nothing in the Profile Tree Pane and no windows are open in the
Display Pane)
This situation occurs when there is no Profile open in SIDRA TRIP after you start the
program or after you close a Profile. You should simply Open an existing Profile or create a
new Profile.

Model Selection
Considerable care is needed when using SIDRA TRIP with different Units (Metric and US
Customary).
When you use create a new Profile, it will be created in accordance with the current option
settings. To check or change the current model, use Tools - Options - Settings.
When you use the Save As option, the new Profile will retain the model setup of the Profile
being copied from.

Working with both US HCM Metric and US HCM Customary Units

It is not possible to convert a Profile created using Metric units to a Profile with US
Customary Units. Similarly, it is not possible to convert a Profile created using US
Customary Units to a Profile with Metric units.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - GETTING STARTED 2.29

2.5.5 Output Problems

Results are Different on Another Computer
It is possible to obtain differences in text output and some graphs on different computers
because of different Option settings. Use Tools - Options to check your settings.
You should also ensure that your copy of SIDRA TRIP has been kept up to date by the
application of all available Update Packs.

Controlling page breaks

The Print option in the SIDRA TRIP File menu is fairly basic and does not handle insertion
of page breaks. Before printing SIDRA output, right-click in the text area of the output
window and select Print Preview to inspect the output.
Instead of printing the contents of an output window, select the text and pictures using Edit -
Select All, and copy to the clipboard using Edit - Copy. Then paste the output into a word
processor, e.g. Microsoft Word. Insert page breaks as required. See Section 4 for further
information.
No output after processing a Profile
If there is no output produced after processing a Profile, you probably have one or more
input errors.
Copying text and graphs
You must select items before copying. Use Edit - Select All in the main menu, press
Ctrl+A, or right-click in the display area and click Select All in the menu. Refer to
Section 4 for further information.
Exporting to Microsoft Excel
SIDRA TRIP uses Microsoft Internet Explorer to display text output windows. If you install
Microsoft Office, this adds the right-click function "Export to Microsoft Excel" to all
Internet Explorer windows. Although this provides limited ability to link to data in some
web pages, Microsoft unfortunately provides no functionality to link to data in programs
such as SIDRA TRIP. If you wish to copy data from SIDRA TRIP to Excel, you should use
the copy and paste functions.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
2.30 Akcelik & Associates Pty Ltd

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SIDRA TRIP
USER GUIDE
SECTION 3 - INPUT

Restricted document
for use under SIDRA TRIP
software licence only

September 2011
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

© AKCELIK & ASSOCIATES PTY LTD 2000 - 2011

All Rights Reserved.
No part of this document may be copied, reproduced, used to prepare derivative works by modifying,
disassembling, decomposing, rearranging or any other means, stored in a retrieval system or
transmitted in any form or by any means: electronic, electrostatic, magnetic tape, mechanical,
photocopying, recording or otherwise, without the prior and written permission of Akcelik &
Associates Pty Ltd.
The information provided in this document is CONFIDENTIAL and must not be used for any
commercial purposes or in any way that infringes on the intellectual property or other rights of Akcelik
& Associates Pty Ltd.
Readers should apply their own judgement and skills when using the information contained in this
document. Although the information contained in this document is considered accurate, no warranties
or guarantees thereto are given. Whilst the authors have made every effort to ensure that the
information in this document is correct at the time of publication, Akcelik & Associates Pty Ltd, save
for any statutory liability which cannot be excluded, excludes all liability for loss or damage (whether
arising under contract, tort, statute or otherwise) suffered by any person relying upon the information
contained in the document. Any such statutory liability is reduced to the full extent lawful.
Any product, trade or manufacturer name(s) appear in this document only because they are considered
essential for the purposes of this document, and Akcelik and Associates Pty Ltd does not endorse,
market, support, represent or accept any liability for any product or manufacturer appearing in this
report unless it is so specified.

Any examples given in User Guides, training manuals and similar documents for SIDRA SOLUTIONS
software products, or any templates included in SIDRA SOLUTIONS products, have been prepared for
the purpose of demonstrating software features or providing a basis for user input, and do not
necessarily represent the best design practice.

SIDRA SOLUTIONS software products are professional tools for the purpose of capacity, level of
service, operating performance and travel quality analysis of road traffic. They are not safety design or
evaluation tools. We recommend the use of appropriate safety analysis and audit tools for this
purpose.

ACKNOWLEDGEMENTS
Akcelik & Associates Pty Ltd acknowledges the contributions by numerous users from many countries
around the world through their valuable comments towards the development of SIDRA SOLUTIONS
software products.

IMPORTANT

User Guides and training manuals for SIDRA SOLUTIONS software products are RESTRICTED
DOCUMENTS for use under software licence only. These documents may not be placed in any public
library, may not be rented, loaned or distributed by any means. They are under the COPYRIGHT of
Akcelik and Associates Pty Ltd and may only be reproduced with written permission.
SIDRA TRIP User Guide 3.1

3. INPUT
This section discusses general aspects of SIDRA TRIP input (Section 3.1), presents detailed
description of data specification in individual input (Edit Profile) dialogs (Sections 3.2 to 3.9), and
explains the Diagnostics facility (Section 3.10).

3.1 GENERAL ASPECTS OF SIDRA TRIP INPUT

Edit Profile Dialog for Input
The node called Edit Profile in the Input group of the Profile Tree is used for input data
specification (see Figure 3.1). To edit input data, double-click the Edit Profile node. Detailed
information on the SIDRA TRIP user interface is given in Section 2.3.
When you use Tools - Edit Profile, the nodes displaying various settings will be seen in the
Input Data Tree Pane on the left-hand side of the dialog (Figure 3.1). To open a display, click
the node in the Input Data Tree. The input values of settings for the selected node will be seen on
the right-hand side of the dialog.

Double click the Edit Profile node in the

Profile Tree to open the input dialog

Click the desired node in the

Input Data Tree to access
Input Data the input data fields
Tree Pane

Figure 3.1 - Edit Profile dialog for input

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.2 Akcelik & Associates Pty Ltd

When you save the input changes you made in the Edit Profile dialog by clicking the OK button,
any existing output will be discarded, the new data will be processed, and new output will be
generated automatically. The Input Report provides a summary of input data given in the Edit
Profile dialog. You can specify more commonly used parameter values in Defaults dialog (Tools -
Defaults).

Methods to Describe Trip Profiles

Trip data representing a vehicle movement for SIDRA TRIP can be in the form of:
 microscopic (second-by-second) trip data from an instrumented car, for example, data
collected using a Global Positioning System (GPS) data logger using a variety of data file
formats, namely CSV (comma-separated values), Text (tab-separated), NMEA Text, GPS
Exchange, Track and Garmin Database formats (see Section 3.3.3), or
 trip data formed by the user in drive-cycle format simply by specifying initial and final
speeds to represent vehicle idling, cruise, acceleration and deceleration manoeuvres with
markers representing "traffic events".
The first data format is referred to as travel-based trip profile, and the second format is called the
event-based trip profile. The corresponding input methods are referred to as the Travel Data
Method and Event Data Method, respectively.
Microscopic (second-by-second) trip data representing standard vehicle drive cycles can also be
used as travel-based trip profiles.
You cannot convert a travel-based trip profile to an event-based trip profile. You can use File -
Save Trip Data As to export data from a travel-based or event-based trip profile contained in the
Profile (.aam) file to a raw (source) data file in CSV, Text, GPS Exchange, or Track format as
applicable (see Section 3.3.3). You can then import the data after creating a new travel-based trip
profile using File - New.

Data Method Dialog

In the SIDRA TRIP main menu, select File - New to create a new Profile, File - Open to open an
existing Profile, or File - Save As to create a new Profile by making a copy of the current Profile.
When you choose File - New to create a new Profile, the Data Method dialog will appear
(Figure 3.2). You must choose one of the two following data methods:
 Travel Data Method: Choose this option to create a travel-based trip profile if you have a
file containing a series of time points along with associated speeds, distances and/or
coordinates, e.g. based on data obtained using a GPS data logger.
 Event Data Method: Choose this option to create an event-based trip profile by specifying
initial and final speeds and markers that describe "events". SIDRA TRIP will determine
acceleration and deceleration profiles for speed-change manoeuvres.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.3

Figure 3.2 - Data Method dialog

Edit Profile Dialog

After you choose the data method you wish to use, the Edit Profile dialog will appear for
specification of input data for the new Profile (see Figure 3.1).
When you use File - Open to open an existing Profile, or when you use File - Save As to create
a new Profile from an existing file, and double-click the Edit Profile node in the Profile Tree, the
Edit Profile dialog will be opened for editing input data.
The left-hand side of the Edit Profile dialog contains the Input Data Tree. Click the desired node
in the tree to access the input data fields. As seen in Figure 3.1, the Input Data Tree presents the
following input groups:
 General Settings
 Trip Data
 Speed Settings
 Noise Settings
 Cost & LOS Parameters
 Vehicles
 Drivers (Event Data method only).
Contents of each input data group differ according to the data method. The Drivers data group is
not available in the case of Travel Data method since driver characteristics are inherent to the data
collected using an instrumented vehicle.
The name of the Edit Profile dialog box (top left corner) will include the name of the data method
used as well as the name of selected input node in brackets, e.g. Edit Profile - Travel Data
Method (General Settings). In this guide, specific aspects of the dialog will be referred to using
the name of the node only, e.g. General Settings input dialog.
Input data specification in individual dialogs listed above is explained in Sections 3.2 to 3.9, and
the Diagnostics facility is explained in Section 3.10.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.4 Akcelik & Associates Pty Ltd

3.2 GENERAL SETTINGS

The General Settings input dialog (Figures 3.3a and 3.3b) allows you to:
 type text in the Title, Subtitle and Description data fields (Title and Subtitle will appear
in text output),
 select a Vehicle from the Default and User-Specified vehicles using a drop-down list,
 select a Driver from the Default and User-Specified drivers using a drop-down list
(if using the Event Data method), or enter a Driver ID (if using the Travel Data method),
 specify the Number of Vehicle Trips for calculating Sums for a number of trips (or a
number of vehicles),
 specify a Trip Time (if using the Event Data method),
 specify a Trip ID (intention is a short identifier; use Title and Subtitle lines for longer
headers in text output), and
 select the Start Section and End Section from drop-down lists to define the section of trip
to be analysed using the markers defined in the Trip Data input dialog (if using the Travel
Data method).

Start Section and End Section data

fields are used in the case of
Travel Data method only.

Figure 3.3a - General Settings input dialog for Travel Data method

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.5

Trip Time data field is used

in the case of the Event Data
method only.

Figure 3.3b - General Settings input dialog for Event Data method

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.6 Akcelik & Associates Pty Ltd

3.3 TRIP DATA USING TRAVEL DATA METHOD

The Trip Data input dialog is used to specify data that describe the vehicle movement. The Trip
Data input dialog is very different for the Travel Data and Event Data methods (Section 3.1). The
Travel Data Method is explained in this section. The Event Data Method is explained in
Section 3.4.

3.3.1 Importing Trip Data

The Travel Data method uses microscopic (second-by-second) trip data from an instrumented car,
for example, data collected using a GPS data logger.
When you create a new Profile using the Travel Data method, and click or right click the Trip
Data node in the Input Data Tree on the left-hand side of the Edit Profile dialog, the Trip Data
input dialog shown in Figure 3.4a will be displayed. At this stage the Profile is empty.
Click the Import Trip Data button at the bottom of the input dialog, or select the Import Trip
Data option in the right-click menu opened when you right-click the Trip Data node in the Input
Data Tree. The Open Source Data File dialog will appear (see Figure 3.4b). The available source
data file types are CSV (*.csv), Text (*.txt), NMEA Text (*.txt), GPS Exchange (*.gpx), Track
(*.trk), and Garmin Database v 1.0/2.0 (*.gdb). Select the desired data file type, and then select
the file to open, and click Open.
Although the NMEA Text (GPS-standard) files and the general (tab-separated) Text files have the
same (txt) extension, the contents of these file types are very different. When you choose one of
these file types, all data files with txt extension (i.e. files of both types) will be presented in the
Open Source Data file dialog. SIDRA TRIP will identify the NMEA file type according to the
contents of the file. The source data file formats are discussed in more detail in Section 3.3.3.
In the case of GPS Exchange and Garmin Database files, the Select Track dialog will appear for
selection of a data track (see Figure 3.4c).
After you click Open in the Open Source Data File dialog, the data will be imported and displayed
in a grid in the Trip Data input dialog (see Figure 3.5d). The data shown will depend on the
contents of the source data file. The import process must result in at least five rows of data in the
Trip Data input dialog for the process to be successful.
Source Data Units for Speed and Distance (top left corner of the Trip Data input dialog) are used
to specify the units used for data shown in the grid. In the case of source data files in CSV (*.csv)
or Text (*.txt) format, you need to specify the Source Data Units that match the units used in the
source data file. On the other hand, in the case of source data files in NMEA Text (*.txt), GPS
Exchange (*.gpx), Track (*.trk), and Garmin Database v 1.0/2.0 (*.gdb) formats, the program
will determine the units used in the source data file and convert them to match the Source Data
Units specified by the user before importing trip data. Once data appear in the grid, you can no
longer change the Source Data Units.
The units of the data imported can be different from the units selected in Tools - Defaults (Current
Defaults System), which is shown in the Trip Data input dialog. However, irrespective of the units
of the imported data, the simulation will be performed and output will be generated in units
selected for the Current Defaults System at the time the Profile was created.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.7

Units of
Defaults
System
(set in
Tools -
Choose the Units Time Zone Defaults)
of trip data to be Adjustment
imported (these (the
can be different preferred
from the Units of method
the Defaults specified in
Click to import trip System)
data from external Tools -
(source) data file Options)

Figure 3.4a - Trip Data input dialog for Travel Data method (before importing data)

Figure 3.4b - Open Source Data File dialog (file types shown))

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.8 Akcelik & Associates Pty Ltd

Figure 3.4c - Select Track dialog

Right click for data

editing functions

Choose the type of data

to use for simulation

Figure 3.4d - Trip Data input dialog for Travel Data method (after importing data)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.9

The units selected for Distance will also apply to the Altitude data. However, when the unit
selected for Distance is km or mi, the unit to be used for Altitude will be metres or feet,
respectively.
You also need to select the type of data (Speed, Distance or Coordinates) to be used for
simulation according to the data available. The choice of one of these options is needed due to the
relationships between these parameters.
The use of the Speed option is recommended when speed data are available since speed is the key
parameter determining vehicle movement in simulation. When the Distance option is used, SIDRA
TRIP will determine the speed to be used as a basis of simulation. When the Coordinates option is
used, SIDRA TRIP will determine the distance from the coordinates, and then calculate speed from
the distance. When the Distance or Coordinates option is used, the imported data seen in the Speed
column of Trip Data input dialog remains unchanged, and is not used in simulation.
If you wish to analyse a subset of data, define the sections to be analysed by specifying the start
and end points using markers (any text) given in the Location column (optional).
You can use the right mouse button to access the functions for editing data (Delete Row, Insert
Row, Copy Row, Paste Row) as seen in Figure 3.4d. When there are data rows that seem to be
problematic, you can edit the data or use the Delete Row function. You can delete multiple rows of
data.
If SIDRA TRIP identifies problems with data quality, a Diagnostics node will appear in the Profile
Tree and the Diagnostics text window will be opened automatically after data processing is
complete. You can inspect the window for messages about the problems and take corrective action
in the Trip Data dialog accordingly.
Click OK when the data is ready. The data will be processed (i.e. simulation will be carried out),
and several output windows will be opened according to the Options settings, automatically. When
you click OK, the Importing Trip Data dialog may appear indicating the progress of data
processing. With large data files, this process may take a long time.
Parameter values imported from a data file or computed by SIDRA TRIP as applicable (e.g. speed
values from distance data, or distance values from speed data) are stored with up to 7 decimal
places accuracy (rounded up).

3.3.2 Conversion of Units Used in Data File

You can convert a Travel Data Profile between Metric and US Customary Units by using File -
Save Trip Data As and export the trip data as a source data file in CSV (*.csv) or Text (*.txt)
format. The exported data will be saved using the units of the Current Defaults System. Use
Tools - Defaults, and select Current Defaults System to set units to Metric or US Customary as
desired before exporting the data. Thus, if the simulated data is in Metric units and the Current
Defaults System is in US Customary units, or vice versa, the units will be converted before being
saved in the source data file as appropriate.
The exported data will be in units of:
 km/h for Speed and metres for Distance when the Defaults System is in Metric Units, and
 mph for Speed and feet for Distance when the Defaults System is in US Customary Units.
The next step is to create a new Travel Data Profile using File - New, and import the source data
file (CSV or Text) exported previously. Make sure that you specify the Source Data Units (Speed
and Distance) to match the data to be imported since the units of the imported data will be
determined in accordance with the Source Data Units settings. Irrespective of the units of the

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.10 Akcelik & Associates Pty Ltd

imported data, the simulation will be performed and output will be generated in units of the Current
Defaults System.
You cannot directly convert an Event Data Profile between Metric and US Customary Units.
However, you can export the trip data created in the Event Data Profile to a source data file in CSV
(*.csv ) or Text (*.txt) format, and then import the data as a Travel Data Profile using the above
procedure.

3.3.3 Source Data File Formats

The following data file formats can be imported by SIDRA TRIP:
 CSV (comma-separated values) file (csv),
 Text (tab-separated text) file (txt),
 NMEA Text (GPS-standard) file (txt),
 GPS Exchange file (gpx), and
 Track file (trk).
 Garmin Database v 1.0/2.0 file (gdb).
For the CSV and Text (tab-separated) file formats, source data files need to be prepared by the user
with parameters given in the order shown in Example 1 in Figures 3.5a and 3.5b. The Units in
these examples are km/h for Speed and metres for Distance.
Note the following about the CSV and Text (tab-separated) file formats:
 These files can include initial descriptive comment lines starting with the # symbol, which
will be ignored during the import process.
 It is not necessary to include all parameters (i.e. some may be left blank). The Time Step
(if Date and Time data not given) and Speed (or Distance) parameters are essential. An
example is given in Example 2 in Figures 3.5c and 3.5d, where only the Time Step, Speed
and Distance data are given.
NMEA Text (*.txt) files use a standard format many GPS devices can produce. They contain most
of the information that can be imported by SIDRA TRIP readily, i.e. the NMEA Text format is
recognized by SIDRA TRIP and converted to the required trip data format automatically.
NMEA Text format is defined by the US National Maritime Electronics Association
(www.nmea.org). A NMEA file is a comma-separated text file with one or more NMEA records
for each time step (typically each second). All NMEA records start with $GP and ends with a
checksum starting with a star (*). The NMEA file contains the following NMEA records for each
time step:
 $GPRMC: Recommended minimum specific GPS data,
 $GPGGA: Global positioning system fix data,
 $GPGSA: GPS DOP (dilution of precision) and active satellites, and
 $GPGSV: GPS Satellites in view (data for up to 4 satellites per GSV line)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.11

#TimeStep,Speed(km/h),Distance(m),Grade,Date,Time,Latitude,Longitude,Altitude,Heading,Location
1,35.2,9.7,1.8,20051128,084931,-37.951389,145.077083,41.2,9.3,Greythorn Rd
2,29.6,17.8,1.7,20051128,084932,-37.951306,145.077083,41.5,9.6,
3,26.2,24.4,1.2,20051128,084933,-37.951222,145.077111,41.8,9.5,
4,19.7,29.7,1.7,20051128,084934,-37.951167,145.077111,42.3,10.1,
5,12.4,33.1,0.6,20051128,084935,-37.951111,145.077139,42.5,9.8,

Figure 3.5a - Trip Data: CSV (comma-separated values) file format (Example 1)

#TimeStep Speed(km/h) Distance(m) Grade Date Time Latitude Longitude Altitude Heading Location
1 35.2 9.7 1.8 20051128 084931 -37.951389 145.077083 41.2 9.3 Greythorn Rd
2 29.6 17.8 1.7 20051128 084932 -37.951306 145.077083 41.5 9.6
3 26.2 24.4 1.2 20051128 084933 -37.951222 145.077111 41.8 9.5
4 19.7 29.7 1.7 20051128 084934 -37.951167 145.077111 42.3 10.1
5 12.4 33.1 0.6 20051128 084935 -37.951111 145.077139 42.5 9.8

Figure 3.5b - Trip Data: Text (tab-separated) file format (Example 1)

#TimeStep,Speed(km/h),Distance(m),Grade,Date,Time,Latitude,Longitude,Altitude,Heading,Location
1,35.2,9.7,,,,,,,,,,Greythorn Rd
2,29.6,17.8,,,,,,,,
3,26.2,24.4,,,,,,,,
4,19.7,29.7,,,,,,,,
5,12.4,33.1, ,,,,,,,,

Figure 3.5c - Trip Data: CSV (comma-separated values) file format (Example 2)

#TimeStep Speed(km/h) Distance(m)

1 35.2 9.7
2 29.6 17.8
3 26.2 24.4
4 19.7 29.7
5 12.4 33.1

Figure 3.5d - Trip Data: Text (tab-separated) file format (Example 2)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.12 Akcelik & Associates Pty Ltd

$GPRMC,214701,A,3757.6004,S,14504.3621,E,021.3,100.4,190306,011.8,E*6C
$GPGGA,214701,3757.6004,S,14504.3621,E,1,08,1.1,35.0,M,-1.4,M,,*7E
$GPGSA,A,3,01,,11,13,16,20,23,24,25,,,,2.2,1.1,2.0*36
$GPGSV,3,1,09,01,32,116,51,04,02,212,00,11,26,328,47,13,20,265,44*78
$GPGSV,3,2,09,16,27,056,50,20,78,218,48,23,51,245,50,24,31,242,47*7F
$GPGSV,3,3,09,25,46,131,51*42
$GPRMC,214702,A,3757.6014,S,14504.3697,E,021.9,099.5,190306,011.8,E*69
$GPGGA,214702,3757.6014,S,14504.3697,E,1,08,1.1,34.9,M,-1.4,M,,*79
$GPGSA,A,3,01,,11,13,16,20,23,24,25,,,,2.2,1.1,2.0*36
$GPGSV,3,1,09,01,32,116,52,04,02,212,00,11,26,328,47,13,20,265,44*7B
$GPGSV,3,2,09,16,27,056,50,20,78,218,48,23,51,245,50,24,31,242,47*7F
$GPGSV,3,3,09,25,46,131,51*42

Figure 3.5e - Trip Data: NMEA Text (txt) file format

(bold values shown in Table 3.1)

Table 3.1
Parameters in NMEA records

Parameter Format Comment NMEA Example in

Record Figure 3.5e
Latitude Real DDMM.mmmm N/S RMC, GGA 3757.6004 S
Longitude Real DDMM.mmmm W/E RMC, GGA 14504.3621 E
Altitude Real Metres GGA 35.0
Speed Real Knots (nm/h, multiply by 1.852 to get km/h) RMC 21.3
Heading Real Degrees, 0 = North, clockwise RMC 100.4
Date Integer DDMMYY RMC 190306
Time Integer HHMMSS RMC, GGA 214701
HDOP Real Horizontal dilution of precision (x,y) GSA, GGA 1.1
VDOP Real Vertical dilution of precision (z) GSA 2.0
PDOP Real Point dilution of precision (x,y,z) GSA 2.2
NSatUsed Integer Number of satellites used to fix position GGA 8
NSatView Integer Number of satellites in view GSV 9
Valid fix Integer 0-invalid fix, 1-valid fix, 2-8-special GGA7 1
2D/3D fix Integer 1-no fix, 2-2D fix, 3-3D fix GSA3 3

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.13

An example of NMEA Text format is given in Figure 3.5e. The most relevant information from
NMEA records is summarised in Table 3.1 (with parameter values for the example shown in
Figure 3.5e shown in the last column).
When importing from the NMEA Text data files, SIDRA TRIP determines the horizontal and
vertical accuracy index (HAI, VAI) values for each time step according to the number of satellites
available at the time data were recorded. These values are kept in the SIDRA TRIP Profile (aam)
file but they are not displayed in the Trip Data input dialog. The Trip Statistics output will include
average values of HAI and VAI for the trip (or section of a trip as applicable) in the case of NMEA
text data. The index values are in the range 1 to 5 (1: Very Poor, 5: Very Good).
A GPS Exchange(www.topografix.com/gpx.asp) file is an XML based text file with information
for each point along the track (see Figures 3.5f). A Track file is a semicolon -separated text file
with information for each point along the track (see Figures 3.5g). The file can be imported to
Excel or similar programs.
The date and time value in the Track format (e.g. 1142649491 in Figure 3.5g) can be decoded by
dividing the value by 86400. The resulting whole number is the number of days since 1/1/1970 and
the remainder is the number of seconds since midnight:
 Date: Int (1142649491/86400) = 13225 days since 01/01/1970 = 18/03/2006
 Time: Mod (1142649491, 86400) = 9491 seconds since midnight = 02:38:11 AM

<?xml version="1.0"?>
<gpx
version = "1.0"
creator = "GPS Tuner 4.0 - http://www.gpstuner.com"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns = "http://www.topografix.com/GPX/1/0"
xsi:schemaLocation = "http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd">
<time>2006-03-18T13:35:22Z</time>
<bounds minlat="-37.9667333333333" minlon="145.05493" maxlat="-37.7899183333333"
maxlon="145.101496666667"/>
<trk>
<trkseg>
<trkpt lat="-37.7910366666667" lon="145.093976666667"> Latitude and Longitude (decimal degrees)
<ele>58.2</ele> Altitude (m)
<time>2006-03-17T07:05:35Z</time> Date and Time (YYYY-MM-DD & HH:MM:SS)
<speed>0.308666666666667</speed> Speed (m/s)
<type>Trackpoint</type>
</trkpt>
<trkpt lat="-37.7910383333333" lon="145.094">
<ele>58.7</ele>
<time>2006-03-17T07:05:36Z</time>
<speed>0.514444444444444</speed>
<type>Trackpoint</type>
</trkpt>
<trkpt lat="-37.7910383333333" lon="145.093988333333">
<ele>58.9</ele>
<time>2006-03-17T07:05:37Z</time>
<speed>0.977444444444444</speed>
<type>Trackpoint</type>
</trkpt>

Figure 3.5f - Trip Data: GPX Exchange (gpx) file format

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.14 Akcelik & Associates Pty Ltd

GPS Tracklog (Time Interval)

Latitude;Longitude;Altitude(m);Speed(km/h);DateandTime (Latitude and Longitude in decimal degrees)
-37.9637466666667;145.065375;37.7;1.2964;1142649491;1
-37.9637533333333;145.065375;37.8;2.5928;1142649492;0
-37.9637616666667;145.065373333333;37.9;3.704;1142649493;0
-37.9637883333333;145.065368333333;38.1;6.6672;1142649495;0
-37.963815;145.065361666667;38.1;11.2972;1142649496;0
-37.9638533333333;145.06535;38.2;15.5568;1142649497;0
-37.9638983333333;145.065336666667;38.1;18.52;1142649498;0
-37.9639466666667;145.065321666667;38;19.446;1142649499;0
-37.963995;145.065306666667;37.8;19.6312;1142649500;0

Figure 3.5g - Trip Data: Track (trk) file format

Garmin (www.garmin.com) uses a Garmin Database (gdb) format for Garmin GPS units, and the
MapSource software for data transfer and communication. SIDRA TRIP can read directly form
Garmin Database version 1.0 and 2.0 files.

3.3.4 Parameters in the Trip Data Input Dialog

The input data parameters in the Trip Data input dialog are explained below.

Time Step
Time Step is the number of seconds elapsed since the start of the trip. The size of the time step
(Data Time Interval) is automatically calculated based on the most common interval in the source
data. The Data Time Interval determined by the program is given in the Trip Data Settings
section of Trip Statistics output.
SIDRA TRIP makes allowance for missing steps by linear interpolation. This can be seen as linear
sections in the Speed - Time graph generated as output.
The first Time Step value should be zero, and the subsequent Time Step values represent
cumulative trip time since the start of the trip. If the initial step has a Time Step value larger than
zero (due to the use of a section of a trip), all Time Step values are normalised with the first Time
Step value set to zero. The normalised Time Step values will be saved (overwrite the original
values). These can be seen in the Trip Data input dialog next time it is opened.
If Date and Time data are specified, the Time Step value will be determined from these parameters
and the value in the Time Step column will be overwritten (valid for all data file formats). Time
Step is required if Date and Time parameters are not given.
All data values as used in simulation can be seen by exporting the simulation data using File - Save
Trip Data As (in csv or txt format) or File - Save Sim Data As (in csv, txt or xml format).

Speed
Speed is an instantaneous speed value for a given Time Step (in kilometres per hour, metres per
second, miles per hour or feet per second, as specified for the source data in the Trip Data input
dialog). Speed data are required if you wish to perform the simulation using the Speed Data
option. If you choose the Distance Data or Coordinates option, speed is calculated from Distance
or Coordinates for use in simulation. During simulation, the distance travelled is always
determined by the speed used in simulation (hence it may differ from the distance values given in
the Trip Data input dialog). The original speed data are kept in the Profile when the Speeds are
calculated from Distance or Coordinates Data.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.15

Distance
Distance is the cumulative distance travelled since the start of the trip (in metres, kilometres, feet
or miles, as specified for the source data in the Trip Data input dialog). If the analysis is performed
using the Distance Data option and the initial Distance value is not zero (e.g. when an initial
section of data is deleted), the simulated Distance values are normalised with the first Distance
value set to zero. The original Distance data are kept in the Profile.

Grade
Grade is specified as a percentage value. This represents the slope of the road in the direction of
travel (positive for uphill grade, negative for downhill grade, zero for level road) as seen in
Figure 3.6.
Grade influences instantaneous tractive force, energy and power values, and therefore fuel
consumption, emissions and cost estimates. If Grade data are not given, level road is assumed.
In Tools - Options - Settings, the following options are available for calculating Grade data from
Altitude data (if available) for each Time Step during import:
 Never
 If Grade Data not given
 Always
If the Altitude data are reliable, SIDRA TRIP can calculate plausible grade values.

Downhill:
G<0
Uphill:
G>0

Figure 3.6 - The Grade definition in SIDRA TRIP

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.16 Akcelik & Associates Pty Ltd

Date and Time

Date and Time are obtained from the GPS device. For CSV and Text (tab-separated) file formats:
 Date may be specified in YYYY-MM-DD or DD-MM-YYYY format (using a dash, slash
or dot as a separator). Leading zeros are optional.
 Time must be specified in HH:MM:SS format (using a colon or dot as a separator).
 Date and Time formats with no separators (YYYYMMDD, HHMMSS) are also
acceptable.
For NMEA Text and Track formats, internal date formats are used. Date and Time code in the
Track format is specified in the number of seconds since 1 January 1970 (see Section 3.3.3).
The GPS Exchange format uses the YYYY-MM-DDTHH:MM:SS format only, where "T" is a
literal T that must occur, e.g. 2006-01-29T21:39:24, which is the standard way of showing dates
and times in XML-based files.
The date format MM-DD-YYYY is not supported.
If both a Time Step and the Date and Time are specified, the Time Step will be recalculated from
the Date and Time.
Time Zone Adjustment: Date and Time values in CSV (*.csv) or Text (*.txt) formats are imported
without any adjustment. Date and Time values in NMEA Text (*.txt), GPS Exchange (*.gpx),
Track (*.trk), and Garmin Database v 1.0/2.0 (*.gdb) formats are stored in UTC format. During
trip data import, these may be converted to the current time zone and daylight saving time settings.
In Tools - Options - Settings, various options are available for the method to be used for Time
Zone Adjustment:
 No Time Zone Adjustment: Date and Time values in the source data file are imported
without any adjustment;
 Adjust to Current Time Zone (default option): Date and Time values are converted to the
current time zone according to the Date and Time settings of your computer, including the
daylight saving time settings;
 Adjust to Specified Time Zone: Date and Time values are adjusted using a specified
value.
When trip data are imported from a source data file created in another time zone or before a change
to or from daylight saving time, the imported Date and Time values may be wrong when the
Adjust to Current Time Zone method is used. The option Adjust to Specified Time Zone can
be used in such cases.

Latitude and Longitude

Latitude and Longitude (Coordinates) are optional unless you wish to perform the simulation
using the Coordinates option. Note that unless you have high-precision data, an analysis based on
coordinates will not be reliable.
Coordinates are specified as decimal degrees. SIDRA TRIP also supports the format
DDDMM.mmm… where DDD is degrees, MM is minutes, and mmm… is decimal minutes, hence
147o 31.842' is formatted as 14731.842. This format should be used with care. This is equivalent
to 147.5307 in decimal degrees.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.17

Altitude
Altitude (elevation) data are used for calculating approximate grade values when Grade data are
not given. This is subject to the option selected under "Calculate Grade data from Altitude data
if available during import" in Tools - Options - Settings (options available are Never, If Grade
Data not given, Always). No smoothing is performed in grade calculations, so the resulting grade
values may not be reliable.
The units for Altitude data are based on those used for Distance data but only metres and feet are
applicable (metres if Distance data are in metres or kilometres, and feet if Distance data are in feet
or miles).

Location
Location provides a way to specify markers for defining sections of a trip. The location markers
are specified in free-form text format. These are shown in the Start Section and End Section
drop-down lists in the General Settings input dialog. Duplicate location marker descriptions are
allowed.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.18 Akcelik & Associates Pty Ltd

3.4 TRIP DATA USING EVENT DATA METHOD

The Event Data method uses trip data defined by the user in drive-cycle format simply by
specifying initial and final speeds to represent vehicle idling, cruise, acceleration and
deceleration manoeuvres with markers representing traffic events.

3.4.1 Specifying Event Data

When you create a new Profile using the Event Data method, and click the Trip Data node in the
Input Data Tree on the left-hand side of the Edit Profile dialog, the Trip Data input dialog will be
opened. At this stage the Profile will have Event Group 1 and Event 1 created automatically.
These will be seen under the Trip Data node in the Input Data Tree. Figure 3.7a shows an Event
Group with more Events specified by the user. This view is obtained when the Event Group node
is clicked. Figure 3.7b shows the view when the Event 2 node is clicked for the same example.
You can right-click the Event Group node in the Input Data Tree, or click the buttons at the
bottom of the dialog (see Figure 3.7a), and choose:
 Add Event Group to add an Event Group with a single Event (added after the last Event
Group);
 Clone Event Group (make a copy of the selected Event Group and add after the last
Event Group);
 Delete Event Group (delete the selected Event Group); or
 Add Event (add new Event at the end of the selected Event Group).
You can right-click any Event node in the Input Data Tree, or click the buttons at the bottom of the
dialog (see Figure 3.7b), to choose:
 Add Event (add new Event at the end of Event Group);
 Insert Event (add new Event after the selected Event), or
 Delete Event (delete the selected Event).
The data that can be specified in the Trip Data input dialog for Event Data method include the
following:
 Event Data:
o Initial Speed (km/h or mph)
o Final Speed (km/h or mph)
o Grade (percent)
o Event Duration (s) / Distance (m or ft)
 Marker Data:
o Marker Type (drop-down list)
o Setback Distance (m or ft)
 Loop Data:
o Check box (click the check box for other data fields to be accessible)
o Length (m or ft)
o Setback Distance (m or ft)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.19

Right click for

Event Group
functions

Figure 3.7a - Trip Data input dialog - Event Group for Event Data method
(for "Event Group 1" in this example)

Right click for

Event functions

Figure 3.7b - Trip Data input dialog - Event for Event Data method
(for "Event 2" in this example)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.20 Akcelik & Associates Pty Ltd

3.4.2 Initial and Final Speeds

You need to specify an Initial Speed and a Final Speed for the first Event of the trip. For all
subsequent Events, the Initial Speed is set equal to the Final Speed of the previous Event
automatically. When you change the Final Speed of an Event, the Initial Speed of the next Event
will be set equal to it automatically.
When you Add or Insert an Event, or when you Add or Clone an Event Group, the Initial and Final
Speed adjustments will be made automatically:
 When the Add Event function is used, a new Event is added to the end of the Event Group.
The Initial Speed of the new Event is set equal to the Final Speed of the last Event in the
group, and the Final Speed of the new Event is set equal to the Final speed of the Event
that was selected when Add Event function was used.
 When the Insert Event function is used, a new Event is added immediately after the
selected Event. The Initial and Final Speeds of the new Event are both set equal to the
Final speed of the previous Event.
 When the Add Event Group function is used, the Initial and Final Speeds of the first
Event in the new Event Group are set equal to the Final Speed of the last Event in the
previous Event Group.
 When the Clone Event Group function is used, the Initial Speed of the first Event in the
new Event Group is set equal to the Final Speed of the last Event in the previous Event
Group.

3.4.3 Event Type

An Event Type is determined automatically according to the Initial and Final Speed values.
Possible Event Types are:
 Cruise / Idle if the Final Speed equals the Initial Speed (Cruise if the speed is greater than
zero, Idle if the speed if zero), and
 Speed Change if the Final Speed is greater than the Initial Speed (Acceleration) or if the
Final Speed is less than the Initial Speed (Deceleration).

3.4.4 Event Markers

Event Marker Types

The following Marker Types are available in the drop-down list:
 None
 Give-Way / Yield Sign
 Pedestrian Crossing
 Roundabout

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.21

 Speed hump
 Stop Sign
 Traffic Signals
The markers are displayed with graphical symbols indicating locations during animation.

Event Marker Location

Event Marker location (position) is specified using the Setback Distance parameter. The Setback
Distance is measured back from the location reached by the vehicle at the end of the current Event
(see Figure 3.8). The default value of Event Marker Setback Distance is zero. Marker locations
are calculated using simulated distance values.
If the current Event is idling (zero speed), the distance to the end of the Event is the same as the
distance at the end of the previous Event. If the first Event is idling, the position of the vehicle at
the end of this event is still as at the start of the trip (zero distance travelled). The Setback Distance
in this case should be zero only. There are no other restrictions on the Marker Setback Distance, so
the Marker location may be within previous Event distance areas.

Marker
Setback
Start of Current distance, Ls
trip Event

Event
distance, Le

Distance to the end of Marker

current Event location

Figure 3.8 - Event Marker location

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.22 Akcelik & Associates Pty Ltd

3.4.5 Loops
Detector loops can be specified to simulate vehicle detection by presence detectors. Default values
of loop data are:
 Loop Length: 4.5 m or 15 ft
 Loop Setback Distance: 1.5 m or 5 ft
Loop location is determined using the Setback Distance parameter in the same way as the method
used for Event Markers. The Setback Distance is measured back from the location reached at the
end of the current Event (see Figure 3.9). This determines the position of the downstream edge of
the loop.

Loop
length Setback
Start of
Current distance
trip
Event

Event distance

Distance to the end of

current Event
Loop
location

Figure 3.9 - Loop location

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.23

3.5 SPEED SETTINGS

The Speed Settings input dialog (Figure 3.10) allows you to specify the following speed
parameters (km/h or mph).
 Desired Speed: Click the check box if you want to specify a desired speed, otherwise the
program will determine the desired Speed automatically.
 Lower Speed for a Stop and Upper Speed for a Stop:
o for a stop to be counted, the vehicle must cross the speed band defined by these
two speeds during deceleration from a speed above the Upper Speed to a speed
below the Lower Speed, and
o for a subsequent stop to be counted, the vehicle must first cross the speed band
during acceleration to a speed above the Upper Speed and then must decelerate to a
speed below the Lower Speed.
 Speed Groups: Click the check boxes and type the desired upper speed values to define
speed ranges for the trip time spent and the percentage value of travel in each speed group
to be given in Trip Statistics output.
When the program determines the desired Speed, it is rounded to the nearest 5 km/h or 5 mph.
Speeds less than 5 km/h or 5 mph are rounded to 5 km/h or 5 mph.

Click to specify Desired

Speed (rather than
automatic determination
by the program)

Click and enter

values to modify the
Speed Groups

Figure 3.10 - Speed Settings input dialog

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.24 Akcelik & Associates Pty Ltd

3.6 NOISE SETTINGS

SIDRA TRIP estimates noise levels (dBA) generated during the trip using three different models:
 ASJ 2003 (Japanese) Model
 SonRoad (Swiss) Model, and
 RLS-90 (German) Model.
The models to be used for generating noise graphs (showing instantaneous values of noise levels)
and various noise statistics in text output windows can be specified using check boxes in Tools -
Options - Output.
For each model, noise levels received at a Fixed Receptor point and at a Relative Receptor point
are simulated. The Fixed Receptor is at a fixed location defined with reference to the start of the
trip. The Relative Receptor is at a constant distance from the vehicle, and moves with the vehicle.
The Noise Settings input dialog (Figure 3.11) allows specification of the following parameters:
 Flow Rate (veh/h): used for estimating an Average Equivalent Noise Level (LeqT) for a
traffic stream.

Specify Flow
Rate for Average
Equivalent Noise
Level (LeqT)
calculation

Specify fixed
Receptor point
Coordinates method
not available for
Event Data method

Figure 3.11 - Noise Settings input dialog

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.25

 Fixed Receptor location:

o Distance from the Start of Trip (m or ft), or
o Coordinates (this option is not available in the case of the Event Data method, and
available in the case of Travel Data method only when Coordinates are being used
to perform the simulation).
 Relative Receptor location: Distance between Source (vehicle) and Receptor (m or ft).
 Heights:
o Height of Source above Ground (m or ft), and
o Height of Receptor above Ground (m or ft).
According to the average headway, h = 3600 / q (seconds) corresponding to the Flow Rate,
q (veh/h) specified, the Fixed Receptor point may be determined by the program if the Fixed
Receptor distance is specified as zero (default) or the distance exceeds the total trip distance.
General information about noise modelling is given is given in Section 4.4.6.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.26 Akcelik & Associates Pty Ltd

3.7 COST & LOS PARAMETERS

The Cost & LOS Parameters input dialog allows you to specify various parameters for SIDRA
TRIP to determine the Operating Cost or User Cost statistics for a trip. The Operating Cost is
appropriate for use in traffic management and planning as a cost to the community, and excludes
the tax component of the pump price of fuel. The User Cost is appropriate for use by an individual
or an operating agency as a cost including the total pump price of fuel as well as any toll costs
experienced during the trip.
The Operating Cost and User Cost estimates include:
 the vehicle operating cost (the resource cost or full cost of fuel and additional running costs
including tyre, oil, repair and maintenance as a factor of the cost of fuel), and
 the time cost to driver and passengers.
The Cost & LOS Parameters input dialog (Figure 3.12) allows the user to calibrate the cost model
for local conditions. Calibration parameters include Cost Unit (user’s own currency), Vehicle
Cost Parameters (Pump Price of Fuel, Fuel Resource Cost Factor, Ratio of Running Cost to
Fuel Cost), Time Cost Parameters (Average Income, Time Value Factor, Average
Occupancy), Level of Service Parameters (Lower Limit for Travel Time Ratio) and Cost
Method Parameters (Toll Cost, Cost Method).

Select
Operating Cost
or User Cost

Figure 3.12 - Cost & LOS Parameters input dialog

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.27

The cost model parameters for Australia, New Zealand and USA are given in Table 3.2. The
standard default values of cost model parameters for SIDRA TRIP are the Australian values given
in Table 3.2 for when Metric Units are chosen, and the USA values when US Customary Units are
chosen (the units are chosen in Tools - Defaults).
In the Tools - Defaults - Cost & LOS Parameters dialog, the Cost Unit (e.g. $) is automatically
determined by the Windows regional settings and used as the default value when you create a new
profile. The Cost Unit can be changed in the Cost & LOS Parameters input dialog (Figure 3.2).
You can choose the Cost Method (Operating Cost or User Cost) using the drop-down list in the
Cost Method Parameters group in the Cost & LOS Parameters input dialog, or using Tools -
Defaults - Cost & LOS Parameters. The Toll Cost is added to the total cost when the User Cost
method is selected. For User Cost, fuel resource cost factor = 1.0 is used by the program
automatically, i.e. pump price of fuel applies fully.

Table 3.2
Cost model parameters for SIDRA TRIP

Parameter Symbol Australia New Zealand USA

Cost Unit $ (AUD) $ (NZD) $ (USD)
Parameters for Vehicle Operating Cost (ko)
Pump price of fuel in "Cost Unit" per litre (or (Pp) 1.20 ($/L) 1.60 ($/L) 0.65 ($/L)
per gallon) (2.40 $/gal)
Fuel resource cost factor * (fr) 0.50 0.60 0.70
Running cost/fuel cost ratio (fc) 3.0 2.5 3.0
Parameters for Time Cost (kt)
Average income (full time adult average hourly (W) 28.00 ($/h) 21.00 ($/h) 19.00 ($/h)
total earnings) in "Cost Unit" per hour
Time value factor as a proportion of average (fp) 0.60 0.60 0.40
hourly income
Average occupancy in persons per vehicle (fo) 1.5 1.5 1.2
Calculated Values
Vehicle operating cost factor in "Cost Unit" per (ko = fc fr Pp) 1.800 ($/L) 2.400 ($/L) 1.365 ($/L)
litre (or per gallon) of fuel (5.040 $/gal)
Time cost per person in "Cost Unit" per hour (fp W) 16.80 ($/h) 12.60 ($/h) 7.60 ($/h)
Time cost per vehicle in "Cost Unit" per hour (kt = fo fp W) 25.20 ($/h) 18.90 ($/h) 9.12 ($/h)

* For User Cost, fuel resource cost factor = 1.0 is used.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.28 Akcelik & Associates Pty Ltd

Values calculated for various parameters described below are given in Table 3.2.
Total operating cost, Ct in "Cost Units" (e.g. $), can be calculated from:
Ct = ko Ft / 1000 + kt Tt / 3600 ( 3.7.1 )
where
ko = vehicle operating cost factor (Cost Unit per litre or per gallon of fuel, e.g. $/L or $/gal),
kt = time cost factor ("Cost Unit" per hour, e.g. $/h),
Ft = total fuel consumption (mL), and
Tt = travel time (seconds).
The vehicle operating cost factor, ko in Cost Unit per litre or per gallon of fuel, e.g. $/L or $/gal is
calculated from:
ko = fc fr Pp ( 3.7.2 )
where
fc = an aggregate cost factor used to convert the cost of fuel to total running cost including
tyre, oil, repair and maintenance;
fr = fuel resource cost factor (ratio of the resource price of fuel to the pump price); resource
price is the wholesale price plus retail margin less taxes;
Pp = pump price of fuel in "Cost Unit" per litre (per gallon if US Customary Units are used),
e.g. $/L or $/gal.
The time cost per vehicle, kt in "Cost Unit" per hour, e.g. $/h, is calculated from:
kt = fo fp W ( 3.7.3 )
where
fo = average occupancy in persons per vehicle;
fp = time value factor that converts the average income to a value of time;
W = average income (full time adult average hourly total earnings) in "Cost Unit" per hour,
e.g. $/h.

Level of Service
The default value of the Level of Service (LOS) parameter Lower Limit for Travel Time Ratio
can be specified using Tools - Defaults - Cost & LOS Parameters, or it can be specified for a
specific case in the Cost & LOS Parameters input dialog. Detailed information about the LOS
method for the Level of Service Index used in SIDRA TRIP is described in Section 4.4.1 (Output
Statistics - Trip Assessment).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.29

3.8 VEHICLES
The input dialogs in the Vehicles group of the Input Data Tree (Figure 3.13) are used to specify
data that describe the vehicle characteristics. The title bar of the input dialog gives the name of the
selected Vehicle in brackets.
SIDRA TRIP provides three types (classes) of default vehicles under the Vehicles node in the
Input Tree, namely Passenger Car, Light Vehicle and Heavy Vehicle. Definitions of these
vehicle classes and detailed information about the default vehicle parameters are given in
Section 2.4.1.
The parameter values of default vehicles cannot be changed, and the default vehicles cannot be
deleted from the tree.
You can right-click the Passenger Car, Light Vehicle or Heavy Vehicle node in the Input Tree Pane
and click the Clone Vehicle option, or click the corresponding button at the bottom of the dialog,
to clone the selected vehicle. This will make a copy of the vehicle and paste it under the User node
in the tree. You can specify the parameters of user-specified vehicles to define a particular vehicle
or an aggregate (representative) vehicle type that you may have prepared.

Maximum values
used for
Diagnostics

Fuel Consumption and

Emission Parameters
given in this group are
always in Metric Units
(even when the Current
Defaults System is US
Customary Units)

Figure 3.13 - Vehicles input dialog (for "My Car" in this example)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.30 Akcelik & Associates Pty Ltd

You can right-click the user-specified vehicle node in the Input Data Tree and click the Delete
Vehicle option, or click the corresponding button at the bottom of the dialog, to delete the selected
user-specified vehicle from the tree.
Rather than creating user-specified vehicles in an input dialog for a particular Profile, you can
create such vehicles using Tools - Defaults - Vehicles. These user-specified vehicles as well as the
default vehicles will be available for selection in the General Settings input dialog for all profiles.
SIDRA TRIP allows importing of user-specified vehicles which are included in a Profile when that
Profile is opened. This is optional (use the "Import new Vehicles and Drivers when opening
Profiles" option in Tools - Options - Settings).

3.8.1 Fuel Consumption and Emission Parameters

SIDRA TRIP uses the same power-based model with different parameters for estimating fuel
consumption and emissions of Carbon Monoxide (CO), Hydrocarbons (HC) and Nitrogen Oxides
(NOx) (Bowyer, Akçelik and Biggs 1985, Holyoake 1985, Biggs 1988, Taylor and Young 1996).
Carbon Dioxide (CO2) is estimated directly from fuel consumption by applying a CO 2 factor to the
fuel consumption rate.
Default vehicle parameters for fuel consumption and CO, HC and NOx emission rates are
summarised in Table 3.3. Fuel consumption and emission model parameters are specified in
Metric Units even when the Current Defaults System is US Customary Units (Section 2.4.1).
Some fuel consumption model parameters given in Table 3.3 are based on those reported in
Bowyer, Akçelik and Biggs (1985), and the emission model parameters are based on those derived
by Holyoake (1985). Heavy vehicle parameters represent a mixture of vehicles that use petrol and
diesel fuel (70 per cent diesel use for the selected vehicle composition) as seen in Table 2.2a.in
Section 2.4.3.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.31

Table 3.3
Default vehicle parameters for estimating fuel consumption and various emission rates
(Metric units only)

Unit for Unit for Veh.

Parameter Description Fuel CO HC NOx
Fuel Emissions Class
fi Idling fuel mL/h g/h PC 1300 50 8 2
consumption or
emission rate LV 1350 50 8 2
HV 2000 50 8 2
A Drag fuel mL/km g/km PC 20 1 0 0
consumption or
emission parameter, LV 21 1 0 0
mainly related to
rolling resistance HV 100 1 0 0

B Drag fuel (mL/km)/ (g/km)/ PC 0.00500 0.0000 0.00002 0.00006

2 2
consumption or (km/h) (km/h)
emission parameter LV 0.00550 0.0000 0.00002 0.00006
mainly related to
aerodynamic drag HV 0.01800 0.0000 0.00002 0.00006

b1 A / (1000 1) kN kN PC 0.2222 0.0667 0.0000 0.0000

LV 0.2333 0.0667 0.0000 0.0000
HV 1.2500 0.0667 0.0000 0.0000
2 2
b2 0.01296 B / 1 kN/(m/s) kN/(m/s) PC 0.00072 0.00000 0.00000 0.00078
LV 0.00079 0.00000 0.00000 0.00078
HV 0.00292 0.00000 0.00000 0.00078

c1 1 b1 mL/m g/m PC 0.020 0.001 0.000 0.000

LV 0.021 0.001 0.000 0.000
HV 0.100 0.001 0.000 0.000

c2 1 b2 mL/m) (g/m) PC 0.0000648 0.000 0.000 0.00000078

2 2
/(m/s) /(m/s)
LV 0.0000713 0.000 0.000 0.00000078
HV 0.0002333 0.000 0.000 0.00000078
1 Efficiency parameter mL/kJ g/kJ PC 0.0900 0.0150 0.0000 0.0010
LV 0.0900 0.0150 0.0000 0.0010
HV 0.0800 0.0150 0.0000 0.0010
2 Energy-acceleration mL/ g/ PC 0.0300 0.0250 0.0004 0.0002
2 2
efficiency parameter (kJ.m/s ) (kJ.m/s )
LV 0.0300 0.0250 0.0004 0.0002
HV 0.0200 0.0250 0.0004 0.0002

PC: Passenger Car, LV: Light Vehicle, HV: Heavy Vehicle

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.32 Akcelik & Associates Pty Ltd

3.8.2 Fuel Consumption Model

The following model is used to estimate the instantaneous fuel consumption rate (mL/s),
representing the fuel consumption rate at any instant during the trip determined as a value per unit
time:
ft = { + 1 RT v + [2 Mv a2 v / 1000]a>0} for RT > 0 ( 3.8.1 )
=  for RT  0
RT = max (0, b1 + b2 v2 + Mv a / 1000 + 9.81 Mv (G/100)/1000) for v > 0 ( 3.8.2 )
= 0 for v = 0
PT = min [Pmax, RT v] ( 3.8.3 )
3
= min [Pmax, max (0, b1 v + b2 v + Mv a v /1000 + 9.81 Mv (G/100) v /1000])
where
ft = instantaneous fuel consumption rate (mL/s),
RT = total tractive force (kilonewtons, kN) required to drive the vehicle, which is the sum of
drag force (first two terms), inertia force (third term) and grade force (fourth term),
PT = total tractive power (kilowatts, kW),
G = road grade (per cent), negative if downhill,
Mv = vehicle mass (kg) including occupants and any other load,
v = instantaneous speed (m/s) = v (km/h) / 3.6
a = instantaneous acceleration rate (m/s2), negative for deceleration,
 = constant idle fuel consumption rate (mL/s), which applies during all modes of driving (as
an estimate of fuel used to maintain engine operation):
 = fi /3600 ( 3.8.4 )
where fi = idle fuel consumption rate in mL/h,
b1 = vehicle parameter related mainly to the rolling resistance (kN):
b1 = A / (1000 1) if 1 > 0 ( 3.8.5a )
=0 if 1 = 0
b2 = vehicle parameters related mainly to the aerodynamic drag (kN/(m/s) 2):
b2 = 0.01296 B / 1 if 1 > 0 ( 3.8.5b )
=0 if 1 = 0
1 = the efficiency parameter which relates fuel consumed to the energy provided by the
engine, i.e. fuel consumption per unit of energy (mL/kJ or g/kJ), and
2 = the efficiency parameter which relates fuel consumed during positive acceleration to the
product of inertia energy and acceleration, i.e. fuel consumption per unit of energy-
acceleration (mL/(kJ.m/s2) or g/(kJ.m/s2)).
Parameter b1 (or A) is roughly proportional to vehicle mass and parameter b 2 (or B) is
approximately proportional to the frontal area of the vehicle. Parameters b1 and b2 (or A and B)
also reflect some component of drag associated with the engine.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.33

Equation (3.8.1) represents an energy or power-based fuel consumption or emission model, where
the total tractive power (kW) is PT = RT v (Equation 3.8.3) and the inertial power (kW) is PI = Mv a
v / 1000.

3.8.3 Model for Emission Rates (CO, HC, NOx,)

The model for estimating the instantaneous Carbon Monoxide (CO), Hydrocarbons (HC) and
Nitrogen Oxides (NOx) emission rates (g/s), representing the emission production rate at any
instant during the trip determined as a value per unit time, has the same structure as the
instantaneous fuel consumption model (Equations 3.8.1 and 3.8.2) with different parameters
(Table 3.3). For these emission rates, parameters in (Equations 3.8.1 to 3.8.3) are defined as
follows:
ft = instantaneous emission rate (g/s),
 (or fi) = constant idle emission rate (g/s or g/h),
1, 2 = the efficiency parameters (g/kJ and g/(kJ.m/s2).
The definition of RT from Equation (3.8.2) as "tractive force" is correct for fuel consumption
estimation only. For emission rates (CO, HC, NOx), RT should not be interpreted as "tractive
force". In other words, separate RT calculations are needed for fuel consumption and different
emission rates using appropriate model parameters.

3.8.4 Model for Carbon Dioxide Emission (CO2)

The values of instantaneous Carbon Dioxide (CO2) emission rate (g/s as a value per unit time) are
estimated directly from the instantaneous fuel consumption rate:
ft(CO2) = fCO2 ft(fuel) ( 3.8.6 )
where
ft(fuel) = fuel consumption rate in mL/s calculated from Equation (3.8.1) and,
fCO2 = CO2 to Fuel Consumption Rate in grams per millilitre (kg per litre) of fuel
(g/mL or kg/L).
The following default values of CO2 to fuel consumption rate (fCO2) in kg per litre of fuel (kg/L) are
used in SIDRA TRIP:
 Passenger Cars and Light Vehicles: 2.5 kg/L, and
 Heavy Vehicles: 2.6 kg/L.

3.8.5 Fuel and Emission Model Calibration

The following step-wise calibration method is recommended for determining the default or input
values of fuel consumption and emission model parameters summarised in Table 3.3 (based on
Bowyer, Akçelik and Biggs 1985, Appendix B, Section B1). Since fuel consumption and emission
model parameters are specified in Metric Units, the conversion factors given in Table 3.4 would be
useful if the data are in US Customary units.
(i) Determine the idle fuel consumption or emission (CO, HC, NOx) rate (fi) by measuring the
total fuel consumption or emission while idling (warm engine) for about 200 s.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.34 Akcelik & Associates Pty Ltd

(ii) Determine parameters A and B from regression using cruise fuel consumption or emission
data obtained by driving at steady speeds between 15 and 120 km/h on a level road. The
cruise fuel consumption or emission rate, ftc (mL/s or g/s) on a level road is given by:
ftc =  + c1 vc + c2 vc3 ( 3.8.7 )
where  = fi / 3600 is the known idle fuel or emission rate (mL/s or g/s) as determined in
step (i), vc is the steady cruise speed (m/s), c1 and c2 are the coefficients found by regression.
Parameters c1 and c2 are related to parameters b1 and b2 in Equations ( 3.8.5a) and ( 3.8.5b)
as follows:
c1 = b1 1 ( 3.8.7a )
c2 = b2 1 ( 3.8.7b )
and therefore, parameters b1, b2, A and B are given by from:
b1 = c1 / 1 if 1 > 0 ( 3.8.7c )
=0 if 1 = 0
b2 = c2 / 1 if 1 > 0 ( 3.8.7d )
=0 if 1 = 0
A = 1000 b1 1 = 1000 c1 ( 3.8.7e )
B = 1000 c2 / 12.96 ( 3.8.7f )
where the parameter units are as follows:
c1 : mL/m or g/m
c2 : (mL/m)/(m/s)2 or (g/m)/(m/s)2
A : mL/km or g/km
B : (mL/km)/(km/h)2.
(iii) Determine the efficiency parameters  1 and 2 using instantaneous fuel consumption or
emission data collected by at least 1000 s of driving. Data should correspond to a wide
range of speed and acceleration values representing on-road driving conditions. Determine
the ftc component of fuel for each point using Equation (3.8.7) with known parameter values
(, c1 and c2) as determined in steps (i) and (ii). Calculate the inertial component of fuel
consumption or emission for each data point (from Equations (3.8.1) to (3.8.3)):
fI = ft - ftc = 1 PIG + 2a PI ( 3.8.8a )
where the inertial components of power are:
PIG = (Mv a v + 9.81 Mv v (G/100)) / 1000 ( 3.8.8b )
a PI = Mv a2 v / 1000 ( 3.8.8c )
and the total power is:
PT = b1 v + b2 v3 + PIG ( 3.8.8d )
Since fuel consumption or emission values cannot be measured accurately as instantaneous
values, data should be aggregated into reasonably long time intervals (e.g. 10 to 20 seconds
for a fuel flow meter, and 1 to 5 seconds for measurements on a dynamometer). For each
time interval k, determine values of:
FIk =  (ft - ftc ) ( 3.8.9a )
PIGk =  PIG for PT > 0 ( 3.8.9b )
a PIk =  a PI for PT > 0 and a >0 ( 3.8.9c )

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.35

where the summations are over the points in time interval k subject to restrictions on the
total power (PT) and acceleration rate (a).
Determine the values of  1 and 2 jointly by regression of (PIGk) and (a PIk) on FIk through
the origin.
Apply an iterative method starting with some initial values of 1 and  2 (e.g. the default
values given in Table 3.3) in Equation (3.8.8a), and by substituting the newly estimated
values of  1 and  2 in Equation (3.8.8a) and repeating the estimation process. Continue until
estimated  1 and  2 values do not change.
Negative values of  2 should not be obtained (a likely cause of this error is that the time
interval for aggregation is too short).
(iv) Once 1 and 2 are determined, calculate parameters b1 and b2, A and B from
Equations (3.8.7c) to (3.8.7f).

Table 3.4
Useful conversion factors

Quantity Unit Unit for Fuel

Length foot 1 ft = 0.3048 m
mile 1 mi = 1609.3 m
Mass pound 1 lb = 0.4536 kg = 453.6 g
Speed foot per second 1 ft/s = 0.3048 m/s
mile per hour 1 mi/h = 0.4470 m/s = 1.6093 km/h
Acceleration foot per second squared 1 ft/s2 = 0.3048 m/s2
Volume US gallon 1 US gal = 3.7854 L = 3785.4 mL
Force pound-force 1 lbf = 4.448 N
Energy foot pound-force 1 ft.lbf = 1.356 J
calorie 1 cal = 4.1868 J
Power foot pound-force per second 1 ft.lbf/s = 1.356 W
calorie per second 1 cal/s = 4.1868 W
horsepower 1 hp = 0.7457 kW
Fuel US gallon per hour 1 US gal/h = 3785.4 mL/h = 1.0514 mL/s
Consumption
US gallon per mile 1 US gal/mi = 2.3522 L/km (or mL/m)
= 235.22 L/100km
mile per US gallon 1 mi/US gal = 0.42514 km/L (or m/mL)
[mpg (US)] [235.22 / mpg (US) = L /100km]

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.36 Akcelik & Associates Pty Ltd

3.9 DRIVERS
The input dialogs in the Drivers group of the Input Data Tree (Figure 3.14) are used to specify data
that describe the driver characteristics. The title bar of the input dialog gives the name of the
selected Driver in brackets.
The Acceleration and Deceleration Adjustment Factors in this dialog affect the acceleration
time and distance values estimated by SIDRA TRIP in the case of the Event Data method when the
time or distance value is not specified by the user.
The Drivers group of data is not available in the case of the Travel Data method since driver
characteristics are inherent to the data collected using an instrumented vehicle.

Specify Adjustment
Factors to modify
acceleration and
deceleration rates

Figure 3.14 - Drivers input dialog for Event Data method (for "My Driver" in this example)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - INPUT 3.37

3.10 DIAGNOSTICS
If simulation data violate the Maximum Power, Maximum Grade, Maximum Speed or
Maximum Acceleration values specified for the vehicle (Section 2.4.1), this means that the data
are not reliable. In this case, warning messages about data quality will appear in all text output
windows, and more detailed information will be given as follows:
 In the case of the Travel Data method, a Diagnostics node will appear in the Profile Tree,
and the corresponding window will be opened automatically (Figure 3.15). The
Diagnostics window will include various messages about data problems (highlighted using
red font). The data values shown in this dialog are simulated values which may differ from
input values.
 In the case of the Event Data method, the Event Statistics window will be opened
automatically (Figure 3.165). In the Profile Tree, the window will be represented by the
Diagnostics icon. The Acceleration Statistics table in the Event Statistics window will
include messages about data problems (highlighted using red font).

Diagnostics node and text

messages appear when the
program identifies that
results are not reliable

Acceleration from 0 to 60 km/h and deceleration

from 60 to 0.4 km/h in one second causes the
problems in this example.

Figure 3.15 - Diagnostics node and window (Travel Data method)

In the case of the Travel Data method, you can inspect the Diagnostics window for messages about
the problems, and in the Trip Data dialog, you can edit the Speed, Distance or Grade values, or
delete data rows that cause the problems. You can then check the output again to see if the data
revision removes the problems.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
3.38 Akcelik & Associates Pty Ltd

The following should be noted about the use of highlighting in the Diagnostics window to indicate
problems:
 If Distance data have been used to perform the simulation, any problems with Speed data
will be related to Distance values in the current and previous row used to determine the
speed value.
 Any problems with Acceleration data will be related to Speed values in the current,
previous and following row used to determine the acceleration value.
In the case of the Event Data method, you can inspect the Acceleration Statistics table in the
Event Statistics window for messages about the problems, and you can edit the data in the Trip
data dialog (Initial Speed, Final Speed, Event Duration / Distance, Grade), or delete Events that
cause the problems. You can then check the output again to see if the data revision removes the
problems.
You should also review vehicle Mass and Maximum Power values in such problem cases.

User-specified short acceleration time for

0 to 100 km/h on 10% uphill grade, and
cruise at 100 km/h on 10% grade cause the
problems in this example.

Symbol of Event Statistics

node changes to indicate a
Diagnostics case

Figure 3.16 - Diagnostics in Event Statistics window (Event Data method)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

SIDRA TRIP
USER GUIDE
SECTION 4 - OUTPUT

Restricted document
for use under SIDRA TRIP
software licence only

September 2011
 Akcelik & Associates Pty Ltd
PO Box 1075G, Greythorn, Vic 3104 AUSTRALIA
[email protected]

Management Systems Registered to ISO 9001

® ABN 79 088 889 687

© AKCELIK & ASSOCIATES PTY LTD 2000 - 2011

All Rights Reserved.
No part of this document may be copied, reproduced, used to prepare derivative works by modifying,
disassembling, decomposing, rearranging or any other means, stored in a retrieval system or
transmitted in any form or by any means: electronic, electrostatic, magnetic tape, mechanical,
photocopying, recording or otherwise, without the prior and written permission of Akcelik &
Associates Pty Ltd.
The information provided in this document is CONFIDENTIAL and must not be used for any
commercial purposes or in any way that infringes on the intellectual property or other rights of Akcelik
& Associates Pty Ltd.
Readers should apply their own judgement and skills when using the information contained in this
document. Although the information contained in this document is considered accurate, no warranties
or guarantees thereto are given. Whilst the authors have made every effort to ensure that the
information in this document is correct at the time of publication, Akcelik & Associates Pty Ltd, save
for any statutory liability which cannot be excluded, excludes all liability for loss or damage (whether
arising under contract, tort, statute or otherwise) suffered by any person relying upon the information
contained in the document. Any such statutory liability is reduced to the full extent lawful.
Any product, trade or manufacturer name(s) appear in this document only because they are considered
essential for the purposes of this document, and Akcelik and Associates Pty Ltd does not endorse,
market, support, represent or accept any liability for any product or manufacturer appearing in this
report unless it is so specified.

Any examples given in User Guides, training manuals and similar documents for SIDRA SOLUTIONS
software products, or any templates included in SIDRA SOLUTIONS products, have been prepared for
the purpose of demonstrating software features or providing a basis for user input, and do not
necessarily represent the best design practice.

SIDRA SOLUTIONS software products are professional tools for the purpose of capacity, level of
service, operating performance and travel quality analysis of road traffic. They are not safety design or
evaluation tools. We recommend the use of appropriate safety analysis and audit tools for this
purpose.

ACKNOWLEDGEMENTS
Akcelik & Associates Pty Ltd acknowledges the contributions by numerous users from many countries
around the world through their valuable comments towards the development of SIDRA SOLUTIONS
software products.

IMPORTANT

User Guides and training manuals for SIDRA SOLUTIONS software products are RESTRICTED
DOCUMENTS for use under software licence only. These documents may not be placed in any public
library, may not be rented, loaned or distributed by any means. They are under the COPYRIGHT of
Akcelik and Associates Pty Ltd and may only be reproduced with written permission.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide 4.1

4. OUTPUT

4.1 INTRODUCTION
The SIDRA TRIP output system provides various text output (Trip Statistics, Sums and Event
Statistics) and graphs (Motion Graphs, Fuel Graphs, Emission Graphs, Cost Graphs, Noise
Graphs, etc.). It also provides animation of vehicle movement using graphical Animation Pane,
Speedometer and Powermeter displays.
You can inspect the text output and graphs by double-clicking the corresponding names in the
Profile Tree. You can view the animation displays by using the toolbar buttons or the View menu.
Text output, graphs and animation are explained in Section 4.2. Information on printing, copying
and saving SIDRA TRIP text output and graphs is given in Section 4.3.
Study Section 4.4 to learn about technical aspects of SIDRA TRIP output. For additional
information on SIDRA TRIP models, refer to published papers and reports listed at the end of
Section 1 (Introduction).

4.2 TEXT OUTPUT, GRAPHS, ANIMATION

Text output and graph windows can be opened by double-clicking the corresponding names
(nodes) in the Profile Tree on the left-hand side of your screen. The display window will be
opened in the Display Pane on the right-hand side of your screen. See Section 2.3.2 for detailed
information on the SIDRA TRIP user interface.
To close an output display window, click the box at the top right-hand corner of the window or
press Ctrl+F4. To close all display windows, use Window - Close All. Closing windows in the
display pane will not close a profile. To close the Profile, select File - Close from the menu.
If the relevant information does not exist, the node(s) representing the output will not appear in the
Profile Tree. If SIDRA TRIP finds any data or processing error, no output nodes will be present in
the Profile Tree.
When processing of input data is completed for the first Profile after starting SIDRA TRIP, Text
Output windows will be opened in the Display Pane according to the settings in Tools - Options -
Output. No graphs will be opened automatically.
Click the check boxes in the Default Text Output group in Tools - Options - Output to select the
output windows you want to be opened automatically. Subsequently, if you use Edit Profile to edit
data and click OK, the output in windows that were currently open before data editing will remain
open, and the output in those windows will be updated.
To open Text Output windows or Graphs that were closed previously, double-click the
corresponding node in the Profile Tree.
4.2 Akcelik & Associates Pty Ltd

4.2.1 Text Output

The following HTML-style text output windows are available in SIDRA TRIP (see Figures 4.1
to 4.3):
 Trip Statistics
 Sums
 Event Statistics (if using the Event Data method)
The Trip Statistics output (Figure 4.1) gives statistics for the evaluation of the simulated single
vehicle trip. It includes the following sections:
 Header,
 Trip Assessment,
 Speed,
 Cost (Operating or User) ,
 Fuel Consumption,
 Emissions (CO2, CO, HC, NOx), and
 Noise.
When the Travel data Method is used, the Trip Statistics output window includes information about
Trip Data Settings used in simulation (Data Time Interval, Speed and Distance Units in Source
Data, and Simulation Performed Using Speed data / Distance data / Coordinates)
When using data from NMEA Text files, the Trip Statistics output includes a section titled Input
Data Accuracy. SIDRA TRIP determines the horizontal and vertical accuracy index (HAI,
VAI) values for each time step according to the number of satellites available at the time data were
recorded. These values are kept in the SIDRA TRIP Profile (aam) file. The Trip Statistics output
includes average values of HAI and VAI for the trip (or section of a trip as applicable) in the case
of NMEA text data. The index values are in the range 1 to 5 (1: Very Poor, 5: Very Good).
The Sums output (Figure 4.2) gives results for a given number of trips (or a number of vehicles)
using the results for the single vehicle trip.
The Event Statistics (Figure 4.3) output gives detailed results per event (or per drive cycle
element) in the case of the Event Data method. This window does not appear when the Travel
Data method is used.
The search function (Edit - Find) can be useful for finding the desired section of any text in
HTML-based output displays.
For information on printing text output, or copying text output into a word processor file, see
Section 4.3.
Detailed information about output statistics is given in Section 4.4.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.3

Figure 4.1 - Example of Trip Statistics output

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.4 Akcelik & Associates Pty Ltd

Figure 4.2 - Example of Sums output

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.5

Figure 4.3 - Example of Event Statistics output

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.6 Akcelik & Associates Pty Ltd

4.2.2 Graphs

SIDRA TRIP generates a large number of graphs (Figure 4.4) which will appear in the Profile Tree
according to the graph output options selected in Tools - Options - Output (graphs which are
checked will be listed in the Profile Tree).
The Graphs are not opened automatically. To view a Graph, double-click the desired Graph (node)
listed under Graphs in the Profile Tree. Graphs can be resized on the screen by dragging the
window border with the mouse.
To close a Graph window, click the box at the top right-hand corner of the window. See
Section 2.3.2 for detailed information on the SIDRA TRIP user interface.
To select a section of a graph (to zoom in), click the graph area and drag the mouse to the right and
down. To move the graph contents, right click the graph area and drag. To reinstate the original
graph (to zoom out), click and drag in reverse direction (left and up).
For information on printing Graphs, or copying Graphs into a word processor or graphics file, see
Section 4.3.
The following graphs for cumulative (total) and instantaneous (per unit time) values of various
parameters are available:
 Motion Graphs (Distance, Speed, Acceleration, Jerk, Average Speed),
 Fuel Graphs (Fuel Consumption Total, Fuel Consumption Time Rate, Fuel Economy),
 Emission Graphs (CO2 Total, CO2 Time Rate, CO Total, CO Time Rate, HC Total,
HC Time Rate, NOx Total, NOx Time Rate),
 Cost Graphs (Cost Total, Cost Time Rate),
 Energy-Related Graphs (Energy Total, Power, Tractive Force),
 Noise Graphs(ASJ 2003 Japanese, SonRoad Swiss, RLS 90 German), and
 Miscellaneous (Loop).
All graphs are linked to animation dynamically, i.e. graphs will be drawn with the vehicle
movement during animation. In Tools - Options - Output, an option is available to plot graphs
before animation.
The following options are also available in Tools - Options - Output:
 Maximum Metric Fuel Economy (L/100km), which is the largest value to be displayed
in the Fuel Economy graph (relevant only when Metric units are in use), and
 various options for Noise Graphs (Fixed Receptor or Relative Receptor model, show
receptor location for Fixed Receptor, and show Leq and LeqT values, i.e average equivalent
noise levels for the trip and for a traffic stream).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.7

To select a section of
the graph (zoom in),
click the graph area
and drag.
To reinstate the original
graph (to zoom out),
click and drag in reverse
direction (left and up).

Figure 4.4 - Example of graphs

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.8 Akcelik & Associates Pty Ltd

4.2.3 Animation
The animation feature in SIDRA TRIP allows you to animate the movement of a vehicle as defined
in the trip profile with dynamic graphs linked to the vehicle movement (Figure 4.5). You can
animate driving on the left-hand or right-hand side of the road.
The Animation Pane can be hidden or displayed (toggle action) by clicking the Animation Pane
button on the toolbar or using View - Animation Pane. The View menu also contains the options
Speedometer (show or hide the Speedometer display) and Powermeter (show or hide the
Powermeter display). These view options have a toggle action (show or hide). The program
remembers the status of these view options.
The size of Speedometer and Powermeter displays can be changed by clicking the plus and minus
symbols on the display. Speedometer also displays the distance from the start of trip. These
displays can also be closed by clicking the box at the top right-hand corner of the display.
The colour code used for vehicle, Speedometer and Powermeter indicates the status of the vehicle
manoeuvre:
 Green: Cruise,
 Yellow: Deceleration,
 Red: Idling,
 Magenta: Acceleration.
In the case of Travel Data method, the distance since the start of trip is shown in the Animation
Pane. In the case of the Event Data method, the event markers, their distance from the start of the
trip, loops and loop numbers are shown in the Animation Pane.
The Animate menu contains the options Play (run animation), Pause (stop animation temporarily),
and Reset (stop animation and reset to the start of trip). Animation speed can be changed by using
the Time Factor button in the toolbar.
The following options can be set in Tools - Options - Animation:
 Drive Rule (Left or Right to indicate which side of the road the vehicle uses);
 Smoothness (Low, Medium or High to determine the smoothness of vehicle movement,
which is related to the animation frames per second);
 Scale (Very Small, Small, Normal, Large or Very Large to determine the distance
shown in one frame of animation, which also affects the vehicle size shown).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.9

Adjust the Time Factor

Scale to speed up the
animation

Run, Pause,
Stop buttons

Colour code
shows vehicle
manoeuvre status

Figure 4.5 - Animation

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.10 Akcelik & Associates Pty Ltd

4.3 PRINTING, COPYING and SAVING OUTPUT

In SIDRA TRIP, text output and graphs can be printed:
 directly using the associated Print function (standard Windows printing facilities apply), or
 by copying and pasting into a word processing (e.g. Microsoft Word) or graphics (e.g.
Microsoft Paint) file.
To print text output or a graph, or copy it to the Windows clipboard, you must first:
 open the desired text output or graph display window by double-clicking its name in the
Profile Tree, or
 select the desired text output or graph display window if it was opened previously by using
the list of open items in the Window menu or clicking the desired display window in the
Display Pane.
If you wish to print or copy only a section of the text output, select the desired section.

Printing Text Output and Graphs

The HTML-based text output (Section 4.2.1) and graphs (Section 4.2.2) generated by SIDRA TRIP
can be printed using File - Print (or Ctrl + P) or using the Print function in the right-click menu.
These will open the Print dialog before printing. You can use various options to specify print
settings in the Print dialog.
SIDRA TRIP text output is printed in a continuous form, i.e. without any page breaks. You can use
File - Print Preview before you print the HTML-based text output to check that the display fits in
pages as you wish. If not in the format you want, you need to copy the display into a Word
document and format for printing.

Network Printers
Sending output to a printer on your network is handled by Windows. It is your responsibility to
select the correct printer and set it up correctly (paper settings, etc.). Facilities such as notification
that printing has been completed are provided by your network, not by SIDRA TRIP. If you
require assistance in this area, contact your network administrator or IT Department.

Copying Text Output and Graphs

To copy text to the clipboard:
 select Edit - Select All then Edit - Copy from the main menu, or
 select the desired section of text, then select Edit - Copy from the main menu, or
 press Ctrl+A then Ctrl+C, or
 right-click in the display area and click Select All in the menu, and then right-click in the
display area again and click Copy.
You can then open a word processor (e.g. MS Word) and Paste the text in a new document or the
document you are working on (Edit - Paste or press Ctrl+V), edit it (format it as you like, e.g.
delete some rows in a table, specify single line spacing with desired spacing before and after the
line, specify smaller font size, introduce border lines and shading, etc), and then save or Print as
desired.
To copy a graph to the clipboard:
 right-click in the graph area and click Copy in the menu, or

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.11

 select Edit - Copy from the main menu, or

 press Ctrl+C.
You can then open a word processor or graphics application and Paste the picture in a new file, edit
it and then save or Print as desired.

Saving Text Output and Graphs

You can save the HTML-based text output as separate files using File - Save Output As. Use of
the Save As Type selected as Formatted Web Archive, single file (*.mht) is recommended. This
creates a file suitable for viewing with web browsers like Microsoft Internet Explorer or Mozilla
Firefox.
You can also use File - Save Output As with Save As Type selected as Raw XML File (*.xml).
You can save a graph as a separate file using File - Save Graph As, or using the Save Graph As
function in the right-click menu. The graph will be saved as a picture file in Enhanced Metafile
(*.emf) format. You can then use the picture in various applications.
Note that File - Save and File - Save As functions are relevant to the Profile (.aam) file, File - Save
Sim Data As is for saving detailed simulation data in XML (*.xml) format, and File - Save Trip
Data As is for saving trip data contained in the Profile (.aam) file in a raw (source) data format
(CSV, Text, GPS Exchange, or Track as applicable).
You can also export data used in simulation using File - Save Trip Data As (in csv or txt format)
or File - Save Sim Data As (in csv, txt or xml format).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.12 Akcelik & Associates Pty Ltd

4.4 OUTPUT STATISTICS

This section presents detailed information on SIDRA TRIP output statistics.
Information in this section is structured to correspond to sections of the Trip Statistics text output
window (Section 4.2.1):
 Trip Assessment,
 Speed,
 Cost (Operating or User),
 Fuel Consumption,
 Emissions (CO2, CO, HC, NOx), and
 Noise.
Information on output statistics contained in the Sums and Event Statistics text output windows
(Section 4.2.1) and Graphs (Section 4.2.2) are included in relevant sections.
Generally, output includes total (cumulative) and average values, lowest and highest instantaneous
values, and various derived values for the trip. It also includes distance rates (i.e. values per unit
distance, per km or per mi) and percentage values (as percentage of total trip value) where relevant.
In the case of Travel Data method, the term "trip" in relation to the output statistics (text and
graphs) refers to the simulated trip which corresponds to all or a section of the trip data, in
accordance with the Start Section - End Section specification in the General Settings dialog of the
Profile.
In SIDRA TRIP, the instantaneous value of a variable, e.g. fuel consumption rate, fj (mL/s), for the
jth simulation interval (whose duration is T s seconds) is considered to belong to the end point of the
simulation step. Thus, the instantaneous value at the start of the interval belongs to the previous
simulation step (fj-1).
For determining the incremental value of the variable for the simulation step, e.g. fuel consumed
during a simulation interval, Fj (mL), an average value is determined using the instantaneous
values at the start and end of the interval, e.g. Fj = 0.5 (fj-1 + fj) Ts.
The cumulative value of the variable since the start of trip is then determined as the sum of
incremental values, (Fj).
Values of statistics (e.g. Desired Cost for Trip, Desired Fuel for Trip, etc) are calculated for
conditions of driving at constant Desired Speed, i.e. they are not based on simulation.
Output statistics such as Excess Cost for Trip, Excess Fuel for Trip, etc are determined as the
difference between the Cost for Trip, Fuel for Trip, etc and Desired Cost for Trip, Desired Fuel for
Trip, etc. The latter are calculated for conditions of driving at constant Desired Speed, i.e. they are
not based on simulation. Excess values may be negative if a saving has been made in comparison
to the value at the Desired Speed.
All fuel consumption values are in US gallons (not imperial gallons) when US Customary Units are
used.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.13

4.4.1 Trip Assessment

Travel Distance
Travel Distance, Lt (km or mi) is the total distance travelled during the trip determined as the sum
of the distance travelled in each simulation interval:
Lt (km) = [Lj] / 1000 ( 4.4.1a )
Lt (mi) = [Lj] / 1609.3 (4.4.1b )
Lj = 0.5 (vj-1 + vj) Ts / 3.6 ( 4.4.1c )
where
Lj = distance travelled (metres) during jth simulation interval,
vj = instantaneous speed at the end of current simulation interval (km/h),
vj-1 = instantaneous speed at the end of previous simulation interval (km/h),
Ts = Simulation Time Interval (s),
and summation is for all simulation intervals (whole trip).
The Distance graph in the Motion Graphs group shows the cumulative distance travelled (m or ft)
during the trip.
Travel Distance is based on the distance determined using the instantaneous speed values used in
simulation. When the "Perform Simulation Using Distance Data" option is selected in the Edit
Profile - Trip Data input dialog (for the Travel Data method), distance data are used to determine
speed values first, and then simulation is carried out using the calculated speed values. As a result,
the simulated distance may differ from the input distance values.
Zero Travel Distance, Lt = 0 condition will occur when the whole trip consists of idling at zero
speed. In this case, all outputs statistics for per unit distance as well as the Travel Time Index and
Level of Service will be undefined.
Figure 4.6 depicts the movement of a vehicle that stops and starts at traffic signals as an example
of a time-distance diagram to show definitions of travel distance, time and speed statistics.

Travel Time
Travel Time, Tt (seconds) is the total travel time for the trip.
Travel time per unit distance, Ttx (s/km or s/mi) is determined from:
Ttx = Tt / Lt ( 4.4.2 )
where Lt is the Travel Distance (km or mi).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.14 Akcelik & Associates Pty Ltd

Distance
Travel Time, Tt

Desired Trip Time, Td Travel Delay, dt

Idling
Time, To
Running time, Tr

vd
vr vt
Travel Distance, Lt

Uninterrupted Travel with

travel idling

vd: Desired Speed

Idling vr: Average Running Speed
Time, To vt: Average Travel Speed

Time
Cruise Deceleration Stopped Acceleration Cruise
(idling)

Figure 4.6 - Definitions of travel distance, time and speed statistics

Idling Time
Idling Time, To (seconds) is the total time during the trip when the vehicle is fully stopped (zero-
speed condition).
Stopped Time per unit distance, T ox (s/km or s/mi) and the percent time when the vehicle is
stopped, pTo are determined from:
Tox = To / Lt ( 4.4.3a )
pTo = 100 To / Tt ( 4.4.3b )
where Lt is the Travel Distance (km or mi) and Tt is the Travel Time (seconds).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.15

Running Time
Running Time, T r (seconds) is the total time during the trip when the vehicle is moving (speed
greater than zero):
Tr = Tt - To ( 4.4.4a )
The Running Time per unit distance, T rx (s/km or s/mi) and the percent time when the vehicle is
running, pTr are determined from:
Trx = Tr / Lt ( 4.4.4b )
pTr = 100 Tr / Tt ( 4.4.4c )
where Lt is the Travel Distance (km or mi) and Tt is the Travel Time (seconds).
The percent time when the vehicle is stopped and the percent time when the vehicle is running add
up to 100 per cent (pTo + pTr = 100).

Desired Trip Time

Desired Trip Time, Td (seconds) is the time to travel the Travel Distance at constant Desired Speed,
vd (km/h or mph):
Td = 3600 Lt / vd ( 4.4.5a )
The Desired Trip Time per unit distance, T dx (s/km or s/mi) and the Desired Trip Time as a
percentage of Travel Time, pTd are determined from:
Tdx = Td / Lt = 3600 / vd ( 4.4.5b )
pTd = 100 Td / Tt ( 4.4.5c )
where Lt is the Travel Distance (km or mi) and Tt is the Travel Time (seconds).

Travel Delay
Travel Delay, dt (seconds) is an excess travel time value determined as the difference between the
actual Travel Time, Tt and the Desired Trip Time, Td:
dt = Tt - Td ( 4.4.6a )
The Travel Delay per unit distance, dtx (s/km or s/mi) and the Travel Delay as a percentage of
Travel Time, pdt are determined from:
Tdx = dt / Lt ( 4.4.6b )
pdt = 100 dt / Tt ( 4.4.6c )
where Lt is the Travel Distance (km or mi) and Tt is the Travel Time (seconds).
The Desired Trip Time and Travel Delay as percentages of Travel Time add up to 100 per cent
(pTd + pdt = 100).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.16 Akcelik & Associates Pty Ltd

Travel Time Index

The Travel Time Index (TTI) is determined from:
TTI = 10 (pT – pL) / (1 – pL) for pT > pL ( 4.4.7 )
=0 for pT  pL)
where
pT = Td / Tt = Travel Time Ratio, i.e. the ratio of Desired Trip Time to the actual Travel Time
for the trip, and
pL = lower limit of the Travel Time Ratio (a selected constant; range: 0 to 0.3, default: 0.1).
The Travel Time Index is unique to SIDRA TRIP. It has been developed by Akçelik (1999), and is
based on driver frustration research reported by Gunatillake, Cairney and Akçelik (2000). The
basis of the TTI formulation given in Equation (4.4.7) is shown in Figure 4.7. This formulation
gives TTI values in the range:
 10 = best (pT = 1.0, i.e. Tt = Td, hence travel delay, dt = 0) to
 0 = worst (pT  pL, i.e. Tt  10 Td, hence travel delay, dt  9 Td).
The lower limit of the Travel Time Ratio, p L can be specified as input in the Edit Profile - Cost &
LOS Parameters input dialog, and the corresponding default value can be specified in Tools -
Defaults - Cost & LOS Parameters. This sets the condition for the worst case (TTI = 0). The
default value of p L = 0.1 means TTI = 0 when Tt = 10 Td (i.e. when the Travel Time equals ten
times the Desired Trip Time). Using pL = 0.2 would mean TTI = 0 when Tt = 5 Td. (i.e. when the
Travel Time equals five times the Desired Trip Time).

Travel Time
Index, TTI

10

0
pL 1.0 Travel Time
Ratio, pT
Default and input values of the
Lower Limit of Travel Time Ratio (pL)
can be specified by the user.

Figure 4.7 - Travel Time Index (TTI)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.17

The Travel Time Index is undefined for zero Travel Distance, Lt = 0 which may occur when the
whole trip consists of idling at zero speed.
Note that pT is equivalent to the Speed Efficiency Ratio given in the Speed section of Trip Statistics
output, pT = Td / Tt = vt / vd where vt is the Average Travel Speed and vd is the Desired Speed.

Level of Service
The trip Level of Service (LOS) is determined in relation to a Travel Time Index (TTI) using a
method developed by Akçelik (1999). The reader is referred to the US Highway Capacity Manual
(TRB 2000) for discussions of the level of service concept and its application to different traffic
facilities using different criteria.
Table 4.1 presents the LOS grades (Good, Fair, Poor and Very Poor). The Travel Time Index
ranges for LOS grades given in Table 4.1 were chosen considering their implications for the degree
of saturation, speed and travel delay values using travel time - flow functions developed by Akçelik
(1991, 1996, 2002a,b, 2003, 2006a).
Level of Service is undefined for zero Travel Distance (Lt = 0). This will occur when the whole
trip consists of idling at zero speed.

Table 4.1
Level-of-service definitions based on Travel Time Index

Level of Service Traffic Time Index

Good 7 < Index  10
Fair 5 < Index  7
Poor 3 < Index  5
Very Poor 0  Index  3

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.18 Akcelik & Associates Pty Ltd

Number of Stops
Number of Stops, Ht for the trip is counted during simulation according to the definition of a Stop
using a Lower Speed, vL and an Upper Speed vU (km/h or mph) for this purpose (Figure 4.8). The
standard default values are:
Lower Speed for a Stop: 5 km/h or 3 mph
Upper Speed for a Stop: 25 km/h or 15 mph
These speed values can be specified in Tools - Defaults - Speed Settings as general default values,
or in the Edit Profile - Speed Settings input dialog as values specific to a Profile.
For an additional stop to be counted, the vehicle speed needs to be at or above the upper limit first
(v  vU), and then the vehicle speed must go below the lower limit (v < vL). After this, another stop
will be counted only if the vehicle speed goes to or above the upper limit first (v  vU), and then
goes below the lower limit again.
Number of Stops per unit distance, Htx (stops/km or stops/mi) is determined from:
Htx = Ht / Lt ( 4.4.8 )
where Lt is the Travel Distance (km or mi).

Speed vs Time
50

45
2 stops in this example
40

35

30 Upper Speed for

Speed (km/h)

a Stop (vU)
25

20

15

10 Lower Speed
for a Stop (vL)
5

0
0 1 2 3 4 5 6 7 8 9
1st Stop
10 11 12 13 14 15 16 17 18 19 20
2nd Stop
21 22 23 24 25 26 27 28
Time (s)
i

Figure 4.8 – Definition of a Stop

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.19

Acceleration and Deceleration Rates

The Trip Assessment section of Trip Statistics output includes Highest Acceleration and Highest
Deceleration rates (m/s2 or ft/s2) for the trip as determined during the simulation.
In the case of the Event Data method, Average and Highest Acceleration rates (negative values for
deceleration) for each event (relevant to speed change events) are given in the Acceleration
Statistics table of Event Statistics output.
The Acceleration graph in the Motion Graphs group shows the instantaneous values of
Acceleration (negative for deceleration) during the trip.
For detailed information on acceleration and deceleration models used in SIDRA TRIP (Event Data
method), refer to Akçelik and Besley (2001b).

Jerk
Jerk is the rate of change of acceleration (or inertia force). The pattern and values of Jerk gives an
indication of driving roughness (or comfort). The Trip Assessment section of Trip Statistics output
includes Highest Jerk (m/s3 or ft/s3) for the trip as determined during the simulation.
In the case of the Event Data method, Highest Jerk (negative value for deceleration) for each event
(relevant to speed change events) is given in the Acceleration Statistics table of Event Statistics
output.
The Jerk graph in the Motion Graphs group shows the instantaneous values of Jerk during the
trip.

Tractive Power
The Tractive Power, PT (kW or hp) required to drive the vehicle includes the drag power, inertia
power and grade power (Equation (3.8.3) in Section 3.8.2). This equation also shows the
relationship between Tractive Power and Tractive Force.
The Trip Assessment section of the Trip Statistics output includes the Highest Tractive Power for
the trip as determined during the simulation.
In the case of the Event Data method, the Highest (Tractive) Power for each event is given in the
Acceleration Statistics table of the Event Statistics output.
The Tractive Power graph in the Energy-Related Graphs group shows the instantaneous values
of Tractive Power during the trip.
A Powermeter is available to display the instantaneous values of tractive power during animation.
If any instantaneous Tractive Power value exceeds the Maximum Power value specified for the
vehicle, Diagnostic messages are given in SIDRA TRIP output (Section 3.10).
When determining the acceleration profile for each speed change event when the Event Data
method is used, the Tractive Power values are checked against the Maximum Power, and the
acceleration rate is adjusted to satisfy this constraint. The program will override any user-specified
Event Duration or Distance in this case. All speed-change Events with user-specified Duration or
Distance values will be affected if the Maximum Power constraint applies for any Event.
Diagnostic messages will be given in the Event Statistics window in such cases (Section 3.10).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.20 Akcelik & Associates Pty Ltd

Tractive Force
The Tractive Force, RT (kN or lbf) required to drive the vehicle includes the drag force, inertia
force and grade force (Equation (3.8.2) in Section 3.8.2).
The Trip Assessment section of Trip Statistics output includes Highest Tractive Force for the trip
as determined during the simulation.
In the case of the Event Data method, Highest (Tractive) Force for each event is given in the
Acceleration Statistics table of the Event Statistics output.
The Tractive Force graph in the Energy-Related Graphs group shows the instantaneous values
of Tractive Force during the trip.

Energy for Trip

Energy for Trip, et (kJ) given in the Trip Assessment section of the Trip Statistics output is the total
energy consumed for the vehicle movement during the trip. This is determined as the sum of
energy consumed during all simulation intervals:
et =  (ej) ( 4.4.9a )
where ej (kJ) is energy consumed during the jth simulation interval, which is based on the average
Tractive Power during the interval:
ej = 0.5 (PTj-1 + PTj) Ts ( 4.4.9b )
where:
PTj = instantaneous tractive power value at the end of current simulation interval (kW),
PTj-1 = instantaneous tractive power value at the end of previous simulation interval (kW),
Ts = Simulation Time Interval (s).
In the case of the Event Data method, Total Energy for each event is given in the Acceleration
Statistics table of Event Statistics output.
The Energy Total graph in the Energy-Related Graphs group shows the cumulative values of
Energy during the trip.
In SIDRA TRIP, energy results are always given in kilojoules (kJ) even when the US Customary
Units are used.
Energy for Trip per unit distance, etx (kJ/km or kJ/mi) is determined from:
etx = et / Lt ( 4.4.9c )
where Lt is the Travel Distance (km or mi).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.21

Acceleration Noise
Acceleration Noise, a (m/s2 or ft/s2) is a statistic used in the literature to represent speed variations
during a trip, e.g. Drew (1968, p.362). The word Noise in this term has no relation to sound.
Acceleration Noise is determined from:
a = {(Ts / Tr)  [a(t) - at]2 }0.5 ( 4.4.10a )
at = (Ts / Tr)  a(t) ( 4.4.10b )
where Ts is the Simulation Time Interval (seconds), Tr is the Running Time (seconds), a(t) is the
acceleration rate at time (t) as determined for each simulation step, at is the average acceleration
rate for the trip, and summation is for the whole trip except idling (zero-speed) intervals.

PKE
The Positive Kinetic Energy, PKE (m/s2 or ft/s2) parameter is a useful measure of speed variations
during a trip, and has been used in aggregate fuel consumption models in the literature, e.g. Akçelik
(1983a), Bowyer, Akçelik and Biggs (1985). PKE (m/s2) is determined from:
PKE = 0.3858 x 10-4 [ (vf2 – vi2)] / Lt ( 4.4.11 )
where
vi, vf = initial and final speeds (km/h) during each positive acceleration event (vf > vi, a > 0), and
Lt = Travel Distance (km).
The summation in Equation (4.4.11) is for all positive speed change events during the trip (i.e.
deceleration manoeuvres are not included).

Total Loop Occupancy Time

Total Loop Occupancy Time is the sum of all loop occupancy times for the trip. Detector Loops
can be specified only when the Event Data method is being used (Section 3.4.5). Occupancy Time
for each loop is given in the Loop Statistics section of the Event Statistics output.
As seen in Figure 4.9, the detector loop occupancy starts when the front of the vehicle reaches the
upstream edge of the loop (location L1, time t 1,) and finishes when the tail of the vehicle clears the
downstream edge of the loop (location L2 = L1 + Lp + Lv, time t2 = t1 + (Lp + Lv) / v). As depicted
in Figure 4.9, loop occupancy time, to (seconds) for travel at constant cruise speed is:
to = (Lp + Lv) / v ( 4.4.12 )
where Lp is the detector loop length (m or ft), Lv is the vehicle length (m or ft) and v is the speed
(m/s or ft/s).
For example, using loop length, Lp = 3.0 m and car length, Lv = 4.5 m, occupancy time for travel at
60 km/h is to = (3.0 + 4.5) / (60 / 3.6) = 0.45 s.
However, the loop occupancy time for each loop is determined by simulation, hence the accuracy
of occupancy time will be limited by the value of the Simulation Time Interval (seconds).
The Loop graph in the Miscellaneous Graphs group shows the loop on/off times during the trip.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.22 Akcelik & Associates Pty Ltd

Distance

L2

Lv
v

Lp
Loop
location L1

ON OFF Time
to

t1 t2

Figure 4.9 - Loop occupancy

4.4.2 Speed
The Speed section of the Trip Statistics output includes various speed statistics which are explained
in this section. Speed is the main input parameter that determines other results in the simulation
process.
The Speed graph in the Motion Graphs group shows the instantaneous values of Speed during the
trip.
Speed, v (km/h, m/s, mph, or ft/s) is distance travelled per unit time. In a time-distance diagram
(e.g. Figures 4.6 and 4.9), the slope of the time-distance trace of a vehicle is its speed.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.23

Average Travel Speed

Average Travel Speed, vt (km/h or mph) is the average speed including the effect of all time lost
(delay) due to slowing down and stopping (idling) during the trip (Figure 4.6). It is given by:
vt = 3600 Lt / Tt ( 4.4.13 )
where
Lt = Travel Distance (km or mi), and
Tt = Travel Time (seconds).

Average Running Speed

Average Running Speed, vr (km/h or mph) is the average speed including the effect of all time lost
during the trip except any stopped (idling) times (Figure 4.6). It is given by:
vr = 3600 Lt / Tr ( 4.4.14 )
where
Lt = Travel Distance (km or mi), and
Tr = Running Time (seconds).

Desired Speed
Desired Speed, vd (km/h or mph) is the reference speed used in determining various output
statistics including:
 Desired Trip Time,
 Travel Delay,
 Travel Time Index and Level of Service,
 Speed Efficiency Ratio and Congestion Coefficient,
 Desired Cost for Trip and Excess Cost for Trip,
 Desired Fuel for Trip and Excess Fuel for Trip, and
 Desired CO2, CO, HC, NOx for Trip and Excess CO2, CO, HC, NOx for Trip.
Desired Speed is considered to be an average target (base) speed value which drivers aim to use on
a given road facility in the absence of all delaying factors. This corresponds to free-flow speed or
zero-speed concepts used in the literature, and is related to the quality and speed limit of the road
facility.
By default, SIDRA TRIP will determine the Desired Speed for each trip automatically as the
highest speed value during the trip but rounded to the nearest 5 km/h or 5 mph. If the highest speed
value is less than 5 km/h or 5 mph, the desired speed is 5 km/h or 5 mph.
To override the program determined value, the user may wish to specify a Desired Speed value as a
general default using Tools - Defaults - Speed Settings, or as an input value specific to a particular
trip using the Edit Profile - Speeds Settings input dialog.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.24 Akcelik & Associates Pty Ltd

Speed Efficiency Ratio and Congestion Coefficient

Speed Efficiency Ratio, re (ratio of Average Travel Speed to Desired Speed) and Congestion
Coefficient, rc (ratio of Desired Speed to Average Travel Speed) have been used in the literature as
parameters representing traffic performance:
re = vt / vd ( 4.4.15a )
rc = vd / vt ( 4.4.15b )
where
vt = Average Travel Speed (km/h or mph), and
vd = Desired Speed (km/h or mph).
Speed Efficiency Ratio is equivalent to the Travel Time Ratio, re = pT = Td / Tt used in Travel Time
Index (Equation 4.4.5), and Congestion Coefficient is related to the Speed Efficiency Ratio through
rc = 1/ re.

Highest and Lowest Speed

The Speed section of the Trip Statistics output includes Highest Speed and Lowest Speed values
(km/h or mph). These are determined from instantaneous speed values observed during the trip.
In the case of the Event Data method, the initial and final speed values for individual events, and
the Highest Speed and Lowest Speed values for the trip are given in the Event Characteristics table
of Event Statistics output.
The Acceleration graph in the Motion Graphs group shows the instantaneous values of
Acceleration (negative for deceleration) during the trip.
For detailed information on acceleration and deceleration models used in SIDRA TRIP (Event Data
method), refer to Akçelik and Besley (2001b).

Speed Groups
Trip Statistics output gives information on Speed Groups as specified in Edit Profile - Speed
Settings input dialog (or in Tools - defaults - Speed Setting). The information includes time spent
(seconds) in the speed range for each group, time per unit distance (s/km or mi/km) and the time as
a percentage of the total Travel Time.
The percent time in all Speed Groups should add up to 100 per cent. However, the sum of the
percentage values for Speed Groups may differ from 100 per cent due to rounding. Similarly, the
sums of the time values for Speed Groups may differ from the values for the trip (Travel Time in
the Trip Assessment section of Trip Statistics output).

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.25

4.4.3 Operating Cost and User Cost

The Cost results in SIDRA TRIP output may be the Operating Cost or User Cost depending on
the user choice (Section 3.7). The Operating Cost is appropriate for use in traffic management and
planning as a cost to the community, and excludes the tax component of the pump price of fuel.
The User Cost is appropriate for use by an individual or an operating agency as a cost including the
total pump price of fuel as well as any toll costs experienced during the trip.
Cost for Trip, Ct (in Cost Units, e.g. $) given in the Trip Statistics window is the total cost
incurred during the trip. For both Operating Cost and User Cost methods, the total cost includes
the vehicle operating cost (the resource cost or full cost of fuel and additional running costs
including tyre, oil, repair, maintenance, depreciation and various other running costs), and the time
cost to driver and passengers. The Cost model used in SIDRA TRIP is described in Section 3.7.
Cost Unit (e.g. $) is automatically determined by the Windows regional settings and cannot be
changed.
In the case of the Event Data method, Total Cost for each Event is given in the Cost, Fuel and
Emissions table of Event Statistics output.
Cost for Trip per unit distance, Ctx ($/km or $/mi) is determined from:
Ctx = Ct / Lt ( 4.4.16a )
where Lt is the Travel Distance (km or mi).
Cost per hour for Trip, Ctt ($/h) is determined from:
Ctt = 3600 Ct / Tt ( 4.4.16b )
where Lt is the Travel Time (seconds).
Desired Cost for Trip, Cd ($) is calculated for conditions of driving at constant Desired Speed.
This includes the Toll Cost when the User Cost method is used.
Excess Cost for Trip, Ce ($) is determined relative to the cost experienced if the vehicle travelled
in the cruise mode at the Desired Speed. This is calculated as the difference between Cost for Trip
and Desired Cost for Trip:
Ce = Ct - Cd ( 4.4.16c )
Desired Cost per unit distance, Cdx ($/km or $/mi) and Excess Cost for Trip per unit distance,
Cex ($/km or $/mi) are calculated in the same way as Cost for Trip per unit distance:
Cdx = Cd / Lt ( 4.4.16d )
Cex = Ce / Lt ( 4.4.16e )
where Lt is the Travel Distance (km or mi).
The Cost Total and Cost Time Rate graphs in the Cost Graphs group show the cumulative and
instantaneous values of Cost during the trip, respectively.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.26 Akcelik & Associates Pty Ltd

4.4.4 Fuel Consumption

Fuel for Trip, Ft (mL or gal) given in the Trip Statistics window is the total fuel consumed during
the trip. The fuel consumption model used in SIDRA TRIP is described in Section 3.8.
Vehicle parameters that influence the amount of fuel consumed by a vehicle can be specified in the
input dialogs under Edit Profile - Vehicles, or under Tools - Defaults - Vehicles (see
Sections 2.4.3 and 3.8.1 to 3.8.5).
In the case of the Event Data method, Total Fuel for each Event is given in the Cost, Fuel and
Emissions table of Event Statistics output.
Fuel for Trip per unit distance, Ftx (mL/km or gal/mi) is determined from:
Ftx = Ft / Lt ( 4.4.17a )
where Lt is the Travel Distance (km or mi).
Fuel per hour for Trip, Ftt (mL/h or gal/h) is determined from:
Ftt = 3600 Ft / Tt ( 4.4.17b )
where Tt is the Travel Time (seconds).
Desired Fuel for Trip, Fd (mL or gal) is calculated for conditions of driving at constant Desired
Speed.
Excess Fuel for Trip, Fe (mL or gal) is determined relative to the fuel consumed if the vehicle
travelled in the cruise mode at the Desired Speed. This is calculated as the difference between Fuel
for Trip and Desired Fuel for Trip:
Fe = Ft - Fd ( 4.4.17c )
Desired Fuel per unit distance, Fdx (mL/km or gal/mi) and Excess Fuel for Trip per unit
distance, Fex (mL/km or gal/mi) are calculated in the same way as Fuel for Trip per unit distance:
Fdx = Fd / Lt ( 4.4.17d )
Fex = Fe / Lt ( 4.4.17e )
where Lt is the Travel Distance (km or mi).
Output in the Fuel Consumption section of the Trip Statistics window also include Fuel Economy
for Trip (L/100km or mpg) and Desired Fuel Economy (L/100km or mpg) values. These are
determined from:
Ftx (L/100km)= 0.1 Ftx (mL/km) ( 4.4.17f )
ftx (mpg)= 1 / Ftx (gal/mi) ( 4.4.17g )
Fdx (L/100km)= 0.1 Fdx (mL/km) ( 4.4.17h )
fdx (mpg)= 1 / Fdx (gal/mi) ( 4.4.17i )

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.27

Note that Fuel Economy (mpg) in the case of US Customary Units is not a fuel consumption rate
per unit distance. The relationship between this (based on US gallons) and metric Fuel Economy
(L/100km) is given by:
fx (mpg) = 235.22 / Fx (L/100km) ( 4.4.17j )
The Fuel Consumption Total (mL or gal) and Fuel Consumption Time Rate (L/h or gal/h)
graphs in the Fuel Graphs group show the cumulative and instantaneous values of Fuel during the
trip, respectively. The Fuel Economy (L/100km or mpg) graph included in the same group shows
the instantaneous fuel economy values. Since these rates are very high for the metric fuel economy
(L/100km) variable when vehicle speed is low, a Maximum Metric Fuel Economy (L/100km)
parameter is used to set the largest value to be displayed in the Fuel Economy graph. You can
specify this parameter using Tools - Options - Output (click the check box and enter the desired
value).

4.4.5 Emissions (CO2, CO, HC, NOx)

The Trip Statistics window includes sections that give output statistics for CO2, CO, HC, NOx
emissions. The pattern of statistics is the same for each emission, and the relationships are similar
to the Fuel Consumption statistics. The word "Emission" and symbol E will be used in this section
to represent any one of CO2, CO, HC, NOx emissions.
Emission statistics are given in metric units only even when the US Customary Units are in use.
A mixed rate (grams per mile) is used for emissions per unit distance
Emission for Trip, Et (grams) given in the Trip Statistics window is the total Emission produced
during the trip. The emission model used in SIDRA TRIP is described in Section 3.8.
Vehicle parameters that influence the amount of emission produced by a vehicle can be specified in
the input dialogs under Edit Profile - Vehicles, or under Tools - Defaults - Vehicles (see
Sections 2.4.3 and 3.8.1 to 3.8.5).
In the case of the Event Data method, Total Emission for each Event is given in the Cost, Fuel and
Emissions table of Event Statistics output.
Emission for Trip per unit distance, Etx (g/km or g/mi) is determined from:
Etx = Et / Lt ( 4.4.18a )
where Lt is the Travel Distance (km or mi).
Emission per hour for Trip, Ett (g/h) is determined from:
Ett = 3600 Et / Tt ( 4.4.18b )
where Lt is the Travel Time (seconds).
Desired Emission for Trip, Ed (grams) is calculated for conditions of driving at constant Desired
Speed.
Excess Emission for Trip, Ee (grams) is determined relative to the emission produced if the
vehicle travelled in the cruise mode at the Desired Speed. This is calculated as the difference
between Emission for Trip and Desired Emission for Trip:
Ee = Et - Ed ( 4.4.18c )
Desired Emission per unit distance, Edx (mL/km or gal/mi) and Excess Emission for Trip per
unit distance, Eex (mL/km or gal/mi) are calculated in the same way as Emission for Trip per unit
distance:

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.28 Akcelik & Associates Pty Ltd

Edx = Ed / Lt ( 4.4.18d )
Eex = Ee / Lt ( 4.4.18e )
where Lt is the Travel Distance (km or mi).
The CO2, CO, HC, NOx Total (grams) and CO2, CO, HC, NOx Time Rate (kg/h) graphs show
the cumulative and instantaneous values of emission during the trip, respectively.

4.4.6 Noise

The Noise section in the Trip Statistics window gives the following statistics related to the noise
levels produced by the vehicle during the trip:
 Minimum Noise Level for the Trip, Lmin (dBA),
 Maximum Noise Level for the Trip, Lmax (dBA),
 Average Equivalent Noise Level for the Trip, Leq (dBA), and
 Average Equivalent Noise Level for a traffic stream, LeqT (dBA), which is based on the
specified flow rate of the traffic stream.

SIDRA TRIP estimates noise levels (dBA) generated during the trip using three different models:
 ASJ 2003 (Japanese) Model,
 SonRoad (Swiss) Model, and
 RLS-90 (German) Model.
For each model, noise levels received at a Fixed Receptor point and at a Relative Receptor point
are simulated. The Fixed Receptor is at a fixed location defined with reference to the start of the
trip. The Relative Receptor is at a constant distance from the vehicle, and moves with the vehicle.
The models to be used for generating noise output can be specified using check boxes in Tools -
Options - Output. The text output and graphs are given for selected models only.
Output statistics for various Noise levels are affected by vehicle type and various parameters
defining Receptor location (Section 3.6). The Flow Rate (veh/h) parameter is used for estimating
an Average Equivalent Noise Level for a traffic stream. These parameters can be specified using
Edit Profile - Noise Settings, or Tools - Defaults - Noise Settings.
In the case of the Event Data method, the minimum and maximum Noise levels for each Event are
given in the Noise Levels (dBA) - Fixed Receptor and Noise Levels (dBA) - Relative Receptor
tables of Event Statistics output.
The noise graphs (by model name) in the Noise Graphs group show the instantaneous noise levels
during the trip. The graphs are given either for Fixed Receptor or for Relative Receptor according
to the selection in Tools - Options - Output (Noise Graphs group).
General information about noise and parameters describing various traffic noise levels is given
below to help with understanding of SIDRA TRIP estimates of noise levels.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.29

General Information about Noise

Noise is unwanted sound. Since the sound generated by road traffic is generally unwanted, it is
appropriate to refer to it as traffic noise. However, vehicle noise gives a warning of vehicle's
approach and this is used by pedestrians, especially those with sight impairment.
The level of noise is measured using a sound level meter. This instrument mimics the operation of
the human ear which responds to minute pressure variations in the air. The pressure variations in
the air cause the eardrum to vibrate and this is heard as sound in the brain. The stronger the
pressure variations, the louder the sound is heard.
Sound pressure is the difference between the pressure in a sound wave and ambient pressure. The
instantaneous sound pressure is the deviation from the ambient pressure caused by a sound wave at
a given location and given instant in time. The effective sound pressure is the root mean square of
the instantaneous sound pressure averaged over a given interval of time.
The SI unit for sound pressure is the pascal (Pa = 1 Newton / m2).
A logarithmic decibel amplitude scale is used since the human ear can detect sounds with a very
wide range of amplitudes.
Since the ear is not as effective in hearing low frequency sounds as it is hearing high frequency
sounds, sound pressure levels are often frequency weighted so that the measured level will match
perceived levels (or subjective loudness of the noise) more closely. Several weighting schemes
exist. Environmental noise levels are most commonly expressed in terms of the "A-weighted"
decibel scale. A-weighted sound pressure levels are labelled dBA or dB(A).
Sound pressure level (SPL or Lp ) in decibels (dB) is given by:
Lp = 10 log10 (p2 / po2) = 20 log10 (p / po) ( 4.4.19a )
where
p = sound pressure (Pa),
po = a reference sound pressure which is usually taken to be the approximate threshold of
human hearing (20 µPa).
From Equation (4.4.19a):
Lp/10
p2 / po2 = 10 ( 4.4.19b )
Lp/20 Lp/20
p = po 10 = 0.00002 10 ( 4.4.19c )
The sum of the sound pressure levels from several sound sources is given by:
Lp = 10 log10 [n(pi2 / po2)] = 10 log10 [n(10Lpi/10)] ( 4.4.19d )
where
Lpi = sound pressure level for the ith source (dBA),
pi = sound pressure for the ith source (Pa),
n = summation for n sound sources.
Table 4.2 shows examples of sound pressure and sound pressure level values, and the
corresponding source and loudness descriptions. The quietest sound that humans can hear is
associated with a pressure value of approximately 20 µPa (micropascals) or a sound pressure level
of 0 dBA. Long-term exposure to a sound pressure level around 90 dBA can permanently damage
the ear. Sound levels in excess of 130 dB are more than the human ear can safely withstand and
can result in serious pain and permanent damage.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.30 Akcelik & Associates Pty Ltd

A rise of 10 dBA in sound level corresponds approximately to a doubling of subjective loudness.

For example, a sound of 70 dBA is twice as loud as a sound of 60 dBA.
When sound pressure levels from separate sources are added (Equation 4.4.19d), the maximum
sound pressure level tends to dominate. For example, adding 70 dBA, 60 dBA and 50 dBA, the
sound pressure level is found to be Lp = 10 log10 (1070/10 + 1060/10 + 1050/10) = 70.5 dBA.
Sound pressure decreases with distance from a point source (inverse function of distance).

Traffic Noise Parameters

There is a large number of parameters (noise indices) used in assessment of road traffic noise (e.g.
see AUSTROADS 2005, Homburger, et al 2001). For example:
 L1: The noise (or sound pressure) level in dB(A) that is exceeded for 1 per cent of a
specified time period.
 L10: The noise level in dBA that is exceeded for 10 per cent of a specified time period.
 L50: The noise level in dBA that is exceeded for 50 per cent of a specified time period.
 L90: The noise level in dBA that is exceeded for 90 per cent of a specified time period.
 Leq: Equivalent noise level in dBA as a constant continuous sound level that would
produce the same overall amount of noise (total sound energy) as the time-varying sound
level received at a receptor point over a given period of time.

Table 4.2
Examples of sound pressure and sound pressure levels (from various sources)

Sound pressure Sound pressure Loudness

Source of sound
(Pa) level (dBA)
200 140 Permanent damage
100 134 Threshold of pain
Loud thunder, Very loud (hearing damage due
20 120
jackhammer at 1.5 m to short-term exposure)
Jet engine, 100 m distant 6–200 110–140 Very loud
Discotheque 2 100 Very loud
Very loud (hearing damage due
Compressor at 15 m 0.6 90
to long-term exposure)
Passenger car (at 10 m) 0.02–0.2 60–80 Quiet to loud
Normal talking (at 1 m) 0.002–0.02 40–60 Very quiet to quiet
Very calm room 0.0002–0.0006 20–30 Very quiet
Whisper 0.0002 20 Very quiet
0.000020 0 Threshold of hearing (at 2 kHz)

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
SIDRA TRIP User Guide - OUTPUT 4.31

Traffic Noise Parameters Used in SIDRA TRIP

Minimum and Maximum Noise Levels for a Single Trip

The Minimum Noise Level (Lmin) and the Maximum Noise Level (Lmax) for a single trip as
received at a fixed receptor or relative receptor point are determined as the lowest and highest
values estimated from the simulation of vehicle trip.

Average Equivalent Noise Level for a Single Trip

The Average Equivalent Noise Level for a Single Trip (Leq) as received at a fixed receptor or
relative receptor point is calculated using instantaneous noise levels at all simulation intervals.

Average Equivalent Noise Level for a Traffic Stream

The Average Equivalent Noise Level for a Traffic Stream (LeqT) as received at a fixed receptor
point (specified by distance from the start of trip) is estimated using instantaneous noise levels and
allowing for the specified flow rate of the traffic stream (representing frequency of vehicles
passing the receptor point).

Minimum and Maximum Noise Levels for a Traffic Stream

The minimum sound level for a traffic stream, LminT would differ from Lmin for the single trip. The
maximum sound level for a traffic stream, LmaxT is the same as the value to for the single trip,
LmaxT = Lmax.

Different Vehicle Classes

To determine the average noise level for a traffic stream consisting of different vehicle classes,
SIDRA TRIP can be used to simulate a typical trip for each class using the flow rate (therefore
average headway) for each class. The following formula can then be used to calculate the
LeqT value for the mixed traffic stream:
LeqT = 10 log10 [n(10LeqTk/10)] ( 4.4.20a )
where
LeqTk = average equivalent noise level for kth vehicle class (dBA), and
n = summation for n vehicle classes.
For example, for light and heavy vehicle classes:
LeqT = 10 log10 (10LeqTLV/10 + 10LeqTHV/10] ( 4.4.20b )
where
LeqTLV = average equivalent noise level for light vehicles (dBA), and
LeqTHV = average equivalent noise level for heavy vehicles (dBA).
In this case, light and heavy vehicle flow rates (qLV, qHV in veh/h) would be used to determine
LeqTLV and LeqTHV.

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
4.32 Akcelik & Associates Pty Ltd

RESTRICTED DOCUMENT for use under SIDRA TRIP software licence only.
Thank you for choosing
SIDRA TRIP