-
Notifications
You must be signed in to change notification settings - Fork 3
OPEnS Project Progression
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.
Figure 1. Network Diagram
This figure depicts the flow of an OPEnS project through its 8 phases
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
- New Personnel Training
- Expected Operating Conditions: Template
- Target Specifications Table: Template
- Napkin Drawing: Example
- System Block Diagram: Example
- Lucidchart for making block-and-arrow diagrams to show the evolving concept of the systems / parts, their functions, and how they work together
- Wikipedia
- State Machine Diagram: Example, Wikipedia
- BOM: Template
- Stakeholder Sign-off: Template
- Create a Wiki page for your project: Template; Wiki Contribution Guide
- Gantt Chart: Template
- Start posting updates on your Wiki page
During the Prototyping phase, project teams purchase materials to build the project, design any PCBs or mechanical structures, and write code.
Deliverables and Resources
- State Diagrams of all Modules: Example
- Sign-off for each prototype module
- Design and order custom PCBs
- Purchase BOM for 1 prototype
- Build electronics for 1 prototype
- Create Github code repository within the OSU OPEnS organization
- Find/create code for each sensor
- Loom Resources:
- Procure industry-standard sensors/solutions for validation
- Calibrate sensors against industry sensor or solutions
- CAD and Mechanical Designs
- Reassess Timeline and BOM
- Develop actual specifications based upon module validation/calibration
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
- Loom Resources:
- 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.
- PCB Guidance / Resources
- Send .brd file to Chet and designated peer PCB reviewer for approval
- 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
- Examples of brands previously used:
- Assemble
- Start build guide
- Build Guide Example: See section 5 of this publication for the HyperRail
- Stakeholder Demo sign-off
- Update BOM / Timeline / Documentation
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
- Create testing plan
- Testing Plan Example: Smart Rock Rev 2.5 2019
- Create software release for version being lab tested
- Purchase and Build 2 prototypes
- Collect a ton of data and analyze
- Prove enclosure in simulated conditions
- Prove sensors in simulated conditions
- Procure industry-standard sensors for validation
- Prove sensors against industry sensors
- Calibrate sensors to industry sensor
- Create a FMEA
- Redesign / modify / repeat
- Create operating manual
- Operating Manual Example: See section 6 of this publication for the HyperRail
- Paper outline
- Refer to Paper/Publication Resources below for a paper template and guides.
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
- Testing Protocol Example:
- 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
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
- Refer to Paper/Publication Resources below for a paper template and guides.
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
-
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
During the Publication phase, project teams write a paper to be published in an academic journal such as Hardware X.
Resources
-
OPEnS Specific
-
External
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
- Project Planning
- Prototyping
- Synthesis
- Lab Testing
- Field Testing
- Finalization/Production
- Poster/Presentation
- Publication
- CRES
- Dendrometer
- Djinn
- eDNA Sampler
- eGreenhouse
- Evaporometer
- FloDar
- HyperRail
- Hypnos
- Isotopic Sampler
- Lilypad
- Loom
- Micro-Aggregating Sewer Sampler
- Mooraca
- OPEnSampler
- Pied Piper
- Rag Guard
- Rain Gauge Calibrator
- RainSavor
- RFID Moisture
- Sap Flow Meter
- SitkaNet
- Slide Sentinel
- Smart Rock
- Spool
- WeatherChimes
- Weed Warden
- Wisp
- Archived Project Blogs