U.S. patent application number 14/324609 was filed with the patent office on 2016-01-07 for systems and methods for utilizing sensor informatics to determine insurance coverage and recoverable depreciation for personal or business property.
This patent application is currently assigned to United Services Automobile Association. The applicant listed for this patent is Michael J. Allen, Cleburne R. Burgess, Ramsey Devereaux, David S. Franck, Spencer Read, Kathleen L. Swain, Daniela Wheeler. Invention is credited to Michael J. Allen, Cleburne R. Burgess, Ramsey Devereaux, David S. Franck, Spencer Read, Kathleen L. Swain, Daniela Wheeler.
Application Number | 20160005130 14/324609 |
Document ID | / |
Family ID | 55017312 |
Filed Date | 2016-01-07 |
United States Patent
Application |
20160005130 |
Kind Code |
A1 |
Devereaux; Ramsey ; et
al. |
January 7, 2016 |
SYSTEMS AND METHODS FOR UTILIZING SENSOR INFORMATICS TO DETERMINE
INSURANCE COVERAGE AND RECOVERABLE DEPRECIATION FOR PERSONAL OR
BUSINESS PROPERTY
Abstract
A computer device and method for processing data to determine
insurance coverage for objects and associated recoverable
depreciation based upon informatic data. Informatic data is
received from one or more informatic sensor devices relating to one
or more objects associated with an insured property. Computer
analysis is performed on the received informatic data to determine
an insurance claim event for at least one of the one or more
objects associated with the insured property. Computer analysis is
also performed on the received informatic data to determine if
recoverable depreciation is applicable to a determined insurance
claim.
Inventors: |
Devereaux; Ramsey; (San
Antonio, TX) ; Allen; Michael J.; (San Antonio,
TX) ; Read; Spencer; (Helotes, TX) ; Franck;
David S.; (San Antonio, TX) ; Wheeler; Daniela;
(Boerne, TX) ; Swain; Kathleen L.; (Peoria,
AZ) ; Burgess; Cleburne R.; (Fair Oaks Ranch,
TX) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Devereaux; Ramsey
Allen; Michael J.
Read; Spencer
Franck; David S.
Wheeler; Daniela
Swain; Kathleen L.
Burgess; Cleburne R. |
San Antonio
San Antonio
Helotes
San Antonio
Boerne
Peoria
Fair Oaks Ranch |
TX
TX
TX
TX
TX
AZ
TX |
US
US
US
US
US
US
US |
|
|
Assignee: |
United Services Automobile
Association
San Antonio
TX
|
Family ID: |
55017312 |
Appl. No.: |
14/324609 |
Filed: |
July 7, 2014 |
Current U.S.
Class: |
705/4 |
Current CPC
Class: |
G06Q 10/20 20130101;
G06Q 40/08 20130101; G06Q 40/025 20130101; G06K 9/00536 20130101;
G06Q 2220/00 20130101; G06K 9/00637 20130101 |
International
Class: |
G06Q 40/08 20120101
G06Q040/08 |
Claims
1. A computer system for processing data, comprising: a memory
configured. to store instructions; a processor disposed in
communication with the memory, wherein the processor upon execution
of the instructions is configured to: receive informatic data from
one or more informatic sensor devices relating to one or more
objects associated with an insured property; perform analysis on
the received informatic data to determine an insurance claim event
for at least one of the one or more objects associated with the
insured property; and perform analysis on the received informatic
data to determine if recoverable depreciation is applicable to a
determined insurance claim.
2. A computer system as recited in claim 1, wherein the processor
upon execution of the instructions is further configured to:
receive an insurance policy associated with the insured property;
analyze the insurance policy to identify one or more relevant
sections of the insurance policy relating to the determined
insurance claim event regarding the at least one object; and apply
predefined business rules using the determined insurance claim
event and relevant sections of the insurance policy to determine if
the insurance policy supports an insurance claim regarding the
determined insurance claim event.
3. A computer system as recited in claim 2, wherein the processor
upon execution of the instructions is further configured to provide
notification to an insured that identifies an insurance claim for
the determined insurance claim event that is supported by the
insurance policy wherein the notification further identifies the
determined applicability of recoverable depreciation for an
insurance claim.
4. The computer system as recited in claim 1, wherein the processor
upon execution of the instructions is further configured to
determine one or more third party vendors regarding repairs to be
made regarding the determined insurance claim event.
5. The computer system as recited in claim 4, wherein the processor
upon execution of the instructions is further configured to
schedule repair services for the at least one object from one or
more of the determined third party vendors.
6. The computer system as recited in claim 1, wherein the processor
upon execution of the instructions is further configured to
identify product documentation relating to the at least one
object.
7. The computer system as recited in claim 6, wherein the product
documentation includes a service manual related to the at least one
object.
8. The computer system as recited in claim 1, wherein at least one
camera sensor device detects indicia associated with the at least
one object located in the insured property wherein analysis of the
indicia determines insurance coverage for the at least one
object.
9. The computer system as recited in claim 8, wherein the indicia
is provided by an insurance company providing insurance coverage
for the at least one object.
10. A computer system as recited in claim 1, wherein analysis for
determining recoverable depreciation for the at least one object
includes: determining if an insured has replaced an object
regarding an insurance claim; and determining the value or
replacement cost of the replaced item.
11. A computer system as recited in claim 1, wherein determining
recoverable depreciation includes: determining if an insured has
repaired an object regarding an insurance claim; and determining
the value of the repaired object or cost to repair or restore the
repaired item to its pre-loss condition.
12. A computer system for processing data, comprising: a memory
configured to store instructions; a processor disposed in
communication with the memory, wherein the processor upon execution
of the instructions is configured to: receive informatic data from
one or more informatic sensor devices relating to one or more
objects associated with an insured property; perform analysis on
the received informatic data to determine an insurance claim event
for at least one of the one or more objects associated with the
insured property; receive an insurance policy associated with the
insured property; analyze the insurance policy to identify one or
more relevant sections of the insurance policy relating to the
determined insurance claim event regarding the at least one object;
apply predefined business rules using the determined insurance
claim event and relevant sections of the insurance policy to
determine if the insurance policy supports an insurance claim
regarding the determined insurance claim event; and perform
analysis on the received informatic data to determine if
recoverable depreciation is applicable to a determined insurance
claim.
13. The computer system as recited in claim 12, wherein the
processor upon execution of the instructions is further configured
to determine one or more third party vendors regarding repairs to
be made regarding the determined insurance claim event.
14. The computer system as recited in claim 13, wherein the
processor upon execution of the instructions is further configured
to schedule repair services for the at least one object from one or
more of the determined third party vendors.
15. The computer system as recited in claim 11, wherein the
processor upon execution of the instructions is further configured
to identify product documentation relating to the at least one
object.
16. The computer system as recited in claim 15, wherein the product
documentation includes a service manual related to the at least one
object.
17. A computer system as recited in claim 12, wherein analysis for
determining recoverable depreciation for the at least one object
includes: determining if an insured has replaced an object
regarding an insurance claim; and determining the value or
replacement cost of the replaced item.
18. A computer system as recited in claim 12, wherein determining
recoverable depreciation includes: determining if an insured has
repaired an object regarding an insurance claim; and determining
the value of the repaired object or the cost to repair or restore
the repaired item to its pre-loss condition.
19. A computer implemented method for processing insurance data
comprising: receive, by processor, informatic data from one or more
informatic sensor devices relating to one or more objects
associated with an insured property; perform, by processor,
analysis on the received informatic data to determine an insurance
claim event for at least one of the one or more objects associated
with the insured property; receive, by processor, an insurance
policy associated with the insured property; analyze, by processor,
the insurance policy to identify one or more relevant sections of
the insurance policy relating to the determined insurance claim
event regarding the at least one object; apply, by processor,
predefined business rules using the determined insurance claim
event and relevant sections of the insurance policy to determine if
the insurance policy supports an insurance claim regarding the
determined insurance claim event; and perform analysis on the
received informatic data to determine if recoverable depreciation
is applicable to a determined insurance claim.
20. The computer implemented method as recited in claim 19, wherein
the object is an appliance.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. patent application
Ser. Nos.: 61/866,779 filed Aug. 16, 2013; 61/926,093 filed Jan.
10, 2014; 61/926,091 filed Jan. 10, 2014; 61/926,095 filed Jan. 10,
2014; 61/926,098 filed Jan. 10, 2014; 61/926,103 filed Jan. 10,
2014; 61/926,108 filed Jan. 10, 2014; 61/926,111 filed Jan. 10,
2014; 61/926,114 filed Jan. 10, 2014; 61/926,118 filed Jan. 10,
2014; 61/926,119 filed Jan. 10, 2014; 61/926,121 filed Jan. 10,
2014; 61/926,123 filed Jan. 10, 2014; 61/926,536 filed Jan. 13,
2014; 61/926,541 filed Jan. 13, 2014; 61/926,534 filed Jan. 13,
2014; 61/926,532 filed Jan. 13, 2014; 61/943,897 filed Feb. 24,
2014; 61/943,901 filed Feb. 24, 2014; 61/943,906 filed Feb. 24,
2014; and 61/948,192 filed Mar. 5, 2014 which are each incorporated
herein by reference in its entirety.
FIELD OF THE INVENTION
[0002] The disclosed embodiments generally relate to a method and
computerized system for collecting and utilizing sensor data, and
more particularly, to utilizing sensor informatics to determine
insurance coverage for personal or business property associated
with an insured property and associated recoverable
depreciation.
BACKGROUND OF THE INVENTION
[0003] Smart house functionality is a maturing space, but the
opportunity for insurance companies remains largely untapped. Thus,
the terms of insurance policies, such as homeowner insurance
policies, may not be reflective of the true nature of the risks
being insured.
[0004] Accordingly, there is an unmet need for measuring
information relating to an insured risk, such as a residence or
structures located on the residence premises, and utilizing that
information to make appropriate modifications to insurance policy
terms, such as the deductible amount.
SUMMARY OF THE INVENTION
[0005] The purpose and advantages of the below described
illustrated embodiments will be set forth in and apparent from the
description that follows. Additional advantages of the illustrated
embodiments will be realized and attained by the devices, systems
and methods particularly pointed out in the written description and
claims hereof, as well as from the appended drawings.
[0006] To achieve these and other advantages and in accordance with
the purpose of the illustrated embodiments, in one aspect described
is a computer device and method for processing insurance claim data
to determine insurance coverage for personal or business property
and associated recoverable depreciation based upon informatic data.
Informatic data is received from one or more informatic sensor
devices relating to one or more items associated with an insured
property and computer analysis is performed on the received
informatic data to determine an insurance claim event for at least
one of the one or more objects associated with the insured
property. Preferably, electronic data relating to an insurance
policy associated with the insured property is also received and
analyzed to identify one or more relevant sections of the insurance
policy relating to the determined insurance claim event regarding
the at least one item. Predefined business rules are preferably
utilized using the determined insurance claim event and relevant
sections of the insurance policy to determine if the insurance
policy supports an insurance claim regarding the determined
insurance claim event. Computer analysis is preferably also
performed on the received informatic data to determine if
recoverable depreciation is applicable to a determined insurance
claim.
[0007] The recoverable depreciation may be calculated by
determining if an insured has replaced an object regarding an
insurance claim and determining the value of the replaced item.
Alternatively, the recoverable depreciation may be calculated by
determining if an insured has repaired an item regarding an
insurance claim and determining the value of the repaired item or
the cost of the repairs.
[0008] In other aspects, electronic notification is provided to an
insured that identifies an insurance claim for the determined
insurance claim event that is supported by the insurance policy
wherein the notification preferably identifies the determined
applicability of recoverable depreciation for an insurance claim.
Additionally, a determination may be made regarding the
identification of one or more third party vendors relating to
repairs to be made in connection with the determined insurance
claim event, and further, repair services may be scheduled from the
one or more third party vendors. Product documentation may also be
electronically identified relating to the at least one item,
wherein the product documentation preferably includes a service
manual relating to the at least one item.
[0009] In yet another aspect, at least one camera sensor device
detects indicia associated with the at least one object located in
the insured property wherein analysis of the indicia determines
insurance coverage for the at least one object. The indicia may be
provided by an insurance company providing insurance coverage for
the at least one object.
[0010] This summary section is provided to introduce a selection of
concepts in a simplified form that are further described
subsequently in the detailed description section. This summary
section is not intended to identify key features or essential
features of the claimed subject matter, nor is it intended to be
used to limit the scope of the claimed subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The accompanying appendices and/or drawings illustrate
various non-limiting, example, inventive aspects in accordance with
the present disclosure:
[0012] FIG. 1 illustrates an example system for utilizing
informatics to inform and assist appliance repair, management,
maintenance, and usage;
[0013] FIG. 2 illustrates a network computer device/node in
accordance with an illustrated embodiment; and
[0014] FIG. 3 is a flow diagram of operational steps of the
structural informatics module of FIG. 1.
DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS
[0015] The illustrated embodiments are now described more fully
with reference to the accompanying drawings wherein like reference
numerals identify similar structural/functional features. The
illustrated embodiments are not limited in any way to what is
illustrated as the illustrated embodiments described below are
merely exemplary, which can be embodied in various forms as
appreciated by one skilled in the art. Therefore, it is to be
understood that any structural and functional details disclosed
herein are not to be interpreted as limiting, but merely as a basis
for the claims and as a representation for teaching one skilled in
the art to variously employ the discussed embodiments. Furthermore,
the terms and phrases used herein are not intended to be limiting
but rather to provide an understandable description of the
illustrated embodiments. Also, the flow charts and methods
described herein do not imply either required steps or a required
order to the steps, and the illustrated embodiments and processes
may be implemented in any order and/or combination that is
practicable.
[0016] Unless defined otherwise, all technical and scientific terms
used herein have the same meaning as commonly understood by one of
ordinary skill in the art to which this invention belongs. Although
any methods and materials similar or equivalent to those described
herein can also be used in the practice or testing of the
illustrated embodiments, exemplary methods and materials are now
described.
[0017] It must be noted that as used herein and in the appended
claims, the singular forms "a", "an," and "the" include plural
referents unless the context clearly dictates otherwise. Thus, for
example, reference to "a stimulus" includes a plurality of such
stimuli and reference to "the signal" includes reference to one or
more signals and equivalents thereof known to those skilled in the
art, and so forth.
[0018] It is to be appreciated the illustrated embodiments
discussed below are preferably a software algorithm, program or
code residing on computer useable medium having control logic for
enabling execution on a machine having a computer processor. The
machine typically includes memory storage configured to provide
output from execution of the computer algorithm or program.
[0019] As used herein, the term "software" is meant to be
synonymous with any code or program that can be in a processor of a
host computer, regardless of whether the implementation is in
hardware, firmware or as a software computer product available on a
disc, a memory storage device, or for download from a remote
machine. The embodiments described herein include such software to
implement the equations, relationships and algorithms described
above. One skilled in the art will appreciate further features and
advantages of the illustrated embodiments based on the
above-described embodiments. Accordingly, the illustrated
embodiments are not to be limited by what has been particularly
shown and described, except as indicated by the appended claims.
Commonly assigned U.S. Pat. Nos. 8,289,160 and 8,400,299 are
related to certain embodiments described herein and are each
incorporated herein by reference in their entirety.
[0020] As used herein, the term "risk related data" means data or
information that may be relevant to an insurance company's
decisions about underwriting, pricing, and other terms and
conditions on which it is willing to issue insurance policies.
[0021] As used herein, the term "insurance policy" refers to a
contract between an insurer, also known as an insurance company,
and an insured, also known as a policyholder, in which the insurer
agrees to indemnify the insured for specified losses, costs, or
damage on specified terms and conditions in exchange of a certain
premium amount paid by the insured. In a typical situation, when
the insured suffers some loss for which he/she may have insurance
the insured makes an insurance claim to request payment for the
loss. It is to be appreciated for the purpose of the embodiments
illustrated herein, the insurance policy is not to be understood to
be limited to a residential or homeowners insurance policy, but can
be for a commercial, umbrella, and other insurance policies known
by those skilled in the art.
[0022] As also used herein, "insured" may refer to an applicant for
a new insurance policy and/or may refer to an insured under an
existing insurance policy.
[0023] As used herein, the term "insurance policy" may encompass a
warranty or other contract for the repair, service, or maintenance
of insured property.
[0024] As used herein, "insured property" means a dwelling, other
buildings or structures, personal property, or business property,
as well as the premises on which these are located, some or all
which may be covered by an insurance policy.
[0025] Turning now descriptively to the drawings, FIG. 1 depicts an
exemplary system 100 communicatively connected to sensors at an
insured property in which below illustrated embodiments may be
implemented. As to be further described below, it is to be
understood examples of sensors include, but are not limited to,
camera devices, webcams, smart tv camera devices (and other
appliance camera devices), smart phone devices, tablet devices,
satellite imaging devices (including high-device imaging satellite
devices), infrared and/or radar devices and the like. It is to be
further understood that first and second networks 50 are each a
geographically distributed collections of nodes interconnected by
communication links and segments for transporting data between end
nodes, such as personal computers, work stations, smart phone
devices, tablets, televisions, sensors and or other devices such as
automobiles, etc. Many types of networks are available, with the
types ranging from local area networks (LANs) to wide area networks
(WANs). LANs typically connect the nodes over dedicated private
communications links located in the same general physical location,
such as an insured property, structure, residence or campus. WANs,
on the other hand, typically connect geographically dispersed nodes
over long-distance communications links, such as common carrier
telephone lines, optical lightpaths, synchronous optical networks
(SONET), synchronous digital hierarchy (SDH) links, or Powerline
Communications (PLC), and others.
[0026] Communications 75 represents computerized communications as
known by those skilled in the art. For instance, communications 75
may be wired links or may comprise a wireless communication medium,
where certain nodes are in communication with other nodes, e.g.,
based on distance, signal strength, current operational status,
location, etc. Moreover, each of the devices can communicate data
packets (or frames) with other devices using predefined network
communication protocols as will be appreciated by those skilled in
the art, such as various wired protocols and wireless protocols
etc., where appropriate. In this context, a protocol consists of a
set of rules defining how the nodes interact with each other. Those
skilled in the art will understand that any number of nodes,
devices, links, etc. may be used in the computer network, and that
the view shown herein is for simplicity. Also, while the
embodiments are shown herein with reference to a general network
cloud, the description herein is not so limited, and may be applied
to networks that are hardwired.
[0027] As will be appreciated by one skilled in the art, aspects of
the present invention may be embodied as a system, method or
computer program product. Accordingly, aspects of the present
invention may take the form of an entirely hardware embodiment, an
entirely software embodiment (including firmware, resident
software, micro-code, etc.) or an embodiment combining software and
hardware aspects that may generally be referred to herein as a
"circuit," "module" or "system." Furthermore, aspects of the
present invention may take the form of a computer program product
embodied in one or more computer readable medium(s) having computer
readable program code embodied thereon.
[0028] Any combination of one or more computer readable medium(s)
may be utilized. The computer readable medium may be a computer
readable signal medium or a computer readable storage medium. A
computer readable storage medium may be, for example, but not
limited to, an electronic, magnetic, optical, electromagnetic,
infrared, or semiconductor system, apparatus, or device, or any
suitable combination of the foregoing. For exemplary purposes and
without limitations, examples of the computer readable storage
medium include the following: an electrical connection having one
or more wires, a portable computer diskette, a hard disk, a random
access memory (RAM), a read-only memory (ROM), an erasable
programmable read-only memory (EPROM or Flash memory), an optical
fiber, a portable compact disc read-only memory (CD-ROM), an
optical storage device, a magnetic storage device, or any suitable
combination of the foregoing. In the context of this document, a
computer readable storage medium may be any tangible medium that
can contain, or store a program for use by or in connection with an
instruction execution system, apparatus, or device.
[0029] A computer readable signal medium may include a propagated
data signal with computer readable program code embodied therein,
for example, in baseband or as part of a carrier wave. Such a
propagated signal may take any of a variety of forms, including,
but not limited to, electro-magnetic, optical, or any suitable
combination thereof. A computer readable signal medium may be any
computer readable medium that is not a computer readable storage
medium and that can communicate, propagate, or transport a program
for use by or in connection with an instruction execution system,
apparatus, or device.
[0030] Program code embodied on a computer readable medium may be
transmitted using any appropriate medium, including but not limited
to wireless, wireline, optical fiber cable, RF, etc., or any
suitable combination of the foregoing.
[0031] Computer program code for carrying out operations for
aspects of the present invention may be written in any combination
of one or more programming languages, including an object oriented
programming language such as Java, Smalltalk, C++ or the like and
conventional procedural programming languages, such as the "C"
programming language or similar programming languages. The program
code may execute entirely on the server computer, partly on the
server computer, as a stand-alone software package, partly on the
server computer and partly on a remote computer (such as computing
device 300) or entirely on the remote computer. In the latter
scenario, the remote computer may be connected to the server
computer through any type of network, including a local area
network (LAN) or a wide area network (WAN), a combination thereof,
or the connection may be made to an external computer (for example,
through the Internet using an Internet Service Provider).
[0032] Aspects of the present invention are described below with
reference to flowchart illustrations and/or block diagrams of
methods, apparatus (systems) and computer program products
according to embodiments of the invention. It will be understood
that each block of the flowchart illustrations and/or block
diagrams, and combinations of blocks in the flowchart illustrations
and/or block diagrams, can be implemented by computer program
instructions. These computer program instructions may be provided
to a processor of a general purpose computer, special purpose
computer, or other programmable data processing apparatus to
produce a machine, such that the instructions, which execute via
the processor of the computer or other programmable data processing
apparatus, create means for implementing the functions/acts
specified in the flowchart and/or block diagram block or
blocks.
[0033] These computer program instructions may also be stored in a
non-transitory computer readable medium that can direct a computer,
other programmable data processing apparatus, or other devices to
function in a particular manner, such that the instructions stored
in the computer readable medium produce an article of manufacture
including instructions which implement the function/act specified
in the flowchart and/or block diagram block or blocks.
[0034] The computer program instructions may also be loaded onto a
computer, other programmable data processing apparatus, or other
devices to cause a series of operational steps to be performed on
the computer, other programmable apparatus or other devices to
produce a computer implemented process such that the instructions
that execute on the computer or other programmable apparatus
provide processes for implementing the functions/acts specified in
the flowchart and/or block diagram block or blocks.
[0035] Turning to FIG. 1, system 100 includes sensors 90 and
management module 105 that includes retrieval engine 110, data
engine 120, command generation engine 130 and policy engine 140. In
one embodiment, first network 50 is a LAN and second network 50 is
a WAN (best shown in FIG. 1), such as the internet, although it is
contemplated herein that networks 50 may be any system and/or
method of computerized communications as understood by those
skilled in the art.
[0036] FIG. 2 is a schematic block diagram of an example computing
device 300 that may be used (or components thereof) with one or
more embodiments described herein. As explained above, in different
embodiments these various devices be configured to communicate with
each other in any suitable way, such as, for example, via
communication 75 over networks 50.
[0037] Device 300 is only one example of a suitable system and is
not intended to suggest any limitation as to the scope of use or
functionality of embodiments of the invention described herein.
Regardless, computing device 300 is capable of being implemented
and/or performing any of the functionality set forth herein.
[0038] Computing device 300 is operational with numerous other
general purpose or special purpose computing system environments or
configurations. Examples of well-known computing systems,
environments, and/or configurations that may be suitable for use
with computing device 300 include, but are not limited to, personal
computer systems, server computer systems, thin clients, thick
clients, hand-held or laptop devices, multiprocessor systems,
microprocessor-based systems, set top boxes, programmable consumer
electronics, network PCs, minicomputer systems, mainframe computer
systems, and distributed data processing environments that include
any of the above systems or devices, and the like.
[0039] Computing device 300 may be described in the general context
of computer system-executable instructions, such as program
modules, being executed by a computer system. Generally, program
modules may include routines, programs, objects, components, logic,
data structures, and so on that perform particular tasks or
implement particular abstract data types. Computing device 300 may
be practiced in distributed data processing environments where
tasks are performed by remote processing devices that are linked
through a communications network. In a distributed data processing
environment, program modules may be located in both local and
remote computer system storage media including memory storage
devices.
[0040] Device 300 is shown in FIG. 2 in the form of a
general-purpose computing device. The components of device 300 may
include, but are not limited to, one or more processors or
processing units 310, a system memory 340, interface device 320,
and a bus 305 that couples various system components including
system memory 340 to processor 310.
[0041] Bus 305 represents one or more of any of several types of
bus structures, including a memory bus or memory controller, a
peripheral bus, an accelerated graphics port, and a processor or
local bus using any of a variety of bus architectures. By way of
example, and not limitation, such architectures include Industry
Standard Architecture (ISA) bus, Micro Channel Architecture (MCA)
bus, Enhanced ISA (EISA) bus, Video Electronics Standards
Association (VESA) local bus, and Peripheral Component Interconnect
(PCI) bus.
[0042] Computing device 300 typically includes a variety of
computer system readable media. Such media may be any available
media that is accessible by device 300, and it includes both
volatile and non-volatile media, removable and non-removable
media.
[0043] System memory 340 can include computer system readable media
in the form of volatile memory, such as random access memory (RAM)
342, cache memory, and hard drive 345, which may include database
346. Computing device 300 may further include other
removable/non-removable, volatile/non-volatile computer system
storage media. By way of example only, hard drive 345 can be
provided for reading from and writing to a non-removable,
non-volatile magnetic media. Interface device 320 includes, without
limitation, a magnetic disk drive for reading from and writing to a
removable, non-volatile magnetic disk (e.g., a "floppy disk"), and
an optical disk drive for reading from or writing to a removable,
non-volatile optical disk such as a CD-ROM, DVD-ROM or other
optical media can be provided. In such instances, each can be
connected to bus 305 by one or more data media interfaces. As will
be further depicted and described below, memory 340 may include at
least one program product having a set (e.g., at least one) of
program modules that are configured to carry out the functions of
embodiments of the invention.
[0044] Management module 105, has a set (at least one) of engines,
such as retrieval engine 110, data engine 120, command generation
engine 130 and policy engine 140 described below, which may be
stored in memory 340, and may function solely or in combination
with an operating system, one or more application programs, other
program modules, and program data. Each of the operating system,
one or more application programs, other program modules, and
program data or some combination thereof, may include an
implementation of a networking environment. Management module 105
generally carry out the functions and/or methodologies of
embodiments of the invention as described herein.
[0045] Device 300 may also communicate with one or more interface
devices 320 such as a keyboard, a pointing device, a display, etc.;
one or more devices that enable a user to interact with computing
device 300; and/or any devices (e.g., network card, modem, etc.)
that enable computing device 300 to communicate with one or more
other computing devices. Such communication can occur via
Input/Output (I/O) interfaces. Still yet, device 300 can
communicate with one or more networks such as a local area network
(LAN), a general wide area network (WAN), and/or a public network
(e.g., the Internet) via a network adapter 320. As depicted,
network adapter 320 communicates with the other components of
computing device 300 via bus 305. It should be understood that
although not shown, other hardware and/or software components could
be used in conjunction with device 300. Examples, include, but are
not limited to: microcode, device drivers, redundant processing
units, external disk drive arrays, RAID systems, tape drives, and
data archival storage systems, etc.
[0046] FIGS. 1 and 2 are intended to provide a brief, general
description of an illustrative and/or suitable exemplary
environment in which embodiments of the below described present
invention may be implemented. FIGS. 1 and 2 are exemplary of a
suitable environment and are not intended to suggest any limitation
as to the structure, scope of use, or functionality of an
embodiment of the present invention. A particular environment
should not be interpreted as having any dependency or requirement
relating to any one or combination of components illustrated in an
exemplary operating environment. For example, in certain instances,
one or more elements of an environment may be deemed not necessary
and omitted. In other instances, one or more other elements may be
deemed necessary and added.
[0047] Sensor 90 includes captured data related to structures. It
is contemplated herein that structures include any type of insured
property structure (e.g., residential, commercial, retail,
municipal, etc.) in which the capture and analysis of sensor data
is useful for the reasons at least described herein. It is further
contemplated herein that sensors may be installed on property that
may or may not have a structure. In one embodiment, sensors 90
communicate directly with management module 105. However, it is
contemplated herein that sensors 90 may communicate with computing
device 300 operating on the same network 50 (best shown in FIG. 1).
In this embodiment, computing device 300 receives information from
sensors 90 and communicates the information to management module
105. Computing device 300 may immediately transfer the information
to management module 105, it may be a delayed transfer (e.g.,
scheduled for the middle of the night when interne(usage is low),
and/or it may be any communication methodology as known by those
skilled in the art. Computing device 300 is preferably configured
and operational to receive (capture) data from various sensors 90
regarding certain measured aspects of the insured property and
transmit that captured data to a management module 105 via network
50. It is noted that device 300 may perform analytics regarding the
captured sensor data regarding the insured property, and/or
management module 105, preferably located or controlled by an
insurance company/carrier, may perform such analytics, as also
further described below. Further, sensors 90 may be connected to
computing device 300 by wire, or by a wireless technology, or via
any communication methodology as known by those skilled in the
art.
[0048] Although various sensor types are illustrated in FIG. 1 and
described below, the sensor types described and shown herein are
not intended to be exhaustive as embodiments of the present
invention may encompass any type of known or unknown sensor type
which facilitates the purposes and objectives of the certain
illustrated embodiments described herein. It is to be understood
and appreciated, in accordance with the embodiments herein, sensors
90 are preferably installed, and its data is collected, maintained,
accessed and otherwise utilized pursuant to the permission of the
insured(s) and subject to appropriate security and privacy
protections. Exemplary sensor types include (but are not limited
to):
Motion sensor--One type of motion sensor 90 detects motion within a
range of sensor 90. Thus, motion sensor 90 may be placed to detect
when people, animals and/or objects move within sensor's 90 field
of vision. Another type of sensor 90 may sense motion in the
structure to which sensor 90 is attached. Although structures
typically do not move, in the event of an earthquake, flood, damage
to that part of the structure, and/or other devastating event,
motion sensor 90 may detect the movement of the structure itself.
Temperature sensor--Temperature sensor 90 detects the temperature
of the desired medium. Thus, temperature sensor 90 may be
configured to measure the temperature of ambient air or of a
specific surface (e.g., the wall to which temperature sensor 90 is
attached). It is contemplated herein that temperature sensor 90 may
be placed outside the structure (e.g., on an outside wall and/or
the roof), inside the structure (e.g., on an interior wall, an
interior ceiling, an interior floor, a basement, an attic, a
kitchen, a bathroom, a bedroom, a workspace, etc.), or at a
boundary therebetween. Humidity sensor--As with other sensors 90,
humidity sensor 90 may be placed anywhere inside/outside/on the
structure as recognized by those skilled in the art. Gas detection
sensor--Detects the presence of various gasses. As with other
sensors 90, gas detection sensor 90 may be placed anywhere
inside/outside/on the structure as recognized by those skilled in
the art. For exemplary purposes only and without limitation, gas
detection sensor may be configured to detect the presence of carbon
monoxide (or any other harmful gasses, such as radon), oxygen,
and/or methane (or any other flammable gasses). Further, the
readings may be binary (e.g., either the gas is present or it is
not present), or the readings may be quantitative (e.g., the
percentage of air the comprises the gas, parts per million of the
gas). Smoke detector sensor--Detects the presence of smoke. As with
other sensors 90, smoke detection sensor 90 may be placed anywhere
inside/outside/on the structure as recognized by those skilled in
the art. The readings of smoke detection sensor may be binary
(e.g., either the gas is present or it is not present), or the
readings may be quantitative (e.g., the percentage of air the
comprises smoke, parts per million of smoke). Water pressure
sensor--Detects the water pressure at various locations within the
structure. Water pressure sensors 90 may be placed anywhere inside
or outside the structure and thus may provide information related
to the stresses being induced upon the structure's plumbing system
(including sewer lines, water lines, HVAC system, appliances, and
automatic fire suppression systems). This information may be
utilized by management module to indicate a plumbing system that is
operating close to stress limits, and thus, a structure for which
water damage may be more likely. Water flow sensor--Detects the
amount of water flowing through selected points in the plumbing
system(including sewer lines, water lines, HVAC system, appliances,
and automatic fire suppression systems). Water flow sensor 90 may
be placed anywhere inside or outside the structure and thus may
provide information related to the amount of water being routed to
the structure, and more particularly, which parts of the structure
are receiving exactly (or approximately) how much water. Leak
detection sensor--configured and operational to preferably monitor
the presence of leaks from gas and water plumbing pipes both inside
and outside the walls of the insured property. The leak detection
sensor may have one or more probes attached to various locations of
the insured property's plumbing and piping, and this device 90 may
record the fact that there is a gas or water leak. An example of
this is that a leak detection sensor can be placed behind the
washing machine. If the hoses that connect the washing machine to
the water line were to break the leak detection sensor would know
that there was a water leak and notify the insured and/or the
insurance company. The insured can also give prior authorization to
the insurance company to act on their behalf to correct the water
leak. For instance, call a plumber to turn off the water at the
street when the leak detector activates and the insured does not
respond to the leak detection sensor after a certain period of
time. The leak detection sensors do not need to necessarily be
placed around the appliance or pipe that they are intended to check
for leaks. For example, an insured could place a sensor on the main
water line that goes into the insured property and this sensor
could know by changes in pressure, temperature, etc. that there is
a later or gas leak in the insured property--even if the leak was
inside the walls and not viewable inside the home. An analysis
model could use the information about how often the leak detection
sensor alerts, whether the insured uses leak detection sensor(s),
and where they are placed in various ways such as rating the home
insurance, tracking water pressure, and/or providing advice and
guidance. Wind speed sensor--Wind speed sensor 90 detects the wind
speed at that location and may be placed anywhere inside or outside
the structure. Air pressure sensor--Air pressure sensor 90 may be
placed anywhere inside or outside the structure. This information
may be analyzed, for example, to determine how quickly and easily
the structure's air pressure equalizes to air pressure changes to
the outside air. Electrical system sensor--Electrical system sensor
90 detects the operational parameters of the structure's electrical
system. Readings from sensor 90 could be used to determine if the
voltage is (persistently) too high, too low, or if the voltage
frequently drops and/or spikes. Such conditions may suggest that
the insured property 300 is at risk for fire. Other types of
electrical measurements could be taken, such as readings of current
flowing through the electrical system. Still other types of
electrical measurements could be determined include how energy is
used and at what times of day it is used, etc. Structural
sensor--Structural sensor 90 may be configured to detect the
(changing) conditions of the structure's elements (e.g., support
beams, floors, ceilings, roofs, walls, etc.). Structural readings
from one or more locations inside and/or outside the structure
could thus be recorded by sensor 90 and transmitted to management
module 105. Environmental Sensor--Environmental sensor 90 may be
configured to detect various environmental conditions relating to
insured property 300, such as the air quality present in the
structure, the presence of mold/bacteria/algae/lead paint or any
contaminant adverse to human health (whether airborne or attached
to a portion of the structure of the structure). Camera
Sensor--Camera sensor 90 may be configured to detect various
wavelengths, including without limitation visible light, infrared,
and thermal. It is contemplated herein that cameras may be
two-dimensional (2D) cameras, three-dimensional (3D) cameras,
and/or any functionality as known in the art. It is contemplated
herein that multiple 2D cameras may be used in cooperation and/or
conjunction such that the location of detected objects may be
determined, such as, again for exemplary purposes and without
limitation, a common 3D camera configuration (e.g., two 2D cameras
located a few inches apart horizontally), and a different 3D
configuration (e.g., two 2D cameras located a few inches apart
vertically, two or more 2D cameras located at different known
locations such that the location of commonly detected objects can
be calculated).
[0049] With exemplary sensors 90 identified and briefly described
above, and as will be further discussed below, it is to be
generally understood sensors 90 preferably record certain data
parameters relating to products and services provided by an
insurance carrier, such as USAA, to determine insurance policy
modifications and other value added services such as those
described below. It is to be understood and appreciated the
aforementioned sensors 90 may be configured as wired and wireless
types integrated in a networked environment (e.g., WAN, LAN, WiFi,
802.11X, 3G, LTE, etc.), which may also have an associated IP
address. It is to be further appreciated the sensors 90 may consist
of internal sensors located within the structure of a structure;
external sensors located external of a structure; sound sensors for
detecting ambient noise (e.g., for detecting termite and rodent
activity, glass breakage, intruders, etc.); camera sensors (e.g.,
visible light, infrared light and/or any wavelength) such as those
consisting of camera standalone devices, or by integrating into
existing camera devices in a structure. It is additionally to be
understood and appreciated that sensors 90 can be networked into a
central computer hub (e.g., device 300) in an insured property to
aggregate collected sensor data packets or sensors 90 may be
communicatively connected to other sensors 90 and/or computing
device 300 (e.g., hard wired to either). Aggregated data packets
can be analyzed in either a computer system (e.g., computing device
300) or via an external computer environment (e.g., management
module 105). Additionally, it is to be understood data packets
collected from sensors 90 can be aggregated in computing device 300
and sent as an aggregated packet to management module 105 for
subsequent analysis whereby data packets may be transmitted at
prescribed time intervals (e.g., a benefit is to reduce cellular
charges in that some insured properties may not have Internet
access or to send during low internet usage hours).
[0050] In accordance with an illustrated embodiment, in addition to
the aforementioned, computing device 300 may additionally be
coupled to a clock which may keep track of time for sensors 90,
thereby allowing a given item of data to be associated with the
time at which the data was captured. For example, sensor 90 may
recurrently capture readings of temperature, wind speed, humidity,
appliance operating times, etc., and may timestamp each reading.
The time at which the readings are taken may be used to reconstruct
events or for other analytic purposes, such as those described
herein. For example, the timestamps on wind speed readings taken
during a hurricane may allow it to be determined, after the
hurricane has occurred, how quickly the wind speed rose in the
vicinity of the structure.
[0051] A storage component may further be provided and utilized to
store data readings and/or timestamps in sensors 90. For example, a
storage component may include, or may otherwise make use of,
magnetic or optical disks, volatile random-access memory,
non-volatile random-access memory, or any other type of storage
device. There may be sufficient data storage capacity to store
several hours or several weeks of data readings. For example, the
severe part of a hurricane might last for half a day, a full day,
or several days. A storage component might have sufficient storage
capacity to allow twelve or more hours of readings to be stored,
thereby allowing forensic reconstruction of how the hurricane
affected the structure during the full time that the structure was
experiencing the hurricane's impact.
[0052] A communication component may further be provided and
utilized to communicate recorded information from computing device
300 to an external location, such as management module 105, which
may be associated with an insurance carrier such as USAA. The
communication component may be, or may comprise, a network
communication card such as an Ethernet card, a WiFi card, or any
other communication mechanism. However, the communication component
could take any form and is not limited to these examples. The
communication component might encrypt data that it communicates, in
order to protect the security and/or privacy of the data.
Additionally, data from sensors 90, a computerized clock and/or a
storage component may be communicated directly to management module
105, via network 50, thus obviating or mitigating the need for
computing device 300.
[0053] Management module 105 may include, or otherwise may
cooperate with, retrieval engine 110. Retrieval engine 110 receives
information from sensors 90 and/or computing device 300. In one
embodiment, retrieval engine 110 sends a query to computing device
300 to respond with data generated by sensors 90. In another
embodiment, retrieval engine 110 sends a query to sensors 90 to
retrieve data they generated. In yet another embodiment, sensors 90
send data to retrieval engine 110 as the data is generated. In
still another embodiment, sensors 90 store data and periodically
(e.g., every night at 3:00 A.M.) send to retrieval engine 110.
However, such is not an exhaustive list of methods of communicating
data from sensors 90 to retrieval engine 110, and it is
contemplated herein that data may be sent in any way as known in
the art, including permutations of methods described herein.
[0054] In one embodiment a single instance of management module 105
receives communications from sensors 90 at a plurality of
structures/locations (e.g., thousands of sensor locations
communicating to a single management module 105), however it is
contemplated herein that any permutation of sensor(s) 90 and
management module(s) 105 may be utilized as would be readily
understood by those skilled in the art.
[0055] Management module 105 may further include data engine 120
that analyzes data that has been generated by sensors 90. Data
engine 120 may apply business rules to identify manuals related to
an appliance that informatics has been communicated about,
scheduling a repair for an appliance that informatics has been
communicated about, sending a message to change a setting of an
appliance that informatics has been communicated about, and/or
sending a message about a repair and/or alteration including
instructions on attending to such repair and/or alteration.
[0056] Data engine 120 may further electronically receive an
insurance policy (e.g., covering an insured property) to identify
one or more relevant sections of the insurance policy relating to
the a determined insurance claim event regarding at least one or
more items located in or on the insured property. Predefined
business rules are preferably utilized in view of a determined
insurance claim event for an item located in or on the insured
property and relevant sections of the insurance policy to determine
if the insurance policy supports an insurance claim regarding the
determined insurance claim event for an item located in or on the
insured property.
[0057] For exemplary purposes only, in one embodiment, detection
sensors may detect indicia (e.g., a sticker, label, barcode, glyph,
or the like) on an item, such as an appliance, that is consistent
with warranty coverage for the item. The label may identify a
coverage for the item (e.g., language such as "three-year
warranty") and/or the label may identify a repairing party and when
the repairs were performed (e.g., a repair history for the item)
(in which case, the parts that were worked on may be covered by a
warranty provided by the repairing party). It is to be appreciated
an insurance company may generate and provide the aforesaid indicia
for a specific item. The indicia is preferably applied/associated
with the intended object by the insured, an agent of the insured or
an insurance company representative, such that the insurance
company can readily electronically identify the object via analysis
of informatics relating to the indicia.
[0058] In one embodiment, informatics is gathered about one or more
items in a house, such as an appliance. The type of the appliance
may be identified by data engine 120, and manuals relating to the
appliance may be identified and electronically sent, such as to the
owner of the appliance. Particular reference to a portion of the
manual may be specifically identified and/or provided regarding an
action to be taken.
[0059] In another embodiment, informatics is gathered about an
appliance and that informatics is analyzed to determine a working
condition of the appliance. For exemplary purposes only, the
informatics may relate to a sound that the appliance is making
(e.g., a clicking sound may indicate that the appliance is broken),
the informatics may relate to a length of time that certain actions
require as compared to a previous length of time that the same or a
similar action required (e.g., previously it was five minutes for
the temperature of ambient air in a freezer to stabilize after it
was opened to remove an object, but now it is six minutes),
infrared readings of the object (e.g., detecting a greater heat
leakage in the seals of a refrigerator, detecting an increased high
temperature for a dryer, detecting an increased amount of time for
an object, such as a washing machine, to cool down). Based on the
gathered and analyzed informatics, a repair service appointment
maybe scheduled. It is also contemplated that once repair service
is necessary an insurance company such as USAA can assist the owner
of the appliance in scheduling the appointment using a contractor
network or other network known to by the insurance company.
[0060] In another embodiment, based on the gathered and analyzed
informatics, a message may be sent that recommends and identifies a
setting change for an appliance (e.g., reduce HVAC burden, increase
operating temperature of refrigerator because of sub-optimally
performing cooling mechanism). It is also contemplated that advice
and guidance can be provided to the insured by the insurance
company based upon the gathered analyzed informatics about the
appliance. This advice and guidance can be used to help extend the
life of the appliance or help with scheduled maintenance.
[0061] In another embodiment, the informatics gathered using data
engine 120 and this data can be compared to how the appliance is
intended to perform as prescribed by the manufacturer. This
information can be gathered from the manufacturer, from the manuals
about the appliance, or other sources. When the appliance does not
perform as intended by the manufacturer the insurance company or
the appliance owner can be alerted. For example, the washing
machine is intended to use X amount of water per minute, but the
sensor in the appliance determines that a higher than acceptable
amount of water is being consumed. This could indicate that the
appliance is in need of repair and is in danger of breaking and
causing water damage to the surrounding area.
[0062] In still another embodiment, a work project is identified
based on gathered informatics. For exemplary purposes only, the
work project may be painting a wall, creating an addition,
replacing an appliance, finishing drywall, waterproofing a
basement, and replacing and/or upgrading a roof. Subsequent to data
engine 120 determining and identifying the work project, that
determination may be utilized to inform and/or cause future
decisions/recommendations.
[0063] In yet another embodiment, sensors can determine if
recoverable depreciation in a claim for a covered loss can be
provided to the insured. An example of how this could occur is a
sensor 90 can send notification to the data engine 120 that the
insured has replaced, repaired or maintained an item in question
with like kind and quality or item(s) of similar quality and
usefulness. When this happens, the insurance company is notified
and can provide the insured recoverable depreciation. Management
module 105 may further include command generation engine 130.
Command generation engine 130 may send commands to sensors 90. Such
commands may be sent through intermediary computing device 300, or
such commands may be sent directly to sensors 90. Such commands may
include, for exemplary purposes only and without limitation, an
instruction to take an immediate reading, an instruction to take a
series of readings (e.g., every five minutes for one hour, every
minute for one week), an instruction to take more frequent readings
(e.g., every hour rather than every six hours), an instruction to
take less frequent readings (e.g, every day rather than every
hour), and/or any permutations or derivations thereof as will be
known by those skilled in the art.
[0064] Management module 105 may further include policy engine 140.
Policy engine 140 may analyze the data such as described above with
respect to data engine 120. It is contemplated herein that data
engine 120 and policy engine 140 may work in cooperation/tandem,
independently of each other, without interaction with the other, or
any other permutations or derivations thereof as will be known by
those skilled in the art.
[0065] FIG. 3 shows, in the form of a flow chart (process 1000),
exemplary operational steps of utilizing system 100. Before turning
to descriptions of FIG. 3, it is noted that the flow diagram shown
therein are described, by way of example, with reference to
components shown in FIGS. 1-2, although these operational steps may
be carried out in any system and are not limited to the scenario
shown in the aforementioned figures. Additionally, the flow
diagrams in FIG. 3 shows an example in which operational steps are
carried out in a particular order, as indicated by the lines
connecting the blocks, but the various steps shown in these
diagrams can be performed in any order, or in any combination or
sub-combination.
[0066] With reference to FIG. 3, starting at step 1001, detection
devices, such as sensors 90, are installed at a property, such as a
structure, covered by the insurance policy. In one embodiment,
sensors 90 may have been previously installed for other reasons
(e.g., security cameras) and later re-configured to integrate with
system 100. In another embodiment, sensors 90 are installed for at
least the reason of integrating with and working with system 100.
In still another embodiment, sensors 90 include a combination of
pre-installed sensors 90 and newly-installed sensors 90.
[0067] Subsequently, information is gathered (step 1002) and
received from sensors 90 (step 1003). As discussed above,
information may be sent from sensors 90 to computing device 300,
and subsequently to management module 105. In another embodiment,
computing device 300 is not installed onsite and sensors 90
communicate directly to management module 105. In yet another
embodiment, computing device 300 is installed onsite, and sensors
90 communicate directly to management module 105, through computing
device, and/or a combination thereof.
[0068] Information is analyzed by management module (step 1004),
such as by data engine 120 and/or policy engine 140. In one
embodiment, data engine 120 considers the data and identifies
appliances and their correlated documentation, such as repair
instructions, recommends and/or schedules repair services, and/or
provides recommendations based on a valuation of an appliance's
working condition.
[0069] In one embodiment, command generation engine 130 may send
additional commands to sensors 90 and/or computing device 300, such
as via computing device 300 and/or directly to sensors 90. These
commands may alter the types of measurements being performed, the
frequency of measurements, the speed/frequency in which information
is communicated from sensors 90, and/or any other settings.
Subsequent to additional commands being sent to sensors 90, sensors
90 and/or computing device 300 execute and/or perform the
additional commands and send additional information to management
module 105. The additional information may be analyzed independent
of the previously received information, and/or it may be analyzed
and/or correlated with the previously received information.
[0070] Related information, such as, for exemplary purposes only
and without limitation, maintenance advice, repair instructions,
operating manuals, and/or repair services, may be sent (step 1005).
Finally, a message, such as, for exemplary purposes only and
without limitation, operating advice, may be sent to the operator
of the item/appliance (step 1006).
[0071] In one embodiment, information received at management module
105 is immediately analyzed and then discarded. In another
embodiment the information is analyzed and stored temporarily. In
yet another embodiment, the information is stored for later
analysis. And in still another embodiment, the information is
stored via another device/module/engine.
[0072] The term "module"/"engine" is used herein to denote a
functional operation that may be embodied either as a stand-alone
component or as an integrated configuration of a plurality of
subordinate components. Thus, "modules"/"engines" may be
implemented as a single module or as a plurality of modules that
operate in cooperation with one another. Moreover, although
"modules"/"engines" may be described herein as being implemented as
software, they could be implemented in any of hardware (e.g.
electronic circuitry), firmware, software, or a combination
thereof.
[0073] With certain illustrated embodiments described above, it is
to be appreciated that various non-limiting embodiments described
herein may be used separately, combined or selectively combined for
specific applications. Further, some of the various features of the
above non-limiting embodiments may be used without the
corresponding use of other described features. The foregoing
description should therefore be considered as merely illustrative
of the principles, teachings and exemplary embodiments of this
invention, and not in limitation thereof.
[0074] It is to be understood that the above-described arrangements
are only illustrative of the application of the principles of the
illustrated embodiments. Numerous modifications and alternative
arrangements may be devised by those skilled in the art without
departing from the scope of the illustrated embodiments, and the
appended claims are intended to cover such modifications and
arrangements.
* * * * *