With the most recent release of Infralink/IMMS (v.3.5.29), we are happy to offer the following new features and
...
functionality.
Table of Contents
...
SMS Text Notifications via AWS SNS Integration
...
InfraLink notification features have expanded to now support SMS (i.e., text messages) in addition to traditional email notifications.
...
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
Rules for Default Activity Start Date/Time
...
InfraLink allows Users to log Activities (e.g., labor hours, travel time, etc.) for various Work Tickets, Cases, and Tasks, and sometimes Contracts. This information then propagates directly to M.C. Dean Timesheet via an integration service. This integration saves time, improves the accuracy of work records, and results in a comprehensive display of Users' weekly Activities.
...
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
Web Application Support for Case Creation and Case Display on Pin-Enabled Drawings
...
The Job Connect mobile application has supported pin-enabled Drawings. Pins act as a visual means of identifying where a Case is in relation to a Drawing. Case Placement has allowed Job Connect Users to drop a pin onto a Drawing, in effect creating a Case associated with that geographical region of the Drawing. The Root System Element of the Drawing will become the System Element associated with that pinned Case. Not all Drawings support pin-drop functionality. Drawings configured for pin-drop functionality will display "Drawing Enabled for Case Placement" directly under the Drawing name. Is is important to reiterate that pinned Cases are related to Drawings only in terms of geography. A pin-enabled Drawing cannot be altered or edited because the pinned Cases will not move with the new Drawing.
...
Gliffy Diagram name Pin-Enabled Drawing (Web) pagePin 1
Milestone Progress Report View
...
Complex System configurations often include individual components, which have their own life cycles and work progressions. In InfraLink, these are represented by Components and Links/Connections, as well as the associated Terminations. These dependencies, while represented in hierarchical and topological formats, were never directly aggregated within any specific views, reports or dashboards.
...
The view functions similarly to other grid views with a Filter Panel to the left hand side, the main grid view in the middle, and a Details Panel - upon record selection - to the right hand side. The grid view itself is split into two sections: the top half displays a summary of tasks completed or statuses reached by Location and the bottom half (the Device/Equipment List) displays a summary of tasks completed or statuses reached per the Systems status lifecyclelife cycle. The Device/Equipment List portion allows Users to customize the column display as well as create and share saved views.
What You Will See in the User Interface:
- Access the Milestone Progress Report nder from the Production stack within the Main Menu.
- The Summary by Location section displays the percentage of work (or tasks) left to be completed according to the Location of the System Elements, while the Device/Equipment List section displays the percentage of work (or tasks) left to be completed according to the System Elements and associated life cycle statuses.
- The view is blank until a System Element Type selection is made in the Filters panel. Once a type is selected from the Filter Panel, the Device Equipment List column options will expand to include the statuses of that System Element Type’s Lifecyclelife cycle. Only statuses associated with that System Element Type's Lifecycle life cycle will be available for selection and Users must add the statuses to the Device/Equipment List half of the grid view via View → Columns to see any records in the grid view. Once added to the Device/Equipment List section, the the columns will automatically populate in the Summary by Location section.
...
Note | ||
---|---|---|
| ||
In order for dependencies to be counted in the amount of work left to complete for a System, a Default Status Dependency must be configured within a System Life Cyclelife cycle. |
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
|
Excerpt | ||
---|---|---|
| ||
Highlighted features include: SMS Text Notifications via AWS SNS Integration; Rules for Default Activity Start Date/Time; Web Application Support for Case Creation and Case Display on Pin-Enabled Drawings; and Milestone Progress Report View. - |