[MUSIC] In this lecture, we will learn how to create a model of a project and save it as a scenario file using the project team builder scenario builder. The scenario builder creates and saves project data as a scenario file. It is also used to edit the content of an existing scenario file. This file can then be loaded into the PTB simulator to create project plans and to analyze the schedule, cost, benefit, and risks of such plans. It is also possible to simulate the execution, monitoring, and control of such project plans. The project model can be created from scratch or based on an important Microsoft Project file or based on an existing scenario file. To use the Scenario Builder, go to sandbox model website. Go to Run It and select PTB Scenario Builder. Click on it, and then, click on PTB Scenario Builder again. The software will be loaded, and you'll be prompted for username and a password. Click OK. The Scenario Builder main screen has three parts in it. On the left hand side, you'll see the Scenario Tree with all the different object in the scenario. In the right hand side, the upper part is the Network of the chose precedence relations among the different tasks. And the lower right hand side shows information about the object you are currently in. We will start with a new scenario. We'll click on Scenario1, which is the default, and we'll change the name into newscenario. Once we do it, we can add objects, and we click on the new scenario on the left hand side, and now we can add two types of objects. We can add the project and we can add the resource type. Let's add a project and we'll call it project 1. Next, we can see it under the new scenario. Let's add a resource type, call it engineers. Now we can see it under this scenario. For each object, we can see the information of the object by clicking on it. For example, if click on Engineers we can see all the information for the resource Engineer. Later on, we will update all the information for all the objects. But for now, we want to add three tasks to the project. We will add the first task after pointing at project one, and we'll call it task one. Then we add task 2, And task 3. Next, we want to make task 1 and task 2 predecessors of of task 3. Let's click on task 3. And select task1 as a predecessor, moving it to the right, and then we do it for task2. Now we can refresh the network and see it in the upper right part of the screen. Click on Refresh Network, and we can see that task one and task two are predecessors of task three. If we will try to save the project, going to File and Save, we will get in the lower part an error message. Can't save incomplete scenario, please add at least one mode. Correct the issue or save temporary scenario instead. A temporary scenario is an incomplete scenario. What we'll do now, we'll add at least one mode to each task. So we'll go to task1, point at it, click on it, and add a mode. Let's call it mode1a. We'll add another mode, we'll call it mode1b. We do the same for task2 and 3. And if we try to save the model now, We'll be prompted with a save option. We will save it on the desktop, we'll call it a new scenario, and we'll save it. Now, we can add detailed information for the scenario in each of the objects. For example, if we go to new scenario, we can put in the target cost, say $1,000. We can describe this scenario, a new scenario for training. And we can add different functions to the scenario. For example, we can enable the history mechanism, which will allow the user to go back in time to see his past decisions, or even to load past points in time and to re-run the simulator. You can see that we can allow to split tasks, to assign or release resources. We can limit the number of resources if we want. We can use the System Engineering, or the quality requirements. And we can allow saving of simulations during our trials. What we do next is to look at the project and now we want to put in the initial cash, which is $2,000. The target finish time, which is ten periods, and the bonus and penalty for early finish, late finish. Let's make them both 50. Again, we want to use the system engineering feature which is managing the requirements. Next, we go to the tasks. And task1 is the first one. It has no income associated with it. And the splitting of the task cost 10. This task has no predecessors, as we saw earlier. However, if you go down the screen, you see that there are no resources yet. So what we want to do is we want to add mode with resources. Click on mode 1. And here you see the resource engineers. In mode 1, we need one engineer. If you go to mode 2, we'll change it to two engineers. Therefore, in mode 1, the tasks take longer. The optimistic duration is 5, the most likely is 6, and the pessimistic duration is 8. However, in the second mode, it takes shorter, so the optimistic duration is 2, the most likely is 3, and the pessimistic is 4. We can also change the fixed cost of each mode, say, 40. And the first mode is 20. What we want to do next is to update the task2 and 3, if we like. But what I want to add now is a quality requirement. Therefore, we'll click on the project icon, project one, and we add a quality requirements. Suppose we want to add reliability as a quality requirement. Now reliability is defined, and we need to decide which of the tasks impact reliability. Suppose the task1 impact reliability, so we add a quality perimeter, reliability of task1 And once we define it, we can go to this parameter and define the notation for it, which will be rt1. We can put in a description for this requirement, at this time, I want to add a requirement to task2. We put equality requirements which is reliability, Of task2. And again, we click on the object, and we can change the notation to rt2. Now we can enter formula for reliability. If we click on reliability, we will see that there is a space to define formula here. Let's look at the available parameters. We have two parameters that we already defined, rt1 and rt2. Let's make reliability of the project a function of rt1 and rt2 so that it is rt1 plus two times rt2. So, let's put rt1, And next, + 2*, rt2. Recheck if the formula is correct, and there is no viable alternative input at line 0:-1. So what's the problem? We made a mistake here with the parenthesis we have to change it and now it should be correct. Success without having a value of 1 is 3. Okay, now we can save this scenario. And we'll keep it under the desktop with the same name. So I'll go to the desktop, And keep it under the same name. In order to test the scenario, we can open the PTB simulator and upload the scenario. We'll open it from the desktop. And now the scenario is opened, and we can look at the default plan. The Gantt chart, for example, will show us the schedule for this project. We can see that task two and task three are still having only one mode with a duration of one, and of course, we can update the duration of these tasks. This is the basics of the project simulator Scenario Builder, and of course, you can change anything by going back to the scenario, and modifying any of the objects. What we'll do now, we will upload the scenario from the desktop. Open Scenario, the current file will disappear, and we will just go to new scenario on the desktop, and the scenario is now uploaded. We can edit it, change it in any way you like. And, of course, modify and save it. You can find much more information in the video tutorial and in the Help of the Scenario Builder. Creating a project model with the Scenario Builder is straightforward. The challenging part is gathering the information about the project to create an accurate project model. Try it yourself. Create a scenario file and load it into the project in Builder Simulator to simulate managing the project you created. [MUSIC]
