Annually, Paradigm’s internal IT develops its IT Strategic Plan to align the projects execution to the company’s goals. This is a key input to our Annual Operating Plan from a financial perspective. Enterprise Architecture has helped us tremendously to identify the gaps in our existing systems and business process. This information is being used to guide our Application Development and Systems design and implementation. In particular, by mapping our goals, objectives, business processes, systems, information management, network implementation (to name a few) to Zachman Framework, we are able to clearly recognize the gaps to our existing technology and architecture landscape.

As a result, Paradigm was able to build up a guiding principle to our system implementation. As an example, four major direct outputs from our EA exercise are the following:

• Master Data Management
• Security Services, Corporate Services and System Services
• Workflow Management
• Information Management (Warehouse and Business Intelligence)

Currently, all Active Projects are adapting to these guiding principles and framework as applicable. We are harnessing direct benefits from this approach:

• Standard design patterns to support scalable and robust systems’ needs
• Shorter turn-around-time for application design phase
• Providing solutions directly aligned to the company’s visions with positive direct impact to Strategic and Operational Plan
• Narrowing identified gaps from business process, systems and architecture perspective
• Provided communication tool to business and executives

Every organization has the obligation to know and understand how they spend their money on IT and what risks they run. Nowadays this is called IT Governance. IT Governance has many definitions, but at the least all agree that it is about making sure to do the right “things” (both projects as well as life cycle management on infrastructure and application systems), doing it efficient and against an acceptable level of risk. So far so good.

IT Architecture should make sure that the above themes can be supported in such a way that on business, application and infrastructure level the right decisions are taken. And this is where IT Architecture, in particular in larger organizations, often has let us down. IT Architecture is a means to an end, not a purpose in itself. The semi-devaluation of the term “Architect” in the IT world over the last couple of years does not help either. It is time that we get the real IT Architect back in our organization.

This presentation is to explore where and how the link between IT Architecture and properly implemented IT Governance processes need to be established and strengthened.

In today's world of constant change, creating architecture and growing it as per the business need has been the most challenging for the CIOs.Globalization, Mergers and acquisitions, security, technology rate of change, obsolescence, refresh cycles, emergence of standards, compliances and regulations - All are contributing to the complexity of enterprise architecture. Is there a way out of it? Should the CIOs and CTOs have to live with the complexity? This presentation is aimed at discussing and elaborating on these challenges and sharing strategies adopted by some organizations.

The information age is producing humungous amount of data that requires a paradigm shift in thinking about how to store and process this data. Traditional architectures fade into cost overruns, scalability and ROI issues. Distributed computing is the answer. In traditional High performance settings, one often assumes a "well-behaved" system: no faults or failures, minimal security requirements, consistency of state among application components, availability of global information and simple resource sharing policies. While those assumptions are arguably valid in tightly coupled systems, they break down as systems become more distributed.

This presentation will talk about the Cloud computing in Yahoo with emphasis on Hadoop Grid. The Grid Computing group at Yahoo! Bangalore focuses on Grid frameworks that scale to thousands of machines and handle peta-bytes of data. The group is especially involved in the development of the Open Source Hadoop platform and its deployment within Yahoo!

Anyone who has ever flown on a commercial airliner has experienced a Major Incident Handling plan. From the steward and stewardess droning on about seat belts and oxygen masks, to the pilots in the cockpit reviewing checklist after checklist, to the little cards in the seatbacks ahead of you detailing exit locations and water landing procedures all of these are examples of Major Incident planning in support of the airline’s Risk Management goals and objectives. Plans such as these not only make good sense but are critical requirements driven by fiduciary responsibility, moral obligation, and legislative and safety mandates.

That said, many corporations continue to do business today with no Major Incident Handling plan as part of their overall Risk Management strategy. Worse yet, when it comes to addressing that gap, far too many choose to remain in denial leaving Major Incident planning for the proverbial, “…next fiscal year.”

This does not need to happen. All that is required is some forethought and a common sense approach to planning and documentation. The goal of this presentation is to clearly demonstrate why a Major Incident Handling plan is a core business requirement in today’s world, provide you some tools that you can use as a starting point for creating your own Major Incident plan, and to show you how relatively simple actions like creating flowcharts, procedures and call lists can bring big returns to the organization’s overall risk posture, allowing it to increase its risk appetite and create opportunities for a more a dynamic, agile and competitive business strategy.

Omkar has a career span of over 11 years. He has rich experience in Industrial Automation and Automotive Electronics domains. At KPIT Cummins Infosystems Ltd, he is a key member of CREST (Center for Research in Engineering Sciences and Technology).

Omkar is spearheading AUTOSAR Application migration initiative as a part of Automotive CREST activities. He is also a key driving force behind Automotive Infotainment and Graphics initiatives running within CREST.

Omkar is a practicing architect with the main focus on Product Line Architecture and Model Based Development. He has pioneered OOAD and UML based system design both for desktop application as well as embedded systems. He has conducted number of training programs and workshop within KPIT and for customers in the areas of OOAD, UML, and design patterns, especially as applicable to embedded systems.

Omkar has Bachelors Degree in Mechanical Engineering from University of Pune.

This presentation will explore in some detail the nature and structure of machine-readable semantic metadata that is now coming on line in standards for the manufacturing and financial services industries and is being increasingly used by ERP vendors, opening up possibilities for a new generation of tools that make integration analysts substantially more productive and accurate.  It elaborates on the basic concepts covered by the keynote address on the same topic. 

Subjects include:
• The coming use of semantic metadata in the ISO 20022 financial services standard
• Semantic metadata and the Semantic Web
• Semantic metadata and the UN/CEFACT Core Components standard
• Semantic metadata and XBRL

In view of large number of e-governance applications developed across the country, there is an increasing need to support the flow of information and to improve the coherence of Information Systems maintained by individual ministries and departments. This would facilitate Government systems to communicate and inter operate with other systems, both within the Government and external to it, efficiently and effectively and thus present a unified face of e-Governance in the country.

Federated enterprise architecture framework is perceived as a foundation for decision and integrated Services delivery through a unified gateway by de-linking tightly coupled legacy applications and data.

Some of the specific objectives aimed at:

• Data from various applications distributed logically, as well as physically across the Federated Government need to be seamlessly integrated by following open standards for data interchange / exchange and archival.
• Extraction of data from horizontally and vertically integrated databases through hierarchical levels of Data Abstraction Layers
  
• Building the intelligence to cater to complex queries of data extraction, calculations, trend analysis, inference building etc.
  Building and maintaining repository of common data elements, e-forms, templates, re-usable software solution components, common taxonomy, ontology etc. for meeting requirements of data exchange, data interchange and archival etc.

The presentation outlines the approach of FEA for E-Governance applications.