Difference between revisions of "Outline for Lab Equipment Manual"

From StemNode Lit Reviews
Line 1: Line 1:
 
The goal of this outline is to standardize the communication of scientific and technical information. Try to follow the spirit of the outline but delete irrelevant sections and alter as needed. If information for a section is not available at the time of page creation, but the section is still relevant, keep the section to indicate the opportunity to contribute to others. Additional guidance is provided in comments that only appear in the source code.  
 
The goal of this outline is to standardize the communication of scientific and technical information. Try to follow the spirit of the outline but delete irrelevant sections and alter as needed. If information for a section is not available at the time of page creation, but the section is still relevant, keep the section to indicate the opportunity to contribute to others. Additional guidance is provided in comments that only appear in the source code.  
  
Click "Edit Source" above, then copy and paste the text below the dotted line to start a page for a process node.
+
== Click "Edit Source" above, then copy and paste the text below the dotted line to start a page for a process node. ==
 
 
 
----------
 
----------
 
<!-- This shows the authors that have edited a page and gives them credit for their contribution -->
 
<!-- This shows the authors that have edited a page and gives them credit for their contribution -->
Line 10: Line 9:
 
'''Keywords:'''
 
'''Keywords:'''
  
 +
 +
 +
== Operation ==
 +
 +
==Maintenance and Repair==
 +
===Maintenance Schedule===
 +
<!--This section is for expected maintenance. Repairs of unexpected problems should go under the "Typical Failures and Known Solutions" section. Cost data should be omitted since it will change over time-->
 +
 +
<!--This table is generally only appropriate for specific systems (manuals on a specific make and model).  Consider omitting for generalized systems-->
 +
{| class="wikitable sortable"
 +
|-
 +
! Frequency
 +
! Action
 +
! Who Performs?
 +
! Time to Complete
 +
|-
 +
| (state the frequency)
 +
| (state the action)
 +
| (User, Professional, Manufacturer, Anyone)
 +
| (Number and unit of time)
 +
|}
 +
 +
===Troubleshooting ===
 +
<!--Historical significance of a failure is better suited for Wikipedia or other sites.  You are encouraged to link out to these sites from this section.  -->
 +
 +
<!--Problems are user oriented since a problem to one entity may not be a problem to another, Symptoms are an observable, and sometimes measurable trait, Fundamental causes connect the problem with subsystems or symptoms, and Solutions are actions that can be taken to remedy the problem -->
 +
{| class="wikitable sortable"
 +
|-
 +
! Problem
 +
! Symptom (s)
 +
! Fundamental Cause
 +
! Solution
 +
 +
|-
 +
| A goal the user cannot achieve
 +
| Usually a measurable or observable attribute
 +
| Connect to a more fundamental principle
 +
| Action that can be taken
 +
|}
 +
 +
===Repairs===
  
 
=Principles of Operation=
 
=Principles of Operation=
Line 48: Line 88:
 
===Requirements for Operation===
 
===Requirements for Operation===
 
<!-- Only briefly state anything that the StemNode Diagrams can cover as inputs. Use metric base units (Kg, L, m, A, cd, mol) where practical, with the exception of temperature which should be in Celsius instead of Kelvin. Chemical and biochemical processes should be in molar ratios.-->
 
<!-- Only briefly state anything that the StemNode Diagrams can cover as inputs. Use metric base units (Kg, L, m, A, cd, mol) where practical, with the exception of temperature which should be in Celsius instead of Kelvin. Chemical and biochemical processes should be in molar ratios.-->
 
 
 
=Diagrams=
 
=Diagrams=
 
<!--Insert images or link to CAD, PDF, image and vector files, or other visual models that host the files. This section is often only useful for specific systems (manuals on a specific make and model). Use [http://www.example.com link title], and replace "link title" with the desired text to appear -->
 
<!--Insert images or link to CAD, PDF, image and vector files, or other visual models that host the files. This section is often only useful for specific systems (manuals on a specific make and model). Use [http://www.example.com link title], and replace "link title" with the desired text to appear -->
 
 
=Maintenance and Repair=
 
==Maintenance Schedule==
 
<!--This section is for expected maintenance. Repairs of unexpected problems should go under the "Typical Failures and Known Solutions" section. Cost data should be omitted since it will change over time-->
 
 
<!--This table is generally only appropriate for specific systems (manuals on a specific make and model).  Consider omitting for generalized systems-->
 
{| class="wikitable sortable"
 
|-
 
! Frequency
 
! Action
 
! Who Performs?
 
! Time to Complete
 
|-
 
| (state the frequency)
 
| (state the action)
 
| (User, Professional, Manufacturer, Anyone)
 
| (Number and unit of time)
 
|}
 
 
==Known Failures and Solutions==
 
<!--Historical significance of a failure is better suited for Wikipedia or other sites.  You are encouraged to link out to these sites from this section.  -->
 
 
<!--Problems are user oriented since a problem to one entity may not be a problem to another, Symptoms are an observable, and sometimes measurable trait, Fundamental causes connect the problem with subsystems or symptoms, and Solutions are actions that can be taken to remedy the problem -->
 
{| class="wikitable sortable"
 
|-
 
! Problem
 
! Symptom (s)
 
! Fundamental Cause
 
! Solution
 
 
|-
 
| A goal the user cannot achieve
 
| Usually a measurable or observable attribute
 
| Connect to a more fundamental principle
 
| Action that can be taken
 
|}
 
  
 
=Commissioning=
 
=Commissioning=

Revision as of 02:08, 3 March 2019

The goal of this outline is to standardize the communication of scientific and technical information. Try to follow the spirit of the outline but delete irrelevant sections and alter as needed. If information for a section is not available at the time of page creation, but the section is still relevant, keep the section to indicate the opportunity to contribute to others. Additional guidance is provided in comments that only appear in the source code.

Click "Edit Source" above, then copy and paste the text below the dotted line to start a page for a process node.


Authors:

This system is also called: Keywords:


Operation

Maintenance and Repair

Maintenance Schedule

Frequency Action Who Performs? Time to Complete
(state the frequency) (state the action) (User, Professional, Manufacturer, Anyone) (Number and unit of time)

Troubleshooting

Problem Symptom (s) Fundamental Cause Solution
A goal the user cannot achieve Usually a measurable or observable attribute Connect to a more fundamental principle Action that can be taken

Repairs

Principles of Operation

Modes of Operation

Operating Specifications

Operating Parameters and Limitations

Parameter Optimum Operating Range Units Effect on Outputs
(e.g. Mode 1) (e.g Mode 2) (e.g. Mode 3)
(e.g. Temperature) (Mode 1 Optimum) (Mode 2 Optimum) (Mode 3 Optimum) (e.g. 40-70) (e.g °C) (notes)
(e.g. pH) (e.g. 7) (e.g. 6.5-8.5) - (notes)

Requirements for Operation

Diagrams

Commissioning

Best Practices

Warranties

Systems Instances

Make Model Dates of Production End of Production Number Produced
(Insert Company) (Insert Model) (State a Date) (State a Date) (State a unitless quantity)
Location Date Installed Owner/Operator

Upgrades, Modifications, Hacks

Case Studies

Versions of the System

Version Dates of Production End of Production Number Produced
(Insert Version) (State a Date) (State a Date) (State a unitless quantity)

Safety

Intellectual Property

End of Life

Cost Data

Manufacturer Information