First OMAC Symposium Reportout: - PowerPoint PPT Presentation

1 / 59
About This Presentation
Title:

First OMAC Symposium Reportout:

Description:

MSMUG- Should be horizontal across all (discrete, process, hybrid, etc. ... Toyota, Nissan, Dodge (who do we get to the table) Get the OMAC message out! ... – PowerPoint PPT presentation

Number of Views:68
Avg rating:3.0/5.0
Slides: 60
Provided by: isa60
Category:

less

Transcript and Presenter's Notes

Title: First OMAC Symposium Reportout:


1
First OMAC Symposium Report-out Identifying and
Bridging Gaps Creating OMAC Future
Hosted by
2
OMAC Timeline of Development
2005 Affiliation with ISA
2007 1st OMAC Integration Symposium
2007-8 Symposium Output Action Items
Network Integration
1997 Evolution of Working Groups
2008 OMAC Sponsors BOD input
  • Packaging
  • Mfg Infrastructure
  • Machine Tools

Assessment Direction Setting
1994 OMAC Organized
2008 Fall 2nd OMAC Symposium
ThenNow.. and .. Future
3
Accomplishments of the Symposium
  • Face to face networking with colleagues.
  • Technical presentations by members.
  • Tour of the Boeing 787 final assembly area.
  • Identifying the OMAC body (who we are, and what
    we are here together to do).
  • Working together to define needs and requirements
    of the global community / market place with
    respect with what OMAC can offer.
  • Identifying possibilities of what OMAC can and
    should (and should not) offer.
  • Prioritizing those possibilities.
  • Accepting action items to move forward activities
    to accomplish creating further clarity regarding
    the direction and purpose of OMAC.

4
Demographics Who attended
  • Industry Areas 50
  • Discrete 40
  • Hybrid 2
  • Process 1
  • Work Groups 50
  • Packaging 2
  • Manufacturing Infrastructure 2
  • Machine Tools 8
  • Other (revote of all) 38
  • Tech Providers 17
  • End Users 17
  • Global Mfg 2
  • System Integrators 2

5
Discovery Process
Outputs Demographics Topic Categories Needs /
Rqmnts Essential Dialogue Issues Parking Lot
OMAC Vision, Mission, Goals, Objectives
Strategic Roadmapping Exercise
Brainstorming Exercise
Closure Session
Outputs Action Items Prioritization Future
Topics Issues List

Outputs Topic Issues Issues Ranking
6
Rolled-up Topics Summary
  • Industry Areas Discrete / Hybrid / Process
  • Does OMAC still meet an industry needs?
  • Working Groups Packaging / Mfg Infrastructure /
    Machine Tools / Others ?
  • Does OMAC have the right Working Groups in their
    ranks are they addressing the right issues?
  • Is MSMUG a good fit for OMAC?
  • How do we capture greater participation from new
    Machine Builders
  • Globalization
  • Security / Sourcing / Supply chain mgmt ./ Mfg.
    machines / Dev. Nations / Interoperability
  • Standardization
  • Standards / Bus. Process / Com. Process / Best
    practices
  • How to get adopt
  • Better define Integration of OMAC Standards into
    Industry Standards
  • How to Leverage Best Practices and Lessons
    Learned (to define guidelines for integration
  • Workforce Development
  • Education training / Skills / Certification

7
Team Prioritized Summary
  • The next seven charts represent the top voted
    (consensus) items from the teams that selected to
    work that particular topic.
  • (n) signifies the team whos input it is.
  • signifies an action item that was initiated on
    the item, followed by a brief description of who
    and what will be worked.

8
Industry Areas Discrete / Hybrid / Process
  • Refine OMAC mission statement. (2) BOD
  • Broaden membership base, globally and by
    industry. (2) BOD also Collective Machine
    Tool Show - Sept 2008 and ARC Forum - Feb 2008,
    have an OMAC booth
  • Greater end user participation. (3 4) BOD-
    mission statement alignment also create a
    Marketing Team - Darrin Elliott
  • Incentives for innovations. (4)

9
Working Groups Packaging / Mfg Infrastructure /
Machine Tools
  • Review mission statement, identify target segment
    OMAC is trying to reach. (1) BOD
  • Board of Directors needs to clarify the roles of
    the Automation Federation in each of the
    different entities (ISA, WINA, WBF, OMAC). (1)
    BOD
  • Enterprise / line Integration (e.g. packaging).
    (2)
  • Engineering process (e.g. life cycle). (2)
    Collective Whitepaper for OMAC 2008
  • Articulating the need to the industry. (4)
  • Synthesizing best practices to the industry. (4)

10
Globalization
  • Review mission statement. (2) BOD / Technical
    Advisory Board
  • Redirect / Re-brand OMAC name change? (3) BOD
    / Technical Advisory Board
  • Mobility of machines in production (e.g.
    Manufacturing movement). (4)
  • Consolidation National standards. (4)

11
Standardization
  • Too many organizations / societies competing for
    the same membership. (1) BOD sponsorship
    clarity / mission statement review
  • Providing best practices to OMAC membership, via
    web need a working group to manage this
    activity. (1)
  • Define business benefits. (2)
  • Harvest existing standards guidelines. (2)
  • Enable and promote benchmarking. (3)
  • Modular architecture standard stack-up. (4)
  • Intuitive visibility (dashboard standard) of
    process from end user all the way up to
    management. (4)
  • CNC pilot - Demonstrate PackML mode and states
    definitions for machine tools. (2) John
    Michaloski, Dave Bauman and Sid Venkatesh

12
Workforce Development
  • Developing control systems that are fault
    tolerant, easy to use, and can easily interface
    with other systems. (1)
  • Develop next generation of professionals via
    University and High School programs. (1)

13
Machine Manufacturing
  • Lean manufacturing best practices as it applies
    to controls. (1)
  • OMAC to reference a guideline regarding
    design/build safety and safeguarding. (1)
    Thomas Hoertig new work group formation
  • Define value proposition (3)

14
Business Operations
  • Not worked by any of the teams.

15
Lexicon of Terms
  • TBD Sid (take this action item???) all acronyms
    terms given, that are not clear to
    stakeholders, newcomers, or outsiders who will be
    looking at this report.

16
End of Summary
  • Second OMAC Symposium will be hosted by Okuma
    America Corporation, Charlotte NC Fall 2008.

17
4-Team Brainstorm Lists on the 7 Summary Topics -
Details
18
Brainstorm Topics
  • Industry Areas Discrete / Hybrid / Process
  • Does OMAC still meet an industry needs?
  • Working Groups Packaging / Mfg Infrastructure /
    Machine Tools / Others ?
  • Does OMAC have the right Working Groups in their
    ranks are they addressing the right issues?
  • Is MSMUG a good fit for OMAC?
  • How do we capture greater participation from new
    Machine Builders
  • Globalization
  • Security / Sourcing / Supply chain mgmt ./ Mfg.
    machines / Dev. Nations / Interoperability
  • Standardization
  • Standards / Bus. Process / Com. Process / Best
    practices
  • How to get adopt
  • Better define Integration of OMAC Standards into
    Industry Standards
  • How to Leverage Best Practices and Lessons
    Learned (to define guidelines for integration
  • Workforce Development
  • Education training / Skills / Certification

19
Team 1 - 1 Working Groups
  • Review mission statement (OMAC current relevance
    to industry) Identify target segment OMAC is
    trying to reach.
  • BOD should clarify roles of Automation Federation
    on how governing body is provided to all the
    different entities (ISA, WINA, WBF, OMAC)
  • Recruit for OMAC participation from industry
    building critical mass.
  • Promote MSMUG to Automation Federation.
  • Build a matrix of societies and industries and
    their roles, responsibilities and authority to
    determine OMAC participation, goals, and
    objectives.
  • (Goal) Build reference list of application of
    standards (success stories/failures), general
    application rule of thumbs.
  • Typical business problems and how they are solved
    by standards.
  • Build a glossary of terms and definitions.

20
Team 1 - 2 Standardization
  • Problem Too many organizations (societies) are
    competing for the same membership.
  • Best Practices Communication best practices to
    OMAC members/(industry).
  • List applicable standards for specific industries
    and/or machines.
  • Reference list of standards to OMAC members.
  • (Issue) OMACs role with respect to standards
    (new?) or guidelines (current)?
  • Success stories, solicit OMAC members (symposium
    presentations, etc.)
  • Better definition integration standards

21
Team 1 - 3 Machine Manufacturing
  • Lean manufacturing/best practices as applies to
    controls.
  • OMAC reference of guidelines (best practices)
    regarding machine safeguarding (and training)
    (build in safety, lean).
  • OMAC reference of regulation and requirements
    regarding machine safety and operation.
  • Lean manufacturing education and training with
    respect to OMAC.

22
Team 1 - 4 Workforce Development
  • Developing control systems that are more fault
    tolerant, user friendly, and can easily interface
    with other systems.
  • Developing next generation professionals.
    Participate university/high school education.
  • Training in safety.

23
Team 2 Topics Voted
  • Industrial areas 7
  • Work group 8
  • Globalization 6
  • Standards 9
  • Workforce development 3
  • Manufacturing and machinery 3
  • Business operations 2

24
Team 2
  • Refine OMAC mission statement
  • Broaden membership base globally and by industry
    process.

25
Team 2 - 1 Industry Areas
  • Process industry already had this activities,
    have standards.
  • Consolidated automation forums
  • Participation at similar events (medical)
  • Technology providers should be active in
    spreading the word
  • Awareness of OMAC in other industries not there
    yet.
  • How to relate OMAC to other groups/activities
  • Avoid redundancy
  • Concentrate on concepts/architecture
  • What is OMAC?
  • What are the boundaries of OMAC?
  • Go beyond hardware/software
  • OMAC/controls to restrictive?
  • Initial goal interoperability
  • System vs. enterprise integration
  • Integration not industry specific
  • Align with existing standards
  • Naming vs. definitions
  • Take input from various areas (Asia, )
  • New formats of participation (internet,)

26
Team 2 - 2 Working Groups
  • MSMUG addresses interoperability
  • Tow main topics enterprise integration, line
    integration.
  • PackML should go beyond packaging
  • PackML already applies to other areas (material
    handling)
  • Engineering process important
  • Draw in other industries with more generic
    groups
  • OMAC should focus
  • MSMUG does not fit current OMAC scope
  • Relation of ISA, OMAC, Automation Federation
  • Introduce generic topics like IT security and
    patch management to cover more industries.
  • Focusing vs. broadening
  • Working groups should have clear deliverables and
    finite lifetimes
  • OMAC activities and standards should have impact

27
Team 2 - 3 Standardization
  • How to handle regional specifics
  • Can standards apply to various regions?
  • Guidelines vs. international standards
  • Prerequisite business benefit
  • Harvest existing standards, OMAC can build on top
    of them (extend PackML)
  • Directory of standards
  • Use other groups for reviewing
  • What are other relevant standards?
  • Turn guidelines into standards
  • Which areas should be addressed (vision, RFID, )

28
Team 3
  • Get greater end-user participation
  • Make it easy, give them rationale
  • Redirect/re-brand OMAC
  • Define value proposition
  • Papers, education, presentations
  • Enable and promote benchmarking
  • Symposiums, conferences, etc
  • Standards, best practices, processes
  • Collaborate with other user groups

29
Team 3 Top Four Items
  • Industry areas How do we get representation
    from
  • Standardization
  • Globalization
  • Machine and manufacturing

30
Team 3 - 1 Industry AreasHow do we capture
greater representation from other industry
areas?Does OMAC still meet industry needs?
  • MSMUG- Should be horizontal across all (discrete,
    process, hybrid, etc.)
  • Should MSMUG be a member of OMAC or should they
    be separate?
  • Packaging workgroup successful
  • OMAC mechanism to pull together the discrete
    industry
  • Evaluate the effectiveness of the workgroup?
  • Toyota, Nissan, Dodge (who do we get to the
    table)
  • Get the OMAC message out!
  • How do we get the end-users back?
  • PAC-EXPO
  • IMTS (AMT) machine tool group?
  • Newsletter
  • Small and medium sized company
  • Electronic
  • Should a company of any size join OMAC?

31
Team 3 - 2 GlobalizationSecurity, sourcing,
supply chain management, interoperability,
developing nations
  • How do gain the advantage in a global market
  • Source and integrate, level of performance?
  • Leverage Automation Federation relationships
  • Join How do we capture greater representation
    from other industry areas?
  • Does OMAC still meet industry needs?
  • Join OMAC and globalize (S-M B)
  • Focus on US success before moving
    abroad-international
  • New branding name?
  • Advanced manufacturing
  • Collaboration

32
Team 3 - 3 Standardization- Standards, business
process, best practices- How to get and adapt-
Better define OMAC standards integration into
industry standards- How do we best leverage OMAC
standards and lessons learned- Get greater
involvement- Get a replacement for dave_at_boeing
  • S88P5
  • Spread the word?
  • Whos using it?
  • Will they talk about it?
  • Leverage the proliferation
  • Articles
  • PLC Open with OMAC PLVGS
  • ISO, ISA relationships
  • Advocate the use of standards
  • STEP for dummies machine tool
  • S88
  • Build consensus through presentations at
    symposiums/conferences
  • CNC manufacturers
  • CAM
  • Machine tool
  • Tool change guideline completed

33
Team 3 - 4 Machine and Manufacturing -
Operations, safety, efficiency
  • Identify lean users
  • Identify process optimization users
  • How can OMAC help?
  • Redesign manufacturing infrastructure working
    group to address
  • Optimization
  • Lean architecture
  • MES, ERP
  • PLM

34
Team 4 Industry Areas
  • Industry areas not as stratified as given
  • Industry is fragmented
  • Should synthetic
  • Needs deliverable
  • Stagnation
  • Should we do away with separation?
  • End user focus currently vendor/OEM
  • Greater participation
  • Collaborative web site
  • Greater visibility
  • Better definition of purpose
  • Deep or wide or both
  • Matrix of purpose
  • Discrete lags process
  • Less different 55-80 same
  • Define common set
  • V-interoperability
  • X-supply chain

35
Team 4 Industry Areas Top 5
  • Greater participation
  • End users mom/pops
  • Should we go deep or wide?
  • Discrete should borrow from process
  • Collaborate with other groups like IEEE, SME, AMT
  • Resource management
  • Optimize OEE, reduce scrap
  • MOMOSA, IMS

36
Team 4 Working Groups
  • Deep or wide
  • Process Hybrid Discrete integration
  • Lessons learned
  • Packaging/process
  • ERP
  • Data modeling
  • Equal representation
  • Do we have the right groups?
  • Infrastructure wide or narrow
  • Packaging
  • Machine tools narrow
  • Methodology
  • User forum experts
  • Knowledge base web
  • Integration
  • Recommendation body
  • Articulate needs of the industry
  • Raise business/process issues
  • Synthesize best practices across industry

37
Team 4 Working Groups Top
  • Charter
  • Articulate needs of industry
  • Knowledge base/expert moderated user forum on web
  • Equal representation
  • Produce methodology white paper
  • Synthesize best practices across industries
  • Add workgroup
  • Integration
  • Strategy vision and mission statement

38
Team 4 - Globalization
  • Countries do share the same standards
  • Mobility of machines and production
  • Cost issue
  • Regulations
  • No safety standards
  • Retrofit cost
  • Nation specific standards
  • Consolidation of national standards organizations
  • International standards organization same problem
  • Regional bias CE
  • Global standards
  • Outsourcing moving to clustering

39
Team 4 - Standardization
  • Modular architecture
  • Standard stack
  • Define where we fit in the mosaic
  • Interoperability
  • Technology vs. business process
  • Marketing
  • Intuitive visibility of processes to end users
  • Up to management

40
Team 4 Standardization (cont.)
  • Modular architecture
  • Interoperability
  • Collaborate with other groups (Aberdeen, AMT,
    ISO, IEEE, )
  • Technology/process (business)
  • Two flavors
  • Intuitive visibility to end users
  • Up to high level
  • 100s K lost in machine maintenance
  • Move toward predictive maintenance
  • Marketing
  • Standardization stack
  • Stratification
  • Open / free
  • Define level where we fit in mosaic

41
Organizing Objectives
42
OMAC Users Group - Objectives
  • The OMAC Users Group was formed in 1994 as an
    organization for companies to work together and
  • Collectively derive common solutions for both
    technical and non-technical issues in the
    development, implementation, and
    commercialization of open, modular architecture
    control (OMAC) technologies. 
  • Promote OMAC development among control technology
    providers and OMAC adoption among end users,
    OEMs, and system integrators. 
  • Act as a repository for OMAC requirements and
    operating experience from users, software
    developers, hardware builders and OEMs in
    manufacturing applications. 
  • Facilitate the accelerated development and
    convergence of industry- and government-developed
    technology guidelines to one set that satisfies
    common use requirements. 
  • Collaborate with users groups around the world in
    pursuit of common international technology
    guidelines.

43
OMAC Users Group in 2007
  • We currently operate three Working Groups
    Packaging Machinery, Manufacturing
    Infrastructure, and Machine Tool. These groups
    lead the way in producing consensus guidelines to
    improve flexibility, improve capability, and
    reduce system integration costs. We also seek to
    improve the automation industrys capabilities by
    defining the educational and training needs of
    our community.OMAC has about 500 member
    representatives from end-user companies, OEM's,
    and technology providers and integrator
    companies. These members include companies with
    vested interest in developing and implementing
    open control technologies for manufacturing
    applications.

44
2007 OMAC Forum
  • OMAC welcomes you to attend its first Annual
    Technical Symposium. The theme of this symposium
    is "Bridging the Gap Between the Discrete
    Process Industries," and will focus on improving
    integration by leveraging best practices and
    lessons learned.Purpose
  • The theme of the symposium will be centered on
    integration between the process and discrete
    industries, using standards like those for CAM
    and CNC control, inspection, CAD definition, data
    packaging, process planning, and automotive.
  • This two day event is intended to bring together
    and integrate the OMAC Working Groups (machine
    tools, packaging, MS MUG, etc.) into a single
    cohesive body that will work towards a common
    objective enhancing the collaboration between
    process and discrete industries.
  • The goals of the event include developing a
    collaboration and integration roadmap, creating a
    forum, enabling better collaboration between the
    process and discrete industries via the OMAC
    Working Groups, and serving as an effective
    networking opportunity for attendees. Another
    outcome of the symposium is the identification
    and organization of a planning committee for the
    2008 OMAC Technical Conference.

45
Packaging Working Group
  • The objective of the Packaging Working Group is
    to maximize the business value of packaging
    machinery by improving automation guidelines.
    This will lead to improved flexibility, improved
    capability, and reduced system integration
    costs.
  • We seek to maximize end-user and OEM machine
    automation choices, and increase flexibility,
    facilitate a smaller footprint machine, achieve
    faster throughput, and reduce costs through
    greater industry openness and interoperability.
    This will allow end users to connect-and-pack
    different technology solutions to meet their
    business needs.
  • To attain this goal, we work with automation
    suppliers, OEMs, and trade groups worldwide to
    encourage their supporting of the
    connect-and-pack guidelines throughout their
    products and practices, creating a mutually
    beneficial environment for the guidelines.
  • We also seek to further expand and develop the
    connect-and-pack guidelines to provide easier
    integration horizontally (process to packaging)
    and vertically (packaging to ERP
    systems).Guidelines for Packaging Automation
    Version 3.1 - This document is a compilation of
    the guidelines for the OMAC Packaging Workgroup
    and is periodically updated as the subgroups
    develop and enhance these guidelines.  This
    version is updated with the PackAL guidelines
    developed by the PackSoft sub-group.

46
VMGO Packaging (cont)
  • There are five Packaging sub-groups
  • PackSoft - developing guidelines for machinery
    programming languages to ease learning, support
    transportability of software across platforms,
    and allow continuing innovation
  • PackConnect - defining the control architecture
    platforms and connectivity requirements for
    packaging automation systems
  • PackAdvantage - Identify and communicate to the
    packaging industry the Benefits/Results of using
    connect pack guidelines for packaging
    automation systems
  • PackML  naming convention guidelines for
    communications between production machinery
    within the packaging industry.
  • PackLearn - promotes awareness of Group
    initiatives by defining, and developing programs
    to meet, the educational and training needs of
    the industry
  • PackAL V1.3 Proposal - This document is the
    updated PackAL document that has been updated by
    the PackSoft subgroup. The major changes to this
    document are to reflect the PackML Version 3
    changes. This proposed update will be voted on at
    the OPW Executive Committee at their meeting
    scheduled for May 14th. Please provide any
    comments on this document to Gerd Hoppe
    (g.hoppe_at_beckhoff.com) who led the team that has
    updated this document.
  • PackML Version 3.0 Approved - This is the latest
    version of PackML that was approved at the OMAC
    Packaging Workgroup Executive Committee Meeting
    on October 31st at PackExpo.
  • PackTags V3.0 Approved - This is the latest
    version of PackTags that was approved by the OPW
    Executive Committee on January 8th.

47
Manufacturing Infrastructure Working Group
  • The mission of the Manufacturing Infrastructure
    Working Group (MIWG) is to maximize the business
    benefits of manufacturing systems by developing
    common guidelines and solutions for architecture
    and software usage issues when implementing and
    integrating manufacturing systems and ensuring
    architecture consistency.
  • We aim to become the leading advocacy group for
    resolving manufacturing system implementation and
    integration issues and defining common
    manufacturing architecture and software usage
    guidelines, resulting in business benefits to end
    users, technology suppliers, and machine
    builders.
  • Currently, there are two subgroups under this
    working group
  • OMAC Architecture Group
  • Microsoft Manufacturing Users Group

48
Manufacturing Infrastructure Working Group
  • OMAC Architecture Group
  • Our mission is to define the concept of Open
    Modular Architecture Controls (OMAC) and
    associated high-level control system
    architectures for discrete, hybrid, and
    continuous manufacturing systems. The goal of the
    OMAC architecture is to reduce the total life
    cycle cost associated with manufacturing control
    systems by leveraging systems built on open and
    de facto standards and commercial off-the-shelf
    hardware and software components.
  • To this end, we will promote the open systems
    available in manufacturing control systems and
    plant floor systems that support manufacturing
    operations and identify areas where open system
    standards are lacking in manufacturing control
    systems and address them.
  • Microsoft Manufacturing User Group (MS MUG)
  • The Microsoft Manufacturing User Group was formed
    in 1999 to address issues that arise when
    applying Microsoft technology in manufacturing.
    Our mission is to define and resolve these
    issues, such as version management, system
    integration, maintenance, and supplier
    responsibility.
  • To achieve this goal, we seek to develop a set of
    best practices that will aid in the use of
    Microsoft operating systems in manufacturing
    environment provide input to Microsoft on the
    special needs of this environment encourage and
    influence software suppliers to support these
    best practices and provide user input to the OPC
    Foundation on changes and improvements to OPC.
  • There are three teams under this sub-group
  • MUGSecure focused on increasing Windows
    operating system reliability and security by
    developing Best Practices for configuring Windows
    in a control system environment.
  • MUGPatch concentrates on best practices for
    upgrade validation with OS patches
  • MUGOPC concentrates on the expanding need to
    update user issues into OPC standards

49
Machine Tool Working Group
  • The Machine Tool Working Group is charged with
    maximizing the business value of discrete part
    machinery by providing automation guidelines,
    developing best practices, and assisting in
    international standards development.
  • Our primary objective is to create an environment
    that maximizes the machine automation choices of
    end-users and OEMs, and increases their
    flexibility through greater openness and
    interoperability. To ensure that this goal
    becomes a win-win situation, we work with CNC
    controller vendors, CAD/CAM suppliers, and CNC
    OEMs to encourage their support of OMAC-endorsed
    open-architecture specifications and other best
    practices through their products and practices.
  • There are two sub-groups under this working
    group
  • STEP-NC working to understand and assess ISO
    10303 in the context of OMAC
  • HMI-API - defining a common HMI API for all CNC
    devices

50
OMAC Parking Lot Items
  • Industry Areas Discrete / Hybrid / Process
  • How do we involve or capture representation,
    membership participation from other industry
    areas?
  • Does OMAC still meet an industry need?
  • Are there new needs we should be addressing?
  • Working Groups Packaging / Mfg Infrastructure /
    Machine Tools / Others ?
  • Does OMAC have the right Working Groups in their
    ranks are they addressing the right issues?
  • Is MSMUG a good fit for OMAC?
  • How do we capture greater participation from new
    Machine Builders

These items are included in the Master topics
list, as well
51
Process Descriptions
52
Creating the Future
  • Roadmapping A strategic process to identify and
    meet future marketplace needs (and requirements)
    by strategic visioning, connecting, and linking
    of technologies, products and services to those
    needs.Our version of this modified process
    yields affinitized (rolled up) categories of
    essential items of interest germane to OMACs
    existence.
  • Integrated planning activity A lightly
    structured brainstorming process based on the
    categories from the Roadmapping process, to drive
    out details of practical interest and to help
    create tactical plans for accomplishing near-term
    goals and objectives.

53
Integrated Roadmapping Concept
Ensures alignment of Technology Product
Development Plans with Market Opportunities
Influences
Product Service Roadmap
Know What
Drivers / Thrusts
  • Potential Product Services Offerings Both Pull
    Push
  • Strategic Capability Needs

Options
Technology Process Roadmap
Know How
Needs / Requirements
  • Progressive, Alternative Disruptive Solutions /
    Processes
  • Intra Inter -Structure
  • Partnerships
  • Suppliers, VCs, Etc.

Time
54
Keep in Mind the End Objective..
  • The 7 Habits of Highly Effective People

55
Notional Information
  • These next few charts indicate the direction of
    interest for the current body of OMAC, that was
    in attendance at the 1st Symposium.

56
OMAC Market Roadmap Information (42) 32 - 5yr /
8 10yr / 2 -
  • Globalization (15)
  • Security / Sourcing / Supply chain mgmt ./ Mfg.
    machines / Dev. Nations / Interoperability
  • Standardization (10)
  • Standards / Bus. Process / Com. Process / Best
    practices
  • How to get adopt
  • Workforce Development (8)
  • Education training / Skills / Certification
  • Machine Manufacturing (6)
  • Operations / Safety / Efficiency
  • Business Operations (3)
  • Geo-political / Industry consolidation / Mergers.
    Acquisitions

57
OMAC Products Services Roadmap (40) 33 - 5yr /
4 10yr / 3 -
  • Services (14)
  • Training Education / Conferences symposia /
    Working group collaboration (9)
  • Industry liaison / Networking tool /
    Communication marketing tool (5)
  • Products (26)
  • Standards / Guidelines

58
OMAC Needs Requirements (34) 28 - 5yr / 4
10yr / 2 -
  • Standards (21)
  • Business Operations (9)
  • Workforce Development (4)

59
OMAC Technology Roadmap (25) 20 - 5yr / 4
10yr / 1 -
  • Training Education (8)
  • Standards (14)
  • Business Operations (3)
Write a Comment
User Comments (0)
About PowerShow.com