N00421-10-R-0027-0001.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The number of offeror copies required 3 has been added.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTR., CONDITIONS & NOTICES

PART A GENERAL INSTRUCTIONS

1.1 The North American Industry Classification Code System (NAICS) code for this requirement is 541330.

1.2 This contract will be awarded based upon full and open competition.

1.3 Offerors are 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 approach, expertise, experience and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the offeror has a thorough understanding of the requirements and associated risks and is able, willing and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for all requirements and potential risk areas. Respond to all requirements of the solicitation. Do not alter or rearrange the solicitation. The burden of proof for all the evaluation factors identified in this solicitation rests with the offeror. The offerors are 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 volume, no cost or pricing information should appear in any other volume. Alternate proposals are not acceptable.

1.4 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. It is the responsibility of the offeror to present enough information to allow the various work efforts, support, and management approaches, as well as price, to be meaningfully evaluated without discussions. Statements that the prospective offeror understands, can or will comply with the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate and may render a rating of unsatisfactory. For the purpose of this acquisition, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects or 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 participation of Principal Subcontractors, Team Members, or Critical Team Members.

1.5 The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. Failure to clearly and positively address a specific factor or subfactor 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.

1.6 Offerors are expected to comply with all requirements of the Request For Proposal (RFP). The Government advises offerors that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable and the offeror ineligible for award 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 as defined in FAR 15.001. Each offeror must submit an offer/proposal and other information in strict accordance with these instructions. Each offeror’s submission shall be screened by the Procuring Contracting Officer (PCO) or a designee upon receipt to ensure compliance with the instructions contained in the RFP.

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

1.8 Reserved

1.9 QUESTIONS: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at amber.f.wood@navy.mil. It is requested that all questions be received within fifteen (15) days of the date this solicitation was issued.

2.0 INSTRUCTIONS FOR SUBMISSION OF PROPOSALS

2.1 PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 pt normal font (no reduction permitted), single-spaced with one 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 one 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 one 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.

The offeror will provide one complete copy of the written proposal to the PCO as electronic files fully compatible with Microsoft Office 2000 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 Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content with 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.

The offeror must present its proposal information in a manner that facilitates a one to one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its paragraph number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the offeror may add lower tier subparagraphs. The offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third and fourth parts correspond to the volume, book, section, and element, etc., in offeror’s proposal.

3.0 PROPOSAL CONTENT AND VOLUMES

3.1 Each proposal shall contain the following volumes and sections as specified in the table below.

Each volume of the proposal shall be submitted as one original and additional copies as specified on the SF-33 cover page. Submission of all volumes of the original proposal to the address provided in section 4.2 will determine timeliness of receipt.

Each volume must 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

The offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the offeror’s proposal. The CRM should be a single integrated matrix which cross-references the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Note: This column shall address all paragraphs in Sections xx and xy of the Performance Specification

Volume 2 Technical

Volume 2 Technical

3.2 It is anticipated that adequate price competition exists for this solicitation. Therefore, in accordance with the Federal Acquisition Regulation, certified cost or pricing data is not required to be submitted with this proposal.

4.0 PROPOSAL PACKAGING

The offerors 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. Also, each carton shall be single person portable. However, the Master Set, as described below, shall be packaged separately and marked as the Master Set. 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”. The Master Set shall include all original proposal volumes including the original/signed documents submitted as part of Volume 1 Executive Summary.

4.1 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP.

Proposals shall be submitted via United States Postal Service, commercial carrier, or hand carried to the address provided below. Proposals are not to be submitted by facsimile or electronically via email.

All proposals shall be mailed/delivered to:

Naval Air Warfare Center Aircraft Division, Contracts Department

Building 441 (Attn: Code 2.5.1.3)

Attn: Amber Wood

21893 Bundy Road, Bldg 441

Patuxent River, MD 20670

The outside shipping container shall be marked with RFP# N00421-10-R-0027.

IMPORTANT NOTICE: All packages entering the Consolidated Mail Facility onboard the Naval Air Warfare Center Aircraft Division are being scanned. If the contents of the box/package contains electronic components or media, or otherwise should not be scanned because of potential damage to the contents, the sender/vendor shall mark the box/package with a “DO NOT SCAN” sticker.

5.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

6.0 SOLICITATION CHANGES

For any changes and additional information regarding the solicitation, please go to the Federal Business Opportunities website:

https://www.fbo.gov/index?mode=form&id=224890ed773dafac7a214dd2a69492e2&tab=ntype

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1 – Offer Letter/Section K

1.1 Offer Letter

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

Identify at a minimum the solicitation number, enclosures being transmitted, contractor's name, proposed subcontractors and team members to be utilized under the requirement, the CAGE code, DCMA, DCAA, and DFAS offices for the prime contractor and all proposed subcontractors and team members, a statement regarding Representations and Certifications being incorporated, attached to offer, or available at On-line Representations and Certifications Application (ORCA) at orca.bpn.gov, acknowledgement of solicitation amendments, and acknowledge that the Government requires that offers remain effective for a period of 180 days from receipt of offers as specified in block 9 of the Standard Form 33 (SF 33), Solicitation, Offer and Award. Unless a different period is inserted in block 12 of the SF 33, the offeror agrees to this effective proposal period.

1.2 Complete and submit the following, which will constitute Volume I:

- Standard Form 33 (RFP, page 1), "SOLICITATION/CONTRACT" with blocks 12 through 18 completed.

- Acknowledgement of RFP amendments, by signature on each applicable Standard Form 30.

- Affirmation of no Exceptions, Deviations or Waivers.

1.3 Completed Section K

Complete and submit Section K of the solicitation and state whether information is available on ORCA

1.4 Provide offeror’s authorized contact information as required by NAVAIR Clause 5252.201-9502 CONTRACTOR’S AUTHORIZED CONTRACT COORDINATOR AND TECHNICAL LIAISON.

2.0 VOLUME 2 - TECHNICAL

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

2.1 Workforce

The offeror shall provide the following information:

2.1.1 Workforce Qualifications Spreadsheet (20 page limit)

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 shall have a letter of intent submitted under Volume 2. The letter of intent is a separate written agreement signed by the potential employee(s) to work for the offeror effective at contract 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 contract award.

2.1.2 Labor category information (15 page limit)

The offeror shall submit contractor labor category titles, functional responsibilities and labor qualifications for all key and non-key labor categories proposed under the anticipated contract. The offeror shall indicate how the contractor labor categories correspond to the Government labor categories identified under Section L, paragraph 2.1.4 if they differ. 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 anticipated contract. Labor qualifications shall include experience and/or education requirements for all labor categories proposed. The labor qualification information proposed will be incorporated into Section C in the resulting contract, thereby becoming the standards for use during performance of the effort.

2.1.2.1 Key Labor Categories. The offeror shall submit a list of the proposed key labor categories and applicable personnel.

2.1.3 Key Personnel Résumés or Personnel Data Form (PDF) (2 page limit per résumé or PDF)

2.1.3.1 For any proposed key personnel, the offeror shall provide a résumé of the work assignments, training, etc., that demonstrates the experience and specialized qualifications of each key person proposed. Résumés or PDFs 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.3.2 The Government may check educational background to verify degrees or certifications received.

2.1.4 Government estimated minimum personnel qualifications

2.1.4.1 The contractor shall be responsible for employing personnel having the following levels of education, professional and technical experience, as well as the appropriate level of security clearance. These qualifications are only a baseline. Contractors should strive for technical excellence in personnel by demonstrating experience and qualifications beyond these minimum qualifications.

2.1.4.2 The specialized experience included as part of the required qualifications shall have been obtained in the field of endeavor indicated by the applicable labor categories listed below. The experience indicated in the following labor categories must have been performed during the past five years. In cases requiring experience of more than five years, at least five years of the total experience must be within the past five years. Key personnel are those who will be performing in the Key Labor Categories listed below. The contractor shall provide one résumé or PDF for each key personnel.

2.1.4.3 Personnel must have or be able to obtain the appropriate security clearances as stated on the DD Form 254. One person bid for each of the labor categories annotated with an “*” below shall be capable of obtaining a Secret clearance at the time of award. In addition to these categories, Secret clearances may be required for other labor categories depending on actual tasking throughout the duration on the contract. Proof of U.S. citizenship is required to be permitted access to Government installations, aircraft, and ships.

Note: All required experience for all labor categories may have been obtained cumulatively.

All degrees shall be obtained from an accredited college or university.

LABOR CATEGORIES

Senior R&M Engineer* (Key)

R&M Engineer* (Key)

Junior R&M Engineer

Safety Engineer* (Key)

Safety Technician* (Key)

Computer Specialist

Senior Engineering Technician* (Key)

Junior Engineering Technician

Administrative Assistant

Data Analyst

Program Manager

DEFINITIONS

As used in the minimum personnel qualification descriptions for this contract, the terms indicated shall be defined or their meanings qualified as follows:

- Academic year - a full or complete year of study at a junior college, college, university, or other academic institution toward which at least 30 semester hours or 45 quarter hours of undergraduate study, or 18 semester hours or 27 quarter hours of postgraduate study, were completed.

- Accredited institution - a post-secondary educational institution (junior college, college, university, or technical trade, or professional school) which was approved by an accrediting agency listed as nationally recognized by the U.S. Department of Education.

- Accredited program - an educational program or course of study offered by a post-secondary educational institution which was approved by an accrediting agency listed as nationally recognized by the U.S.

Department of Education.

- Degree - an academic title conferred by an educational institution upon completion of a unified course of study; if not otherwise qualified, the term shall mean a degree at the bachelors, masters, or doctoral levels only.

- Engineering or engineering discipline - when used in relation to educational or work experience requirements, "engineering' shall mean any of the following specific subjects, disciplines, or areas of work experience only: computer, electrical, electronics and engineering technology.

- Experience and years of experience –

a) When used in relation to requirements for past participation in professional work or employment activities, "experience" shall mean full-time (on the basis of a standard forty hour work week) participation, at least one-half of which time was spent performing qualifying functions as a practitioner or employee.

b) When used in relation to requirements for a particular term or period of participation, "years of experience" shall mean full, productive years of participation. Productive years are work years of fifty-two weeks reduced by reasonable amounts of time for holiday, annual, and sick leave. If participation was part-time, or if less than one-half of the standard work week was spent performing qualifying functions, the actual time spent performing qualifying functions may be cumulated to arrive at full years (or years and months) of experience. For example, only the actual number of full days (or full-day equivalents) of duty or drills completed during a year of military reserve participation, or in other qualifying part-time employment or practice, may be cumulated toward years of experience.

Qualifying part-time experience performed in addition to other full-time qualifying employment during the same period of time may be cumulated on a full-time equivalent basis and added to the full-time experience to satisfy a total experience requirement.

- Postgraduate degree - a masters, Ph.D., or other professional degree for which completion of an undergraduate curriculum for receipt of a bachelors degree was a prerequisite.

- Related field - a field of study with similar curriculum but which is referenced by a different name.

SENIOR R&M ENGINEER – KEY

(a) Functions

Applies high-level practical, theoretical, and conceptual R&M principles and practices to current and future issues in the design, development, implementation, and test and evaluation of Naval aircraft, weapons systems, and aircraft support equipment. Serves as a source of state-of-the-art knowledge in R&M theory, probabilistic analysis, R&M modeling, and risk assessment and evaluation. Applies this knowledge to engineering and technical analyses, system integration issues, R&M testing challenges, and other complex problems related to engineering and R&M requirements for aircraft, weapons systems, and aircraft support equipment.

(b) Education

A bachelors degree in engineering, physics, mathematics, electronics, or aeronautics from an accredited college or university.

(c) Experience

At least 10 years of general or practical R&M engineering and technical experience in aircraft, weapons systems, or aircraft support equipment development test and evaluation. Must have experience in solving complex R&M problems through the use of R&M probabilistic analysis, modeling, and risk assessment and evaluation. Understanding of Navy operational and maintenance environments is required. Must have experience in development and operational T&E, including test planning, execution, and reporting, as well as participation in laboratory environmental tests. A masters degree in one of the areas of study indicated in paragraph (b) may be substituted for two years of the minimum general experience requirement.

R&M ENGINEER – KEY

(a) Functions

Applies detailed knowledge of R&M engineering principles and procedures in the design, development, implementation, test and evaluation of Naval aircraft, weapons systems, and aircraft support equipment. Reviews and prepares R&M engineering and technical analyses, reports, change proposals, and other documentation. Applies engineering experience to perform functions such as system integration, configuration management, reliability and maintainability testing, quality assurance testing. Analyzes, designs, develops, tests or evaluates data processing and software related to engineering and R&M functional requirements of aircraft, weapons systems, and aircraft support equipment.

(b) Education

A bachelors degree in engineering, physics, mathematics, electronics, or aeronautics from an accredited college or university.

(c) Experience

At least five years of general or practical engineering experience in R&M engineering associated with aircraft, weapons systems, or aircraft support equipment development, test, and evaluation. Experience in using probability or mathematical based models and analysis techniques. Understanding of Navy operational and maintenance environments is required. Must have experience in development and operational T&E, including test planning, execution, and reporting, as well as participation in laboratory environmental tests. A masters degree in one of the areas of study indicated in paragraph (b) may be substituted for two years of the minimum general experience requirement.

JUNIOR R&M ENGINEER

Applies knowledge of R&M engineering principles and procedures in the design, development, implementation, test and evaluation of Naval aircraft, weapons systems, and aircraft support equipment. Assists in the review and preparation of engineering and technical analyses, reports, change proposals, and other documentation. Applies engineering techniques to perform functions such as system integration, configuration management, reliability and maintainability tests, and qualify assurance testing. Compiles and organizes data and utilizes computerized data analysis software and hardware systems related to engineering and R&M functional requirements of aircraft, weapons systems, and aircraft support equipment.

A bachelors degree in engineering, physics, mathematics, electronics, or aeronautics from an accredited college or university.

Experience

None required.

SAFETY ENGINEER – KEY

Applies detailed knowledge of system safety engineering principles and procedures in the design, development, implementation, test and evaluation of Naval aircraft, weapons systems, and aircraft support equipment to identify hazards. Reviews and prepares engineering and system safety analyses, technical reports, engineering change proposals, and other documentation. Compiles, processes, reduces, and analyzes engineering data and presents results and recommendations.

Education

A bachelors degree in engineering, physics, mathematics, electronics, or aeronautics from an accredited college or university.

(c) Experience

At least five years of general, practical, or engineering experience in aircraft, weapons systems, or aircraft support equipment development, test and evaluation. A masters degree in one of the areas of study indicated in paragraph (b) may be substituted for two years of the minimum general experience requirement.

SAFETY TECHNICIAN – KEY

Applies system safety engineering techniques, principles and precedents to develop, design, modify, install, test and evaluate Naval aircraft, weapons systems, or support equipment to identify hazards. Reviews, analyzes, develops, prepares and applies engineering, technical or maintenance specifications, policies, standards or procedures. Plans and performs tests and evaluations of systems equipment or components. Compiles, processes, reduces, and analyzes engineering data and prepares technical system safety analyses and presents results and recommendations.

A high school or General Equivalency Diploma (GED) graduate. Successful completion of a technical school, trade school, or advanced armed services technical school curriculum or course of study in electronics, avionics, mechanics, or engineering technology; or completion of at least 30 semester hours (or 45 quarter hours) of course studies at an accredited college or university in engineering, scientific, computer sciences, mathematics, or technical curriculum. This education shall have led to the development of basic understanding of aircraft operating principles, theory, skills, and activity related to his/her area of technical specialty.

At least six years of general or practical experience in aircraft, weapons systems, or aircraft support equipment. This experience shall have led to the development of basic understanding of aircraft operating principles, theory, skills, and activities related to his/her area of technical specialty. Military experience in aviation maintenance is applicable and desirable. Experience in technical writing, including preparation of well organized technical documents and reports that included significant analysis and discussion of the subject matter with pertinent conclusions and recommendations is required. The completion of two college level English or technical writing courses (6 semester hours) which required extensive writing may substituted for this writing experience requirement.

COMPUTER SPECIALIST

(a) Functions

Supports the development of software based R&M tool sets and maintains specialty and COTS hardware and software products. Ensures compliance with all Navy and Government applicable standards and directives.

(b) Education

A high school or General Equivalency Diploma (GED) graduate and successful completion of at least 15 semester hours from an accredited college or university in an information technology, mathematics, and/or sciences curriculum.

(c) Experience

Four years of general or practical experience within the information technology field or a related discipline providing support on computer hardware or software systems. Experience with the development of web sites and applications. Completion of a specific certification track, e.g., MCSE, MCSD, Oracle Certification, CISCO Certification, etc. may be substituted for the educational requirement of 15 semester hours or for two years of the general or practical experience requirement.

SENIOR ENGINEERING TECHNICIAN – KEY

Applies engineering techniques, principles and precedents to develop, design, modify, install, test and evaluate Naval aircraft, weapons systems, or aircraft support equipment. Maintains, repairs, inspects, troubleshoots, or programs systems equipment or components. Reviews, analyzes, develops, prepares and applies engineering, technical or maintenance specifications, policies, standards or procedures. Plans and performs test and evaluation of systems equipment or components. Compiles, processes, reduces, and analyzes engineering data and prepares technical reports and presents results and recommendations.

A high school or General Equivalency Diploma (GED) graduate. Successful completion of a technical school, trade school, or advanced armed services technical school curriculum or course of study in electronics, avionics, mechanics, or engineering technology: or completion of at least 30 semester hours (or 45 quarter hours) of course studies at an accredited college or university in an engineering, scientific, computer sciences, mathematics, or technical curriculum.

At least ten years of general or practical experience in aircraft, weapons systems, or aircraft support equipment. This experience shall have led to the development of a strong understanding of basic principles, theory, support and maintenance of aircraft, aircraft systems and equipment, or ground support equipment. Military experience in aviation maintenance is applicable and highly desirable.

JUNIOR ENGINEERING TECHNICIAN

Applies engineering techniques, principles, and precedents to develop, design, modify, install, test and evaluate Naval aircraft, weapons systems, or aircraft support equipment. Maintains, repairs, troubleshoots, or programs systems, equipment, or components. Reviews, analyzes, develops, prepares and applies engineering, technical or maintenance specifications, policies, standards or procedures. Plans and performs tests and evaluations of systems equipment or components. Compiles, processes, reduces, and analyzes engineering data, prepares technical reports, and presents results and recommendations.

A high school or General Equivalency Diploma (GED) graduate.

Experience

At least two years of general or practical experience in aircraft, weapons systems, or aircraft support equipment. This experience shall have led to the development of basic understanding of aircraft operating principles, theory, skills, and activities related to his/her area of technical specialty. Military experience in aviation maintenance is applicable and desirable.

ADMINISTRATIVE ASSISTANT

Conducts administrative and record keeping functions and has knowledge of office management, methods, and procedures in producing and maintaining documentation, correspondence, records, or directives. Reports on matters related to project/program progress and status documentation, budget, finance, property accounting, or personnel management. Produces technical reports and papers, test plans, or other project/program documentation in final format from rough notes or drafts. Applies familiarity with specialized and technical terminology to proofread and correct spelling, grammar and phraseology.

Education

A high school or General Equivalency Diploma (GED) graduate.

(c) Experience

Four years performing general administrative functions. Two years of general experience requirement must be in office management, filing, greeting, and related office equipment operations. One year of experience providing computer word processor support using Microsoft Word with functional experience in Excel and Power Point. Completely familiar with desktop computers and other office equipment, e.g., fax machines, telephones, and copiers.

DATA ANALYST

Conduct data related research on well-established topics in support of a larger analytical effort. Compile and organize data in response to assigned taskings of increasing complexity including the entry of data into a database system. Maintain data files and conduct searches to provide information as part of more in-depth analytical taskings. Perform basic analysis by correlating data from a limited number of sources.

A high school diploma or equivalent training and/or experience.

As this position requires familiarity with the types of data to be processed, at least one year of general or practical experience in aircraft, weapons systems, or aircraft support equipment is necessary. This experience shall have led to the development of basic understanding of aircraft operating principles. Military experience in aviation maintenance is applicable and desirable.

PROGRAM MANAGER

Manages and administers the contract and serves as the primary point of contact between the contractor and the Government on program/project and contract administrative issues. Supervises program/project operation by developing management procedures and controls, planning and directing project execution, and monitoring and reporting progress.

Education

Position requires a bachelors degree in business or a related field from an accredited college or university.

(c) Experience

Minimum of fifteen years of recent and relevant professional experience with weapon systems and operational analysis. Demonstrated aptitude and capacity for conducting management. Experience in directing the integration of a program team with demonstrated experience and success in technical management.

2.2 Understanding of the Work

2.2.1 Performance Based Work Statement Approach (30 page limit)

2.2.1.1 Provide a written narrative of the offeror’s proposed understanding and capability to perform the requirements of the Performance Based Work Statement (PBWS). The narrative shall address the elements set forth below:

2.2.1.1.1 Provide a detailed description of the approach including a detailed step-by-step procedure and methodology which would be used in accomplishing each task

2.2.1.1.2 Identify reference documents that would be utilized to perform the PBWS tasking

2.2.1.1.3 Provide a product outline describing what would be the expected deliverable(s) as a result of the tasking

2.2.1.1.4 Identify any areas that may impact successful performance

2.2.1.1.5 Provide a description of possible areas to be investigated in researching each task

2.2.1.1.6 Implementation plan that includes:

2.2.1.1.6.1 Reserved

2.2.1.1.6.2 Warranty of work

2.2.1.1.6.3 Quality control of work product

2.2.1.1.6.4 Quality assurance plan to monitor performance based metrics

2.2.2 Sample Tasks (5 page limit per task)

2.2.2.1 The offeror shall provide written responses to the sample tasks provided below.

Note: All proposed costs associated with the sample tasks shall only be presented in Volume 4 and shall be in accordance with Section L, paragraph 4.2. The sample tasks are scenarios being used for proposal evaluation purposes only and do not reflect actual task orders planned to be issued.

Sample Task #1

You have been given an aircraft Configuration Definition Document (CDD) with a Built-in-test (BIT) Mean Flight Hour Between False Alarm (MFHBFA) threshold of 40 hours. Your tasking is to create the associated Test and Evaluation Master Plan (TEMP) and vendor specifications inputs. Submit the methodologies, staffing, and cost associated with completing this task. (Note: Cost information to be provided separately in Volume 4.)

Sample Task #2

Given a system with a CDD mean flight hour between failure (MFHBF) threshold of 250 hours and a flight test program of only 100 flight hours, provide the risk assessment and associated mitigation steps for meeting the threshold. You can assume that a "standard" R&M System Development and Demonstration (SD&D) program was required by the SOW which included: R&M Program Planning, Reliability Stress Analysis and Prediction Report, Failure Modes and Effects Analysis, Maintainability and BIT Prediction, Maintainability/BIT Demonstration, Highly Accelerated Life Test (HALT), and Environmental and Performance Qualification Testing. Given that additional flight testing is not an option, would you recommend any additional tasking? The benefits of additional tasking have to be justified and the return on investment provided and explained. Submit the methodologies, staffing, and cost associated with completing this task. (Note: Cost information to be provided separately in Volume 4.)

Sample Task #3

The fleet is complaining that the Mean Time To Repair (MTTR) of a fielded radar system is excessive. You have been tasked with resolving this issue. Submit a technical approach explaining the methodologies and steps that will be taken to research, identify the root causes, and resolve the issue. Also, include staffing and cost associated with completing this task. (Note: Cost information to be provided separately in Volume 4.)

For the Sample Tasks, the offeror shall address each of the following areas in their proposal:

2.2.2.1.1 Unique methods of resolving problems identified in the Sample Tasks above are encouraged, however, be mindful of the need for timely accomplishment of task order objectives with minimal risk to program achievement, schedule and cost. The sample task responses shall include, but not be limited to, the following guidelines:

2.2.2.1.1.1 a description of possible areas to be investigated in researching each task,

2.2.2.1.1.2 a detailed description of the approach including a detailed step-by-step procedure and methodology which would be used in accomplishing each task,

2.2.2.1.1.3 a breakdown of the hours proposed to complete the tasking by labor category

2.2.2.1.1.4 identification of additional information that would be used in accomplishing each task,

2.2.2.1.1.5 a detailed work plan for implementation and

2.2.2.1.1.6 a product outline describing what would be the expected deliverable(s) as a result of each task.

2.3 Management Plan (20 page limit)

The offeror’s management plan shall address the following:

2.3.1 Overall Management Approach

Offerors shall address in sufficient detail the following:

2.3.1.1 adequacy of corporate management and resources to support the technical requirements of the solicitation and ability to function as a viable and productive partner with the Government;

2.3.1.2 proposed management roles of the offeror’s proposed workforce for this requirement;

2.3.1.3 proposed lines of responsibility, authority, and communication through which the tasks will be managed;

2.3.1.4 procedures to be taken to ensure quality and cost control;

2.3.1.5 processes for managing the requirement from start to finish, including the role of program manager in product/process quality and how these functions are accommodated in the acquisition and overhead structures; and

2.3.1.6 plan for early identification and resolution of problems.

2.3.1.7 identification of potential performance risks and proposed risk mitigation strategies

2.3.2 Usage of Teaming, Personnel, and Subcontractors

Offerors shall present in sufficient detail the following:

2.3.2.1 Subcontract management approach detailing how each subcontractor will be managed to ensure cohesive integration into the overall management approach;

2.3.2.2 description of the integration of the teaming partners into the overall management approach and how the offeror will leverage their strengths to increase value to the customer through technical leadership, quality assurance, and process improvement;

2.3.2.3 how and why selected subcontractor(s) were chosen, which knowledge and skills the prime will be acquiring through each subcontract, the level of subcontract effort expected; and

2.3.2.4 how the offeror will maintain control during the performance of work.

2.3.3 Qualification, Recruitment and Retention

Offerors shall present in sufficient detail the following:

2.3.3.1 qualification and recruitment procedures that would provide workforce improvements and upgrade the skills of highly trained and motivated personnel;

2.3.3.2 description of process for qualifying personnel to perform PBWS tasks;

2.3.3.3 explanation of approaches for maintaining technical competence to perform the tasks in the PBWS; and

2.3.3.4 employee retention plan.

2.3.4 Transition Plan

The services under this solicitation are vital to the Government and must be continued without interruption. The offeror is required to submit a written narrative delineating a transition plan that ensures a smooth workplace changeover from an incumbent with no loss of service and minimal loss of corporate knowledge. The plan should take into consideration the following elements as well as any additional elements deemed necessary by the offeror:

2.3.4.1 Work turnover

2.3.4.2 Quality assurance

2.3.4.3 Training

2.3.4.4 Risk mitigation strategies

2.3.4.5 Security requirement to include OPSEC, facility clearances and base access

2.3.4.6 Data transfer

3.0 Volume 3 - Past Performance (10 page limit for Past Performance Matrix)

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

3.1 The offeror shall identify on the Past Performance Matrix (Attachment P3) contracts whose performance is within five years of this proposal submission and contains efforts similar to those efforts (e.g., with regard to tasks, contract type, location, contract dollar value, etc.) required by this solicitation for itself, primary subcontractors, and critical team members. A primary subcontractor is defined as any subcontractor who is providing at least 20% of the total labor cost proposed. 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, and two of the most relevant contracts for each primary subcontractor.

3.2 If a past performance problem has been identified, describe the status of the improvement efforts and, where applicable, demonstrate the impact that the improvement effort had on resolving the problem such that it would not reoccur for each contract identified on the Past Performance Matrix (Attachment P3).

3.3 FOR CONTRACTS THAT ARE CURRENTLY IN THE CONTRACTOR PERFORMANCE ASSESSMENT REPORTING SYSTEM (CPARS), AND FOR WHICH ANNUAL REPORTING HAS BEEN PERFORMED, DO NOT SEND THE PAST PERFORMANCE QUESTIONNAIRE FOR SERVICES TO THE CUSTOMER.

3.4 For contracts that have Contractor Performance Assessment Reports (CPARs) that are more than 12 months old, the offeror will complete items numbered 1 through 8 on page 1 of the Past Performance Questionnaire Package for Services (Attachment P4) and forward it to the contract customer’s Program Manager to address only the items numbered 9 to 15 on page 1. For all contracts identified which do not have CPARs, the offeror will complete items numbered 1 through 8 page 1 of the Past Performance Questionnaire Package for Services (Attachment P4) and forward the 2 pages to that contract customer’s Technical Point of Contact or Contracting Officer’s Representative (COR). 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 paragraphs 3.1 and 3.2. The offeror shall include past performance package instructions to the customers. 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.

3.5 Offerors shall provide written consent from their primary subcontractors that will allow the Government to coordinate their past performance issue(s) with the prime offeror. If offerors do not submit such written consent, then the Government will address any past performance issues directly with the primary subcontractor and the offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any primary 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.

3.6 Offerors are reminded that the Government may use information other than that provided by the offerors 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 does not assume the duty to search for data to cure the problems it finds in the information provided by the offeror. The burden of providing thorough and complete past performance information remains with the offeror.

3.7 If the offeror does not have any past performance, it shall provide an affirmative statement stating it has no past performance. This statement shall be provided in the submittal under Volume 3 Past Performance.

4.0 VOLUME 4 PRICE PROPOSAL (No page limit)

4.1 Complete and submit Section B.

4.2 All cost and/or pricing information shall be contained in Volume 4 only. Offerors shall submit their cost/price proposal utilizing the CLIN Breakout Spreadsheet (Attachment P5). The offeror shall submit a fully completed Attachment P5. For the three sample tasks in paragraph 2.2.2, the offeror shall provide a completed Attachment P5 for each.

4.3 In preparing the cost/price proposal, the offeror shall ensure the submittal is easy to understand and includes the following information:

4.3.1 This solicitation is, and the resulting contract will be, subject to the Service Contract Act of 1965, as amended, and to FAR clause 52.222-41, contained in Section I of this solicitation. Offerors shall propose employee wages in accordance with the attached Wage Determination provided as Attachment 2 in Section J of this solicitation. Attachment 2 also provides a matrix identifying those RFP labor categories which the Government feels are covered by the Wage Determination. As part of the cost/price proposal, the offeror shall furnish the names of the proposed labor categories and the corresponding labor categories from the attached Wage Determination as well as documentation of compliance with the minimum monetary wages and fringe benefits for service employees as specified in the Wage Determination. Offerors are required to submit a total compensation plan setting forth salaries and fringe benefits proposed for employees (including temporary and part time employees) who will work under the contract and are subject to the Act. Escalation on labor should be proposed and addressed.

4.3.1.1 If the offeror’s proposed employees are under a collective bargaining agreement, a copy of the agreement shall be provided.

4.3.2 Provide a narrative that addresses any assumptions made during the preparation of the cost/price proposal and discuss the basis for the cost elements listed below:

4.3.2.1 Labor hours per labor category

4.3.2.2 Direct labor rates by category. The offeror is required to submit labor rates for proposed individuals. If composite or category averages are proposed, provide a breakdown of how rates are developed.