SFDC 1009
`
`SFDC 1009SFDC 1009
`
`
`
`

`
`Chart
`
`Claim Chart of U.S. Patent No. 6,243,717, to Gordon et al. (filed Sept. 18, 1998) (“Gordon”)
`
`as prior art to
`
`Asserted Claims of U.S. Patent No. 7,356,482 (“the ‘482 Patent”)
`
`
`
`‘482 Patent
`Claim 1
`A system for providing a
`dynamically generated
`application having one or
`more functions and one or
`more user interface
`elements; comprising:
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`
`To the extent that this preamble is construed to be limiting,
`GORDON discloses a system for providing a dynamically generated
`application having one or more functions and one or more user
`interface element. See, e.g.:
`
`GORDON at Cols. 6-7: “With reference still to FIG. 2, in one
`embodiment, system 200 further includes workbench 240 and
`client applications 250, 260 and 270. Workbench 240 provides a
`collection of user applications to facilitate object and model
`definitions, user and security management, and also database
`configurations. Client applications 250, 260 and 270 are
`application extensions that enhance and/or customize the
`functionalities of system 200 and may include third party off-the-
`shelf applications, user developed custom applications, additional
`user interfaces, and the like. It is appreciated that client
`applications 250, 260 and 270 are entirely optional to system 200.
`Users of system 200 can implement more or fewer client
`applications based on their own needs within the scope of the
`present invention.
`
`Still referring to FIG. 2, in one embodiment, application server
`210 communicates with data server 220 via named pipes. In
`particular, using named pipes provides for scalability of system
`200 by delivering data from multiple applications running on one
`or more application servers. On the other hand, application server
`210 communicates with workbench 240 and client applications
`250, 260 and 270 through published interface 230. Published
`interface 230 is a consistent, public interface which serves as a
`bridge between application server 210 and client applications 250,
`260 and 270 and also workbench 240. In one embodiment,
`published interface 230 is built upon Microsoft’s COM/DCOM
`and ActiveX technologies. As such, users of system 200 can easily
`customize and/or extend the functionalities of the system by
`adding application extensions, such as client applications 250, 260
`and 270, which are compliant with these industry standard
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`technologies. Through published interface 230, users can even
`integrate system 200 with other computer implemented systems,
`such as enterprise resource planning (ERP) systems, to provide a
`seamless enterprise computing environment.”
`
`GORDON at Col. 9: “FIG. 6 is a diagram illustrating an exemplary
`graphical user interface (GUI) for user designation of a choice of
`version of the RME referenced in a GME in accordance with one
`embodiment of the present invention. In one embodiment of the
`present invention, two data fields 61 and 62 are presented to the
`user within a GUI 60 on display device 118 when a GME is being
`created or modified. Field 61 allows the user to specify a
`particular version number of the referenced RME. Field 62 is an
`indicator representing the choice “revision of record” of the RME
`and can be either selected or unselected. In one embodiment,
`version number field 61 is disabled (thus preventing the user from
`entering a value therein) when “revision of record” indicator field
`62 is selected. In another embodiment, the value entered into
`version number field 61 is ignored when “revision of record”
`indicator field 62 is selected. In both embodiments, version
`number field 61 is effective for stipulating a particular version of
`the RME only when “revision of record” field 62 remains
`unselected. In a second embodiment, fields 61 and 62 can be
`merged into a single field having multiple functionalities.”
`
`GORDON at Col. 13: “FIGS. 11A and 11B are exemplary
`graphical user interfaces with labels in different languages as a
`result of different login user IDs. In FIG. 11A, user NickA 601 has
`specified English as his language of choice. Thus, the text in title
`bar 605, the dialog box label 610, the various field labels 615, 620,
`625, 630, 635 and 640 and also the text on the push buttons 645
`and 650 are all displayed in English. In contrast, in FIG. 11B, user
`StephanH 651 has specified French as his language of choice. So,
`the text in title bar 655, the dialog box label 660, the various field
`labels 665, 670, 675, 680, 685 and 690 and also the text on the
`push buttons 695 and 700 are all displayed in French. FIGS. 11A
`and 11B serve to visually depict the user dependent views seen by
`users with different terminology set and/or language settings.
`Importantly, the change in view is transparent to the user because
`the proper view is automatically determined by the system when
`the user logs in based on the user’s associated language and
`terminology set, and the customizable terms will be displayed
`accordingly. As such, no user action is necessary to ensure that the
`designated language or terminology set is used.”
`
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`[a] a server computer;
`
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`Figures 6, 9, 11A, and 11B and the accompanying text.
`
`GORDON at claims 10 and 16.
`
`To the extent this reference does not teach this claim element, this
`reference in combination with the knowledge of one of ordinary
`skill in the art and the disclosures of each of the prior art
`references provided in Salesforce’s Petitions related to the ‘482
`and ‘111 Patents renders this claim element obvious.
`GORDON discloses a server computer. See, e.g.:
`
`GORDON at Cols. 6-7: “FIG. 2 is a high level block diagram of an
`exemplary configuration of the computer implemented system in
`accordance with the present invention. One embodiment of the
`computer implemented system of the present invention is a
`Manufacturing Execution System (MES) for integrating and
`managing information from the factory floor and for providing
`production management capabilities and factory automation
`solutions. Specifically, in one embodiment, system 200 includes
`application server 210, which encapsulates business rules and
`application logic as data objects and access methods, thus enabling
`flexible and powerful modeling of manufacturing data and
`processes. In a preferred embodiment, the novel method of
`revision management of the present invention is implemented
`within data server 220 and exposed through application server
`210. In one embodiment, multiple application servers can be
`maintained within system 200 to provide for additional scalability
`of the system.
`
`System 200 also includes data server 220 and database 250. Data
`server 220 is responsible for managing the translation of data from
`objects (e.g., modeling entities such as configurable data objects
`(CDOs)) in application server 210 to the proper database format
`for storage in database 250, and vice versa. Thus, data is retrieved
`from and stored to database 250, with the appropriate translation,
`via data server 220. In one embodiment, database 250 is a
`relational database management system (RDBMS), thereby
`allowing the use of industry standard tools for data access.
`Examples of commercially available RDBMS’s include SQL
`Server V6.5+ for Windows NT by Microsoft Corporation and
`Oracle 7.3+ for Windows NT or UNIX by Oracle Corporation. In
`one embodiment, communications between data server 220 and
`database 250 are supported via open database connectivity
`(ODBC), thus enabling full database independence.
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`
`
`With reference still to FIG. 2, in one embodiment, system 200
`further includes workbench 240 and client applications 250, 260
`and 270. Workbench 240 provides a collection of user applications
`to facilitate object and model definitions, user and security
`management, and also database configurations. Client applications
`250, 260 and 270 are application extensions that enhance and/or
`customize the functionalities of system 200 and may include third
`party off-the-shelf applications, user developed custom
`applications, additional user interfaces, and the like. It is
`appreciated that client applications 250, 260 and 270 are entirely
`optional to system 200. Users of system 200 can implement more
`or fewer client applications based on their own needs within the
`scope of the present invention.
`
`Still referring to FIG. 2, in one embodiment, application server
`210 communicates with data server 220 via named pipes. In
`particular, using named pipes provides for scalability of system
`200 by delivering data from multiple applications running on one
`or more application servers. On the other hand, application server
`210 communicates with workbench 240 and client applications
`250, 260 and 270 through published interface 230. Published
`interface 230 is a consistent, public interface which serves as a
`bridge between application server 210 and client applications 250,
`260 and 270 and also workbench 240. In one embodiment,
`published interface 230 is built upon Microsoft’s COM/DCOM
`and ActiveX technologies. As such, users of system 200 can easily
`customize and/or extend the functionalities of the system by
`adding application extensions, such as client applications 250, 260
`and 270, which are compliant with these industry standard
`technologies. Through published interface 230, users can even
`integrate system 200 with other computer implemented systems,
`such as enterprise resource planning (ERP) systems, to provide a
`seamless enterprise computing environment.”
`
`Figure 2 and the accompanying text.
`
`To the extent this reference does not teach this claim element, this
`reference in combination with the knowledge of one of ordinary
`skill in the art and the disclosures of each of the prior art
`references provided in Salesforce’s Petitions related to the ‘482
`and ‘111 Patents renders this claim element obvious.
`GORDON discloses one or more client computers connected to the
`server computer over a computer network. See, e.g.:
`
`[b] one or more client
`computers connected to the
`
`04554.00001/6142698.1
`
`SFDC 1009
`
`

`
`‘482 Patent
`server computer over a
`computer network;
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`
`
`GORDON at Cols. 6-7: “With reference still to FIG. 2, in one
`embodiment, system 200 further includes workbench 240 and
`client applications 250, 260 and 270. Workbench 240 provides a
`collection of user applications to facilitate object and model
`definitions, user and security management, and also database
`configurations. Client applications 250, 260 and 270 are
`application extensions that enhance and/or customize the
`functionalities of system 200 and may include third party off-the-
`shelf applications, user developed custom applications, additional
`user interfaces, and the like. It is appreciated that client
`applications 250, 260 and 270 are entirely optional to system 200.
`Users of system 200 can implement more or fewer client
`applications based on their own needs within the scope of the
`present invention.
`
`Still referring to FIG. 2, in one embodiment, application server
`210 communicates with data server 220 via named pipes. In
`particular, using named pipes provides for scalability of system
`200 by delivering data from multiple applications running on one
`or more application servers. On the other hand, application server
`210 communicates with workbench 240 and client applications
`250, 260 and 270 through published interface 230. Published
`interface 230 is a consistent, public interface which serves as a
`bridge between application server 210 and client applications 250,
`260 and 270 and also workbench 240. In one embodiment,
`published interface 230 is built upon Microsoft’s COM/DCOM
`and ActiveX technologies. As such, users of system 200 can easily
`customize and/or extend the functionalities of the system by
`adding application extensions, such as client applications 250, 260
`and 270, which are compliant with these industry standard
`technologies. Through published interface 230, users can even
`integrate system 200 with other computer implemented systems,
`such as enterprise resource planning (ERP) systems, to provide a
`seamless enterprise computing environment.”
`
`GORDON at Col. 5: “In general, computer system 100 includes an
`address/data bus 102 for communicating information, a central
`processor 104 coupled with the bus for processing information and
`instructions, a volatile memory 106 (e.g., random access memory
`RAM) coupled with the bus 102 for storing information and
`instructions for the central processor 104 and a non-volatile
`memory 108 (e.g., read only memory ROM) coupled with the bus
`102 for storing static information and instructions for the
`processor 104. Computer system 100 also includes a data storage
`
`SFDC 1009
`
`

`
`U.S. Patent No. 6,243,717, to Gordon et al.
`device 110 (“disk subsystem”) such as a magnetic or optical disk
`and disk drive coupled with the bus 102 for storing information
`and instructions. Data storage device 110 can include one or more
`removable magnetic or optical storage media (e.g., diskettes,
`tapes) which are computer readable memories. Memory units of
`system 100 include 106, 108 and 110. Computer system 100 can
`also include a signal input output communication device 112 (e.g.,
`modem, network interface card NIC) coupled to the bus 102 for
`interfacing with other computer systems.”
`
`Figure 2 and the accompanying text.
`
`
`
`GORDON discloses a first layer associated with the server computer
`containing information about the unique aspects of a particular
`application. See, e.g.:
`
`GORDON at Cols. 6-7: “FIG. 2 is a high level block diagram of an
`exemplary configuration of the computer implemented system in
`accordance with the present invention. One embodiment of the
`computer implemented system of the present invention is a
`Manufacturing Execution System (MES) for integrating and
`managing information from the factory floor and for providing
`production management capabilities and factory automation
`solutions. Specifically, in one embodiment, system 200 includes
`application server 210, which encapsulates business rules and
`application logic as data objects and access methods, thus enabling
`flexible and powerful modeling of manufacturing data and
`processes. In a preferred embodiment, the novel method of
`revision management of the present invention is implemented
`within data server 220 and exposed through application server
`210. In one embodiment, multiple application servers can be
`maintained within system 200 to provide for additional scalability
`of the system.
`
`System 200 also includes data server 220 and database 250. Data
`server 220 is responsible for managing the translation of data from
`objects (e.g., modeling entities such as configurable data objects
`(CDOs)) in application server 210 to the proper database format
`for storage in database 250, and vice versa. Thus, data is retrieved
`from and stored to database 250, with the appropriate translation,
`via data server 220. In one embodiment, database 250 is a
`relational database management system (RDBMS), thereby
`allowing the use of industry standard tools for data access.
`
`‘482 Patent
`
`[c] a first layer associated
`with the server computer
`containing information
`about the unique aspects of
`a particular application;
`
`04554.00001/6142698.1
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`[d] a second layer
`associated with the server
`computer containing
`information about the user
`interface and functions
`common to a variety of
`applications,
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`Examples of commercially available RDBMS’s include SQL
`Server V6.5+ for Windows NT by Microsoft Corporation and
`Oracle 7.3+ for Windows NT or UNIX by Oracle Corporation. In
`one embodiment, communications between data server 220 and
`database 250 are supported via open database connectivity
`(ODBC), thus enabling full database independence.”
`
`Figure 2 and the accompanying text.
`
`To the extent this reference does not teach this claim element, this
`reference in combination with the knowledge of one of ordinary
`skill in the art and the disclosures of each of the prior art
`references provided in Salesforce’s Petitions related to the ‘482
`and ‘111 Patents renders this claim element obvious.
`GORDON discloses a second layer associated with the server
`computer containing information about the user interface and
`functions common to a variety of applications. See, e.g.:
`
`GORDON at Cols. 6-7: “FIG. 2 is a high level block diagram of an
`exemplary configuration of the computer implemented system in
`accordance with the present invention. One embodiment of the
`computer implemented system of the present invention is a
`Manufacturing Execution System (MES) for integrating and
`managing information from the factory floor and for providing
`production management capabilities and factory automation
`solutions. Specifically, in one embodiment, system 200 includes
`application server 210, which encapsulates business rules and
`application logic as data objects and access methods, thus enabling
`flexible and powerful modeling of manufacturing data and
`processes. In a preferred embodiment, the novel method of
`revision management of the present invention is implemented
`within data server 220 and exposed through application server
`210. In one embodiment, multiple application servers can be
`maintained within system 200 to provide for additional scalability
`of the system.
`
`System 200 also includes data server 220 and database 250. Data
`server 220 is responsible for managing the translation of data from
`To the extent this reference does not teach this claim element, this
`reference in combination with the knowledge of one of ordinary
`skill in the art and the disclosures of each of the prior art
`references provided in Salesforce’s Petitions related to the ‘482
`and ‘111 Patents renders this claim element obvious.objects (e.g.,
`modeling entities such as configurable data objects (CDOs)) in
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`application server 210 to the proper database format for storage in
`database 250, and vice versa. Thus, data is retrieved from and
`stored to database 250, with the appropriate translation, via data
`server 220. In one embodiment, database 250 is a relational
`database management system (RDBMS), thereby allowing the use
`of industry standard tools for data access. Examples of
`commercially available RDBMS’s include SQL Server V6.5+ for
`Windows NT by Microsoft Corporation and Oracle 7.3+ for
`Windows NT or UNIX by Oracle Corporation. In one
`embodiment, communications between data server 220 and
`database 250 are supported via open database connectivity
`(ODBC), thus enabling full database independence.
`
`With reference still to FIG. 2, in one embodiment, system 200
`further includes workbench 240 and client applications 250, 260
`and 270. Workbench 240 provides a collection of user applications
`to facilitate object and model definitions, user and security
`management, and also database configurations. Client applications
`250, 260 and 270 are application extensions that enhance and/or
`customize the functionalities of system 200 and may include third
`party off-the-shelf applications, user developed custom
`applications, additional user interfaces, and the like. It is
`appreciated that client applications 250, 260 and 270 are entirely
`optional to system 200. Users of system 200 can implement more
`or fewer client applications based on their own needs within the
`scope of the present invention.
`
`Still referring to FIG. 2, in one embodiment, application server
`210 communicates with data server 220 via named pipes. In
`particular, using named pipes provides for scalability of system
`200 by delivering data from multiple applications running on one
`or more application servers. On the other hand, application server
`210 communicates with workbench 240 and client applications
`250, 260 and 270 through published interface 230. Published
`interface 230 is a consistent, public interface which serves as a
`bridge between application server 210 and client applications 250,
`260 and 270 and also workbench 240. In one embodiment,
`published interface 230 is built upon Microsoft’s COM/DCOM
`and ActiveX technologies. As such, users of system 200 can easily
`customize and/or extend the functionalities of the system by
`adding application extensions, such as client applications 250, 260
`and 270, which are compliant with these industry standard
`technologies. Through published interface 230, users can even
`integrate system 200 with other computer implemented systems,
`such as enterprise resource planning (ERP) systems, to provide a
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`[e] a particular application
`being generated based on
`the data in both the first and
`second layers;
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`seamless enterprise computing environment.”
`
`GORDON at Col. 1: “Modern computer implemented systems
`generally include functionalities by which data is stored, updated
`and accessed. In these computer implemented systems, data
`records are stored in a retrievable storage (e.g., a database residing
`in magnetic and/or optical media), and cross references or links
`among related data records are common. Typically, such cross
`references are stored in the retrievable media together with the
`associated data records. In the prior art, a user typically has to
`manually update all data records that reference a data record
`whenever the referenced data record is revised to ensure that any
`changes in the referenced data record are reflected accordingly in
`the referencing data record(s). Alternatively, the user has to
`specifically write a program or script to perform the same
`updating task. Numerous drawbacks exist for these prior art
`schemes. First, manual updating or additional programming as
`required in the prior art is error prone. For instance, if any
`referencing data record is not updated due to an omission or
`undetected programming error, the user is not alerted about the
`missing update and the integrity of the data is compromised.
`Furthermore, when an outdated referencing data record is itself
`referenced subsequently, it may even propagate the incorrect
`information with respect to the first referenced data record,
`thereby further degrading data integrity.”
`
`GORDON at claims 10 and 16.
`
`Figures 6, 9, and 10, and the accompanying text.
`
`To the extent this reference does not teach this claim element, this
`reference in combination with the knowledge of one of ordinary
`skill in the art and the disclosures of each of the prior art
`references provided in Salesforce’s Petitions related to the ‘482
`and ‘111 Patents renders this claim element obvious.
`GORDON discloses a particular application being generated based
`on the data in both the first and second layers. See, e.g.:
`
`GORDON at Cols. 6-7: “FIG. 2 is a high level block diagram of an
`exemplary configuration of the computer implemented system in
`accordance with the present invention. One embodiment of the
`computer implemented system of the present invention is a
`Manufacturing Execution System (MES) for integrating and
`managing information from the factory floor and for providing
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`production management capabilities and factory automation
`solutions. Specifically, in one embodiment, system 200 includes
`application server 210, which encapsulates business rules and
`application logic as data objects and access methods, thus enabling
`flexible and powerful modeling of manufacturing data and
`processes. In a preferred embodiment, the novel method of
`revision management of the present invention is implemented
`within data server 220 and exposed through application server
`210. In one embodiment, multiple application servers can be
`maintained within system 200 to provide for additional scalability
`of the system.
`
`System 200 also includes data server 220 and database 250. Data
`server 220 is responsible for managing the translation of data from
`objects (e.g., modeling entities such as configurable data objects
`(CDOs)) in application server 210 to the proper database format
`for storage in database 250, and vice versa. Thus, data is retrieved
`from and stored to database 250, with the appropriate translation,
`via data server 220. In one embodiment, database 250 is a
`relational database management system (RDBMS), thereby
`allowing the use of industry standard tools for data access.
`Examples of commercially available RDBMS’s include SQL
`Server V6.5+ for Windows NT by Microsoft Corporation and
`Oracle 7.3+ for Windows NT or UNIX by Oracle Corporation. In
`one embodiment, communications between data server 220 and
`database 250 are supported via open database connectivity
`(ODBC), thus enabling full database independence.
`
`With reference still to FIG. 2, in one embodiment, system 200
`further includes workbench 240 and client applications 250, 260
`and 270. Workbench 240 provides a collection of user applications
`to facilitate object and model definitions, user and security
`management, and also database configurations. Client applications
`250, 260 and 270 are application extensions that enhance and/or
`customize the functionalities of system 200 and may include third
`party off-the-shelf applications, user developed custom
`applications, additional user interfaces, and the like. It is
`appreciated that client applications 250, 260 and 270 are entirely
`optional to system 200. Users of system 200 can implement more
`or fewer client applications based on their own needs within the
`scope of the present invention.
`
`Still referring to FIG. 2, in one embodiment, application server
`210 communicates with data server 220 via named pipes. In
`particular, using named pipes provides for scalability of system
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`200 by delivering data from multiple applications running on one
`or more application servers. On the other hand, application server
`210 communicates with workbench 240 and client applications
`250, 260 and 270 through published interface 230. Published
`interface 230 is a consistent, public interface which serves as a
`bridge between application server 210 and client applications 250,
`260 and 270 and also workbench 240. In one embodiment,
`published interface 230 is built upon Microsoft’s COM/DCOM
`and ActiveX technologies. As such, users of system 200 can easily
`customize and/or extend the functionalities of the system by
`adding application extensions, such as client applications 250, 260
`and 270, which are compliant with these industry standard
`technologies. Through published interface 230, users can even
`integrate system 200 with other computer implemented systems,
`such as enterprise resource planning (ERP) systems, to provide a
`seamless enterprise computing environment.”
`
`GORDON at Col. 1: “Modern computer implemented systems
`generally include functionalities by which data is stored, updated
`and accessed. In these computer implemented systems, data
`records are stored in a retrievable storage (e.g., a database residing
`in magnetic and/or optical media), and cross references or links
`among related data records are common. Typically, such cross
`references are stored in the retrievable media together with the
`associated data records. In the prior art, a user typically has to
`manually update all data records that reference a data record
`whenever the referenced data record is revised to ensure that any
`changes in the referenced data record are reflected accordingly in
`the referencing data record(s). Alternatively, the user has to
`specifically write a program or script to perform the same
`updating task. Numerous drawbacks exist for these prior art
`schemes. First, manual updating or additional programming as
`required in the prior art is error prone. For instance, if any
`referencing data record is not updated due to an omission or
`undetected programming error, the user is not alerted about the
`missing update and the integrity of the data is compromised.
`Furthermore, when an outdated referencing data record is itself
`referenced subsequently, it may even propagate the incorrect
`information with respect to the first referenced data record,
`thereby further degrading data integrity.”
`
`GORDON at claims 10 and 16.
`
`Figures 6, 9, and 10, and the accompanying text.
`
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`[f] a third layer associated
`with the server computer
`that retrieves the data in the
`first and second layers in
`order to generate the
`functionality and user
`interface elements of the
`application; and
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`To the extent this reference does not teach this claim element, this
`reference in combination with the knowledge of one of ordinary
`skill in the art and the disclosures of each of the prior art
`references provided in Salesforce’s Petitions related to the ‘482
`and ‘111 Patents renders this claim element obvious.
`GORDON discloses a third layer associated with the server
`computer that retrieves the data in the first and second layers in
`order to generate the functionality and user interface elements of
`the application. See, e.g.:
`
`GORDON at Cols. 6-7: “FIG. 2 is a high level block diagram of an
`exemplary configuration of the computer implemented system in
`accordance with the present invention. One embodiment of the
`computer implemented system of the present invention is a
`Manufacturing Execution System (MES) for integrating and
`managing information from the factory floor and for providing
`production management capabilities and factory automation
`solutions. Specifically, in one embodiment, system 200 includes
`application server 210, which encapsulates business rules and
`application logic as data objects and access methods, thus enabling
`flexible and powerful modeling of manufacturing data and
`processes. In a preferred embodiment, the novel method of
`revision management of the present invention is implemented
`within data server 220 and exposed through application server
`210. In one embodiment, multiple application servers can be
`maintained within system 200 to provide for additional scalability
`of the system.
`
`System 200 also includes data server 220 and database 250. Data
`server 220 is responsible for managing the translation of data from
`objects (e.g., modeling entities such as configurable data objects
`(CDOs)) in application server 210 to the proper database format
`for storage in database 250, and vice versa. Thus, data is retrieved
`from and stored to database 250, with the appropriate translation,
`via data server 220. In one embodiment, database 250 is a
`relational database management system (RDBMS), thereby
`allowing the use of industry standard tools for data access.
`Examples of commercially available RDBMS’s include SQL
`Server V6.5+ for Windows NT by Microsoft Corporation and
`Oracle 7.3+ for Windows NT or UNIX by Oracle Corporation. In
`one embodiment, communications between data server 220 and
`database 250 are supported via open database connectivity
`(ODBC), thus enabling full database independence.
`
`
`SFDC 1009
`
`

`
`‘482 Patent
`
`04554.00001/6142698.1
`
`U.S. Patent No. 6,243,717, to Gordon et al.
`With reference still to FIG. 2, in one embodiment, system 200
`further includes workbench 240 and client applications 250, 260
`and 270. Workbench 240 provides a collection of user applications
`to facilitate object and model definitions, user and security
`management, and also database configurations. Client applications
`250, 260 and 270 are application extensions that enhance and/or
`customize the functionalities of system 200 and may include third
`party off-the-shelf applications, user developed custom
`applications, additional user interfaces, and the like. It is
`appreciated that client applications 250, 260 and 270 are entirely
`optional to system 200. Users of