All The Claims

1. A system for extending software change management to handle unmanaged artifacts comprising:
one or more processors, which are hardware processors;
one or more non-transitory storage mediums storing digitally encoded information;
an object comprising of a reference stored within a software change management (SCM) system, comprising the one or more processors and the one or more non-transitory storage mediums, wherein the reference is a linkage to a remote managed artifact stored within a repository, wherein the at least one reference lacks artifact restrictions, wherein the artifact restrictions are traditional software change management artifact restrictions associated with a managed artifact within the SCM, wherein the object is associated with a binding to the managed artifact stored within the SCM; and
an SCM engine able to perform operations on the object in a manner consistent with a managed artifact; and
a portion of metadata associated with the object, wherein the metadata comprises of at least a name information and a location information associated with the remote managed artifact, wherein the location information is a Uniform Resource Identifier (URI), wherein the URI is associated with a source code repository.
2. The system of claim 1, wherein the operations are at least one of a fetch operation and a compare operation.
3. The system of claim 1, wherein the managed artifact is a source code entity, and wherein the portion of metadata is stored within an extensible markup (XML) language file within the SCM, wherein the portion of metadata indicates a means to access the remote managed artifact.
4. The system of claim 1, wherein the system is a portion of a Web-enabled service.
5. The system of claim 1, wherein the SCM performs a dependency check on each unmanaged artifact associated with the object.
6. The system of claim 1, wherein the object comprises of at least one remote managed artifact.
7. The system of claim 1, wherein the SCM is an IBM RATIONAL ASSET MANAGER software.
8. A computer program product comprising a non-transitory computer readable storage medium having computer usable program code embodied therewith, the computer usable program code comprising:
computer usable program code stored in a non-transitory tangible storage medium, when said computer usable program code is executed by a processor it is operable to store an object within a software change management (SCM) system, wherein the object is managed as a traditional SCM artifact, wherein the object comprises a reference to one or more unmanaged artifacts, wherein the unmanaged artifacts lack restrictions imposed by the software change management system, wherein the unmanaged artifacts are associated with a binding of the traditional SCM managed artifact, wherein the object has associated metadata, wherein the metadata comprises of at least a name information and a location information associated with one of the unmanaged artifacts, which is a remote managed artifact, wherein the location information is a Uniform Resource Identifier (URI), wherein the URI is associated with a source code repository; and
computer usable program code stored in a non-transitory tangible storage medium, when said computer usable program code is executed by a processor it is operable to trigger a programmatic action on the stored object in response to an action associated with at least one of the traditional SCM artifact and the stored object.
9. The computer program product of claim 8, wherein the traditional SCM artifact is a source code entity, wherein the restrictions that the unmanaged artifacts lack are at least one of a lifecycle, access rule, and a management policy, wherein the binding is a compile time dependency binding, wherein the unmanaged artifacts is associated with a remote repository, wherein within the remote repository, the unmanaged artifacts are managed as another traditional SCM artifact, and wherein the action that triggers the programmatic action is a provisioning action.
10. The computer program product of claim 9, wherein the provisioning action results in importing at least one unmanaged artifact into a development environment associated with a client computing device.
11. The computer program product of claim 8, wherein the programmatic action is performed prior to or subsequent to compile time.
12. The computer system of claim 1, wherein the object is associated with at least one of a source code trunk, a source code branch, and a source code merge of the remote managed artifact.
13. The system of claim 1, wherein the object comprises a linkage, the linkage coupling a managed artifact stored within the SCM to the remote managed artifact.
14. The system of claim 13, wherein the coupling is one of a loose coupling and tight coupling, wherein the loose coupling enables minimal constraints on the object and wherein the tight coupling enables rigid constraints on the object.
15. The system of claim 1, wherein the SCM engine is configured to:
determine automatically one or more managed artifacts dependent on a traditional managed artifact; and
create the object within the SCM system based on the dependency.
16. The computer program product of claim 8, wherein the object is associated with at least one of a source code trunk, a source code branch, and a source code merge of the remote managed artifact.
17. The computer program product of claim 8, wherein the object comprises a linkage, the linkage coupling a managed artifact stored within the SCM to the remote managed artifact.
18. The computer program product of claim 8, wherein the coupling is one of a loose coupling and tight coupling, wherein the loose coupling enables minimal constraints on the object and wherein the tight coupling enables rigid constraints on the object.
19. The computer program product of claim 8, wherein the SCM engine is configured to:
determine automatically one or more managed artifacts dependent on a traditional managed artifact; and
create the object within the SCM system based on the dependency.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A transducer comprising:
a sensor configured to sense a parameter and to produce an output signal based thereon; and
a programmable circuit having an input port configured to receive the output signal of said sensor, wherein said programmable circuit is configured to produce an output signal based on said output signal of said sensor.
2. The transducer of claim 1, wherein said sensor comprises a pressure sensor.
3. The transducer of claim 2, further wherein said programmable circuit is configured to produce a linear output signal based on said output signal of said sensor.
4. The transducer of claim 2, said pressure sensor being optimized to operate in low pressure environments.
5. The transducer of claim 2, wherein said pressure sensor comprises a pair of pressure sensors in a wheatstone bridge configuration.
6. The transducer of claim 1 wherein said programmable circuit and said sensor are located within a case.
7. The transducer of claim 1, said programmable circuit comprising an application specific integrated circuit (ASIC).
8. The transducer of claim 1, said sensor comprising a pair of sensors, said pair of sensors being mechanically and electrically cross-coupled with each other such that errors associated with one of said pair of sensors is compensated or substantially cancelled by errors associated with the other of said pair of sensors.
9. The transducer of claim 1 wherein said programmable circuit is configured to produce a linear output signal based upon said output of said sensor.
10. The transducer of claim 1 wherein said programmable circuit is configured to produce an output signal that corrects for thermal effects on said sensor.
11. The transducer of claim 1 wherein said programmable circuit is configured to produce an output signal that is within a predetermined range of output levels.
12. The transducer of claim 11 wherein said predetermined range is from about 0.25 volts to about 4.25 volts.
13. A method of calibrating a transducer comprising a sensor coupled to an ASIC, said method comprising:
testing the sensor at a first predetermined condition to determine the output of the CB0 at decision diamond 216. If the there have been N consecutive CB0,
programming the ASIC such that the output of the ASIC at the first predetermined condition is within a first predetermined range.
14. The method of claim 13 wherein said first predetermined condition comprises room temperature and zero pressure.
15. The method of claim 13 wherein the first predetermined range is the range approximately within 0.25% of 0.25 volts.
16. The method of claim 13 further comprising:
testing the sensor at a second predetermined condition to determine the output of the sensor; and
programming the ASIC such that the output of the ASIC at the second predetermined condition is within a second predetermined range.
17. The method of claim 16 wherein said second predetermined condition comprises room temperature and a maximum pressure.
18. The method of claim 16 wherein said second predetermined range is the range approximately within 0.25% of 4.25 volts.
19. The method of 16 further comprising:
testing the sensor at a third predetermined condition to determine the output of the sensor; and
programming the ASIC such that the output of the ASIC at the third predetermined condition is within a third predetermined range.
20. The method of claim 19 wherein said third predetermined condition comprises a low temperature and zero pressure.
21. The method of 19 further comprising:
testing the sensor at a fourth predetermined condition to determine the output of the sensor; and
programming the ASIC such that the output of the ASIC at the fourth predetermined condition is within a predetermined range.
22. The method of claim 21 wherein said fourth predetermined condition comprises a low temperature and maximum pressure.
23. The method of 21 further comprising:
testing the sensor at a fifth predetermined condition to determine the output of the sensor; and
programming the ASIC such that the output of the ASIC at the fifth predetermined condition is within a fifth predetermined range.
24. The method of claim 23 wherein said fifth predetermined condition comprises a high temperature and zero pressure.
25. The method of claim 23 further comprising:
i) testing the sensor at a sixth predetermined condition to determine the output of the sensor; and
j) programming the ASIC such that the output of the ASIC at the sixth predetermined condition is within a sixth predetermined range.
26. The method of claim 25 wherein said sixth predetermined condition comprises a high temperature and maximum pressure.

1. A system for reporting device management information in a network environment, said system comprising:
plural device data collection units, each device data collection unit amongst the plural device data collection units collecting device data from a corresponding plurality of network devices associated with the device data collection unit;
one or more core management units, each core management unit of the core management units being associated with a corresponding group of collection units from amongst the plural device data collection units, and the core management unit communicating with the group of associated collection units to manage and maintain persistent device data collected from the associated collection units;
a device data store that stores the persistent device data collected from the plural device data collection units; and
a reporting unit including a report interface part to provide a user interface to another device to receive device parameter criteria, input by a user of said another device, to specify types of device data to be collected from the plurality of network devices and to be uploaded to the device data store and cause the one or more core management units to upload device data of the types corresponding to the specified device parameter criteria to the device data store,
wherein the report interface part operates to receive a data access request from an external device external to the network environment, authenticate the data access request from the external device, and upon authentication, provide requested data in the device data store to the external device, in response to the data access request from the external device,
wherein the requested data provided by the reporting unit in response to the data access request from the external device includes information indicating whether an error or problem exists or has occurred at one or more of the network devices and information regarding the properties of the device.
2. The system of claim 1, wherein the reporting unit includes a first interface part that operates to connect and communicate with any specified one of the core management units, and a second interface part that operates to connect and communicate with any specified one of the network devices.
3. The system of claim 2, wherein the report interface part provides a user interface to the external device to allow a user at the external device to modify a configuration of a network device, and the reporting unit communicates through the first interface parts with a specific core management unit associated with managing the network device.
4. The system of claim 2, wherein the report interface part provides a user interface to the external device to allow a user at the external device to select a network device, and the reporting unit communicates through the second interface parts with the selected network device to obtain device status information from the selected network device.
5. The system of claim 1, wherein the core management unit tracks a last upload time device data was uploaded, and uploads to the device data store, at a current upload time, collected device data from the last upload time through the current upload time.
6. The system of claim 1, wherein the core management unit uploads collected device data to the device data store, and then communicates a notification to the reporting unit to notify the reporting unit that the collected device data has been uploaded to the device data store.
7. The system of claim 1, wherein the core management unit, for each network device from which device data is collected by a corresponding collection unit in the group of associated collection units associated with the core management unit, uploads at a regular interval of time to the device data store the device data collected from the network device by the collection unit from a last upload time through a current upload time.
8. The system of claim 1, wherein when the report interface part authenticates the external device, the report interface part transmits an authentication token to the external device, and wherein the token has an associated period of time after which the token expires.
9. The system of claim 8, wherein the token transmitted to the external device expires if not used within a defined usage period.
10. The system of claim 1, wherein when the report interface part authenticates a user operating the external device, and upon authentication of the user, determines a scope of data to be accessible to the authenticated user, and limits data access by the user to said scope.
11. A method for a device reporting system for reporting device management information in a network environment said method comprising:
collecting, by each device data collection unit amongst plural device data collection units of the device reporting system, device data from a plurality of network devices associated with the device data collection unit;
communicating, by each core management unit of one or more core management units of the device reporting system, a corresponding group of collection units associated with the core management unit, from amongst the plural device data collection units, to manage and maintain persistent device data collected from the associated collection units;
storing by a device data store the persistent device data collected from the plural device data collection units;
providing a user interface by a reporting unit to another device to receive device parameter criteria, input by a user of said another device to specify types of device data to be collected from the plurality of network devices and to be uploaded to the device data store and causing the one or more core management units to upload device data of the types corresponding to the specified device parameter criteria to the device data store; and
receiving by the reporting unit a data access request from an external device external to the network environment, authenticating the data access request from the external device, and upon authentication, providing requested data in the device data store to the external device, in response to the data access request from the external device,
wherein the requested data provided in response to the data access request from the external device includes information indicating whether an error or problem exists or has occurred at one or more of the network devices and information regarding the properties of the device.
12. The method of claim 11, further comprising:
providing, by the reporting unit, a user interface to the external device;
receiving, via the user interface, a user request to modify a configuration of a network device; and
communicating with a specific core management unit associated with managing the network device.
13. The method of claim 11, further comprising:
providing, by the reporting unit, a user interface to the external device;
receiving, via the user interface, user selection of a network device; and
communicating with the selected network device to obtain device status information from the selected network device.
14. The method of claim 11, further comprising:
tracking a last upload time device data was uploaded, and uploading to the device data store, at a current upload time, collected device data from the last upload time through the current upload time.
15. The method of claim 11, further comprising:
uploading collected device data to the device data store, and then communicating a notification to the reporting unit to notify the reporting unit that the collected device data has been uploaded to the device data store.
16. The method of claim 11, further comprising:
uploading at a regular interval of time to the device data store the device data collected from a network device by a collection unit from a last upload time through a current upload time.
17. The method of claim 11, further comprising:
authenticating the external device, and transmitting an authentication token to the external device, wherein the token has an associated period of time after which the token expires.
18. The method of claim 11, further comprising:
authenticating a user operating the external device, and upon authentication of the user, determining a scope of data to be accessible to the authenticated user, and limiting data access by the user to said scope.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1) A curing agent for use in concrete comprising a superabsorbent material.
2) The curing agent of claim 1 where the superabsorbent material is a polymer.
3) The curing agent of claim 2 wherein the polymer is a hydro-gel forming polymer.
4) The curing agent of claim 3 wherein the hydro-gel forming polymer is a polypromancic polymer.
5) The curing agent of claim 1, wherein a dispersant is added to the curing agent.
6) The curing agent of claim 5, wherein the dispersant comprises glycerin, ground granulated blast furnace slag, or polyethylene glycol.
7) The curing agent of claim 6, wherein there are two or more dispersants used.
8) The curing agent of claim 1, wherein water is added to form a liquid curing agent.
9) The curing agent of claim 5, wherein water is added to form a liquid curing agent.
10) A curing agent for use in concrete comprising:
0.05% to 10% by weight of a hydro-gel forming polymer;
0.0% to 75% by weight slag;
0.0% to 75% by weight silica fume;
and
10% to 80% by weight water.
11) The curing agent of claim 10, wherein:
the hydrogel forming polymer consists of a partial sodium salt of cross-linked polypromancic acid.
12) The curing agent of claim 1, wherein:
the hydrogel does not reabsorb water once it releases the bound water in the hydrogel.
13) The curing agent of claim 10, wherein:
the hydrogel does not reabsorb water once it releases the bound water in the hydrogel.
14) A curing agent for use in concrete comprising:
0.05% to 10% by weight of a hydro-gel forming polymer;
0.0% to 75% by weight slag;
0.0% to 30% by weight glycerin;
0.0 to 30% by weight polyethylene glycol;
and
10% to 80% by weight water.
15) A concrete mixture comprising:
the curing agent of claim 1;
cementitious materials;
aggregate;
water;
and
admixtures.
16) A concrete mixture comprising:
the curing agent of claim 8;
cementitious materials;
aggregate;
water;
and
admixtures.
17) A concrete mixture comprising:
the curing agent of claim 12;
cementitious materials;
aggregate;
water;
and
admixtures.
18) A pervious concrete mixture comprising:
the curing agent of claim 1;
cementitious materials;
coarse aggregate;
water;
and
admixtures.
19) A means of curing concrete comprising:
placing the concrete;
then spraying the curing agent of claim 9 on the surface.
20) A means of curing concrete comprising:
adding the curing agent of claim 1 to the plastic concrete mix;
then placing the concrete.