Slide 1Wireless Sensor NetworksExamples of WSNWSN Examples ContinuedBenefitsMarket HistoryHistory of Dust NetworksMarket SizeValue ChainValue in ServiceOpportunity RecognitionTeam StructureHardware and Protocol StandardsOpen vs. Proprietary SoftwareSlide 15Course ConceptsSukun KimRufus McLainMBA 290 / ENG 298A – Introduction to the MOTWireless Sensor Networks•Motes•SmartMesh Manager•Redundant Network•SmartMesh SoftwareExamples of WSN0 2 4 6 8 10 12 14 16 18-1-0.500.51Low resolution Sensor, Test4, Increasing frequencyTime (sec)Acceleration (g)Vibration ChangesOf Golden Gate BridgeEarthquake MonitoringWSN Examples ContinuedMonitoring enemy in battlefieldMonitoring electricity usage in grocery storeBenefits1. Reduced wiring costs•Cost of wire•Installation cost•Maintenance cost2. Speed of Installation3. Locations where wired sensors are not possibleGo Wireless!!!Market HistoryEric BrewerDavid WagnerShankar SastryDavid CullerCollaborationRob ConantDavid TennenhouseKris PisterHistory of Dust NetworksJuly 2002Jan 2003 Jan 2005Feb 2004 Dec 2004Aug 2004Dust FoundedPister on LeaveSeries A - $7 MillionSeries B - $22 MillionPister Returns to BerkeleySmartMesh ShippedMarket SizeRevenue by IndustryMarket Size in UnitValue ChainSystem integrators creates the largest valueSystem IntegratorNetwork ManufacturerComponent ManufacturerMicrocontrollerRadio ChipDirectly contact customerService & ConsultingSell HW and SWValue in Service•Should Dust shift from a product company to a service company?•Majority of the money is going to be made in system integration and support.•Focus on adoption now and service later.Market PenetrationDevelopment TimelineTechnology PushMarket PullValue CreationValue CaptureValue DeliveryOpportunity Recognition•Killer application of WSN is not yet clear•Like Honda, organize to recognize opportunity, to move quickly and to take advantage of it•Organizational agility - being speedy and adaptive (Pascale)–Need be integrated into entire company culture (not just an independent process)Team Structure•Originally a tiger team •Team structure is limited by the size & resource–Number of Employee is 20~50–R&D employee will be less than 10 (Everyone participates in every project – 3 lines)•Light weight team would work best–Product Manger makes sure tasks get done on time–Accumulate knowledge easily–React quickly to new opportunitiesHardware and Protocol Standards•Architecting system is not very difficult•In the future compatibility will become a serious issue•802.15.4 compliant radio standard hardware•Dust networks is behind its competitors in adopting standards–Even Dust can’t lead standard, it should continue to participate in standardizationVs.•Open source works betterwhen developer = user–PC software: interaction with human, general and diverse needs•Proprietary software works better in WSN–software is used less by other members of community–Embedded software: interaction with machine, narrow and specific needOpen vs. Proprietary Software•Crossbow & Intel–Crossbow get technical assistance from UCB–Everything gets published on the Internet•Dust Networks–Has their own designers and engineers–Proprietary software is a better long-run strategyOpen vs. Proprietary SoftwareCourse ConceptsValue in Services• Future move towards service model Opportunity Recognition• Organizational AgilityTeam Structure• Light-weight TeamsHardware and Protocol Standardization• Continue to adopt standardsOpen vs. Proprietary Software• Proprietary software key for future