TWI857905B - Computer readable media, server and cross organizational project collaboration method the server implements - Google Patents

Abstract

A cross organizational project collaboration method, comprising: receiving a project connection instruction via a network for connecting a first project of a first organization to a second project of a second organization; receiving a first connection instruction from a first user computer used by a first user of the first organization for connecting a first form to the first project, wherein the first form is built according to a first form template of the first organization, wherein the first form template includes multiple second data fields; receiving a second connection instruction from the first user computer used by the first user for connecting the first form to the second project which is already connected to the first project.

Description

Computer-readable recording media, server, and cross-organizational project collaboration method implemented therein

This application relates to network information systems, and more particularly to methods and systems for sharing information across organizations.

Existing network information systems facilitate information sharing within an organization. Multiple users within an organization can access files within the organization through the network. For example, construction workers at a construction site use current smartphones and tablet computers to access files at any time in various work environments. These files may include self-checklists for work items, inspection reports of construction materials, work safety inspection reports, etc. Construction workers or supervisors do not need to fill out the above forms with pen and paper, nor do they need to scan paper forms into electronic files. Even if they are scanned into electronic files, it is difficult to search for each field.

However, these electronic files are stored in the information system controlled by the organization and cannot be shared externally. For example, since they belong to different organizations or companies, if the supervisor wants to access the form filled out by the construction personnel, he can only access the paper form in the office, or ask the construction personnel to print the electronic file into paper for sharing. Even if there is instant messaging software that can share files, the construction personnel must first retrieve the electronic file from the information system, download it, and then send it to the supervisor via email or instant messaging software. In other words, it is impossible to perform permission control and version control on the sharing of electronic files in the information system.

In view of this, there is an urgent need for a cross-organizational network information system that can provide file access, notification and/or to-do management functions within and across organizations, and provide a convenient collaborative environment for the daily operation of multiple large-scale collaborative projects involving hundreds or thousands of people across organizations or departments.

According to an embodiment of the present application, a cross-organizational project collaboration method is provided, which includes: receiving a project association instruction through a network to associate a first project corresponding to a first organization with a second project corresponding to a second organization; receiving a first association instruction issued by a first user corresponding to the first organization from a first user computer through the network to associate a first form with the first project, wherein the first form is established based on a first form template of the first organization or the first project, wherein the first form template includes multiple first data fields; and receiving a second association instruction issued by the first user from the first user computer through the network to associate the first form with the second project corresponding to the first project.

Preferably, in order to control whether the first form is shareable, the cross-organizational project collaboration method further includes: receiving a sharing instruction corresponding to the first form sent by the first user from the first user computer via the network; and setting the first form to be shareable.

Preferably, in order to allow the second user corresponding to the second project to read the second form, the cross-organizational project collaboration method further includes: receiving a read instruction corresponding to the first form sent by a second user corresponding to the second organization from a second user computer via the network; determining whether the second user is associated with the second project; and when the second user is associated with the second project, transmitting the first form to the second user computer via the network.

Preferably, in order to control whether the first form is shareable so that the second user corresponding to the second project can read the second form, the cross-organizational project collaboration method further includes: after receiving the read instruction corresponding to the first form, determining whether the first form is shareable; and when the first form is shareable, executing the above-mentioned step of determining whether the second user is associated with the second project.

Preferably, in order to determine whether the first user updates the first form at a specified location, the cross-organizational project collaboration method further includes: receiving an update command issued by the first user from the first user's computer via the network, for updating a location field among the multiple first data fields included in the first form, the location field including the location information of the first user's computer when the update command is issued.

Preferably, in order to allow the system to allow users who do not belong to any organization to collaborate, the cross-organizational project collaboration method further includes: establishing a control form based on a control form template related to the first organization, wherein the control form template includes multiple data fields; receiving a third association instruction issued by the first user from the first user computer via the network to associate the control form with the first project; receiving a fourth association instruction issued by the first user from the first user computer via the network to associate the control form with a third user, wherein the third user does not correspond to any organization; and transmitting the control form to a third user computer used by the third user via the network.

Preferably, in order to allow the system to allow third users who do not belong to any organization to collaborate, the cross-organizational project collaboration method further includes: establishing a control form based on a control form template related to the second organization, wherein the control form template includes multiple data fields; receiving a fifth association instruction issued by a second user associated with the second project from a second user computer through the network to associate the control form with the second project; receiving a sixth association instruction issued by the second user from the second user computer through the network to associate the control form with a third user, wherein the third user does not correspond to any organization; and transmitting the control form to a third user computer used by the third user through the network.

Preferably, in order to determine whether the third user updates the control list at a specified location, the cross-organizational project collaboration method further includes: receiving an update command issued by the third user from the third user computer via the network, for updating a location field among the multiple data fields included in the control list, the location field including the location information of the third user computer when the update command is issued.

Preferably, in order to provide the system with a function of automatically generating a form, the cross-organizational project collaboration method further comprises: receiving a summary instruction issued by the first user from the first user computer via the network, wherein the summary instruction corresponds to a summary form template, the first form and a second form, the second form is established according to a second form template of the first organization, the second form template includes a plurality of second data fields, the summary form template The invention comprises one or more induction rules and one or more induction data fields, wherein the induction rule is a method of induction according to at least one first data field among the plurality of first data fields and at least one second data field among the plurality of second data fields; and a induction form is established according to the induction form template and the induction rule contained therein, wherein the data in the induction data field of the induction form is generated by induction according to the induction rule.

According to an embodiment of the present application, a server for implementing the above-mentioned cross-organizational project collaboration method is provided, which includes: a network device for connecting to the network; and a central processing unit for executing instructions stored in a computer-readable memory to implement the above-mentioned cross-organizational project collaboration method.

According to an embodiment of the present application, a computer-readable recording medium storing a program is provided, wherein when the server loads and executes the program, the cross-organizational project collaboration method as described above can be completed.

According to the cross-organizational network information system provided by the present application, the server it contains and the cross-organizational project collaboration method it implements can simultaneously provide file retrieval, notification and/or to-do list management functions within and across organizations, and provide a convenient collaboration environment in the daily operation of multiple large-scale collaborative projects involving hundreds or thousands of people across organizations or departments.

This application will describe some embodiments in detail as follows. However, in addition to the disclosed embodiments, this application can also be widely applied to other embodiments. The scope of this application is not limited by these embodiments, but is subject to the scope of the subsequent patent application. In order to provide a clearer description and enable those familiar with the technology to understand the content of this application, the various parts in the diagram are not drawn according to their relative sizes, and the ratio of certain sizes to other related scales will be highlighted and exaggerated, and irrelevant details are not fully drawn in order to simplify the diagram. In addition, other steps unrelated to this application can be inserted into each step shown in each flow chart of this application. Unless there is a causal dependency, this application does not limit the execution order of each step.

Please refer to FIG. 1 , which is a block diagram of a network information system 100 according to an embodiment of the present application. The network information system 100 includes a server 110, a network 120 and a plurality of user computers 130. The network 120 may be a combination of one or more physical networks, which may include one or more interconnected wide area networks or telecommunications networks, and one or more access networks or local area networks connected to the wide area network or telecommunications network. The wide area network or telecommunications network may be a wired or wireless network provided by a telecommunications operator. For example, it may be the Internet, a wireless mobile network such as 3G/4G/5G/6G, or a satellite communication network of the Starlink or Iridium Project. The access network or local area network can be a wired or wireless local area network, such as a wired network that complies with the IEEE 802.3 series of protocols, or a wireless network that complies with the IEEE 802.11 series of protocols. The network 120 can transmit information between the server 110 and the user computer 130.

Please refer to FIG. 2 , which is a block diagram of a server 110 according to an embodiment of the present application. The server 110 may include a combination of one or more physical or logical computers, such as a server composed of virtual machines in one or more physical computers. In terms of software functions, the server 110 may include a database management system (DBMS) 210, an application/logic serving system (Application/Logic Serving System) 220, an interface system 230, and a Web interface system 240.

The database management system 210 may include a relational database management system, such as the common MySQL, Oracle, DB2, or a non-relational database management system, or even a simple spreadsheet system. It is used to store various forms and form templates, organizations, users, projects, and other related data of the network information system 100.

The application logic server system 220 may include a common application server and/or business logic system, such as Oracle's J2EE server and Microsoft's ASP.NET server. The application logic server system 220 may implement different applications or business logics, utilize the data in the database management system 210, and communicate with the user computer 130 through the interface system 230 and/or the Web interface system. For example, Enterprise JavaBeans and ASP programs may be used to implement the methods and steps provided by the present application, so as to perform various operations on the data in the database management system 210.

The interface system 230 may include a proprietary and/or industry standard transmission protocol compliant interface system for communicating with an application installed on the user computer 130. The web interface system 240 may communicate with a web browser installed on the user computer 130 using HTTP, HTTPS, HTML, etc., such as the common Apache Web Server.

The present application does not limit the software implemented by the server 110 to the above-mentioned three-tier architecture, and may also be composed of a single customized software package. However, in any case, a person with ordinary technical skills in the computer field can understand that the server 110 of the present application includes the ability to connect to the network 120, the ability to implement the methods and steps provided by the present application, and the ability to store related data.

Please refer to FIG. 3 , which is a block diagram of a user computer 130 according to an embodiment of the present application. The user computer 130 may be a wearable mobile device, a smart phone, a personal digital assistant, a tablet computer, a laptop computer, a desktop computer and/or any other form of computer. For example, the user computer 130 may be a computer of the Von Neumann architecture or a variation thereof.

The user computer 130 may include a central processing unit 310, a memory module 320, an input/output interface module 330, an output device 340, an input device 350, a storage device 360 and/or a network device 370. The central processing unit 310 includes at least one microprocessor, such as a microprocessor applicable to one of the RISC-V, x86, x64, ARM, and Alpha instruction sets, for executing instructions stored in the memory module 320, so as to control the user computer 130 through software such as an operating system and/or an application, and to use the operating system and/or the application to control the hardware to implement the methods and steps provided in the present application.

The input/output interface module 330 may be a proprietary or industry standard interface, such as a USB series, SATA series, SCSI series, PCI series, PCI-Express series, etc., for connecting the above-mentioned output device 340, input device 350, storage device 360 and/or network device 370. The output device 340 is used to output data outside the user computer 130, such as outputting corresponding signals such as sound, image, data, etc. Common output devices 340 include displays, speakers, printers, etc. The input device 350 is used to input data to the user computer 130. Common input devices 350 include touch pads, touch screens, keyboards, mice, microphones, cameras, satellite positioning devices, 2D or 3D scanners, etc. The storage device 360 includes non-volatile memory, such as hard drives, flash memories, optical disks, magnetic disks, etc. The network device 370 is used to connect to the network 120, such as an access network included in the network 120.

In one embodiment, the network device 370 can know the location of the user computer 130 through the location of the connected router and the location of the wireless base station. In addition, the operator of the wireless or satellite communication network can also use multiple base stations or satellites to triangulate the communication waves emitted by the network device 370. And the location of the user computer 130 is transmitted to the user computer 130 through the location-based service (LBS).

The storage device 360 is used to store the above-mentioned operating system and application program to assist in implementing the method and steps provided by the present application. In one embodiment, the user can connect to the Web interface system 240 of the aforementioned server 110 through a general or dedicated web browser installed on the user computer 130 to communicate with the server 110. In another embodiment, the user can connect to the interface system 230 through a dedicated communication protocol installed on the user computer 130 to communicate with the server 110. A person skilled in the art of computer science can understand that when the methods and steps provided by the present application need to be executed on the user computer 130, the webpage program (such as HTML5, Java Bytecode, ASP, java-script, etc.) provided by the server 110 can be used to make the browser execute part or all of the methods and steps. Alternatively, an application program installed on the user computer 130 can be used to execute part or all of the methods and steps according to the instructions and/or data provided by the server 110.

A person skilled in the art can understand that although the block diagram shown in FIG3 is an embodiment of a user computer 130, it can also be applied to the server 110 shown in FIG1. The server 110 can include a central processing unit, a network device, a memory module and other related devices for implementing the methods and steps provided in this application.

Please refer to FIG. 4, which is a block diagram of a data structure used by a network information system 100 according to an embodiment of the present application. The network information system 100 includes a plurality of users 410 and one or more organizations 420. The user can connect to the server 110 through the user computer 130 described above, through a browser or a dedicated application. The network information system 100 can accept the user's telephone number, e-mail number, identification code of the user computer 130 or other public account services as the user's unique identification code. The central processor 310 of the user computer 130 can provide the above-mentioned unique identification code. The telecommunications network operator may provide the user's registered telephone number, user identification code (IMSI, International Mobile Subscriber Identity), identification code (IMEI, International Mobile Equipment Identity), media access control address (MAC, Media Access Control address), etc. The above globally unique number, address, identification code, etc. may be used as all or part of the data for identifying the user's identity.

In one embodiment, the network information system 100 may require the user to log in and use the network information system 100 using the user computer 130 with the hardware or service identification code corresponding to the user's identification code. For example, when the identification code of the network device 370 is used as part of the identification of the user, the user must use the user computer 130 with the network device 370 to log in and use all or part of the services of the network information system 100.

In one embodiment, the network information system 100 may require the user to use a user computer 130 near a certain location to log in and use all or part of the services of the network information system 100. For example, when the location of the user computer 130 obtained through a location-based service or a satellite/base station positioning service is within a certain geographical range, the user can use the corresponding user computer 130 to log in and use all or part of the services of the network information system 100.

The network information system 100 may include more than one organization 420, each of which corresponds to at least one user 410. The above-mentioned organization 420 may be a legal person, and the network information system 100 may store information that the organization is required to disclose by law. For example, an organization 420 in the network information system 100 may correspond to a certain construction company. At least one employee in the construction company may be a user 410 of the network information system 100. The server 110 may not be owned by the construction company. In other words, the server 110 of the network information system 100 may be provided by a third-party organization for the organization 420 and the user 410 to use.

The organization 420 may correspond to more than one form template 430. For example, a construction company needs various forms such as self-inspection forms for work items, inspection reports for construction materials, and work safety inspection reports. These forms all have their templates. The format of the template and the data fields included may come from the requirements of the government or other inspection agencies. The form template 430 may contain more than one data field, and each data field may have a data range in its legal format. For example, some data fields are numbers, some data fields are positive integers, and some data fields are one of A~D. Some data fields are graphic files, and other data fields are attachments of various forms. The form template 430 may include explanatory text or questions related to each data field.

The organization 420 may correspond to more than one form 440, which is established based on a form template 430. The data fields in the form 440 are consistent with the data fields designed by the form template, but contain actual data. The form 440 may no longer need to repeatedly include instructions or questions related to each data field. The network information system 100 may verify the data on the user computer 130 and/or the server 110 to determine whether it complies with the format and data range of the data field. In another embodiment, the project 460 corresponding to the organization 420 may also have a project-specific form template 430. For example, the project 460 and the organization 420 both have a form template 430 for a work item self-checklist, but the form template 430 of the project 460 has one or more data fields, or one or more data fields, descriptions, or questions of the form template 430 corresponding to the organization 420 are changed. In this application, the form template 430 can correspond to the organization 420 or the project 460.

The user 410 corresponding to the organization 420 may have access rights to the form template 430 and the form 440. For example, common access methods such as adding, deleting, modifying, and querying. The network information system 100 may record the access history of the user 410 to the form template 430 and the form 440. However, the user 415 who does not belong to the organization 420 cannot know the form template 430 and the form 440 through the network information system 100, and does not have access rights.

For example, user 415 may correspond to a worker who outsources the glass project of the construction company. The worker creates an account of user 415 in the network information system 100. However, since user 415 does not correspond to the organization 420 of the construction company, he cannot see the form 440 in the construction company.

When the construction company's site manager (user 410) reads a form 440 and finds a problem with the glass project from the data, the user 415 cannot read the form 440. Therefore, the site manager (user 410) can add a control form 450, which can include a description of the problem with the glass project. The newly added control form 450 can be associated with the form 440, as well as the user 410 in the organization 420 and the user 415 outside the organization 420. The control form 450 can be used to control the user 415 from reading and responding to the control form 450.

For example, the user 415 can go to a construction site to inspect and repair a problem with a glass project, and then use his user computer 130 to connect to the server 110 and reply to the question on the control form 450. In one embodiment, the network information system 100 can record the location of the user 415 when replying to the control form 450. In another embodiment, the user 415 can use the input device 350 of the user computer 130, such as a photo taken by a camera, to add the photo to the response data of the control form 450.

Then, the network information system 100 can notify the site manager about the content of the control form 450 replied by the user 415. After the user 410, i.e. the site manager, reads the control form 450 and knows from the attached photos and responses that the problem of the glass project has been solved, the user 410 can remove the control of the control form 450, or even delete or seal the control form 450. The user 410, i.e. the site manager, can go back and modify the source form 440 corresponding to the control form 450, indicating that the problem of the glass project has been solved by the user 415 associated with a certain control form 450.

The control form 450 may also correspond to a form template 430, that is, the control form 450 is derived from the form template 430. However, the difference between the control form 450 and the form 440 is that the control form 450 can be used to specify a user 415 outside the organization 420 to reply. Of course, the control form 450 can be used to specify another user 410 within the organization 420 to reply. In addition, the network information system 100 can record which user 410 or 415 corresponds to the control form 450 that is still under control, and remind these users 410 or 415 to reply or respond to the control form 450. For the user 410 or 415, the control form 450 can be regarded as a to-do item.

Please refer to FIG. 5 , which is a block diagram of a data structure used by a network information system 100 according to another embodiment of the present application. The network information system 100 shown in FIG. 5 is a variation of the one shown in FIG. 4 . The network information system 100 includes a plurality of users 410A to 410D, a user 415, and an organization 420A and an organization 420B. The organization 420A corresponds to two users 410A and 410B, and another organization 420B corresponds to another two users 410C and 410D. User 415 still does not belong to any organization. As in the above example, the organization 420A can correspond to a construction company, and the organization 420B can correspond to a supervision company.

Since a construction company may contract many construction projects at the same time, the network information system 100 may add a project 460A to correspond to a construction project of the organization 420A. Similarly, since a supervision company may contract many supervision projects at the same time, the network information system 100 may add a project 460B to correspond to a supervision project of the organization 420B.

In one embodiment, the above-mentioned projects 460A and 460B may have different identification codes. In another embodiment, the above-mentioned identification code may be a composite key. For example, the identification code of the first organization 420A is ORG_A, and the identification code of the second organization 420B is ORG_B. Then the identification code of the project 460A may be a composite key of ORG_A and the project number PROJECT_460 (e.g., ORG_A_PROJECT_460). The identification code of the project 460B may be a composite key of ORG_B and the project number PROJECT_460 (e.g., ORG_B_PROJECT_460). A person skilled in the art will appreciate that this application does not limit the method used to represent projects 460A and 460B, or other organizations, users, forms, or other data structures.

Form 440 can correspond to project 460A instead of directly corresponding to organization 420A. In other words, the above-mentioned self-checklist for work items, inspection report of construction materials, and work safety inspection report can correspond to the construction project of a certain building. In addition, organization 420A can correspond more than one user to project 460A. For example, user 410A corresponds to project 460A, but user 410B does not correspond to project 460A. In one embodiment, the access rights of form 440 can be restricted to the user corresponding to project 460A. In other words, in the embodiment of Figure 5, project 460A only corresponds to user 410A, and project 460B only corresponds to user 410C.

When project 460B of organization 420B corresponds to project 460A of organization 420A, for example, a supervision project of a supervision company supervises a construction project of a construction company, the users corresponding to projects 460A and 460B can agree to associate the two projects 460A and 460B. When user 410A decides to grant read access to form 440 to the users of the corresponding project, in one embodiment, since project 460A to which form 440 belongs has been associated with project 460B of organization 420B, user 410C corresponding to project 460B can read form 440. In another embodiment, the users 410C and 410D corresponding to the organization 420B corresponding to the project 460B can read the form 440. Thus, the user 410C can read the form 440 created by different organizations. The network information system 100 can realize cross-organizational collaboration among users of related projects.

Continuing with the above example, when user 410C, the supervisory engineer of the supervisory company (organization 420B), sees the content of form 440 and finds that there is a problem with the glass project, he can report it to user 410A of the construction company (organization 420A) for processing. User 410A can also add a control form 450 based on form 440, and associate the control form 450 with user 415, the worker in charge of the glass project, and user 410C in charge of supervision. User 410C can read the processing process of user 415 on the control form 450 and give immediate feedback. If user 410C believes that user 415's processing is still insufficient, he can also give guidance in the content of control form 450. When user 410A sees on control form 450 that user 410C is satisfied with the improvement made by user 415, user 410A, i.e. the construction site manager, can go back and modify the source form 440 corresponding to control form 450, indicating that the problem of the glass project has been solved by user 415 associated with control form 450.

Please refer to FIG6, which is a block diagram of a data structure used by a network information system 100 according to another embodiment of the present application. The network information system 100 shown in FIG6 is a variation of the one shown in FIG5. The organization 420B also has a corresponding form template 430B, and another form 440B corresponding to the form template 430B.

Since organization 420B is a supervisory company, the form 440B generated by it does not need to be read by user 410A of organization 420A, i.e., a construction company. Therefore, user 410C may choose not to share form 440B with other users of the collaborative project.

When user 410C sees the problem with form 440B, he can also add a control form 450 and associate the control form with user 415 outside organizations 420A and 420B. In addition, the control form 450 can also be associated with user 410A of project 460A. Therefore, user 410A and user 415 must reply to the content of the control form 450 until user 410C releases the control of the control form 450, or deletes or seals the control form 450. Finally, user 410C can also find the source form 440B of the control form 450 and modify its content to indicate that the problem has been solved.

When associating a form corresponding to a project with a user, the network information system 100 can list users of other organizations to which the associated project belongs for selection. When associating a form corresponding to a project with other organizations, the network information system 100 can list users of other organizations to which the associated project belongs for selection.

Please refer to FIG. 7, which is a block diagram of a data structure used by a network information system 100 according to another embodiment of the present application. The network information system 100 shown in FIG. 7 is a variation of the one shown in FIG. 4 to FIG. 6. For the sake of convenience, the data structure shown in FIG. 7 omits the part already described in FIG. 4 to FIG. 6.

As shown in FIG7 , an organization 420 corresponds to two form templates 430P and 430Q, and a summary form template 470. The summary form template 470 also includes one or more data fields, and description text or questions related to the data fields. In addition, the data fields also correspond to the data fields of the associated form templates 430P and 430Q, and their summary rules.

For example, form template 430P has a data field of working hours, and form template 430Q also has another data field of working hours. The summary form template 470 has a data field of total working hours, and the rule for summarizing is the total of the two working hours contained in the two form templates 430P and 430Q.

In another example, form template 430P has a data field for passing or failing, and form template 430Q also has another data field for passing or failing. The summary form template 470 has a data field for passing or failing, and its summary rule is the AND logical operation result of the two passing or failing data contained in the two form templates 430P and 430Q respectively. Only when both source data are passing, the summarized data will be passing. When any source data is failing, the summarized data will be failing.

After filling out the forms 440P and 440Q according to the form templates 430P and 430Q respectively, the user can make the network information system 100 automatically generate the summary form 480 according to the summary form template 470, the forms 440P and 440Q. The data of the total work hours field of the summary form 480 will be the sum of the data of the corresponding work hours of the forms 440P and 440Q according to the above-mentioned summary rules. The data of the pass/fail field of the summary form 480 will be the AND logical operation result of the data of the corresponding pass/fail fields of the forms 440P and 440Q according to the above-mentioned summary rules.

A person skilled in the art can understand that the above-mentioned induction rule can be used to summarize sources known at the time of design, such as specifying forms 440P and 440Q generated based on two form templates 430P and 430Q. However, the above-mentioned induction rule can also be used to summarize sources known only at the execution time. For example, when the induction form 480 refers to the data field of the working hours of N forms 440, where N is a positive integer, the total addition operation will be performed on the working hours of the N forms 440 and stored in the data field of the total working hours of the induction form 480. In another embodiment, when the summary form 480 refers to the pass/fail data fields of N forms 440, where N is a positive integer, an AND logical operation is performed on the pass/fail data of the N forms 440, and the result is stored in the pass/fail data fields of the summary form 480.

In addition to the data fields with the summarization rules, the summarization form template 470 may also have common data fields without the summarization rules like the form template 430. The data fields of the summarization form template 470 may also include corresponding format and data range restriction conditions.

The network information system 100 and the method provided by the present application can allow users outside the organization to collaborate with users belonging to the organization, and can also allow users from different organizations to collaborate with each other using projects as contact units. In terms of traditional construction projects, a large-scale construction project often requires the use of hundreds or thousands of vendors and workers, using paper forms that are enough to fill up an entire room, hiring multiple managers to organize the address books and forms of vendors and workers, making telephone calls and following up on control forms, and using paper and pen calculations to generate summary forms. The network information system 100 and its method provided by the present application can make the above process paperless, electronic, and mechanized to save a lot of costs. In particular, it can add images, sounds, and animations to the forms to record and reproduce the on-site construction conditions, and can also use authority control and the location of the user's computer to confirm that the filling and review of the form actually occurred on the construction site.

In addition to being applied to the construction industry, this application can also be applied to other industries that require cross-organizational collaboration. For example, the factory production process requires close cooperation with upstream suppliers and downstream brand customers, and generates many forms for product quality, production progress, quality inspection, design changes, etc.

Please refer to Figure 8, which is a flow chart of a cross-organizational project collaboration method 800 according to an embodiment of the present application. The cross-organizational project collaboration method 800 can be implemented using the network information system 100 shown in Figure 1, and in particular, implemented by the server 110. For example, it is implemented by the central processing unit of the server 110 executing instructions and data stored in a memory module (such as a non-volatile memory module or a computer-readable medium). If there is no direct or indirect causal relationship between any two steps, the present application does not limit the execution order of these two steps. The cross-organizational project collaboration method 800 can start with step 805.

Step 805: Receive a project association instruction via a network, for associating a first project corresponding to a first organization with a second project corresponding to a second organization. In one embodiment, the project association instruction may be issued by a user corresponding to the first organization or the second organization. In another embodiment, the project association instruction may be issued by a user corresponding to the first project or the second project. In other embodiments, when the project association instruction is issued by the user corresponding to the first party, a confirmation project association instruction may be issued by the corresponding user of the second party. When both parties agree to associate the first project with the second project, the two projects will be associated.

Step 810: Receive a first association instruction issued by a first user corresponding to the first organization from a first user computer via a network, and associate a first form with a first project corresponding to the first organization, wherein the first form is established based on a first form template of the first organization or the first project, wherein the first form template includes multiple first data fields.

Step 820: Receive a second association instruction issued by the first user from the first user computer via the network to associate the first form with a second project corresponding to the first project, wherein the second project corresponds to a second organization.

Optional step 830: receiving a sharing instruction corresponding to the first form sent by the first user from the first user computer via the network; and setting the first form to be shareable.

Optional step 840: receiving an update command issued by the first user from the first user computer via the network, for updating one of the plurality of first data fields included in the first form. The updated data field may be a location field, the location field including location information of the first user computer when the update command is issued.

Optional step 850: receiving a read instruction corresponding to the first form sent by a second user corresponding to the second organization from a second user computer via the network. Then, the process can proceed to step 860, or directly proceed to step 870.

Optional step 860: Determine whether the first form is shareable. When the first form is shareable, the process proceeds to step 870; otherwise, the process proceeds to step 890.

Optional step 870: Determine whether the second user is associated with the second project. When the second user is associated with the second project, the process proceeds to step 880; otherwise, the process proceeds to step 890.

Optional step 880: sending the first form to the second user computer via the network.

Optional step 890: Do not send the first form to the second user computer.

Please refer to FIG. 9 , which is a flow chart of a cross-organizational project collaboration method 900 according to an embodiment of the present application. The cross-organizational project collaboration method 900 can be implemented after steps 810 and 820. The cross-organizational project collaboration method 900 can be implemented using the network information system 100 shown in FIG. 1 , and in particular, by the server 110. For example, the central processing unit of the server 110 executes instructions and data stored in a memory module (such as a non-volatile memory module or a computer-readable medium) to implement it. If there is no direct or indirect causal relationship between any two steps, the present application does not limit the execution order of these two steps. The cross-organizational project collaboration method 900 may begin with step 910 .

Step 910: Create a control form according to a control form template related to the first organization, wherein the control form template includes a plurality of data fields.

Step 920: Receive a correlation instruction issued by the first user from the first user computer via the network to correlate the control form to the first project. In one embodiment, the control form can be further correlated to a form associated with the first project.

Step 930: Receive a correlation instruction issued by the first user from the first user computer via the network to correlate the control list to a third user, wherein the third user does not correspond to any organization.

Step 940: Send the control list to a third user computer used by the third user via the network.

Optional step 950: receiving an update command issued by the third user from the third user computer via the network, for updating one of the plurality of data fields included in the control table. One of the plurality of data fields is a location field, and the location field includes location information of the third user computer when the update command is issued.

Please refer to FIG. 10 , which is a flowchart of a cross-organizational project collaboration method 1000 according to an embodiment of the present application. Like the cross-organizational project collaboration method 900 shown in FIG. 9 , the cross-organizational project collaboration method 1000 can be implemented after steps 810 and 820. The cross-organizational project collaboration method 1000 can be implemented using the network information system 100 shown in FIG. 1 , and in particular, by the server 110. For example, the central processing unit of the server 110 executes instructions and data stored in a memory module (e.g., a non-volatile memory module or a computer-readable medium) to implement the method. If there is no direct or indirect causal relationship between any two steps, the present application does not limit the execution order of the two steps. The cross-organization project collaboration method 1000 may start from step 1010. Steps 930 to 950 similar to the cross-organization project collaboration method 900 will not be repeated.

Step 1010: Create a control form according to a control form template related to the second organization, wherein the control form template includes a plurality of data fields.

Step 1020: Receive a linking instruction from a second user associated with the second project from a second user computer via the network to link the control form to the second project. In one embodiment, the control form can be further linked to a form associated with the second project. Then, the process can proceed to step 930.

Please refer to FIG. 11 , which is a flow chart of a cross-organizational project collaboration method 1100 according to an embodiment of the present application. The cross-organizational project collaboration method 1100 can be implemented after steps 810 and 820. The cross-organizational project collaboration method 1100 can be implemented using the network information system 100 shown in FIG. 1 , and in particular, by the server 110. For example, the central processing unit of the server 110 executes instructions and data stored in a memory module (such as a non-volatile memory module or a computer-readable medium) to implement it. If there is no direct or indirect causal relationship between any two steps, the present application does not limit the execution order of these two steps. The cross-organizational project collaboration method 1100 may begin with step 1110 .

Step 1110: Receive a summary instruction issued by the first user from the first user computer through the network, wherein the summary instruction corresponds to a summary form template, the first form and a second form. The second form is established according to a second form template of the first organization, the second form template includes a plurality of second data fields, the summary form template includes more than one summary rule and more than one summary data field, and the summary rule is a method of summarizing according to at least one first data field among the plurality of first data fields and at least one second data field among the plurality of second data fields.

Step 1120: Create a summary form according to the summary form template and the summary rule contained therein, wherein the data in the summary data field of the summary form is generated by summarizing according to the summary rule.

Optional step 1130: receiving an update command issued by the first user from the first user computer via the network, for updating one of the plurality of summary data fields included in the summary form.

According to an embodiment of the present application, a cross-organizational project collaboration method is provided, which includes: receiving a project association instruction through a network to associate a first project corresponding to a first organization with a second project corresponding to a second organization; receiving a first association instruction issued by a first user corresponding to the first organization from a first user computer through the network to associate a first form with the first project, wherein the first form is established based on a first form template of the first organization or the first project, wherein the first form template includes multiple first data fields; and receiving a second association instruction issued by the first user from the first user computer through the network to associate the first form with the second project corresponding to the first project.

Preferably, in order to control whether the first form is shareable, the cross-organizational project collaboration method further includes: receiving a sharing instruction corresponding to the first form sent by the first user from the first user computer via the network; and setting the first form to be shareable.

Preferably, in order to allow the second user corresponding to the second project to read the second form, the cross-organizational project collaboration method further includes: receiving a read instruction corresponding to the first form sent by a second user corresponding to the second organization from a second user computer via the network; determining whether the second user is associated with the second project; and when the second user is associated with the second project, transmitting the first form to the second user computer via the network.

Preferably, in order to control whether the first form is shareable so that the second user corresponding to the second project can read the second form, the cross-organizational project collaboration method further includes: after receiving the read instruction corresponding to the first form, determining whether the first form is shareable; and when the first form is shareable, executing the above-mentioned step of determining whether the second user is associated with the second project.

Preferably, in order to determine whether the first user updates the first form at a specified location, the cross-organizational project collaboration method further includes: receiving an update command issued by the first user from the first user's computer via the network, for updating a location field among the multiple first data fields included in the first form, the location field including the location information of the first user's computer when the update command is issued.

Preferably, in order to allow the system to allow users who do not belong to any organization to collaborate, the cross-organizational project collaboration method further includes: establishing a control form based on a control form template related to the first organization, wherein the control form template includes multiple data fields; receiving a third association instruction issued by the first user from the first user computer via the network to associate the control form with the first project; receiving a fourth association instruction issued by the first user from the first user computer via the network to associate the control form with a third user, wherein the third user does not correspond to any organization; and transmitting the control form to a third user computer used by the third user via the network.

Preferably, in order to allow the system to allow third users who do not belong to any organization to collaborate, the cross-organizational project collaboration method further includes: establishing a control form based on a control form template related to the second organization, wherein the control form template includes multiple data fields; receiving a fifth association instruction issued by a second user associated with the second project from a second user computer through the network to associate the control form with the second project; receiving a sixth association instruction issued by the second user from the second user computer through the network to associate the control form with a third user, wherein the third user does not correspond to any organization; and transmitting the control form to a third user computer used by the third user through the network.

Preferably, in order to determine whether the third user updates the control list at a specified location, the cross-organizational project collaboration method further includes: receiving an update command issued by the third user from the third user computer via the network, for updating a location field among the multiple data fields included in the control list, the location field including the location information of the third user computer when the update command is issued.

Preferably, in order to provide the system with a function of automatically generating a form, the cross-organizational project collaboration method further comprises: receiving a summary instruction issued by the first user from the first user computer via the network, wherein the summary instruction corresponds to a summary form template, the first form and a second form, the second form is established according to a second form template of the first organization, the second form template includes a plurality of second data fields, the summary form template The invention comprises one or more induction rules and one or more induction data fields, wherein the induction rule is a method of induction according to at least one first data field among the plurality of first data fields and at least one second data field among the plurality of second data fields; and a induction form is established according to the induction form template and the induction rule contained therein, wherein the data in the induction data field of the induction form is generated by induction according to the induction rule.

According to an embodiment of the present application, a server for implementing the above-mentioned cross-organizational project collaboration method is provided, which includes: a network device for connecting to the network; and a central processing unit for executing instructions stored in a computer-readable memory to implement the above-mentioned cross-organizational project collaboration method.

According to an embodiment of the present application, a computer-readable recording medium storing a program is provided, wherein when the server loads and executes the program, the cross-organizational project collaboration method as described above can be completed.

According to the cross-organizational network information system provided by the present application, the server it contains and the cross-organizational project collaboration method it implements can simultaneously provide file retrieval, notification and/or to-do list management functions within and across organizations, and provide a convenient collaboration environment in the daily operation of multiple large-scale collaborative projects involving hundreds or thousands of people across organizations or departments.

100: Network information system 110: Server 120: Network 130: User computer 210: Database management system 220: Application logic server system 230: Interface system 240: Web interface system 310: Central processing unit 320: Memory module 330: Input/output interface module 340: Output device 350: Input device 360: Storage device 370: Network device 410: User 410A: User 410B: User 410C: User 410D: User 415: User 420: Organization 420A: Organization 420B: Organization 430: Form Template 430A: Form Template 430B: Form Template 430P: Form Template 430Q: Form Template 440: Form 440A: Form 440B: Form 440P: Form 440Q: Form 450: Control Form 460: Project 460A: Project 460B: Project 470: Summary Form Template 480: Summary Form 800: Cross-Organizational Project Collaboration Method 805~890: Steps 900: Cross-Organizational Project Collaboration Method 910~950: Steps 1000: Cross-organizational project collaboration method 1010~1020: Steps 1100: Cross-organizational project collaboration method 1110~1130: Steps

FIG. 1 is a block diagram of a network information system 100 according to an embodiment of the present application. FIG. 2 is a block diagram of a server 110 according to an embodiment of the present application. FIG. 3 is a block diagram of a user computer 130 according to an embodiment of the present application. FIG. 4 is a block diagram of a data structure used by a network information system 100 according to an embodiment of the present application. FIG. 5 is a block diagram of a data structure used by a network information system 100 according to another embodiment of the present application. FIG. 6 is a block diagram of a data structure used by a network information system 100 according to another embodiment of the present application. FIG. 7 is a block diagram of a data structure used by a network information system 100 according to another embodiment of the present application. FIG. 8 is a flow diagram of a cross-organizational project collaboration method 800 according to an embodiment of the present application. FIG. 9 is a flow diagram of a cross-organizational project collaboration method 900 according to an embodiment of the present application. FIG. 10 is a flow diagram of a cross-organizational project collaboration method 1000 according to an embodiment of the present application. FIG. 11 is a flow diagram of a cross-organizational project collaboration method 1100 according to an embodiment of the present application.

800: Cross-organizational project collaboration method 805~890: Steps

Claims (7)

A cross-organizational project collaboration method comprises: receiving a project association instruction through a network to associate a first project corresponding to a first organization with a second project corresponding to a second organization, wherein the second organization corresponds to a second user; receiving a first association instruction issued by a first user corresponding to the first organization from a first user computer through the network to associate a first form with the first project, wherein the first form is established according to a first form template of the first organization or the first project, wherein the The first form template includes a plurality of first data fields; a second association instruction issued by the first user is received from the first user computer via the network to associate the first form with the second project corresponding to the first project; a read instruction corresponding to the first form sent by the second user is received from the second user computer via the network; it is determined whether the second user is associated with the second project; and when the second user is associated with the second project, the first form is transmitted to the second user computer via the network. The cross-organizational project collaboration method as described in claim 1 further includes: receiving a sharing instruction corresponding to the first form sent by the first user from the first user computer via the network; and setting the first form to be shareable. The cross-organizational project collaboration method as described in claim 1 further includes determining whether the first form is shareable after receiving the read instruction corresponding to the first form; and when the first form is shareable, executing the above-mentioned step of determining whether the second user is associated with the second project. The cross-organizational project collaboration method as described in claim 1 further includes: receiving an update command issued by the first user from the first user computer via the network, for updating a location field among the plurality of first data fields included in the first form, the location field including the location information of the first user computer when the update command is issued. The cross-organizational project collaboration method as described in claim 1 further comprises: receiving a summary instruction issued by the first user from the first user computer via the network, wherein the summary instruction corresponds to a summary form template, the first form and a second form, the second form is established according to a second form template of the first organization, the second form template includes a plurality of second data fields, and the summary form template includes more than one A summary rule and one or more summary data fields, wherein the summary rule is a method of summarizing according to at least one first data field among the plurality of first data fields and at least one second data field among the plurality of second data fields; and a summary form is established according to the summary form template and the summary rule contained therein, wherein the data in the summary data field of the summary form is generated by summarizing according to the summary rule. A server for implementing a cross-organizational project collaboration method as described in any one of claims 1 to 5, comprising: a network device for connecting to the network; and a central processing unit for executing instructions stored in a computer-readable memory to implement the cross-organizational project collaboration method. A computer-readable recording medium storing a program, wherein when the server loads and executes the program, it is used to complete the cross-organizational project collaboration method as described in any one of claims 1 to 5.