smarter planet solutions with sensor monitoring, part 4: asset

Smarter Planet solutions with sensor monitoring,Part 4: Asset tracking for process optimizationSkill Level: Intermediate

Tim Hanis ([email protected])WebSphere Sensor Events Chief ArchitectIBM

Allen Smith ([email protected] )Senior Software EngineerIBM

John Senegal ([email protected])WebSphere Sensor Events Lead DeveloperIBM

Ken Greenlee ([email protected])Advisory Software EngineerIBM

Bruce Hyre ([email protected])Senior Software EngineerIBM

03 Mar 2010

Smarter Planet™ initiatives are playing a major role in how technology is shaping ourinteractions with the world around us. Common to many of these smarter planetinitiatives is the observation and processing of sensor data to extract insights fromthe physical world. Part 4 in this series discusses a hypothetical manufacturing linethat leverages real time asset location tracking data to improve the efficiency of thesystem. You will see how this sensor data can be incorporated into the businessprocesses governing the work-in-process execution flow, and also how monitoringcapabilities can be utilized to show operational dashboards. You will see how aconnected process flow system can become more intelligent and obtain added valueby improving the process flow.

Asset tracking for process optimization© Copyright IBM Corporation 2010. All rights reserved. of 21

mailto:[email protected]





http://www.ibm.com/legal/copytrade.shtml

Introduction

Part 3 of this series discussed how home health care device integration is beingused to improve the overall effectiveness of health care. This article looks at how theintegration of real time asset location tracking can improve work flow operations,such as that of a manufacturing system.

In order to achieve a lean, efficient, and responsive manufacturing process flow, it isimportant to know exactly what parts and assemblies are on hand, and where theyall are. Increasing visibility to the location and availability of parts, assemblies,calibrated tools, and even workers can both improve the efficiency of the productionprocess and provide line management with additional real time data upon whichprocess improvements can be based. To improve operation efficiency, the flow ofworks-in-progress must be uninterrupted and predicable. Management needs to beable to analyze inventory levels, cycle time, wait time, throughput, equipment andpersonnel utilization, and many other factors at all points in the process.

This article describes how asset location tracking integrated into IBM® WebSphere®Sensor Events can be used to create a smarter manufacturing solution. This article:

• Discusses the manufacturing solution and its components.

• Defines the architecture of the solution.

• Describes an example use case to demonstrate specific aspects of thesolution.

• Provides sample code for the use case described.

Manufacturing process monitoring

In a typical manufacturing enterprise today, operations managers are responsible forcoordinating all floor operations. This includes making sure that the right personnel,the right parts, tools, and equipment are at the right stations. This coordination iscritical to any manufacturing process; without it, the production operation will notoperate at capacity or will produce inferior products.

Look at automobile manufacturing, for example. The cost of manufacturing a car issubstantial and automobile manufacturers spend a significant amount of resourcesdesigning the appropriate line for the model of car they are trying to produce. Thatdesign makes assumptions about the exact parts intersecting with the appropriateskilled persons, at a precise location, at a precise time. As you can imagine, this canbe a monstrous task. Without this precision, the production output can be reduced orthe quality can be affected.

developerWorks® ibm.com/developerWorks

Asset tracking for process optimization of 21 © Copyright IBM Corporation 2010. All rights reserved.

http://www.ibm.com/developerworks/websphere/techjournal/1001_hanis/1001_hanis.html


What if an operations manager could monitor the manufacturing floor from a centrallocation? What if the manager could see how many doors were at the door station,and see if the quantity was right and that no door was damaged? What if themanager could see whether the right people were at their stations and not still onbreak when the line started moving again? What if the manager could be notifiedthat a robot arm was malfunctioning before it actually stopped working? Supposeyou are installing a specialized automobile part that requires a special set of tools.The line manager could ensure that the tools were all in place before the workstarted. Imagine starting that kind of detailed work and the tool you need is not at thestation. The work would have to stop so that the tool could be found.

These are just a few examples of the types of monitoring, checks, and balances thatare possible with a smarter manufacturing solution. Like all other Smarter Planetsolutions visibility is the answer; here, the operations manager is enabled withunprecedented visibility into the process operations. This solution can help preventline outages and quality problems by providing managers with greater insight tooperations, station by station.

This article discusses and demonstrates smarter manufacturing through anautomobile manufacturing example, but the insight of knowing that all the necessarycomposite parts, tools, equipment, and personnel must all intersect at the rightlocation at the precise time is invaluable to any manufacturing process. It is visibilitythat provides this insight and enables manufacturing processes to become smarter.

Instrumented

As we discussed in previous articles, the first step to becoming smarter is throughinstrumentation. It is instrumentation that will provide the foundation for visibilityinto each step of the manufacturing process. In manufacturing, instrumentationrefers to devices such as programmable logic controllers, conveyors, diverters, andalso RFID and barcode readers. Active RFID tags can provide the real time locationof a given asset and follow its progress through the factory. Instrumentation is notonly about devices and tags applied to the composite manufacturing parts andpersonnel but it also relates to sensors that monitor the operational aspects of thenecessary equipment. Most manufacturing equipment today has the ability tomonitor the state of the equipment. However, a smarter planet solution goes onestep further and monitors the state of the equipment, plus validates the location of allthe parts, personnel, and tools. Instrumentation is the first part of visibility.

Interconnected

Without an overall, integrated global view of the process that includes real time asset

ibm.com/developerWorks developerWorks®



location, it is difficult to manage, balance, and optimize the flow through the entiresystem. Problems and inefficiencies at one point in a complex process can beamplified as the assets travel up and down the production line. In order to add valueto the overall process, these devices and systems need to be interconnected andintegrated, so that managers can have a clear high-level view of the overall process.Interconnectivity means bringing together real time location information for parts,tools, and personnel along with equipment health status and inventory stock levels.The intersection of all this data needs to be brought together in one place so that thedata can be filtered and correlated.

Intelligent

Once this monitored data becomes visible to line operation managers, the wholesystem can become intelligent. You can automate routine sensor monitoring thatcan otherwise waste time and resources. Real time location tracking means thatparts, assemblies, and products can be tracked through each step in the process. Ifan assembly takes too long to progress through a step (cycle time), then there isclearly a problem. However, an increase in the time between steps (dwell time) isjust as important, as this represents a flow problem -- standing interim stock andtied-up capital -- and increases the total cycle time for the entire line. All of thisinstrumentation also makes it easy to track long-term trends and make moreaccurate predictions on stock consumption and throughput.

The next section looks at how sensor event processing can help in process flowexecution.

Solution architecture

Figure 1. Smarter manufacturing reference architecture




Elements of this healthcare reference architecture (Figure 1) include:

• Data captureWhen implementing a smart manufacturing system, the Data Capture andDelivery component is the main integration point for connected devices,being the first stop in the chain of processing between the sensor deviceand the WebSphere Sensor Events server. Data Capture and Delivery isa component of WebSphere Sensor Events and consists of a softwarestack that resides on or near the sensor device. It provides a frameworkto build device adapters for device communications, and also provides alocation for business logic with low latency requirements. It also activelymanages devices such as scanners, conveyor belts, diverters, and so on.In a smart manufacturing system, sensors will monitor the movement ofparts, containers, and personnel as they move through the manufacturingprocess. Data Capture and Delivery provides a framework to normalize,filter, smooth, and summarize the data, eliminating extraneous data orcompressing the data volume to reduce the bandwidth and server load. Italso buffers the data, handling unreliable communications so thatapplication logic doesn’t have to.

• WebSphere Sensor EventsBecause it was discussed in earlier articles in this series, and its role inthe solution architecture does not change for a smarter manufacturingsolution, the function and purpose of the WebSphere Sensor EventsGateway component will not be discussed here. However, the role andservices provided by WebSphere Sensor Events does change. In a




smarter manufacturing solution, WebSphere Sensor Events could provideservices such as filtering, smoothing, zone determination, and assetvisualization. When tracking mobile assets as part of a manufacturingprocess, the location of the asset is typically forwarded through DataCapture and Delivery from the location tracking device, either using arelative location coordinate reference (such as an X, Y, Z reference for adefined origin point on the manufacturing floor) or a reference to anestablished physical space, such as a workstation, room, floor, or zone. Inthe case of relative coordinate references, WebSphere Sensor Eventscould be used to resolve those reference points into known physicalspaces. In the example presented below, it is assumed that asset locationevents are already "zone" determined. Therefore, you will see how theselocation events can be integrated with IBM WebSphere Business Eventsand IBM WebSphere Business Monitor to derive business value.

• WebSphere Business EventsWebSphere Business Events provides the ability to discover importantpatterns in the flow of parts, containers, and personnel during themanufacturing process. It can provide alarms if all the necessary parts orpersonnel are not at the required station at the required time. Othercustom rules can be based on things like dwell time; for example, if a partor person is at a workstation for too long, indicating there is a problemand someone else needs to be dispatched. WebSphere Business Eventsprovides the framework to define and execute a full set of rules thatmanage and monitor these kinds of manufacturing processes.

• WebSphere Business MonitorWebSphere Business Monitor provides the facilities for manufacturingsupervisors to easily monitor WebSphere Business Events or WebSphereSensor Events output for suspicious trends. Monitoring can be in the formof various dashboards, charts, or graphs. Manufacturing supervisors canthen use this data for decision support to optimize the process, inventorycontrol, and personnel scheduling. The data from WebSphere BusinessMonitor can be forwarded to other systems or to IBM Cognos® for furtheranalysis using data from other systems.

• IBM Cognos Business IntelligenceThe location events forwarded from Data Capture and Delivery havearrived in the WebSphere Sensor Events server and have been persisted.WebSphere Business Events has monitored the events based on therequired rule set. WebSphere Business Monitor has the location of all themanufacturing resources in a dashboard. Although the sensor dataprovides supervisors a wealth of knowledge that was not previouslyavailable, you know that the sensor data alone is not complete enough for




supervisors to perform analysis on process efficiencies. In order forsupervisors to be able to provide actionable recommendations for processoptimization, you must have the ability to provide analytics capabilities tothe solution. IBM Cognos is the platform that provides the necessaryanalytics for manufacturing supervisors to give fast but accuraterecommendations based on production schedules and outputperformance.

Leveraging real time location tracking in a manufacturing line

Real time locating systems (RTLS) use wireless technologies such as Wi-Fi,ultra-wideband, RFID, Bluetooth, and GPS to identify and track the location of itemsor people in real time. In an RTLS solution, the item or person being tracked typicallyhas some means of emitting a radio signal. A battery powered tag, for example,might be attached to the item or person being tracked. The emitted radio signals arereceived by the RTLS solution’s locating component and interrogated to determinethe location of the item or person being tracked. RTLS solutions identify an item’slocation using dimensional coordinates or zonal information.

A common RTLS implementation uses battery-powered tags with an onboard radiotransmitter, along with a matrix of location sensors that are deployed throughout thearea being monitored. The radio signals emitted by the tags are received by thesensors and relayed to the location component, which uses a variety ofmethodologies to calculate the location of the tag. These calculations might bebased on visibility (whether the tag is in the sensor’s line of sight), the signalstrength, or the amount of time it takes the signal to travel from the tag to the sensor.Regardless of the method used, the location component is responsible fordetermining the location of the tag and making this information available toapplications for consumption. A consuming application might, for example, definethe zones that a tagged asset is permitted to be in and trigger an alarm when itappears outside those zones.

In the sample scenario presented next, an RTLS solution is used to track thelocation of an automobile as it moves along an assembly line. The assembly line isdivided into five work zones. The RTLS solution uses a matrix of sensors, one foreach zone, to receive radio signals emitted from an active RFID tag affixed to theautomobile’s frame. The sensors pass the received radio signals to a locationcomponent that determines which zone the automobile is in. The locationcomponent is configured such that it generates an event only when the automobileenters a work zone. These events are used to determine the required parts and thework to be performed on the automobile in a given work zone. The line supervisorcan then monitor the flow of the vehicle through this five step manufacturing processusing a simple Business Monitor Business space display. The work zones used inthis scenario are:




• Frame assembly

• Side panel assembly

• Body assembly

• Paint work

• Inspection.

Sample scenario

To illustrate smarter manufacturing, this example tracks an automobile as it movesalong an assembly line from work zone to work zone. The two important aspects ofthis scenario are to:

• Display the automobile's current location (by zone).

• Display an error if the automobile skips a zone (after all, manufacturing isusually a serial process).

To fulfill this scenario, the following software stack is used:

• WebSphere Sensor Events

• WebSphere Business Events

• WebSphere Business Monitor.

To show the automobile's status, a GUI application is used to display theautomobile's current zone and whether the automobile's movement along theassembly line is valid.

Figure 2 shows how events flow from creation through the software stack and ontothe display:

1. As the automobile moves along the assembly line, an active RFID tagtransmits its location. An RTLS detects the RFID tag's movements anddetermines the zone. Upon entering a zone, the RTLS sends a zone entryevent to WebSphere Sensor Events.

2. WebSphere Sensor Events receives the event, transforms it, and sends itto WebSphere Business Events.

3. WebSphere Business Events evaluates rules to implement the scenario.The sample includes two rules: one to forward a zone entry event, and




one to decide whether the automobile has missed a manufacturing step.The results are sent to WebSphere Business Monitor.

4. With WebSphere Business Monitor, you create monitor modelapplications. These applications collect metrics and key performanceindicators (KPI) from incoming events. The metrics and KPI values areavailable for display in a dashboard.

5. The dashboard environment, which is part of WebSphere BusinessMonitor, provides a flexible system for constructing a GUI from themetrics and KPI.

Figure 2. Event flow

So, the event starts by moving the automobile along the assembly line and ends withan updated dashboard GUI.

Implementing the sample

To run the sample application, you need to perform these steps to satisy theprerequisites:

1. Install WebSphere Sensor Events V6.2 (and its prerequisite software) intoits own IBM WebSphere Application Server profile.

2. Install WebSphere Business Monitor V6.2 into its own WebSphereApplication Server profile, or into the same profile containing WebSphereSensor Events.

3. Install IBM Rational® Application Developer V7.5.1.

4. Install the WebSphere Business Monitor Toolkit V6.2 into RationalApplication Developer.

5. Create the connection between IBM WebSphere MQ (which is installedwith WebSphere Sensor Events) and WebSphere Business Monitor byfollowing these steps.http://www.ibm.com/developerworks/library/i-bam618/ Do not enablesecurity on the WebSphere MQ link.

You will need values for these required parameters:




• IP address of server running WebSphere Sensor Events.

• Default application port of profile running WebSphere Sensor Events.

• Host name of server running WebSphere Sensor Events.

• IP address of server running WebSphere Business Monitor.

• Default application port of profile running WebSphere Business Monitor.

• WebSphere Business Events login credentials (default user ID/passwordis admin/admin).

Setting up the sample

1. Start the servers.Start the WebSphere Application Server profiles for both WebSphereSensor Events and WebSphere Business Monitor.

2. Customize WebSphere Sensor Events.WebSphere Sensor Events includes a library of Reusable Components(RUCs), each of which performs a specific function. These RUCs processmessages retrieved from the WebSphere Application Server SI (ServiceIntegration) bus. The RUC responsible for sending messages toWebSphere Business Events is called WBERUC. In order for WBERUCto receive this sample application's message, the message selector of theJMS activation specification must be modified:

a. In a Web browser, navigate to the WebSphere Application Serveradministrative console (for example, http://wseServer:9060/admin).

b. Select Resources > JMS > Activation specifications.

c. Scroll through the list of activation specifications and selectWBERUCAS.

d. Change the message selector to: ibmse LIKE'%SmarterManufacturing/ZoneEntry'.

e. Click OK.

f. Save the configuration changes.

3. Deploy the WebSphere Business Events project.To send the output from WebSphere Business Events to WebSphereBusiness Monitor, the properties of the WebSphere Business Event's




actions must be updated with the current server's host name:

a. Start the WebSphere Business Events Design Data application.(WebSphere Business Events is installed with WebSphere SensorEvents.)

b. Open the sample WebSphere Business Events project calledSmarterManufacturing_WBEProject.xml.

c. Delete any existing WebSphere Business Events objects from therepository:

1. Select Tools > Repositories.

2. Select the WBE Runtime tab.

3. Enter the host name and IP address of the profile runningWebSphere Sensor Events.

4. Click OK.

5. Enter the WebSphere Business Events credentials.

6. Click Login.

7. Select all assets.

8. Click Delete.

9. Confirm the delete action.

10. Click Close to exit the Repository window.

d. Update the ZoneAlert_Action properties:

1. In the Touchpoints window, expand WebSphere SensorEvents Server.

2. Right-click ZoneAlert_Action and select ActionProperties.

3. Select the Connection tab.

4. Click Configure.

5. Click Provider.




6. For the URL, enter the IIOP URL for the server runningWebSphere Business Monitor (for example,iiop://wbmServer:2810).

7. Click OK to close the Provider window.

8. Click OK to close the Message Queue Action Connection.

9. Click OK to close the Action Properties window.

e. Update the properties for ZoneEntry_Action following the sameprocess you used in step 3d to update the ZoneAlert_Actionproperties.

f. Deploy the WebSphere Business Events objects:

1. Select Tools > Repositories.

2. Select the Project tab.

3. Select all assets.

4. Click Add In.

5. Click Close to exit the Repository window.

g. Save the WebSphere Business Events project and exit the DesignData application.

4. Reload the repository assets in WebSphere Business Events.After deploying the repository assets, WebSphere Business Events mustbe restarted in order to pick up any new assets:

a. In a Web browser, navigate to the WebSphere Business Eventsadministrative console (for example, http://wseServer:9080/wbe).

b. Login using the WebSphere Business Event credentials; beforeclicking Login, change the Tool list to Administration.

c. Click the Console icon in the upper-left corner of the WebSphereBusiness Events admin console.

d. Click the Reload icon in the upper-right corner of the consolewindow.

e. Wait for a message indicating that the repository was successfully




loaded.

f. Exit from the WebSphere Business Events admin console.

5. Update the XML name space.The XML name space in the model application's inbound events is veryimportant. The name space must match exactly what is sent byWebSphere Business Events:

a. Start Rational Application Developer and import the projects fromthe SmarterManufacturing_RAD.zip project interchange fileincluded with this article.

b. Go to the Business Monitoring perspective.

c. In the Project Explorer view, expand Smarter Manufacturing >Event Definitions.

d. Open file Action_ZoneAlert_Action.xsd in the XSD editor.

e. Change all occurrences of wse62 to the host name of the serverrunning WebSphere Sensor Events.

f. Close the XSD editor, saving the changes.

g. Ignore any errors; they will be corrected later.

h. Repeat steps 5d through 5g for file Action_ZoneEntry_Action.xsd.

i. In the Project Explorer view, expand Smarter Manufacturing >Monitor Models.

j. Open file Smarter Manufacturing Model.mm in the monitor modeleditor.

k. Select the Smarter Manufacturing Model.mm tab at the bottom ofthe editor window.

l. Change all occurrences of wse62 to the host name of the serverrunning WebSphere Sensor Events.

m. Close the monitor model editor saving the changes.

6. Generate the J2EE™ model application.After updating the XML name space, generate the J2EE classes thatmake up the model application:




a. In Rational Application Developer, right-click SmarterManufacturing Model.mm and select Generate Monitor J2EEProjects.

b. Click Finish and wait for the process to complete.

7. Export the J2EE model application.After generating the J2EE model application, create a J2EE EAR filecontaining the model application:

a. In Rational Application Developer, select File > Export > Java EE> EAR file.

b. Click Next.

c. Select the Smarter Manufacturing Model Application EARproject.

d. Enter a destination.

e. Click Finish.

8. Install the J2EE model application:Install the J2EE model application to the WebSphere Application Serverprofile running WebSphere Business Monitor:

a. In a Web browser, navigate to the WebSphere Application Serveradministrative console.

b. Select Applications > Install New Application and install themodel application J2EE EAR.

c. When done, select Applications > Monitor Models.

d. For the Smarter Manufacturing Model, click the version link.

e. Click Manage schema.

f. Select Run script to delete the schema during uninstallation.(This step is necessary to make cleanup easier when the J2EEapplication is uninstalled.)

g. Click OK.

9. Install the business space.




The business space is the Web-based user interface that containsdashboards to display the result of a model application. A business spacethat contains a dashboard showing the tag's current zone is available inthe sample application:

a. In a Web browser, open the WebSphere Business MonitorBusiness Space (for example,http://wbmServer:9081/BusinessSpace).

b. Click Manage Business Spaces.

c. Click the Import Business Space toolbar icon.

d. Import the file SmarterManufacturing_BusinessSpace.data.

e. Click developerWorks to access the newly ported BusinessSpace.

f. You can display the model data using an Instances widget includedin the Smarter Manufacturing page.

10. Restart the server profiles.To pick up all the configuration changes you made, you need to restartthe server profiles:

a. Restart the WebSphere Application Server profile runningWebSphere Sensor Events.

b. Restart the WebSphere Application Server profile runningWebSphere Business Monitor.

11. Start the connectors.Events sent outbound from WebSphere Business Events are handled byanother application called Connectors. Start the Connectors applicationbefore continuing.

Running the sample application

The sample application includes a Web-based GUI to simulate moving theautomobile through the assembly line. When you run the application, you can simplydrag and drop the automobile icon onto different points along the assembly line.Dropping the automobile sends an event to WebSphere Sensor Events to begin theevent flow though the system.




To run the GUI simulator:

1. Unzip SmarterManufacturing_WorkFlowSimulator.zip, included withthis article.

2. Open WorkFlowSimulator\WebContent\WorkFlowSimulator.html.

3. Drag and drop the automobile along the assembly line.

Figure 3. Assembly line GUI

To view the output of the dashboard:

1. In a Web browser, open the WebSphere Business Monitor BusinessSpace (for example, http://wbmServer:9081/BusinessSpace).

2. Select the developerWorks Business Space.

3. Select the Smarter Manufacturing dashboard page (Figure 4).

4. The dashboard page updates to display the result of moving theautomobile:

• Zone: Displays the name of the zone that the automobile was movedinto.

• Status: Displays either "OK" (zone was not skipped) or "Error!" (zonewas skipped).

Be patient; the page may take several seconds to refresh.

Figure 4. Smarter manufacturing Web page




Summary

You can imagine that this demo would only be the first step in providing visibility. Asdiscussed earlier, the next step would be providing the same location awareness topersonnel, tools, and equipment at these stations, followed by using WebSphereBusiness Events to make sure all the required composite resources are available ateach station. If you wish to continue this exercise, you can add personnel and toolsdata to this sample application. The source is provided in the included download file.

In conclusion, this article described how process flow execution can be assisted withreal time location asset tracking. Although this was discussed in the context oftracking assets through a manufacturing process, real time asset tracking can beused in a wide variety of process flow scenarios. Similar needs exist in healthcare,aerospace & defense, energy, transportation, and utilities sectors.

In general, benefits that can be realized through real time asset tracking include:

• Improving asset utilization and employee productivity by providing thecurrent location of existing resources.

• Reducing capital expense by reducing asset loss, shrinkage, andresulting over-purchasing of assets.




• Enforcing business rules and regulatory requirements with location-basedevents and an automatically-triggered workflow.

• Minimizing downtime by dispatching the right resource with the right toolsto the right location.

• Preventing asset shortages, and improving audit and compliancecapabilities.

• Providing real time location visualization.

• Providing KPIs through analytics, and visibility related to inventory,utilization, and exceptions.




Downloads

Description Name Size Downloadmethod

Code sample SmarterManufacturing.zip 299 KB HTTP

Information about download methods



http://public.dhe.ibm.com/software/dw/wes/techjournal/1003_hanis/SmarterManufacturing.zip

http://www.ibm.com/developerworks/library/whichmethod.html


Resources

• More in this series

• WebSphere Sensor Events product information

• WebSphere Sensor Events Information Center

• IBM Sensor Solutions

• Service Oriented Architecture

• WebSphere Business Process Management product information

• Continua Health Alliance

• IBM developerWorks WebSphere

About the authors

Tim HanisTim Hanis is the lead architect in WebSphere Sensor Events development at IBM inResearch Triangle Park, NC. He has led a number of development projects withinIBM and has extensive experience helping customers solve business problems withWebSphere products.

Allen SmithAllen Smith is a Senior Certified IT Specialist in IBM's Application and IntegrationMiddleware Software group in Research Triangle Park, North Carolina. He works withbusiness partners to design and implement sensor based solutions using WebSphereSensor Events. You can contact Allen at [email protected].

John SenegalJohn Senegal is the lead developer for WebSphere Sensor Events Server at IBM inResearch Triangle Park, NC. He has broad experience working with IBM customersand partners building solutions using IBM tooling and middleware.



http://www.ibm.com/developerworks/views/websphere/libraryview.jsp?sort_by=&show_abstract=true&show_all=&search_flag=&product_by=-1&topic_by=-1&type_by=All+Types&search_by=Smarter+Planet+solutions+with+sensor+monitoring

http://www.ibm.com/software/integration/sensor-events/index.html

http://publib.boulder.ibm.com/infocenter/pvcsensa/v6r2m0/index.jsp

http://www.ibm.com/sensors

http://www.ibm.com/software/solutions/soa/

http://www.ibm.com/software/info1/websphere/index.jsp?tab=products/businessint

http://www.continuaalliance.org/

http://www.ibm.com/developerworks/websphere/



Ken GreenleeKen Greenlee is an Advisory Software Engineer with the WebSphere Sensor Eventsteam at IBM in Research Triangle Park, NC. He has extensive Java/WebSphereexperience and is responsible for many components within the WebSphere SensorEvents server product. He has worked with customers to create solutions based uponthe WebSphere Sensor Events software stack. He has reached the third patentplateau, most on RFID technologies.

Bruce HyreBruce Hyre is a Senior Software Engineer with the IBM Sensor Solutions inResearch Triangle Park, North Carolina. He specializes in the design and integrationof WebSphere Sensor Events with business partners and device manufacturers.




smarter planet solutions with sensor monitoring, part 4: asset

Documents