Prior TSS/AIM2’s automation of Cloud intake, all requests for new cloud resources in Azure required a significant amount of manual effort in order to determine the department needs and requirements in order to build the required cloud infrastructure solution. The TSS AIM2 team was tasked with creating a custom cloud intake application that would emphasize a flexible intake design in order support the many different types of requests we have today in TSS, but also what we may have “tomorrow-unknown”. The focus cannot be for just Azure, but rather the many other cloud providers. i.e. (Azure, AWS, Google).
The Cloud Intake application will be used by all county employees to request services across the many different cloud providers. The application makes use of a predefined set of user templates, which helps guide the user during their request submission. The building of templates is a dynamic process that allows for an easily managed plug-play development environment. This design approach reduces I.T costs when changes or additions are needed to the any application object. There are no code changes required since all the building block objects are available and fully leverageable. The object-oriented design approach carries over to all application data objects, security permissions, expressions and resource types.
In addition, the applications flexibility allows for other SCC teams to quickly build a new intake request process since the application design is not limited to just cloud resources and providers. A key staple of the applications flexibility is the ability to quickly build a new intake request form or template and define a process flow. The needed workflow to support a new intake request is easily configurable and the application ensures automated notification to all interested parties as the request progresses through its lifecycle. Agile-Scrum methodology is being used to develop the Cloud Intake app in the Azure Cloud using .NET framework with SQL Server DB. Currently, the team is working on refining the user interface and conducting UAT to ensure the tool meets our customer’s expectations. Planned go-live – October 2019.