SoluDyne APOS

APOS Advanced Process Oriented Steering

APOS is process tool that ensures compliance with external laws and regulations, standards and requirements in the work processes. Handle all tasks according to documentation management in relation to the work processes.

The core elements of APOS are Work Processes with Roles, Governing Elements, Job Function - Role connection and Competency Requirements.

Net Account

Best Practices & Other Governing Elements

03 - APOS

01 - Introduction

B-10059 - Work Process - Definition

NO: En arbeidsprosess beskriver aktiviteter som må gjennomføres i en bestemt rekkefølge, for å oppnå en ønsket tilstand; leveranse, resultat, produkt, tjeneste etc..

En arbeidsprosess beskrives grafisk ved bruk av et flytskjema, som viser aktiviteter i rollebånd, med roller knyttet til stillinger. Et flytskjema eies av en prosesseier.

En arbeidsprosess er et krav. Det vil bl.a. si at formell avviksbehandling kreves dersom arbeidsflyten i et flytskjema ikke følges.

B-12428 - Navigating in Processes

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes basic skills necessary to navigate in processes in SoluDyne.


01 Description

It is possible to navigate in processes from the Main Page in the system. See example below for how to do this.

02 Example

  

Navigate from the Home Page and down to the first Sub Process Level.

  1. Click on the Main Process shape Operations.

 

  1. Click on Sub Process 03 - Work Permit.


 

  1. Click on Sub Process 02 - Plan and prepare Work Permit.

 

  1. Icons indicate if Requirements, Best Practices or Local Amendments are linked to an activity.

 

  1. Place the mouse pointer on the activity shape Evaluate need for SJA.

  2. The pop-up window shows the content of Governing Elements linked to the activity.

 

  1. Click on the Info button.

  2. Click on Preferences in the menu shown.

 

  1. In this dialog it is possible to change "Show only Requirements and Best Practice where".

 

 

  1. Place the mouse pointer on a Role Band, here Originator - Applicant.

  2. The pop-up window shows the Job Function linked to the selected Role.

B-12436 - Check for Definition

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes the how to check the definition of a word in SoluDyne.

01 Description

When double-clicking on a word, the user can check the definition of this word. All Definitions are defined in a Definitions register. If no definition exists, the text "No hits!" appear when double-clicking the word.

02 Example

 

  1. Double-click on a word to view the Definition of the selected word.

 

 

After double-clicking the word, the definition shows. If "Not hits!" appears, the word has not yet been defined in the Definition library.

02 - Elements

Best Practice

B-10056 - Best Practice - Definition

NO: Beste Praksis beskriver metode og gir uttrykk for hvordan en aktivitet skal utføres.

Beste Praksis er også i mange tilfeller assosiert med et krav og beskriver derved en metode som også ivaretar kravet.

Beste Praksis eies av prosesseier som er ansvarlig for kontinuerlig forbedring av den aktuelle Beste Praksis på basis av tilbakemelding fra brukerne, hendelser eller annen relevant input.
 
Beste praksis deles inn i følgende kategorier i forhold til avviksbehandling:

Kritisk Beste Praksis (Ikon Rød 1st):
Skal følges strengt, men avvikende utførelse kan være aktuelt dersom spesielle forhold krever det. Avviksbehandles i Synergi, med godkjenning fra eier av Beste Praksis. Denne kategorien brukes for Beste Praksis som er særskilt kritisk for sikker utførelse eller andre viktige forhold.

Normal Beste Praksis (Ikon Blå 1st):
Skal følges konsekvent, men alternativ og minst like sikker utførelse er tillatt i enkelttilfeller, uten formell avviksbehandling i Synergi. Alternativ utførelse skal kvalitetssikres og godkjennes i den enkelte org.enhet. av leder operativ enhet (f.eks. Plattformsjef/Terminalsjef/Boreoperasjonsleder). En har ikke anledning til å etablere en permanent alternativ praksis, men har anledning til å godkjenne enkeltvise avvik fra Normal Beste Praksis.
Det skal gjennomføres en saksbehandling som sikrer at den alternative utførelsen minst er like god som Normal Beste Praksis og at overordnede krav ivaretas. I noen tilfeller vil det være nødvendig å søke assistanse fra fagavdeling på land, for å verifisere alternativ utførelse. Saksbehandlingen registreres i APOS under den aktuelle Beste Praksis, ved bruk av "Alternativ metode".
Innholdet i Beste Praksis skal være styrende og beskriver hvordan utførelsen skal være. Dersom en har behov for en omfattende, detaljert, styrende arbeidsbeskrivelse (sjekkliste) skal denne legges inn som et linket filvedlegg til den Beste Praksis.

Dictionary

B-12207 - Abbreviations and Definitions

Overview

Definitions and abbreviations are created in a Dictionary Register in Handbooks & Manuals and can be linked to and from elements. The drilldown D117 Definitions and Abbreviations shows which elements a dictionary entry is valid for. The Report R110a Process & Requirement is used for creating a complete report of a process or a sub process with all its related elements. The report heading displays all definitions and abbreviations that are referred to and from the current process area. The following functionalities are covered:

  1. Create Dictionary Register with Definitions and Expressions
    • The Dictionary Register with dictionary entries are created by using the New-button. A dictionary entry can be set as Governing or Advisory. If the type is set to Governing, the heading in the Dictionary Pop Up is shown as red. If the type is set to Advisory, the heading in the Dictionary Pop Up is shown as blue.
  2. Link from Dictionary Entry to Elements
    • A dictionary entry can be linked to the elements Main Process, Sub Process, Workflow with Roles, Activity, Requirement, Best Practice and Local Practice by using Add links on the dictionary entry's form.
  3. Link from Elements to Dictionary Entry
    • The elements can be linked to a dictionary entry by using Add links on the elements' respective forms.
  4. Show Elements where the Dictionary Entry has been linked to in D117 Definitions and Abbreviations
    • After having linked the Dictionary Entry to the Elements for which they shall be valid, the Elements will appear in the drilldown D117 Definitions and Abbreviations. By selecting a dictionary entry, all areas where the word or expression has been linked to will be listed below Links.
  5. Show Dictionary Entry in the report R110a Process & Requirement
    • The report R110a Process & Requirements will display all relevant dictionary entries below the items that the entry is linked to or from. 

Prerequisites

  1. Must be logged in as a user that has permission to add new registers with child nodes to perform item 1.
  2. Must be logged in as a user that has permission to edit nodes to perform items 2 and 3. 

    Description

1. Create Dictionary Register with Definitions and Expressions

 

  1. Click on the New-button on the SoluDyne Toolbar.
  2. Click on New Register.
  3. Click on Dictionary.

 

  1. Fill in a title.
  2. Fill in Owner and Responsible.
  3. Click on Publish.

 

  1. To add dictionary entries, open Handbooks & Manuals.
  2. Click on the Dictionary Register in Handbooks & Manuals.
  3. Right click on the Dictionary in the tree.
  4. Click on New Node.
  5. Click on Dictionary Entry, or Dictionary Group to group different Dictionary Entries.

 

  1. Fill in the word/expression which is to be described, e.g. Revision Handling.
  2. Select whether the dictionary entry shall be Governing or Advisory by clicking on the drop down menu arrow.
  3. Describe the dictionary entry in the Description field.
  4. Click Publish.

Link from Dictionary Entry to Elements

 

  1. Open Handbooks & Manuals.
  2. Click on the Dictionary Register.
  3. Navigate to and click on the Dictionary Entry, e.g. Revision Handling, and set in Edit mode.
  4. Click on Add links and a dialog box will appear.

 

  1. In the dialog box, navigate in the tree and select the relevant Element, e.g. the Flowchart M1.01 - Planning Work Order.
  2. Close the dialog box by clicking on the X in the top right corner.

 

  1. The linked Element is now visible below Links.
  2. Click Publish. 

 

3. Link from Elements to Dictionary Entry:


 

  1. Navigate to the Element, e.g. Flowchart 01 - Change Process, and click on Edit.
  2. For Flowchart, click on the arrow to go to page 2 and the Element's form.

 

  1. In the form, click on Add links to Definitions and a dialog box will appear.

 

  1. In the dialog box, navigate in the tree and click on the relevant Dictionary Entry, e.g. Revision Handling.
  2. Close the dialog box by clicking on the X in the top right corner.

 

  1. The Dictionary Entry is now visible below Definitions.
  2. Click on Publish.


4. Show Elements where the Dictionary Entry is valid for in D117 Definitions and Abbreviations

 

  1. Open Handbooks & Manuals.
  2. Click on the drilldown D117 Definitions & Abbreviations.
  3. Click on Show Filter.
  4. Write the title of the Dictionary Entry, e.g. Revision Handling.
  5. Click on Filter.
  6. The areas where the Dictionary Entry us valid for is listed below Filter result.


5. Show Dictionary Entry in the report R110a Process & Requirement

  

  1. Open Process.
  2. Click on the report R110a Process & Requirements.
  3. Click on an Element, e.g. the Flowchart 01 - Change Process to which the Dictionary Entry Revision Handling has been linked. 
  4. The Dictionary Entry is visible in the report.

Document

B-13169 - Document Class

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes the Document class functionality in SoluDyne.

01 Description

The Document Class is Governing Element that can be used in SoluDyne for handling documents and use in Flowcharts with Activities.

When mouseover an Activity in a Flowchart with a Document, the Document Title and description is shown in the pop-up.

02 Example

  1. Open up Expanding Menu.
  2. Click on Handbooks & Manuals.
  3. Click on the Manual where the Document is to be created.
  4. Right click on a Section where the Document is to be created. If no sections exist, start with creating a new Section under Manual.
  5. Click on New Node.
  6. Click on Document.
  7. Fill in ID.
  8. Fill in a Title.
  9. Set a Type from the dropdown menu
  10. Owner and Responsible are inherited from the parent node.
  11. Fill in a description in the Description field.
  12. Click on Publish button to Publish Document.

 

Figure 1. Document form

 

Figure 2. Flowchart showing Document in a Flowchart and Activity.

File

B-11698 - File Nodes

00 Overview
01 Description
02 Example
02.1 Creating File node
02.2 Adding File node via drag & drop
02.3 Basic Operations
02.4 Renditions

00 Overview

This Best Practice describes how to work with File nodes in SoluDyne.

01 Description

In order to use the same standard functionality for file attachments as for other data classes in SoluDyne, instances of the File class can be created. The information registered in the File nodes (file name, size, creation date, etc) can be searched for, file names can be altered, and file copies with alternative formats, which are called renditions, can be provided.

The basic principles of working with file attachments in SoluDyne are applicable to the File nodes, see B-12190 - Add and Edit Files. The File nodes also support simple addition via drag & drop into various nodes - for example, into Section nodes.

Support for various file formats is provided by File nodes via renditions, see B-12947 - How to work with File renditions.

02 Example

02.1 Creating File node

  1. Expand the desired parent node in the Treeview.
  2. Use New Node menu from context menu or from the SoluDyne Toolbar and select File in it. If present, Templates can be used for new File nodes with predefined content.
  3. Confirm the new node creation if required.

  
Figure 02.1.1 - Select File from New Node menu

  
Figure 02.1.2 - New, empty File node created

02.2 Adding File node via drag & drop

  1. Expand the desired Section node in the Treeview.
  2. Open the folder containing the file to be attached in Windows Explorer.
  3. Drag the file from the folder into the target Section node.
  4. Confirm the drop of file.
  5. A new File node containing the attached file will be created under Section node.

  
Figure 02.2.1 - Drag & drop of file into the Treeview

  
Figure 02.2.2 - File drop confirmation

  
Figure 02.2.3 - File node created with dropped file attached to it

02.3 Basic Operations

See examples from B-12190 - Add and Edit Files.

02.4 Renditions

See examples from B-12947 - How to work with File renditions.

B-12232 - Linking Files to Governing Elements

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to create, link and show links to files in Governing Elements and on Processes in SoluDyne.

01 Description

Perform the following to create, link and show links to files in Governing Elements and on Processes:

  1. Navigate to a Section and create a new file by clicking on a File node template.
  2. A new File node is created.
  3. Rename the File and update the name of the physical file by pressing the Update Filename button. Remember to publish the node.
  4. Navigate to a Requirement node. Link the File node to the requirement by pressing the link button on the SoluDyne Toolbar.
  5. Select Handbooks and Manuals.
  6. Select the register where the File node can be found.
  7. Navigate to the File node and click on it to link it to the Requirement.  Click on the anchor image to insert the link in the Requirements text field. Note ! The Requirement text field must have focus / be selected before the anchor can be inserted.
  8. The link to the governing element has been inserted in the Requirement text field.
  9. Link the Requirement to an Activity.
  10. The content on the Requirement text field including the link to the File node is shown in the shape popup.
  11. Clicking on the link to the File node the File node form is opened.
  12. If the physical file is to be opened directly when clicking on the link in Requirement text field, click the hide page button on the toolbar; hide / show eye, to hide the first page. The file node will then be opened directly.
  13. For MS Word document a dialog box will show before the document is opened.

NOTE: Links should be created from Processes/Activity to Governing Element for the element to be shown in Shape Popup in flowcharts.

02 Example

 Figure 1. Navigate to a Section and create a new file by clicking on a File node template.

Figure 2. A new File node is created.

Figure 3. Rename the File and update the name of the physical file by pressing the Update Filename button. Remember to publish the node.

 

Figure 4. Navigate to a Requirement node. Link the File node to the requirement by pressing the link button on the SoluDyne Toolbar.

Figure 5. Select Handbooks and Manuals.

Figure 6. Select the register where the File node can be found.

Figure 7. Navigate to the File node and click on it to link it the Requirement.  Click on the anchor image to insert the link in the Requirements text field. Note ! The Requirement text field must have focus / be selected before the anchor can be inserted.

Figure 8. The link to the governing element has been inserted in the Requirement text field.

Figure 9. Link the Requirement to an Activity.

Figure 10. The content on the Requirement text field including the link to the File node is shown in the shape popup.

Figure 11. Clicking on the link to the File node the File node form is opened.

Figure 12. If the physical file is to be opened directly when clicking on the link in Requirement text field, click the hide page button on the toolbar; hide / show eye, to hide the first page.  The file node will then bi opened directly.

 

Figure 13. For MS Word document a dialog box will show before the document is opened.

FlowChart with Roles

B-10021 - Setting and updating Owner and Responsible on Flowcharts

Content

0.00   Definitions
1.00   General Description
2.00   Question
3.00   Answer
4.00   Sample Session


0.00   Definitions

N/A

1.00   General Description

When updating the fields Owner and/or the Responsible within a template of type Flowcharts with Roles, this will affect elements that reside beneath the Flowchart.

2.00   Question

When updating the fields Owner and/or Responsible on a Flowchart with Roles, what are the effects?

3.00   Answer

All elements that reside beneath the Flowchart with Roles will have the fields Owner and Responsible updated. This requires that an actual change is performed within one or both Owner and Responsible fields on the Flowchart form and the Save button is clicked. The fields Owner and Responsible for these child nodes will be updated upon clicking the Save button. All elements that reside below the Flowchart will have their Owner and Responsible fields updated, even elements that don't have these fields available on their forms.

4.00   Sample Session

The Owner and/or the Responsible values on Flowcharts with Roles:


Figure 1 - Owner and Responsible is visible on Flowcharts and can be changed - Changes will propagate down into child nodes, like Activities or Requirements.

Changing the values of Owner and/or the Responsible values on Flowcharts with Roles:


Figure 2 - The Responsible value is being changed. The changes will apply to all child nodes after clicking the Save button.

Checking that child nodes are affected:


Figure 3 - All elements below the Flowchart are updated, note that this Requirement now has the same value for Responsible as the Flowchart was just set to.

B-12218 - Purpose & Scope on Flowchart

00 Overview
01 Description

02 Sample Session

00 Overview

This Best Practice describes the Purpose & Scope on flowchart functionality in SoluDyne.

01 Description

Purpose & Scope is set on page 2 on a flowchart. Purpose & Scope is visible under heading '1.1 Purpose & Scope' when running Print Tree.

02 Sample Session

Set Purpose & Scope on flowchart 'Q05.01 Management Review of Management System':

  1. Open flowchart 'Q05.01 Management Review of Management System'
  2. Navigate to page 2
  3. Type in Purpose & Scope into the Description field. See figure 1
  4. Publish flowchart
  5. Open Print Tree and verify that Purpose & Scope is visible under heading '1.1 Purpose & Scope'. See figure 2

 
Figure 1. Purpose & Scope

 
Figure 2. Purpose & Scope visible on Print Tree

B-12817 - How to import FlowCharts from file

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes import FlowCharts from files into SoluDyne. Also, it contains an example of Import of Visio files in VDX format.

01 Description

Process Charts can be imported from files with one of formats supported by SoluDyne Import functionality.

The processes can be imported into existing Main Process, Sub Process of FlowChart with Roles nodes. A file containing multiple charts can be imported only into a Main Process or a Sub Process. Each imported chart will be represented as a child FlowChart node. A warning message will be displayed and the operation will be cancelled if the user tries to import a file with several charts into a FlowChart node.

Existing SoluDyne nodes will be synchronized if the same document is being imported again. I.e. new Shapes and Flow Charts will not be created if they were already imported. The existing nodes will be updated to reflect changes in the modified source document. 

02 Example

One of formats supported by SoluDyne import is Visio files in VDX format. Files of other Visio formats must be converted to VDX before importing them into SoluDyne.

Here is a list of steps for importing a Visio drawing into a Sub Process node in SoluDyne:

  1. Select a node which a Visio file is to be imported into.
  2. Right-click on the node and select "Import FlowChart from file" in the context menu (see Figure 1).
  3. Select a VDX file in the opened "Select file" dialog and click "Upload" (see Figure 2).
  4. Wait until the import operation finishes.
  5. The imported drawing will appear as child FlowChart with Roles and Activity nodes under the target Sub Process (see Figure 3).

  
Figure 1. The "Import Visio" command is called from the context menu.

 
Figure 2. A Visio file is selected for upload into SoluDyne.

 
Figure 3. The imported Visio drawing appears as child FlowChart with Roles and Activity nodes under the target Sub Process.

B-13167 - How to import BPMN file

00 Overview
01 Description

01.02 Mapping
01.03 Outside Scope of mapping
02 Example

00 Overview

This Best Practice describe the import of BPMN files into SoluDyne.

General principles of the Import functionality are described in B-12817 - How to import FlowCharts from file. The given document described some details of import from BPMN files.

01 Description

SoluDyne supports import of processes from BPMN files. Imported processes must be provided as XML files with processes' schema in accordance with BPNM standard. File extension must be .BPMN.

BPMN process in one file is imported into one FlowChart node. The process can be imported into existing Main Process, Sub Process of FlowChart with Roles nodes. When BPMN is imported into a Main Process or a Sub Process, it will be represented as a child FlowChart node. When BPMN is imported into FlowChart node, then the given FlowChart will be updated.

Existing SoluDyne nodes will be synchronized if the same BPMN process is being imported again. I.e. new Shapes and Flow Charts will not be created if they were already imported. The existing nodes will be updated to reflect changes in the modified source document. 

01.02 Mapping

Import is performed in accordance with the following mapping of BPMN objects to SoluDyne shapes

BPMN Type/Symbol BPMN Elements SoluDyne Shape
Task businessRuleTask
manualTask
receiveTask
scriptTask
sendTask
serviceTask
task
userTask
BPMN Activity
Gateway complexGateway
eventBasedGateway
exclusiveGateway
inclusiveGateway
parallelGateway
Decision
Start Event startEvent BPMN Start Event
End Event endEvent BPMN End Event
other types of Event

implicitThrowEvent
intermediateCatchEvent
intermediateThrowEvent

BPMN Intermediate Event
Sub Process adHocSubProcess
callActivity
callChoreography
subProcess
transaction
Predefined Process
Data Object dataObjectReference Data Object
Sequence flow sequenceFlow Connector 

01.03 Outside Scope of mapping

Data Object Reference

BPMN Charts contain dotted lines between Activity/Task shapes and Data Object shapes. They are represented by references elements: dataInput, dataOutput, dataInputAssociation, dataOutputAssociation etc. These references look like Connectors, but they have some differences. For example, such lines do not have geometry definition in BPMN file. So, the import generates shapes, but does not to provide lines for references (because SoluDyne System does not have corresponding object/shape for them).

On example below, BPMN diagram has dotted lines from/to Data objects, but the result of import of this BPMN into SoluDyne System does not.

02 Example

 
Figure 1 - BPMN diagram with Data Objects.

 
Figure 2 - Imported BPMN with Data Object in SoluDyne.

Text Annotation

The represented example contains Text Annotation elements; "Get a collection of Data" and "Each instance processes a single item of the collection data". BPMN Import does not support this type of elements. The result of import into SoluDyne does not contains corresponding shapes..

Embeded Sub-Processes

The implemented Import BPMN does not support embedded Sub-Processes. The example below is outside scope of the existing functionality:

  
Figure 3 - Embedded sub-process. Not supported by the Import.

03 Example

Example of import of "Simple Process" BPMN process into SoluDyne System.

 
Figure 4 - "Simple Process" process shown by Yaoqiang BPMN Editor 4.0.

 
Figure 5 - Imported "Simple Process" process.

Key Control

B-12763 - Creating a Key Control

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to model a Key Control in SoluDyne.

01 Description

A Key Control is a management tool which helps the business mitigate risk, implement quality management within work processes and ensure compliance.
 
In APOS it is used as a governing element that is used to register a requirement to a control / control activities that must be performed by the specified role.

The purpose of Key Controls is to:

  • Manage risk. By linking Risks to Key Controls, the company is able to visualise risk mitigation.
  • Support quality management by:
    • Providing routine and consistent checks to ensure data integrity, correctness, and completeness;
    • Identifying and addressing errors and omissions;
    • Documenting and archiving material and recording all quality control activities.
  • Ensure compliance with company policies and procedures.

02 Example

 

  1. Open the SoluDyne Expanding Menu.
  2. Select Handbooks & Manuals.
  3. Select the Manual where the Key Control will be located.
  4. Expand the Manual.

NOTE: If no manual or section(s) exist, start with creating a new section under Manual. See B-12480 - Best Practice for Modeling a Manual and B-12481 - Best Practice for Modeling a Section for more information.

 

  1. Right click on the specific section where the Key Control will be created.
  2. Select "New Node".
  3. Select "Key Control".

 

Close the slide menus to enlarge the editing field.

  1. The ID is automatically generated, but this can be customised if required.  
  2. Owner and Responsible are inherited from the parent node. These can be changed if required.
  3. Fill in the Title.

 

  1. To add the Performer, select "Add Links" in the Performer Field.
  2. Add the Performer(s) by navigating to the required role or job function in the pop-up. This field is mandatory. Multiple roles/functions can be selected if required.
  3. When a function/role has been selected, it will appear in the links tab at the bottom of the pop-up.
  4. Close the pop-up window when you are finished.

Add the Involved in the same way as adding the Performer. This field is mandatory. Multiple roles can be selected if required.

   

  1. Add the Frequency by selecting an option from the drop-down menu. This field is mandatory as indicated by the blue icon.

NOTE: All required fields are indicated as mandatory by the blue icon. Fields which do not contain this icon are optional.

 

  1. Add the Deadline by selecting an option from the drop-down menu.

All dropdown menu categories are added in the same way.

 

  1. Add the How description. This is a free text field where the work steps and controls are described.

All free text fields are filled in using the same method.

Continue to add information for remaining dropdown or free text fields, including:

  • Type of Validation
  • Document Requirements
  • Risk Area
  • Control characteristics

 

  1. To add the Type, tick one of the two options (Preventative/Detective). This field is optional.

All check-box fields are filled in using the same method.

Continue to add information for remaining dropdown, free text and check-box fields, including:

  • System
  • Materiality
  • Assertions

 

  1. If required, add additional Document Links by selecting "Add Links". Navigate to the required item in the register pop-up in the same way as Performer and Involved were added.
  2. If required, add links to Risks selecting by "Add Links". Navigate to the required item in the register pop-up in the same way as Performer and Involved were added.
  3. Publish the Key Control when you are finished.

B-12764 - Linking Key Controls to a Flowchart Activity

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to link a Key Control to an activity in a flowchart.

01 Description

A Key Control is a type of Governing Element that can be linked to a process, a sub-process, a flowchart and an activity in a flowchart. For more information on linking Governing Elements in general, see B-12498 - Best Practice for Linking Governing Elements.

02 Example

 

  1. Navigate to the required flowchart.

 

  1. Select the activity where the Governing Element will be placed. In this example, "Analyse Loan Requirements: Short / Long Term".

 

  1. Put the activity into edit mode by selecting edit-button.  

 

  1. Select the "Link" button on the editor tab.

 

  1. Expand the tree to locate the Key Control.
  2. Select the required Key Control.  
  3. The linked element is now visible in the links list.
  4. Close the window.

 

  1. Publish the activity.
  2. Navigate back to the flowchart.

 

  1. Control that the Key Control icon has appeared on the activity.

Local Amendment

B-10058 - Local Practice

Until clear processes for Local Practices are implemented, Local Practice is owned by APOS Unit Leader and reviewed by the APOS Document Coordinator. Following implementation, it should be owned by the process owner with an appointed case handler in the installation's operational organization on land.

The contents of Local Practice shall govern and describe the execution. If there is a need for a comprehensive, guiding job description (list), this should be added to the local practice as a linked file attachment.

Predefined Process

B-10009 - Adding a Predefined Process shape to a Flowchart

Content

0.00   Definitions
1.00   General Description
2.00   Question
3.00   Answer
4.00   Sample Session


0.00 Definitions

N/A

1.00 General Description

Creating a Predefined Process Activity from within a Flowchart. The Predefined Process Activity represents a sub set of Flowcharts/Requirements/Best Practice that must be performed on this step.

2.00   Question
How is a predefined process Activity added to a Flowchart?

3.00   Answer
Open a Flowchart. Set the Flowchart in edit mode.
Choose Predefined Process from the Flowchart toolbar.
Move the Predefined Process to the desired location.
Search or select a Process that the Predefined Process Activity should link to.
Verify that the Predefined Process is created on the Flowchart.

4.00   Sample Session
  1. Open a Flowchart
  2. Set the Flowchart in edit mode


    Figure 1 - Open a Flowchart and set it in edit mode.

     
  3. Choose Predefined Process from the Flowchart toolbar

  4. Move the Predefined Process to the desired location


    Figure 3 -  Choose Predefined Process from the toolbar and move it to the desired location.

  5. Search or select a Process that the Predefined Process Activity should link to in the Predefined Process link window.


    Figure 4 - Predefined Process link window.

  6. Verify that the Predefined Process is created on the Flowchart.


    Figure 5 -  Verify that the Predefined Process is created on the Flowchart.

Procedure

B-13084 - Work Processes rather than Procedures

Procedures often contain a mixture of text and Governing Elements like Responsibility, Best Practice, Requirements, Competence/Checklists and References.

Procedures rarely identify Roles, but describe responsibilities associated to a Job Function. This means that the Procedure must be revised when the organization is in need of change.

In many businesses one will find that different procedures overlap each other.

Many businesses have used procedures to capture experience.
 
Investigations of accidents and incidents will often result in changes and additions.

Overall, this will contribute to greater complexity and increased risks of ambiguities and misunderstandings

Requirement

B-10057 - Requirement - Definition

Et krav linkes til det element eller dokument hvor det hjemles fra. For eksempel til Paragraf, Standard, Vission, Mission, Strategier, Value Statements og Produkt.

Planlagt avvik fra krav krever saksbehandling i avvikshånteringssystemet med godkjennelse av kraveier.
Dersom utførelsen av en aktivitet viser seg å ikke ivaretar kravet, kreves formell avviksbehandling i Synergi.  Avviket må behandles av fagenhet og godkjennes av kraveier.

Spesifikke krav til arbeidsmiljø
Spesifiserte krav som definerer en nødvendig standard til arbeidsmiljø for å nå overordnet HMS-målsetning.

Spesifikke krav til beredskap (Ytelseskrav til beredskapen)

Krav til effektiviteten av de beredskapstiltakene som benyttes for å møte de definerte fare- og ulykkessituasjonene.  De skal utrykkes slik at den etablerte beredskapen kan kontrolleres opp mot kravene.

Spesifikke krav til security
Målbare krav til effektiviteten til de securitytiltak som benyttes.

Role

B-10060 - Role in a Work Process - Definition

NO: En Rolle i en arbeidsprosess representerer personer eller stillinger som er ansvarlig for å utføre aktivitetene i sitt rollebånd, i arbeidsprosessen.

Rollenavnene som benyttes, bør være beskrivende for funksjonen rollene har / aktivitetene rollene utfører, i arbeidsprosessen. Rollenavnene må ikke forveksles med jobb / stilling (en må ikke bruke rene stillingsbetegnelser som rolle og heller ikke organisasjonsenheter).

For å unngå for mange ulike og forvirrende rollenavn, bør en sjekke hvilke rollenavn som er i bruk i lignende eller tilstøtende arbeidsprosesser. Der hvor det er hensiktsmessig, skal en bruke følgende standardiserte rollenavn:

Behovsmelder
Tilrettelegger (- drift), (- fag), (- planlegging)
Saksbehandler (- drift), (- fag), (- planlegging)
Utførende (- drift), (- fag), (- transport)
Verifiserende (- drift), (- fag)
Godkjenner
Dersom det er flere som utfører samme standardiserte rolle, kan man skille mellom disse, ved å føye til en beskrivelse etter hver f.eks (- drift).

B-11970 - Rolle versus stilling

Rollenavnene som benyttes, bør være beskrivende for funksjonen rollene har / aktivitetene rollene utfører, i arbeidsprosessen. Rollenavnene må ikke forveksles med jobb / stilling (en må ikke bruke rene stillingsbetegnelser som rolle og heller ikke organisasjonsenheter).

For å unngå for mange ulike og forvirrende rollenavn, bør en sjekke hvilke rollenavn som er i bruk i lignende eller tilstøtende arbeidsprosesser. Der hvor det er hensiktsmessig, skal en bruke følgende standardiserte rollenavn:

Behovsmelder
Tilrettelegger (- drift), (- fag), (- planlegging)
Saksbehandler (- drift), (- fag), (- planlegging)
Utførende (- drift), (- fag), (- transport)
Verifiserende (- drift), (- fag)
Godkjenner
Dersom det er flere som utfører samme standardiserte rolle, kan man skille mellom disse, ved å føye til en beskrivelse etter hver f.eks (- drift).



 

B-12178 - Role Wizard

Overview
This Best Practice describes the Role Wizard in SoluDyne. Role Wizard is used for creating links between Roles and Job Functions.

Prerequisites
The config class for the Role Wizard is activated in the System Access Control under System in SoluDyne Expending Menu.

Description

  

  1. Click on Process in SoluDyne Expanding Menu. 
  2. Click on Role Wizard. 
  3. Open the Wizard by clicking on Run Wizard.

  

  1. Click on Info to open and close help.

 

  1. Retrieve Roles from Job Function. Search for a Job Function Node. Click Next.
    Note! This step is only necessary if you want to add roles from an existing job function.

 

  1. Select Roles or add more roles using: Select Additional Roles. Click Next.

 

  1. Select an Organization.
  2. Select Job Functions (s).
  3. Click Next.

 

  1. Preview selected Job Functions.
  2. Preview selected Roles.
  3. Choose action Add or Replace.
  4. Click Next.

 

  1. Preview changes to be implemented.
  2. Click Next.

 

  1. Verify Results.
  2. Click Finish.

 

  1. Open the target Job Function and check that selected Roles are linked. 

B-13290 - Role Type Creation

Overview
This Best Practice describes how to create a new Role Type in SoluDyne.

Prerequisites
Role Type Register, Role Type Group and Role Type Classes must be active and User must have permissions to Add and Write.

Description

 

  1. Click on New button on Toolbar. 
  2. Click on New Register item.
  3. Click on Role Type Register to create a new one.

 

  1. Change the Title for Role Type Register. 
  2. Click on Save button.
  3. Click on New button on Toolbar.
  4. Click on New Child Node item.
  5. Click on Role Type Group item.

 

  1. Fill in Id and Title for Role Type Group.
  2. Click on Save button. 
  3. Click on New button on Toolbar.
  4. Click on New Child Node item.
  5. Click on Role Type item.

 

  1. Fill in Id and Title for Role Type. Note that only Title Field is visible on Role Node customization.
  2. Click on Publish button. 

 

  1. Now new Role Type is available to be selected as a Type on Role. 

  

  1. All Roles with specific Role Type are listed in List of roles Field of Role Type Node. 

03 - Modeling Manuals & Governing Elements

06.04 - Establish Governing Elements

B-12270 - Best Practice

Best Practice must be supported by a Requirement.

K-18931 - Quality Control

B-12269 - APOS Modelling Quality Control (QC)

Use and document in APOS Modelling Quality Control Checklist.

B-12298 - ISO Pyramid

ISO Pyramiden er vanligvis strukturert i pyramideform med tre eller fire nivåer av dokumentasjon. Modellen er et verktøy for å administrere og synliggjøre overordnede krav og retningslinjer i kvalitetssystemet.

Elementer som ligger direkte under en seksjon blir automatisk synlig i Styringspyramiden ved å holde musepekeren over ønsket Vertikal / Horisontal tekst i pyramiden. Elementer lenkes opp på vanlig måte ved hjelp av Legg til lenker / Add Links eller Dra-og-Slipp / Drag and Dropp verktøyet. 

Eksempel med Fil:
1) Naviger til ønsket Fil som skal plasseres under Styringspyramide
2) Åpne Dra-og-Slipp/Drag and Drop verktøyet og plasser i ønsket seksjon på Styringspyramiden
3) Elementet vil nå være synlig ved å holde musepeker over

Eksempel med Krav:
1) Naviger til ønsket Seksjon som skal ha et kravelement og klikk Edit/rediger knappen.
2) Scroll ned i Seksjonen og klikk Add links. Naviger til og klikk på ønsket kravelement(er). Klikk "X" for å lukke vinduet.
3) Publish. Kravelement(er) vil nå være synlig i seksjon ved å holde musepeker over valgt Seksjon.

Hvis elementet skal ligge under to eller flere Seksjoner, må bruker gå inn på underseksjonen og velge Add Links til noden og deretter Linke den opp i Seksjon feltet for at den skal bli synlig i pyramiden ved å holde musepeker over.

Eksempel med Fil:
1) Naviger til ønsket Fil som skal plasseres under Styringspyramide
2) Åpne Dra-og-Slipp/Drag and Drop verktøyet og plasser i ønsket seksjon på Styringspyramiden
3) Sett Seksjonen Filen skal ligge under i redigerings/Edit modus, og velg Add Links/Legg til lenke
4) Link opp til ønsket Fil
5) Velg side 2 på Seksjonsskjema og venstreklikk i Seksjonsfeltet.
6) Velg Link i SoluDyne Verktøylinje 
7) Klikk på Ankeret på ønsket Fil. Publiser.
7) Gå tilbake til Styringspyramiden og elementet vil nå være synlig ved å holde musepeker over seksjonen.

B-12480 - Best Practice for Modeling a Manual

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to model a Manual in SoluDyne.

01 Description

A Manual is used for storing Sections with Governing elements in SoluDyne. Create a new Manual by clicking on the New button, and then on New Register > Manual.

02 Example

 

  1. Click on New button.

 

  1. Click on New Register.

 

  1. Click on Manual.

 

  1. Click on OK to Continue.

 

  1. Navigate to page 2 by clicking on next button.

  

  1. Type in a new title in the Title field.
  2. Type in Owner. Type in part of the name or job function and press enter, or use the search button (4) to find a relevant match.
  3. Type in Responsible. Type in part of the name or job function and press enter, or use the search button (4) to find a relevant match.
  4. Search button.
  5. Alternatively, click on the View Tree button to find the correct job function/employee in the Organization/Employee Tree.

 

  1. Click on Publish button to Publish Manual.

B-12481 - Best Practice for Modeling a Section

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes how to model a Section in SoluDyne.

01 Description

Sections can be added under a Manual, or under other sections as sub-sections.

02 Example

Navigate to a manual by clicking on Handbooks & Manuals. Note! If you have created a new manual within the last minute: Click on the Home button to refresh the Expanding Menu if the new Manual does not show.


  

  1. Right click on the node where the new Section shall be added.

 

  1. Click on New Node.
  2. Click on Section.

 

  1. A Section has been created.
  2. Fill in an Id. Id is alphanumeric.
  3. Fill in a Title.
  4. Owner and Responsible is inherited from the parent node.

  

  1. Click Publish to Publish document.

B-12482 - Best Practice for Adding Definitions & Abbreviations

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes how to enter a definition or abbreviation into the SoluDyne system.

01 Description

Main Processes, Sub Process, Workflow with Roles, Activities, Requirements, Best Practices, and Local Practices can be linked to a dictionary entry on their respective forms.


02 Example

Navigate to Handbooks & Manuals where the new definition shall be added.

  1. Choose a Definitions & Abbreviations register to create a new definition. Click on a Definitions & Abbreviations register to open register in Expanding Menu sub-menu.
     


 

  1. Right click on Definitions & Abbreviations.
  2. Click on New Node.
  3. Click on Dictionary Entry to create new Dictionary Entry. 

  

  1. Fill in the new Word\Expression.
  2. Select Type.
  3. Fill in a Description of the definition.

  

  1. Click Publish to Publish document.

B-12484 - Best Practice for Modeling a Requirement

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes how to model a Requirement in SoluDyne.

01 Description

A Requirement can be created under a Section in SoluDyne.


02 Example

  1. Open up Expanding Menu.
  2. Click on Handbooks & Manuals.
  3. Click on the Manual where the Requirement is to be created.
  4. Right click on a section where the Requirement is to be created. If no sections exist, start with creating a new section under Manual.

   

  1. Right click on a section.
  2. Click on New Node.
  3. Click on Requirement.

  

  1. Id is filled in automatically.
  2. Fill in a Title.
  3. Owner and Responsible are inherited from the parent node.
  4. Fill in a description in the Requirement field.
  5. Click on Publish button to Publish Requirement.

  

  1. Example of a Published Requirement.

B-12486 - Best Practice for Adding Links to Definitions

00 Overview
01 Description

02 Example
03 Note


00 Overview

This Best Practice describes how to add links to Definitions on a Requirement or Best Practice in SoluDyne.

01 Description

Links to definitions can be added to Requirements and Best Practices under Handbooks & Manuals. 

02 Example

 

  1. Click on Add links to Definitions to do so.

    

Select Links window opens.

  1. Click on plus icon next to a Definitions & Abbreviations Register to find a Definition.

  

  1. Click on desired Definition.

 

  1. Definition is now linked, as it appears under the heading Name.
  2. If incorrect Definition has been linked up, use delete button to delete link.
  3. Click on close button to close window.

 

  1. Definition has now been linked up, and is showing at top of Requirement.

Publish document when finished using Publish button on toolbar.

 

  1. Example of published Requirement with Definition linked at top.

03 Note:
When copying a node, only links to Definitions will be copied. Links from Definitions to a node will not be copied.

B-12487 - Best Practice for Linking to Standard / Paragraph

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to link standards/paragraphs in SoluDyne.

01 Description

Standards/paragraphs can be linked to Requirements, Best Practices and activities in a flowchart.

02 Example

 

  1. Expand the menu.
  2. Find and select a previously established Requirement.

 

  1. Ensure that the Requirement is in edit mode.
  2. Click the add links icon to attach links to the selected node.

  

  1. Navigate to Rules and Regulations.
  2. Click on a relevant book.

 

  1. Click on a paragraph.
  2. The selected element is now visible in the links list below. 
  3. Close the pop-up window when you are finished.  

  

  1. A paragraph is now linked to the Requirement.
  2. The Requirement is now modeled and can be published. Click on publish.

B-12488 - Best Practice for Modeling a Best Practice

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to model a Best Practice in SoluDyne.

01 Description

A Best Practice can be created under a Section in SoluDyne.

02 Example

  

  1. Navigate to the section where the Best Practice should be located.
  2. Right click on the desired section.
  3. Select New Node.
  4. Select Best Practice.

 
    

  1. The ID is generated automatically.
  2. Fill out the title field.
  3. Choose the type of Beste Practice.
  4. Write the reguired text in the SoluDyne Editor field.
  5. The owner and responsible cascade from the previous level.
  6. Remember to save.


 

  1. Choose the location(s) which apply to the Best Practice by selecting the box infront of the location title.  
  2. Click on publish button.  


 

Example of a published Best Practice.

B-12489 - Best Practice for Adding Images to HTML Fields

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to attach an image to a Governing Element in SoluDyne.

01 Description

Images can be attached to Requirements, Best Practices and activity descriptions.

02 Example

 

  1. Navigate to and select a previously established Best Practice.
  2. Ensure that the Best Practice is in edit mode.

  

  1. Place the cursor where you want the image to appear, and click.
  2. Click on insert file button.

  

  1. Select browse button to locate the required file.

 

  1. Attach the required file and select Upload.

 

  1. Select Insert.
  2. Ensure that Insert link only is deselected in order to attach the image as opposed to a link to the image.

  

  1. The picture is now attached in the SoluDyne Editor field.

  

Example of a published Best Practice with an attached image.

B-12490 - Best Practice for Creating a Checklist

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to create a checklist in SoluDyne.

01 Description

Checklists can be created under Governing Elements and activity descriptions. 

02 Example


  

  1. Navigate to the section where the checklist should be located.
  2. Right click on the desired section.
  3. Select New Node.
  4. Select Checklist.


  

  1. The checklist is now available under the section.


   

  1. The ID is generated automatically.
  2. Fill in the title.


  

  1. Click the location in the SoluDyne Editor field where you want the checklist to appear.
  2. Select the table icon to add the table.
  3. The table will now be visible in the SoluDyne Editor field.

 
  

  1. Right click inside the table to add rows and columns.
  2. Add the required text to the table. 
  3. Publish the end result.


  

  1. Click to open the Best Practice that the checklist should be linked to. 
  2. Highlight "checklist" in the Best Practice text.
  3. Select the link icon.  


  

  1. Navigate down to the established checklist.
  2. Select it. The checklist will now be visible in the links field.
  3. Select the anchor icon in the links field to anchor the checklist to the highlighted word in the SoluDyne Editor field.  
  4. Close the window.


  

  1. Control that the link has been correctly inserted into the text. 
  2. Publish.


  

Example of a published Best Practice with a linked checklist.



04 - Modeling Processes

01 - Modelling Main Process

B-12491 - Best Practice for Modeling a Main Process

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes how to model a main process in SoluDyne.

01 Description

The main process is modeled by adding a new registry. The process owner and responsible must be added in each main process.

A new Main Process is added with a default shape type. Both shape type and location of shape can be changed by naviagating to Flowchart tab on Home Page (only available for admininstrators).

02 Example

   

  1. Click on the new icon in the SoluDyne toolbar.

  

  1. Select New Register.

  

  1.  Select 1100 Main Process.

  

  1. Click OK to continue.  

 

  1. The main process is established. Go to page two to add the owner and responsible.

 

  1.   Fill out the title.


 

  1. Add the process owner and responsible.

Click on publish button to publish document.

02 - Modeling Sub Process

B-10022 - Setting and updating Owner and Responsible on all other types than Flowcharts

Content

0.00   Definitions
1.00   General Description
2.00   Question
3.00   Answer
4.00   Sample Session


0.00   Definitions

N/A

1.00   General Description

When updating the fields Owner and/or the Responsible within a template that is not of type Flowcharts with Roles; will not affect elements that reside beneath the current element.

2.00   Question

When updating the fields Owner and/or Responsible on template that is not of type Flowchart with Roles, what are the effects?

3.00   Answer

When updating the fields Owner and/or Responsible on templates that are not of the type Flowchart with Roles, the fields Owner and Responsible for the child elements will not be affected.

4.00   Sample Session

When changing the Owner and/or Responsible fields on a Sub Process and clicking Save. This does not affect elements below the Sub Process, like Flowcharts and Sub Processes below this level in the tree.

  
Figure 1 - Changing the contents in the fields Owner and/or Responsible will not affect the Owner and Responsible fields of elements below this Sub Process.

B-12492 - Modeling a Sub Process

Beste praksis

00 Overview
01 Description

02 Example

00 Overview

 This Best Practice describes how to model a Sub Process in SoluDyne.

01 Description

A Sub Process is located under a Main Process. Several Sub Processes can be made under the same Main Process. The Owner and Responsible must be added for each Sub Process.

02 Example

Navigate to a Main Process.  Click the expand icon/plus icon to expand the menu if required.

  

  1. Right click on the Main Process that the Sub Process will be located under.


   

  1. Select New Node.


  

  1. Select 1102 Sub Process.


  

  1. The Sub Process is now established. Go to page 2 to name and number the Flowchart, and set the Owner and Responsible.


   

  1. Fill in the ID.
  2. Fill in the title of the Sub Process. 
  3. Add the Owner. 
  4. Add the Responsible. 
  5. Save when you are finished. 


   

 In some cases, a pop-up window may appear when the publish button is selected. When this occurs:

  1. Write a short comment describing what was changed/done.
  2. Select Publish Changes.


  

  1. The Sub Process is now published. Select Main Process where Sub Process was created to view the Sub Process.

03 - Modeling FlowChart with Roles

01 - Modeling requirements and best practices - Flowchart

B-12265 - Establish Flowchart

Establish Flowchart by right clicking on a subprocess, choose New Node and 1103 Flowchart with Roles.

B-12266 - Horizontal Holder

Horizontal Holder is the first shape added in the flowchart.

02 - Modeling requirements and best practices - Flowchart Roles

B-12267 - Functional Band

Functional Band is added to the flowchart, and can be found in the APOS Shapes toolbar.

03 - Modeling requirements and best practices - Flowchart Activities

B-12268 - Activities

Activities are added in to the Role Bands.

B-12493 - Modeling Flowchart with Roles

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to model a flowchart with roles in SoluDyne.

01 Description

A flowchart is typically located under a Sub Process. Several Flowcharts can be made under the same Sub Process. The Owner and Responsible must be added for each Flowchart.

02 Example

Navigate to a previously established Sub Process. Click the expand icon, or plus icon to expand the menu.

 

  1. Right click on the Sub Process that the Flowchart will be built under.

 

  1. Select New Node.
  2. Select 1103 Flowchart with Roles.

 

  1. The flowchart is now established. Go to page 2 to name and number the Flowchart, and set the Owner and Responsible.

 

  1. Fill in the ID.
  2. Fill in the title of the Flowchart. 
  3. Add the Owner. 
  4. Add the Responsible. 
  5. Save when you are finished. 

 

  1. Go to page 1 to start modeling the Flowchart.

  

  1.  Close the menu to expand the modeling space.

 

  1.  Select the grid tool. This ensures it will be easier to align the activities on the Flowchart.

 

  1. Select the Horizontal Holder figure to make the frame. The Horizontal Holder displays the ID, Title, Owner and Responsible. Click once, and move the figure to the desired location.

    TIP! Set Top and Left to 1 under Properties

  

  1. Select the Functional Band figure to add a role band. Click once, and move the figure to the desired location. It is possible to add as many Role Bands as required. To add more, click the Functional Band figure again.

    TIP! Set Top to 60 under Properties for first Functional Band

  

  1.  It is possible to change the height and width of the role bands. To do this, select the role and holding the mouse button down, drag the  sides of the band to the desired height/width using the small yellow squares.

 

  1. Remember to save changes/updates to the flowchart while you model.  

 

  1. After selecting a role band, click the drop menu in the Role Type field to select the role type.

 

  1. Select a predefined role type. This needs to be done for each role band.

 

  1. The role title can be added in the text field. This needs to be done for each role band. 
  2. Click update button after the role has been added to the text field.

 

  1. When all the required text has been added to the role bands, select the Terminator figure. A flowchart should always start and end with one or more terminators.

 

  1. Click once in the frame to move the terminator to the required location.

 

  1. Add text for the terminator by writing in the text field.
  2. Select Update.

  

  1. Select the Activity icon to add an activity.  

 

  1.  Click once in the frame to move the activity to the required location.

 

  1. Add text for the activity by writing in the text field.
  2. Select Update.  

  

  1. Select the Decision icon to add a decision box.
  2. Click once in the frame to move the decision box to the required location.
  3. Add text for the decision box by writing in the text field.

 

  1. Add the rest of the activities and place them in the correct role bands. Add activity titles to all the boxes.  

 

  1. If some activities require an interaction between two or more roles, select the Group icon.
  2. Click once in the frame to move the group shape to the required location. The height and width can be adjusted by dragging the yellow squares.

 

  1. Add text for the group by writing in the text field.
  2. Select Update.  

 

  1. Select the line tool to draw direction arrows between the shapes.

 

  1. Select the shape you want to draw the arrow from. Hold the mouse button and drag towards the white field, which will appear on the shape you want the arrow to go to. Repeat between all the shapes in the flowchart to define the workflow.

 

  1. It is possible to add text to the arrows. This is required for arrows that navigate from a decision Box. Select the arrows, and add the required text in the text field.
  2. Select Update

 

  1. Select the publish button to publish the flowchart when you are finished.  

 

 In some cases, a pop-up window may appear when the publish button is selected. When this occurs:

  1. Write a short comment describing what was changed/done.
  2. Select Publish Changes.

 

Example of a modeled, published flowchart.

B-12494 - Numbering of Flowchart and Activities

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to number a Flowchart and its Activities in SoluDyne.

01 Description

All activities in a flowchart must be numbered. This ensures that the activities appear in chronological order in the tree and the Print Tree.

02 Example

 

  1. Navigate to published flowchart.

 

  1. Select the first box/terminator in the flowchart.

 

  1. Fill out the number in the number/No. field.
  2. Select Publish.

 

 In some cases, a pop-up window may appear when the publish button is selected. When this occurs:

  1. Write a short comment describing what was changed/done.
  2. Select Publish Changes.

 

  1.  Navigate back to the flowchart by selecting the flowchart view in the path, here 02 - Plan and Prepare Work Permit.

 

  1. Repeat the same numbering process in the succeeding shapes so that all the boxes are numbered in chronological order.

 

  1.  Select the expansion symbol, or plus symbol to expand the flowchart in the tree.

 

  1. Activities now appear in chronological order.

04 - Linking Elements to Processes

B-12495 - Best Practice for Linking Job Functions to Roles

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how a job function is linked to a role in SoluDyne.

01 Description

Job functions can be linked to established roles in a flowchart. The job functions are located under Organization in the menu.

02 Example

 

  1. Select a role band by clicking on the text in the role. In this case, Responsible - Work Permit.

 

  1. Select the link icon.

 

  1. Select Organization.

 

  1. Expand the tree and navigate to a job function. Click once to select the job function.
  2. The job function is now visible in the links field.
  3. Close the window when you are finished.

 

  1.  Select Publish.

 

The job function is now visible under References - Links.  

B-12498 - Best Practice for Linking Governing Elements

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to link Governing Elements in SoluDyne.

01 Description

Governing Elements can be linked to a process, a sub-process, a flowchart and an activity in a flowchart.

When linking Governing Elements to activities, it is a prerequisite that the Governing Element has already been established under the Governing Elements section in Handbooks & Manuals.

Please Note: if the link under <Requirement> is chosen, only Requirements will be shown in the pop-up box. In the same way, if the link under <Best Practice> is chosen, only Best Practices will appear, etc. The same applies for Local Amendments.

02 Example

 

 Navigate to a published flowchart.

 

  1. Select the activity where the Governing Element will be placed. In this example, Evaluate Need for SJA

 

  1. Put the activity into edit mode by selecting edit-button.  

 

  1. Select Add links under the requirements section.

 

  1. Expand the tree to locate the requirement.
  2. Select the desired requirement.

 

  1. The linked element is now visible in the links list.
  2. If required, the link can be removed by selecting the delete icon. 
  3. Close the window when you are finished.

 

  1. The requirement is now linked up to the activity, and is visible under the requirements section.    

 

  1. Select Add links under the Best Practice section.

 

  1. Navigate to the required Best Practice.
  2. Select the Best Practice to link it to the activity.
  3. The linked element is now visible in the links field.

 

  1. The Best Practice is now linked to the activity and is visible under the Best Practice section.
  2. Publish the results to link the governing elements to the activity in the flowchart.

 

  1. Navigate back to the flowchart using either the tree/expanding menu;
  2.  or the path.  

 

  1. Open the flowchart and control that the Governing Elements are linked to the correct activity.  

Shapes

B-12106 - Changing Shape Type

00 Introduction

SoluDyne supports many different shape types that can be used in the SoluDyne Flowchart Editor. Different types of shapes are meant to be used with specific types of classes, but any Shape Type can be used with any type of node.

01 Changing Shape Type

  1. Click on the shape to change. See figure 1 below.
  2. Select the shape type in the Type field of the Properties box. See figure 2 below.

 
Figure 1 - Selected shape is marked with markers along the outside.

 
Figure 2 - The list of available shape types. Note that the top entry is the currently selected shape type.

NOTE: The types list is separated into two, the list of shapes associated with the selected element and all other shapes. The shape types associated with the current selected element are placed first in the list and show up as normal black text. The other shape types are found last in the list and are displayed using gray text. See figure 3.

The list of shapes not associated with the selected element are displayed using gray text.

02 Finding the Shape Type of an Existing Element

  1. Click on the element
  2. The currently selected item is displayed in the Type field.

NOTE: If the name of the shape type is wider than the available space, the full name can be revealed by clicking on drop-down arrow in the Type field to display the list. The currently selected shape type will be at the top of the list. See figure 2 above.

05 - Rules and Regulations

B-12349 - Compliance Reports

Overview

This Best Practice describes the compliance reports available in SoluDyne.

Prerequisites
N/A 

Description

The following compliance reports are available in SoluDyne under Rules and Regulations in SoluDyne Expanding Menu:

  • 'DQ101 - Compliance with Statutory Requirements; Rules and Regulations' shows requirements that are linked to rules and regulations. Full description is available in B-12756 - DQ101 - Compliance with External Requirements Drilldown

B-12717 - Linked Requirement and Paragraph

 
Beste praksis
00 Overview
01 Description

02 Example

00 Overview

This best practice describes how to Navigate to and from a Paragraph via a Requirement.

01 Description

Navigate to and from a Paragraph via a Requirement.
 

02 Example


 

  1. Click on the link and navigate to the Paragraph.


 

  1. The paragraph shows Standards and Regulations as they are shown on internet, or as in this example, with text.
  2. Scroll down to see the bottom of the form.


 

  1. This section shows the links to the Requirement where the Paragraph is referred. 
  2. Click on the link and navigate back to the Requirement.


     

The Requirement view is visible again.

B-12756 - DQ101 - Compliance with External Requirements Drilldown

Overview

The DQ101 - Compliance with External Requirements drilldown report is used for checking compliance of internal Governing Elements and Processes with Paragraphs of external Standards, Rules and Regulations in SoluDyne.

Prerequisites
N/A

Description

   

  1. Open the left Expanding Menu.
  2. Select Rules and Regulations in the Expanding Menu.
  3. Click on DQ101 - Compliance with External Requirements. The drilldown tree will be opened.
  4. Use Filter for selecting the needed data. Filter has the following fields:

    - Register: the register where a Paragraph is located.
    - Group: the Standard Group or Rules and Regulations Group where a Paragraph is located.
    - Law/Regulation/Standard: the Standard or Rule that is parent for a Paragraph.
    - Paragraph: a Paragraph that is referenced or not by an internal Governing Element.
    - Governing Element: an internal Governing Element (Requirement, Best Practice, etc.) that reference a Paragraph.
    - Activity: a Process Activity that is linked or associated with the Governing Element.
    - Process: a Flowchart With Roles or Sub Process that refers to a Paragraph directly or via child Activities.
    - In use: a flag (Yes/No) indicating if a Paragraph is referenced by internal Governing Elements or not.

 

  1. All the nodes shown in the drill-down can be opened from the drill down grid by clicking on their titles in grid cells.
  2. Report results can be exported to Excel.
  3. In case of any changes in links between Governing Elements and Processes and Paragraphs Log out and Login again to see updated data in DQ101 - Compliance with External Requirements drilldown.  

06 - Comment/Change

B-12195 - Comment/Change - Responsible

Overview

The change process ensures that changes to important documents are evaluated and verified by qualified personnel in a formal process. 

A change process is initiated when someone in the organization creates a new Comment/Change.

Prerequisites

  • To ensure a correct and efficient handling of a Comment/Change, the Originator should create the new Comment/Change directly on the node/process/document where the change is requested.
  • The Originator should provide a detailed description of the requested change, preferably with a suggestion to improved text. Provide a link to a document if relevant.
  • All involved parties should use the comment field to comment and confirm that the change request has been reviewed before the Comment/Change is signed to the next step.

Description

How a new Comment/Change is created is described here: B-12439 - Comment/Change – Originator. When the new Comment/Change has been filled in and signed by the Originator, the change request is automatically sent to the responsible person's workqueue for further handling.

   

To open a received Comment/Change, do the following:

  1. Open the SoluDyne menu.
  2. Click on General.
  3. Click on Workqueue.
  4. Click on 0197 Comment/Change to open a list of received change requests.
  5. Click on the requested Comment/Change.

    

The form A-3 Evaluate Comment / Change Request - Responsible opens:

  1. Read the comment from the Originator below the heading Comments / Description of Requested Change.
  2. Add a suitable title to the change request.
  3. If another personnel is requested to handle the change request further, an Alternate Responsible can be filled in here, before the change request is signed to this person. 
  4. On this step, it is also possible to reject the change request, see description here: B-13287 - Reject a Comment/change, or to put the change request on hold. If the change request is put on hold, the Comment/Change will remain in the workqueue to the Responsible / Alternate Responsible.
  5. If the change request shall be further handled, click on the link View Tree to perform the change in a change package. A new window opens.

   

  1. Click on the +/- icon to navigate down to the node where the change request is created. In this case K-10714.
  2. Click on K-10714 to open the requirement.
  3. Update the node according to the change request.
  4. Click on the Save button and close the window.

Note that the change performed is located in a change package. The node is locked for other editing, and the change is not visible to others than the people involved in the change process.

   

  1. Describe the change performed to the node in the Comment Responsible field.
  2. Evaluate if the change needs approval from the owner of the node or not, and tick off accordingly.

Sign the Comment/Change form to the next step, A-5 Review. The Originator will at the same time receive a receipt where status of the change request is indicated.

    

In this step, the responsible person shall evaluate if the change request should be sent on review or not.

  1. The form will automatically be ticked off with the status No Review / Review Completed. If a review is not required, sign the Comment/Change to the next step.
  2. If a review is required, click on Add Review Recipient.

Follow B-13345 - Comment/Change - Review for further explanation of the review process.

If no review is required, or the review process is performed, the review request will be sent to either:

  • Owner of the node for approval, see B-13346 - Comment/Change - Approver.
  • Responsible person for implementation of the change, see below.   

  

The person responsible for the node receives a link to the Comment/Change in the workqueue when the change is ready to be implemented.

  1. Read the comments from the previous steps. If required, write a description of the change.
  2. Click on the Publish button in order to implement the change package into the system, and make the updated node visible to the rest of the organization.
  3. Note that the Signature field is locked when the Publish button is not activated. 

 

  1. When the Responsible person has published the change, the Comment/Change form can be signed. Push Enter on the keyboard.

The Originator will receive a receipt in the workqueue to confirm that the handling of the change request has been completed.

B-12196 - D120 Active Comments/Change Reqeusts

00 Overview
01 Description

02 Sample Session

00 Overview

This Best Practice describes the D120 Active Comments/Change functionality in SoluDyne.

01 Description

Use drill down D120 Active Comments/Changes to view active and not processed 0197 Comments/Changes requests. Drill down is available under Process in SoluDyne Expanding Menu.

Filter options; Step, Performer, Reporting date, Reported On, Reported By, Comments/Changes.

02 Sample Session

N/A

B-12327 - D123 All Comments / Change Requests

00 Overview
01 Description

02 Sample Session

00 Overview

This Best Practice describes the D123 All Comments/Change Requests functionality in SoluDyne.

01 Description

Use drill down D123 All Comments/Changes to view all Comments/Change requests. Drill down is available under Process in SoluDyne Expanding Menu.

Filter options; Step, Performer, Reporting date, Reported On, Reported By, Comments/Changes.

02 Sample Session

N/A

B-12439 - Comment/Change – Originator

Overview

This Best Practice describes how a new Comment/Change is created in SoluDyne. A Comment/Change can be created by anyone in the organization.

Prerequisites

  • The Originator should create the Comment/Change directly on the node/process/document where the change is requested. This to ensure that the Comment/Change is handled in a proper and efficient way.
  • The Originator should provide a detailed description of the required change, preferably with a suggestion to improved text. If necessary, provide a link to a document.

Description


 

Navigate to the node where the change proposal is requested. In this case, K-10714 - Performance of a SJA.

  1. Hoover over the activity Perform to reveal the pop-up.
  2. Click on the link K-10714 - Performance of a SJA to open the requirement.

 

  1. Click on the Comment/Change icon on the toolbar.
  2. Click on OK. 

 

  1. An unique ID is automatically granted to the new Comment/Change.
  2. A change request is added as a new child node to the element it is reported on.
  3. The Due Date is automatically set three months ahead in time. Change the Due Date if requested.
  4. Write a detailed description of the requested change.
  5. Add a link, if required.
  6. Add a file, if required.
  7. Sign the Comment/Change and press Enter to send the change request to the next step.
    1. If the Comment/Change is saved but not signed, it will remain in the Originator's workqueue. In this way the Originator can continue to work with the Comment/Change form and sign it at a later occasion. 

Further handling of a Comment/Change is described here: B-12195 - Comment/Change - Responsible

When the Comment/Change has been handled by the Responsible on step A-3 Evaluate Comment / Request Change - Responsible, the Originator will receive a receipt showing further handling of the change request.

   

  1. The Status field indicates the further handling of the Comment/Change. The Status is dependent on what the Responsible ticks off at the step A-3 Evaluate Comment / Request Change - Responsible.
  2. Click on Revision list to open the colored table marked in red, if this is not visible.
  3. If requested, click on Working Copy to see the updated node. It will not be possible to perform any changes to this node.
  4. If requested, click on the node icon where the change request has been created. This to see the original node before any changes were made to it.
  5. Sign the form to sign the receipt out of the workqueue.

If the Comment/Change is to be further handled, the process is described here: B-12195 - Comment/Change - Responsible.

When the handling of the Comment/Change has been completed, the Originator will receive a new receipt in the workqueue. This receipt shows the final outcome of the change request.

 

  1. Read the comments written on each step to see the changes that have been performed.
  2. Click on Revision list to open the colored table marked in red, if this is not visible.
  3. If requested, click on Working Copy to see the updated node. It will not be possible to perform any changes to this node.
  4. If requested, click on the node icon where the change request has been created. This to see the original node before any changes were made to it.
  5. Sign the form to sign the receipt out of the workqueue.

The node is now updated in the system and the new version is visible to the whole organization.

08 - Print

B-11697 - Print of Flowchart

To ensure that printouts of flowcharts look their best it is recommended that the standard size of Horizontal Holder is not changed. Changes to the width or height can cause printouts to span multiple pages.

B-12187 - My Processes and Requirements (R111)

The My Processes and Requirements report shows Requirements, Best Practices, Local Practices and Information nodes (Governing Elements or elements) connected to activities (link or parent), with roles connected to the current user.

The resulting report tree has the following structure:

Main Process
 Sub Process Level 1
  ...
  Sub Process Level n
    FlowChart
      Activity
       Governing Elements
        Governing Elements

  
Figure 1 - Marked in red - The link for My Process & Requirements can be found under Shortcuts on the gadget panel.


  
Figure 2 - The report shows:

1.) The path and the Flowchart where the User has Roles.

2.) All the activities that are located in Role Bands linked to the User's Job Function.

3.) The Governing Elements linked to the activities.

B-12398 - Print of Flowchart in Landscape

00 Oversikt
01 Beskrivelse

02 Eksempel
02.01 Naviger til prosess
02.02 Print knapp på SoluDyne verktøylinje
02.03 Justere printformat
02.04 Print ut


00 Oversikt

Denne Beste Praksis beskriver hvordan printe prosesser og flytskjema fra SoluDyne.

01 Beskrivelse

Prosesser og flytskjemaer kan skrives ut fra SoluDyne i forskjellige formater. Under er en fremgangsmåte med eksempler:  

  1. Naviger til ønsket prosess. Se eksempel 02.01.
  2. Klikk på print på SoluDyne verktøylinje. Se eksempel 02.01.
  3. Klikk Print This Form. Se eksempel 02.01.
  4. Utfør endringer i Page Setup om nødvendig. For eksempel å endre fra stående til liggende side. Se eksempel 02.02.
  5. Klikk Print. Se eksempel 02.04.
  6. Velg skriver. Se eksempel 02.04.
  7. Klikk Print. Se eksempel 02.04.

Liggende eller landskap format kan settes som standard om ønskelig. Se B-11767 for mer informasjon.

02 Eksempel

02.01 Naviger til prosess


 
Figur 1 - Naviger til prosess.

02.02 Print knapp på SoluDyne verktøylinje

 

    

Figur 2 - Klikk på Print på SoluDyne verktøylinje.

 

   

Figur 3 - Klikk Print This Form.

02.03 Justere printformat


 

Figur 4 -  Klikk Page Setup.

 

 

Figur 5 - Utføre endringer i lay-out om nødvendig.

02.04 Print ut

  

Figur 6 - Klikk på Print.

 

Figur 7 - Velg printer og klikk på Print.

B-12431 - Print Tree on Work Process

00 Overview
01 Description
02 Example

00 Overview

This Best Practice describes the Print Tree on Work Process functionality in SoluDyne.

01 Description

When clicking on Print Tree on a Flowchart, a report is generated that shows the Flowchart, the path and all the Governing Elements related to the Flowchart.

02 Example

    

  1. Click on the Print button.
  2. Click on Print Tree in the menu.

 

   

The Report shows the Flowchart, the path and all the Governing Elements related to the Flowchart.

  1. Click on the Print button to print the Report.

 

B-12499 - Print Tree

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to generate a Print Tree in SoluDyne.

01 Description

The Print Tree is a process report which shows all linked elements, roles and responsibilities, requirements and best practices.

02 Example

 

Navigate to a published flowchart.

 

  1. Select the print icon in the toolbar. Select Print Tree.

 

  1. Select Print... in the pop-up window to print out the report.  

B-12748 - Print Tree Report on Main Process

Best practice

00 Overview
01 Description
02 Content
03 Example

00 Overview

This Best Practice describes the functionality for printing tree reports from main processes in SoluDyne.

01 Description

To print tree report from a main process, a main process has to be opened. Next, the print button is clicked on. Four choises appear:
Print this form - Prints the open form.
Print forms - Prints the open form and any form under it.
Print tree - Prints the open form, any form under it including all text and links it contains.
Print other reports - Prints files that might be uploaded to the node.
Choose Print tree. A printed tree report is generated.

02 Content

Class Field
R110a Process & Requirements Path
Main Process Path
Report: All Investigations 2: Type
Sub Process Path
D101 Requirements & Best Practice - Ordered List Alphabetic ordering
FlowChart with Roles Flow Chart
FlowChart with Roles Description
Activity Path
Activity Description
Predefined Process Path
Predefined Process Report Path
Predefined Process Process
Requirement Path
Requirement Requirements
Best Practice Path
Best Practice Best Practice
Local Amendment Path
Local Amendment Local Amendment
Information Path
Information Information
Dictionary Entry Description
Section Section
Procedure Path
Procedure Procedures
Form Path
Form Description
0231 Role Path
Checklist Path
Checklist Checklist
Key Control Path
Key Control Description

Includes links to and from Section, Requirement, Information, Procedure, Form, Key Control, 0231 Role, Best Practice, Dictionary Entry, Checklist and Local Amendment.

NB: Print Tree report does not show linked links.

03 Example

To generate a print tree report for a main process:

  1. Open the main process
  2. Click on the "print" button in the SoluDyne Toolbar - figure 1
  3. Select "print tree" - figure 1
  4. Print tree report is generated - figure 2

As an example, here is the report: Consulting Services

 
Figure 1 - Print tree button in main process where print tree is selected for print.
 
 
Figure 2 - Print tree report for main process.

B-12750 - Print Tree Report on Sub Process

Best practice

00 Overview
01 Description
02 Content
03 Example

00 Overview

This Best Practice describes the functionality for printing tree raports from sub processes in SoluDyne.

01 Description

To print tree report from a sub process, a sub process has to be opened. Next, the print button is clicked on. Four choises appear:
Print this form - Prints the open form.
Print forms - Prints the open form and any form under it.
Print tree - Prints the open form, any form under it including all text and links it contains.
Print other reports - Prints files that might be uploaded to the node.
Choose Print tree. A printed tree report is generated.

02 Content

Class Field
FlowChart with Roles  Cover Sheet Subform 
FlowChart with Roles Subform Page Break (from the 2nd node)
FlowChart with Roles TABLE OF CONTENTS
FlowChart with Roles Introduction
FlowChart with Roles Definitions and Abbreviations
FlowChart with Roles Process Description
FlowChart with Roles Roles and Responsibilities
FlowChart with Roles Subform Page Break (for the 1st node only)
FlowChart with Roles Activity Description
FlowChart with Roles Path
FlowChart with Roles Flow Chart
FlowChart with Roles Subform Page Break (for the 1st node only)
Activity Path
Activity Description
Predefined Process Path
Predefined Process Report Path
Predefined Process Process
Requirement Path
Requirement Requirements
Best Practice Path
Best Practice Best Practice
Local Amendment Path
Local Amendment Local Amendment
Information Path
Information Information
Dictionary Entry Description
Section Section
Procedure Path
Procedure Procedures
Form Path
Form Description
Checklist Path
Checklist Checklist
Key Control Path
Key Control Description
FlowChart with Roles Risk Assessment
FlowChart with Roles Referenced documents
FlowChart with Roles References to this document

NB: Print Tree report does not show linked links.

03 Example

To access print tree report on sub process:

  1. Open up sub process
  2. Click on the print button in the SoluDyne Toolbar - figure 3
  3. Choose print tree - figure 3
  4. Print tree report is generated - figure 4

As an example, here is the report: 01 - Consulting Service Strategy

 
 
Figure 1 - Print tree button in sub process where print tree is selected for print.


   
Figure 2 - Print tree report on sub process.

B-12751 - Print Tree Report on Flowchart with Roles

Best practice

00 Overview
01 Description
02 Content
03 Example

00 Overview

This Best Practice describes the functionality for printing tree raports from flowcharts in SoluDyne.

01 Description

To print tree report from a flowcharts, a flowchart has to be opened. Next, the print button is clicked on. Four choises appear:
Print this form - Prints the open form.
Print forms - Prints the open form and any form under it.
Print tree - Prints the open form, any form under it including all text and links it contains.
Print other reports - Prints files that might be uploaded to the node.
Choose Print tree. A printed tree report is generated.

02 Content

Class  Field
FlowChart with Roles  Cover Sheet Subform  
FlowChart with Roles Subform Page Break (from the 2nd node)
FlowChart with Roles TABLE OF CONTENTS
FlowChart with Roles Introduction
FlowChart with Roles Definitions and Abbreviations
FlowChart with Roles Process Description
FlowChart with Roles Roles and Responsibilities
FlowChart with Roles Subform Page Break (for the 1st node only)
FlowChart with Roles Activity Description
FlowChart with Roles Path
FlowChart with Roles Flow Chart
FlowChart with Roles Subform Page Break (for the 1st node only)
Activity Path
Activity Description
Predefined Process Path
Predefined Process Report Path
Predefined Process Process
Requirement Path
Requirement Requirements
Best Practice Path
Best Practice Best Practice
Local Amendment Path
Local Amendment Local Amendment
Information Path
Information Information
Dictionary Entry Description
Section Section
Procedure Path
Procedure Procedures
Form Path
Form Description
Checklist Path
Checklist Checklist
Key Control Path
Key Control Description
FlowChart with Roles Risk Assessment
FlowChart with Roles Referenced documents
FlowChart with Roles References to this document

Includes links from Requirement, Information, Key Control, Best Practice, Local Amendment.
Includes links to Requirement, Information, Key Control, Best Practice, Dictionary Entry, Local Amendment.

NB: Print Tree report does not show linked links.

03 Example

To generate a print tree report for a flowchart:

  1. Open the flowchart
  2. Click on the "print" button in the SoluDyne Toolbar - figure 1
  3. Select "print tree" - figure 1
  4. Print tree report is generated - figure 2

As an illustration, here is the print tree report: 01 Strategic Assessment.

  
 Figure 1 - Print tree button in flowchart with roles where print tree is selected for print.

  
 Figure 2 - Print tree report on flowchart with roles.

B-12752 - Generate Print Tree Reports for Requirements

Best practice

00 Overview
01 Description
02 Content
03 Example

00 Overview

This Best Practice describes the functionality for printing tree reports from requirements in SoluDyne.

01 Description

To print tree report from a requirement, a requirement has to be opened. Next, the print button is clicked on. Four choises appear:
Print this form - Prints the open form.
Print forms - Prints the open form and any form under it.
Print tree - Prints the open form, any form under it including all text and links it contains.
Print other reports - Prints files that might be uploaded to the node.
Choose Print tree. A printed tree report is generated.

02 Content

Class Field
R110a Process & Requirements Path
Main Process Path
Report: All Investigations 2: Type
Sub Process Path
D101 Requirements & Best Practice - Ordered List Alphabetic ordering
FlowChart with Roles Flow Chart
FlowChart with Roles Description
Activity Path
Activity Description
Predefined Process Path
Predefined Process Report Path
Predefined Process Process
Requirement Path
Requirement Requirements
Best Practice Path
Best Practice Best Practice
Local Amendment Path
Local Amendment Local Amendment
Information Path
Information Information
Dictionary Entry Description
Section Section
Procedure Path
Procedure Procedures
Form Path
Form Description
0231 Role Path
Checklist Path
Checklist Checklist
Key Control Path
Key Control Description

Includes links to and from Section, Requirement, Information, Procedure, Form, Key Control, 0231 Role, Best Practice, Dictionary Entry, Checklist and Local Amendment.

NB: Print Tree report does not show linked links.

03 Example

To generate a print tree reports for requirements:

  1. Open a requirement
  2. Click on the "print" button in the SoluDyne Toolbar - figure 1
  3. Select "print tree" - figure 1
  4. Print tree report is generated - figure 2

As an illustration, here is the print tree report: K-10639 - EFQM - European foundation for Quality Management

 
Figure 1 - Print tree button in requirement where print tree is selected for print.

 
Figure 2 - Print tree report for requirement.

B-12753 - Generate Print Tree Report on Definition

Best practice

00 Overview
01 Description
02 Content
03 Example

00 Overview

This Best Practice describes the functionality for printing tree reports from definitions in SoluDyne.

01 Description

To print tree report from a definition, a definition has to be opened. Next, the print button is clicked on. Four choises appear:
Print this form - Prints the open form.
Print forms - Prints the open form and any form under it.
Print tree - Prints the open form, any form under it including all text and links it contains.
Print other reports - Prints files that might be uploaded to the node.
Choose Print tree. A printed tree report is generated.

02 Content

Class Field
Dictionary Title
Dictionary Group Title
Dictionary Group Description
Dictionary Entry Word \ Expression
Dictionary Entry Description

NB: Print Tree report does not show linked links.

03 Example

To generate a print tree report for a definition:

  1. Open a definition
  2. Click on the "print" button in the SoluDyne Toolbar - figure 1
  3. Select "print tree" - figure 1
  4. Print tree report is generated - figure 2

As an illustration, here is the print tree report: Document. 

 
Figure 1 - Print tree button in definition where print tree is selected for print.


 
Figure 2 - Print tree report for definition.

B-12754 - Print Tree Report on My Processes & Requirements (R111)

Best practice

00 Overview
01 Description
02 Content
03 Example

00 Overview

This Best Practice describes the functionality for printing tree reports from My Processes & Requirements in SoluDyne.

01 Description

To print tree report from My Processes & Requirements, R111 My Processes & Requirements has to be opened. Next, the print button is clicked on. One option appears:
Print report - Prints the report.
Click on it and a printed tree report is generated.

02 Content

Class Field
Main Process  Path 
Report: All Investigations 2: Type
Sub Process Path
FlowChart with Roles Path
FlowChart with Roles Flow Chart
FlowChart with Roles Description
Activity Path
Activity Description
Predefined Process Path
Predefined Process Report Path
Requirement Path
Requirement Requirements
Best Practice Path
Best Practice Best Practice
Local Amendment Path
Local Amendment Local Amendment
Information Path
Information Information
Dictionary Entry Description
Key Control Path
Key Control Description

NB: Print Tree report does not show linked links.

03 Example

To generate a print tree report for "My Processes & Requirements":

  1. Open "R111 My Processes & Requirements"
  2. Click on the "print" button in the SoluDyne Toolbar - figure 1
  3. Select "print report" - figure 1
  4. Printed report is generated - figure 2

As an illustration, here is the print tree report: Q02 - Risk Management

 
Figure 1 - Print report button in "R111 My Processes & Requirements" is selected for print.

 
Figure 2 - Printed report for "My Processes & Requirements".

B-12761 - Coversheet

00 Overview
01 Description

02 Example

00 Overview

Coversheet is currently only available on Print Tree for Sub Process and Flowchart with Roles.

01 Description

The coversheet shows Id, Title and Revision information for the element that is being printed. Coversheet is currently only available on Print Tree for Sub Process and Flowchart with Roles.

02 Example

For examples of use of Coversheet see

B-12751 - Print Tree Report on Flowchart with Roles
B-12750 - Print Tree Report on Sub Process











Save