The Need for Standards to Ensure Efficient eBusiness

1
The Need for Standards to Ensure Efficient
e-Business

• John Kendall EMSA Technical Coordinator

2
Agenda

• What is EMSA
• What is e-Business
• What is marine Product Data
• Industry Standards EMSA Protocols
• Hull structures
• Machinery and equipment
• Benefits

3
Introduction

• Why standards are important
• Expanding the business
• Learning lessons form other industries
• beyond CAD to PDM and ERP
• Reuse of data in service and Product Lifecycle
  Support (PLCS)
• From hull to machinery and equipment

4
EMSA Summary

• Founded in 1994
• Membership includes shipyards, class societies,
  model basins, software houses and research
  institutions from Europe and US
• 4 Levels of membership
• Full large company (12,000)
• Full small company (4,800)
• Observer (2,400)
• Academic (Free, but must contribute effort)

5
EMSA Function

• Promote deployment of Product Data Standards in
  the Maritime Industry
• Implement early versions of models and test
  prototypes
• Provide harmonised contributions to the
  development of ISO 10303 Ship Product Model
• Define scenarios based on existing business
  processes
• Establish, co-ordinate, and support maritime
  Product Data projects
• Disseminate Know-how and results
• Maintain repository of marine International
  Standards

6
What is e-business

• e-business is doing your business electronically
• What do you want it to be?
• It is necessary to look at your business needs
  first
• But generally
• e-business is the use of information and
  communication technology to streamline business
  processes and improve communication with internal
  and external organisations.

7
What is e-business

• It may constitute one or more of the following
  components
• Electronic working
• System integration
• Marketing
• E-commerce
• Supply chain integration
• Collaborative product commerce

8
Why e-business?

• Use e-business to
• Streamline your business processes
• Lower costs
• Create savings
• By
• Linking dealers and suppliers
• Reducing lag time and paperwork
• Online procurement
• Links to vendors
• Web enabled billing and payment

9
Implementing e-business

• Technology is not a substitute for a business
  strategy
• Look at your business first!
• Business objectives
• Business processes
• Information required to fulfil those processes
• Interfaces
• Organisations, both internal and external
• Systems
• Implementation technology
• Formats
• Platforms

10
What is Product Data

• Digital description of the characteristics of a
  physical product, for example
• Shape
• Material
• Surface treatment
• Configuration
• Function
• Manufacturing data
• More than is covered by traditional exchange
  formats such as DXF and IGES

11
What standards?

• ISO 10303 (STEP)
• ISO 13584 Parts Libraries
• ISO 15926 Oil and Gas
• XML
• (MTML Marine e-Commerce Association)

12
ISO 10303 Ship Application Protocols
Outfit and furnishing (AP236)
(AP227)
Electrical (AP212)
13
Deck
Bulkhead
Plates
Stiffeners
opening
14
EMSA Protocols

• Industry standards for the exchange of product
  data within clearly defined usage scenarios
• Achieve business benefit in advance of the
  International Standards being published
• Exact subsets of International Standards
• Will be withdrawn when Standards covering the
  same scope are published
• XML Schemas based on EP models published (e.g. on
  XML.org)
• Coordination with other standards (e.g. NSRP)

15
Hull Business cases
Classification Society
Owner
Prime Shipbuilder
Model Test Basin
Subcontracting Yard
16
Business cases published as Industry Standards
17
Structural Design for Hull Cross Section Approval
18
Hull Form Design for Model Testing
19
Hull Condition Monitoring
20
Machinery based business cases

• Machinery 7 new business cases. Exchange of
• Product data to support quotation based
  procurement process
• BOM to support CAD/ERP integration and
  cartalogue based procurement
• Machinery design data to support simulation and
  functional verification
• Machinery design data to support class type
  approval and product certification.
• Machinery product data to configure maintenance
  systems
• Machinery operational data to support survey and
  maintenance requirements
• Component libraries and product catalogues

21
Quotation based procurement processes

• The following parties play a role in this
  scenario
• Yards with an ERP system maintaining a collection
  of RFQs related to a project
• Suppliers of equipment, with an internal CRM/ERP
  system for follow-up
• An e-business service provider supporting the
  shipbuilding RFQ procurement process.
• The information to be exchanged will have the
  following scope
• Top-level RFQ data
• RFQ line items
• Technical requirements/specification
• Commercial terms and delivery requirements
• Address and contact information
• Attachments and drawings
• Prices and performance data (quote)

22
CAD/ERP integration and catalogue based
procurement

• The following parties play a role in this
  scenario
• Yards with both a CAD and ERP system
• Component suppliers
• e-Business service provider supporting the
  shipbuilding procurement process.
• The information to be exchanged will have the
  following scope
• BOM meta-data
• BOM fittings line items
• Commercial terms and delivery requirements
• Address and contact information
• Attachments and drawings
• Prices and performance data (quote)

23
Simulation and reliability analysis

• The design of machinery systems involves the
  necessary validation of the design by simulation.
  
• This simulation can consist of both
  quasi-stationary and dynamic simulation,
• The success of such design software is dependent
  on the quality of the source data on which the
  simulation is based.
• In many cases the data will come from multiple
  sources, in that the yard will assemble the
  system but the components of the system may come
  from several suppliers.

24
Classification Society type approval and product
certification

• Unlike the classification of ships, which are
  done on an individual basis, a Classification
  Society will use its rules and regulations to
  approve machinery on a 'type' basis.
• All instances of that type are then deemed to be
  approved by the Classification Society.
• This type approval can involve many calculations
  on the parameters of the machinery.
• This process can be speeded up and services
  improved by the application of electronic data
  exchange.

25
Configuration of planned maintenance systems

• A planned maintenance system is used to determine
  the need for inspection or maintenance of
  equipment items and mechanical systems.
• Input to a maintenance system consists of initial
  maintenance requirements these are created by the
  supplier of the equipment and delivered as a part
  of it.
• planned maintenance systems especially onboard
  ships PMS operate as stand-alone applications.
  However, they need and produce information today
  this cannot directly be communicated with other
  systems.
• Machinery maintenance requirements data include
  in this context
• product identification data, such as serial
  number and type description,
• types of maintenance jobs
• the intervals at which the supplier requires
  them.

26
Operational and maintenance data to support
survey and maintenance

• Focuses on safety critical equipment and feedback
  from operation, maintenance, and inspection.
• Feedback is provided through data communication
  from ship to shore, i.e. shipowner/manager and
  classification society.
• The purpose of this data communication is to give
  input to risk based survey schemes and
  reliability centred maintenance systems.
• Such schemes and systems will make it possible to
  enhance inspection and maintenance interventions
  reducing costs for the ship manager.
• The benefits of such data transfer are to
• Optimise planned maintenance activities
• Harmonise classification survey with operational
  and maintenance experiences
• Obtain systematic feedback from maintenance to
  design and classification rules.

27
Expected Benefits - Shipbuilder

• Facilitates business process re-engineering for
  improved efficiency
• Facilitates single source of data throughout
  design, production and in service support
• saving costs
• greater scope for plug and play IT solutions
• Reduction in time for design and construction
  more time to investigate design options

28
Expected Benefits - Class Society

• Reduce the need to re-digitise data supplied by
  shipbuilders for
• stability assessment
• hull design assessment
• Improve efficiency of processes
• Improve accuracy of data capture
• Improve turn-round time and response

29
Expected Benefits - Ship Owner

• Reduced lead time for design and manufacture
• Lifecycle support for ship data
• Survey
• Maintenance
• Disposal

30
Expected Benefits - Software Houses

• Fewer translators to support
• Niche products more easily integrated
• Competitive advantage by giving the customer what
  he wants

31
Benefits - Example savings

• European shipyard estimates
• Reduction in design time 4 to 6 weeks per design
• A saving of 500 kECU per design
• 20 reduction in effort for Classification plan
  approval
• model basin spends 300 to 500 man days per year
  to digitising data

32
Demonstration
33
Summary

• The industry has the need to manage ship data
• as part of business
• more efficiently and effectively
• Cost-savings and increased efficiency will
  materialise from e-Business implementations
• Standards will ensure that the benefit from
  investment in e-Business technology can be
  maximised
• EMSA provides a forum for the development of
  Marine Related data exchange and management
  standards
• EMSA will harvest the results from funded
  projects and provide a repository for future
  development
• EMSA promotes the development and use of product
  data standards

34
Contact

• John Kendall
• EMSA technical coordinator
• Eurostep Limited
• Coordinator_at_emsa.org
• http//www.emsa.org