costiq user guide - seerbygalorath.com · in costiq, a case represents a completed seer project,...

25
CostIQ User's Guide Page 1 SEER CostIQ User’s Guide Galorath Incorporated www.galorath.com Corporate Headquarters El Segundo, CA USA Phone: +1 (310) 414 3222 E-mail: [email protected] Support: [email protected] International Headquarters Galorath International Ltd. Farnham, Surrey UK Phone: +44 (0) 1252 724518 E-mail: [email protected]

Upload: others

Post on 01-Aug-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 1SEER CostIQ

User’s Guide

Galorath Incorporated

www.galorath.com Corporate Headquarters El Segundo, CA USA Phone: +1 (310) 414 3222 E-mail: [email protected] Support: [email protected] International Headquarters Galorath International Ltd. Farnham, Surrey UK Phone: +44 (0) 1252 724518 E-mail: [email protected]

Page 2: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 2

Copyright 2018 by Galorath Incorporated. SEER® is a trademark of Galorath Incorporated. No portion of this manual (except where explicitly stated) may be reproduced in any form without the express written permission of Galorath Incorporated.

Page 3: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 3

SEER CostIQ User Guide Contents Introduction .............................................................................................................................................. 4 Setting Up A Data Source .......................................................................................................................... 5 Overview: The Case-Based Reasoning Tool.............................................................................................. 6

Selecting a Domain ............................................................................................................................... 7 Specifying Requirements ...................................................................................................................... 7 Rating Relevance................................................................................................................................... 8 Editing the WBS Structure .................................................................................................................... 8 Parameter Settings ............................................................................................................................... 8 Exporting to SEER.................................................................................................................................. 9

Overview: The Domain Authoring Tool .................................................................................................... 9 Create or Edit a Domain...................................................................................................................... 10 Adding Requirements ......................................................................................................................... 11 Adding Cases....................................................................................................................................... 11 Entering Requirements Values ........................................................................................................... 12 Parameter Defaults............................................................................................................................. 12

Tutorial: CBR Tool................................................................................................................................... 12 Background ......................................................................................................................................... 12 1. Start the CBR Tool .......................................................................................................................... 12 2. Select a Domain ............................................................................................................................. 12 3. Specify Primary Requirements........................................................................................................ 13 4. Specify Derived Requirements........................................................................................................ 14 5. Rate the Relevance of Each Case .................................................................................................... 14 6. Edit the Work Breakdown Structure............................................................................................... 15 7. Parameter Settings ......................................................................................................................... 16 8. Create a SEER Project...................................................................................................................... 17

Tutorial: DAT .......................................................................................................................................... 18 Background ......................................................................................................................................... 18 1. Start the DAT................................................................................................................................... 19 2. Create a Domain ............................................................................................................................. 19 3. Edit the Domain .............................................................................................................................. 19 4. Add Requirements to the Domain .................................................................................................. 20 5. Add Cases to the Domain................................................................................................................ 21 6. Setting Derived Requirements Importance .................................................................................... 23 7. Set the Relative Importance of Each Requirement......................................................................... 24 8. Set the Parameter Handling Default ............................................................................................... 25 9. Save the Domain ............................................................................................................................. 25

Page 4: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 4

Introduction CostIQ is a tool for creating a SEER project based on a limited set of high level project requirements. This allows you to create the initial version of an estimate at a very early stage in the development process, at a point where you may know the basic requirements, but nothing else. CostIQ works by applying a technique called case-based reasoning to a database (known as a case base) of similar development projects, where each project has been amended with high level requirements and performance information. It uses these ‘requirements’, along with your inputs and work element selections, to produce an estimate based on corresponding elements in the case base. You can then tailor this estimate to more closely match the project. CostIQ actually consists of two separate tools, along with the case base and other supporting files. The Case-Based Reasoning Tool (or CBR) is the one which you actually use to select cases based on your requirements and create a SEER project. The other tool, known as the Domain Authoring Tool (or DAT) is for setting up and administering the case base. CostIQ actually can serve you in a number of roles. Numerous domains (types of systems) are delivered with it, which you can immediately put to good use. You also can create your own domains. Another role of CostIQ is as a knowledge management tool; if you already have created many projects, CostIQ enables you to associate them with broadly identifying metadata, and then to retrieve and freely combine past projects in new ways. You are fruitfully reusing past work and realizing great efficiencies doing so. Using the SEER Enterprise Database will greatly facilitate this process.

Page 5: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 5

Setting Up A Data Source CostIQ can use either the CostIQ Dedicated Database or the SEER Enterprise Database (SEER-DB) to store case data. The SEER-DB is designed to store ongoing and completed SEER project data; the CostIQ Dedicated DB is, as its name implies, dedicated to storing CostIQ information. This section covers accessing the databases but not setting them up. It also does not cover setting up system-level connections to the database on the client desktop; these tasks are covered in a separate document, CostIQ Manual SEER-DB Setup and Connection. The following guidance applies to both the CostIQ CBR and DAT tools:

1. Click on the Data Source menu and select either CostIQ Dedicated DB or SEER Enterprise DB. The Dedicated option will be a specialized Access database that either was installed with CostIQ or perhaps instead shared among multiple users.

2. In the "Specify Source" dialog box, enter a data source or select one by pressing the Specify

button. Your selection will only be used for CostIQ; it will not affect SEER-DB connections used by other SEER applications.

Page 6: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 6

3. If you clicked on the Specify button, the "Select Data Source" dialog box will appear. Choose the data source that you will be using and press the Select button.

4. The "Odbc Credentials" dialog box will next appear. You will take different actions depending

on the database type: • SEER Enterprise Database. This is SQL Server and so permissions are required to access

it. Enter a valid User ID and Password. For the CostIQ CBR tool, the ID can be that of a CostIQ admin or user account. For the CostIQ CBR DAT, you must use a CostIQ admin account. Click on OK; you will now be connected.

• CostIQ Dedicated Database. No credentials are required, so just press Ok.

Overview: The Case-Based Reasoning Tool When you use the Case-Based Reasoning Tool, you start with your requirements, and you go through a series of simple steps which end with the creation of a SEER project, which will open in the appropriate SEER application.

Page 7: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 7

The CBR Tool Interface

Selecting a Domain The first step is to let CostIQ know what kind of project you will be estimating by selecting a domain. Domains each represent a unique type of system, being defined on the basis of a common function, application, or type of technology. A domain in turn contains cases, which are specific past instances that are used for future comparison. For example, the domain citrus could contain cases for an orange, lemon and grapefruit. Each case in the CostIQ case base represents a completed SEER project.

Specifying Requirements Each domain is associated with a unique set of predetermined requirements, which are based on typical requirements for the types of systems represented by the domain. After you have selected an appropriate domain, you must specify values for these requirements.

Derived Requirements Derived requirements are intended to ease the informational requirement for generating a new project. As their name implies, derived requirements’ values are determined based on entries in an initial (primary) set of requirements. In the CBR tool, they are shown on a separate tab so that their values can be determined once the set of primary requirements has been specified. If the primary requirements for a missile, for example, include its range, speed, and payload, the derived

Page 8: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 8

requirements could include its weight, length, and diameter; CostIQ will provide suggested values (which you may override) for those requirements.

Rating Relevance After you have entered requirement values, CostIQ will select cases from the domain which most closely match those requirements. It will give each of the cases a relevance score; you can enter your own relevance rating for each case, from "Not Relevant" to "Extremely Relevant".

Editing the WBS Structure CostIQ generates a SEER work element structure (also known as a WBS structure) that is a composite of all retrieved cases based on your relevance selections; it will be exported to SEER, and will serve as the framework of your SEER estimate. The cases which are included in the composite WBS depend on the relevance setting; cases at or above the relevance rating will be included.

While the WBS structure that is generated will include all work elements from all included cases, not all may be relevant for the current project. You therefore can view the work element structure and choose which work elements will be exported to SEER, and which will not. This is done by clicking checkboxes next to each element.

Note the percentages shown to the right of each element; these indicate the proportion of cases that include this element. For example, if 4 out of 5 cases include an element its percentage will be 80%.

Parameter Settings When CostIQ exports the WBS structure to SEER, it automatically generates parameter settings within each WBS element. After you select the work elements to be included in the exported WBS structure,

Page 9: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 9

you can choose the method which CostIQ will use to generate those settings. These methods are all based on the parameter values of the included cases; options include values set across the full range of those found in relevant cases ("range"), averaged without weighting, and averaged with greater weight given to more relevant cases. For the last option, you may select either automatically determined weightings or those you specified.

Exporting to SEER After CostIQ has created a project in SEER, you can add, remove or change work elements, and adjust parameter settings as necessary, just as you would with any SEER project. The advantage of using CostIQ is that rather than starting with a blank project and filling it in, you will be starting with a WBS structure (and parameter settings) based on your requirements.

Overview: The Domain Authoring Tool The CostIQ Domain Authoring Tool (or DAT) is an administrative tool for maintaining the data which CostIQ uses to generate estimates. This data is contained in a database that is referred to as the "case base". In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements are NOT parameters. Parameters are specified in SEER, while requirements are specified in CostIQ; the latter would be more recognizable to a lay person or something seen in a brief description of a system. For example, an engine’s requirements could be described by its horsepower, valves and fuel type. When modeling the engine inside SEER, a much more detailed set of parameters are necessary, including material, internal pressure, material type, machining, etc. The CostIQ Domain Authoring Tool imports new cases from SEER projects stored in the Enterprise Database by: 1. Using a local version of SEER software, reading the project from the SEER Enterprise Database. 2. Resaving the information in CostIQ-specific format back into the SEER Enterprise Database. A user of the Domain Authoring Tool is therefore required to have installed the SEER software for which domains have been created. As of January 2018, the following minimal compatible versions of SEER support CostIQ: SEER for Hardware: last released version (tested with version 7.3.35) SEER for IT: last released version (tested with version 2.3.9) SEER for Software: last released version (tested with version 8.2.38) SEER for Manufacturing: not yet released

Page 10: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 10

The DAT Interface

Cases are organized into domains; each domain represents a type of project (air to air missiles, robots, unmanned aerial vehicles, etc.); when you use the CostIQ Case-Based Reasoning Tool to create a project or obtain an estimate, you start by selecting a domain. The Domain Authoring Tool allows you to create new domains, to add cases to or remove them from existing domains, and to add new cases to or remove them from the case base itself. You can also edit overall data for a domain (such as its description, requirements, and its default method for generating parameter settings), as well as the requirements, picture files, and case name settings of individual cases. Cases can only be added while creating or editing a preexisting domain.

Create or Edit a Domain To use the DAT, you first create a new domain or select one that already exists. When you create a new domain, you select the SEER application with which it will work. The selections are Hardware (SEER-H), Software (SEER-SEM), Manufacturing (SEER-MFG), and Information Technology (SEER-IT). When you use the domain to create a work element structure (WBS structure) in the CostIQ CBR Tool, it will export the WBS structure to the SEER application which you assign to it at this stage. In the DAT, if you want to add cases to the domain by importing SEER projects or work elements, it will import them from that SEER application.

Page 11: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 11

Adding Requirements Since CostIQ is requirements-based, a domain consists not only of the cases which it contains, but also the requirements which apply to those cases. In effect, the requirements define each case in the domain. In the DAT, you must specify each requirement which will be included in the domain. To define a requirement, you give it a name, select the type (list, number, percentage, or qualifier), and specify the range of possible entries. Every case assigned to this domain must then be specified in terms of the requirements defined for the domain. As previously discussed, requirements are not SEER parameters nor do they play any direct role in setting SEER parameters.

Requirement Formats For number and percentage requirements, the user enters a number; you specify the lower and upper bounds of allowable entries. The default range for number requirements is unlimited (within the practical range for the number type itself); for percentage requirements, it is 0% to 100%. For list requirements, the range is actually a list of choices; you specify the choices on the list, and you determine whether each pair of choices is not related, overlapping, or identical. The default relationship between list items is "not related". Qualifier requirements are like list requirements, except that the list is preset: it consists of a qualitative scale from Vlo (very low) to Ehi (extra high). You can select the lower and upper bounds, but the names of settings and their relationships are pre-determined. The qualifier range default is Vlo to Ehi. While SEER tool parameters’ qualitative ratings are identically named, there is no relation between them and the rating scale used in CostIQ.

Requirement Relationships You can also set the relative importance of each requirement and indicate whether the values of any of the requirements will be derived. The CBR Tool calculates a derived requirement's initial value, which can be overridden, based on the values which the user enters for one or more of the other requirements. You can set the relative contribution of each requirement to the derived requirement. Derived requirements are intended as an aid when not enough is known about a new system. For both requirements and derived requirements, you can either set importance manually, or use the automatically calculated importance by means of the Use Auto Weights/Use Manual Weights button. Use Manual Weights reverts to the last manually-adjusted importance setting.

Adding Cases After you define the requirements, you can add cases. Each case is the equivalent of a SEER project or rollup; a case could represent an airplane, a wing, a computer program, a network server, or anything else which you would typically model at the project/rollup level in a SEER application. A domain should consist of cases of an at least broadly similar type or function, such as robots, surface-to-air missiles, local networks, data warehousing, wing structures, etc. You can add cases directly from the case base, and you can add new ones by importing SEER projects for use as cases. Each imported project will appear as a separate case in the case list, and will be added to the case base for later use.

Page 12: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 12

Entering Requirements Values For each case, you also enter requirement values. The CostIQ CBR Tool will compare the user's requirements entries for a new project against the values specified for each case, and rate the cases' relevance based on those comparisons. You can also add a picture to a case. For a hardware item, for example, it could be a photograph, an engineering drawing, or a schematic diagram. The image will be displayed in the Rate Relevance page of the CostIQ CBR Tool.

Parameter Defaults You can also set the default method that the CostIQ CBR Tool will use to generate parameter settings. Note that this is just the default; the user can change the parameter setting method when creating a project in the CBR Tool.

Tutorial: CBR Tool This tutorial is designed to step you through the process of creating a SEER estimate using the CBR Tool. It assumes that you are familiar with the basics of cost estimation, and that you have some familiarity with SEER estimating tools.

Background Your company is looking into the possibility of producing a long-range unmanned aerial vehicle (UAV), largely for civilian reconnaissance use. Among the options being considered is a high-altitude hovering vehicle with some stealth capabilities. At this point, the proposal consists largely of some basic engineering designs and a set of requirements. Your job is to turn these requirements into a cost estimate using the SEER family of estimating tools. Since you have a set of requirements on hand, you can simplify the process by starting with CostIQ.

1. Start the CBR Tool In the Windows Start menu, select SEER-CostIQ from the SEER submenu, then select the SEER-CostIQ icon. This will bring up the CostIQ Case Based Reasoning Tool (CBR Tool).

2. Select a Domain In the CBR Tool's Start tab, click on the Domain field to bring up the domain list; each domain consists of a set of related cases. Since you are estimating the cost of an unmanned aerial vehicle, select Unmanned Aerial Vehicles (UAVs). The Domain Details fields (Model, Author, and Description) display information about the domain. In this case, the description indicates that the domain which you selected is relevant to your project.

Page 13: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 13

Domain and Session Information

In the Session Info section, the Date field shows today's date. Enter the following text in the Notes field: Hovering long-range UAV proposal: initial estimate. Click on the Next button to go to the Specify Primary Requirements tab.

3. Specify Primary Requirements The Specify Primary Requirements tab will display the primary requirements fields for the Unmanned Aerial Vehicles (UAVs) domain.

Primary Requirements

Page 14: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 14

Enter or select the following requirements information for your project: Mission: Reconnaissance Echelon: Command/Strategic Duration (Hours): 12 (in the Likely column) Range (Miles): 700 (in the Likely column) Altitude (Feet): 25000 (in the Likely column) Stealth: Moderate Wing Type: Rotary Communications: Over the Horizon (such as UHF/Satellite) Structural Configuration: Fuselage with Vertical & Horizontal Stabilizers Propulsion Type: Jet Weight Empty: 300 (in the Least column) 1000 (Likely) 5000 (Most) Total Weight: 700 (Least) 1800 (Likely) 7000 (Most) Click on the Next button to go to the Specify Derived Requirements tab.

4. Specify Derived Requirements The Specify Derived Requirements tab displays requirements with initial values which are based on your primary requirements entries.

Derived Requirements

You can override these values if you need to. In this case, you will set the following value: Service: Civilian These two requirements should set to the following values by default: Launch Platform: Vertol Recovery Method: Vertol If they are set to other values, reset them as shown above. Click on the Next button to go to the Rate Relevance tab.

5. Rate the Relevance of Each Case CostIQ automatically calculates a relevance score for each case in the domain, based on your requirements entries. In the rate relevance tab, it lists the cases in order of their scores (shown in the Auto Score column). You can use the Your Relevance Rating column to override these scores.

Page 15: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 15

Rating Relevance

Click on the case labeled CL-327 Guardian (CL-227 Sentinel). You can see from the picture that it closely resembles the design of your proposed vehicle, so you reset its relevance rating to Quite Relevant. The same is true of the Dragonfly Canard-Rotor-Wing, Vigilante, RQ-8A - MQ08 Fire Scout, and QH-50 D Gyrodyne cases; set them all to Quite Relevant. Leave the other cases as-is. Click on the Next button to go to the Edit WBS tab.

6. Edit the Work Breakdown Structure The Edit WBS tab shows the Work Breakdown Structure which CostIQ generated for your project, based on your relevance selections; the percentage to the right of each item indicates how many contributing cases the particular WBS element is found in. Below the WBS structure window is a slider control which allows you to set the minimum level of relevance for the cases used in generating the WBS structure. For this example, you want the WBS structure to be based only on cases which you have rated as Quite Relevant or higher. Move the slider one notch to the right, so that the caption to the right of the slider now says "Quite Relevant." When you move the slider, the work elements shown in the WBS structure will change. Look at the WBS structure; you can click on the Open in larger window button to display the WBS structure in an expandable window. Each work element and rollup has a checkbox next to it; you can uncheck any items which you do not want to include in the project.

Page 16: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 16

Editing the Work Breakdown Structure

Scroll down to the bottom of the WBS structure and look at the rollup labeled Armament/Payload. The proposed vehicle is designed to use either off-the-shelf or customer-supplied surveillance systems, so they do not need to be included in the estimate. Click on the checkbox to the right of the OPTICAL/I.R. SYSTEMS work element so that it is not marked. Next, click on the checkbox to the right of the Radar Systems rollup; the rollup and all of the items subordinate to it should no longer be checked. Click on the Next button to go to the Parameter Settings tab.

7. Parameter Settings The Parameter Settings tab allows you to select the method that CostIQ will use when it calculates the initial parameter values for the project; you can change these values later, in the project that CostIQ creates in SEER.

Parameter Settings

Select Average; this means that the Least, Likely, and Most values for each parameter will be based on the average of the included cases. Click on the Next button to go to the Finish tab.

Page 17: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 17

8. Create a SEER Project

Estimating the Project in CostIQ When you reach the Finish tab, you're ready to create a SEER project. But first, you want to get a quick mini-estimate. To do this, click on Obtain estimate in CostIQ. An entry box labeled Production Quantity Year 1 will appear; the projected first-year production run is 10 vehicles, so enter that number in the box, and click on the Obtain Estimate button.

Estimating in CostIQ

CostIQ will ask you to enter a name for the project; Type in "Long-range Civilian UAV" and click on the Proceed button. SEER-H will run in the background (you'll see the splash screen), creating an estimate based on the WBS structure and your default parameter settings selection. Look at CostIQ's capsule estimate; it shows costs and labor hours for both development and production, along with the average per-unit cost. This gives you a chance to see whether the project's cost is within its projected budget range. The current project's mini-estimate looks OK.

Sending the Project to SEER Now it's time to create the actual SEER project. Click on Create SEER Project; the Production Quantity Per Year 1 input and the mini-estimate will disappear, and the button will now be labeled Create SEER Project.

Page 18: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 18

Creating a SEER Project

Click on the Create SEER Project button and enter the project name, just as you did for the mini-estimate, and click on Proceed. The SEER-H splash screen will appear, followed by the progress meter, then the main SEER-H window, with the project's WBS structure already laid out according to your specifications. You can now edit the project to match the specific details of your proposal; from this point on, you can treat it as a standard SEER-H project.

The SEER Project Work Breakdown Structure

Tutorial: DAT You probably won't use the DAT as frequently as you use the CBR Tool, and you may not use it at all. But if you need to create or edit a domain or a case, it is the tool that you will use. This tutorial steps you through setting up a simple domain with five requirements and three cases; a real-world domain, of course, will probably include more requirements and many more cases. This tutorial assumes that you are familiar with the basics of cost estimation, that you have some familiarity with SEER estimating tools, and that you are familiar with the CBR Tool, or at least its tutorial. If you are not familiar with the CBR Tool, please step through the CBR Tool tutorial before proceeding.

Background In this tutorial, your job is to create a domain and associate it with a collection of use cases for rotor-wing unmanned aerial vehicles (UAVs). The cases are already in the case base, so you only need to set

Page 19: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 19

up the domain, then add the cases to it. Importing cases into the case base from SEER involves an extra step, but otherwise the process is basically the same as that described here.

1. Start the DAT In the Windows Start menu, select SEER-CostIQ from the SEER submenu, then select the SEER CostIQ Domain Authoring Tool icon. This will bring up the CostIQ Domain Authoring Tool (DAT).

2. Create a Domain Select New Domain from the DAT's File menu. Enter the following domain name in the New Domain dialog box: Rotor-wing UAVs. Click on the OK button after you have entered it.

3. Edit the Domain In the DAT's Start tab, the Domain field should be grayed-out, and display the name that you entered. Select Hardware (SEER-H) as the SEER Model, if it is not already selected. Enter the following text in the Description field: "Sample domain -- rotor-wing unmanned aerial vehicles." In the field labeled Your Name, enter "DAT Tutorial".

Creating the Domain

Click on the Save Domain button. The DAT will tell you that the domain has been saved, then automatically proceed to the Edit Requirements tab.

Page 20: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 20

4. Add Requirements to the Domain In the Edit Requirements tab, you will specify requirements for the domain. When cases are added, each will need to be specified in terms of these requirements. The CostIQ CBR Tool will later match the user's specified requirements with appropriate cases based on the requirement values describing each. As discussed elsewhere, requirements in CostIQ are not related to SEER parameters. Click on the Add button; you will see a row of entry fields for the first requirement. Enter "Duration (Hours)" in the Name field. It is a best practice to specify the unit of measure in parenthesis. Click on the Type field and Select "NUMBER" from the list. The Range field should now say "From: Any to Any". Click on it to bring up the range entry dialog box; enter 2 in the From field and 24 in the To field, then click on the OK button. The checkbox in the Derived field should be unmarked; leave it as it is. The Duration requirement's settings should now look like this:

Entering a Requirement

Remember, at this stage you are only configuring the requirements list. Later on, each case added to the domain will need to have values specified for each requirement, given the way you’ve configured the requirements on this screen.

Adding More Requirements Click on the Add button again, and enter the following data for the following requirement: Name: Range (Miles) Type: Number Range: From 50 to 1000 Derived: Unchecked Name: Altitude (Feet) Type: Number Range: From 10 to 50,000 Derived: Unchecked Name: Empty Weight (Pounds) Type: Number Range: From 50 to 10000 Derived: Unchecked

More Requirements Options The last requirement is going to be a little different. Enter "Perimeter Surveillance" in the name field. Select "LIST" as the type; notice that the Range field now says "List". Click on the Derived box so that it is checked for "Perimeter Surveillance". Next, click on the Range field to bring up the List entry

Page 21: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 21

dialog box. It will have one blank list field. Enter "Near" in the field; the program will automatically display another blank list field. Now enter the following items, each in a new blank field: "Medium-range", "Wide-range", and "Multiple Location".

The Domain's Requirements

Setting Requirement Relationships Click on the Next button when you are done. You will see a dialog box with the list items displayed in boxes on either side of a slider labeled "Not Related". This is where you set the relationship between each pair of list choices: Not Related, Overlap, and Identical. The default is Not Related. In this case, all pairs of list items are Not related, except for Wide-range and Multiple Location, which can overlap. Click on Wide-range in the left-hand list and Multiple Location in the right hand list so that they are both selected. Move the slider to the middle, so that it is labeled Overlap. Click on the OK button to return to the main Edit Requirements tab.

Requirements Relationships

In the edit Requirements tab now, click on Next Step to bring up the Edit Cases (Projects) tab.

5. Add Cases to the Domain The Edit Cases (Projects) tab is where you will add cases (either preexisting ones from the case base or newly imported from SEER projects) to the domain. Click on the Add button to bring up the Add Case dialog box.

Add Case Dialog Box In the Add Case dialog box, scroll down the list until you find the section with items that have "Unmanned Aerial Vehicles (UAVs)" in the Currently assigned domain(s) column. (To make looking for

Page 22: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 22

these cases easier, click on the column to sort the list. Now click on and drag the lower right corner of the dialog so that it is expanded.) Find the item labels "UAV UAV CL-327 Guardian", and click on the checkbox to the left of the name so that it is marked. Do the same thing with "UAV Dragonfly Canard-Rotor-Wing" and "UAV QH-50D", so that all three items are marked with a check.

Adding Cases

Now click on the Close and Add button.

Update the Requirements The Edit Cases (Projects) tab should list the three cases that you chose. Notice that the field on the far right, Reqmts Status, says "Not Complete" in bold, black type for all three cases.

Requirements Status

Before you proceed, you need to fill in the requirements for all three items. The first requirement listed should be labeled "UAV UAV CL-327 Guardian". Next find the Requirements column and click on Click to update in the requirements field to bring up the Requirement Entry dialog box for the CL-327 Guardian.

Enter Requirements Values The Requirement Entry dialog box contains input fields for the requirements that you created. You are going to enter the actual specifications for the CL-327 Guardian in these fields; when a user enters project requirements in the CBR Tool, it will match them against what it finds here. In the Duration (Hours) field, 6.25; in the Range (Miles) field, enter 62; in the Altitude (Feet) field, enter 18,000, and in the Empty Weight (Pounds) field, enter 570. Now click on Value field for Perimeter Surveillance, and select "Medium-range" from the list. Click on Update and Proceed to Next when you are done.

Page 23: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 23

Enter Values for the Other Cases Now repeat this procedure for the Dragonfly and QQH-50D, using the following values: UAV Dragonfly Canard-Rotor-Wing Duration (Hours): 2 Range (Miles): 500 Altitude (Feet): 20000 Empty Weight (Pounds): 1314 Perimeter Surveillance: Wide-Range UAV QH-50D Duration (Hours): 6 Range (Miles): 350 Empty Weight (Pounds): 16000 Empty Weight (Pounds): 2175 Perimeter Surveillance: Wide-Range

Entering Requirements

After you have finished entering the data for the list item, click on the Update and Close button to return to the Edit Cases (Projects) tab. The Reqmts Status for each item should now say "Complete" in bold green letters. Click on the Next Step button to go to the Derived Requirements Importance tab.

6. Setting Derived Requirements Importance The values of derived requirements are determined bases on the values of other ("primary") requirements. In the Derived Requirements Importance tab, you set the relative importance of each primary requirement in determining the value of each derived requirement. In this example, there is only one derived requirement, Perimeter Surveillance, so you will set the strength of the other requirements in determining its value. The "Perimeter Surveillance" requirement rates the vehicle's overall value as an aerial surveillance device for patrolling regions based on geographic area. Duration (Hours) and Range (Miles) have a very strong effect on the Perimeter Surveillance value, so you should leave them both set to 10. Altitude (Feet) is much less important; move its slider all the way left to 0. Empty weight is somewhat more important; set it to 4. When you have finished, click on the Next Step button to go to the Requirements Importance tab.

Page 24: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 24

Derived Requirements

CostIQ automatically sets derived requirement weights, so override the settings on this tab only if you are sure you have a better sense of which primary requirements determine a derived requirement’s value. You can switch back and forth between the automatically calculated weights and your last set of manually entered weights by means of the Use Auto Weights/Use Manual Weights button.

7. Set the Relative Importance of Each Requirement In the Requirements Importance tab, you set the relative importance of each requirement in determining a best match to existing cases, based on the CBR Tool user's inputs. If a requirement is of low importance, CostIQ will give it less weight when it selects items from the case base. If a requirement is of high importance, CostIQ will give it much more weight when determining each case's relevance to the user's project. Set Duration (Hours) to 8, Range (Miles) to 10, Altitude (Feet) to 7, Empty Weight (Pounds) to 4, and Perimeter Surveillance to 7.

Requirements Importance

Note the Key Discriminator checkbox under Perimeter Surveillance. In this case, we want to leave it unchecked; if it were checked, the Perimeter Surveillance requirement would be decisive in determining which cases were selected; only cases specified with the same value would be judged relevant. When you have finished, click on the Next Step button to go to the General Parameter Handling tab. You can switch back and forth between the automatically calculated weights and your last set of manually entered weights by means of the Use Auto Weights/Use Manual Weights button.

Page 25: CostIQ User Guide - seerbygalorath.com · In CostIQ, a case represents a completed SEER project, along with high level requirements describing that project. Note that these requirements

CostIQ User's Guide

Page 25

8. Set the Parameter Handling Default In the Parameter Handling tab, you can set the default method which CostIQ will use in determining parameter settings when creating an estimate in SEER. Note that this is only the default setting; the CBR Tool user can override it.

Parameter Handling

In this case, we want it to be set to the first option, which is "A range from all retrieved cases".

9. Save the Domain When you have finished, click on the Save button. The Domain Authoring Tool will display a message saying that the domain has been saved. Now, if you open the CBR Tool, you will see the Rotor-wing UAVs domain listed along with the other domains; it will contain the cases and requirements which you gave it in this tutorial exercise.