Home

20110526 LATIS TMfS07 User Manual V4.3

1. LATIS Commission Development of Modelling Framework In August 2006 Transport Scotland commissioned MVA Consultancy to a Term Commission for the maintenance and enhancement of the Transport Model for Scotland TMfS and the accompanying Transport Economic and Land use Model of Scotland TELMoS A central element of the Commission was to develop and deliver an enhanced 2007 based land use and transport modelling system MVA proposed a hierarchical modelling framework with a single National Strategic Travel demand and Land Use Modelling framework as the upper tier Regional Travel Demand Models as the mid tier and detailed local models eg microsimulation as the lower tier The National Modelling Framework has now been developed It incorporates a number of technical enhancements and new and more robust data and replaces its predecessor TMfS TELMoS 05 On 6 November 2008 the TMfS Term Commission changed its name to Land Use and Transport Integration in Scotland LATIS The service is provided by Transport Scotland and their supporting consultants and offers a wide range of support and technical advice The LATIS service currently includes four distinct elements as follows a a user engagement programme consultations discussions and advice on a range of transport and travel planning issues the collection and provision of land use planning data the collection of transport data through the use of the Data Collection Contract and
2. Program Subway_BYO17 LIN a Runs Tram_BYO17 LIN es 7 a evo a Input Lines a Networks m M PoR Site Files Figure 5 1 PT Input File Directory Structure 5 3 3 Figure 5 2 illustrates an example of a PT service or lines file in a Cube network format and Figure 5 3 describes the PT service within a text editor Figure 5 2 PT Lines File in Cube Network Format mvaconsultancy TMfS 07 User Manual 5 5 5 4 5 4 1 5 4 2 5 5 5 5 1 5 5 2 5 5 3 5 5 4 RT 11 N 100357 100300 RT 23 N 100299 RT 28 N 100294 RT 33 LINE NAME 1006 LONGNANE NEWCRAIGHALL gt DUNBLANE MODE 3 OPERATOR 1 ONEWAY T CIRCULAR F HEADWAY 1 30 HEADWAY 2 30 HEADWAY 3 30 CROWDCURVE 1 1 CROWDCURVE 2 1 CROWDCURVE 3 1 SEATCAP 136 CRUSHCAP 190 LOADDISTFAC 100 CROWDCURVE 1 1 N 100344 100345 100346 100347 RT 2 N 100330 100320 RT 11 N 100348 RT 18 N 100349 100350 100319 100355 100307 RT 23 N 100357 100356 100301 RT 35 N 100389 RT 41 100296 100289 RT 46 N 100390 RT 49 N 100290 100391 100288 RT 56 N 100383 RT 65 N 100281 RT 69 N 100078 RT 78 LINE NAME 1007 LONGNAME EDINBURGH gt DUNBLANE manm AnrnarTsaned QUIT IT A See Figure 5 3 PT Lines File in Text Editor Format PT Intervention Coding Coding of a new scenario could include one or more of the following steps depending on the test being undertaken update network to
3. File Naming Description TIME time period ie AM IP or PM a LTIM time period ie A AM B IP or C PM E YEAR modelled year eg 7 11 and E LOOP demand model loop eg 1 5 5 6 2 Figure 5 4 illustrates the output file directory structure Figure 5 5 illustrates an example of an output assigned PT network in Cube mvaconsultancy TMfS 07 User Manual 5 8 5 PT Assignment Model TmMfso7_ 1 08 CD Base a Params Program Runs e 7 BYO Input Output a ACP Demand a Co Hw PnR PT B am Gr PM Telmos a a TESTO CTelmos 3 PT_COUNTS csv 3 FINAL_PT NET 3 LOADED_PT NET E NON_TRANSIT_LEGS NTL Name a TMf507_V1 08 Base a B Params Program Runs 8e 7 a Bo Input amp Output e Gace Demand a GHW OPR a PT am a GIP a PM Figure 5 4 PT Output File Directory Structure Figure 5 5 Example of Output PT Network File PT Network Volume Fields E AM_ON_OFFS_1 DBF E AM_RAIL_LOADINGS DBF AM_PT_ASSIGNED1 LIN 3 AM_PT_COMPCST1 MAT S AM_PT_IW_1 MAT S AM_PT_NWC_1 MAT S AM_PT_NWO_1 MAT 5 AM_PT_WKONLYTRIPS1 MAT pe TOTS LCY 3 AM_PT_ASSIGNED_1 NET AM_PT_ENUM NET 5 AM_PT_LOADED_1 NET a AM_PT_ASSIGNED PRN a AM_PT_ENUM PRN PTAM_BYOLACP71 PTM E PF total link passenger flow all user classes combined P
4. TMfS 07 User Manual 8 4 8 5 7 8 5 8 8 5 9 8 5 10 8 5 11 space In most circumstances these grids will be created in a mapping extent measured in British National Grid coordinates i e metres the coordinate system can be specified by the user Thirdly enter the grid height and width thus defining the area to be looked at Note that the cells are square but the grid does not necessarily have to be The fourth box allows the user to provide a name for the grid being created with the fifth and final box used to select the required projected coordinate system The final result will produce a grid such as that illustrated in Figure 8 5 which also illustrates the TMfS network in the background Untitled mxd ArcMap ArcView Ele Edt view Bookmarks Insert Selection Tools Window Help ee o e u E 3 iy Fi RAR 23 oy a W e e e Le Op 18 E da ten v G EB MR i EE Editor gt I Tas ZI raser A O B 2 QQx Eee Mok Onsen se BA sa a a 30 REVISED_BASE_NE K O Livingston amp Border 2 K y s i ad a 5 U Lu LE KA pees 5 AM_HY_LOADED_h lt gt J LEA M rade 3 e 2 me an KI ia
5. 3 2 7 The third page contains the keys required for the PT model P amp R model and the secondary post test analysis features These include a PT run on All Loops or First and Last Loops Only and Delete Route File switches and Lines Files locations a P amp R run on All Loops or First and Last Loops Only and P amp R Occupancy used in reporting only and E Post Run Analysis enables options for the user to exclude specific local authority areas and road link type from analysis There is a key for selecting emissions outputs in kilograms rather than tonnes and emissions per km rather than total emissions 3 3 On Screen Display 3 3 1 When the model starts up it will open the main Task Manager window If CLUSTER is being used the process also opens two or four Voyager windows depending on the number of processor cores on the PC and a Wait for Files window The Voyager windows display model progress for each of the cores The Wait for Files window keeps track of which processes are complete and waits until all necessary stages are complete before continuing to the next stage 3 3 2 There is a step at the end of the model that will close all the Voyager windows that are open 3 3 3 The various on screen displays are illustrated in Figure 3 3 mvaconsultancy TMfS 07 User Manual 3 4 EF Voyager l Input Script File Application Status Work Directory Catalog D C3713500_Forth_Replacement_Crossing_SupportiForth
6. Bus Tram Flow PCUs PM_Bus_Flow Average PM Peak hour 1700 1800 Bus Tram Flow PCUs LA Local Authority 1 to 32 See table 5 2 for equivalence list N A Distance Road Link Distance Kilometres CAP Road Link Capacity N A Speed Free Flow Road Link Speed km hr Link_Type Road Link Type See table 5 3 for equivalence list N A mvaconsultancy TMfS 07 User Manual 4 3 Attribute Link_Class Roadname Fare_Light Fare_Heavy TOID_S URBAN Trunk_Road One_Way Capind_V_C Bus_Corrid Toll_Light Toll_Heavy App_Rur_RB SCHEME SCHEME_CHA Description Road Link Class Road Name Ferry fare for Cars and LGVs Ferry fare for HGVs Shortened Topographic Object Identifier Type of geographical area road link is within 0 Rural 1 Small town 2 Suburban Area 3 Non Central Area 4 Central Area Set to 1 if the link is part of trunk road network 0 otherwise N A Set to 1 if the road link is one way 0 otherwise N A If volume of traffic on a link is greater than the capacity this N A attribute determines which Flow Delay relationship is applied 1 No junction 2 A node is junction 3 B node is Junction and 4 A node and B nodes are junctions Set to 1 if the Road link contains a bus lane 0 otherwise Toll for light vehicles Cars and LGVs Toll for heavy vehicles HIV s Set to 1 if the link is approaching a rural roundabout O otherwise Additional link relating to Do Minimum a
7. IFSC Dublin 1 Ireland T 353 0 1 542 6000 F 353 0 1 542 6001 Edinburgh Stewart House Thistle Street North West Lane Edinburgh EH2 1BY United Kingdom T 44 0 131 220 6966 F 44 0 131 220 6087 Glasgow Seventh Floor 78 St Vincent Street Glasgow G2 SUB United Kingdom T 44 0 141 225 4400 F 44 0 141 225 4401 Email info mvaconsultancy com Offices also in Bangkok Beijing Hong Kong Shenzhen and Singapore London Second Floor 17 Hanover Square London W1S 1HU United Kingdom T 44 0 20 7529 6500 F 44 0 20 7529 6556 Lyon 11 rue de la R publique 69001 Lyon France T 33 0 4 72 10 29 29 F 33 0 4 72 10 29 28 Manchester 25th Floor City Tower Piccadilly Plaza Manchester M1 4BT United Kingdom T 44 0 161 236 0282 F 44 0 161 236 0095 Marseille 76 rue de la R publique 13002 Marseille France T 33 0 4 91 37 35 15 F 33 0 4 91 91 90 14 Paris 12 14 rue Jules C sar 75012 Paris France T 33 0 1 53 17 36 00 F 33 0 1 53 17 36 01 Woking Dukes Court Duke Street Woking Surrey GU21 5BH United Kingdom T 44 0 1483 728051 F 44 0 1483 755207 Mvaconsultancy
8. Network Stats 3 5 2 This feature should be used with care and the user should ensure that all appropriate files are in place before selecting the relevant warm start point 3 6 Model Run Times 3 6 1 For the most efficient model run times users should make use of CUBE CLUSTER software which allows the utilisation of multiple processor cores Approximate run times for the model are a highway model assignment 45 minutes per time period a PT model assignment 4 hours per time period and a full demand model P amp R Road and PT Assignment Run 20 hours approx 3 6 2 Note that run times for the inter peak assignments will be lower than those described here mvaconsultancy TMfS 07 User Manual 3 7 3 6 3 These model run times were realised using a quad core PC and a four node cluster licence The model specification reflected four inner loops and five external loops of the demand model 3 6 4 The CUBE CLUSTER software allows all three time period assignments to run simultaneously if connected to multiple processors Therefore for a road or PT assignment all time periods can be run in the same time as for one assignment The road and PT assignments are automatically run simultaneously during the demand model if using Cluster mvaconsultancy TMfS 07 User Manual 3 8 Road Assignment Model 4 1 Overview 4 1 1 This chapter describes the operation of the Road Assignment Model and will cover necessary input and output f
9. V3_1 V4_1 V5_1 1 9 Bus flows can also be added to the total vehicles if required the bus vehicle flows are in the volume fields AM_BUS_FLOW IP_BUS_ FLOW and PM_BUS_FLOW Emissions The Carbon and CO2 e emissions from a network are output after a road assignment or a demand model run The annualised files with emissions by link are output to the following location Drive TMfSO7_ Version Runs Year Test Output Scenario HW ENEVAL ALL_ANN_ALL CSV Note There are also files with emissions by link for each time period These emissions can then be attributed to the network by joining the A and B nodes If required these emissions can be converted to emissions per unit distance by dividing by the DISTANCE volume field Accidents Accidents by type are output from road assignment or a demand model run to the following location Drive TMfSO7_ Version Runs Year Test Output Scenario HW ACCDNT ANNUALISATION_BY_LINK CSV In a similar way to emissions these can be joined to the network using the A and B nodes Other attributes on the network for example vehicle time and vehicle kilometres can also be mapped but the three described above will be the most common Method to map these to the Grid To select the cells from the grid for thematic mapping i e those that intersect the network the select by location tool should be used from the Selection menu see figure below Select the features from the grid
10. test5 shp FR FRN Pa an mc gt H a4 ai zones y l TZ AT q a on i M Background Scot 2 BY ae Fa WAR A ak OD it a oF te Sat LE Er E A A i r om gt LL gt og ee CH A hae Ae 3 GT OE k AS Noaned Las am S AN f gt eae ae ail oe os td LA ER 3 A A A J al hel KE A 3 i FT 2 CA T B Y STE AY TE Display Selection jeu au a RE See is J 4 f Drawing RC 2 vy AY w Br uj Aw r ver 244274 58 673078 673 Meters ELA EC EEE Figure 8 5 Example Grid created by Fishnet Once the grid and the TMfS 07 network have been opened in ARCMap the network attributes can then be prepared for mapping Congestion The output TMfS Network contains both free flow speed in the volume field SPEED and the congested speed in the field CSPD_1 Using the volume field DISTANCE the congestion per vehicle on each link can be calculated in a new volume field using the formula CONG_PER_VEH DISTANCE 1 CSPD_1 1 SPEED mvaconsultancy TMfS 07 User Manual 8 5 8 5 12 8 5 13 8 5 14 8 5 15 8 5 16 8 5 17 8 5 18 The model contains individual user class PCU flows in volume fields V1_1 V2_1 V3_1 V4_1 and V5_1 These are for Car In Work Car Non Work Commute Car Non Work Other LGV and HGV respectively These volume fields can then be used to get total time lost to congestion using the formulas below TOTAL_CONG CONG_PER_VEH V1_1 V2_1
11. 0 12084526272 100 3600 1 0 0 70004 700 12 0 25 0 3 1800 2 0 0 0 0 5 59061549152 100 3600 1 0 0 70003 700 13 0 25 0 3 1800 2 0 0 0 0 6 60187125928 100 3600 1 0 0 70012 70 14 0 25 0 3 1800 1 0 0 0 0 0 49889598370 83 1800 1 0 o 70006 700 15 0 25 a 1800 1 0 0 0 0 0 04087164396 83 1800 1 0 0 70007 700 16 0 25 0 3 1800 1 0 0 0 0 0 1870519398734 83 1800 2 0 0 70008 435 17 0 25 0 3 1800 1 0 0 0 0 0 123942134704 83 1800 2 0 0 43504 700 18 0 25 0 3 1800 1 0 0 0 0 005013245226 83 1800 1 0 0 70008 700 19 0 25 0 3 1800 1 0 0 0 0 0 05003933828 83 1800 1 0 0 70009 700_ 20 0 25 0 3 1800 1 0 0 0 0 007184461785 83 1800 1 0 0 70010 700 21 0 25 0 3 1800 1 0 0 0 0 0 37204194172 83 1800 1 0 0 70010 700 22 0 25 0 3 1800 1 0 0 0 0 091162046421 83 1800 1 0 0 70006 700 23 0 26 0 3 1800 2 0 0 0 0 7 07132769364 100 3600 1 0 0 70011 700 24 0 2 0 3 1800 2 0 0 0 0 6 45480174987 100 3600 1 0 0 70032 700 25 0 25 0 3 1800 2 0 0 0 0 0 55863417097 100 3600 1 0 0 70013 700 26 0 25 0 3 1800 2 0 0 0 0 0 32311648494 100 3600 1 0 0 70012 435 27 0 25 0 3 1800 2 0 0 0 0 0 24216124600 100 3600 1 0 0 43507 700 28 0 2 0 3 1800 2 0 0 0 0 051396251023 100 3600 1 0 0 70031 700 29 0 2 0 3 1800 2 0 0 0 0 0 51285142992 100 3600 1 0 O 70037 700 30 0 26 0 3 1800 2 0 0 0 0 0 2607 1490858 100 3600 1 0 0 70031 700 31 0 26 0 3 1800 2 0 0 0 0 0 04093430555 100 3600 1 0 0 70033 700 32 0 26 0 3 1800 2 0 0 0 0 0 21701830662 100 3600 1 0 0 70034 700 33 0 26 0 3 1800 2 0 0 0 0 0 224143586510 100 3600 1 0 0 70
12. File omor omo1_16 e omo1_21 s RCO C3 RCOI_16 RCO121 S C Remove Non Stope A Schemes D C2 Params Program 8 Runs Temp Figure 4 12 Location of the PT Lines Files Using the Cube Network Window 4 4 22 The model Do Minimum and Reference Case Prelim networks can also be altered using the standard network building features within the Cube Network Window If using this method the new Prelim network should be linked into modules 5 6 7 and 8 of the network building process in order to include the PT preloads to the updated network All Do Minimum and Reference Case radio buttons should be switched off as these changes will already be included within the updated network 4 4 23 Following these network changes the PT lines file may also require updating The output will be a Do Minimum or Reference Case scenario plus relevant test scheme changes 4 5 Secondary Analysis 4 5 1 There are three main types of secondary analysis available to the model user including a Select Link Analysis E Sub Area Analysis and Travel Cost Skims 4 5 2 Select link analysis and sub area analysis both take place in a separate standalone catalog titled the Secondary_Analysis_V1 0 cat The Secondary Analysis Catalog 4 5 3 This catalog can be stored anywhere on a PC hard drive and files linked in via catalog key to the national model It consists of two applications which are
13. HGV_Speeds_V1 dbf This file should not be altered by the user and is located in the Params folder a Random sampling of willingness to pay Tolling _Model_V1 dbf This file should not be altered by the user and is located in the Params folder a travel demand matrix eg HYAM_BYO1ACP71 HWM which is produced by the demand model in forecast years and a prelim network eg BYO17_ALL NET which the user should prepare Travel Demand Matrix 4 2 2 The AM Inter and PM peak hourly travel demand matrices eg HYAM_BYO1ACP71 HWM contain origin and destination traffic demand for each of the five vehicle classes Matrix units are described in Passenger Car Units pcus and matrix files can be viewed using CUBE 4 2 3 Travel demand associated with each user class is contained in separate tables as follows E Table 1 Total users although not used in assignment is useful for analysis E Table 2 car in work single occupancy E Table 3 car in work high occupancy E Table 4 car non work commuter single occupancy a Table 5 car non work commuter high occupancy Table 6 car non work others single occupancy Table 7 car non work others high occupancy El Table 8 LGV and a Table 9 HGV mvaconsultancy TMfS 07 User Manual 4 2 4 2 4 The high occupancy vehicle matrix tables are currently empty and are included for forward compatibility if HOV modelling is included in future The file naming convention associated with t
14. PowerPoint NOOK 10 12 Figure 4 5 The Network_Build cat Window with Six Scenario Options mvaconsultancy TMfS 07 User Manual 4 10 9 File Scenario Edit View Data Program Control Functions Application Group Settings Run Utilities Other Apps Window Help SReSeEa KEE sivie ri X tit a Stage Build rs aS Script File Stage2 Build Fe Link Net 1 p jii Link Net 2 BS Link Net 1 mn Link Net 3 B Link Net 2 RCO1 _11 ARCS DMO1_16 Link Net 4 P Link Net RCO1_16 Link Net 5 B Link Net 4 DMO1_21 Link Net 6 BS Link Net 5 RCO1_21 Link Net 7 B Link Net 6 Link Net 8 Link Net 7 Link Net 9 BS Link Net 8 Applications Link Net 10 S Ne WS Link Net 9 Netwvork_Build Node File 2 Node File 3 Node File 4 Node File 5 Node File 6 Node File 7 Node File 8 Node File 9 Node File 10 Figure 4 6 Standard Network Build Scenarios double click the relevant scenario enario pu pplication Network_ Name DMO1_11 Scheme 1 in place 1 in place Co od Scheme 2 in place 1 in place co od Scheme 3 in place 1 in place co od Scheme 4 in place 1 in place co od Scheme 5 in place 1 in place co od Scheme 6 in place 1 in place co od Scheme 7 in place 1 in place eo mi Scheme 8 in place 1 in place 0 od Scheme 9 in place 1 in place co od Cancel N
15. a travel demand and land use modelling suite The TMfS 07 and TELMoS 07 models are designed to deliver the fourth of these elements This document details how to operate the TMfS 07 National Model it describes the use of the Road Model the Public Transport Model the Demand Model and the Park and Ride Model mvaconsultancy TMfS 07 User Manual i Introduction 1 1 Model Background 1 1 1 In 2008 MVA Consultancy was commissioned by Transport Scotland to create an enhanced version of the Transport Model for Scotland TMfS This new National Model TMfS 07 is a multi modal model covering Scotland s strategic transport system and sits at the top of a model hierarchy with more detailed regional models below TMfS 07 contains the following components E Road Assignment Model E Public Transport PT Model Demand Model and Park and Ride Model 1 1 2 TMfS 07 is calibrated to a 2007 base year with standard forecast years of 2012 2017 2022 2027 and 2032 1 1 3 Planning data collected from local authorities forms the basis of the TMfS 07 forecast year data This data is input to the Transport and Economic Model of Scotland TELMoS and used to generate future year traffic and travel forecasts within the National Model 1 1 4 Further information regarding the development and calibration of TMfS 07 is provided in the model development reports which are available on the LATIS Website 1 2 Conditions of Use 1 2 1 TMfS 07
16. and E Network Build will then build and assign bus pre loads saving the output files into the relevant scenario directory eg Network Build Base DM01_11 Cube Licensed to MVA Consultancy Network Build app Network Build Scenario DMO1_11 Catalog Network_Build cat SJ File scenario Edt View Data Program Control Functions Application Group Settings Run Utilities Other Apps Window Help 36688 KB D ses Network_Build cat Scenarios Base DMot_41 RCO114 MO1_16 gt 2 Stage2 Build Fe Link Net 1 gt Link Met 2 ETAPE 2 2 F RES RCO1_16 DM0 _21 RCO1_21 ge ag lo Node File 3 Node File 4 Node Fie 8 Node Fie 9 Data S Inputs Outputs 1 Reports Node Fie 4 Node File 7 Bi Node Fis 10 ETES Staged Build Final Network gt ET Value a 2 22 E HE w ols PAP ele ele all pmo1_11 2t E F D Zz 2 LA gt Locally linked input file gt gt Public File Build final network with bus pre loads gt gt External linked input file gt gt Line File 1 Script File o Scenario Specific File DEEE wa PELLE pa D gt eration specific fe DEEE TRE ss K D Fie name cludes a Catalog Key gt System File 1 ea ENa Dre amp D gt Script file references a Catalog Key gt LAM Bus Flows for Pre Load Script File F eto bl D Novell Groupwise M CD TMFS 07 PT Andy c37136_1mFS 07_Us ET E Microsoft
17. and Ride Site File and some of these files can be altered by the user when coding up or testing a transport or policy intervention mvaconsultancy TMfS 07 User Manual 3 1 Model Output Files 3 1 5 All model output files are located in Runs Year Scenario Output which is then split into Demand HW Road Highway PT and PnR Park and Ride The required output folders are created automatically at the start of a model run 3 1 6 The key outputs from each stage are as follows a Demand Model Outputs final loop generalised cost matrices GCM and from home FHS to home THS and non home based NHS trip matrices assignment matrices for road and PT models HWM and PTM respectively which are placed in the road and PT output folders for convenience a Road Model HW Outputs Split into AM IP and PM final loop traffic cost skims MAT and Assigned Network HWN The Road Output directory also contains secondary analysis files including ENEVAL applied for environmental analysis ACCDNT applied to undertake road traffic accident analysis and Network_Stats applied to extract road traffic statistics csv format E Public Transport PT Model Outputs final loop travel cost skims composite costs PTS assigned network and passenger loading file PTN and database of passenger boardings and alightings Dbf Park and Ride P amp R Model Outputs fr
18. associated with the link and E Scheme provides linkage to the transport scheme associated with each link mvaconsultancy TMfS 07 User Manual 4 13 4 4 13 Remove nodes DBF when adding in new schemes it is often necessary to delete links and nodes from original network to allow the new replacement schemes to replace them These deletions can be undertaken automatically by adding them into the network build using a DBF then referring to them in the scripting This Remove Nodes DBF lists the nodes that need to be deleted for each scheme using the following three fields N the node number to be deleted SCHEME_DEL this flags the nodes that should be deleted for the relevant scheme and a REMOVE a flag 1 to be used in scripting to execute the delete 4 4 14 Remove links DBF in the same way as nodes are deleted links can also be flagged using this DBF to ensure that they are deleted following the introduction of a new scheme The DBF follows a similar structure to that described for the remove nodes file 4 4 15 Change links DBF in some instances rather than adding and deleting links for new schemes it is easier to simply modify existing links For example the part of the M80 completion project involves upgrading the A80 to motorway status As such it is only the attributes of the links that need to be updated without editing any network distances or structure This can be achieved t
19. directory structure of the AM peak hour travel demand matrix file mvaconsultancy TMfS 07 User Manual 4 5 TMfS07_V1 08 Z HYAM_BYO1ACP71 HWM O Params Program B Runs B 7 svo Input O Lines Networks Highway O PnR_Site_Files Output ace Demand Hw am Or pm pre pt Figure 4 3 File Location of the AM Peak Hour Travel Demand Matrix 4 2 12 The model directory structure described above must be followed in order to operate the road model assignment successfully 4 3 Road Model Output Files 4 3 1 There are four main output files associated with the Road Assignment Model including AM_REPORT PRN text file containing convergence statistics by iteration This file can be viewed using text editors such as Textpad or Notepad E AM_PRINTFILE text file containing assignment control parameters as defined in the road model assignment script and convergence statistics by iteration a AM_HY_LOADED_NET NET final assigned network This file can be viewed using Cube and a HYAM_BYO1ACP71 HWM hourly demand matrix containing origin destination demand for each of the eight user classes as well as a total Units are in pcus and this file can be viewed using Cube Directory Structure of Required Output Files 4 3 2 Figure 4 4 illustrates the typical AM peak hour road model outputs for the base year model mvaconsultancy TMfS 07 User Manual 4 6 3 TMFs07
20. in each scenario s relevant directory structure and can be updated as required 4 4 6 Schemes 1 26 represent the current November 2007 set of Do Minimum and Reference Case scenario specified interventions Schemes 27 30 can be used to add in any additional schemes that may be required for testing A lookup table for the number associated with each scheme is contained in the scheme code numbers xls spreadsheet mvaconsultancy TMfS 07 User Manual 4 9 4 4 7 The necessary steps to alter the existing Do Minimum and Reference Case networks within the Network Build application are described below open the Network Build catalog in Cube Voyager in the catalog under scenarios click the sign to expand Base E the six standard forecast year scenarios should now appear as shown in Figure 4 4 a double click on the scenario required and a window will appear with a number of radio buttons in it as shown in Figure 4 5 and Figure 4 6 the radio buttons are set to the default position for the standard Do Minimum and Reference Case scenarios the input lines files are specified on the last page of the window Figure 4 7 and also setup for the standard scenarios This is where modified PT lines should be included as inputs Figure 4 8 turn a scheme off or on by selecting a different radio button and run the network build application click run
21. is that the required input files do not exist cannot be found By opening the model run print file the user can identify the location where the model has failed Checking the appropriate program print file should enable the user to identify the missing files Print files are located in the model output directory and the most recent files can be identified by sorting by Date Modified Note that the error may not always be within the most recent print file Note that when setting up a new scenario if the user changes the Code box to be consistent with the scenario ID then this code should appear in the main print file s name The missing file issue is most likely to occur when restarting a model run as the necessary files may have been deleted in a previous step In this scenario there are two further options If the file exists elsewhere copy it across to the relevant location or start the model run from the stage prior to the missing file being created The user will be able to identify the required file from the relevant print file Miscellaneous If the model fails with a run time error or hangs it could be due to the PC running out of disk space Check the disk space if there is little space remaining free some disc space and rerun the model If the PC hangs or does not produce any output files then check the PC to make sure it has a CUBE dongle connected to it It may also be that some of the files in the
22. select Polygon gt New and proceed to draw the polygon Once the shape turns orange it is finished The second method is similar except allows importing of a pre existing shape say a local authority region for instance Select the layer control icon and open your chosen boundary file Once loaded select Polygon gt copy from boundary layer and then click on the boundary layer until it turns orange Next select Polygon gt subarea extraction and select a location to save the new sub area file Finally some choices are available to specify zone conversion between the parent network and the sub area network Itis highly recommended that you keep existing zones the same number and start new external to the sub area region zones above any existing parent network zones and outwith the range of regular node numbers of the parent network This allows for much easier matching between matrices networks Once you have created your sub area network then link it to the application via catalog key subarea network and run the application The output is a subarea matrix with the same user classes as the road assignment model excluding high occupancy car Travel Cost Skims The Road and Public Transport Models can be used to generate travel cost skims matrices which describe the modelled travel cost to travel between each zone These outputs can be used as an input to economic appraisal software such as TUBA Public Transport Travel Cost Skims are creat
23. the accuracy reliability and completeness of the information and no responsibility is accepted to any third party for the whole or any part of its content No part of the contents nor any reference thereto may be included in any published document circular or statement nor published in any way without Transport Scotland and MVA Consultancy s prior written agreement of the form and context of such text 1 3 User Support 1 3 1 The Transport Scotland agreement with MVA Consultancy can include the provision of the installation of TMfS 07 an Operator s Manual training and support via telephone and e mail 1 3 2 For further information regarding LATIS please visit the website at www latis org uk or by contacting the LATIS team via E Alison Irvine Transport Scotland Project Manager Tel 44 0 141 272 7590 Em il Alison Irvine transportscotland gsi gov uk or Kevin Lumsden MVA Consultancy Project Manager Tel 44 0 131 240 8918 Em il Klumsden mvaconsultancy com 1 3 3 Support specific to the CUBE VOYAGER software modules can be obtained under a separate CUBE User Licence Agreement with Citilabs 1 3 4 The purpose of this User or Operator s Manual is to familiarise the user with the structure and application of TMfS 07 so that the user can prepare and implement model appraisals 1 3 5 It is assumed that the user is familiar with both the principles and operation of the CUBE software suite and has a sound understand
24. the installation of VOYAGER 5 02 It also requires an update to the Public Transport package Route Enumeration stage VOYAGER 5 03 Beta It is highly recommended to obtain CUBE CLUSTER four nodes to enable the most efficient model performance and reduce run times 2 3 Installing TMfS 07 2 3 1 The following requirements are necessary for the model to function correctly the model can be installed on a local hard drive usually the C or D drive E the model files can be copied from a DVD and are over 4 GB in size a DualCore exe and Close_Voyager exe should be located in C BAT The user will require administrative rights on the computer for these programs to function appropriately a resource files for these programs should be located in the following directory structure C program files Citilabs Cube Resource User a the amended MATRIX RSC file should also be located in the C program files Citilabs CubeVoyager Resource directory structure and ptprocesses dil PT dil and PT TDF should be located in the C program files Citilabs Cubevoyager directory structure 2 3 2 These programs and files will be supplied as part of the installation A member of the LATIS support team can be made available to assist with the installation procedures mvaconsultancy TMfS 07 User Manual 2 1 Model Operation 3 1 3 1 1 Model and File Directory Structure The file directory structure is similar to that used in previou
25. 037 700 34 0 26 0 3 1800 2 0 0 0 0 0 03721598617 100 3600 1 0 0 70036 700 Figure 4 9 Example DBF file Representing Additional Links Required for a Scheme 4 4 11 Scheme Node DBFSs if a new scheme requires additional nodes to those in the base network they are added using a node DBF This should follow the format of the node DBFs used to add other schemes The key fields that must be completed include X and Y the coordinates British National Grid of the nodes calculated from GIS or by other means N represents the node number which must be a number that is not already used as a node in the base or in other scheme nodes DBFs and E Scheme this represents the scheme code number to which these new nodes should be associated with to allow network changes to be easily edited in the script file Currently numbers 27 30 are available for use 4 4 12 Scheme Link DBFs the new road or rail links are added using link DBFs The base network link DBF contains numerous fields but when adding a new scheme DBF only the following fields are mandatory for road network links E DISTANCE the length of the link in kilometres a SPEED the free flow speed on the link km hr CAP the capacity of the link a REV whether the link is one way 1 or two way 2 E A and B the A node and B node of the link E LINK_CLASS linking to the speed flow curve
26. 100303 5 0 1 0 0 0 0 0 0 o 0 13 9 1009 5 0 25 i 67 0 0 02 0 26 0 28 2 13 241 1445264 14 10 1010 5 0 28 1 1388 0 01 0 04 0 6 0 65 4 93 5 58 33533 58 15 11 1011 5 0 24 i 73 0 0 02 0 29 0 31 2 38 269 16152 45 16 12 1012 5 0 57 1 28 11 0 03 0 16 2 48 2 68 20 34 2301 138250 97 17 13 1013 5 0 28 1 1065 0 01 0 03 0 46 05 3 78 428 25730 02 18 13 1913 5 0 28 1 481 0 0 01 0 21 0 22 1 71 193 11620 79 19 14 1014 5 0 48 1 0 78 0 0 0 06 0 06 0 48 0 54 3230 49 20 15 1015 5 0 56 1 169 o 0 01 0 15 0 16 12 1 36 8165 96 21 15 4132 5 0 56 1 134 o 0 01 0 12 0 13 0 95 1 08 6474 78 22 15 4138 5 0 56 1 554 0 01 0 03 0 48 0 52 3 94 4 46 26768 88 23 15 9015 5 0 56 1 606 0 01 0 03 0 53 0 57 431 487 29281 49 24 15 100307 5 0 1 0 o 0 0 0 0 0 0 25 16 1016 5 0 76 118 o 0 01 0 21 0 23 1 74 196 11803 71 26 17 1017 5 0 51 1 11 03 0 01 0 06 0 87 0 94 7 14 8 08 48537 59 27 17 9017 5 0 51 1 20 47 0 02 0 1 1 62 174 13 25 1499 90078 37 28 18 1018 5 0 29 1 13 47 0 01 0 04 0 61 0 65 4 96 5 61 33705 29 29 19 9019 5 0 56 1 5382 0 06 03 4 87 5 03 38 25 43 29 260054 4 30 20 1020 5 1 03 1 139 0 0 01 0 22 0 24 1 82 206 12353 34 Figure 8 2 ACCDNT Example Output The hourly files can be annualised to reflect annual accident levels The accident procedure does not include accidents associated with buses Intra zonal vehicle movements are also excluded from the accident analysis procedure Environmental Analysis Environmental analysis is undertaken using the ENEVAL proc
27. 16 07 2010 09 15 16 07 2010 09 08 14 01 2010 10 04 14 01 2010 10 04 06 05 2008 11 15 02 09 2008 08 49 12 05 2008 11 06 19 05 2008 16 44 12 05 2008 11 15 18 01 2010 14 54 18 01 2010 14 54 06 05 2009 12 39 28 12 2008 20 59 24 10 2008 10 11 16 07 2010 09 08 06 05 2009 12 38 28 12 2008 20 59 24 10 2008 10 11 16 07 2010 09 09 18 01 2010 14 18 13 08 2010 10 13 18 01 2010 13 19 3 1 2 The directory structure is used to separate model inputs and output files and different model test scenarios Note that the model structure can now accommodate four digit test ID s although due the Voyager Software a test ID cannot start with a number TMfS 07 Catalog 3 1 3 The TMfS 07 Voyager Catalog is used to operate the model running procedure This file is located in the top level folder and named TMfSO7 cat Model Input Files 3 1 4 There are two main sets of model input files which include a Demand Model Inputs these files are located in Runs Year Demand Growth these files consist of Trips Ends Mode Specific Constants Generalised Cost Matrices and Add In matrices A description of these files is contained in Chapter 6 and generally these files are fixed for each forecast year scenario Assignment Model Inputs these files are located in Runs Year Test ID Input these files consist of public transport PT input files ie PT service or lines files factors system files etc road network and the Park
28. CIW_TLL car in work average toll 4 5 20 Note that this cost matrix file from a typical road assignment run will be empty This file will be populated only if the skim Catalog key is set to Y mvaconsultancy TMfS 07 User Manual 4 19 PT Assignment Model 5 1 Overview 5 1 1 This chapter provides an overview of the Public Transport PT model and describes the model input files the coding of new tests the PT model assignment procedures and the model output files The procedure for running the PT model is described in Chapter 3 5 1 2 The PT Assignment Model is used to E undertake route choice a produce travel costs for the Demand Model and the Park and Ride Model and a produce travel costs and passenger flows for operational and economic appraisals of Public Transport interventions Public Transport Model Dimensions 5 1 3 The TMfS 07 PT model has been developed using the Citilabs Cube Voyager software and requires an update to the Public Transport package Route Enumeration stage VOYAGER 5 03 Beta The model dimensions are as follows a three hourly time periods AM peak 0800 0900 inter peak 1 6 of 1000 1600 PM peak 1700 1800 E multi class assignment with three user classes in work commute non work other E six modes urban bus inter urban bus rail subway ferry tram a distanced based fares structure and a rail crowding in AM and PM peaks 5 2 PT Model Proces
29. DBFs can also be included The schemes and connectors DBFs are all located within the Schemes folder as shown in Figure 4 10 mvaconsultancy TMfS 07 User Manual 4 14 2 rs507_v1 08 Base Networkbuild O 07 Base Network O Base L Network change files C2 Rail Schemes IO Scheme connectors D Trams C2 Params C2 Program Runs E Temp TRAINING O Voyager Examples Printers and Faxes A GHighway Schemes Rad Schemes E Scheme connectors Trams K scheme code numbers xls File Folder File Folder File Folder File Folder Microsoft Excel Wor Figure 4 10 Directory Location of Scheme and Connector DBFs 4 4 18 The remove nodes remove links and change links DBFs are added in module 4 These should be updated to include any additional deletions or changes required for the user s schemes The current versions of these files can be found in the network change files folder as shown in Figure 4 11 3 TFS07_v1 08 E change links dbF CD Base B remove links dbF Networkbuid B remove nodes dbf LI 07 Base Network C2 PT lines C2 Schemes Params O Program D CD Runs Temp E TRAINING E Voyager Examples Printers and Faxes 2 gh workgroup a 9 Web Client Network 2 D drive on Jeff Davidson Edinburgh Cr5052 2 Don CRS0S3 Stephen Canning CrS0S3 Figure 4 11 Location of the Changes DBF Files 4 4 19 Providing
30. E microsoft PowerPoint I TR Task Monitor FORT Figure 3 5 Unsuccessful Completion of Model Test Display mvaconsultancy TMfS 07 User Manual 3 6 3 4 Undertaking Multiple Model Testing 3 4 1 Using CUBE multiple model test scenarios can be undertaken simultaneously Once the scenarios are set up pressing F2 will display the scenario selection menu A user can then select the relevant scenarios to run Clicking run will start the first test scenario 3 4 2 Note that if the first model should fail for any reason then the Application Manager will skip to the next scenario selected However if cluster has been selected then the subsequent runs may fail if it is unable to close existing processor controls 3 5 Re Starting the Demand Model 3 5 1 A demand model test run can be re started or warm started from a number of different points This includes any outer loop between one and the maximum set by the Demand Loop key Potential warm starting points include start default value demand model All and IP SOV HOV split used during high occupancy vehicle modelling only E P amp R model E reverse factoring process Creation of To Home and Non Home based trips a assignment prep period to hour factoring and add ins E highway assignment ALL IP and PM a PT assignment ALL IP and PM E generalised cost calculations E trip frequency E macro time of day and E post run analysis ENEVAL ACCDNT
31. F1 in work passenger flow business travel ia PF2 commute passenger flow home based work m PF3 other passenger flow home based other shopping education leisure and a WF walk flow all user classes mvaconsultancy TMfS 07 User Manual 5 9 Demand Model 6 1 6 1 1 6 2 6 2 1 6 2 2 6 2 3 6 2 4 6 2 5 6 2 6 Overview This section describes the required input files to the TMfS 07 Demand Model and the files created by the demand model process Demand Model Options The Demand Model includes the following components E mode choice a destination choice a Park and Ride a trip frequency and macro time of day choice and a high occupancy vehicle modelling Mode and Destination Choice The choices of mode and destination are integral to the Demand Model and therefore these elements are combined within the default demand model process Park and Ride Park and Ride is also a central component within the Demand Model but elements of Park and Ride such as new sites additional parking capacity can be altered by the user The Park and Ride Model is discussed further in Chapter 7 Trip Frequency and Macro Time of Day The model allows the user to use if the Trip Frequency and Macro Time of Day components are used These options are not used in the default setting but can be switched on by selecting the appropriate radio button High Occupancy Vehicle The demand model contai
32. Land Use and Transport Integration in Scotland LATIS Transport Model for Scotland mvaconsultancy Document Control Project Title Land use and Transport Integration in Scotland LATIS MVA Project Number C37136 00 Document Type User Manual Directory amp File Name H Contracts Live C3713600_TMfS Update Report User Manual 20110526 LATIS C37136 TMfS07 User Manual V4 3 Doc Document Approval Primary Author Chris Robinson Other Author s Matthew Pollard Graham Bell Andrew Bagnall Andrew Weir Chris Cullen Reviewer s Jeff Davidson Formatted by Nicola Milne Distribution Date Distribution Comments 24 02 2009 Chris Robinson Internal Review 08 05 2009 Jeff Davidson Internal Review 13 05 2009 Transport Scotland 1st Release Version 28 04 2011 Jeff Davidson Updated Release Version for Internal Review 28 04 2011 Transport Scotland 2nd Release Version 1 Introduction 1 1 1 1 Model Background 1 1 1 2 Conditions of Use 1 1 1 3 User Support 1 2 1 4 User Manual Structure 1 3 2 Setup and Installation 2 1 2 1 Hardware Requirements 2 1 2 2 Software Requirements 2 1 2 3 Installing TMfS 07 2 1 3 Model Operation 3 1 3 1 Model and File Directory Structure 3 1 3 2 Operating the Model 3 2 3 3 On Screen Display 3 4 3 4 Undertaking Multiple Model Testing 3 7 3 5 Re Starting the Demand Model 3 7 3 6 Model Run Times 3 7 4 Road Assignment Model 4 1 4 1 Overview 4 1 4 2 Road Model Input Files 4 2 4 3 Road M
33. RC scenario a Create bus and tram preloads the process then creates bus and tram pre loads which describe the number of PT services using each link in the network These preloads are based on the PT service coding lines file and are added into each specific scenario using modules 5 AM peak 6 inter peak and 7 PM peak and Build final network Module 8 then builds a final scenario specific DM or RC network by combining the outputs from the PT pre load modules and the network structure for each scenario created from module 4 Output network files are automatically stored in the relevant scenario directory structure Altering the Existing Do Minimum Reference Case Networks 4 4 4 Each specific future year transport intervention is represented by a catalog key which can be turned on or off by the user However it should be noted that each scenario is set up based on the default configuration of the assumed Do Minimum and Reference Case schemes and as such alterations should only be made for bespoke network building 4 4 5 Furthermore turning on or off individual schemes alters the physical network structure but does not automatically alter the PT service lines coding which may require updating to be compatible with the selected scheme alterations The PT service coding associated with each scheme is identified within the Do Minimum and Reference Case DVPTLF alterations files located
34. S 07_FACTOR_FILE_ YEAR _NW_ IP FAC TMFS 07_FACTOR_FILE_ YEAR _IW_ IP_ZERO_DEMAND FAC TMFS 07_FACTOR_FILE_ YEAR _NW_ IP_ZERO_DEMAND FAC It is anticipated that the only amendment a model user would make to the Factor file is the allocation of fare tables to operators where YEAR is modelled year eg 7 Fares File Definition of distance based fare tables TMfS07_FARES_AM FAR Fare tables can either be allocated by TMfS07_FARES_IP FAR operator in the Factor file or by individual service in the Lines file If a service has a fare table allocated by operator and is also is allocated a fare table in the Lines file then the fare table statement in the Lines file takes greater precedence and is applied TMfS07_FARES_PM FAR 5 3 2 Figure 5 1 illustrates the directory structure of the PT input files mvaconsultancy TMfS 07 User Manual 5 4 5 PT Assignment Model Name Lines 2 oo Networks CPrR_Site_Files 8 Params Zones _Coords dat amp Program E PT_Dump_Links def a G Runs S IW_FACTOR_FILE FAC a 7 E NW_FACTOR_FILE FAC a Gj eyo1 TM S07_FACTOR_FILE_NO_VOT FAC Input E TMfS07_FARES_AM FAR a Lines E TMfS07_FARES_IP FAR E Networks 2 TMfS07_FARES_PM FAR H user defined Zones_String csv a PR Sie Files TM S07_SYSTEM_FILE PTS A Outout Name a TMfS07_ 1 08 Ferry _BY017 LIN a Base Inter_Urban_Bus_BY017 LIN Intra_Urban_Bus_BY017 LIN Params Rail _BY017 LIN
35. _ 1 08 4 AM_REPORT PRN Params AM_PRINTFILE PRN Program AM_H _LOADED_NET NET 3 Runs E HYAM_BYOLACP71 HWM m 7 BY01 O Input Output ace C3 Demand 3 Hw O am IP D mM Pnr PT Figure 4 4 Location of Road Model Assignment Output Files 4 3 3 A description of the link volume field information contained within the output loaded road networks is contained in Table 4 2 mvaconsultancy TMfS 07 User Manual 4 7 Table 4 2 List of final assigned network volume fields Attribute Description TOTAL PCU traffic flow PCUs Congested Road link travel Time Minutes mins TOTAL PCU traffic flow V_1 Road Link Capacity N A Congested Road Link Speed km hr Vehicle Distance travelled TOTAL PCU traffic flow Kilometres km Road Link Distance Vehicle Hours travelled TOTAL PCU traffic flow Hours hrs Congested Road network travel time 60 Car In Work Traffic flow Car Non Work Commute Traffic flow Car Non Work Other Traffic flow LGV Traffic flow HGV Traffic flow Combined two way TOTAL PCU traffic flow Combined two way Car In Work Traffic flow Combined two way Car Non Work Commute Traffic flow Combined two way Car Non Work Other Traffic flow Combined two way LGV Traffic flow Combined two way HGV Traffic flow 4 4 Network Building 4 4 1 There are a number of transport interventions that are assumed to be in place in each of the forecast year scenar
36. _Regional_Model_V1 11Forth08 cat rwo el lel 2 Scenar Bas Scenario BYO1_BS_7 4 Project Prefix Application Forth Model Base 00 pen Page Height 1 Width Group Cluster Set up 00 Full Model 00 Run ID Create Mats Yor First Loop 00 I Notify When Done I Send Email When Done Normal Priority gt Demand Model 00 Mode and Destination Choice 00 PILOT v 10 01 2008 5 0 2 Mon Feb 23 10 07 55 2009 0 00 14 Print D ENT_CROSSING_SUPPORTSFORTH_REGIONAL_MODEL_V1 11 TPPL2371 PRN Step 1 MATRIX v 10 07 2008 5 0 2 Mon Feb 23 10 07 55 2009 0 00 14 Calculate HOV Average Gen Costs for Base Costs Description User Program 1 Zone 181 Program Status Program CBATDualCore exe Group Execution Order 2 of 3 Task Executing WAIT4FILES Cr i CH Input Script File Input Script File Eo Lavoie Work Directory Work Directory Project Prefix Project Prefix Page Height Page Height 000 Width p5 Run ID Wait for All Files to be Created Toe Seer BOTT ChaProl sorpiend il When Done Normal Priority z D ClusPro2 script end Waiting for DAC ROSSING_SUPPORT FORTH_REGIONAL_HC Ready Press Cancel bt FILU y IW UI 2ue 9 0 4 MON FED 25 1 03 2UUS Internal Zones Print D ENT_CROSSING_SUPPORT FORTH_REGIONAL_MODEL_V1 11 TPPL2370 PF UC x Zones Step 2 MATRIX v 10 07 2008 5 0 2 Mon Feb 23 10 07 55 2009 Check Interval sec Calculate Aver
37. age Generalised Costs for Base Costs Step 2 MATRIX RetumCode 0 Elapsed Time 00 00 14 1 PPR Zones Cluster Model Run Optior jumpto Sa VOYAGER RetumCode 0 Elapsed Time 00 00 16 Set_Outer_Loopt Base Year RE KE ab veine ecg S cube LR Task Monitor FORT GF Step MATRIX vil GF step 2 MATRIX v t Waiting for ClusProtivv 2 Gp waiting for CusProa tear ER Figure 3 3 On Screen Display End of Model Test 3 3 4 The screen displayed at the end of a completed model run is shown in Figure 3 4 If for any reason the model should fail the user will see a screen similar to that illustrated in Figure 3 5 If unsuccessful the View Run Report File button will open a print file relating to the whole model run with the step that caused the error appearing at the bottom of the file note that pressing F6 while over the print file of the stage that caused the failure will take the user directly to that print file mvaconsultancy TMfS 07 User Manual 3 5 POSTRUMASSOO APP Post Run Analysis Scenario BYOT_BS_ 7 Catalog Forthow cathy Base BYO1_BS_7 Task Monitor BYO1_TF_7 H BYO1_PS_7 BYM MT 7 t ej eal Application Status Catalog D 1C3713500_Forth_Replacement_Crossing_SupportForth_Regional_Model_V1 111Forth08 cat Scenario BYD1_BS_7 Application Forth Model Base 00 Appicatons Group Full Model 00 Forth Model Base ome panes Ti Loop OU emand M
38. alogue Box 3 3 Figure 3 3 On Screen Display 3 5 Figure 3 4 Successful Completion of Model Test Display 3 6 Figure 3 5 Unsuccessful Completion of Model Test Display 3 6 Figure 4 1 File Location of Generalised Cost Coefficients and HGV Speed Limits 4 5 Figure 4 2 File Location of Input Prelim Network 4 5 Figure 4 3 File Location of the AM Peak Hour Travel Demand Matrix 4 6 Figure 4 4 Location of Road Model Assignment Output Files 4 7 Figure 4 5 The Network_Build cat Window with Six Scenario Options 4 10 Figure 4 6 Standard Network Build Scenarios double click the relevant scenario 4 11 Figure 4 7 Infrastructure Scheme Selection Buttons 4 11 Figure 4 8 Options to Alter the Input PT Lines Files and Start Build Process 4 12 Figure 4 9 Example DBF file Representing Additional Links Required for a Scheme 4 13 Figure 4 10 Directory Location of Scheme and Connector DBFs 4 15 Figure 4 11 Location of the Changes DBF Files 4 15 Figure 4 12 Location of the PT Lines Files 4 16 Figure 5 1 PT Input File Directory Structure 5 5 Figure 5 2 PT Lines File in Cube Network Format 5 5 Figure 5 3 PT Lines File in Text Editor Format 5 6 Figure 5 4 PT Output File Directory Structure 5 9 Figure 5 5 Example of Output PT Network File 5 9 Figure 7 1 Example Output Park and Ride CSV File 7 3 Figure 8 1 Example Network Statistics File 8 1 Figure 8 2 ACCDNT Example Output 8 2 Figure 8 3 Example ENEVAL Output File 8 3 mvaconsultancy TMfS 07 User Manual 4 Background
39. based on the number of vehicles travelling on each link and the average accident rate associated with different types of road Casualty and accident rates associated with different road types are contained within a Casualty_Ratesv5 dbf and Accident_Ratesv8 dbf These input files are located in the Params folder The financial costs associated with different severities of road accidents are located in the Total_Costsv7 dbf file which is also located in the Params folder The model output files include accident statistics by link or by local authority for each time period An example output from the link based file is illustrated in Figure 8 2 Note The column entitled V_1 is output flow from the Highway Network A Bela D E F G H l J K L M 1A B LA DISTANCE LINK_TYPE V_1 FATAL_CAS SERIOUS_CAS SLIGHT_CAS TOTAL_CAS DAMAGE_ONLY ALL_ACCIDENTS COMB_COST 2 1 2 5 0 1 0 0 0 0 0 0 0 0 3 1 1001 5 0 53 1 3479 0 04 0 18 2 86 3 08 23 4 25 48 159097 29 4 2 1002 5 0 35 1 2102 0 01 0 07 1 14 1 23 9 34 1057 63479 46 5 3 1003 5 0 41 1 303 0 02 0 12 1 93 2 07 15 77 17 84 107191 16 6 4 1004 5 0 22 1 5 78 0 0 01 0 2 0 21 1 61 183 10971 93 7 5 1005 5 0 21 1 51 04 0 02 0 11 1 66 1 79 13 6 15 39 92483 11 8 5 100306 5 0 1 0 0 0 0 0 0 o 0 9 6 1006 5 0 26 1 421 o 0 01 0 17 0 18 1 39 1 57 9444 69 10 7 1007 5 0 31 1 20 98 0 01 0 07 1 01 1 09 8 25 934 56117 67 11 8 1008 5 0 21 1 774 0 0 02 0 25 0 27 2 06 233 14024 67 jz 8
40. basically variations of the road assignment procedure from the main model There are selections of catalog keys for these applications as detailed below mvaconsultancy TMfS 07 User Manual 4 16 Table 4 13 Secondary Analysis Catalog Keys Function Default Value Parent Network Major assignment network input networks only Parent Demand Matrix Major demand matrix Subarea Network Subarea network MaxIters Maximum number of iterations Select_Link_Defintition CSV file that defines links to be analysed in select link analysis Tolerance Level of tolerance NSUCC Number of successive loops Minimum number of iterations Model Year Model Year as integer 2000 Time_Period Time Period either AM IP or PM Select Link Analysis 4 5 4 The select link analysis requires an unassigned network and assignment matrix which can be linked in via the catalog keys as defined above It also requires a select link parameter file which is linked to the application via the Select_Link_Defintition key 4 5 5 This file should be in csv format with only the first 3 columns used They are for select link number A node and B node The select link number is a sequential ID code of which the first must have a one value and each new row increases by one 4 5 6 Once this file has been created and linked to the application the full application should be run in order to first create script amendments and then assign the network an
41. d retrieve select link matrices Currently the catalog prepares select link matrices for an unlimited number of specified select links for each assigned user class In addition an assigned network with select link volumes is prepared however this is limited to showing the first three specified select links for each assigned user class due to limitations in the Voyager mvaconsultancy TMfS 07 User Manual 4 17 4 5 7 4 5 8 4 5 9 4 5 10 4 5 11 4 5 12 4 5 13 4 5 14 4 5 15 software As an alternative a highway assignment can be undertaken in the main model with path files set to Y and then these can be used to derive select link diagrams via the standard Cube Voyager Network interface It should be noted the path file produced is very large several gigabytes and the interactive select link procedures can take some time eg up to 20 minutes Sub Area Analysis There are three inputs required for a sub area process namely an assignment matrix E a full unassigned network and E a sub area network The first two requirements are taken from the relevant year and scenario of the model and can be linked in via catalog keys see above while the third needs to be created In order to create a subarea network a region of the parent network should be extracted There are two basic methods for this The first method requires that a polygon be drawn over the parent network Open the parent network within Cube and
42. details can be found in the software help files Table 5 1 PT Model Input Files Description File Name Assigned Produced by road assignment model one See Chapter 4 Road file for each time period Networks Travel Produced by demand model one file for See Chapter 6 Demand each time period with a table for each user Matrices class and a total demand table for presentation purposes Matrix files are provided as part of the standard model installation for the required forecast years As matrix files are an output of the Demand Model process a PT assignment run of a test in a forecast year requires that the Demand Model has already been run to generate the relevant matrices mvaconsultancy TMfS 07 User Manual 5 2 Description File Name System file Includes TMfSO7_SYSTEM_FILE PTS definition of modes definition of operators definition of wait time curve s and e definition of crowd curve s It is anticipated that the only amendment a model user would make to the System file is the definition of new service operators Line Files Single file for each mode includes following Intra_Urban_Bus_ 1ID YEAR LIN information roreacM codediimg Inter_Urban_Bus_ ID YEAR LIN name can be any combination of alpha numeric characters eg 1000 1000b redbus Subway_ ID YEAR LIN Rail_Y ID YEAR LIN mode Ferry_ ID YEAR LIN operator headway for each time period zero headway means there
43. e Pence a Site Attraction Factor Not recommended to adjust base sites E Base Attraction Factor Required to align base overcapacity a Car Park Capacity this is the capacity of the official P amp R site cars will be allowed to park outside the main car park but with a greater time penalty Off Street Capacity where this is unknown a zero should be used mvaconsultancy TMfS 07 User Manual 7 1 7 3 2 7 4 7 4 1 7 4 2 7 4 3 7 4 4 7 4 5 7 4 6 7 4 7 7 4 8 a Catchment Area Origin Zones string must be enclosed by single quotation marks and a Catchment Area Destination Zones string must be enclosed by single quotation marks This information is required for any additional Park and Ride sites added to the model Note that due to the comparative nature of the park and ride process the site attractiveness factor should be relative to competing sites For this reason a secondary process has been created which creates an appropriate site attraction factor Future Year Attractiveness Factor Calculation The Future PnR Site Attractiveness Calculation catalog allows a range of options to be defined for calculating attractiveness factors This process calculates a site attractiveness value for a new site by comparing the attractiveness values for travel movements provided by competing PnR sites These comparisons can either be weighted by the number of similar zone to zone travel movements or the level o
44. ed automatically by the PT model and are described in Chapter 5 To undertake full skimming of the road model the skim Catalog key must be set to Y Note that there will be an increase in run time over a typical road assignment with this option approximately 15 minutes per time period for the 07 base year This full skimming procedure is undertaken on all iterations of the road assignment model mvaconsultancy TMfS 07 User Manual 4 18 4 5 16 The generated road cost Skim matrix file is named AM_HY_SKIMS_5 MAT where AM is time period and is located in the output Road time period folder as illustrated in Figure 4 13 3 TMF507_Y1 08 All 2 AM_HY_SKIMS_1 MAT O Params O Program Runs B 7 svo Input B Lines 5 Networks O PnR_Site_Files Output ace Demand 3 Hw am Or pm pnr pt Figure 4 14 File Location for Road Cost Skim 4 5 17 The road cost skim matrix file contains 20 tables and can be viewed using Cube 4 5 18 There are four tables associated with each of the five assigned user classes including generalised cost in pence average time in mins average distance in kilometres and average toll in pounds 4 5 19 Using Car In Work as an example the matrix tables are labelled as follows CIW_T car in work average time skim CIW_D car in work average distance skim CIW_C car in work average generalised cost skim and
45. edure This process calculates carbon emissions associated with road traffic cars and goods vehicles per link and at a local authority level The procedure can also be used to output Carbon Dioxide Equivalent CO2 e mvaconsultancy TMfS 07 User Manual 8 2 8 4 2 8 4 3 8 4 4 8 4 5 8 4 6 8 5 8 5 1 These outputs are displayed in tones unless the output in kilograms option is chosen by the user and reflect annual emissions of carbon The user can also output the data in emissions per kilometre format The ENEVAL procedure does not include emissions associated with buses Intra zonal vehicle movements are also excluded from the ENEVAL procedure The following input files are required to operate the ENEVAL program and are all stored in the Params folder Efficiency dbf car efficiency changes file EmissionsA dbf emission rates file a Fleet Split dbf fleet composition file and a Fuel ConsumptionA dbf fuel consumption rate file The information in these files reflects emissions modelling guidance associated with WebTAG An example output file by local authority is shown in Figure 8 3 A B C D 1 LA TOTAL_CARBON TOTAL_CO2 E 1 0 0 am 2 0 0 4 3 1 74 6 37 5 4 3 25 11 92 6 5 31 97 117 21 6 19 54 71 63 7 0 0 8 0 0 0 0 0 0 0 0 0 0 7 54 27 63 15 14 14 58 53 48 16 15 0 0 17 16 0 0 Figure 8 3 Example ENEVAL Output File Congestion Mapping The congestion mapp
46. ext Back Run Figure 4 7 Infrastructure Scheme Selection Buttons mvaconsultancy TMfS 07 User Manual 4 11 Scenario DMO1 _11 Application Network_Buitd i Scheme 28 in place 1 in place o cq Scheme 29 in place 1 in place eo Foe Scheme 30 in place 1 in place o C1 Set input lines file for Intra Urban Bus D ATMIS O7 TMIS 07 PT Andy Forecast Year Networks network and add ins NetworkBuild PT_lines DMO1_11 Intra Urban Bus_ Browse Set input line file for Inter Urban Bus D STMfS O7ZSTMIS 07 PT Andy Forecast Year Networks network and add ins NetworkBuild PT_lines DMO1_11Mnter Urban Bus_ Browse Set input line file for Tram Phase_la DATES OF TMES 07 PT Andy Forecast Year Networksinetwork and add ins NetworkBuild PT_lines DMO1_114Tram1a_DMO1_1 Browse Set lines file input for Rail o ATMIS O7 TMIS 07 PT Andy Forecast Year Networks network and add ins NetworkBuild PT_lines DMO1_11 Rail_DMO1_11 LI Browse Set input lines file for Ferry Browse Cancel Jext Back Run Figure 4 8 Options to Alter the Input PT Lines Files and Start Build Process Coding a New Intervention 4 4 8 There are two main methods to insert a new intervention or scheme test into the model network including E using DBF files as inputs to the Network Build process and a using the Cube Network Window to modify the network Using DBF Files 4 4 9 Within Vo
47. f travel demand between these zones To operate the catalog open it in CUBE Voyager and create a new scenario The input file should read to your new park and ride site file which should be complete in all fields except the site and base attractiveness factors which should have zero values State the number of zones and also the site number of the first new site The process includes an option to weight the attractiveness factor by base year travel demand If selected the next 3 fields after the radio button should be linked to the base year park and ride demand this demand is taken from before the P amp R assignment and represents full end to end trips with no regard for site choice The total available level of base year PnR travel demand can also be illustrated for a single site This can generate a broad indication of the level of potential demand that could use a new site If base demand weighting is not chosen the sites are compared on an i j pair weighting counting the number of i j pairs available for each new site which are also provided by each pre existing typically base year site The final stage requires the user to open the PnR Site Attractiveness calculation spreadsheet 20110526 _PnR_Site_Attractiveness_Calculation_V 2 0 xls and turn to the Controls sheet Set cells D2 through D4 appropriately and then import the site file followed by the results sheet either weighted or unweighted depending on your choice in the pre
48. hat define the range of routes that will be retained for each zone pair based on their generalised time relative to the minimum generalised time This stage also includes a representation of passenger fares based on a proportion of the generalised cost associated with each mode Passenger crowding is not considered within this Route Enumeration stage Route Evaluation This stage calculates the probability of use for each of the enumerated routes between zone pairs including the impacts of crowding and fares Further details of the PT Assignment Model development and calibration can be found in the TMfS 07 National Public Transport Model Calibration and Validation Report 5 6 5 6 1 PT Output Files Table 5 2 Model Output Files Description Files produced for each individual time period in separate folders Loaded network Lines loading table Skims matrix Composite cost matrix Walk demand matrix Matrix summary table Network with assigned passenger and walk volumes by user class DBF file containing detailed information of loaded services by line node including on off volumes link distance and time and headway Skims matrix by user class including composite cost transit distance time walk distance time total boardings boardings by mode fares wait time and boarding penalties Matrix containing in work and non work composite cost skims Note that Commute and Non Work Other user classes have
49. he separate Runs Year Demand folders are a set of full demand scenarios New demand scenarios can be named in any way the user chooses there is not a limit on the length of a scenario name 6 3 2 The files located within the Demand Model folder include CTE and TOD files represent the trip end files created by the trip end model E TEC files are the base reference logsum cost utilities these should not be changed E MSP represent the mode specific constants and are specific to this particular scenario there is a separate file for each time period and trip purpose E GCM and GCMH represent generalised cost matrices and the HOV equivalent for each period and purpose a _ADD MAT represent the add in matrices each matrix has 3 tables AM IP and PM except PT_ADD MAT which has nine tables IW NWC and NWO for each period a PARKING_CHARGE MAT is the parking charge matrix containing two tables NWC and NWO and a SOV_PROP MAT are the base year single occupancy proportions for use in HOV modelling If not undertaking HOV modelling the default values can be left in the file It should be noted that this folder must contain the files relating to any of the optional modules Macro Time of Day Choice Trip Frequency and HOV Modelling regardless of whether those options have been chosen 6 3 3 Relevant forecast year eg 2012 2017 amp 2022 etc input Trip End files are supplied by MVA along with the relevan
50. he travel demand matrices is as follows AM represents the morning peak modelled time period IP for the average inter peak hour and PM for evening peak hour BYO1 represents the four character test ID for the network E ACP represents the three letter travel demand and planning data scenario E 7 represents the modelled year eg 7 2007 11 2011 etc and E 1 is the demand model external loop number which is always 1 for the base year For modelled forecast years the demand model external loop number will be dependent on the number of demand model external loops run by the user eg 1 to 5 The current recommendation is five external loops of the demand model Prelim Network 4 2 5 The prelim network eg BY017_ALL NET contains information relating to the development of the road and public transport network infrastructure and bus preload information ie unloaded network files a BYO1 represents the four character test ID for the network a 7 represents the base model year and E ALL represents road and public transport infrastructure 4 2 6 This naming structure will typically be used in all model scenarios 4 2 7 A description of the link volume field information contained within the prelim networks is contained in Table 4 1 Table 4 1 Description of Prelim Network Volume Fields Attribute Description AM_Bus_Flow Average AM Peak hour 0800 0900 Bus Tram Flow PCUs IP_Bus_Flow Average Inter Peak hour 1 6 of 1000 1600
51. hrough the Change links DBF which details the link attributes that need to be changed when a certain scheme is developed In the scripting the original volume fields are then updated to contain the values stated in this DBF The DBF contains the following fields but only the attributes that require updating will actually have to be included and referred to in scripting E A and B the A node and B node of the links to be changed SCHEME_CHA the scheme code number for which the changes should be made E N_CAP_L the new capacity of each lane N_NUM_L the new number of lanes on that link NEW_CAP the new capacity of the link NEW_REV the new link direction distinguishing between one way or two way links N_L_CLASS the new link class and E NEW_SPEED the new speed on the link 4 4 16 Connectors DBFs in some instances it is necessary to modify or create new connectors to the network ie when adding new rail stations These connectors should be added using the connector DBFs used in the Do Minimum and Reference Case networks Adding New Scheme Information Using DBFs 4 4 17 Scheme nodes and scheme links DBFs are added in module 1 2 and 3 However these modules are currently using the maximum number of input files and as such another identical module could be added after module 3 and connected in the same way As required updated connector
52. iles network building and secondary analysis components 4 1 2 The Road Assignment Model is used to a undertake route choice a produce road based travel costs for the Demand and Park and Ride Models a provide bus speeds for the Public Transport Model and qa produce road based travel demand and costs for operational economic accident and environmental appraisals 4 1 3 The Road Assignment Model covers three time periods within a typical weekday including a average AM peak hour between 0700 1000 E average inter peak hour 1 6 of 1000 1600 and a average PM peak hour between 1600 1900 4 1 4 The Road Model includes eight user classes including the following five vehicle classes a car in work a car non work commuters car non work others a LGV and a HGV 4 1 5 The High Occupancy Vehicle modelling option allows for single and high occupancy version of each user car user class bringing the total number of user classes to eight 4 1 6 The Road Assignment Model is operated using the Cube Voyager HIGHWAY module software version 5 0 2 mvaconsultancy TMfS 07 User Manual 4 1 4 2 Road Model Input Files 4 2 1 There are four main input files required operating the Road Assignment Model as follows E generalised cost coefficients database file GenCostTable_V4 dbf This file should not be altered by the user and is located in the Params folder E Heavy Goods Vehicle HGV speed limits database file
53. include changes to transport infrastructure see Chapter 4 for more details of the network development E update routing of services coded within existing lines files to follow new network E modify routing headways capacities of existing services within the lines files add new services in relevant lines file ia specify new fares table and allocate to individual services or operators and or a re allocation of fares tables As the assigned road network provides modelled road network speeds and times for bus services any changes to the modelled network structure including rail only changes would require re assignment of the road model to provide the required inputs for a PT model assignment PT Assignment The assignment is carried out by the Cube Voyager PT module The effects of crowding on rail services are included in the AM and PM Peaks but are not included for bus tram or ferry services Wait curves are applied to inter urban bus and rail services but are not included for urban bus or subway services The model assignment is split into two stages as follows Route Enumeration This stage identifies a set of discrete routes between each zone pair along with the probabilities that passengers will use each route Routes that fail to meet certain criteria are discarded mvaconsultancy TMfS 07 User Manual 5 6 5 5 5 5 5 6 5 5 7 The criteria are specified using the Spread Factor and Spread Constant parameters t
54. ing of a Windows operating system It is also expected that users have an understanding of transport and land use modelling and how to interpret model outputs 1 3 6 It is also expected that the user would attend a TMfS training course prior to applying the models mvaconsultancy TMfS 07 User Manual 1 2 1 4 User Manual Structure 1 4 1 The remainder of this manual is structured as follows E Chapter 2 describes the model setup and installation process a Chapter 3 explains the TMfS 07 Model in operation a Chapter 4 describes the Road Assignment model a Chapters 5 describes the Public Transport Assignment model E Chapter 6 describes the Demand Model a Chapter 7 describes the Park and Ride Model E Chapter 8 describes the additional analysis procedures available with TMfS 07 E Chapter 9 explains potential troubleshooting techniques and a Chapter 10 provides additional useful information mvaconsultancy TMfS 07 User Manual 1 3 Setup and Installation 2 1 Hardware Requirements 2 1 1 Whilst it is expected that TMfS 07 will operate on most computers running Windows XP for best results and the quickest run times we would recommend the following specification a a quad core computer a at least a 2 5GHz processor 3GB of RAM and a at least 20GB of hard disk space on the PC 2 1 2 The model can be operated on either Windows XP or Windows Vista machines 2 2 Software Requirements 2 2 1 TMfS 07 requires
55. ing tool is a secondary standalone application which can be used in conjunction with certain model outputs to produce maps of congestion accident rates and emissions based on link analysis on a user defined area scale mvaconsultancy TMfS 07 User Manual 8 3 Analysis Procedures 8 5 2 Standard grids can be provided which cover the following modelled areas a Entire Modelled Area E Central Belt E Forth Regional Modelled Area E Edinburgh a Glasgow and a Aberdeen 8 5 3 Alternatively users can create their own grids these need to be polygon shape files using the fishnet tool which is an add on for ARCMap This can be downloaded from the ESRI website in script format which can then be imported into ARCMap in the tools menu by following the instructions in the read me file which comes with the program 8 5 4 Once the fishnet grid tool is installed choose the selected area in which the grid is to be created then click on the fishnet tool The dialog box shown below will then open YT Browse YT Browse M se es Figure 8 4 Fishnet Dialog Box 8 5 5 In the first two boxes enter the X and Y coordinates of the position to the lowest and furthest left of the area in which the grid is to be created 8 5 6 The second step involves entering the value to represent the width and height of each of the cells within the grid This value is measured with respect to the units used in the mapping mvaconsultancy
56. io 3 2 3 The necessary output folders that reflect the test scenario are automatically created by CUBE PILOT when the model run starts 3 2 4 There are typically three pages of keys this can change depending on screen display format with the first page containing the following components general model settings such as test ID growth planning data scenario model year number of inner and outer demand model loops Cluster On Off switch this option must be OFF if CLUSTER is not installed on PC Warm Start Options jump point to re start a test from an intermediate point requires starting loop number and switches for optional forecasting choice models trip frequency macro time of day modelling and high occupancy vehicle modelling mvaconsultancy TMfS 07 User Manual 3 3 3 2 5 The second page contains keys for selecting the type of model to run including full demand and assignment models E road assignment only and a public transport assignment only 3 2 6 When running an assignment only test the required time period must be selected ie All AM IP and PM along with the relevant trip matrix loop number The default value for the matrices is to use the last loop matrices based on the growth scenario model year and demand model loop keys set on the first page NOTE If running a Full Model then these keys can be left as the default values However they will not be used by the model if they are altered
57. ios These Do Minimum and Reference Case schemes are described on the LATIS Website mvaconsultancy TMfS 07 User Manual 4 8 4 4 2 These future year Do Minimum DM and Reference Case RC schemes are built into the model networks through an application called Network_Build app which can be displayed in full catalog format with Network_Build cat 4 4 3 The application operates by creating a network which contains all proposed road and public transport DM and or RC schemes that are assumed to be in place over time The procedure is then used to exclude schemes that are not relevant for specific forecast year scenarios There are four key stages in the network building process a Build all schemes firstly modules 1 3 build in the network based attributes and modifications associated with every future year scheme to the original 07 Base Network Due to the number of schemes involved this process is undertaken in three stages with the output from module three containing every scheme E Removal of irrelevant schemes module 4 builds the scenario specific network by deleting all nodes and links and removing any network modifications that are not related to the scenario This process is contained within the scripting and involves deleting or removing changes based on the catalog key that represents each scheme Once complete module 4 outputs a combined road and PT network structure for each specific DM or
58. is no services in where ID is test identifier eg BY007 that time period and fare table if coded individually by service seated capacity for crowd model and applicable modes crush capacity which is assumed as 140 of seated capacity for crowd model and applicable modes crowd curve for crowd model and applicable modes routing through network nodes and cumulative run times at nodes for all modes except bus Tram_ ID YEAR LIN YEAR is modelled year eg 7 Blank Lines files are not accepted in Cube Voyager Therefore if a mode has no services enter a dummy service with zero headways mvaconsultancy TMfS 07 User Manual 5 3 Description File Name Factor file Includes TMfS 07_FACTOR_FILE_ NO_VOT FAC 7 values of time TMfS 07_FACTOR_FILE_ZERO_DEMAND_ NO_VOT FAC fare table if coded by operator assignment parameters TMfS 07_ FACTOR FILE NO_VOT_IP FAC boarding and transfer penalties and NO VOTZIRFAC allocation of wait time curves and wait Which produce time factors TMFS 07_FACTOR_FILE_ YEAR _IW FAC A Factor file without values of time is the TMFS 07_FACTOR_FILE_ YEAR _NW FAC master file A model process then adds in TMFS 07_FACTOR_FILE_ YEAR _IW_ values of time from a dbf table in the ZERO_DEMAND FAC Params folder creating two Factor files for TMFS 07_FACTOR_FILE_ YEAR _NW_ In work and Non work journey purposes ZERO_DEMAND FAC TMFS 07_FACTOR_FILE_ YEAR _IW_ IP FAC TMF
59. is released for use with the following conditions Intellectual Property Rights The intellectual property rights and copyright of the TMfS model interface data and procedures remain with Transport Scotland and MVA Consultancy as defined by separate agreement The intellectual property rights and copyright of the Cube and related software remain with Citilabs The user shall have no licence to copy or use any of the model interface data or procedures outside the terms agreed with Transport Scotland and MVA Consultancy Licences The TMfS model interface data and procedures are provided under a general agreement that they will be used only for Transport Scotland Scottish Executive and or Scottish Local Authority and Regional Transport Partnership projects The CUBE software licences are not part of this agreement and the relevant licences are assumed to have been obtained from Citilabs mvaconsultancy TMfS 07 User Manual 1 1 Limitations Transport Scotland and MVA Consultancy shall not incur any liability under or in connection with this release of the TMfS model interface data or procedures to the extent that any failure to perform any or all of its functions has been caused by or contributed to by any force major event or circumstances beyond reasonable control of MVA Consultancy The TMfS model interface data and procedures are provided in good faith and the user accepts full responsibility to satisfy itself of
60. nd Reference Case scheme code number 1 to 26 Equivalence list contained in Scheme Code Numbers xls Change of existing link relating to Do Minimum and Reference Case scheme code number 1 to 26 Equivalence list contained in Scheme Code Numbers xls mvaconsultancy TMfS 07 User Manual 4 4 Directory Structure of Required Input Files 4 2 8 The generalised cost coefficients and HGV speed limits database input files are contained within the Params folder as illustrated in Figure 4 1 TMfS07_v1 08 E GenCostTable_ 2 dbf O Params HGV_Speeds_ 1 dbf C2 Program Runs DB 7 3 syo1 Input B Lines Networks O Highway O PnR _Site_Files B Output Figure 4 1 File Location of Generalised Cost Coefficients and HGV Speed Limits 4 2 9 The location of the relevant input prelim network file is illustrated in Figure 4 2 TMf507_V1 08 A BY017_ALL NET C2 Params fom Program Runs B 7 svo D Input O Lines Networks O Highway CD PnR_Site_Files Output Figure 4 2 File Location of Input Prelim Network 4 2 10 The input travel demand matrix is located in the output file directory In the model forecast years the travel demand matrix is created as an output from the demand model therefore the travel demand matrix is both an input file to the road assignment model and an output file from the demand model 4 2 11 Figure 4 3 illustrates the
61. ns preliminary functionality to provide for High Occupancy Vehicle HOV Modelling This can be turned on by altering the HOV catalog key It should be noted however that the HOV Model is provided to cater for the further separation of travel demand Users will need to check that this process is suitable for the requirements of specific projects and update accordingly In addition there are a list of requirements that need to be made to certain files to allow HOV modelling namely mvaconsultancy TMfS 07 User Manual 6 1 Proportion files a Highway network Highway assignment script 6 2 7 The proportion files are found in the Params folder DPMs and will need updated to represent relevant user defined HOV proportions At present these matrix type files include some dummy values and should be amended accordingly For more details on the role of the HOV module within the demand model see the TMfS 07 Demand Model Development Report 6 2 8 If the highway network is to incorporate high occupancy lanes then these must be coded into the network as separate links with a new link type that flag up their specific use There is an option to incorporate more than one link type to represent different link attributes speedflow curves capacity etc and these should also be coded in to the highway script For more information for making HOV changes in the assignment script please contact MVA 6 3 Demand Model Input Files 6 3 1 Under t
62. nu 8 2 2 An example Network Statistics output from an AM Peak Assignment is shown in Figure 8 1 In the example _K stands for vehicle kilometres and _T for vehicle time AM_CIW_K AM_CNWC_K AM_CNWO_K AM_LGV_K AM_HGV_K AM_CIW_T AM_CNWC_T AM_CNWO_TAM_LGV_T AM_HGV_T 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 13 536 2 467 2 254 3 007 089 12734069 9 520 660 3 063 180 1 618 657 27 602 6 332 3 873 19 083 189 94 685 686 61 257 759 23 182 413 16 149 961 243 936 65 695 64 484 74569848 394 030 818 223 161 752 106 725 203 107 640 934 141 408 39 714 31 258 17 551 635 96 011 559 59 308 756 29 615 053 20 664 997 0 0 0 0 0 0 0 0 Co J On en 4 wR a 48 301 l 1 164 565 3 931 059 4 543 519 1 112 368 1 840 544 102 275 17 797 274 105 409 227 71 659 300 24297 955 38 290 677 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 66 221 21 616 11 537 830 92 146 263 59 520 775 25 984 294 36 830 033 20 930 J 7 123 2 307 965 19 514 474 12 276 608 6 126 334 6 050 266 186 378 41 248 33 839 578 197 732 239 136 616 202 76 843 689 44 320 537 76 861 18 881 3 912 327 22 090 165 15 580 959 7 970 296 6 200 133 0 0 0 0 0 0 0 Figure 8 1 Example Network Statistics File mvaconsultancy TMfS 07 User Manual 8 1 8 3 8 3 1 8 3 2 8 3 3 8 3 4 8 3 5 8 3 6 8 4 8 4 1 Road Traffic Accident Analysis The accident analysis procedure calculates the number and cost of road traffic casualties by severity and road type The procedure calculates accidents
63. odel Mode and Destination Choice 00 AM Mode and Destination Choice 00 Program Status Task Run Result Program CBATICIOS VOYAGER Run of Application Forth Model Base 00 is complete Description User Progr Group Execution Order 14 View Run Report File Task VOYAGER E Microsoft PowerPoint MAE sven megs tem Figure 3 4 Successful Completion of Model Test Display D Cube Licensed to MVA Co OO APP Post Run Analysis Sc 5 BYOT_ BS 7 ForthO cat see XS 1 P ER Task Monitor Application Status catalog DC3713500_Forth_Replacement_Crossing_Support Forth_Regional_Model_V1 111Forth08 cat Scenario BYO1_BS_7 Application Forth Model Base 00 Task Run Result i Catalog D C3713500_Forth_Replacement_Crossing_Support Forth_Regional Model V1 114F Scenario BYO1_BS_7 icati Forth Model Base 00 Applications Application ForhMe p Program Status Current Group ENEVAL 00 a Execution Order Bots Description 4 Program Description AM ENEVAL Aggregate Data View Program Print File Group Executior Program MATRIX failed View Run Report File Unable to continue running the Application Group Program Task ok Do you want to L cancel Return to curent Application Manager Session to view the failed program C Start new Application Manager session to view the failed program C Ext
64. odel Output Files 4 6 4 4 Network Building 4 8 4 5 Secondary Analysis 4 16 5 PT Assignment Model 5 1 5 1 Overview 5 1 5 2 PT Model Processes 5 1 5 3 PT Input Files 5 2 5 4 PT Intervention Coding 5 6 5 5 PT Assignment 5 6 5 6 PT Output Files 5 7 6 Demand Model 6 1 6 1 Overview 6 1 6 2 Demand Model Options 6 1 6 3 Demand Model Input Files 6 2 6 4 Demand Model Output Files 6 3 7 Park and Ride Model 7 1 mvaconsultancy TMfS 07 User Manual 2 7 1 7 2 7 3 7 4 7 5 8 1 8 2 8 3 8 4 8 5 8 6 9 1 9 2 10 10 1 10 2 10 3 Overview Model Process Park and Ride Input Files Future Year Attractiveness Factor Calculation Park and Ride Output Files Analysis Procedures Overview Network Statistics Road Traffic Accident Analysis Environmental Analysis Congestion Mapping Accessibility Analysis Troubleshooting Restarting a Model Run Common Issues Additional Information TMfS Website GIS Data Extra Public Transport Mode Tables Table 4 1 Description of Prelim Network Volume Fields Table 4 2 List of final assigned network volume fields Table 4 13 Secondary Analysis Catalog Keys Table 5 1 PT Model Input Files Table 5 2 Model Output Files 7 1 7 1 7 1 7 2 7 3 8 1 8 1 8 1 8 2 8 2 8 3 8 8 9 1 9 1 9 1 10 1 10 1 10 1 10 1 4 3 4 8 5 2 5 7 mvaconsultancy TMfS 07 User Manual 3 Figures Figure 3 1 TMfS 07 National Model File Directory Structure 3 1 Figure 3 2 Test Scenario Di
65. om home and to home P amp R trip matrices FHS THS and P amp R Summary statistics csv 3 2 Operating the Model 3 2 1 The TMfS 07 Catalog is used to operate the model running procedures Figure 3 2 illustrates the dialog box that appears in CUBE when a new scenario is created mvaconsultancy TMfS 07 User Manual 3 2 F Cube Licensed to MVA Consultancy Scenario BY01_ACP7 Application Forth Model Base GF Elle scenario Edit Run Utilities Other Apps Window Help Se in Arig Forth08 cat Scenarios Base BY01_ACP7 DMO1_AHD11 Applications Forth Model Base A ximvaconsultancy Run ID Growth Inner Loops Demand Loop Cluster on C ott Model Run Options Warm Start allows the user to Jump to a specified point in the model structure Start From Scratch C Warm Start Jump to Start Starting Outer Loop Number must be less than number of Demand Loops Model Year C7 cn C16 ca Trip Frequency C Yes No Peak Spreading C Yes No High Occupancy Vehicles C Yes No Macro Time Of Day Choice C Yes No Figure 3 2 Test Scenario Dialogue Box 3 2 2 Test scenarios can be set up edited and run using the section in the top left of the screen Double clicking the scenario will bring up a list of Catalog keys The Next and Back buttons can be used to scroll between the pages Clicking Run will start the current scenar
66. ork Each of these cells will now also contain all the values from the network within that grid cell These cells can now be mapped thematically any desired value using the quantity option in the symbology tab by right clicking on the new grid shapefile and selecting properties It is recommended that the ranges are set based on what is being mapped and what geographical location Figure 8 7 shows an example output of a thematic map for congestion in Edinburgh note this was calculated using 250m grid squares mvaconsultancy TMfS 07 User Manual 8 7 Figure 8 7 Example Thematic Output 8 6 Accessibility Analysis 8 6 1 Outputs from the Road and PT Assignment Models can be used to undertake accessibility related analysis Useful outputs relating to this area are public transport travel time skims and road network journey time isochrones An example image is illustrated in Figure 8 8 mvaconsultancy TMfS 07 User Manual 8 8 Glasgow LAAR Hamilton 50 East Kilbride Figure 8 8 Travel Time Isochrones mvaconsultancy TMfS 07 User Manual 8 9 Troubleshooting 9 1 9 1 1 9 2 9 2 1 9 2 2 9 2 3 9 2 4 9 2 5 9 2 6 9 2 7 9 2 8 Restarting a Model Run Users can make use of the warm start facility to restart a failed model run from the relevant stage See section 3 5 of this manual for further details Common Issues Missing Files One of the most common modelling issues
67. program Params or test directory are read only in which case remove this property and restart the model run If all the above fails then get in contact with the LATIS support team at LATIS transportscotland gsi gov uk mvaconsultancy TMfS 07 User Manual 9 1 Additional Information 10 1 10 1 1 10 2 10 2 1 10 3 10 3 1 TMfS Website Further information relating to TMfS 07 can be found on the Website at www latis org uk GIS Data The following GIS data can be made available upon request a base year networks a zone systems and E local authority boundaries Extra Public Transport Mode A user should not add an extra public transport mode into TMfS 07 without consulting the LATIS support team Therefore if you require a version of the model with more than the standard six modes please submit a model request form stating the requirements to LATIS transportscotland gsi gov uk mvaconsultancy TMfS 07 User Manual 10 1 wWww mvaconsultancy com Abu Dhabi Suite 118 The Avenue Business Centre Emirates Tower P O Box 33763 Abu Dhabi UAE T 971 0 2 412 4118 Birmingham Second Floor 37a Waterloo Street Birmingham B2 5TJ United Kingdom T 44 0 121 233 7680 F 44 0 121 233 7681 Dubai Office 402 Building 49 Dubai Healthcare City PO Box 123166 Dubai UAE T 971 0 4 433 0530 F 971 0 4 423 3613 Dublin First Floor 12 13 Exchange Place Custom House Docks
68. s versions of the model The file structure of the TMfS 07 National Model is illustrated in Figure 3 1 Address D TMfS07_V1 11 Model Folders a Ga TMfSO7_V1 11 5 Model Params Program Runs 27 8Y04 a Input Lines Networks E Output AHP 3 Hw 4M Or PM PT 4m Or PM a 12 a DM 5 Input MOES x Name A Params Program QRuns Temp E DemandLoop app FIMODELCHOICE APP EA TMfS07_Base app IN Copy 2 of mva2 bmp Ni mva2 bmp N mva3 bmp N mvad bmp SMvAConsultancy2 bmp ClusPro2 Script end S ClusPro2 Script message DEMANDLOOP REP FORTH_BASE REP MODELCHOICE REP MFSO7_BASE REP DEMANDLOOP S 2 FORTH_BASE S MODELCHOICE S la TMfS07_Base S Ii ClusPro2 script e TMfS07 cat E NUMBEROFCORES TXT Size 19 KB 4KB 1KB 3 039 KB 2 651 KB 2 664 KB 3 039 KB 356 KB 1KB 1KB 22 KB 69 KB 52 KB oKe 0KB 1 020 KB 828 KB 972 KB 18KB 16 KB 1KB Figure 3 1 TMfS 07 National Model File Directory Structure Type File Folder File Folder File Folder File Folder ApplicationMana ApplicationMana ApplicationMana Bitmap Image Bitmap Image Bitmap Image Bitmap Image Bitmap Image END File MESSAGE File REP File REP File REP File REP File S File S File S File S File SCRIPT File Security Catalog Text Document Date Modified 16 07 2010 09 19 06 04 2011 12 35 05 04 2011 17 13
69. same value of time and therefore cost skims are identical and are displayed in a single table Matrix of demand assigned as walk only no transit boardings for OD movements Matrix totals summary including composite cost transit distance time walk distance time total boardings boardings by mode volume of walk only trips Table 5 2 provides a summary of the Public Transport output files File Name TIME _PT_LOADED_ LOOP NET TIME _ON_OFFS_ LOOP DBF TIME _PT_IW_ LOOP MAT TIME _PT_NWC_ LOOP MAT TIME _PT_NWO_ LOOP MAT TIME _PT_COMPCST LOOP MAT TIME _PT_WKONLYTRIPS LOOP MAT TIME _MATRIX_TOTALS _ LOOP CSV mvaconsultancy TMfS 07 User Manual Dit Description File Name Assigned lines file Assigned lines file for all modes and services with TIME _PT_ASSIGNED passenger volumes by user class LOOP LIN Files produced combining information from three time periods in outputs PT parent folder Loaded network Network with assigned passenger and walk volumes LOADED_PT NET by time period Non transit legs Non transit legs essentially a series of walk links NON_TRANSIT_LEGS NTL which are generated prior to assignment for all three time periods Files produced for three time periods in PT TELMoS folder TELMOS costs TELMoS composite cost skims by time period and in C LTIM WP work non work user classes YEAR 00 DAT in work C LTIM NP YEAR 00 DAT non work
70. ses 5 2 1 The TMfS 07 PT Model can be summarised in the following stages Assignment Preparation etc common to all three time periods a input of values of time into Factor file a conversion of road model network with calculation of bus speeds including bus lanes and a creation of non transit legs essentially walk links mvaconsultancy TMfS 07 User Manual 5 1 Assignment for each time period a enumeration generation of possible routes for each OD within specified range takes no account of crowding and fares modelling is included by factoring the generalised cost associated with each mode and E evaluation calculates probability of use for enumerated routes including crowding and fares and assigns travel demand Post Assignment for each time period a addition of assigned volumes by user class to network not a standard output from assignment a matrix totals reporting and 5 reporting of rail boardings and alightings by station and rail loadings by service Post Assignment combining three time periods a addition of total assigned volumes for each time period to network including comparisons with observed data E combine rail boardings and alightings by station for each time period into a DBF file and generate generalised travel cost files 5 3 PT Input Files 5 3 1 Table 5 1 provides a summary of the input files required for the PT model These files are all in the standard Voyager format and more
71. t Do Minimum networks These files reflect the planning data and land use forecasts output from the TELMoS land use model mvaconsultancy TMfS 07 User Manual 6 2 6 3 4 Once an intervention or test is run through the transport model where appropriate relevant scheme test files can be supplied to MVA and input to TELMoS A run of the land use model can then be used to prepare new trip end inputs that reflect the land use effects associated with a particular intervention 6 4 Demand Model Output Files 6 4 1 The demand model outputs are located in Runs Year Scenario Output Growth Demand and are automatically created when running the model The outputs remaining at the end of a full model run include E GCM and GCMH generalised cost matrices from the final assignment One for each Period and Purpose combination and HWM and PTM road and PT assignment matrices E FHS THS amp NHS From Home To Home and Non Home Based Trips from the last loop of the demand model One for each Period and Purpose combination mvaconsultancy TMfS 07 User Manual 6 3 Park and Ride Model 7 1 7 1 1 7 2 7 2 1 7 2 2 7 2 3 7 2 4 7 2 5 7 3 7 3 1 Overview This section describes the process and required input files relating to the TMfS 07 Park and Ride model Model Process The Park and Ride model is run automatically within the Demand Model and contains the Park and Ride infrastructure associated
72. te Number Site Name Car Park Capacity Total Demand 1 Aberdour 20 23 2 Bathgate 172 339 3 Bridge_of_Allan 146 38 4 Brunstane 0 41 5 Burntisland 20 40 6 Camelon 30 41 7 Cupar 40 0 8 Curriehill 0 0 9 Dalgety_Bay 194 10 Dalmeny 142 87 11 Dunblane 95 23 12 Dunfermline_Q_Margaret 93 50 13 Dunfermline_Town 175 14 Edinburgh_Park 0 28 15 Falkirk_Grahamston 340 36 16 Ferrytoll 1014 17 Gleneagles 60 0 18 Glenrothes 80 17 19 Haymarket 0 0 20 Hermiston 21 Ingilston 22 Inverkeithing Figure 7 1 Example Output Park and Ride CSV File mvaconsultancy TMfS 07 User Manual 7 3 Analysis Procedures 8 1 Overview 8 1 1 TMfS 07 contains a number of additional procedures that can be used to undertake a range of analysis relating to the core model outputs These procedures include a network statistics road traffic accidents environmental analysis congestion mapping and E accessibility analysis 8 1 2 Note that where relevant these analysis procedures reflect the Annualisation Factors contained in the Params directory within the file ANNUALISATION FACTORS DBF 8 2 Network Statistics 8 2 1 This procedure calculates vehicle kilometres and road travel time for the five road user classes IW Commute Other LGV and HGV by modelled link and by local authority This procedure is applied automatically following a demand or road model run It can also be run for a model already converged from the warm start me
73. that intersect the features from the loaded network mvaconsultancy TMfS 07 User Manual 8 6 8 5 19 8 5 20 8 5 21 8 5 22 8 5 23 8 5 24 Select By Location Lets you select features from one or more layers based on where they are located in relation to the features in another layer I want to select features from KZ the Following layer s O 4M_HY_LOADED_NET O arid shp D Only show selectable layers in this list that intersect T the features in this layer RD AM_H _LOADED_NET M M Use selected features 2 features selected Apply a buffer to the features in AM_H _LOADED_NET a econo fm 2 Help OK Close Figure 8 6 Select by Location It is important to undertake this selection before proceeding with the spatial join as otherwise the join can take a very long time as the software will attempt the join for every cell in the grid The next step which is the attribution of the network information to the grid involves using the spatial join tool from the overlay box in the ARC toolbox see image below This tool will now attribute the values from the network to the cells in the grid To do this select the grid in the first dialog box and the network in the second The join operation should be JOIN_ONE_TO_ONE and the match option should be set to INTERSECTS Once the tool has finished a new shapefile will be created including only those cells in the grid that are intersected by the netw
74. that scheme code numbers 27 30 have been used for the additional schemes no modifications to the OONETOOC S script file are required it should automatically implement and undo changes depending on whether the scheme radio button is set to 1 or O However if additional attribute fields are required to be edited using the change links DBF the script file will need to be updated to reflect this 4 4 20 If more than four additional schemes are required any existing schemes that are not required could be replaced by the user s new schemes by using the same scheme code number as the scheme it is replacing Additionally a GIS shapefile and DBF could contain multiple schemes within only one file providing that there is no requirement to be able to turn those schemes on or off individually 4 4 21 The final stage of the network build process is to update the Public Transport lines files to reflect any infrastructure modifications implemented in the network The PT lines files are found in PT_lines folder as shown in Figure 4 12 mvaconsultancy TMfS 07 User Manual 4 15 3 THS07_v1 08 All E DMO1_11 dvptif txt Text Document D Base Inter Urban Bus_DMO1 _11 LIN LIN File NetworkBuild Z Intra Urban Bus_DMO1 _11 LIN LIN File amp 07 Base Network Ra_DMO1_11 BAK BAK File 5 Base S Ral_DMO1_11 UIN LIN File amp CD Network change files S Tram1a_DMOI _11 BAK BAK File 3 PT ines SS Tramia_DM01_11 LIN LIN
75. vious section Note that this will always import the last results sheet so must be undertaken directly after each catalog run The results will be output in the Controls sheet in the appropriate columns and these should be put directly into the site file As a test to ensure formatting is correct it is recommended that the catalog is ran through a second time to make sure no stray commas etc exist as this is quicker to check than a full demand model run Note that the base attractiveness factor for new sites should be set at the same value as the site attractiveness factor mvaconsultancy TMfS 07 User Manual 7 2 7 5 Park and Ride Output Files 7 5 1 The model outputs the following files from the park and ride process a AM FHS represents the AM period 0700 1000 From Home Park and Ride Person Demand Matrices PM THS represents the PM Period 1600 1900 Home Park and Ride Person Demand Matrices and csv represents the car park occupancy summary files One file is output for each trip purpose and each file describes the official car park capacity and the modelled car park occupancy This information can be used to ascertain the number of vehicles parking outside the main car park An example output is shown in Figure 7 1 E PRN details the park and ride iterative procedure convergence results Shows the number of loops required as well as the criteria that was met to satisfy convergence requirements Si
76. with the relevant Base Year Do Minimum and Reference Case networks This includes parking at rail stations The model operates within the AM time period for home based travel purposes Home Based Commute Home Based Other and Home Based Employers Business The model reverses the AM peak outputs to reflect the PM peak period The process allows up to 250 Park and Ride sites to be included within the model The model calculates the use of Park and Ride sites by identifying the road and public transport travel costs associated with relevant travel movements Where the modelled occupancy of a site is higher than the defined capacity a penalty an increased attractiveness factor is added for any additional users The Park and Ride model cannot be run separately as it relies on inputs which are an integral part of the demand model However a Park and Ride test can be undertaken by running the model with the PnR only catalog key checked Note that the outer loop number also needs to be defined and if certain files namely the six current loop demand inputs for instance AM_HOZ_D1 MAT are not in place the model will fail Park and Ride Input Files The Park and Ride Site input file contains a line for each site Each line represents the following information and is separated by commas a Site Number These must be in sequential order a Site Name No spaces allowed Zone Number where the site is located Car Park Charg
77. yager software new transport schemes or tests can be coded using a DBF file This process allows for transport schemes to be coded within a GIS system and transferred to the model The DBF file can also be updated without a GIS system 4 4 10 Figure 4 9 presents an example of a DBF file The columns required depends on whether the DBF represents links nodes or changes that are required for a scheme The structure and purpose of the DBF files is discussed below mvaconsultancy TMfS 07 User Manual 4 12 E Microsoft Excel AWPR net dbf LE E cle Edt yew Insert Format Tools Data Window Help ees D GAY E I 21 M 100 Arial 10 BLU PSP SHO NN EE L d A Al amp TOID S A B H J K L M is P Q Ra 1 foi SILA URBAN LINK TYPECAPACITY NUMBER_ITRUNK_RCBUS_LANEHGV_LANEONE_WAY DISTANCE SPEED CAP ANODE B NODE A B i 2 0 25 0 3 2 0 0 0 0 0 157926836021 100 3600 1 0 0 70005 441 3 0 25 0 3 1800 2 0 0 0 0 0 16684953466 100 3600 1 0 0 44137 700 4 0 25 0 3 1800 2 0 0 0 0 0 13171334087 100 3600 1 0 0 70005 700 5 0 25 0 3 1800 2 0 0 0 0 10810058605 100 3600 1 0 0 70000 700 6 0 25 0 3 1800 2 0 0 0 0 0 23314302321 100 3600 1 0 0 70001 441 7 0 25 0 3 1800 2 0 0 0 0 0 22788162334 100 3600 1 0 0 44132 700 8 0 25 0 3 1800 2 0 0 0 0 0 13465435995 100 3600 1 0 0 70001 700 9 0 25 0 3 1800 2 0 0 0 0 0 023550397 30 100 3600 1 0 0 70002 700 10 0 25 0 3 1800 2 0 0 0 0 0 02140073720 100 3600 1 0 0 70003 700 11 0 25 0 3 1800 2 0 0 0 0

20110526 LATIS TMfS07 User Manual V4.3

Contents

Download Pdf Manuals

Related Search

Related Contents