Presentation is loading. Please wait.

Presentation is loading. Please wait.

Industrial Technologist’s Toolkit For Technical Management (ITTTM) Process Overview: Orientation Tutorial Presentation 3 1. Explanation of this presentation,

Similar presentations


Presentation on theme: "Industrial Technologist’s Toolkit For Technical Management (ITTTM) Process Overview: Orientation Tutorial Presentation 3 1. Explanation of this presentation,"— Presentation transcript:

1 Industrial Technologist’s Toolkit For Technical Management (ITTTM) Process Overview: Orientation Tutorial Presentation 3 1. Explanation of this presentation, context 2. RCA courseware process structure 3. SDA courseware process structure 4. Review, broader ITTTM relationships Dr. John W. Sinn, Professor, Bowling Green State University jwsinn@bgnet.bgsu.edu, www.bgsu.edu/colleges/technology/qs

2 Explanation Of This Presentation, Context This is the third of four related presentations used to help you understand and use ITTTM courseware. The four ITTTM orientation tutorials can help you see relationships in core knowledge and technical management as part of ITTTM. The four related presentations are: 1. ITTTM Introduction, Overview 2. ITTTM Content Overview 3. ITTTM Process Overview 4. ITTTM Assessment Overview

3 Documentation Tools, Lean Data Tools, Six Sigma Service, Tools Manufacturing, Non-Manufacturing Synchronous Tools, New Product Development Applied Research, Project Team Cultural Change, Industrial And Academic Core Values Quality Management System Product Realization Measurement Analysis Improvement Resource Management Analysis, Global Views, Values Integration, Pragmatic Field Information Disciplined Knowledge, Research And Development Interaction, Problem Solving, Decision Making Communication, Internal, External, E-commerce Management Responsibility ISO Total Quality, Baldridge Leadership Context, Continuous Improvement Professional Outputs Primer Inputs Model System: Industrial Technologists’ Toolkit For Technical Management (ITTTM) Explanation Of This Presentation, Context

4 Six sets define core, overview 42 tool courseware system:  Primer Tools  Cultural Tools  Data Tools  Documentation Tools  Service Tools  Synchronous Tools  A tool set is about a course, can be entire text, or support  Online flexibility, e-commerce, strong communication  Digital, MS Word, CD format, based on Office Suite Current presentation is on systems for delivery, processes Explanation Of This Presentation, Context

5 Tools, as courseware, conclude with applications:  Applications synthesize tool content, project reflection  Focus, team communication, management, improvement  Work done in “tables” compiled individually, team  Table format to collect, compile data and documentation  Iterative improvement, courseware assessment structure  Portfolio emerging as assessed collection, best practices  Portfolio accumulatively built as multiple tools, phased  Courseware RCA, SDA structures knowledge, portfolio Six tools in a course, tool set, apply and grow knowledge Explanation Of This Presentation, Context

6 1. Team Does Startup, Identifies Project 2. All Do Tool Work Individually, Coordinated 3. Team Work Posted, Blackboard, Assessed 4. Chat Based On Feedback Assessment, Reviews 5. Do Next Tool, Repeat Cycle For Six Tools Total 6. Phase I, II, Synthesize 3 Tools In Portfolio Portfolio development, assessment, six tools……… startup is where the process begins, start of course Explanation Of This Presentation, Context

7 SDA’s and RCA’s have several features, many in common:  Both allow interaction, teams grow portfolio, knowledge  Both facilitate individual responses by each researcher  What and when each researcher contributed, documented  Both compiled by team member as grand form in portfolio  Both guide, have multiple areas to be filled in, detailed  Both require analysis, reflection, writing by all to improve  RCA’s recycled, SDA’s focus tool progress RCA’s and SDA’s are the heart of the courseware……… RCA Courseware Process Structure

8 1. Regular Critique Assessment (RCA’s) 2. RCA’s Are Built On, Grown With Each Tool 3. Grow Knowledge, Assess Work In RCA’s 4. Analyze, Synthesize, Information, Apply Project 5. Raise Questions, Assess Own Project 6. RCA’s Improve, Format As Portfolio Each tool has Regular Critique Assessment (RCA)…… Four are done in each tool to assess progress of team. RCA Courseware Process Structure

9 Four RCA’s assess team progress, grow knowledge:  Portfolio Presentation Documentation Planning Organization Assessment (PPDPOA). A portfolio plan, team roadmap.  Required Reading Analysis Assessment (RRAA). A tool summary, like a traditional lecture, but written content.  Information Research Abstract, Bibliography, Citation Assessment (IRABCA). Team researches external sources.  Team Portfolio Presentation Management Assessment (TPPMA). Internal, external reviews by and of team. Each of these are explained, detailed in the next five slides RCA Courseware Process Structure

10 General team information, all research, one compiles all These important diagrams help communicate various technical features of the project All agree to assignments, each line reflecting persons’ work Compiler reflects on all information, work by all, summarizes RCA-Portfolio Presentation Documentation Planning Organization Assessment (PPDPOA) General Use/Application: PPDPOA enables organization and planning responsibilities for completion of work assignments for the team, including context of project completion. All issues are addressed by one or two persons but all are engaged via information and relationships for improvement in documentation forms provided. This is one of the first forms to be placed in the entire presentation with each toolkit, and all else should be organized from this. When completed, each researcher should be listed on the left, showing critical portfolio assessments they were assigned to do, including others’ work they helped review ahead of submission, for improvement, and when all was due for compilation and completion. Compilers also develop a synthesized abstract of team focus, over time, based on inputs contributed by each person on the team. This will evolve and improve based on feedback from persons internal and external to the team. Phase:Tool:Date:Researcher:Compiler (s), Suggested To Be Team Leader Up To Mid Term, Minimum: Team: ResearcherSDA’s (Team Selects)RCA’s (All Do All) SDA, RCA’s Due Dates Other Work ReviewedOther Due Date Compile, Post Portfolio Researcher 1.Sub-team, Compilers Assigned Compilers Assigned Note, these may vary All Review Others’ Work, Assigned Reviewed Others’ Due All Compiled Work Due Collect From All, Compile Abstract And Synthesis Of Key Project Focus And Objectives: Diagram 1: Project Organizational Chart For Team Diagram 2: Technical Flow Chart Of Process/System Being Assessed Diagram 3: Technical Layout Of Process/System Being Assessed ResearcherProject Focus, Input As Objective (s), Problem Statement, etc.: Relationship, Value Added, To ISO Elements Emerging, Specifically Described/Explained: Assessment Question, Pros And Cons, For Required Or Regular Team Chats: Researcher 1.1. Collect From All, Compile Compiler Portfolio Reflections, Summary Of Technical Work, Assessment, Based On Individual Researcher Inputs: Compiler Reflections To Help Improve Quality Of Work In Portfolio Based On All Individual Researcher Inputs: This provides general project information RCA Courseware Process Structure

11 RCA-Required Reading Analysis Assessment (RRAA) General Use/Application: RRAA enables a summary and synthesis of each toolkit lecture, demonstrated as key information and relationships. One or more persons compile the actual RRAA, but all must read the lecture and contribute to the individual “main technological concepts” portion of the RRAA form. Each researcher should provide assessment questions for required chats. Phase:Tool:Date:Researcher:Compiler (s) :Team: Information Source (Tool) In Bibliographic Form: Abstract And Synthesis Of Key Information (usually approximately 300-400 words) completed by compiler (s) based on submissions by all on team as well as their own review of the tool content: ResearcherMain Technological Concept:Relationship, Value Added, To Project/Technology: Assessment Question, Pros And Cons, For Required Instructor Chat: Researcher 11. Collect From All, Compile Compiler Portfolio Reflections, Summary Of Technical Work, Assessment, Based On Individual Researcher Inputs: Compiler Reflections To Help Improve Quality Of Work In Portfolio Based On All Individual Researcher Inputs: This is general team information, all research, one compiles all Compiler summarizes tool information, abstract Based on input by all All on team write about tool content, each line reflecting persons’ views, project concepts/relationships, value added to solve problems and provide solutions, improvements, questions to address in chat, etc. Compiler reflects on all information, work by all, summarize team views RCA Courseware Process Structure

12 This is general team information, all research, one compiles all Compiler organizes all abstracted information, in collective “grand” form All write about their article researched, reflecting technical details and analytical views, project relationships, value added to solve problems, provide solutions, improvements, SDA’s connected to, and how, etc. Compiler reflects on all information, work by all, summarize team views RCA-Information Research, Abstract, Bibliography, Citation Assessment (IRABCA) General Use/Application: IRABCA is a summary and synthesis of each toolkit information source researched and used, demonstrated as key information and relationships to project and toolkit key points. All persons research and develop one IRABCA, but all must be familiar with the total body of knowledge, based in the RRAA. Compiler (s) take all individual researched IRABCA’s and place into a “grand form” for portfolio submission with each tool portfolio or phase portfolio presentation. The IRABCA should be completed interactively and iteratively with SDA’s to enable relationships to emerge and be built as value- adding knowledge in the team project and portfolio. These relationships and connections will be directly detailed to show citation locations and broader relationships, by design. Phase:Tool:Date:Researcher:Compiler (s):Team: Abstract Of Key Information (usually approximately 300-500 words—each tool submission requires one for each team member) : ResearcherBibliographic Source: Author; How To Access; How/Who, Published; Type Source, etc.: Why Is This Source Relevant; How Does It Add Value (Reflections By Researcher)? SDA’s Connected: Researcher 11. Collect From All, Compile Compiler Portfolio Reflections, Summary Of Technical Work, Assessment, Based On Individual Researcher Inputs: Compiler Reflections To Help Improve Quality Of Work In Portfolio Based On All Individual Researcher Inputs: RCA Courseware Process Structure

13 This is general team information, all research, one compiles all Compiler organizes all information, in “grand” form All write views, reflecting technical details and analytical project issues, value added to solve problems, provide solutions, improvements, etc. Compiler reflects on all information, work by all, summarize team views RCA-Team Portfolio Presentation Management Assessment (TPPMA) General Use/Application: TPPMA enables improving team portfolio presentation, ongoing. Each presentation all do one or more assessment elements, and recommend improvement actions, as well as internal and external matrices for numerical analysis. When totally compiled based on inputs and tables from all on team, there should be at least one assessment element for improvement form from each person which assesses all others on their team, and one form showing all teams’ numerical ratings from each person (internal and external reviews). Total team average will compute automatically if used properly. One or more person (s) compiles all contributions, on a rotating basis, as a regular critique or phase portfolio. When completed, each researcher should be listed on the left, detailing assessment elements needing improved, recommendations for improvement, and other professional inputs, as reflections by all. Compilers develop reflections synthesized over time, based on inputs contributed by each person, and their own review, reflections of team’s work. Phase:Tool:Date:Researcher:Compiler (s):Team: Researcher:Portfolio Presentation Management And Organization Assessment Element Needing Improved, Why? Recommended Improvement Actions: Other Information: Researcher 11. Collect From All, Compile Compiler Portfolio Reflections, Summary Of Technical Work, Assessment, Based On Individual Researcher Inputs: Compiler Reflections To Help Improve Quality Of Work In Portfolio Based On All Individual Researcher Inputs: RCA Courseware Process Structure

14 Team names for internal assessment. External uses other teams’ names Compiler organizes excel rating forms, in TPPMA collective “grand” form All researchers rate others on separate excel forms and post individual TPPMA RCA work Various characteristics are described to help assess each persons’ work in the TPPMA RCA Courseware Process Structure

15 1. Standard Dedicated Audit (SDA’s) 2. SDA’s Are Targeted To Each Tool Content 3. Grow Knowledge, Assess Areas Specifically 4. Analyze, Synthesize, Information, Apply Project 5. Raise Questions, Assess Own Project 6. SDA’s Assess Project, Do Portfolio Second tool form, Standard Dedicated Audit (SDA)…… focused specifically on content in each tool…….. SDA Courseware Process Structure

16 SDA’s follow RCA’s, evolving courseware project features which underscore technical management of projects:  SDA’s focus on content in specific tool rather than process  Work posted by each is one content analysis, interpretation  Teams go back at phase review, enhance, change, SDA  Each individual analysis posted, grows project, portfolio  All work compiled in portfolio shows many analyses  SDA content areas researched, detailed, “do” the project  RCA IRABCA, RRAA’s tied to SDA’s, pre-designed  SDA’s raise questions, assess content-project relationships SDA’s are the application of courseware content……… SDA Courseware Process Structure

17 SDA’s, and broader ITTTM courseware, facilitate team project with technical management content applied:  SDA’s focus on content in ways unique to each tool  Each SDA is unique technical format, infrastructure  Two required SDA’s, two selected by team for project  SDA format grows quality management system QMS)  SDA’s require team analysis, management via PPDPOA  SDA content areas researched, detailed, “do” the project  SDA questions assess ISO/QS 9000 project relationships SDA’s are technical management principles applied……… SDA Courseware Process Structure

18 Review, Broader ITTTM Relationships This was the third of four presentations to help understand, use ITTTM courseware. The four presentations in the ITTTM Orientation Tutorial folder include: 1.ITTTM Introduction, Overview 2.ITTTM Content Overview 3. ITTTM Process Overview 4. ITTTM Assessment Overview After viewing these, best in order, you can review or use the courseware provided in the ITTTM 42 Tools folder. Give feedback by using forms in the ITTTM Research Folder. Contact the author at jwsinn@bgnet.bgsu.edu


Download ppt "Industrial Technologist’s Toolkit For Technical Management (ITTTM) Process Overview: Orientation Tutorial Presentation 3 1. Explanation of this presentation,"

Similar presentations


Ads by Google