N68335-15-R-0147-0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04 EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See Summary of Changes

1. CONTRACT ID CODE PAGE OF PAGES

S 1 16

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY

16B. UNITED STATES OF AMERICA 15C. DATE SIGNED 15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer) (Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N68335-15-R-0147

X 9B. DATED (SEE ITEM 11)

04-Nov-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

U0003

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

25-Nov-2015

CODE

NAVAL AIR WARFARE CENTER AD (LKE)

CODE 2.5.2.2.3 BLDG 562-3

HWY 547

LAKEHURST NJ 08733-5082

N68335 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODE CODE

EMAIL: TEL:

N68335-15-R-0147

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

ADMENDMENT 0003

Amendment 0003 is hereby issued to:

1. Update Section L Part A General Instructions 1.0 General

2. Update Section L Part A General Instructions 2.0 Proposal Format

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

CONTENT OF PROPOSAL

PART A GENERAL INSTRUCTIONS

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

25% 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. Attachment P1 10pt font is accetpable.

The Offeror will provide one complete copy of the written proposal to the Procuring Contracting Officer (PCO) as electronic files fully compatible with Microsoft Office 2010 and for information not supported by MS Office products, with the latest Adobe Acrobat reader on a CD-ROM. The Offeror will ensure that the Price/Cost Volume is provided on 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 suggested page limit will not be reviewed as part of the evaluation.

Volume Number Volume Title Suggested Page Limit Copies Required

1 EXECUTIVE SUMMARY 5 1 Original/ 3 Copies

2 TECHNICAL 1 Original/ 3 Copies

2.1.1 Understanding the Work 25

2.1.2 Workforce

2.1.2.1 Workforce Qualification Spreadsheet 10

2.1.2.2 Labor Category information 5

2.1.2.5 Key Personnel Resumes 2 pages per resume

2.1.2.6 Workforce Hour Matrix 10 pages

2.1.3 Management Plan 15

3 PAST PERFORMANCE 10 1 Original/ 2 Copies

4 PRICE/COST 50 1 Original/ 1 Copies

5 EXCEPTIONS, DEVIATIONS AND

WAIVERS

3 1 Original/ 3 Copies

Each volume shall contain the following information:

Cover and title page

Title of proposal and proposal number as applicable

Offeror’s name, address and POC

RFP number

Proposal volume/book number

Copy number

Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

Use tabs and dividers

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.

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

Katelyn O’Connor AIR-2.5.2.2.3

Hwy 547

Bldg 562, Floor 3, Room 307

JB-MDL, NJ 08733

Solicitation Number: N68335-15-R-0147

Hand carried proposals may be delivered to the address above, attention Katelyn O’Connor.

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-15-R-0147

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: EXECUTIVE SUMMARY

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

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:

i. A concise abstract of the Offeror’s strategy for each of the evaluation criteria contained in the solicitation.

ii. Offeror Summary Table: The Offeror shall complete the table below. The Offeror should include all subcontractors and team members who will be involved with the performance or management of the program work and should list all sites where the work will be performed. If a teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below.

Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name

(Indicate Prime, Team Member or Sub)

Place of

Performance/DUNS # if applicable

Brief Work Description and/or Program

Responsibility

% of Total

Proposed Price

iii. Signed SF33 for basic solicitation and each amendment

iv. Signed Representations, Certifications and Acknowledgements or Registered System for Award

Management (SAM)

v. Affirmation of no Exceptions, Deviations or Waivers if Volume 5 is not being submitted as part of the proposal.

2.0 VOLUME 2: TECHNICAL

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 Understanding 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.

2.1.2 Workforce

http://www.fbo.gov/

2.1.2.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.2: 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 task order. 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 contract 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, within the first six months of the contract, must be approved by the Government Contracting Officer.

2.1.2.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. Offerors who do not identify sufficient key personnel to meet the technical requirements of the SOW will be rated as unacceptable. 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 task order. 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.2.3 Labor Categories. ALL COLLEGE DEGREES MUST BE FROM AN ACCREDITED COLLEGE

OR UNIVERSITY. In the following descriptions, the term "Engineer" refers to a person who has a Bachelor of

Science degree in engineering from an accredited college or university. The term "Technician" refers to an individual who does not possess an engineering degree but rather possesses specialized knowledge and skill gained from experience. The labor categories for this solicitation are as follows:

1) Engineering Technician III

A. Education: High School diploma or equivalent (A bachelor’s degree or Military certification preferred).

B. Experience: A minimum of ten (10) years, with minimum of five (5) years out of the last ten (10) years’ experience must be in performing engineering on DOD systems or military experience. Must be proficient in the utilization of automated office and engineering design tools (experience with MS Excel, MS Power Point, MS

Word, Pro-Engineering and or AUTOCAD preferred). Must have knowledge of DOD equipment management systems (experience with NAVY SEMS system preferred).

2) Engineer/Scientist II

A. Education: Bachelor of Science (BS) or Bachelor of Arts (BA) degree in a "Relevant Engineering/Science Field."

Relevant Engineering/Science fields are Aerospace/Electrical/Mechanical/Computer Engineering or Computer

Science.

B. Experience: At least three (3) years of experience in a "Relevant Engineering/Science Field". Must be proficient in the utilization of office automation tools (experience with MS Excel, MS Power Point and MS Word). Knowledge of engineering design tools such as LABVIEW, ORCAD, AUTOCAD, and Pro-Engineering.

3) Engineer/Scientist III (Electrical Engineer)

A. Education: BS in Electrical Engineering or Equivalent, Masters Preferred.

B. Experience: Minimum six (6) years of experience in the Electrical Engineering Field, of which a minimum of three (3) years experience must be in performing electrical engineering efforts on DOD systems, PE license preferred. Must be proficient in the utilization of automated office and engineering design tools (experience with

MS Excel, MS Power Point, MS Word, Pro-Engineering, LABVIEW and ORCAD preferred).

4) Engineer/Scientist III (Mechanical Engineer)

A. Education: BS in Mechanical Engineering or Equivalent, Masters Preferred.

B. Experience: Minimum six (6) years of experience in the Mechanical Engineering Field, of which a minimum of three (3) years must be in performing mechanical engineering efforts on DOD systems, PE license preferred. Must be proficient in the utilization of automated office and engineering design tools (experience with MS Excel, MS

Power Point, MS Word, LABVIEW, Pro-Engineering and Pro-Mechanical preferred).

5) Engineer/Scientist V (Electrical Engineer) – Key Position

A. Education: Master of Science (MS) or Master of Arts (MA) degree in Electrical Engineering.

ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of work experience employed as an Electrical Engineer can be substituted for an MS or MA degree.

B. Experience: At least ten (10) years of experience in an electrical engineering position, three (3) of which must be directly related to Naval Aviation systems. Demonstrated knowledge in area of engineering expertise. PE license preferred. Must be proficient in the utilization of automated office and engineering design tools (experience with MS

Excel, MS Power Point, MS Word, Pro-Engineering, LABVIEW and ORCAD preferred).

6) Engineer/Scientist V (Mechanical Engineer) – Key Position

A. Education: MS or MA degree in Mechanical or Aerospace Engineering.

ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of work experience as a

Mechanical Engineer can be substituted for an MS or MA degree.

B. Experience: At least ten (10) years of experience in a mechanical or aerospace engineering position, three (3) of which must be directly related to Naval Aviation systems. Demonstrated knowledge in area of engineering expertise. PE license preferred. Must be proficient in the utilization of automated office and engineering design tools (experience with MS Excel, MS Power Point, MS Word, LABVIEW, Pro-Engineering and Pro-Mechanical preferred).

7) Information Assurance Analyst, Senior

A. Education: BS or BA degree in Computer Science, Information Systems or Computer Engineering.

ALLOWABLE SUBSTITUTION: An AS or AA degree and an additional three (3) years of experience can be substituted for a BS or BS degree.

B. Experience: Minimum of seven (7) years of practical CEAT computer security experience in secure network and system design, analysis, procedure/test generation, test execution and implementation of computer/network security mechanisms. This position requires a minimum of five (5) years software IA experience supporting DoD weapon system/SE programs and/or their supporting IT-related networks, hardware, firmware, and software subject to the

Clinger-Cohen Act. Must have demonstrated experience applying DoD and DoN IA and Information Security (IS) policies and standards. Experience is required in assessing system/software risk and vulnerability, developing IA strategies, defining connectivity and interface requirements, preparing IA support documentation packages, supporting IA integration, and performing DITSCAP Certification and Accreditation activities, preferably for

ATS/TPS programs.

8) Engineer/Scientist III (Software Engineer)

A. Education: BS in Software Engineering or Equivalent.

B. Experience: Minimum of six (6) years of experience in a Software Engineering position, of which a minimum of three (3) years experience must be with databases, or with Java, C++, or comparable software language. The effort requires working smoothly on teams with senior and junior personnel in a variety of technical disciplines.

9) Engineer/Scientist V (Software Engineer) – Key Position

A. Education: MS or MA degree in Software or Computer Engineering or Equivalent.

ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of experience can be substituted for an MS or MA degree.

B. Experience: At least ten (10) years of experience in a Software engineering position, three (3) of which must be directly related to Naval Aviation systems (including shipboard) software systems. Demonstrated knowledge in area of Software engineering expertise. The effort encompasses leading the technical efforts of senior and junior personnel in a variety of technical disciplines.

10) Program Analyst

A. Education: BS or BA degree in a Business, Management or Business Administration. ALLOWABLE

SUBSTITUTION: An AS or AA degree and an additional four (4) years of experience.

B. Experience: At least four (4) years of experience in a program management, technical or business analysis discipline, of which at least two (2) years must include 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. Knowledge of engineering design tools such as LABVIEW, ORCAD, Pro-Engineering and Pro-Mechanical preferred. Must have knowledge of DOD equipment management systems (experience with NAVY SEMS system preferred).

11) Program Manager, Senior

A. Education: MS or MA degree in a Business, Management, or MS in an Engineering Discipline. ALLOWABLE

SUBSTITUTION: A BS or BA degree and an additional four (4) years of experience can be substituted for an MS or MA degree.

B. Proposed Experience: At least twelve (12) years of professional experience in Department of 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 support equipment, 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.

2.1.2.4 While an Offeror is not required to possess the skills identified as “preferred” above, an Offeror’s description of Corporate and Personnel experience which includes these elements may be rated more highly than those who do not. Offerors 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

Offeror has worked and clearly identify and discuss the similarities and differences). Offerors 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 Offeror’s Technical

Proposal.

2.1.2.5 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)

The Government may check educational background to verify degrees or certifications received.

2.1.2.6 Workforce Hour Matrix. The offeror shall provide a breakdown of hours for each individual labor category proposed for each ordering year period of performance. The offeror must submit a labor category breakdown that covers the completion of the tasks in the SOW in Section C of the solicitation in accordance with the format in the Workforce Hour Matrix (Attachment P2). Subcontractors’ and team members’ information shall be included under the prime contractor’s submission. Rationale for the proposed labor categories and hours, and mix of personnel shall be provided in a narrative.

2.1.3 Management Plan

2.1.3.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.3.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.3.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.3.4 Financial Management and Reporting. The offeror shall describe its 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.3.5 Small Business Utilization:

2.1.3.5.1 Strategies for using Small Business (SB) Concerns All Offerors (Large and Small Businesses) 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:

· Describe its approach to identifying SB Concerns;

· Describe the extent of participation of SB Concerns on this contract, especially as principal subcontractors;

· Describe the extent of commitment to use such SB Concerns;

· Describe the complexity and variety of the work SB Concerns are to perform;

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

· Demonstrate (Large Business only) that its SB strategy is consistent with its SB Subcontracting Plan.

· Provide targets, expressed as dollars and percentages of total contract values for SB participation. Targets of subcontractors must be listed separately. Note: This calculation is different from the calculation required by FAR

52.219-9 in the Subcontracting Plan, as the Plan requires percentage of subcontracting value;

· 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.

2.1.3.5.2 SB Subcontracting Plans: The Large Business Offeror shall provide its SB Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as Annex 1. If the Offeror is a participant in the

DoD Comprehensive Subcontracting Test Program specified in DFARS 219.7, the Offeror shall describe how SB participation on this contract will contribute to its overall Comprehensive Subcontracting goals. The Offeror shall describe its specific efforts to ensure the resulting contract meets or exceeds proposed goals. These efforts shall include, but are not limited to: sponsoring program specific outreach programs and industry conferences, establishing Mentor-Protégé relationships and using the NAVAIR Office of Small Business Programs website

(http://www.navair.navy.mil/osbp ) to locate small business concerns.

The Subcontracting Plan of the successful Offeror(s) will be reviewed and approved by the PCO prior to contract award. See FAR 19.702 Statutory Requirements (a)(1) regarding failure of the apparent successful Offeror to negotiate and submit a Plan acceptable to the Contracting Officer.) The successful Offeror’s Subcontracting Plan will be incorporated as an attachment to the resultant contract.

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 http://www.navair.navy.mil/osbp 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 Katelyn

O’Connor Contract Specialist, at Email Katelyn.OConnor@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. Contractor Name P1 P2 P3 P4 PX S1 SX

2. Title of contract

3. Contract number/type

4. Procuring agency

5. Description of product or service

6. Period of performance

7. Place of performance 1 and CAGE Code/ DUNs #

8. Dollar value of contract

9. Acquisition Phase(s) of Contract, e.g., SDD, Production

10. CPARs? - CPARS completion date - on DOD PPIRS? 2

11. Recency 3

12. Relevancy 4

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 applicable, how these techniques, elements, and tools will be used during this contract.

Earned Value (If applicable): Provide earned value data generated for that contract, such as Cost Performance

Report Format I, with variances, Cost Performance Index, and Schedule Performance Index. Identify if there were any Over Target Baselines or restructures, and how performance data was impacted. For CPARS data, explain significant differences between earned value measure and CPARS rating, e.g., Exceptional CPARS rating under

Schedule and SPI of 0.85.

Award Fee (If applicable): Provide a summary of the award fee available and earned for each evaluation period over the past three years of an on-going contract, or last three years of a completed contract (both in dollars earned and percentage of available award fee received).

Small Business Concerns Participation Goals (if applicable): Note whether the contract met or exceeded small business, small disadvantaged business, small business HUB Zone, veteran-owned small business, service disabled veteran owned small business, women-owned small business participation and subcontracting goals.

3.2. Past Performance Data Requirements

Provide all the information identified below separately for each contract. Provide a summary of the

Customer’s Points of Contact in a MS Word Table using the format below which is illustrated with an example.

Include an electronic copy of this table in MS Word on a CD.

1. Offeror’s Name (Prime, Principal Sub, or Critical

Team Member, JV/SLE, JV/SLE Member)

1. Contract #,

4. Offeror’s Role (e.g., Customer’s Name 1. CPARS? Recent?

2. Questionnaire # __ Sent?

3. For Subs - Agreement to allow Coordination with

Point of Contact’s Name;

Phone Number, Fax Number and

E-mail address prime or sub)

Prime?

AB (prime) 1. N009,

4. Prime

RYP 1. CPARS: No

2. Questionnaire #1: - Sent 5/4/05

3. N/A

Al (PM)

444-444-4444, fax 555-555- 5555, Al@RYP

1. CPARS: No

2. Questionnaire #2: - Sent

5/4/05

3. N/A

Sue (PCO)

333-333-3333 fax 222-222-2222 Sue@RTP

1. CPARS: No

2. Questionnaire #3: - Sent

5/4/05

3. N/A

Joe (ACO)

111-111-1111 fax 888-888-8888 Joe@ RYP

AB (prime) 1. N008,

4. Sub

L&M 1. CPARS: Yes/No

2. Questionnaire # 1: - Sent 5/4/05

3. N/A

Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@AB

NNB (sub) 1. N007,

4. Prime

RST 1. CPARS: Yes/Yes

2. Questionnaire: - Not Sent

3. Agreement: Yes

Sue (PCO)

333-333-3333 fax 222-222-2222

Sue@NNB

4.0 VOLUME 4: PRICE/COST PROPOSAL

4.1 Volume Content:

(a) This Volume shall contain the information requested below and shall include a copy of Section B with the

Contract Line Item (CLIN) and Sub-CLIN Unit Prices and for evaluation purposes, the Total Prices filled in

(Supplies and/or Services and Prices and/or Costs) using the estimated quantities value in the solicitation and the instructions below. If applicable, Offeror's labor classifications should cross-reference to Department of Labor

(DOL) wage determination classifications as much as possible. In addition, the Offeror shall provide a percentage breakdown of the Offeror’s indirect costs and burdens added to the Government estimates for any and all Cost

Reimbursable CLINs in section B. Section B prices shall be provided separately in one digital data copy in MS

Office 2010 Excel format on CD-ROM media. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

(b) All price/cost and price/cost supporting information shall be contained in section B and the price/cost proposal. No price or pricing information shall be included in any other technical volume including cover letters.

Offeror are responsible for submitting sufficient information to enable the Government to fully evaluate their price/cost proposal.

4.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, any price/cost documentation requested shall not be certified cost or pricing data in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4, in order to ensure a reasonable and realistic price/cost.

Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2. Offeror shall acknowledge the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.

(b) The cost of general purpose items required to conduct normal business operations will not be considered allowable Other Direct Charges. The following types of general purpose costs required to conduct normal business operations are not directly reimbursable: the cost and associated costs for telephones and telephone charges (except for project-related telephone charges for performance of this contract which, per contractor's DCAA-approved accounting system, may be directly reimbursed under communication expenses), modems, typewriters, reproduction machines, word processing equipment, personal computers, computer software, Internet access charges, facsimile machines, commercial carrier charges, pagers, and other general purpose office equipment and office supplies.

(c) The Offeror shall provide sufficient information to support its price/cost as well as an explanation of all ground rules and assumptions that affect the price/cost estimates. Any apparent imbalances in the pricing, high or low proposed prices/costs as compared to historical data, or any other anomalies should be fully explained. Topics to be addressed include, but are not limited to, investments, programmatic variables (e.g., inflation/escalation, location, make/buy decisions, prime/subcontractor relationships, and business base concerns), etc.

4.3 Price/Cost Information:

(a) Reasonableness and Consistency between the Technical and Price/Cost Volumes. Demonstrate that the unit prices and the total proposed price/cost are reasonable, realistic, and commensurate with the work required by the solicitation and the technical and management approaches identified in the Technical Volume of the proposal. Show traceability with the CLINS, SubCLINs, the PWS, proposed effort, proposed manning levels, and the prices/costs.

Refer to specific sections in the Technical Volume as needed to illustrate the consistency between the Price/Cost

Volume and the Technical Volume. The Offeror shall explain any inconsistency between promised performance and price/cost, as well as any appearance of unbalanced pricing, in the proposal.

(b) The Government is not soliciting any investments. However, in order for the Government to properly assess a proposed price/cost that appears low due to a corporate decision to absorb costs, e.g., lower than usual burdens or rates, the Offeror shall fully identify and explain any such investments.

(c) The Offeror shall identify the proposed prices/costs for each CLIN or SLIN as specified in Section B of this solicitation. The Offeror shall provide a fully burdened rate (i.e., "wrap-rate") for each CLIN/SLIN. When completing the Cost/Price Spreadsheet, the offeror (e.g. prime vendor) shall not utilize any fully burdened hourly rates when pricing the labor of its employees.