* Complex Systems Design / Independent Consultant
* Enterprise Wisdom Management / Sun Microsystems
* Graduate Instructor / University of Phoenix
* Research & Development / Lawrence Berkeley National Laboratory
* Reactor Plant Operator / Submarines, U.S. Navy
Systems Modeling, Nuclear, and Astrodynamics
A brief Case Study providing context to the management responsibilities described below can be found at:Sun Microsystems Recognizes a Problem and an Opportunity
Co-managed the design, development, and implementation of Sun's WM System, to include:
[1a] the ontology, taxonomy, vocabulary, and semantic model that promote semantic-content capture, rationalization, and dissemination of enterprise wisdom;
[1b] testing of the WM System's backend, which involved testing of policies and processes for managing semantic content, editing, maintenance, reuse, semantic restructuring, content-searching, versioning, and end-of-life archiving; and
[1c] managed several teams of subject-matter-experts and knowledge-consultants for conversion of 20 information-technology (IT) services from hardcopy and tacit knowledge into an efficient wisdom base for use by Sun sales representatives globally.Developing the WM System involved deconstructing key service documents into layers of data, information, and knowledge, and then atomizing each of those layers into reusable and sharable components down to individual sentences. Similar semantic content was compared and rationalized to create the best content among alternatives. Sun sales representatives from around the world reviewed and submitted localized semantic content for incorporation into the WM System.
[1d] RESULTS. The WM System eliminated massive redundancy and inconsistency, while providing global sales representatives the best content from around the world. The WM System dynamically generates customized service documents that include legal documents like statements of work; market-scope documents like service definition and proposal documents; service work plans like detailed implementation instructions; resource requirements like software, hardware, and the human resources required to implement the services; and test procedures and plans. The WM System also delivers supporting native static documents that include build templates, runbooks, customer presentations, workflow diagrams, and more.
[2a] Enterprise Security Services. Managed development and rollout of Sun's new enterprise security services that included Security Policy Workshop, Security Policy Development, Security Hardening, Firewall-DMZ Assessment, and Enterprise Security Assessment.
[2b] Business Continuity Services. Managed development of Sun's new enterprise business-continuity services that included Readiness Assessment, Risk Assessment, Business Impact Analysis, Strategy Solution and Architecture, Policy Development, Implementation, Auditing, and Program Management.
[2c] Expanded the WM System. Coordinated efforts between numerous managers, knowledge engineers, knowledge consultants, subject matter experts, field sales representatives, engagement and practice managers for development of service methodology and for adding new domain knowledge to the WM System.
[2d] Training Materials. Coordinated the creation of training materials designed to bring new users up to speed on the semantic model, capabilities, and application of the WM System.
[2e] Usage and Quality Measures system. Developed GUI-based satisfaction and quality questionnaires. Solicited frank feedback through anonymous online forms. Tracked and evaluated global methodology, head counts, resources, budget, matrixed personnel, and service methodology development work being done in the United States, England, Germany, and Italy.
[2f] RESULTS. The WM System required 1.5 years to develop, test, trial, and commission for use in the North Americas, Italy, Germany, and Britain. All sales regions globally were notified of the existence of the WM System and many sales representatives worldwide began using it. Before the WM System, it took Sun 2 years to create a patchwork of 20 IT infrastructure services. But by only 6 months after commissioning the WM System, the former 20 services had been updated and integrated with another 40 new services for a broad portfolio of more than 60 customizable IT infrastructure services. More importantly, sales representatives could sit down with the customer and use the WM System to create customized solutions with all of the required methodologies (legal, pricing, installation, management, and other documents) in hours rather than the 1-to-3 weeks that was usual without the WM System. The WM System also provides for more complete and up-to-date methodology that contains the best expertise captured from across the globe.
Initiated and drove development of the Knowledge Management Group's intellectual-property-capture program to identify business-process patentability for protection of Sun's IT service offerings. Obtained buy-in from executive management, legal, and the Knowledge Management Group. Initiated the Global Patent Council and the Draft-IP review process. Worked closely with Sun's legal department to assure robust procedures for assessing candidate IP for protection. Developed the patentability-criteria procedure. Developed the intellectual-property-capture training program. Developed an intellectual-property submission and tracking website to minimize the administrative burden on personnel.
(1a) common problems when managing teams of programmers from across the globe, having different cultures, values, time zones, languages, and local technology;
(1b) a survey of programming languages and programming environments as they apply to real-world business and technical applications paying special attention to JAVA, C++, and Visual Basic;
(1c) an understanding of the roles of HTML, XML, RDF, KRLs and their schema languages in the construction of modern and future intelligent web portals;
(1d) an understanding of how HTML, XML, RDF, and KRLs process data, information, knowledge, and wisdom;
(1e) the importance of managing stakeholder expectations to include frequent mockups and functional builds to garner early and continuous buy-in and design participation by stakeholders;
(1f) the careful introduction of a new or replacement software product, to include stress and crash testing of new software modules and integrated product, and the operation of a parallel beta site prior to replacing the older product; and
(1g) principles of good communication among team members and stakeholders. Words, and the personal meanings that each person attaches to those words, can be calibrated across the team fairly easy, but if the personal values of individual team members differ significantly, then interpersonal conflict is likely to cause intractable difficulties.
(1h) MODEL TRUTH. Of particular importance to me is the issue of "model quality and realism". Engineering and software quality assurance give confidence that a software model works to specification, but what standards and methodology give us confidence that our model represents reality? To this end the importance of the following concepts were stressed and exhibited:* the importance of building conservation-of-dimensionality into the parameters and dependent variables of the models (a step beyond object typing), and * the importance of driving the software model to the boundary conditions (the place in domain space where a faulty model is most likely to collapse).
Management & Business Lectures
Radiation Detection, Radionuclides, and Nuclear Waste Management
Quality Assurance Plans & Procedures
[1a] Operated pressurized-water nuclear reactors during multiple submarine deployments; during serious casualty conditions that included reactor scrams, partial loss of the power plant, single-loop operation and other unusual power-plant lineups; during flooding and fires; and performed many emergency fast recovery startups.
[1b] Served as the Reactor Operator for two Reactor Safeguard Exams.
[1c] Operated and maintained all reactor instrumentation and control equipment; completed numerous work packages and maintenance tagout packages; acted as the Calibration Lead for reactor-control instrumentation; and was responsible for Reactor Quarterly Data reports.
[1d] Performed numerous primary instrumentation repairs while at sea and at power. Meritoriously cited for troubleshooting and repair of faulty rod position indication while at sea and at power. Meritoriously cited for troubleshooting and repair of steam generator water level control problems while at sea and at power.
[1e] Supervised, trained, mentored, and evaluated Reactor Controls Division personnel. Meritoriously cited for efforts to qualify 8 personnel in various watch stations in one year in the Reactor Controls Division.
* reactor primary shield removal;
* neutron detector replacement;
* ion-exchange resin blowdown;
* primary coolant blowdown;
* reactor core defueling; and
* numerous system tagouts and work packages.
* Engineering Watch Supervisor;
* Radiation Control Point Entry;
* Electronics Technician, Nuclear Field Class A1;
* Subsafe and Nuclear QA;
* Submarine Dolphins; and
* Shutdown Reactor Operator.