Robot Simulation Sprint
Starting at $2,000
- One robot, one scenario, one engineering question
- Manipulation, navigation, ROS / ROS 2 testing
- Simulation, tests, and evidence as scoped
- Target 7–10 business days for standard sprints
Questions a sprint can help answer
MRPX turns robot models, CAD, layouts, and operating scenarios into simulation environments. Typical engineering questions include:
- Can this arm reach every required pose?
- Will this robot collide with nearby equipment?
- Can this AMR complete the route?
- How long does the automated cycle take?
- Can this layout support the planned workflow?
- What happens when an obstacle blocks the nominal path?
- Can we demonstrate the proposed automation before installation?
You do not need a complete simulation specification to start. Send the robot, environment, and the decision you need to make.
Three products
Choose the engagement that matches the engineering question. Hosting and later connected-twin work are available — but not required — after a sprint.
Virtual Commissioning Sprint
Fixed-scope quote
- Robot cells, cobots, AMRs, warehouse automation
- Reachability, collisions, paths, layouts, cycle time
- Arrive onsite with fewer surprises
- Does not replace PLC or safety certification
Hosted Validation Twin
Starting at $200/month
- Keep the validated simulation available
- Reviews, demos, and repeated test runs
- Browser access when useful
- Simulation twin today; connected twin if required later
Typical expansion path (optional):
Simulation Sprint or Virtual Commissioning Sprint → Hosted Validation Twin → connected operational twin if telemetry integration is required.
Customers may enter at any point.
Need a dashboard add-on, extended engineering, or a private deployment? Those remain available as separately scoped work. See pricing or contact MRPX.
Safety note: Virtual commissioning and digital-twin work do not replace customer-side validation, hardware safety systems, PLC commissioning, or professional engineering review. MRPX does not claim safety-critical autonomous control.
When this is a fit
- The physical robot is not ready yet, but software still needs a place to run
- You need to validate an automation concept before building it
- Internal simulation engineers have a backlog
- You need to test one scenario without another full-time hire
- A workcell or customer installation is approaching
- You want to catch reachability or collision issues before going onsite
- You need a customer-facing simulation of planned automation
- You want repeatable robot tests and an evidence package
What you provide
You do not need complete files to start a discussion. Depending on the project, useful inputs include:
- CAD files — STEP/STP, or split visual/collision meshes
- URDF / XACRO / USD — robot structure and scene assets
- STL / OBJ / DAE meshes — visual and collision geometry
- ROS packages / interfaces — topics, launch files, or API notes
- Environment layout — workcell, warehouse, or station drawings
- Photos, videos, and dimensions — if CAD is not yet available
- The engineering question — what the simulation should prove or help you decide
What MRPX delivers
Potential or scope-dependent outputs — not every project includes every item:
- Simulation environment and scenario implementation
- Browser-accessible demo when practical
- Recorded simulation, screenshots, and metrics
- Pass/fail tests and data export where scoped
- Engineering summary of what the scenario showed
- Hosted Validation Twin access for later reviews and reruns
Best fit / not a fit
Best for
- One defined scenario that should not wait on another hire
- Virtual commissioning before a customer installation
- ROS / ROS 2 test environments during development
- Customer demonstrations of planned automation
- Repeatable validation as software changes
Not for
- Instant hardware integration or turnkey production deployment
- Unlimited engineering without a written scope
- Safety-critical autonomous control without customer-side validation
- Clinical care, regulatory submission, or production safety certification
Files, uploads, and workflow
After a project is confirmed, use your account to upload categorized files and track build status.
Upload categories
| Category | What to put here |
|---|---|
| Visual meshes | Appearance geometry (.stl .obj .dae) for rendering |
| Collision meshes | Simplified or dedicated collision bodies |
| URDF / XACRO | Robot structure (.urdf .xacro) |
| CAD | STEP/STP when meshes are not yet split |
| Config files | .yaml .yml .json |
| Dynamics data | Mass, COM, inertia tables or notes |
| Control mappings | Input-to-motion mapping notes and requirements |
| Interface / API docs | SDKs, protocols, message contracts (digital twin) |
| Calibration references | Transforms, reports, calibration data |
| Videos / images | .mp4; .png / .jpg |
| General documentation | README, acceptance criteria, specifications |
Allowed extensions: .urdf .xacro .stl .obj .dae .step .stp .zip .yaml .yml .json .pdf PNG/JPEG images .mp4. Other formats available on request.
Frequently asked questions
What kinds of robots can MRPX simulate?
Mobile robots, manipulators, inspection/field platforms, warehouse/AMR systems, research robots, and other custom platforms. Scope depends on available models, interfaces, and the defined scenario — not every robot is a standard sprint.
What files do I need to get started?
You do not need complete files to start. Ideally URDF/XACRO with mesh files, but we can also work with CAD, photos, videos, dimensions, ROS packages, or a clear scenario description.
How long does a Simulation Sprint take?
Standard fixed-scope Simulation Sprints target 7–10 business days after scope and required inputs are accepted. Larger or more complex simulation projects are estimated separately and may take multiple weeks.
Must every deliverable be browser-based?
No. Review the simulation from the browser when that helps your team or customer. A sprint can also deliver recordings, results, and other agreed technical outputs.
Can I keep the simulation after the sprint?
Yes. A Hosted Validation Twin keeps the environment available for reviews, demos, reruns, and later updates. That is a simulation twin today. A connected operational twin with live telemetry is scoped separately if the business case requires it.
Does virtual commissioning replace PLC or safety work?
No. MRPX can simulate planned robot or automation behavior so your team finds integration problems earlier. It does not replace full PLC commissioning, safety certification, or professional engineering review.
Is this safe for controlling real robots?
Connected operational twins are scoped carefully. MRPX does not claim safety-critical autonomous control. Real-robot pathways require customer-side validation, hardware safety systems, and agreed operating procedures.
What does the $200/month hosting cover?
Hosted access to your validated simulation via browser (when that is the delivery model), maintenance, uptime monitoring, and limited monthly usage. Usage limits depend on compute requirements and simulation complexity.
What do you need to validate?
Start with one robot, one scenario, and one engineering question. Upload what you have — files do not need to be complete to begin.
Questions? manuel.retana@mrpxtech.com · Home