ezMES

ezMES is a streamlined Manufacturing Execution System (MES) designed for small businesses to improve manufacturing efficiency, ensure data traceability, and simplify workflow management. It provides role-based access to various functionalities like creating routes, work orders, and sales orders. With advanced tracking, custom roles, and comprehensive data collection features, ezMES ensures accurate record-keeping and smooth manufacturing operations. Built with Flask and JavaScript technologies, it offers a scalable and user-friendly solution.

Overview

Create Users with certain Roles. Based on the Roles assigned, the User can access different portions of the tool.
- There are Roles to create Routes/Operations.
- There are Roles to work on the certain Operations of the Work Orders.
- There are Roles to create Sales Orders and Work Orders.
- You can also create custom roles to do certain things, if you would like, such as a "Test" or "Final QC".
You can create Sales Orders for billing the customer and laying out the specifics of the order.
There is a Part Number handling system for individual components and complete assemblies.
- The Individual Part Numbers have a:
  - Revision
  - Description
  - Quantity (if in an Assembly)
  - Type (Part or Assembly)
There are Work Centers to keep track of where the work is happening.
There are Programs for the different projects being worked on. They are used separate who is allowed to work on which Work Orders.
There are Routes, which have Operations in a certain order that you can create.
- The Operations can be sequential and/or parallel, so you can create any process.
- The Routes are for manufacturing a certain Part Number (Assembly).
- Each Operation has:
  - Instructions for the Operation, so the person working on it knows what to do. Typically you would link documents in the instructions from a document control system.
  - Data Collections for information gathering.
  - Part Collections for grabbing the Lot No. and/or Serial No. for sub-assembly components.
  - Tool Collections for keeping track of what tools were used where and when they were used.
  - Buyoffs, so the person working on the operation can confirm that the step was completed. There are checks to make sure all of the above collections were done before allowing the user to buyoff the operation.
There are work orders which are based on the Routes, but specifically for a certain Part Number and a Serial Number range.
- You can select which Serial Numbers you want to work on.
- There are different statuses for the Work Order and Operations based on what is happening with it.
  - In Queue - This is when the Work Order or Operation are ready to be worked on.
  - Active - This is when the Work Order or Operation are being actively worked on.
  - Editing - This is when the Work Order or Operation are being edited to change them.
  - On Hold - This is when the Work Order, Operation or a certain Serial Number are on hold for whatever reason, and they can't be worked on.
  - Canceled - This is when the Work Order is canceled.
- There are Holds that can be for:
  - The entire WO
  - Individual Serial Numbers
  - Certain Operations
- There is a way that you can search Work Orders using filtering.
- You can edit the Work Order's Route.
  - You can add operations to the Work Order manually, as long as they are after any Active operations.
  - You can't edit after a Serial Number is bought off, the history must be kept intact.
- There is a comment section for the entire Work Order and each Operation so everyone can communicate.
- All of the Data Collections, Part Collections, and Tool Collections can be:
  - Edited and updated by other users.
  - Queried and looked at, with a complete history of the entries and any changes.

Functionality

Users

Production Level
- Engineer
- Quality
- Technicians
- Supervisors
- Planner
Admins
- Super Users
- User Setup
Custom Roles
User Login/Logout/Cookies & Timeout
Program Access

Work Orders

Creating WOs:
- Part Number
  - Import Info about the PN
- Router (Revision for PN)
- Quantity
- Current WO Number (generator)
  - Where to start from, when integrating into existing number patterns.
- DateTime
- Buyoff by Planner
Internals of a WO:
- Part Number
- Program
- SN(s) and/or Lot No. based on PN
  - SN(s) Selector
- Router
- Status
  - In Queue
  - Active
  - Editing
  - On Hold
  - Canceled
- Holds
  - Types of Holds:
    - SN Hold
    - WO Hold
    - Operation Hold
- Import BOMs from Parent PN
- Add custom route steps, no editing current ones though because of history.
- Comment Section
Searching WOs
WO Editing Page
- No overwriting history, if one SN passes a step, you can’t edit it.

Routers

Type of Route
- Production
- Prototype
- Rework
Part Number
Program
Individual Steps
- Work Center
- User Roles
- Instructions
- Part Collection
- Data Collection
- Tool Collection
- Time Estimates for Steps
- Buyoff
Ordering
- Linking Steps
- Series and Parallel Steps

Parts & BOMs

Parent Part Numbers and Sub-Assembly layer handling
Individual Part Number
- Sub-PNs/Assemblies (if applicable)
- Revision
- Description
- Quantity (if applicable)
- Type (Part or Assembly)

Work Centers

Name of the Work Center
Type of Work Center (Machine, Workbench, etc.)

Programs

Role Setup from User Roles
Name of the Program
Link Part Numbers to specific Program

Sales Order Creation

Sales Order Generator:
- Assign a Sales Order Number
- Assign a Customer

Software Packages Used

Python
- Flask
- Gunicorn
- Redis
- Flask-SQLAlchemy
- Flask-Security-Too
- Flask-Session
- Flask-Mail
- Flask-Talisman
- Flask-Compress
JavaScript
- jQuery
- Bootstrap 4
- Bootstrap-Table
- CKEditor
- FontAwesome