Now we will add a new resource to represent the video server at the exchange. Its capacity will be limited by memory and throughput and can be defined for now in terms of Mbit/s. Later we will look at an alternative model where it can be measured indirectly in concurrent video streams.
Save the model as WiMAX-DSL36
Toolbar 
- Click the
button on the toolbar and then click again within the view to create a new resource. Name it Video server.
-
Set the inputs Capacity = 256.0, Capacity Unit = Mbit/s and Physical Lifetime = 5 (icon menu/Capacity and Lifetime).
-
Set the input Capital Cost = 50,000.0 and add a formula for
Maintenance Cost
as Capital * 0.05 (icon menu/Costs).
-
Create a requirement for this new resource from the Video service, being sure to set the basis of the link to Busy Hour Traffic (rather than the default of Connections).
Save and run the model and all of its scenarios
- Draw the following charts and make sure that you are happy with the results:
-
Service Demand – Busy Hour Traffic
-
Resource Capacities, Capital Expenditure and Operating Costs.
- Why is the capex double in 2012?
Tip: draw Resource Installed and Incremental Units for the new Video server resource.
Things that you should have seen and understood
New resource, new requirement, incremental demand, replacement
Requirement, Basis