WO2002010969A2

WO2002010969A2 - System and method for workflow data management

Info

Publication number: WO2002010969A2
Application number: PCT/US2001/023743
Authority: WO
Inventors: Peter H. Au; Isabella James P. Ellis; James Patrick Block
Original assignee: Netune Communications, Inc.
Priority date: 2000-07-28
Filing date: 2001-07-27
Publication date: 2002-02-07
Also published as: AU2001278054A1

Description

SYSTEM AND METHOD FOR WORKFLOW DATA MANAGEMENT

Field of the Invention This invention relates generally to a data management system and methodology and, more particularly, to an automated data management system for networking and interconnecting disparate data into a comprehensive workflow management system.

Background of the Invention Many businesses today, including the motion picture and television production practice, do not offer any acceptable system for automated workflow procedures. Most businesses are mainly driven by paper transfers, couriers, and individual custom solutions using generic off-the- shelf applications such as Microsoft Word and Excel. For example, current practice in motion picture and television production involves non-standard and non-uniform methods of collecting and entering data that are used to track all aspects of the production process. Data is most often entered and saved in paper form that is then collected, stored and archived at the end of the production. Different units of the production manage their information separately in a non- cohesive and non-standard manner. Currently, there is no method that manages all aspects of production in an integrated and cohesive, automated system.

Prior to the advent of digital technologies, fihnmaking was a very linear process. Filmmaking was a photochemical, mechanical, analog process, that had to be sequential. A first task had to be completed before a second task begun. In order to compress a schedule, only a part of that process could be compressed, sometimes at the expense of another aspect. However, the digital world now allows for multi-tasking. Live action components of an effect can be shot at one location, while CGI (computer-generated images) are created simultaneously in a facility located elsewhere. Thus, physically separate events can now be produced "in parallel" (multi- tasked) rather than sequentially.

The programs that are in the market today for budgeting, accounting, scheduling, information reporting, and the like are all designed as stand alone items that are incapable of sufficient networking and/or interconnectivity. For example, current budgeting software does not provide satisfactory integration with accounting or scheduling programs. Unfortunately, in reality, deviations in budgeting and/or scheduling often do affect and interact with accounting concerns, and vice versa. There is a continuing need for greater interconnectivity and networking in information and data management. Currently, not only is the collection and storage of this data done manually via paper, the data is also being stored in isolation. Consequently, the sharing of this information and data is not an automated process. There is no database or data repository, either centrally or locally, that individual users and departments can access. It is with respect to these considerations and others that the present invention has been made. Accordingly, those skilled in the art have long recognized the need for a data management system which provides for the collection, dissemination, and manipulation of data, by any number of users, in a quick, efficient, and secure manner without regard to either the location of the data and without regard to time constraints.

Summary of the Invention Briefly and in general terms, the present invention resolves the above and other problems by providing an integrated information and data management system that serves to collect and link disparate data, eliminate redundant data entry and distribute data with intelligence across the system to the proper locations and/or users.

More particularly, a preferred embodiment information and data management computer system for integrated information and data management includes a plurality of data collection nodes in a meshed network each including at least one computing station, and a transmission/reception medium. Preferably, at least one data collection node is defined as a primary data collection node that facilities data synchronization. The collection nodes links disparate data and validates data upon entry into the system against pre-defined criteria or previously entered data. Further, the collection nodes notifies appropriate users of any data discrepancies, as well as intelligently sorts, filters, and initiates dissemination of data using logical structures. In the collection nodes, data is input into the computing stations and transmitted to other collection nodes. The data is input and reviewed by a relevant specialists, thereby reducing errors and redundant data entry. The transmission/reception medium is configured to transfer information between the collection nodes using a data transfer protocol. This information transfer includes collecting disparate data and selectively disseminating data across the system to users at computing stations according to user identification, hardware identification, data clearance level, and data release authority.

In accordance with other aspects, the present invention relates to a data management system that maintains a given reporting structure while the collection nodes link together related data, thereby intelligently automating data reporting to the computing stations. The collection nodes receives data in incoming reports from the computing stations which is sorted and analyzed to create distinct outgoing reports that are transmitted to predetermined computing stations. Each report in the collection nodes dynamically builds dependencies to other reports according to predefined criteria.

In accordance with still other aspects, the present invention relates to a data management system that presents data in an individualized template format to each specific user in the computing stations. Only data and functions relevant to a specific user are presented to that user when the user logs onto a computing station of the system. Preferably, the system protects sensitive data by making the data visible only to a user with an authorized access level, and wherein there is no indication to users without the proper access level that data is being withheld. Further, some types of data are locked and unavailable to all but authorized users until the data is released by an authorized user.

In accordance with other aspects, the present invention relates to a data management system that prompts the collection nodes, whenever a change is made to data in the system, to intelligently scan all remaining data in order to determine if any remaining data is affected by the change. Further, users receiving data that was subject to a change are notified of the change and any possible associated problems resulting from the change. Moreover, linkages between different sets of data within the system are customizable, thus providing automatic updating when a change occurs to one or more data elements in the system. In one preferred embodiment of the present invention, the data managed by the system is selected from a group consisting of, by way of example only, information, text, voice, audio, video, images, and their digital counterparts. Preferably, the system predicts probable outcomes and monitors events for variances using data compilation analysis.

In accordance with still other aspects, the present invention preferably relates to a data management system that tracks physical assets, and correlates and tracks physical assets to other derivative forms of the physical assets. In one preferred embodiment of the present invention, groupings of data and supersets of data are customizable through assignment of custom rule sets.

In accordance with other aspects, the present invention relates to a data management system in which the data managed by the system is selected from a group consisting of film and television production, pre-production, and post-production data. In other embodiments of the present invention, the data managed by the system is selected from a group consisting of medical related data, tele-medicine, oil and gas exploration, international construction, disaster relief, and distance learning/education. Preferably, the system utilizes a browser based interface with the computing stations for standardization across platforms. A preferred embodiment data management system includes broadband satellite links for transmitting text, data, and still and moving images at high-definition and standard definition resolutions. In this regard, the transmission/reception medium of the data management system is preferably a satellite or transmission subsystem incorporating one or more satellites. In some embodiments of the present invention, however, the transmission/reception medium is selected from a group consisting of, by way of example only, fiber optic cables, modems, cable modems, cable routers, digital subscriber lines (DSL), asymmetrical digital subscriber lines (ADSL), Tl (or fractions thereof), T2 (or fractions thereof), T3 (or fractions thereof), local area networks (LAN), wide area networks (WAN), microwave networks, line-of-sight laser, and the Internet, either in addition to or in place of a satellite system.

In one preferred embodiment, the data management system of the present invention creates an automated system for managing information generated before, during, and after the television and film production process, and provides a method for interconnecting the production data into a comprehensive workflow data management system. The present invention automates the process of creating, managing, and tracking production data through the entire process of pre- production, production, and post-production. In one preferred embodiment, by way of example only, data consists of information regarding: script, editors notes, budgeting, accounting, scheduling, daily progress reporting, camera information, sound information, video assist data, time card information, visual effects data, lab data, telecine, dailies and dailies data, and the like.

Preferably, the present invention provides shared and controller access to all data accumulated by current and "in process" productions. The method of controlling the access is achieved by presenting unique views of data based on role, function, authority level, and need of user. The present invention manages a collection nodes that are synchronized with each other in remote locations. Preferably, the individual departments input their data locally and the data is systematically updated to a primary collection node. Once the data is in the primary collection node, the data is accessible by any user with the proper access privileges. Preferably, some data is global while other data has specific access permission rules attached to it. Permission rule sets and data access are capable of being generally defined on a "per production" basis. Using a browser based interface for standardization across platforms, departmental data is input by a user and stored in the collection nodes. Since the data is in a repository of at least one node, the data is extractable by all branches of production that need and are allowed access to the data in an automated fashion that increases efficiency and accuracy. The business of film production is disparate in nature, with information and data tending to be spread over a wide geographical area and residing in multiple locations. The present invention preferably allows for near instant retrieval of such information and data. Through methods of time stamping and synchronization, the present invention prevents the loss and unnecessary duplication of data as well as flagging potential discrepancies in data from multiple input sources. A preferred embodiment of the present invention predicts normal projections and flags variances from expected results through the continual tracking of production information. This allows for early detection of anomalies. Where more than one department tracks the same information, the information is preferably collated and compared before publication of the various reports in which the information is included. Individual users are notified of discrepancies and given the chance to correct errors before the publishing of any relevant reports, thereby maximizing efficiency and reducing costly errors. The present invention utilizes local nodes of the individual departments and preferably synchronizes them with a primary collection node. Users input job-specific information locally and the present invention then disseminates information automatically to the proper people and places. One preferred embodiment of the present invention provides the unique ability to distribute voice, video, graphics, text, and images on one unified, seamlessly integrated, network infrastructure. This embodiment of the present invention is directed towards a novel converged digital network that preferably utilizes geo-stationary satellites. The type of data exchanged with other people is adjustably selectable. Real-time collaboration or annotations are contemplated, as well as transmission to other recipients for viewing at a later time.

A preferred embodiment of the present invention provides a turn-key solution incorporating software and broadband satellite links for distributing still and moving images, along with text, such as production and cost reports, accessed through data management software operated via an easy-to-use Web browser. The present invention transmits information and data on demand at either high-definition or standard definition resolutions, and with full interactivity capabilities. Preferably, the present invention utilizes a standard web browser graphical user interface (GUI) in order to maximize productivity and efficiency, however, custom web browsers may also be used. Further, the present invention provides users with accessible and easy to use communications services.

Traditionally, satellites have been very complicated, user-unfriendly, arcane infrastructures requiring highly specialized knowledge. However, the data network infrastructure of the present invention utilizes redesigned user-friendly satellite distribution technology, while also preferably interfacing with existing terrestrial fiber (or non-fiber) networks. The present invention is capable of managing and transmitting all types of data including digital film dailies, computer generated images (CGI) images, edited sequences, payroll or production management data. One desirable benefit of the present invention; is that it facilitates the collaboration of business efforts. In the film production embodiment, everything in pre-production, production, and post-production is interconnected and interdependent. Moreover, the present invention is applicable to the communications business at large, including the world wide web, network infrastructures, TCP/IP -type protocol, and multimedia data sharing. In accordance with still other aspects, the present invention relates to a process for networked data management that gathers disparate data, reduces redundant data entry, and efficiently disseminates data. The process includes collecting data from a plurality of computing stations in a network and storing the data in another computing station in the network, validating data upon entry into the network against pre-defined criteria or previously entered data, checking the data entered from different computing stations in the network for discrepancies and notifying appropriate users at their computing stations in the network of such events, intelligently sorting, filtering, and linking data in accordance with logical structures, and distributing data and derivatives of the data across the network to computing stations and users according to preselected criteria. In a preferred process, the pre-selected criteria for distributing data and derivatives of the data across the network to computing stations and users is selected from a group consisting of user identification, hardware identification, data clearance level, and data release authority.

The present invention may be implemented as a computer process, a computing system, or as an article of manufacture such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoded with a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoded with a computer program of instructions for executing a computer process.

In accordance with yet other aspects, the present invention relates to a computer program product readable by a computing system and encoded with a computer program of instructions for executing a computer process for an interconnected data management system. The computer program product executes a computer process that includes collecting data from at least one location in a network and storing the data in another location in the network, validating data upon entry into the network against pre-defined criteria or previously entered data, checking data entered from different locations in the network for discrepancies and notifying appropriate users at locations in the network, intelligently sorting, filtering, and linking data in accordance with logical structures, and distributing data or its derivatives across the network to predetermined locations and users according to pre-selected criteria. In a computer program product executing a preferred computer process, the pre-selected criteria for distributing data and derivatives of the data across the network to computing stations and users is selected from a group consisting of user identification, hardware identification, data clearance level, and data release authority.

Other features and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate by way of example, the features of the present invention.

Brief Description of the Drawings FIGURE 1 illustrates a relational diagram of a general purpose computer system for implementing one embodiment of the present invention;

FIGURE 2 illustrates a relational flow of a collection node, script, script breakdown, schedule, call sheets, script supervisor report, camera report, sound report, VTR (video assist) report, flex file, accounting, purchase orders, daily report, production report, dailies and visual effects in accordance with the present invention;

FIGURE 3 illustrates another relational data flow between a script, script breakdown, scheduling, budgeting, production report, financial/accounting report, production list, vendor list, real time database, historical database, and daily payroll as practiced in one embodiment of the present invention; FIGURE 4 illustrates an exemplary relational data flow from a script daily report, a camera report, a sound report, a schedule, a script breakdown, department out times, and actors out times to a collection node, and from the collection node to create a production report as shown in FIGURE 3, and in turn to produce cost reports in accordance with the present invention;

FIGURE 5 illustrates an exemplary operational matrix containing rule sets governing a user's accessibility to specific data in practicing one embodiment of the present invention;

FIGURE 6 illustrates an exemplary sample of annotated video clip data for use in collaborative viewing in practicing the present invention;

FIGURE 7 illustrates a perspective view of the hardware in an exemplary embodiment of the present invention which includes a satellite that links a visual effects facility, a post- production facility, a studio, an operations center, and multiple remote locations; and

FIGURE 8 illustrates a close-up view of the hardware in an exemplary embodiment of the present invention specifically focusing on the remote locations network interface, which includes an automatic antenna system, a mobile satellite gateway, and associated devices in a meshed network interface.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention relates to a data management system for providing an efficient system and method for collecting, disseminating, and manipulating data by any number of users, in a quick, secure, and efficient manner without regard to location and time constraints. Referring now to the drawings, wherein like reference numerals denote like or corresponding parts throughout the drawings, and more particularly to FIGURES 1-3, there is shown one embodiment of an integrated information and data management system 10 constructed in accordance with the present invention that serves to collect and link disparate data, reduce redundant data entry, and intelligently distribute data across the system 10 to any number of proper locations and/or users. Referring now to FIGURES 2-4, a preferred embodiment of the present invention validates data upon entry into the management system 10 against pre-defined criteria or previously entered data, identifies discrepancies in the data, and notifies the appropriate users of such discrepancies. A preferred embodiment also includes logical structures to intelligently sort, filter, and disseminate data. Furthermore, information entered from different sources is collected, validated, checked for discrepancies, and routed to the appropriate destinations which may receive this data in various other forms, such as stand-alone reports. A preferred embodiment data management system 10 eliminates redundant entries by allowing the data to be input and reviewed by specialists, thus, reducing the chance of errors. Further, the automation of the management system 10 speeds the process of disseminating information and increases efficiency. A preferred embodiment of the management system 10 keeps a given reporting structure intact and adds intelligent automation to the reporting process. The management system 10 pulls information from concurrent reports to create new unique reports. Each report in the management system 10 dynamically builds dependencies to other reports according to predefined criteria. Preferably, the standard format of the report is not changed, but the data within the report changes according to its dependencies on other reports in the system 10.

Preferably, the management system 10 presents a template or "view" specific to each user and his function. When the user logs onto the management system 10, only the information and functions relevant to that user are presented. This provides a secure method of protecting sensitive material since that material is only visible to a user with the proper access level. Further, in some preferred embodiments, certain material is considered "locked" and unavailable to other users until the material is released by a user with the proper authority. In this event, there is no indication on the display screen of material that a specific user cannot access.

When global changes are made to data, a preferred embodiment of the present invention intelligently scans all other data that might be affected by such changes and notifies the appropriate users of the changes and possible problems. Moreover, a preferred embodiment allows users to customize linkages between different sets of data for automatic updating when a change occurs to one or more data elements that are in the system 10. The data that the present invention is capable of managing covers a wide range of areas, including but not limited to, information, text, voice, audio, video, images, and their digital counterparts. These different types of data are linkable together to create larger data structures that are also manageable, in turn, by the system 10.

Through data compilation, a preferred embodiment data management system 10 of the present invention predicts probable outcomes and monitors events for variances. Preferably, physical assets are tracked and auto-correlated. Further, assets are also tracked to other forms of the physical asset, such as digital media. A preferred embodiment data management system 10 allows custom groupings of data and supersets of data (which are comprised of smaller data elements) that are assigned custom rule sets.

As shown in FIGURE 5, in a preferred aspect of a data management system 10 of the present invention, access into the system 10 is controlled via an access control matrix 320. Each user identification and password combination is assigned to an access level within the matrix 320. Access level gives users a template that specifies access to each data group within the system 10. After this initial template assignment, the system 10 further customizes access to each data group individually for each user. Data access is further controlled via aging, publishing, and sequential controls. Utilizing aging control, a specified user has access to data in a time dependant manner. Thereafter, access may be granted with or without restriction. Utilizing publishing control, one or more users must review the data and decide to publish the data before the data is released to other users. Utilizing, sequential control, users with access to a data group are further assigned into access layers. Users of a higher layer must review the data before users of a lower layer may view the same data. The hierarchy of this control is dependent on the number of layers assigned.

As shown in FIGURE 6, in another preferred aspect of a data management system 10, the present invention, has the capability to add audio and visual annotations to selected frames during image sequence playback for collaborative viewing 330. These annotations include both graphical annotations 340 (e.g., circling, marking, arrows, etc.) and textual annotations 350 (e.g., "Look, the boom is in the frame."). Preferably, these annotations are stored for display during subsequent collaborative viewings 330. However, real time collaboration capability is also possible. In accordance with the present invention, a session controller manages multiple viewing environments and coordinates messages between the various viewers within the session. A viewer establishes a link to the session controller to pass and receive control and annotation data to and from the session controller. The session controller, in turn, relays the data to other viewers in the session. This gives the users the ability to communicate regarding the same image and observe each other's actions. The system 10 also has the ability to further enhance the communication capability by providing video teleconferencing "on demand" along with the collaboration session. Referring again to FIGURES 2-4, a preferred embodiment information and data management system 10, in accordance with the present invention, greatly enhances working efficiency by interconnecting the vast flow of data that currently creates substantial amounts of paperwork. Information is input into the management system 10 from a plurality of locations. The data is collected, linked, and intelligently distributed across the system 10 to various locations and/or users. A preferred embodiment management system 10 connects users at various locations via a private network that provides a high level of security. However, any other communication system with appropriate security may also be used. Preferably, the management system 10 utilizes individual or departmental specific templates or "views" that incorporate personalized information and functions. When each user logs on, their screen is personalized with user specific pertinent information. Each user sees and/or is capable of manipulating only the data that pertains to their position. Any material to which they are not permitted access is invisible to them rather than being "greyed out" (viewable as being inaccessible). In this way, the user is not aware of being denied access to various functions. Preferably, each user on the management system 10 has their own identification and password. Users are then capable of loading specific data into the management system 10. Referring again to FIGURES 1 and 2, the following discussion is intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While preferably the invention runs at least in part on an operating system in conjunction with one or more personal computers (as well as collection nodes^As94and a transmission medium), those skilled in the art will recognize that the invention also may be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, and the like. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices (such as Personal Digital Assistants (PDAs)), multiprocessor systems, microprocessor-based or programmable consumer electronic devices, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Referring particularly to FIG. 1, an exemplary system 10 for implementing the present invention includes a conventional personal computer 20, including a processing unit 21, a system memory 22, and a system bus 23 that couples the system memory to the processing unit 21. The system memory 22 includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines which assist the transfer of information between elements within the personal computer 20, such as during startup, is stored in the ROM 24. A personal computer 20 preferably further includes a hard disk 27, a magnetic disk drive 28, e.g., to read from or write to a removable disk 29, and an optical disk device 30, e.g., for reading a CD-ROM disk 31 or to read from or write to other optical media. Preferably, the hard disk 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively. The drives and their associated computer-readable media provide non-volatile storage for the personal computer 20. Although the description of computer-readable media above refers to a hard disk, a removable magnetic disk and a CD-ROM disk, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, and the like, may also be used in an exemplary operating environment.

A number of program modules may be stored in the drives and RAM 25, including an operating system 35, one or more application programs 36, other program modules, such as an installer program in accordance with an exemplary embodiment of the present invention, and program data, such as a configuration database associated with the installer program. The operating system 35 may include a system registry 39. In this embodiment, the invention may reside within the installer program and the configuration database. A user may enter commands and information into the personal computer 20 through a keyboard 40 and pointing device, such as a mouse 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like.

These and other input devices are often connected to the processing unit 21 through a serial port interface that is coupled to the system bus, but may not be connected by other interfaces, such as a game port or a universal serial bus (USB). A monitor or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor, personal computers typically include other peripheral devices (not shown), such as speakers or printers.

The personal computer 20 preferably operates in a networked environment using logical connections to one or more remote computers, such as remote computer 49. In addition, the computer 20 is also connected to a collection node 94 via a transmission/receiver medium. The remote computer 49 may be a server, a router, a peer device, or other common network node, and typically includes many or all of the elements described relative to a personal computer 20, such as a memory storage device 50. The logical connections described may include a local area network (LAN) 51 and a wide are network (WAN) 52. Such networking environments are commonplace in offices, enterprise- ide computer networks, intranets, and the Internet.

When used in a LAN networking environment, a personal computer 20 is preferably connected to the LAN 51 (or a wireless LAN) through a network interface 53. When used in a WAN networking environment, a personal computer 20 typically includes a modem 54 or other connection interface for establishing communications over the WAN 52 (or a wireless WAN), such as the Internet. A modem 54, which may be internal or external, is connected to the system bus 23 via the port interface 46 (including, but not limited to serial, USB, or other interface). In a networked environment, program modules depicted relative to a personal computer 20, or portions thereof, may be stored in a remote memory storage device 50. It will be appreciated that the network connections shown are exemplary and other devices that establish a communications link between the computers or other system components may also be used.

A computing data management device, such as the computing data management system 10, typically includes at least some form of computer-readable media. Computer readable media can be any available media that can be accessed by the computing system. By way of example, and not by limitation, computer-readable media might comprise computer storage media and communication media.

Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the computing data management system 10.

Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example , and not by limitation, communication media includes wired media such as a wired network or direct- wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media. Computer-readable media may also be referred to as computer program product.

Referring again to FIGURES 2-4, in one exemplary embodiment, the present invention is a completely integrated data management system 10 that is specifically tailored for use with film and television production. The following description gives specific detail of this particular embodiment, by way of example only, and not by way of limitation. It will be appreciated by those skilled in the art that the information and data management system 10 of the present invention is readily applicable to many other areas of practice outside of film and television production.

FIGURE 7 illustrates an overview of the hardware in an exemplary, non-limiting, data management system 10 which includes a transmission/reception medium, such as a satellite 60 (or satellite network), that links a various network sub-systems, including a visual effects facility 62, a post-production facility 64, a studio 66, an operations center 68, and multiple remote locations 70 and 74. In this exemplary system, the remote locations 70 and 74 network interface with the satellite 60 via automatic antenna systems 71 and 75 and mobile satellite gateways 72 and 76. Further, in this exemplary system, the visual effects facility 62, studio 66, and operations center 68 are also connected to one another by a terrestrial global fiber network 69. Thus, one preferred embodiment data management system 10 utilizes satellite transmissions, terrestrial fiber connections, and local and/or wide area wireless transmissions in a meshed network interface. It will be appreciated by those skilled in the art that the system 10 of the present invention may also utilize more, less, or different system 10 sub-systems which may or may not be redundantly connected with satellite transmissions and terrestrial fiber connections.

FIGURE 8 illustrates a close-up view of the hardware in an exemplary, non-limiting, system 10 specifically focusing on the remote locations 70 and 74 network interface, which includes an automatic antenna system 71 and 75, a mobile satellite gateway 72 and 76, and associated devices portion of the meshed network interface. In this exemplary, non-limiting, remote locations 72 and 76 network interface, a production office 80 (which preferably includes at least a digital dailies viewing station 81, a production office station 82, and an editing station 83) is connected to a mobile set/location 85 (which preferably includes at least a production manager station 86, a first assistant director station 87, and a production coordinator station 88) via a wireless local area network 90 with integrated IP telephony 92. Additionally, this remote location production office 80 and mobile set/location 85 are connected to the automatic antenna system 71 or 75 and thus, the remainder of the system 10 via a mobile satellite - gateway 72 or 76. It will be appreciated by those skilled in the art that the system 10 of the present invention may also utilize more, less, or different associated devices.

The logical operations of the various embodiments of the present invention are implemented (1) as a sequence of computer implemented steps or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, the logical operations making up the embodiments of the present invention described herein are referred to variously as operations, structural devices, acts or modules. It will be recognized by one skilled in the art that these operations, structural devices, acts and modules may be implemented in the management system 10, in firmware, in special purpose logic, analog circuitry, or any combination thereof without deviating from the spirit and scope of the present invention as recited within the claims attached hereto. Examples of possible departments and/or users that will input and/or access data from the film and television production embodiment of the data management system 10 of the present invention are described below. A preferred flow of information to and from these reports (or operational areas) in the data management system 10 is shown in FIGURE 2. Although data from one operational area in the data management system 10 can affect many other operational areas, the general dependency hierarchy of one preferred embodiment is as follows: From the script 100 the script breakdowns 110 are created. From the script breakdowns 110 the schedule 120 is created. From the schedule 120 the call sheet 130 is created. From the call sheet 130 the production report 220 is started, (with additional information from the script 100, camera report 150, and sound reports 160, and gathered department "out times 290" and actor "out times 300" on every member of the production). Finally, from the production report 220 the cost reports 310 are created. Referring now to FIGURES 2 and 3, in this embodiment of the present invention, the script 100 serves as a central linkage in the data management system 10, since all of the data relates to the script 100. In pre-production, the script 100 is approved and imported into the data management system 10. The data management system 10 then searches the script 100 and populates collection nodes^Λs94with specific scene information. The data management system 10 of the present invention enhances automated completion. In the present invention, however, the management system 10 automates this process. Since the format of a script 100 is standard, the data management system 10 reads the scene number first (which is the basic unit of reference).

There is a capitalized line that is called a slug line. From this, the data management system 10 gets the following information: Int/Ext, Set, Day/Night. The data management system 10 then scans the scene, line by line. If there is no indentation, then the scene is read as a description block. The character names are capitalized and indented to head the dialogue portions, so the data management system 10 can input the characters in the scene by capturing this text. It should be noted that some props tend to be capitalized in the description area of the scene; however, the first introduction of the character in that scene is capitalized. Thus, the data management system 10 also checks if the capitalized word is a noun if the word doesn't match a character in the collection node^Λs94. If the word is a noun and not a character, the word is input as a prop. Further, the data management system 10 breaks the scenes into 1/8's of pages.

General script breakdowns 110 of each scene are created and stored in the collection nodes^Λs94. This information is then manipulatable into specific reports that are accessible by appropriate departments and/or users. Without the data management system 10, when a department breaks down the script 100, they often highlight the objects in the script 100 that are pertinent to their area. In the data management system 10 of the present invention, a user views the script 100, chooses which script breakdown 110 they are creating, and then selects on any words that they want to include in the script breakdown 110. Preferably, selecting words causes the visual highlighting of those words. This is a much quicker and more efficient way to break down the script 100.

When a department, such as the prop department, creates their script breakdown 110, this breakdown becomes the definitive prop script breakdown 110 that is accessed by all. If another department is routinely doing a prop script breakdown 110 and enters conflicting data, this data is not entered automatically into a main collection node^As94. The data is routed to the prop department with a notice asking if this information is correct. The prop department then decides whether or not to add the information to the script breakdown 110. In this manner, the script breakdown 110 of a specific area maintains accuracy and reflects what that particular department is visualizing and planning for the execution of that scene. In the absence of the data management system 10 of the present invention, various departments track different items, and thus, their script breakdown 110 methods would tend to differ substantially. The data management system 10 provides a script breakdown 110 interface that is customized to each department. Pricing data can be attached to objects to automate department cost reporting 310. For instance, the Director of Photography (DP) creates lighting plans. To do this, the blueprints of a set are scanned into the system 10. The data management system 10 of the present invention allows the DP to "place" lights on the blueprint. The DP has a toolbox of symbols that represent the different types of lights. The DP is able to drag and drop these symbols to where he wants to place these lights. The rental price information is linked to each symbol, with accompanying rule sets (e.g., "if over 4 are rented, the price goes down by this amount"). Therefore, after the DP has drawn up the lighting plans, the pricing of the lighting package is immediately known and an equipment list is posted to his electric department. Both the electric and grip department have access to these plans which helps them figure the necessary pre-rig days and crew sizes.

The script breakdown 110 is an automated feature that breaks the script 100 down into Scenes, Int/Ext, Day/Night, Location, Characters, props, page count, and the like. Once this first breakdown 110 is complete, the user can go through and add to it. The data management system 10 provides for more efficiency since users are able to set the type of breakdown 110 to be created and then simply select on the words that they want to add to that category's breakdown 110 of the scene. Preferably, the data management system 10 also counts loops for the characters.

In certain situations, such as the locations breakdown 110, several different departments contribute to the breakdown 110. The locations department starts the breakdown 110 with customary information including: picture of location, price, restrictions, permits required, booked or not booked, and the like. The management system 10, in accordance with the present invention, allows the various departments to input information into the system 10 after they have seen the location on a technical scout. Thus, the management system 10 provides access to information that has been previously inaccessible outside of the department. For instance, the electric department might note a restriction on power load after seeing the location, which would certainly affect others. The management system 10 provides easy access to all location infoπnation by scene, and thus, reduces the number of unpleasant surprises that occur on the day of shooting.

In the locations department script breakdown 110, the data management system 10 starts the script breakdown 110 with a listing of the various sets needed in the script 100. As locations are searched, the information is entered into the data management system 10 with a reference to the scene number. Therefore, at any point, the location person can pull up all the pending possibilities for a set. The data management system 10 also manages the pictures of the location, as well as other pertinent information (dates available, cost, restrictions, address, etc). Once the location has been determined, the data management system 10 registers the location as being the set for the specified scenes. Pulling up a list of sets that have still not been decided upon is a simple task with the data management system 10. Just before shooting, a "technical scouting" is performed. This involves taking the technical departments to see all of the locations. Each of the departments take notes. The data management system 10 allows these department specific notes (e.g., the electrics noting that there is no local power and all power must be from a generator) to be accessed by all others. In the aforementioned electrical note example, the sound person would be alerted to bring extra baffling that day, to combat the noise of the generator. Without the data management system 10, this information is not readily available.

Movie scheduling is another important step. While the Assistant Director creates a schedule 120, the management system 10 provides access to the various department breakdowns 110 that are stored in the collection nodes^Λs94. This provides the scheduler with additional information during scheduling decisions. Different versions of the schedules and calendars can be created using the management system 10. The management system 10, in accordance with the present invention, greatly automates this task, since the information for the other departments is already in the system 10. Further, the management system 10 also provides a visual representation of a calendar to work with that includes "drag and drop" capabilities.

If a schedule 120 change occurs, the management system 10 assesses the information affected by these changes and alerts the various departments. By using the management system 10, the departments have instant access to every new schedule 120, instead of having to wait for a schedule 120 to be printed, as is currently required using standard paper practice. Intelligent calculation of flagging problems is also provided by the management system 10. For example, if Scenes 5, 14 and 72 were originally scheduled on different days and each required a Titan® Crane, and the scenes are now scheduled to be shot on the same day, the management system 10 will recognize that only one crane is needed - not three. This information is passed on to the necessary departments, such as accounting.

The scheduling portion of the data management system 10 automates the process by allowing the user to enter a set or several sets of priorities. For example, to meet the criteria of (1) shooting the exterior scenes first, (2) shooting a specific set first, and (3) shooting all the scenes with an actor that is only available for a specific 10 day period, the data management system 10 creates a schedule 120 that best suits this scenario. The data management system 10 also interfaces with the various department script breakdowns 110 and flags potential problems or conflicts. For example, a set may not be available on a certain date, or might cost more after a specific date, or another actor might not be available, or the scene that blows up the car is being shot before the scenes that requires the pristine car. The user can override all these notices and proceed or change the schedule 120 accordingly. The interface preferably includes drag and drop capabilities. The data management system 10 also provides several versions of the schedule 120 to be created and reports on the differing impact that the versions have on budget 240, schedule 120, actor availability, and the like. The data management system 10 provides different views — both the traditional "stripboard" view and a calendar view, which is not available without the data management systems 10. Therefore, the user has the flexibility to work in the visual environment that is best suited to that particular user.

During the course of the shoot, the schedule 120 often changes. The data management system 10 of the present invention allows the Assistant Director (AD) to create these changes "on the fly" and to see the impact of the changes. After a schedule 120 commitment is reached, the schedule 120 is posted and the data management system 10 flags and notifies the various departments of what changes affect their particular area. Therefore, the prop department could be notified that the schedule 120 change means that the grand piano is needed for an extra month. In another example, the production manager could be notified that the three scenes that need a Titan crane® have now been scheduled on the same day, so the production only needs one day of crane rental, not three. When a change in the schedule 120 occurs, the data management system 10 calculates what affects this change has by cross checking the various department script breakdowns 110. The data management system 10 notifies the department heads of what items are affected (e.g., a scene could be re-scheduled for a date that occurs after one of the character is wrapped from the show).

Another document that has to be generated every day is the call sheet 130 (See Appendix, Page 16). This document lists the planned work for the next day. In a preferred embodiment management system 10, the generation of the call sheet 130 is highly automated. The original template in the management system 10 contains the information from the schedule 120, which usually does not change. However, if a scene is not completed on its scheduled day, that scene is automatically listed as a partial "to complete" in the system 10. The page count is kept accurate since the management system 10 collection nodes^As94 have the requisite information from the script supervisor regarding partial page count credit. By utilizing the management system 10, the script supervisor's breakdowns 110 and reporting are automatically incorporated into a primary collection node^Λs94 of the management system 10. Presently, without the management system 10, the call sheet 130 often contains incorrect page count information because the pages have changed, but only the script supervisor is tracking the new information. As a result, incorrect information can result in incorrect scheduling.

The call sheet 130 also lists the characters (actors) to be used on a given day and specific department information, such as props needed, wardrobe issues, special equipment, and the like. Currently, without the management system 10, this information comes from the Assistant Director's personal breakdowns 110, which generally are not as extensive or as accurate as the individual department breakdowns 110. Due to this fact, this information is often ignored on the call sheet 130. The management system 10 of the present invention greatly increases the accuracy of the call sheet 130, since the management system 10 pulls together the required information automatically from the various departments.

The advance schedule also appears on the call sheet 130. Using the management system 10, this information is automatically filled in from the schedule 120 information. A crew list and their call times are also part of this document. The management system 10, in accordance with the present invention, includes a template for this document. Additionally, the call time is globally adjustable by manually entering any variations. For certain highly predictable activities, the departmental information is preferably input into a call sheet 130 template in the management system 10, thereby expediting the process.

The management system 10 allows the call sheet 130 to be accessed from the assistant director's PDA, laptop, or other similar device for continuous updating. Currently, without the data management system 10 of the present invention, the call sheet 130 must be created on the set and then generally brought to the production office to be copied for distribution. Unfortunately, events often occur that make it impossible to finalize the call sheet 130 until very close to the actual wrap of the day. This can cause incorrect call sheets 130 to be in circulation or require handwritten corrections placed upon every individual call sheet 130. Using the management system 10, the call sheet 130 is published at "wrap time" to all the departments, as well as the production office. The call sheet 130 is viewable and printable by each crew member simply by logging onto the management system 10 network.

The data management system 10 automatically calculates a call time that does not invade any turnaround by calculating each union local's requirements for turnaround. The call sheet 130 starts with a template that is called from the schedule 120. If a scene has been only partially shot, the data management system 10 calculates the amount of page count remaining.

The script supervisor takes notes on everything that is shot. Without the data management system 10, this information is then sent to the Editor as "facing pages" which are viewed on the left side of a binder with the corresponding script 100 page being on the right side. The script supervisor also creates the "lined script" which is a visual representation of what has been shot. Lines which represent shots, are drawn down the page and identified by shot type and shot coverage (e.g., CU of Mary). Thus, without the data management system 10 of the present invention, the script supervisor creates the lined script by drawing colored lines down the script page that represent the setup. There is only one version of the lined script so the script supervisor keeps the lined script during the shoot and gives it to the editor at the end of the shoot. Therefore, the editor is working with black and white copies while cutting during the shoot portion of the production. This process of lining the script is time consuming and inefficient. Further, if any changes are made in the script 100 as it is actually shot, the script supervisor records these changes and sends them in the form of new script pages to the editor. Currently, without the management system 10 of the present invention, only the script supervisor and the editor have access to the pages that reflect what was actually shot. In a preferred embodiment management system 10, these "as-shot" pages are available to others.

The data management system 10 allows the script supervisor to create the lined script on a computer or other suitable device. The script 100 is already accessible to the script supervisor who draws the lines on the page by selecting at the start area. (A straight line indicates when the line covered is spoken by the character on camera and a squiggly line indicates that the speaker is not on camera.). The data management system 10 allows the script supervisor to reproduce this system. The setup lines are linked to the specific location in the script 100 so when the script 100 changes format because of revisions, the lining is still correct. Without the data management system 10, when new pages are published, the script supervisor must reline these pages adding more work. The data management system 10 allows the editor to access these lined pages immediately without having to wait for them to be delivered to him. The lined pages are also in color within the data management system 10, which makes them a more effective visual reference. The data management system 10 allows the editor to select on the setup line and bring the detailed notes to the setup up on the left. The system 10 can also bring up the digitized material on an electronic editing device so it is easy to locate the material.

In a preferred embodiment management system 10, the most current version of the script 100 is always available since the script 100 is used as a central focal point. Currently, without the management system 10, new pages are published on different colored sheets when changes are made in advance. The creates more potential sources of error. For example, a pink revised page could become a yellow revised page, and there would be no way of knowing that this page was the second revision. A preferred embodiment management system 10 uses a colored bar to indicate the color of revision with a block of color(s) at the bottom to indicate any previous revisions. Preferably, when a user logs on to the management system 10, the user is informed of the existence of new pages and is allowed to call up the new pages for review. In this manner, the management system 10 accelerates the process of correcting the department breakdowns 110 to reflect the new pages. Preferably, the management system 10 also stores the previous versions of the pages for quick reference. Without the data management system 10, the original versions of the pages are often lost. Further, a preferred embodiment management system 10 allows a user to pull up the script 100 pages to be shot on the following day

(information that comes from the call sheet 130). This functionality allows the user to better prepare for the next day of shooting. By using the management system 10, the script supervisor is able to identify a visual effects shot when entering information for the facing page notes. The management system 10 also provides for these specific notes to be sent to the visual effects 234 house, as well as ensuring that the dailies 230 of the set-up are sent. Moreover, the management system 10 provides other choices (such as sound house or title house) that will ensure that these often overlooked areas of production automatically receive the information they need. A subset of the notes forms the "Print Log" which is a simplified list of what was printed that the assistant editor uses when viewing dailies 230.

In the script supervisor report 140 portion of a preferred embodiment data management system 10, the page count credit is added up each day, saved as the total count for that specific day, and subtracted from the total script 100 page count to give the amount of the film left to finish. The total numbers of scenes shot is calculated for the day's work, saved as that day's total, and then subtracted from the total number of script 100 scenes to give total remaining amount. Thus, when the script 100 changes, the page count and the number of scenes also change. The number of set ups is automatically calculated from the script's facing page notes, saved as the set up amount for that day, and then added to the previous total to make the total to date. The amount of time credited for each scene shot that day is added to create that day's total time, added to the previous total of time to create the total of time shot to date, and then subtracted from the total original estimated time. The script's report includes the time of the meal breaks that are used to calculate meal penalties on the production report 220 (if the meal break occurs later than 6 hours after the call or last meal, a penalty is incurred). If a meal penalty is incurred, the data management system 10 calculates the final cost report 310 since each department may accrue the penalty differently. The data management system 10 tracks what scenes are considered complete, which are considered partially complete, and which have not yet been shot.

The script's notes include the selected prints, which are entered into the system 10 periodically throughout the day, and uploaded into the Assistant Camera's reports, the sound person's reports and the VTR's reports. The data management system 10 checks for discrepancies and reports back to the script supervisor, should any be found. At the end of the day, the relevant portions of the script's, camera's and sound's reports are merged together, and checked for discrepancies before being sent to the lab. The assistant camera person creates a camera report 150 during the day. The camera roll number and the magazine number of each roll of raw stock shot are written down in this report. Further, the scene numbers and the take numbers are written down on each report, as well as whether or not this information is printed. This information on prints originates from the assistant cameraman and is a potential source of error. For instance, it is possible for the script supervisor to indicate the wrong take for printing, which causes havoc in the lab when they see that he's printing take 3 and not take 2 but the sound is transferring take 2 and not take 3.

Using the management system 10, the script supervisor inputs his print information into the system 10. This print information is then compared with any information that the assistant camera person has entered. Preferably, any discrepancies are flagged, allowing them to be dealt with immediately. This information is also checked against the sound man's information in the same manner.

The lens information appears in the script notes. However, typically the script supervisor must get this information from the assistant camera person whenever there is a lull in the shooting. In a preferred embodiment management system 10, the lens information is already incorporated into the camera report 150, and thus, is automatically pulled into the script supervisor's notes. Any specific camera information about a take (e.g., "out of focus") is also entered into the camera and sound reports 150 and 160, and included in the script supervisor's notes to the editor (preferably, with an indication that the comment came directly from camera department). Without the management system 10 of the present invention, the editor only gets the notes that the script supervisor sends. This includes information from the camera or sound only if passed on by the corresponding departments, which often does not occur due to time constraints.

The camera report 150 includes timing reports from the Director of Photography and developing notes for the lab. In a preferred embodiment management system 10, this information is forwarded straight to the lab and telecine facility to assist in preparation for processing. Each roll of film is identified with a bar code that is embedded in the camera report 150 for that roll and also travels with the film cans to the lab and telecine to facilitate tracking.

The assistant cameraman (AC) keeps ongoing camera reports 150 during the shooting day. The AC records the film stock used and the footage length of each take. Once the selected print information is included in the report, the data management system 10 creates an inventory report that includes the total of footage broken down by "good" (printed takes), bad ("not printed") and short ends (left over film not developed). This information needs to be added up by film stock and subtracted from the inventory total, to give a new total. This information automatically is included into the production report 220. The accounting 190 portion of the data management system 10 takes in this information, checks it against the expected totals, and flags any detected variances. The accounting 190 portion of the data management system 10 also calculates the cost reports 310 for the day's film footage and the payroll 280. Preferably, the data management system 10 is customizable (warning levels can be added to alert when a film stock's inventory drops below a specific amount) in order to help the assistant cameraman anticipate shortages in film stock. This warning level can be different for the different film stocks.

Each camera report 150 has a bar code associated with it which also travels with the film cans to the lab and telecine. This allows these elements to be tracked. Also, if there is a problem with the film in the lab, the bar code instantly allows all persons to know what camera roll was affected and what scenes were shot on that roll. In a preferred embodiment management system 10, the sound person enters the scene, takes, and prints information into a sound report 160 on his laptop (as well as any specific sound notes). This information becomes part of the editor's notes. The management system 10 also allows the sound person to add general time code information for each take into the sound report 160 which further expedites the telecine and synching process. The VTR person records the takes on a video tape in the camera. Further, the VTR person needs to log the tape's time code number, the scene numbers, and take numbers so that specific takes easily locatable for later reference. A commonly encountered problem is that often the VTR person is quite far away from the set, and as a result, misses a scene number change, which throws off his numbering system. However, a preferred embodiment management system 10 catches these type of discrepancies in the VTR report 170, in the same manner as the camera and sound print discrepancies are caught. Moreover, the management system 10 of the present invention is capable of interfacing with a video tape or a hard drive, which is where tape material is commonly recorded on the set for rough cutting or frame checking.

The camera report 150, the sound report 160 and certain fields of the script supervisor's report 140 combine as a flex file 180. Without the management system 10 of the present invention, the telecine house does not receive this data in a timely fashion, even though the information needed for the flex file 180 is entered in the notes on the set. Thus, the telecine house has to manually enter this information during the telecine session. Additionally, when tapes go to the assistant editor to be digitized, the assistant editor may have to record the information yet again if the format does not match the script notes. The management system 10 eliminates this redundancy, since the flex file 180 creation is initiated on the set and the file is sent directly to the telecine house. The specific telecine information is then added, and the flex file 180 forwarded to the assistant editor. The management system 10 provides this file in the correct format, and has the necessary information to allow the assistant to digitize without any extra manipulation of the file. Accordingly, the management system 10 saves a substantial amount of time.

The accounting department 190 gathers specific information on cost reports 310 for salaries, equipment costs, location cost, etc. starting in pre-production. A preferred embodiment management system 10 utilizes intelligent functioning that enables this information to be linked with line items in the budget 240, thus allowing production to easily review costs at any point in the process of making a film, including payroll 280. As the film progresses, the management system 10 provides average costs analysis and is capable of alerting the accounting department 190 and production when costs deviate from expectations. The management system 10 also has the capability of allowing users watch for specific potential problems (i.e., specific "red flag items" to the production), that require particular attention. Day to day costs are calculated in the accounting department 190. The data management system 10 creates cost reports 310 that track this information so that these costs do not have to be entered manually, as is the standard practice. This automation by the management system 10 reduces the possibility of input errors. The data management system 10 also produces the payroll 280 reporting from the production report 220. Further, throughout all phases of production, financial reports are sent to the studio. These reports are very confidential. Rather than having excess paper versions traveling about, the management system 10 allows this information to be ported to the computers of only the people who have been granted access to such information.

Utilizing data from the script 100, the budget 240 is then finalized within the management system 10. Preferably, the budget 240 information is stored in the collection nodes^Λs94 with specific line items and their functions customized per production. In one exemplary embodiment, a crew member's pay rate and box rental rate are linked (e.g., if a crew member's prep period is lengthened, this modification is reflected not only in the budget 240, but also automatically in a total box rental increase.). The linkage of budget 240 items produces intelligence and automation in a preferred embodiment management system 10 of the present invention. Since a preferred embodiment management system 10 utilizes collection nodes^Λs94, budget 240 items are interconnected so as to share information.

Various departments work on their specific budgets 240 that are viewed by the production manager and compared to the costs anticipated by the budget 240. The management system 10 allows secure transmission of these preliminary estimates between departments and the production manager. Additionally, the management system 10 provides the production manager with specific tools with which to view various possible scenarios before making final cost decisions. Preferably, all departments' budgets are constantly tracked by the management system 10 during the production, allowing accessibility to financial information such as what has been spent, how much is left in the budget 240, and variances in the original estimated costs from the actual cost reports 310.

In the accounting 190 portion of a preferred embodiment data management system 10, the user is able to link items, allowing automatic recalculation when one of the items is changed. For example, a crew member's rate and his kit rental are currently considered separate items in most budgeting programs. In a preferred embodiment data management system 10, these categories are linked, so the budget 240 automatically reflects the additional kit rental, should the crew member be given another week of prep.

The accounting report 190 accumulates ongoing information during the shoot and predicts average monetary figures on a week to week basis. Should large variances be encountered, the data management system 10 calculates the differences and flags the items. Preferably, the accounting 190 portion of the data management system 10 compares weekly cost reports 310 that show where the variances occur. The data management system 10 also flags any specific areas that are consistently off their anticipated budgets (e.g., a department which is consistently over- budget each week).

Preferably, all purchase orders 200 originate from the management system 10. A problem which is often encountered in production is that the process of obtaining a purchase order 200 is time consuming. If an item is needed immediately, the item must purchased without the proper paperwork. This causes "lost" expense items that are not incorporated in the constant surveillance of the overall cost of a film and causes inadvertent overages. A preferred embodiment management system 10 speeds the process of purchase order 200 approval (e.g., a crew member on the set can send in the request over the network of the management system 10 without having to physically leave the set). Once the purchase order 200 is approved, the purchase order 200 is locked into the management system 10 and becomes part of the "committed costs" column.

A preferred embodiment management system 10 also gathers specific information from the production list 250. The production list 250 includes personal information such as name, home address, phone numbers, and email address, for each person in the production. A preferred embodiment management system 10 also gathers specific information from the vendor list 260. The vendor list 260 personal information such as name, home address, phone numbers, and email address, for each vendor involved with the production.

In a preferred embodiment management system 10, the daily report 210, which is created by the script supervisor, is imported directly into the production report 220. The management system 10 also records what was shot that day, as well as the page count credit given. Additionally, a total of the number of scenes, page count, time and setups to date is maintained, as well as a calculation of what is left to be finished. Call time, meal time, 1^st AM and 1^st PM shot, and camera wrap are also noted. The meal times determine the meal penalty, if any, that must be added to the general cost of the day. This information appears on the production report 220, the daily cost report 310, and the weekly cost report 310. The management system 10, in accordance with the present invention, transfers this information via the system network and automatically enters this information into the report, rather than requiring the assistant director to manually enter this information into his production report 220 as is necessary without the management system 10.

Prior to shooting, the script supervisor creates an estimated time list that is broken down by scenes. As each scene is filmed, the script supervisor reports 140 on the actual time at which the scene played. The management system 10 marks the variances between the estimated and the actual shot time. This is critical information in judging whether a movie is running too long or too short. Further, the management system 10 allows the Director of Photography to create a representative digital frame of a setup. In a preferred embodiment management system 10, the Director of Photography is able to manipulate the image and send the image to the lab for a timing reference, thus eliminating the need for dailies 230 reprints. Moreover, the management system 10 allows the production office to check which reports have been sent (e.g., the production report 220) and to verify that the unsent reports are finished and posted. Moreover, the management system 10 allows the production office to track the status of specific elements (such as whether the film has reached the lab or if it is already in telecine) via a bar coding feature. Finally, the production office is also able to take the script 100 revisions that have been prepared in advance and publish them with the corresponding revision color.

During shooting of a film, reports are generated at the set. Currently, without the data management system 10, the Assistant director produces a daily "Production report" 130 (See Appendix, Page 17) that includes information gathered from various printed reports. However, by utilizing the management system 10 in accordance with the present invention, the data no longer has to be entered manually. Referring now to FIGURES 2-4, and more particularly to FIGURE 4, the portions of other reports (from, for instance, the script supervisor and camera department) that are relevant are automatically entered into the production report 220 by the management system 10. The procurement of information that the assistant director must obtain himself is greatly automated by the management system 10, thereby increasing efficiency and accuracy. For example, presently, the assistant director has to list the actors used each shooting day and their "in and out times 300" as well as to obtain a signature verifying the out times 300. Using the management system 10 of the present invention, the actors used that day are already entered into the system 10, since that information has already been input from that day's call sheet 130, which was pulled directly from the script 100 and the character breakdowns 110. The "in times" of the actors are also automatically entered into the management system 10, since that information previously appeared on the call sheet 130. When an actor leaves, his "out time 300" is automatically entered into the management system 10 by using Ms digital signature entered on the assistant director's PDA or tablet.

Similarly, the crew and their "in times" are automatically entered into the management system 10 from each day's production report 220. The departments enter the crew "out times 290" into the management system 10 as they finish work, instead of the assistant director having to physically search down each crew member and find out their crew "out times 290," as is currently required without the data management system 10. Using the management system 10, this information automatically appears on the production report 220.

Currently, without the data management system 10, the assistant cameraman must manually write down the footage used for each take, as well as the film stock used. This information must be entered on a camera report 150. This information also appears on the production report 220. This manual tallying is generally performed after a long day which results in numbers that don't typically balance correctly. In a preferred embodiment management system 10, the assistant camera man enters this footage and stock information during the day in a PDA instead of on a piece of paper. After uploading this information, the management system 10 performs the necessary calculations and sends the results to the production report 220.

In the management system 10 of the present invention, the production report 220 also includes other information such as number of meals served, extra personnel used, and equipment brought in for that specific day. All this information is used to calculate the actual cost of the day. When the report is submitted into the management system 10, this information goes directly to the accounting department and populates their daily "hot costs" report 310. Both the hot costs report 310 and the production report 220 are submitted, in turn, to the production manager who reviews the information before forwarding it to the producer and the studio. As previously mentioned, during the shoot the management system 10 tracks all relevant financial information and alerts the accounting department of any areas that exceed expected costs.

Portions of the production report 220 are automatically filled with information from the script 100, camera, sound reports 160. Information from the production report 220 is automatically input into the accounting departments daily cost reports 310 (e.g., the crew "out time 290" of the crew members allows the accounting department to know how much was spent on crew that day). The actors' "in and out times 300" are also calculated in terms of cost, as is film footage. Meal penalties and the number of meals served are also cost items.

As shown in FIGURES 2-3, in a preferred embodiment management system 10, the dailies 230 and other visual and audio effects are transferred to the various locations via the system 10 network, thereby eliminating the need for low quality video tapes. In one preferred embodiment, an access control is added that allows one person (such as the director) to view the dailies 230 and other visual and audio effects first and then release them for viewing elsewhere. Moreover, a preferred embodiment management system 10 allows the dailies 230 to be annotated with notes for specific people. Preferably, these notes are invisible to everyone except the intended recipient. In one preferred embodiment, a specific area of a frame can be marked and commented upon. When the intended recipient views the dailies 230, the management system 10 stops the footage on the frame with the note. Preferably, additional functionality of the management system 10 allows the recipient to respond to the note. These annotations are preferably stored for future reference.

A preferred embodiment management system 10 also allows variations in how the dailies 230 and other visual and audio effects are delivered. For example, in one preferred embodiment, the visual effects 234 house has the capability to send a first rough version of their work (thus allowing for immediate feedback). Importantly, the management system 10 allows the director to view the dailies 230 at a greater resolution than video tape is capable of providing. This allows the director (or others) to make more accurate judgments as to the quality and acceptability of the dailies 230. The high bandwidth (preferably near or above 45Mbps) of the broadband network 10 allows the present methodology to bundle enhanced resolution digital dailies with the video conferencing and telephony. Specifically, the high resolution digital dailies have a video motion signal that is preferably greater than 720 x 480 pixels, more preferably at or greater thanl280 x 720 pixels, and most preferably at or greater than 1920 x 1080 pixels. Using the methodology of the present invention, these enhanced digital dailies are transferred to various remote locations within the system 10, thereby eliminating the need for low quality video tapes. In one preferred methodology, access control is added which allows one person (such as the director) to view the enhanced digital dailies first and then to release them for viewing elsewhere. Importantly, the methodology of the present invention, using the broadband system 10, allows the director to view the enlianced digital dailies in high definition, which is a greater resolution than standard video tape is capable of providing. This allows the director (or others) to make more accurate judgments as to the quality and acceptability of the enhanced digital dailies. It should be noted that high resolution is an often misused term that does not have clear associated parameters. However, high definition is a clearly defined term that refers to a video motion signal which is typically between "1280 x 720 pixels" and "1920 x 1080 pixels. Since the management system 10 is a preferably private network (i.e., not connected to the Internet), messages are sent back and forth simply and securely. People involved in the production are easily accessed for email or other types of data transfer communication methods. One such other method by communication on the production site is a general announcement banner on the screen. For example, a posted announcement such as "Dailies are at 7 PM tonight" ensures that everyone receives this message. This technique is more effective than the methods currently in use. Additionally, the management system 10, in accordance with the present invention, allows video conferencing and collaborative editing systems 10 for real time collaboration (which currently is generally impossible during the shooting period when people are in different locations).

As the management system 10 grows, historical data from previous productions is stored in the collection nodes^Λs94 that is beneficial to setting up a new production. In this manner, the management system 10 allows a more accurate assessment of costs to be generated by viewing similar past experiences. Since all the information on a shoot is contained in the management system 10 collection nodes^As94, any configuration of information is accessible. For example, identifying the specific scenes a particular actor is in is easily achieved. The management system 10 also allows for "what-if ' scenarios. For example, two actors could be up for the same role with different availabilities. A preferred embodiment management system 10 relays what impact their availability or lack thereof has on a schedule 120 and, consequently, on the cost of the film. For example, perhaps with actor A, you will have to go back to a previously filmed location since he is not available when you are first there. The management system 10 added not only automation, but intelligent programming which helps the production solve or avoid problems.

Preferably, the management system 10 provides each department with custom applications to manipulate their specific breakdowns 110. For example, what may be a red flag for the wardrobe department would not be applicable to the property department.). Cross-linking between the departments is a built-in feature of the management system 10 of the present invention. For example, if special effects are planning a rain sequence in Scene 52, the wardrobe department will be notified so they know to provide multiple costumes. The management system 10 of the present invention preferably carries through the post-production period, providing the same interconnectivity as during filming, including budgets 240, schedules 120, and tracking elements.

A preferred embodiment data management system 10 utilizes drag & drop capabilities that greatly speed data entry. The system 10 also utilizes drop down menus and auto-fill fields. Further, the data management system 10 allows the user to see information in a calendar format, as well as to allow "drag and drop" items across the calendar. The data management system 10 ties all the steps of making a film together. The system 10 works from pre-production through the end of post-production. All parts of the system 10 are able to share the input data. Each area typically affects another area (e.g., the schedule 120 affects the budget 240). The data management system 10 tracks these types of dependencies. Preferably, any discrepancies in data are immediately noted and flagged.

FIGURES 2-4 and the following discussion provide an example of the interactive capabilities of a preferred embodiment data management system 10 on a typical day in the production of a film: The crew walks onto the set with call sheets 130 that were published the night before. Their call sheets 130 were displayed when they called up their individual screens the night before. The call sheet 130 lists the scenes that are to be shot. When the user selects on a scene number the script 100 pages appear, so that the next day's work is readable. When in the script 100 view, the user can call up any department's particular breakdown 110 and see, for instance, if the special effects department is planning to use smoke tomorrow. If a certain vehicle is plaimed to used in a scene, the prop department knows that the interior car prop is needed and the scenic department knows that the dusting machine is needed to dirty up the car. This is especially useful in a situation where the director has an inspiration to include this car into a scene (when it wasn't planned for before) but only notified the vehicle department. The data management system 10 allows information that sometimes now resides only in the primary department to be circulated.

The sets are listed for each scene and by selecting on that listing, the set breakdowns 110 are pulled up (into the screen in an embodiment utilizing a web browser type interface). Therefore the prop department can check if the appliances in the kitchen set are "practical" (i.e. can function) and then realize that they might need to use actual food. Selecting on the location listing (a specific point on the screen in an embodiment utilizing a web browser type interface), which is where the set physically exists, brings up a map to the location. The data management system 10 knows the user's information and also knows the location of the user's home base and generates the correct map accordingly.

Selecting on the actor's name generates a "day out of days" breakdown 110 that lists when that character works in the schedule 120 and his final working date. This is important since these days will have been set contractually and to work an actor longer costs the production a lot of money. The director might be planning to grab a few additional close-ups of the actor for another scene and mention this to the script supervisor who could then use the data management system 10 to quickly check whether those shots must be taken that day if, for example, it is the actor's final day. (This situation comes up quite often because of the sheer volume of actors in a film.).

Without the data management system 10 of the present invention, paper call sheets have to be given to the crew with a general call time on the front page and then list each person's actual call time on the back. The crew member must look down the list on the back and find his name to ascertain his call. The data management system 10 automatically publishes the user's own call time on the front time. The list of crew and their call times is still accessible, so people can know if a department has a later call and can plan accordingly. The advance schedule is listed and a user can select on the scene numbers to bring up the script 100 pages that pertain to what will be shot in the next days.

At the start of each day, individual departments logs onto the data management system 10 and display their particular breakdowns 110 for that day's scenes. This allows them to double check that they have the material needed for that day. Production wide announcements (such as "Dailies will be 70 minutes long today and will be viewed a half hour after wrap" or "There are new page revisions to be published this afternoon") appear on every department's screen.

Without the data management system 10, the communication between the shooting crew on location and the production office or individual department offices consists of runners traveling back and forth with paperwork. This creates a very slow stream of data. Therefore, many decisions are made in the field without contacting the production office for reasons of expediency. This leads to problems like purchases being made without issued purchase orders 200 that later get lost in the system and cause inadvertent overages. The various departments can also have their central offices in locations other than the production office. A preferred embodiment data management system 10 allows people in the field (on the set) to contact the authorities in their department or of the production before committing to a purchase or making controversial decisions. The data management system 10 also allows a customized (per production) tiered approval system for time critical decisions.

As the day progresses, rehearsals are run for the planned scenes. During the course of rehearsals, script 100 changes may occur. Without the data management system 10, these changes are noted by the script supervisor who includes them in the editor's set of notes for that day. The other people on the set do not generally have access to this information and if these pages are generated "on the fly," they are not a part of the script 100 that the departments will work with, since they were never officially published. Specific people with access privileges are able to input script 100 changes (script supervisor, director, production coordinator, for instance). These changes, are published for all the departments to see after being "submitted."

Script 100 pages have very strict formatting rules - once the script 100 is "locked", the pagination and scene numbers must remain the same. (For example, if additional dialogue is added to the middle of page 14, rather than have the end of page 14 spill over to page 15, a new page numbered "14A" is created. Thereby, the top of page 15 remains constant.) The data management system 10 follows these formatting rules and adds automates to the process. When a scene is added or omitted, the data management system 10 calculates how each department is affected. (For example, if the scenes that are omitted are the only scenes in which the 1966 Mustang appears, the data management system 10 notifies the vehicle department of this and flag this item as possibly no longer necessary. If a character is added to an existing scene but' that scene is scheduled at a date after the wrap date of the actor playing that character, this is flagged immediately.) The data management system 10 only notifies the persons needing to know of the change, thus reducing the amount of information provided a user, thus increasing manageability of the information. The camera magazine is loaded in the camera truck and a set of duplicate bar codes is attached to that specific magazine. When the magazine is loaded onto the camera on set, the bar code is read into the assistant's PDA that then links that specific film roll to the camera report 150. Preferably, this is accomplished by a pen device that works with the PDA. The assistant inputs the magazine number and film stock number by accessing the drop down menus. The date is automatically entered into the report when the report is started (for instances of night shoots, if it is desired to consistently enter the same date after midnight, this is preset). The assistant can change the default footage (which would be a full magazine) to accommodate short ends (remainders of previously shot rolls that did not use the full amount). In a preferred embodiment data management system 10 of the present invention, all of this data entry is automated by drop down menus and defaults to speed up the process. As the setup is shot, the assistant camera man records the setup number and take number of each take. Without the data management system 10, the script supervisor, the sound man, and the VTR man are all entering the exact same information at the same time. All but the VTR man are also keeping track of what takes are to be printed. Without the data management system 10, the script supervisor, who receives the print information from the director, must relay this information to camera and sound. Often this exchange occurs at the end of the day and a lot of errors occur because people are tired and mis-mark their reports. In the data management system 10, the setup and take information are submitted into the system 10 periodically during the day. Discrepancies are flagged and the last user who enters the conflicting data, as well as the script supervisor, are notified immediately. This allows errors to be found in a timely fashion. The script supervisor is ultimately responsible for prints so her data on the prints selection overwrites any areas of discrepancies. This is an example of a discrepancy checking ruleset with a hierarchal structure (i.e., a specified user's data will overrule other data"). However, a discrepancy report is nevertheless sent back to the specified key person and the user who generated the differing data. This allows the possibility of checking for errors in the key person's data. The scene and take fields are entered by the script supervisor who then post them to the system 10, eliminating the need for the other users to enter this data. This is a work method choice by the individuals involved.

The above information (as well as additional data) is part of the lab and the telecine reports. Without the data management system 10 these areas receive the camera and sound reports (the script's report is not completed in time to be shipped with the film) and must collate 160 the information from both reports that sometimes contain conflicting data. The data management system 10 sorts out the discrepancies before the lab and telecine houses receive the reports. Importantly, the data management system 10 allows the script supervisor's report 140 to be part of this process and be the final word in this area. The take footages must also travel to the lab to enable them to find the selected takes that are to be printed. Sometimes the slate (the board that is held up and filmed before the take to visually identify that take) might have been incorrect or missed all together and the footages are all that the lab has to go on. In the data management system 10, this information is already electronic, which shortens the lab's work. Each can of film is identified by it's own bar code. When unloading the film from the magazine, the bar code is physically taken from the magazine and put onto the individual can. Each electronic report is linked to the physical film roll by the bar code. A shipping label is printed at the end of the day from the camera report 150 information. This enables the production to track individual rolls of film, since specific information on the film is included in shipping labels and reports.

With the data management system 10, the lab receives the reports electronically before the physical film arrives. This allows the lab to prepare for the shipment by knowing the exact amount to be developed and printed, as well as the film stocks involved. This helps the lab schedule their baths and printing runs more efficiently.

In the data management system 10, the camera report 150 also includes developing and color timing instructions from the Director of Photography. In current practice without data ^■ management system 10, the Director of Photography relays this information to the assistant and he writes this somewhere on the camera report by hand. The data management system 10 allows the Director of Photography to enter the information himself at the end of the day. The Director of Photography is not aware of the number of the camera roll, so it is confusing at the end of the day if the DP (Director of Photography) says to the AC (Assistant Cameraman),"Make sure they time that the close-up (CU) of Mary in the school house scene for the shadows, not the highlights." This forces the AC to track down the script supervisor and ask her what that particular setup was numbered and then find it on his camera reports.

The script supervisor's notes are accessible in data management system 10 so the DP can call up the scene and look at the take descriptions and input the instructions (if he so desires). The DP can think of this after the filming is wrapped for the day (and the film is shipped) and be sure that the lab has the instructions before the film is processed. In the current situation without the data management system 10 of the present invention, this requires panicked phone calls to the AC, who then must contact someone at the lab and then check the next day whether the developing information was actually passed on to the proper person. Camera lens information is closely tracked of for every setup. Without the data management system 10 of the present invention, the script supervisor must acquire this information from the camera department directly. This is difficult since changes to the shot can occur right up to the actual shooting. The accuracy of the information can not be assured unless the information is received just before the camera rolls or after the setup. If the information is incorrect in the script right after the setup, the assistant can easily forget the information as he concentrates on the new setup. (On some shoots the assistant also keeps track of this information, but the information must still be shared with the script supervisor.). Unfortunately, right after the setup is a time when the script supervisor is generally not available since she is interfacing with the other departments about the next setup or talking with the director. Thus, obtaining the lens information is a difficult process. In the data management system 10, however, the AC preferably enters the information in a PDA or other similar device. Once the information is submitted, it becomes part of the script notes. It is also possible for the script supervisor to enter the information if the assistant cannot enter the information. This is another instance of hierarchical discrepancy checking rule set, since the AC's information overrules the script supervisor's information. A discrepancy report is sent out to both individuals, allowing for entry error checking. The data management system 10 also allows for single entry instead of double entry of the data and allows the script supervisor to use that information in her report as well as being able to call up the information when needed. Preferably, the data management system 10 also provides precise lens and focal distance information used on the setup shots earlier in the day (in order to create matching shots, like close-ups). The script supervisor or AC calls up the setup numbers and the short descriptions of the shot.

The script supervisor is responsible for a very detailed set of information on each setup. One of the reports created by the script supervisor is the "facing page notes." These are notes that on specific setups that are inserted into the paper script opposite the script page on which the specific set up starts. Each setup includes: setup id (a number or number & letter), date shot, set, a short description for searches, a longer detailed description, camera information (lens, focal distance, filters used, frame rate), interior/exterior, the script supervisor records whether the setup rolled sound or not. For each take, the script supervisor records: take number, print/no print, length of the take, technical information (tail slate, frame rate (if it differs from other takes in the setup), false start, no slate, action changed, pick up, if the take started from a latter point than other takes), comments on the content of that specific take (actor seemed too angry, good for beginning, but director didn't like ending, light went out mid-take, lines said incorrectly, eyeline NG, as examples), the camera roll(s), and the sound roll, if any.

The data management system 10 of the present invention takes this data, the setup id, take number, print/no print, camera roll number, sound roll number, brief description and technical notes and includes the data in the lab and telecine report. The sound man's report (setup id, take number, sound timecode, print/no print, sound roll number) also makes up the lab and telecine report. As this data from these departments is submitted into the data management system 10 periodically during the day, the data is checked for discrepancies that are flagged and sent to the proper people. A hierarchical structure specifies (per field) which user has the overwriting privilege. The discrepancy messages enable error catching.

Preferably, in the data management system 10, no one but the script supervisor enters the print information. The script supervisor works with a PDA or other devices to create the basic template of the facing pages report which includes setup ID, take, int/ext, short description, set, date, MOS or sync, print/no print, technical information, camera roll and sound roll. This is automated with drop down menus. Every set in the movie can be called up by entering the first letter and then selecting the set. To enter the short description, one chooses from a drop down list of the type of shot (Master, CU, 2 Shot, MCU, LS, Medium Shot, ECU) and then another drop down list pulls up every character name to easily select. The date defaults to "today's date" (unless specifically set which can be done at the beginning of the day if it desired for the sheets to reflect the same date after the hour of midnight). The take number automatically increments when a new record in the same setup is created. The camera roll and sound roll defaults to the last entered roll number. The technical information is also a pull down list of choices - tail slate, pickup (and then a line number is enter), false start, 48fps, etc. Int/Ext, MOS/Sync are choices or one letter entries. Preferably, the script supervisor does not have to enter the lens information, but has access to that information. Camera and sound have access to the print information if needed. Without the data management system 10, part of the information entered into the facing pages notes consists of specific camera and sound notes, which the script supervisor must try to acquire on each setup and often cannot acquire because the script supervisor is busy checking continuity. In the data management system 10, the camera and sound can enter and access this information immediately. (This is important because if there was a focus problem at the end of the take, the camera person might assume that the previous takes could be used for that portion.) Only the script person would know that the director was not happy with the ending of any of the previous takes, and was relying on the last take. With this information, the script supervisor could flag the director of this problem and another take could be shot before leaving the set. The camera report 150 contributes to the film stock data as well as timing and developing notes to the lab and telecine reports. The sound report 160 adds to the sound timecode information. All of this information is synchronized to create one report which also generates the flex file 180.

The flex file 180 is the file that the telecine uses when they transfer film to tape. This file breaks the footage down into setup ID and take numbers and has the timecode of the tape that they are creating. Other information such as film key numbers are also contained in this file. This file travels with the tapes to the assistant editor who adds more information into this file before using it to digitize the dailies 230 into the electronic editing device. Certain information in the flex file 180 (such as setup ID, take number, and the descriptions that the assistant editor has entered) is dumped into the electronic editing system. Without the data management system 10, three people enter data that is used in the flex file 180, most of which is redundant. Often, because the data is not entered in the format that the assistant editor wants (who is working off of the script notes from the set), the assistant editor has to re-enter the same information. The data management system 10 starts the creation of the flex file 180 on the set when the data is generated. This eliminates redundant entry and ensures a higher level of accuracy.

The script supervisor also generates the daily report 210 which contains the following information: (1) Scene information: Total in script 100, previously shot, Shot today, Shot to date, remaining to shoot. (2) Page Count Info: Total in script 100, previously shot, shot today, shot to date, remaining to shoot. (Each page is divided into l/8s of pages, so a scene is considered to be 3/8's of a page long). (3) Timing (as in length) info: Total estimated length of the script 100, Length of time previously shot, Length of time shot today, remaining time, according to the original estimate. A constant tally of the variance between the time estimated for the scene in pre-production and the actual time of the shot scene is maintained and informs the script supervisor of the differences. These figures allow the producer to know if they are in the process of shooting an over or under length movie. When this information is available during the actual shooting portion of the production, it allows for corrections to be made to the script 100 (lengthening it or shortening it) or, for example, to correct the pacing of the acting (perhaps, overall, the performances are too languid) at the time of the shooting. This is a much more cost effect solution and is better for the final movie product, rather than randomly losing complete scenes during the editing process. (4) Setups: The number of setups talcen each day is recorded and a running total of the accumulated number of setups is kept. Each individual shot is considered a setup. The setup ID changes with each new shot with a notable exception. When multiple cameras are used, the setup ID is the same, but the camera roll numbers are different. (For example, there can be 5 setups 179B - take 2. The A camera is the master, the B Camera is the 2 shot, the C Camera is the Medium shot, the D Camera is the CU of Mark and the E Camera is the CU of Mary.) Without the data management system 10, the script supervisor has to go through her notes carefully at the end of the day, being sure to include the multi-camera setups in her count. The data management system 10 tracks this information for the script supervisor and constantly updates the system 10. All of the above information is required on the production report 220 and automatically becomes part of that report once submitted. This avoids redundant data entry. If there is a question on the values that have been entered, the script supervisor is questioned. Only the script supervisor can make these changes.

The Daily report 210 also includes the crew call, the first AM shot, lunch break time, 1^st PM shot, Dinner break and camera wrap. This information is used for cost purposes. Besides the obvious calculation of the hours of the day from the call and wrap times, subtracting meal breaks, this information also calculates meal penalty information. If there is a longer time period than 6 meals between call and a meal or between meals, then a penalty incurs. The Production report 220 is automatically populated with this data which, when submitted, populates the daily cost report 310 where calculation of this data turns into currency figures.

The Daily report 210 (without the data management system 10) includes the film stock shot that day, the camera roll numbers, as well as the sound rolls numbers and any wild track numbers. This information is currently put on the daily report 210 for the purpose of the production report 220, but is not necessary to the function of the script supervisor. The data management system 10 obtains this information from the sound department and camera department and automatically populates the production report 220 with this data. The script supervisor accesses the information if desired, but does not have the responsibility of entering the information.

The daily report 210 lists the scenes shot, with a description of the set and action, the length of the scene as shot, the number of pages created, and whether or not the scene was completed. The script supervisor has the list of the planned scenes for the day from the schedule 120 data and modifies it if required (if an additional scene were taken that day, for example). If the script supervisor marks the scene as complete, the full amount of the page is credited and added to the total for the day - or if it were a scene that had previously been partially completed, the data management system 10 only adds the remaining uncredited page count. If the script supervisor marks it as partial, the page count for the total scene as well as any credit previously assigned is displayed. The script supervisor then enters the amount of the page count that is considered to have been covered that day. At any point, after the script supervisor has submitted this information, the information is accessible by users with the permission to do so, which helps others access the progress of the day. Many times a "lunch report" is required, which is a shortened report for the studio which indicates what the progress of the day is as of lunch. This includes scenes finished, page count accrued, length shot, setups so far, and first AM shot. Without the data management system 10, this requires a runner to the production office or a phone call to pass the data to the coordinator who will relay the information to the studio. With the data management system 10, when the production breaks for lunch, the coordinator calls up the information immediately on a computer.

The daily report 210 also contains any "pickups" (shots of scenes already counted as complete) and "retakes" (specific shots that are redone). When the script supervisor creates facing pages, she indicates if the set up fits into this category so it is automatically included in the daily report 210. The script supervisor works with a PDA and a laptop or other simiilar configuration. This allows her to start the reports between takes and after hot syncing to the laptop, finishes any of the more type-intensive portions of the reports with a bigger keyboard. The PDA also allows her to instantly access the information coming from the sound and camera departments.

The information from the script supervisor, the camera department, and the sound department found in the production report 220 is only viewable by selective users. When the data is collected for the production report 220 and the AD has checked it (the assistant director's department also adds data to this report), he "submits" the data to the next level. This allows the production manager to view the document. The production manager can request changes and send these requests (or requirements) to the various departments responsible for the data. These users make the changes and inform the production manager accordingly. The production manager signs off on the document and sends it to the producer and the accounting departments. These users view the document and send it back for corrections or sign off on the document with digital signatures. At this point, the production report 220 is submitted to the studio. The data management system 10 of the present invention sets the permission levels of users at the start of the production, but these can be changed at any point during the production if the customer so requires.

The AD's portion of the production includes the signing in and out of actors. In the data management system 10, the actors are automatically added to the day's production report 220 that lists the scenes (which automatically comes from the call sheet 130 that comes from the schedule 120). The scene identification then accesses the actor breakdown and lists those required that day into the production report 220. Their "in times" are taken from the their call times on the call sheet 130. Without the data management system 10, when an actor leaves the set for the day (which occurs at various points during the day), the assistant director must find the actor and have them sign a form. The data management system 10 uses a digital signature to achieve this result. The AD has a PDA, or other similar device, into which data is entered. The AD has another PDA that contains the digital signatures of all the actors. This PDA is preferably encrypted so it only interfaces with the AD's PDA. The actor enters his private password into the signature PDA and "beams" his signature to the AD's PDA. The signature data is "time stamped" on transfer and used to calculate the actor's "out time 300." When the production report 220 is sent to the accounting department, the data management system 10 accesses the actor's contract and calculates the cost for that day.

The production report 220 is also used to report the cerw "in and out times 290" of the crew. The data management system 10 automatically populates the report with the crew members' names and their "in times," which are taken from the call sheet 130. Without the data management system 10, the AD has to find each crew member as they are leaving the set to learn their "out time 290," since different departments finish at different times after wrap. Often, this information is not received until the following day, when he will ask the crew member what time they wrapped the night before. If the AD guesses the times on the report, and these guesses are incorrect, not only will the daily cost reports be incorrect, but there will be a problem when the payroll company gets the crew member's timecard which differs from the production information.

The payroll company cannot adjust a worker's timecard, so this causes a delay in the process while the discrepancy is checked. The data management system 10 allows the departments to enter their "out times 290" into the computer as they finishing for the day. Not only is the information timely (no waiting until the next day) but the information is accurate, since the information comes from the crew member himself. The data management system 10 at this point starts the timecard report, which means the crew member does not have to manually keep a list of his times that week, since that information always resides locally on his computer. At the end of the week, the crew member enters that day's "out time 290" and generates the timecard which is sent directly to the accounting department where the data management system 10 generates the payroll 280.

Without the data management system 10, when the production report 220 goes into accounting, they must manually translate the information on the report into costs. The data management system 10 performs this task automatically, saving the accounting department a great deal of work. The data management system 10 also inputs these costs into a cost report 310 that checks for variances between actual costs and budgeted costs. The data management system 10 flags these variances. The AD is also responsible for the call sheet 130. While the production report 220 is a reflection of today's costs, the call sheet 130 is the projection of tomorrow's costs. The call sheet 130 typically contains information on the scenes that will be shot the next day, the page count of those days, the story days involved, the sets involved, the locations involved, the cast needed, a list of extras needed, a very brief breakdown of necessary props, wardrobe, etc, and the advance schedule. On the back of the call sheet 130, each crew member is listed and their specific call time is given. General notes, such as "bring wet weather gear since we will be producing rain effects" can also appear.

Without the data management system 10, the AD inputs all this information separately. The data management system 10 creates the call sheet 130 automatically. Since the schedule 120 already exists, the data management system 10 pulls the scenes meant to be shot for that day. If there was a scene that was not finished the day before, that also automatically appears on the call sheet 130. The page count information is accurate since the data management system 10 keeps track of any partial page count (without the data management system 10, it is rare that call sheets 130 that reflect partial scenes show accurate page count). All the script breakdowns 110 for the scheduled scenes are accessible because the data management system 10 references everything by scene. Therefore, the actors and their character names which are needed are automatically listed. Without the data management system 10, the limited "breakdown 110" information that appears on the call sheet 130 comes from the AD's breakdown 110 and is not extensive. However, the data management system 10 is able to populate the report with each department's actual breakdown 110 (which makes the document much more meaningful). The props listed reflects the props that actually will be used, rather than the AD's concept of what might be used. The advance schedule also appears automatically.

In the data management system 10, all the crew is listed automatically on the call sheet 130 and a global call time is set. The AD changes individual calls times manually if he wants a department or person to come in earlier or later. However, the data management system 10 allows the AD to create specific rule sets (such as "the call for the assistant cameraman is always Vz hour earlier than the main call, unless doing so puts him in turnaround"). This way, such alterations appears automatically, as well as preventing inadvertent turnaround invasion.

Without the data management system 10 of the present invention, the call sheet 130 is not published until camera wrap, since the call time is often not determined until then. However, it is helpful for departments to view this document earlier, to start planning for the next day. This is often not allowed because of the fear of alternate versions of the call sheet 130 being in circulation that could cause confusion as to the real call time. The data management system 10, however, allows the departments access for viewing this document during the day as the call sheet 130 is formulated since it is clearly marked as a non-official version. When the call sheet 130 is officially published, the data management system 10 clearly marks the call sheet 130 as published. This can't be done without the data management system 10 since the production is relying on a paper based system, and therefore waits until the last minute to make the necessary copies. If the call sheet 130 is printed prematurely, each call sheet 130 has to be manually marked with a notation such as "All calls pushed Vi hour" if things change. Sometimes, two versions of the call sheet 130 are printed up, ready to distribute, and the time that the company wraps determined which call sheet 130 is used. However, this runs the risk of the wrong call sheet 130 getting into circulation and causing confusion. Without the data management system 10, the call sheet 130 must be approved by the production manager. This requires that a courier delivers the AD's version to the office for the production manager's perusal and then returns it to the set. The AD's version is then sent back again to make the copies for distribution. The data management system 10 submits the call sheet 130 directly from the field to the production manager in the office who annotates it and sends the call sheet 130 back to the AD. This allows for greater communication between the AD and the production manager, and facilitates more informed decisions being made.

The data management system 10 distributes the call sheet 130 to each department and indicates those users' call time at the top of the sheet. Thus, individuals don't have to search through the crew list for their specific call time. Without the data management system 10, it is easy to mistakenly identify one's own call time if it differs from the majority.

An Appendix comprises pages 1-15 which shows exemplary templates or customizable "views" of the information presented to specific departments and/or users in accordance with a preferred embodiment data management system 10 of the present invention that is directed towards film and television production. Appendix page 1 illustrates an exemplary template view of the information presented as a Producer View by the data management system 10. Appendix page 2 illustrates an exemplary template view of the information presented as a Director View by the data management system 10. Appendix page 3 illustrates an exemplary template view of the information presented as a Studio View by the data management system 10. Appendix page 4 illustrates an exemplary template view of the information presented as a Script Supervisor View by the data management system 10. Appendix page 5 illustrates an exemplary template view of the information presented as an Editor View by the data management system 10. Appendix page 6 illustrates an exemplary template view of the information presented as a Production Man View by the data management system 10. Appendix page 7 illustrates an exemplary template view of the information presented as a Production Design View by the data management system 10. Appendix page 8 illustrates an exemplary template view of the information presented as an Art Department View by the data management system 10. Appendix page 9 illustrates an exemplary template view of the information presented as a Make Up/Hair View by the data management system 10. Appendix page 10 illustrates an exemplary template view of the information presented as a Wardrobe Department View by the data management system 10. Appendix page 11 illustrates an exemplary template view of the information presented as a Visual EFX View by the data management system 10. Appendix page 12 illustrates an exemplary template view of the information presented as an Ad View by the data management system 10. Appendix page 13 illustrates an exemplary template view of the information presented as a Lab View by the data management system 10. Appendix page 14 illustrates an exemplary template view of the information presented as a Grip View by the data management system 10. Appendix page 15 illustrates an exemplary template view of the information presented as an Electric View by the data management system 10.

In other preferred exemplary embodiments, the present invention is a networked data management system 10 that is specifically tailored for use with businesses which include, but are not limited to, tele-medicine, oil and gas exploration, international construction, disaster relief, and distance learning/education. A preferred embodiment of the present invention aids these industries in issues of mobility, data transmission and management, collaboration, security, access control, data verification, synchronization and replication, and ease of use, as well as other issues.

Specifically, in tele-medicine, uses of preferred exemplary embodiments include tele- radiology, which involves digital medical images (CAT scans, CT scans, mammography, PET scans and the like). Other tele-medicine applications include remote consultations, which involve videoconferencing with collaboration and markup of medical images and real-time remote diagnostics data from medical instruments. Further, still other tele-medicine applications include nomadic medicine, which involves mobile care with specialist consultations. In this regard, medical images are shared with remote specialists. In oil and gas exploration, a preferred embodiment of the present invention preferably takes readings, images and data on site at a potential drilling location and transmits this information for expert analysis. Images, video, and other data created during the oil excavation process are shared with engineers, executives, or specialists at various locations. Additionally, in the international construction arena, a preferred embodiment of the present invention is preferably utilized for site surveys, architectural drawing, engineering blueprints, and project scheduling software. While in disaster relief, a preferred embodiment of the present invention is utilized preferably for logistical data procurement and the tracking of vital supplies, remote communications, and services. Finally, in distance learning/education, a preferred embodiment of the present invention is preferably utilized for multimedia distribution, access, and real-time collaboration, including videoconferencing and data dissemination. Moreover, many aspects of the present invention that have been discussed above in the context of entertainment production are applicable in other markets as well. These include multimedia content management and distribution, management and distribution of data, security with need to know access, and replication and synchronization of data in multiple geographically dispersed locations. Preferably, data is accessed tlirough a web browser, allowing for ease of use. Input data in each of these scenarios is checked for validity against a set of business rules, as well as against other correlated data. Any discrepancies are highlighted to the appropriate person or people for quick resolution. These other markets may also utilize the communications services being offered to the entertainment production industry, including videoconferencing, real-time video, telephony over satellite, and Internet access. Images and video relevant to each of these industries are also able to be shared and discussed in real-time with versions of the annotation and collaboration tools being created for entertainment production.

Although the invention has been described in language specific to computer structural features, methodological acts, and by computer readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific structures, acts, or media described. Therefore, the specific structural features, acts and mediums are disclosed as exemplary embodiments implementing the claimed invention.

Furthermore, the various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. Those skilled in the art will readily recognize various modifications and changes that may be made to the present invention without following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.

Claims

WHAT IS CLAIMED IS:

1. A computer system for integrated information and data management, the

system comprising:-

a plurality of data collection nodes in a meshed network each including at least one

computing station, wherein data is input into the at least one computing station and

transmitted between collection nodes, said data being input and reviewed by relevant

specialists, thereby reducing errors and redundant data entry;

a transmission/reception medium configured to transfer information between

collection nodes using a data transfer protocol, said transfer of information including

collecting disparate data and selectively disseminating data across the system to users at

computing stations according to user identification, hardware identification, data clearance

level, and data release authority;

wherein the collection nodes link disparate data, validate data upon entry into the

system against pre-defined criteria or previously entered data, notify appropriate users of any

data discrepancies, intelligently sort, filter and initiate dissemination of data using logical

structures.

2. The computer system of claim 1, wherein at least one data collection node is

defined as a primary data collection node that facilities data synchronization.

3. The computer system of claim 1, wherein the system maintains a given

reporting structure and the collection nodes link related data to intelligently automate data

reporting to the computing stations.

4. The computer system of claim 1 , wherein the collection nodes receives data in

reports incoming from the computing stations that is sorted and analyzed to create distinct

reports that are outgoing to predetermined computing stations, and wherein each report in the

collection nodes dynamically builds dependencies to other reports according to pre-defined

criteria.

5. The computer system of claim 1, wherein the collection nodes present data in

an individualized template format to each specific user in the computing stations.

6. The computer system of claim 1, wherein only the data from the collection

nodes and functions relevant to a specific user are presented to said user when said user logs

onto a computing station of the system.

7. The computer system of claim 1, wherein the system protects sensitive data by

making said data visible only to a user with a proper access level, and wherein there is no

indication to users without the proper access level that data is being withheld.

8. The computer system of claim 1, wherein certain data is identified as locked

and unavailable to all but authorized users until said data is released by an authorized user.

9. The computer system of claim 1, wherein a change made to data in the system

prompts the collection nodes to intelligently scan all remaining data to determine if any

remaining data is affected by said change.

10. The computer system of claim 9, wherein users receiving data that was subject

to changes are notified of said changes and any possible associated problems resulting from

said changes.

11. The computer system of claim 1 , wherein linkages between different sets of

data within the system are customizable, thereby providing automatic updating when a

change occurs to one or more data elements in the system.

12. The computer system of claim 1 , wherein the data managed by the system is

selected from a group consisting of information, text, voice, audio, video, images, and their

digital counter parts.

13. The computer system of claim 1 , wherein the system predicts probable

outcomes and monitor events for variances using data compilation analysis.

14. The computer system of claim 1, wherein the system tracks physical assets,

and correlates and tracks physical assets to other derivative forms of the physical assets.

15. The computer system of claim 1, wherein groupings of data and supersets of

data are customizable through assignment of custom rule sets.

16. The computer system of claim 1, wherein the transmission/reception medium

comprises at least one satellite.

17. The computer system of claim 1 , wherein the transmission/reception medium

is selected from a group consisting of fiber optic cables, modems, cable modems, cable

routers, digital subscriber lines (DSL), asymmetrical digital subscriber lines (ADSL), Tl (or

fractions thereof), T2 (or fractions thereof), T3 (or fractions thereof), local area networks

(LAN), wide area networks (WAN), microwave networks, line of sight lasers, intranets, and

the Internet.

18. The computer system of claim 1 , wherein the data managed by the system is

selected from a group consisting of film and television production, pre-production, and post-

production data.

19. The computer system of claim 1 , wherein the data managed by the system is

medical related data.

20. The computer system of claim 1 , wherein the system utilizes a browser based

interface with the computing stations for standardization across platforms.

21. The computer system of claim 1 , wherein the system includes broadband

satellite links for transmitting text, data, and still and moving images at high-definition and

standard definition resolutions.

22. A process for networked data management that gathers disparate data, reduces

redundant data entry, and efficiently disseminates data, the process comprising: collecting data from at least one computing station in a meshed network and storing

said data in another computing station in the network;

validating data upon entry into the network against pre-defined criteria or previously

entered data;

checking data entered from different computing stations in the network for

discrepancies and notifying appropriate users at their computing stations in the network;

intelligently sorting, filtering, and linking data in accordance with logical structures;

and

distributing data and derivatives of said data across the network to computing stations

and users according to pre-selected criteria.

23. The process of claim 22, wherein the pre-selected criteria for distributing data

and derivatives of said data across the network to computing stations and users is selected

from a group consisting of user identification, hardware identification, data clearance level,

and data release authority.

24. The process of claim 22, wherein a given reporting structure is maintained in

the network and related data is linked such that data reporting to the computing stations is

intelligently automated.

25. The process of claim 22, wherein data in incoming reports from the computing

stations is sorted and analyzed to create distinct outgoing reports that are transmitted to

predetermined computing stations within the network, and wherein each report in the network

dynamically builds dependencies to other reports according to pre-defined criteria.

26. The process of claim 22, wherein the network presents data in an

individualized template format to each specific user in the computing stations.

27. The process of claim 22, wherein only the data and functions relevant to a

specific user are presented to said user when said user logs onto a computing station of the

network.

28. The process of claim 22, wherein the network protects sensitive data by

29. The process of claim 22, wherein certain data is identified as locked and

unavailable to all but authorized users until said data is released by an authorized user.

30. The process of claim 22, wherein a change made to data in the network

prompts scanning all remaining data to determine if any remaining data is affected by said

change.

31. The process of claim 30, wherein users receiving data that was subj ect to

changes are notified of said changes and any possible associated problems resulting from said changes.

32. The process of claim 22, wherein linkages between different sets of data

within the network are customizable, thereby providing automatic updating when a change

occurs to one or more data elements in the network.

33. The process of claim 22, wherein data managed by the network is selected

from a group consisting of information, text, voice, audio, video, images, and their digital

counter parts.

34. The process of claim 22, wherein the network predicts probable outcomes and

monitor events for variances using data compilation analysis.

35. The process of claim 22, wherein the network tracks physical assets, and

correlates and tracks physical assets to other derivative forms of the physical assets.

36. The process of claim 22, wherein groupings of data and supersets of data are

customizable through assignment of custom rule sets.

37. The process of claim 22, wherein the transmission/reception medium

comprises at least one satellite.

38. The process of claim 22, wherein data is collected and distributed by a

transmission/reception medium selected from a group consisting of fiber optic cables,

modems, cable modems, cable routers, digital subscriber lines (DSL), asymmetrical digital

subscriber lines (ADSL), Tl (or fractions thereof), T2 (or fractions thereof), T3 (or fractions thereof), local area networks (LAN), wide area networks (WAN), microwave networks, line

of sight lasers, intranets, and the Internet.

39. The process of claim 22, wherein the data managed by the network is selected

from a group consisting of film and television production, pre-production, and post-

production data.

40. The process of claim 22, wherein the data managed by the network is medical

related data.

41. The process of claim 22, wherein the network utilizes a browser based

interface with the computing stations for standardization across platforms.

42. The process of claim 22, wherein the network includes broadband satellite

links for transmitting text, data, and still and moving images at high-definition and standard

definition resolutions.

43. A computer program product readable by a computing system and encoding a

computer program of instructions for executing a computer process for an interconnected data

management system, said computer process comprising:

collecting data from at least one location in a network and storing said data in another

location in the network;

entered data; checking data entered from different locations in the network for discrepancies and

notifying appropriate users at locations in the network;

and

distributing data or its derivatives across the network to predetermined locations and

users according to pre-selected criteria.

44. The computer program product of claim 43, wherein the pre-selected criteria

for distributing data and derivatives of said data across the network to computing stations and

users is selected from a group consisting of user identification, hardware identification, data

clearance level, and data release authority.

45. The computer program product of claim 43, wherein a given reporting

structure is maintained in the network and related data is linked such that data reporting to the

computing stations is intelligently automated.

46. The computer program product of claim 43, wherein data in incoming reports

from the computing stations is sorted and analyzed to create distinct outgoing reports that are

transmitted to predetermined computing stations within the network, and wherein each report

in the network dynamically builds dependencies to other reports according to pre-defined

criteria.

47. The computer program product of claim 43, wherein the network presents data

in an individualized template format to each specific user in the computing stations.

48. The computer program product of claim 43, wherein only the data and

functions relevant to a specific user are presented to said user when said user logs onto a

computing station of the network.

49. The computer program product of claim 43, wherein the network protects

sensitive data by making said data visible only to a user with a proper access level, and

wherein there is no indication to users without the proper access level that data is being

withheld.

50. The computer program product of claim 43, wherein certain data is identified

as locked and unavailable to all but authorized users until said data is released by an

authorized user.

51. The computer program product of claim 43, wherein a change made to data in

the network prompts scanning all remaining data to determine if any remaining data is

affected by said change.

52. The computer program product of claim 51 , wherein users receiving data that

was subject to changes are notified of said changes and any possible associated problems

resulting from said changes.

53. The computer program product of claim 43, wherein linkages between

different sets of data within the network are customizable, thereby providing automatic

updating when a change occurs to one or more data elements in the network.

54. The computer program product of claim 43, wherein data managed by the

network is selected from a group consisting of information, text, voice, audio, video, images,

and their digital counter parts.

55. The computer program product of claim 43 , wherein the network predicts

probable outcomes and monitor events for variances using data compilation analysis.

56. The computer program product of claim 43, wherein the network tracks

physical assets, and correlates and tracks physical assets to other derivative fonns of the

physical assets.

57. The computer program product of claim 43, wherein groupings of data and

supersets of data are customizable through assignment of custom rule sets.

58. The computer program product of claim 43, wherein the

transmission/reception medium comprises at least one satellite.

59. The computer program product of claim 43, wherein data is collected and

distributed by a transmission/reception medium selected from a group consisting of fiber

optic cables, modems, cable modems, cable routers, digital subscriber lines (DSL), asymmetrical digital subscriber lines (ADSL), Tl (or fractions thereof), T2 (or fractions

thereof), T3 (or fractions thereof), local area networks (LAN), wide area networks (WAN),

microwave networks, line of sight lasers, intranets, and the Internet.

60. The computer program product of claim 43, wherein the data managed by the

network is selected from a group consisting of film and television production, pre-production,

and post-production data.

61. The computer program product of claim 43, wherein the network utilizes a

browser based interface with the computing stations for standardization across platforms.

62. The computer program product of claim 43, wherein the network includes

broadband satellite links for transmitting text, data, and still and moving images at high-

definition and standard definition resolutions.