Skip to content

OPEnS Project Progression

Cara Walter edited this page Apr 21, 2023 · 43 revisions

OPEnS Flow

Projects at the OPEnS Lab that result in the creation of an environmental sensing device all go through a set of 8 phases before they are published and considered complete.

OPEnS_Flow Figure 1. Network Diagram

This figure depicts the flow of an OPEnS project through its 8 phases

Phase Descriptions

Project Planning

During the project planning phase, projects get defined and described then approved by OPEnS lab administration and any stakeholders of the project. This definition/description of the project includes creation of a problem statement for the project that covers specifications, estimated cost, expected operating conditions, and timeline creation.

Deliverables and Resources

Combined Template

Prototyping

During the Prototyping phase, project teams purchase materials to build the project, design any PCBs or mechanical structures, and write code.

Deliverables and Resources

Synthesis

During the synthesis phase, project prototypes are finalized and assembled to a point where they can be tested in the lab for functionality. At least two prototypes are built for testing.

Deliverables and Resources
  • Prove Loom Integrations
  • Prove Full System Functionality
    • Prototype should perform all functions (e.g. collect all types of data (with expected values) at specified interval, save data to SD, sleep) through at least one full cycle of operations (e.g. operate, sleep, operate).
  • Finalize PCBs
    • All necessary connections and components in optimal locations. Mounting holes for mechanical mounting if less than two parallel headers are present.
  • Finalize CAD and Mechanical
  • Print / Purchase PCBs
  • Print / Purchase Enclosures
  • Assemble
  • Start build guide
  • Stakeholder Demo sign-off
  • Update BOM / Timeline / Documentation

Lab Testing

During the Lab testing phase, projects are tested in lab to prove their ability to function as specified in the project planning phase. Conditions the device will be deployed in are simulated for testing so that data can be collected and analyzed for accuracy. This phase is also when documentation such as build guides and operation manuals are created.

Deliverables and Resources

Field Testing

During the Field Testing phase, multiple assemblies of the projects are deployed in the field. During this deployment, project teams will determine what is needed in deployment and servicing guides for their project. Documentation such as the operation manual and field guides are also finalized in this step.

Deliverables and Resources
  • Build 2 or 3 field units
  • Create and utilize post production testing protocol for each component
  • Create software release for version being field tested
  • Deploy on campus for at least 1 week
  • Analyze data and performance - campus deployment
  • Update/fix any hardware or software issues discovered during campus deployment
  • Test deployment at site with Stakeholder
  • Analyze data and performance - Stakeholder deployment
  • Update/fix any hardware or software issues discovered during field deployment
  • Solicit and incorporate Stakeholder sign-off / suggestions

Finalization / Production

During the Finalization / Production phase, project documentation is polished and posted to GitHub, as well as shared with project stakeholders. Any requested assemblies of this project are put together and sent out with set up, operation and maintenance information.

Deliverables and Resources
  • Ensure stakeholders can operate/service
  • Finalized operation manual
  • Finalized post production testing protocol
  • Finalized build guide
  • Optimize for scaled-up runs
  • Updated BOM / build guide for assembly line
  • Build target # of units for PI
  • Test all produced units meet specifications
  • Create software release for version being deployed
  • Full Deployment with Stakeholder
  • Finalized Wiki / Documentation
  • Write draft Validation section of HardwareX paper
  • Paper final draft

Poster / Presentation

During the Poster / Presentation phase, a poster is created for the project and the project team presents at a formal research event such as the American Geophysical Union Fall Meeting, other scientific research conferences or an event on the Oregon State University Campus.

Resources
  • Guide to Writing an AGU Abstract

  • In Person Poster Template

  • OPEnS Guide to Poster Content

    • Posters are powerful marketing tools of cutting-edge technology for immediate problem-solving
    • For ePosters, the initial view of the poster should be brief enough to be comprehensively scanned in just a few minutes but detailed enough to entice interested viewers to explore deeper
    • Your poster is the best advertisement for your prowess in instrument design
    • Posters should be aimed at least indirectly at potential grad schools and employers
  • Example Posters:

Example sections
  • What is it?
    • A network of sensors to monitor ___, ___, and ___ in .
    • Sensor output is collected by ___.
    • Sensor data are collated and transmitted to ___.
  • How does it work?
    • Currently installed sensors include ...
  • Where is it currently deployed and why?
  • Operation and maintenance
    • Exemplary data
    • Battery life
    • Data backup and manual collection
  • Future modifications
    • Replace the thing-a-ma-jig with a do-hickey to ___
  • Other potential applications
Deliverables
  • Abstract
  • Purpose
  • Component breakdown
  • Methods/calculations/extra info that's important
  • Results
  • Conclusion/Future
  • Acknowledgements
  • Zenodo Doi

Publication

During the Publication phase, project teams write a paper to be published in an academic journal such as Hardware X.

Resources
Deliverables for HardwareX
  • Abstract (200 words)
  • Title (20 words)
  • Key words
  • Specifications table
  • Hardware in context
  • Hardware description
  • Design files
  • Design file summary
  • BOM
  • Build instructions
  • Operation instructions
  • Validation and characterization
  • Zenodo Repo, DOI of your GitHub
Clone this wiki locally