Abstract: A system and method of synchronizing recipes and bills of materials (BOM). An approved recipe is parameterized in a planning interface. A BOM is synchronized with the parameterized recipe. The BOM is then displayed in a graphical user interface to allow a user to modify by a resolve conflict present during synchronization.

Abstract: In some implementations, a benchmarking system may be used to provide benchmarking data or reports. The benchmarking system may include benchmarking scenario tag templates that may include tags associated with defined data structures. In some instances, the data structures may be defined in a technology- or solution-independent manner. A business data provider may request a benchmarking tag template and associate the tags with the relevant elements of business data. The tagged elements of the business data may be extracted and transformed to be loaded into the benchmarking system. In some instances, the tagged elements of the business data may be transformed by anonymization or pseudonymization. The benchmarking system may use the tagged elements of the business data and other data to generate benchmarking data. The business data provider may opt in to a scenario to include the tagged elements of the business data into a benchmarking data database.

Abstract: Generation of an engineering change case is initiated by associating an identified problem for a product with an engineering change case template. The engineering change case can include a plurality of structured folders that can be populated with content characterizing the identified problem as well as proposed solutions to the identified problem with each folder being assignable to one or more users and having associated deliverables for such users. The various users populate the folders with content associated with the deliverables with at least a portion of the deliverables being delegable and requiring completion in a sequential order. Thereafter, generation of the engineering case can be finalized when an indication is received that all deliverables requiring approval have been completed. Otherwise, the engineering change case can be canceled. Related apparatus, systems, techniques and articles are also described.

Abstract: This disclosure provides various embodiments of a system, method, and software for implementing a logically centralized source for collaboration on objectives. In one aspect, the method identifies one or more requirements and requirement statuses associated with a business entity for use in a business object stored within a logically centralized repository, the repository storing a plurality of business objects, identifies one or more solutions and solution statuses associated with the identified requirements for use in the business object, and notifies a party of an update to one of the statuses associated with the identified requirements and solutions.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a customer project invoicing agreement, an engineering change case, a product design, a product design version hierarchy, and/or a project expense view business object.

Abstract: A system and method of synchronizing recipes and bills of materials (BOM). An approved recipe is parameterized in a planning interface. A BOM is synchronized with the parameterized recipe. The BOM is then displayed in a graphical user interface to allow a user to modify by a resolve conflict present during synchronization.

Abstract: Generation of an engineering change case is initiated by associating an identified problem for a product with an engineering change case template. The engineering change case can include a plurality of structured folders that can be populated with content characterizing the identified problem as well as proposed solutions to the identified problem with each folder being assignable to one or more users and having associated deliverables for such users. The various users populate the folders with content associated with the deliverables with at least a portion of the deliverables being delegable and requiring completion in a sequential order. Thereafter, generation of the engineering case can be finalized when an indication is received that all deliverables requiring approval have been completed. Otherwise, the engineering change case can be canceled. Related apparatus, systems, techniques and articles are also described.

Abstract: This disclosure provides various embodiments of a system, method, and software for implementing a logically centralized source for collaboration on objectives. In one aspect, the method identifies one or more requirements and requirement statuses associated with a business entity for use in a business object stored within a logically centralized repository, the repository storing a plurality of business objects, identifies one or more solutions and solution statuses associated with the identified requirements for use in the business object, and notifies a party of an update to one of the statuses associated with the identified requirements and solutions.

Abstract: Systems and techniques for tailoring the storage of information. In one implementation, a computer program product is operable to cause data processing apparatus to create a framework of elements to present a user with a presentation of options for tailoring an object, receive user input for tailoring the object in response to the presentation of options, define the tailored object to include the first field and the second field, associate an identifier of the first participant with the first field to indicate that the first participant is to be excluded from a first activity performed with the first field, and associate an identifier of the second participant with the second field to indicate that the second participant is to be excluded from a second activity performed with the second field. The received user input can identify a first field to be included in the tailored object, a second field to be included in the tailored object, a first participant, and a second participant.