The following scenarios describe how you might use Location Awareness Services for WebSphere® Premises Server to track the movements of visitors on the premises.
The following scenario includes examples of how you might use the Web services that are supplied with Location Awareness Services for WebSphere Premises Server in the business processes.
For example, when contractors arrive at the company’s premises, they receive a tag ID and predefined business rules are activated. These business rules identify areas and zones of the company’s premises where contractors are allowed to enter or where they require escorting. Contractor-specific rules can be created as part of the business process as needed. You can define business rules using the LasRuleServices - createRuleInstance Web service.
The contractors are registered in Location Awareness Services for WebSphere Premises Server, for example using the LasItemRegistrationServices - createItem Web service.
When the contractors enter the premises or the zones defined for escorting, an escort can be informed automatically using the SubscriberService Web service of a contractor's arrival.
When the contractors enter the work zone, Location Awareness Services for WebSphere Premises Server can verify that the relevant work tools are available for every worker in the zone. Otherwise they can be dispatched using the SubscriberService Web service. The number of tools can also be counted using the LasQueryServices - getTimeReportByZone Web service.
When the job is done and the contract ends, the contractors are unregistered using the LasItemRegistrationServices - registeritem Web service. A tools check can be performed for the work area using the ItemsInZoneService Web service and a final billing for the contractors' working hours is kicked off using the LasQueryServices - getTimeReportByTag Web service. Any contractor-specific rules can be deleted using the LasRuleServices - deleteRuleInstance Web service.