advertisement

IE 1107 Paiva Joe SOA Implementation

60 %
40 %
advertisement
Information about IE 1107 Paiva Joe SOA Implementation
Entertainment

Published on February 12, 2008

Author: Valeria

Source: authorstream.com

advertisement

A Warriors Guide to Business Architecture:  A Warriors Guide to Business Architecture This Presentation is NOT endorsed or supported by any Government organization. The views, ideas and concepts are solely and exclusively those of the presenter and do NOT represent any official or unofficial policy. Saving Money and Supporting the Warfighter Purpose of Brief:  Purpose of Brief To provide an update about Army efforts to develop and use enterprise architectures and service oriented architectures (SOA). This presentation is Unclassified and will focus on the “Business” side of the Army. DoD and Army Governance Structure:  Enterprise Information Environment Mission Area (EIEMA) DoD Lead: DoD CIO/ASD(NII) | Army Lead: CIO/G-6 Governance Business Mission Area (BMA) DoD Lead: USD(C) | Army Lead: USA Acquisition Owner: USD(AT&L) | Army Lead: ASA(ALT) Financial Management Owner: USD(C) | Army Lead: ASA(FM&C) Human Resource Management Owner: USD(P&R) | Army Lead: ASA(MR&A) Logistics Owner: USD(L&MR) | Army Lead: ASA(ALT) Installations & Environment Owner: USD(AT&L) | Army Lead: ASA(I&E) Civil Works Army Owner: ASA(CW) Governance Warfighting Mission Area (WMA) DoD Lead: CJCS | Army Lead: G-3/5/7 Battlespace Awareness Owner: V. Dir Intel, J-2, JS | Army Lead: G-2 Battlespace Communications Owner: V. Dir. C4, J-6, JS | Army Lead: G-6 Focused Logistics Owner: V. Dir. Log., J-4, JS | Army Lead: G-4 Protection Owner: Dep. Dir FP, J-4, JS | Army Lead: G-8 Force Application Owner: Dep. Dir JWCS, JS | Army Lead: G-8 Information Assurance Domain Owner: Director, Information Assurance | Army Lead: CIO/G-6 Communications Owner: D, Wireless | Army Lead: CIO/G-6 Computing Infrastructure Owner: D, Architecture & Interoperability | Army Lead: CIO/G-6 Core Enterprise Services Owner: D, Information Management | Army Lead: CIO/G-6 Governance National Intelligence Mission Area DoD Lead: USD(I) | Army Lead: G-2 Governance In Work In Work Governance National Intelligence Technical Infrastructure Mission Area (NITMA) Owner: ICSIS | Army Lead: In Work Draft Army Alignment with GIG ES Governance 4 Mission Areas: - 15 Domains - 9 Domain Owners DoD and Army Governance Structure Purpose of Army BEA Effort:  Purpose of Army BEA Effort Ensure the Army “To-Be” Business Enterprise fully supports a Modular, Expeditionary Army Joint Interoperability Decrease the In-Theater Sustainment Footprint Make Army Sustainment More Cost-Effective Ensure Required Army Programs meet IOC Goals Compliance Defense Authorization & Appropriation Acts Clinger-Cohen Act and other Congressional Guidance USD(AT&L), USD(C) and other DoD Requirements Executive Orders and other (i.e. OMB) guidance BEA & EIE MUST Align to WMA :  BEA & EIE MUST Align to WMA WMA requirements must be fed into the mission area architectures for the BMA and EIE MA to ensure business systems are fully aligned to the operational needs of the Army. Procurement Disposition Garrison Storage & Transportation Depot Maintenance Human Resources Design & Development Planning, Budgeting IT Infrastructure Legal Field Maintenance Operational Usage Strategic Storage & Transportation WMA Training Medical Services Oriented Implementation EA is NOT “A CIO Thing”:  EA is NOT “A CIO Thing” It’s About Better Business Process Management, NOT Computer Systems! Roles of CIO:  Roles of CIO Technical Strategy Support/Assistance Honest Broker/ Facilitator Integrator/Librarian DoD and Army Governance Structure:  Enterprise Information Environment Mission Area (EIEMA) DoD Lead: DoD CIO/ASD(NII) | Army Lead: CIO/G-6 Governance Business Mission Area (BMA) DoD Lead: USD(C) | Army Lead: USA Acquisition Owner: USD(AT&L) | Army Lead: ASA(ALT) Financial Management Owner: USD(C) | Army Lead: ASA(FM&C) Human Resource Management Owner: USD(P&R) | Army Lead: ASA(MR&A) Logistics Owner: USD(L&MR) | Army Lead: ASA(ALT) Installations & Environment Owner: USD(AT&L) | Army Lead: ASA(I&E) Civil Works Army Owner: ASA(CW) Governance Warfighting Mission Area (WMA) DoD Lead: CJCS | Army Lead: G-3/5/7 Battlespace Awareness Owner: V. Dir Intel, J-2, JS | Army Lead: G-2 Battlespace Communications Owner: V. Dir. C4, J-6, JS | Army Lead: G-6 Focused Logistics Owner: V. Dir. Log., J-4, JS | Army Lead: G-4 Protection Owner: Dep. Dir FP, J-4, JS | Army Lead: G-8 Force Application Owner: Dep. Dir JWCS, JS | Army Lead: G-8 Information Assurance Domain Owner: Director, Information Assurance | Army Lead: CIO/G-6 Communications Owner: D, Wireless | Army Lead: CIO/G-6 Computing Infrastructure Owner: D, Architecture & Interoperability | Army Lead: CIO/G-6 Core Enterprise Services Owner: D, Information Management | Army Lead: CIO/G-6 Governance National Intelligence Mission Area DoD Lead: USD(I) | Army Lead: G-2 Governance In Work In Work Governance National Intelligence Technical Infrastructure Mission Area (NITMA) Owner: ICSIS | Army Lead: In Work Draft Army Alignment with GIG ES Governance 4 Mission Areas: - 15 Domains - 9 Domain Owners DoD and Army Governance Structure Domain Leader Activities:  Domain Leader Activities Iterative Feedback Notional Domain Organization:  Notional Domain Organization Federated Architecture Approach:  Federated Architecture Approach Army EA Joint Federated Architecture Joint BEA DoD LOG Joint LOG Navy LOG Army LOG AF LOG Army BEA Army WF Army EIE Army Intel OSD LOG GCSS-A PLM+ LMP LDSS The Army is too big to manage as a single monolithic entity; A federated architecture breaks the elephant into interoperable, bite-size segments. Army FM Army I&E Army HR Army CE Navy EA AF EA EA Must Impact Development:  EA Must Impact Development Analyze & Integrate Domain Architectures Cross Domain Integration Optimization Analyses Bandwidth Reduction Opportunities Footprint Reduction Opportunities Assess Information Assurance Vulnerabilities Develop Technical Strategies & Provide Technical Guidance Interoperability Reduced Footprint COTS Utilization/Optimization Help Domains Develop Architectures Develop & Provide Common Templates Standardize Processes Develop & Teach EA Courses PMs Develop & Field Systems CIO EA Team Roles EA Is An Iterative Process:  EA Is An Iterative Process Recognize Constraints; Change & Improve Continuously. Hybrid Service Oriented Architecture :  Hybrid Service Oriented Architecture Hybrid Model Enterprise Services provide Interoperability for Common Requirements System-System Interfaces used where required/more effective Enterprise Services Core (CES) Business (BES) Intra-Domain Service Bus or Integration Broker System-System Interfaces Three Types of Processes:  Different Types of Processes Need to be Handled Differently: Transactional Processes – Not good SOA Candidates Verification Processes – Good SOA Candidates Management Processes – Good SOA Candidates Three Types of Processes Concept taken from Corning, Inc. Slide16:  Only Share Some Services Not all processes should be “shared” Some processes are different/unique for a reason 10 roofers are sometimes less efficient than 5 on a small roof 50M Gallons of soda is no cheaper per gallon than 25M (but costs more to store and handle) Concept taken from Corning, Inc. Army/DOD Hybrid Architecture:  Army/DOD Hybrid Architecture GIG-ES USAF-ES Individual Programs and Proponents HR Web- Sphere CW TBD ACQ TBD I&E TBD LOG Net- Weaver FM TBD Domain Integration Brokers/ESBs ARMY LandWarNet Core Enterprise Services (CES) Enterprise Services Core (CES) Business (BES) Current Implementation Concept:  Current Implementation Concept GIG-ES USAF-ES Individual Programs and Proponents HR Web- Sphere CW TBD ACQ TBD I&E TBD LOG Net- Weaver FM TBD Domain Integration Brokers/ESBs ARMY LandWarNet Core Enterprise Services (CES) Vendor Neutral Services; Published, Discoverable and Re-usable. Sample Implementations:  Sample Implementations LandWarNet - ES DOD GIG-ES Federated ESB/SOI Enterprise Service Bus Services Oriented Implementation NMCI - ES EA Template Details:  EA Template Details Common Templates Are Critical:  Common Templates Are Critical Common Templates Systems Inventory:  Systems Inventory Enterprise Level Domain-Capability Matrix :  Enterprise Level Domain-Capability Matrix Domain Level Program-Capability Matrix :  Domain Level Program-Capability Matrix The Army Domain Level SV-5 acts to specifically assign Domain Level ROCs to one or more Programs within the domain. This Matrix specifically enables the tying of MDEP funding lines (occurring at the program level) back to ROCs from The Army Plan (TAP Codes). Domain Level System-Capability Matrix:  Domain Level System-Capability Matrix System Service Exchange Matrix:  System Service Exchange Matrix Identifies the operational processes being enabled by information systems providing specific services. Enables managing systems development to better support continuously improving (i.e. changing) operational business processes. It also supports Information Assurance and Standards development efforts. Communications Matrix:  Communications Matrix Enterprise Service – Info Assurance Matrix:  Enterprise Service – Info Assurance Matrix Uses existing standards and tools for data element IA Criticality Assessment, and provides an easy way to assess the level of IA effort each system within the Domain will need. Services Standards Profile:  Services Standards Profile Back Up Slides:  Back Up Slides Challenges:  Challenges Data, Data and Data Security, Security and Security Vertically Integrated Tool Sets Governance – Mindset Change Portfolio Management Details:  Portfolio Management Details DOD BEA Certification Process:  DOD BEA Certification Process CIO/G6 Certifies Domain Leader Submits Army Validation Architecture Precedes Portfolio Reviews:  Architecture Precedes Portfolio Reviews Domain Architectures are tools used for many things, including Portfolio Management Army Portfolio Management process requires Domains to have validated Domain architectures completed before performing portfolio reviews Domain Leaders Complete Domain Architectures G6 Federates Mission Area Architectures Domains Conduct Portfolio Reviews Army Programs Prepare PfM Packages Move Forward Architecture Validation Portfolio Management What Is Enterprise Architecture ?:  What Is Enterprise Architecture ? A Tool for Managing Business Processes & Assets The Value of Architecture (1 of 2):  The Value of Architecture (1 of 2) Deliver More Effective Systems In Less Time with Less Money Architectures provide a tool to better manage and document requirements. Better requirement definition leads to fewer program cost and schedule overruns. Eliminate “Stove-Pipes” Architectures help identify functional gaps and overlaps Ensure Information Infrastructure Planning Meets Operational Needs Architectures provide a means to forward plan & program bandwidth The Value of Architecture (2 of 2):  The Value of Architecture (2 of 2) Enable Interoperability Between Force Sustainment and Projection Systems Architectures provide common frameworks for technology development, thereby ensuring alignment of technology strategies Make the Army More Adaptable Architectures allow Business Process Management to drive technology (and not technology to drive processes) Enhance Army Joint Warfighting Capabilities Architectures provide common frameworks for the development of solutions which cross services and agencies (e.g. Medical, Logistics, Joint Fires, etc.) Notional CIO Team Organization:  Notional CIO Team Organization Core Enterprise Services (CES):  Core Enterprise Services (CES) Application Sharing Web Conference People Discovery Text Messaging Whiteboard Workspaces Content Delivery Content Discovery Content Store Identity and Metadata Management Enterprise Services Support Infrastructure ESB/Integration Layer Parts:  ESB/Integration Layer Parts Vendor Products BEA – WebLogic IBM – WebSphere Suite Microsoft – BizTalk, etc. Oracle – SAP – NetWeaver Sonic – Sonic ESB Sun – OpenSource Efforts WDI Business Integration Engine MULE Framework Hybrid Architecture:  Hybrid Architecture GIG-ES USAF-ES Individual Programs and Proponents HR Web- Sphere CW TBD ACQ TBD I&E TBD LOG Net- Weaver FM TBD Domain Integration Brokers/ESBs ARMY LandWarNet Core Enterprise Services (CES) Enterprise Services Core (CES) Business (BES) Army Pre-Certification Process:  Army Pre-Certification Process Ensure Army Business Information Systems beyond FY-2011: Align to WMA (Operational) Architecture; Don’t Create Gaps or Overlaps Business architectures aligned to Army warfighting architecture & operational requirements (G3, in coordination with TRADOC and appropriate Domain leaders, validates OV-5 to APGM/COCOM 127 and Army Doctrine) Align to EIE MA Architecture Will work with future LandWarNet (G6 Validates AV-2, SV-2 and TV-1) Interoperate with Other Business Systems Follow Army technical strategy for interoperability (G6 Validates AV-2, SV-2 and TV-1) Use Army-wide Taxonomies and Ontologies (NetCentric Data Strategy, SW Blocking, JTA, etc.) Do Not Conflict with Other Business AIS; Align with POM Transition Plan matches Army Acquisition Plans and POM (ASA(ALT), in coordination with G8, validates SV-8) CIO/G6 Staffs for Domain Leader Army CIO Pre-Certifies To OSD CIO/G6 Submits to OSD Domain Develops Architecture CIO/G6 AAIC Teams with & Supports Domains Domain Leader Approves Architecture Only; NOT PfM Component Planning Guidance Drives BEA:  Component Planning Guidance Drives BEA OV-5a and 5b OV-5c SV-5 SV-4 TV-1 Army “Perspective” Drives Army Process:  OV-5a & 5b: Required Operational Capabilities (ROC) listed by TAP Code (PCnnnn) from Army Planning Guidance (APG) in Section II of The Army Plan (TAP) SV-4 & 5: Use Cases / IT-Enabled Processes Defined in DoD and Army Regulations and Operating Procedures OV-5c: Specific Tasks/Capabilities Defined in Army Doctrine and Unit Level Doctrine Army BEA Design Process Flow Example Using Logistics Process PC1029: An inland bulk fuel storage and distribution system supporting U.S., joint, and Allied Forces in theaters of operation TRADOC documentation of process(es) by which battalions will order and receive fuel at forward deployed locations including which sub-tasks are IT-enabled Ability for Stryker Battalion S-4 staff to order fuel delivery at forward position and have fuel arrive just before Stryker Battalion Information Services provided by FCS/LDSS and GCSS-A as required to support automated portions of TRADOC developed process for forward fueling SV-4a, 5a & TV-1: Information Services As Implemented in Supporting Information Systems Army “Perspective” Drives Army Process Data Challenge:  Data Challenge Vertical Toolset Challenge:  Vertical Toolset Challenge Security Challenge:  Security Challenge

Add a comment

Related presentations

Related pages

A Warriors Guide to Business Architecture Powerpoint Slide ...

IE 1107 Paiva Joe SOA Implementation.ppt File Size: 5.71 KB Published on: July 23rd, 2011 Publisher: www.infoworld.com (Embed Code) Add to your ...
Read more

www.science.gov

A computerized recognition system for the home-based physiotherapy exercises using an RGBD camera. PubMed. Ar, Ilktan; Akgul, Yusuf Sinan. 2014-11-01 ...
Read more

calicutbooks.com

Sl.No. Title Author Publisher; 4903: GEOMETRIC ALGEBRA FOR COMPUTER GRAPHICS: VINCE: YESDEE : 4902: COMPILER DESIGN: VENKATESH: YESDEE : 4901: GRID AND ...
Read more

Ivory/vocab.en-fr.en at master · lintool/Ivory · GitHub

buffoonish billfish suntan 0456/2000 papadopoulo ie ... wwf. toothcomb implementation. progress ... 0632/2000 circuit paiva prototyp iedn ...
Read more

Loot.co.za: Sitemap

... Joe Eckstein 9780962173943 ... 9780619286293 0619286296 *Nh IE ... 9786611805623 6611805621 Soa Cookbook - Design Recipes for Building Better Soa ...
Read more