Central work-product management system for coordinated collaboration with remote users

A remote user collaborative data system interface for accessing a licensee-owner work-product data management central computer system, the interface comprising:

• providing, by a central processor, the central processor coupled to one to a plurality of remote user information device interface receivers and transmitters, remote access to licensee-owner selected, work-product data and work-product information, wherein the licensee-owner selected, work-product data and work-product information is associated with one to a plurality of user process ledgers modules (UPLM), wherein tasks are implemented by the one to a plurality of UPLMs, the implemented tasks including:
• implementing operating system type components, the operating system type components including:
• a data entry point member,
• an entry location of data,
• an association of components,
• a destination directory,
• a data server application procedures,
• implementing installed application services, the installed application services including:
• a central application component,
• a central data management application component,
• a interface application service,
• a interface device service,
• user selected references for selected applications including required support components needed for said selections,
• a retrieval application,
• a requirement for proper application processing,
• background information in areas of expertise of said UPLMs,
• background information in areas of expertise of remotely access application,
• a licensee-owner database structure,
• a database access application,
• a remote access information application,
• a user specific remote access application,
• implementing data store type components, the data store type components including:
• data storage in a relational database,
• data storage in a non-relational database,
• data storage in an ASCII text file having delimited or fixed length fields,
• iv. data downloaded into a text file from a network,
• v. data storage from a network by internet, main frame, local, or single computer data search, and retrieval,
• implementing text file components, the text file components including:
• a data file conversion component from an unsupported data management application or operating system,
• an ad hoc data file generation component with a text editor,
• a text file input/output operation component including a log file component,
• a data reading component for reading data from said selected data files, updating fields, adding new records,
• a data writing component for writing data back to text file for output generation,
• implementing database components, the database components including:
• a manage data binding component,
• adding and saving data to an underlying database, as a new record from a said UPLM specific data sets,
• an enabling data entry for record update,
• a rolling back at least one of said UPLM specific data sets or associated database on occurrence of associated process or system error events or decision to cancel process,
• a licensee-owner account database storage space selection,
• a database for items selected in separate application,
• one to a multiple specific information retrieval about data type retrieved from a database connection,
• implementing plug-in components, the plug-in components including:
• ActiveX controls,
• Java applets,
• any plug in technology, and
• a licensee-owner account interface, by a central processor, the central processor coupled to one to a plurality of remote user information device interface receivers and transmitters, which accesses the licensee-owner selected, work-product data management components and employs the remote user central interface connecting a remote user device to central licensee-owner data and data management applications, and is implemented by user option selection references, wherein the remote user central interface includes user process ledger modules (UPLMs),
• wherein the remote user central interface is limited to a specific hierarchy of input requests that are associated only to the specific needs of the individual client for data input, and
• wherein licensee-owner specified generation of the UPLMs encapsulates abilities, the abilities including;
• selecting licensee-owner defined database functionality based on data in underlying licensee-owner central system database, the databases including:
• implementing and generating queries,
• adding or modifying data connections, and
• generating fields and select field data types,
• selecting licensee-owner defined database tools, the tools including:
• building SQL statements that retrieve data or modify table data fields contents,
• generate grids or displays of database objects, representing data, data fields, tables and said data relationship %
• generate and modify database objects and append records to a table in a database,
• enter data in a network browser type page text field element and implementing licensee-owner defined code to append data to corresponding fields in licensee-owner database, and
• generate a data set as an underlying a data object to provide an intermediate, middle tier between licensee-owner database table and a network browser type page to change and update data displayed therein,
• selecting name objects, including use of a Universal Naming Code (UNC), for accessibility tea Web server,
• removing and adding a database project when disconnected from said licensee-owner database for off line systems
• selecting objects that establish said user option selection references,
• selecting objects that establish connections to said user remote interface devices,
• adding a selection element to said UPLM specifying items to be presented in said selection element,
• adding code to said UPLM load event procedure,
• adding a procedure to present a processing parameter,
• adding a procedure to present input or output said user option selection references,
• generating a dynamic link library for said UPLM,
• generating a network browser type page for said UPLM,
• generating a selection element of database objects on an Hypertext Markup Language (HTML) template page, including a selection list, binding said HTML template page dements to said database,
• generating a dialog box element specifying said data object name, said database connection, and data source,
• selecting a network browser type page application components as objects, the objects including:
• Graphic User Interface (GUI) configuration forms,
• UPLM templates,
• Hypertext Markup Language (HTML)
• document objects formatted for Web documents, and
• document objects providing hypertext linking between documents, including;
• drawings, pictures, sound, and multimedia content,
• documents referring to other documents by resource location including:
• Internet's Uniform Resource Locator (URL), and
• links pointing to other sections in different documents, on the same document, or different servers at different locations on different platforms,
• selecting a remote device, associated device central system interface, and associated UPLM user interface presentation format for said user option selection references specific to each user, and
• selecting central system applications providing required data access drivers for said central system applications interfacing with licensee-owner configured UPLM
• wherein the generation of said UPLMs can be achieved by either or both central system programmer or by licensee-owner designation of user option selection references within a UPLM component selection template resulting in the user not having to relearn the business or application model during each use or for access;
• and
• wherein the licensee-owner specified generation of said UPLMs includes licensee-owner designated work-product interactive interface components, the components including:
• a licensee-owner designated data selection list,
• a licensee-owner designated information collection means,
• a licensee-owner designated document generation means,
• a licensee-owner designated fill in work-product data gathering page placing said data or information into including;
• tables, display grid, data cells,
• a page providing a search engine interface letting said users search limited licensee-owner designated data,
• a page with licensee-owner designated references to licensee-owner data source objects supplying data, the data being supplied to other objects including:
• a delimited text tile,
• a Web page,
• a temporary data store object,
• a text document,
• a data consuming application,
• a user remote interface display,
• a user remote device,
• a user remote device for caching data sectors to be read offline,
• a server object written to dump user data, and
• a Data URL property to specifying a data set,
• a custom licensee-owner designated data provider object generated from licensee-owner central application objects,
• said licensee-owner designated data provider object as a reusable transaction object with roll-back abilities,
• an independent software vendors licensee-owner designated user interface,
• a service object that obtains user data from licensee-owner designated data source object using existing database management system providing including:
• licensee-owner designated SQL statements, and
• update, insert, and delete capabilities for licensee-owner designated access to said licensee-owner data source work-product object,
• a H323 or similar standard based voice and video conferencing collaborations tool,
• a multipoint licensee-owner designated data conference using T119 data conferencing or similar standards including:
• clipboard operations
• file transfer,
• whiteboard review,
• ability to update information and data,
• chat using text messages, and
• TAPI computer telephony integration,
• a speech service by internet connection or any voice-over-IP type application employing a telephone device using speech to listen to including;
• licensee-owner designated database items
• licensee-owner designated text to speech converted data, and
• licensee-owner designated prerecorded audio files,
• licensee-owner designated data field HTML elements,
• licensee-owner designated programming variable objects referencing procedures including;
• user input variables,
• licensee-owner designated remote access application,
• user remote interface device applications,
• output generation applications, and
• programming variable objects referencing database objects and components, and
• said user option selection references processing including;
• receiving and transmitting means,
• an intermediate file system for extracting said selected ledger output
• a message transmission
• a means for responsive to receipt of said UPLM user option selection,
• menu driven selection descriptors,
• user identifiers,
• unique mapping identifiers,
• user data input mapping,
• licensee-owner designated data output format Ides, documents or databases,
• voice files of international dialects output type requested format files,
• scanned images,
• licensee-owner designated workflow automation systems,
• licensee-owner designated output alerts,
• licensee-owner designated electronic document central management system EDCMS, user data applications, including interactive voice dictation applications, for frequently referenced database locations
• user data applications, including interactive voice dictation applications, for frequently referenced database locations,
• procedures that after call roll back to original database state if communication is disconnected,
• accounting and financial management related application components,
• quantitative method analysis for business decisions related application components, tracking, scheduling, and document storage related applications,
• tracking, scheduling, and document storage related applications, information services related application components,
• remote data device information storage application components, and
• remote data device communications systems application components, whereby interactive UPLMs can offer use˜a limited selection of specific licensee-owner designated central system work-product application functions designated for that specific remote user.

A system of one to a plurality of detection and communication devices coupled to a central processing system for collaborative accessing and transferring of digital data segments, the one to a plurality of detection and communication devices including

• remote user devices, wherein each remote user device comprises:
• an associated central processing system device interface, the interface capable of at least one of receiving and transmitting for transmitting and receiving remote user communications, and an interface providing, by a central processor, the central processor coupled to one to a plurality of remote user information device interface receivers and transmitters, remote access to licensee-owner selected, work-product data and work-product information, wherein the licensee-owner selected, work-product data and work-product information is associated with one to a plurality of user process ledgers modules (UPLM), wherein tasks are implemented by the one to a plurality of UPLMs, the implemented tasks including,
• implementing operating system type components, the components including:
• a data entry point member,
• an entry location of data,
• an association of components,
• a destination directory,
• a data server application procedures,
• implementing installed application services, the application services including:
• a central application component,
• a central data management application component,
• a interface application service,
• a interface device service,
• user selected references for selected applications including required support components needed for said selections,
• a retrieval application,
• a requirement for proper application processing,
• background information in areas of expertise of said UPLMs,
• background information in areas of expertise of remotely access application,
• a licensee-owner database structure,
• a database access application,
• a remote access information application,
• a user specific remote access application,
• implementing data store type components, the data store type components including:
• data storage in a relational database,
• data storage in a non-relational database,
• data storage in an ASCII text file having delimited or fixed length fields,
• data downloaded into a text file from a network,
• data storage from a network by internet, main frame, local, or single computer data search, and retrieval,
• implementing text file components, the text file components including:
• a data file conversion component from an unsupported data management application or operating system,
• an ad hoc data file generation component with a text editor,
• a text file input or output operation component including a log file component,
• a data reading component for reading data from said selected data files, updating fields, adding new records,
• a data writing component for writing data back to text file for output generation,
• implementing database components, the database components including:
• a manage data binding component,
• adding and saving data to an underlying database, as a new record from a said UPLM specific data sets,
• an enabling data entry for record update,
• a rolling back at least one of said UPLM specific data sets or associated database on occurrence of associated process or system error events or decision to cancel process,
• a licensee-owner account database storage space selection,
• a database for items selected in separate application,
• one to a multiple specific information retrieval about data type retrieved from a database connection,
• implementing plug-in components, the plug-in components including:
• ActiveX controls,
• Java applets,
• any plug in technology, and
• wherein the interface is limited to a specific hierarchy of input requests that are associated only to the specific needs of the individual client for data input, and
• wherein licensee-owner specified generation of the UPLMs encapsulates abilities, the abilities including;
• selecting licensee-owner defined database functionality based on data in underlying licensee-owner central system database, the databases including:
• implementing and generating queries,
• adding or modifying data connections, and
• generating fields and select field data types,
• selecting licensee-owner defined database tools, the tools including:
• building SQL statements that retrieve data or modify table data fields contents,
• generate grids or displays of database objects, representing data, data fields, tables and said data relationship %
• generate and modify database objects and append records to a table in a database,
• enter data in a network browser type page text field element and implementing licensee-owner defined code to append data to corresponding fields in licensee-owner database, and
• generate a data set as an underlying a data object to provide an intermediate, middle tier between licensee-owner database table and a network browser type page to change and update data displayed therein,
• selecting name objects, including use of a Universal Naming Code (UNC), for accessibility tea Web server,
• removing and adding a database project when disconnected from said licensee-owner database for off line systems
• selecting objects that establish said user option selection references,
• selecting objects that establish connections to said user remote interface devices,
• adding a selection element to said UPLM specifying items to be presented in said selection element,
• adding code to said UPLM load event procedure,
• adding a procedure to present a processing parameter,
• adding a procedure to present input or output said user option selection references,
• generating a dynamic link library for said UPLM,
• generating a network browser type page for said UPLM,
• generating a selection element of database objects on an Hypertext Markup Language (HTML) template page, including a selection list, binding said HTML template page dements to said database,
• generating a dialog box element specifying said data object name,
• said database connection, and data source,
• selecting a network browser type page application components as objects, the objects including:
• Graphic User Interface (GUI) configuration forms,
• UPLM templates,
• Hypertext Markup Language (HTML)
• document objects formatted for Web documents, and
• document objects providing hypertext linking between documents, including;
• drawings, pictures, sound, and multimedia content,
• documents referring to other documents by resource location including:
• Internet's Uniform Resource Locator (URL), and links pointing to other sections in different documents, on the same document, or different servers at different locations on different platforms,
• selecting a remote device, associated device central system interface, and associated UPLM user interface presentation format for said user option selection references specific to each user, and selecting central system applications providing required data access drivers for said central system applications interfacing with licensee-owner configured UPLM, and
• a central processing system, wherein the central processing system comprises:
• licensee-owner work-product designated central application components presenting remote user option selections and responding to remote user options selection requests for at least one of:
• data input, or
• verification information output associated with licensee-owner central data source account structure,
• centralized data management system of the licensee-owner work-product information in said licensee-owner central account, accessible by user process ledgers module (UPLM) processing instructions,
• central non-transitory computer storage mediums for digitally storing user process ledgers modules (UPLM), remote user accessed licensee-owner work-product information, central data management applications, and the licensee-owner work-product designated central application,
• wherein the UPLM specifications are selected from UPLM configuration templates (UPLM CT),
• wherein the UPLM CTs are generated by a localization tool, the generation of the UPM CTs includes:
• binding data in a grouping hierarchy data set to a set of controls on a form,
• binding data in a relation hierarchy data set to a set of controls on a form,
• configuring a collection of file templates that export reports in at least one of a plurality of data formats, and
• passing data from an application or object to another application or object,
• wherein the UPLM CT is at least on of a plurality of layouts containing objects,
• wherein the localization tool:
• tracks any additions, changes, or deletions of UPLMs, accesses selection of directories of native language voice filed which are used for UPLM implementation,
• stores alert and error messages containing replacement parameters of text and character sets.