bannerd

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tabsetup
01. Design and Development
12. Implementation
23. Maintenance
34. Lists
Div
idtabs-1

1.Design and Development

1.1 Definition of Process Asset Templates

Process Asset Templates are a natural evolution of guidance in SWEs and Topics. They typically start out as checklists, process step lists, document content structures, or other content and evolve into templates that can be used in project activities or as prototypes to be modified, tailored, and improved before being used in a project.

Process Asset Templates is a general category of pages. Any page that is not a SWE, topic, or the Introduction page is eligible for inclusion here.  These pages include: 

  • Checklists - preformatted checklists to be used in some activity. Can be modified to suit a project's unique needs. 
  • Process Lists - lists of things that may be done in some specified order. Can be modified to suit a project's unique needs. 
  • Principles - a previously not numbered group of pages but are being included in this effort for consistency

A PAT will be numbered so that existing code in templates and macros for references and tools can be reused. The PAT number series will be included in the first 7 characters of the page title. 

1.2 Layout of PATs  

The PATs are being developed in two spaces on the SWEHB site: SITE, and SWEHBVD

In SITE space

  • The SITE space is the location of the PAT Database. This is where the PATs are located. From This location, they will be available to all versions of the SWEHB. The container page is named “PAT Database” and it a child of the “Home” page of SITE.
  • The template for the “pat” is stored in SITE. This is used as the Live Template for creating PAT pages.

In SWEHBVD space


Div
idtabs-2
Include Page
Initial Implementation of PATs
Initial Implementation of PATs
Div
idtabs-3

3. PAT Maintenance

3.1 Assets in a PAT

Every asset that becomes a Process Asset Template in SWEHB gets it's own page in the SITE space. From this location, the PAT can be: 

  • maintained under the version control afforded by Confluence, 
  • has certain standard formatting, as Word documents, Excel spreadsheets, PowerPoint presentations, etc.
  • made available to all versions of SWEHB by using the Include Page and Excerpt Include macros. 

3.2 PAT LifecycleLife cycle

Each Process Asset Template goes through a life cycle where it is created, implemented in a SWEHB page, updated, and finally retired or replaced. 

  1. Create a PAT according to SWEHB standards - May be a Word doc, Excel Spreadsheet, or other type of reusable format. 
    1. Must be stored in usable format, not a PDF. 
    2. Details in Configuring an Asset as a PAT
  2. Implement PAT in SWEHB pages
    1. Create the PAT page in PAT Database


Expand the items below as needed to complete items in the PAT flow. 

Expand
titleConfiguring an Asset as a PAT

Include Page
Configuring an Asset as a PAT
Configuring an Asset as a PAT

Expand
titleManaging Attachments

Include Page
Managing Attachments
Managing Attachments


3.2 Building / Updating PAT Pages 

Expand
titleAdd a New PAT

Include Page
Add a New Pat
Add a New Pat

Expand
titleUpdating a PAT

Include Page
Updating a PAT
Updating a PAT

Expand
titleAdd or Update a PAT on a SWE or Other Page

Include Page
Add or Update a PAT on a SWE or Other Page
Add or Update a PAT on a SWE or Other Page

Div
idtabs-4

4.