BSM Context Properties
The following tables describe the BSM context properties that enable the main features of BSM.
| Property | Description |
|---|---|
|
Note: For more information on how BSM integrates with the EAM Asset Works service,
contact your Trapeze Customer Care representative.
|
|
| Host name of the EAM service. | |
| Instance name of the EAM service. | |
|
Location of the asmx file. For example, the path to the AssetWorks.asmx file:
The ServerAddress is the URL specified by the EAM Integration/ServerAddress property (See the context properties in the Trapeze6 Client Shell). |
|
Namespace of the AssetWorks namespace URI, for example,
"http://tempuri.org" format="html" scope="external" |
|
| Prefix used to generate the equipment ID in EAM. | |
|
|
Key to encrypt the user name and password. |
| Block size to use Rijndael encryption, for example, 16, 24, or 32. | |
| If selected, the EAM Asset Works service is activated. | |
| Property | Description |
|---|---|
| Data Source Name (DSN) | |
| Login name of the user. | |
| Password to be associated with the login name. | |
| Number of characters to be displayed in the EDI list. If set to 0, the system displays all. |
| Property | Description |
|---|---|
| If selected, the geocoding offset feature is activated. | |
| Distance to use when snapping points to an offset from an intersection. | |
|
Threshold radius when applying an offset distance when geocoding. The intersection offset is only applied when found within the threshold. |
|
| Distance to use when snapping points to an offset from the road. | |
|
Threshold radius when applying an offset distance when geocoding. The snap offset is only applied if a street is found within the threshold. |
| Property | Description |
|---|---|
|
If selected, the address data associated with the geocoded location is read from the map data based on the thresholds set in other properties. |
|
|
Threshold radius when using the latitude and longitude of a point to do a reverse lookup of an address. |
|
| Threshold radius to use when setting the distance from a cross street. |
| Property | Description |
|---|---|
|
Maximum distance when searching points to an offset from a vehicle. The information window, which contains details about a point, appears on the map when you hover between the point and the location of the vehicle on the map. |
| Property | Description |
|---|---|
|
Maximum number of rows to be displayed in the History screen. This is set to 200 by default. If set to 0, the system displays all search results. |
| Property | Description |
|---|---|
|
List of email addresses of users who are to be sent notifications on non-stop
points.
Note: Email addresses are separated by commas. |
|
|
List of email addresses of users who are to be sent notifications on non-stop points that have been deleted. |
|
|
List of email addresses of users who are to be sent notifications on non-stop points that have been edited. |
|
|
List of email addresses of users who are to be sent notifications on non-stop points that have been moved. |
|
|
List of email addresses of users who are to be sent notifications on non-stop points whose data has been signed out / signed in. |
|
|
List of point types for which notifications are sent. The point types are separated by commas. |
|
| List of email addresses of users who are to be sent notifications on stop points. | |
|
List of email addresses of users who are to be sent notifications on stop points that have been deleted. |
|
|
List of email addresses of users who are to be sent notifications on stop points that have been edited. |
|
|
List of email addresses of users who are to be sent notifications on stop points that have been moved. |
|
|
List of email addresses of users who are to be sent notifications on stop points whose data has been signed out / signed in. |
|
| If selected, email notifications on points and non-stop points are allowed. | |
|
List of email addresses of users who are to be sent notifications on work orders that have been closed. |
|
|
List of email addresses of users who are to be sent notifications on work orders that have comments. |
|
|
List of email addresses of users who are to be sent notifications on work orders that have been created. |
|
|
List of email addresses of users who are to be sent notifications on work orders that have been edited. |
|
|
List of email addresses of users who are to be sent notifications on work orders that are in transition. |
|
| If selected, email notifications on work orders are allowed. | |
|
If selected, email notification on work orders are sent to the reporters (transit staff who initiated the work order). |
|
|
If selected, email notifications on work orders are sent to the assignees (transit staff responsible for completing the work). |
| Property | Description |
|---|---|
|
If selected, the Auto Populate rules are applied to the attributes of the selected point automatically. |
|
| If selected, the Auto Populate rules are case sensitive. | |
|
If selected, the description of the amenity type or attribute type is shown instead of its name. |
|
| If selected, a warning ID is shown when amenities are changed. | |
| If selected, the system can autogenerate custom stop numbers. | |
| Fields to store the generated custom stop number (tablename.fieldname). | |
| Map dataset name for generating custom stop numbers. | |
|
Minimum Sequence Number for both {SEQUENCE} and {GROUPSEQUENCE} in the template. |
|
|
Template for the custom stop numbers. The content inside {} could be any field from the MapPolygon, CmnPoint, MapPoint or Stops tables, use {SEQUENCE} or {GROUPSEQUENCE} for sequential number. The content outside the {} can be any constant character except "|{}:". Multiple segments can be joined by "|". Number follows ":" is the length of that segment. 0 means no length limit. Functions LEFT(field, n), MID(field, m, n) and RIGHT(field, n) can be used in template (case sensitive). {SEQUENCE} or {GROUPSEQUENCE} must be put in a single segment. |
|
| If selected, the point abbreviation and common name are displayed. | |
| If selected, you can type a custom query for reports. | |
|
If selected, you can edit the points that do not belong to your OrgUnit. If not selected, you can only edit the points that are within your OrgUnit. If you selected the Cmn/OrgUnit/Enforce Entity Security context property, then you will only be able to see the point types that are assigned to the same organization as your user. |
|
|
Tab shown by default when you create a new point or edit an existing point. The options are: Point, Location, Attachments, and Amenities. |
|
|
If selected, a point is stamped appropriately when the stop position is moved regardless of how it was moved, for example, manual geocode, GPS. FS (Far Side), NS (Near Side), and MB (Mid-block) are added to the point abbreviation. If cross streets are used in the geocoding, that is, the point is exactly in the middle of an intersection, “XX” is added instead of “FS” or “NS” at the end of a string that is stamped on the point abbreviation. |
|
Choose the appropriate option whether or not you want to display the Tp4 Stop
ID when creating new points of Stop type:
|
|
|
If selected, the lookup results are sorted by Line Stop Sequence if Line and Direction were used as search filters. |
|
| List of users who can send the point list report. | |
| List of users who can receive a copy of the point list report. | |
| List of users who can receive a blind carbon copy of the point list report. | |
| Subject of the report that is added automatically when the report is sent out. | |
| If selected, the Stop ID is shown in the information window. | |
Choose the appropriate Point identifier to be used in notifications:
|
|
Choose the Point fields to be displayed when a Point is selected in a work
order:
|
| Property | Description |
|---|---|
| Zoom level for displaying a map with selected points. | |
|
|
Zoom level for displaying a map with attached points. |
| Property | Description |
|---|---|
Format of the work order number and whether it is shown or hidden:
|
|
| List of users who can send the work order report. | |
| List of users who can receive a copy of the work order report. | |
| List of users who can receive a blind carbon copy of the work order report. | |
|
Subject of the work order report that is added automatically when the report is sent out. |
|
Choose the work order parts that you want to export:
|
|
| If selected, the work order is assigned to the person who created it when it reaches its last workflow state. |