Troubleshooting and frequently asked questions (FAQ)

Here you will find common errors, known limitations and frequently asked questions about work packages and transmittals.

TABLE OF CONTENTS

Common errors
Known limitations
What the module does not do
Frequently asked questions
Glossary

Common errors

Problem	Cause	Solution
The work package menu is missing	The licence for work packages is missing, or the user group does not have access	Check that the module is activated (contact Telaris) and that the user group has access
The package is not in the list	The package was created in a different project area	Switch project area and search again
The progress is standing still	The tags in the package lack requirements, or the requirements are not weighted	Check the requirements and the weighting on the tag types
Documentation is missing from the bundle	The checklists are not completed, or the files are on tags that are not in the package	Check the content of the package before the bundle is built
The document bundle does not arrive	The assembly runs in the background and takes time for large packages	Wait until the job is finished; check the status of the background job if the wait is long
The transmittal cannot be sent	Recipient, reason for issue or other mandatory details are missing	Fill in the fields and set the transmittal to ready
The recipient cannot open the transmittal	The link or the password is wrong, or the transmittal is closed	Send the link again, and check the status
The status cannot be changed back	The transmittal is closed	A closed transmittal is final; create a new revision instead
The deviation points are not shown in the package	The points are registered on tags that have not been added to the package	Add the tags to the package

Known limitations

Work packages belong to one project area, and the number series is specific to each area
The progress on the package comes from the requirements on the tags – without requirements there is no progress to show
Document bundles are built in the background, and are not immediately available for large packages
A closed transmittal cannot be reopened; changes require a new revision
Com and MC packages assume that the business actually works according to NORSOK Z-007
The recipient's access applies to the transmittal, not the work package as a whole

What the module does not do

The work package does not carry out the work – it gathers what is done on the tags
The transmittal is not an e-signature service; the acceptance is recorded in the system
The module does not replace project planning – progress schedule and milestones are in the planning module
The content of the document bundle is not quality-assured automatically; what has been filled in is included

Frequently asked questions

What is the difference between a work package and a deviation point?

The work package delimits a delivery to be completed and handed over. The deviation point is a single finding to be rectified. They are built on the same underlying structure, but are used for entirely different things.

What is the difference between a work package and a transmittal?

The work package is the content – the tags, the work and the documentation. The transmittal is the formal letter that sends the documentation out to the recipient.

Why does it take time to create the document bundle?

Because it is assembled as a background job. A package can contain hundreds of forms and files.

Can the recipient see the whole system?

No. The recipient opens the transmittal through a dedicated link with a password, and sees only the documentation that belongs to it.

How do we know the transmittal has been received?

The system records when it was opened and when it was accepted, with a timestamp.

We need to change something in a transmittal that has been sent – what do we do?

Create a new revision. A sent or closed transmittal is not changed afterwards.

What do the phases construction, mechanical completion and commissioning mean?

It is the usual division in industrial projects. Businesses that do not work this way usually use only the first stage.

Glossary

Term	Explanation
Work package	Delimited delivery that gathers tags, tasks and documentation
Work package type	The type that determines how the package behaves
Transmittal	Formal transmittal of documentation to a recipient
Transmittal type	The type that governs the setup of a transmittal
Reason for issue	The reason a transmittal is sent
Revision	Edition number of a transmittal
Document bundle	Combined PDF built from the documentation in the package
Incoming file	Documentation received from outside and placed on the package
Task file	File that originates from the work on the tags
MC package	Package for mechanical completion per NORSOK Z-007
Com package	Package for commissioning per NORSOK Z-007
MCSI	Status report for mechanical completion per system
CSRI	Status report for checklist status
Deviation point	Finding to be rectified, often called punch

Recent Searches

Troubleshooting and frequently asked questions (FAQ)