This document discusses the technology challenges of Aadhaar, India's unique identification system. It notes that Aadhaar handles large volumes of data like 10 fingers per person which is 6 petabytes of data for 1.2 billion people. It also must process 4 million enrollments per day while de-duplicating records. Aadhaar aims for fast response times of 2-3 seconds while comparing 1 billion records for each enrollment against the whole database. The document advocates for automating IT management using tools that can autoscale infrastructure, plan for growth, support error remediation, and orchestrate data and workflows across distributed datacenters to monitor end-to-end transactions. This would help Aadhaar better
34. Automated Management of IT to Support Aadhaar Provides platform for effective business planning and operations Common and consistent way for sharing information across IT functions SERVICE REQUEST MANAGEMENT DATA MANAGEMENT INCIDENT MANAGEMENT SERVICE LEVEL MANAGEMENT CAPACITY MANAGEMENT EVENT AND IMPACT MANAGEMENT CONTROLS AND COMPLIANCE BSM RELEASE MANAGEMENT ASSET MANAGEMENT CLOUD LIFECYCLE MANAGEMENT CONFIGURATION AUTOMATION Simplifies, standardizes and automates IT processes with OoB workflows Enabling IT to Scale better and consistently meet expectations ENTERPRISE SCHEDULING CHANGE MANAGEMENT PERFORMANCE & AVAILABILITY MANAGEMENT
35. Automate: Autoscale based on capacity trends during enrollment or authentication Planning: Plan future growth and define supply and demand strategies Support: Aadhaarenrollment errors deduction and remediation Design: Continuous auto discovery of infra and association to Aadhaar applications Orchestrate data and workflow across Aadhaar DCs BMC Simplifies and Automates IT management Monitor: Ensure end-to-end transactions across enrollments, auth, fraud detection and other Aadhaar apps
Editor's Notes
Slide objective: Show that BSM solves these challenges by simplifying, standardizing, automating, and integrating IT processes and functions using a common data model with a shared definition of services, assets and IT configurations…Key Points:-- Just as ERP provided a platform for effective business planning and operations, BSM provides a platform for effective IT planning and operations-- BSM offers a common and consistent way for information to be shared across IT functions and departments-- BSM also simplifies, standardizes, and automates IT processes through out-of-the-box best practice templates and integrated workflow-- BMC learned from early ERP implementations, and built a platform that avoids the traditional challenges of ERP adoptionSample presentation:Just as ERP provided a platform for effect to business planning and operations, BSM provides a platform for effective IT planning and operations. The notion of a platform provides two fundamental benefits. First, the platform provides a consistent way of sharing information. Just as businesses needed to standardize around terms such as "customer", IT organizations need to standardize around consistent terms, such as "services", "resources", and so on. A platform approach also standardizes the communications and workflow between functions through APIs and a shared data model. With a platform-based approach, the output of one function becomes the input to another (for example, the output of request management is an input to change management). Second, this platform provides the ability to quickly adopt best practices and automate workflow. Historically, IT organizations have worked in silos, which is great for building and maintaining areas of functional expertise, but inefficient when multiple IT departments are required to work together. By delivering out-of-the-box best practice templates for IT processes and automating many mundane, repetitive, and error prone tasks, IT organizations can focus time and effort on better meeting business expecations and requirements.In making this analogy to ERP, it's important to note that BMC has learned from the 20 years of ERP implementations have happened globally. Two key ways in which BSM has differentiated itself from traditional ERP. First, implementation does not have to be an "all or none" issue. We strongly believe in a stepwise implementation path, where return on investment can be demonstrated at each step along the way. Second, the architecture for BSM is not a single-monolithic architecture. Rather, it combines key attributes of composite applications, such as rapid implementation, ability to work standalone, and rapid integration with other components (e.g. SOA-based APIs and federation vs. centralization of your most critical IT information.)
