8/8/2019 Manufacturing Enterprise System
1/26
Manufacturing Enterprise Systems
Submitted by:-
Richa Sahni(09609072)
Snigdha Nehru(09609117)Himanshu Johari(06104663)
8/8/2019 Manufacturing Enterprise System
2/26
Current environment
Successful businesses develop product to meet customer needs,
and they bring product to the market quickly, priced for value.
convince users that their product will improve their productivity,
quality and profitability
Business Challenges
To achieve the proper level of decentralization.
To integrate the manufacturing processes and information with the
other business processes.
28-Sep-102
Manufacturing Enterprise Systems
8/8/2019 Manufacturing Enterprise System
3/26
Challenges In The Focus Areas
Time Management
Introduce new products into the market more quickly,
Attain useful cycle time measurements to apply towards cycle time
reduction.
Resources
Effectively allocate materials, equipment and people to the right
processes and tasks.
Attract and retain people with the right skills and qualities
Business Activities or Processes
Effectively coordinate and manage the companys activities
Look for and implement continuous process improvement.
28-Sep-103
Manufacturing Enterprise Systems
8/8/2019 Manufacturing Enterprise System
4/26
Technology
Determine the right level of automation that should be applied to
business processes
Define the best technologies to use or develop
Apply a long-range vision to technology and tool usage
Regulations
Manage and track compliance with a variety of environmental,health, safety and consumer information statutes.
Business Strategies
To respond to these challenges, businesses develop
strategies to guide the introduction and application of
specific solutions. Six such strategies are listed below
28-Sep-10
4Manufacturing Enterprise Systems
8/8/2019 Manufacturing Enterprise System
5/26
Six Such Strategies Are Listed Below
28-Sep-105
Manufacturing Enterprise Systems
8/8/2019 Manufacturing Enterprise System
6/26
High-Level Manufacturing Enterprise
Model
An Enterprise Model can define an enterprise in terms of its
functions, resources, processes, products, data requirements and
constraints.
In the manufacturing enterprise, this model defines a unique set of
business processes that are performed to design, plan, produce and
market the enterprises products
28-Sep-106
Manufacturing Enterprise Systems
8/8/2019 Manufacturing Enterprise System
7/26
High-Level Manufacturing Enterprise Model
28-Sep-107
8/8/2019 Manufacturing Enterprise System
8/26
The Business Processes
Business
Management
Quality Mgtand
Improvement
ProductSupport
ProductDistribution
and Logistics
ProductionOperations
ProductionPlanning
ProductDesign
MarketingSupport
28-Sep-108
Manufacturing Enterprise Systems
8/8/2019 Manufacturing Enterprise System
9/26
Current Approaches to Manufacturing
Solutions
All Processes listed can be supported by appropriate computer-
based systems:
Market and product support systems
Product design systems Production planning systems
Production operations systems
Distribution and logistics systems
Business Management systems
Quality Management systems
8/8/2019 Manufacturing Enterprise System
10/26
Computer-Integrated Manufacturing(CIM):
Integration happens with the use of computational resources, of the manufacturingand assembly functions and resources within an industrial environment. CIMinteracts with all of the other functions of the factory enterprise from equipment onthe floor to information systems in the main office.
Product Design and Product Data:
Design of a product is a key activity within the manufacturing lifecycle. It requires two-way exchanges of product information between groups.
Support tools used-
Product Design Automation (PDA) Systems
Product Data Management (PDM) Systems
8/8/2019 Manufacturing Enterprise System
11/26
Computer-Aided Design (CAD):
two- and three-dimensional drawing capabilities
mathematical calculations simulation or manufacturing purposes,
Outputs --numerical control programs for machines, masks for printed or integratedcircuits
Monolithic - Drafting, 3D visualization, modeling, simulation, and machine controlprogram output have been lumped together in large packages with few standardizedformats and interfaces.
Embodies - product design knowledge of the organization, yet this information ishard to manage and access.
STandard for the Exchange of Product model data:
Developed - ISO 10303, supports the definition of a product and all the relationshipsit includes.
Specifies how various applications, can exchange information about that product
Independent of software and hardware system characteristics
8/8/2019 Manufacturing Enterprise System
12/26
Interfaces to External Systems:
Manufacturing organizations often include functions typically considered in
other vertical markets such as distribution, sales, customer service and
financial services. All of these systems need to have interfaces for the data
they share.Beside financial systems, interfaces may be required with other systems,
including:
Human resource management
Product distribution
Time and attendance
Customer service
Environment tracking
8/8/2019 Manufacturing Enterprise System
13/26
Infrastructure Requirements
Infrastructure requirements can be organized according to their
performance ,
system access and
integration issues.
Significance of these requirements are:
Computing Performance Requirements
Semantic Integration Requirements
Access to System Information and Functionality
8/8/2019 Manufacturing Enterprise System
14/26
Computing Performance Requirements
Performance requirements can be used by an organization for several purposes:
to set objective criteria for the selection of manufacturing objects and services from
commercial product offerings;
to define requirements for systems or objects that are developed internally; to make rational and timely decisions about system upgrades required to keep up
with expanding workloads.
Semantic Integration Requirements
Semantic Integration means allowing a client system to access information in termsof common business concepts rather than in terms of its representation in the
different systems.
Semantic Integration increases system resource load because it introduces an
additional layer of indirection in inter-application communication.
8/8/2019 Manufacturing Enterprise System
15/26
Access to System Information and Functionality:
Requirement to access, from newly-developed applications, data and
functionality.
Reusability of code is difficult and expensive if programmatic interfaces are
not already provided to that functionality and data.
8/8/2019 Manufacturing Enterprise System
16/26
ARCHITECTURE
8/8/2019 Manufacturing Enterprise System
17/26
TOP LEVEL MODEL OF OOPS
9/28/2010
17
Manufacturing Enterprise System
APPLICATION
ARCHITECTURE
APPLICATIONFRAMEWORK
SYSTEMS
ARCHITECTURE
8/8/2019 Manufacturing Enterprise System
18/26
THE APPLICATION ARCHITECTURE
Model ofBusiness policy and business process.
Implemented as a set of operating policies and procedures.
4 Cs
Complete,
concise, consistent and
coherent.
Should be described in classes, objects , attributes, services etc.
9/28/2010Manufacturing Enterprise System
18
8/8/2019 Manufacturing Enterprise System
19/26
BUSINESS PROCESS SUPPORT
Market and product support
Product design
Production planning
Production operations
Distribution and logistics
Business management
Quality management
28-Sep-10Manufacturing Enterprise Systems
19
8/8/2019 Manufacturing Enterprise System
20/26
PROBLEMS
No such fully elaborated model is currently available at any price.
Every manufacturing concerns actual business policy or process may be
different.
Neither the Manufacturing DTF nor the OMG as a whole may be able to
motivate the proper players to participate in the construction of a fully
elaborated Manufacturing Enterprise Model.
The application architecture may impose requirements on the Analysis and
Design Task Force to provide sufficiently robust analysis methods to capture
the significant characteristics of manufacturing systems business policy and
processes.
9/28/2010Manufacturing Enterprise System
20
8/8/2019 Manufacturing Enterprise System
21/26
THE SYSTEMS ARCHITECTURE
Model of an automation mechanism.
Preferred model is OMA(Object Management Architecture).
Components of OMA
CORBA, the Common Object Request Broker Architecture,
CORBA services, previously known as Object Services,
CORBA facilities, previously Common Facilities,
Application Objects.
9/28/2010Manufacturing Enterprise System
21
8/8/2019 Manufacturing Enterprise System
22/26
POTENTIAL EXTENSIONS @
MANUFACTURING Externalization Service: to validate how object state is
provided within manufacturing systems.
Naming Service: to make sure that it supports the waymanufacturing entities are identified.
Logging Service: to make sure that it supports the types of
audit trails needed in manufacturing. Security Service: to support the authentication of multiple,
serialized users of the same object or facility.
Synchronization Service between redundant data may berequired for performance reasons, especially within thecontext of a virtual enterprise.
Event Notification Service: to ensure that thepublish/subscribe paradigm promoted by the OMG satisfymanufacturing requirements.
9/28/2010Manufacturing Enterprise System
22
8/8/2019 Manufacturing Enterprise System
23/26
QUALIT OF SERVICE (QOS)
In order to support the needs of manufacturing, objectservices, object facilities and application objects need tobe measured and selected according to at least thefollowing qualities of service:
Performance: number of transactions or messages per
second, ability to respond in real time(e.g.,predictability of the response time).
Reliability: mean time to failure, mean time to repair,etc.
Scalability: Number of systems, objects, instances, thatcan be manipulated by the system before the
performance specifications of the system stop beingmet.
Resource consumption: amount of memory and diskspace required to support a service of facility.
9/28/2010Manufacturing Enterprise System
23
8/8/2019 Manufacturing Enterprise System
24/26
THE APPLICATION FRAMEWORK
a collection of reusable, collaborating object abstractions (e.g.,machine, operator), services (e.g., move a machine through its lifecycle) and protocols (e.g., transfer of material between twomachines).
Relationships (associative, hierarchical) are defined between these
abstractions to provide an overall design.
provides the software infrastructure that permits the composition ofexisting framework classes to customize or enhance the domainknowledge.
provides a common environment for the integration of applications
and the sharing of information in a given problem domain.
Framework protocols are platform independent, and should belanguage independent to the extent possible, thus promoting theirinteroperability and portability across distributed, heterogeneoussystems.
9/28/2010Manufacturing Enterprise System
24
8/8/2019 Manufacturing Enterprise System
25/26
PROBLEMS
The Application Framework may impose requirements on the Analysis and
Design Task Force to provide design methods that are sufficiently robust to
capture its significant characteristics.
The sharing of application architecture concepts across multiple subject
areas would probably impose the same kind of sharing on the applicationframework.
There is not necessarily a one-to-one correspondence between the
Manufacturing Enterprise Model concepts and application subject areas,
and the ultimate partitioning of the Application Framework.
The huge investment required for a supplier to recast an existing (legacy)
manufacturing application into the form defined by an Application
Framework introduces a significant barrier to commercial availability.
9/28/2010Manufacturing Enterprise System
25
8/8/2019 Manufacturing Enterprise System
26/26