Nomadic data collection and management method including pessimistic locking of data

A method of managing a nomadic data system, wherein the nomadic data system comprises a central data repository and nomadic data devices, and wherein updating a data element associated with the central data repository by a nomadic data device, the method comprises:

• authorizing the nomadic data device to access a data element in the central data repository;
• checking out the data element to the authorized nomadic data device, while locking the data element to other nomadic data devices, wherein locking the data element prevents the other nomadic data devices from accessing the data element that has been checked out to the authorized nomadic data device;
• disconnecting the authorized nomadic data device from the central data repository to indicate to the other nomadic data devices that the authorized nomadic data device is locally working with the checked out data element at the authorized nomadic data device;
• collecting updated data for the data element from the authorized nomadic data device, wherein the updated data was generated at the authorized nomadic data device while the data element was locked out to the other nomadic data devices and while the authorized nomadic data device was disconnected from the central data repository;
• receiving a release check out signal from the authorized nomadic data device, wherein the release check out signal indicates that specific items of data are being checked back in to the central data repository without any changes;
• in response to receiving the release check out signal, sending a confirmation signal to the authorized nomadic data device, wherein the confirmation signal alerts the authorized nomadic data device that any changes made to the specific items of data while checked out to the authorized nomadic data device will be lost;
• checking the specific items of data back in to the central data repository in response to the authorized nomadic data device accepting the confirmation signal;
• creating a client definition;
• creating an engagement definition;
• creating an authorization profile;
• creating a group profile;
• creating a user entry and assigning the user entry to a specific group within a single engagement;
• checking out an access collection to a user that meets the client definition, the engagement definition, the authorization profile, and the group profile, while locking other users out of the access collection;
• and
• checking in an updated data file to the access collection, wherein the updated data file was generated at the authorized nomadic data device while the data element was locked out to the other nomadic data devices.