WO2003081467A2

WO2003081467A2 - Synchronizing users on shared data with locks

Info

Publication number: WO2003081467A2
Application number: PCT/IB2003/001614
Authority: WO
Inventors: Wolfgang Kalthoff; Thomas Vogt; Guenter Huber; Guido Hoeckele; Beate Koch
Original assignee: SAP SE
Current assignee: SAP SE
Priority date: 2002-03-21
Filing date: 2003-03-21
Publication date: 2003-10-02
Anticipated expiration: 2004-09-21
Also published as: EP1523716A2; AU2003219415A8; WO2003081467A3; US20050091179A1; US8499036B2; AU2003219415A1

Abstract

Methods and apparatus, including computer program products, for sharing information. The technique includes defining a stored data set maintained by a first entity to include a locked data set and an unlocked data set, and providing a second entity with access to the stored data set. The second entity has permission to change only the unlocked data set and view the locked data set.

Description

COLLABORATION PROCESS

BACKGROUND The present invention relates to data processing, and more particularly, to sharing data. An important factor in the success of businesses in the current era is the ability to flexibly react to the requirements of the market. Shorter product cycles require decreased product development times and quicker introduction to market while increased customer demands for individual solutions increases the number of variants.

These factors require businesses to be able to proceed simultaneously with the definition of the product requirements and its structure as well as the introduction of collaborative processes during communication with subcontractors and development partners. New products must be introduced rapidly to market based on internally and externally defined requirements. In order to do this, different approaches must be considered, and input can be provided by different groups of people. Thus, the data used in the collaborative processes has to be monitored for consistency.

For example, one process that requires collaboration is the integration of engineering partners into product development. Different groups of people can change the available data while working on their part of the project. This can lead to logical corruption of data, where two different copies of the same data are edited simultaneously. This logical corruption can render the data unreliable.

SUMMARY The present invention provides methods and apparatus, including computer program products, for sharing data in a product creation process.

In general, in one aspect, the invention features methods and apparatus implementing a technique for sharing information. The technique includes defining a stored data set maintained by a first entity to include a locked data set and an unlocked data set and providing a second entity with access to the stored data set. The second entity has permission to change only the unlocked data set and view the locked data set. Particular implementations can include one or more of the following features. Providing a second entity with access to the stored data set can include providing an application in a computer system with access to the stored data set. The application can be maintained at a location external to the first entity. The application can include a testing application. The locked data set can include information to call the application while the unlocked data set can include data to be used by the application. Alternatively, the locked data set can include version data for the application and the unlocked data set can include raw data for the second entity to look at or use.

The first entity can also be provided with access to the stored data set. The first entity can have permission to change only the locked data set, and view the unlocked data set. The second entity can include a testing entity.

Providing the second entity with access to the stored data set can include sending the data to the second entity. The second entity can include an entity that is external to the first entity. Data in the stored data set can be assigned to the locked data set and the unlocked data set based on predetermined criteria. The stored data set can also include a restricted data set including data that is not part of the locked data set or the unlocked data set. Data can be assigned to the locked data set based on closeness criteria. Closeness criteria can include geometric closeness, organizational closeness, and collective closeness. Data in the stored data set can be assigned to the locked data set and the unlocked data set based on a function of the second entity.

The technique can also include transmitting data from the stored data set to the second entity, receiving modified data from the second entity, and integrating the modified data corresponding to the unlocked data set into the stored data set. The stored data set can be defined to include a locked data set and an unlocked data set based on user input.

In another aspect, the invention features methods and apparatus implementing a technique for sharing information. The technique includes defining a master data set in a first entity, assigning permissions to a subset of data within the master data set based on predetermined criteria, transmitting a copy of the master data set with indications of the permissions to a second entity, and receiving manipulated master data set in accordance with the assigned permissions. The assigned permissions can include permission to change data. Particular implementations can include one or more of the following features. The technique can also include receiving a modified copy of the master data set from the second entity and integrating the modified copy of the master data set with the master data set. The modified copy of the master data set can includes additional data, test results and/or changed data. The changed data can include data that has been changed in response to testing.

The assigned permissions can include authority to read data, authority to change data, authority to add data and authority to delete data. The assigned permissions can also include authority to access predetermined types of data within the subset.

Assigning permissions can include assigning permissions based on at least one of entity, function of the entity and position within the entity. Assigning permissions based on position within the entity can include assigning permissions according to a hierarchy within the entity so that a highest ranking member of an entity has a greater number of permissions, and a number and extent of permissions decrease as rank decreases.

Assigning permissions can also include assigning different permissions for different subsets of the unlocked data.

In yet another aspect, the invention features methods and apparatus implementing a technique for sharing information. The technique can include receiving, from a first entity in a second entity, a copy of a master data set with permissions for using the master data set, modifying the copy of the master data set according to the permissions, and transmitting the modified copy of the master data set to the first entity. The master data set can include locked and unlocked data.

Particular implementations can include one or more of the following features. Receiving the copy of the master data set in a second entity can include receiving the copy of the master data set in a computer application. Receiving the copy of the master data set in a computer application can include receiving version information regarding the computer application in the locked data and raw data to manipulate in the unlocked data.

Modifying the copy of the master data set can include performing testing on the unlocked portion of the data.

Receiving the copy of the master data set with permissions for using the master data set can include receiving permissions to do one or more of read, change and add data to the unlocked data. Receiving the copy of the master data set with permissions for using the master data set can also include receiving the copy of the master data set with permissions based on subsets of the unlocked data, with different permissions assigned for different subsets of the unlocked data.

Receiving the copy of the master data set with permissions for using the master data set can further include receiving the copy of the master data set with permissions based on at least one of the second entity, the function of the second entity and hierarchy of the second entity.

The invention can be implemented to realize one or more of the following advantages. An entity can share data with other entities while ensuring that the data is consistent and reliable. By defining a master data set to include a locked data set and an unlocked data set, an entity that maintains a master data set can protect data in the master data set that it shares with other users and/or applications. Locking data and maintaining a master data set also allows avoidance of reconciliation processes. Since the master data keeps track of all changes, only an entity having the appropriate permissions can change the data. Thus, two edited versions of data do not need to be reconciled.

Providing locked data with unlocked data, or data that an entity is permitted to edit, allows an entity to receive context information related to the data the entity is permitted to edit. Thus, an entity can see how modifications of the unlocked data will affect related data. The details of one or more implementations of the invention are set forth in the accompanying drawings and the description below. Other features and advantages of the invention will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a product creation system. FIG. 2 is a block diagram illustrating a data sharing system.

FIG. 3 is a block diagram illustrating an alternative data sharing system.

FIG. 4 is a flow diagram illustrating a method of sharing data.

FIG. 5 is a flow diagram illustrating an alternative method of sharing data.

FIG. 6 is a flow diagram illustrating an implementation of a method of using shared data.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION As shown in FIG. 1 , a data sharing system can be implemented in a product creation system 100. The product creation system 100 includes a central module 110 and entity modules 120. Each of the modules 110, 120 includes a data store 115, 125. Although the following description is directed to a product creation system, the data sharing system can be used with any system in which data is shared by two entities.

The central module 110 represents a centralized control for a product creation process. The entity modules 120 represent entities involved in the product creation process. The entities can include computer applications as well as companies, departments or individuals. Many different entities can participate in the development of a product. The entities can include internal and external entities. For example, entity modules 120 can include modules for design, testing, purchasing, marketing, sales, manufacturing, installation, customer service, technical services, customers, dealers, distributors, suppliers, vendors, and regulatory organizations. The central module 110 and the entity modules 120 can communicate through a network 130.

The central module 1 10 includes a central data store 115 that stores master data for a product creation process. The master data includes objects associated with the product creation process. These objects can include product classes, attributes, product line designs, parts lists, materials lists, quality specifications, requirements, routing and process structures.

The central data can be accessed by the entity modules 120, based on permissions, or transmitted to the entity modules 120 through network 130. Each of the entity modules 120 includes a data store 125 for storing the data received from the central module 110 and for additional entity specific data developed in entity module 120. For example, if the entity module 120 is a marketing module, the corresponding data store 125 could store marketing specific information.

The entity modules 120 can develop objects of the product creation process in parallel. Each entity module 120 can develop different versions of each object of the product creation process. For example, classes of a product can include types, models, body styles, sizes, etc. Attributes can include information about component parts such as engine type (e.g., 95 HP, 110 HP, 125 HP, etc.) or brake type (e.g., disc or drum), or characteristics such as body color (e.g., black, silver, red, etc.) or fuel efficiency (e.g., 30 m.p.g.). FIG. 2 is a block diagram illustrating a data sharing system 200. The data sharing system 200 includes a set of master data 210 stored in a first entity data store, such as central data store 115. The first entity can include central module 110. The master data 210 can be shared with a second entity 120 by allowing access to the second entity, such as an entity module 120. The data sharing system 200 allows master data 210 to include a locked data set 220 and an unlocked data set 230. Data within the master data 210 can be assigned to the locked data set 220 and unlocked data 230 by the first entity or users associated with the first entity. The master data 210 can also include a set of restricted data 240. The restricted data 240 can be assigned by the first entity. The restricted data includes all data that is not included in the locked data set 220 or the unlocked data set 230. The restricted data set 240 can include data that is not relevant to the second entity 120 or confidential data to which the second entity 120 is not given access. Unlocked data set 230 can include data that is to be manipulated by the second entity. The locked data set 220 can include information that the second entity has access to but does not have permission to use. For example, if the second entity is a testing application, the unlocked data set 220 can include testing data while the locked data set 230 can include information that the first entity uses to call the testing application. The testing application can access the unlocked data set 230 and manipulate the data, such as by performing tests based on the available data and updating the testing results in the unlocked data set 230.

The unlocked data set 230 can include a variety of permissions for manipulation. The permissions can include permissions to read the data, add new data within the unlocked data set 230 (e.g., add a new category of data), and permission to change or delete existing data in the unlocked data set. The unlocked data set can be divided into smaller subsets where the permissions vary from set to set. For example, the entity can read one subset, change data in another subset, and add and change data in a third subset. The permissions can be assigned to the second entity according to a hierarchy. For example, if the second entity is an entity including a plurality of employees, the permissions can be assigned according to position within the entity so that a highest ranking member of the entity has a greater number of permissions, and a number and extent of permissions decrease as rank decrease. For example, the director of a group could have permission to read, add and change data in all subsets of the unlocked data set, while supervisors for departments within the group can have permission to read, add and change subsets of data that apply to their departments only. Lower level employees can be given permission to only read data within the subset of the unlocked data that applies to their departments. In addition to permissions, locked data could include identifiers for versions of applications or even applications to use in manipulating the data (the unlocked data).

The permissions can also be used to divide the master data set 210 into the locked data set 220, unlocked data set 230 and the restricted data set 240. For example, data that is made available to the second entity 120 with an assigned a permission of read only can be part of the locked data set 220. Data that is assigned a permission allowing the second entity 120 to change the data can be part of the unlocked data set 230.

Data can be separated between the locked data set 220 and the restricted data set 240 based on closeness criteria. Closeness criteria can include geometrical closeness, organizational closeness, and/or collective closeness. An algorithm for including data in the locked data set 220 that is based on geometrical closeness can cause the locked data set 220 to include data about items that are geometrically or physically close to the subject of the unlocked data set 230. For example, if the unlocked data set 230 includes data regarding design of headlights of a car, the locked data set 220 can include information regarding the headlight support on the body of the car. Because the headlight support is physically close to the headlight, and the headlight support can affect headlight design. Information regarding the car's rear wheel can be left in the restricted data set 240 because the rear wheel is not close to the headlight.

An algorithm based on organizational closeness can cause the locked data set to include data regarding items that are a part of the same organizational structure as the subject of the unlocked data set 230. For example, if the unlocked data set 230 includes data about the motor of a car, the locked data set 220 can include information regarding the rear axle of the car. Although the motor and the rear axle may not be geometrically close, they are part of the same organizational structure. An algorithm based on collective closeness can cause the locked data set 220 to include data regarding items that are a part of the same data collection as the subject of the unlocked data set 230. Thus, if the unlocked data set 230 includes data regarding a car's headlights, the locked data set can include information regarding the car's battery. Although the battery is not geometrically close to the headlights, or part of the same organizational structure, the headlight and battery can be part of the same data collection.

Thus, collective closeness can be used to override exclusions based on geometric or organizational closeness criteria. Inclusion of data in the locked data set 220 can be limited by permissions, as discussed above. If data that can be included in the locked data set 220 based on the closeness criteria is considered too confidential to be shared with a second entity 120, the confidential data is excluded from the locked data set 220 and remains in the restricted data set 240.

FIG. 3 is a block diagram illustrating an alternative data sharing system 200. The first entity data store includes locked data 220a and unlocked data 230a. The first entity can use or change unlocked data 230a, but can only view the locked data 220a. The first entity can transmit a copy of the master data 210 to the second entity 120. The second entity receives a copy of the master data 210 from the first entity over network 130. The second entity stores the received copy in a data store 125. When the copy of the master data set 210 is transmitted to the second entity, the locked and unlocked data become reversed in the second entity data store 125. The locked data set 220a in the first entity becomes the unlocked data set 230b in the second entity 120, while the unlocked data set 230a in the first entity becomes the locked data set 220b in the second entity 120.

The second entity can manipulate and modify the copy of the master data 210 in its data store 125 in accordance with permissions attached to the data. The second entity 120 transmits the modified copy of the master data to the first entity. The first entity can integrate the modified copy of the master data with the copy of the master data 210 stored in data store 115 according to the permissions assigned. For example, if the modified copy of the master data includes changes or new data from sources that did not have permission to manipulate the data, those modifications are not included in the master data 210 stored in data store 115. FIG. 4 is a flow diagram illustrating a method of sharing data. The method includes defining a locked data set 220 and an unlocked data set 230 in a master data set 210. (step 410) Defining the locked data set 220 and unlocked data set 230 can include defining the locked data set 220 and unlocked data set 230 based on permissions, as described above. Thus, data that is in the locked data set 220 for one entity 120 can be in the unlocked data set 230 for another entity 120.

The locked set of data 220 and the unlocked set of data 230 can also be divided based on the function of the entity 120 receiving the data. For example, if the entity 120 receiving the data is the marketing department, the unlocked set of data 230 can include marketing related information, such as marketing statistics or sales projections.

When the locked set of data 220 and the unlocked set of data 230 have been defined, a first entity can provide a second entity with access to the master data set 210 based on the permissions assigned to the second entity, (step 420) The second entity can include an organization, an individual, a computer application, or any other entity capable of using data. The second entity can manipulate the unlocked data set according to the permissions assigned to it.

If the second entity includes a computer application, the locked data set can include information to call the application while the unlocked data set includes data to be used by the application. For example, the locked data set can include version data of the application called while the unlocked data set includes raw data for the application to look at or use in its execution.

FIG. 5 is a flow diagram of another implementation of a method of sharing master data. The method can include transmitting the set of master data 210 from a first entity, such as central module 110, to a second entity, such as entity module 120. (Step 510) The master data can be defined as described above with reference to FIG. 4.

The method further includes receiving a modified copy of the master data from the second entity. (Step 520) The modified copy of the master data can include additions or changes to the master data 210 performed by the second entity according to permissions assigned to the second entity.

The first entity integrates the modified copy of the master data into the master data set 210 stored in central data store 1 10, according to the permissions assigned to the second entity. (Step 530) For example, the first entity can replace data in the unlocked data set 230 with modifications made in the unlocked data set by the second entity. The first entity can further check the source of each modification to determine if the source of the change in the second entity had permission to modify the data. Then, the first entity can modify the data in the unlocked data set 230 in central store 1 15 only if the source had permission. FIG. 6 is a flow diagram illustrating an implementation of a method of using shared master data 210 by the second entity. The method of using the shared master data 210 can include receiving a copy of the master data set 210 with permissions. (Step 610) The shared master data 210 is received in the second entity from the first entity. The second entity can modify the copy of the master data set according to the permissions received with the copy of the master data set. (Step 620) For example, if the second entity is a testing application, the second entity can perform tests using the unlocked data, and update testing data. After the second entity is finished manipulating the copy of the master data set, the second entity transmits the modified copy of the master data set to the first entity (630). The first entity integrates the modified copy with the master data set in data store 115, as described with reference to FIG. 5.

The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The invention can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

Method steps of the invention can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.

To provide for interaction with a user, the invention can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

The invention can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or an Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), and the Internet. The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The invention has been described in terms of particular embodiments. Other embodiments are within the scope of the following claims. For example, the steps of the invention can be performed in a different order and still achieve desirable results. What is claimed is:

Claims

1. A method of sharing information, comprising: defining a stored data set maintained by a first entity to include a locked data set and an unlocked data set; and providing a second entity with access to the stored data set, the second entity having permission to change only the unlocked data set, and view the locked data set.

2. The method of claim 1, wherein providing a second entity with access to the stored data set includes providing an application in a computer system with access to the stored data set.

3. The method of claim 2, wherein providing an application in a computer system with access to the stored data set includes providing an application maintained at a location external to the first entity with access to the stored data set.

4. The method of claim 2, wherein providing an application in a computer system with access to the stored data set includes providing a testing application with access to the stored data set.

5. The method of claim 2, wherein defining a stored data set maintained by a first entity to include a locked data set and an unlocked data set includes defining the locked data set to include information to call the application and the unlocked data set to include data to be used by the application.

6. The method of claim 2, wherein defining a stored data set maintained by a first entity to include a locked data set and an unlocked data set includes defining version data for the application as the locked data set and defining raw data for the second entity to look at or use as the unlocked data.

7. The method of claim 1, wherein providing a second entity with access to the stored data set includes sending the data to the second entity.

8. The method of claim 1, further comprising providing the first entity with access to the stored data set, the first entity having permission to change only the locked data set, and view the unlocked data set.

9. The method of claim 1, wherein providing a second entity with access to the stored data set includes providing a testing entity with access to the stored data set.

10. The method of claim 1 , wherein providing a second entity with access includes providing an entity that is external to the first entity with access.

11. The method of claim 1 , wherein defining the stored data set to include a locked data set and an unlocked data set includes assigning data in the stored data set to the locked data set and an unlocked data set based on predetermined criteria.

12. The method of claim 1, wherein defining the stored data set to include a locked data set and an unlocked data set further includes defining the stored data set to include a restricted data set including data that is not part of the locked data set or the unlocked data set.

13. The method of claim 1, wherein defining the stored data set to include a locked data set and an unlocked data set further includes assigning data to the locked data set based on closeness criteria.

14. The method of claim 13, wherein assigning data to the locked data set based on closeness criteria includes assigning data to the locked data set based on at least one of geometric closeness, organizational closeness, and collective closeness.

15. The method of claim 1, wherein defining the stored data set to include a locked data set and an unlocked data set includes assigning data in the stored data set to the locked data set and the unlocked data set based on a function of the second entity.

16. The method of claim 1 , further comprising: transmitting data from the stored data set to the second entity; receiving modified data from the second entity; and integrating the modified data corresponding to the unlocked data set into the stored data set.

17. The method of claim 1, wherein defining the stored data set to include a locked data set and an unlocked data set includes defining the stored data set to include a locked data set and an unlocked data set based on user input.

18. A method of sharing information, comprising: defining a master data set in a first entity; assigning permissions, including permission to change data, to a subset of data within the master data set based on predetermined criteria; transmitting a copy of the master data set with indications of the permissions to a second entity; and receiving manipulated master data set in accordance with the assigned permissions.

19. The method of claim 18, further comprising receiving a modified copy of the master data set from the second entity and integrating the modified copy of the master data set with the master data set.

20. The method of claim 19, wherein receiving the modified copy of the master data set includes receiving additional data.

21. The method of claim 20, wherein receiving additional data includes receiving test results.

22. The method of claim 19, wherein receiving the modified copy of the master data set includes receiving changed data

23. The method of claim 22, wherein receiving changed data includes receiving data that has been changed in response to testing.

24. The method of claim 18, wherein assigning permissions includes assigning authority to read data.

25. The method of claim 18, wherein assigning permissions includes assigning authority to change data.

26. The method of claim 18, wherein assigning permissions includes assigning authority to add data.

27. The method of claim 18, wherein assigning permissions includes assigning authority to delete data.

28. The method of claim 18, wherein assigning permissions includes assigning authority to access predetermined types of data within the subset.

29. The method of claim 18, wherein assigning permissions includes assigning permissions based on at least one of entity, function of the entity and position within the entity.

30. The method of claim 28, wherein assigning permissions based on position within the entity includes assigning permissions according to a hierarchy within the entity so that a highest ranking member of an entity has a greater number of permissions, and a number and extent of permissions decrease as rank decreases.

31. The method of claim 18, wherein assigning permissions includes assigning different permissions for different subsets of the unlocked data.

32. A method of sharing information, comprising: receiving, from a first entity in a second entity, a copy of a master data set with permissions for using the master data set, the master data set including locked and unlocked data; modifying the copy of the master data set according to the permissions; and transmitting the modified copy of the master data set to the first entity.

33. The method of claim 32, wherein receiving the copy of the master data set in a second entity includes receiving the copy of the master data set in a computer application.

34. The method of claim 33, wherein receiving the copy of the master data set in a computer application includes receiving version information regarding the computer application in the locked data and raw data to manipulate in the unlocked data.

35. The method of claim 32, wherein modifying the copy of the master data set includes performing testing on the unlocked portion of the data.

36. The method of claim 32, wherein receiving the copy of the master data set with permissions for using the master data set includes receiving permissions to do one or more of read, change, delete and add data to the unlocked data.

37. The method of claim 32, wherein receiving the copy of the master data set with permissions for using the master data set includes receiving the copy of the master data set with permissions based on subsets of the unlocked data, with different permissions assigned for different subsets of the unlocked data.

38. The method of claim 32, wherein receiving the copy of the master data set with permissions for using the master data set includes receiving the copy of the master data set with permissions based on at least one of the second entity, the function of the second entity and hierarchy of the second entity.

39. A computer program product, tangibly stored on a computer-readable medium, the computer program product comprising instructions operable to cause a programmable processor to: define a stored data set maintained by a first entity to include a locked data set and an unlocked data set; and provide a second entity with access to the stored data set, the second entity having permission to change only the unlocked data set, and view the locked data set.

40. The con^ "t program product of claim 39, wherein the instructions operable to cause a programmable processor to provide a second entity with access to the stored data set includes instructions operable to cause a programmable processor to provide an application in a computer system with access to the stored data set.

41. The computer program product of claim 40, wherein the instructions operable to cause a programmable processor to provide an application in a computer system with access to the stored data set includes instructions operable to cause a programmable processor to provide an application maintained at a location external to the first entity with access to the stored data set.

42. The computer program product of claim 40, wherein the instructions operable to cause a programmable processor to provide an application in a computer system with access to the stored data set includes the instructions operable to cause a programmable processor to provide a testing application with access to the stored data set.

43. The computer program product of claim 40, wherein the instructions operable to cause a programmable processor to define a stored data set maintained by a first entity to include a locked data set and an unlocked data set includes the instructions operable to cause a programmable processor to define the locked data set to include information to call the application and the unlocked data set to include data to be used by the application.

44. The computer program product of claim 40, wherein the instructions operable to cause a programmable processor to define a stored data set maintained by a first entity to include a locked data set and an unlocked data set includes the instructions operable to cause a programmable processor to define the locked data set to define version data for the application as the locked data set and raw data for the second entity to look at or use as the unlocked data.

45. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to provide a second entity with access to the stored data set includes instructions operable to cause a programmable processor to send the data to the second entity.

46. The computer program product of claim 39, further comprising instructions operable to cause a programmable processor to provide the first entity with access to the stored data set, the first entity having permission to change only the locked data set, and view the unlocked data set.

47. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to provide a second entity with access to the stored data set includes the instructions operable to cause a programmable processor to provide a testing entity with access to the stored data set.

48. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to provide a second entity with access includes instructions operable to cause a programmable processor to provide an entity that is external to the first entity with access.

49. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to define the stored data set to include a locked data set and an unlocked data set includes instructions operable to cause a programmable processor to assign data in the stored data set to a locked data set and an unlocked data set based on predetermined criteria.

50. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to define the stored data set to include a locked data set and an unlocked data set includes instructions operable to cause a programmable processor to include a restricted data set including data that is not part of the locked data set or the unlocked data set.

51. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to define the stored data set to include a locked data set and an unlocked data set includes instructions operable to cause a programmable processor to assign data to the locked data set based on a closeness criteria.

52. The computer program product of claim 51 , wherein the instructions operable to cause a programmable processor to assign data to the locked data set based on closeness criteria include instructions operable to cause a programmable processor to assign data to the locked data set based on at least one of geometric closeness, organizational closeness, and collective closeness.

53. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to define the stored data set to include a locked data set and an unlocked data set includes instructions operable to cause a programmable processor to assign data in the stored data set to the locked data set and the unlocked data set based on a function of the second entity.

54. The computer program product of claim 39, further comprising instructions operable to cause a programmable processor to: transmit data from the stored data set to the second entity; receive modified data from the second entity; and 5 integrate the modified data corresponding to the unlocked data set into the stored data set.

55. The computer program product of claim 39, wherein the instructions operable to cause a programmable processor to define the stored data set to include a locked data set and an unlocked data set includes instructions operable to cause a o programmable processor to define the stored data set to include a locked data set and an unlocked data set based on user input.

56. A computer program product, tangibly stored on a computer-readable medium, the computer program product comprising instructions operable to cause a programmable processor to: 5 define a master data set in a first entity; assign permissions, including permission to change data, to a subset of data within the master data set based on predetermined criteria; transmit a copy of the master data set with indications of the permissions to a second entity; and 0 receive changes of the master data set in accordance with the assigned permissions.

57. The computer program product of claim 56, further comprising instructions operable to cause a programmable processor to receive a modified copy of the master data set from the second entity and integrating the modified copy of the master 5 data set with the master data set.

58. The computer program product of claim 57, wherein the instructions operable to cause a programmable processor to receive the modified copy of the master data set includes instructions operable to cause a programmable processor to receive additional data. 0

59. The computer program product of claim 58, wherein the instructions operable to cause a programmable processor to receive additional data include instructions operable to cause a programmable processor to receive test results.

60. The computer program product of claim 57, wherein the instructions operable to cause a programmable processor to receive the modified copy of the master data set include instructions operable to cause a programmable processor to receive changed data.

61. The computer program product of claim 60, wherein the instructions operable to cause a programmable processor to receive changed data include instructions operable to cause a programmable processor to receive data that has been changed in response to testing.

62. The computer program product of claim 56, wherein the instructions operable to cause a programmable processor to assign permissions include instructions operable to cause a programmable processor to assign authority to read data.

63. The computer program product of claim 56, wherein the instructions operable to cause a programmable processor to assign permissions include instructions operable to cause a programmable processor to assign authority to change data.

64. The computer program product of claim 56, wherein the instructions operable to cause a programmable processor to assign permissions include instructions operable to cause a programmable processor to assign authority to add data.

65. The computer program product of claim 56, wherein the instructions operable to cause a programmable processor to assign permissions include instructions operable to cause a programmable processor to assign authority to delete data

66. The computer program product of claim 56, wherein the instructions operable to cause a programmable processor to assign permissions include instructions operable to cause a programmable processor to assign authority to access predetermined types of data within the subset.

67. The computer program product of claim 56, wherein the instructions operable to cause a programmable processor to assign permissions include instructions operable to cause a programmable processor to assign permissions based on at least one of entity, function of the entity and position within the entity.

68. The computer program product of claim 67, wherein the instructions operable to cause a programmable processor to assign permissions based on position within the entity include instructions operable to cause a programmable processor to assign permissions according to a hierarchy within a department so that a highest ranking member of a department has a greater number of permissions, and a number and extent of permissions decrease as rank decreases.

69. A computer program product, tangibly stored on a computer-readable medium, the computer program product comprising instructions operable to cause a programmable processor to: receive, from a first entity in a second entity, a copy of a master data set with permissions for using the master data set, the master data set including locked and unlocked data; modify the copy of the master data set according to the permissions; and transmit the modified copy of the master data set to the first entity.

70. The computer program product of claim 69, wherein the instructions operable to cause a programmable processor to receive the copy of the master data set in a second entity include instructions operable to cause a programmable processor to receive the copy of the master data set in a computer application.

71. The computer program product of claim 70, wherein the instructions operable to cause a programmable processor to receive the copy of the master data set in a computer application include instructions operable to cause a programmable processor to receive version information regarding the computer application in the locked data and raw data to manipulate in the unlocked data.

72. The computer program product of claim 70, wherein the instructions operable to cause a programmable processor to modify the copy of the master data set include instructions operable to cause a programmable processor to perform testing on the unlocked portion of the data.

73. The computer program product of claim 71, wherein the instructions operable to cause a programmable processor to receive the copy of the master data set with permissions for using the master data set include instructions operable to cause a programmable processor to receive permissions to do one or more of read, change, delete and add data to the unlocked data.

74. The computer program product of claim 69, wherein the instructions operable to cause a programmable processor to receive the copy of the master data set with permissions for using the master data set include instructions operable to cause a programmable processor to receive the copy of the master data set with permissions based on subsets of the unlocked data, with different permissions assigned for different subsets of the unlocked data.

75. The computer program product of claim 69, wherein the instructions operable to cause a programmable processor to receive the copy of the master data set with permissions for using the master data set include instructions operable to cause a programmable processor to receive the copy of the master data set with permissions based on at least one of the second entity, the function of the second entity and hierarchy of the second entity.