Framework · RSF

Five Capability-Layer Needs

What RSF is designed to address

Chapter 1 frames RSF as the missing service-capability layer between formal compliance standards and everyday robotics service operations.

Need 1Building a service-engineer competence certification system.

Need 2Building a cross-platform service lifecycle framework.

Need 3Building service procedures for AI/ML-integrated systems.

Need 4Building an SLA framework for robotics service.

Need 5Building specifications for remote service and service-data management.

The framework is written for readers who need a shared service language before discussing detailed service procedures.

Use RSF to structure post-delivery service readiness, overseas support, and product-service documentation.

Use RSF to describe service capability, field coverage, maintenance scope, and escalation boundaries.

Use RSF to map training, assessment, CPD, and future ATC readiness to a shared capability model.

Platform	RSF relevance
Industrial arms	Full lifecycle service, commissioning, diagnostics, preventive maintenance, and decommissioning.
Collaborative robots	All RSF domains apply, with dedicated attention to collaborative safety verification and field procedures.
AMRs	Remote operations, SLAM/navigation diagnostics, predictive maintenance, and mixed-fleet service coordination.
Service robots	Scenario-based risk, customer-facing SLA design, and lifecycle service documentation.
Humanoid robots	Multi-modal perception, embodied-AI service methods, advanced diagnostics, and fast-evolving lifecycle requirements.

Layer	Role	RSF relationship
Compliance baseline	Formal standards and legal requirements.	RSF respects and references this layer without replacing it.
RSF framework	Capability domains, service methods, certification pathway.	The main contribution of the initiative.
Operational pattern reference	Lessons from 4S service, ITIL, CMMI, and mature service operations.	Adapted as operational logic, not copied as compliance authority.

Domain	Capability focus	Tier
Domain 1 · Service Lifecycle Management	Plan, execute, record, and improve service activities from delivery and commissioning through operation, maintenance, and decommissioning.	Service execution
Domain 2 · Fault Diagnosis & Technical Support	Identify and localize root causes across mechanical, electrical, software, and AI layers, then deliver effective technical resolution.	Service execution
Domain 3 · Remote Service & Digital Operations	Use remote connection, digital twins, predictive maintenance, monitoring, and OTA workflows to support off-site service delivery.	Service execution
Domain 4 · SLA Design & Service Commitment	Design, negotiate, track, and improve robotics service commitments such as response time, availability, escalation, and performance indicators.	Management architecture
Domain 5 · Cross-Platform Service Procedures	Build unified service procedures across industrial arms, cobots, AMRs, humanoid robots, and other robot platforms while preserving safety requirements.	Management architecture
Domain 6 · AI/ML System Service Methods	Diagnose AI-layer service issues, evaluate model performance, manage model updates, and define service methods for learning-enabled robot systems.	Management architecture

Scenario	Primary domains	Reason
New-equipment delivery and commissioning	Domain 1 · Domain 2	Acceptance, installation, parameter setup, safety verification, and operator handover require lifecycle control plus diagnostic readiness.
Preventive maintenance execution	Domain 1 · Domain 3	Maintenance cycles and service records are supported by monitoring data and predictive-maintenance triggers.
On-site fault response and repair	Domain 2 · Domain 1 · Domain 5	Root-cause diagnosis must consider lifecycle state and platform-specific service procedures.
Remote fault response	Domain 3 · Domain 2 · Domain 4	Remote connection, diagnosis, service commitment, and response-time tracking operate together.
AI-component performance degradation	Domain 6 · Domain 2 · Domain 3	AI-layer symptoms require model evaluation, stratified localization, and data from remote/digital operations.
SLA review and customer communication	Domain 4 · Domains 1-3	Service commitments are measured against lifecycle records, diagnostic work, and remote-service data.
Mixed-platform service environment	Domain 5 · Domain 2 · Domain 1	Shared work-order logic must coexist with platform-specific safety and diagnostic differences.
OTA firmware update and version management	Domain 3 · Domain 1 · Domain 2	Updates require backup, rollout, verification, rollback planning, and lifecycle change records.

Technical layer	Associated domains	Example service work
Mechanical body	Domain 1 · Domain 2 · Domain 5	Lubrication, backlash measurement, TCP verification, joint replacement, and mechanical-wear assessment.
Electrical control	Domain 1 · Domain 2 · Domain 3	Servo tuning, safety-circuit testing, LOTO operations, sensor calibration, and communication troubleshooting.
Software middleware	Domain 2 · Domain 3 · Domain 5	Firmware updates, parameter backup/restore, log analysis, protocol inspection, and coordinate-system verification.
AI decision layer	Domain 6 · Domain 2 · Domain 3	Perception benchmark testing, model-performance evaluation, distribution-shift detection, rollback, and data-quality audit.

Tier	Competence logic	Indicative role
Professional	Know-How: execute standard service procedures and complete basic service records.	Qualified robot service professional under defined work scope.
Specialist	Know-Why: handle complex faults, interpret service data, and mentor routine operations.	Advanced troubleshooting or domain-specific service lead.
Expert	Know-Across: integrate across domains, design service systems, and lead complex customer operations.	Service-system architect, escalation lead, or future ATC trainer.
Master	Know-Beyond: define best practices, contribute to governance, and shape ecosystem-level service methods.	Framework contributor, standards participant, or service-network leader.