Presentation is loading. Please wait.

Presentation is loading. Please wait.

CSEP Preparation Program

Similar presentations

Presentation on theme: "CSEP Preparation Program"— Presentation transcript:

1 CSEP Preparation Program
Certification for Systems Engineering Professionals Overview

2 What is Certification? Certification is a formal process whereby a community of performing, skilled representatives, such as INCOSE, warrant that a person has achieved competency in certain skills. Licenses are permissions granted by a government entity for a person to practice within its regulatory boundaries. Certification also differs from a certificate that documents the successful completion of a training or education program. Notes: Explain what certification is and how it is different from licensing and certificate programs. The objective for the INCOSE Professional Certification Program is to provide a formal method for recognizing the knowledge and experience of systems engineers

3 INCOSE CSEP Background
Systems Engineering Certification 2001 – Survey of need for and interest in SE Certification 2002 – Exam created 2003 – Beta test (300 questions, 167 retained) 2004 – First 50 people certified as CSEP 2005 – CSEP program open for public enrollment Notes: Continue INCOSE overview. Distribute Handout 1-1 at end of this slide. Inform the students that INCOSE would like to receive information from them about certification. Ask them to answer the questions during the day and return the handout to you when it is complete.

4 CSEP Designation What is the designation for a Certified Systems Engineering Professional? CSEP For example on a business card John Doe CSEP, PMP . . Jane Doe CSEP, PMP, PE . . . What Organization certifies me as a CSEP? International Council on Systems Engineering (INCOSE) What proof will be given to me that I am a CSEP? Wallet Card, Certificate, and Lapel Pin INCOSE Certification Letter INCOSE Database Notes: When candidates becomes certified, What their designation will be What organization certifies them What proof will there be that they are Certified Systems Engineers

5 Fun CSEP Facts: What are these numbers?
84 Number of CSEPS 50 Number of CSEPS – Pilot Program 34 Number of CSEPS – Post Pilot 40% Percent through CSM Prep Program 45 In the pipeline Numbers are approximate as of end of June, 2006

6 Requirements for Certified Systems Engineering Professional (CSEP)*
SE Experience - 5 years minimum in multiple SE disciplines Education – Bachelor’s degree/equivalent in technical field (Additional experience must be substituted for non-technical degree) 5 more years of engineering for non-technical Bachelor’s (total 10 years) 10 more years of engineering if no Bachelor’s degree (total 15 years) Recommendations from at least 3 Colleagues/Peers/Managers who are knowledgeable in Systems Engineering Certification Exam * Application and Fee Submittals Required Application requires copy of degree transcript or diploma Application fee is $400 – discounted to $300 for INCOSE members Test fee is $80 payable to Testing organization at time of exam. Explain this chart slowly. Emphasize minimum 5 years of SE Experience. Explain degree variation effect on experience requirement. Point out reference details. On the application submittal, remind them that they must submit a COPY of their degree, transcript, or diploma. They can scan these in to electronic form for submittal. Warn them not to submit an actual diploma because we will not send it back. Note INCOSE cost advantage, and test payment is made at time of test. Be sure to emphasize INCOSE membership is not a requirement. INCOSE membership not required to participate in program

7 What are the criteria for earning Systems Engineering Certification?
1. Applicant’s education Determines the extent of required experience Supported by copies of college transcripts or degrees 2. Applicant’s verifiable experience At least five years of experience in systems engineering (technical degree) Additional 5 years engineering experience if non-technical degree Additional 10 years engineering experience if no degree 3. Applicant’s advocates At least three references are to be selected by the applicant References must know and understand Systems Engineering References must provide written endorsement verifying applicant’s systems engineering skills and experience 4. Successful completion of an exam based on: INCOSE Handbook Version 2a, and ISO Systems Engineering — System Life Cycle Processes Notes: Explain that the basis of Systems Engineering Certification is Verifiable education Verifiable experience Acknowledgement by 3 Advocates (who understand Systems Engineering) of the candidates Systems Engineering Experience Passing an exam that is based on the INCOSE Handbook version 2a and ISO 15288

8 CSEP Exam Information The CSEP Exam is based on current INCOSE SE Handbook Version 2A which is available on INCOSE’s web site. Exam cost is $80 per exam Consists of 120 questions 2 hours in length Pass/Fail results provided immediately upon exam completion Candidates eligible for two re-tests within the year SE Handbook version 3 released in 2006. Certification is good for 3 years Explain this chart slowly. Be sure to mention the SE Handbook is downloadable free to INCOSE members. Also explain each candidate can take the exam up to three time in order to pass, however they must be at least 3 months apart, and all 3 exams must be taken within the maximum 1 year application/certification process. The applicant must also pay for each exam at the time it is taken. Also note as the INCOSE SE Handbook is updated, the exam will be updated to match its contents.

9 Current Certification Process
Application Development 1. Verifiable Education 2. Verifiable Experience 3. Applicant’s Advocates (three references knowledgeable about SE) Take Cert Exam (Prometrics Test Center) Pay test fee INCOSE Application Center Evaluation $ Completed And Fee Notify Applicant Two weeks ISO 15288 INCOSE SE Handbook Version 2a Study Pass 3 year Certification Notes: Walk the Class through the certification process – This chart is animated – Bring one group at a time and talk to that group Group 1 - Application Development Documented Systems Engineering experience Applicants Education Applicants Advocates recommendation Payment to INCOSE Group 2 INCOSE review of the Application and applicant notification Application approval – Application disapproval What if the application is not accepted? – There is an appeal process! The applicant will be notified as to what areas need additional information, proof or may result in finding additional advocates. Group 3 Studying for the exam when application is approved Group 4 Appointment with the Prometrics test centers and setting for the exam Notification will be immediate Group 5 INCOSE will send the successful candidate their certificate and card – good for 3 years Group 6 Once the candidate has been awarded CSEP status – they must start accumulating PDUs for certification renewal. Group 7 Show that areas that this course will provide assistance Application Support Certification Exam support Also discuss the appeals process Four to six weeks Applicant’s own pace Applicant has up to one year to pass the test (three tries 3 months apart). Test is scheduled directly with Thompson-Prometrics. Timeline

10 Continuing Education Credits for Certification Renewal
INCOSE requires 120 PDUs during the three-year certification period Education Activity Credit 1 College or unit semester hour 45 PDU 1 College or unit quarter hour  30 PDU 1 Continuing Education Unit (CEU) 10 PDU 1 Professional Development Hour (PDH) 1 PDU 1 hour of teaching of professional development coursework. Teaching credit is awarded for teaching a course/seminar for the first time only. Not applicable to full-time faculty. 2 PDU Authoring published papers, articles or books in any area relevant to practice 1 hour of participation in professional and technical society working groups/management Patents                                                        1 hour of professional development in coursework, seminars, or professional or technical presentation made at meetings, conventions, conferences, or exam preparation Highlight that this is the current draft of the PDU table. The final breakout may be different as the differences between “American” and “Global” education requirements are considered, and evaluated. Point out this is a three year requirement, and that as many as 30 PDUs may be carried forward.

11 The Opportunity INCOSE has an opportunity to advance the industry, increase memberships and create broad visibility through its certification program Based on the success experienced from PMI’s PMP certification program, CSEP can drive the same success for INCOSE, and our industry Qualify the value proposition for the industry We get to invent a NEW acronym! CSEP Based on market indicators, CSM is highly optimistic on the success of the CSEP program Based on proven programs (PMI/PMP Certification) Vertical view of CSM customers and forecasted growth over the next 4 years Forecasted employment growth in Engineering disciplines, primarily Systems Engineering The Bureau of Labor & Statistics (May 18, 2004), forecasts employment growth in the systems design and related service industry to be one of the fastest growing occupations thru 2012.

12 CSEP Potential Impact PMP Experience INCOSE Opportunity*
*Based on CSM’s projected forecast Slide shows PMI’s success over the past 11 years, dating back to 1994. Early success was limited due to gating factors: volunteer staffing, long application review cycles, limited advertising, lack of proven value propositions Recent success based on: Full-time employees Reduced application approval times <11 days Word of mouth advertising Value propositions (business now require PMP certification) Based on historical data provided by PMI, the number of PMP’s today exceeds more than 116,000 or 78% of total members. CSM’s CSEP forecast using current market indicators suggests similar success!

13 Market Analysis (C.A.G.R.)
Market Trends Market Analysis Market Analysis (C.A.G.R.) $Billions A vertical view of CSM’s client base shows strong compounded annual growth rates (C.A.G.R.) with the largest coming from the aerospace manufacturing industry.

14 Concentration of CSEP’s (as of 6/05/06)

15 Discussion of the CSEP Application
Notes: Distribute Exercise 2-1—CSEP Application Form The forms will be used throughout the rest of the day

16 CSEP Application – SE Experience
Section 5: Experience Use additional pages as needed. Describe at least five years of systems engineering experience performing tasks defined in Appendix A of the INCOSE application instructions (next chart). Under “Your Duties and Responsibilities” include the depth of detail typically provided on a job resume about the SE tasks/functions you performed. If you do not have a technical degree, describe your additional years of engineering experience required to qualify for certification. Reverse chronological order is preferred. Use the checklist at the end of this section as a summary of your SE experience. Notes: Tell participants that this section is not as simple and straightforward as it appears. Briefly describe what is expected by INCOSE.

17 Experience Summary Table
Systems Engineering areas of work - See Application Instructions for Detailed Definitions Total Months of Experience 1. Technical Planning 2. Requirements Engineering 3. Baseline Control 4. Technical Effort Assessment 5. Design Development 6. Qualification, Verification, and Validation 7. Process Definition 8. Tool Support 9. Training 10. Systems Integration 11. Risk and Opportunity Management 12. Quality Assurance 13. Specialty Engineering 14. Other Notes: INCOSE reviewers aren’t just looking for systems engineering experience. They want to see experience in these experience areas. Emphasize that it is important for them to present their experience in these category areas and to use some specific language that will be presented shortly

18 Depth and Breadth of Experience and Education
Distribution of Experience in the Systems Engineering Areas Amount of SE Experience Required Maximum Depth Breadth Intermediate 5 years with Bachelor’s degree, or equivalent, in technical field 3 years in any 1 area and 2 years in other areas 1 year in each of 3 areas and 2 years in other areas Any combination between maximum depth and maximum width Note: Additional engineering experience must be substituted if you are lacking a technical Bachelor’s degree or equivalent: A minimum of 5 additional years of engineering experience with Bachelor’s degree or equivalent in a non-technical field (total minimum of 10 years) A minimum of 10 additional years of engineering experience with no degree (total minimum of 15 years) Notes: This chart illustrates the breadth and depth of experience that is required for certification – Walk through this chart. Note that if the applicant does not have a technical degree, additional engineering experience (not necessarily in systems engineering) is required. As noted in the chart, For a non-technical degree holder, the requirement is at least five years engineering experience plus five years of Systems Engineering experience. One problem is what does INCOSE mean by “non-technical degree?” In general a B.S. (or S.B.) is a technical degree. A B.A. is considered a non-technical degree. A challenge not yet resolved is that some universities give a B.S. for a degree in math, while others give a B.A. for the same course of study. If this arises, suggest the applicant contact the INCOSE Certification Office for resolution. If an applicant has no degree he or she needs ten years of professional level engineering experience plus five years of systems engineering experience. Advise the applicants that documenting more experience than the minimum is a good idea since some experience may be deemed inappropriate, and you don’t want to fall below the minimum. This is especially an issue with person with a B.S. and barely five years of experience. Experience requirement is only satisfied by RELEVANT Systems Engineering experience ACCEPTED by INCOSE

19 Depth and Breadth Examples

20 Description Of Experience Must Be Clear And Direct.
Experience must convey your direct systems engineering involvement in tasks Avoid terms like Participated on a team that … Led an effort to develop … Was involved with the planning of … The following pages provide a reference of areas of Systems Engineering activities defined by the certification program and examples of direct language explanations Notes: The Applicants experience will be a critical element of the INCOSE review – The application is NOT a RESUME – Keep the experience direct and applicable and use language that is unambiguous Avoid terms like, Participate, Led, Involved with, responsible – . Explain why these terms are unacceptable—INCOSE is looking for primary responsibility, hands-on experience. Ask the class for other terms that e.g. Managed, facilitated, monitored, worked on …. The following pages are directly out of the INCOSE Certification Plan that talks to Systems Engineering experience – And suggest direct language that would help in the evaluation of your experience Ask the class for other terms that would be direct and clear for their experience.

21 Relating Life Cycle Phases to Vee Icon

22 1. Technical Planning Identify: Prepare Systems Engineering
User needs Program objectives Technical development strategy Program metrics including product technical performance measures and key performance parameters Program resource needs in terms of equipment, facilities, and personnel capabilities Prepare Systems Engineering Management Plans (SEMP) Define Product Breakdown Structures Prepare Integrated Master Plans Prepare Integrated Master Schedules Prepare program Work Breakdown Structures Master Technical Planning and Strategies is performed in the early stages of the development. The master technical plan such as the Integration, Verification, and Validation are identified at the beginning of the project/program. The details of the various plans may be developed during the stages where the definition of that activity is done. For example the Master Verification plan is done as part of the Systems Engineering Management Plan, which one of the very initial products. But the verification plans for requirements are done during the development of requirements themselves and the same is true for Integration.

23 2. Requirements Engineering
Analyze customer and stakeholder needs Develop Requirements Management Plan At each level (for selected concept) Generate/develop requirements Develop measures of effectiveness and performance Perform functional analyses Develop architectural concept Allocate or derive requirements (for next level) Implement Requirements Management Plans Ensure requirements quality Control requirements Maintain requirements database Requirements engineering is done at the early stages as illustrated. The idea is that engineering a set of requirements starts with the customer needs and problem space. The systems engineer must understand the problem space and keep the big picture in mind as the problem space becomes defined and clarified to the point where a validated set of requirements can be documented. The set of requirements must be linked to a customer need and address the problem space. The requirements must be verifiable, clear, minimal. The performance of the requirements must be specified such that they can be measured through a Test, Demonstration, Inspection, or Analysis. Concurrent with these requirements a verification plan is developed. This is needed to help ensure that each requirement can be verified, and, in addition, the need to create verifiable requirements will help in formulation of the requirements. This is a form of a quality check on each requirement. Once a validated set of requirements is documented and approved by the customer this becomes a baseline. Any changes that occur must now go through a formal change process.

24 3. Baseline Control Planning Develop Configuration Management Plans
Defining Establish change control processes Establish and update baselines for requirements and evolving configurations/products Performing Implement Configuration Management Plans, including change control process Participate in configuration item identification and status accounting Approve technical changes prior to presentation to CCB Participate in CCB Participate in functional and physical configuration audits Planning Defining Baseline Control or Configuration Management is a way to mange and control the integrity of the products of the project/program. Product integrity means that what is in the product is accurately documented to the point where the product can be implemented without a design activity. Baseline control is done in three stages Planning – Development of a system configuration management plan that will last for the life of the systems (other configuration management plans will be developed for the components of the system; for example in major software activities, a software configuration management plan will be developed by the software development team) Defining – A definition of products that need to be controlled is created. These are called configuration Items – these not only include the software and hardware products and human interactions required by the system, but artifacts such as test plans, production drawings, simulators, requirements etc. Performing – Changes will happen, after the baseline has been established. Any changes to that baseline need to be authorized through a change management process. This process includes an assessment of the recommended change, risks, impact, costs, schedule, trade study against alternatives. A change board made up of the customer, lead technical staff and project management decides on changes to the system. Information on changes are captured by the status accounting systems and to ensure that changes are implemented correctly – both a functional (verification) and Physical Audit (inspecting that the documentation matches the product) are made. Performing CCB = Configuration Control Board

25 4. Technical Effort Assessment
Planning Actions for all program metrics, including product technical performance measures and key performance parameters: Collect Analyze Report Status (track) Planning Technical effort assessment is a continuous process throughout the development of the system. Collecting metrics that are meaningful is an important part of systems engineering responsibility. These metrics are analyzed and tracked to ensure that the technical aspects of the project are in line with the customer’s expectations and that any deviation from expectations are identified as early as possible. Audits and reviews are forums in which the metrics are reviewed and impacts are assessed across the system Issues such as process and product improvements need to be considered continuously, so that early warning of defects in the process or product identified and improvements made. Actions

26 4. Technical Effort Assessment (Cont’d)
Actions Conduct audits and reviews Assess process and tool usage compliance Conduct capability assessments Recommend process and product improvements Implement approved process and product improvements Planning Technical effort assessment is a continuous process throughout the development of the system. Collecting metrics that are meaningful is an important part of systems engineering responsibility. These metrics are analyzed and tracked to ensure that the technical aspects of the project are in line with the customer’s expectations and that any deviation from expectations are identified as early as possible. Audits and reviews are forums in which the metrics are reviewed and impacts are assessed across the system Issues such as process and product improvements need to be considered continuously, so that early warning of defects in the process or product identified and improvements made. Actions

27 5. Design (Concept Architecture) Development
Prepare Trade Study Plans At each level and as appropriate Identify alternate candidate concepts and architectures Evaluate concepts and architectures Select and optimize baseline candidate concept and architecture Conduct trade studies Document trade studies Prepare system/solution description documents The Design areas of activities are shown here because much of the area of experience specified by the plan is in concept development. In this case concepts are developed during the concept exploration or sometime called Mission Analysis phase of the project. Most of this is done by the customer prior to issuing an RFP for the actual development of the systems or product. However contractor involvement is common, working with the customer team. The principles of defining a baseline concept are also appropriate at each level of system definition. For example, a Concept of Operation is done at each level of definition as well as an architecture, and at each level trade studies are performed to ensure that the most cost effective architecture for that level is recommended. The final phase of Component detailed design is the preparation of “Build to” documentation, which is done just prior to implementation.

28 6. Qualification, Verification, and Validation
Planning Develop Qualification, Verification, and Validation Plans Implement Qualification, Verification, and Validation Plans Defining Develop verification requirements Prepare requirements verification matrix and qualification certificates Develop pass/fail criteria Performing Conduct qualification, verification, and validation efforts and corrective actions Record results of qualification, verification, and validation efforts, and corrective actions Planning Defining Performing Qualification, Verification and Validation is also done in three stages: Planning As part of the systems engineering management planning, Master Qualification, Verification, and Validation plans are developed. Defining The Verification, Validation, and Qualification plans are develop concurrently with the requirements and refined through out the decomposition of the system Performing Conducting Verification, Validation, and Qualification is done when the components and sub-systems are recomposed – anomalies are identified, addressed and managed

29 7. Process Definition Enterprise Level Project/Program Level
Define enterprise processes Define enterprise best practices Project/Program Level Tailor enterprise processes for program/project applications Enterprise Process definition is usually done at the enterprise level, (Company, Division, Department). The definition of the systems engineering process is defined and documented based on the business objectives of the organization. Each project within the organization starts with these documented processes and procedures – and then tailored for the given needs of the project and customer. This tailoring is documented and traced and used by the Quality Assurance of the project. Project/Program Level

30 8. Tool Support Specify requirements Evaluate candidates
Actions for Systems Engineering computer programs and tools: Specify requirements Evaluate candidates Select appropriate choice Configure for use Systems that have a moderate level of complexity will benefit from Systems Engineering tools These tools include Modeling, Simulation, Requirements management, Risk Management, Verification tools, Decision Support. These tools can be complex in configuring them for a given project or program. Sometime the tools need to model the system of interest or be configured for modeling the information of the system and its relationships. Systems engineering is becoming reliant on these types of tools to perform their work. Systems engineering is needed to configure many of these tools. Actions

31 9. Training Develop Training Plans for Approved Systems Engineering
processes and tools Implement Training Plans Develop training courses on Give training Enterprise Training plans are done at the enterprise and project/program level. Training includes a wide range of knowledge areas such as accepted processes and procedures, fundamental training in systems engineering, and orientation to systems engineering tools. Enterprise Level Process training – CM, Requirements, Project Management, QA, Risk Management Courseware development – Training material, train the trainers, instructor aids Project/Program Level Product training – Operational guides, logistics, Maintenance, Project/Program Level

32 10. Systems Integration Planning Defining Performing
Define technical integration strategy Develop Integration Plans Defining Develop integration test scripts Develop and implement integration test scenarios Performing Develop integration procedures (based on integration plans) Conduct and document integration tests Track integration test results and retest status Planning Defining Performing Systems Integration is done in the following three stages: Planning Integration strategy and the Master integration plans are developed as part of the systems engineering management planning and early stages of development. Defining Occurs during the project architecture and high level design of the system, where the interfaces are defined for both the internal and external systems here the definition of test scripts, integration scenarios can be initially developed. Performing Is the doing of integration when the real hardware/software components and subsystems come together after implementation. Integration issues are addressed, and integration anomalies are identified, addressed, and managed.

33 11. Risk and Opportunity Management
Planning Develop Risk and Opportunity Management Plan Create Risk mitigation and Opportunity achievement plans Implement Risk and Opportunity Management Plans Performing Implement risk mitigation and opportunity achievement plans Identify risk issues and opportunities Assess risk issues and opportunities Prioritize risks and opportunities Track risk reduction opportunity achievement activities Planning Risk and Opportunity Management is another activity that is performed throughout the project Life Cycle. Identifying technical risks is a key systems engineering activity. Planning Start with a risk management plan that is based on the sensitivity of the customer to project risks and opportunities. Performing Opportunity/Risk Identification – Identifies potential opportunity/risk Opportunity/Risk Analysis – Assesses the opportunity/risk for probability of Occurrence and Impact to project Opportunity/Risk priority – prioritizes the opportunity/risk Opportunity/risk mitigation plan – develops a opportunity/risk mitigation/achievement plan that provides a profile of each opportunity/risk, triggers and tracking information Performing

34 12. Quality Assurance Planning Develop a Quality Assurance Plan
Performing Implement the Quality Assurance Plan Perform quality audits Report quality audits Defining Define quality corrective actions Track quality corrective actions Planning Defining Quality Assurance is used through out the Life cycle of the system and starts with Planning: Planning: Establishes a quality assurance plan for the system and identifies the processes that will be followed, as well as any tailoring requirements Performing Implementing the QA plan is a continuous process through out the Life Cycle of the system. The systems engineer is responsible for monitoring to ensure that the processes that were identified are followed and that any deviation to the process is documented. The systems engineer needs to determine if the process needs to be corrected, or the implementation of the process changes needs to be documented. Performing

35 13. Specialty Engineering
Planning: Develop Specialty Plans covering: Reliability Maintainability Supportability Survivability Security Safety Electromagnetic environmental effects Environmental engineering Human engineering Logistics support Packaging and handling Implement Specialty Plans Planning Implement Specialty Engineering – is a broad area of supporting activities that are critical for systems development. Usually they are very specialized activities that address specific system environments. In each case, these activities must be planned and in most cases defined and then performed.

36 14. Other Many domains practice systems engineering but use specialized jargon and activities; the following are examples: Intelligent Transportation Systems Regional Architecture – example of a framework that identifies User Services and Market Packages for one or more metropolitan areas Highway Development Civil engineering uses Plans, Specifications, and estimates to progress through a design Requirements come out of planning and long range forecast models Medical – Clinical Trials – (process for developing a new drug) Configuration management – that tracks every test performed without identification of individuals (HIPAA requirement) Etc. If you use this category, show the relationship of your experience to the thirteen areas above, and justify your effort as systems engineering. Define HIPAA – Health Insurance Portability and Accountability Act What does the HIPAA Privacy Rule require the average provider or health plan to do? For the average health care provider or health plan, the Privacy Rule requires activities, such as: - Notifying patients about their privacy rights and how their information can be used. - Adopting and implementing privacy procedures for its practice, hospital, or plan. - Training employees so that they understand the privacy procedures. - Designating an individual to be responsible for seeing that the privacy procedures are adopted and followed. - Securing patient records containing individually identifiable health information so that they are not readily available to those who do not need them. HIPAA = Health Insurance Portability and Accountability Act

37 CSEP Application: Section 6 - References
An application shall contain the names of not less than three persons who have personal knowledge of the experience on which the applicant predicates his/her qualifications and who are not related to the applicant by blood or marriage An application shall contain the reference endorsements of not less than three persons … References will be contacted by you You will submit the list of references with the application The references will submit their endorsement DIRECTLY to INCOSE Notes: Explain the difference between references and the supervisors listed in Section 5. References can come from anywhere in their Systems Engineer careers. Go over each line of Section 6 and explain the importance of it. Also point out that each reference must have Systems Engineering experience as described below. A reference, is an associate or fellow worker who is equal or at a higher level in abilities and qualifications "systems engineering wise," and, because of that can attest to your "systems engineering knowledge” and past experience in successfully performing “systems engineering tasks.” Part of the process in certifying an applicant as a Systems Engineering Professional is to obtain data from references that the applicant performed the tasks as described in the application. All of the following categories of people should qualify as credible references: Supervisors for whom you work and/or who provide your systems engineering performance rating Program Managers/Task Leaders for whom you work and/or who provide input for your systems engineering performance rating College Professors of Systems Engineering who grade your knowledge and systems engineering performance through classroom assignments and projects at the graduate level INCOSE Fellows who are acquainted with your work (experience), knowledge, leadership, and contributions to systems engineering INCOSE Leadership who are acquainted with your work (experience), knowledge, leadership, and contributions to systems engineering INCOSE Certified Systems Engineering Professionals who are acquainted with your work (experience), knowledge, leadership, and contributions to systems engineering An applicant should provide references from a mixture of these categories. Thus, an applicant should limit references to two from any one category. References, who provide information to support an applicant and their reasons for the recommendation, will be requested to submit information on their own work (experience), knowledge, leadership, and contributions to systems engineering. It is YOUR responsibility to Select appropriate ADVOCATES for your certification application. Let your references know what experience and performance you are citing as evidence of your qualifications for certification

38 CSEP Application: Section 6 - References
(An application shall contain the names of and reference endorsements of not less than three persons, not related to the applicant by blood or marriage, who have personal knowledge of the experience on which the applicant predicates his/her qualifications.) Reference 1: Name: ______________________________________________________________ Address: ____________________________________________________________ Address: ______________________________________________________ Phone Number: ______________________________________________________ Reference 2: Phone Number: _______________________________________________________ Reference 3: Let your ADVOCATES know that they may be contacted. Verify that each ADVOCATE’s contact information is current. Notes: Explain the importance of providing complete contact information for each reference Explain the importance of contacting each reference BEFORE submitting the application. Discuss how to prepare the reference. They will be contacted by INCOSE They will be asked to describe THEIR SE experience (in general and in each of the 14 experience areas) They will be asked to provide detailed information on your SE experience Explain that each reference should be an advocate, not just a reference. Have the students complete this section of the application. Note: The correct INCOSE term is “References”; We are using the term “Advocates” to emphasize the proper role of your references.

39 Characteristics of a “Good” Advocate
Ensure the advocates you select can provide positive information about your Systems Engineering experience Select advocates who have Systems Engineering knowledge sufficient to judge your skills – An advocate needs to convince INCOSE evaluators that the advocate understands Systems Engineering Your current or past supervisors may – or may not – be good advocates for you Notes: This chart explains what is meant by a Good Advocate – And make sure the class understands that the Advocate must recommend the candidate for certification. IMPORTANT – Tell your advocates what Systems Engineering tasks you performed while you worked with them…

40 Next Steps Finalize your application form
Be sure to communicate with your references Submit the application to INCOSE Upon acceptance from INCOSE, schedule you certification examination with Thomson Prometric (directions will be included in your acceptance letter)

41 The Certification Examination
Computer-based examination Given at Prometric testing centers 120 multiple choice questions from the INCOSE Systems Engineering Handbook and ISO 15288 Study Hard! You must understand these two documents to pass the test. Two hour time limit Immediate notification of results Notes: Emphasize that this is a computer-based test and that the test is based on the INCOSE Systems Engineering Handbook The INCOSE website shows a question typical of what might be on the examination. CSM has also developed a set of illustrative questions. .

42 CSEP Value Propositions
Certification offers value to business and professionals! Business Value Propositions: Standardization drives predictable results that impact bottom line Reflects positive investment in staff--greater employee retention Increased competitiveness in pursuit of new business (key differentiator) Individual Value Propositions: Formal recognition of professional’s expertise and experience Higher compensation – PMP’s averaged more than 14% increase in 2004 Enhanced employment prospects The key to this slide is to agree on what the value propositions are and promote them on your website and through press activities i.e., cert mag, cert cities etc. that prove out certification advantages that can be used as strong value statements and drive for the program We want businesses to require CSEP certified professionals!

43 CSM’s CSEP Preparation Program
Three Point Program: One-day application workshop Two-day INCOSE handbook review Just-in-time support Multiple Delivery Methods: Open enrollment On-site training CSM partners Course Content: Guide professionals in organizing a strong application Handbook overview Assess individual strengths and weaknesses and together we develop study guides with students Multiple practice tests Use slide content to discuss

44 CSM’s CSEP Preparation Program – Continued
Available Delivery Methods: On-site (dependent on class size) At CSM Headquarters (Vienna, VA) Available Dates: Offered monthly Visit CSM’s CSEP Preparation Program is offered both on-site and via the company’s open enrollment program A.K.A. Client Impact Training Open Enrollment Courses offered monthly. To view our schedule, visit Under new programs you will find Client Impact Training. By clicking on the highlighted Client ImpactTraining link, you will be brought to our published schedule. To order, simply click the button at bottom of web page, order now!

45 CSM’s CSEP Preparation Program – Continued
What is Included: Application Workshop 2-day Handbook Review Practice exams (Pre & Post) Course Materials Study Guide INCOSE Handbook V.2a Follow-up and Coaching

46 Sample of Practice Test Questions
What are two aspects of the definition of concurrent engineering? (Choose two.)  All technical disciplines are involved as requirements are developed. Products and their related processes are developed simultaneously. All technical disciplines are co-located during definition. Ensure that system engineering staff are available throughout the development. Pg 79, ¶ 5 Answer A is unchanged from the Agency version. Answer B was modified to match the format (should be a sentence) of the other three questions. NOTE: The triple line was inserted to alert the instructor that the NEXT mouse click will highlight the answer. This question IS NOT from the INCOSE Certification Exam. The format and content are similar (based on SEHv2a), however it was created for a CSM client by CSM and Prometric, and is used with permission.

47 Question 1-10 What is a best practice for concurrent engineering?
Ensure monthly meetings of technical staff. Ensure continuous integration of the entire product team. Ensure that the team fully understands all the user requirements. Ensure the availability of state-of-the-art systems engineering tools. Pg 79, ¶ 5 Answer B was modified from “B. Ensure timely involvement of all technical disciplines” to the text in the slide so it matches the SEHv2a text exactly. NOTE: The triple line was inserted to alert the instructor that the NEXT mouse click will highlight the answer. This question IS NOT from the INCOSE Certification Exam. The format and content are similar (based on SEHv2a), however it was created for a CSM client by CSM and Prometric, and is used with permission.

48 Question 1-11 Which two factors are critical for Integrated Project Teams (IPT) implementation? (Choose two.)  The team is co-located. To be effective, team members must maintain a constant level of involvement during development. The team should be empowered with the authority to match its responsibility. Each team has at least 5 full time equivalent members (SE, design engineering, manufacturing, SW development, system test). The team has cost, schedule, and performance responsibility. Pg 81, ¶ 1 Pg 88, Fig 7-6 Previous answers for B and C, now deleted, were: B. The team leader is a coach/facilitator. C. The team has risk management responsibility. While these are true, they are not explicitly stated in the INCOSE SEHv2a. So these answers were changed, as follows: B. This new distracters is false (SEHv2a pg 82,paragraph 5), which says “These team members’ participation will vary throughout the product cycle…” C. The team should be empowered with the authority to match its responsibility (true). D. Added the words in the parentheses to make this distracter more plausible. Also, changed from “Choose three” to “Choose two.” Answers = C, E NOTE: The triple line was inserted to alert the instructor that the NEXT mouse click will highlight the answer. This question IS NOT from the INCOSE Certification Exam. The format and content are similar (based on SEHv2a), however it was created for a CSM client by CSM and Prometric, and is used with permission.

49 Next Steps We wish you good luck and success in your CSEP journey!
Prepare application carefully. Get application critiqued. Line up qualified references. Study Hard! Remember that you need to understand the Systems Engineering Process as defined in the INCOSE Handbook, version 2a, and ISO15288. Consider CSM’s CSEP Preparation Course We wish you good luck and success in your CSEP journey!

50 © 2005 Center for Systems Management, Inc.
Thank You! For additional information of CSEP Preparation Courses contact: Kevin Magee © 2005 Center for Systems Management, Inc. 1951 Kidwell Drive, Suite 750 Vienna, VA 22182 (800)

Download ppt "CSEP Preparation Program"

Similar presentations

Ads by Google