What’s New in the
Polar Release of Atheer
The Atheer Polar Release is now available.
TECHNICIAN CO-PILOT
Setup
- To set up Technician Copilot on the Atheer platform, follow these simple steps:
- Identify and Add Content: Gather all the files that you want to make available to Technician Copilot. This can include guides, manuals and other relevant documents.
- Raise a Jira Ticket: List the content and raise a Jira ticket with the engineering team to process the content. This step ensures that the content is processed and made accessible to Copilot.
- Consolidate and Classify Files: Once all the files have been processed, consolidate and classify them into topics. This is an optional step. However, it is a recommended best practice to create one topic per equipment model number and add the applicable content to that topic.
- Add Commands: Commands are references for AiRForms and Ticket templates. If there are specific Ticket templates or AiRForms that can be used for specific tasks, add these to the list of commands along with a short description and label. For example, if you have a ticket template for reporting an incident, add a command for "Report an Incident" with the ticket template ID. Commands can point to Content, AiRForms, or Tickets. Usage example - In case a user asks a co-pilot - “How do I raise an incident report” OR “I want to report an incident” OR “Incident report” Or any other way - the co-pilot will understand the request and suggest the ticket.
- Update the Home Page JSON: Specify if you want the Copilot as a tile or a floating action button on the home page. This step helps in configuring the Copilot interface according to your preference.
- Update Quick Actions: In the home page json under the tile or floating action button for co-pilot, update the quick actions. These quick actions should point to already defined commands. Quick actions are shortcuts for frequently asked questions, which can be provided upfront when Copilot is launched.
Nameplate OCR
- Setup
- For Equipments create Topic records and set the "External ID" in the topic to the Model No of the Equipment
- Add the Equipment documents as Content
- Process the documents for use in AI flows
Working
- Perform OCR
- Response will be details from the nameplate
- The content, AiRforms from the Topic related to the equipment get listed
- The copilot conversation has the equipment details set as the conversation context, you can notice the title of the conversation has been updated
- Ask a question
- System will look for the answer related to the equipment only
- Check Feature Flag: Ensure that the Copilot feature flag is set to True. This step activates the Copilot feature and makes it accessible to users.
- By following these steps, you can effectively set up Technician Copilot on the Atheer platform, enhancing the support and guidance available to field technicians.
AUTHORING COPILOT
- Access AiRForm Studio: Open AiRForm Studio and locate the option for auto-generate - this is available in any AiRForm which is in the Draft state
- Initiate Auto-generate:
- In the modal that appears, select the content file that you want to use as a reference.
- Write a prompt that provides details of what you want to author.
- Select the output type for the AiRForm (steps) such as a guide, checklist, or standard operating procedure.
- Click Generate: Once you have filled out the necessary information, click on the "Generate" button.
- Review Generated Steps: The Co-pilot will automatically generate the steps of the AiRForm based on the information provided. Review these steps to ensure accuracy and completeness.
- Edit Steps (Optional): If needed, you can further edit the generated steps in the AI generator. This allows you to customize fields and response types according to your requirements.
- Add Steps to AiRForm: Once you are satisfied with the generated steps, add them to the AiRForm. Your AiRForm is now ready for use.
MERGED REALITY
Merged Reality feature in AiRSessions is covered under the "Enable MR in AiRSessions" feature flag.
Users whose role includes the "Start MR Session" permission can only start the merged reality in AiRSessions. Best practice would be if this expert user with the requisite permissions is on a desktop and preferably has an external camera plugged into their machine, facing a white background.
User can use the white background like a mouse pad, and user any object (such as a pen or pencil or hand) as a pointer, to guide the remote technician through their work.
In the AiRSession bottom toolbar, the "Start Merge Reality" button appears for users with the "Start MR Session" permission when the feature flag is enabled. This button is available only in desktop web browsers, not in mobile web browsers or the lens app, even with proper permissions and the feature flag on.
The "Start Merge Reality" button is enabled only when two users are in the call and is disabled during screen share, annotation, or recording.
During an MR session, all other buttons and controls are disabled. After the MR session ends, the session returns to normal.
To ensure proper results, users should select the external camera before starting the MR session and avoid changing cameras during the session. They can select the desired camera after joining the AiRSession from AiRSession settings.
For a better user experience when an expert starts an MR session and other participants join through Lens and mobile browsers, they should keep their device in landscape mode.
Others
1 | Auto refresh functionality for Job Boards | FOS-13627 |
2 | Request to save Job board View selection | FOS-13626 |
3 | Lens: Support 3 lines for Content & AiRForm in the listview inside explore, unified search & Topic details screen | FOS-13463 |
4 | Public API : User GET to include Security Roles assigned to user | FOS-13896 |
5 | Dynamic Team created via API - can now be edited from Studio. The issue of not being able to update team criteria has been addressed | FOS-13901 |
6 | Invite users functionality in the workspace | FOS-13671 |
7 | Team Create & Update API support to set the dynamic team criteria- Support for Team criteria using Profile group | FOS-14170 |
8 | Support to define criteria for Dynamic team via API | FOS-14170 |
9 | Images in job reports are showing distorted | FOS-14213 |
10 | Insights - User data sync not working | FOS-14243 |
- Auto refresh time interval can be specified on in Settings → Workspace Info
- Job Board / Ticket Board auto refresh interval
- Unit = Minutes
- If set as zero (0) means NO AUTO REFRESH
- For all existing workspaces set as 0
- For new workspaces default = 0
- If a user is on a particular job board / ticket board - at a specified time interval, the job board / ticket board will automatically refresh and show the latest jobs / tickets.
* Point no. 8 to 10 are added via Polar HF1.
Please feel free to reach out to our customer success team for additional information support@atheerair.com
Comments
0 comments