Product Support Manager Handbook
The Program Managers Handbook—Common Practices to Mitigate the. IPT Integrated Product Team. Fielding/Deployment, and Operational Support PM Program Manager.
ILSM Guide to Configuration Management Integrated Logistics Support Manager's Configuration Management Handbook The Project Manager (PJM) has the responsibility of ensuring that configuration management provisions have been adequately addressed within acquisition contracts for training devices. However, the Integrated Logistics Support Manager (ILSM), with inputs from the Engineering competency, has the assignment to implement the policy and procedures of sound configuration management on behalf of the PJM. This handbook has been created to assist ILSM's by providing a brief understanding of configuration management, and will hopefully aid the ILSM in implementing CM on their trainers., roles and responsibilities are located in the Configuration Management Advisor. The handbook has been divided into three separate sections that are under the ILSM's direct control: SOW Requirements, CDRL Requirement, and PCA Requirements. The full Table Of Contents is as follows. 1.0 General 1.1 Technical Progress Reviews & CM 1.2 PCA 1.3 Contractor Configuration Mgmt Plans 1.4 Recommended SOW paragraphs For CM 1.5 Summary of the Four Elements of CM 1.5.1 Configuration Identification 1.5.2 Configuration Control 1.5.3 Configuration Status Accounting 1.5.4 Configuration Audit 2.0 CM CRDLs 2.1 Required CDRLS 2.2 Optional CDRLs 3.0 Configuration Audits 3.1 PCA Team Composition 3.2 PCA Scheduling 3.3 PCA Planning 3.4 PCA Kickoff Meeting 3.5 PCA Checklist 3.6 PCA Closeout Meeting 3.7 Contractual Reqmts/Provisions Section 1 - SOW REQUIREMENTS 1. Coordination with the PJM and SE regarding all CDRLs and SOW paragraphs pertaining to CM is essential to assure that all aspects of ILS and Engineering are covered and not duplicated.
1.1 Technical Progress Reviews and CM. At all Technical Progress reviews during the development of a trainer or modification the ILSM should make sure that the conference agenda contains a presentation of the Contractors CM progress. During these progress reviews the ILSM should ask to see the CSA records and other related CM data. At these progress reviews and at the ILSMT's, the ILSM should reinforce to the Contractor that the following logistics technical documents are under configuration control:. Operation & Maintenance Manuals (O&M). Planned Maintenance Systems (PMS). Commercial Off The Shelf (COTS) manuals.
Instructor Utilization Handbook (IUH). Provisioning Data Base 1.2 Physical Configuration Audit (PCAs). There is no longer a requirement for a deliverable PCA Plan. The ILSM should, however, ensure that the contract schedule contains a PCA if appropriate (the requirement for a PCA is a subjective call based on the size and complexity of the modification/trainer acceptance and should be a project acquisition team decision).
If a PCA is not required, the appropriate paragraph 3.x.4 in the SOW should be tailored to reflect the change. For smaller modifications or trainer acceptance efforts the PCA could be accomplished during one of the ILSMTs or other scheduled meeting prior to shipping or final acceptance. For additional information applicable to NAWCTSD PCA's, see of the Configuration Management Advisor.
The Functional Configuration Audit (FCA) is an engineering responsibility and will not be discussed in this handbook. 1.3 Contractor CM Plans. There is no longer a requirement for a deliverable Configuration Management Plan. Consequently, it is imperative that all ILSM ensure that configuration management planning is being properly addressed by the contractor.
This can be accomplished by the ILSM conveying to prospective bidders, through the solicitation that their proposals will be evaluated on how they intend to accomplish configuration management during the development of the training device/modification. 1.4 Recommended SOW paragraphs for CM. 1.4.1 Referenced Documentation. None 1.4.2 Configuration Management.
Include the following paragraphs in each SOW and tailor as appropriate. 3.x Configuration Management: The Contractor shall establish a configuration management program that addresses all new and/or modified hardware, firmware, software and documentation resulting from this contract. The Contractors CM program shall provide configuration identification, configuration control, configuration status accounting, of all new and/or modified trainer hardware, firmware, software, and documentation including Government Furnished Property for the duration of the contract. 3.x.1 Configuration Identification (CI): The hardware and software configuration of the trainer shall be identified by the Functional Baseline and Product Baseline. The Functional Baseline is defined by the system specification. The Product Baseline is defined by the Engineering Drawings, Associated Parts List, Computer Software Configuration Items, and Engineering and Logistics Life Cycle Documentation. The Contractor shall, in consonance with the Government maintenance concept, select the Configuration Items (CIs) to be identified and assign hierarchical identifiers to each CI, select the configuration documentation to be used to identify each CI, define and document interfaces between CIs, and establish a release system for the control of configuration documentation and computer software source code.
3.x.2 Configuration Control (CC): The hardware and software product baseline shall be controlled by Form, Fit, Function, Interchangeability and Interoperability in consonance with the Government maintenance concept. The Product Baseline shall be controlled and changed using contractor change process and engineering release process. However, proposed changes that impact the Form, Fit, Function, Interchangeability or Interoperability of the current system configuration shall be submitted for approval to the Government in accordance with the Contract Data Requirements List (CDRL).
Changes to the Product Baseline shall result in a common configuration for Government operational use and maintenance activities that provide interchangeability and interoperability in accordance with the Government maintenance concept for the trainer. 3.x.3 Configuration Status Accounting (CSA): All baselines, ECPs, deviations and wavers shall be documented in the contractors configuration status accounting database. 3.x.4 Physical Configuration Audits (PCA): The PCA shall be the formal examination of the as-built configuration of the CI against its design documentation. The PCA for a CI shall not be started unless the FCA for the CI has already been accomplished or is being accomplished concurrent with the PCA.
After successful completion of the audit and establishment of a Product Baseline (PBL), all subsequent changes are processed by formal engineering change action. 3.x.5 Functional Configuration Audit (FCA): This paragraph is an engineering responsibility and must be provided by engineering. 1.5 Summary of the Four Elements of CM. The following paragraphs explain, in general, the purpose of each Configuration Management paragraph to be added to the SOW. 1.5.1 Configuration Identification. This is the process of establishing the baselines, selecting appropriate Configuration Items (CI's) and assuring that these CI's are properly identified.
In general, any item requiring logistics support or designated for separate procurement is a CI. Identification involves labeling and marking of hardware to assure correlation between the documentation, and CI and assignment of hardware serial numbers and lot numbers, as required, to establish CI effectivity for each configuration. The baselines involved with trainer acquisition are Functional and Product. The functional baseline consists primarily of the SOW and the Specification (i.e. System requirements) and is produced by the Government. The Product baseline consists of engineering detail drawings, engineering documentation, ILS documentation, and other technical documentation (physical characteristics) and is produced by the Contractor.
Configuration documentation provides the specific technical description of an item at any point in time. Baselines, plus approved changes to those baselines, constitute the current approved configuration identification.
1.5.2 Configuration Control. Configuration control is the formal method of documenting trainer changes by means of Engineering Change Proposals (ECP's), waivers and deviations. Generally speaking, there are three ways to request a change to a training device. This is usually associated with a change to the Weapon System, and as such the change request originates from the W/S prime contractor, a NADEP facility or some other W/S end user. Theoretically when a W/S ECP goes before the sponsors Change Control Board (CCB) for review we should be on distribution for that ECP so that we can determine if there are any training systems impacts and consequently provide a ROM C<E for inclusion in the sponsors budget projections.
This review should include comments requested from the ISEO or COTR who may be more cognizant of the changes and the effect on the trainer. More often than not, this doesn't happen. Typically the sponsor takes a guess at the training impact and enters a rough cost estimate in order to have a training wedge included in the budget.
And some times the ECP's go through the weapon systems CCB with out any training impact at all (someone just checks the NO box for training impact and pushes the ECP through the board). The result of not getting to review W/S ECPs for training impact is that if the ECP is approved by the weapon system CCB, and funded by the class desk, our trainers aren't included in the allocated funding. It is more difficult to go back and ask for money after the fact than it is to plan for it during the ECP review process.
The other obvious problem with not being part of the W/S ECP (training impact review) is that we tend to get out of configuration with the W/S that we are trying to simulate. TECPs are changes to the training system that are not related to the W/S, for example a change to the host computer, visual system upgrade, etc. And are normally initiated by the training system contractor or NAWCTSD. The acquisition team should review an W/S ECP or TECP for trainer applicability, cost, schedule, etc. TECRs are usually proposed by the USERs, ISEOs, COMS contractors, COTRs, etc. TECRs tend to address reliability and maintainability problems, or discrepancies that the users want corrected in trainer performance or capabilities. TECRs can be submitted via 4720s or by cover letter through the users chain of command.
The bottom line here is that regardless of which of the three methods are used to initiate a proposed change to the trainers configuration baseline they are tracked by the CMSS database. Code 362 logs the ECP/TECP/TECR into the database and notifies the acquisition team of the proposed change by way of the TECCB (Trainer Engineering Change Control Board) Evaluation Input Form. A TECCB Evaluation Input Form is a form that is generated by the CMSS when a modification request is received. It provides information concerning the modification request, such as TECCB number automatically system assigned tracking number, TECCB board date, weapon system designator, device designator, SE, PJM, type of change, change number, change date, priority, and the title of the modification. In addition, the evaluation sheet serves as a tool for the project team to evaluate different aspects of the modification request that may be overlooked. For example, the estimated cost is broken down to reflect in-house travel, material, contractor services and, ultimately, total funds required. The information is obtained and/or reviewed by the members of the project team and results in a recommendation from the PJM and concurrence by the PD (who acts as the chairman of the TECCB).
During review of the TECCB Evaluation Input Form, it is the ILSM's responsibility to ensure that all ILS aspects of the modification have been covered. These would include but are not limited to:. Cost and Lead Time Estimates (C<Es). If a modification is to be accomplished by the ISEO, the ISEO, through coordination with the ILSM, will provide a C<E that estimates the cost associated with the incorporation of the modification. The estimate shall include the cost to update SW/HW, ILS documentation (drawings and publications), spares needed, and identify any necessary COMS involvement. The ILSM is the contact point for development and planning of the logistics elements of the modification in coordination with the ISEO and the PJM. The ILSM, and necessary logistics element managers, will provide developmental support during design and installation and will be responsible for a completed logistics package at modification completion.
NTSCORL 4720/15. Serves as the information transfer medium between a ISEO and/or a SE and a PJM for Cost and Lead Time Estimates for development and installation of a specific modification task.
Contractual Modifications. As a team member, the ILSM provides to the SE the cost associated with all related ILS elements (drawings and publications). The ILSM will coordinate changes to the COMS contract as required. The estimated ILS cost figure derived by the ILSM is added to the engineering cost to reflect the TOTAL cost. Hardware Changes. Any time there is a change to the hardware configuration of a training system there most likely will be changes to the:.
Drawings. O&M manual.
COTS manuals. Provisioning Technical Documentation. and possibly changes to the IUH and PMS cards. Consideration should be given to disposition of the removed hardware. Software Changes. Software changes, although every bit as important, tend to be less obvious from the ILS perspective. These changes are most likely to impact:.
IUH. and possibly the O&M manual.
A TECD is a technical directive utilized to direct the accomplishment and recording of engineering changes to training equipment. The TECD is also used to document the changes which have been incorporated during the development phase by the contractor (baseline) or to document for record purposes those changes incorporated by other than normal procedures. It is the ILSM's responsibility to ensure that all ILS aspects of the modification have been covered. These would include but are not limited to: (1) Documentation Affected. A listing of current documentation that shall require changes based on the modification being incorporated should be included. The ILSM should review this list for ILS impact and ensure it is accurate. (2) Kit Required.
Download igi 2 game setup for windows 7. Change pages or drawings being delivered to the sites as a result of the modification should all be listed. New documentation being created as a result of the modification should be included as well. The ILSM should review this list for ILS impact and ensure it is accurate. Verify all change numbers are correct as well as any version/revision identifiers.
(3) Spares Effectivity. Spares required as a result of the modification need to be identified.
The ILSM should review this list for ILS impact and ensure it is accurate. 1.5.3 Configuration Status Accounting (CSA). The purpose of CSA is to provide an up-to-date accounting of the exact configuration of each device. Status includes part numbers with appropriate revision levels, approved waivers and deviations, and incorporated or unincorporated Engineering Change Proposals (ECP's). This information is helpful to assure that the necessary logistic support elements can be correctly programmed in time to support the Configuration Item (CI). The contractor should be expected to review the data and assure its accuracy.
The contractor should provide CSA information from the contractor's information system to the maximum extent possible. 1.5.4 Configuration Audit. The FCA and PCA are audits designed to verify, to the government, the accuracy and acceptability of the Functional and Product baselines and assure that the hardware is, in fact, built to these baselines. Hence, the FCA and PCA will be conducted by the government, with contractor support, prior to acceptance of a CI.
For additional information applicable to NAWCTSD Configuration Audit's, see of the Configuration Management Advisor. The Functional Configuration Audit is the responsibility of engineering and is conducted for each configuration item for which a separate development or requirements specification has been created. This audit verifies, for the government, the configuration item's performance against its configuration documentation. The Physical Configuration Audit is the formal examination of the as-built configuration of a CI against its design documentation. Following successful completion of the PCA and the establishment of the Product Baseline (PBL), all subsequent changes are processed by formal engineering change action. The PCA includes a detailed audit of engineering drawings, specifications, ILS documentation, and software documentation.
Since the ILSM is responsible for the conduct of the PCA, more details and suggestions for planning and conducting a PCA are offered in the section titled PCA Requirements. Section 2 - CDRL REQUIREMENTS 2. The following are two lists of Configuration Management CDRLs to be considered in trainer acquisition contracts. The first list (required CDRLs) is mandatory and should always be included.
The second list (additional CDRLs) may or may not be required depending upon the specific trainer requirements. Each ILSM should review carefully the need for CDRLs included in the second list. Note additional information relative to CDRL requirements can be found in the Acquisition Guide section. Block (5) of each CDRL, DD Form 1423 should reference the applicable SOW paragraph number as the requirements source vice MIL-STD-973. Additionally, the following statement should be added in Block 16: 'Any military specification or standard which may be referenced by this DID shall be considered for information only'. 2.1 Required CDRLs.
DID DID# Conference Agendas DI-ADMN-81249A Conference Minutes DI-ADMN-81250A Configuration Audit Summary Report DI-CMAN-81022C Section 3 - PCA REQUIREMENTS 3.1 PCA Team Composition. The ILSM will serve as the lead for the conduct of PCAs. Assistance and support of other Government personnel may include the Systems Engineer, Logistics Element Managers, In-Service Engineers,Software Engineers, etc. Contractor personnel also support this effort as required. 3.2 PCA Scheduling. The ILSM must carefully review the contract schedule to assure that the PCA is scheduled. When the Contractor notifies the Government of their readiness for a PCA based on contract requirements, the ILSM will coordinate the formal scheduling of the PCA, in close coordination with the PJM and other project team members.
3.3 PCA planning. The Preliminary Audit information identified below should be considered during the planning and preparation for a PCA. PRELIMINARY AUDIT CHECKLIST. Prior to the actual PCA, there are several areas for the ILSM to review to coordinate a smooth PCA as follows:. Review reference designator assignments. Here the ILSM can assess the entire device and make initial team assignments. Assemble government audit team and inform them of upcoming responsibilities.
Discussions with team members of designator assignments could lead to revisions of assignments. Advise contractor of Statement of Limitation of Authority (see below). This will be addressed once again at the kick off meeting, but is important enough to address now to minimize any possibility of omission. Review configuration control system. If documentation is available, a thorough knowledge of the contractor CM system now will save valuable time during the PCA. Provide copies of PCA checklists to each team member.
3.4 PCA Kickoff Meeting. A PCA Kickoff Meeting should be conducted to establish a mutual understanding of PCA requirements between Government and Contractor personnel. A sample checklist of items to be covered during a PCA Kickoff Meeting is provided below.
STATEMENT OF LIMITATION OF AUTHORITY YOU ARE HEREBY NOTIFIED THAT I DO NOT HAVE THE AUTHORITY TO DIRECT YOU IN ANY WAY TO ALTER YOUR OBLIGATIONS OR CHANGE THE STATEMENT OF WORK IN YOUR CONTRACT. FURTHER, IF THE DEPARTMENT OF THE NAVY, AS A RESULT OF THE INFORMATION OBTAINED FROM TODAY'S DISCUSSION, DOES DESIRE TO ALTER YOUR CONTRACT OBLIGATIONS OR TO CHANGE THE CONTRACT STATEMENT OF WORK, CHANGES WILL BE ISSUED IN WRITING AND SIGNED BY THE CONTRACTING OFFICER. YOU SHOULD TAKE NO ACTION ON ANY CHANGE UNLESS AN UNTIL YOU RECEIVE SUCH A CHANGE ORDER.
Ground rules for disassembly of any hardware (in most cases, the contractor will perform all disassembly tasks). Review results of FCA.
Review shortages/deviations/waivers. Review ECP's status. Establish sub-teams and assign areas for PCA. Establish Deficiency Report (DR) rules, numbering. Establish schedule for daily meeting.
3.5 PCA Checklist. The conduct of the PCA will encompass reviews of both engineering drawings, technical documentation, and hardware. A 100% review of all documentation and hardware would be time prohibitive for most large acquisitions.
For this reason, a 10-20% sampling is recommended. If the PCA uncovers few discrepancies and is acceptable with the 10-20% review, it is low risk to assume that the entire device and associated support documentation is also acceptable. The ILSM should, however, reserve the right to expand the review to as much as 100%, if necessary, to assure that the government receives a quality product.
This provision would be applied to any area suspected by the ILSM to be potentially high risk if not reviewed in more detail. Specific list of items to be reviewed is impractical because each contract brings unique devices and criteria.
Each ILSM should create his own PCA checklist tailored to the specific needs of his contract. To aid in the creation of this list, the following is provided as a general guideline. ENGINEERING DRAWING REVIEW During the PCA, engineering drawings will be reviewed for format. Some suggested areas to review are as follows:.
Drawings continuity - Top drawing down to piece part drawing. Parts Lists/Part Numbers. ECP Incorporation/Contract MOD.
ECN's Outstanding. Deviations Requested/Approved. Waivers Requested/Approved. Vendor Manuals.
Compliance with DOD-STD-100 (or ASME Y14.100M) HARDWARE TO BE AUDITED Below are listed suggested items to be included in an ILSM PCA checklist. The list is not all inclusive and should be scrutinized by the ILSM to meet his own specific needs. In general, however, identification markings, decals, labels, and warnings should be included in any review. Also included should be any provisions involving operator safety:.
Unit Numbers/Product Marking. Cable Marking - To/From.
Assembly Number Marking. Reference Designator Marking. ESD Marking/Warning Decals. High Voltage/Safety Decals. Labeling of Functional Controls. Labeling of Jacks/TP's.
Labeling of Fuse Sizes. Labeling of Terminal Boards/Wires.
Trainer ID Tag. Component Identification - Ref. Firmware Identification. Grounding/Bonding. EMI Provisions. PC Boards Ident/Rev Levels.
Spare PC Boards Ident/Rev Levels. Over Temp/Emergency Shutdown System.
GFI Provisions, Personnel Safety, IAW UL-943 (5MA). General Workmanship/Cable Slack TECHNICAL DOCUMENTATION AUDIT Review of all ILS documentation is part of the PCA. The detailed review will be accomplished during the verification period, but a cursory review can be accomplished by reviewing the following;. Review general format to assure that it is in accordance with contract specification (Technical Manual Contract Requirements TMCR). Assure that all manuals are present. Assure that all documents are controlled in accordance with contractor configuration management procedures. DOCUMENTATION: The following documentation shall be available at the PCA.
A list delineating both approved and outstanding changes against the configuration item. Complete shortage list. Operating, maintenance, and illustrated parts breakdown manuals.
List of approved waivers. Manuscript copy of all software CI manuals. Computer Software Version Description Document. Current set of listings and updated design descriptions or other means of design portrayal for each software CI. TASKS: The following tasks shall be accomplished at the PCA.
Drawing Review. Review shortages and unincorporated design changes. Review Software User's Manuals, Software Programmer's Manuals, Computer System Operator's Manual, & Firmware Support Manual, Operation and Maintenance Manual, Planned Maintenance System, and Instructor Utilization Handbook. Review software CIs for the following:.
Preliminary and detailed Software Component design descriptions. Preliminary and detailed Software interface requirements. Data base characteristics, storage allocation charts and timing and sequencing characteristics. 3.6 PCA Close-out Meeting.
Following the review of all hardware/documentation, a final meeting of the PCA team should be convened. A sample of items to be covered during a PCA Close-out Meeting is provided below.
Review all DR's written by PCA Team. Establish schedule for DR workoffs. If PCA is unacceptable (Judgment Call) consult with SE/PJM and arrange for re-audit. Establish ground rules for DR signoffs. Sign PCA certification sheets (as applicable). Although sign off is possible at this time, it is not expected until all DR's have been completed.
Review proposed DD-250 for trainer acceptance. Instruct contractor on submission of minutes and post-audit report. Instruct contractor on submission of final audit report. 3.7 Contractual Requirements/Provisions.
On behalf of the PJM, the ILSM will ensure that provisions for configuration audits are included in each procurement contract, if the size and complexity of the procurement warrants an audit. This is usually accomplished by statement of work tasking and by invoking DI-CMAN-81022C (Configuration Audit Summary Report) in the applicable Contract Data Requirements List, form DD 1423. Last Update: 23 August 2014.
Please enable javascript to play this video. Quick Facts: Sales Managers $117,960 per year $56.71 per hour Bachelor's degree Less than 5 years None 385,500 7% (As fast as average) 28,900 Sales managers direct organizations' sales teams. They set sales goals, analyze data, and develop training programs for organizations’ sales representatives. Sales managers often are required to travel. Most sales managers work full time, and they often have to work additional hours on evenings and weekends. Most sales managers have a bachelor’s degree and work experience as a sales representative.
The median annual wage for sales managers was $117,960 in May 2016. Employment of sales managers is projected to grow 7 percent from 2016 to 2026, about as fast as the average for all occupations. Employment growth of these managers will depend primarily on growth or contraction in the industries that employ them. Explore resources for employment and wages by state and area for sales managers.
Compare the job duties, education, job growth, and pay of sales managers with similar occupations. Learn more about sales managers by visiting additional resources, including O.NET, a source on key characteristics of workers and occupations. Sales managers recruit, hire, and train new members of the sales staff. Sales managers direct organizations' sales teams. They set sales goals, analyze data, and develop training programs for organizations’ sales representatives.
Sales managers have a lot of responsibility, and the position can be stressful. Sales managers held about 385,500 jobs in 2016. The largest employers of sales managers were as follows: Wholesale trade 20% Retail trade 18 Manufacturing 12 Professional, scientific, and technical services 10 Finance and insurance 9 Sales managers have a lot of responsibility, and the position can be stressful. Many sales managers travel to national, regional, and local offices and to dealers’ and distributors’ offices. Work Schedules Most sales managers work full time, and they often have to work additional hours on evenings and weekends. Most sales managers have a bachelor’s degree and previous work experience as a sales representative. Most sales managers have a bachelor’s degree and work experience as a sales representative.
Education Sales managers are typically required to have a bachelor’s degree, although some positions may only require a high school diploma. Courses in business law, management, economics, accounting, finance, mathematics, marketing, and statistics are advantageous. Work Experience in a Related Occupation Work experience is typically required for someone to become a sales manager. The preferred duration varies, but employers usually seek candidates who have at least 1 to 5 years of experience in sales. Sales managers typically enter the occupation from other sales and related occupations, such as,. In small organizations, the number of sales manager positions often is limited, so advancement for sales workers usually comes slowly. In large organizations, promotion may occur more quickly.
Important Qualities Analytical skills. Sales managers must collect and interpret complex data to target the most promising geographic areas and demographic groups, and determine the most effective sales strategies. Communication skills. Sales managers need to work with colleagues and customers, so they must be able to communicate clearly. Customer-service skills. When helping to make a sale, sales managers must listen and respond to the customer’s needs.
Leadership skills. Sales managers must be able to evaluate how their sales staff performs and must develop strategies for meeting sales goals. Note: All Occupations includes all occupations in the U.S.
Bureau of Labor Statistics, Occupational Employment Statistics The median annual wage for sales managers was $117,960 in May 2016. The median wage is the wage at which half the workers in an occupation earned more than that amount and half earned less. The lowest 10 percent earned less than $55,790, and the highest 10 percent earned more than $208,000. In May 2016, the median annual wages for sales managers in the top industries in which they worked were as follows: Finance and insurance $151,030 Professional, scientific, and technical services 141,320 Manufacturing 122,610 Wholesale trade 119,900 Retail trade 85,770 Compensation methods for sales managers vary significantly with the type of organization and the product sold. Most employers use a combination of salary and commissions or salary plus bonuses. Commissions usually are a percentage of the value of sales, whereas bonuses may depend on individual performance, on the performance of all sales workers in the group or district, or on the organization's performance. Most sales managers work full time, and they often have to work additional hours on evenings and weekends.
Note: All Occupations includes all occupations in the U.S. Bureau of Labor Statistics, Employment Projections program Employment of sales managers is projected to grow 7 percent from 2016 to 2026, about as fast as the average for all occupations.
Employment growth of these managers will depend primarily on growth or contraction in the industries that employ them. An effective sales team remains crucial for profitability.
As the economy grows, organizations will focus on generating new sales and will look to their sales strategy as a way to increase competitiveness. Online shopping is expected to continue to increase, meaning more sales will be completed without a sales worker involved in the transaction. However, “brick and mortar” retail stores also are expected to increase their emphasis on customer service as a way to compete with online sellers. Because sales managers will be needed to direct and navigate this mix between online and brick-and-mortar sales, sustained demand is expected for these workers. Job Prospects Similar to other managerial positions, competition for these jobs is expected to be strong as there are more applicants than open positions. Employment projections data for sales managers, 2016-26 Occupational Title SOC Code Employment, 2016 Projected Employment, 2026 Change, 2016-26 Employment by Industry Percent Numeric SOURCE: U.S.
Bureau of Labor Statistics, Employment Projections program Sales managers 11-2022 385,500 414,400 7 28,900. State & Area Data Occupational Employment Statistics (OES) The (OES) program produces employment and wage estimates annually for over 800 occupations. These estimates are available for the nation as a whole, for individual states, and for metropolitan and nonmetropolitan areas.
Product Management Handbook
The link(s) below go to OES data maps for employment and wages by state and area. Projections Central Occupational employment projections are developed for all states by Labor Market Information (LMI) or individual state Employment Projections offices. All state projections data are available. Information on this site allows projected employment growth for an occupation to be compared among states or to be compared within one state. In addition, states may produce projections for areas; there are links to each state’s websites where these data may be retrieved.
CareerOneStop CareerOneStop includes hundreds of with data available by state and metro area. There are links in the left-hand side menu to compare occupational employment by state and occupational wages by local area or metro area. There is also a to search for wages by zip code. Similar Occupations This table shows a list of occupations with job duties that are similar to those of sales managers. Occupation Job Duties ENTRY-LEVEL EDUCATION 2016 MEDIAN PAY Advertising, promotions, and marketing managers plan programs to generate interest in products or services. They work with, and financial staff members. Bachelor's degree $127,560 Advertising sales agents sell advertising space to businesses and individuals.
They contact potential clients, make sales presentations, and maintain client accounts. High school diploma or equivalent $50,380 Market research analysts study market conditions to examine potential sales of a product or service. They help companies understand what products people want, who will buy them, and at what price. Bachelor's degree $62,560 Retail sales workers help customers find products they want and process customers’ payments. There are two types of retail sales workers: retail salespersons, who sell retail merchandise, such as clothing, furniture, and automobiles; and parts salespersons, who sell spare and replacement parts and equipment, especially car parts. No formal educational credential $22,900 Sales engineers sell complex scientific and technological products or services to businesses.
Product Support Manager Handbook
They must have extensive knowledge of the products’ parts and functions and must understand the scientific processes that make these products work. Bachelor's degree $100,000 Wholesale and manufacturing sales representatives sell goods for wholesalers or manufacturers to businesses, government agencies, and other organizations. They contact customers, explain the features of the products they are selling, negotiate prices, and answer any questions that their customers may have about the products. $60,530 Public relations managers plan and direct the creation of material that will maintain or enhance the public image of their employer or client. Fundraising managers coordinate campaigns that bring in donations for their organization.
Bachelor's degree $107,320 Public relations specialists create and maintain a favorable public image for the organization they represent. They craft media releases and develop social media programs to shape public perception of their organization and to increase awareness of its work and goals. Bachelor's degree $58,020 Buyers and purchasing agents buy products and services for organizations to use or resell. Purchasing managers oversee the work of buyers and purchasing agents. Bachelor's degree $64,850 Insurance sales agents contact potential customers and sell one or more types of insurance.
Product Support Manager Jobs
Insurance sales agents explain various insurance policies and help clients choose plans that suit them. High school diploma or equivalent $49,990. Pay The Pay tab describes typical earnings and how workers in the occupation are compensated—annual salaries, hourly wages, commissions, tips, or bonuses. Within every occupation, earnings vary by experience, responsibility, performance, tenure, and geographic area. For most profiles, this tab has a table with wages in the major industries employing the occupation. It does not include pay for self-employed workers, agriculture workers, or workers in private households because these data are not collected by the Occupational Employment Statistics (OES) survey, the source of BLS wage data in the OOH.