Presentation on theme: "CSEP Preparation Program"— Presentation transcript:
1CSEP Preparation Program Certification for Systems Engineering ProfessionalsOverview
2What 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
3INCOSE CSEP Background Systems Engineering Certification2001 – Survey of need for and interest in SE Certification2002 – Exam created2003 – Beta test (300 questions, 167 retained)2004 – First 50 people certified as CSEP2005 – CSEP program open for public enrollmentNotes: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.
4CSEP DesignationWhat is the designation for a Certified Systems Engineering Professional?CSEPFor example on a business cardJohn 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 PinINCOSE Certification LetterINCOSE DatabaseNotes:When candidates becomes certified,What their designation will beWhat organization certifies themWhat proof will there be that they are Certified Systems Engineers
5Fun CSEP Facts: What are these numbers? 84Number of CSEPS50Number of CSEPS – Pilot Program34Number of CSEPS – Post Pilot40%Percent through CSM Prep Program45In the pipelineNumbers are approximate as of end of June, 2006
6Requirements for Certified Systems Engineering Professional (CSEP)* SE Experience - 5 years minimum in multiple SE disciplinesEducation – 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 EngineeringCertification Exam* Application and Fee Submittals RequiredApplication requires copy of degree transcript or diplomaApplication fee is $400 – discounted to $300 for INCOSE membersTest 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
7What are the criteria for earning Systems Engineering Certification? 1. Applicant’s educationDetermines the extent of required experienceSupported by copies of college transcripts or degrees2. Applicant’s verifiable experienceAt least five years of experience in systems engineering (technical degree)Additional 5 years engineering experience if non-technical degreeAdditional 10 years engineering experience if no degree3. Applicant’s advocatesAt least three references are to be selected by the applicantReferences must know and understand Systems EngineeringReferences must provide written endorsement verifying applicant’s systems engineering skills and experience4. Successful completion of an exam based on:INCOSE Handbook Version 2a, andISO Systems Engineering — System Life Cycle ProcessesNotes:Explain that the basis of Systems Engineering Certification isVerifiable educationVerifiable experienceAcknowledgement by 3 Advocates (who understand Systems Engineering) of the candidates Systems Engineering ExperiencePassing an exam that is based on the INCOSE Handbook version 2a and ISO 15288
8CSEP Exam InformationThe CSEP Exam is based on current INCOSE SE Handbook Version 2A which is available on INCOSE’s web site.Exam cost is $80 per examConsists of 120 questions2 hours in lengthPass/Fail results provided immediately upon exam completionCandidates eligible for two re-tests within the yearSE Handbook version 3 released in 2006.Certification is good for 3 yearsExplain 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.
9Current Certification Process ApplicationDevelopment1. VerifiableEducation2. VerifiableExperience3. Applicant’sAdvocates (three references knowledgeable about SE)Take Cert Exam(Prometrics Test Center)Pay test feeINCOSEApplicationCenterEvaluation$CompletedAnd FeeNotifyApplicantTwo weeksISO 15288INCOSESE HandbookVersion 2aStudyPass3 yearCertificationNotes:Walk the Class through the certification process – This chart is animated – Bring one group at a time and talk to that groupGroup 1 -Application DevelopmentDocumented Systems Engineering experienceApplicants EducationApplicants Advocates recommendationPayment to INCOSEGroup 2INCOSE review of the Application and applicant notificationApplication approval –Application disapprovalWhat 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 3Studying for the exam when application is approvedGroup 4Appointment with the Prometrics test centers and setting for the examNotification will be immediateGroup 5INCOSE will send the successful candidate their certificate and card – good for 3 yearsGroup 6Once the candidate has been awarded CSEP status – they must start accumulating PDUs for certification renewal.Group 7Show that areas that this course will provide assistanceApplication SupportCertification Exam supportAlso discuss the appeals processFour to six weeksApplicant’s own paceApplicant has up to one year to pass the test (three tries 3 months apart). Test is scheduled directly with Thompson-Prometrics.Timeline
10Continuing Education Credits for Certification Renewal INCOSE requires 120 PDUs during the three-year certification periodEducation ActivityCredit1 College or unit semester hour45 PDU1 College or unit quarter hour 30 PDU1 Continuing Education Unit (CEU)10 PDU1 Professional Development Hour (PDH)1 PDU1 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 PDUAuthoring published papers, articles or books in any area relevant to practice1 hour of participation in professional and technical society working groups/managementPatents 1 hour of professional development in coursework, seminars, or professional or technical presentation made at meetings, conventions, conferences, or exam preparationHighlight 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.
11The OpportunityINCOSE has an opportunity to advance the industry, increase memberships and create broad visibility through its certification programBased on the success experienced from PMI’s PMP certification program, CSEP can drive the same success for INCOSE, and our industryQualify the value proposition for the industryWe get to invent a NEW acronym! CSEPBased on market indicators, CSM is highly optimistic on the success of the CSEP programBased on proven programs (PMI/PMP Certification)Vertical view of CSM customers and forecasted growth over the next 4 yearsForecasted employment growth in Engineering disciplines, primarily Systems EngineeringThe 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.
12CSEP Potential Impact PMP Experience INCOSE Opportunity* *Based on CSM’s projected forecastSlide 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 propositionsRecent success based on:Full-time employeesReduced application approval times <11 daysWord of mouth advertisingValue 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!
13Market Analysis (C.A.G.R.) Market TrendsMarket AnalysisMarket Analysis (C.A.G.R.)$BillionsA 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.
15Discussion of the CSEP Application Notes:Distribute Exercise 2-1—CSEP Application FormThe forms will be used throughout the rest of the day
16CSEP Application – SE Experience Section 5: ExperienceUse 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.
17Experience Summary Table Systems Engineering areas of work - See Application Instructions for Detailed DefinitionsTotal Months of Experience1. Technical Planning2. Requirements Engineering3. Baseline Control4. Technical Effort Assessment5. Design Development6. Qualification, Verification, and Validation7. Process Definition8. Tool Support9. Training10. Systems Integration11. Risk and Opportunity Management12. Quality Assurance13. Specialty Engineering14. OtherNotes: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
18Depth and Breadth of Experience and Education Distribution of Experience in the Systems Engineering AreasAmount of SE ExperienceRequiredMaximumDepthBreadthIntermediate5 years with Bachelor’sdegree, or equivalent, intechnical field3 years in any 1 areaand 2 years in other areas1 year in each of 3 areas and 2 years in other areasAny combinationbetween maximumdepth and maximum widthNote: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
20Description Of Experience Must Be Clear And Direct. Experience must convey your direct systems engineering involvement in tasksAvoid terms likeParticipated 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 explanationsNotes: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 unambiguousAvoid 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 experienceAsk the class for other terms that would be direct and clear for their experience.
221. Technical Planning Identify: Prepare Systems Engineering User needsProgram objectivesTechnical development strategyProgram metrics including product technical performance measures and key performance parametersProgram resource needs in terms of equipment, facilities, and personnel capabilitiesPrepare Systems EngineeringManagement Plans (SEMP)Define Product Breakdown StructuresPrepare Integrated Master PlansPrepare Integrated Master SchedulesPrepare program Work BreakdownStructuresMaster 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.
232. Requirements Engineering Analyze customer and stakeholder needsDevelop Requirements Management PlanAt each level (for selected concept)Generate/develop requirementsDevelop measures of effectiveness and performancePerform functional analysesDevelop architectural conceptAllocate or derive requirements (for next level)Implement Requirements Management PlansEnsure requirements qualityControl requirementsMaintain requirements databaseRequirements 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.
243. Baseline Control Planning Develop Configuration Management Plans DefiningEstablish change control processesEstablish and update baselines for requirements and evolving configurations/productsPerformingImplement Configuration Management Plans, including change control processParticipate in configuration item identification and status accountingApprove technical changes prior to presentation to CCBParticipate in CCBParticipate in functional and physical configuration auditsPlanningDefiningBaseline 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 stagesPlanning – 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.PerformingCCB = Configuration Control Board
254. Technical Effort Assessment PlanningActions for all program metrics, including product technical performance measures and key performance parameters:CollectAnalyzeReportStatus (track)PlanningTechnical 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 systemIssues 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
264. Technical Effort Assessment (Cont’d) ActionsConduct audits and reviewsAssess process and tool usage complianceConduct capability assessmentsRecommend process and product improvementsImplement approved process and product improvementsPlanningTechnical 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 systemIssues 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
275. Design (Concept Architecture) Development Prepare Trade Study PlansAt each level and as appropriateIdentify alternate candidate concepts and architecturesEvaluate concepts and architecturesSelect and optimize baseline candidate concept and architectureConduct trade studiesDocument trade studiesPrepare system/solution description documentsThe 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.
286. Qualification, Verification, and Validation PlanningDevelop Qualification, Verification, and Validation PlansImplement Qualification, Verification, and Validation PlansDefiningDevelop verification requirementsPrepare requirements verification matrix and qualification certificatesDevelop pass/fail criteriaPerformingConduct qualification, verification, and validation efforts and corrective actionsRecord results of qualification, verification, and validation efforts, and corrective actionsPlanningDefiningPerformingQualification, Verification and Validation is also done in three stages:PlanningAs part of the systems engineering management planning, Master Qualification, Verification, and Validation plans are developed.DefiningThe Verification, Validation, and Qualification plans are develop concurrently with the requirements and refined through out the decomposition of the systemPerformingConducting Verification, Validation, and Qualification is done when the components and sub-systems are recomposed – anomalies are identified, addressed and managed
297. Process Definition Enterprise Level Project/Program Level Define enterprise processesDefine enterprise best practicesProject/Program LevelTailor enterprise processes for program/project applicationsEnterpriseProcess 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
308. Tool Support Specify requirements Evaluate candidates Actions for Systems Engineering computer programs and tools:Specify requirementsEvaluate candidatesSelect appropriate choiceConfigure for useSystems 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
319. Training Develop Training Plans for Approved Systems Engineering processes and toolsImplement Training PlansDevelop trainingcourses onGive trainingEnterpriseTraining 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 LevelProcess training – CM, Requirements, Project Management, QA, Risk ManagementCourseware development – Training material, train the trainers, instructor aidsProject/Program LevelProduct training – Operational guides, logistics, Maintenance,Project/Program Level
3210. Systems Integration Planning Defining Performing Define technical integration strategyDevelop Integration PlansDefiningDevelop integration test scriptsDevelop and implement integration test scenariosPerformingDevelop integration procedures (based on integration plans)Conduct and document integration testsTrack integration test results and retest statusPlanningDefiningPerformingSystems Integration is done in the following three stages:PlanningIntegration strategy and the Master integration plans are developed as part of the systems engineering management planning and early stages of development.DefiningOccurs 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.PerformingIs 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.
3311. Risk and Opportunity Management PlanningDevelop Risk and Opportunity Management PlanCreate Risk mitigation and Opportunity achievement plansImplement Risk and Opportunity Management PlansPerformingImplement risk mitigation and opportunity achievement plansIdentify risk issues and opportunitiesAssess risk issues and opportunitiesPrioritize risks and opportunitiesTrack risk reduction opportunity achievement activitiesPlanningRisk and Opportunity Management is another activity that is performed throughout the project Life Cycle. Identifying technical risks is a key systems engineering activity.PlanningStart with a risk management plan that is based on the sensitivity of the customer to project risks and opportunities.PerformingOpportunity/Risk Identification – Identifies potential opportunity/riskOpportunity/Risk Analysis – Assesses the opportunity/risk for probability of Occurrence and Impact to projectOpportunity/Risk priority – prioritizes the opportunity/riskOpportunity/risk mitigation plan – develops a opportunity/risk mitigation/achievement plan that provides a profile of each opportunity/risk, triggers and tracking informationPerforming
3412. Quality Assurance Planning Develop a Quality Assurance Plan PerformingImplement the Quality Assurance PlanPerform quality auditsReport quality auditsDefiningDefine quality corrective actionsTrack quality corrective actionsPlanningDefiningQuality 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 requirementsPerformingImplementing 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
3513. Specialty Engineering Planning:Develop Specialty Plans covering:ReliabilityMaintainabilitySupportabilitySurvivabilitySecuritySafetyElectromagnetic environmental effectsEnvironmental engineeringHuman engineeringLogistics supportPackaging and handlingImplement Specialty PlansPlanningImplementSpecialty 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.
3614. OtherMany domains practice systems engineering but use specialized jargon and activities; the following are examples:Intelligent Transportation SystemsRegional Architecture – example of a framework that identifies User Services and Market Packages for one or more metropolitan areasHighway DevelopmentCivil engineering uses Plans, Specifications, and estimates to progress through a designRequirements come out of planning and long range forecast modelsMedical – 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 ActWhat 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
37CSEP 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 marriageAn application shall contain the reference endorsements of not less than three persons …References will be contacted by youYou will submit the list of references with the applicationThe references will submit their endorsement DIRECTLY to INCOSENotes: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 ratingProgram Managers/Task Leaders for whom you work and/or who provide input for your systems engineering performance ratingCollege Professors of Systems Engineering who grade your knowledge and systems engineering performance through classroom assignments and projects at the graduate levelINCOSE Fellows who are acquainted with your work (experience), knowledge, leadership, and contributions to systems engineeringINCOSE Leadership who are acquainted with your work (experience), knowledge, leadership, and contributions to systems engineeringINCOSE Certified Systems Engineering Professionals who are acquainted with your work (experience), knowledge, leadership, and contributions to systems engineeringAn 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 toSelect appropriate ADVOCATES for your certification application.Let your references know what experience and performance you are citing as evidence of your qualifications for certification
38CSEP 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 referenceExplain the importance of contacting each reference BEFORE submitting the application.Discuss how to prepare the reference.They will be contacted by INCOSEThey 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 experienceExplain 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.
39Characteristics of a “Good” Advocate Ensure the advocates you select can provide positive information about your Systems Engineering experienceSelect advocates who have Systems Engineering knowledge sufficient to judge your skills –An advocate needs to convince INCOSE evaluators that the advocate understands Systems EngineeringYour current or past supervisors may – or may not – be good advocates for youNotes: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…
40Next Steps Finalize your application form Be sure to communicate with your referencesSubmit the application to INCOSEUpon acceptance from INCOSE, schedule you certification examination with Thomson Prometric (directions will be included in your acceptance letter)
41The Certification Examination Computer-based examinationGiven at Prometric testing centers120 multiple choice questions from the INCOSE Systems Engineering Handbook and ISO 15288Study Hard!You must understand these two documents to pass the test.Two hour time limitImmediate notification of resultsNotes:Emphasize that this is a computer-based test and that the test is based on the INCOSE Systems Engineering HandbookThe INCOSE website shows a question typical of what might beon the examination.CSM has also developed a set of illustrative questions..
42CSEP Value Propositions Certification offers value to business and professionals!Business Value Propositions:Standardization drives predictable results that impact bottom lineReflects positive investment in staff--greater employee retentionIncreased competitiveness in pursuit of new business (key differentiator)Individual Value Propositions:Formal recognition of professional’s expertise and experienceHigher compensation – PMP’s averaged more than 14% increase in 2004Enhanced employment prospectsThe 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 programWe want businesses to require CSEP certified professionals!
43CSM’s CSEP Preparation Program Three Point Program:One-day application workshopTwo-day INCOSE handbook reviewJust-in-time supportMultiple Delivery Methods:Open enrollmentOn-site trainingCSM partnersCourse Content:Guide professionals in organizing a strong applicationHandbook overviewAssess individual strengths and weaknesses and together we develop study guides with studentsMultiple practice testsUse slide content to discuss
44CSM’s CSEP Preparation Program – Continued Available Delivery Methods:On-site (dependent on class size)At CSM Headquarters (Vienna, VA)Available Dates:Offered monthlyVisitCSM’s CSEP Preparation Program is offered both on-site and via the company’s open enrollment program A.K.A. Client Impact TrainingOpen 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!
45CSM’s CSEP Preparation Program – Continued What is Included:Application Workshop2-day Handbook ReviewPractice exams (Pre & Post)Course MaterialsStudy GuideINCOSE Handbook V.2aFollow-up and Coaching
46Sample 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, ¶ 5Answer 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.
47Question 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, ¶ 5Answer 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.
48Question 1-11Which 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, ¶ 1Pg 88, Fig 7-6Previous 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, ENOTE: 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.
49Next 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 CourseWe wish you good luck and success in your CSEP journey!