You are on page 1of 78

FUTURA2011 November3rd PalmSprings,CA

Items
WhatisCCS? WhyCloud? Benefits

WhatisCCS?
CUBECloudServices Acloudbasedenvironment

fortraveldemandmodelinginCUBE

WhyCloud?
Speed Scalability Sharing Easeofaccess Easytomanage

Benefits
Internet:movementfromadesktopbound,lockedenvironmenttoaninternetbased,open,

sharable,workfromanywhere/anytimeenvironment
CommunityResource:modelapplicationandplanninganalysisdonebynonexpertsusing

commonwebbrowsersmovingmodelstoanactiveroleincollaborativetransportation planning
CloudComputing:placementofthemodels,dataandsoftwareinacloudcomputing

environmentloweringhardwarecostslocallywhileprovidingunlimitedhighspecresources
Lowercostsfortheuser:movementfromlocallylicenseddesktopstoasoftwareasaservice

model.Monthlysubscriptionbusinessmodelallowingmanytousethemodelatlow,oreven, nocost
LessensITcomplexity:muchoftheITburdenofmodelingisshiftedfromtheusertothe

vendor
DataandSoftwareIntegration:easiertointegratewithexternalsystems:development

reviews,regionalairqualityanalysis,pavementmaintenancesystems,trafficandtransitITS systemsandtoreceiveandusedatafromdataprobes,detectorsandstaticdatasources

FUTURA2011
November1st PalmSprings

,CA

Items
UnderstandingCCSdirectorystructure Inputfilereferences Outputfilereferences OutputtoInternalinputfile Filepathkeys Filereferencetokens Inputfileswithsimilarnames Userprograms

Items
Systemcommands CCSclustersetup MultipleapplicationsOutput>Input Reports&ApplierGroups Bestpractices

UnderstandingCCSDirectory Structure
Minimal/fixeddirectorystructure

UnderstandingCCSDirectory Structure
Model Thishasauniquefoldernameforeachmodel Workingdirectory/scenariodirectory Apps Modelscriptfileandcataloginformation(.xml) Inputs Allinputs(scenariospecific,fixedinputs) Outputs Emptyandusedtostorefixedoutputswhenmodelis run

UnderstandingCCSDirectory Structure
CCSExport Compilemodelscriptsandmodelcatalog Createonemodelscriptanda.xmlfileinweb\apps Copyinputfilestoweb\inputs Compresswebfolderforupload CCSModelRun Eachscenariorungetsitsowncopyofthemodel folder AlloutputsaresavedintheOutputsfolderorthe Modelfolder(scenario/workingdirectory)

InputFileReferences
Scenariospecificinputs(e.g.,zonedata,highway

networketc.) Fixedmodelinputs(e.g.,frictionfactors,modechoice factorsetc.) Internalfileinputs(READ,LOOKUP,RENUMBER statements)

InputFileReferences
ScenarioSpecificInputfiles FILEIinputfilestatementswith{SCENARIO_DIR} inpathname
e.g.,FILEIZONEI[1]={SCENARIO_DIR}\Zones\ZoneData.DBF

CCSexporterdoesnotrecognizescenariospecific inputs
Warning:ScenarioSpecificInputs.TheApplicationscriptsare

valid,butthereiscurrentlynointerfacetothisdatainCCS.

Usefilekeys
e.g., FILEIZONEI[1]={zonedata}

InputFileReferences
FixedInputFiles FILEIstatementswithfixedfilepath
FILEIRECI=C:\Model\Parameters\MC_PAR.DBF

CCSexporterwillcopythesefilestotheInputsfolder TheCCSmodelscriptwillbeupdatedas
FILEIRECI={SCENARIO_DIR}\Inputs\MC_PAR.DBF

CCSuserwillnotbeabletoupdateanewversionor

editthisfile Useafilekeytoinputthisfile

InputFileReferences
InternalInputFiles FILE=statementsforREAD,RENUMBER,LOOKUP statements.
e.g.,READFILE="{SCENARIO_DIR}\INPUT\ACCESS.PRN

CCSExporterdoesnotacceptanyfilepathkeysinFILE=

statements.Exporterdoesnotcopythisfiletotheinputs directory.
Warning.ThefollowingInternal"FILE="entriesarepresentinthe

model.TheyhavebeenassociatedwiththeVOYAGERcommandshown below,andcopiedtotheappropriatefolder.NotethatforCCSPublish, thebestandsafestapproachistoavoiduseofFILE=,andusean alternativeVOYAGERconstructifavailable;e.g.forPRINTcommands, usePRINTO=.

InputFileReferences
Useauserdefinedkeyforthesetypesoffilesor

referencethesefilesusing{CATALOG_DIR}key.
e.g.,READFILE="{ACCESS}"

OutputFileReferences
FILEO,PRINTFILE=andCOPYENDCOPY

statements
e.g.,FILEOMATO[1]=

"{SCENARIO_DIR}\OUTPUT\MATRIX\OUTPUT.MAT

CCSmodelrunwilloutputthesefilestotheoutputs

directoryunlessthefileisoutputdirectlytothe scenariodirectory Subsequentstepsreadingthesefilesinternallywillfail inCCS. Outputallscenariospecificfilesdirectlyto {SCENARIO_DIR}


e.g.,FILEOMATO[1]="{SCENARIO_DIR}\OUTPUT.MAT

OutputtoInternalInputFile
FILEO/COPY/PRINTOtoREAD,

RENUMBER,LOOKUP(FILE=)statements
Program1Matrix: FILEOPRINTO[1]="{SCENARIO_DIR}\READ_OUT.PRN"

Program2Matrix:
READFILE="{SCENARIO_DIR}\READ_OUT.PRN

CCSExporterwillshowaerrormessage
Warning:ThefollowingInternalfiles(definedviaFILE=)couldnotbefound,

sotheApplicationswillnotruncorrectly

Itisagoodpracticetodirectlylinkoutputfilesto

inputsinsubsequentprogramsratherthanreading internally

FilePathKeys
FILEIstatementswithuserdefinedfilepathkeys
FILEIMATI[1]="{LOCATION}\AllWalk.MAT"

CCSexporterdoesnotacceptanykeys(otherthan

{CATALOG_DIR})infile PATH ofFILEIstatements.


Error:ThefollowingfileshaveKeysintheirPath.Thisconstructis

incompatiblewithCCS.

Usethe{CATALOG_DIR}keytorefertothisfileasshown

beloworusefilekeysasdiscussedabove
FILEIMATI[1]="{CATALOG_DIR}\Base\Input\AllWalk.MAT"

FileTokens
Filereferencesusingtokens
e.g.,READFILE="@CPI_FILE@"

CCSexporterdoesnotgiveanywarningsorerrors CCSmodelscriptisupdatedtoread
READFILE={CATALOG}\OUTPUTS\@CPI_FILE@

Usevalidfilepathsinsteadoftokens

InputFilesWithSimilarNames
CCSexporterappendsasuffix(_cw#)inputfileswith

similarnames. Italsoupdatesthecatalogkeyvaluesforthesefiles withupdatedfilenames


e.g.,{File1}=C:\Model\Base\ZoneData.dbf

{File2}=C:\Model\Base\Parameters\ZoneData.dbf
Exporterwillcopy2filestotheinputsfolderwiththenames ZoneData.dbf&ZoneData_cw1.dbfandupdatethefilekeyvaluesas follows
{File1}=inputs\ZoneData.dbf {File2}=inputs\ZoneData_cw1.dbf

UserPrograms
BuiltinuserprogramsinCUBE Programsbuiltbymodeldeveloper

UserPrograms
BuiltinUserPrograms
e.g.,TRCOPY,TRDEL

CCSexporterwillshowawarning
Warning:UserProgramscurrentlyrequiresomemanual

interventiontoimplementinCCS.

Builtinuserprogramswillworkwithoutanyproblems

inCCS

UserPrograms
Usersupplieduserprograms
e.g.,any.exefilestoperformspecialfunctions

Allinputfilesandoutputfilesto/fromtheuser

programshouldbereferencedtothe {SCENARIO_DIR} Updateanycontrolfiles/inputfileswithfilepaths Executetheuserprogramsfrom{SCENARIO_DIR}

SystemCommands
AnyMSDOSsystemcommands
e.g.,COPY,DELetc.

CCSExporterwillshowawarningmessage
Onlycopysystemcommandswithnowildcardsarecurrently

supportedbyCCSforfilenameconversion.

Itisrecommendedtocopytheindividualfilesusingone

copycommandforeachfileasshownbelow.
E.g.,*COPY{SCENARIO_DIR}\INPUTS\*.csv{SCENARIO_DIR}

Willnotwork *Copy{SCENARIO_DIR}\INPUTS\File1.csv {SCENARIO_DIR}

CCSClusterSetup
CCSprovidesscalabilityofavailableclusternodesfor

eachmodelrun ProcessNum/ProcessList forDistributeMultistepand DistributeIntrastepstatementsshouldbecalculated withinthescriptbasedonthenumberofcores availableforthatrun Thenumberofcoresavailableforthemodelrunis inputusingascenariokey. Noneedforclustercommandstostartandclose clusternodes.
e.g.,*ClusterTest110startexit

MultipleApplicationsOutput/Input
FromApplication1
FILEOMATO[3]="{SCENARIO_DIR}\OUTPUT.MAT

InApplication2
FILEIMATI[1]="{SCENARIO_DIR}\OUTPUT.MAT

Multipleapplicationsarenotcurrentlysupportedin

CCS CCSExporterwillshowawarningmessage
Warning:ThefollowingfilesrequireapreviousApplicationtoberun

firstinordertocreatethem

Reports&ApplierGroups
CCSdoesnotcurrentlyallowuploadingmodelswith

reportsormorethanoneappliergroups Uploadingamodelwithreportswillcauseanerrorin theuploadingprocess CCShasinbuiltanalysistoolstodochartsandmaps Deletereportsandappliergroupsbeforeuploading

BestPractices
Usefilekeysforinputfiles Useuniquefilenamesforscenariospecificinputfiles Referenceallmodelrunoutputstothe

{SCENARIO_DIR} Directlylinkoutputfilesinapplicationmanager insteadofreadingthefileinternally Alwaysusedoublequotesforfilepathsandnames

Items
WhatisCCSexporter? Register\Login Switchingusers Active\Pendingcatalogs Exporting Handlingerrorsandwarnings Uploading Pending

WhatisCCSexporter?
BuiltinCUBE6.0tool PreparesyourmodelforCCS UploadsthemodeltoCCS ListsyourexistingCCSmodels(pending/active) RequiresaCCSaccounttoaccessthefunctionsof

exporter LocatedatFile>Export>CloudServicesExport

Register/Login
www.planthecity.com CCSwebsite Providesaccessintowww.planthecity.com Freetoregister

Exporter

Export/Upload

Models

Errors,Warnings &Logs

Status

SwitchingUsers
AllowstoswitchCCSuseraccountsinsideexporter File>SwitchUser

Active/PendingCatalogs
ActiveCatalog ACCSmodelwhichisapprovedand

isreadytoberun PendingCatalog ACCSmodelwhichhasbeen uploadedbytheuserandiswaitingforCitilabsto approvethemodel Approvalprocess


CheckthemodelforcompatibilitywithCCS Providemodeladminpermissions

Exporting
SMandAMshouldbeopen Checkthecatalogname Export Compilesmodelscripts BuildCCSscript Buildcataloginformation(.xml) Copyinputs Compressuploadfolder Createswebandweb.zipfile Listserrorsandwarningsfromtheexportprocess

HandlingErrorsandWarnings
Errors Criticalissueswhichhavetobeaddressed

beforeuploadingthemodel Warnings Possibleissuestobereviewedbytheuser Details


ErrororWarning Description Numberofinstances

Locationofeachinstance

Uploading
Title NameofthemodelinCCS Description Abriefdescriptionofthemodel.This

descriptionwillbelistedinwww.planthecity.com Checkuploadlogtoconfirmmodelupload

WhatsNext?
ModelwillbelistedasPendingon

www.planthecity.com ReviewandApprove Assignadminprivilegestotheuser Inviteusertoedit/runmodel

Items
Activateapprovedmodel Modelspage

ActivateApprovedModel
UserinviteemailfromCitilabs Clickonloginlink Loginwiththeusernameassociatedwiththatemail Multipleusernameswithsameemailisallowed

ModelsPage
Listsallyourcurrentmodels Selectcontractsforyourmodels

Items
Addnewscenarios Upload/editscenarioinputs Deletescenarios

AddScenarios
AllnewscenariosarelocatedunderBasescenario CreateChild Scenario createsanewscenariounder

thecurrentlyselectedscenario
Name Description Sharetype

Inputfilesandkeyvaluesarecopiedfromtheparent Collapseandexpandscenariofamilies

Upload/EditScenarioInputs
EditScenario activateseditcontrolsforthe

currentlyselectedscenario Inputfiles(filekeys) Allinputfilescanbeupdated byuploadinganewfile Checkboxes(Booleankeys) Allotherkeytypesarelistedastexteditboxes

DeleteScenario
DeleteScenario deletesthecurrentlyselected

scenario Requiresuserconfirmation

Items
Model/Clustersetup Selectingcontract Schedulingruns Checkingrunstatus

Model/Clustersetup
CUBE/CCSmodelrunenvironment
e.g.,CUBE5.1.4,CTRAMP5.1.4,etc

Clusterprocessname shouldmatchwiththename

usedinyourmodel Numberofcorestobeusedforthismodelrun

SelectContract
Contracttobebilledforthecurrentmodelrun Liststheavailablecontractsunderyouradministration

ScheduleModelRuns
Selectscenario UpdateNumberofProcessorCoresAvailablefor

ModelRun
SameasNumberofCoresunderModelsetup

ScheduleScenariostartsmodelrun Requiresuserconfirmation

CheckModelRunStatus
Status Listscurrentlyrunningscenariosandcompleted scenarioruns Status

Pending themodelrunispendingtobestarted Running themodeliscurrentlyrunning Completed themodelruncompleted

Items
Modelsetup Sharingyourmodel Managemodelusers Trackingmodelrunactivity

Modelsetup
Modellogo appearsonthemodelpage Modelrunenvironment CUBEversion Clusterprocessname sameastheoneusedinyour

modelscripts Numberofcores
Numberofprocesscoresforthemodelrun Multiplesof8(8coresoneachCCSmachine)

Sharingyourmodel
Inviteusers Useremail Userscanhavemultipleaccountsunderthesameuser email Modeluservs ModelAdmin Modeluserwillnothaveaccesstomodeladminpage Modelusercannotinvite/manageotherusers

ManagingModelAccess
Disable/Enableadminpermissions Setupmodelrunpaymentoption Deleteuserfromthemodel

Items
Datapage Workingwithoutputfiles Managingdatafolders

DataPage
Providesaccesstoallyourscenariorunoutputs Organizedbymodelsandscenarios FollowsaMSWindowslikefolderstructure Toolstoorganizeyouroutputdata

WorkingWithFiles&Folder
Copyfilesbetweenfolders Downloadfiles UploadfilesfromyourPC Deletefiles Add/Download/Deletefolders

Items
Networks/Maps Database/Charts

Networks/Maps
CCShasmaptoolstoplotnetworkdata Theloadednetworkhastobeinageodatabase

(.mdb) Thegeodatabaseshouldhavethecorrectprojection defined Copymdb to{SCENARIO_DIR}andwriteloaded networkstomdb UseGeometrySourcekeywordintheNETWORK programtoassignshapeinformationtoloaded network

Database\Charts
CCSprovides4charttypestoplotdata Thedatabaseshouldbeavailableinageodatabase

(.mdb) Thedatashouldbesummarized ChartTypes:


Pie StackedBar Line Scatter

Database\Charts
PieChart
Value
Category1 7%

Category Category1 Category2


Category2 13%

Value 100 200 300 400 500

Category5 33%

Category3 Category4

Category3 20%

Category5

Category4 27%

Database\Charts
StackedBarChart
ChartTitle
350 300 250

Category Category1 Category2

Columns 1 2 1 2

Value 100 200 200 100

Value

200 150 100 50 0 1 Columns 2 Category2 Category1

Category1 Category2

Database\Charts
LineChart
30 25 20 Value 15 10 5 0 0 1 2 Columns 3 4

Category Category1 Category2 Category1


Category1 Category2

Columns 1 1 2 2 3 3

Value 10 20 15 25 5 15

Category2 Category1 Category2

Database\Charts
ScatterPlot
6 5 4 YAxis 3 2 1 0 0 1 2 XAxis 3 4 5 Category1 Category2 Category3

Category Category1 Category1 Category2 Category2 Category3 Category3

XAxis 1 2 0 4 2 3

YAxis 2 3 2 3 4 5

Items
Contractdetails ContractActivity InviteUsers ManageUsers

ContractDetails
Contracthours

ContractActivity
Listsallthemodelrunsunderthecontractactivity

InviteUsers
ContractuserVsContractAdmin Contactuser cannotinviteotheruserstothecontract Contractuser cannotchangeuserprivilegesorremove usersfromthecontract

ManageUsers
Changeuserprivileges Removeuserfromcontract

You might also like