欢迎来到 Aconex。 您可能想知道，“什么是 Aconex，它如何帮助我？”。

建筑和工程项目会产生大量信息和数据。

文件； 图纸； 一致; 过程。

您面临着一项艰巨的任务，即在多个团队、组织和地点之间保持所有数据的组织、安全和访问。

如果到处都是，更不用说试图获得有用的见解了。

这就是 Aconex 的用武之地。

Aconex 将您的项目整合在一起，并将信息安全地在线存储在一个地方。 平衡数据安全和协作的需求。

您需要的所有工具都已内置。无论您身在何处，都可以快速查找内容、管理流程和成本、与项目中的每个人协作、从数据中提取有价值的见解并查看全局。 如果需要，您可以与其他系统集成。

当 Aconex 设置正确并且每个人都了解基础知识时，它可以帮助更快、更轻松地完成工作并在预算内完成。

那么它是怎样工作的？

在 Aconex 中取得成功的关键是在前期和整个项目中捕获所有相关信息。 我们使用 Mail 和 Document 类型来做到这一点。

邮件用于通信、问题、答案、建议和其他过程。

Documents用于图纸和其他需要经过一系列修改的文件。

邮件和文档类型可帮助您设置正确的信息。 选择类型会设置表单以在正确的时间收集正确的详细信息。

这一点点的工作可以节省时间，并释放搜索、工作流、报告和几乎所有其他过程的力量，从开始到项目结束。

在 Aconex，您的信息被安全存储并有选择地共享。

可在任何设备上、任何地点访问，您的信息就是您的信息。 首先，组织只能访问他们创建或接收的数据。 然后每个组织决定他们与他人分享的内容。 没有人会自动访问项目中的所有内容。

此外，Aconex 会保留所有内容的记录，因此您始终可以看到谁做了什么，无论项目或所涉及组织的规模如何。

这个公平的竞争环境创造了信任和共同的责任，鼓励每个人合作并在同一页面上。

而且，这仅仅是个开始。 一旦您了解了基础知识，Aconex 将成为您的一站式商店，提供文档审查和标记、现场检查、问题和成本管理、BIM 模型等等。

在您的 Aconex 之旅中，支持中心将成为您的向导，通过像本文这样的操作方法文章和视频的组合，详细介绍 Aconex 的方方面面。

欢迎来到 Aconex，很高兴与您合作。

So, what is a Project Admin and what do they do?

A Project Administrator, or Project Admin, works for the Aconex project-owning organization. They manage project-wide settings that affect everyone working on a project.

Project Admins ensure each organization on the project has all they need to keep the project running smoothly. This includes setting up the way users work with Mail and Documents throughout the project.

They also manage access to the project by deciding how users can be invited. When required, they can remove users and archive organizations that are no longer participating in the project.

While Project Admins have access to project settings, they don't have any extra access to project data. Each organization decides who can see its data, so no one sees more than they need.

Now you know what a Project Admin is and what they do.

所以，我们已经登录了 Aconex，并被邀请参与一个项目。

任务页面是我们看到的第一个页面。它就像是你在 Aconex 的主页。

在这里，我们可以找到需要处理的事项，查看我们参与的项目，并且有常见任务的快捷方式。

在左侧面板中，我们可以访问其他我们被邀请参与的项目的信息。

要查看我们所有项目的任务汇总，可以点击这里。

或者我们可以通过这里的下拉菜单快速切换它们 - 这在 Aconex 的任何地方都可以使用。

哦，我们在 Five Star 项目上有几个需要处理的任务。

在处理这些任务之前，让我们快速看看如何在 Aconex 中导航。

在这里是主菜单。它始终可见，这使得移动变得简单。

每个菜单都提供了通往最有用操作的快捷方式，例如搜索图纸或发送 RFI。

我们每个人看到的内容可能会稍有不同，

这取决于项目配置和分配给我们的权限。

如果我们没有正确的权限，可以联系组织管理员。

我们可以在这里找到他们。

这些是我们组织中 Aconex 的主要联系人，他们管理我们的用户权限。

如果我们遇到困难，应用内帮助从未远离。

点击这里查看文章、视频和指南 - 始终与您当前所在的屏幕相关。

好的，现在我们已经浏览了一下，让我们回到那些任务上，它们不会自己完成。

首先是邮件收件箱。

任何未读、待处理或逾期的邮件项目都会显示在这里。

嗯，我们有几封邮件逾期。

我们只需点击邮件以查看更多细节。

默认情况下，这个列表中显示的是十个最旧的任务，但我们可以点击“查看所有”，这样可以显示所有任务。

让我们返回任务页面。

接下来是传输文件。传输文件是我们在组织之间发送文档的方式。

看起来我们被分配了一些需要审核的施工图。

和邮件一样，我们可以点击链接查看更多细节。

当我们向下查看屏幕时，

我们还会找到 Aconex 其他功能的行动项，

例如包裹或供应商文档。

好的，我们已经看到了任务页面上所有可以看到的内容。全部就绪。

不妨去 Aconex 的任务页面四处看看？

Today we'll look at the details of our project. This is the first thing we see in project settings.

At the top, we can set our project's logo. It appears in any mail sent on the project, and on the tasks page. Let's upload a logo by clicking the edit button and dropping in our image.

Next is the project name and code. We should never need to change these. 

The short name is used in places like the project list on the Task page and the project selector at the top of the screen. All users can see this, so if we need to change it, we'll let our users know in advance. 

We'll skip down to Access Level.

We can set the default access level for new users to normal or read only, we'll leave it as normal.
And here we can change the access level for a whole organization. As well as normal and read-only, we can choose archive.
Archive is handy when we have organizations no longer working on a project. They can still view their existing data, but they can't receive mail or update documents. They are hidden in the project directory, and can't be re-invited to the project, unless we change their access level back to Normal.

Finally, we'll check the Contacts section. This information is shown in the directory, so it’s a good idea to make sure the address and contact numbers are correct and up-to-date. 

Remember we should always communicate any project setting changes to the team –before we make them. This keeps our team informed to prevent any disruption or confusion.

Today we'll learn how to configure Project Roles. 

These help us set the types of information each organization on the project can create, such as Mail and Document types.

Because it's project-level, a subcontractor, for example, can have different roles for each project they're on, depending on what they need.

Assigned roles don’t restrict the type of information someone can view; just what they can create. 

From Setup, we click Project Settings. Then, select Mail and Documents Role Settings.

All organizations working on this project are listed here. And, here are the roles they've been assigned. 

Each project starts with an initial set of roles. However, as needs change, we can update the project roles and even add new ones. Let's add a new one now.

We click here to create a new role. First, give the role a meaningful name.

Let's create this one for the consulting organizations on this project.

The set as default option is something we’ll come back to in a moment.

The four tabs we need to configure are for Mail Types, Doc Types, Doc Statuses, and Review Status Sets – which relate to Workflows.

On the left we see the list of available mail types and on the right are the types selected for this role. Let’s select a couple of types.

'Notice to Proceed' and 'Instruction' are needed by consulting organizations. Just click and use the arrows to move them or double-click a type.

We need a 'Change Order', but it's not on the list. We click the Show All checkbox and filter to find it. Then we double-click to add it.

Now, let's do the same for Doc Types, <pause>, and then Doc Statuses. 

We should keep the available types as few as possible to help the consultants find the right ones quickly with few mistakes.

We won't configure Review Status Sets today but the process is the same. 

As a Project Admin, it's important to make sure organizations newly invited to our project are assigned to the correct role.

If we forget this, they may end up with access to the wrong Mail and Document types.

Let's set this one as default. 

Once we're done, click OK to save the role. 

We can see the newly added role here, and it's clearly marked as the default role.

Finally, we need to assign the role to the appropriate organizations on this project.

To assign the role, we tick the box for the organization under the relevant role. If we tick more than one role, they will get access to all the types from both roles.

That's how we add new roles, but how do we edit an existing one? It's easy. On this screen, we just click the role name.

We remove the Doc Status 'For Information', as it's no longer needed for this project, and click OK.

Congratulations, now you know how to create and edit Project roles. You won't need to do this often, so we suggest bookmarking this page to come back to, when you need a refresher.

Today we’ll learn how to configure Document Fields.

Document Fields help us capture information about our documents on the project. This helps us, and others easily find them later on.

The fields are set up when a project is first created, but we can make some changes as the project evolves.

From Setup, Project Settings, we click Documents and then Document Fields.

If we scroll down we see lots of fields and options. 

Let's look at these in more detail.

Starting on the left is the Label.

It's best to keep these easy to understand, so users know what to enter in each field.

To avoid confusion, we don't recommend changing a field label on an active project. But if we need to, we'd contact Oracle support.

Tick 'use field' to make a field available. Some fields such as the Document Number must be used on all projects.

If we need to, we can make a field Mandatory here.

Next, we see the Type and max length of each field. These can't be changed.

We used this information during the initial project setup, to choose which fields were needed on the project.

We have text fields, select lists, and more. 

The Discipline field is a single select list.

Select lists contain values that users choose from a dropdown list. 

Each value can be up to 50 characters in length.

Let's edit the list of disciplines. 

We'll add 'Structural', 

And give it a code, which is used for autonumbering.

Save the changes.

Now all users on the project can choose 'Structural' when they upload their documents.

Let's return to the fields list.

Editable Inline allows us to make changes to fields directly from the upload screen, so we don't have to go into setup each time to add more values.

We'll scan over the list and make any other changes needed, then click Save.

It's best practice to only add the document fields we know we'll use. This helps keep the list short and ensures we only capture the information we need.

Now you've got the basics of document fields, why not log in and check your project is set up for success?

Today we'll look at our project preferences in Aconex.

We’ll head over to the Setup menu, Preferences, and click the project tab. 

If a setting has a recommended default, checking the box in this column will use that.

The default setting should work for most projects, but if we want to make changes, we need to uncheck it.

Then, switch things on and off in the Settings column as needed.

Changes in this top section will apply to all users in our organization who are working on the project.

We’re from the organization that owns the project, so we can see project-wide settings. These apply to all users on the project, not just the project-owning organization.

Another Project Administrator may change settings here that can override ours, so it’s important we communicate any changes.

Let’s focus on the areas that are most relevant for a new Project Admin.

Under Security settings there are a few options:

Project-wide password strength lets us set the password requirements for all users on the project.

Project-wide password access rule controls expiry options for users on this project.

And, project-wide session time duration sets how long users’ web browsers can be idle before they’re automatically logged out of Aconex.

Further down, the project invitation method controls how users can be invited to our project.

The default and recommended setting is Open. This means that anyone on the project can invite anyone else to collaborate. Note that data ownership rules still apply, and each organization only sees information that was created by or shared with them.

Restricted automatically sets newly invited users as shadow users. A shadow user is hidden from the project directory and can only be made visible by a project admin. 

Explicit means that only Project Administrators from the projects owning organization can invite new users to the project. This comes with a bit of extra admin so is really only useful for sensitive projects, such as defense.

Under Documents, Project-wide auto numbering allows the project’s documents to be automatically assigned unique document numbers. 

Here, we can set the default columns that appear in search results.

If there's a commonly used upload profile on your project, this can help speed up uploads

And here we can set the arrangement of search filters for Documents <pause> and Drawings. 

Here in Mail, we can set values for the “Reason for issue” field. This is used when sending transmittals.

We can also choose how mail is numbered to ensure a consistent sequence across the project.

We should always keep the project roles locked. This ensures the mail and document types we've configured for each organization cannot be overridden. 

That's it. We can save our changes and our project preferences are all set.

Today we’ll learn how to manage access to our project.

Let’s start with how to add, or invite, users.

Go to Setup and select project settings.

Under project, select project participants.

Here's the list of users currently invited to this project.

To invite someone, click invite user and start typing their name.

Find the correct person from the correct organization, and select them from the drop-down.

We check the box to make sure they get an email invitation. This helps them know what to do next.

If we can't find the user we can try the advanced search. This gives us a few more search options.

We can search by organization name, first name, and more.

Once we've found who we're looking for, we have two user types to choose from. We can either add them as a full user or a shadow user.

Both user types have access to the project, but the shadow user cannot be seen by others in the project directory. This is useful for people who just need to view information without being involved in project processes.

Let’s add as Full User, and click OK.

As the Project Admin we can see some users are shadowed on our project. Click their eye icon to make them visible in the project directory. This helps others find them to collaborate.

Sometimes a user or organization will leave the project. We can select users and remove them here. At least one user needs to remain in each organization - we cannot remove them all, as they are entitled to view their historic data. 

If we want to remove an entire organization, we'll need to change it's access level. 

Under project, click project details, and scroll down to access levels.

Click Edit and select the organization we want to remove.

Set access level, to archive. 

This organization is no longer participating on the project. They can still view their existing data, but they can't receive mail or update documents. They are hidden in the project directory, and can't be re-invited to the project, unless we change their access level back to Normal.

Congratulations. Now you know how to manage access to your project.