IE20170071A1 - A data and content transfer and work flow management system - Google Patents

Abstract

A data and content transfer system has a send and receive components, in which the receive component pulls data and content from the send component and integrates the data and content site in a receiving system, and prompts and control activities involving use of the data and content at the receiving site. The transfer system includes a template component used by both the send and receive components, the template component governing how the received data and content is to be stored; structure of the received data and content; and integration of received data and content into a work flow component of the transfer system. An analytics system tracks all aspects of the transfer and receipt. The content and data may be for technical transfer for manufacture of a pharmaceutical, biotechnology, or medical device product. The template component is programmed to store a set of data and content for subsequent use in a next transfer. Also importantly, an analytics component tracks movement of data and content from the send component to the receive component by receiving updates from a project management component, and tracks milestone data from the workflow component, and to raise alerts if process data is not transferred by target times. <Figure 3>

Description

INTRODUCTION Field of the Invention The invention relates to transfer of content and data from one system to another and to use of the data and content in the receiving system. The content and data may be generally referred to as “information” or “knowledge”. The content and data may be for technical transfer for manufacture of a pharmaceutical, biotechnology, or medical device product.

Prior Art Discussion US6397036 and US6669485 describe systems, methods and program products for collaborative learning. They provide for remote access (e.g. via video conferencing), the use of interactive training materials, and the retention of these materials for offline learning, future consultation of indefinite on-going use.

US8589414 describes a computer implemented system and method for providing a community and collaboration platform for transfer of knowledge, tangible assets, intangible assets and information assets. In this system, experts provide knowledge which is parsed into structured information within a system, which than can be made selectively available to users.

US7809671 and US8069134 describe rapid knowledge transfer among workers, based around transfers related to specific applications. A plan and engagement site is generated for each instance of a transfer, using a wizard, templates and best practices. Users and roles, for experts providing knowledge transfer and consultants receiving knowledge transfer, are defined and access controlled according to security needs.

Objectives of the Invention The invention is directed towards providing an improved method and system for data and 30 content transfer. The invention further describes that 2D or 3D devices can be used to transfer, analyse, organise and manage data. -2SUMMARY OF THE INVENTION According to the invention, there is provided a data and content transfer system for transfer of data and content from a sending system to a receiving system, the transfer system comprising a send component, and a receive component configured to pull data and content from the send component, to integrate the data and content in a receiving system, and to prompt and control activities involving use of the data and content at the receiving system, wherein said send and receive components comprise: a work flow component configured to interface with the receiving system, a template component used by both the send and receive components, said template component governing: how the received data and content is to be stored in a receiving system; structure of the received data and content in a receiving system; and integration of received data and content into the work flow component; a collaboration component; a project management component; and an analytics component; wherein the work flow component and the template component, are distributed across the send and receive components to set a rule configuration for use by a receiving system of the received data and content, in which the workflow component implements settings provided by the template component, wherein the template component is configured to set access control level to transferred data and content both initially and with progressive changes as said data and content are used by a receiving system, wherein the send and receive components are configured to interface with the collaboration component to provide workspaces for functions of sending and receiving systems, wherein the template component is configured to store a set of data and content for subsequent use in a next transfer, and wherein the analytics component is configured to: track movement of data and content from the send component to the receive component by receiving updates from the project management component, track milestone data from the workflow component, and to raise alerts if process data is not transferred by target times. -3 In one embodiment, the template component is configured to set per-workspace access control criteria.

In one embodiment, the analytics component is configured to: track access control by receiving updates from a collaboration component and an access control component, and to perform assessment of performance at the receiving system which can help with productivity and process improvement.

Preferably, the system comprises a rules-based management component configured to dynamically present workspaces of the send and receive components according to conditions, either separately, or partially merged, or fully merged.

In one embodiment, the template component contains libraries of content document frameworks, predefined workflows for operation of the receiving system after a transfer, and project roles for each category of transferred data and content.

In one embodiment, the receive component is configured to pull data from laboratory or manufacturing equipment of a sending organisation.

Preferably, the receive component is configured to pull said data from a laboratory information management system.

In one embodiment, the send component is configured to buffer said equipment data for managed transfer.

In one embodiment, the system is configured to operate as a source of documents and data to allow continual assessment, learning, and performance improvements at the receiving site.

In one embodiment, the system is configured to, in a receiving system: automatically pull data and content and install said data and content in selected structures of the receiving system; and set up work flow configurations of the receiving system to use the received data and content. -4In one embodiment, the system is configured to progress different data and content streams at different rates and to create dependencies between streams.

Preferably, the receive component is configured to manage resource allocations during and after a transfer, and to establish peer relationships across sending and receiving organisations.

In one embodiment, the system is configured to act as a record of responsibilities for audit and traceability, to set access controls and role definitions for a security model, and to manage handover of activities from one worker to another. In one embodiment, the receive component is configured to retain data for a period of years after a transfer is complete.

In one embodiment, the system is configured to generate and manage mapping between a sending organisation and a receiving organisation whereby two individual data units (T2, T3) are merged into a single data unit (R2T3), and dependent data units are reordered accordingly, and in which a data unit (T4) is split into two data units (T4.R1, T4.R2) in the receiving organisation, and said data units are tagged in the receiving organisation, such that the mapping can also be carried out in reverse as required.

In one embodiment, the project management component is configured to interface with the collaboration component and the workflow component.

In one embodiment, the system comprises an access control component configured to manage access to facilities of the collaboration component. Preferably, the collaboration component is configured to feed events to the analytics component, which processes them and generates notifications back to the collaboration component.

In one embodiment, the system further comprises an organising component configured to determine static and dynamic characteristics of the collaboration component, supported by the template component for static parts and the rules-based management component for the dynamic parts.

In one embodiment, the receive component is configured to retain received data and content in a structured repository, in which artefacts including documents, communications, milestones, -5equipment data, regulatory forms, training materials provided by a sending organisation are preserved in a layout in terms of workspaces and in formats that are understood and chosen by the receiving organisation to best fit their own needs, and not necessarily the same, nor required to be the same as the layout and formats of the sending organisation.

Preferably, the access control component is configured implement controls on a functional level, in which access is based on an intersection according to set theory of the function with the role.

In one embodiment, the system is configured to contain a code library of conversion procedures, which are capable of converting data from one format to another.

In one embodiment, the conversion procedures are chained, so that it is not necessary to provide a conversion from every source format to every destination format, in which a source format may be converted to an intermediate format, which is further converted to the destination format.

In one embodiment,: the collaboration component is supported by the workflow component and the project management component which are integrated with it, the collaboration component is configured to receive a feed of raw data from an industrial data processing system, access to facilities of the collaboration component is determined by the access control component, the collaboration component is configured to feed events to the analytics component, which is configured to processes them and to generate notifications back to the collaboration component, and the transfer system comprises an organising component configured to determine static and dynamic characteristics of the collaboration component, supported by the template component for the static parts and the rules-based management component for the dynamic parts.

We also describe a data and content transfer method performed by a system including a send component and a receive component, in which the receive component pulls data and content from the send component and integrates the data and content in a receiving system, and prompts and controls activities involving use of the data and content at the receiving site, and a work flow component, a template component, a collaboration component, and an analytics component, and -6in which the work flow component and the template component are distributed across the send and receive components, and the method comprises the steps of,: the work flow component interfacing with the receiving system, the template component being used by both the send and receive components, said template component governing: how the received data and content is to be stored in a receiving system, structure of the received data and content in a receiving system; and integration of received data and content into the work flow component to set a rule configuration for use by a receiving system of the received data and content, in which the workflow component implements settings provided by the template component, the receive and template components setting access control level to transferred data and content both initially and with progressive changes as said data and content are used by a receiving system, the send and receive components interfacing with the collaboration component to provide workspaces for functions of sending and receiving systems, the template component storing a set of data and content for subsequent use in a next transfer, and the analytics component tracking movement of data and content from the send component to the receive component by receiving updates from a project management component, and tracking milestone data from the workflow component, and to raise alerts if process data is not transferred by target times In one embodiment, the analytics component performs the steps of: tracking access control by receiving updates from a collaboration component and an access control component, and performing assessment of performance at the receiving system which can help with productivity and process improvement.

In one embodiment, the receive component pulls data from laboratory or manufacturing equipment of a sending organisation.

In one embodiment, the send and receive components transfer data and content from one or more sending system to a plurality of receiving systems, by providing a separate instance of the send and receive components for each sending and receiving system. -Ί In one embodiment, the system progresses different data and content streams at different rates and to create dependencies between streams.

In one embodiment, the receive component manages resource allocations during and after a transfer, and establishes peer relationships across sending and receiving systems.

In one embodiment, the system acts as a record of responsibilities for audit and traceability, setting access controls and role definitions for a security model, and manages handover of activities from one worker to another.

In one embodiment, the system generates and manages mapping between a sending organisation and a receiving organisation whereby two individual data units (T2, T3) are merged into a single data unit (R2T3), and dependent data units are reordered accordingly, and in which a data unit (T4) is split into two data units (T4.R1, T4.R2) in the receiving organisation, and said data units are tagged in the receiving organisation, such that the mapping can also be carried out in reverse as required.

In one embodiment, the collaboration component feeds events to the analytics component, which processes them and generates notifications back to the collaboration component.

In one embodiment, the receive component is configured to retain received data and content in a structured repository, in which artefacts including documents, communications, milestones, equipment data, regulatory forms, training materials provided by a sending organisation are preserved in a layout in terms of workspaces and in formats that are understood and chosen by the receiving organisation to best fit their own needs, and not necessarily the same, nor required to be the same as the layout and formats of the sending organisation.

In one embodiment, the data and content which is transferred comprises manufacturing technology data and content including source code, configuration files, key performance data, control parameters, and raw data directly from sending organisation manufacturing and laboratory systems; and the transfer system installs in the receiving system the source code, configuration files, key performance, control parameters and raw data directly into the receiving system including a receiving manufacturing and laboratory systems. -8We also describe anon-transitory computer readable medium comprising software code for performing operations of a method of any embodiment when executing on a digital processor.

Information can be transferred, received and viewed either in 2D devices - laptops, tablets etc. The information can also be shared using a 3D device (e.g. Virtual devices such as Oculus and Samsung gear VR). This has the advantage of confidentially sharing information when working with others (e.g. while travelling). Generating, storing and sharing 3D technical information such as manufacturing process lines in 3D - aids understanding and can be used for training purposes.

In one embodiment, the receive component is configured to retain received data and content in a structured repository, where all of the documents, communications, milestones, equipment data, regulatory forms, training materials and other artefacts provided by a sending organisation, are preserved in a layout in terms of workspaces and in formats that are understood and chosen by the receiving organisation to best fit their own needs. They are not necessarily the same, nor required to be the same as the layout and formats of the sending organisation. The receiving site can also share information and data via 3D device which can be different to information shared by the sending site.

In one embodiment, the send and receive components are configured to interface with a collaboration component to provide workspaces for functions of the sending and receiving systems. Collaborative component can include 2D and 3D devices, which is particularly useful when sharing 3D video content for visual learning.

Additional Statements According to the invention, there is provided a data and content transfer system comprising a send component and a receive component, in which the receive component is configured to pull data and content from the send component and to integrate the data and content in a receiving system, and to prompt and control activities involving use of the data and content at the receiving site.

In one embodiment, the transfer system includes a template component used by both the send and the receive components, said template component governing: how the received data and content is to be stored; structure of the received data and content; and -9integration of received data and content into a work flow component of the receiving system.

In one embodiment, the receive and template components are configured to set access control levels to transferred data and content both initially and with progressive changes as said data and content are used by a receiving system.

In one embodiment, the system further comprises a collaboration component, and the send and receive components are configured to interface with the collaboration component to provide workspaces for functions of the sending and receiving systems.

In one embodiment, the template components set per-workspace access control criteria, and provide efficient transfer and receipt by storing a basic set of data and content for subsequent use in a next transfer.

Preferably, the system comprises: a work flow component, and a template component, and said components are distributed across the send and receive components to set rule configuration for use by the receiving system of the received data and content, in which the workflow component implements settings provided by the template component.

In one embodiment, the system comprises an analytics component configured to: track movement of data and content from the send component to the receive component by receiving updates from a project management component, track milestone data from the workflow components, and to raise alerts if process data is not transferred by target times, track access control by receiving updates from a collaboration component and an access control component, and to perform assessment of performance at the receiving system which can help with productivity and process improvement.

In one embodiment, the system comprises a rules-based management component configured to dynamically present workspaces of the send and receive components according to conditions, either separately, or partially merged, or fully merged. - 10In one embodiment, the template component contains libraries of content document frameworks, predefined workflows for operation of the receiving system after a transfer, and project roles for each category of transferred data and content.

Preferably, the receive part is configured to pull data from laboratory or manufacturing equipment of a sending organisation. In one embodiment, the send component is configured to buffer said equipment data for managed transfer.

In one embodiment, the system is configured to operate as a source of documents and data to allow continual assessment, learning and performance improvements at the receiving site.

In one embodiment, the system is configured to, in a receiving system: automatically pull data and content and install said data and content in selected structures of the receiving system; and set up work flow configurations of the receiving system to use the received data and content.

In one embodiment, the system is configured to progress different data and content streams at different rates and to create dependencies between streams.

In one embodiment, the receive component is configured to manage resource allocations during and after a transfer, establish peer relationships across sending and receiving organisations.

In one embodiment, the system is configured to act as a record of responsibilities for audit and traceability, set access controls and role definitions for a security model, and manage handover of activities from one worker to another.

In one embodiment, the receive component is configured to retain data for a period of years after a transfer is complete.

In one embodiment, the system is configured to generate and manage mapping between a sending organisation and a receiving organisation whereby two individual data units (T2, T3) are merged into a single data unit (R2T3), and dependent data units are reordered accordingly, and in -11 which a data unit (T4) is split into two data units (T4.R1, T4.R2) in the receiving organisation, and said data units are tagged in the receiving organisation, such that the mapping can also be carried out in reverse as required.

In one embodiment, the system comprises a collaboration component, a project management component, and a workflow component which interface with each other.

In one embodiment, the system comprises an access control component and access to facilities of the collaboration component is determined by the access control component. In one embodiment, the collaboration component is configured to feed events to an analytics component, which processes them and generates notifications back to the collaboration component.

In one embodiment, the system further comprises an organising component configured to determine static and dynamic characteristics of the collaboration component, supported by the template component for static parts and a rules-based management component for the dynamic parts.

In one embodiment, the receive component is configured to retain received data and content in a structured repository, where all of the documents, communications, milestones, equipment data, regulatory forms, training materials and other artefacts provided by a sending organisation, are preserved in a layout in terms of workspaces and in formats that are understood and chosen by the receiving organisation to best fit their own needs. They are not necessarily the same, nor required to be the same as the layout and formats of the sending organisation.

In one embodiment, the access control component is configured implement controls on a functional level, in which access is based on an intersection according to set theory of the function with the role.

In one embodiment, the system is configured to contain a code library of conversion procedures, which are capable of converting data from one format to another. Conversion procedures may be chained, so that it is not necessary to provide a conversion from every source format to every destination format, in which a source format may be converted to an intermediate format, which is further converted to the destination format. -12In another aspect, the invention provides a data and content transfer method performed by a system including a send component and a receive component, in which the receive component pulls data and content from the send component and integrates the data and content in a receiving system, and prompts and controls activities involving use of the data and content at the receiving site.

In one embodiment, the transfer system includes a template component used by both the send and the receive components, said template component governing: how the received data and content is to be stored; structure of the received data and content; and integration of received data and content into a work flow component of the receiving system.

In one embodiment, the receive and template components set access control level to transferred data and content both initially and with progressive changes as said data and content are used by a receiving system.

In one embodiment, the send and receive components are configured to interface with a collaboration component to provide workspaces for functions of the sending and receiving systems.

In one embodiment, the template components set per-workspace access control criteria, and provide efficient transfer and receipt by storing a basic set of data and content for subsequent use in a next transfer.

In one embodiment, the system comprises a work flow component, and a template component, and said components are distributed across the send and receive components to set rule configuration for use by the receiving system of the received data and content, in which the workflow component implements settings provided by the template component.

In one embodiment, the system comprises an analytics component which performs the steps of: tracking movement of data and content from the send component to the receive component by receiving updates from a project management component, -13 tracking milestone data from the workflow components, and raising alerts if process data is not transferred by target times, tracking access control by receiving updates from a collaboration component and an access control component, and performing assessment of performance at the receiving system which can help with productivity and process improvement.

Other embodiments of the method include the steps performed by the components of the system as defined above in any system embodiment.

In another aspect, the invention provides a non-transitory computer readable medium comprising software code for performing operations of a method of any embodiment when executing on a digital processor.

DETAILED DESCRIPTION OF THE INVENTION Brief Description of the Drawings The invention will be more clearly understood from the following description of some embodiments thereof, given by way of example only with reference to the accompanying drawings in which :Fig. 1 is a high level diagram illustrating a data and content transfer system of the invention; Fig. 2 is a high level diagram illustrating logical and physical separation of parts of the system; Fig. 3 illustrates domain-partitioned and time-ordered transfers; Fig. 4 illustrates major steps for transfers performed by the system; Fig. 5 illustrates pseudo code for a transfer; and Fig. 6 shows the major steps for work flow management in the receiving system. -14Description of the Embodiments A system of the invention comprises servers with digital processors executing software and which are linked via local or wide area networks, including satellite links.

The system performs a transfer of information between a sending system and a receiving system. The term “transfer” is intended to mean both sending and receiving. Also, the terms “information” and “knowledge” cover both data and content. The term “data” is intended to mean information which is normally stored in databases and may for example be used in process control for manufacturing. It could be, for example, provided directly by equipment such as sensors in a laboratory or factory. The term “content” is intended to mean information which is in narrative form to be read by humans to describe things such as processes and procedures, and also video, virtual or 3D, or live streaming information.

The term “component” in this specification means a subsystem of the overall transfer system, implemented in hardware with digital processors and software, and the components are part of the two major subsystems or components of the overall transfer system, the send and receive components. The send and receive components are sometimes referred to as send and receive “parts”. The sending and receiving systems are not part of the transfer system of the invention, rather they are part of the sending and receiving sites.

The content and data may be for technical transfer for manufacture of a pharmaceutical, biotechnology, or medical device product. Such transfers commonly involve many thousands of steps across a wide range of aspects including specifying manufacturing equipment, validation of such equipment, health and safety requirements, environmental conditions, regulatory requirements for each step or sequence of steps, Thus, not only are there many steps involved, but there is considerable cross-functional complexity.

Such transfer requires assessment needs to be made of the receiving site process equipment in detail as compared to the sending site process equipment flow. As described in more detail below, templates are used to automatically trigger and compare information to significantly reduce risk in the transfer process. -15In more detail, a technology transfer may happen when a pharmaceutical company changes from an existing manufacturing site to a new manufacturing site. More generally, it can also involve a move from one process train to another, or perhaps from one facility to another.

Examples of information to be transferred include: Packaging line trials - if a product is new to the site, it is crucial to perform line trials, filling the product into the proposed bottle or cap.

Stability indicating methods should already be in place, enabling onsite transfer against the protocol signed off by the client.

Cleaning validation needs to be assessed, and specifications and batch records need to be written.

A Health and Safety Review needs to be conducted to ensure the ability to safely handle the product.

Also, the sending site may provide a list of equipment, makes and models for production, including filling, packing and control.

Other information includes qualification and validation documentation, drawings, manuals, maintenance logs, calibration logs; and procedures for things such as equipment set-up, operation, cleaning, maintenance, calibration, and storage Factors to be compared between sending (transfer) site and the receiving site include: minimum and maximum capacity, material of construction, critical operating parameters, critical equipment components such as filters, screens, and temperature/pressure sensors, critical quality attribute, range of intended use, Transfer of the information involves having information about the receiving site recorded, such as location of equipment in the receiving site’s manufacturing facility, and building of the receiving site.

The information be transferred may also include process maps or flow charts of the manufacturing process, flows of personnel and material, data representing impact of including -16new products on the receiving site, any modification of existing equipment that may be needed to be documented in the transfer project plan.

In the transfer system of the invention detailed templates are used to ensure transfer of information from the technical transfer site to the receiving site, and a receiving site template is automated to ensure all information is received. For example, the receiving site template can prompt to get the following information from a processing reactor based on information required and provided by Sending site: capacity, pressure, temperature, agitator speed, process flow (liquid) rate, and pump capacity and rates.

Detailed information such as the above can be obtained, matched and any variances flagged The transfer is according to a template which sets in a pre-configured manner: (a) how the sent and received data and content is to be stored, (b) the structure of the transferred content, particularly documents; (c) the structure of the receiving systems in terms of work flow processing of the received data and content.

The transfer system includes software in the receiving system, and so there is in the receiving system a group of hardware servers and other data devices with processors which are programmed to perform the role of the receiving and sending side of the transfer system.

The system performs transfers of long and complex information for subjects such as the pharmaceutical, biotech and medical device industries where the transfer and embedding of knowledge at receiving site can take several years. The system allows the receiving site to gather, learn, manage and use the complex technical data required to ensure processes can be effectively earned out or products efficiently manufactured. The system allows the sending site to gather, manage and transfer information in a controlled and efficient way to a partner site which can be an internal or external organisation to that of the sending site. -17The system performs receiving and embedding of complex information over an extended period: push and pull. Information can be requested from the receiving site. The system of the invention is particularly effective at receiving complex and large-scale information, and ensuring that the information is embedded in the receiving system in a manner for optimum use. For example, it may be used by the receiving system for management and control of a manufacturing process in a highly regulated environment. Also, the system is configured for transfer to multiple receiving sites.

Advantageously, the template component is programmed to store a set of data and content for subsequent use in a next transfer. Also importantly, an analytics component tracks movement of data and content from the send component to the receive component by receiving updates from a project management component, and tracks milestone data from the workflow component, and to raise alerts if process data is not transferred by target times, The software in the receiving system is configured: (a) to automatically pull the required data and content and (b) to install it is the required structures of the receiving system; and (c) to set up work flow configuration of the receiving system to use the received data and content.

The above structure (c) includes the transfer system receiving component automatically establishing links to rules in the receiving system for work flows using the received data and content.

The rules are configured to: - allow controlled access of the receiving system to the data and content, and - over time, reduce the levels of access by the sending system as changes are made by the receiving system to the data and content.

The access control is performed at least partly by a real time analytics component which runs in the receiving system. The analytics component collects alerts from the work flow rules as they execute during use by the receiving system of the transferred data and content. -18The analytics component also generates reports indicating the access control changes, and also generates triggers for additional data and content to be transferred.

In this specification, the term “Technology Receipt” represents the activities and goals of a receiving organisation who takes responsibility for the success of a “Technology Transfer”, and encompasses not only the Technology Transfer itself, but the additional activities undertaken by the receiving organisation to ensure that the information remains useful after the sending organisation has disengaged from the transfer process and any subsequent processing or development of the received knowledge. The Technology Transfer is the transferred data and content and work flow rule configurations. The receiving part can provide data, video and technical details to assist the sending site to prepare for a successful transfer. Video can include a virtual tour of the receiving site. Live streaming can allow immediate transfer of knowledge between sending and receiving sites.

The following are some of the characteristics of Technology Receipt: (a) Manages transfers that extend over years. (b) Manages large volumes of data. (c) Manages complex segmented and structured data. (d) Ability to progress different streams at different rates. (e) Ability to create dependencies between streams. (f) Directly drives the activities of the receiving organisation, e.g. manufacturing. (g) Uses multiple means of input, of transfer and of output, including web, messaging, video conferencing telephone and industrial data processing including 3D, virtual devices. (h) A goal here is to provide effective control, supervision, and collaboration from the receiving organisation's point of view. 3D can also provide a greater understanding of a complex process or equipment. And can highlight differences between the sending and receiving sites. (i) Another goal is to achieve a receipt which meets a measurable standard of quality.

The transfer system manages receipt of knowledge by an organisation (the receiving organisation) from one or more other organisations (the sending organisations). Multiple receipts may occur from a single or multiple sending organisations simultaneously. Also the knowledge received will be both complex and broad in scope (ranging from e.g. environmental aspects, to manufacturing aspects, to quality aspects). -19A Send Part is a component, or “subsystem”, available to a sending organisation (either physically or logically), and the Receive Part is a component available to the receiving organisation. These Parts allow the systems to prepare effectively for the transfer, interfacing at both ends with a number of subsystems for the collection of input information and embedding received information. These Parts interface with a Collaboration subsystem, a Workflow Management subsystem, and a Project Management subsystem. The Project Management subsystem organises and structures the transfer to ensure that over the extended period of the transfer, the correct sequence of tasks and events are completed, and helps to identify prerequisites and dependencies on the sending organisation.

The Project Management subsystem drives the success of a specific current receipt, the analytics component gathers data which may be used to improve the overall receipt process across receipt activities and over a longer period of time. Alerts can be automated to ensure that the project remains on or ahead of schedule.

Content and data is collected from interactive sessions, including file upload, or by direct connection between the Send Pail and e.g. file sharing or e-mail mechanisms, or by direct input from industrial equipment, for the transfer of, for example, manufacturing data. Content and data in the Receive Part may be delivered via interactive session, may be retrieved from a central repository, and may be directly input to drive industrial production.

Collaboration supports are provided both in the Send Part and in the Receive Part. The system can incorporate such facilities as threaded discussions (similar to e-mail), chat facilities, e-mail integration, live streaming, and/or audio-visual and 3D virtual systems for communications and for training, and a document repository for permanent storage of all of the documents required by the receiving organisation.

The Receive Part also manages resource allocations during and after the receipt, establishing peers and other personal relationships across the various sending organisations and the receiving organisation. This provides a number of facilities: (1) acts as a record of responsibilities and for audit and traceability, (2) forms the basis of access controls and role definitions for a security model, and (3) simplifies the handover of activities from one worker to another (either in the sending or receiving organisation) in terms of handing over key relationships to other workers. -20Due to the transfer system, the receiving organisation can enjoy better and more economic receipts through being able to integrate data and content into their existing processes rather than having to deal with a variety of different knowledge transfer systems used by sending organisations.

Receipt may involve multiple sending organisations, who may be at different stages of transfer and levels of disclosure. In particular, one organisation's receipt documentation must not be visible to another. This is achieved by the separation of the Send Part, for which each sending organisation will have at least one instance, and which is therefore physically or logically separate from other sending organisation’s Send Parts, thereby ensuring confidentiality and security of the transferred information Fig. 1 shows the system, which consists of two main parts, and a number of subsystems. The Send Part gathers information from the sending organisation. Advantageously, this involves control of confidential information before sending it to the receiving organisation. Such access control is managed by approving documents sent via a workflow. Confidential information can be further protected especially if people are in transit by reviewing data including video using a 3D device that can be viewed by an individual.

The Send Part ensures that requirements and interdependencies are met. In this, the send and receipt is directed by an Organising component, supported by a Template component, which defines the static elements of the system overall, and a Rules-based Management component, which handles the dynamic aspects (e.g. document conversion) of the send and receipt overall. Together they implement the requirements and interdependencies for each send and receipt. The Organising component is connected to individual systems such as PCs, laptops, tablets, 3D devices such as the Oculus and HTC vive etc. for interactive access and update. It can also be driven (in the preferred pharma embodiment) by industrial input, collecting raw data directly from for example manufacturing and laboratory equipment. This has the additional benefit of reducing human error, reducing cost and shortening the time to gather the pre-requisites for transfer. This includes the collection of data from the sending organisation’s internal systems, such as e-mail, share-point or EDS for live sharing of information via video.

The Receive Pail interfaces with a Project Management component which progressively -21 transfers data from the sending organisations to the Receive Part, according to its availability and completion. This data is organised effectively into folders and by category as determined by the structure of the receiving organisation, to meet their needs and corporate standards, which may differ from the sending organisation. Through this mechanism, there is a clear separation between transfer data that is “in preparation” and data that has been formally transferred. The Receive Part furthermore retains the data long after the transfer is complete, and remains as the receiving organisation's authoritative reference for the knowledge transfer, even in the case when the personnel involved in the original transfer differ from the personnel actively using the transferred expertise at a later date.

The Receive Part also manages collaboration tools and archives collaborative data such as discussions, chats, e-mails, audio-visual exchanges and screen captures, for example.

This system may reside within the sending organisation as shown here, or in alternate configurations as shown in Fig. 2. The receive part can send video/live information such as operational equipment to sending part.

Fig. 2 shows three possible configurations of the parts of the sending system.

In the first case, the parts are physically separate and the Send Part resides in the sending organisation, and the Receive Part resides in the receiving organisation. In the second case, the parts remain logically separate, but may be co-located externally to both parties. For example, this could be sited in a data centre and be accessed as a “cloud” service. In the third case, the parts remain logically separate, but may be co-located within the receiving organisation. In a fourth case the Send and Receive Parts are in the same system, for example if the transfer is within a single organisation.

In all cases, there may in fact be many instances of the Send Part corresponding to multiple transfers from a single sending organisation, or multiple transfers from multiple transferring organisations.

Fig. 3 illustrates the importance of identifying interdependencies between data units provided by the sending organisation and received by the receiving organisation. For an effective transfer and receipt to occur, not only the primary data units, but also all identified, dependent data units, -22including any nested dependencies, are be made available and mapped onto the receiving organisation formats and structures in a controlled manner, and according to workflows and tracked by the project plan. In this way, the receiving organisation can define a number of milestones to be achieved, track progress and quickly identify any blockers and automated or manual intervention triggered as required.

Fig. 3 shows mapping between the sending organisation and the receiving organisation whereby two individual data units (T2, T3) are merged into a single data unit (R2T3), and dependent data units are reordered accordingly. Data unit T4 is split into two data units T4.R1 and T4.R2 in the receiving organisation. These documents are tagged in the receiving organisation, such that the mapping can also be carried out in reverse as required, e.g. R2T3.1 can be seen to belong to T3 in sending organisation; T4.R1 and T4.R2 can be seen to belong to the same sending data unit T4.

Fig. 4 illustrates the components as described in more detail below. At a high level, it illustrates the dependencies between them: - The Collaboration component is the most immediately visible component, supported by the Workflow component and the Project Management component which are integrated with it - In some cases, raw data may be fed directly to and from the Industrial Data Processing component to the Collaboration component - Access to the facilities of the Collaboration component is determined by the Access Control component - The Collaboration component feeds events to the Analytics component, which processes them and generates notifications back to the Collaboration component.

The Organising component determines the overall static and dynamic characteristics of the Collaboration component, supported by the Template component for the static parts and the Rules-based Management component for the dynamic parts. In Fig. 4, the learning function may in some embodiments include visual 3D learning, assisting with providing context to complex equipment setup, which is key for fields of technology such as life sciences.

Fig. 5 illustrates how the overall structure of the project is determined from a Project Profile, represented by one or more inter-related documents that describe the initial project state, and -23how this assembles all of the project artefacts in their various forms.

Fig. 6 illustrates automated decision-making flow through the system, whereby the individual components provide data to analytics, which builds insights, which are reconciled against a Project Profile, and supported by static and dynamic project libraries, thereby allowing an organising component to notify events to users, update the system and trigger automated actions within the system.

In the transfer system of the invention Knowledge Receipt by a receiving organisation recognises that knowledge transfer is typically a process managed by the sending organisation. Knowledge Receipt considers the transfer from the perspective of the receiving organisation, and acknowledges that there will be activities required in the receiving organisation which go beyond the traditional concerns of knowledge transfer. It recognises that a period of time may be required before the recipient is ready to make use of the received knowledge, at which point the sending organisation may have long completed the knowledge transfer from their perspective.

Also, the transfer system uses a Template, which provides a pre-existing framework for creating a new knowledge receipt process, and greatly simplifies the on-boarding of the sending organisation.

The knowledge (data and content) sent and received will typically be segmented and arranged into hierarchies, reflecting specific domains of expertise, and particular units within the sending and receiving organisations. Each segment of knowledge or organisational unit is generically referred to as a Function, which represents a subset of the transfer and receipt.

Knowledge transfer is a process whereby the knowledge concerning some domain which is held by one organisation is passed to another organisation a closed loop system with a goal on embedding technology at the receiving site. We refer to the first organisation as the sending organisation, and the second organisation as the receiving organisation. This can be a complex process in the case knowledge is represented in multiple forms. Some of these may be relatively easy to transfer - for example specifications, designs, manuals, and tools. Others may be more difficult, such as tacit knowledge, activities, conventions.

Knowledge receipt is the process by which the receiving organisation manages its pail of a -24knowledge transfer, and furthermore reorganises, structures, and transforms the transferred knowledge so that it becomes fully integrated in and adapted to the receiving organisation. Knowledge receipt ensures that the knowledge is not only successfully transferred but it is also retained within the receiving organisation in a highly usable format, which may be further developed within the receiving organisation using an iterative process.

The transfer system manages knowledge receipt using some or all of the following features. - utilising a plan or map of the received knowledge in the form of a template, - making readily and conveniently available and securing for the future all of the received knowledge in its various forms to maximise its utility to the receiving organisation, - transforming the knowledge to terms which are compatible with the receiving company - adaption of technical specifications to the standards system used by the receiving company, - restructuring the received data to fit the receiving organisational structure - preparation of training systems for employees, - translation of documentation, - providing measurement systems to present an objective status of the state of the receipt to the receiving company, - providing analytics to interactively guide and adapt the receiving process and to highlight any problems or shortfalls, and to support overall process improvement across multiple knowledge receipt activities, - support the need for access controls to the knowledge, including access controls between the sending and receiving organisations and also between different sending organisations. - demonstrably meeting the standards and regulations applicable to the knowledge received and applied.

As the same class of knowledge may undergo receipt multiple times, from different sending organisations, there will be some, and potentially quite a lot of commonality across these from the point of view of the receiving organisation. This commonality can be captured in the form of a Project Profile, which allows the receiving organisation to initiate and configure a new knowledge receipt project quicker, with reduced effort and more reliably. The Project Profile consists of one or more inter-related files, with sufficient structure to permit automated processing, which will typically be organised as a hierarchical data structure, which might further be typically represented using an existing standard for such structures, such as YAML, -25JSONorXML.

As illustrated in the example of FIG 5, the Project Profile unites various elements that define the system. It identifies through references key resources of the project in the form of static files or live video stored in and accessible from the Template component. It links in logic elements, such as workflows, document conversion algorithms and rules from the Rules-based Management component. Based on these it then defines user roles, access controls, workflow and project plans. It then combines these in an overall framework which represents the overall project structure in terms of workspaces, how resources are allocated to these, who may access them and how they are processed between the Send Part and the Receive Part. Ultimately the Project Profile is input into the Organising component, which is then responsible for applying the intent of the Project Profile across the system and to instantiate and maintain the project structure across the sending organisation and the receiving. The specific syntax and semantics used here, and the use of XML as a supporting syntax, is purely exemplary.

Overview of the Components The Send Pail and a Receive Part are sub-divided into components, and these components are logically distributed in some cases across the above two top-level parts. These components are: - Collaboration component - Workflow component - Analytics component - Project Management component - Access Control component - Rules-based Management component - Template component - Organising component - Industrial Data Processing subsystem - Training and Learning subsystem Send Part and Receive Part In the following the various components are understood to be partitioned into two separate Parts, one for the Send Part, and one for the Receive Part. The mapping of access roles, groups of users, collaborative workspaces and functional sub-divisions is derived initially from the Template, customised for the specific project and then managed and directed by the Rules-based -26Management component. The Send Part is largely concerned with the collection of knowledge from the sending organisation and transmission to the receiving organisation, whereas the Receive Part is largely concerned with the management of the receipt of knowledge from the sending organisation, and the further processing of that knowledge to better meet the needs of the receiving organisation. Also, the sending organisation can send information/video/live information to convince sending organisation that they are the right organisation to whom the transfer should be made.

An important aspect of the Receive Part not addressed by existing technology transfer systems is that it retains the received data in a structured repository, where all of the documents, communications, milestones, equipment data, regulatory forms, training materials and other artefacts provided by the sending organisation, are preserved in a layout (in terms of workspaces) and in formats that are understood and chosen by the receiving organisation to best fit their own needs (and not necessarily the same, nor required to be the same as the layout and formats of the sending organisation). These are further retained in this useful layout and these formats long after the sending organisation has ceased to be involved with the receiving organisation. This provides advantages to the receiving organisation, in that they don't have to (and won't in general) commence acting on the received technology immediately to ensure that the receipt is bedded in, and also it is possible that the users who take up the activities which depend of the received knowledge (e.g. manufacturing) in the receiving organisation aren't necessarily the same as the users who were involved in the actual transfer phase.

It is also possible that the receiving organisation may have to perfect its own processes before fully receiving the technology. This means that an iterative process will be required that only or mostly involves the receiving organisation; and that the various components in the Receive Part will support this ongoing work in the form of additional collaboration, workflows, project milestones, notifications and analytics, which (largely or actually) don't involve the sending organisation.

To that end, the Receive Part supports extra capabilities beyond merely knowledge transfer; for example it can incorporate systems supporting education, such as a video streaming component; it can provide an issue tracking (or trouble ticket) component to track issues that arise in the iterative process, so they may be distributed to the appropriate users in turn for development and resolution, so that they can be prioritised and the most important items resolved first, and so that -27a record can be built up which may usefully be reviewed to even further optimise the process in subsequent projects.

Collaboration Component This is a collaboration component which includes elements of known collaboration systems (such as Alfresco, Drupal, Microsoft Share-point, and Atlassian Confluence). The Collaboration component is responsible for supporting the work of transfer and receipt by allowing the sending and receiving organisation to work together in a structured environment. Each function in the sending and receiving organisation will have access to a Workspace, where they may collaborate using the various tools of the component, supported by the other components. The Collaboration component implements a security model defined by the Access Control component which ensures that workspaces, documents and other artefacts within the system are accessible only to the relevant parties in each organisation and also that projects are fully separated from one another, whether they involve the same sending organisations, or different sending organisations. The relationships between the two organisations is defined within the Template component and directed by the Rules-based Management component. This furthermore connects to the Project Management component to track overall progress of the transfer, and the Analytics component, to measure the effectiveness of the transfer and receipt, and to identify any opportunities for better execution. Some activities in will be guided by workflows which are managed by the Workflow component.

In a typical example, a user in the sending organisation will connect to the Collaboration component using a Web browser, and will see a shared virtual workspace in which they can upload documents, communicate with their peers (by e-mail or instant messaging), set and receive actions, tasks and deadlines, and co-ordinate the collective work of transfer and receipt. The layout and access controls on the Send Part will reflect the organisational arrangements and division of responsibilities within the sending organisation, whereas the layout and access controls of the Receive Part will reflect the organisational arrangements and division of responsibilities within the receiving organisation. This will be further extended to support the special features as described in the other sections of this document, including Workflows, Project Management, and Analytics, The mapping between the two organisations and the management of transfer and receipt of knowledge is described in the sections Rule-based Management Component and Template Component both of which are implemented across the Send Part and the Receive Part as described in the section Organising Component. -28Workflow Component In some cases, there will be a requirement for a set of steps to be carried out, each of which represents a specific milestone in a sub-activity of the transfer and receipt. Workflow Management systems exist already to create workflows tailored to specific tasks. Such systems are often combined with a Collaboration system, and the Workflow component here is integrated with the Collaboration component in this manner. For example, Activiti is a workflow management system which uses the BPEL (Business Process Execution Language) standard to define and implement automated workflow management, and is integrated with the Alfresco collaboration management system. These existing capabilities are extended however to provide the necessary integration into the Project Management and Analytics components, so that key milestones within a workflow are automatically incorporated into the project plan, along with metrics for successful and timely completion, so that delays in delivery can be identified by senior management and they can engage if necessary to remove the identified blocking point.

The existing workflow design capabilities (such as tools based on BPEL) are further extended to integrate with the Analytics component, to determine which workflows are being used and which not, possibly indicating that certain activities have been altogether neglected, have been complete by another means, or have been undertaken without use of workflow management. This can be used to trigger actions such as consultancy to identify underlying causes, or training (using the Learning component) to help staff better avail of the system.

Workflows are implicitly multi-user; in particular workflows support the ability for a user to mark a flow complete, and for another user to sign-off on the work as closed.

Analytics Component The Analytics component tracks all aspects of the transfer and receipt. A particular point of focus is the movement of data from the Send Part to the Receive Part, and a further point of focus is the access, processing, workflow activity and project management state of workspaces in the Receive Pail, in terms of measuring and validating that Technology Receipt has been successful. It operates to flag impending milestones to ensure that future activities are complete to allow the transfer to remain on or ahead of a timeline.

Data is extracted by or forwarded to the Analytics components using well-known existing mechanisms such as database queries (e.g. SQL), notifications (e.g. XMPP), web analytics (e.g. -29Javascript, PHP,...).

In the case of the Workflow component, each milestone achieved, and signed off, will be notified to the Analytics component, together with target and actual dates. In the case of the Collaboration component, logistical data such as level of login activity of users of each organisational unit, documents uploaded, and communications events (numbers of e-mails) will be notified to the Analytics component. In the case of the Project Management component, overall project progress as well as details of individual task streams will be notified to the Analytics component, both in terms of the baseline goals, and actual progress. Analytics can provide critical predictive information such as sending site recommends a step to take 2 months. System flags that this step typically takes 3 months based on historical data stored.

Advantageously, in some embodiment, all of the complex data resides in this system. Examples include; Example 1=3 years of project time - analytics system flags several areas where the project did not meet timelines and where time could be saved e.g. 3 months (10% reduction).

Example 2 = Laboratory process runs were unsuccessful by one technical expert and captured in the system - this data flagged a requirement for further training for the person involved Example 3 = data assessment indicated that there were 50 Safety documents transferred but only 5 engineering documents - possible opportunity to streamline the safety documents for future process transfer Example 4 = sending site projects 2 months to complete a project activity. System flags to user that the step in question typically takes 3 months (predictive) thus allowing a more accurate project timeline to be developed.

The preceding represents some important examples of analytical data collected by the Analytics component. Clearly there could be many other interesting data points, as would be appreciated by those skilled in the art.

The Analytics component can be further set up with parameters that determine when automatic notifications should be raised to identify potential issues that may need to be addressed. For example a minimum level of login activity could be defined. Variations in communications can -30be highlighted, for example a lull in activity compared to previous history. Correlations can be built up whereby certain events occur naturally with others (a reduction in detailed activity after completion of a project milestone) and sequencing can also be examined (determining if all workflow activities are complete prior to a project milestone being crossed). Rules can be defined within the Analytics component which look for individual events, aggregated events (e.g. a count or sum of values from individual events), trends (e.g. a change in the rate of progress), correlated events (several events which must occur within a time-frame) and sequenced events (where events occur in a certain order). These are identified and automatically notified by the Analytics component.

This knowledge can be notified in a structured way to senior management in the receiving organisation, so that they can engage in a productive way with the sending organisation, and also on an individual level with staff responsible for a particular function both in the sending and receiving organisations. Project completed on or ahead of time can increase sales and or reduce costs.

Notifications can take place using existing mechanisms, such as e-mail, SMS, web alerts, and provide the supporting data via links and attachments.

While it is also conceivable that notifications could be raised by individual components (e.g. the Project Management component could notify tasks running late), the benefit in placing responsibility for notifications with the Analytics component is that it can draw on a holistic view, rather than being confined to data from a single component.

Project Management Component The Project Management component tracks progress and detects any points where the project has fallen behind expected performance levels. It facilitates the elimination of blockers and delivers automatic notifications via the Analytics component. Also, it can accelerate decision making through better integration of cross functional (and very diversified, e.g. EHS, manufacturing, quality) team.

The Project Management component includes some existing technology which defines a project baseline (tasks, with durations and assigned resources) and then records actual progress against the baseline. This will include a graphical representation (Gantt charts) of the project for easy -31 review, and will support typical project management activities such as scheduling, dependency analysis, resource planning and critical path analysis. However this technology is extended by integration to support the specific features of sending and receiving technology knowledge.

The Project Management component is integrated into the Collaboration component, so that each user of the system can track the progress of their area of the project. This is further integrated into the Access Control component to ensure that data relating to the overall project is only selectively displayed to each user as is relevant to them. This can be configured according to the project needs so that, in certain cases, all users may have visibility of the entire project, or they may have visibility across a major function, or possible only have visibility of the progress of activities within their own specific function. The project management component also contains critical information key to successfully transfer products such as pharmaceutical products, information required in a highly regulated environment.

The Project Management component is integrated in addition to the Analytics component, to expose key progress data for further processing. Notifications may be raised in response to the data delivered by the Project Management component.

Access Control Component The Access Control component serves to protect the transferred and received knowledge from a number of different perspectives. In the first instance, it protects the knowledge from access by unauthorised parties, such as external users and organisations not party to the transfer. In the second instance, it ensures that certain confidential knowledge is only presented to those users and at those times when access is granted, as determined by the Access Control component, in conjunction with the other components.

The Access Control component implements Role-based Access Control (RBAC) which defines access rights to the system in terms of specific roles (e.g. administrator, engineer, marketer, manager) and then each user of the system is assigned one or more roles. The rights of that user then become the union (as in set theory) of the rights of roles assigned.

The access rights concerned cover traditional resources, such as access to specific documents and workspaces, particular workflows, and operations. For example, an engineer role may be able to enter and complete a workflow, but a manager role may be required to sign-off the -32workflow as closed.

As well as a role-based approach, the Access Control component implements controls on a functional level. In this case, access is based on an intersection (as in set theory) of the function with the role. So an engineer role in a manufacturing function will not have access to resources that are available to the same engineer role in a legal function. This functional partitioning is implemented as a hierarchical system, in that it separates access to each function, and also separates access to each project, thereby ensuring in particular that projects carried out with differing sending organisations are kept separate from each other. Through this means, the power of RBAC, including derivatives such as hierarchical and constrained RBAC, can be combined flexibly with functional separation with authorisation levels.

The Access Control component in the system extends to controlling visibility not only of resources, but also influences the presentation of global data to the user. The Project Management component for example can present a view of project progress to all users, however detail can be selectively suppressed according to the access rights of the individual user. Not just the sending and receiving sites are secure - there is security between multiple receiving sites which allows the sending site to securely manage knowledge across a number of sites which can be internal or individual and separate companies.

Finally, the Access Control component enforces a separation between the Send Part and the Receive Part, so that transfer knowledge which is initially available to the sending organisation is not available to the receiving organisation until signoffs (as implemented by the Workflow Management component) have been completed, and also to ensure that received knowledge that is further developed and processed within the receiving organisation is accessible only to the receiving organisation and not to the sending organisation. Use of 3D devices can also provide extra security such as when travelling - experts can view information in a secure way and avoid pitfalls of the information being viewed by other parties - e.g. laptops being used on planes.

Rules-based Management Component The Rules-bases Management component, in conjunction with the Access Roles component and the Organising component, allows the separate workspaces of the Send Part and Receive Part to be presented as a single virtual workspace for all of the parties involved in collaboration. By partitioning these into a Send Part and a Receive Part, it is possible to address potential -33 differences between the sending organisation and the receiving organisation. We consider three examples here: (1) A specific function, whose knowledge is being sent and received, lies entirely within the domain of one organisational unit of the sending organisation. The same function is however split across two units of the receiving organisation. In this case the functional workspace is split in two and each assigned to the relevant organisational unit of the receiving organisation. The organisational unit in the sending organisation is given access to both functional workspaces. This may be presented as two distinct workspaces, or may be presented as a single combined workspace to the sending organisation. (2) A specific function, whose knowledge is being transferred and received, lies entirely within the domain of one organisational unit of the receiving organisation. The same function is however split across two units of the sending organisation. In this case the functional workspace is split in two and each assigned to the relevant organisational unit of the sending organisation. The organisational unit in the receiving organisation is given access to both functional workspaces. This may be presented as two distinct workspaces, or may be presented as a single combined workspace to the receiving organisation. (3) A specific first function, whose knowledge is being sent and received, lies within the domain of one organisation unit of the sending and receiving organisations. However the sending organisation unit also has responsibility for a second function, and the receiving organisation also has responsibility for a third function, where all three functions are different. In this case, the only workspace that is shared between the two organisational units will be the workspace related to the first function, although both the sending and receiving organisations will have also have access to workspaces related to the second and third functions respectively. This workspace may be presented as a distinct workspace for the first function only, or may appear as a first combined workspace for the sending organisation and a second combined workspace for the receiving organisation.

In all cases above, where workspaces are combined, where knowledge is entered into a combined workspace, the user will be requested to identify which of the functions the knowledge relates to, thereby ensuring that the knowledge is released only to the correct organisational unit in the peer organisation. -34It is the job of the Rules-based Management component to ensure that these relationships are enforced across the Send Part and the Receive Part, and in particular that documents are synchronised across the two Parts between the correct shared workspaces. Information is not just synchronised, but also the correct information is approved for transfer in either direction (to protect the confidentiality of the information).

It is also a task of the Rules-based Management component to carry out conversions of documents from formats used by the sending organisation to those used by the receiving organisation. The conversion is carried out automatically as the documents are uploaded. Both versions are stored; documents in the original fonnat are presented to the sending organisation in the original format and to the receiving organisation in the converted format once published. The documents may also be available in converted format to the sending organisation so that they may collaborate in the verification of the conversion if necessary.

Template Component The Template component provides the static elements of a transfer and receipt project. It defines the base layout of workspaces in the Receive Part, which will form the basis of a mapping from the Send Part defined in the Rules-based Management component, which is then adapted as needed for each project. The Template component also contains libraries of document frameworks, predefined workflows, baseline project plans, and standard project roles for each category of technology receipt which the receiving organisation engages in, which serve in part as a base for demonstrating and ensuring full regulatory compliance. As new categories of project arise, additions may be made to the library to provide new Templates. Templates are owned by the transferring system to allow them to be used for new projects (save time in setting up new projects) and for the benefit of the receiving site i.e. templates can be made available to the receiving site for their use and to help ensure that project can be completed on time.

The Template component also contains a code library of conversion procedures, which are capable of converting data from one format to another. Conversion procedures may be chained, so that it is not necessary to provide a conversion from every source format to every destination format. Instead a source format may be converted to an intermediate format, which is further converted to the destination format. The use of an intermediate format reduces the number of conversion procedures required, since if there are M destination formats, for each source format there would need to be M conversion procedures, one for each of the destination formats. Use of -35the intermediate format means that, for each source format, only one conversion procedure is required to the intermediate format.

Organising Component The purpose of the Organising component is to implement an event-driven mapping between the Send Part and the Receive Part, reflecting the transmission of knowledge from the sending organisation to the receiving organisation. In doing so it derives a base mapping from a Template, and is driven by the Rules-based Management component.

As described above, the Organising component will receive the Project Profile as input at project setup time, and will use this to instantiate the project across the various components, drawing on the existing resources of the Template component, the Rules-based Management component and the collaborative system.

As the Project Profile itself may be a complex document, or set of documents, as an alternative to manual construction, this may be produced as the output of a Design Tool, which has links to the Template and Rule-based Management components. These links can allow it e.g. to prepopulate fields with resource names, permit drag and drop linking and organisation, automatically generate references and can prefill data fields with default values, thereby making the task of creating a new Project Profile considerably easier.

The Template component defines the static elements of a transfer and receipt project. It provides the base layout of workspaces in the Send Part and Receive Pail. The Rules-based Management component provides the dynamic element of a transfer and receipt project. It defines the parameters for the conversion process of knowledge from the sending organisation to the receiving organisation.

It is the task of the Organising component to actually implement the static and dynamic mapping using the other components by responding to events and drawing on the resources of the Template component and Rule-based Management component, always within the context of the Project Profile.

As an example, a user in the sending organisation uploads a document and tags it within the Collaboration component. Based on the Template, the Organising component knows a workflow -36is required for this type of document, so it engages the Workflow Management component to drive the document through the workflow. At some point, the document is signed-off by the sending organisation, resulting in an event to the Organising component, which makes the document available to the receiving organisation in the Receive Part. In the process of doing this, it will be employ the Rules-based Management component to do any required conversion of the document before publishing it to the Receive Part in the correct format, in the correct workspace, and via the Analytics component, notifying the correct users in the receiving organisation.

This type of process can equally well operate in the reverse direction, whereby the receiving organisation can prepare, approve and forward information to the sending organisation.

The Organising component depends on receiving key events, so it is notified of any new artefacts that enter the Send or Receive Parts, and it is also notified of any changes in status (e.g. workflow transition, project milestone reached) so it may engage both the Template and Rulesbased Management components to activate any required further automated processing.

Industrial Data Processing Component The process of collecting technology knowledge from the sending organisation and delivering to the receiving organisation can be simplified, and the accuracy of receipt improved, if they can be collected in a form that is directly driven by and directly drives manufacturing equipment in both organisations. The Industrial Data Processing component therefore fulfils two distinct roles: (i) in the Send Part, it is responsible for downloading source code, configuration files, key performance, control parameters and other raw data directly from the sending organisation manufacturing and laboratory systems; (ii) In the Receive Part, it is responsible for installing source code, configuration files, key performance, control parameters and raw data directly onto the receiving organisation's manufacturing and laboratory systems. As an example, Programmable Logic Controllers (PLCs) are widely used in the manufacturing sector to drive equipment from source code for example as defined in IEC 61131-3; where both organisations make use of the same PLCs, the program logic can be read directly from the sending organisation repositories, transferred to the receiving organisation, where the Rules-based Management component defines the routing to and destination where it will be downloaded directly onto the receiving organisation PLC equipment (or software repository which is used to drive the same PLC equipment). Configuration files may be encoded in any of a number of formats like XML, JSON or YAML or even a database (and so accessible in SQL format). -37Performance or control parameters may be stored in CSV or other structured text or binary file formats.

In cases where the organisation makes use of differing PLC (or other classes of) equipment, it implements an automatic conversion between the two formats, or at least a partially automatic conversion, which is completed manually. In this case the Template component must provide the necessary library procedures; rules must be added to the Rules-based Management component to define the type of conversion required, and the Organising component will then automatically implement the conversions as required, also initiating a workflow in the Receipt Part where further human intervention is required to complete any manual work.

It is quite possible that the sending organisation does not have the means to automate the collection process, or that it is not cost-effective for them to do so. In this case these artefacts can be uploaded by a manual process, but advantage will still exist on the receiving side, where as described above, they are directly installed onto the manufacturing equipment of the receiving organisation. It is more likely that this automation capability will be viable within the receiving organisation, as it is an assumption that they will conduct multiple technology receipts, and they will have commonalities, and it is a goal of this invention to provide a system which deliver benefits in this particular case.

Training and Learning Component Closely related to the Collaboration component, the Learning component encompasses all of the training elements of knowledge receipt, providing specific additional benefits contributing both to the actual quality of the receipt, as well as providing measurable evidence of the success of the receipt. Among these, it ensures that the knowledge receipt is not a once-off event, but knowledge can be received long after the transfer has completed.

Resources for training consist in general of two parts: - training materials - these are specific to each transfer and receipt they must be sourced from the sending organisation - they constitute part of the transferred and received knowledge can play a significant role in ensuring received knowledge can be passed on to new users in the receiving organisation even after the sending organisation is no longer actively -38participating in the process - training systems - these are provided by the Learning component and may include but is not limited to - video player - slide browser - automated examinations, live streaming, and AR.

The Learning component makes use of the capabilities of the other components. The Access Control component ensures training materials are made available to relevant users only. The Workflow Management component checks that training has been completed as an input to signoff and transfer processes. The Analytics component tracks the level of compliance with training goals, and can create notifications should actual performance lie outside certain bounds. The Collaboration component can play a key role in supporting an interactive learning environment, where users in both organisations support the training process.

As it is possible that the sending organisation and receiving organisation rely on different formats for training materials, e.g. different codecs, the Rule-based Management component can direct the conversion of formats (for example, an AVI format audio-visual file could be converted to an AVC format file). This is only required in cases where the facilities of the Learning cannot handle the formats used by the sending organisation directly.

The invention is not limited to the embodiments described but may be varied in construction and detail.

Claims (25)

1. , 170071 Claims

1. A data and content transfer system for transfer of data and content from a sending system to a receiving system, the transfer system comprising a send component, and a receive component configured to pull data and content from the send component, to integrate the data and content in a receiving system, and to prompt and control activities involving use of the data and content at the receiving system, wherein said send and receive components comprise: a work flow component configured to interface with the receiving system, a template component used by both the send and receive components, said template component governing: how the received data and content is to be stored in a receiving system; structure of the received data and content in a receiving system; and integration of received data and content into the work flow component; a collaboration component; a project management component; and an analytics component; wherein the work flow component and the template component, are distributed across the send and receive components to set a rule configuration for use by a receiving system of the received data and content, in which the workflow component implements settings provided by the template component, wherein the template component is configured to set access control level to transferred data and content both initially and with progressive changes as said data and content are used by a receiving system, wherein the send and receive components are configured to interface with the collaboration component to provide workspaces for functions of sending and receiving systems, wherein the template component is configured to store a set of data and content for subsequent use in a next transfer, and wherein the analytics component is configured to: track movement of data and content from the send component to the receive component by receiving updates from the project management component, track milestone data from the workflow component, and to raise alerts if process data is not transferred by target times. -402. A transfer system as claimed in claim 1, wherein the template component is configured to set per-workspace access control criteria.

2. 3. A transfer system as claimed in claim 2, wherein the analytics component is configured 5 to: track access control by receiving updates from a collaboration component and an access control component, and to perform assessment of performance at the receiving system which can help with productivity and process improvement. 10

3. 4. A transfer system as claimed in any preceding claim, wherein the system comprises a rules-based management component configured to dynamically present workspaces of the send and receive components according to conditions, either separately, or partially merged, or fully merged.

4. 5. A transfer system as claimed in any preceding claim, wherein the template component contains libraries of content document frameworks, predefined workflows for operation of the receiving system after a transfer, and project roles for each category of transferred data and content.

5. 6. A transfer system as claimed in any preceding claim, wherein the receive component is configured to pull data from laboratory or manufacturing equipment of a sending organisation. 25

6. 7. A transfer system as claimed in claim 6, wherein the receive component is configured to pull said data from a laboratory information management system.

7. 8. A transfer system as claimed in claims 6 or 7, wherein the send component is configured to buffer said equipment data for managed transfer.

8. 9. A transfer system as claimed in any preceding claim, wherein the system is configured to operate as a source of documents and data to allow continual assessment, learning, and performance improvements at the receiving site. -41 10. A transfer system as claimed in any preceding claim, wherein the system is configured to, in a receiving system: automatically pull data and content and install said data and content in selected structures of the receiving system; and 5 set up work flow configurations of the receiving system to use the received data and content. 11. A transfer system as claimed in any preceding claim, wherein the system is configured to progress different data and content streams at different rates and to create dependencies

9. 10 between streams.

10. 12. A transfer system as claimed in any preceding claim, wherein the receive component is configured to manage resource allocations during and after a transfer, and to establish peer relationships across sending and receiving organisations.

11. 13. A transfer system as claimed in claim 12, wherein the system is configured to act as a record of responsibilities for audit and traceability, to set access controls and role definitions for a security model, and to manage handover of activities from one worker to another.

12. 14. A transfer system as claimed in any preceding claim, wherein the receive component is configured to retain data for a period of years after a transfer is complete.

13. 15. A transfer system as claimed in any preceding claim, wherein the system is configured to 25 generate and manage mapping between a sending organisation and a receiving organisation whereby two individual data units (T2, T3) are merged into a single data unit (R2T3), and dependent data units are reordered accordingly, and in which a data unit (T4) is split into two data units (T4.R1, T4.R2) in the receiving organisation, and said data units are tagged in the receiving organisation, such that the mapping can also be carried 30 out in reverse as required.

14. 16. A transfer, system as claimed in any preceding claim, wherein the project management component is configured to interface with the collaboration component and the workflow component. -4217. A transfer system as claimed in any preceding claim, wherein the system comprises an access control component configured to manage access to facilities of the collaboration component.

15. 18. A transfer system as claimed in any preceding claim, wherein the collaboration component is configured to feed events to the analytics component, which processes them and generates notifications back to the collaboration component. 10

16. 19. A transfer system as claimed in any preceding claim, further comprising an organising component configured to determine static and dynamic characteristics of the collaboration component, supported by the template component for static parts and the rules-based management component for the dynamic parts. 15 20. A transfer system as claimed in any preceding claim, wherein the receive component is configured to retain received data and content in a structured repository, in which artefacts including documents, communications, milestones, equipment data, regulatory forms, training materials provided by a sending organisation are preserved in a layout in terms of workspaces and in formats that are understood and chosen by the receiving

17. 20 organisation to best fit their own needs, and not necessarily the same, nor required to be the same as the layout and formats of the sending organisation.

18. 21. A transfer system as claimed in any of claims 17 to 20, wherein the access control component is configured implement controls on a functional level, in which access is 25 based on an intersection according to set theory of the function with the role.

19. 22. A transfer system as claimed in any preceding claim, wherein the system is configured to contain a code library of conversion procedures, which are capable of converting data from one format to another.

20. 23. A transfer system as claimed in claim 22, wherein the conversion procedures are chained, so that it is not necessary to provide a conversion from every source format to every destination format, in which a source format may be converted to an intermediate format, which is further converted to the destination format. -43A transfer system as claimed in any of claims 17 to 23, wherein: the collaboration component is supported by the workflow component and the project management component which are integrated with it, the collaboration component is configured to receive a feed of raw data from an industrial data processing system, access to facilities of the collaboration component is determined by the access control component, the collaboration component is configured to feed events to the analytics component, which is configured to processes them and to generate notifications back to the collaboration component, and the transfer system comprises an organising component configured to determine static and dynamic characteristics of the collaboration component, supported by the template component for the static parts and the rules-based management component for the dynamic parts. A data and content transfer method performed by a system including a send component and a receive component, in which the receive component pulls data and content from the send component and integrates the data and content in a receiving system, and prompts and controls activities involving use of the data and content at the receiving site, and a work flow component, a template component, a collaboration component, and an analytics component, and in which the work flow component and the template component are distributed across the send and receive components, and the method comprises the steps of,: the work flow component interfacing with the receiving system, the template component being used by both the send and receive components, said template component governing: how the received data and content is to be stored in a receiving system, structure of the received data and content in a receiving system; and integration of received data and content into the work flow component to set a rule configuration for use by a receiving system of the received data and content, in which the workflow component implements settings provided by the template component, the receive and template components setting access control level to transferred data and content both initially and with progressive changes as said data and content are used by a receiving system, -44the send and receive components interfacing with the collaboration component to provide workspaces for functions of sending and receiving systems, the template component storing a set of data and content for subsequent use in a next transfer, and 5 the analytics component tracking movement of data and content from the send component to the receive component by receiving updates from a project management component, and tracking milestone data from the workflow component, and to raise alerts if process data is not transferred by target times 10 26. A transfer method as claimed in claim 25, wherein the analytics component performs the steps of: tracking access control by receiving updates from a collaboration component and an access control component, and performing assessment of performance at the receiving system which can help 15 with productivity and process improvement. 27. A transfer method as claimed in claims 25 or 26, wherein the receive component pulls data from laboratory or manufacturing equipment of a sending organisation. 20 28. A transfer method as claimed in any of claims 25 to 27, wherein the send and receive components transfer data and content from one or more sending system to a plurality of receiving systems, by providing a separate instance of the send and receive components for each sending and receiving system.

21. 25 29. A transfer method as claimed in any of claims 25 to 28, wherein the system progresses different data and content streams at different rates and to create dependencies between streams.

22. 30. A transfer method as claimed in either of claims 28 or 29, wherein the receive component 30 manages resource allocations during and after a transfer, and establishes peer relationships across sending and receiving systems.

23. 31. A transfer method as claimed in claim 30, wherein the system acts as a record of responsibilities for audit and traceability, setting access controls and role definitions for a 35 security model, and manages handover of activities from one worker to another. -4532. A transfer method as claimed in any of claims 25 to 31, wherein the system generates and manages mapping between a sending organisation and a receiving organisation whereby two individual data units (T2, T3) are merged into a single data unit (R2T3), and 5 dependent data units are reordered accordingly, and in which a data unit (T4) is split into two data units (T4.R1, T4.R2) in the receiving organisation, and said data units are tagged in the receiving organisation, such that the mapping can also be carried out in reverse as required. 10 33. A transfer method as claimed in any of claims 25 to 32, wherein the collaboration component feeds events to the analytics component, which processes them and generates notifications back to the collaboration component.

24. 34. A transfer method as claimed in any of claims 25 to 33, wherein the receive component is 15 configured to retain received data and content in a structured repository, in which artefacts including documents, communications, milestones, equipment data, regulatory forms, training materials provided by a sending organisation are preserved in a layout in terms of workspaces and in formats that are understood and chosen by the receiving organisation to best fit their own needs, and not necessarily the same, nor required to be 20 the same as the layout and formats of the sending organisation.

25. 35. A transfer method as claimed in any of claims 25 to 34, wherein the data and content which is transferred comprises manufacturing technology data and content including source code, configuration files, key performance data, control parameters, and raw data 25 directly from sending organisation manufacturing and laboratory systems; and the transfer system installs in the receiving system the source code, configuration files, key performance, control parameters and raw data directly into the receiving system including a receiving manufacturing and laboratory systems. 30 36. A non-transitory computer readable medium comprising software code for performing operations of a method of any of claims 25 to 35 when executing on a digital processor.