Document Management

A controlled record beyond an attachment

SERP Document Management supports documents, revision files, reviews, issues and engineering changes. It serves a different purpose from an ordinary transaction attachment: users can identify a revision and its review or release state when deciding which information should be used.

From draft to release

Create the document and revision, organize it with the available types, folders and tags, then request review through the intended workflow. Draft, Review and Released states describe different stages. Releasing a later revision can supersede the previous released version and make the older revision obsolete.

Reviews, issues and engineering changes

Document reviews have their own pending, approved, rejected and change-request states. Issues use a different set of states, while engineering changes provide their own context. Keep these distinctions visible in operating procedures so an issue resolution is not mistaken for document release authority.

Find and coordinate information

Controlled Documents and Advanced Search help locate records. Notifications and review views support follow-up. Check-out identifies the user holding the document lock; check-in releases it. Coordinate using the displayed information before editing a document that another person is working on.

Permissions and connected operations

View, edit, review, engineering-change and administration access are distinct. Connect document discussions with the relevant manufacturing, quality or sales context, but do not assume that attaching a controlled document authorizes production. Verify the released revision and required approvals at the business handoff.

Evaluate the capability with your team

Bring a representative business question and the people responsible for the source data, review and final action. Ask for the relevant company configuration, permissions and exception handling to be demonstrated. Follow the result back to its underlying transaction or document so the evaluation is based on an observable workflow.

Agree which functions are needed at launch and which depend on later configuration. Review the effect of incomplete data, missing permission and uncertain external outcomes. These details help set useful operating procedures and identify the information that an administrator must maintain.

Choose the current revision deliberately

A team should be able to identify which revision is being reviewed and which is released for the intended use. Uploading a new revision does not make it released. A later release can supersede an older released version, leaving that earlier revision obsolete. This distinction is useful when an engineering or operational instruction changes: a reviewer can discuss both the proposed change and the version currently in use without confusing their states.

Keep review responsibilities separate

The person preparing a revision may need edit access, while another person needs permission to review or release it. Document viewing, editing, review, engineering-change and administration are separate access areas. Define the responsibilities in the operating procedure and test the available actions with representative roles. A user who can attach a file to a sales record should not be assumed to have authority to release a controlled engineering revision.

Coordinate work around locks and notifications

Check-out information identifies the person holding the document lock. Use that context to coordinate changes before editing, and complete the intended check-in procedure when appropriate. Notifications and review lists help users locate work requiring attention. Search, folders, tags and types provide organizational context, but they do not replace the review or release decision. Finding a document is different from establishing that it is the authorized version for a particular business use.

Manage issues without losing their meaning

An issue can move through open, review, accepted, rejected, resolved and closed states, while a document review has a different state set. Preserve the object being discussed when recording an outcome. Resolving a reported issue does not automatically establish that a revision has been released. Engineering changes and follow-up should retain the relevant document context so the next person can explain the decision and find its supporting evidence.

Practical questions this capability can answer

• How are revisions controlled? Documents use separate draft, review and released revision states. Releasing a later revision can supersede the earlier release.
• Are attachments the same as controlled documents? No. Ordinary attachments do not establish revision review or release authority.
• What does check-out mean? Check-out identifies the user holding the document lock. Coordinate with that user and follow the authorized check-in process.