Rule based system and method for automatically generating photomask orders in a specified order format

• US 6,842,881 B2
• Filed: 07/30/2002
• Issued: 01/11/2005
• Est. Priority Date: 07/30/2002
• Status: Expired due to Term

• Current Assignee: Phototronics Incorporated
• Original Assignee: Phototronics Incorporated
• Inventors: Croke, Charles E., Ridgway, Nicolas P
• Primary Examiner(s): Smith, Matthew
• Assistant Examiner(s): LEVIN, NAUM B
• Application Number:
  US10/209,254
• Publication Number:
  US 20040025137A1
• Time in Patent Office: 896 Days
• Field of Search: 716/1, 716 19- 21, 716/4, 716/11, 705 26- 27, 705/75, 700/121, 717104-108
• US Class Current: 716/50
• CPC Class Codes: G03F 1/68 Preparation processes not covered by groups G03F1/20 - G03F1/50
• CPC Class Codes: G06F 2111/04 Constraint-based CAD
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]
• CPC Class Codes: G06Q 30/0641 Shopping interfaces

Abstract

The present invention relates generally to a rule based system and method for automatically generating photomask orders in a specified format, and more particularly, relates to software which includes templates in which photomask order data is entered and rules for guiding the user in entering such data and rules for ensuring that such data is entered accurately. The rules and templates implemented in the present invention are organized and stored in a manner which allows for the software to be easily adapted to meet the criteria of any existing standard (e.g., SEMI P10) or proprietary photomask order format now known or hereinafter developed. Additionally, the software of the present invention provides for the ability to generate new photomask orders using templates and/or existing photomask order data.

Claims

1. A rule-based system for generating photomask orders in a specified format comprising:

at least one template for the entry and storage of photomask order data, wherein said template is created based upon requirements of a specified photomask format;

at least one first set of rules corresponding to said at least one template, wherein said first set of rules is stored separately from said at least one template and includes instructions which ensure that a user enters complete information into said template as required by the specified format;

at least one second set of rules which corresponds to said at least one template, wherein said second set of rules is stored separately from said at least one template and includes instructions which ensure that the user enters accurate information to said template as required by the specified format; and

a graphical user interface associated with at least one said template, wherein the user can access said at least one template to enter photomask order data and create an order in the specified format.

2. The system of claim 1, wherein said at least one template and said at least one first and second set of rules are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

3. The system of claim 2, wherein said at least one template includes components, wherein data which can be entered into said components are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

4. The system of claim 2, wherein said at least one template includes subcomponents, wherein data which can be entered into said subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

5. The system of claim 2, wherein said at least one template includes components and subcomponents, wherein data which can be entered into said components and subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

6. The system of claim 5, wherein the type of data that can be entered into said components and said subcomponents is limited to specific attributes set in accordance with the requirements of a particular standard and/or proprietary photomask format.

7. The system of claim 1, wherein said first set of rules specify the type of photomask data which must, can and/or must not be entered to complete a photomask order in a specified format.

8. The system of claim 1, wherein said second set of rules specify the format in which the photomask data required to be entered by said first set of rules must, can and/or must not be input.

9. The system of claim 8, wherein said format is a binary, string, integer, real number, date, Boolean and/or a list.

10. The system of claim 1, wherein said system includes instructions for associating said first and second sets of rules with said templates.

11. The system of claim 1, wherein said first and second sets of rules are combined to form a single set of rules.

12. The system of claim 1, wherein said templates and said first and second sets of rules are stored external to the system.

13. The system of claim 12, wherein said templates and said first and second sets of rules are stored in a relational database.

14. The system of claim 12, wherein said templates and said first and second sets of rules are an XML file.

15. The system of claim 12, wherein said first and second sets of rules and templates are stored as an object-oriented class.

16. The system of claim 1, further comprising a search engine for searching for specific templates and/or order data previously generated on said system and merging said previously generated templates and/or order data into at least one new template and/or order.

17. The system of claim 1, wherein said at least one template is interpreted by a software object and said at least one first and second sets of rules are embedded within said software objects.

18. The system of claim 17, wherein said at least one first and second sets of rules include instructions which relate to one or more attributes of said software objects.

19. The system of claim 18, wherein said software objects are hierarchical.

20. The system of claim 1, wherein said system is deployed as a stand-alone secure application.

21. A rule-based system for generating photomask orders and/or templates in a specified format comprising:

at least one template for the entry and storage of photomask order data, wherein said template is created based upon requirements of a specified photomask format;

at least one set of rules corresponding to said at least one template, wherein said rules govern the entry of photomask order data into said template as required by the specified format,

a graphical user interface associated with said at least one template, wherein the user can access said at least one template to enter photomask order data and create an order in the specified format; and

a search engine for locating preexisting photomask order data and/or at least one preexisting template and merging at least a portion of said preexisting order data or said at least one preexisting template into a new order and/or new template in the specified format.

22. The system of claim 21, wherein said at least one template and said at least one set of rules are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

23. The system of claim 22, wherein said at least one template includes components, wherein data which can be entered into said components are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

24. The system of claim 22, wherein said at least one template includes subcomponents, wherein data which can be entered into said subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

25. The system of claim 22, wherein said at least one template includes components and subcomponents, wherein data which can be entered into said components and subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

26. The system of claim 25, wherein the type of data that can be entered into said components and said subcomponents is limited to specific attributes set in accordance with the requirements of a particular standard and/or proprietary photomask format.

27. The system of claim 21, wherein said at least one set of rules includes instructions for ensuring that a user enters complete and accurate information into said at least one template.

28. The system of claim 27, wherein said at least one set of rules specify the format and type of photomask data which must, can and/or must not be entered.

29. The system of claim 28, wherein said format is a binary, string, integer, real number, date, Boolean and/or a list.

30. The system of claim 21, wherein said system includes instructions for associating said at least one first set of rules with said at least one template.

31. The system of claim 21, wherein said templates and said at least one set of rules is stored external to the system.

32. The system of claim 31, wherein said templates and said at least one set of rules is stored in a relational database.

33. The system of claim 31, wherein said templates and said at least one set of rules is an XML file.

34. The system of claim 31, wherein said at least one set of rules is stored as an object-oriented class.

35. The system of claim 21, wherein said at least one template is interpreted by a software object and said at least one set of rules is embedded within said software objects.

36. The system of claim 35, wherein said at least one set of rules includes instructions which relate to one or more attributes of said software objects.

37. The system of claim 36, wherein said software objects are hierarchical.

38. The system of claim 21, wherein said system is deployed as a stand-alone secure application.

39. A rule-based system for generating photomask orders in a specified format comprising:

at least one template for the entry and storage of photomask order data, wherein said template is created based upon requirements of a specified photomask format;

at least one set of rules corresponding to said at least one template, wherein said rules govern the entry of photomask order data into said template as required by the specified format;

a graphical user interface associated with said at least one template, wherein the user can access said at least one template to enter photomask order data and create an order in the specified format; and

said at least one template includes components and subcomponents, wherein one or more subcomponents may be copied to one or more other subcomponents within said order in the specified format.

40. The system of claim 39, wherein said at least one template and said at least one set of rules are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

41. The system of claim 40, wherein data which can be entered into said components is set in accordance with the requirements of a particular standard and/or proprietary photomask format.

42. The system of claim 40, wherein data which can be entered into said subcomponents is set in accordance with the requirements of a particular standard and/or proprietary photomask format.

43. The system of claim 40, wherein data which can be entered into said components and subcomponents is set in accordance with the requirements of a particular standard and/or proprietary photomask format.

44. The system of claim 43, wherein the type of data that can be entered into said components and said subcomponents is limited to specific attributes set in accordance with the requirements of a particular standard and/or proprietary photomask format.

45. The system of claim 39, wherein said at least one set of rules includes instructions for ensuring that a user enters complete and accurate information into said at least one template.

46. The system of claim 45, wherein said at least one set of rules specify the format and type of photomask data which must, can and/or must not be entered.

47. The system of claim 46, wherein said format is a binary, string, integer, real number, date, Boolean and/or a list.

48. The system of claim 39, wherein said system includes instructions for associating said at least one first set of rules with said at least one template.

49. The system of claim 39, wherein said templates and said at least one set of rules is stored external to the system.

50. The system of claim 49, wherein said templates and said at least one set of rules is stored in a relational database.

51. The system of claim 49, wherein said templates and said at least one set of rules is an XML file.

52. The system of claim 49, wherein said at least one set of rules is stored as an object-oriented class.

53. The system of claim 49, wherein said at least one template is interpreted by a software object and said at least one set of rules is embedded within said software objects.

54. The system of claim 53, wherein said at least one set of rules includes instructions which relate to one or more attributes of said software objects.

55. The system of claim 54, wherein said software objects are hierarchical.

56. The system of claim 39, wherein said system is deployed as a stand-alone secure application.

57. The system of claim 39, wherein said at least one template and said at least one set of rules are stored separately.

58. The system of claim 39, further comprising a search engine for searching for specific templates and/or order data previously generated on said system and merging said previously generated templates and/or order data into at least one new template and/or order.

59. A rule-based system for generating photomask orders in a specified format comprising:

at least one template for the entry and storage of photomask order data, wherein said template is created based upon requirements of a specified photomask format;

at least one set of rules corresponding to said at least one template, wherein said rules govern the entry of photomask order data into said template as required by the specified format, wherein rules are stored independently of said at least one template; and

a graphical user interface associated with said at least one template, wherein the user can access said at least one template to enter photomask order data and create an order in the specified format.

60. The system of claim 59, wherein said at least one template and said at least one set of rules are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

61. The system of claim 60, wherein said at least one template includes components, wherein data which can be entered into said components are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

62. The system of claim 60, wherein said at least one template includes subcomponents, wherein data which can be entered into said subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

63. The system of claim 60, wherein said at least one template includes components and subcomponents, wherein data which can be entered into said components and subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

64. The system of claim 63, wherein the type of data that can be entered into said components and said subcomponents is limited to specific attributes set in accordance with the requirements of a particular standard and/or proprietary photomask format.

65. The system of claim 59, wherein said at least one set of rules includes instructions for ensuring that a user enters complete and accurate information into said at least one template.

66. The system of claim 65, wherein said at least one set of rules specify the format and type of photomask data which must, can and/or must not be entered.

67. The system of claim 66, wherein said format is a binary, string, integer, real number, date, Boolean and/or a list.

68. The system of claim 59, wherein said system includes instructions for associating said at least one first set of rules with said at least one template.

69. The system of claim 59, wherein said templates and said at least one set of rules is stored external to the system.

70. The system of claim 69, wherein said templates and said at least one set of rules is stored in a relational database.

71. The system of claim 59, wherein said templates and said at least one set of rules is an XML file.

72. The system of claim 59, wherein said at least one set of rules is stored as an object-oriented class.

73. The system of claim 59, wherein said at least one template is interpreted by a software object and said at least one set of rules is embedded within said software objects.

74. The system of claim 73, wherein said at least one set of rules includes instructions which relate to one or more attributes of said software objects.

75. The system of claim 74, wherein said software objects are hierarchical.

76. The system of claim 59, wherein said system is deployed as a stand-alone secure application.

77. The system of claim 59, further comprising a search engine for searching for specific templates and/or order data previously generated on said system and merging said previously generated templates and/or order data into at least one new template and/or order.

78. A rule-based system for generating photomask orders in at least two different specified formats comprising:

at least one template for the entry and storage of photomask order data, wherein said template is created based upon requirements of a specified photomask format;

at least one set of rules corresponding to said at least one

template, wherein said at least one set of rules includes instructions which ensure that a user enters complete and/or accurate information into said template as required by said at least two different formats,

a graphical user interface associated with said at least one template, wherein the user can access said at least one template to enter photomask order data and create an order in said at least two different specified formats.

79. The system of claim 78, wherein said at least one template and said at least one set of rules are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

80. The system of claim 79, wherein said at least one template includes components, wherein data which can be entered into said components are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

81. The system of claim 79, wherein said at least one template includes subcomponents, wherein data which can be entered into said subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

82. The system of claim 79, wherein said at least one template includes components and subcomponents, wherein data which can be entered into said components and subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

83. The system of claim 82, wherein the type of data that can be entered into said components and said subcomponents is limited to specific attributes set in accordance with the requirements of a particular standard and/or proprietary photomask format.

84. The system of claim 78, wherein said at least one set of rules includes instructions for ensuring that a user enters complete and accurate information into said at least one template.

85. The system of claim 84, wherein said at least one set of rules specify the format and type of photomask data which must, can and/or must not be entered.

86. The system of claim 85, wherein said format is a binary, string, integer, real number, date, Boolean and/or a list.

87. The system of claim 78, wherein said system includes instructions for associating said at least one first set of rules with said at least one template.

88. The system of claim 78, wherein said templates and said at least one set of rules is stored external to the system.

89. The system of claim 88, wherein said templates and said at least one set of rules is stored in a relational database.

90. The system of claim 88, wherein said templates and said at least one set of rules is an XML file.

91. The system of claim 88, wherein said at least one set of rules is stored as an object-oriented class.

92. The system of claim 88, wherein said at least one template is interpreted by a software object and said at least one set of rules is embedded within said software objects.

93. The system of claim 92, wherein said at least one set of rules includes instructions which relate to one or more attributes of said software objects.

94. The system of claim 93, wherein said software objects are hierarchical.

95. The system of claim 78, wherein said system is deployed as a stand-alone secure application.

96. The system of claim 78, wherein said at least one template and said at least one set of rules are stored separately.

97. The system of claim 78, further comprising a search engine for searching for specific templates and/or order data previously generated on said system and merging said previously generated templates and/or order data into at least one new template and/or order.

98. A rule-based system for generating photomask orders in a specified format comprising:

at least one template for the entry and storage of photomask order data, wherein said template is created based upon requirements of a specified photomask format and wherein at least some of said photomask order data is imported from a preexisting order template;

at least one set of rules corresponding to said at least one template, wherein said rules govern the entry of photomask order data into said template as required by the specified format,

a graphical user interface in with at least one said template, wherein the user can access said at least one template to enter photomask order data and create an order in the specified format.

99. The system of claim 98, wherein said at least one template and said at least one set of rules are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

100. The system of claim 99, wherein said at least one template includes components, wherein data which can be entered into said components are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

101. The system of claim 99, wherein said at least one template includes subcomponents, wherein data which can be entered into said subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

102. The system of claim 99, wherein said at least one template includes components and subcomponents, wherein data which can be entered into said components and subcomponents are set in accordance with the requirements of a particular standard and/or proprietary photomask format.

103. The system of claim 102, wherein the type of data that can be entered into said components and said subcomponents is limited to specific attributes set in accordance with the requirements of a particular standard and/or proprietary photomask format.

104. The system of claim 98, wherein said at least one set of rules includes instructions for ensuring that a user enters complete and accurate information into said at least one template.

105. The system of claim 104, wherein said at least one set of rules specify the format and type of photomask data which must, can and/or must not be entered.

106. The system of claim 105, wherein said format is a binary, string, integer, real number, date, Boolean and/or a list.

107. The system of claim 98, wherein said system includes instructions for associating said at least one first set of rules with said at least one template.

108. The system of claim 98, wherein said templates and said at least one set of rules is stored external to the system.

109. The system of claim 108, wherein said templates and said at least one set of rules is stored in a relational database.

110. The system of claim 108, wherein said templates and said at least one set of rules is an XML file.

111. The system of claim 108, wherein said at least one set of rules is stored as an object-oriented class.

112. The system of claim 108, wherein said at least one template is interpreted by a software object and said at least one set of rules is embedded within said software objects.

113. The system of claim 112, wherein said at least one set of rules includes instructions which relate to one or more attributes of said software objects.

114. The system of claim 113, wherein said software objects are hierarchical.

115. The system of claim 98, wherein said system is deployed as a stand-alone secure application.

116. The system of claim 98, wherein said at least one template and said at least one set of rules are stored separately.

117. The system of claim 98, further comprising a search engine for searching for specific templates and/or order data previously generated on said system and merging said previously generated templates and/or order data into at least one new template and/or order.