Listed below are questions that address many of the past support issues we've solved for our customers. Click on the question to view the answer.
The Technical Support Department can be reached from 7:30 AM to 4:00 PM (Mountain Time Zone). The support queue closes at 3:00 PM on Thursdays.
The ESA offers customers many services including access to the online tutorials, help files, training webinars, technical assistance through phone and email, software updates and discounts on future license purchases. ESA’s are renewed on an annual basis. A current ESA is required in order to provide service or support.
Training/implementation works with companies to properly configure and customize ManagerPlus. Their professional experience will assist in establishing company processes and training employees based on those processes. Training can be done as a group or in a one-on-one setting. Implementation will assist in obtaining and implementing customizations or integrations.
Training/Implementation is a paid service that can use your companies data to work through online meetings, onsite trainings (we come to you), classroom trainings (you come to us), seminars or generalized paid services.
Training/Implementation can answer user specific questions and offer professional, experienced advice such as: “What is the best way to setup…”, “How should this be configured?”, etc.
Technical Support is provided through your current Extended Support Agreement (ESA). Technical support staff will assist with installing, upgrading and troubleshooting ManagerPlus software. Technical Support staff can also provide limited user help in the form of “targeted” questions. Technical Support user help should generally be limited to 10 minutes or less per call.
Technical support can help with ManagerPlus related technical questions, and smaller scope user help questions like: “What is this feature?”, Where is the option to…”, etc.
User licenses determine which individuals in an organization can access ManagerPlus products, as well as their level of access. The following is a breakdown of the different user types available.
Named User
A named user can access anything in the program. This type of license is “used up” when the named user is created, and it is generally designated for one specific person. The named user can only log in at one place at any given time.
Concurrent User
A concurrent user license is “used up” when one of the users actually logs in, and is released when they log out. One license is not designated for a specific person, and could thus support multiple users, but only one person can log in at any given time. These users can only access the main application.
Mobile User
Mobile users work like named users, but mobile users are limited to the mobile module.
Mobile + Concurrent
If you have concurrent users available, then a mobile user can log into the main application. When the mobile user does log into the main application, it “uses up” a concurrent user.
M+ Work Requests Users
Work Requests users are unlimited with purchase of the Work Requests module. These users can only access the work requests tools (mobile app, website, email), and cannot access the full program.
ManagerPlus Cloud uses UTC (Universal Time Coordinated) to calculate timestamps within the system. By default, the time zone is set to CST (Central Standard Time). Using the Time Zone Offset found in the “Company” module under the “Options” tab, you have the ability to change it to your primary time zone. Below is a chart of the UTC time zones in North America with their Daylight offsets (where applicable).
|
Time Zone in North America |
UTC Offset (Standard Time) |
UTC Offset (Daylight Time) |
|
Atlantic |
UTC -4 |
N/A |
|
Eastern |
UTC -5 |
UTC -4 |
|
Central |
UTC -6 |
UTC -5 |
|
Mountain |
UTC -7 |
UTC -6 (n/a for Arizona) |
|
Pacific |
UTC -8 |
UTC -7 |
|
Alaska |
UTC -9 |
UTC -8 |
|
Hawaii |
UTC -10 |
N/A for Hawaii |
A schedule is essentially a set of service tasks (e.g. oil changes, calibrations, etc.), parts, labor, etc., associated with the routine maintenance performed on assets. These schedules are used to generate work orders at specified intervals (work orders can either be created manually by a user, or can be set in some cases to generate automatically). These intervals can be based on timeframes (e.g. monthly, quarterly, etc.), or they can be tied to log records (e.g. hours, mileage, etc.). The “Reset my schedules” setting you’re being asked to configure during the initial client installation process determines when that interval is reset (e.g. starts counting down again).
There are two options for the “Reset my schedules” setting:
1. Reset schedule on work order creation. If this option is selected, schedules will reset and begin counting down to the next time they’re due when the previous work order is generated. While the current work order is still in progress, the schedule is still counting down.
2. Reset schedule on work order completion. If this option is selected, the schedule will reset and begin counting down to the next time it’s due only after the existing work order is completed. The schedule will not start counting down to its next due date while a work order it has already generated is still open.
1. Open ManagerPlus and click the "Help" tab.
2. Click "About ManagerPlus"
3. In the "About ManagerPlus" window, your product version will be at the top of the list.
FIFO is short for First In First Out. This is the same concept as “stocking from the back” when adding/removing parts. This inventory method, like LIFO, is more of a process than a calculation or equation. Whatever inventory is “oldest” or brought in first, will be consumed first. The most recently purchased parts will be left in stock. This will cause a continual “roll-over” of our inventory costs, where we’re keeping everything relatively recent.
Example:
1. We purchased 2 x widgets at $5, our inventory value is $10 (5 + 5), our current part cost is $5 each.
2. We purchased 2 x widgets at $10, our inventory value is $30 (5 + 5 + 10 + 10), our current part cost is 5.
3. We purchased 1 x widget at $12, our inventory value is $42 (5 + 5 + 10 + 10 + 12), our current part cost is 5.
4. We consumed 3 x widgets, our inventory value is $22 (10 + 12), the first two were charged out at 5 each, the third was charged out at 10, our current part cost is 10.
5. We purchased 1 widget at $6, our inventory value is $28 (10 + 12 + 6), our current part cost is 10.
LIFO is short for Last In First Out. This is the same concept as “stocking from the front” when adding/removing parts. This inventory method, like FIFO, is more of a process than a calculation or equation. Whatever inventory is “newest” or brought in most recently will be consumed first. The oldest parts will be left in stock. This will cause the newest items to be brought in and used while leaving old items “on the back of the shelf.”
Example:
1. We purchased 2 x widgets at $5, our inventory value is $10 (5 + 5), our current part cost is $5 each.
2. We purchased 2 x widgets at $10, our inventory value is $30 (10 + 10 + 5 + 5), our current part cost is $10 each.
3. We purchased 1 x widget at $12, our inventory value is $42 (12 + 10 + 10 + 5 + 5)
4. We consumed 3 x widgets, our inventory value is $10 (5 + 5), the one widget was consumed at 12, then two were consumed at 10, our current part cost is 5.
5. We purchased 1 widget at $6, our inventory value is $16 (5 + 5 + 6), our current part cost is 6.
Rolling average is based off the following calculations:
When stating the consumed value/cost, we’re using the cost that it was purchased at.
Part purchase/consumption is handled in a FIFO order, using the rolling average part cost.
(Sum of all received part costs – sum of all consumed part costs)/Quantity remaining = current part cost (as listed in the inventory screen).
Whenever adding a part to something (WO, PO, Adjustment, transfer, etc.), it will default to this part cost.
The part cost is only updated/recalculated when we receive more parts (adjustment gain, receive a transfer, PO, etc.). It is not recalculated when parts are consumed (adjustment loss, WO, etc.).
Current part cost * Quantity = Inventory Value
The overall effect is that the “rolling average” is giving us the part cost of our current inventory (not any consumed inventory). Along the same lines, if we “zero out” our inventory at any point, our rolling average will essentially start over.
*Note* the “Avg. Cost” listed in the Inventory Valuation report is not necessarily equal to the part cost. The Avg. Cost is simply the average of all purchase costs, and doesn’t directly have anything to do with the inventory method “Rolling Average.”
Ex. If we purchase 1 widget at $200, then we consume it.
Then we purchase 1 widget at $100:
Our average cost is $150, our part cost is $100, our quantity is 1 and our inventory value is $100.
Example:
1. We purchased 2 x widgets at $5, our inventory value is $10 (5 + 5), our current part cost is $5 each.
2. We purchased 2 x widgets at $10, our inventory value is $30
(5 + 5 + 10 + 10 or 7.5 x 4) our current part cost is $7.5 each [(10+10+5+5)/4].
3. We purchased 1 x widget at $12, our inventory value is $42
(5 + 5 + 10 + 10 + 12 or 8.4 x 5) our current part cost is $8.4 each [(12+10+10+5+5)/5].
4. We consumed 3 x widgets, our inventory value is $16.8 (42 – 8.4 - 8.4 - 8.4 or 8.4 x 2), the widgets were consumed at the rolling average part cost of 8.4, our current part cost is still 8.4.
5. We purchased 1 widget at $6, our inventory value is $28 (10 + 12 + 6 or 9.3333 x 3), our current part cost is 9.3333 [(10 + 12 + 6)/3 = 9.3333].
Last cost is a very “now” centric inventory method. It essentially takes the last purchase price and simply applies it to all history of that part. Everything is driven off of the last purchase price.
Example:
1. We purchased 2 x widgets at $5, our inventory value is $10 (5 + 5), our current part cost is $5 each.
2. We purchased 2 x widgets at $10, our inventory value is $40 (10 + 10 + 10 + 10), our current part cost is 10.
3. We purchased 1 x widget at $12, our inventory value is $60 (12 + 12 + 12 + 12 + 12), our current part cost is 12.
4. We consumed 3 x widgets, our inventory value is $24 (12 + 12), the three parts were all consumed at the part cost of 12 , our current part cost is still 12.
5. We purchased 1 widget at $6, our inventory value is $18 (6 + 6 + 6), our current part cost is 6.
The easiest way to manage AutoCorrect Options is to:
From here you can manage your AutoCorrect settings.
One option is to uncheck the box that says “Active” under “Replace text as you type.” This will disable the AutoCorrect functionality.
Custom fields can be added to the list view in all modules that utilize custom fields.
If it is necessary to move asset between entities:
Should I delete a user in ManagerPlus?
Yes, if a user is not tied to preexisting records within ManagerPlus and or has not perform work within the ManagerPlus system, the user can simply be deleted without record degradation.
No, if a user has been tied to records within ManagerPlus, an error notification will be prompted notifying that this user is tied to records within the system. ManagerPlus recommends, making the user inactive to maintain database integrity.
What to do if a user is tied to a record within ManagerPlus:
In order to maintain proper records, it is recommended to leave the user in the system, and mark it as inactive.
Marking a user inactive will free up a user license without removing any records within the system.
How to delete, or inactivate a user:
Within ManagerPlus, there is an ability to purge or “delete” an asset from within the system.
The only time it would be recommended to purge an asset from the system is when an asset was added incorrectly during initial setup and configuration.
As an alternative, an asset can be marked as inactive to remove the asset from the active asset list. The asset can also be renamed, if the original name needs to be reused for a new or future asset.
Marking an asset as inactive maintains links with all appropriate records, allowing all budgeting, work order, labor, parts and other reports to continue to pull back all accurate information.
Persistent is a cycling option for schedules that use calendar based cycles.
Persistent has two main functions:
Advantages: A persistent schedule cannot be skipped, the cycle maintains consistent date regularity. The schedule will always come due based on the cycle set. For example, if Monthly and Persistent are used, then every month a work order will come due and cannot be skipped no matter what date completed is set to. This provides total audit functionality where every month either states the job was done or whether the job was not done, 12 work orders would be there with 12 explanations. The system will maintain consistency and always have a work order with persistent checked. If this is set to the 15th of the month with a Monthly-Persistent schedule, every month there will be a work order and it will always show as due the 15th.
NOTE: Because the schedule is “locked in” the “adjust progress” button must be utilized in order to set the cycle on the desired date. Persistent can cause the schedule to “get ahead” or “get behind” (i.e., If a monthly schedule was created in Jan, and hasn’t been completed until May, it will be 100% due until a work order is completed for all previous months leading up to May. Because of the way persistent works, best practices would be to use persistent on schedules that are at least a month between cycles.
For Cloud users: M+ mobile solutions can send and receive data directly to and from the program over any internet connection (3G, 4G, fiber, cable, etc.). Because our Cloud products are accessed through the web, no additional network configuration is required.
For Desktop users: There are two ways that mobile devices can connect to our Desktop products. The first is to sync data when connected directly to your company's internal network. Mobile devices can be still be used in offline mode to gather data, but can only be synced when in range of the internal network. This setup requires no additional network configuration by IT staff.
The second way is to configure your company's internal server(s) so that they can push and pull data over the internet. This enables users to sync data from their mobile device anywhere they have internet access. Important note: configuring internal server(s) to push and pull data from the internet is not directly supported by ManagerPlus support staff and must be handled by internal or third party IT services.
The connections file holds the information for the client computer to connect to the server.
The connections file is normally found in the user’s appdata folder.
Start > Run > %appdata% > click OK > ManagerPlus
The connections file can also be moved into the installation directory (for example: C:\Program Files\ManagerPlus ) so that it will be computer specific instead of windows user profile specific.
Typically, you’ll receive an email notification when ManagerPlus is updated. This email will contain all the information you’ll need to update, including specific information for that particular version.
A typical update will involve the following steps:
M+ Work Requests is the ManagerPlus work order request module. This application allows non-ManagerPlus users (requesters) to submit a request for work that can be processed into work orders within the ManagerPlus system. Additionally, logs (i.e., meters such as hours, miles, etc.) can also be entered through the Work Requests website. The Work Requests website is a server based Internet Information Services (IIS) application (website) that can be easily accessed from a web browser.
Two major advantages of M+ Work Requests:
For more information on M+ Work Requests, visit http://www.managerplus.com/maintenance-software/modules/workrequests