Lead Architect Enterprise Information Architecture

Transcription

1 Lead Architect Enterprise Information Architecture Location: [Asia & Pacific] [Malaysia] Town/City: *Preferred locations: Kuala Lumpur, Malaysia; Chennai, India or the Middle East & Eastern European Region to be determined by home country of successful candidate where WVI is registered to operate. Category: Information Technology *Preferred locations: Kuala Lumpur, Malaysia; Chennai, India or the Middle East & Eastern European Region to be determined by home country of successful candidate where WVI is registered to operate. PURPOSE OF POSITION: Lead Architects facilitate the development of the right future-state architecture and ensures its effective adoption. They provide overall direction, guidance and definition of architecture programs which effectively support business strategies. Lead Architects advocate and support the enterprises IT strategies, identify and analyze enterprise business drivers, analyze the current IT environment to detect critical deficiencies, recommend solutions for improvement and develop strategies aligning IT to the business. They must have significant business knowledge and have one or more areas of technical expertise in which they concentrate. These technical areas may include network, security, applications and systems software, data and Internet. Individuals in this role lead, consult or oversee multiple architectural engagements. They work on highly complex projects that require in-depth knowledge within a domain: technical, solutions, business or information. They are viewed as an expert and provide knowledge / counsel to others. They also lead a domain specific architecture board. Individuals in the Architect job family interface across all business areas, acting as visionaries to proactively assist in defining the direction for future projects. They conceive strategies and solutions, build consensus, and sell/execute solutions. They are involved in all aspects of the project life cycle, from the initial kickoff through to requirements analysis, design and implementation. Additional responsibilities may include the establishment of the overall architectural viewpoints and the establishment and oversight of organization standards and policies. Architects identify major system interfaces, build e-business capabilities, and identify existing architecture weaknesses and opportunities for systems. Page 1/7

2 KEY RESPONSIBILITIES: Information Architecture: Sets information architecture standards and methodologies. Identifies the information which the enterprise produces and consumes. Ensures regulatory issues are considered surrounding information assets (such as consumer privacy laws, data retention policies, outsourced data and specific industry guidelines are adhered to). Creates the strategic requirements, principles, models and designs that strengthen the network effect of sharing such information across the enterprise. Establishes the rules for describing and completing a data valuation process for data objects. Implements a discipline and approach to managing information assets and converting the principles of the architecture into a technology solution. Leads the design of the information architecture, across multiple data types. Coordinates new development activities and ensures they are consistent and well integrated with the established enterprise information architecture. Architecture Strategy: Leads and coordinates the domain technical and business discussions relative to future architecture direction. Participates in enterprise strategy development, including environmental analysis, opportunity identification, value cases and business innovation portfolio development. Contributes to the IT strategy and ensures alignment with architectural strategy and business goals. Architecture Roadmap: Analyzes, designs, and develops a roadmap and implementation plan based upon a current vs. future state in a cohesive architecture viewpoint.

3 Defines principles that guide technology decisions and the relationship between enterprise business context (industry and market trends) and specified technology. Architecture Requirements: Reviews and/or analyzes and develops architectural requirements at domain level. Aligns architectural requirements with IT strategy. Assesses near-term needs to establish business priorities. Quality Assurance: Leads and analyzes information to evaluate the effectiveness of controls, determine the accuracy of reports, and monitor the efficiency and security of operations. Standards: Supports, develops, and communicates domain-wide policies, standards, guidelines and procedures. Designs standard software configurations. Promotes the EA process, outcomes and results. Governance: Participates in the EA Governance process. Leads and facilitates the domains architecture governance process based on EAs governance structure. Manages exceptions to architectural standards at a domain level. Reviews and approves recommendations to architectural standards at a domain level. Page 3/7

4 Reuse: Identifies opportunities for reuse. Supports the development of architectural models or views. Architecture Improvements: Analyzes the current architecture to identify weaknesses and develop opportunities for improvements. Identifies and when necessary, proposes variances to the architecture to accommodate project needs. Architecture Compatibilities: Ensures compatibility with existing solutions, infrastructure, services, and strategic requirements. Manages the design of enterprise-wide systems. Consulting: Provides strategic consultation to clients and IT teams. Participates in quality reviews and provides feedback. Advises on options, risks, costs versus benefits, system impacts, and technology priorities. Works with business leaders to understand business requirements and help them understand how technology tradeoffs influence strategy. Consults on application or infrastructure development projects to fit systems or infrastructure to the technical architecture, and identify when it is necessary to modify the technical/solution architecture to accommodate project needs. Consults on business-facing projects and maintains knowledge of their progress. Page 4/7

5 Communications: Keeps ITs technology and service managers aware of key customer issues, identifying and resolving potential problems and conflicts. Sells the architecture process, its outcome and ongoing results. Develops a communication plan for architecture at the domain level. Oversight: Coordinates architecture implementation and modification activities. Assists in post-implementation continuous-improvement efforts to enhance performance and provide increased functionality. Ensures the conceptual completeness of the technical solution. Works closely with project management to ensure alignment of plans with what is being delivered. Research: Leads the research and evaluation of emerging technology, industry and market trends to assist in project development and/or operational support activities. Considers potential application and impact to domains architecture. Provides recommendations based on business relevance, appropriate timing and deployment. Assists in project development and/or operational support activities. Tool Selection: Identifies the tools and components used within the domain based on the enterprise toolset and can define exceptions as warranted. Page 5/7

6 Finance: Recommends expenditures based on the size, scope, and cost of hardware and software components. Assists in developing business cases. Change Management: Recommends changes that impact strategic business direction. Supports change management initiatives. Project Status: Collaborates with project management on reporting project status, issues, risks and benefits. Meets with project leaders and IT Leaders to ensure progress towards architectural alignment with project goals and requirements. Technical Leadership: Develops, motivates, and directs staff to create a team environment. Provides leadership, technology guidance and mentors others throughout their domain. Recommends training programs targeting specific areas of improvement. KNOWLEDGE, SKILLS & ABILITIES: Bachelors degree in Computer Science, Information Systems, Computer Engineering, Systems Analysis or a related field. Typically have 15 or more years of experience in multiple IT areas of these at least more than 10 years of architecture

7 Powered by TCPDF ( experience mainly in enterprise information management and strategy. Willingness and ability to travel domestically and internationally, as necessary. Effective in written and verbal communication in English. Preferred: Strong leadership skills. Strong stakeholder management skills. Requires expert level knowledge and understanding of enterprise information architecture, strategy and implementation. Requires exposure to multiple, diverse technologies and processing environments specific to information management and related areas. Strong information strategy experience. Work Environment: The position requires ability and willingness to travel domestically and internationally up to 20% of the time. Page 7/7