NEXTAS FMS is software that can plan and track work across a cell. It is not the cell itself. FMS means flexible manufacturing system. The app may send jobs, read machine states, and share shop data.
The hardware is a separate part of the deal. A robot, pallet store, CNC change, fixture, sensor, guard, or network part is not in the order just because it is shown on this page. Each item must be on the signed item list.
Physical context only
Watch the cell, then check the order
The video shows a physical FMS cell. Use it to see one type of shop flow. Do not use it as the item list for your order.
Ask which app tools, machines, robot, pallet store, guards, and site work are in the quote. Ask for a drawing and a signed list.
This video shows a physical FMS cell. It does not list the software or hardware in an order.
Start with proof tied to your order
The NEXTAS FMS page shows a public product offer. It is not an order. A buyer needs proof for the quoted app version and the named site.
| Proof | What it shows | What it does not show |
|---|---|---|
| Web page or catalog. | It shows the public offer and possible uses. | It does not show your tools, links, results, or hardware. |
| Quote and scope list. | They name the seller, app version, tools, fees, and item list. | They do not prove that each link works at your site. |
| Link sheet. | It says what each side sends, who owns it, and how it will be tested. | It does not prove that the test has passed. |
| FAT and SAT record. | It shows the test, app version, load, and result. | It does not cover a version or use that was not tested. |
| Shop run record. | It shows what happened in the buyer’s own process. | It does not promise the same result at another shop. |
A scope list says what is in, out, or supplied by someone else. A bill of materials, or BOM, is the item list for hardware. Both should be signed.
Ask who the legal seller is and who sets up each app tool. Record the licence and the app version. “Deployment” means where the app will run and who will host it. Also ask who owns the data, who can log in, and how the buyer can export it.
Write down the help hours, remote access rules, update plan, backup plan, and end date for support. Do not rely on the words “one platform.”
Draw a clear line around the software
Make a scope list with three choices: in the order, out of the order, or supplied by others. Add one owner and one proof item to every line. This finds gaps before they reach the shop floor.
| Area | Possible items | Buyer check |
|---|---|---|
| FMS app. | Jobs, queue rules, machine state, pallet ID, alarms, and reports. | Name each tool, version, user count, and where it will run. |
| Cell hardware. | CNCs, robot, pallet store, transfer unit, fixtures, sensors, and panels. | Count only items on the signed BOM. |
| Link work. | Gateways, robot links, data links, network work, and site setup. | Name both ends, the owner, and the test. |
| Safety. | Risk check, guards, safety control, access, and safe reset. | Keep safe motion and stops in the checked cell safety system. |
| Service. | User training, help hours, updates, backups, spares, and later changes. | State the term, limits, route, and price in the order. |
The FMS app is not a safety controller. It may ask for a task or show a state. The cell safety system must control safe motion, access, and stops. The cell builder must check this work as part of the site risk review.
Make a link sheet for each CNC
The full name is interface control document. In plain words, it is a link sheet. It says what each side sends, when it sends it, and what happens if the link fails.
Make one link sheet for each CNC. List the maker, model, control type, app version, and link that is on the machine. A brand name alone does not prove fit.
- Name: Link each message to the right machine, job, program, pallet, and part.
- Ready: State when the CNC can take a job or a pallet.
- Command: State which system may start, hold, stop, or move a job.
- Done: State what proves that a cut or move is done.
- Fault: State what is sent, who clears it, and what happens after reset.
- Lost link: State what happens when a message is late, sent twice, or lost.
A protocol is the set of rules used by both ends of a link. Pick it only after both ends are known. The link may use an agreed plant protocol, app link, data file, or database. Test the exact versions before you call them a match.
Give handling its own set of states
A robot, pallet store, guided cart, or transfer unit does not use the same states as a CNC. Write a short state path. It may read: ask, hold a slot, pick, place, check, done, or fault.
Choose one source for the true pallet or part location. Name the system that may send each move. Then write the response to a missing pallet, a bad ID, a fixture that is not ready, or a move that does not end.
Do not make the operator guess what the app last saved. Give each fault a safe stop, an owner, and a clear way to start again.
Clamp, part, and safe-position signals can help the normal work flow. They are not safety functions by default. Their use must match the ordered control plan.
Write plain rules for each data link
MES means manufacturing execution system. It tracks work on the shop floor. ERP means enterprise resource planning. It holds business data such as orders and stock.
Do not write “MES/ERP link” as one vague line. Name each system and version. Say why the link is needed and who owns it.
A data contract is a short set of rules for each field. It lists the field name, unit, format, source, and who may change it. It also says how often the field moves and what to do with a bad or lost value.
Test good data and bad data. Test a late message, a copy of the same message, and a broken link. Check time stamps and units as well.
The order should name user roles, login rules, event logs, network zones, and remote access. Add steps for backup, restore, updates, and going back to the last good version. Set rules for how long data is kept and how it can be sent out.
If the buyer needs a screen or report, list its fields and user actions. A screen image proves only that the screen exists. It does not prove that the buyer’s data and work flow are linked.
Raise the proof at each gate
Use small gates so a bad link is found before site start-up. Give each gate an input, a pass rule, and a saved record.
- Scope freeze. Sign the seller, app tools, version, licence, BOM, and owner list.
- Design check. Sign the system map, network map, state flow, data rules, alarm list, and link sheets.
- Bench test. Use a test tool or real device to check messages, states, and faults.
- FAT. Test the ordered app with the gear that is ready at the seller’s site.
- SAT. Repeat site-based tests on the buyer’s network and machines.
- Shop trial. Run the agreed jobs and work hours. Close open work with proof.
Keep an open-work list at each gate. Name the owner, due date, new test, and effect on sign-off. Check the tests again if a CNC control, app version, or link changes.
Keep FAT and SAT as two decisions
FAT means factory acceptance test. It checks the agreed scope before site sign-off. SAT means site acceptance test. It checks the site-based work after install. One test does not replace the other.
| Gate | What to check | What to save |
|---|---|---|
| Bench test. | Send good and bad messages. Check states, wait times, copies, lost data, and reset. | Save the app version, input, pass rule, and result. |
| FAT. | Check job flow, CNC and robot links, tracking, alarms, roles, reports, and backup. | Save signed tests, logs, screen proof, open work, and new test results. |
| SAT. | Check the buyer’s network, real devices, site access rules, IDs, reset, and data links. | Save the site setup, signed results, and open-work list. |
| Shop sign-off. | Run the agreed jobs, queue rules, user steps, help route, and test time. | Save run records, pass limits, gaps, and the final sign-off. |
Put clear pass limits in the order. They may cover reply time, state accuracy, queue rules, reset, missing data, or run time. The buyer must set those limits for the real process. This page does not set fixed cycle, accuracy, use, or output results.
Send facts that can become tests
Send the list of CNCs, control types, and app versions. Add each robot, pallet store, cart, or transfer unit. Show how parts and pallets should move. Add the job and queue rules.
Name each link to MES, ERP, quality tools, and reports. Add user roles, network limits, cyber rules, remote access, alarm and reset needs, backup steps, and pass limits.
If the buyer also needs a cell, send the item list, layout, and safety owner list. Ask the reply to show what is sure, what is an option, what is out, and what still needs proof.
Reviewing an FMS control app?
Turn the link packet into a test plan
Send the system list, state rules, data fields, and pass limits. Ask NEXTAS to return the app scope, hardware line, open links, and test steps in separate parts.
Frequently Asked Questions
What is NEXTAS FMS software?
NEXTAS FMS is presented here as a software and control platform for scheduling, work orders, equipment states and production data. The ordered module list, version, licence and deployment model must be stated in the proposal.
Does NEXTAS FMS software include the robot, cell or pallet magazine?
Not by default. A robot, pallet magazine, CNC changes, workholding, sensors, guarding, safety controls, network hardware and installation are included only when they appear in the signed bill of materials and scope matrix.
Can NEXTAS FMS connect to my CNC, MES or ERP?
Compatibility must be confirmed for each named system. Define the controller and software versions, data points, protocol or file method, command owner, error response and test case in an interface control document.
What evidence should I request before ordering?
Request the software module and version list, licence terms, architecture and network diagram, interface control document, data map, hardware bill of materials, security and backup roles, support terms and a signed FAT and SAT plan.
How should FAT and SAT be split for FMS software?
Use bench or simulated interface checks first, then an integrated factory acceptance test on the ordered scope. Run site acceptance after installation, followed by a defined production trial. Each gate needs pass criteria, records and an owner for open items.
What should I send for an FMS software scope review?
Send the machine and controller list, handling devices, pallet or part flow, job and queue rules, required data links, user roles, alarm and recovery needs, network limits, cybersecurity rules and buyer acceptance targets.