| Line 436: | Line 436: | 
|  | |25 minutes, Bilingual |  | |25 minutes, Bilingual | 
|  | |- |  | |- | 
| − | |With increased reliance oncommercial cloud servicescomes increased fears ofrisking technical lock-in. This fear,however, can unjustly lead organisations to ?? theopportuntity gained fromplatforms services that offer alower operational burden,increase cost control, andshort lead times.???  | + | |As the GC becomes increasingly reliant on commercially provided services, the risk of lock-in | 
|  | + | weighs on the minds of departments. However, It is important to have a balanced | 
|  | + | perspective and properly weigh the risk of lock-in against the opportunities gained when | 
|  | + | using as-a-service models. <br> | 
|  | + | Information Technology has increasingly become commoditized. as-a-Service models and | 
|  | + | public cloud are at the forefront of this commoditization. Using these services to modernize | 
|  | + | application portfolios and at-risk technologies involves increasing reliance on private sector | 
|  | + | providers. This brings with it the fear of lock-in. Lock-in is not unique to cloud, for years the | 
|  | + | GC has been managing the exit strategy from a variety of technologies such as mainframe, | 
|  | + | data centres, operating systems, databases, and Enterprise Resource Planning systems to | 
|  | + | name a few. As this guide will show, the decision to commit to a technology and when to exit | 
|  | + | cannot be driven by fear and risk alone, but must be weighed against the opportunity gained.  | 
|  | + | TBS guidance can be found here: https://wiki.gccollab.ca/images/5/52/02_-_Lockin_EN.pdf | 
|  | + |   | 
|  | |} |  | |} | 
|  | <br> |  | <br> |