WO2013109155A2

WO2013109155A2 - Hypervisualization process tool for architecture

Info

Publication number: WO2013109155A2
Application number: PCT/PT2013/000003
Authority: WO
Inventors: João António de Almeida MOTA; Pirjo Annikki HAIKOLA
Original assignee: Universidade De Aveiro
Priority date: 2012-01-17
Filing date: 2013-01-17
Publication date: 2013-07-25
Also published as: WO2013109155A3

Abstract

This tool serves the needs in practice of architecture: primarily to provide the missing overview of the entire design process, tie together, and provide access to, the fragmented processual information. The readily apparent 3D interface 'hypervisualization' allows easy and fast wayfinding. As projectual practice is growing more complex, better digital support is needed for it. The tool makes parts of the complexity designers face in their practice understandable and workable through visual interface, and allows more efficient working. It also allows more participants access to the overview and documentation (retaining the possibility to control levels of access) improving the quality and creativity of work. The 'hypervisualization', allows access and control of information related to people/parties, files/documentation, notes, phases/tasks and events. Entering the system user privileges are determined, consequently allowing for instant visual recognition of needed information, and performing actions related to prior mentioned tasks.

Description

DESCRIPTION

"HYPERVISUALIZATION PROCESS TOOL FOR ARCHITECTURE"

FIELD OF THE INVENTION

The present invention relates to the design process, specifically in architecture, and to workflow, information visualization and interfaces; design and process tools; project management in design, architecture and other fields of projectual activity; team management in design, architecture and other fields of projectual activity; information/file management and search tools for the files produced by a large team in a specific project in design, architecture and other fields of projectual activity.

BACKGROUND OF THE INVENTION

Patent application WO 9853391 (A2), Spatial Browsing Approach to Multimedia Information Retrieval, relates to a three-dimensional user interface, which allows browsing of a database displayed as a three-dimensional information space. The invention was conceived to work in the environment of browsing TV guide content.

It utilizes already known (precedent for instance Coopers' 'Information Landscapes') 3D environment to allow browsing of large sets of information and to transition smoothly to watch the desired programs.

Both the above application and the present invention use a 3D space to access large sets of information. However, the above application does not foresee the possibility of adding or modifying contents, and the interface is 3D and does not include the temporal aspect. Furthermore, the method of browsing the information is through the 3D space and through a hierarchical system, whereas in the present invention, in addition to the 3D (or 4D as it includes temporal) browsing, non-hierarchical browsing systems are used and the content is reorganized in novel visual ways.

Patent application US 2006/0156228 Al, Spatially driven content presentation in a cellular environment, relates to techniques for integrated content presentation via cells arranged geometrically in a cellular environment. Users can navigate various orientations and zoom states of the cellular environment to access information via different applications, media types, visual presentations and from different underlying content sources.

As in the previous document, it is possible to view and access information through 3D browsing. However, in this case, the media content is not specified, browsing is organized as a cellular space and information can be organized according to various logical relationships.

Patent application US 2002/0147729 Al, Method and system for a four- dimensional temporal visualization data browser, relates to a method and system for accessing data from information databanks in all four dimensions, providing the ability to interactively experience and naturally visualize the temporal progression of important data components, their attributes and, most importantly, their naturally changing relationships. The method and system builds 4D portals into information databanks, through which computer generated 4D worlds are served to users in 4D browser, which can be naturally experienced in both temporal and spatial context to derive knowledge from the dataset.

Although both the above application and the present invention use 4D to browse and access information, the above application uses hierarchical relationships conversely to the broader, predominantly visual strategies of the proposed invention. The proposed invention creates different types of visualizations of the data, depending on the query of the user. One such possible instance, for example, may be when the user wants to see only critical and finished files of a specific team, which result in a specific kind of visualization. Another example may be when the user defines the axis in the 3D view, choosing z axis as time, y as criticality of files, and x as extensions of files, creating a completely different kind of visualization showing all files, but allowing quick recognition of their criticality. Conversely to this patent application, the proposed invention also allows visualization of planned events in the same way as described above (namely in case of phases, meetings, tasks, deadlines etc.) Furthermore, the visualization includes notes specific for the user. These notes work as a communication tool with other users and offer the possibility of being directly attached to the files or previews of the files linked to a central database.

There are other distinguishing features between the above application and the proposed invention: - The above application is meant for any type of content that is used to audit trail data, i.e. to follow the past actions of, for example, goods. As described "many database management systems create daily audit trails for backup and recovery purposes which can be reorganized around the 4D object definitions. " Conversely, the specific functions of the proposed invention derive from the needs in the design process.

- The above mentioned application transforms database information into 4D representation. Conversely, the proposed invention is a tool for daily use by professionals, in projectual activity, mainly design, to see past actions, but also to plan future actions and dynamically modify and access content (by different participants).

- The above application allows users to access and analyze temporal data relationships. Conversely, the proposed invention allows for a variety of functions specific to the design process, access and control of information related to people/teams/parties, files/documentation, phases/tasks, notes and meetings.

Patent application US 2009199113 (Al), Graphical user interfaces, relates to a graphical User Interface (GUI) for use in project management. It is meant as a simple tool to be used by middle and junior managers running projects and addresses mainly one of the problems of the proposed invention, i.e., the need to avoid loosing the 'big picture' . However, the above application differs in many ways from the proposed invention:

- The above application is meant primarily to be used by the middle and junior managers running projects not specifying the domain. Conversely, the proposed invention is meant for all the participants in the (design) project, allowing everyone access to the project overview, while retaining the possibility to control levels of access.

- The above application has a 2D interface organized as printable pages. Conversely, the proposed invention has a navigable, 3D/4D hypervisualization interface. - The above application contains typical project management functions known from other tools and, additionally, meeting planning and documentation. Conversely, the proposed invention contains a variety of functions related to people/parties, files/documentation, phases/tasks, notes and events, allowing not only planning and overseeing projects, but working through the tool, previewing and controlling files and communicating with participants, i.e. , it is the primary interface to the project for all participants.

The above patent documents demonstrate that different types of 3D and 4D browsing of information applications exist, as that as an idea is known (although not so much as commercial applications), for example Cooper's early 'Information Landscapes'

However, the search further demonstrates that visualizations and 3D/4D are not commonly used as interfaces for software applications, for project management or process tools, which is the domain of this invention.

Furthermore, those applications do not take into consideration the ability of multiple users to add, control or modify contents. Hence, in the design process domain, the application of this tool is novel due to its several domain specific functions such as access and control of files, project and event planning, and communication and management tasks. In the domain of design, 3D applications are commonly used for modeling the artefacts, but have not been used to 'model' the process of design itself.

Despite existing project management, process tools and building information models (BIM), architects still experience lack of overview and 'project memory' in complex projects where this invention is proposing a solution by collecting relevant information in one application and additionally providing it a readily apparent visual interface.

SUMMARY OF THE INVENTION

The invention relates to computer implemented program for architectural or design project management comprising: - providing a user interface for accessing and searching a project database,

- generating representations of objects, searched from the project database, in a 3D visualization field, wherein the axis of 3D field are defined by the user and said representations are based on at least one attribute of the objects;

- creating, in the visualization field, 3D representations of connections between objects, and providing access to the objects searched from the project database through the representations of said objects in the 3D visualization field.

In one aspect of the invention, accessing the database comprises creating projects. In another aspect of the invention, accessing the database comprises defining information access levels for each user. In a further aspect of the invention, accessing the database comprises creating and managing project phases, project tasks and project breaks.

In still another aspect of the invention, accessing the database comprises creating and managing parties, teams and people.

In a further aspect of the invention, accessing the database comprises at least one of: uploading, previewing, opening, saving, assigning/changing status and tracking changes in files. In one aspect of the invention, accessing the database comprises creating and replying to notes attached to files or file previews.

In another aspect of the invention, accessing the database comprises creating meetings and accessing meeting related information.

In an aspect of the invention, database searching is based on semantic, temporal, spatial criteria or a combination thereof.

In an embodiment of the invention, one of the axis of the 3D field represents time.

In another embodiment of the invention, the connections between objects in the 3D visualization are represented by lines, shapes or forms. The invention also relates to a computer readable medium comprising the above described computer implemented program. The invention further relates to a computer system comprising:

- a database in which architectural or design project data are stored;

- a server connected to the database;

- at least one computer connected to the server, and

- at least one computer readable medium as described in claim 11 , connected to the server and to the at least one computer.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will be described, by way of example only, with reference to the accompanying drawings:

Figure 1:

Concept image of the 3D 'hyper visualization' interface, viewing part of the information.

Figure 2:

Class Diagram of the objects in the tool. Figure 3:

Client-server architecture principle. Figure 4:

Meetings visualized as shapes 'wrapping' around people (cylindrical shapes). Figure 5:

Files visualized as shapes with file extensions attached to them.

Figure 6:

Files visualized as shapes with file types attached to them.

Figure 7:

Files visualized as shapes with file previews attached to them. Figure 8:

Notes on top of a running program.

Figure 9:

Tasks visualized as shapes 'wrapping' around people (cylindrical) shapes and showing their relation from one party to another.

Figure 10:

People visualized as cylindrical shapes.

DETAILED DESCRIPTION OF THE INVENTION

The objectives of the invention are to provide solutions to the following problems: - lack of project overview regarding people/parties/teams, files/documentation, phases/tasks, communication and meetings;

- lack of collective/cohesive "project memory" due to difficulty in retrieving all relevant information associated with large projects;

- management of fragmented project information. The invention solves the problems by:

- providing Project/process visualizations 'hypervisualizations'(3D interface) that act as the primary interface for people/parties, files/documentation, notes, phases/tasks and events, and novel, more readily apparent, visual ways of organizing information;

- creating structured organization of information in two ways. Both 3D and 2D ways are dependent on the search criteria of the user ; - enabling communication of the information in a novel way through notes, which are directly attached to the files or previews of the files and linked to a central database;

- linking together processual information that until now has not been collected in one system, by making it accessible through one interface. With the visual interface, the tool acts as the central access point for the project. Additionally, it is also possible to control which parties and participants have access to what information;

- combining many design process relevant functions involving intranet, file sharing, file storage, file management, search function, agenda (meeting planner), project/process management tool and communication (notes/comments for project related information), in one tool.

To provide solutions to the aforementioned problems the invention is a software tool to run as a computer application, to be accessed through a Graphical User Interface (GUI) and mouse or tablet (or such like).

It is designed to complement the use of other tools in the (architectural) design process, such as 3D modeling tools, other High Functionality Applications, physical models etc. The invention is targeted primarily, but not limited to, large international architecture offices and other parties involved in architecture projects - in particular with complex long-term projects. The invention can be used in other similarly structured design projects and projectual activities.

The invention works as follows and includes, but is not limited to, the following embodiments:

The system follows client-server architecture, where the server maintains a database with the project data (Fig. 2), and the client accesses that information and displays it to the user. The application is currently implemented as a client-server application, for storage and collaboration. The server manages the database and the client creates the visualization. A description of client-server architecture deployment diagram is shown in Fig. 3. Cloud computing is an extended possibility for the software. Cloud computing means applications delivered via the internet are accessed from web browsers and client computers, while the data are stored on servers at a remote location. A cloud client consists of computer hardware and/or computer software that relies on cloud computing for application delivery. Cloud tasks provide compute, storage, communication and management capabilities. (Wikipedia, 'Cloud computing' Online at: http : //en . wikipedia . org/wiki/Cloud_computing) .

The visualizations of the project for the user are created based on the information on the client database. Each object on the database has a 3D object assigned to, with a number of variable attributes, for example: Position, Scale, Rotation and Color. Most of the attributes of the 3D object are directly related to the attributes of the database object. For example, a person is represented by a cylinder, and the position of that cylinder on the XY Plane is given by which Party that person belongs to, and their occupation/work title on said Party (Fig. 3).

The interface consists of two views (visualizations) of the same data: 3D and/or 2D (side orthographic view). In both 3D and 2D views, one of the axes usually represents time (and thus the 3D view can be described as 4D). However, the time axis in the 3D view can also be used to signify other characteristics than time, in order to generate different visualizations, depending on the search criteria of the user.

The interface also includes GUI controls. To achieve a visualization of the database, every object on the class diagram (Fig. 2) is associated with a 3D and/or a 2D representation, based on one or more attributes of that object (Fig. 1).

The position of the visual objects in the interface on the time axis is based on their creation date or other time-related attribute, the position on the other axis is mostly based on object connection/relation with other objects or other characteristic based on search criteria (Fig. 2).

In the 3D and 2D views, the user can zoom in and out to see specific months/weeks/days/hours and the associated information described herein below. User can also navigate the 3D space by rotating etc. to enable finding/accessing/modifying needed information using the GUI controls. An overview of the interface and visualization is shown in Fig 4.

User privileges / authentication: Upon opening the application, user must login and select a project(s) (or create a new one). I.e. before the client can access the data on the server, it needs to authenticate himself with a username and password. After a successful authentication, the server sends to the client the most recent copy of the database.

The data is filtered using the user access permissions. As a consequence, varying level of user access permissions are determined.

Communication between server and clients is encrypted to ensure a secured and private connection. The information across all the clients is synchronized: each time a database located on the client side is modified those changes are sent to the server, which will update his own database and propagate the changes to all the other clients. The server is assigned with the task of maintaining the consistency of the database, and will deny modifications that would corrupt or invalidate the database. It will also check for concurrency problems, when two or more clients try to change the same data at the same time.

The client will only allow certain operations on the database, based on the access permissions of the current user. Any operation that is not allowed to the user will not be visible to him. Furthermore, the server will also check if any request for modification of the database has the required access permissions to do so.

While logged into the system, a user can perform the following functions, not necessarily in this sequence (Fig. 2).

Tool functions:

A user with the correct privileges is able to set-up a new Project and to manage process through the tool. Meetings management:

User can plan meetings and access/modify information related to them (see Fig. 2 meetings and meetings pending).

The user can plan a meeting by choosing the participants (from the 3D view, or from the 2D view), after which he/she will be asked to provide the necessary information to schedule the meeting, namely date, time and place (see fig. 2, meeting pending) Once the information is provided, the tool generates a shape(s) in the 3D visualization and/or 2D view, in the correct temporal/spatial location, showing who is intended to participate and who has already accepted the invitation (Fig. 4).

User is also asked if he/she wants to upload a file (simple files in Fig. 2). Files are shown attached to the meeting's shape (Fig. 4), making it easy to view/modify what information has been prepared.

Once the scheduled procedure is complete, the intended participants will get a notification (on the computer screen where they are logged in and/or through the tool interface) that they have a pending meeting to review.

Meetings are shown in a timeline (in the 3D interface and side orthographic view) which can be zoomed up to an hourly view (see Fig. l for overview of the interface). After the meeting has taken place, files can again be uploaded to the same processual/temporal location, attached to the meeting visual shape, to make it easier to find decisions and information from the meeting afterwards.

User can open these linked files (in the appropriate computer application) or their previews directly from the 3D interface. File management:

The function can be used to manage all the files (see Fig. 2 advanced files) related to the project.

User can add (save/upload) files that are automatically placed in the current processual and temporal location in the 3D interface hypervisuahzation (see Fig. l for overview). User is required to choose a file status (which is visible in the 3D interface through a codification based on colours) - as 'critical', 'accepted', 'finished', 'in progress' or 'tests/outdated' .

The status can be changed when needed using the GUI controls. If a file is marked as 'critical' it must be assigned to another user and the assigned person will get a notification (on the computer screen where they are logged in and/or through the tool interface) that there is a file expecting to be reviewed.

The file, or its preview can be opened from the 3D interface, reviewed and the status changed or notes added, as needed.

As one or more persons can be working on the same file, the interface shows with an identifier shape who is, or has been, working on which files. When the file is saved again, the different versions of the file are visually linked to each other allowing to track file changes (Fig. 5-7).

In addition to see/change the 'file status' user can choose one of the following viewing options through the GUI controls (this applies also to simple files attached to meetings):

-'file extensions' (.xls, .doc, ,3ds etc.), Fig. 5; -'file types' (presentations [P], 3D, 2D, Images [I] and documents [D]), Fig. 6;

-'previews' (previews are shown attached to the file visual shape and can be opened as full screen previews as well), Fig. 7.

Notes:

It is possible to write notes (comments, questions, remarks) for all files (see Fig. 2 notes).

User can create a note in the following ways:

- when opening a file preview, by going to a desired file shape/preview through the 3D interface, a full screen image/preview becomes visible on the computer screen. On top of the preview there is a small transparent note. User can simply start typing on the note and the tool adds information on the author and the date/time of the creation of the note (see Fig. 2 notes and Fig. 8). - when opening a file (by going to a desired file shape/preview through the 3D interface), with the appropriate application. On top of the application a small transparent note is visible (Fig. 8). User can simply start typing on the note and the tool adds information on the author and the date/time of the creation of the note. In both cases notes can be moved in different places of the window and they will remain there when the file/preview is opened again. Further notes can be created, by cloning a note. In that case a new empty note is created.

When a note is written, other user(s) working on the file (and/or tagged user[s]) will be notified there is a new note expecting to be reviewed.

These users can either: - review the note(s) when opening a full screen preview of a Working file, where the transparent notes will be layered on top, enabling the user to continue to see the previewed working file underneath.

- open the application where the file was created (or can be worked on) and transparent notes will be visible on top of the open application, automatically showing the note(s). Users can work on the file using the application while seeing the notes layered on top and go back and forth to the open application and the notes (for example to accept, comment or move them).

- Users can also decide to view only the notes in order to view, for example, the history of all notes related to a certain sequence of files, by selecting this option from the

GUI controls.

It is also possible to respond to a note, simply by continuing to type into the note. Instead of communicating via e-mail and attaching files to e-mails, this feature of the tool allows easier and more organized communication.

The Design Brief / Regulations:

The design brief and regulations (a collection of different types of files), independent from the processual and temporal location are always easily accessible through GUI controls.

This collection of files can be directly opened from the interface, like all files linked to the tool. Task management: Tasks can be planned and they can include several types of information (see Fig. 2 tasks).

A user can create a task by using the appropriate GUI controls, after which the necessary information must be provided, namely the description, deadline, the users involved and their responsibilities (see Fig. 2 tasks).

The planned task is visualized in the 3D and/or 2D view. The participants and the length of the task are also shown as a shape. Tasks can also have a relation to each other - it is possible to plan a task for one party /team and a related task that another party continues with.

Tasks and their relations are also shown visually in the hypervisualization with a shape that continues from one party to another. (Fig.9)

Search and visual organization of information:

Since the software tool functions as the central point for information and communication related to a project, search and filter functions are crucial.

The software tool according to the present invention enables information to be organized and visualized in multiple ways allowing it to be understood by all parties and also according to personal preferences.

A user can search desired information through the following criteria:

- temporal, using the timeline to navigate, or selecting a time frame using the GUI controls;

- semantic, using key words; - choosing to view certain types of information, for example, only critical files, only meetings, all files produced by a team, everything produced by a person among other possibilities; - spatial, by navigating around in the 3D/4D space;

- a combination of previously explained search strategies.

Only the information related to the search results is shown, resulting in different kinds of visualizations, depending on the search criteria.

Search can be done using different GUI controls and, in the case of semantic search, by typing into a search 'box' .

Phase management:

Project phases can be planned and modified. They are shown visually in the 3D space and in the orthographic view.

When creating a phase, the user selects the option from the GUI controls after which he/she is asked to provide the necessary information, namely a description and a deadline (see fig 2 phases). Once the necessary information is provided, the tool creates the phase shapes in the 3D and/or 2D view.

Parties:

Each project includes parties. The user can add them in the beginning throughout the project. When adding a party, the user selects the appropriate GUI control and is prompted to provide the necessary information, namely, name, field of work, contact details, (see Fig. 2 parties)

Parties are shown visually in the 3D interface and/or 2D view.

Parties include two further objects: People: People can be added and removed during the project, as for parties (see

Fig. 2 people).

They are shown visually inside the parties in the 3D interface and/or 2D view as cylindrical shapes (Fig. 10). Position of a person in a party /project is also visually represented concentrically (In a customized search by a user the relation to other objects may be different).

Teams: Teams can be planned (and modified) during projects, as for parties (see Fig 2 teams).

Teams are also shown visually in the 3D interface and/or 2D view.

Breaks:

As design processes are asynchronous and intermittent, it is necessary to make explicit breaks and manage them in the project workflow.

They can be related to the absence of people, or related to the whole project, for example if the project is suspended for some reason for a period of time. Breaks are also shown visually in the 3D interface and/or the 2D view. The user can add/manage breaks through the appropriate GUI controls of the tool (see Fig. 2 breaks). The software tool according to the invention provides:

- improved information consolidation and workflow analysis/representation, leading to improved process management and productivity amongst heterogeneous teams; - better design outcomes due to better, more comprehensive overview of the entire project process and the embedded knowledge associated with it;

- faster and easier access to desired information; - a manner of preventing managers and project architects from being the central repository of collective information, since processual information is readily available to all people and parties involved;

- smoother transition when additional parties or participants are introduced at different points in the project, or when projects have been suspended for periods of time and require participants to recall knowledge and information concerning past work quickly and easily.

EXAMPLES

The following examples illustrate the benefits resulting from the software tool according to the invention: 1] (Partial) technical solution to a problem in work environment - Lost or irretrievable knowledge

In organizations/projects it is common that when a person leaves, or is away for a period of time, it is hard to follow up on his/her work. Information is fragmented between e-mails, e-mail attachments, files, personal notes and so on. This tool provides help for this problem, by converging the production of artefact and management of process in one tool. Correspondence/communication about development of artefacts is directly attached to the documentation of the artefact and is kept organized, stored and searchable from one interface, in one application. This allows people who are following up on someone else's work to find needed information, without having to ask to forward e-mails, scan notes or go through piles of papers, or similar repetitive administrative tasks, for example. This brings also an advantage that the process as a whole can be looked at after it is finished, and the project memory the tool provides can be used by the organization, or by a new person to learn about the process in a particular organization.

2] Increased time efficiencies for senior and management staff

Senior and management staff are often occupied with being the central point for information and knowledge. By providing a tool that allows information to be easily searchable and retrievable, and providing a better overview of the development of the artefact, including the process and communication related to them, all people in the process will have access to better quality information. Thus, senior and management staff will be available for other tasks, resulting in overall saving of time, more efficient process and better artefacts. 3] Fragmented communication; between physical notes, emails, comments in pdf files etc.

A very common problem in projectual activity (of any kind, but design in particular) is that when developing an artefact there is a large amount of correspondence between people commenting on and discussing different types of documentation (images, text, 3D models etc.).

For example, an architect receives comments to something he/she is working on (a physical model or file). Receiving those comments by email is currently common practice. He/she has to go from comments in the e-mail to an e-mail attachment, perhaps to notes from a meeting, even to ask/call someone for additional information and eventually getting to an actual physical model/file to be improved (and back and forth) and continuing the correspondence by sending further attachments via e-mail. These complicated sequences to retrieve and use information often cause confusion, loss of time, miscommunication and great difficulties in finding out why something was done the way it was done.

One of the solutions the tool offers is to allow communication while developing an artifact within a single application. This way, the architect (or other professional) creates or opens a file and adds notes/comments to it, either to a preview or on top of the application where file is worked on. Person(s) working on the file will be notified with a reminder in the tool that he/she has notes to review. He/she can open the file directly from the tool, in any application where it was created and transparent notes are visible on top of the running program. They can be moved around and approved, for instance, while working on the file. One can also respond to the notes.

This improves communication and reduces unnecessary communication both in distributed and co-located work situations and makes the communication easy to follow afterwards. All notes and communication are also saved in the program and can be easily retrieved. These features increase overall efficiency of process by reducing miscommunication and clarifying the responsibilities and interdependencies of all parties involved.

4] Unable to find a specific piece of information

Another very common problem the tool addresses is the difficulty in locating specific pieces of information. Currently, when people look for information related to projects they:

-go through e-mails searching by who might have sent/said something in an e- mail; - try to locate the correct folder where a file might be;

- try possible file names;

- check printed papers related to the project, etc.

As the tool is independent from a folder system (and files are uploaded to a cloud/central database), and centralizes the information, different search strategies can be used, depending on the type of information that is being looked for (see chapter search function). Even files that are currently difficult to locate in folders, such as photographs or scans of hand written notes, can be searched/retrieved using different strategies and the information that currently is easily lost can be saved in the 'project memory' .

Claims

A computer implemented program for architectural or design project management comprising:

- providing a user interface for accessing and searching a project database, characterized in that it further comprises:

- generating representations of objects, searched from the project database, in a 3D visualization field, wherein the axes of 3D field are defined by the user and said representations are based on at least one attribute of the objects;

- creating, in the visualization field, 3D representations of connections between objects, and

- providing access to the objects searched from the project database through the representations of said objects in the 3D visualization field.

The computer implemented program according to claim 1, characterized in that accessing the database comprises creating projects.

The computer implemented program according to claim 1 , characterized in that accessing the database comprises defining information access levels for each user.

4. The computer implemented program according to claim 1 , characterized in that accessing the database comprises creating and managing project phases, project tasks and project breaks.

5. The computer implemented program according to claim 1, characterized in that accessing the database comprises creating and managing parties, teams and people.

6. The computer implemented program according to claim 1 , characterized in that accessing the database comprises at least one of: uploading, previewing, opening, saving, assigning/changing status and tracking changes in files.

7. The computer implemented program according to claim 1, characterized in that accessing the database comprises creating and replying to notes attached to files or file previews.

8. The computer implemented program according to claim 1, characterized in that accessing the database comprises creating meetings and accessing meeting related information.

9. The computer implemented program according to claim 1 , characterized in that database searching is based on semantic, temporal, spatial criteria or a combination thereof.

The computer implemented program according to claim 1 , characterized in that one of the axes of the 3D vizualization field represents time.

The computer implemented program according to claim 1, characterized in that the connections between objects in the 3D visualization are represented by lines, shapes or forms.

A computer readable medium characterized in that it comprises the computer implemented program as described in any of the preceding claims.

13. A computer system characterized in that it comprises:

- a database in which architectural or design project data are stored;

- a server connected to the database;

- at least one computer connected to the server, and

- at least one computer readable medium as described in claim 12, connected to the server and to the at least one computer.