Your diagnosis, your design and your first ninety days, assembled from the modules you have completed. Software defines the service, AI runs it, and human beings are why customers choose yours.
0of 12 sections
Import a module export to fill the model.
Saved locally· never leaves this machine
Worked exampleA complete Operating Model for Northwind Managed Services, a fictional UK managed service provider, assembled from all six modules. Every number below is computed by the kit from the data in those modules, and every one of them reconciles, so check them. The assumptions they rest on: 21 working days a month, so the 3,666 contacts that arrive are 174.6 a day and 175 a day are closed, which is the stability Little's Law asks for; a desk open ten hours a weekday, with elapsed time on the calendar clock, nights and weekends included, and lead times in working days, so 2.4 working days of lead time is about 81 hours on the clock; a desk of eight people at 140 productive hours each, which is 67,200 minutes of capacity a month against the 58,255 minutes of handling in the demand table, and that ratio is the 86.7 per cent utilisation; and £16 fully loaded per contact, which is where the £288,000 comes from. The journey in module ii, four sensors in iv and four functions in v are tied to module i's lines. The ranked list prices the moves it shows from them: the journey, the dashboard still to become a sensor, and the first place AI lands. Nothing here is saved to your machine.
Two different saves.Download a copy gives you a data file to reopen, move between machines or share. Save as PDF gives you the finished document for a board. When you print, switch off headers and footers in the print dialog, or your browser stamps a URL and a timestamp on every page.