Manufacturing execution
Chapter 1
1.0
Introduction
Ever since, manufacturing execution was used and implemented by ancient
civilization. They used this process to give a good service and to gain more profit to their
customers. So they develop a manufacturing execution system to monitor the production
if it meets the following standards.
Nowadays, companies are using quality management systems to maintain the
quality of their product, Quality Management system have a variety of functions that
have purpose in businesses. Quality management system is assuring that the product meet
the standards and consistency of their products. A company must have a good quality
management system in order to supervise the company’s success. Quality management is
focused not only on product/service quality but also the means to achieve it. Quality
management therefore uses quality assurance and control of processes as well as products
to achieve more consistent quality. Quality planning, quality control quality assurance
and quality improvement are the main components of quality management system.
1.1
Project Overview
The manufacturing execution is the most important thing in enterprise operation
system. It necessarily to make products that meets the standard of the industry. Without
those standards the whole enterprise operation will be useless.
To implement those processes, it necessary to make a plan on how the quality
process should be implemented and think what is the assurance of the customer if they
buy their product.
The overview of this project study is to implement good production of the
enterprise and to improve the quality management of the enterprise. By improving the
manufacturing execution of a company, it will gain more productivity and the consumers
trust the products they buy. To achieve those it is necessary to make a good planning and
consider what customer wants to buy.
Project Study
Page 1
Manufacturing execution
1.2 Problem domain
1.2.1
Statement of the Problem







1.3
Quality departments who fail to take advantage of a harmonized
quality management system to address these requirements.
Uncover ineffective controls.
Disorganized documentation.
Lack of comprehensive management ultimately hurts product quality.
Assign actions needed for containment, correction, and prevention of
problem recurrence
corrective action methods to record, track, follow-up on, resolve and
report problems and concerns within the company, caused by
suppliers, or raised by customers
Manage supplier quality by tracking supplier status, certification level,
problem history, quality performance and other metrics

Prevent purchase orders from being issued to suppliers with an
unknown or unacceptable status

Integrated with Supplier List, Problem Control, Purchasing and
Shipping and Receiving
Objectives of the project
Ensure that the requirements of all applicable Customers Project
specifications are satisfied, particularly with regard to
quality assurance (QA) and quality control (QC) as it pertains to design,
procurement, construction and testing




Project Study
Effectively manage quality throughout all phases of project
execution, including those activities conducted by
Subcontractor, Vendor/Sub vendors, Suppliers, Fabricators and
Installation Contractor.
Provide assurance that the completed work associated with the
facilities will conform to the project specifications, design
codes, regulatory requirements, and sound engineering and
construction practices.
Describe the process for developing a project scope statement
using the project charter and preliminary scope statement.
Discuss the scope definition process and work involved in
constructing a work breakdown structure using the analogy,
top-down, bottom-up, and mind-mapping approaches.
Page 2
Manufacturing execution

1.4
. Understand the elements that make good project scope
management important.
Significance & Scope of the Project

A deliverable is a product produced as part of a project, such as hardware
or software, planning documents, or meeting minutes.

Scope refers to the work involved in creating the products of the project
and the processes used to create them.

Project scope management includes the processes involved in defining and
controlling what is or is not included in a project.
1.5
Documentation of Existence & Seriousness of the Problem.
1.5.1 Documentation of Current System
According to our resources and some online researching, many companies
specifically manufacturing are still using manual system. They not using the literal
manual process but most of the transactions and other quality procedure of their
process are still manual. Having well developed process in a company might be a big
help.
1.5.2 Problem identified with the existing systems
Project Study

Spending a lot of time in checking the information.

Monitoring of machineries and manpower

Monitoring of quality of the products

Quality control and assurance of the product
Page 3
Manufacturing execution
1.5.3 Process models of existing systems contributing to the
problem
Inspector write down the test results in
a paper and pass it to admin.
Process Model of
Manual System
Admin will record it to the log book
and analyze it
Admin create a complaints
regarding to inspector reports
Admin pass the created complaints
to production planning section
Figure 1- Process model of existing system
Project Study
Page 4
Manufacturing execution
1.5.4 Data models of these existing systems
Data Models for Manual
Process
Admin
-First Name
-Last Name
-Classification
*Promote ()
*Demote ()
*Terminated ()
*Add Employee ()
Employee
-Last Name
-First name
-Middle Name
-Age
-Birthday
-Gender
*Add ()
Figure 2 - Data model
Project Study
Page 5
Manufacturing execution
Data Models for Existing System
product
inspector
-First Name
-Last Name
-Password
-Classification
-Name
-description
-design
-status
*Promote ()
*Demote ()
*Terminated ()
*Add Employee ()
*Add ()
*Edit ()
*Delete ()
*Update ()
*Print ()
Figure 3 – data model of existing system
Project Study
Page 6
Manufacturing execution
1.5.5 Data (or any form of statistics) that may be relevant
to prove existence & seriousness of the identified
problem
As the researcher, the company we went through becomes so very strict in
giving some related data that relevant to the existence problem of their company’s
system. But depending on the above information they provide some problems
would be identified. The management doesn’t allow us to have copy of those
documents we need for their company’s privacy. And as a professional researcher
and students we don’t force the company to have those documents as a respect to
their company.
1.6
Review of Existing Alternatives
By the experience of the users in using manual system, they can observe
how hard, effort and time consuming to work with that kind of process. As our
recommendations to the company, it is applicable to use computerized system.
With this, they can sure the consistency of reports and documents of the system.
However, they use an ordinary system that accommodates the clients. By
developing the existing system the company will have an easiest process when
filtering and giving reports.
Project Study
Page 7
Manufacturing execution
1.6.1 Assess the best available resources for addressing the
problem
As a student and a researcher the best resources that everyone could have
is the computer. It cannot be very specific at times but it can produce different
answers to such questions. Computer is the resources for hardware and
technology but human resources could also be a resource for solving some
problems.
1.6.2 Describe how your purpose to take advantage of
existing & current best practice in your project
Our proposed system is to developed Manufacturing execution system.
For our programming language, our lead programmer used Java Eclipse to have a
design that suits to our proposed system. In doing some testing and evaluating the
proposed project, the user can have the opportunity to know if our proposal is fit
to the satisfaction of their company need.
Project Study
Page 8
Manufacturing execution
Chapter 2 – Review of related literature and study
2.0 Introduction
This literature review and study discusses the Manufacturing execution system.
With this literature and study, we should get a better understanding on how
Manufacturing execution should be implemented on enterprise operation.
It should be important to an enterprise to have a manufacturing execution to
monitor the quality of their production and to meet the standards of the industry.
By studying or reading some books about those enterprise processes you should
gain a better understanding on how the quality management should be implemented
before the product should be delivered to their customers.
2.1 Related literature
2.1.1 Foreign literature
MANILA, PHILIPPINES and ARMONK, NY - 29 Mar 2007: IBM
(NYSE: IBM) today announced that Universal Robina Corporation (URC), one of the
largest branded food product companies in the Philippines with a growing presence in
other Asian markets, is streamlining business processes to help boost productivity and
information accessibility with a Service Oriented Architecture (SOA) powered by IBM
software.
A household name in the Philippines manufacturing a diverse mix of food products with
distribution to more than 120,000 accounts, URC's first strategic SOA project is to
streamline and integrate its supply chain to enable increased resource efficiencies and
enhanced collaboration with, and responsiveness to, its distributors and key customers.
With an SOA, URC is able, for instance, to more rapidly fulfill order commitments to its
customers. Prior to adopting SOA, orders were received via email or file transfers with
information being keyed into, and extracted from, different systems and applications
through the various order fulfillment stages such as order consolidation, production
planning, supplier sourcing and distribution.
Now with the adoption of SOA and open standards, the supply chain is streamlined and
accelerated through an integration framework, including SAP forecasting system,
manufacturing execution system, and human workflow, enabling automation of
exchanging essential information resulting in greater efficiencies including improved
order fulfillment rate as well as significant reduction in production order entry errors and
duplicate orders.
Project Study
Page 9
Manufacturing execution
Further, before SOA, approximately 30 percent of URC's IT man hours were spent
writing integration interface code. Now, with IBM SOA, which enables conversion of
SAP and legacy IT assets -- without modification -- into reusable services, URC expects
a significant reduction in both the costs and hours spent in the development, support and
maintenance of interfaces allowing more productive use of their IT resources.
"In today's highly competitive environment, you need to look for solutions that help you
to be agile and responsive to both changing market dynamics and to your customers -especially when a key growth objective is to expand into new markets," said Ester
Asinas, Corporate IT Director, Universal Robina Corporation. "This is precisely what we
have achieved with SOA and by having IBM as our technology partner."
To achieve this, URC tapped the expertise of IBM Advanced SOA Technologies Team
and business partner, Teligent Systems, to build an SOA environment using IBM
WebSphere software which enabled the company to preserve their existing IT
investments while more closely aligning technology with the needs of their business.
"IBM is deeply committed to helping businesses in the Philippines realize and take
advantage of the benefits of SOA," said James Velasquez, Country General Manager,
IBM Philippines. "IBM has helped thousands of companies deploy SOA solutions, giving
them greater flexibility and responsiveness to quickly meet new market opportunities and
challenges. IBM's team of dedicated experts is all geared up to help drive business
growth and productivity for URC."
2.1.2 Local literature
Manufacturing operations management gives a detailed overview of all the
activities that support manufacturing in the area of production, inventory, maintenance
and quality. As well MES as Lean activities can be classified within this framework.
3.1.1 MES activities Saenz et al. (2009) describe the traditional internal structure of most
MES solutions. They are designed on a modular basis, so each system can be configured
and integrated as desired. As a consequence, the complexity of analyzing the
manufacturing operations support needed for each manufacturing case is high and far
from trivial. The contribution of the ISA 95 standard is only discussed briefly by Saenz et
al. (2009) as the formalization of the exchange around the manufacturing system to other
areas of the company. It’s use is presented as the design of information flows between
shop floor level applications and those of a higher level. In addition ISA 95 is stated to
deliver a consistent terminology. Although these are in fact the main contributions, it’s
practical benefits reach a lot further and deserve some extra attention. ISA 95 part 1, 2 &
3 (ISA 2000) provide a number object models and terminology that serves as a common
model of integration, a standard terminology to define system requirements and
Project Study
Page 10
Manufacturing execution
integration between different software systems. By mapping the existing manufacturing
systems and tools on the models (AS-IS situation), filling the blanks with new systems,
checking the integration needs and considering the different information flows, ISA 95
can be the roadmap for a well structured analysis. Based on the ISA 95 models, a
blueprint of the TO-BE situation can be constructed. Scholten (2007) describes the
procedure to construct a User Requirements Specification (URS) document. This
document is used by consultants to clearly specify the requirements of the manufacturing
company within the manufacturing operations domain. The result can be used in the
selection procedure of the MES solution that best fits all needs.
2.2 Related studies
2.2.1 Foreign studies
AMR Research, a Boston-based industry and market analysis firm, defines a
Manufacturing Executing System (MES) as “a functional layer of information technology
that links business planning and shop floor control systems to deliver to manufacturing an
achievable and realistic production plan.” To help understand AMR’s explanation the
term shop floor control system should be defined as: “A system for using data from the
shop floor to maintain and communicate status information on shop orders
(manufacturing orders) and on work centers. Shop floor control can use order control or
flow control to monitor material movement through the facility. The major sub-functions
of shop floor control are:
1. Assigning priority of each shop order
2. Maintaining work-in-process quantity information
3. Conveying shop order status information to the office
4. Providing actual output data for capacity control purposes
5. Providing quantity by location by shop order for work-in-process inventory and
accounting purposes
Project Study
Page 11
Manufacturing execution
6. Providing measurement of efficiency, utilization, and productivity of the workforce
and machines.
The major sub-functions for flow control are based primarily on production rates
and feeding work into production to meet these planned rates, then monitoring and
controlling production.” (APICS Dictionary, 12th Edition) It may appear that an MES is
a relatively new class of system, although it is has been around for 15+ years awareness
of MES continues to grow as the rate of acceptance increases. The adoption of MES has
expanded as companies realize MES is used to evaluate and manage production activities
using the latest technologies to support traceability, monitoring, and management of shop
floor activities.
It can be confusing to obtain an exact description of MES in that many
designations are perceived to fill the Manufacturing Execution space, such as: Shop floor
execution systems, supply chain execution system, manufacturing operations
management, assembly management systems, plant floor visibility solution, enterprise
production system, and data collection solutions. However, MES is a distinct functional
group, not to be confused with systems that only address one or two aspects of a
complete MES system. Central to an MES is the “execution” aspect, as in Manufacturing
Execution System versus “planning”, as in Enterprise Planning. As in all ventures
planning has its significance, however planning without execution is ineffectual. An
MES is not one single simple application. An effective MES consists of an integrated set
of production activity and support applications that have been developed using correctly
matched technologies. With so many components creating an MES, implementing an
MES in a variety of degrees becomes possible; from uncomplicated WIP tracking to a
solution integrated throughout a plant floor collecting data, monitoring, and managing
resources while co-existing with other systems such as Enterprise Resource Planning
(ERP), Product Lifecycle Management (PLM), and Supervisory Control And Data
Acquisition (SCADA). The real key to understanding an MES is to be aware that it
simply automates the information loop between the shop floor and enterprise information
systems. An MES makes up-to-the minute shop floor information available
companywide, which allows a swift response to conditions and requirements. Bottom
line, MES is the ideal application to collect data needed by any other system in the
Project Study
Page 12
Manufacturing execution
organization, providing a real-time database for traceability while providing information
for continuous improvement in operations.
Today’s intense economic conditions favor manufacturers who can do more with
less and do it faster, better and more cost effectively. Manufacturers are experiencing
rising material and overhead costs and are looking for ways to implement lean processes
and better visibility of the shop floor, including quicker turnarounds which keep
inventory low. To assist manufacturers in accomplishing this, an MES offers a
foundation of real-time data and details for continuous improvement and decision
support. Current economics continue to influence manufacturing toward shorter and
smaller production runs with more stress on quality and complex regulatory
requirements. An MES offers access to real-time shop floor information to allow quick
and timely responses to any challenge that could negatively influence efficiency, quality
and regulatory compliance. There is one certainty, that good data is required to get good
information. An MES system supplies that “good data” by offering uninterrupted
visibility into production operations, gaining a complete overall view of the shop floor.
Unlike an ERP that measures transactions in terms of days, weeks and months, an MES
measures movement on the shop floor in terms of hours, minutes and seconds. With the
robust approach an MES offers, manufacturers are able to capture and manage data to
make mission critical decisions and react in a timely manner throughout an organization.
MES compliments the capabilities of an ERP, helping to leverage an
organization’s ERP investment. Both systems collectively supply information, which
creates more accurate schedules resulting in realistic production plans, shorter cycle
times, less WIP and lower inventory. MES also provides the shop floor control and
visibility needed to effectively deal with multifaceted traceability requirements. Using
real-time “good data” from automated transactions collected from the shop floor, MES
links supplier information, lot numbers, serial numbers, time/date or other records to the
appropriate finished goods, back to the work order or demand signal. MES not only
provides production people with accurate information so they can schedule precisely, but
also offers an electronic network for performance improvement.
(Freedom MES 12th edition)
Project Study
Page 13
Manufacturing execution
2.2.2 Local studies
Universal Robina Corporation (URC) traced its beginnings all the way back to
1954. John Gokongwei, Jr. was doing very well then as a trader/importer. He had learned
the trade when his father died before the war, and had worked hard through the war and
postwar years to prosper. However, while he thrived, he took a long hard look at his
company, and correctly predicted that trading would remain a low-margin business.
On the other hand, a successful manufacturer controlling its own production and
distribution would command more profitable margins. Mr. John decided to construct a
corn milling plant to produce glucose and cornstarch, Universal Corn Products (UCP),
the first building block of the company that would become URC.
For a time, business was good. However, Mr. John was still looking ahead, working with
an eye towards the future. While the business was doing very well, it was producing
essentially a commodity, which a customer could easily access elsewhere. To stay ahead
in the game, Mr. John had to diversify by producing and marketing his own branded
consumer foods, similar to the multinational companies in the Philippines like Nestle and
Procter & Gamble. In a sense, he wanted to put up the first ‘local’ MNC, borne out of
their best practices.
Thus, in 1961, Consolidated Food Corporation was born. Their first ‘home run’ product
was Blend 45, the first locally-manufactured coffee blend, dubbed as the “Pinoy coffee”.
This became the largest-selling coffee brand in the market, even beating market leaders
Café Puro and Nescafe. After coffee came chocolates. Nips, a panned chocolate similar to
M&Ms, was a staple of Filipino childhood.
In 1963, Robina Farms started operations, beginning with poultry products. This was also
the beginning of the vertical integration of the Gokongwei businesses, as the farms would
be able to purchase feeds from UCP in the future. Later that decade, Robichem
Laboratories would be put up, to cater to the veterinary needs of the farms businesses.
Robina Farms expanded as it entered the hogs business in the latter part of the 70s.
1966 saw the establishment of Universal Robina Corporation, which pioneered the savory
snacks industry in the Philippines through its Chiz Curls, Chippy, and Potato Chips,
under the “Jack ‘n Jill” brand. Other snack products would follow over the years, as the
company successfully introduced market leaders like Jack 'n Jill Pretzels (pretzels),
Piattos (fabricated potato chips), and Maxx (hard candy).
The coming decades saw more acquisitions and expansion. In the early 1970s, the
Gokongwei family entered the commodities business through the formation of
Continental Milling Corporation, for flour milling and production. The late 1980s
brought the acquisition of three sugar mills and refineries, under URC Sugar. These two
businesses provided stable cash flows, and allowed for further vertical integration in the
supply chain, to help URC weather any volatility in the cyclical commodities markets. In
line with this strategy, the late 1990s saw the entry of URC into the plastics business,
through URC Packaging.
San Miguel To enforce this dedication to quality a powerful tool was needed for
continuous improvement of processes and products, and one that would support an
Project Study
Page 14
Manufacturing execution
integra-ted quality management approach across all plants with a structured way of handling product and process data.Mahou–San Miguel decided to imple-ment a LIMS
(laboratory information management system) that would inte-grate the management of
the existing laboratories in each of the company’s production units, and could replace the
different small home-grown systems for lab management.A thorough screening of the
LIMS mar-ket turned out SIMATIC IT Unilab, which is Siemens’ LIMS, and forms part
of the Siemens MES (Manufacturing Execution Systems) portfolio. Decisive factors in
the selection were flexibility, capabilities and performance.SIMATIC IT Unilab was
designed to fill the gap between lab and production envi-ronments. It manages lab
workflows and optimizes collection, analysis and repor-ting of quality data from lab
instruments as well as process data captured from the production lines. The main LIMS
functionality in use at Mahou-San Miguel is: • Management of all quality data (raw
material, finished products, environ-mental samples, etc..)• Full and flexible support for
definition and execution of complex test plans• Direct connections to lab instruments and
equipment • Immediate feedback on quality excep-tions• Support of quality standards
such as GLP, GAMP, ISO, FDA, HACCP• Compliance support to 21 CFR Part 11The
labs at Mahou-San Miguel basically carry out chemical and physicochemical analyses.
Next to the daily environmental analyses the labs take samples at various stages of the
production process. In their requirement specification Mahou-San Miguel defined an
information management system to efficiently manage all quality data and activities in
the labs. The tool had to support compliance with the EU food traceability law that
applies since January 2005. This law stipulates that a company must be able to trace back
any substance involved in the production or distribution process of food or feed products.
2.3 Synthesis and significance of the studies
Through research and general understanding we learn different techniques,
methods, and components of the given system. Discussion in this paper has focus on
summering, comparing, and obtaining an excellent understanding of the system. We got
new ideas and learning to develop a system. With this kind of documentation we trained
ourselves to be more productive and patient in every activity that we made.Researching
something is like knowing something better that probably can help many people in the
Project Study
Page 15
Manufacturing execution
near future. Having a review related literature and review of related studies help each
person especially the students to gather different ideas in creating system.
3.0 Software Requirements Specification
3.1 Introduction
3.1.1.1 Goals and objectives
The purpose of this document is to describe requirements for the said company
software that will serve as a foundation for the final product. It is important that an
agreement of these requirements be reached so that everyone expectations will be met.
Although some of these diagrams seem not to convey similar information they typically
do.
3.1.1.2 Statement of scope
This section contains a general description of the software functionality followed
by the detailed requirements that will be traced throughout the project
User requirements for production execution and quality management
Req. no.
Admin accessibility
R1
Priority
Reference
Description
high
Admin
R2
high
Admin
R3
high
Admin
R4
high
Admin
R5
high
Admin
R6
high
Admin
The
admin
can
manage
different
transaction
Can manage the
quality of the product
Monitor
the
production of the
products
Accessing the files
inside the system
Viewing
reports
inside the system
Deleting
any
information on the
system
High
Inspector
Quality Control
R7
Project Study
Monitor
the
production inside the
plant
Page 16
Manufacturing execution
R8
High
Inspector
R9
High
Inspector
R10
High
Inspector
R11
High
Inspector
Employee
accessibility
R12
High
Employee
R13
High
Employee
R14
Medium
Employee
R15
Low
Employee
R16
High
Operator
R17
High
Operator
R18
High
Operator
Tests the product
quality
Verified the product
before executing
Test materials before
Delivering
to
production plant
Verified
materials
before executing
Record
materials
delivered
Check the quantity of
materials
Delivered reports to
admin
Delivered materials to
plant
Create a product with
quality
Checks the machine
if there`s any problem
Execute
products
after packaging
3.1.1.3 Software context
Enterprise operation system is the one the biggest system running. Many companies need
an expert for their operation especially to Manufacturing execution. The success of the
enterprise relay to the manufacturing execution system of the company
3.1.1.4 Major constraints
The production execution and quality management system will use JAVA
programming language and mySQL as a database to integrate the whole enterprise
operation system (EOS) and android application for the production tracking inside the
shop floor.
Project Study
Page 17
Manufacturing execution
3.1.2 Usage Scenario
3.1.2.1 User profiles
Administrator
Administrator has an access to all
transaction happens to entire operation of
production. The administrator also does the
part of employee and the inspector to assure the
quality of production.
Inspector
Inspector should check and verify the materials
needed, monitor every production, also check and
verify the finish product to assure the good quality
and check the packaging if it is ready for shipping.
Employee
Receive plan from administrator. Employee needs
to deliver right material for production and also
employee starts the production process. Employee
need to create a report and pass it to admin
3.1.2.2 Use-Case
1. Check production schedule
2. Execute plan
3. Receive reports
4. View reports
5. Production complaints
6. Receive plan
7. Deliver raw material
8. Start production process
9. Return to warehouse
10. Monitor production
11. Inspect materials
12. Test products
Project Study
Page 18
Manufacturing execution
13. Verify products
14. Record test result
15. Inspect package
16. Generate reports
3.1.2.2.1 Use-Case Diagram
This use-case diagram shown in this figure shows the production
execution and how the quality management should be implemented during the
production process and before the production happens.
Figure 1 – Use case diagram
Project Study
Page 19
Manufacturing execution
3.1.2.2.2 Use-Case Descriptions
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Check production schedule and plan
Admin
Check the schedule
The admin needs to verify the scheduled product
Production schedule and plan pop-out to system
1. Admin view the production schedule
2. Admin check the information indicated in production
schedule
3. Admin assures that the production plan has a detailed
information of product
4. Admin checks the quantity, design, materials needed and
the given time to produce the product.
Exceptions:
If production schedule and plan has a missing data it should go
back to production planning
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Execute plan
Admin
To execute the plan
Assuring the plan is ready to execute
The plan is analyzed and approved
1. Admin assure that the plan is free of error
2. The plan is ready for production
3. Admin execute the plan immediately
Exceptions:
Executing was cancelled by admin
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Receive reports
Admin
Receiving a reports from inspector and employee
Generated reports from employee and inspector
Employee and inspector generate a report
1. Admin waits for generated reports
2. System will prompt the new reports has been entered
3. Admin choose to system report files
Exceptions:
Project Study
Page 20
Manufacturing execution
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Monitor production
Admin
Check the production
Monitoring of machinery and manpower
Monitor the production works
1. Admin must go to monitor production
2. Admin must watch the production works through CCTV
3. Admin monitor the machinery section
4. Admin assures that the machinery are working properly
5. If machine not working properly, Admin give an order to
repair it immediately.
6. Admin check the manpower works
Exceptions:
Totally damage machineries will be dump and replace a new one
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
View reports
Admin
To view a report
Information required for the report has previously been entered
Admin decides to view a summary of inspector and employee
reports
1. Admin logs onto the system
2. Admin selects the view report
3. Admin selects the name of the report from the report name
4. System select the reports from the database
5. The report display on the screen
6. Admin choose to print or close the report
7. The report is close or printed
Scenario
Exceptions:
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Project Study
Deliver raw materials
Employee
To deliver a qualified materials for production
The materials should be inspected and qualified for production
Employee go to stock room
1. Employee get the materials needed
2. Employee record the material information
3. Employee will record the quantity, specification, and the
time released of material.
Page 21
Manufacturing execution
4. Employee delivered the materials to shop floor
Exceptions:
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Test product
Inspector
To assure the quality control of a product
It should be pass to product testing
Inspector wait for the product
1. Inspector conduct tests to product
2. Inspector apply the slip resistance test
3. Apply the Surface abrasion test
4. Inspector grade the tile
5. Apply the water absorption test
6. Product will soak in a boiling water
7. Apply the size and flatness test
8. Calibrate the product
9. Check the design and the size
Exceptions:
If the product didn`t passed the test, the product will be rejected
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Receive plan
Employee
Receive a plan
Plan of production and schedule
Admin execute the plan and schedule of production
1. Employee check the process
2. Employee analyze the requirements of production
3. Employee check the quantity to be produced
4. Employee check the time needed to produced products
5. Employee pass the quality management of the product
6. Inspector receive the quality management plan of
production
7. Employee start production on time
Exceptions:
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Project Study
Generate reports
Inspector
Create different reports
o Reports of test result
o Reports of materials rejected
Page 22
Manufacturing execution
o Production complaints
Trigger
Scenario
Inspector finished the verifying materials and product and
recording the test result
1. Inspector encode different reports
2. Inspector create reports for the test result
3. Encode the record of the test result
4. Inspector create a new report for materials verified and
product verified
5. Inspector create a report for production error
6. Inspector create a complaints for production
7. Inspector submit the reports
Exceptions:
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Verify materials
Inspector
Inspect the material
Material has a quality required for production
Materials has been delivered
1. Inspector check the specification of material
2. Inspector check the detail of material
3. Inspector check the quantity of material needed for
production
4. Material must match to production requirements
5. Material has been approved by inspector
Exceptions:
If material was rejected, materials returned to warehouse
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Record test result
Inspector
Record the result of product testing
Record product if passed or failed to tests
Inspector record the result
1. Inspector record if product passed to slip resistance test
2. Inspector record if product passed to surface abrasion
3. Inspector record if product passed to water absorption test
4. Inspector record if product passed to size and flatness test
5. Inspector record the product passed
6. Inspector record the product rejected
Exceptions:
If the record doesn`t match, recording test result must rechecked
Project Study
Page 23
Manufacturing execution
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Production complaints
Admin
Return the unsuccessful plan and schedule to the production
planning
Complaints must be surely check and has a proof
Admin waits the report created by inspector
1. Admin read the report regarding to complaints
2. Admin will base on the report created by inspector
3. Admin will create a complaint to production
4. Admin list down the problems regarding to plan and
schedule
5. Admin passed the complaints to production planning
Exceptions:
If the production is successful admin will not create a complaints
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Returning to warehouse
Employee
Stock the rejected products in warehouse
Employee assured that the rejected products and material was
recorded before returning to warehouse
Employee wait the rejected products to be recorded
1. Employee collects the rejected products
2. Employee collects the rejected materials
3. Employee delivered the rejected products and materials to
warehouse
4. Employee stock the rejected products and material to their
designated area
Trigger
Scenario
Exceptions:
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Product verifying
Inspector
Review the test happens to product
Inspector must check the tests happens to product
Wait for the product
1. Check the test requirements of the product
2. Inspector review the tests
3. Check the tests happens to product
4. Verify the product
5. Approve the product passed to the test
Exceptions:
If product didn`t pass the verification it must be rejected
Project Study
Page 24
Manufacturing execution
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Start production process
Employee
Create the product according to plan
Employee operate all the machinery needed in production
Raw materials are delivered
1. Employee ready the materials
2. Start the machine
3. Machine mix the materials
4. Machine store the mix materials into different storage
5. Machine apply design to a product
6. Machine reject products with defects
7. Machine package the finished products
Exceptions:
If machinery is totally damage, the production will stop
immediately
Use-case:
Primary Actor:
Goal In Context:
Preconditions
Trigger
Scenario
Inspect package
Inspector
Inspect the packaging of the products
Package must have a correct label and no defects
The product is passed and ready to be packed
1. Product passed to machine
2. Machine packed the product
3. Inspector inspect the packaged
4. Inspector checked the label of the package
5. Inspector checked if the package is broken or damaged
6. Inspector approve the package
Exceptions:
If the box has a wrong label or damaged, product must go to
repackaging
3.1.2.3 Special usage considerations

Project Study
Unsaved file will be automatically saved when system shutdown
unexpectedly.
Page 25
Manufacturing execution
3.1.2.4 Activity Diagrams
This figure shows how the admin should login to system. It shows the
activity of login
Figure 2 - Activity diagram of login
Figure 3 shows the activity diagram of production schedule and plan. It
shows the step by step activity.
Project Study
Page 26
Manufacturing execution
Figure 3 – Activity diagram of production schedule and plan
Figure 4 show the activity diagram of monitor production. You can see
how the admin can monitor the production.
Project Study
Page 27
Manufacturing execution
Figure 4 – Activity diagram of monitor production
In figure 5 you can see the view reports. It is how the admin can view the
reports using the system
Project Study
Page 28
Manufacturing execution
Figure 5 – Activity diagram of view reports
In figure 6 it shows how the materials needed in production picked up and
delivered to the shop floor
Project Study
Page 29
Manufacturing execution
Figure 6 – Activity diagram of Admin
Figure 7 is the test product activity diagram. It shows the activity of
testing the product to assure the quality
Project Study
Page 30
Manufacturing execution
Figure 7 – Activity diagram of Inspector
Project Study
Page 31
Manufacturing execution
Figure 8 shows the generated reports. It show how generated reports
can be done.
Figure 8 – Activity diagram of generated reports
Project Study
Page 32
Manufacturing execution
In this figure, figure 9 shows the activity on how the raw materials
delivered to production plant
Figure 9 – Activity diagram of delivered raw material
Project Study
Page 33
Manufacturing execution
Figure 10 shows the activity happens when recording the test results. Only
the inspector can perform this operation.
Figure 10 – Activity diagram of record test result
Project Study
Page 34
Manufacturing execution
Figure 11 the last activity diagram, It shows the activity of how the
package inspect by inspector.
Figure 11 – Activity diagram of inspect package
Project Study
Page 35
Manufacturing execution
3.1.3 Data model and descriptions
3.1.3.1 Data objects
Material data object
Material ID
A unique ID number for specific material
Material Name
Name of specific material
Material Description
Description of material
Material Verification
A material should undergo to different tests
before it will use for production.
Test result data object
Slip resistance test
Product must passed
Surface abrasion test
Product must passed
Water absorption test
Product must passed
Size and flatness test
Product must passed
Product passed
the number of product passed to test
Products rejected
the number of product rejected
Production schedule and plan data object
Product ID
unique identifier of product
Product name
Name of product
Product description
description of product
Product design
Design of product
Time to create
start of product to be created
Time to finished
time of the product to be finished
Quantity
number of product to be created
Inspector data object
Project Study
Inspector ID
A unique number for inspector
Inspector Name
Name of inspector assigned
Page 36
Manufacturing execution
Last name
Last name of inspector
Assigned department
the assigned department of inspector
Generate reports data object
Report name
type of report
Report description
describe the reports
Production complaints
complaints to production if successful or not
Production test result
creating a report regarding to records of test
result
3.1.3.2 Relationships
Material should pass through inspection before it will use for production.
To assure its quality the inspector has to verify it.
Test results are the check list of test happens to a product. Inspector check
the number of product passed in production by checking the tests.
Inspector counts the number of product passed and rejected. After
recording the test result, Inspector generates a report of what happens to
production. Inspector must create a complaint and encode the record of
test results.
An inspector verifies and tests the products. If the production is
unsuccessful, Inspector should create a complaint. Inspector record the
number of product passed and the number of products rejected.
Employee receives a plan for production. An employee analyzes the data
and gathers the materials needed for production and deliver it. Employees
also start the production and pass the quality management plan to
inspector.
Production schedule and plan is the guide of the employee to create a
product. Production schedule was executed by admin and pass it to
employee to begin the production.
Project Study
Page 37
Manufacturing execution
3.1.3.3 Complete data model
Figure 12 – Complete data model
Project Study
Page 38
Manufacturing execution
3.1.4 Functional Model Description
3.1.4.1 Class Diagrams
Figure 13 – Class diagrams
Project Study
Page 39
Manufacturing execution
3.1.4.2.1 External machine interfaces
System counts product creates and the time of product creation
would be on time as the product requested.
3.1.4.2.2 External system interfaces
Production execution and Quality management communicates with
other sub-systems using LAN.
3.1.4.2.3 Human interfaces
System allows navigating the reports only using mouse or
keyboard. Only the admin has the permission to add, edit or delete a file inside the
system.
3.1.4.3 Reports
Inventory of Reports
Layout of Reports
Data Dictionary of Reports
3.1.5 Behavioral Model Description
3.1.5.1 Description of software behavior
3.1.5.1.1 Events
Production schedule class events
Check schedule
Choose product
Product quantity
Product specification
Execute production
Employee class events
Get the lists of material
Record material
Project Study
Page 40
Manufacturing execution
Create reports
Give the reports
Material verify class events
Check material needs
Material tests
Material verify
Material approval
Deliver materials
Inspector class events
Monitor production
Test materials
Verify materials
Test products
Verify products
Create reports
Pass reports
Product test class events
Product tests
Product verify
Product passed
Ready for packaging
Generate report class events
Encode test results
Create complaints
Encode material result
Submit reports
Project Study
Page 41
Manufacturing execution
3.1.5.1.2 States
Start production state
Material ready
Creating
Testing
Packing
Description
materials to be used is ready
machine starts the production
machine check the product
product was packed
Inspector state
Material check
Product test
Passed
Reject
Record result
Create report
Description
checking the material if qualified
product undergo to different test
the material and product passed
material and product was rejected
record the result of tests
create a report for the production
Execute plan state
Analyzing
Description
the schedule and plan was being
analyze
the schedule and plan was cancelled
the plan and schedule approve
revision of the schedule and plan
Cancelled
Approved
Revising
Employee state
Receive plan
Follow plan
Deliver material
Start production
Admin state
Execute plan
Monitor production
Receive reports
Complaints
Project Study
Description
new plan has arrive
following the plan
gather the materials needed and
deliver
start the production process
Description
execute the plan and schedule
check the works of employee and
machinery
receive generated reports
submit a complaints for production
Page 42
Manufacturing execution
3.1.5.2 State Chart Diagram
Figure 14 – Production over all
State chart diagram
Project Study
Page 43
Manufacturing execution
Figure 15 – Employee
State chart diagram
Project Study
Page 44
Manufacturing execution
Figure 16 – Admin
State chart diagram
Project Study
Page 45
Manufacturing execution
Figure 17 – Inspector
State chart diagram
Project Study
Page 46
Manufacturing execution
3.1.6 Restrictions, Limitations, and Constraints
 System should integrate to different sub-system to complete the Enterprise





Operation System.
Program codes were written in Java.
Android mobile device
Internet connection
Database management uses mySQL as database.
System run on windows XP operating system or up x64 and x86 bit
3.1.7 Validation Criteria
Software validation will ensure that the system responds according to the user’s
expectation; therefore it is important that the end users be involved in some phases of the
test procedure.
3.1.7.1 Class of tests

Unit testing will be conducted on all of software subsystems
including
1. Check production schedule
2. Monitor production
3. Material verifying
4. Product testing
5. Verifying
6. Start production process
7. Execution of product
3.1.7.2 Expected software response

The software should not be deleted the application logs, it will be
generated for reports.

System shows the state of production

The software will estimate the time of the production to be finished
3.1.7.3 Performance bounds

Project Study
The system shall support file recovering, file recover will be use
when the save data was deleted.
Page 47