Difference between revisions of "Outline for Lab Equipment Manual"

From StemNode Lit Reviews
Line 13: Line 13:
 
== Operation ==
 
== Operation ==
  
==Maintenance and Repair==
+
=== Operation Methods ===
 +
 
 +
===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
 +
|}
 +
 
 +
==Maintenance ==
 
===Maintenance Schedule===
 
===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 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-->  
Line 31: Line 51:
 
|}
 
|}
  
===Troubleshooting ===
+
==Repair ==
<!--Historical significance of a failure is better suited for Wikipedia or other sitesYou are encouraged to link out to these sites from this section-->  
+
 
 +
== Safety ==<!--Personal protective equipment, or operating requirements -->
 +
 
 +
== Upgrades, Modifications, Hacks ==
 +
 
 +
==Versions of the System==
 +
<!--This only applies to specialized systems (those that have a make, model that have specific systems within themDelete section for specific systems -->
  
<!--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"
 
{| class="wikitable sortable"
 
|-
 
|-
! Problem
+
! Version
! Symptom (s)
+
! Dates of Production
! Fundamental Cause
+
! End of Production
! Solution
+
! Number Produced
  
 
|-
 
|-
| A goal the user cannot achieve
+
| (Insert Version)
| Usually a measurable or observable attribute
+
| (State a Date)
| Connect to a more fundamental principle
+
| (State a Date)
| Action that can be taken
+
| (State a unitless quantity)
 
|}
 
|}
 
===Repairs===
 
  
 
=Principles of Operation=
 
=Principles of Operation=
Line 125: Line 148:
 
|  
 
|  
 
|}
 
|}
 
==Upgrades, Modifications, Hacks==
 
  
 
==Case Studies==
 
==Case Studies==
 
==Versions of the System==
 
<!--This only applies to specialized systems (those that have a make, model that have specific systems within them.  Delete section for specific systems -->
 
 
{| class="wikitable sortable"
 
|-
 
! Version
 
! Dates of Production
 
! End of Production
 
! Number Produced
 
 
|-
 
| (Insert Version)
 
| (State a Date)
 
| (State a Date)
 
| (State a unitless quantity)
 
|}
 
 
==Safety==
 
<!--Personal protective equipment, or operating requirements -->
 
  
 
==Intellectual Property==
 
==Intellectual Property==

Revision as of 02:16, 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

Operation Methods

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

Maintenance

Maintenance Schedule

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

Repair

Safety

Upgrades, Modifications, Hacks

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)

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

Case Studies

Intellectual Property

End of Life

Cost Data

Manufacturer Information