Process flow
A readable flowchart showing $START, each operation, every outcome or exception, loops, holds, scrap paths, rework, and $DONE.
Route Builder tabs
Proposed entries for the FLOW, PROCESSES, OPERATIONS, CONDITIONS, and NEXT_STEP tabs in the CELLS Route Builder “Next Step” Table.
Other CELLS setup
CellsAdmin assembly and work-order records, ODBC connection, users, stations, task data, documents, defects, permissions, and reporting requirements.
Test plan
Normal-path, failure-path, missing-data, authorization, duplicate, rework, history, reporting, backup, and restoration tests.
Complete AI request template
The Copy button above combines this request with the process information entered in the box. Paste the result into the AI system your organization permits.
Review the current Unisoft CELLS Workflow MES documentation available at https://www.unisoft-cim.com/cells_download.htm and the linked CELLS manuals. Use those primary sources and distinguish documented CELLS functionality from recommendations, assumptions, or customization that must be confirmed.
Analyze the process information supplied below and determine how it should be implemented in CELLS Workflow MES.
Here are the links to the CELLS Workflow MES manuals and information:
https://www.unisoft-cim.com/cells_download.htm
https://www.unisoft-cim.com/cells-help_operators-guide.html
https://www.unisoft-cim.com/cells-route-builder.html
https://www.unisoft-cim.com/cells-help_system-administrator-guide.html
https://www.unisoft-cim.com/cells-help_tables.html
https://www.unisoft-cim.com/cells-knowledge-base-expanded.html
https://www.unisoft-cim.com/cells.php
https://www.unisoft-cim.com/cells_faq.htm
https://www.unisoft-cim.com/cells_doc.htm
https://www.unisoft-cim.com/admin_tables.htm
https://www.unisoft-cim.com/cells_databases.htm
https://www.unisoft-cim.com/cells-reports.htm
https://www.unisoft-cim.com/cells_requirements.htm
https://www.youtube.com/watch?v=Yi-35C9x0gc
The preferred export document created would be a compatible MS Word document displaying the fonts, images, etc. as needed.
Analyze the process flow information given and report at the top of your document if CELLS Workflow MES can do this.
Create a complete process flowchart showing how the process would work and put together a basic setup using the Unisoft CELLS Workflow MES manuals and information from the links provided.
Key is to provide the proposed CELLS Route Builder “Next Step” Table configuration. Organize the Route Builder setup separately by the FLOW, PROCESSES, OPERATIONS, CONDITIONS, and NEXT_STEP tabs. For every tab, identify the proposed IDs, descriptions, conditions, default paths, alternate paths, next operations, and reserved CELLS entries such as $START, $PASS, $DONE, or $SCRAP where appropriate. Clearly state that each of these entries is made or reviewed within the CELLS Route Builder “Next Step” Table. Please include as much as you can to show the complete process flow in the Cells Route Builder (Next Step), and also create a step-by-step procedure explaining how to set up that routing flow. Provide each of these in a neat table. Be very specific about what is entered or configured in each tab, and clearly state that each step is being completed within the CELLS Route Builder (Next Step) Table.
Provide an ordered, screen-by-screen procedure for creating the routing with READ FROM DATABASE, editing the route, reviewing every Route Builder tab, using WRITE TO DATABASE, reading the route back, and testing it. Do not invent exact menu names, field names, or database codes that are not established by the current documentation. Identify anything that must be confirmed in the installed CELLS version.
Look through all the documentation and determine whether any other applications within the CELLS Workflow MES software need to be populated with data for this process to work properly. This includes the CELLS Work Order Admin (CellsAdmin) software, setting up the ODBC (Open Database Connectivity) connection, and any other CELLS applications or items that need to be configured or populated with data. Be very specific about which application you are working in and which tab you are using, if there are tabs within that application. We do not want any confusion about exactly where data needs to be entered to make this entire process flow work properly within the CELLS Workflow MES software. So, determine everything else that must be configured outside Route Builder. Cover the Windows ODBC System DSN and database connection; Cells Work Order Admin (CellsAdmin) assembly and work-order records; USERS, STATIONS, user/operation authorization, DATA_ITEMS, DATA_ENTRY and SUB_LOCATION mappings, DEFECTS, OPERATION_DEFECTS, DOCUMENTS, ASSEMBLIES, WORKORDERS, HISTORY, WIP, reporting, backups, and any ERP, BOM, barcode, machine, or custom integration implicated by the process. For each item, name the CELLS application, table, screen, or tab in which it belongs.
Show which data items must be required at each operation. Explain how the user, station, date/time, work order, serial number or quantity, operation, outcome, scans, measurements, defects, and comments will be retained for later genealogy and reporting.
Evaluate every validation or mistake-proofing requirement. State whether it is documented standard CELLS behavior, ordinary table configuration, a custom CELLS data type, or an external/custom integration. Do not claim that CELLS automatically compares scans or performs a job-specific lookup unless the documentation or a live test proves it.
Finish with a pilot acceptance-test table covering the normal path, every alternate outcome, incomplete required data, wrong or duplicate scans, unauthorized users, overrides, rework, history retrieval, reports, database backup, and restoration. List the questions that must be answered before the configuration is put into production.
PROCESS INFORMATION PROVIDED BY THE USER:[The process information entered on this page will be inserted here.]
Sample process descriptions
These examples show the level of detail that is useful. They are intentionally short; replace them with the actual process and rules.
Example 1 Electronics assembly and test
Track each board by serial number under a work order.
Normal route: Incoming Inspection → Board Preparation → SMT Assembly → Automated Test → Final Inspection → Packing → $DONE.
At Incoming Inspection, record supplier lot, received quantity and inspection result.
At SMT Assembly, record line, program revision, solder-paste lot and operator.
Automated Test may PASS to Final Inspection or FAIL to Repair. Repair must record a defect and return the board to Automated Test.
Only qualified test operators may perform Automated Test. Display the current assembly drawing and test procedure at the appropriate operations.
Example 2 Machine shop with outside processing
Track each production lot by work order and quantity; serialize parts before Final Inspection.
Normal route: Material Issue → Saw → CNC Machine → In-Process Inspection → Outside Plating → Final Inspection → Ship → $DONE.
Capture material heat number, machine ID, CNC program revision and critical measurements.
An inspection failure goes to MRB. MRB may return the lot to CNC Machine, approve use-as-is, or send it to $SCRAP.
The outside-plating step must record supplier, purchase order, ship date, return date and plating certificate.
Example 3 Batch mixing and packaging
Track each batch by batch number and work order.
Normal route: Weigh Ingredients → Mix → Laboratory Test → Fill Containers → Label → Final Release → $DONE.
At Weigh Ingredients, scan every ingredient lot and record actual weight. Do not allow the operation to pass until every required ingredient is complete.
Laboratory Test may PASS to Fill Containers, RETEST back to Laboratory Test, or FAIL to Quality Hold.
Final Release requires an authorized quality user and must record the specification revision, expiration date and release result.