In-House Solution Stack Hack How to create perfect-fit custom solutions that transcend quick fix hacks and become truly scalable

Size: px

Start display at page:

Download "In-House Solution Stack Hack How to create perfect-fit custom solutions that transcend quick fix hacks and become truly scalable"

Melissa Brittany Maxwell
6 years ago
Views:

1 Surviving the Marshall DenHartog President DPS Telecom In-House Solution Stack Hack How to create perfect-fit custom solutions that transcend quick fix hacks and become truly scalable 1

2 What is a Solution Stack Hack? Multiple pieces of gear Homebrew integration elements (scripts/cables/power/programming) Only you understand and can support this solution 2

3 In-House Solution Stack Hacks How they originate Why they are important to company performance Why they fail... eventually How to fix the process and maximize the positive impact 3

4 Earlier this year at CommTech East... DPS CEO Bob Berry spoke on this topic: He offered advice for upper management. The audience was mostly system designers and installers. Today, I'll help you no matter what role you play. 4

5 How does a good idea... 5

6 How does a good idea......become a horror story? 6

7 Types of Candidates for In-House Solution Stack Hack: The Big 4 Recurring problems Workarounds & adaptation 7 Repetitive tasks, automation, & test tools Information sharing & logging

8 Key Benefits of In-House Solutions These are solutions designed to impact exactly the biggest local issues hurting your company. Solutions are designed by local subject-matter experts. These designs are totally focused on a positive outcome for the company. The trick is to lock in all these gains while protecting against all the risk points. 8

9 Who initiates the hunt for a solution stack? Technician with an idea to save time or trouble Manager who sees a pattern User Complaint 9

10 Where is it developed? Locally Out of band (invasive...) Iteratively Used and refined over time Most project starts never become final prototypes, but those that do, work! 10

11 Impact Horizons Most opportunity for improvement occurs in 1 site. It usually only organically spreads to a small region. The Impact Horizon is small enough that a single technician & manager can decide to solve a problem. The larger the impact horizon, the more friction to change. 11 Key point: The original plan was built for a small, localized problem.

12 Why would you be leary? Difficult to scale Difficult to maintain Purchase Access (versions cannot be locked in ) Supporting documentation can be lacking Key people can be squandered in a support role Stress can soar. Job roles suddenly spike & change Sudden cleanup costs can be huge 12

13 Business Statistics 68% of IT projects fail 65 and 80% of IT projects fail to meet their objectives, and also run significantly late or cost far more than planned. Portland Business Journal...50% of respondents indicated that their project failed to consistently achieve what they set out to achieve. KPMG New Zealand 13

maintenance. The value is locked in until he leaves or the Stack breaks.

14 If the Solution works, that's when the trouble starts! While deployed to a single site, the Solution Builder can handle the install, turn-up, and maintenance. The value is locked in until he leaves or the Stack breaks. While deployed to a small region, you still have the same story, except now a small Guide is developed to help others to install and setup the solution. 14

15 The trouble starts if......the deployment spreads: Support can become a full-time job for an extended period during roll-out The Setup Guide will need more detail Purchasing & product availability can become increasingly problematic As more people play with the Solution, the number of issues can skyrocket. Off-the-shelf parts chained together can get really tough to keep in sync, leading to skyrocketing support demands. New versions of off-the-shelf parts may not be form, fit, & function compatible. 15

16 So, how do you lock in the gains and protect yourself? 16

7 steps to maximize your benefits 1Document the plan first, then build a demonstration prototype. 2Demo the prototype to all interested parties. Brainstorm to maximize value.

17 7 steps to maximize your benefits 1Document the plan first, then build a demonstration prototype. 2Demo the prototype to all interested parties. Brainstorm to maximize value. 3Implement the new selected features. Don't get stuck. 4Demo the final prototype. Discuss any design deviations. 5Document the project: Keep a full project file Create a user/setup guide Document full vendor part number(s) 6Document all setup screens, 7especially screens that are defaulted 8Create support team 1Keep log of all Q&A and build a FAQ 2Publish FAQ in convenient place 17

18 Documenting everything in the project is key Will the project survive The Bus Test? The project, and the ability to maintain and develop, should survive! 18

19 Scaling Solutions for Roll-Out Maximizing solution value Building product Field trials & technology proofs Installation planning Ongoing support & maintenance 19

20 4 ways to move solution to the field 1.In-House Solution Stack 2.Design in-house & use contract manufacturing 3.Pay NRE on original equipment to create special version 4.Work with an engineering & manufacturing partner who specializes in developing perfect-fit solutions 20

21 But no matter your deployment plan......the key decisions are the same Brainstorm and involve all shareholders Think about the packaging Plan field trials Plan a phased roll-out Create an in-house support plan 21

22 Bit Bucket works for Software & Documentation Store your project in the Cloud Share tools & FAQs to enable self-support Avoid the trap of new maintenance responsibilities (you still have your own job to do) 22

23 Start with a virtual prototype Generate a photo-realistic design: Device package Connectors & cabling LCD, LEDs, & User Interface Power connection 23

Use the virtual prototype to drive brainstorming Get key shareholders together Using a virtual prototype Get people to really imagine the product in use What

24 Use the virtual prototype to drive brainstorming Get key shareholders together Using a virtual prototype Get people to really imagine the product in use What else would add value? How would we hook it up? What are the physical limitations? Connector types? What setup & configuration & test tools will be needed? 24

How would software or firmware be updated? Could things be bumped or damaged?

25 Brainstorm Use brainstorm session outputs to create another virtual prototype Don't forget to talk about Risk How would the unit be replaced? How would software or firmware be updated? Could things be bumped or damaged? What if different sites have different power voltages? Repeat until everybody is satisfied 25

26 Resist Temptation to Commoditize Don't reduce the scope of the solution to make it more like an existing product Don't confuse Cost of Acquisition with Total Cost of Ownership Find a way to estimate the solution's value to the company 26

27 Resist Temptation to throw in everything but the kitchen sink Make the team articulate the value of everything Think about implementation cost only to help eliminate nice to haves Remember extra stuff has a carrying cost: -More documentation -More ways to get it wrong -More support required 27

28 Field Trial Planning Testing solutions in a field-like setting is often overlooked or done superficially. This is a test designed to verify the solution works in the real world. The better the trial, the better the solution. Tougher field trial = Easier roll-out 28

29 Limited and Phased Development Try in a few easy sites let it bake! Try in a high-impact site Limit the initial roll-out to a small number of sites Roll out the rest in phases watch for problems. Update the process & documentation as needed. 29

30 Tech Support Documents & Services Determine whether to use inside or outside technical support services. Either way, you'll need manuals, install guides, and troubleshooting guides. Always have access to an evolving FAQ of problems, questions, & answers. 30

31 Lock-in Availability of Parts Estimate size of the roll-out Estimate years of service needed Estimate additions & maintenance sparing Give great thought to guaranteed parts access: -Buy all units & spares upfront (OR) -Work with vendor to guarantee access 31

32 A good manufacturer is key MFD parts suddenly become in-house solutions A reliable manufacturer pushes end-of-life out forever 32

33 Amateur vs. Pro 33

34 Amateur vs. Pro 34

35 Amateur vs. Pro 35

36 Vertical Integration 36

37 Vertical Integration 37

38 Valve-Control Project 38

39 A single vendor has a big stake The project is large, so vendor can afford to support you. Ex. On a DPS valve-control project, we sent someone to the site to help. Superior to X vendors with 1/X of a stake 39

40 A single vendor makes you look good Gain the prestige of an engineer who delivers a polished solution. Ex. DPS has designed gear to match client's branding. 40

41 Global electronics manufacturers We designed equipment that matched the look and feel of their other components. Product reinforced their brand How would you like to be the engineer in charge of a product like that? 41

42 Multi-Regional Telco Monitoring Device with Fiber Interface Alarm Data 42

43 Automated School Security Dialer 43

44 Any questions or comments? 44

45 Marshall DenHartog President DPS Telecom

Medical Device Product Development for Startups

Medical Device Product Development for Startups - The Bitter Pill AZBIO WEEK / CEI 8/19/2016 ERIC MILLER PADT, INC. Agenda Introduction Medical Device Development Fundamentals The Design Process Manufacturing