Method for creating down load script, product for storing data, product for storing machine accessible instruction, and method for processing down load script
Abstract
Problem to be solved.To disclose a method for setting an absence state of equipment in a process factory and a module class object. A method disclosed as an example for creating a configuration entity used to configure a process factory includes a first data structure indicating one or more process elements that make up the process entity. It consists of creating a class object that represents a process entity within a process factory and creating a module object based on a class object that contains a second data structure, the second data structure of which constitutes the process entity. Includes a configurable first indicator to indicate whether a particular process element that matches the first of one or more process elements is absent. [Selection diagram] Fig. 5

Term
9.8 yearsto projected expiry
Projected expiry 25 July 2036, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
94 claims: 13 independent, 81 dependent
- 1プロセス工場の設定に使用される設定エンティティを作成する方法であり、 プロセスエンティティを構成する一つ又は複数のプロセスの要素を示す第1のデータ構造を含むプロセス工場内のプロセスエンティティを示すクラスオブジェクトを作成することと、 第2のデータ構造を含むクラスオブジェクトに基づいてモジュールオブジェクトを作成することを含み;該第2のデータ構造が、プロセスエンティティを構成する一つ又は複数のプロセス要素の第1のものに一致する特定のプロセス要素が不存在かどうかを示すための設定可能な第1の指標を含む、ことを特徴とする方法。
- 2クラスオブジェクトにより表されるプロセス工場の特定のプロセスエンティティに、該作成されたモジュールオブジェクトを結合することをさらに含む請求項1に記載の方法。
- 3クラスオブジェクトに基づいたモジュールオブジェクトの作成により特定のプロセス要素用のオブジェクトが作成されることを特徴とし、且つ、 第2のデータ構造が、プロセス要素オブジェクトの描写を含み、第1の指標がプロセス要素オブジェクトのパラメータであることを特徴とする請求項1に記載の方法。
- 4特定のプロセス要素が欠如状態にあるとして構成されない場合、プロセス要素オブジェクトを、プロセス工場の特定のプロセス要素に結合することをさらに含む請求項2に記載の方法。
- 5クラスオブジェクトからモジュールオブジェクトを作成するためおよび、モジュールオブジェクトをプロセス工場の特定のプロセスエンティティに結合するためにユーザーインタフェースを提示することをさらに含む請求項1に記載の方法。
- 6第2のデータ構造が、特定のプロセス要素に関連したプログラミングをさらに含むことを特徴とし、且つ、プログラミングが、プロセス工場の稼動中に該設定可能な第1の指標に基づいて実行されることになっていることを特徴とする請求項1に記載の方法。
- 7第1の指標に基づいてプログラミングの制御を実行することをさらに含む請求項6に記載の方法。
- 8第1の指標によって、特定のプロセス要素が不存在の場合にもプログラムがエラーなく実行することを許可することを特徴とする請求項6に記載の方法。
- 9クラスオブジェクトが、第1の指標の設定を可能にする第2の指標を含むことを特徴とする請求項1に記載の方法。
- 10第2の指標の構成を図るためにユーザーインタフェースを提示することをさらに含む請求項9に記載の方法。
- 11第2の指標が第1の所定値を有する場合に第1の指標の構成をできるようにすることをさらに含む請求項9に記載の方法。
- 12クラスオブジェクトへの変更をモジュールオブジェクトに適用することをさらに含む請求項9に記載の方法。
- 13第1の指標の値に関係なく、該変更が、モジュールオブジェクトに適用されうることを特徴とする請求項12に記載の方法。
- 14モジュールオブジェクトに変更がなされる際に第1の指標の状態を維持することをさらに含む請求項12に記載の方法。
- 15第1の指標の構成を図るためにユーザーインタフェースを提示することをさらに含む請求項1に記載の方法。
- 16第1の指標を構成するためにバルク入力データを処理することをさらに含む請求項1に記載の方法。
- 17特定のプロセス要素が無視されていることを示すユーザーインタフェースの提示をさらに含む請求項1に記載の方法。
- 18第2のデータ構造が、プロセスエンティティを構成する一つ又は複数のプロセス要素に一致する一つ又は複数の特定の現存プロセス要素に関する一つ又は複数の付加的な指標をさらに含むことを特徴とし、且つ、 該一つ又は複数の特定の現存プロセス要素に関連したプログラムがプロセス工場の稼動中に実行されることになっていることを特徴とする請求項1に記載の方法。
- 19プロセスエンティティがユニットであり、一つ又は複数のプロセス要素がユニットの下位要素であることを特徴とする請求項1に記載の方法。
- 20ユニットの一つ又は複数の下位要素が設備要素を含むことを特徴とする請求項19に記載の方法。
- 21プロセスエンティティが設備エンティティであり、一つ又は複数のプロセス要素が設備エンティティの下位要素であることを特徴とする請求項1に記載の方法。
- 22第1の指標に基づいてプロセス工場のコントローラのダウンロードスクリプトを作成することをさらに含む請求項1に記載の方法。
- 23プロセス工場のコントローラに第1の指標を備えることをさらに含む請求項1に記載の方法。
- 24プロセス工場の設定に使用されるモジュール・クラスオブジェクト・エンティティであり、 機械アクセス可能なメモリと;プロセス工場内のプロセスエンティティを示し、且つプロセスエンティティを構成する一つ又は複数のプロセス要素を示す第1のデータ構造とクラスオブジェクトから作成されたモジュールオブジェクトを示す第2のデータ構造とを含む、機械アクセス可能なメモリ上に格納されたクラスオブジェクトとからなり、 該モジュールオブジェクトが、プロセスエンティティを構成する一つ又は複数のプロセス要素の第1のものに一致する特定のプロセス要素が不存在かどうかを示す設定可能な第1の指標を含むように構成されることを特徴とする、モジュール・クラスオブジェクト・エンティティ。
- 25第1のデータ構造が、クラスオブジェクトにより表されるプロセス工場の特定のプロセスエンティティにモジュールオブジェクトを結合すること含むことを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 26モジュールオブジェクトが、特定のプロセス要素用のオブジェクトへの参照を含んでいることを特徴とし、且つ、 第2のデータ構造が、プロセス要素オブジェクトの参照を含み、第1の指標がプロセス要素オブジェクトのパラメータであることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 27特定のプロセス要素が欠如状態のものとして構成されない場合に、プロセス要素オブジェクトが、プロセス工場の特定のプロセス要素へのプロセス要素オブジェクトの結合を含むことを特徴とする請求項26に記載のモジュール・クラスオブジェクト・エンティティ。
- 28モジュールオブジェクトが、特定のプロセス要素に関連したプログラムをさらに含むことを特徴とし、且つ プログラムが、プロセス工場の稼動中に第1の指標に基づいて実行されることになっていることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 29第1の指標が、特定のプロセス要素が欠如状態の場合にも、プログラムがエラーなく実行することを可能にすることを特徴とする請求項28に記載のモジュール・クラスオブジェクト・エンティティ。
- 30第1の指標が第2のデータ構造に関連したパラメータで、プログラムの制御実行に使用可能であることを特徴とする請求項28に記載のモジュール・クラスオブジェクト・エンティティ。
- 31第1の指標が、プログラムの流量を制御するために数値と比較されうるパラメータであることを特徴とする請求項28に記載のモジュール・クラスオブジェクト・エンティティ。
- 32モジュールオブジェクトがクラスオブジェクトから作成され、クラスオブジェクトが第1の指標の設定を可能にする第2の指標を含んでいることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 33第2の指標が第1の所定値を有する場合、第1の指標の値が選択可能であることを特徴とする請求項32に記載のモジュール・クラスオブジェクト・エンティティ。
- 34クラスオブジェクトになされた変更が、モジュールオブジェクトにより継承されることを特徴とする請求項32に記載のモジュール・クラスオブジェクト・エンティティ。
- 35第1の指標の状態を維持しながら、クラスオブジェクトになされた変更がモジュールオブジェクトに自動的に適用されることを特徴とする請求項32に記載のモジュール・クラスオブジェクト・エンティティ。
- 36第1の指標が設定インターフェースを介してユーザ設定できることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 37第1の指標がバルク処理アプリケーションを介して設定可能であることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 38第2のデータ構造が、プロセスエンティティを構成する一つ又は複数のプロセス要素に一致する一つ又は複数の特定の現存するプロセス要素の付加的な指標を一つ又は複数および、プロセス工場の稼動中に実行される一つ又は複数の特定の現存するプロセス要素に関連したプログラムをさらに含むことを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 39プロセスエンティティが1個のユニットであり、一つ又は複数のプロセス要素がユニットの下位要素であることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 40ユニットの下位要素の一つ又は複数が設備要素を含んでいることを特徴とする請求項39に記載のモジュール・クラスオブジェクト・エンティティ。
- 41プロセスエンティティが設備エンティティであり、一つ又は複数のプロセス要素が設備エンティティの下位要素であることを特徴とする請求項24に記載のモジュール・クラスオブジェクト・エンティティ。
- 42実行時、機械に、プロセスエンティティを構成する一つ又は複数のプロセス要素を示す第1のデータ構造を含んでいるプロセス工場内のプロセスエンティティを示すクラスオブジェクトを作成させ、且つ、第2のデータ構造を含んでいるクラスオブジェクトに基づいてモジュールオブジェクトを作成させ、該第2のデータ構造が、プロセスエンティティを構成する一つ又は複数のプロセス要素の最初の一つに適合する特定のプロセス要素が欠如状態であるかどうかを示す設定可能な第1の指標を含んでいることを特徴とする、機械可読指示を格納する製造品。
- 43機械可読指示が、実行時、機械に作成されたモジュールオブジェクトを、クラスオブジェクトにより表されるプロセス工場の特定のプロセスエンティティに結び付けさせることを特徴とする請求項42に記載の製造品。
- 44機械可読指示が、実行時、クラスオブジェクトからモジュールオブジェクトを作成しモジュールオブジェクトをプロセス工場の特定のプロセスエンティティに結合するために、機械にユーザーインタフェースを提示させることを特徴とする請求項42に記載の製造品。
- 45機械可読指示が、実行時、機械に第1の指標に基づいてプログラムの制御実行を行わせることを特徴とする請求項42に記載の製造品。
- 46クラスオブジェクトが、第1の指標の構成を可能にする第2の指標を含んでいることを特徴とする請求項42に記載の製造品。
- 47機械可読指示が、実行時、機械に、第2の指標の構成を図るユーザーインタフェースを提示させることを特徴とする請求項46に記載の製造品。
- 48機械可読指示が、実行時、機械に、第2の指標が第1の所定値を有する場合に第1の指標の構成を可能とさせることを特徴とする請求項46に記載の製造品。
- 49機械可読指示が、実行時、機械に、モジュールオブジェクトへのクラスオブジェクトになされた変更を作用させることを特徴とする請求項46に記載の製造品。
- 50機械可読指示が、実行時、機械に、第1の指標の構成を図るユーザーインタフェースを提示させることを特徴とする請求項42に記載の製造品。
- 51プロセス工場を設定するための設定システムであり、 プロセス工場内のプロセスエンティティを表し且つプロセスエンティティの一つ又は複数のプロセス要素の関連性を含むモジュール・クラスオブジェクトを格納するライブラリと、 プロセッサと、 実行時、モジュール・クラスオブジェクトに基づいてモジュールオブジェクト・データ構造を作成するため、且つ、プロセスエンティティの特定のプロセス要素に一つ又は複数のプロセス要素を関連させるために、プロセッサに第1のユーザーインタフェースを提示させると共に、一つ又は複数のプロセス要素の特定のものの不存在指標を設定するために、該プロセッサに第2のユーザーインタフェースを提示させるところの機械アクセス可能指示と、からなる構成システム。
- 52実行時に、機械可読指示が、実行時、プロセッサに、一つ又は複数のプロセス要素の特定のものの不存在を設定することを可能にするために第3のユーザーインタフェースを提示させることを特徴とする請求項51に記載の構成システム。
- 53プロセス要素の特定のものの欠如を構成することが第3のユーザーインタフェースを介して可能な場合、実行時機械可読指示が、実行時、プロセッサに第2のユーザーインタフェースを提示させることを特徴とする請求項52に記載の構成システム。
- 54実行時機械可読指示が、実行時、プロセッサに、欠如指標に基づいて一つ又は複数のプロセス要素の特定のもののプログラムを構成するために第3のユーザーインタフェースを提示させることを特徴とする請求項51に記載の構成システム。
- 55実行時機械可読指示が、実行時、プロセッサに、モジュールオブジェクト・データ構造に欠如指標を格納させることを特徴とする請求項51に記載の構成システム。
- 56実行時機械可読指示が、実行時、プロセッサに、第1のユーザーインタフェースによってモジュール・クラスオブジェクトのプロパティを設定させ、該プロパティがライブラリに格納されることを特徴とする請求項51に記載の構成システム。
- 57実行時機械可読指示が、実行時、プロセッサに、作成されたモジュールオブジェクトおよび欠如指標に基づいてプロセスエンティティのダウンロードスクリプトを作成させることを特徴とする請求項51に記載の構成システム。
- 58実行時機械可読指示が、実行時、プロセッサに、プロセス工場のコントローラに欠如指標を提供させることを特徴とする請求項51に記載の構成システム。
- 59実行時機械可読指示が、実行時、プロセッサに、コントローラのメモリに欠如指標を書き込ませることを特徴とする請求項58に記載の構成システム。
- 60プロセスエンティティがユニットであり、一つ又は複数のプロセス要素がユニットの下位要素であることを特徴とする請求項51に記載の構成システム。
- 61ユニットの下位要素の一つ又は複数が設備要素を含んでいることを特徴とする請求項60に記載の構成システム。
- 62プロセスエンティティが設備エンティティであり、一つ又は複数のプロセス要素が設備エンティティの下位要素であることを特徴とする請求項51に記載の構成システム。
- 63プロセス工場のコントローラ用のダウンロードスクリプトを作成する方法であり、コントローラに関連したプロセスエンティティのプロセス要素が欠如状態に構成されているかどうかを判断することと、 プロセスエンティティが無視されるように構成されている場合、プロセスエンティティが欠如状態であることを示すためにダウンロードスクリプトにフィールドを追加することとからなり、 フィールドが第1の値に設定される場合コントローラにより使用されるフィールドがエラーを抑制する、ことを特徴とする方法。
- 64プロセスエンティティが欠如状態に構成されているかどうかを判断することが、プロセス要素に関連したモジュールオブジェクトのパラメータに基づく請求項63に記載の方法。
- 65プロセスエンティティが無視されるように構成されるかどうかを判断することが、パラメータを所定値と比較することからなることを特徴とする請求項63に記載の方法。
- 66パラメータおよび所定値がブールの値であることを特徴とする請求項65に記載の方法。
- 67フィールドの追加が、ダウンロードスクリプトの節にブール値化されたフィールドを追加することからなることを特徴とする請求項63に記載の方法。
- 68プロセスエンティティがユニットの下位要素であることを特徴とする請求項63に記載の方法。
- 69プロセスエンティティが設備エンティティであることを特徴とする請求項63に記載の方法。
- 70プロセスエンティティが設備エンティティの下位要素であることを特徴とする請求項63に記載の方法。
- 71プロセスエンティティがモジュールオブジェクトの従属オブジェクトであることを特徴とする請求項63に記載の方法。
- 72機械アクセス可能なデータを格納する製造品において、 該データがプロセス工場のコントローラのダウンロードスクリプトからなり、 該スクリプトが、プロセス工場のプロセスエンティティの要素を識別する第1のフィールドおよび、プロセスエンティティが欠如状態かどうか示す第2のフィールドを含む、ことを特徴とする、機械アクセス可能なデータを格納する製造品。
- 73第2のフィールドがブール値からなることを特徴とする請求項72に記載の製造品。
- 74ブール値が、プロセスエンティティに関連したパラメータを所定値と比較することにより決定されることを特徴とする請求項73に記載の製造品。
- 75パラメータが第2のブール値であり、第2のブール値がTRUE(真)の値を表す場合に第2のフィールドがTRUE(真)の値を表すように設定されることを特徴とする請求項74に記載の製造品。
- 76プロセスエンティティが1ユニットの下位要素である。ことを特徴とする請求項72に記載の製造品。
- 77プロセスエンティティが設備エンティティであることを特徴とする請求項72に記載の製造品。
- 78プロセスエンティティが設備エンティティの下位要素であることを特徴とする請求項72に記載の製造品。
- 79プロセスエンティティがモジュールオブジェクトの従属オブジェクトであることを特徴とする請求項72に記載の製造品。
- 80機械可読指示を格納する製造品において、 機械可読指示が、実行時、機械に、コントローラに関連したプロセスエンティティのプロセス要素が欠如状態に構成されているかどうかを判断させ且つ、プロセスエンティティが無視されるように構成されている場合にプロセスエンティティが欠如状態であることを示すためにダウンロードスクリプトにフィールドを追加させ、 フィールドが第1の値に設定される場合に、エラーを抑制するためにコントローラによりフィールドが使用されることを特徴とする機械可読指示を格納する製造品
- 81機械可読指示が、実行時、機械に、プロセス要素に関連したモジュールオブジェクトのパラメータに基づいてプロセスエンティティを欠如状態に構成するかどうかを判断させることを特徴とする請求項80に記載の製造品。
- 82機械可読指示が、実行時、機械に、パラメータを所定値と比較することによりプロセスエンティティが無視されるように構成されているかどうかを判断させる、ことを特徴とする請求項81に記載の製造品。
- 83機械可読指示が、実行時、機械に、ダウンロードスクリプトの節にブール値化されたフィールドを追加することによりフィールドを追加させることを特徴とする請求項80に記載の製造品。
- 84プロセス工場のコントローラでダウンロードスクリプトを処理する方法であり、 コントローラに関連したプロセスエンティティのプロセス要素が欠如状態に構成されているかどうかを判断するためにダウンロードスクリプトの節をパーズすることと、 プロセス要素が欠如状態に構成されている場合にプロセス要素に関連したエラーを無視することと、からなる方法。
- 85プロセス要素が欠如状態に構成されていない場合に、プロセス要素に関連した制御ルーチンをダウンロードすることをさらに含む請求項84に記載の方法。
- 86プロセスエンティティが欠如状態に構成されているかどうかを判断することが節のフィールドに基づいて行われることを特徴とする請求項84に記載の方法。
- 87フィールドがブール値化されたフィールドであることを特徴とする請求項86に記載の方法。
- 88プロセスエンティティが1ユニットの下位要素であることを特徴とする請求項84に記載の方法。
- 89プロセスエンティティが設備エンティティであることを特徴とする請求項84に記載の方法。
- 90プロセスエンティティが設備エンティティの下位要素であることを特徴とする請求項84に記載の方法。
- 91プロセスエンティティがモジュールオブジェクトの従属オブジェクトであることを特徴とする請求項84に記載の方法。
- 92実行時、機械に、コントローラに関連したプロセスエンティティのプロセス要素が欠如状態に構成されているかどうかを判断するためにダウンロードスクリプトの節をパーズさせ、プロセス要素が欠如状態に構成されている場合にはプロセス要素に関連したエラーを無視させる機械可読指示を格納する製造品。
- 93プロセス要素が欠如状態に構成されてない場合に、機械可読指示が、実行時、機械に、プロセス要素に関連した制御ルーチンをダウンロードさせることを特徴とする請求項92に記載の製造品。
- 94機械可読指示が、実行時、節のフィールドに基づいてプロセスエンティティが欠如状態に構成されているかどうか、を機械に判断させることを特徴とする請求項92に記載の製造品。
Independent claims94
126 paragraphs, as filed
The present disclosure relates generally to process factories, and more specifically to methods and module class objects for setting the absence of equipment in process factories.
Processes and systems related to chemicals, petroleum, and / or others, and distributed process control systems such as those used in process factories are usually via analog, digital, or analog-digital composite buses, etc. Includes one or more process controllers communicatively linked to one or more field devices. In such systems and / or processes, field devices such as valves, valve positioners, switches and / or transmitters (eg, sensors for temperature, pressure, level, flow rate, etc.) are installed in the process environment and valves. Performs process control functions and / or process control functions such as opening and closing of valves and measurement of process parameters. Also, smart field devices, such as field devices that are adaptable to any Fieldbus protocol, have a wide variety of functions, including control calculations, alarm functions and / or other control and / or monitoring functions, by or on the controller. Can be done. A process controller that can be installed in the factory environment also receives a signal indicating the process measurements and results generated by the field device and / or other information about the field device. The process controller, for example, based on the received signal, makes decisions about process control, generates control signals, and / or coordinates with other functional blocks and / or control modules performed by field devices such as HART and Fieldbus field devices. Run controller applications to implement various control modules, routines and / or software threads to do so. The control module in the controller (s) sends control signals to the field device over the communication line to control the operation of the process factory.
Information from field devices and / or controllers typically goes through data highways or communication networks to one or more other hardware devices such as operator workstations, personal computers, data historians, reporting routines, centralized databases, etc. It is available from. Such devices are generally installed in control rooms or elsewhere away from the relatively harsh factory environment. These hardware devices are used, for example, by an operator to change the settings of various functions related to a process (s) in a process factory (eg, process control routines (s), and to operate a control module in a process controller and / or field device. Modifications, current status of the process (s), display of alarms generated by field devices and / or controllers, simulation of process (s) behavior for personnel training and / or testing of process control software, configuration database Run an application that allows you to maintain and / or update, etc.).
As an example, Emerson Process Management, Fisher-Rosemount Systems, The Delta VTM control system sold by Inc. is capable of supporting multiple applications that can be stored and executed in different devices installed in various different locations within the process factory. With configuration applications (stored in and / or executed in one or more operator workstations), users create and / or modify process control modules and / or data highways or communication networks. Through this, you will be able to download process control modules to a dedicated distributed controller. In general, these control modules are based on the receive input. It consists of communicably linked and interconnected functional blocks that perform functions on the premises and supply output to other functional blocks within the control mechanism. The configuration application also allows the system configuration engineer and / or operator to create and / or modify the operator interface used in the display application, eg, to display data to the operator, and / or the operator in a process control routine. It may be possible to make it possible to change settings such as setting points. Each dedicated controller (and in some cases a field device) stores and / or executes a controller application that executes a control module assigned to perform the actual process control function. For example, a display application that can be run on one or more operator workstations receives data from a controller application via a data highway and / or has a large number of operator displays, engineer displays, technician displays, and so on. Display the data to a process control system engineer, operator or user using a user interface that can provide any of the different displays. A data historian application is generally stored and / executed by a data historian device that collects and / or stores some or all of the data provided via the data highway. The configuration database application may run on yet another computer communicatively linked to the data highway to store the current process control routine configuration (s) and / or related data. Alternatively, the configuration application (s), the display application (s), the data historian application (s), the configuration database (s), and / or the configuration database application (s) can be any number of workstations. Station (eg, one workstation)
The configuration application of the embodiment includes a library of template objects such as functional block template objects and / or control module template objects used to configure and build control strategies for process factories. The template objects of the examples have the associated default characteristics so that the process engineer and / or operator can select and / or use one or more template objects to develop the control module via the configuration screen. , Settings and / or methods are provided. In the process of selecting template objects through the configuration screen, the engineer interconnects the inputs and / or outputs of these objects and / or modifies their parameters, names, tags and other characteristics in the process factory. It is possible to create a specific control module suitable for a specific application. After creating one or more such control modules, the engineer creates an instance of the control module and is the appropriate controller (s) and / or field device (s) to run during the operation of the process factory. You can download them to.
Engineers can also create one or more displays for use by operators, maintenance personnel, and others in process factories, for example by selecting and / or constructing display objects using a display creation application. These indications are generally implemented for the entire system via one or more workstations and are preset indications indicating the control system (s) in the factory and / or the operating state (s) of the equipment. To the operator or maintenance personnel. The display of the embodiment is an alarm screen that receives and / or displays an alarm generated by a controller or device in the process factory, and the operating state (s) of the controller (s) and other devices (s) in the process factory. ), A maintenance screen showing the functional status of the equipment (s) and / or equipment in the process factory, etc. In some embodiments, the display contains graphics related to the physical and logical element and is capable of communicating with the physical and or logical element to receive data about the physical and or logical element. Created through the use of objects concatenated to .. The object can change the graphic of the display screen based on the received data, for example, to indicate that the tank is half full, the flow rate measured by a flow rate sensor or the like.
Like the control settings application, the display creation application includes tanks, valves, sensors, operator control buttons (s) that can be placed on the screen with any desired settings (s) to create operator display screens, maintenance screens, etc. It is equipped with template graphic display elements such as a slide bar and on / off switch. When placed on the screen, the individual graphic elements can be interconnected on the screen in such a way as to provide different users with some information and / or an indication of the internal structure of the process factory. To animate the graphic display, the display author manually determines the position of the valve by manually specifying the association between the graphic unit and the associated data source (s) within the process factory. It connects each of the graphic elements with the data generated in the process factory, such as the data shown and the data measured by the sensor.
The control template objects included in the control settings application and the display elements included in the display creation application can be conveniently copied and used to create various control modules and graphic displays, but in most cases It is required to create many copies and / or instances of the same control module and / or graphic display for each different facility in the process factory. For example, a process factory is equipped with many instances (cases) of the same and / or similar equipment that can be controlled and / or monitored using the same basic general control module and / or display. However, in order to create these numerous control modules and / or displays, a general control module and / or display module is created, after which the general control module and / or display module is copied to each of the different applicable equipment. Module. Of course, after being copied, each of the new controls and / or display modules must be manually modified in the configuration application to specify the particular equipment to which it is attached. After that, instances must be created for all of the control and / or display modules and downloaded to the process control system (s).
Since the control module and / or display element is not modular in any way, therefore, after copying, each of the control module and / or display is to specify the equipment in the factory to which each is associated. Appropriate settings The application (s) and / or the interface (s) need to be manually and / or individually modified. In the case of a process factory that includes many repetitions of the same type of equipment (eg, multiple identical equipments), such a process is not only patience and time consuming, but also error prone. Also, once programmed, these different control modules and / or displays do not recognize each other (ie, information about what is contained in one display is not available for other displays). Therefore, in order to make changes to an already created control module, the control and / or system configuration engineer must manually make the same or similar changes to each of the different control modules in different duplication equipment. .. This is not only patience and time consuming, but also error prone. This problem also applies to graphic displays created for different sets of equipment that are repeatedly installed in the factory. In other words, once a particular control module and / or a particular graphic display is created individually and or by copying from a template object and tied to a particular set of equipment in the factory, this control module and / or The graphic display exists as a separate entity and / or object within the control system and / or process factory without automatically recognizing the same or similar other control module and / or graphic display. As a result, certain types of control modules and / or graphic displays Changes that fall under one or more of the above must be made individually for the module and display.
Furthermore, since the control module and display are separate objects, all of their internal parameters, displays, functional blocks and / or other elements can be modified, set, modified and / or displayed by any user. It must be open in the sense that it must be. Thus, for example, none of these control modules and / or display specific elements (proprietary software, methods, alarm functions, etc.) can be hidden from the control module and / display user and are immediately available.
<p num="0011"> The configuration system for the process factory uses module class objects to assist in setting, organizing, and / or modifying control and / or display operations within the process factory. Each module class object is generally a process entity (one device, one facility). , One control operation, etc.) can be used to model and / or symbolize and create instances of objects called module objects that symbolize and / or are associated with specific equipment within a process factory. Module class objects can symbolize any range of process entities desired. This means that a single module class object can be used to set up control and display tasks for process entities with any desired scope within the process factory, not just at the control module level. .. In particular, module class objects with wide applicability can be used to set vast compartments and / or parts within a process factory. Therefore, setting up a process factory is easier and less time consuming. A module class object is, for example, a unit module class object that reflects a physical device in a process factory, or a physical facility in a process factory. It can be an equipment module class object, a control module class object that reflects a control module or control mechanism in a process factory, or a display module class object that reflects a display routine that provides information to users in a process factory.</p><p num="0012"> In order to improve the utilization of the module class object in the setting work, the module class object is provided with references and placeholders for other module class objects, and the module objects created from different module class objects are provided with each other. They may be able to recognize each other and / or incorporate each other. In some embodiments, to equipment module class objects, control module class objects and / or display module class objects interconnected with other simple equipment and control modules as needed to form a unit. References can be included in unit module class objects. Similarly, an equipment module class object may contain a reference to a control and / or display module class object, while a control module class object may contain a reference to a display module class object.</p><p num="0013"> To further extend a module class object, and / or a module object created from and / from a module class object, the elements of the module class object and / or the module class object are, and / or Each part of the object created from it has properties that allow the system configuration engineer to identify, configure, and / or identify that it is in an "absent state." Equipment in such an absent state is not required and / or used by or in a particular process, equipment, equipment, etc. It is intentionally absent because of the reason. Therefore, it is different from the equipment that is absent against the original intention due to equipment failure, communication failure, installation error, or the like. By extending a module class object and a module object to include equipment that is intentionally absent, the module class object and / or the module object can transform various module objects (each variant is associated with it). Can be used to create (to benefit from changes and / or extensions made to module class objects).</p><p num="0014"> Each module class object has and is associated with an instance (module object) created from that module class object. Therefore, the created module object still recognizes the module class object. As a result, changes made to a module class object can be automatically propagated to the module object associated with that module class object. This eliminates the need to manually make the same changes to multiple control modules and / or display applications in the process factory. This feature is associated with each of multiple repetitive facilities by making changes to the appropriate module class object and automatically propagating the changes to the module object created from that module class object. Allows changes to control and / or display routines. This also eliminates the need to make the same changes to a number of different individual control modules for each of a plurality of repetitive separate installations. Similarly, the combination of different module objects related to the same module class object also allows the parameters, inputs / outputs, equipment, etc. of the module objects to be actually different devices in the process factory, for example in a single display field or screen display. It will be possible to do it in a bulk (mass batch) method by using a spreadsheet application related to. In addition, for the module object created from the module class object, which of the information the module class object to which the user does not have access can display or cannot access is not possible. Or can be controlled. Thus, information about different module objects associated with that module class object can be hidden from the operator or other users.</p>
Process factories often include repetitive equipment and / or process entities consisting of many units and / or aggregates performing similar functions and / or processing. By reusing phase classes, algorithms, settings, controls and / or display routines that are common and / or shared throughout the repeated equipment, it becomes easier to streamline the setup and / or operation of the process factory. .. Even if the repeated equipment contains modifications and / or modifications, common and / or shared phase classes, algorithms, settings, controls and / or display routines may still be available. For example, a first processor with two or more valves A second device, where one of the valves is intentionally absent. It can be used (diverted) repeatedly as a process entity. However, the first and second process entities share a common structure and can be controlled using similar routines. In particular, if the shared routine is aware of (and has the ability to identify) equipment that is intentionally absent, the shared routine can be executed without error even in the absence of equipment. .. Methods and class objects for configuring, describing, and specifying process entities, and for allowing system configuration engineers to identify absent equipment, are described below. As mentioned above, such a class object is when an instance is created to indicate a particular piece of equipment. , A part of the equipment can be set to be represented and / or identified as "absent". Therefore, when a control routine for a class object is executed by a controller to control a particular piece of equipment during the operation of a process factory, the controller will see if that part is absent. It can be identified and, in the case of non-existence, it can act to exclude unnecessary and meaningless alarms associated with the non-existent part.
FIG. 1 is a schematic view showing an example of a process factory 10 in a certain embodiment. The process factory 10 in the embodiment of FIG. 1 includes all kinds of various process controllers. In Figure 1 Thus, three of the various process controllers are indicated by reference numbers 12A, 12B and 12C. The process controllers 12A-C in the embodiment of FIG. 1 are various communication paths (s), buses (s) and / or network 15 (s) (eg, Ethernet®-based local area network (LAN)). Etc.) through all sorts of Communicatably connected to various workstations. Three of the workstations are shown in FIG. 1 with reference numbers 14A, 14B and 14C.
In order to control at least a portion of the process plant 10 of the embodiment, in the embodiment of FIG. Controller 12A is implemented, constructed and also according to the popular Fieldbus protocol. Is operated (eg) via any variety of communication lines or buses 18 such as the communication bus 18 and / or a combination thereof, any variety of equipment (s) and / or equipment (s) within the process plant 10 of the embodiment. It is connected so that it can communicate with (s). Not shown in Figure 1, but through For those skilled in the art, the process controllers 12B and 12C of the embodiment are similarly communicably linked to the same, alternative and / or additional equipment and / or equipment of the process plant 10 of the embodiment. That should be obvious at a glance.
The process controllers 12A, 12B and 12C in the embodiment of FIG. 1 can communicate with control elements such as field devices and / or functional blocks within the field devices that are distributed throughout the process plant 10 of the embodiment. Performing and / or performing one or more of the process control routines 19A, 19B and 19C related to each of the process factories 10. Implement the desired control configuration and / or process. In some of the process factories of the examples, the controller 12A-C is a Delta VTM controller sold by Fisher-Rosemount Systems, Inc., one of Emerson Process Management.
In the embodiment of FIG. 1, the process control routines 19A-C include what is referred to herein as a "functional block". As used herein, a functional block is used to implement a process control loop within the process factory 10 of an embodiment (possibly working with other functional blocks via a communication link). ) All or part of the overall control routine. In some embodiments, functional blocks are (a) input functions associated with transmitters, sensors and / or other process parameter measuring devices, and (b) control functions associated with control routines that control PID, fuzzy logic, etc. And or (c) of any device (valve, etc.) to perform any physical function within the process factory 10. It is an object of the object-oriented programming protocol that performs the output function that controls the operation. Of course, hybrid and / or other types of complex functional blocks also exist, such as model predictive control elements (MPCs) and optimizers. Fieldbus Pro Tocol and / or the DeltaV system protocol uses functional blocks and / or control modules 19A-C designed and / or implemented via object-oriented programming protocols. On the other hand, the control modules 19A-C of the embodiment of FIG. 1 can be designed using various control programming mechanisms including sequential functional blocks, ladder logic, etc., functional blocks and / or specific programming techniques and / or It is not limited to designing using a language.
To store the process control routines 19A-C of the embodiment, each of the process controllers 12A-C of the embodiment of FIG. 1 includes any variety of data storage mechanisms 20. Professional In addition to storing the cess control routine 19A-C, the data storage mechanism 20 of the embodiment of FIG. 1 is used to communicate with workstation 14A-C and / or the control element of the process factory 10 of the embodiment. It may store any of the additional and / or alternative control and / or communication applications used. The data storage mechanism 20 of the embodiment is any variety of volatile (eg, random access memory (RAM)) and or non-volatile (eg, FLASH, read-only memory (ROM) and / or hard disk drive) data. Storage element (s), device (s) And / or contains a unit (s).
Each of the process controllers 12A-C of the embodiment of FIG. 1 includes one of the various processors 21 to execute and / or execute the process control routines 19A-C and / or functional blocks. I'm out. The processor 21 of the embodiment of FIG. 1 is particularly accessible to the machine among various instructions. It may be any type of processor, such as a processor core, processor and / or microcontroller, as long as it can execute the instructions.
The workstation 14A-C of the embodiment is a variety of personal computers and Includes one or computer workstation. Work stay of the embodiment of FIG. The 14A-C is, for example, by one or more system configuration engineers. It can be used to design and configure the process control routine 19A-C of the embodiment that is to be performed by the controller 12A-C. In addition to or instead, workstations 14A-C of the embodiments shown in the figure can be used to design and / or set up display routines performed by workstation 14A-C and / or other computers. In addition, the workstation 14A-C of the example, in addition to or as an alternative, Communicates with controller 12A-C and sends process control routine 19A-C to controller 12A-C Can be provided and / or downloaded. In addition, the workstation 14A-C of the embodiment is In addition to, or instead, a display routine may be executed that receives and / or displays information about the process factory 10 of the embodiment, active elements and / or subordinate elements of the process factory 10.
To store applications such as configuration design applications, display and / or viewing applications, and / or to store data such as configuration data related to the settings of the process factory 10 of the examples. Work station of the example of Each of the 14A-Cs includes any variety of storage mechanisms or memories 22. The storage mechanism 22 of the embodiment of FIG. 1 is any variety of volatile (eg, RAM) and / or non-volatile (eg, RAM). For example, it can be a FLASH, ROM, and / or hard disk drive) data storage element (s), device (s) and / or unit (s).
For example, to run an application so that a system configuration engineer can design process control routines and / or other routines, and / or download these process control routines to the controller 12A-C and / or other computer of the example. Each of the workstations 14A-C of the embodiment of FIG. 1 uses one of the various processors 23 to collect and / or display information for the user while the process factory 10 is in operation. Includes. The processor 23 of the embodiment of FIG. 1 is particularly shown in FIG. 15 and also among various instructions. Can be any type of processor, such as a processor core, processor and / or microcontroller, as long as it can execute instructions accessible to the machine performing the method of the embodiment of FIG.
The workstations 14A-C of the embodiment of Figure 1 are the control elements in the process control routine 19A-C. With respect to the controllers 12A-C of the embodiment, through any variety of display screens 24 showing, or in such a manner that these control elements are configured to provide control of the process plant 10. It is possible to provide the user with a graphic display description of a series of process control routines 19A-C. The example system of FIG. 1 includes a configuration database 25 to store configuration data used by process controllers 12A-C and / or workstations 14A-C. In Figure 1 The configuration database 25 of the embodiment is communicably linked to the controller 12A-C and the workstation 14A-C via the Ethernet®-based LAN 15 of the embodiment. Figure 1 The configuration database 25 of the embodiment also functions as a data historian by collecting and / or storing data generated by and / or inside process factory 10 for later use and / or recall. To do.
In the embodiment shown in FIG. 1, the process controller 12A has three reactors having the same configuration (referred to herein as reactor_01, reactor_02 and reactor_03). That is, it is communicably connected to the repeated equipment) via the bus 18 of the embodiment. The process work of the embodiment of FIG. 1 to provide main control for controlling the water flow to each reactor. In the field 10, each of the reactors of the examples (reactor_01, reactor_02 and reactor_03) Includes a shared water distribution valve mechanism 110 connected upstream of the water pipe.
The reactor_01 of the embodiment of FIG. 1 includes all kinds of various reactor tanks or tanks 100, acids and a. Connected to control the fluid inflow piping that provides Lucari and water to each reactor tank 100 It includes three input valve mechanisms (ie, three installations) 101, 102 and 103 and an outlet valve system 104 connected to control the flow of fluid flowing out of the reactor tank 100. (Re The sensor 105 (which may be any desired type of sensor, such as a bell sensor, temperature sensor, pressure sensor, etc.) is located in or near the reactor tank 100 of the embodiment. Shown in Figure 1 In the embodiment, the sensor 105 is a level sensor.
Similarly, the reactor_02 of the embodiment of FIG. 1 includes a reactor tank 200, three input valve mechanisms 201, 202 and And 203, the outlet valve system 204 and the level sensor 205 are included. Similarly, the reactor_03 of the embodiment of FIG. 1 includes a reactor tank 300, three input valve mechanisms 301, 302 and 303, an outlet valve system 304 and a level sensor 305.
For those skilled in the art, the process plant 10 of the embodiment and, or more specifically, the reactor of the embodiment (reactor_01, reactor_02 and / or reactor_03) can be of any variety. It should be easy to understand that it can be used to produce and / or output various products. For example, the input valve mechanisms 101, 201 and 301 of the examples are acids, the input valve mechanisms 102, 202 and 302 of the examples are alkalis, and the input valve mechanisms 103, 203 and 303 of the examples are co-located. By providing water to reactor tanks 100, 200 and 300 in cooperation with the water manifold 110, salts can be produced in reactor reactor_01 and reactor_02 and / or reactor_03. Outlet valve Stems 104, 204 and 304 drive the product out of the flow path directed to the right of each of the reactors (reactor_01, reactor_02 and / or reactor_03) of FIG. And or To discharge waste or other waste materials out of the flow path towards the bottom of Figure 1. , Can work.
In the process factory 10 of the embodiment of FIG. 1, the controller 12A of the embodiment has sensors 105, 205 and 305 and valve mechanisms 101, 102, 104, 110, 201, 202, 204, 301, 302 via bus 18. And 304 communicably connected to the reactors of the Examples (Reactor_01, Reactor_02 and Control the operation of these elements to perform one or more processing operations on reactor_03) To do. Such an operation is generally referred to as a "phase" in the industrial field, for example, filling the reactor tanks 100, 200, 300 of the embodiment, heating materials in the reactor tanks 100, 200, 300, the reactor. It may include drainage inside tanks 100, 200, 300, cleaning of reactor tanks 100, 200, 300, etc.
The valves, sensors, and other equipment 101, 102, 104, 105, 201, 202, 204, 205, 301, 302, 304, and 305 of the examples in Figure 1 are Fieldbus devices, standard 4-20mA devices and also. Can be any variety of equipment, including, but not limited to, HART equipment, and fieldbus protocol, HART protocol, and / or 4-20mA analog. It is possible to communicate with the controller 12A of the embodiment using various communication protocols (s) and / or techniques (s), including, but not limited to, protocols. It In addition to, or in lieu of, other types of equipment may also be controlled and / or coupled by controllers 12A-C in accordance with the principles set forth herein.
Generally, the process plant 10 of the example of FIG. 1 is used to carry out a batch process. sell. In the batch process, for example, Workstation 14A-C of Examples and also One of the controllers 12A of the embodiment produces a particular type of salt or other product. Of one or more of the reactors (reactor_01, reactor_02, reactor_03) and other equipment to perform a series of different steps and / or actions (ie phases) required for this. Execute a batch executive routine, which is a high-level control routine that directs operations. To perform the different phases, the batch executive routine uses what is commonly referred to as a "recipe" that specifies the steps to be performed, the quantity and / or time associated with the steps, and / or the order of the steps. The steps included in one recipe include, for example, the step of filling the reactor tank with appropriate materials and / or ingredients, the step of mixing the materials in the reactor tank, and the step of identifying the materials in the reactor tank at a specific time. It may include heating to the temperature of, emptying the reactor tank, and / or cleaning the reactor tank in preparation for the next batch operation. Each step defines a phase of batch operation and also implements Figure 1. The batch executive routine in the example controller 12A is in each of these phases. Therefore, different control algorithms can be executed (possibly). Of course, the particular ingredients, amount of ingredients, heating temperature, time, etc. may vary from recipe to recipe, and therefore these parameters are also used by and / or products produced. Depending on the recipe, it may vary from batch operation to batch operation. Although the control routine and / or configuration is described herein for batch operation of the reactors of the examples illustrated in FIG. If a person skilled in the art desires to perform any of the desired alternative or additional batch processes, or to carry out continuous process operation, a person skilled in the art. Should be easily understood that control routines can be used to control any of the alternative and / or additional devices.
And, of course, the same phases and / or steps of a batch process, Figure 1 In each of the different reactors (reactor_01, reactor_02, reactor_03) at the same time, It can be performed with a partial shift and at different times. Further, the reactors of the examples (reactor_01, reactor_02, reactor_03) generally include the same number and / or type of equipment. As such, the same standard phase control routine for a particular phase can be used to control each of the different reactors. However, it may be necessary to modify this standard phase control routine to control specific hardware and / or equipment associated with different reactors. For example, the filling control routine 19A of the embodiment is one or more valves of the input valve mechanisms 101, 102 and 103 to carry out the filling phase of reactor_01 (the phase of filling the tank 100 of the embodiment). For a predetermined time (for example, the container tank 100 of the embodiment It will open (until the level meter 105 of the embodiment detects that it is full). Deer While this same control routine 19A simply specifies the input valve valve mechanism 101, 102 and And 103 instead of valve mechanisms 201, 202 and 203, and the specified level meter changed to level meter 205 instead of level meter 105 to fill reactor_02. It can also be used when carrying out
Control routines and / or module class objects as described below with reference to Figure 5. The ct can be constructed and / or utilized to symbolize and / or embrace any equipment within the process plant. The module class object of the embodiment symbolizes the valves 101, 102, 201, 202, 301, 302 of the embodiment. On the other hand, the module class object of another embodiment symbolizes a reactor (reactor_01, reactor_02 and reactor_03). As will be described later, this Objects such as, facilitate the reuse of control routines 19A-C for similarly constructed (eg, repeated) equipment of any magnitude. However, some implementations In an example, similarly repeated equipment may differ in that any particular part, subelement, or device of the equipment may be intentionally absent. As will be described later with reference to FIG. 8-16, such intentionally absent parts, subelements, devices and / or equipment are identified as "absent" by, for example, a system configuration engineer. Therefore, it can be subsequently ignored by the process controller 12A-C of the embodiment during the execution of the process control routine 19A-C. Therefore, the process control routine 19A-C is even a specific inn of equipment. Even if there are missing parts, subelements and / or equipment in the stance, they can be reused and / or utilized in their repeated equipment (transformed equipment).
One of ordinary skill in the art should be able to easily understand that any equipment in the process plant can thus identify missing elements in the equipment in the process plant. In an embodiment, the reactor_02 may be similar to the reactor_01 of the embodiment, except that valve 202 is intentionally absent and therefore ignored by processing routines 19A-C. In another embodiment described below with reference to FIGS. 2 and 3, the valves 101, 102, 103, 201, 202, 203, 301, 302 and 303 of the embodiments are fine-tuning valves and coarse-tuning valves. Includes. However, within the process plant of the example, some instances of valves 101, 102, 201, 202, 301, 302 and / or 110 do not include, for example, fine tuning valves. In some cases. If the fine-tuning valve can be easily identified as "absent" when setting up the process factory, the common control mechanism procedure 19A-C can be used to valve 101, 102, 201, 202, 301, 302 and / or 110 can be controlled (regardless of the presence of a fine-tuning valve in each case).
The process factory 10 of the embodiment is shown in FIG. 1, while the controller 12A-C shown in FIG. , Workstation 14A-C, buses 15 and 18, as well as controls, etc. by various methods It can be split, concatenated, rearranged, excluded, and / or implemented. In addition, the process plant 10 of the embodiment has all sorts of additional and / or alternative controls other than those shown in FIG. It may include rollers, workstations, buses, controllers, and / or the numbers shown in Figure 1. It can include a large number of controllers, workstations, buses, and controllers. For example, the process factory may contain any number of controllers and / or workstations.
In addition, the process plant is in addition to and / or the reactor of the embodiment illustrated in FIG. Alternatively, it may include a wide variety of process entities. Furthermore, process factories can use a wide variety of processing steps to produce a wide variety of products. Therefore, for those skilled in the art, the process factory 10 of the embodiment of FIG. 1 is merely one aspect of the present invention. It should be obvious at a glance. Furthermore, a process factory may include and / or include, for example, one or more geographic locations, such as one or more buildings within and / or near a particular geographic location. In addition, the process factory 10 of the embodiment of FIG. 1 sets the absence of equipment. Although can be employed to illustrate the methods and module class objects of the examples for, those of ordinary skill in the art will appreciate the methods and objects disclosed herein in the absence of equipment in a wide variety of process factories. It should be easy to understand that it can be used to configure.
In general, the reactor uses one or more process steps to combine one or more components to produce an output product. The reactor of the embodiment can be constructed and / or implemented using a wide variety of valves (s), tanks (s) and / or sensors (s). FIG. 2 shows a method as an example in which the reaction apparatus of the example (reactor _01, reactor _02, reactor _03 of FIG. 1) is carried out. Reactor of Example (Reactor_01, Reactor Both _02 and reactor _03) can be represented by FIG. 2, but the apparatus of FIG. 2 is referred to as reactor _01 for the purpose of simplifying the explanation. As described above with reference to FIG. 1, the reaction device of the embodiment of FIG. 2 is generally used. Place_01 is the reaction tank 100 of the example and the fruit for adding acid, alkali and water to the tank 100. To remove raw materials from the example input valve systems 101, 102, 103, 110 and tank 100 The outlet valve system 104 of the embodiment and the level sensor 105 of the embodiment are included. More specifically, each of the input valve mechanisms 101, 102 and 110 of the embodiment of FIG. 2 uses a similar equipment entity (ie, repeated equipment) referred to herein as a "totalizer". The equipment entity is two bars arranged in parallel with each other as shown in FIG. Includes a flow meter installed downstream of the valve and the two valves.
In order to perform coarse adjustment control of the flow rate, the totalizer 101 of the embodiment includes a coarse adjustment valve 101A. I'm sorry. What kind of rough adjustment valve 101A in the embodiment is an on / off type valve? It may be one. In order to perform fine adjustment control of the flow rate, the totalizer 101 of the embodiment is a fine adjustment valve. Contains Lub 101B. The fine-tuning valve 101B of the embodiment can be an on / off type valve. Anything can be used. The maximum achievable flow rate through the fine adjustment valve 101B is less than the achievable flow rate through the coarse adjustment valve 101A. Therefore, by using the coarse adjustment valve 101A and the fine adjustment valve 101B together, it is possible to easily control the flow rate for a wide range of flow rates.
In order to measure the flow rate through the totalizer 101 of the embodiment, the totalizer 101 of the embodiment of FIG. 2 includes a flow rate measuring instrument 101C arranged on the downstream side of the valves 101A and 101B of the embodiment. To. The totalizer 101 of the embodiment of FIG. 2 is associated with it and one or more control modules or routines (eg, eg) used to control the acid input using the measurement results of the flow meter 101C of the embodiment. It is provided with one of the control routines 19A-C) of the embodiment of FIG. The first routine of such a control routine uses the coarse adjustment valve 101A and the fine adjustment valve 101B. , High-speed flow control can be performed through the totalizer 101. On the other hand, of such a control routine The second routine is to control the coarse adjustment valve 101A and the fine adjustment valve 101B separately. Therefore, precise flow rate control can be performed through the totalizer 101.
As is clear from FIG. 2, the alkaline input valve totalizer 102 includes a coarse adjustment valve 102A, a fine adjustment valve 102B, and a flow rate measuring instrument 102C, and the shared water input valve mechanism 110 includes. Includes coarse adjustment valve 110A, fine adjustment valve 110B and flow meter 110C. Smell of the example of FIG. Each of the totalizers 101, 102 and 110 of the embodiment symbolizes repeated equipment. So, even if it is used in different places in the reactor_01 unit of the example, accordingly, It is displayed as an instance of a common totalizer object and can be controlled through a common set of control routines.
It should be obvious to those skilled in the art that there are many variations of the totalizers 101, 102 and 110 of the embodiment of FIG. For example, the modified version shown in Fig. 3. The tareizer 101M can be constructed by not including the fine adjustment valve 101B in the totalizer 101 of the embodiment of FIG. That is, the fine adjustment valve 101B of the embodiment of FIG. 2 is intentionally absent in the totalizer 101M of the embodiment of FIG. In such cases, for example, the process and / or process phase to be performed by Reactor_01 of the Example ( The fine-tuning valve 101B is intentionally absent because it is not necessary to properly perform (s). However, for those skilled in the art, the modified totalizer 101M is similar to the totalizer 101 of the embodiment except for the missing fine adjustment valve 101B. It should be obvious, therefore, that it can be controlled using a control procedure that is substantially similar to the control procedure used to control the totalizer 101 of the embodiment of FIG. Depending on the requirements of the process and / or process phase, the modified version of the totalizer 101M of the embodiment may be used as an alternative to any of the totalizers 101, 102 and / or 110 of the embodiment of FIG. To.
For reference back in FIG. 2, the outlet valve system 104 of the embodiment is another repetitive piece of equipment, including three valves. As shown in FIG. 4, the outlet valve system 104 of the embodiment is shown in FIG. Must be opened no matter what material is discharged from tank 100 of the embodiment of Must be with the main outlet valve 104A and the main outlet valve 104A when delivering the product from tank 100 Product valve 104B that must be opened and tank 100 for substances such as waste and cleaning fluids Includes a drain valve 104C that must be opened with the main outlet valve 104A when draining from and / or draining into the waste system. Of course, one or more control routines will take the tank 100 In connection with the outlet valve system 104, which controls the state of valves 104A, 104B and 104C to close, drain from tank 100, or remove product to empty tank 100. There is.
For reference, returning to FIG. 1, conventionally, the reactors of the examples (reactor_01 and reactor_02 and To generate control routines for the control of different equipment associated with one or reactor_03). The system configuration engineer first, for example, one of the workstations 14A-C in the example. He was creating a large number of essentially standard template control modules that were stored in a library that was stored in one. When creating the template control module, engineers used graphics to connect different functional blocks together to provide control routines for different elements and / or loops executed in connection with the reactor. Once standard template control modules have been created (usually based on valves and / or control loops), these template control modules can be copied and a copy of the template control modules can be manually manipulated within Process Factory 10. It could be tied to a particular piece of equipment (eg, one particular piece of equipment within the reactors Reactor_01, Reactor_02 and Reactor_03). These are directly (more specifically as described in U.S. Pat. No. 6,385,496). The reactor where the combined copy of the control module is downloaded and combined to one or more of the controllers 12A-C of the embodiment after being combined altogether and or using an alias. It was used to perform process control tasks related to. However, the combined control modules created from the template control modules were virtually independent when used in a process control system because they had no association and / or relationship with the underlying template module from which they were created. It existed as a control module (of Standalone) or an object. U.S. Pat. No. 6,385,496 will be referred to here. It will be used more throughout.
Moreover, in these systems, the setting work had to be performed at the control module level. That is, separate control modules had to be created for each of the different equipment and / or loops within the process plant. At the control module level, there are usually many different types of control modules that must be created and combined for each of the process entities in the process factory. As a result, system configuration engineers have spent a great deal of time copying individual control modules and connecting them to individual equipment in the factory. For example, a system configuration engineer must create and copy dozens of control modules for a reactor in a factory and then connect each of these control modules to a particular piece of equipment in the reactor. There wasn't. When the reactor is repeated in the factory, it takes a lot of time and many human errors for the system setup engineer to copy and combine dozens of control modules for each of the repeated equipment. The work of the system configuration engineer became even more patience as the work had to be done.
Traditionally, system configuration engineers could develop unit modules, but these unit modules can simply be run on a single unit. It was like a container for housing and did not include indicators of equipment related to the unit or control mechanisms used for basic control operations of equipment within the unit. Also, although it was possible to create templates for control elements used to control different equipment, higher levels installed in the factory such as equipment and unit elements (eg, totalizer or reactor). There was no control module package that could be used to indicate the repeated elements of. That is, in order to create control routines for different repeating elements within process plant 10, the system configuration engineer copies the control modules at the most basic level of control for each repeated piece of equipment, and then separates and separates them. Alternatively, each of these control modules was required to be completed individually for a particular facility or other entity within the process plant 10. In the case of a large factory with many repetitive equipment, this task was time consuming and involved many configuration errors. Furthermore, repeated equipment-related control module changes had to be manually performed for each of the different control modules in different equipment, which also required patience and a great deal of time. It was a task with many errors. Also, the operator display screen had to be created separately from or separately from the control module. Also, like the control module, the display had to be created, modified and modified individually and connected to the equipment in the process factory.
Performed by at least one of the workstations 14A-C of the example of FIG. 1 to facilitate the creation and / or modification of process settings and / or not to require too much time. The configuration application 50 utilizes a set of one or more module class objects 52 used to configure the process control factory 10. The module class object 52 in the embodiment of FIG. 1 is intentionally absent (plural). This is especially useful when setting up a factory with a large number of repetitive equipment, including repetitive equipment that can include (possible). Different module class objects 52 are, generally speaking, repeated and / or used within the process factory 10 for each different type of physical device and / or equipment that is repeated and used within the process factory 10. It can be created for each type of control work, for each different type of screen display application that is repeated or used in the process factory 10. Module class of the embodiment shown in FIG. Once the object 52 is created, it can be used to configure the elements of the process factory 10 that correspond to the various module class objects 52.
The module class object 52 of the example in Figure 1 is a standard process entity. Represents a version and is therefore not tied to any particular physical process entity. In the embodiments shown herein, module class object 52 can include associated lower level objects and / or instances, four of which are illustrated in FIG. 1 with reference numbers 53, 54, 55 and 56. ing. When a module object is created from a module class object 52, it inherits the same structure and / or characteristics as the original module class object 52. However, each module object is tied to a specific physical entity within Process Factory 10. Thus, while a module object exists and is created separately for each of the different reactors belonging to a particular type that actually exists in factory 10, the module class object 52 is for that type of reactor ( Only one reactor needs to be created (regardless of how many reactors are present in the plant 10).
A module object created from a module class object 52 is dedicated to and associated with a module class object 52. As a result, changes to the associated module class object 52 can be automatically propagated and / or reflected in each of the module objects associated with the module class object 52. Therefore, many module objects (each of the different module objects is different) When created from a particular module class object (eg, module class object 52) (while tied to a process entity), each of the different module objects simply modifies the module class object 52 and then , Can be changed by automatically propagating the change to the relevant module object.
Similarly, once module objects are created from module class object 52, these module objects can be combined with specific equipment within process plant 10 using bulk editing methods. In particular, all module objects of a particular module class object 52 are dedicated and concatenated by the same module class object 52, so all of the module objects at once, for example by using a spreadsheet type application. Can be set. Thus, the detailed setting of a particular relationship between the module object in question and the particular equipment of the factory 10 associated with it becomes easier and / or less time consuming. An example method for setting up a set of module objects using a spreadsheet-type application is described in U.S. Pat. No. 7,043,311, the entire contents of which are described. Or referred to here.
The module class object 52 of the embodiment of FIG. 1 is generally described in the industry. It is what is called an "object" in a project-oriented programming environment and / or language. As a result, these module class objects 52 have the ability to occupy and / or refer to other objects. Generally speaking, a module class object 52 is an indicator and / or definition of an individual element, such as a control routine, equipment, or other element associated with a process entity, as well as how the individual elements interact. A high-level object that can contain definitions and / or indicators of how physical elements are interconnected, or how logical elements work with physical elements. That is, the module class object 52 can be, for example, an object in an object-oriented programming language that provides a basis for controlling and / or displaying a specific one or group of equipment, control elements, displays, etc. in the process factory 10. It can be useful in creating a large number of instances of the element for use in setting up different repetitive equipment within the factory 10.
Basically, each of the module class objects 52 in the example of Figure 1 is a process. The standard definition of an entity is used by the controllers 12A-C of the examples to control that entity and / or to perform display work on that entity. Applicable to the entity used by example workstation 14A-C A set storage container and / or set template, including in the form of a loose control and / or display application and / or routine. The module class object 52 can represent a process entity of any nature, such as a unit, equipment, control element, display application, and so on. When configuring process factory 10, use module class object 52 to configure each process entity's configuration instance for any number of different process entities that meet the definitions provided by module class object 52. A configuration instance (a module object created from module class object 52) can be created with it associated with and / or associated with a different real process entity. These different module objects (among others) include control routines and / or display routines associated with specific process entities located within process factory 10. In this case, these control routines can be downloaded and / or used in controllers 12A-C of FIG. 1 to perform the actual control work on the process entity, or the actual on the entity with respect to the process factory 10 in operation. Down the display routine to workstation 14A-C to perform display work Can be loaded.
Different types of module class objects 52 may include control and / or display routines that reflect process entities with different scopes and are therefore set to operate in and with respect to process entities with different scopes. The wider the scope of a process entity, such as a unit, the more control and / or display routines are generally associated with the module class object in question, so using those module class objects is used in the process factory. It becomes easy to set a large division and / or part of. However, the wider the scope of the process entity associated with one module class object 52, the less likely the process will contain repetitive equipment in that scope, making the module class object 52 useful at a large level. It is less likely to be. Conversely, the narrower the scope of the process entity associated with one module class object 52, the more likely it is that the module class object 52 will be effectively used in different locations in the factory. Reduces the amount of configuration made when using class object 52 for any of a particular instance. In any case, the module class object 52 allows the configuration made for different repetitive facilities with a higher level of abstraction than at the control module level. This simplifies the setup of process factories with repetitive units and / or other equipment when using module class objects 52 (especially module class objects 52 with large scope, such as at the unit level). The required time and / or setting error is reduced.
In some embodiments, when configuring a process control system, the system configuration engineer recites different elements that are repeated within the process factory, such as the totalizers 101, 102, 110, 101M of the embodiments of FIGS. 2 and 3. Only one module class object for G 52 can be created. The system configuration engineer can then create an instance of module class object 52 (ie, a module object) for each of the totalizers physically present in the process factory. Each module object thus created contains a control routine used by the process controller to operate the totalizer and is specifically tied and / or coupled to the equipment contained in a particular totalizer. These control routines are then downloaded to the controller and then used during the operation of Process Factory 10. However, once created, each module object is still tied to its associated module class object 52, thus being controlled and modified by the module class object 52 and providing access to that module object. And / or refuse.
There are many possible types of module class objects 52 that can be created and / or used in process factory 10 to perform configuration work in process factory 10, but the specific 4 described here as an example. Types include unit module class objects, equipment module class objects, control module class objects, and display module class objects. Generally speaking, each different type of module class object 52 is designed and / or intended for a different range of control and / or range of use within the process plant 10. The unit module class object 52 is intended to be used to represent and set up control operations for a wide range of equipment within a process factory. In particular, the unit module class object 52 is, for example, the reactor of the embodiment of FIG. 1 having individual and separate elements that function and / or interact with each other in some known manner. It is intended to be a model and / or used in constructing a set of interrelated equipment (typically repetitive equipment).
The equipment module class object 52 is intended to be used to represent and / or set up control operations in less broadly applicable physical equipment contained within process plant 10. Equipment associated with equipment module class object 52 typically includes valves and flow instruments that make up the subsystem of the unit (eg, Figure 2 and). And one or more physical entities such as the totalizer in the embodiment of Figure 3) The module class object 52 is a command method algorithm (CDA), state driven. Method algorithm (SDA), sequential flowchart (SFC) algorithm, functional block diagram (FBD) algorithm, phase algorithm), etc. are executed in the equipment. Can include one or more directives and / or algorithms. Therefore, the equipment module class object 52 is a plurality of low-level components and / or entities (eg, eg) within the unit to provide a basic set of functions when the equipment in question is used within the unit. Coarse adjustment valve 101A, fine adjustment valve 101B, and / or flow rate of the embodiment of FIG. We aim to set the control of measuring instrument 101C). As we all know, the command method Argo Rhythm (command-based control logic) is used when low-level components must be integrated and coordinated through multiple steps to achieve a function. For example, the second The first valve is opened for a certain period of time and then closed while the valve is opened and then closed. May be necessary. The totalizers of the embodiments of FIGS. 2 and 3 use this type of command-based algorithm to provide a coarse-tuning valve (eg, the coarse-tuning valve 101A of the embodiment) and a fine-tuning valve (eg, the fine-tuning of the embodiment). The valve 101B) is first activated and then operated based on the measured values of the flow measuring instrument (eg, the flow measuring instrument 101C of the embodiment) to set the total flow rate through the totalizer to a desired value. State-driven algorithms (state-driven control logic) can specify the states of individual low-level components that can be manipulated in one step. Such a state driven algorithm can be used to control the outlet valve mechanism 104 of the embodiment of FIG. The state of the individual valves contained within the outlet valve mechanism 104 is the desired state of the outlet valve mechanism 104, such as to close the tank 100, to drain the tank 100, or to deliver the product from the tank 100. Controlled separately (but in one step) based on state Is done. However, the equipment module class can be controlled using any applicable control algorithm.
The control module class object 52 is intended to be used to represent and / or set individual control elements and / or control modules within the process factory 10. The control module class object 52 provides and / or specifies a particular type of control to be performed on a factory entity such as a valve, instrument, one equipment and / or one unit. Generally speaking, a control module class object 52 is a communicably interconnected set of functions that define some control module that is executed in the controller and useful for performing repetitive control tasks within the process factory. Provides certain types of control programming, such as blocks. In most cases, the control module class object 52 may provide a standard control method for operating a single device and / or a set of related devices.
The display module class object 52 is intended to be used to represent and set display tasks that are visible to a user, such as a control operator, while the process factory 10 is in operation. Thus, the display module class object 52 is the programming required to generate a particular type of display for the operator workstation (eg, any of the workstations 14A-C of the embodiment of FIG. 1), and / or the factory 10. Programming that should be performed on one or more workstations (and other equipment (s) in process factory 10) so that the display can obtain appropriate data and / or information from the factory during operation. specify. Examples of the type of the display class module object 52 include a warning display, a setting display field screen, an operation display field screen, and a diagnostic display field screen. of course, The display module class object 52 may provide a display that represents and / or is associated with any range of physical elements and / or entities within the process factory. For example, the display module class object 52 may display information about the entire area, unit, one facility, control element, or any combination of these elements within the process plant 10.
Further, as will be described in more detail below, the module class object 52 is a specific part of all or any of the module objects (eg, toe of the embodiment of FIG. 2). The fine adjustment valve 101B) of the examples of Talizer 101, 102, 110 can be set as "absent". Separated and can be defined and / or set to be negligible during the execution of subsequent relevant control routines. When an instance of module class object 52 for such a totalizer is created and associated with a particular physical totalizer in the process factory (that is, when the module object is created), the equipment is absent (that is, when the module object is created). For example, the fine-tuning valve 101B) is identified and / or marked as absent by the system setup engineer to represent a modified totalizer (eg, the modified totalizer 101M of the embodiment of FIG. 3). become. The module class object 52 of the totalizer of such an embodiment can include checking for the existence of potentially non-existent equipment, and thus may be non-existent, for example. Can contain and / or define one or more control routines (which can be executed accurately without displaying the equipment absence error message, whether or not the equipment is actually present). Such a control procedure is suitable for both the totalizer 101 of the embodiment of FIG. 2 and the modified totalizer 101M of the embodiment of FIG. Therefore, such The submissive totalizer module class object 52 can represent and monopolize any of the various variants of the totalizer.
Therefore, in the embodiment shown herein, the particular physically modified totalizer 101M can be an instance of the totalizer module class object 52, and thus the module class object 52 (eg, updated control procedure 19A). ) In addition to The updated updates can be automatically applied to the improved Totalizer 101M. If the totalizer module class object 52 cannot intentionally identify the absent part of the equipment, another module class object 52 is required for the modified totalizer 101M. Such another module class object 52 must be updated and / or maintained separately, even if the two module class objects 52 represent similar devices. However, since the improved totalizer 101M of the embodiment can be created as an instance of the totalizer module class object 52, the totalizer 101 of the embodiment and the modified totalizer 101M have a common totalizer module class. It is configurable and / or controllable through object 52, thus utilizing a set of shared and / or common control routines.
An example of the non-existent equipment is described in connection with the totalizer module class object 52, but if it is a person skilled in the art, the equipment is intentionally absent and / or It should be obvious that a module class object 52 capable of identifying parts can be defined and / or created for any equipment and / or unit in a process factory. For example, it is possible to define a reactor module class object 52 that can make a particular totalizer "absent".
A process factory can be represented by a hierarchy of interconnected module class objects that represent an instance of a module object derived from a particular module class object. Such a hierarchical diagram can represent an embodiment of a larger process entity with a set of process entities containing two or more smaller process entities. Figure 5 is different as used by the configuration application 50 in Figure 1. Shows the hierarchical interconnection between module class objects 52 of type. Figure 5 also shows The interrelationship between the Joule class object 52 and the module object developed from the module class object 52 is shown. To explain from the top of Fig. 5, The Jules class object 52 is classified into unit module class type 400, equipment module class type 402, control module class type 404, and display module class type 406 according to the module class type. Of course, the four types presented herein are merely for the purpose of illustrating embodiments of the present invention, and module class objects 52 of other types and / or classes may be defined, provided, and used. For example, a variety of additional and / or alternative module class object types can be used to represent a process factory. The individual module class objects of the examples (which can be high-level objects, for example, in object-oriented programming languages) are the different types of module classes in Figure 5. Below the 400, 402, 404 and 406, double contours are shown for greater clarity.
The reactor unit class module object 410 of the embodiment is in the process factory. Represents a particular type and / or setting of a reactor (eg, a reactor in process plant 10 of the embodiment of FIG. 1). Similarly, the packing device unit module class object 412 of the embodiment The dryer unit class module object 414 of the embodiment represents a particular type and / or setting of a packing unit within process plant 10. Represents a particular type and / or configuration of a dryer unit. Of course, there can be one or more additional and / or alternative reactor module class objects that represent reactors with different physical structures. Note that FIG. 5 does not attempt to illustrate all different types of units in a process factory that can be represented and / or modeled by the unit module class object 400. For those skilled in the art, different types of factories can be modeled and / or represented by the unit module class object 400. It should be obvious that there are different types of units.
Similarly, there may be various equipment module class objects 402 used to represent, model, or configure a variety of equipment within the process plant 10. The examples shown in Figure 5 are totalizer equipment module class object 416 and outlet valve equipment. Contains module class object 418. Similarly, there can be a wide variety of control module class objects 404s, as shown in FIG. For example, on / off valve control module class object 422, level detector control module class object 424 and the flow meter control module class object 426. Further, the display module class object 406 of the embodiment shown in FIG. 5 includes a warning display module class object 432, a display column screen module class object 434, and a diagnostic display module class object 436. Of course, other desired uni Devices, equipment, control and display module class objects may be created and / or used within the configuration application 50 of the Examples in accordance with the principles set forth herein.
As shown in FIG. 5, each module class object 52 is associated with it and Or it may include and / or refer to sub-objects that are exclusively occupied by it. Such a sub-object can also be a module class object 52 and / or Figure 5. It can be a module object created as an instance of the module class object to which it belongs, as shown in. For example, as shown in FIG. Reactor unit module class object 410 is Reactor_01, Reactor_02 And three reactor modules associated with it, which are named Reactor_03. It has an object. In this case, these reactor module objects correspond to (ie, are combined) with each of the reactors of the embodiment (reactor_01, reactor_02 and reactor_03 in FIG. 1). Figure 5 also shows the totalizer equipment module clutter of the example. Sobject 416 is shown with and / or exclusive use of five different module objects named Water 1, Acid 1, Acid 2, Alkali 1 and Alkali 2. Similarly, the on / off valve control module class object 422 of the embodiment of FIG. 5 includes coarse adjustment valve 1, coarse adjustment valve 2, coarse adjustment valve 3, fine adjustment valve 1, fine adjustment valve 2 and Contains a module object with the name Tweak Valve 3. the same As in the other units, equipment, control and display module class objects in Figure 5. Each may have one or more module objects associated with it. However, to keep the figure concise and easy to understand, these module objects are shown in Figure 5. Not done.
In the embodiment illustrated in FIG. 5, reactor_01, reactor_02 and reactor_03 unit module objects, acid 1, acid 2, alkali 1, alkali 2 and water 1 totalizer ( Equipment) Module object, coarse adjustment valve 1, coarse adjustment valve 2, coarse adjustment valve 3, fine adjustment Adjusting valve 1, fine tuning valve 2 and fine tuning valve 3 control module object and / or so Each of the other units, equipment, control and display module objects is an individual module object associated with the actual unit, equipment, control module and / or display application within Process Factory 10. For example, since multiple physical acid totalizers are used in Factory 10, there are multiple acid totalizer module objects created in the configuration routine. In this case, there is a separate acid totalizer module object for each of the individual acid totalizers present in the factory 10. However, each of the separate totalizer module objects is associated with and / or dedicated to the same totalizer module class object 416. Of course, the example in Figure 5 shows only a limited number of module class objects and related module objects, and other types of module class objects for those of ordinary skill. It should be easy to understand that can be provided and that any desired number of module objects can be created from each of the different module class objects.
Each module class object in FIG. 5 (and thus each module object in FIG. 5) defines and / or constitutes a module definition and a physical and logical process element, and, if desired, a process factory 10. As part of an object, it may include a way in which the process elements physically and logically communicate with each other to perform some work within. For example, the unit module class object 400 is generally a uni. It will include all indicators of the physical and logical control elements within and / or constituting the process entity defined as a device. The unit module class object 400 is also designed to operate as a unit with a specific structure of individual parts. It is possible to define how these parts are physically connected together. Similarly, the equipment module class object 402 is generally defined as a single equipment and / or directive. Contains control routines and / or control modules used to control the entities that are used. Since these facilities and / or commands operate as one facility when placed in the factory 10, the parts interact physically or logically using the control routine and / or control module in question. Define how to do it. Similarly, each control module class object 404 is a form of control work performed in the factory, generally in the form of some kind of control algorithm. So, it will be defined. Also, each display module class object 406 is (its The specified type (if applicable) of the display screen settings and / or information to be displayed, as well as the data to be collected and / or the data manipulation to be performed on the collected data (especially among others). Can be defined for a unit, equipment, factory area, or other physical or logical entity within the factory 10.
Module class object 52, as part of the module class definition, other The module class object 52 may be instructed and / or defined for inclusion and use therein. In this case, the module object created from the module class object 52 as described above is the other module object created from the other module class object 52 according to the relationships defined at that module class level. Will be incorporated, referenced, and / or included. Not necessarily required, but for the unit module class object 400, Other unit module class object 400, equipment module class object The unit 402, the control module class object 404 and / or the display module class object 406 may be incorporated, while the equipment module class object 402 includes other equipment module class objects 402 and the control module class object. You may include an eject 404 and / or a display module class object 406. Control module class object 404 includes other control module class objects 404s and display module class objects 406 may be included and / or referenced. However, if desired, the interrelationships of other module class objects can be used as well. The built-in relationship of the examples is large at the bottom of Fig. 5. Indicated by a clear arrow and any display module class object 406 Also included in the control, equipment and unit module class objects 404, 402, 400 What can be rare or referenced therein and that any control module class object 404 is included in any equipment and unit module class objects 402, 400. It indicates that it can be rare or can be referenced by it, and that the equipment module class object 402 can be included in or referenced by any unit module class object 400. Of course, the module class object may include other module class objects of the same type. For example, the unit module class object 400 is another uni as part of its definition. You may include the module class object 400. Similarly, equipment mod The class object 402 may contain another equipment module class object 402, the control module class object 404 may contain another control module class object 404, and the display module class object 406 may contain another display. Module class Can include object 406. Of course, if desired, the module class object The eject 52 may use or incorporate another module class object 52 multiple times. For example, modeled by Reactor Unit Module Class Object 410 The reactor unit module class object 410 is a totalizer equipment module class object because the reactor contains multiple instances of the totalizer. Act 416 can be incorporated and / or used multiple times.
And, of course, if the first module class object 52 incorporates and / or uses the second module class object 52, then the first module class object 52 Any module object created from or as an instance of project 52 is created from or as an instance of a second module class object 52. Any module object can be incorporated and / or used. Therefore, the totalizer equipment module class object 416 is the outlet valve equipment module class. When incorporating and / or including the Sobject 418, the totalizer equipment module / class Created from Sobject 416 (for example, called Totalizer_1 as its own name) The totalizer module object is a module created from the outlet valve equipment module class object 418 (for example, called the outlet valve_2 as its own name). It will include a project. Thus, the relationship of module class objects 52 as defined at the level of the module class objects is reflected in the module objects developed and / or created from these module class objects 52. Interconnection and / or reference between this module class object 52 (and thus between module objects) increases object variability during configuration work. And / or the transferability can be improved. It also creates a set of very basic underlying module class objects 52, such as control and equipment module class objects 404 and 402, and then the very basic underlying module class object 404. And 402 make it easier to create more complex module class objects 52, such as unit module class object 400. Become. Of course, the module class object 52 can reference and / or use other module class objects, but in addition to and / or instead, valves, sensors, etc. that do not have the associated module class object 52. You can define and / or use simple objects and / or process entities. These simple objects can be fully defined in terms of the control routines used in the module class object 52 itself.
As mentioned above, a module class object generally represents and / or defines the entities that make up and / or make up the module class object. So, of course, when a module object is instantiated from a module class object, the module class object defines the relationships between the actual process equipment that forms the instantiated process entity. Figure 6 shows the unit mod Shown is an example reactor unit module class object 410 that can be used to describe and / or define an entity associated with and within a tool class object. The reactor unit module class object 410 of the embodiment of FIG. 6 includes an index of tank 500 which is a simple object and / or element in the process factory 10 where the module class object does not exist. The tank 500 of the embodiment is illustrated by the dotted line in FIG. 6 because there is no control and / or low level work required to control and / or perform the input / output work with respect to the tank 500. As a result, the tank 500 of the embodiment was simply associated with the reactor unit module class object 410 of FIG. It is only included to show the interconnection between other objects.
The reactor unit module class object 410 of the embodiment of FIG. 6 is also (FIG. 5). Three separate references to the totalizer equipment module class object 416. ) Contains three totalizers 501, 502 and 510, named acid, alkali and water, respectively. The water totalizer module class object 510 of the embodiment of FIG. 6 is a part of the reactor unit module class object 410 (the part separated by the dotted line and is a shared module class object. Therefore, the reactor unit module class object 410 is the other unit module class. Shows that it shares control over this object with the object).
The outlet object 504 of the embodiment of FIG. 6 is the outlet valve equipment module class object of FIG. This is a reference to ACT 418. Similarly, the level sensor 505 of the embodiment is the level detector of FIG. A reference to the control module class object 424, the water supply (WATER_IN) valve 503 of the embodiment can be a simple valve element (hence, by being included within the reactor unit module class object 410 completely. Defined) and / or settings A reference to a valve object, which can be a reference to the valve control module class object 52 defined elsewhere in the strategy. Physical interconnections between different entities and / or parts of the reactor unit module class object 410 are also available. It is shown in Figure 6 to define the interconnection between these different elements. As mentioned above, the reaction Equipment Unit Module Class Object 410 and / or any other type of model A Jules class object can contain simple elements that are fully defined within a module class object (which can contain any of the standard control routines associated with it) and / or a module class object. Module defined outside Can include references to tool class objects.
The reactor unit module class object 410 of the embodiment of FIG. 6 is also shown in FIG. Display column screen module class object 434 and warning display module class It contains two display module class objects 406 of an embodiment called a reactor display field screen 520 and a reactor warning display screen 522, each referring to object 432. These display objects 520 and 522 relate to any of the equipment and / or components of the reactor unit as defined in the reactor unit module class object 410. Define standard display tasks for displaying status (eg, tank fill level) and warnings.
Similarly, the reactor unit module class object 410 of the embodiment of FIG. 6 is a phase class object such as that shown in box 524 as a "filling", "mixing", "draining" and "washing" phase class object. Includes other elements of Units each defined by Reactor Unit Module Class Object 410 Define a standard control routine that works with. Reactor unit module class object 410 may or may not be associated with a phase class object I. The phase class object 524 can be defined elsewhere and / or desired. Imported into reactor unit module class object 410 in any manner You can also do it. Phase class object 524 is a unit filling, unit A command that can operate on the unit defined by the reactor unit module class object 410 to perform different functions such as heating, emptying the unit, cleaning the unit, etc. One or routine.
The reactor unit module class object 410 of the embodiment of FIG. 6 is a memory and / or a memory that stores a reference to a module class object created from the reactor unit module class object 410 by the configuration application 50 (FIG. 1). Contains section 526. Section 526 is a module object whose essence is exclusively occupied by and / or created from the reactor unit module class object 410. Is a list of. Of course, a list of dedicated module objects and / or other indicators can be stored on the workstation and / or by the configuration application 50 in any desired manner and is not necessarily physically contained in the reactor unit module class object 410. It does not have to be included in. In any case, in the embodiment of FIG. 6, the reactor unit module class object 410 is a module object created from the reactor unit module class object 410 of the embodiment of FIG. 6, respectively. It occupies the reactors such as reactor_01, reactor_1, and reactor_02.
The reactor unit module class object 410 of the embodiment of FIG. 6 is also set up by the reactor unit module class object 410 during and / or set up. Each of the following includes a set of methods 530 that can be performed. Method 530 of the example of FIG. 6 is a reaction Module object dedicated by the device unit module class object 410 For each of the 526s, it may include a change management method and / or application that automatically propagates the changes made to the reactor unit module class object 410. Alternatively, the reactor unit module class object 410 and / or it. So security for any of the dedicated unit module objects 526 A security management method that controls access and / or allows a user and / or system configuration engineer to specify modification parameters and / or security parameters for a module class object and / or any module object created from it. , And so on. Of course, the different method 530 is a reactor uni Perform other steps for or related to the module class object 410 sell.
If desired, the reactor unit module class object 410 of the embodiment of FIG. 6 is a unit module with changes made to the reactor unit module class object 410. How to propagate to Joule object 526, as well as security access is a unit You may control how it is set within module object 526. Provide this feature One way is to propagate the changes to the unit module object 526. And or points to how security is handled in unit module object 526 One or more in the reactor unit module class object 410 to determine Flags and / or parameters can be set. In particular, changes made to the reactor unit module class object 410 are automatically made to one or more module clutters. One or more change propagation parameters to specify whether to propagate to 526 Can be set. These change propagation parameters are the unit module object 526 Can be stored in, or throughout the reactor unit module class object 410 Reactor unit module class object 410 (or for each subelement) You can specify whether the changes made should be reflected in the associated unit module object. For example, the reactor unit module class object 410 of FIG. 6 contains a global change parameter 534 (indicated as "C" in the figure). The global change parameter 534 can be set in each unit module object created from the reactor unit module class object 410. Then, the change to the reactor unit module class object 410 is automatically reflected in the unit module object. Enable or disable the function. Similarly, each of blocks 501, 505, 510, 520 and 522, etc. Subelements and / or blocks can include change parameter 536. The change parameter 536 is made to the block in the reactor unit module class object 410. Specifies whether the changes should be reflected in the unit module object (only for the block). Of course, different blocks of the unit module object can be set separately, for example for the reactor unit module class object 410. Changes to the "acid" block 501 are propagated to the corresponding "acid" block of a particular module object 526, but the "al" of the reactor unit module class object 410. The change to "Kali" block 502 is the "alkali" of the particular unit module object. It may not be propagated to the block. In addition, different unit module objects created from one unit module class object will have change parameters that are set differently from each other, to the "alkali" block 502 within the reactor unit module class object 410. The changes are propagated to the corresponding "alkaline" block of the first unit module object 526, but the second unit module Prevent it from propagating to the corresponding "alkaline" block of Joule object 526 May be good. Of course, change management method for reactor unit module class object 410 Is relevant when changes are made to the reactor unit module class object 410 You can access and use the change parameters of unit module object 526 to make or not make changes within the object. sell.
Similarly, the reactor unit module class object 410 of the embodiment of FIG. 6 is secure and / or accessible in each of the unit module objects 526. It may include one or more security parameters that specify the mode to be controlled. The reactor unit module class object 410 is a reactor unit module class. Desired for the entire reactor unit module object created from object 410 Global security parameter 538 that can provide all levels of security (Represented by "S" in the figure) and / or Reactor Unit Module Class of For each subelement of JECT 410 (eg, for each of blocks 501 505, 510, 520, 522) On the other hand, etc.) It may contain different security parameters 540 that specify each security level of the block on a block-by-block basis. Global security parameter 538 can be a locking parameter that locks the unit module class object for all users except those with a pre-authenticated security access level. Of course, security parameters 538 and 540 specify any of a number of different levels of security (eg, inaccessible, limited access, accessible only to users of a particular type or with a particular identity, etc.). You may. Also, the security level may be set differently for different unit module objects and different blocks created from the same unit module class object. If desired, it may include providing encryption of one or more methods or algorithms associated with the unit module class object as part of the security measures.
Not surprisingly, changes to the reactor unit module class object 410 and Alternatively, the security parameters 534 and 538 may be set to default values. And each unit module created from the reactor unit module class object 410 The corresponding changes and security parameters for object 526 were made at the time of creation. The default value of can be adopted. However, the specified values of the modified and / or security parameters 534, 538 are set in the unit module object 526 (by a user with appropriate security access) after these unit module objects are created. ) Can be changed individually. The changes and security parameters 534, 538, etc. are described herein with respect to the reactor unit module class object, but similar changes and security parameters can be found for other types of unit module class objects, as well as any desired. It can be provided in a type of equipment module / class object, control module / class object, display module / class object, and so on.
If desired, the reactor unit module class object 410 of the embodiment of FIG. 6 is stored and / or it for the reactor unit module class object 410. Can include references, URLs or other references to documents related to (including documents related to the unit or any subelement of the unit associated with the reactor unit module class object 410). These references are indicated by reference numeral 549 in FIG.
The reactor unit module class object 410 of the embodiment of FIG. 6 is a reactor unit created from the reactor unit module class object 410 of the embodiment. Includes a global "ignore" property 542 (shown as "I" in Figure 6) that indicates whether an instance of the entire module object is identified as "intentionally absent" and therefore should be ignored. I'm out. Similarly, each of the reactor unit module class objects 410 (for each of blocks 501, 505, 510, 520, 522, etc.) The subelement contains an "ignore" property 544 that indicates whether the instance created from the subelement can be set as "absent". Any person skilled in the art with ordinary skills The reactor unit module class object 410 of the embodiment of FIG. 6, in addition to or as an alternative, defines a simple object and / or process entity such as a valve, sensor, etc. without the associated module class object 52. It should be easy to understand that it can be used. Such a simple object can also have an associated "ignore" property 544.
In the method disclosed herein, the "ignore" properties 542 and 544 of the embodiment of FIG. 6 are named PERMIT_INSTANCES_2B_IGNORED (allow instance ignorance) and have a TRUE (true) or FALSE (false) value (eg). , Logical "1" or logical "0"), Boolean property Can be implemented as a lag. The "ignore" properties 542 and 544 of the module class object from which a particular instance of a module object, sub-object, and / or simple object was created are such that the system configuration engineer is physically absent from the particular instance. Used to determine if it is possible and / or permitted to specify and / or set. For example, if the "ignore" properties 542 and 544 of a module class object for an instance of a particular module object, sub-object and / or simple object have a TRUE (true) value, then the corresponding module object, sub-object and / or Simple objects can be determined and set as "absent" by a system configuration engineer. Unsurprisingly, the reaction of the example of FIG. The "ignore" properties 542 and 544 of the example of the device unit module class object 410 may have default values (eg, FALSE).
In general, the "ignore" property 544 of a particular sub-object 501, 502, 503, 504, 505, 510 takes the value of the associated module class object. For example, the reactor unit module class object 410 of the embodiment of FIG. 6 is the totalizer module of. If defined and / or created to include the eject "acid" 501, the "ignore" property 544 of the "acid" 501 is set based on its "ignore" property 542 of the totalizer module class object 416. .. However, any variety of rules and / or methods can be used when setting the initial "ignore" property 544 (eg, the "ignore" property 542 of a unit module class object that references a module class object, etc. Set them to something new). Any variety of different interfaces (s) can also be used to set the individual "ignore" properties 542 and 544. As an example, a totalizer equipment module class object (eg, the module of the embodiment in Figure 7). -The interface for setting the "ignore" property 544 for the fine-tuning valve of class object 416) will be described below with reference to FIG.
Instantiation when an instance of a module object, sub-object, and / or simple object is specified and / or set by a system configuration engineer as nonexistent (if allowed by the "ignore" property of the associated module class object). The parameters of the module object, sub-object, and / or simple object (not shown) are set to indicate that the module object, sub-object, and / or simple object does not exist. The parameter of the example is a Boolean flag that is named "_IGNORE" and takes a value of TRUE (true) or FALSE (false) (eg, logical "1" or logical "0"). Is. In the embodiments illustrated in the discussion here, the parameters have a default value of FALSE and thus a module. Indicates that there is an object, a sub-object, and / or a simple object. Alternatively, if you leave the parameter undefined as the default value, the FALSE value It is assumed to have. An example interface for designating and / or setting an instance of the module object, sub-object, and / or simple object will be described below in relation to FIG.
Figure 7 shows the d. Related to and / or present in the equipment module class object. An example totalizer equipment module class object 416 that can be used to describe and / or define an entity is shown. The totalizer module class object 416 of the embodiment of FIG. 7 represents a module class object capable of representing any or all of the totalizers 101, 102, 110, 101M of the examples of FIGS. 2 and 3. For those skilled in the art, it is obvious that the structure and / or mode of the expression shown in the embodiment of FIG. 7 is similar to the content and / or structure of the embodiment of FIG. Should be. Therefore, as a matter of course, a person skilled in the art who has ordinary technology should be able to easily understand the embodiment shown in FIG. 7 by comparing with the explanation of FIG. 6 presented above. is there.
More specifically, the totalizer equipment module class object 416 of the embodiment of FIG. 7 is a control module class object named coarse adjustment valve 550 and fine adjustment valve 552, and a flow rate measuring instrument control module class object. Named measuring instrument 554 Includes a previous control module class object and an illustration of the interconnection between these elements. The coarse adjustment valve 550 and the fine adjustment valve 552 of the embodiment of FIG. 7 are on / off type. Represents a control module class object. The flow meter 554 in the embodiment of FIG. 7 represents a flow meter control module class object.
Furthermore, the totalizer equipment module class object 416 of the embodiment of FIG. 7 is a display module including the totalizer warning display module class object 560. Equipment module class object 416 to the Le class object as well as the embodiment Contains a reference to an example to one or more algorithms 564 that may be implemented in. .. The TOTALIZE_FAST command of the example is shown in the list of algorithm 564 of the example of FIG. And examples include the TOTALIZE_ACCURATE directive, but other directives and / or algos. Rhythms may be included and / or used. The directive algorithm 564 of the embodiment of FIG. 7 associated with and / or included in the equipment module class object 564 of the embodiment is described, for example, by coma. It can take any desired form, such as an input algorithm (CDA), a state driven algorithm (SDA), a sequential flowchart (SFC) algorithm, a functional block diagram (FBD) algorithm, or a phase algorithm. However, generally speaking, all of Algorithm 564 of the Examples are of a particular type, such as CDA or SDA. Of course, the algorithm 564 can be written in any desired language and / or programming environment (eg, C or C ++ programming environment, any sequential function chart programming environment, functional block programming environment, etc.).
The totalizer equipment module class object 416 of the example in Figure 7 was also created from the equipment module class object 416 of the example (named Acid 1 and Acid 2, Alkali 1, Alkali 2, Water_HDR1). Exclusive equipment module object 566 (and required Includes any variety of lists and / or memories that store indicators of the channel to it, if desired. The totalizer equipment module class object 416 is similarly an equipment module. It contains a set of methods 570, including change management methods that can be used with global change parameter 572 and / or object-based change parameter 574 to control the propagation of changes to object 566. The totalizer equipment module class object 416 also has object-based security parameters 582 and global security. It also includes parameter 580. The modification and security parameters 572, 574, 580 and 582 are substantially the embodiment of the reactor unit module class object 410 of FIG. It works as described above in connection with the changes and security parameters of, and can be applied to any of the elements of equipment module class object 416, including Directive 564. To keep the explanation here concise, readers interested in further details are mentioned above in relation to Figure 6. See the description of the changes and / or security parameters that have been made.
Similar to the embodiment of FIG. 6, the totalizer equipment module class object 416 of the embodiment of FIG. 7 has an instance of the totalizer module object created from the totalizer equipment module class object 416 of the embodiment "intentionally absent". Indicates whether it is ignored because it can be identified as "" (indicated as "I" in Figure 7). Contains the Ignore property 584. Similarly (for each of blocks 550 552 and 560, etc.) ) Each subelement of the unit module class object 416 is created from the subelements Ignore property 586 that indicates whether the instance can be set as "absent" including. If you are a person skilled in the art with ordinary technology, the equipment module clasp of the embodiment shown in FIG. Project 416, in addition to or as a substitute for, the associated module class It should be easy to understand that simple objects such as valves and sensors that do not have object 52 and / or process entities can be defined and / used. Such a simple object can also have an associated "ignore" property 586. "ignore The use, setting and / or application of properties 584 and 586 is described above in connection with Figure 6. If you are interested in more details about the "ignore" property 584,586, as it is so similar to what is revealed, see the description above in connection with Figure 6. Example toe An example interface for setting the "ignore" property 586 of the fine tuning valve 552 of the Talyzer equipment module class object 416 will be described below in connection with FIG.
Instantance of equipment module objects, sub-objects, and / or simple objects, if permitted by the "ignore" property of the associated equipment module class object. when the scan is designated and or set by the system configuration engineer as absent, The parameters (not shown) of the instantiated equipment module object, sub-object and / or simple object are set to indicate that the equipment module object, sub-object and / or simple object does not exist. The parameter of the example is a Boolean flag that is named "_IGNORE" and takes a value of TRUE (true) or FALSE (false) (eg, logical "1" or logical "0"). Is. In the embodiments illustrated in this description, the parameters have a default value of FALSE and have a default value of FALSE. Therefore, it indicates that there are module objects, sub-objects, and / or simple objects. Alternatively, leave the _IGNORE parameter undefined as the default value If so, it is assumed to have a FALSE value. The module object, sub An example interface for designating and / or setting an instance of an object and / or a simple object will be described below in connection with FIG.
If desired, the equipment module class object 416 of the embodiment of FIG. 7 is stored for and / or related to the equipment module class object (of the equipment or equipment associated with the equipment module class object 416). Related to all subelements Can include references to (including documents) 599, URLs or other references. Similarly, any algorithm of the equipment module class object 416 of the embodiment (such as any of the algorithms 564 of the embodiment) can be encrypted, or these algorithms 564 are encrypted and also. May have its associated security parameters to decrypt. If desired, such encryption and / or decryption can be performed by one of the methods 570.
To return to FIG. 1 for reference, to configure the process factory 10 of the embodiment, system configuration d. Engineers create units, equipment, control and display module class objects in the library associated with the configuration application 50 as needed. In some embodiments, the system configuration engineer creates an entity with a lower scope, such as a control and / or display module class, and then uses and / or references an entity with a lower scope. Develop a module class object for an entity with a high scope, such as a class object. The system configuration engineer then selects and / or specifies the module class object as needed to create the actual module object that corresponds to the selected module class object for each process entity in the factory. become able to. When configuring repeated equipment, the system configuration engineer would create a module object for each instance of the repeated equipment from the same module class object. Therefore, the system setting engineer is the reactor unit mod, which represents the reactor of the embodiment of FIG. You can create a tool class object. Creating other module class objects that may be referenced by reactor unit module class objects (If such other module class objects do not already exist in the library). After that, the system setting engineer starts from the reactor unit module class object to the reactors _01, reactor_02 and the reactors of the embodiment of FIG. And create a reactor unit module object for each of reactor_03 Allows you to set up the process.
After creating one or more module objects from a module class object, the system configuration engineer can also connect the created module objects (including sub-objects and / or referenced objects) to specific equipment in process factory 10. Good. Since the unit module object is associated with a single unit module class object, aliases, parameters and other variables for different unit module objects are specified together using a bulk processing application, for example a spreadsheet application. it can. Of course, by connecting the module object to a specific piece of equipment, the system configuration engineer can control within controller 12A-C. You will actually specify the control variables and channel names used by the routine and / or control module. This work is to perform control work while the process factory 10 is in operation, or by a display routine on workstation 14A-C, for example, while the process factory 10 is in operation. Made to display the variables used. Once the join operation is complete, the system configuration engineer then brings down the joined control routine to controller 12A-C of the example. Load and download the combined display routine to workstation 14A-C of the example To.
Creating module class objects, instantiating module objects, sub-objects and / or referenced objects can be done in any variety of different applications (s), user interfaces (s), screens (s), methods (s). And / or using a process (s). Modular class objects, configuration systems and / or methods of the examples are described in US Pat. No. 7,043,311. And its contents are incorporated by reference here throughout.
8, FIG. 9, FIG. 10, FIG. 11, FIG. 12 and FIG. 13 show, for example, in the process of a system configuration engineer creating, configuring, and using a module class object to configure the process factory 10 of an embodiment. Can be created by the configuration application 50 of the example in Figure 1. , Screen display, user interface, dialog box and / or window screen. The setting screens, user interfaces, dialog boxes and / or window screens of the examples are shown in FIG. 8-13, but for those skilled in the art, various setting display fields (s), A screen (s), an interface (s), a dialog box (s), and / or a window screen (s) are all presented and / or presented to set and / or depict a module class object and / or a module object. It should be obvious that it can be used. Therefore, as a matter of course, the examples of FIG. 8-13 are merely examples for explaining the embodiments of the present invention.
In general, FIGS. 8, 11 and so that those skilled in the art can easily understand. In the illustrated embodiment of FIG. 12, a user interface that includes an explorer display field on the left side of the screen or provides an organizational hierarchy tree structure that represents a portion of the settings of the example of process factory 10. included. Similarly, most of the examples in FIGS. 8, 11 and 12. In, one or more information display fields that provide more detailed information about one of the elements selected in the search display field on the left side are included on the right side of the screen. The information that can be displayed to the user and that can be changed by the user in the information display field is set for each of the different module class objects and / or its subordinate elements, and the embodiment of FIG. 6 and / or FIG. Control and or security parameters 534, 536, 538, 540, 572, 574, 580 and or 5 82 and / or determined by the "ignore" properties 542, 544, 584 and / or 586 of the Examples Or it can be controlled. Thus, a particular element in the search display field is an "ignore" property set in the module class object (s) and propagated to the module object depicted in the search display field, and / or security and control parameters. Can be displayed and / or exposed to the user for the purpose of changing and / or displaying based on. Of course, as mentioned above, certain information can always be hidden, or it can be displayed and / or changed only by the user who entered the password and / or other PIN, but it can be displayed at all times. It can be non-modifiable, always visible and modifiable, or a combination of these or other security change parameters and / or "ignore" properties. Furthermore, if desired, the visibleness and / or changeability of the element is shown in the search display field using highlighting, shading, coloring, or other techniques to show which element provides further details. The user may be informed if it can and / or can be changed.
In some embodiments, the graphical user interface (GUI) is modal. It can be used and / or useful in representing, visualizing, and / or constructing control structures of process factories that use tool class objects and / or module objects. Such an interface provides, in some embodiments, a search display field and / or a window screen that allows a system setup engineer to build a depiction of the process factory and / or set the process factory. The fruit of Figure 8 to provide a display field for search Screen 800 of the example includes portion 802 depicted on the left side of display 800. The search portion 802 of the embodiment of FIG. 8 includes an upper portion 804 depicting a list of module classes and a lower portion 806 depicting a list of module objects. In the embodiment of FIG. 8, the module class and the module object are hierarchically depicted in the search display field 802. Example For example, the totalizer equipment module class 808 of the embodiment (for example, corresponding to the totalizer equipment module class object 416 of the embodiment of FIG. 7) is of the equipment module class. It belongs to library 810. As shown, the totalizer module class 808 of the embodiment includes indicators and / or references to a number of sub-elements, including coarse-tuning valves, fine-tuning valves, monitor screens, and the like. The totalizer class object 808 of the example is the image of the example. The elements of totalizer class object 808 are screen 800 because they are selected on face 800. It is described in more detail in the upper right 812 of.
Similarly, the totalizer module objects 814, 816 and 818 of the examples are implemented. Example Reactor Module Object 820 (eg, Corresponds to Reactor_01 in the Example of Figure 1) Is referenced by. The acid 1 totalizer module object 814 of the embodiment of FIG. 8 (for example, corresponding to the totalizer 101 of the embodiment of FIG. 2) is selected on screen 800 of the embodiment. So the element of the "Acid 1" totalizer module object 814 is to the right of screen 800. Depicted in more detail below 822.
Many GUIs are consistent in setting one or more parameters and / or options And / or to provide an easy-to-understand method, a dialog box is adopted. For example, dialog boxes can be used to select and / or set properties and / or parameters for module class objects and / or instances of module classes. Figure 9 shows one or more properties of a module class object (for example, a tweak bar). Shows an example dialog box for setting (property for lube control module class object). Such a fine-tuning valve control module class object can be used as part of a "totalizer" equipment module class object (eg, module class object 416 of the embodiment of FIG. 5 and / or FIG. 7). Normal technology For those skilled in the art, one or more similar and / or different dialog boxes are used to set the properties and / or parameters of the module class object. It should be obvious what can be done. In addition, the Settings dialog box contains any number and / or type of checkboxes (s), picklists (s), and text boxes (s) for setting any variety of properties and / or parameters of the module class object. Multiple) etc. can be included. In general, the types and / or numbers of properties and / or parameters that can be selected and / or set, and / or the types and / or numbers of dialog boxes (s) and dialog box elements (s) are specific to a particular module class object. It is a thing.
To allow a system configuration engineer to identify and / or configure an instance of a particular module object created from a fine-tuning valve control module class object as "absent," the example dialog box in Figure 9 is provided. Contains check box 905. Checkbox 905 in the embodiment of FIG. 9 is selected and / or deselected to set the corresponding "ignore" property of the fine-tuning valve control module class object. When checkbox 905 is selected (for example, a check mark is displayed Then, the property of PERMIT_INSTANCES_2B_IGNORED (allow instance to be ignored) is set to TRUE (true). Otherwise, the PERMIT_INSTANCES_2B_IGNORED property is set to FALSE and remains undefined. .. Undefined property of PERMIT_INSTANCES_2B_IGNORED (Allow instance to be ignored) If left, it is assumed to be FALSE as a result.
FIG. 10 shows an example dialog box for setting one or more parameters of a module object (eg, a fine tuning valve for a particular totalizer module object). It should be obvious to those skilled in the art that one or more similar and / or different dialog boxes can be used to set the properties and / or parameters of a module object. Also, the Settings dialog box contains any number and / or type of checkboxes (s), picklists (s), text boxes (s) for setting any of the various properties and / or parameters of the module object. Yes) and so on. In general, the type and / or number of dialog box elements, and / or the type and / number of properties and / or parameters that can be selected and / or set, are specific to a particular module object. In addition to or instead, the absence of a particular object module is a bulk editing method, tool used to connect and / or associate the object module with the actual equipment of the process factory. And or can be set via an application (eg, a spreadsheet).
A check box 1005 is included in the example dialog box of FIG. 10 to allow a system configuration engineer to identify and / or set whether a particular object module is absent. Checkbox 1005 in the example in Figure 10 is for setting the corresponding _IGNORE parameter of the fine tuning valve control module object. Is selected and / or deselected. If checkbox 1005 is selected (for example, if a check mark is displayed), the _IGNORE parameter is set to TRUE. To be determined. Otherwise, the _IGNORE parameter is set to FALSE and remains undefined. If the _IGNORE parameter remains undefined, it Is assumed to be FALSE as a result.
PERMIT_INSTANCES_2B_ IGNORED of the relevant module class object The check box 1005 of the example in FIG. 10 is valid only when the property of (Allow ignoring chest of drawers) is set to TRUE (true). If the property of PERMIT_INSTANCES_2B_IGNORED (allow instance ignorance) of the associated module class object is FALSE (false) and / or undefined, checkbox 1005 is disabled (for example, "gray". Shadowed on "), the system configuration engineer has the corresponding _IGNORE (ignore) parameter Checkbox 1005 cannot be selected and / or deselected to set.
In FIG. 11, the setting screen of the embodiment of FIG. 8 shows the system setting engine in which the fine adjustment valve module object 1105 of the acid 1 totalizer module object 814 is absent. Indicates a state marked, set and / or identified by near. For example, a system configuration engineer can activate the fine-tuning valve of a "totalizer" module object that is set or should be identified as "absent" in the dialog box of the embodiment in Figure 9. Can be used. If the system config engineer is allowed to identify one of the specific fine-tuning valves of the totalizer module object (eg, object 1105 in the embodiment of FIG. 11) as "absent", the system config engineer then decides. For example, check box 1005 in the embodiment of FIG. 10 can be used to identify the fine-tuning valve module object 1105 as "absent."
As shown in FIG. 11, the fine-tuning valve module object 1105 is represented as "absent" because the fine-tuning valve module object 1105 has been identified, set, and marked as "absent." In the illustrated embodiment, the graphic 1110 to the left of the name of the module object 1105 has been modified (eg, covered with small spots) and "<ignored>" (ignored) 1115 appears in front of the name. Also in part 822 of screen 800 that provides additional data, details and / or information relating to the "acid 1" module object 814. Similarly, the fine-tuning valve is identified as uncoupled as shown in FIG.
FIG. 12 is an alternative display field and also for the acid 1 module object 814 of the embodiment of FIG. Is the screen 1200 of the embodiment showing the depiction. The screen 1200 of the embodiment of FIG. 12 can be used, for example, to set any variety of parameters and / or control modes for the "acid 1" module object 814 of the embodiment. Since the tweak valve module object 1105 has been identified and / or set as absent by the control engineer, the tweak valve is displayed as absent, as shown as "<ignored>" 1205 in FIG. resulting in, The control engineer cannot connect the fine-tuning valve to a particular physical valve or set the parameters of the fine-tuning valve.
In some embodiments, the control routine is written and / or represented using a text-based scripting language and / or programming language. In such embodiments, tools that assist in creating and / or modifying control routines may be used by control and / or system configuration engineers. FIG. 13 shows, for example, the totalizer equipment module of the embodiment of FIG. Details of the control routine of class object 416 and / or the steps of the control routine Shown is another embodiment screen display 1300 (eg, pop-up window 1300) that can be used to display and / or create. In the embodiments shown here, the _IGNORE parameter of the fine-tuning valve module object 1305 determines the flow rate and / or execution of the control routine. Tested and / or used to control. When the control routine of the embodiment illustrated in FIG. 13 is executed and / or performed for a particular totalizer equipment module object (eg, totalizer 101 of the embodiment of FIG. 2), the referenced_IGNORE parameter is Be controlled For fine-tuning valves for certain totalizer equipment module objects that are in _IGNORE (ignore) It is resolved to a parameter. Thus, of course, the control routines of the embodiment of FIG. 13 can be used for totalizer module objects with or without their associated fine-tuning valves. Thus, the control routine for totalizer equipment module class object 416 is a module object with non-existent equipment (ie, totaler). Can be written and / or constructed to contain (a variant of the Isa module object).
In the embodiment of FIG. 13, the parameter FINE_VALVE / SETPOINT 1310 does not have a fine tuning valve (eg, FINE_VALVE / _IGNORE). Set only if the value of is not TRUE). So you can test the _IGNORE parameter so that the code for the non-existent equipment is not executed, as shown in Figure 13. To. As a result, when the routine of the example of FIG. 13 is actually executed and / or executed, the error messages and / or flags that may be caused by the execution and / or execution of the code for the nonexistent equipment are suppressed. It can be generated or not presented to the system operator and / or user.
For those skilled in the art, the _IGNORE parameter is of any variety. It should be obvious that it can be used in various code statements, combinations, or with any variety of additional conditional statements. For example, the _IGNORE parameter of the coarse adjustment valve You can also check the data.
If you are a skilled person, in all kinds of similar aspects, a system configuration engineer will set the configuration elements for units, equipment, control elements and display elements in the process control environment according to the principles described here. Allows equipment to be set as non-existent, specific equipment as non-existent, and / or other unit module class objects, equipment module class objects, control module class objects, and display modules to create. It should be easy to see that class objects can be used. Also, of course, module class objects, which can contain a great deal of detail in nature, are of great advantage to system configuration engineers when creating configurations. This is because engineers do not have to create individual control elements separately or copy individual control elements separately from control templates, and on the contrary, the ever-increasing bulk used in process factory 10 settings. This is because module class objects with ever-increasing levels or wider scope can be used to create state structures. In addition, the ability to deliberately set a particular module object and / or a particular portion of a module object as "absent" makes the module class object in an increasing number, scope, and / or type of repetitive facility. Being reusable, system configuration engineers can gain additional flexibility and / or capability.
The system configuration engineer also modifies one or more of the unit module class objects and propagates the changes to each of the module objects created from and associated with the unit module class object globally. At any level, you can make changes to the configuration elements of different process entities. This feature makes it easier to make changes in the settings once the settings have already been created, and / or does not take too much time to create them. Also, the system configuration engineer can specify the level of access to different elements or constituents of a module object in the configuration system by setting security parameters within the module class object. As mentioned above, the system configuration engineer can specify security on a module-by-module basis at all levels, including unit module level, equipment module level, control module level and display module level. In this way, some elements of the unit module object may be visible and some may not be visible. Furthermore, benefiting from the flexibility of intentionally configuring and / or identifying non-existent equipment, system configuration engineers can apply configuration changes to an unprecedented range. For example, a system configuration engineer can define a module class object that incorporates multiple variants of absent equipment. As a result, changes to the module class object are intentionally absent. The changes can be automatically propagated and / or applied to all module objects created from module class objects, including module objects with equipment set as.
Of course, once the system configuration is complete and the module objects are joined to the individual process entities within Process Factory 10, the control and display modules or elements associated with these modules are the appropriate controller 12A- in Figure 1. Provided to C and workstations 14A-C, it can be run during the operation of process factory 10. Control and / or display mode Joules or elements include means to download them to the controller, use download scripts, read them by the controller, read them using the download script, write them to the controller's memory, and so on. It can be provided via any variety of means (but not limited to).
In some example process factories, scripts are used to facilitate downloading multiple control routines and / or configuration data for multiple process entities to one or more controllers. For example, a download script can define and / or organize which routines or data should be downloaded, which routines or data should be downloaded, which routines or data should be provided and / or retrieved. FIG. 14 shows the control routine and / or setting data and / or parameters as shown in FIG. Download desk used to download to any of the example controllers 12A-C A section (eg, line) of an example of lypto is shown. Download scripts can be formed using any number of clauses for any number and / or type of object and / or module object. In the download script of the embodiment, each line of the script is configured as shown in FIG. 14, with each line corresponding to a particular object and / or module object.
To identify the module object as indicated by the download section, the download script section of the embodiment of FIG. 14 includes an identifier field 1405 that identifies a particular type of module object. In the embodiment of FIG. 14, identifier field 1405 identifies a fine tuning valve.
In this example, the referenced fine-tuning valve is intentionally set to be absent, so the download script section of the example in FIG. 14 includes ignore field 1410. The neglected field 1410 of the embodiment of FIG. 14 is labeled "IGN". Ludo. The module object referenced by identifier field 1405 is absent and the IGN field 1410 of the embodiment has a value of "T" corresponding to TRUE. If the referenced module object is not absent, the IGN field 1410 in the example should have a value of "F" that corresponds to FALSE. Alternatively, omit the IGN field 1410 and install the equipment The receiving controller 12A-C may assume that there should be.
The controller that receives the control routine and / or the setting data and / or the parameter via the example download script of FIG. 14 (for example, one of the controllers 12A-C of the embodiment) Uses the value of IGN field 1410 to determine which equipment is set as non-existent it can. So, of course, the controller can ignore the state of the absent equipment, thereby causing error messages due to uncoupled, missing and / or unconfigured equipment. And / or it is designed not to issue a warning.
Although FIG. 14 shows a section of the download script of the example, for those skilled in the art, there is a section of the download script and / or the download script. It should be obvious that it can be constructed using a wide variety of alternative and / or additional fields. Furthermore, the fields shown in FIG. 14 can be mixed, split, split and rearranged by any variety of methods.
Any of the methods and / or processing steps of the above embodiment (eg, for setting parameters for module objects, for creating download scripts, and / or for processing download scripts) is a processor, controller. Can be implemented using programs, applications and / or utilities run by computers, workstations, etc. 15, 16 and 17 show examples of methods used and / or performed to process download scripts, in order of description, to set parameters for module objects, to create download scripts, and to process download scripts. It is a flowchart. The methods of the embodiments of FIGS. 15, 16 and 17 can be performed using machine accessible instructions performed by a processor, controller and / or other suitable processing device. For example, the machine accessible instructions used to implement the method of the embodiments of FIGS. 15, 16 and 17 are processors (eg, the processor of the embodiment of FIG. 1). It can be embodied in a coding command stored in a tangible medium such as flash memory, ROM and / or RAM associated with processor 1805), which will be described later in connection with CPU 23 and / or FIG. Alternatively, some or all of the methods of the embodiments of FIGS. 15, 16 and 17 may be any variety of various application specific integrated circuits (ASICs), programmable logic devices (PLDs) (s). ), Field programmable logic unit (FPLD) (s), discrete (single function) logic, hardware, firmware, etc. can be used. Also, some or all of the methods of the embodiments of FIGS. 15, 16 and 17 may be manual operation or any combination of any of the aforementioned techniques (eg, firmware, software, discrete logic and / or hardware). It can be implemented as any combination of wear). Further, the method of the embodiment of FIGS. 15, 16 and 17 is described with reference to the flowcharts of FIGS. 15, 16 and 17, but those skilled in the art will appreciate the module object. It should be easy to see that many other methods can be employed to set the parameters of, create a download script, or process the download script. For example, the execution order of blocks can be changed, and / or some of the blocks described can be changed, deleted, subdivided, or combined. Further, those skilled in the art will appreciate that the methods of the embodiments of FIGS. 15, 16 and 17 are continuous, for example, by another processing thread, processor, device, discrete logic, circuit, and the like. It should be easy to understand that it can be performed and / or can be performed in parallel.
The method of the embodiment of FIG. 15 can be performed and / or performed to set the parameters of the module object. For example, when the system configuration engineer selects a module object to be configured, the method of the embodiment of FIG. 15 begins. If the system configuration engineer is allowed to identify that the module instance should be ignored (eg, via checkbox 905 in the example in Figure 9) (block 1505), the configuration window, display screen, One or more additional and / or alternative elements such as dialog boxes (eg, checkbox 1005 in the embodiment of FIG. 10) are enabled (block 1510). Such elements can be used by a system configuration engineer to identify or configure the absence of equipment. In block 1505, the module class object PERMIT_INSTANCES_2B_IGNORED (allowing the instance to be ignored) from which the module object was created You can use the ropati to determine, for example, whether the setting to ignore module instances is allowed or enabled. Control then shifts to block 1515.
Returning to block 1505, the system configuration engineer ignores the module instance If it cannot be set to (block 1505), control is transferred to block 1515 without enabling additional or alternative elements such as settings windows, display screens, dialog boxes, etc.
In block 1515, a configuration window, display screen, dialog box, etc. are displayed that allow the system configuration engineer to set the parameters of the module object (block 1515). If the system configuration engineer can configure the module instance to be ignored, additional elements such as configuration windows, display screens, and dialog boxes will be enabled as configured in block 1510. Once the system configuration engineer has set up the module object and / or created a variant, for example, press the "OK" button on the presented configuration window, display screen, dialog box, etc. (block 1520), for example. The state of the checkbox for setting the equipment as absent is determined (block 1525). If the equipment is set as non-existent (for example, if checkbox 1005 in the example of Figure 10 is selected) (block 1525), for example, set the _IGNORE parameter of the module object to TRUE. Equipment is not good due to Marked as existing (block 1530). Control then exits from the method of the embodiment of FIG. However, if the equipment is not set as absent (for example, if checkbox 1005 in the example of Figure 10 is not selected) (block 1525), set the _IGNORE parameter of the module object to FALSE. Marks the equipment as existing (block 1535). Control then exits from the method of the embodiment of FIG. Alternatively, in block 1535, leave the _IGNORE parameter undefined You can also leave it as.
The method of FIG. 16 can be used to create a download script for a process controller (eg, one of the controllers 12A-C of the embodiment of FIG. 1). A basic download script section is created for the relevant module object associated with a particular process controller (block 1605). If the module object in question is set as non-existent (for example, its _IGNORE parameter is set to TRUE) (If) (block 1610), a field that identifies the module object as non-existent (eg, IGN field 1410 in the example in Figure 14) is added to the basic download script section. Is added (block 1615). If there are module objects left to process (block 1620), control returns to block 1605 to process the next module object. If there are no remaining module objects (block 1620), control exits the method of the embodiment in Figure 16.
If you return to block 1610 and the module object in question is not set as non-existent (for example, if its _IGNORE parameter is set to FALSE) (block 1610), control should handle it. Move to block 1620 without adding any more fields to the download script section to determine if any module objects remain.
The method of FIG. 17 can be used to process the download script on a process controller (eg, one of the controllers 12A-C of the embodiment of FIG. 1). Download script sections are extracted and / or read from the download script and parsed to retrieve the various fields of the section (block 1705). If the relevant module object corresponding to the clause is set as non-existent (for example, if the IGN field 1410 in the embodiment of Figure 14 is set to TRUE) (block 1710), the controller will be the module of The control routine error corresponding to the eject and / or the setting is set to be ignored (block 1715). If there are still clauses to process (block 1720), control returns to block 1705 to process the next clause. Control if there are no clauses to process (block 1720) Departs from the method of the embodiment of FIG. Returning to block 1710, if the module object in question is not set as non-existent (for example, if the IGN field 1410 in the example of Figure 14 is set to FALSE) (block 1710), the download to process Control shifts to block 1720 to determine if there is a section in the script.
FIG. 18 shows the controller 12A-C of the embodiment of FIG. 1 or the workstation 14A-C of the embodiment. FIG. 5 is a schematic representation of an example processor platform 1800 that can be used and / or programmed to apply. For example, processor platform 1800 can be implemented with one or more general purpose processors, cores, microcontrollers, and the like.
The processor platform 1800 of the embodiment of FIG. 18 includes at least one general purpose programmable processor 1805. Processor 1805 executes coded directives 1810 and / or 1812 that reside in processor 1805's main memory (eg, in RAM 1815 and / or ROM 1820). Processor 1805 can be any type of processor, such as a processor core, a processor and / or a microcontroller. Processor 1805 (among other things) follows the methods of the examples in FIGS. 15, 16 and 17 in the order described, to set parameters for module objects, to create download scripts, and to download. Can be executed for scripting. Processor 1805 communicates with main memory (including ROM 1820 and RAM 1815) via bus 1825. RAM 1815 can be implemented by DRAM, SDRAM and / or any other type of RAM device. ROM The 1820 can be implemented with flash memory and / or other desired type of memory device. Access to memory 1815 and 1820 can be controlled by a memory controller (not shown). RAM 1815 implements, for example, control data storage mechanisms 20, 22, configuration database 25, control routines 19A-C, and / or module class objects 52, 53, 54, 55 and / 56. It can be used to store and / or implement the example library.
Processor platform 1800 also includes an interface circuit 1830. The interface circuit 1830 can be implemented by any type of interface standard such as external memory interface, serial port, general purpose input / output. One or more input devices 1835 and one or more output devices 1840 are connected to interface circuit 1830. The input device 1835 and / or the output device 1840 is, for example, the workstation 14A-C of the embodiment. , The controller 12A-C of the embodiment, and / or all kinds of various control devices are communicably connected. Can be used to
The methods, devices and products of a particular embodiment are described herein, but the scope of this patent is not limited thereto. These examples are merely described as examples for explaining the embodiments of the present invention, and are not limited in any way. Not only that, this patent covers all methods, equipment and products that are fairly included in the appended claims, either literally or on the basis of the doctrine of equivalents.
<figref num="1">It is the schematic of the process factory of an Example.</figref><figref num="2">It is a figure which shows the example of the method for carrying out the reaction apparatus of the Example of FIG.</figref><figref num="3">It is a figure which shows an example of the improved totalizer which can be used in any of the reactors of the examples of FIG. 1 and FIG.</figref><figref num="4">It is the schematic of the outlet valve system of the Example of FIG.</figref><figref num="5">It is a block diagram which shows an example of the logical interrelationship between a module class object and related module objects.</figref><figref num="6">FIG. 2 is a diagram showing an example of a reactor unit module class object that can be used to perform the setting work for the reactor of the embodiment.</figref><figref num="7">It is a figure which shows an example of the equipment module class object for a totalizer which can be used to perform the setting work for the totalizer of the embodiment of FIG. 2 and FIG.</figref><figref num="8">It is a figure which shows an example of the 1st setting screen which can be used to display the setting of a process factory.</figref><figref num="9">It is a figure which shows an example of the first dialog box which can be used to make it possible to identify that a facility is in an "absent state".</figref><figref num="10">It is a figure which shows an example of the 2nd dialog box which can be used to identify the equipment in an absent state.</figref><figref num="11">As an example, it is a figure which shows an example of the 1st setting screen of FIG. 8 after the "fine adjustment valve" object is identified as "absence state".</figref><figref num="12">It is a figure which shows the example of the 2nd setting screen which shows the parameter example of the example of the totalizer module object which includes the fine adjustment valve in the absence state.</figref><figref num="13">It is a figure which shows an example of the 3rd setting screen which can be used to set and display the control routine related to the equipment in an absent state.</figref><figref num="14">It is a figure which shows the example of a part of an example of a controller download script.</figref><figref num="15">It is a flowchart which shows the example of the method which can be executed to set the parameter of a module object.</figref><figref num="16">FIG. 5 is a flowchart showing an example of a method that can be executed to create an example download script of FIG.</figref><figref num="17">It is a flowchart which shows the example of the method which can be executed to process the download script example of FIG.</figref><figref num="18">FIG. 5 is a schematic diagram illustrating an example of a processor platform that can be used and / or programmed to perform the example methods of FIGS. 15, 16 and 17.</figref>
19 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19
Every citation, both ways
| Document | Relation | Office | Category | Cited during | Relevant claims |
|---|---|---|---|---|---|
| JP2019032839A | Cited by | Japan | – | Search report | – |
| DE112017005160T5 | Cited by | Germany | – | Applicant | – |
| JP2019032839A | Cited by | Japan | – | Search report | – |
| JP2004061654A | Cites | Japan | A | Search report | – |
| JP2004061654A | Cites | Japan | A | Search report | – |
| JP2004133900A | Cites | Japan | Y | Search report | 1-11 |
| JP2004133900A | Cites | Japan | Y | Search report | 1-11 |
| JP2004318830A | Cites | Japan | Y | Search report | 2-8,10-11 |
| JP2004318830A | Cites | Japan | Y | Search report | 2-8,10-11 |
| JP2004536391A | Cites | Japan | Y | Search report | 1-11 |
| JP2004536391A | Cites | Japan | Y | Search report | 1-11 |
20 members in 7 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 11537138 | United States of America | – | |
| 53713806 | United States of America | A | |
| 53713806 | United States of America | A | |
| 11537138 | – | – | – |
| US20060537138 | – | – | – |
Members20
| Document | Office | Kind | |
|---|---|---|---|
| GB0719124D0 | United Kingdom | D0 | |
| CN101158870A | China | A | |
| GB2443061A | United Kingdom | A | |
| DE102007046642A1 | Germany | A1 | |
| JP2008135007A | Japan | A | |
| US2008188960A1 | United States of America | A1 | |
| HK1115923A | Hong Kong, China | A | |
| HK1115923A1 | Hong Kong, China | A1 | |
| US7848829B2 | United States of America | B2 | |
| GB201118335D0 | United Kingdom | D0 | |
| GB2484016A | United Kingdom | A | |
| GB2443061B | United Kingdom | B | |
| GB2484016B | United Kingdom | B | |
| PH12011000192A1 | Philippines | A1 | |
| CN101158870B | China | B | |
| JP5586825B2 | Japan | B2 | |
| JP2014225281A | Japan | A | |
| JP6013405B2 | Japan | B2 | |
| JP2016201130AThis record | Japan | A | |
| JP6343307B2 | Japan | B2 |
15 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 2016201130
- Publication, DOCDB
- 2016201130
- Publication, EPODOC
- JP2016201130
- Application
- 145511
- Application, DOCDB
- 2016145511
- Application, EPODOC
- JP20160145511
Titles2
- Japanese
- ダウンロードスクリプトを作成する方法、データを格納する製造品、機械アクセス可能指示を格納する製造品及びダウンロードスクリプトを処理する方法
- English
- How to create download scripts, products that store data, products that store machine accessibility instructions, and how to process download scripts
Classification
- CPC, 6
- G05B19/41865
- G05B15/00
- G05B2219/32137
- Y02P90/02
- G05B19/00
- G05B19/41845
- IPC, 2
- G05B19 418
- G05B23 02