With each release, new features, enhancements, or resolved issues are added to the product.
As opposed to the 3.0 version, which was specific to a particular use case of destination dispatch, the 3.1 version of the plugin supports general dispatch use cases by leveraging all features included in the ThyssenKrupp Destination Dispatch Ethernet Security Specification.The ThyssenKrupp plugin 3.1 includes the following new features and enhancements:
- Add DEDs to landings
- In the ThyssenKrupp plugin 3.0, DEDs
(kiosks) could only be added to elevators. You can now assign DEDs to landings.
From the Config
Plugins task, you can add front or rear landings to elevator
You can add a DED to a landing by right-clicking the landing. The DED will share the same elevator group and side as the parent landing.
- Secure landings on a schedule
- Landings can now be secured on schedule by using security profiles. When a
landing is secured, only specified cardholders can access it. Rather than having
to manually configure each landing to secure it, you can assign security profiles
and schedules to a DED, and the landing will be secured when the schedule is
Security profiles are defined in the Config Tool Plugins task, on the Security Profiles page of the ThyssenKrupp plugin. The selected landing sides are secured according to the schedule, unless the cardholder has access to the landing.
After creating the profile, you can assign a schedule to it from the Configuration page of the DED. If multiple profiles are active at the same time, the landing side specified in both profiles will be secured. If you do not want a landing to be secured, make sure that no active profile is securing the specific landing.
To see which profiles are currently active on a DED, select the DED from the entity browser of the Pugins task, and then click . The active profile is displayed in the diagnostic window.NOTE: A security profile applies to the landings that are both included in the profile and part of the elevator group of the DED that the profile is added to.Example: If DED 2.2.1.F is part of Group 2, which includes Landing 2.2.F and Landing 2.3.F, and a security profile that includes front landings 1, 2, 3, 4, and 5 is added to the DED, the only landings that will be secured are Landing 2.2.F and Landing 2.3.F. The other landings in the profile will not be secured because they are not part of the same elevator group as DED 2.2.1.F.
- Advanced DED modes
- You can now schedule DEDs associated to landings, as opposed to in-elevator DEDs,
to be in Sleep mode or in PIN entry mode. For more information about DED modes,
refer to the ThyssenKrupp
- ThyssenKrupp special features
- The ThyssenKrupp system supports advanced
control features, each defined for a specific dispatch operation. You can now
configure cardholders to use these features from Config
Tool. For example, assigning the
VIP feature to a cardholder by adding the cardholder to the VIP group isolates an
elevator for that cardholder so that it will not stop for other passengers after
it is dispatched. For more information on what each feature can be used for, refer
to the ThyssenKrupp documentation.
- Call registration
- You can now use a dispatch command as the action in an event-to-action to call an elevator on demand. For example, you can configure a call to an elevator to be made when someone walks through turnstiles.
- Support DEDs with embedded readers
- The plugin now supports internal readers. A cardholder can present their badge directly to a DED that has an embedded reader in it instead of to a separate Synergis™ reader. The credentials are processed by the plugin, and then the landings accessible to the cardholder are communicated back to the elevator system.
- Improved reporting
- The plugin now supports reporting with elevator activities, cardholder activities, area activities, and credential activities. A new area entity is created per floor by the plugin. The area can be used to investigate activities on a specific floor, regardless of the elevator group or of the specific landing.
- By enabling the auto-discovery feature, the plugin detects all connected DEDs in
the ThyssenKrupp system, and then
automatically creates ThyssenKrupp entities
Center. If the feature is set
to ON, and you delete an entity from Security
Center, the plugin will automatically
re-create it.NOTE: The auto-discovery feature does not delete entities from Security Center if you delete them from the ThyssenKrupp system.