Home / FAQs / Enterprise operations and operations management system
QUESTION & ANSWER

Field Service System Implementation

The focus of the implementation is not to move paper sheets to mobile phones, but to close the loop for receipt, dispatch, arrival, processing, confirmation and closure. Unusual samples such as weak webs, transfers, spare parts shortages and customer refusals are also prepared well in advance.

Answer the question.

First, give conclusions that can be used for decision-making

The field forms are designed to capture only real impact processing, responsibility and settlement information, and are used to locate photographs for supporting marks, which are not a substitute for professional testing or statutory certification.

DECISION FACTORS

What conditions need to be identified before judgement is made?

The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.

Service staff use mobile phones, PDAs or other terminalsIs it necessary to sign offline, maps, photographs and customers at the scene?Which system is the source of equipment, spare parts and warranty data?How to separate the authority of the co-workers and outsourced engineers
ACTION STEPS

Suggested order of advance

01

First, we'll be clear about the target and the border.

Following the customer service and the engineer restore the real work day.

02

Validation Key Dependence

Harmonized job sheet classification, status, time frame and abnormal code.

03

Development of assessable outcomes

Validation of the mobile end and spare parts interface in one area.

04

Make sure you decide the next step with the real results.

Rewind the resolution rate and the causes of the delay before it is extended.

PRACTICAL EXAMPLE

How do you understand it in the actual business?

Example used to illustrate the method of judgement

The engineer is not connected to the underground equipment, and can view the tasks and fill out the checks offline, and restore the network to the required level. If the same worksheet has been modified, the system is a reminder of conflict and is manually confirmed, and cannot be covered silently.

COMMON RISKS

The easiest pit to step on.

Only testing the mobile end in the office, no weak net and no real device

The location photographs are considered absolute proof, with no error description.

Too many work fields cause a line to bypass the system

ACCEPTANCE

How should we end up receiving and confirming?

Receiving and inspection cover orders, transfers, offline, back-up, conflicts, spare parts, customer refusals, overtime and closure of cases, and check equipment compatibility, information, access and data synchronization.

When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.

Your project conditions are different from the examples above?

Operational objectives, existing systems, sample and planned time could be collated before consultants could make preliminary judgements in relation to actual boundaries.

Associate project consultants