BARRY JEROME BENTLEY
Pilots at Grv Rd, Marsh, PA

6341291, Jan 22, 2002

Apr 22, 1999

09/296738

Keith A. Bentley - Elverson PA
Samuel W. Wilson - Wilmington DE
Barry J. Bentley - Elverson PA
Raymond B. Bentley - Elverson PA
John B. Gooding - Spring City PA

Bentley Systems, Inc. - Exton PA

G06F 1730

707203, 703 4

Conventional file-based engineering design data for an engineering model are represented by a plurality of components. Each component has a unique identifier, a set of fields, each field having a data type and a data value, and a program which interprets and modifies the fields. The plurality of components are stored in a repository of a server. The repository also stores a history of any changes made to the components. A plurality of client computers are bidirectionally connected to the server. Each client computer may obtain the current version of the components and may send locally edited versions of the components back to the server to replace the current versions in the repository. At the client computer, the user interacts with the components using conventional file-based software. Before locally edited versions of the components are committed to the server to replace the current versions, a synchronization and merging process occurs whereby the latest version of the components are downloaded to the client computer and are compared to the locally edited version of the components to detect resolvable (compatible) and unresolvable (incompatible) conflicts therebetween. The commit process is performed only if no unresolvable conflicts exist between the two versions of the components.

8106903, Jan 31, 2012

May 4, 2006

11/417987

William Steinbock - Crestwood KY, US
Barry Bentley - Elverson PA, US
Gino Cortesi - Honey Brook PA, US

Bentley Systems, Incorporated - Exton PA

G06F 17/00

345418

An element template system allowing users to define a named set of element symbology properties to be associated with a graphic element is provided. When the element template is active, it sets the active drawing settings to match the template and associates newly created elements with the active template. Once elements are associated with an element template, the template can be used for checking for compliance with a graphics standards for that project. The element templates technology can be used to update elements and existing files to match a specific set of template properties. The element templates defining a particular graphic element are stored in the same design file as that graphic element so that when the graphic element design file is transported the element templates are also transported with the file, thereby eliminating a need to be coupled to a database or other form of external data.

7194489, Mar 20, 2007

Oct 22, 2001

09/982753

Keith Bentley - Elverson PA, US
Barry Bentley - Elverson PA, US
Raymond Bentley - Elverson PA, US
John Gooding - Spring City PA, US
Sam Wilson - Downingtown PA, US

Bentley Systems Incorporated - Exton PA

G06F 17/30

707203, 707 1, 707200, 717170

Conventional file-based engineering design data for an engineering model are represented by a plurality of components. The plurality of components are kept in stores, which reside on servers. Each store contains the components that correspond to the elements of one design file. The stores also maintain a history of changes made to the components. A plurality of client computers are bidirectionally connected to the servers. Each client computer may obtain the current version of the components and may send locally edited versions of the components back to the servers to replace the current versions in the stores. At the client computer, the user interacts with the components using conventional file-based software. Before the locally edited versions of the components are committed to the servers to replace the current versions, a synchronization and merging process occurs whereby the latest version of the components are downloaded to the client computer and are compared to the locally edited version of the components to detect resolvable (compatible) and unresolvable (incompatible) conflicts. The commit process is performed only if no unresolvable conflicts exist between the two versions of the components.