PLATFORM SELECTION GUIDE
Standard Platforms vs Custom Robot Development
When an existing model and configuration meet the task, confirm the standard supply scope first. Changes to mechanics, power, control interfaces or complete robot form call for a JDM scope with explicit responsibilities, outputs and acceptance.
| Decision factor | Standard Platform Purchase | Custom Development / JDM |
|---|---|---|
| Starting point | Existing model with confirmed payload, battery and version | Mechanical, interface or complete-robot needs beyond the existing configuration |
| Deliverables to agree | Supply configuration, interface materials and support | Engineering tasks, prototypes, validation records and agreed manufacturing outputs |
| Responsibility boundary | Separate platform supply from customer module and application integration | Allocate mechanics, electrical systems, control, intelligence integration and validation |
| Acceptance basis | Purchased configuration and agreed test conditions | Milestones, test scenarios, pass criteria and a change process |
| Cost & schedule | Quoted by configuration, quantity and supply terms | Assessed against development scope, engineering effort and milestones |
Version Choices Have Different Delivery Scopes
C400, C500, C600, C800 and X700 are available as standard or embedded-only platforms. Standard platforms include localization, navigation and obstacle-avoidance algorithms; confirm sensors, algorithms and deliverables separately for embedded-only versions. Standard drivers include source code and TCP/IP documentation; algorithm source code is not supplied. Agree other JDM software, firmware and intellectual property in the project contract.
Turn Requirements into an Agreed Scope of Work
Identify the platform or product engineering assigned to Shining Robotics, the upper modules and intelligence supplied by the customer, and the conditions for joint validation. For each development stage, agree inputs, outputs, pass criteria and change handling. Completion of a product prototype does not by itself establish acceptance of the complete site application.
Four Steps to an Agreed Project Scope
- Separate needs covered by existing models from required changes to mechanics, power, interfaces or the complete robot.
- Allocate inputs, engineering responsibilities and outputs, including software, source-code scope and intellectual property.
- Define reviewable stages for requirements, development and integration, prototype validation, and production introduction.
- Agree the test environment, acceptance conditions, change process, quotation and supply terms before confirming the project plan.
Standard Platform CatalogCustom Development ProcessInterfaces & Delivery Scope
Start with your email and a brief requirement. Model, company, name and attachments can follow later. Quantity is required for academic quote requests.