# MBARI Offsite ## Day 3: Engineering Offsite # ## Wed Mar 23, 2005 structure of strategic council - pull roadmaps together - structure, composition, responsibilities proposal process - what to do before, during after proposal process - evaluating opportunites: economics and sci impact culture - cruise participation - lab leads - oceanography 101 - what are we asking engrs to do? are they all the same? - internal day of sci,tech,ops - too many projects - investing time in research for tech push, keeping current w/ sci/tech trends -------------- Need a strategic council pull together groups and roadmaps across dept composition responsibility authority interfaces Organizational Process Standards Design for tech transfer Evaluation of opportunities Culture DOSTO Cruise Participation Lab Leads Oceanography 101 What we're asking engrs to do: are they the same Too many projects? how to maximize impact What else Platforms Instruments, Software and Data Systems Dept Mix we can trade engr for 2 techs Systems Engineering Where does it occur Should we have a group Proposal Process and reorg What's different What has already changed Leaders should lead and make direct the staff What else from Support Engr? What else from Group? [edgington, mcgill, headley] Group Presentation Recap [support engineering] machine shop, model shop, m techs, e techs Charter: engineering services for science and operations work primarily on deployed systems small scale, short term pjts Sustaining Engr on mature systems Transition systems to ops Scheduling work: -talk to person 1st -see group lead if you don't know who -if person says no, see gp lead -please have correct charge number -try to meet all request -resource conflicts go to PCO -engrs limited time on core pjts -external pjts: on case by case basis * Not a way to get more engineering time Why so busy? data stream support ship support rov, auv mooring science project infrastructure: microwave, data systems (software tools), engr tools mgmt core projects: siam, mmc, ssds, puck consortium Issues: -Ships schedules or ops schedule drives priority -Customers (esp science) feel guilty requesting our help -Other issues? --test platforms, simulators to do testing off line (esp ship systems) --develop test, maintenance plans and tools during projects are there version control issues with that? there were test systems for tiburon, now deployed as spares real time development done on HPUX 10...need engr resources [todd] Technical Support Group - IPC (milspec) certified techs/inspectors - doc generator - EM assy w/ SMT - Systems integration and test to component level Tom Marion: electronics, em assy, prototyping, systems IT, IPC cert Jose Rosal: pcb layout, orcad admin Dick Littlefield: drafting, pcb...philosophy, IPC cert Todd: IPC cert Misconception: support techs are not allocated on proposals Facts: they are there, when needed, as long as needed. No job too small. Getting Work Done: -Contact thrust area person -Must have project charge number -PCO resolves conflicts OrCAD CIS data base (Jose working on upgrading library) new categorization based on digikey parts lab stock and project storage: lots of SMT, unique parts now Instrument Calibration: littlefield working on formalized cal program. ESD Control: littlefield, [Brown] Machine Shop Scope of Services Support Customers - engr, sci, ops Mech Mfg - test and measurement - Drafting, mech design - machine and fab services - Engineering services Points of Contact: -Dean Martinez: DMO/Science -John Peters: aerospace,CAM -Ray Thompson: Instrumentation, medical, industrial, semicond -John Ferriera: Platforms/Science, aero, military -Mike Parker: Semicond, military -Jim Scholfield: aero, military Vertical integration: POCs get involved in projects in review stages of projects Best Practices: - Workflow: current methodology -Allocated vs unallocated resources *they are very busy *communicate needs early to machine shop -Outside services * case by case basis (too big, too busy, high volume) * brown writes PO against project, then later transfers funds back to project * operations, deployments have priority - Documentation Project Library * Machine shop works from project library; it's the place for official docs Auto part numbering tool from Hawk Ridge Systems Technology Focus: - liquid tooling, mold making technology - plastic injection molding (lo pressure) - rapid prototyping - alternative joining processes, welding processes - spring technology (Larry's Ti springs, lathe method) *? Are documentation standards higher for external projects * Yes, paper napkin sketch can be done inside, but not outside [kirkwood] Engineering Issues Should we address MOOS issue? (MOOS uses too many resources, and it's engineering's fault) Strategic Council: responsibility/authority incl science reps too many projects, context switching when to terminate projects conflict of interest[davis] [everyone] yada yada yada Action Items: -------------- - Define charter for each group council [group leads] -- mission statement - Define a functioning charter and interface for SC [Gomes] - Who comprises the members? (Define group composition, membership qualifications) [group leads] -- gp leads nominate members -- term length - Send out notes distilled [bellingham, kirkwood] - Jim and Bill attend members to council [bellingham, kirkwood] -- preview SC concepts to science - Marcia to invite science SC members (as with other committees) [jim] - Work with haddock to arrange DOEST [radochonski] - Collect presentations in project library [hanrahan, presenters] - Oceanography 101 finalize arrangements [bellingham, mellinger] - Determine admin and communication function placement [group councils] -- Where to put 'red' and 'blue' statements (what body is responsible for these) - Presentation of high level state of art technology for instr, sds