ABCDEFGHIJKLMNOPQRSTU
1
tt to sketchupActionsProductsProduct LinksComm Tools/ChannelsTotal Time (Hours)Touch Time (Hours)ResourcesResponsibilityAuthorityTriggersIssuesRisksED Comments
2
ID'd 50 GVCS to CreateComplete50 GVCS definedhttp://opensourceecology.org/gvcs.phpwebsite/wikiEDEDEDEDNoneNone
3
Research & AnalysisCommunity Needs Assessment (2012)http://opensourceecology.org/wiki/Evaluations#Community_Needs_AssessmentsWikiUnkUnkWiki EDEDEDNot 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 EcologyID machines to build based on need timelineProduct Eclogues pagehttp://opensourceecology.org/wiki/EcologyWikiED, future expect projectsED, PLEDPilot projects requiring machines or machines that are used as modules in future machines. machines with the most modularityMachines 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 wikiPriorities change, Ecology's priorities not xferred to schedule, collaborators d/n know ecology rationale (lacks transparency)
5
SME's EmergeContacts TCM or OSE EmailN/AN/ADesign Sprint, email to TCM, email to EDDesign Sprint Announcements, ED's star power (as a draw) and networkTCMSMEVarious--announcements, invitations, events, general interest, social media. trad'l mediaProduct Ecology shifts to ensure OSE uses SME resource while it is available - draws OSE resources from primary products, weakening original time linesSMEs 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 ConceptED thought outBackhoe pagehttp://opensourceecology.org/wiki/BackhoeProduct page on wikiEDEDEDProduct EcologyLocation 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 transparentConcept is not communicated to collaborators, risks major redesign throughout design process, delay to schedule
7
Backhoe Concept Discussionhttp://opensourceecology.org/wiki/Backhoe_Concept_DiscussionPage on wikiWiki EDED
8
OSE Specificationshttp://opensourceecology.org/wiki/OSE_SpecificationsWikiWiki EDED
9
Establish Product Development ScheduleVerbal, WikiGVCS Rollout Sequencinghttp://opensourceecology.org/wiki/GVCS_Rollout_SequencingVerbal, WikiED, future expect projectsEDEDED directs and/or PL, RC, & DPV request for direction or specificationsNo location on wiki or specification requirements, Rollout Sequencing is grossly outdated & difficult to for users to findLow participation due to frustrations, new projects delaying other projectsPL needs to specify feasible rate of development for ED's schedule to be meaningful.
10
Communicate Prod Dev Sched to CommunityVerbally discussedInvitation emailed to communityhttp://opensourceecology.org/wiki/6_in_60_Campaign_-_Design_Sprint_5_InvitationInvitation emailed to communityWiki TCMEDED directs and/or PL, DPV requestsPiecemeal in the form of blogs and Design Sprint announcements, No written scheduleNo accountability, so subject to change, decrease DPV recruitment ability due to schedule churn/last minute schedule changes, etcSchedule 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
Bloghttp://blog.opensourceecology.org/2013/06/all-aboard-the-6-in-60-campaign-continues/Blog/WikiElizabethStaffStaff
12
Landing Pagehttp://opensourceecology.org/wiki/6_in_60_CampaignLanding Page/WikiTCMTCMTCM
13
Events Link on Wiki Main Pagehttp://opensourceecology.org/w/index.php?title=Category:Current_Events&oldid=94675Events Link on Wiki Main PageStaff, Blogger??
14
Discuss Initial Product ConceptVerbally discussedN/AN/AVerbal - no explicit documentationEDED/PLEDPL requestsNo written product concept or specification - this results in many iterations, this discussion rarely happens, no products produced to capture Product ConceptNo 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 InputVerbally discussedN/AN/AVerbal - no explicit documentationPL experiencePLPLPL IDs need during product discussion w/ EDThis step rarely occurs, No written input, no documentation for tracking or communication, DPVs are able to provide a concept > then feedback occurslack 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 ConceptED thought outBackhoe Conceptual Diagramhttp://opensourceecology.org/wiki/Backhoe_Conceptual_DiagramVerbal - no explicit documentationED, PL inputED/PLEDNeed to clearly communicate Product Concept to PL to then communicate to DPVsLittle written documentation, no accountability, product concept is not clearly communicated to collaborators or staff, concept changes during design processrisks major redesigns and delayed schedule; increases workload to collaborators and staff
17
Backhoe Conceptual Specificationshttp://opensourceecology.org/wiki/Backhoe_Conceptual_Diagram
18
Main Machine Info-graphicResearch & DrawInfo-graphicshttp://opensourceecology.dozuki.com/c/CNC_Circuit_MillUploaded on Jean's work log then DozukiWiki, Research, EDDMDMED directs DMNo 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 developmentLack of transparency throught the Company, risks miscommunication to community as to what we are actually designing
19
Create OSE Sketchup WarehouseCreated once. not a stepStandardized Building Componentshttp://opensourceecology.org/wiki/WarehouseVersions kept on DPV logsPL, DPV, RCDPVDPVPL, 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 DrawingED createsSimple Graphichttps://docs.google.com/drawings/d/1xJlrWbgPppF-a6EnjawUsrkubw43OKJL5PFlzxgxelU/editGoogle Drive/DrawEDEDEDNeed to communicate concept to DPV for drawingNo location, kept on personal work logs, using to design - used as concept drawingNot all persons notified when created, risks miscommunication due to lack of detail/specs/interface reqmts; risks major redesign; risks delay in schedule
21
ID ModulesED directsModules listed on LifeTrac 5 wiki pagehttp://opensourceecology.org/wiki/LifeTrac_5Machine or module wiki pageED, DPVs, PL, wiki researchEDEDNeed to communicate concept to DPV for drawingNo 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 ModulesDiscussions between ED, PL, DPVModule wiki pagehttp://opensourceecology.org/wiki/Bobcat_Standard_Quick_Attach_for_LifeTracIterative verbal discussionsED, wiki notes, PL, DPVs, RCs, researchED/DPVEDNeed to communicate concept to DPV for drawingNo location, kept on personal work logs, not all persons notified when created, lack of communication & transparencyRisks 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 DPVsVerbally discussedN/AN/AVerbal - no explicit documentationNumber of DPVsPLPLTo allocate resourcesEqual division is not always possibleLack of responsibility if module is being worked simultaneously - needs a lead
24
Initial Requirements DefinitionVerbally discussedN/AN/AVerbal - no explicit documentationEDDPVEDNeed to communicate concept to DPV for drawingNo written documentation, no accountabilityNo 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 SketchupTime on SketchUpPreliminary skp filehttp://opensourceecology.org/wiki/File:LifeTrac_4_V1_snip.PNGWikiSketch upDPVDPVNeed to begin drawingLacks 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 discussedN/AN/AVerbal - no explicit documentationWiki research, ED inputsDPVDPVNeed to focus design, provide direction for designNo one-stop-shop of prior designs, not adequate timing - should be covered during product conceptMissed opportunity to improve from past mistakes or wins; timing of this reqmt risks delay of schedue/inefficiency
27
Define physical interfacesVerbally discussedInterface integrated onto module designN/AVerbal - no explicit documentationED direction, past interfacesEDEDNeed to complete design - reached a module edgeNeeds one person to coordinate, decide - creates bottleneck, needs to be a step in product conceptPotential 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 ResearchIndividual research, group/team research discussionN/AN/AVerbal - no explicit documentationinternet, wiki researchDPVDPVNeed for direction and specifications by imiting certian options and providing other options for designScope is needed, how do you organize? Lacks standardization where research is documented; not easily navigable for future collaborators to findtoo much time spent researching, not enough time spent researching, inefficient/effective research, too much information
29
Draw modules in SketchUpSPV / CollaboratorsDrawing of module on sketch uphttp://opensourceecology.org/wiki/File:OSEquickAttach.skpSketchUp; WikiPL, DPV, RCDPV/RCDPVDPV assigned moduleLarge scale collaboraiton is not possible in sketchup; Some users have newer/older versions of SketchUpnot perfect as far as fit and function
30
Requirements CreepED changing mind Lucas Log (dates Jul 3-11) shows v 1-8 of LifeTrachttp://opensourceecology.org/wiki/Lucas_LogVerbal, sometimes via logsEDN/AEDDPV requests additional direction, QA identifies missed specificationRequirements/Specs are ill-defined causing churn to dev process; Requires extra time to rework previous designunending cycle - lengthen timeline, not completing in time
31
Compile modulesOne person compiles SketchUp files from collaborators' wiki pagesPreliminary compiled designhttp://opensourceecology.org/wiki/File:OSEquickAttach.skpWikiDPV, RC, PLDPVPLMachine wiki page is created, PL directs modules to be emailed to him or placed on machine's wiki pageThis 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 compiledcompleted 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_LifeTracSketchUpDPVPL
33
http://opensourceecology.org/wiki/LifeTrac_5DPVPL
34
Systems Engineering Breakdown Diagramhttp://opensourceecology.org/wiki/December_18#Redesign_for_CNC_Torch_TableWiki/Google DocsDPVPL
35
Parts dictationVerbally discussedN/AN/AVerbal - no explicit documentationEDED/PL/DPVEDModule design completed, DPV notifies PL or EDNo 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 designConcensus 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 DefinitionVerbally discussedN/AN/AVerbal - no explicit documentationEDEDEDNeed for direction or specification - DPV requests OR parts dictation provides additional specificationsno documentation, need for justification of redesign to justify extra time/resources this requires, endless design cycleendless 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 ReviewNotify other designers that design is ready for review, Trade designs, provide feedbackN/AN/AVerbal feedback - no explicit documentationDPVs, internetDPV/RCDPV/RCDPV/RC reaches stopping point in design - notifies othersFeedback 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 processLacking checks and balance due to designer's sole authority at this stage, lack of documentation risks losing traceability of design rationale
38
Designer RationaleCapture rationale of design creation via mental notes or in writingMay be documented Wiki logDPV/RCDPV/RCDPV/RCContensious issue sparks rationale discussionCaptured mentally or in DPV wiki log - Feedback is not documented, designer has full autonomy to make final design decisionRationale not questioned in open source platform; lack of documentation risks losing traceability of design rationale
39
Design IterationsCheck for conflicts, bolt pattern practicality"Instructional" on wikihttp://opensourceecology.org/wiki/Quality_ControlComm to collaborator via Wiki instructional, skp file in logsDaysDaysWikiDPV/RCPLFinished module re-designSketch 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 Sourcecreate CNC readable filesCNC readable fileshttp://opensourceecology.org/wiki/File:Wheel_Mounts_Part_1.dxfSketchUp/Libre2 hoursWikiDPVEDFinished module designNo 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 wikihttp://opensourceecology.org/wiki/Quality_ControlComm to collaborator via Wiki instructional90 minWikiDPV/RCDPV/RCFinished module designSketch up does not always show issues that crop up in build,little QA protocolRisks skipping a QA step; if there is a problem, it will be found at a later stage
42
QA (Staff)review, provide feedbackN/AN/AVerbal feedbackTBD / Doesn't ExistPL/EDEDDPV/RC finish Designer QA and required redesignSketch up does not always show issues that crop up in build, little QA protocol, no documentationMissing 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 docsHydraulic Schematics for Wheels of the Truckhttps://docs.google.com/a/opensourceecology.org/drawings/d/1_e_DBEq6RrHMsU_Vrcmx9f1cEZdiv5S5BoCDRcgLj6w/editVerbal, Collaborator LogWiki/ Google DocsDPVEDModules complete - natural next stepNo 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 protocolsThe 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 IterationsRedesign/improveFinished Design ProductSketchUp; WikiED/PLDPVEDDPV redesigns to integrate support system interfacesSketch 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 wikihttp://opensourceecology.org/wiki/Quality_ControlComm to collaborator via Wiki instructional, skp file in logsWikiDPV/RCPLFinished module re-designSketch up does not always show issues that crop up in build, little QA protocol, no documentationMissing something, miss communicating an issue because no documentation - no verificition step
46
QA (Staff)Review skp files from Collaborator LogsNoneVia Collaborator Logs, Verbal FeedbackTBD / Doesn't ExistPL/EDED/PLFinished module designSketch up does not always show issues that crop up in build, no QA protocolMissing something
47
Finalize Product 3D DesignUploaded skp file to logFinal skp filehttp://opensourceecology.org/wiki/File:Backhoe_deep_dig.skpCollaborator blog/ WikiDPVDPVEDQA review complete/all changes completeN/ADesign change required during build process due to unforeseen challenge
48
Compile BOM/CutlistIronworker Prototype II BOMhttp://opensourceecology.org/wiki/Ironworker_Prototype_II_BOMWiki, email, google docsDPVDPVEDFinalized 3D DesignBOMs are largely unstandardized: can be text in skp file, in google docs or excelNo BOM template resulting in different BOM outputs
49
Create consolidated list of metal to be cutCutlist Example https://docs.google.com/a/opensourceecology.org/spreadsheet/pub?key=0Ase0fhS6TipedF9OZ2MzbEEyYVZ4RWpFeUtYV0Q4Tnc&output=htmlGoogle docs to wikiDPV, final skp fileDPVDPVNeed to source parts triggers BOM creationNo 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 BOMReview BOM for accuracy compared to skp fileNoneN/AVerbalDPV, final skp fileDPVDPVCompleted BOM triggers QALocated on collaborators' wiki logs. Need to standardize location.No BOM template resulting in different BOM outputs
51
Source PartsInternet (Surplus Center)https://www.surpluscenter.com/Internet & Phoneinternet, phoneDPVEDQA'd BOM provides ability to source partsNo 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 logList of parts & where to get themhttp://opensourceecology.org/w/index.php?title=Leandra%27s_Log&oldid=97294Wiki/personal logs, internet, phoneinternet, phoneDPVEDQA'd BOM provides ability to source partsNo priority regarding time vs cost, no navigable vendor listRisk excess spending or excess time spent to ship
53
Order Parts & Support EquipSurplus Center & Harbor FreightParts http://www.harborfreight.com/Internet & PhoneED/COOED/COOQA'd Sourced Parts List Requires 3 bids - takes timeAccounts resulting in credits could result in unneccessary finance costs; we overlook needed parts - Delays
54
Create Vendor AccountsCall vendors or fill out online account formsVendor AccountN/AInternet & PhoneVendors, phoneOMOMNeed for part from vendor who has account capabilitiesPasswords and log in IDs need to be trackedTime to take creating accounts is always longer than expected
55
Parts Pickup/DeliveryParts delivered via mail or physically picked up by OSE staffParts requisitionN/AN/AOSE Pick-up Truck, Uhaul or other delivery truckOMOMOrders placedTime/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 truckParts 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 InstructionsDPV create using sketch upPheonix Assembly Methodhttps://docs.google.com/a/opensourceecology.org/document/d/13tM4FTpDOzPgkQuV9bw03VBbvS_qLdpoWE0evrU1zok/editSketch up, google drive has instructionsTemplate created in google driveDPVPLFinished BOM, impending buildDifferent templates or procedures have been used - need one methodDifferent procedures resulted in confusion and difficult to understand instruction because the same DPV who build the machine produced the work instructions - too intuitive for themLucas shows current DPV's
57
Inventory (partial): Parts & support equipDPV go to workshop to verify partsN/AN/AVerbalWorkshop, memeory, recollectionPL, DPVPLPL or ED directs DPV to verify parts onhandTime 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 handinefficient 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 equipDrive to sourceN/AN/ANone, no process in place (point and send)OSE Pick-up TruckPLPLNeed for equipmentEmerging 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 truckWasted time
59
CuttingMeasure, cutCut piecesN/ACut-list on a slip of paperAbrasive cut-off sawsDPVDPVImpending build, equipment on handCurrent DPVs were mindful of making cuts to optimize materials and efficient cutting - no protocol in place to ensure this happens each time; Cheap toolswithout cutting protocol - risk wasting materials and having to make extra cuts
60
Take photosTake photoPictureshttp://opensourceecology.org/wiki/File:LifeTrac_5_Photo1.JPGsmart phone, DM's cameraDM's camera, ability to upload as jpgDPV, PL, ED, DM, TCMDMMindful participants, build phaseNo protocol - so unless someone takes responsiblity there is no documentationmissed 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 lapseFraming, Camera Settings, Setting IntervalometerStill PhotosVerbalOSE Digital SLR & Intervalometer; Adobe PremierDM/DPVDMBuild PhaseNo instructionals for setting up time lapse function on camera, no standrdized practice for camera placementDelay due to camera set up issues, not capturing pertinent content/missing documentation
62
Parts Pickup/DeliveryParts delivered via mail or physically picked up by OSE staffParts requisitionN/AN/AOSE Pick-up Truck, Uhaul or other delivery truckOMOMFinalized BOM/ID'd need for partTime/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 truckParts 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 WarehouseCut and Stack build Parts into modules.All cut parts that will be used in the buildhttp://opensourceecology.org/wiki/File:Warehouse_for_LifeTrac.jpegBuild process step / Work InstructionsFloor SpaceDPVPLCutting in progressCheap chop saws break/burn up Make sure it happens again.
64
Mentally Tracked Lessons LearnedAs problems arose, mentally tracked lessons learnedNone (hopefully captured in log after build)NoneMaybe verbal discussion or logDPV/StaffPLPLProblems during prototypingLessons learned are not captured throughout the process and there is no process for capturing issues post-prototyping. We need standard processNot capturing lessons learned produces poor instructionals and sets us up to make the same mistakes later
65
Workflow DiscussionDiscuss where/how modules will be built to determine pre-placement of parts/tooling; teamingNone (whiteboard may be used)NoneVerbalED/PL/DPVPLPLWork reday to beginDoes not happen every time or the workflow is not followed when work starts, workflow not documented, communicated verbally to participantsRisks miscommunication
66
Divide cut parts by module/assyDivide cut parts by exploded parts diagram according to workflow discussionNoneNoneVerbalPrinted Assembly InstructionsDPVPLCompleted cut listNot always done, no QA process to verify that each module has all of the parts needed for the buildSchedule delays as parts are sorted during build, risk oversight that a part was not cut for a module
67
Install time lapseFraming, Camera Settings, Setting IntervalometerStill PhotosN/AVerbalOSE Digital SLR & Intervalometer; Adobe PremierDM/DPVDMBuild PhaseNo instructionals for setting up time lapse function on camera, no standrdized practice for camera placement - crucial to catch pertinent contentDelay due to camera set up issues, not capturing pertinent content/missing documentation
68
Parts Pickup/DeliveryParts delivered via mail or physically picked up by OSE staffParts requisitionN/AN/AOSE Pick-up Truck, Uhaul or other delivery truckOMOMFinalized BOM/ID'd need for partTime/resources to pick up parts that cannot be delivered via mailParts not accounted for
69
Photos/doc of buildTake photos of key steps during build for documentation purposesStill photos/videoN/AN/AOSE Digital SLR & Intervalometer; personal cameras, Adobe PremierStaff/DPVDMBuild PhaseNot 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 learnedMentally captured/discussionN/AN/AN/APhoto, Wiki, mental notesEveryoneALL HandsSolved problems; Efficient methods developedLessons learned are not captured throughout the process and there is no process for capturing issues post-prototyping. We need standard processNot capturing lessons learned produces poor instructionals and sets us up to make the same mistakes later
71
Hydraulics ReviewReview hydraulics via Google docs products/wiki logs, or handwritten on white board/paperGoogle docs product / handwritten producthttps://docs.google.com/a/opensourceecology.org/drawings/d/1_e_DBEq6RrHMsU_Vrcmx9f1cEZdiv5S5BoCDRcgLj6w/editBuild process step / Work InstructionsInternet, Working Dry Erase MarkersEnd user & EDEDTime for hydraulics/ noneDone out of order.Bottleneck potential
72
Install time lapseFraming, Camera Settings, Setting IntervalometerStill PhotosVerbalOSE Digital SLR & Intervalometer; Adobe PremierDM/DPVDMBuild PhaseNo instructionals for setting up time lapse function on camera, no standrdized practice for camera placement - crucial to catch pertinent contentDelay due to camera set up issues, not capturing pertinent content/missing documentation
73
AssembleAll Hands Final Assembly Final Tested Product (dont have)Build process step / Work InstructionsShop Tools; MaterialALL HandsWarehouse of cut material completedHoles don't line up; Safety; Sometimes clear plan; d/n plan for enough time for a prototype buildoutLack of a process slows down build time; long work days create safety concerns/risk personnel being hurt, liability to OSE
74
Install time lapseFraming, Camera Settings, Setting IntervalometerStill PhotosVerbalOSE Digital SLR & Intervalometer; Adobe PremierDM/DPVDMBuild PhaseNo instructionals for setting up time lapse function on camera, no standrdized practice for camera placement - crucial to catch pertinent contentDelay due to camera set up issues, not capturing pertinent content/missing documentation
75
Safety InspectionVisual inspection of plumbing and mechanical processes; Exit plan; Fire extinguishersFunctional Assembly N/AVerbalTBD / Need ProcessPL/StaffStaff/PLCompleting of build phaseNo 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 functionalityBrief test to insure clearance and Hyd functionalityN/AVerbalPLPL/StaffPL/STAFFCompletion of buildNo 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 ResultsDoesnt Exist beyond hypothetical Doesnt Exist beyond hypothetical N/ADoesnt Exist beyond hypothetical TBD / Need ProcessPL/StaffStaff/PLCompletion of testingNo 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 TestRange of Motion, Check for conflicts, Fix problems (Used once) Not a proceedure Functional Loader ArmsN/APhysical testTBD / Need ProcessPL/StaffStaff/PLCompletion of Test StratNo 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 TestMovement, Limited load test (used once) not a proceedureDoesnt Exist beyond hypothetical N/ADoesnt Exist beyond hypothetical TBD / Need ProcessPL/StaffStaff/PLCompletion 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 AssessmentConduct assessment per guidelinesPrototype Assessmenthttp://opensourceecology.org/wiki/Prototype_AssessmentWikiWikiPL/StaffStaff/PLCompletion of Functional TestingLimited Assessments beyond real world applications. (Not the place to do testing or make assessments); no process to capture the data for re-integration into processThough 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 AssessmentDoesnt Exist beyond hypothetical Doesnt Exist beyond hypothetical N/ADoesnt Exist beyond hypothetical TBD / Need ProcessPL/StaffStaff/PLCompletion of Functional TestingLimited 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 DMUpload via Latakoo (need to check)Still PhotosLatakooDPV/StaffDMBuildphase, end of buildIt doesn't happen all the time; It's an afterthought at this point; Not everyone has a smartphone for using Dozuki AppMissing visual documentation
83
Upload video to DMUploaded via LatakooVideoLatakooDPV/StaffDMThroughout build/end of buildNeed good internet; Only one person documenting entire buildSchedule delay
84
Log video and order transcriptsView and process on Latakoo LatakooDMDMVideo upload complete
85
Prepare outline for video documentationWrite in open source documentDocumentEmail/GoogleDMDMBuild phase
86
Write scriptWrite in open source documentScriptEmail/GoogleDMDMOutline complete
87
Send script & video notes to remote editorsEmail to RE'sEmail/GoogleScriptDMDMScript completeNeed remote editors
88
Edit videoIndividual NLE systems/LatakooVideoLatakooScript, LatakooDM/REDMScript complete, video sent to REsTime consumingAll consuming
89
Submit rough video to team for reviewLatakoo, YouTube, Vimeo uploadVideoLatakooLatakooDMDMEditing complete
90
Revise videoIndividual NLE systems/LatakooVideoLatakooLatakooDM/REDMTeam review complete, feedback received
91
Send video to musicianLatakoo, YouTube, Vimeo upload, Email directionsVideo, Emailed directionsLatakooLatakooDMDMEditing complete
92
Integrate musicLatakooLatakooLatakooMusician/REVideo sent to musician
93
Record narrationSmart phone app and emailAudio FileEmail/GoogleScript, Latakoo, recording device (i.e smart phoneDPV/Staff/REDMMusic integrated
94
Integrate narration, etc to complete videoIndividual NLE systems/LatakooVideoLatakooScript, LatakooDM/REDMRevision complete, musician work complete
95
Upload final videoUpload to Latakoo, Youtube, VimeoVideoLatakoo/YouTube/VimeoDMDMVideo complete
96
Workshop Inventory (tools, supplies, parts, materials)
97
Workshop Layout
98
Tool Control
99
Tool Maintenance and Replacement
100