Unisys Corporation

Global Traffic Technologies, LLC

Corium International, Inc.

David R Johnson

James R McBreen

Charles R Caldarale

Merwin H Alferness

Wayne D Ward

Steven Richard Klemm

David C Johnson

David A Goiffon

Gerald E Hartmann

Joseph P Kerzman

Hans Christian Mikkelsen

Kevin Eichhorst

Michael G Marcoux

Ralph E Sipple

Peter B Criswell

Joey L Erickson

Robert Marion Malek

Mark D Aubel

David John Edwardson

Peter John Hancock

James S Sebesta

Richard M Shelton

Nicole Maria Montgomery

Patrick Keenan Cosgrove

James W Douglas

Donna J Plunkett

Francis A Stephens

Donn B Baker

Jerome J Witalka

Kevin Clare Eichhorst

Steven R Klemm

An adhesive device used as a wound dressing, ingredient delivery device or IV hold-down in which inadvertent edge release of these devices along the periphery of the polymeric film layer is minimized when the handling layer, which is adhered to the polymeric film layer, is removed after application of the polymeric film layer to the patient.

Wound dressing, ingredient delivery device and IV hold-down, and method relating to same

Adhesive devices used as wound dressings, ingredient delivery devices and IV hold-downs include a handling layer comprised of a layer of conductive material and at least one layer of non-conductive material, adhered to the non-adhesive coated side of an adhesive coated polymeric film layer, by an electrostatic charge, rather than by an adhesive.

Wound dressing, ingredient delivery device and IV hold-down incorporating a statically retained handle member

Approaches for monitoring traffic signal preemption at one or more intersections. According to one embodiment, a road map that includes a plurality of roads and intersections is displayed with a computer system. Preemption data periodically received by the computer system from at least one preemption controller at a respective intersection is used to update the road map. In response to the preemption data, the road map is updated to include a traffic signal icon at the respective intersection and a vehicle icon at a location on the map corresponding to a location of a vehicle transmitting a preemption request as indicated by the preemption data.

Monitoring traffic signal preemption

Controlling a traffic signal phase at one or more intersections. A control system at an intersection is configured to operate in one of a first mode or a second mode. While operating the controller in the first mode, in response to a transit priority signal received by the control system from a vehicle assigned transit priority, a green phase of the traffic signal is extended in favor of the vehicle assigned transit priority. While operating the control system in the second mode, in response to a transit priority signal received by the control system from the vehicle assigned transit priority, a current non-green phase of the traffic signal is preempted to a green phase in favor of the vehicle assigned transit priority.

Control of traffic signal phases

Management of traffic signal preemption control equipment. In one approach, logged preemption data is periodically read from each of a plurality of intersections having respective preemption controllers for preempting traffic signals at the intersections. The logged preemption data at an intersection describes operational states of the preemption controller and each vehicle control unit that submitted a preemption request at the intersection and data describing each individual preemption request. The logged preemption data read from the plurality of intersections are stored in a database. The database is monitored for data indicative of changes in operational status of the traffic signal preemption control equipment. In response to the data indicating a change in operational status, data descriptive of the change are output.

Monitoring and diagnostics of traffic signal preemption controllers

Managing traffic signal preemption data accumulated at a plurality of intersections. In one approach a method includes reading the preemption data stored at each of the intersections. The preemption data includes for each preemption request an emitter code, and a date and a time the preemption request was submitted. The preemption data read from the intersections are stored in a database, and each emitter code is associated with a vehicle name in the database. Selected preemption data and associated vehicle names are read from the database in response to user input, and the selected preemption data and associated vehicle names are displayed. The database further stores data identifying the intersection from which the preemption data was read.

Monitoring management and presentation of preemption control data of centrally managed traffic signals

Managing traffic signal preemption at a plurality of intersections. In one approach a security level code that specifies one of a plurality of security levels for at least one jurisdiction is input. The security level controls which emitter codes are allowed to preempt traffic signals at the intersections in the jurisdiction. A set of emitter codes for the plurality of intersections in the jurisdiction is determined in response to the security level code. The set of emitter codes is downloaded to a plurality of preemption controllers at the plurality of intersections in the jurisdiction. Each preemption controller accepts a preemption request only if the preemption request contains an emitter code indicated by the downloaded set of emitter codes as being allowed to preempt traffic signals at the intersections in the jurisdiction.

Centralized management of preemption control of traffic signals

Wound dressing, ingredient delivery device and IV hold-down incorporating a statically retained handle

In a computer system a system of exchanging tokens for queue banks is created that permits a requester to directly specify which queue bank is wanted. Only the desired queue bank is withdrawn from a queue bank repository to accomplish this and no sorting or FIFO handling of queue banks is needed. The system uses a schema similar to a coat check room, where the requester is given a token when the requestor wants to deposit a queue bank into the queue bank repository. The queue bank repository returns the queue bank when the token is returned by the requester. In its most efficient form, two machine-level instructions handle the entire operation, a withdraw instruction and a deposit instruction.

Queue bank repository and method for sharing limited queue banks in memory

A tool management system and interface for a disparate set of data processing tools is disclosed. A main tool menu allows selected tools to be launched so that each tool populates a respective window. A tool is selected by choosing an associated window as the currently-active window. Next, a list of all data items that are available for processing by the tool set may be obtained. A data item that is to undergo processing may be selected. A user interface provides a list of all operations that may be used to process the selected data item, including those operations that are supported by the currently-selected tool, and those operations that are not supported by the selected tool. Following selection of the operation, processing of the selected data item is completed by automatically invoking the appropriate tool.

System and method for managing a suite of data management tools

A process-driven object management system for managing data and code modules is disclosed. The object management system includes a repository that stores objects, wherein ones of the objects referred to as &ldquo;Asset elements&rdquo; each describe a respective code or data module. The object management system includes a set of scripted tools for performing renovation, transformation, and code development tasks on the code and data modules. According to one aspect of the invention, the tool invocation constructs are stored as objects in the repository, such that some of the same object management tools and automated repository interface functions used to manage the Asset element can also be used to manage and veiw the tool objects.

Process-driven tool interface for an object management system

A computer-implemented system and method for allowing users to interactively develop search queries is provided. The system performs query development utilizing a hierarchical concept tree stored in memory, wherein the nodes of the concept tree are concepts that describe various search topics. Parent/child relationships are created between the concepts, with children concepts describing sub-categories of a parent concept, and so on. Any concept at any level in the tree structure may be related to one or more character strings descriptive of the related concept. Query development is performed by traversing the various relationships in the hierarchical tree structure to selectively add related character strings to a potential query. According to one embodiment, the user is allowed to control the manner and extent of the traversal, and is further allowed to de-select any located concepts and character strings for further use in query development. According to another embodiment, traversal of the tree is completed according to user specification, with only limited user intervention required to select or de-select the various located character strings for inclusion in a query string. Yet another embodiment allows all query string development to be fully automated based on parameters specifying the extent of the concept tree traversal. After traversal of the tree structure is completed, the located character strings that remain selected based on user specifications are added to a query string. The query string may further be modified to include logical operations. The string may be used to manually or programmatically invoke a wide variety of tools for use in performing searches of text documents, file systems, or a collection of web pages. The system allows the contents and structure of the hierarchical concept tree to be modified by the user. Both the concepts and character strings included in the hierarchical tree may be edited by the user to include search terms tailored to specific search requirements. Additionally, relationships existing between two concepts, or between a concept and a character string, may be added, deleted, or modified to thereby allow the user to control the manner in which query development proceeds.

System and method for developing a selectably-expandable concept-based search

A system for maintaining an object repository within an object management system where the objects are software constructs and the system provides a set of tools for creating packages of the objects that can be reused as well as monitored as they are changed or recombined. The packages themselves become new objects for the repository to store. The set of relationships within a package is also stored as are any relationships between any of the objects within the object management system object repository.

System and method for defining and managing reusable groups software constructs within an object management system

An automated development system which allows developers to more easily incorporate functionality from enterprise-based On-Line Transaction Processing (OLTP) services within an application running on a DCOM-based platform. View files (which describe how parameters will be provided to and received from an OLTP service) are transferred from the enterprise OLTP system to a DCOM environment. These view files and an associated set of interactively supplied user parameters are provided as input to a function builder utility (DGateAce) which generates function files and Interface Definition Language files as output. These output files simplify the creation of DCOM Client and Server modules which enable a DCOM application to communicate directly with an enterprise OLTP service

Automated development system for developing applications that interface with both distributed component object model (DCOM) and enterprise server environments

Growing community of inventors

Oakdale, MN, United States of America

David R Johnson