Professional Documents
Culture Documents
Effective Leader Group of interdependent individuals Complementary skills Shared, meaningful purpose Specific goals Well-defined roles and responsibilities Mutual accountability Collaborative approach Confidence Desire for continuous improvement
Big M, Little e
PEs first and foremost responsibility is: Management of the engineering teams effort Effective Project Engineers:
Are effective team leaders and team builders Display commitment and passion Employ right to left thinking andplanning Show a sense of urgency Are results oriented Are detail focused Have strong communication skills
Business Management
Project Engineering
Mission Assurance
Material Management
System Engineering
Software Engineering
Electrical Engineering
Mechanical Engineering
Optical Engineering
Systems Test
Test Engineering
Configuration Management
PMO Procurement Project Engineer Operations Quality Engineering Team Facilities Export Management
8
Security
10
Additional Roles
Recognize and support the Program Manager as the person ultimately responsible for the program. Provide timely input when the PE perceives the directed course of action will not achieve the divisions goals and if necessary, elevate the problem until it is resolved. Get the job done!
11
Manages Sub-Contracts
Scheduling Issues Technical performance
12
Provide day to day direction for assigned engineers Responsible for hosting and leading design reviews In some cases act as the Cost Account Manager (CAM) Ensure performance to key parameters are monitored and met Review and approve drawings and Change Orders Participate in internal and vendor qualification and evaluation process Provides monthly Technical Project status and all related supports Provides Lessons Learned Supports program close-out
Project Engineering
Our shared mission is to work to achieve the cost, schedule, technical, and customer satisfaction goals for each program assigned.
16
17
Project Engineering
The Secrets of Success for PEs
Organization Planning Communication Vigilance - Fact based decision making
18
Functional Manager
There is an obligation for Functional Manager to:
Contracts with PM and PE to provide skills/expertise to meet program requirements during bid process Provide the qualified resources (personnel, facilities, and equipment) necessary to complete the program on time. Work through PEs when getting involved in program work Involved in programs, to provide timely advice on, and to take timely action when there are personnel or program problems Responsible for meeting overhead budget, indirect labor goals, and program commitments
19
Program Manager
There is an obligation for the Program Manager to:
Ultimate responsibility for successful program execution and customer
satisfaction
20
Conduct periodic briefings on program status and related issues or problems Control Account Manager for PM Admin budget PM and PE signoff authority on all drawings and ECNs Facilitate overall efforts for cost/schedule Coordinate resolution of customer-identified issues & problems Customer interface on existing and related new business opportunities
Chief Engineer
There is an obligation for the Chief Engineer to:
Chart and develop the Business Area roadmap. Coordinates and drives customer requirements on key products Support and strategize existing or new technologies. Support and interface with the customer meetings/reviews. Visits customers, users, conferences to understand mission requirements and works to drive innovative system architectures to meet those requirements. Interface with IRAD & BD to ensure efforts budgeted and planned support customer requirements Supports programs concerns/issues (development/production). Work with the Project Engineer and System Engineer on existing programs and new development programs.
21
Systems Engineering
International Council on Systems Engineering (INCOSE) defines systems engineering as:
Systems engineering is an engineering discipline whose responsibility is to create and execute an interdisciplinary process to ensure that the customer and stakeholders needs are satisfied in a high-quality, trustworthy, and cost and schedule efficient manner throughout a systems entire life cycle. This process is usually comprised of the following tasks: State the problem; Investigate alternatives; Model the system; Integrate; Launch the system; Assess performance; and Reevaluate (SIMILAR). The systems engineering process is not sequential. The functions are performed in a parallel and interactive manner.
22
Systems Engineer
There is an obligation for the Systems Engineer to:
Transform an operational need into a description of system performance parameters and a system configuration through the use of an iterative process of definition, synthesis, analysis, design, test and evaluation, and validation. Integrate related technical parameters and ensure the compatibility of all physical, functional, and program interface. This shall be conducted in a manner that optimizes the total definition and design.
23
Roles/Interface
Chief Engineer Program Manager
PM Checklist Uphold customer relationships Responsible Pgm cost & schedule Supports monthly Status Provides program oversight/leadership Attend customer meetings/reviews Strategize Attend customer meetings/reviews Develops technology roadmap Supports pgm concerns/issues
System Engineer
Establish requirements & flow-down Provides conceptual inputs Generates SEMP Defines Conops Manages operational modes Conducts system modeling Establishes system budgets Conducts sensitivity analysis Identifies KPP Establishes testability requirements Supports Qual/DVT Validates & reviews data Provide technical oversight Conducts/supports Peer reviews Supports program reviews
Project Engineer
24
Establish engineering schedule Assemble engineering team Conduct/oversee peer reviews Support program reviews Monthly Technical Project Status Provide program oversight Responsible for the SEMP Identify risk & uncertainty Responsible for Integration and Qual Attends customer meetings/reviews All documentation & program close-out
Interaction
The Project Engineer, Chief Engineer, and Systems Engineer all have the same goals to provide the best product for our customers. All three groups must work together to achieve this goal
Chief Engineer
System Engineer
Project Engineer
Program Manager
25
Anticipate customer requirements and expectations Manage customer expectations Translate customer needs into specific actions Obtain and respond to customer feedback Open, candid communication develops trust
26
Meetings / Information
Based on the size and maturity of the program, each PE shall be held responsible for conducting the standard reviews (PSDR, PM checklist (30-day kickoff), SRR, SDR, PDR, CDR, TRR, and PRR) All PM support monthly All Program Reviews. The PE are asked to support their PM during Business Area Reviews In addition, PE shall communicate the health of their program at monthly Technical Program Review and/or Engineering Management Reviews If a program experiences significant interruption whether it cost, schedule, technical, or other this information needs to be communicated up the chain of command as expediently as possible
27
Integrity
The PE is the closest to the program and is typically knowledgeable
across all the disciplines. It is the obligation of the team members and the PE to voice issues and concerns as they arise on programs.
The PE represent:
Quality Customer Satisfaction Leadership Integrity People Suppliers
28
Closing Thoughts.
The PE is a KEY member of the Program Team, with a very difficult job Be a Leader
Team builder that displays a commitment and passion Results and detailed oriented, with a sense of urgency Thinking about both today AND tomorrow
Recognize that you own all of the engineering activities, including cost, schedule and technical performance Learn how to balance and prioritize your time
Focus on ramifications if you chose incorrectly
29
Summary
Project Engineers wear many hats and typically do what is needed to get the job done It is not easy being a PE
90% of the program problems and issues are aired while only 10% of the good issues are ever raised
Challenged budgets, manpower issues, and short schedules only contribute to the joy of PEs There is a great deal of satisfaction seeing a program successfully complete and transition to production or sustain production to support the war fighter But with all that said:
31