Configurations

okay, let's learn how to get optioneer fully configured for your infrastructure project we will look at docid jtrk7g3dzvw8ybiv0ite to collate the docid\ uon1ceip4jc8s6sdrysfs you have added to optioneer, and then dive in to docid\ n3fmiwnuuv8uppgtvdeyv if you are using the screening version of optioneer, it is likely that you will have default configurations set up already if you are exploring the development or enterprise subscription, you will receive hands on support from us to make sure everything is configured exactly in line with your company's priorities there are a few key steps involved in configuring optioneer and they are docid jtrk7g3dzvw8ybiv0ite pulling together the data you want optioneer to evaluate docid\ n3fmiwnuuv8uppgtvdeyv telling optioneer which logic blocks to use use on that data if necessary, docid\ bc37whybkkj1hd3hzuay then head to docid\ lfrskxndb1bp2mta6augq to really start accelerating your project development! configurations configurations are used to dictate to the engine how to perceive constraints, and what technical engineering rules to follow when routing your asset they allow you to determine exactly how your project data develops and interacts with the layers on your map when you assign appropriate weightings to your constraints and calculate any relevant metrics for your project they can also be used to configure objectives for route optimisation y ou can also set more generic technical limits in configurations, such as the maximum or minimum elevation, slope, or angle change optioneer stores your configurations in two ways user created configurations and past results (read only) user created configurations an editable version of every manually created configuration in your project can be found in the configurations page past results (read only) whenever you submit a case, whether successful, failed, or still running, optioneer saves a read only version of the configuration in 'past results ' by default, this is not visible it acts like a record, allowing you to keep track of all of the values that were inputted for a specific case for example, this is useful if you need to understand why your current route is generating differently than an older option, if you want to compare cases against each other, or if you want to review the values you entered for a previously created parameter you can also view a result's configuration and parent configuration in the results library to do this in the results library, click the symbol beside any result then click directly on the result's name a case inspection drop down box appears click on the case inspection drop down to open it the result's configuration and parent configuration names are listed you can click on either name to be re directed to its location in the parameters tab for a quick orientation in the parameters page, please view the click path below assigning collections to configurations as discussed in project layers, once you have familiarized yourself with your project's data layers, you can use docid jtrk7g3dzvw8ybiv0ite to combine them into one group, which can then be split into more specific categories note only the list of collections relevant to activated design rules will be visible if you have no active design rules, the list of configurable collections will be empty once you have created collections, you must now assign them to your configurations to assign a collection to your configuration, navigate to the configuration selection tool in the parameters tab then select any configuration from the available 'user created' list use the search bar to filter down the list, if needed under 'primary settings,' click 'datasets' to open the list of required datasets from this list, click the dataset you want to assign to your configuration the 'select collection' panel opens from the drop down menu, select a collection (i e v1, v2 etc ) to assign to your dataset when finished, click 'save configuration' design rules if configurations are the framework for your project, design rules are the framework for your configuration they allow you to apply specific logic, such as additional calculations or engineering design, to your routes and data importantly, they are conditional, meaning that if you input certain information, your generated or evaluated route will act in a specific way conversely, if you do not input certain information, your route will act in another way toggling design rules on or off also allows you to determine what type of asset you are building you can also configure multiple assets at the same time for example, you could toggle on design rules for towers or overhead lines but keep design rules for auger bores toggled off as a result, the engine would not use any auger bores when generating options to locate design rules, click open any existing configuration the list of available design rules will appear in the second panel to show only active design rules, click the filter icon asset type you can use the 'asset type' setting to configure an asset's costing, penalty, and technical parameters toggling on a specific design rule opens the 'edit parameters' panel; from here, you can enter information that tells the engine to populate assets in specific areas or define no go zones in certain layers align assets to set measurements, such as elevation, slope, depth, or length calculate certain technical and layer specific cost objectives when generating or evaluating routes each design rule has several different parameters attached to it additionally, optioneer allows you to toggle on one or multiple design rules for one asset or multiple design rules for a series of assets, if necessary as a result, this means your configuration will not be limited in size or scope to access and edit design rules for available assets select any configuration from the available 'user created' list use the search bar to filter down the list, if needed open the 'group by' drop down menu and click 'asset type ' the list of available design rules automatically updates from this list, open any asset and toggle on any of the available design rules the 'edit parameters' panel opens edit each parameter, as needed when finished, click 'save configuration ' this will overwrite your previous configuration pro tip a time saving feature fill option where you can bulk fill all values using attributes added to the layers please visit docid jhfpa5faxkouptffawap to learn how to enter and manage layer based penalties and costs prioritizing multiple assets the most important things to consider when configuring multiple assets are which assets you're interested in using and where they should be placed on your map, i e on land, underground, or over/under specific crossings how their parameters will be set up and conditioned how you want the engine to prioritize them in your project space pro tip parameters can be used in lots of different ways for example, setting the maximum elevation of microtunnels to be higher than wood poles means that if your route encounters larger obstacles like mountains or hills, the engine will prioritize tunneling over other construction methods for example, consider a route built primarily with wood poles as discussed above, you would likely edit and refine multiple design rules for this asset to ensure its parameters align with your project's needs however, after reviewing your map, you realize some rivers intersect your generated route, making wood pole construction infeasible in this area to circumvent this, you select a second asset, such as microtunnels, and toggle on any relevant design rules however, you now must tell the configuration where you want to place wood poles vs microtunnels to do this, use the search bar to locate and toggle on the 'global parameters' parameter it allows you to edit the order of priority for multiple assets so that, if every asset is equal, the engine will choose to prioritize an asset with higher priority when generating a new route in this scenario, wood poles are ranked higher as the primary asset and microtunnels are ranked lower because they are only used to cross bodies of water lower ranked assets will only be placed under special circumstances to configure these circumstances, toggle on the technical parameters design rule and scroll to locate the 'prioritise installation of \[specific asset] within \[specific layer]' parameter the technical parameter design rule is also useful when working with multiple assets for example, you can also use the 'prioritise asset installation' parameter, which tells the engine to make a certain asset the highest priority if it encounters a specific type of crossing, like a motorway, water crossing, or access road objectives as you learned in https //howto optioneer ai/platform/justifying decision making#c5c8j , objectives measure your options' trade offs to find the most optimal results in parameters, you can input values that tell your configuration which specific objectives will influence your project's optimization simply put, toggling specific design rules on or off affects which objectives will be considered as trade offs on your pareto front chart you can toggle on objectives for cost measures capex and opex (often referred to as technical risk) penalty measures environmental and consenting risks normalized distance (to linear features) uses objective scores to measure how close a route is to a linear feature and encourages staying close to linear features without forcing the algorithm to follow them exactly visual impact assesses how visible overhead transmission lines are between data layers, specific to trade offs for overhead electricity transmission like pylons and towers note if you do not toggle on at least one objective parameter, you will get a 'there is an error with your config' message you must toggle on at least one objective related parameter per configuration to access and edit design rules for objectives select any configuration from the available 'user created' list use the search bar to filter down the list, if needed open the 'group by' drop down menu and click 'objective ' the list of available design rules automatically updates there is also an additional design rule grouping called 'no value ' design rules that are toggled on will not activate or affect any objectives for example, 'costing' or 'penalty' parameters under 'no value' will configure costing and penalty parameters but they will not enable the 'cost' or 'penalty' objective this means that they will affect cost and penalty calculations (i e tradeoff values) but they will not enable specific objectives setup run once you have successfully created a configuration, you can attach it to any point, line, or polygon when you run a generation, evaluation, corridor generation, or site selection case each case processes your data and outputs it on your map in different ways further, you can run multiple cases with the same configuration; this means you can display one route in a mixture of formats to get a larger swath of information note that different setup modes only use specific types of data this means the case you pick determines the data you can run through it evaluation mode lines only generation and corridor generation mode points only site selection mode polygons only best practice before picking a configuration, confirm that you have toggled on all necessary design rules and inputted all relevant values and weightings your data may be set up with errors if certain parameters have not been given values also, ensure that all layer specific parameters have a value above 0 or there will be nothing to optimize for because every area on the map will be weighted equally