Amendment_0001_to_Solicitation_N68335-16-R-0020_(ALRE_ _EAF_PM_Support).docx

N68335-16-R-0020

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

AMENDMENT 001

Amendment 0001 to this solicitation is to incorporate the below Government responses to questions received from vendors regarding this solicitation, and to update Section L in response to those questions.

All other information remains unchanged.

The closing date for this solicitation is hereby extended to 4 PM EST 4 April 2016. Section A has been updated accordingly to reflect the new submission deadline.

VENDOR QUESTIONS & ANSWERS

Question 1:

In Section L, Part B, Subsection 2.1.1.4 of the solicitation under the Senior Program Analyst labor category, education, there is requirement for Level 3 IA certification. However, there is no definition of the requirements for this certification in the solicitation and there does not appear to be a common universal definition for this certification, for example like there is for a Microsoft Certified Professional. We are familiar with the requirements for a Level 3 IAM Certification but that is usually connected to labor categories that are for highly intensive cyber security/information assurance work, not program analyst support work. Can you provide a definition of what is required for this Level 3 IA certification.

Answer 1:

The requirement for a Level 3 IA Certification has been removed. Section L, Part B, Subsection 2.1.1.4 has been updated accordingly.

Question 2: Section L, Part B, Subsection 4.3 (g) states the following:

Labor Hours: The Government estimate is 156,480 hours for the entire work effort. A work-year is defined as 1920 hours exclusive of holidays and leave.

* Key Positions

Question: The Senior Program Analyst and Senior Program Manager each require yearly part time personnel support. Since the small business team the incumbent has joined will enjoy the inherited advantage of proposing skilled part time employees other offerors are at a significant competitive disadvantage as recruiting these SMEs for part time employment will prove difficult if not impossible. Will the Government consider modifying the requirement so that only full time personnel are needed?

Answer 2:

Part Time PM's are required in order to provide the required support to different programs; accordingly, the requirement for Senior Program Analyst and Senior Program Manager remains unchanged.

Question 3:

Section L, Part B, Subsection 2.1.1.2 of the solicitation states:

2.1.1.2 Labor category information. The offeror shall submit labor category titles, functional responsibilities and labor qualifications for all key and non-key labor categories proposed under the prospective contract and that meet the minimum qualifications stated in the SOW if applicable. The labor category title shall be consistent throughout the proposal. Functional responsibilities shall include the principal duties to be performed under that labor category on the prospective contract. Labor qualifications shall include experience and/or education requirements for all labor categories proposed. The labor qualification information proposed will be incorporated by reference into the resulting contract, thereby becoming the standards for use during performance of the effort.

Section L, Part B, Subsection 2.1.1.4 of the RFP further states:

2.1.1.4 The labor categories for this solicitation are as follows:

<< Four labor categories and descriptions are given>>

Further, Section L, Part B, Subsection 4.3 paragraph (g) states

Labor Hours: The Government estimate is 156,480 hours for the entire work effort. A work-year is defined as 1920 hours exclusive of holidays and leave.

Question: If Section L, Part B, Subsection 4.3 paragraph (g) specifically delineates labor category titles and Section L, Part B, Subsection 2.1.1.4 specifically delineates labor category titles, functional responsibilities, and labor qualifications for all key and non-key labor categories proposed, why are offerors required to submit, under Section L, Part B, Subsection 2.1.1.2, “labor category titles, functional responsibilities and labor qualifications for all key and non-key labor categories proposed”.

Answer 3:

The Requirement under Section L, Part B, Subsection 2.1.1.2 for Offerors to provide labor category titles, functional responsibilities, and labor qualifications for all key and non-key labor categories proposed is hereby removed from the solicitation. Section L, Part B is updated accordingly.

Question 4:

In Section L, Part A, Subsection 3.0 PROPOSAL CONTENT AND VOLUMES of the solicitation, the third column in the table is named “Suggested Page Limit”. Is the offeror permitted to exceed the “Suggested Page Limit”?

Answer 4:

The page limits for each proposal volume set forth in the table in Section 3.0 are firm maximum limits. As stated in Subsection 3.0, proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation. Accordingly, the heading in the third column of the table in Section L, Part A, Subsection 3.0 of the solicitation is hereby revised from “Suggested Page Limit” to “Page Limit”.

Question 5:

The last paragraph in Section L, Part A, Subsection 2.0 of the solicitation states: “The Offeror will provide one complete copy of the written proposal to the Procuring Contracting Officer (PCO)…”

The table in Section L, Part A, Subsection 3.0, fourth column (“Copies Required”) requires multiple copies.

1. Please identify the PCO and contact data

2. Are all originals and copies to be sent to the PCO? If not is one copy to be sent to the PCO and the originals and multiple copies to another person(s)?

Answer 5:

All originals and copies of all proposal volumes, both paper copies and electronic copies, are to be submitted to the Point of Contact identified in Section L, Part A, Subsection 4.0 of the solicitation. The last paragraph of Section L, Part A, Subsection 2.0 is hereby revised for clarification purposes as follows (changes in bold):

In addition to the paper copies of each proposal volume specified in Section L, Part A, Subsection 3.0 below, the Offeror will provide one complete electronic copy of each volume of the written proposal to the Procuring Contracting Officer (PCO) Point of Contact identified in Section L, Part A, Subsection 4.0. The electronic copy of each volume must be submitted on a CD-ROM as electronic files fully compatible with Microsoft Office 2010 or, and for information not supported by MS Office products, with the latest Adobe Acrobat reader. The Offeror will ensure that the Price/Cost Volume is provided on its own a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.

Question 6:

FAR part 52.219-9 is not incorporated by reference into the solicitation; 52.219-6 is. Section L, Part B, Subsection 2.1.2.6 requires a detailed Small Business Utilization plan. This is a 100% small business set aside acquisition, yet Subsection 2.1.2.6 requires that offerors:

· Demonstrate that its SB strategy is consistent with its SB Subcontracting Plan.

· FAR 52.219-9 (reference)

Further, Subsection 2.1.2.6 states: · Demonstrating Realism through Submission of Reports: To demonstrate the realism of the utilization strategy, the Large Business Offeror shall provide copies of the final or most recent SF 294s/Individual Subcontracting Reports (ISRs) for the most current three relevant contracts, that best demonstrate the Offeror's ability to achieve the proposed subcontracting goals. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program, they shall provide copies of three final or most recent SF 295s/Summary Subcontracting Reports (SSRs). Explain how the results shown in the recent SF 295/SSR demonstrates the realism of the plan. The Small Business Offeror may provide this information in a format substantially the same as the ISR or SSR.

Since this is a 52.219-6 acquisition, wholly set aside for small business, is there truly a requirement to submit ISR or SSRs, or would the Government consider removing this requirement?

Answer 6:

The requirement for Demonstrating Realism through Submission of Reports set forth in Section L, Part B, Subsection 2.1.2.6 of the solicitation is hereby removed from the solicitation.

Question 7:

Section L, Part B, Subsection 2.1.1.7 of the Solicitation requires that a Workforce Hour Matrix, Attachment P2, be developed and submitted as part of the proposal. This requirement is a legacy of the Seaport-e proposal system. Additionally, the large number of SOW sections (18) and the small number of Labor Categories (4) makes the differences in labor hours assigned to each SOW section by labor category almost statistically insignificant. Only the government and incumbents have any insight into the actual work assigned historically. That may or may not be consistent for five years into the future.

In the interest of reducing small business man-hours required to submit a proposal, will the Government consider deleting this as a proposal requirement?

Answer 7:

The requirement for submittal of a Workforce Hour Matrix, Attachment P2, is hereby deleted. The solicitation is hereby revised to remove all references to the Workforce Hour Matrix and/or Attachment P2.

Question 8:

The solicitation designates 3 labor categories as Key Positions:

Sr. Program Manager Sr. Program Analyst Program Analyst

Section L, Part B, Subsection 4.3 of the solicitation calls for the following hours by Key Position:

Sr. Program Manager - 5,376 hours Sr. Program Analyst - 14,400 hours Program Analyst - 9,600 hours

How many resumes does the Government require to satisfy the response set forth in Section L, Part B, Subsection 2.1.1.6? Based on a man year being defined as 1,920 hours, it would appear that the following number of resumes are required:

Sr. Program Manager = 2.8 man years = 3 resumes Sr. Program Analyst = 7.5 man years = 8 resumes Program Analyst = 5 man years = 5 resumes

Please clarify if the above is the correct understanding of the required number of resumes.

Answer 8:

The above understanding of the required number of resumes is correct: 3 resumes for Sr. Program Manager; 8 resumes for Sr. Program Analyst; 5 resumes for Program Analyst.

Question 9:

Please confirm that The Senior Program Analyst Labor Category requires a “Level 3 IA certification.”

Answer 9:

As stated in the answer to Question 1 above, the requirement for a Level 3 IA certification has been removed, and Section L, Part B, Subsection 2.1.1.4 is updated accordingly.

Question 10:

In the requirement for an Offeror’s Part Performance references, Section L, Part A, Subsection 3.0 of the Solicitation states "When possible, these contracts should include at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor"

However due to the size of tables provided the page limit is restrictive, as provided the two required for each example means that a team consisting of one prime (5 examples) and one critical teammate (5 examples) are already at the ten page limit without providing any of the required narrative. Instead of a hard 10 page limit we suggest that the government places no page limit on the Past Performance volume but incorporates a 2 page limit per reference with a limit to the number of references you can use, for example, require at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor but no more than 7 contracts for the Prime, 6 contracts for the critical team member, and 3 contracts per principal subcontractor.

Answer 10:

The page limit for Volume 3, Past Performance, is hereby deleted and replaced by a 1-page limit per Past Performance reference submitted. The chart in Section L, Part A, Subsection 3.0 is hereby updated accordingly.

Question 11:

With regard to the required qualifications for the "Senior Program Analyst (GS-13 Equivalent) (Key Position)" labor category in Section L, Part B, Subsection 2.1.1.4 of the solicitation, can an employee be proposed who is in the process of obtaining the certification with the understanding that it will be obtained by contract award? If not, requiring the certification at the time of proposal greatly disadvantages non incumbent personnel.

Answer 11:

Yes, a proposed employee can obtain the certification during the solicitation process, with the understanding that it will be obtained by contract award.

Question 12:

Section L, Part B, Subsection 2.1.1.1 of the solicitation states, "The offeror is forewarned that it may receive a weakness if it proposes the predominance of a labor category or SOW section tasking using prospective or contingent hire employees and the evaluation team deems this a risk to successful performance."

If an Offeror does not have access to incumbent employees and is therefore obliged to propose the predominance of a labor category or SOW section tasking using prospective or contingent hire employees it is being placed at an unfair competitive advantage. Will the Government consider removing this requirement?

Answer 12:

No, the Government will not consider removing this from the requirement. A “contingent hire” is an individual who has committed, under a signed letter of intent, to being employed by the offeror if the offeror is awarded the contract. A “prospective hire” is an individual that the offeror has committed to hiring if the offeror is awarded the contract whose identity may not be known until after task order award.

The following have been modified:

POINTS OF CONTACT

Proposals under NAWCADLKE’s Request for Proposal (RFP) number N68335-16-R-0020 shall be submitted prior to 4:00 pm EST 4 April 2016 to:

Naval Air Warfare Center Aircraft Division Hwy 547 Bldg 562-3 Rm 307 Attn: Tammy Fossa 25223

JBMDL, NJ 08733

1.0 General Information

1.1 This solicitation is reserved as a 100% small business set-aside on the Federal Business Opportunities (FedBizOpps) website. This solicitation is for a Cost Plus Fixed Fee five (5) Year Indefinite Delivery Indefinite Quantity (IDIQ) contract. The North American Industry Classification System (NAICS) code for this requirement is 541330.

1.2 Offerors may submit questions requesting clarification of solicitation requirements to the FedBizOpps website under this solicitation announcement. All questions will be consolidated and answers will be sent to all offerors via the FedBizOpps website. The Offeror is expected to comply with all requirements of the RFP.

1.3 The Product Service Code (PSC) for this requirement is R408

1.4 Proposal validity is for a period of 180 days.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

CONTENT OF PROPOSALS

PART A CONTENT OF PROPOSALS

1.0 GENERAL

The Offeror is required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s capability to meet or exceed the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements, and that the Offeror has valid and practical solutions for all requirements and potential risk areas. Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors and or subfactors identified in this solicitation. The Offeror is advised that the Government may incorporate into the final contract enhancing features included in the Offeror’s proposal deemed beneficial to the Government. With the exception of the Price/Cost volume, no cost or pricing information should appear in any volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. The Offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the price/cost proposal without opening discussions. Statements that the prospective Offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may render a rating of unacceptable. For the purpose of this solicitation, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects of relevance include the type of effort (e.g., development, production, repair), the type of requirements (e.g., weapon systems, information systems, engineering services, scheduled depot maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the company that will perform the work, and degree of participation by principal subcontractors, team members, or critical team members. Recency is defined as performance within 5 years of the date of this proposal submission.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor or subfactor clearly may be considered a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Offeror is expected to comply with all requirements of the RFP. The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal unawardable, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be a deficiency.

Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least 10% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract. “Team member” is defined as those entities that make up a joint venture or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. “Critical team member” is defined as those entities of the Offeror that perform a critical function in the performance of the resulting contract, whether it is technical or financial, and/or that have important roles in any high or medium risk areas identified in the Offeror’s proposal.

2.0 PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 pt normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented.

In addition to the paper copies of each proposal volume specified in Section L, Part A, Subsection 3.0 below, the Offeror will provide one complete electronic copy of each volume of the written proposal to the Procuring Contracting Officer (PCO) Point of Contact identified in Section L, Part A, Subsection 4.0. The electronic copy of each volume must be submitted on a CD-ROM as electronic files fully compatible with Microsoft Office 2010 or, and for information not supported by MS Office products, with the latest Adobe Acrobat reader. The Offeror will ensure that the Price/Cost Volume is provided on its own a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.

3.0 PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation Page limitations for each volume if any, are also specified in the table below; title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation.

1 Original/5 Copies

2.1.1 Workforce

Each volume shall contain the following information:

4.0 PROPOSAL SUBMISSION:

Clearly mark all packages with the solicitation number. The submission date for the original proposal,shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. However, Offeror shall also submit copies of Volume (3) Past Performance information in paragraphs 3.1 and 3.2 and Volume I, Executive Summary “Offeror’s Summary Table”, 1.0 (ii) two weeks prior to the submission date/time specified in Block 9 of Standard Form 33 of the RFP.

Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals by facsimile or electronically via email.

Naval Air Systems Command Code: Tammy Fossa AIR-2.5.2.2.3 Hwy 547 Bldg 562, Floor 3, Room 307

JB-MDL, NJ 08733

Solicitation Number: N68335-16-R-0020

Hand carried proposals may be delivered to the address above, attention Tammy Fossa and/or Patrick Smith.

5.0 PROPOSAL PACKAGING:

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Each container shall be single person portable. One container shall include all Original Proposal volumes including the original/signed documents submitted as part of Volume 1 Executive Summary.

Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR-2.101 and 3.104”.

6.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0 SOLICITATION CHANGES

For any changes and additional information for the solicitation please go to Http://www.fbo.gov search by Solicitation Number: N68335-16-R-0020.

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: EXECUTIVE SUMMARY

Note: No cost/pricing information shall be contained in this volume of the proposal.

The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal and strategy. The Offeror shall include the following in this volume:

Contractor Name (Indicate Prime, Team Member or Sub)

2.0 VOLUME 2: Technical Proposal

Note: This volume shall not contain any reference to cost or price aspects of the offer.

2.1 The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal:

2.1.1 Workforce

2.1.1.1 Workforce Qualifications Spreadsheet. The offeror shall complete the attached Workforce Qualifications spreadsheet (Attachment P1) for each current, contingent, and prospective hire employee proposed under this effort. All contingent hires (key and non-key) shall have a letter of intent submitted under Volume 4. The letter of intent is a separate written agreement signed by the potential employee(s) to work for the offeror effective at task order award. Subcontractors and team members shall provide this information either separately or included in the prime contractor’s submission of this document.

The following definitions apply to section 2.1.1: A “contingent hire” is an individual who has committed, under a signed letter of intent, to being employed by the offeror if the offeror is awarded the contract. A “prospective hire” is an individual that the offeror has committed to hiring if the offeror is awarded the contract whose identity may not be known until after task order award.

Note: The offeror is forewarned that it may receive a weakness if it proposes the predominance of a labor category or SOW section tasking using prospective or contingent hire employees and the evaluation team deems this a risk to successful performance. In addition, the Offeror is warned that all changes to key personnel from the proposal must be approved by the Government Contracting Officer.

Performance under this contract requires that all personnel must be United States citizens and will require, at a minimum, a SECRET clearance or interim SECRET clearance at the time of in processing during the transition period.

2.1.1.2 Labor category information. The offeror shall submit labor category titles, functional responsibilities and labor qualifications for all key and non-key labor categories proposed under the prospective contract and that meet the minimum qualifications stated in the SOW if applicable. The labor category title shall be consistent throughout the proposal. Functional responsibilities shall include the principal duties to be performed under that labor category on the prospective contract. Labor qualifications shall include experience and/or education requirements for all labor categories proposed. The labor qualification information proposed will be incorporated by reference into the resulting contract, thereby becoming the standards for use during performance of the effort.

2.1.1.3 Key Labor Categories Offerors who do not identify sufficient key personnel to meet the technical requirements of the solicitation will be rated as unacceptable. All college degrees must be from an accredited college or university. The Government may check educational background to verify degrees or certifications received.

2.1.1.4 The labor categories for this solicitation are as follows:

SENIOR PROGRAM MANAGER (GS-14 Equivalent) (Key Position)

Proposed Function: Acts as the overall lead, manager and administrator for the contracted effort of ACAT I and II programs or manages across multiple teams. Directs efforts of cross-competency team(s) to include contractors at multiple locations. Serves as the primary interface and point of contact with Government program authorities and representatives on technical and program/project issues. Regularly briefs senior leadership on program status and milestones. Oversees contractor personnel program/project operations by developing procedures, planning and directing execution of the technical, programming, maintenance and administrative support effort and monitoring and reporting progress. Manages acquisition and employment of program/project resources and controls financial and administrative aspects of the program/project with respect to contract requirements.

Education: MS or MA degree in a Business, Management, ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of experience, beyond years of experience stated below, can be substituted for an MS or MA degree.

Experience: At least twelve (12) years of professional experience in the Defense acquisition, three (3) years of which must have been in the previous six (6) years, in support of Navy Acquisition management; and a minimum of three (3) years supervisory experience. Experience with aircraft systems, hardware and software, configuration control, test and evaluation, systems integration, and systems supportability. Experience in initiating and maintaining technical direction within broad program objectives directly related to aircraft systems, hardware and software, configuration control, test and evaluation, systems integration, and systems supportability. Experience managing different phases of weapon system acquisition, including Concept Development, SD&D. Knowledgeable of acquisition policies and procedures. Demonstrated knowledge of and experience with the requirements of the DOD 5000 series. Demonstrated ability to work with large and diverse teams and the ability to effectively provide guidance, direction, and supervision in all areas of contracted effort such as program management, systems engineering, major system acquisitions, and financial management.

SENIOR PROGRAM ANALYST (GS-13 Equivalent) (Key Position)

Proposed Function: Performs critical program management, technical, or business analysis of major DoD acquisition systems and provides recommendations to ensure program success. Provides program analysis support for all aspects of the program. Participates as a member of and/or supports the overall Program and Integrated Product Teams (IPTs). Collect, complete, organize and interpret technical data and financial information relating to aircraft acquisition and product programs. Tracks program/project status and schedules. Applies policies and procedures for financial planning.

Education: MS or MA degree in a Business, Management field. ALLOWABLE SUBSTITUTION: A BS or BA degree or PMI certification and an additional three (3) years of experience, beyond years of experience stated below, can be substituted for an MS or MA degree. An additional five (5) years experience, beyond years of experience stated below, may be substituted for the degree requirement.

Experience: At least ten (10) years experience in program management, technical, or business analysis discipline, related to weapon systems acquisition and life cycle management; and a minimum of six (6) years out of 10 years of recent work experience related to analysis and planning. Familiarity with SECNAV, OPNAV, and OSD forms related to PPBS, Military Interdepartmental Procurement Requests, Work Requests, Requisitions, Contract Data Requirements List, and DD254 is required. Demonstrated experience in the program/project status, earned value management and schedules.

PROGRAM ANALYST (GS-12 Equivalent) (Key Position)

Proposed Function: Analyzes program requirements, status, budget and schedules. Performs program management, technical, or business case analyses. Participates as a member of and/or supports the specified Program Integrated Product Teams (IPTs); and IPT directed business meetings. Collect, complete, organize and interpret technical data and financial information relating to aircraft acquisition and product programs. Tracks program/project status and schedules. Applies policies and procedures for financial planning.

Education: BS or BA degree in a Business or Management. ALLOWABLE SUBSTITUTION: An AS or AA degree and an additional four (4) years of experience beyond years of experience stated below ; OR an additional six (6) years of experience beyond years of experience stated below may be substituted for a BS or BA degree.

Background Experience: At least four (4) years of experience in program management, technical or business analysis discipline; and included in the four (4) years, there must be two (2) years professional experience in technical efforts supporting major weapon systems and components development. Demonstrated experience in the program/project status and schedules. Demonstrated knowledge of SECNAV, OPNAV and OSD policy and documentation related to PPBS, life-cycle management of military acquisition programs (as specified in the DoD 5000 series). Must have experience processing program acquisition, funding and contract documentation for military programs.

JUNIOR PROGRAM ANALYST (GS-7 Equivalent)

Proposed Function: Provides program office analysis support. Participates in meetings and supports specified Program Integrated Product Teams (IPTs). Tracks program/project status and schedules, takes minutes, prepares presentations, reports, studies, documentation. Performs tasks under supervision.

Education: AS or AA degree. ALLOWABLE SUBSTITUTION: An additional four (4) years of experience beyond years of experience stated below can be substituted for an AS or AA degree.

Background Experience: At least two (2) years of experience in a business or technical position.

2.1.1.5 Offerers who do not have the specific knowledge and experience identified above should clearly identify all similar and related knowledge and experience (i.e., identify similar software and systems with which the Offerer has worked and clearly identify and discuss the similarities and differences). Offerers should clearly describe all prior corporate and personnel experience which addresses these items and include examples of past experience which demonstrates the claimed experience. It is recognized that the items identified above may not be widely used. Estimates of the time to become fully functional should be included in the Offerer's Technical Proposal.

2.1.1.6 For any proposed Key Personnel provide a resume of the work assignments, training, etc., that demonstrates the experience and specialized qualifications of each key person proposed. Resumes shall contain, at a minimum, the following information:

· Employee name

· Years of employment experience in chronological order including narrative description of duties and responsibilities

· Current position, title and employer

· Educational history

· Institution name, degree or certification earned, and year for all degrees or certifications earned

· Current level of security clearance and status (final, interim, or pending)

2.1.2. Management Plan

2.1.2.1 The offeror shall describe its plan for managing its staff, interfacing with the customer, obtaining feedback on performance from the customer, correcting any deficiencies, recruiting staff, and managing cost, performance, and schedule. In addition, the offeror shall address in detail the following: adequacy of management and resources to support the requirements of the solicitation; processes for managing the contract from start to finish, including the role of senior management and the offeror’s task order manager in product/process quality; plan for early identification and resolution of problems; and a description of the offeror’s communication plan for providing periodic status reports of performance of the assigned tasks and for obtaining feedback from the customer with respect to the customer’s satisfaction/opinion of the offeror’s performance.

2.1.2.2 Usage of Teaming, Personnel, and Subcontractors: Offeror shall address in detail the following: how their proposed subcontractors will be managed to ensure cohesive integration into the overall management approach; how and why selected subcontractor(s) were chosen, which knowledge and skills the offeror will be acquiring through each subcontract, the level of subcontract effort expected; and what percentage of the total proposed contract value represents subcontract awards to small business concerns.

2.1.2.3 Transition Plan. The offeror is required to submit a written narrative delineating a transition plan that ensures a smooth workplace changeover from the incumbent with no loss of service and minimal loss of knowledge. This plan will include a start-up and transition plan for managing the transition from the existing service provider to the successful offeror. The transition plan shall include a schedule which will identify the time (number of days after contract award) that the successful Offeror plans to have all prospective employees on-board and the time (number of days after contract award) that the Offeror intends to be at full operational capability. The services under this solicitation are vital to the Government and must be continued without interruption. The plan should take into consideration the following elements as well as any additional elements deemed necessary by the offeror: Employee transition; Training; Risk Mitigation Strategies; Security Requirements to include OPSEC, facilities clearances and base access; Work Turnover; Quality Assurance; Data Transfer; and Recruiting Plan.

2.1.2.4 Employee Qualification and Retention: Offerors shall present in sufficient detail the following: qualification and retention procedures that would provide workforce improvements and upgrade the skills of highly trained and motivated personnel; and a description of its process for qualifying personnel to perform SOW tasks.

2. 1.2.5 Financial Management and Reporting: The offeror shall describe its project budget, cost accounting and cost tracking system. It shall also describe its usual methods for periodic reporting of the program or project financial status to ensure there are no shortfalls or overruns. This shall include a description of the system used for tracking time and expenses and reporting expenses. The Offeror shall also describe its practices for timely invoicing.

2.1.2.6 Small Business Utilization: Strategies for using Small Business (SB) Concerns. All Offerors shall address their strategies for utilizing SB concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. For purposes of this solicitation, SB shall also include Small Disadvantaged Business, Veteran-Owned SB, Service-Disabled Veteran-Owned SB, HUBZone SB, Women-Owned SB, and Historically Black Colleges or Universities (HBCU) and Minority Institutions (MI). Each subcategory of SB shall be addressed. (This strategy is separate from, but shall be consistent with, the Small Business Subcontracting Plan, if the Plan is required.) In describing its strategy for this solicitation, the Offeror shall, as applicable:

Identify what processes have been implemented to correct past inabilities to meet proposed goals;

2.1.3 Understanding of the work

Provide a written narrative of the offeror’s proposed understanding and capability to perform the requirements of the Statement of Work (SOW). The narrative shall include, but is not limited to, the elements of SOW Paragraph 5.0, titled “Performance Requirements” as follows: Provide a detailed description of the approach, including a detailed step-by-step procedure and methodology which would be used in accomplishing each task; Identify reference documents that would be utilized to perform the SOW; Provide a product outline describing what would be the expected deliverable(s) as a result of the Tasking; and Identify any risk factors that may impact successful performance.

3.0 VOLUME 3: PAST PERFORMANCE

3.1 General

The Offeror shall identify any contracts performed within five years of this proposal submission date which contains efforts performed by the Offeror, Offeror’s principal subcontractors, and critical team members that are relevant to those efforts required in the solicitation. e.g., tasks, complexity, contract type, contract dollar value, etc. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. In general, recent performance will be considered more relevant than older performance. When possible, these contracts should include at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor (as defined in Paragraph 1.0, General Instructions). If proposing as joint venture/single legal entity (JV/SLE), the Offeror should provide the five past performance references for the JV/SLE. If less than the five past performance references are available for the JV/SLE, each member of the JV/SLE should individually submit the five references in addition to their JV/SLE references.

For each contract identified, provide contract data, relevancy, past performance, and systemic improvement information as described below. Demonstrate the relevancy of the Offeror’s, and if applicable, the Offeror’s principal subcontractors’ or critical team members’ past performance and systemic improvements with respect to the solicitation requirements. For each past performance problem identified, describe the status of the systemic improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort had on resolving the problem such that it would not reoccur.

For all contracts identified which do not have CPARS, Reports the Offeror will forward a copy of the Past Performance Questionnaire (Attachment P3) to that contract customer’s PCO, Administrative Contracting Officer, and Program Manager. All questionnaires shall be forwarded within two weeks from the RFP release date with enough lead-time so that responses can be received by the Government concurrent with the Government’s receipt of the Offeror’s Past Performance information submitted as per paragraph 3.1 and 3.2 The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to Tammy Fossa Contract Specialist, at Email Tamara.Fossa@navy.mil, thereby allowing the customer approximately 2 weeks to complete their response. This submittal information is provided at the top of the questionnaires to facilitate the Offeror’s effort in meeting these instructions. The Offeror shall not conduct follow-up actions with regard to this questionnaire. The Government will ensure that the customers have received and will respond to the questionnaires. The Government may send any other questionnaires as necessary. For Contracts that are currently in the CPARS and for which annual reporting has been performed, do not send the Past Performance Questionnaire for services to the customer.

The Offeror shall provide written consent from their principal subcontractors and critical team members that will allow the Government to coordinate their Past Performance issue(s) with the Offeror. If the Offeror does not submit such written consent, then the Government will address any past performance issues directly with the principal subcontractor or critical team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractors and critical team members that do not provide such written consent, provide a point of contact (name, address, phone number, and email address) with which the Government may coordinate these issues and obtain any responses as needed.

The Government may use information other than that provided by the Offeror in their proposals to evaluate past performance. The Government may use Past Performance information obtained from sources other than those identified by the Offeror. The Past Performance Information Reporting System (PPIRS) will be the primary method used to evaluate Past Performance. It is incumbent upon the Offeror to explain the relevance of the data provided. The Government has no duty to search for data to cure the problems it finds in the information provided by the Offeror. The Offeror has the burden of providing thorough and complete past performance information.

(a) Contract Data Provide all the information identified below separately for each contract. Additionally, provide this information electronically as a separate file on CD-ROM, which contains Offeror’s Past Performance proposal in a Word Table in the format depicted below:

Relevant Contract Data

Prime (P), or Sub (S)

1 – Place of Performance should be the same as being proposed in this solicitation. If different please include an explanation.

2 - CPARS (yes/no) - CPARS completion date - on DOD PPAIS (yes/no) (Indicate whether or not any CPARS have been completed and identify the last CPARS completion date and if it is currently on DoD PPAIS) 3 Recency-Efforts performed within the last five years.

4 - Relevancy – Provide a concise assessment of the degree of relevancy that each contract identified has to the solicitation; identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Also provide the Offeror’s assessment of the relevancy of the contract in terms of one of the following ratings: Very Relevant (V), Relevant (R), Somewhat Relevant (S), or Not Relevant (N)

(b) Relevancy -The Offeror shall explain what aspects of the contract are deemed relevant to the proposed contract. At a minimum, identify key or critical tasks of the solicitation and indicate the relevancy of the “past performance” contract to these tasks. Also identify where contract performance took place and provide rationale why it is relevant to the solicitation if the location is different from where the related effort is proposed to take place.

(c) Past Performance Information-The Offeror shall provide a brief description of performance in delivering quality products in each of the following areas: 1) meeting technical requirements, i.e., the quality of technical performance, e.g., performing analysis, design, testing, etc., 2) meeting schedule requirements, i.e., schedule performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., 3) controlling contract cost, i.e., cost performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., and 4) managing the contracted effort, i.e., program management, e.g., cooperation with customer, subcontract management.

(d) Information-Identify those actions taken to resolve past problems. Describe the techniques, elements, and tools used to correct problems and, if…