A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | tt to sketchup | Actions | Products | Product Links | Comm Tools/Channels | Total Time (Hours) | Touch Time (Hours) | Resources | Responsibility | Authority | Triggers | Issues | Risks | ED Comments | ||||||||
2 | ID'd 50 GVCS to Create | Complete | 50 GVCS defined | http://opensourceecology.org/gvcs.php | website/wiki | ED | ED | ED | ED | None | None | |||||||||||
3 | Research & Analysis | Community Needs Assessment (2012) | http://opensourceecology.org/wiki/Evaluations#Community_Needs_Assessments | Wiki | Unk | Unk | Wiki | ED | ED | ED | Not clearly communicated (basis for 50 GVCS), this was buried in wiki - TCM has input from people who want to work on projects that are not a part of GVCS | |||||||||||
4 | Product Ecology | ID machines to build based on need timeline | Product Eclogues page | http://opensourceecology.org/wiki/Ecology | Wiki | ED, future expect projects | ED, PL | ED | Pilot projects requiring machines or machines that are used as modules in future machines. machines with the most modularity | Machines are built based on expected future products, but expected future products are not documented, so constantly changing; Priorities/ecology shift for unanticipated reqmts, wiki page is buried in the wiki | Priorities change, Ecology's priorities not xferred to schedule, collaborators d/n know ecology rationale (lacks transparency) | |||||||||||
5 | SME's Emerge | Contacts TCM or OSE Email | N/A | N/A | Design Sprint, email to TCM, email to ED | Design Sprint Announcements, ED's star power (as a draw) and network | TCM | SME | Various--announcements, invitations, events, general interest, social media. trad'l media | Product Ecology shifts to ensure OSE uses SME resource while it is available - draws OSE resources from primary products, weakening original time lines | SMEs result in reallocation of OSE resources - misallocation, inability to focus on 'everything', SME develops a false sense of ownership and misses opportunities to collaborate, schedule delay on other events | |||||||||||
6 | Initial Product Concept | ED thought out | Backhoe page | http://opensourceecology.org/wiki/Backhoe | Product page on wiki | ED | ED | ED | Product Ecology | Location of information is not standardized, product specification requirements are not standardized, Certain collaborators are collaborated with to acertain this Product Concept - this needs to be transparent | Concept is not communicated to collaborators, risks major redesign throughout design process, delay to schedule | |||||||||||
7 | Backhoe Concept Discussion | http://opensourceecology.org/wiki/Backhoe_Concept_Discussion | Page on wiki | Wiki | ED | ED | ||||||||||||||||
8 | OSE Specifications | http://opensourceecology.org/wiki/OSE_Specifications | Wiki | Wiki | ED | ED | ||||||||||||||||
9 | Establish Product Development Schedule | Verbal, Wiki | GVCS Rollout Sequencing | http://opensourceecology.org/wiki/GVCS_Rollout_Sequencing | Verbal, Wiki | ED, future expect projects | ED | ED | ED directs and/or PL, RC, & DPV request for direction or specifications | No location on wiki or specification requirements, Rollout Sequencing is grossly outdated & difficult to for users to find | Low participation due to frustrations, new projects delaying other projects | PL needs to specify feasible rate of development for ED's schedule to be meaningful. | ||||||||||
10 | Communicate Prod Dev Sched to Community | Verbally discussed | Invitation emailed to community | http://opensourceecology.org/wiki/6_in_60_Campaign_-_Design_Sprint_5_Invitation | Invitation emailed to community | Wiki | TCM | ED | ED directs and/or PL, DPV requests | Piecemeal in the form of blogs and Design Sprint announcements, No written schedule | No accountability, so subject to change, decrease DPV recruitment ability due to schedule churn/last minute schedule changes, etc | Schedule depends on the number + quality of DPVs and Design Sprint participants. Milestones for these need to be established for schedule to be established. Schedule depends on OSE capacity to manage contributions from technical community. Assumption is that development rate increases with contributor numbers. | ||||||||||
11 | Blog | http://blog.opensourceecology.org/2013/06/all-aboard-the-6-in-60-campaign-continues/ | Blog/Wiki | Elizabeth | Staff | Staff | ||||||||||||||||
12 | Landing Page | http://opensourceecology.org/wiki/6_in_60_Campaign | Landing Page/Wiki | TCM | TCM | TCM | ||||||||||||||||
13 | Events Link on Wiki Main Page | http://opensourceecology.org/w/index.php?title=Category:Current_Events&oldid=94675 | Events Link on Wiki Main Page | Staff, Blogger | ? | ? | ||||||||||||||||
14 | Discuss Initial Product Concept | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | ED | ED/PL | ED | PL requests | No written product concept or specification - this results in many iterations, this discussion rarely happens, no products produced to capture Product Concept | No accountability, so subject to change, lack of documentation risks clearly communicating Initial Product Concept to community; PL lacks SA on what the Product Concept, risks misdirection to collaborators | |||||||||||
15 | PL Provides Input | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | PL experience | PL | PL | PL IDs need during product discussion w/ ED | This step rarely occurs, No written input, no documentation for tracking or communication, DPVs are able to provide a concept > then feedback occurs | lack of documentation = lack of accountability; PL lacks SA on what the Product Concept is, risks major redesigns and delayed schedule; increases workload to collaborators and staff | |||||||||||
16 | Product Concept | ED thought out | Backhoe Conceptual Diagram | http://opensourceecology.org/wiki/Backhoe_Conceptual_Diagram | Verbal - no explicit documentation | ED, PL input | ED/PL | ED | Need to clearly communicate Product Concept to PL to then communicate to DPVs | Little written documentation, no accountability, product concept is not clearly communicated to collaborators or staff, concept changes during design process | risks major redesigns and delayed schedule; increases workload to collaborators and staff | |||||||||||
17 | Backhoe Conceptual Specifications | http://opensourceecology.org/wiki/Backhoe_Conceptual_Diagram | ||||||||||||||||||||
18 | Main Machine Info-graphic | Research & Draw | Info-graphics | http://opensourceecology.dozuki.com/c/CNC_Circuit_Mill | Uploaded on Jean's work log then Dozuki | Wiki, Research, ED | DM | DM | ED directs DM | No Staff collaboration with designs, no review process to ensure the product concept is properly conceptualized in the drawing, d/n distinguish betw concept and product in development | Lack of transparency throught the Company, risks miscommunication to community as to what we are actually designing | |||||||||||
19 | Create OSE Sketchup Warehouse | Created once. not a step | Standardized Building Components | http://opensourceecology.org/wiki/Warehouse | Versions kept on DPV logs | PL, DPV, RC | DPV | DPV | PL, DPV create as drawing are finalized | (Contributers make changes by themselves... this file should be locked) No location (doesnt have its own page) , kept on personal work logs, multiple versions created | possible to add to an older version without knowing a newer version exists | |||||||||||
20 | Stick Drawing | ED creates | Simple Graphic | https://docs.google.com/drawings/d/1xJlrWbgPppF-a6EnjawUsrkubw43OKJL5PFlzxgxelU/edit | Google Drive/Draw | ED | ED | ED | Need to communicate concept to DPV for drawing | No location, kept on personal work logs, using to design - used as concept drawing | Not all persons notified when created, risks miscommunication due to lack of detail/specs/interface reqmts; risks major redesign; risks delay in schedule | |||||||||||
21 | ID Modules | ED directs | Modules listed on LifeTrac 5 wiki page | http://opensourceecology.org/wiki/LifeTrac_5 | Machine or module wiki page | ED, DPVs, PL, wiki research | ED | ED | Need to communicate concept to DPV for drawing | No std location on wiki, kept on personal work logs; | Risks delay in schedule due to inefficiencies, collaborators not able to find resources needed for design | |||||||||||
22 | Define Modules | Discussions between ED, PL, DPV | Module wiki page | http://opensourceecology.org/wiki/Bobcat_Standard_Quick_Attach_for_LifeTrac | Iterative verbal discussions | ED, wiki notes, PL, DPVs, RCs, research | ED/DPV | ED | Need to communicate concept to DPV for drawing | No location, kept on personal work logs, not all persons notified when created, lack of communication & transparency | Risks delay in schedule due to inefficiencies, collaborators not able to find resources needed for design, lack of documentation risks not being able to communicate what is being built/lack of transparency | |||||||||||
23 | Divide Modules Among DPVs | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | Number of DPVs | PL | PL | To allocate resources | Equal division is not always possible | Lack of responsibility if module is being worked simultaneously - needs a lead | |||||||||||
24 | Initial Requirements Definition | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | ED | DPV | ED | Need to communicate concept to DPV for drawing | No written documentation, no accountability | No accountability, so subject to change, br {mso-data-placement:same-cell;}lack of documentation = lack of accountability; PL lacks SA on what the Product Concept is, risks major redesigns and delayed schedule; increases workload to collaborators and staff | |||||||||||
25 | Convert stick drawing / concept to Sketchup | Time on SketchUp | Preliminary skp file | http://opensourceecology.org/wiki/File:LifeTrac_4_V1_snip.PNG | Wiki | Sketch up | DPV | DPV | Need to begin drawing | Lacks any kind of detail, literally a stick drawing; No standardized file naming system; | Risks design creep, lack of vision in the beginning, cause to redesign more than necessary.; risks delays to schedule/major redesigns | |||||||||||
26 | Review previously developed modules for integration (In relation to utilizing one module for a different design) | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | Wiki research, ED inputs | DPV | DPV | Need to focus design, provide direction for design | No one-stop-shop of prior designs, not adequate timing - should be covered during product concept | Missed opportunity to improve from past mistakes or wins; timing of this reqmt risks delay of schedue/inefficiency | |||||||||||
27 | Define physical interfaces | Verbally discussed | Interface integrated onto module design | N/A | Verbal - no explicit documentation | ED direction, past interfaces | ED | ED | Need to complete design - reached a module edge | Needs one person to coordinate, decide - creates bottleneck, needs to be a step in product concept | Potential for design not to be able to interface if this discussion does not happen soon enough - should happen in the product concept page | |||||||||||
28 | DPV Research | Individual research, group/team research discussion | N/A | N/A | Verbal - no explicit documentation | internet, wiki research | DPV | DPV | Need for direction and specifications by imiting certian options and providing other options for design | Scope is needed, how do you organize? Lacks standardization where research is documented; not easily navigable for future collaborators to find | too much time spent researching, not enough time spent researching, inefficient/effective research, too much information | |||||||||||
29 | Draw modules in SketchUp | SPV / Collaborators | Drawing of module on sketch up | http://opensourceecology.org/wiki/File:OSEquickAttach.skp | SketchUp; Wiki | PL, DPV, RC | DPV/RC | DPV | DPV assigned module | Large scale collaboraiton is not possible in sketchup; Some users have newer/older versions of SketchUp | not perfect as far as fit and function | |||||||||||
30 | Requirements Creep | ED changing mind | Lucas Log (dates Jul 3-11) shows v 1-8 of LifeTrac | http://opensourceecology.org/wiki/Lucas_Log | Verbal, sometimes via logs | ED | N/A | ED | DPV requests additional direction, QA identifies missed specification | Requirements/Specs are ill-defined causing churn to dev process; Requires extra time to rework previous design | unending cycle - lengthen timeline, not completing in time | |||||||||||
31 | Compile modules | One person compiles SketchUp files from collaborators' wiki pages | Preliminary compiled design | http://opensourceecology.org/wiki/File:OSEquickAttach.skp | Wiki | DPV, RC, PL | DPV | PL | Machine wiki page is created, PL directs modules to be emailed to him or placed on machine's wiki page | This step is constantly skipped, people assume their personal log is being checked for updated module, no single source for where modules are uploaded to be compiled | completed work goes un-QA'd or reviewed, next step is not initiated; risks schedule delays due to finding the correct modules for compiling; lack of transparency for the user | |||||||||||
32 | http://opensourceecology.org/wiki/Bobcat_Standard_Quick_Attach_for_LifeTrac | SketchUp | DPV | PL | ||||||||||||||||||
33 | http://opensourceecology.org/wiki/LifeTrac_5 | DPV | PL | |||||||||||||||||||
34 | Systems Engineering Breakdown Diagram | http://opensourceecology.org/wiki/December_18#Redesign_for_CNC_Torch_Table | Wiki/Google Docs | DPV | PL | |||||||||||||||||
35 | Parts dictation | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | ED | ED/PL/DPV | ED | Module design completed, DPV notifies PL or ED | No one-stop-shop, often certian parts decisions are disputed with no documentation, which means, no accountability - continious issues regarding part choice, no updated inventory--parts availability and parts use requirements should be conveyed earlier in the process as they can effect the design | Concensus is not always made or final decision supported - this result in follow on issues that re attibuted to parts decisions; schedule delays/major redesign if parts dictation occurs at this point in the process | |||||||||||
36 | Requirements Definition | Verbally discussed | N/A | N/A | Verbal - no explicit documentation | ED | ED | ED | Need for direction or specification - DPV requests OR parts dictation provides additional specifications | no documentation, need for justification of redesign to justify extra time/resources this requires, endless design cycle | endless re-design cycle; having further requirments definition at this stage in the process risks major redesign and schedule delays; risks frustrating volunteers; risk volunteer retention | |||||||||||
37 | Designer Review | Notify other designers that design is ready for review, Trade designs, provide feedback | N/A | N/A | Verbal feedback - no explicit documentation | DPVs, internet | DPV/RC | DPV/RC | DPV/RC reaches stopping point in design - notifies others | Feedback is not documented, so continuous issues are not resolved because designer has full autonomy to make final design decision; Slow internet for wiki updated/uploads, no standardized process | Lacking checks and balance due to designer's sole authority at this stage, lack of documentation risks losing traceability of design rationale | |||||||||||
38 | Designer Rationale | Capture rationale of design creation via mental notes or in writing | May be documented | Wiki log | DPV/RC | DPV/RC | DPV/RC | Contensious issue sparks rationale discussion | Captured mentally or in DPV wiki log - Feedback is not documented, designer has full autonomy to make final design decision | Rationale not questioned in open source platform; lack of documentation risks losing traceability of design rationale | ||||||||||||
39 | Design Iterations | Check for conflicts, bolt pattern practicality | "Instructional" on wiki | http://opensourceecology.org/wiki/Quality_Control | Comm to collaborator via Wiki instructional, skp file in logs | Days | Days | Wiki | DPV/RC | PL | Finished module re-design | Sketch up does not always show issues that crop up in build, little QA protocol, no documentation, Slow internet for wiki updated/uploads; No standardized file naming system; | Missing something, miss communicating an issue because no documentation - no verificition step | |||||||||
40 | Create DXF/STL Files to Machinist Source | create CNC readable files | CNC readable files | http://opensourceecology.org/wiki/File:Wheel_Mounts_Part_1.dxf | SketchUp/Libre | 2 hours | Wiki | DPV | ED | Finished module design | No location to store, compile; No standardized file naming system, Process isnt lean yet, making DXF files when not needed. | Lacking ability or step to ensure all sourced work is compiled. | ||||||||||
41 | QA (Designer) | Trade designs for peer review, review, provide feedback | "Instructional" on wiki | http://opensourceecology.org/wiki/Quality_Control | Comm to collaborator via Wiki instructional | 90 min | Wiki | DPV/RC | DPV/RC | Finished module design | Sketch up does not always show issues that crop up in build,little QA protocol | Risks skipping a QA step; if there is a problem, it will be found at a later stage | ||||||||||
42 | QA (Staff) | review, provide feedback | N/A | N/A | Verbal feedback | TBD / Doesn't Exist | PL/ED | ED | DPV/RC finish Designer QA and required redesign | Sketch up does not always show issues that crop up in build, little QA protocol, no documentation | Missing something, miss communicating an issue because no documentation - no verificition step, Risks skipping a QA step; if there is a problem, it will be found at a later stage | |||||||||||
43 | Design Support System Interfaces (hydraulics schematics) | Verbally discussed, sometimes documented in wiki/google docs | Hydraulic Schematics for Wheels of the Truck | https://docs.google.com/a/opensourceecology.org/drawings/d/1_e_DBEq6RrHMsU_Vrcmx9f1cEZdiv5S5BoCDRcgLj6w/edit | Verbal, Collaborator Log | Wiki/ Google Docs | DPV | ED | Modules complete - natural next step | No sourcing of support system SMEs integrated into the plan, no single lead for design, so location to document, Sketch up plug-ins to draw hydralics are not always easy to locate; need to integrate instructional into Design Process protocols | The support system is not always mapped out prior to build due to difficulty associated with drawing and time contraint; lack of effective way of communicating the instructional & standardizatin to new collaborators risks "re-inventing the wheel"--risks longer schedule, lack of standardization | |||||||||||
44 | Design Iterations | Redesign/improve | Finished Design Product | SketchUp; Wiki | ED/PL | DPV | ED | DPV redesigns to integrate support system interfaces | Sketch up does not always show issues that crop up in build, little QA protocol, no documentation, Slow internet for wiki updated/uploads; No standardized file naming system; | Missing something, miss communicating an issue because no documentation - no verificition step | ||||||||||||
45 | QA (Designer) | Check for conflicts, bolt pattern practicality | "Instructional" on wiki | http://opensourceecology.org/wiki/Quality_Control | Comm to collaborator via Wiki instructional, skp file in logs | Wiki | DPV/RC | PL | Finished module re-design | Sketch up does not always show issues that crop up in build, little QA protocol, no documentation | Missing something, miss communicating an issue because no documentation - no verificition step | |||||||||||
46 | QA (Staff) | Review skp files from Collaborator Logs | None | Via Collaborator Logs, Verbal Feedback | TBD / Doesn't Exist | PL/ED | ED/PL | Finished module design | Sketch up does not always show issues that crop up in build, no QA protocol | Missing something | ||||||||||||
47 | Finalize Product 3D Design | Uploaded skp file to log | Final skp file | http://opensourceecology.org/wiki/File:Backhoe_deep_dig.skp | Collaborator blog/ Wiki | DPV | DPV | ED | QA review complete/all changes complete | N/A | Design change required during build process due to unforeseen challenge | |||||||||||
48 | Compile BOM/Cutlist | Ironworker Prototype II BOM | http://opensourceecology.org/wiki/Ironworker_Prototype_II_BOM | Wiki, email, google docs | DPV | DPV | ED | Finalized 3D Design | BOMs are largely unstandardized: can be text in skp file, in google docs or excel | No BOM template resulting in different BOM outputs | ||||||||||||
49 | Create consolidated list of metal to be cut | Cutlist Example | https://docs.google.com/a/opensourceecology.org/spreadsheet/pub?key=0Ase0fhS6TipedF9OZ2MzbEEyYVZ4RWpFeUtYV0Q4Tnc&output=html | Google docs to wiki | DPV, final skp file | DPV | DPV | Need to source parts triggers BOM creation | No standardized QA process for Cutlist, mistakes; best practice: paired cut sections to add up to 10 ft to maximize use of steel (need to integrate this best practice into an instructional) | No BOM template resulting in different BOM outputs | ||||||||||||
50 | QA BOM | Review BOM for accuracy compared to skp file | None | N/A | Verbal | DPV, final skp file | DPV | DPV | Completed BOM triggers QA | Located on collaborators' wiki logs. Need to standardize location. | No BOM template resulting in different BOM outputs | |||||||||||
51 | Source Parts | Internet (Surplus Center) | https://www.surpluscenter.com/ | Internet & Phone | internet, phone | DPV | ED | QA'd BOM provides ability to source parts | No priority regarding time vs cost, no navigable vendor list; we didn't provide appropriate lead time for providers. | Risk excess spending or excess time spent to ship; we overlook needed parts - Delays | ||||||||||||
52 | Input into DPV log | List of parts & where to get them | http://opensourceecology.org/w/index.php?title=Leandra%27s_Log&oldid=97294 | Wiki/personal logs, internet, phone | internet, phone | DPV | ED | QA'd BOM provides ability to source parts | No priority regarding time vs cost, no navigable vendor list | Risk excess spending or excess time spent to ship | ||||||||||||
53 | Order Parts & Support Equip | Surplus Center & Harbor Freight | Parts | http://www.harborfreight.com/ | Internet & Phone | ED/COO | ED/COO | QA'd Sourced Parts List | Requires 3 bids - takes time | Accounts resulting in credits could result in unneccessary finance costs; we overlook needed parts - Delays | ||||||||||||
54 | Create Vendor Accounts | Call vendors or fill out online account forms | Vendor Account | N/A | Internet & Phone | Vendors, phone | OM | OM | Need for part from vendor who has account capabilities | Passwords and log in IDs need to be tracked | Time to take creating accounts is always longer than expected | |||||||||||
55 | Parts Pickup/Delivery | Parts delivered via mail or physically picked up by OSE staff | Parts requisition | N/A | N/A | OSE Pick-up Truck, Uhaul or other delivery truck | OM | OM | Orders placed | Time/resources to pick up parts that cannot be delivered via mail, lack access to the right size vehicle to transport materials, costly due to multiple trips in a smaller truck | Parts not accounted for; schedule delays because parts aren't here, consumes manpower to physically pick up parts; increases cost due to lack of proper sized vehicle (multiple trips, more gas, more manpower) | |||||||||||
56 | Develop Work Instructions | DPV create using sketch up | Pheonix Assembly Method | https://docs.google.com/a/opensourceecology.org/document/d/13tM4FTpDOzPgkQuV9bw03VBbvS_qLdpoWE0evrU1zok/edit | Sketch up, google drive has instructions | Template created in google drive | DPV | PL | Finished BOM, impending build | Different templates or procedures have been used - need one method | Different procedures resulted in confusion and difficult to understand instruction because the same DPV who build the machine produced the work instructions - too intuitive for them | Lucas shows current DPV's | ||||||||||
57 | Inventory (partial): Parts & support equip | DPV go to workshop to verify parts | N/A | N/A | Verbal | Workshop, memeory, recollection | PL, DPV | PL | PL or ED directs DPV to verify parts onhand | Time wasted to verify parts independently - frustratining for DPV, partial inventory was not complete and caused oversights/last minute adds to parts/equipment lists, no standardized process to have SA of parts on hand | inefficient process wastes time and resources; lack of a full inventory and inspection process risks not having all parts/equipment on hand needed...forcing last minute substitions outside of the design parameters | |||||||||||
58 | Pick up support equip | Drive to source | N/A | N/A | None, no process in place (point and send) | OSE Pick-up Truck | PL | PL | Need for equipment | Emerging need results in inefficent sourcing ,br {mso-data-placement:same-cell;}Time/resources to pick up parts that cannot be delivered via mail, lack access to the right size vehicle to transport materials, costly due to multiple trips in a smaller truck | Wasted time | |||||||||||
59 | Cutting | Measure, cut | Cut pieces | N/A | Cut-list on a slip of paper | Abrasive cut-off saws | DPV | DPV | Impending build, equipment on hand | Current DPVs were mindful of making cuts to optimize materials and efficient cutting - no protocol in place to ensure this happens each time; Cheap tools | without cutting protocol - risk wasting materials and having to make extra cuts | |||||||||||
60 | Take photos | Take photo | Pictures | http://opensourceecology.org/wiki/File:LifeTrac_5_Photo1.JPG | smart phone, DM's camera | DM's camera, ability to upload as jpg | DPV, PL, ED, DM, TCM | DM | Mindful participants, build phase | No protocol - so unless someone takes responsiblity there is no documentation | missed opportunities to document, no process in place to capture "how to" documentation -- risks not being able to communicate to users who want to build our machines via instructionals | |||||||||||
61 | Install time lapse | Framing, Camera Settings, Setting Intervalometer | Still Photos | Verbal | OSE Digital SLR & Intervalometer; Adobe Premier | DM/DPV | DM | Build Phase | No instructionals for setting up time lapse function on camera, no standrdized practice for camera placement | Delay due to camera set up issues, not capturing pertinent content/missing documentation | ||||||||||||
62 | Parts Pickup/Delivery | Parts delivered via mail or physically picked up by OSE staff | Parts requisition | N/A | N/A | OSE Pick-up Truck, Uhaul or other delivery truck | OM | OM | Finalized BOM/ID'd need for part | Time/resources to pick up parts that cannot be delivered via mail, lack access to the right size vehicle to transport materials, costly due to multiple trips in a smaller truck | Parts not accounted for; schedule delays because parts aren't here, consumes manpower to physically pick up parts; increases cost due to lack of proper sized vehicle (multiple trips, more gas, more manpower) | |||||||||||
63 | Create Cut Parts Warehouse | Cut and Stack build Parts into modules. | All cut parts that will be used in the build | http://opensourceecology.org/wiki/File:Warehouse_for_LifeTrac.jpeg | Build process step / Work Instructions | Floor Space | DPV | PL | Cutting in progress | Cheap chop saws break/burn up Make sure it happens again. | ||||||||||||
64 | Mentally Tracked Lessons Learned | As problems arose, mentally tracked lessons learned | None (hopefully captured in log after build) | None | Maybe verbal discussion or log | DPV/Staff | PL | PL | Problems during prototyping | Lessons learned are not captured throughout the process and there is no process for capturing issues post-prototyping. We need standard process | Not capturing lessons learned produces poor instructionals and sets us up to make the same mistakes later | |||||||||||
65 | Workflow Discussion | Discuss where/how modules will be built to determine pre-placement of parts/tooling; teaming | None (whiteboard may be used) | None | Verbal | ED/PL/DPV | PL | PL | Work reday to begin | Does not happen every time or the workflow is not followed when work starts, workflow not documented, communicated verbally to participants | Risks miscommunication | |||||||||||
66 | Divide cut parts by module/assy | Divide cut parts by exploded parts diagram according to workflow discussion | None | None | Verbal | Printed Assembly Instructions | DPV | PL | Completed cut list | Not always done, no QA process to verify that each module has all of the parts needed for the build | Schedule delays as parts are sorted during build, risk oversight that a part was not cut for a module | |||||||||||
67 | Install time lapse | Framing, Camera Settings, Setting Intervalometer | Still Photos | N/A | Verbal | OSE Digital SLR & Intervalometer; Adobe Premier | DM/DPV | DM | Build Phase | No instructionals for setting up time lapse function on camera, no standrdized practice for camera placement - crucial to catch pertinent content | Delay due to camera set up issues, not capturing pertinent content/missing documentation | |||||||||||
68 | Parts Pickup/Delivery | Parts delivered via mail or physically picked up by OSE staff | Parts requisition | N/A | N/A | OSE Pick-up Truck, Uhaul or other delivery truck | OM | OM | Finalized BOM/ID'd need for part | Time/resources to pick up parts that cannot be delivered via mail | Parts not accounted for | |||||||||||
69 | Photos/doc of build | Take photos of key steps during build for documentation purposes | Still photos/video | N/A | N/A | OSE Digital SLR & Intervalometer; personal cameras, Adobe Premier | Staff/DPV | DM | Build Phase | Not all DPVs have cameras, add'l cameras for use will provide documentation; d/n pre-ID key/crucial steps during build to ensure proper documentation, other? | ||||||||||||
70 | Lessons learned | Mentally captured/discussion | N/A | N/A | N/A | Photo, Wiki, mental notes | Everyone | ALL Hands | Solved problems; Efficient methods developed | Lessons learned are not captured throughout the process and there is no process for capturing issues post-prototyping. We need standard process | Not capturing lessons learned produces poor instructionals and sets us up to make the same mistakes later | |||||||||||
71 | Hydraulics Review | Review hydraulics via Google docs products/wiki logs, or handwritten on white board/paper | Google docs product / handwritten product | https://docs.google.com/a/opensourceecology.org/drawings/d/1_e_DBEq6RrHMsU_Vrcmx9f1cEZdiv5S5BoCDRcgLj6w/edit | Build process step / Work Instructions | Internet, Working Dry Erase Markers | End user & ED | ED | Time for hydraulics/ none | Done out of order. | Bottleneck potential | |||||||||||
72 | Install time lapse | Framing, Camera Settings, Setting Intervalometer | Still Photos | Verbal | OSE Digital SLR & Intervalometer; Adobe Premier | DM/DPV | DM | Build Phase | No instructionals for setting up time lapse function on camera, no standrdized practice for camera placement - crucial to catch pertinent content | Delay due to camera set up issues, not capturing pertinent content/missing documentation | ||||||||||||
73 | Assemble | All Hands | Final Assembly | Final Tested Product (dont have) | Build process step / Work Instructions | Shop Tools; Material | ALL Hands | Warehouse of cut material completed | Holes don't line up; Safety; Sometimes clear plan; d/n plan for enough time for a prototype buildout | Lack of a process slows down build time; long work days create safety concerns/risk personnel being hurt, liability to OSE | ||||||||||||
74 | Install time lapse | Framing, Camera Settings, Setting Intervalometer | Still Photos | Verbal | OSE Digital SLR & Intervalometer; Adobe Premier | DM/DPV | DM | Build Phase | No instructionals for setting up time lapse function on camera, no standrdized practice for camera placement - crucial to catch pertinent content | Delay due to camera set up issues, not capturing pertinent content/missing documentation | ||||||||||||
75 | Safety Inspection | Visual inspection of plumbing and mechanical processes; Exit plan; Fire extinguishers | Functional Assembly | N/A | Verbal | TBD / Need Process | PL/Staff | Staff/PL | Completing of build phase | No standardized/industry accepted process. No engineering analysis on stress points. | Death/ Dismemberment, schedule delay, liable | |||||||||||
76 | Development Test Strategy | Brief test to insure clearance and Hyd functionality | Brief test to insure clearance and Hyd functionality | N/A | Verbal | PL | PL/Staff | PL/STAFF | Completion of build | No Process in Place; Lack of any real testing methodogy for failure rates, functionality, safety issues etc. | Risk producing a product that does not meet specifications/has safety issues | |||||||||||
77 | Review of Test Results | Doesnt Exist beyond hypothetical | Doesnt Exist beyond hypothetical | N/A | Doesnt Exist beyond hypothetical | TBD / Need Process | PL/Staff | Staff/PL | Completion of testing | No standardized testing procedure. Lack of any real testing methodogy for failure rates, functionality, safety issues etc. | Risk producing a product that does not meet specifications/has safety issues | |||||||||||
78 | Functional Test | Range of Motion, Check for conflicts, Fix problems (Used once) Not a proceedure | Functional Loader Arms | N/A | Physical test | TBD / Need Process | PL/Staff | Staff/PL | Completion of Test Strat | No standardized testing procedure. Lack of any real testing methodogy for failure rates, functionality, safety issues etc. | Risk producing a product that does not meet specifications/has safety issues | |||||||||||
79 | Limited Operational Test | Movement, Limited load test (used once) not a proceedure | Doesnt Exist beyond hypothetical | N/A | Doesnt Exist beyond hypothetical | TBD / Need Process | PL/Staff | Staff/PL | Completion of Safet Inspection | Not always done; done with no regard for safety or the fact that these are prototypes and need to be tested carefully. Lack of any real testing methodogy for failure rates, functionality, safety issues etc. | Risk producing a product that does not meet specifications/has safety issues | |||||||||||
80 | Create Prototype Assessment | Conduct assessment per guidelines | Prototype Assessment | http://opensourceecology.org/wiki/Prototype_Assessment | Wiki | Wiki | PL/Staff | Staff/PL | Completion of Functional Testing | Limited Assessments beyond real world applications. (Not the place to do testing or make assessments); no process to capture the data for re-integration into process | Though this step existsl we have not performed the task; risk producing a product that does not meet specifications and not even knowing it. | |||||||||||
81 | Prototype Assessment | Doesnt Exist beyond hypothetical | Doesnt Exist beyond hypothetical | N/A | Doesnt Exist beyond hypothetical | TBD / Need Process | PL/Staff | Staff/PL | Completion of Functional Testing | Limited Assessments beyond real world applications. (Not the place to do testing or make assessments) | Not able to have lessons learned to improve future products | |||||||||||
82 | Share photos to DM | Upload via Latakoo (need to check) | Still Photos | Latakoo | DPV/Staff | DM | Buildphase, end of build | It doesn't happen all the time; It's an afterthought at this point; Not everyone has a smartphone for using Dozuki App | Missing visual documentation | |||||||||||||
83 | Upload video to DM | Uploaded via Latakoo | Video | Latakoo | DPV/Staff | DM | Throughout build/end of build | Need good internet; Only one person documenting entire build | Schedule delay | |||||||||||||
84 | Log video and order transcripts | View and process on Latakoo | Latakoo | DM | DM | Video upload complete | ||||||||||||||||
85 | Prepare outline for video documentation | Write in open source document | Document | Email/Google | DM | DM | Build phase | |||||||||||||||
86 | Write script | Write in open source document | Script | Email/Google | DM | DM | Outline complete | |||||||||||||||
87 | Send script & video notes to remote editors | Email to RE's | Email/Google | Script | DM | DM | Script complete | Need remote editors | ||||||||||||||
88 | Edit video | Individual NLE systems/Latakoo | Video | Latakoo | Script, Latakoo | DM/RE | DM | Script complete, video sent to REs | Time consuming | All consuming | ||||||||||||
89 | Submit rough video to team for review | Latakoo, YouTube, Vimeo upload | Video | Latakoo | Latakoo | DM | DM | Editing complete | ||||||||||||||
90 | Revise video | Individual NLE systems/Latakoo | Video | Latakoo | Latakoo | DM/RE | DM | Team review complete, feedback received | ||||||||||||||
91 | Send video to musician | Latakoo, YouTube, Vimeo upload, Email directions | Video, Emailed directions | Latakoo | Latakoo | DM | DM | Editing complete | ||||||||||||||
92 | Integrate music | Latakoo | Latakoo | Latakoo | Musician/RE | Video sent to musician | ||||||||||||||||
93 | Record narration | Smart phone app and email | Audio File | Email/Google | Script, Latakoo, recording device (i.e smart phone | DPV/Staff/RE | DM | Music integrated | ||||||||||||||
94 | Integrate narration, etc to complete video | Individual NLE systems/Latakoo | Video | Latakoo | Script, Latakoo | DM/RE | DM | Revision complete, musician work complete | ||||||||||||||
95 | Upload final video | Upload to Latakoo, Youtube, Vimeo | Video | Latakoo/YouTube/Vimeo | DM | DM | Video complete | |||||||||||||||
96 | Workshop Inventory (tools, supplies, parts, materials) | |||||||||||||||||||||
97 | Workshop Layout | |||||||||||||||||||||
98 | Tool Control | |||||||||||||||||||||
99 | Tool Maintenance and Replacement | |||||||||||||||||||||
100 |