Improve the speed of data synchronization and reduce conflicts
Improve the speed of data synchronization and reduce conflicts
Make it easier to record effort on an activity
Improve the login flow
Making list view more uniform and consistent.
Keep the technician updated about important information
Make it easier to edit details of an activity or service call
Capture feedback from the end customer about their field service experience
Technicans often work environments with dangerous equipment and hazardous materials
Improving material screen to make it easier to use items by scanning or
Time line aggregation of efforts
Make stop watch more visible during the workflow steps
As a planner I want to be able to see where my technicians are located, the customers, equipment and activities so that I can better plan my resources
As a planner I want to use more user-friendly filters in order to display the needed information. Filters should apply to technicians on the planning board as well as activities on the planning list. It should be possible to add/remove part of the filters with few clicks.
As a dispatcher I want to have an overview of all my activities in order to better identify and find them without the need of looking on different places like:
The activity list should be the central place to start looking for information. From the single activity I want to be able to jump to the specific "area" where such activity belongs (project management, planning list, planning board, service call)
As a system integrator I want to be able to use ready-to-use interfaces for operations like:
- plan an activity
- release an activity
- unassign an activity
- delete an activity
- resolve the address of an activity
As a planner I would like to be able to view and edit activity and service call information on a main screen (either modal or full-page) instead of using the sidebar so that I have a more comprehensive view of all information without the need of opening and closing different tabs
As a planner I want to be able to review the history of my activities and service calls so that I get a clear overview of what did what on a certain moment in time for a certain service call or activity
As a planner I want to be able to trigger a search based on freetext and retrieve the relevant objects that contains any reference to the searched string so that I can quickly find the information I am interested in.
As a planner I want to be able to modify certain information on an activity at the same time as other users (when allowed via permission) without raising conflicts every time multiple users touch the same activity but different fields
As a planner I want to be able to create up to 500 activities that can then be released and managed in FSM
As a planner I want to be able to assign a team to a project so that I have the overview of the people involved in a project and I can then filter such activities on the mobile device
As a planner I want to be able to define milestones on a project so that I can verify the progress of a project as defined by the milestones
Integrating AI-Services for best matching technician.
New translations for specific areas.
Restrictions for sensitive data.
Capture feedback from the end customer about their field service experience.
Allow end customer to communicate and get support.
End customer gets informed about costs and can accepted/declined before technician is planned in.
So far erp cloud account cannot use crowd feature. Almost all of main contractors are big companies. they are using erp integrated cloud account.
We will be ready for those big companies who are our main market of crowd
Crowd allow user access data between different companies and accounts. So far those data access control hard code in cloud. it is not flexible for users to set up the permission
Make crowd data management more scalable and maintainabl
A company need to verify all new service partners qualification about required certification, files and to ensure agreement before giving job to service partner.
When company build his own service crowd to invite his own service partners. They don't want partner join coresystems platform. it will confuse their service partner.
We have crowd platform allow those big companies build their service crowd. Branding crowd platform will help those companies looks more professional.
Crowd platform not only allows a company connecting to service partner but also can invite individual freelancer. For those freelancers might only need mobile to get job, we need to have quick and simple way to connect those users and share the job with them via mobile
Our crowd platform allows different companies build their own service crowd. For different companies, they have different onboarding steps. As a platform, a company should allow setup his own onboarding steps. when they invite his own service partner, the service partner should follow pre-defined onboard steps.
Improve checklist designer to manage a large amount of templates
Provide customer and back-office with reports based on Checklist Report View
Share checklist instances with external contractors or end-customers and allow them to fill in this information in a browser
Allow to manage photos taken during inspections and service
Allow to prepare documentation required to solve complex industrial field service in offline environments
Import Checklist Templates based on a CSV or Excel Structure
Allow to record effort, material, mileage and expenses in checklists and provide the final report during the checkout.
Improve Query API to allow writing more complex queries
Allow to create and manage several dashboards each containing a set of charts.
Improve Developer Experience to increase efficiency creating reports for FSM
Provide a simple shell to build web apps based on our platform. The shell provides basic functionality like login or routing based on coresystems FSM.
Make Cali Great Again
The autoscheduler (Cali) was created as a prototype for a specific sales lead. Although is used for sales demos, needs polishing to be achieve MVP status
(note: the backend has been used on production - Ring, Mila, but CALI was never used as a full stack feature)
After MVP status, some improvements are needed
Use prediction to save the technician and dispatcher (and eventually end user) of repetitive and inefficient tasks. In the end, CALI will be a pervasive feature across the application. Whenever the Cali logo appears, the user know something intelligent is happening
Besides the feature and application embedded in WFM, CALI should provide a range of loosely coupled services enabling other apps.
In articulation with Core platform architecture, simple and reliable public APIs should be provided.
The goal is to get experience with different IoT platform so a more generic IoT integration Platform solution can be developed.
Currently this is a very high level and will be spliced once more research is done.
Re-architecture the MDM product so data is pulled from an origin system in real time and not stored in the FMS.