1. A radiator monitor, comprising:
a housing;
a detector material having an adjustable density in the housing to select a detection threshold for radiation;
an optical coupler adjacent the detector material to receive Cherenkov energy generated in the detector material;
a photodetector coupled to the optical coupler; and
a processing module coupled to the photodetector to determine whether the detection threshold is exceeded.
2. The monitor according to claim 1, wherein the housing has an adjustable volume.
3. The monitor according to claim 1, further including a reflective material about an outer surface of the housing.
4. The monitor according to claim 1, wherein the housing is generally cylindrical.
5. The monitor according to claim 1, wherein the detector material comprises an aerogel.
6. The monitor according to claim 1, wherein the photodetector comprises a photodiode.
7. The monitor according to claim 1, wherein the photodetector comprises a photomultiplier.
8. The monitor according to claim 1, wherein the detection threshold ranges from about 0.25 to about 30 MeV.
9. The monitor according to claim 1, wherein the housing has an adjustable shape to adjust the density of the detector material.
10. The monitor according to claim 1, further including a supply coupled to the housing to adjust the density of the detector material
11. A method, comprising:
providing a detector material in a housing; and
adjusting a density of the detector material to a selected detection threshold for Cherenkov energy generated in the detector material.
12. The method according to claim 11, further including changing a volume of the housing.
13. The method according to claim 10, further including employing a photodetector coupled to an optical coupler and a processing module coupled to the photodetector to determine whether the detection threshold is exceeded.
14. The method according to claim 10, further including employing a reflective material about an outer surface of the housing.
15. The method according to claim 10, wherein the detector material comprises an aerogel.
16. The method according to claim 10, further adjusting an amount of the detector material in the housing to adjust the density.
17. A system, comprising:
a structure;
a particle accelerator in the structure; and
a radiator monitor, comprising:
a housing;
a detector material having an adjustable density in the housing;
an optical coupler adjacent the liquid to receive Cherenkov energy generated in the detector material;
a photodetector coupled to the optical coupler; and
a processing module coupled to the photodetector to determine whether a detection threshold is exceeded.
18. The system according to claim 17, further including a reflective material about an outer surface of the housing.
19. The system according to claim 17, wherein the detector material comprises an aerogel.
20. The system according to claim 17, wherein a volume of the housing is adjustable.
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 method for determining an impact of a change in a specification on one or more services associated with an enterprise, the method comprising:
obtaining the change in the specification associated with the enterprise, wherein the specification represents a capability of the enterprise to satisfy a service request;
obtaining a plurality of enterprise elements, wherein the enterprise elements are components of the enterprise;
obtaining one or more structural rules stating relationships among the plurality of enterprise elements;
obtaining one or more pre-defined impact rules indicating one or more possible changes associated with the enterprise, the one or more pre-defined impact rules having been pre-defined independent of the one or more services associated with the enterprise;
wherein the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules are stored in a data structure in the form of a model such that the enterprise elements from a non-technical domain of the enterprise and the enterprise elements from a technical domain of the enterprise that are used to implement the enterprise elements of the non-technical domain, and dependencies there between, are represented in the model, and wherein the enterprise elements from the technical domain represent components of a system architecture used to realize the enterprise elements of the non-technical domain; and
determining the impact of the change in the specification on the one or more services, wherein the impact is determined according to the change in the specification and the model which comprises the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules, such that when an enterprise element changes in the model based on the obtained specification change, one or more of the impact rules are used to propagate the change across the model to identify which enterprise elements across the multiple domains are affected;
wherein one or more of the obtaining of the change in the specification, the obtaining of the plurality of enterprise elements, the obtaining of the one or more structural rules, the obtaining of the one or more pre-defined impact rules, the forming of the model, and the determining of the impact are implemented as instruction code executed on a processor device.
2. The method of claim 1, further comprising selecting to implement one or more possible changes related to the one or more services, the one or more possible changes resulting from the determining of the impact of the change in the specification on the one or more services.
3. The method of claim 1, further comprising determining which one or more existing services for the enterprise to at least one of: (i) use; (ii) obtain; and (iii) customize.
4. The method of claim 1, wherein the plurality of enterprise elements comprises at least one of: (i) an enterprise object; (ii) an enterprise scenario; (iii) an enterprise process; (iv) enterprise logic describing the enterprise process; (v) a service; (vi) a service container referring to at least one service; (vii) service logic describing a process flow among the at least one service; (viii) a message; (ix) a message container; and (x) an enterprise fact, and wherein the enterprise scenario describes at least one of: (i) what the enterprise does, and (ii) how the enterprise functions.
5. The method of claim 4, wherein an enterprise process is associated with at least one of: (i) an enterprise object; (ii) a service container, (iii) a message container, (iv) service logic, and (v) enterprise logic.
6. The method of claim 4, wherein the enterprise fact represents a claim related to the enterprise, wherein the claim may be true or false.
7. The method of claim 6, wherein the claim related to the enterprise is a claim about at least one of (i) an enterprise object; (ii) an enterprise process; (iii) an enterprise implemented service; and (iv) an enterprise message.
8. The method of claim 1, wherein the one or more pre-defined impact rules are defined using at least one of: (i) logic programming; and (ii) a stable model.
9. The method of claim 1, wherein the one or more services comprise one or more of: (i) a service provided over a network; (ii) a service provided over the Internet; and (iii) a service associated with a service oriented architecture.
10. The method of claim 1, wherein the change in the specification comprises at least one of: (i) a change related to the enterprise; (ii) a new enterprise specification; (iii) a customization of services requirement; (iv) an enterprise element; (v) an enterprise fact; (vi) a change in a business object; and (vii) a change in a business process.
11. The method of claim 1, wherein the one or more pre-defined impact rules indicate at least one of: (i) an aspect of the enterprise which may be affected by the change in the specification; (ii) a task which could be implemented by the enterprise to meet the change in the specification; (iii) how to modify output content from the one or more services to meet the change in the specification; and (iv) how to modify behavior of the one or more services to meet the change in the specification.
12. The method of claim 1, wherein the one or more pre-defined impact rules relate to at least one of: (i) a business domain; and (ii) an information technology domain.
13. The method of claim 1, wherein the obtaining of the plurality of enterprise elements and the obtaining of the one or more structural rules is according to one or more registries comprising at least one of: (i) known enterprise objects; (ii) known enterprise processes; (iii) known enterprise services; and (iv) known messages.
14. The method of claim 1, wherein the enterprise comprises a business, and the plurality of enterprise elements comprise a plurality of business elements.
15. The method of claim 1, wherein the obtaining of the change in the specification associated with the enterprise comprises a new fact comprising a new claim related to the enterprise.
16. The method of claim 1, wherein the obtaining of the one or more pre-defined impact rules comprises forming the one or more pre-defined impact rules according to at least one of: (i) the plurality of enterprise elements, (ii) the one or more structural rules, and (iii) a stable model.
17. The method of claim 1, wherein the one or more possible changes associated with the enterprise comprise changes in at least one of: (i) the plurality of enterprise elements; and (ii) the one or more structural rules.
18. A system for determining an impact of a change in a specification on one or more services associated with an enterprise, the system comprising:
a specification obtaining module configured to obtain the change in the specification associated with the enterprise, wherein the specification represents a capability of the enterprise to satisfy a service request;
an element obtaining module configured to determine a plurality of enterprise elements, wherein the enterprise elements are components of the enterprise;
a structural rule formation module configured to form one or more structural rules stating relationships among the plurality of enterprise elements;
an impact rule obtaining module configured to obtain one or more pre-defined impact rules indicating one or more possible changes associated with the enterprise, the one or more pre-defined impact rules having been pre-defined independent of the one or more services to be used by the enterprise;
wherein the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules are stored in a data structure in the form of a model such that the enterprise elements from a non-technical domain of the enterprise and the enterprise elements from a technical domain of the enterprise that are used to implement the enterprise elements of the non-technical domain, and dependencies there between, are represented in the model, and wherein the enterprise elements from the technical domain represent components of a system architecture used to realize the enterprise elements of the non-technical domain; and
an impact determining module configured to determine the impact of the change in the specification on the enterprise, wherein the impact is determined according to the change in the specification and the model which comprises the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules, such that when an enterprise element changes in the model based on the obtained specification change, one or more of the impact rules are used to propagate the change across the model to identify which enterprise elements across the multiple domains are affected;
wherein one or more of the obtaining of the change in the specification, the obtaining of the plurality of enterprise elements, the obtaining of the one or more structural rules, the obtaining of the one or more pre-defined impact rules, the forming of the model, and the determining of the impact are implemented as instruction code executed on a processor device.
19. The system of claim 18, wherein the plurality of enterprise elements comprises at least one of: (i) an enterprise object; (ii) an enterprise scenario; (iii) an enterprise process; (iv) enterprise logic describing the enterprise process; (v) a service; (vi) a service container referring to at least one service; (vii) service logic describing a process flow among the at least one service; (viii) a message; (ix) a message container; and (x) an enterprise fact, and wherein the enterprise scenario describes at least one of: (i) what the enterprise does, and (ii) how the enterprise functions.
20. A data structure for storing a model used for determining an impact of a change in a specification on one or more services associated with an enterprise, the model comprising:
a plurality of enterprise elements, wherein the enterprise elements are components of the enterprise;
one or more structural rules stating relationships among the plurality of enterprise elements; and
one or more pre-defined impact rules indicating one or more possible changes associated with the enterprise, the one or more pre-defined impact rules having been pre-defined independent of the one or more services to be used by the enterprise;
wherein the enterprise elements from a non-technical domain of the enterprise and the enterprise elements from a technical domain of the enterprise that are used to implement the enterprise elements of the non-technical domain, and dependencies there between, are represented in the model, and wherein the enterprise elements from the technical domain represent components of a system architecture used to realize the enterprise elements of the non-technical domain;
wherein the model is configured to receive the change in the specification associated with the enterprise;
wherein the model determines the impact of the change in the specification on the enterprise, wherein the impact is determined according to the change in the specification and the model which comprises the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules, such that when an enterprise element changes in the model based on the obtained specification change, one or more of the impact rules are used to propagate the change across the model to identify which enterprise elements across the multiple domains are affected; and
wherein the model is operative to be implemented as instruction code executed on a processor device.
21. The data structure of claim 20, wherein the plurality of enterprise elements comprises at least one of: (i) an enterprise object; (ii) an enterprise scenario; (iii) an enterprise process; (iv) enterprise logic describing the enterprise process; (v) a service; (vi) a service container referring to at least one service; (vii) service logic describing a process flow among the at least one service; (viii) a message; (ix) a message container; and (x) an enterprise fact, and wherein the enterprise scenario describes at least one of: (i) what the enterprise does, and (ii) how the enterprise functions.
22. The data structure of claim 20, wherein the model further comprises at least one of: (i) logic programming; and (ii) a stable model.
23. Apparatus for determining an impact of a change in a specification on one or more services associated with an enterprise, the apparatus comprising:
a memory; and
a processor coupled to the memory and configured to:
obtain the change in the specification associated with the enterprise, wherein the specification represents a capability of the enterprise to satisfy a service request;
obtain a plurality of enterprise elements, wherein the enterprise elements are components of the enterprise;
obtain one or more structural rules stating relationships among the plurality of enterprise elements;
obtain one or more pre-defined impact rules indicating one or more possible changes associated with the enterprise, the one or more pre-defined impact rules having been pre-defined independent of the one or more services associated with the enterprise;
wherein the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules are stored in a data structure in the form of a model such that the enterprise elements from a non-technical domain of the enterprise and the enterprise elements from a technical domain of the enterprise that are used to implement the enterprise elements of the non-technical domain, and dependencies there between, are represented in the model, and wherein the enterprise elements from the technical domain represent components of a system architecture used to realize the enterprise elements of the non-technical domain; and
determine the impact of the change in the specification on the one or more services, wherein the impact is determined according to the change in the specification and the model which comprises the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules, such that when an enterprise element changes in the model based on the obtained specification change, one or more of the impact rules are used to propagate the change across the model to identify which enterprise elements across the multiple domains are affected.
24. An article of manufacture for determining an impact of a change in a specification on one or more services associated with an enterprise, the article of manufacture tangibly embodying a computer readable program code which, when executed, causes the computer to:
obtaining the change in the specification associated with the enterprise, wherein the specification represents a capability of the enterprise to satisfy a service request;
obtaining a plurality of enterprise elements, wherein the enterprise elements are components of the enterprise;
obtaining one or more structural rules stating relationships among the plurality of enterprise elements;
obtaining one or more pre-defined impact rules indicating one or more possible changes associated with the enterprise, the one or more pre-defined impact rules having been pre-defined independent of the one or more services associated with the enterprise;
wherein the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules are stored in a data structure in the form of a model such that the enterprise elements from a non-technical domain of the enterprise and the enterprise elements from a technical domain of the enterprise that are used to implement the enterprise elements of the non-technical domain, and dependencies there between, are represented in the model, and wherein the enterprise elements from the technical domain represent components of a system architecture used to realize the enterprise elements of the non-technical domain; and
determining the impact of the change in the specification on the one or more services, wherein the impact is determined according to the change in the specification and the model which comprises the plurality of enterprise elements, the one or more structural rules, and the one or more pre-defined impact rules, such that when an enterprise element changes in the model based on the obtained specification change, one or more of the impact rules are used to propagate the change across the model to identify which enterprise elements across the multiple domains are affected.
25. The article of manufacture of claim 24, wherein the plurality of enterprise elements comprises at least one of: (i) an enterprise object; (ii) an enterprise scenario; (iii) an enterprise process; (iv) enterprise logic describing the enterprise process; (v) a service; (vi) a service container referring to at least one service; (vii) service logic describing a process flow among the at least one service; (viii) a message; (ix) a message container; and (x) an enterprise fact, and wherein the enterprise scenario describes at least one of: (i) what the enterprise does, and (ii) how the enterprise functions.