Systems Engineering Series WBT

As a provider of scientific, engineering, systems integration and technical services solutions, systems engineering is a core discipline practiced across the company. Most projects involve the close collaboration of systems engineers and non-systems engineers. Because of the complexity of the engineering field, team members that are not systems engineers sometimes are not aware of how their role interacts or intertwines with systems engineering. To address this, the customer wanted a WBT course that introduces non-systems engineers to the systems engineering discipline.

This was an interesting and difficult project. We had little material to start with and basically started from scratch. Our SMEs are longtime experts in the field, having 15-30 years of experience, their world is systems engineering. Getting from them that perfect amount of information that will educate a non engineer and at the same time not put them to sleep or overload them with information was a delicate balancing act. At some point, I felt I could almost be a systems engineer myself. “Almost” This was a project where I was able to see the power of the ADDIE model (analysis, design, development, implementation, evaluation).

Role: Instructional Designer

• Develop high quality, creative WBT courses to meet customer needs and expectations.
• Met with customer to address client needs and ensure customer satisfaction.
• Demonstrate technology capability to broaden customer understanding encourage acceptance.
• Provide various solutions and alternatives to address issues and potential problems with initial training plan as scope of project and customer needs changes.
• Provide and assist customer with long-term implementation process and coordination of duplication and distribution of training materials.

Project Challenges/Issues & Solution

Challenge: Main question, “What to teach, and how much?”

Solution: After careful analysis we decided upon six hourlong WBT modules that covered the major aspects of systems engineering. Each module is standalone and could be taken individually and separately, out of sequence if desired.

Challenge: SMEs are experts that know almost ‘too much’ about everything .

Solution: Using a detailed outline that we developed early in design, worked very closely with SMEs to make sure we are focused and in scope. Subjected drafts to vigorous reviews by peers.

Challenge: With various technology available to use, what is the right combination?

Solution: No two projects are the same, careful analysis of our customer’s needs, our audience and the subject matter allowed us to select the correct combination of tools to use for this project.