Amendment 2 to TDPC RFP N61340-11-R-0010.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

(a) Purpose of this amendment is to:

1. Update the Section J attachment list information for Attachments (6) and (10), which were revised on this amendment.

2. Correct the symbol description in Section L, paragraph B1.1.1 (c) from “Parallelogram, with the top irregularly sloping up from left to right - a manual input” to “Right-angled trapezoid, with the top irregularly sloping up from left to right - a manual input”.

3. Revise the solicitation attachments as follows:

A. Attachment (6) - Renumber questions to correct erroneous numbering sequence.

B. Attachment (10) - Remove Administrative Contracting Officer (ACO) from the list of individuals that form is to be submitted to.

Note: (1) Offerors shall not be required to correct numbering on Attachment (6) forms already completed.

(2) Any questionnaire responses received from ACOs will be reviewed by the Government.

Offerors shall not be required to resubmit new Past Performance Questionnaires to customers to replace the forms that were sent out prior to this amendment.

4. Provide the second round of responses to questions submitted by offerors via Attachment (2). Responses are provided as a PDF file attachment to this amendment. Note that responses may not be in the sequence received due to the Government’s vetting process. The government intends to amend the solicitation weekly until all questions received within the allotted time frame are addressed.

(b) All other terms and conditions of the solicitation remain the same.

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

J Section J - List of Documents, Exhibits and Other Attachments

(To be provided during oral presentation)

(To be provided during oral presentation)

(To be provided during oral presentation)

Rev 1

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L

L CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(MAR 2011)

PART A GENERAL INSTRUCTIONS

A1.0 GENERAL

(a) There are 3 distinct Functional Areas within the TDPC statement of work for which an offeror may propose:

(1) Analysis, Design and Evaluation

(2) Development, Production and Implementation

(3) Sustainment

An offeror may propose to one or more Functional Areas. For each Functional Area to which an offeror is interested in proposing, the offeror is required to submit a distinct proposal addressing all 4 evaluation factors for that Functional Area.

(b) Along with an oral presentation, an offeror is required to submit its proposal for each Functional Area it is proposing to with sufficient information concerning all factors 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 repeatable processes, expertise, experience and capability as further described in Sections L and M. All proposals must clearly and convincingly demonstrate that the offeror not only has the experience but also has repeatable processes that may be applied to solve performance/training problems within a Functional Area.

(c) For each Functional Area proposing to, the offeror must respond to all requirements of the solicitation. The offeror should not alter or rearrange its proposal submission prior to the orals. The burden of proof as to technical, experience, past performance, and price reasonableness rests with the offeror. The offerors are advised that the Government may incorporate into the final contract any part of the offeror’s proposal deemed beneficial to the Government. Alternate proposals are not acceptable.

(d) 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 and presentation. It is the responsibility of the offeror to present enough information as well as price, to be meaningfully evaluated without discussions. Though the Government reserves the right to hold discussions, award may be based upon initial offers. Statements that the prospective offeror understands, can or will comply with the solicitation, and paraphrasing the requirements or parts thereof 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. Refer to Section L paragraphs B2.0 through B2.3 for a detailed description of relevancy for each Functional Area.

(e) 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 may be considered a deficiency. The detailed information must be included in the most logical place and summarized and referenced in other areas. Marketing information such as brochures, samples of previous work, examples of graphics extracted from training materials or other forms of presentation to illustrate your multimedia capabilities is neither necessary nor desired. Any brochures, sample of work or copies of products will not be evaluated.

(f) Offerors are expected to comply with all requirements of the 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.

A1.1 PROPOSAL FORMAT

(a) Proposals (except the Technical Volume Visio process flow diagrams addressed in the following paragraph) must be formatted using Arial 12 pt normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted/printed on standard 8.5 x 11 inch paper. Each Volume must be enclosed in a separate 3 ring binder. Within each binder the offeror must separate with dividers each Functional Area that the offeror elects to propose to. Each divider must be labeled with the name of the Functional Area (Example: Functional Area 1 Experience or Functional Area 1 Past Performance) and each page within a Functional Area should be numbered with Functional Area and page numbers. For example, Functional Area 1 page numbering will be 1-1, 1-2, 1-3, while Functional Area 2 will be 2-1, 2-2, 2-3, etc. The binders must be of an appropriate thickness to accommodate the number of pages to allow ease of turning.

(b) 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.

(c) The Technical Volume Visio Process Flow Diagrams shall be provided in a 3-ring binder for each Functional Area proposed to. Content must be formatted to allow for ease of reading on both the paper and the display versions. Material shall be divided by tabs, labeled, and pages numbered as directed in the paragraph above.

A1.2 Electronic Proposal Media

The offeror shall submit all electronic volumes of its proposal on CD-ROM(s) fully compatible with the operating system and applications defined in paragraph A1.3 below. The offeror will ensure that the Price/Other Volume is provided on a separate CD-ROM following the volume content instructions in Section L paragraph B5.0. If a discrepancy exists between the original paper copy of the proposal and the CD-ROM copy, the paper copy will take precedence. The offeror shall submit two copies of the electronic portions of its proposal. One set of CD-ROM disks shall be marked "Master" and another shall be marked "Back-Up." Both sets of CD-ROM disks shall be clearly marked with the offeror's name and address, the point of contact's name and phone number, and proposal volumes contained therein.

A1.3 Operating System and Applications

Electronic proposal files submitted on the CD-ROMs shall be in the appropriate Microsoft Applications. The appropriate Microsoft Applications are Microsoft Word, Microsoft Excel, Microsoft Visio, and Microsoft PowerPoint, for Office 2007. Use of other application software for submission of proposals is prohibited except where specific instructions for non-Office 2007 Applications are provided. However, other applications (e.g., non-Microsoft drawing programs) can be used in proposal preparation as long as the electronic product can still be viewed by the Microsoft application as an object embedded within the document (i.e., Word, Excel, or PowerPoint).

A1.4 Hyperlinks

The offeror shall not use any hyperlinks within Volumes 2, 3, and 4. Volume 1 may use hyperlinks to allow for ease of movement between processes in the oral presentations. The offeror shall not display any marketing information, graphics or any samples of current or previous work.

A1.5 Virus Free Electronic Submission

The offeror shall be responsible for ensuring that its electronic proposal is free of viruses. The offeror shall submit all electronic proposal information which has been checked for viruses. The offeror shall also ensure that any subsequent proposal information (e.g., responses to evaluation notices, and Final Proposal Revisions) is also virus free.

A1.6 Multimedia

The offeror shall not embed sound or video files into the proposal documents. No graphics or animations are allowed to demonstrate the offeror’s multimedia ability.

A2.0 PROPOSAL CONTENT AND VOLUMES

(a) Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. Submission of all volumes to the address provided in Section L Paragraph A3.0 will determine timeliness of receipt. There is no page limit for any Volume.

*Note: All but the Price Volume may be combined into a single CD-ROM. The Price/Other Volume shall be submitted on a separate CD-ROM.

(b) 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

· Use tabs and dividers

A3.0 PROPOSAL SUBMISSION:

(a) 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.

(b) Proposals shall be submitted via United States Postal Service or through a commercial carrier using the address provided below. Proposals are not to be submitted by facsimile or electronically via email. The mailing address to the point of contact is:

Naval Air Warfare Center - Training Systems Division

Attn: Rafael Soberal CODE – 2.5.3.5.2

12350 Research Parkway

Orlando, FL 32826

Solicitation Number: N61340-11-R-0010

Contact information for Mr. Rafael Soberal is as follows:

Telephone number: (407) 380-4077

Facsimile number: (407) 380-8406

E-mail: rafael.soberal@navy.mil

(c) If a proposal or amendment is hand carried, the offeror must complete a visit request no later than two (2) business days prior to delivery of the proposal to the Contract Specialist. Without the visit request, the offeror will not get beyond the security gate to deliver its proposal. A visit request may be obtained by contacting Mr. Rafael Soberal, Contract Specialist, at (407) 380-4077 mail to: rafael.soberal@navy.mil and Mr. Thomas Courtney at (407) 380-4108, mail to: thomas.courtney@navy.mil Upon arrival to NAWCTSD, please contact Mr. Soberal. In the event that Mr. Soberal is not available, please contact the alternate POC, Mr. Thomas Courtney. Do not use the wooden mailbox located on the counter to deposit hand carried proposals. Guards are not authorized to accept proposals.

A3.1 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. 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”, marked for the intended recipient as identified in paragraph A3.0(b) above.

A3.2 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

A3.3 SOLICITATION CHANGES

For any changes and additional information for the solicitation please go to website:

https://www.fbo.gov/index

(Search for Solicitation Number: N61340-11-R-0010)

A3.4 SOLICITATION QUESTIONS

(a) Questions regarding this solicitation shall be submitted in writing using the Solicitation Question/Response Form (Attachment (2)). The Government may answer questions prior to the deadline for proposal submission provided that those questions are received no later than 25 days following the Final RFP release date. Questions shall be e-mailed to rafael.soberal@navy.mil. Answers to questions will be posted via formal RFP amendments.

(b) The Government reserves the right not to respond to any questions concerning this solicitation received after the time frame specified above. Accordingly, offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal preparation cycle.

A3.5 MINIMUM OFFER ACCEPTANCE PERIOD

(a) "Acceptance period," as used in this provision, means the number of calendar days available to the Government for awarding a contract from the date specified in this solicitation for receipt of proposals.

(b) This provision supersedes any language pertaining to the acceptance period that may appear elsewhere in this solicitation.

(c) The Government requires a minimum acceptance period of 270 calendar days.

(d) In the space provided immediately below, offerors may specify a longer acceptance period than the Government's minimum requirement.

The offeror allows the following acceptance period: ______________ calendar days.

(e) An offer allowing less than the Government's minimum acceptance period will be rejected.

(f) The offeror agrees to execute all that it has undertaken to do, in compliance with its offer, if that offer is accepted in writing within --

(1) The acceptance period stated in paragraph (c) of this clause; or

(2) Any longer acceptance period stated in paragraph (d) of this clause.

A4.0 PRE-PROPOSAL CONFERENCE

(a) A Pre-Proposal Conference will be conducted as follows:

Location:

POC/email/Phone/Fax:

Date/Time/Bldg:

NAWCTSD

Rafael Soberal

26 April 2011

3930 Technology Pkwy rafael.soberal@navy.mil

8:00 a.m. – 12:30 p.m.

Orlando, FL 32826

(407) 380-4077 (phone)

Partnership III, Room 321A

(407) 380-8406 (fax)

(b) All prospective offerors are urged to attend the Pre-Proposal Conference. However, each company is restricted to two (2) attendees at the Pre-Proposal Conference. Exact building/room number location for the Pre-Proposal Conference (if changed from above) will be provided by the POC in paragraph (a) above upon receipt of visitor requests (see paragraph (c) below for Visit Request information).

(c) In order to attend the Pre-Proposal Conference, each offeror shall submit visit requests for those company officials who will attend. Send electronic Visit Requests for the Pre-Proposal Conference a minimum of five (5) business days prior to the scheduled visit to the POC listed in paragraph (a) above.

(d) Questions generated at the Pre-Proposal Conference shall be submitted in writing IAW Section L, paragraph A3.4. At no time will the Government answer questions regarding the solicitation to a single potential offeror without providing the answer to all potential offerors. The Government will not engage in “side-bar” question and answer sessions with any individual or potential offeror. Questions submitted formerly (by the date noted in Section L, paragraph A3.4) will be answered and distributed to offerors through RFP amendment.

(e) Failure of a prospective offeror to attend the conference or to submit any questions will be construed to mean that the offeror fully understands all requirements of the solicitation. Prospective offerors are advised that the conference will be held solely for the purpose of explaining the specifications and terms and conditions of this solicitation. The Pre-Proposal Conference will be the only opportunity afforded to any prospective offeror to meet with the Government prior to proposal submission. All prospective offerors are advised that this solicitation will remain unchanged at the conclusion of the conference, unless this solicitation is amended in writing. If an amendment is issued, normal procedures relating to the acknowledgement and receipt of any such amendment shall be applicable. In no event will failure to attend the conference constitute grounds for a claim after award of the contract.

(f) The Government is not responsible for, nor will the Government pay, any portion of the costs associated with attendance at the respective site visit by prospective contractor personnel.

PART B SPECIFIC INSTRUCTIONS

B1.0 VOLUME 1 - TECHNICAL

Within technical, all LOT I offerors shall respond to two elements; the offeror’s technical capability and its Small Business Utilization Strategy. LOT II offerors shall respond to the technical capability element only. For each of the Functional Areas the offeror is proposing to, the Technical Proposal shall include both a written portion (comprised of Technical Visio Process Flow Diagrams and Small Business Utilization Strategy(LOT I offerors only)) and an oral presentation portion. Details are described below.

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

B1.1 TECHNICAL CAPABILITY

A common grouping of processes, sub-processes and the skills needed to execute taskings are identified within each of the Functional Areas. The TDPC approach affords the Government team the opportunity to identify the potential offerors most susceptible of performing the required processes within acceptable risk. Offerors may elect to propose to one or more Functional Areas.

B1.1.1 TECHNICAL VISIO PROCESS FLOW DIAGRAMS

(a) For each Functional Area being pursued by the offeror, a detailed visual depiction of its repeatable processes shall be submitted. The repeatable processes shall be represented in a series of Microsoft Office 2007 Visio process flow diagrams identifying the processes and sub-processes required by the potential prime offeror to perform all work activities that may occur within a Functional Area. Sufficient detail should be provided to effectively communicate how work is accomplished. The Visio process flow diagrams shall identify the offeror’s repeatable processes for implementation of the Instructional Systems Development (ISD) and Human Performance Models. The fully integrated Visio process flow diagrams shall identify the processes / sub-processes, the input / output products of each process, and the labor categories responsible for performing the work activity.

Note: A graphical representation of the ISD model is documented in MIL-HDBK-29612, Part 2.

When the ISD model is discussed herein the following processes are included:

· Analysis

· Design

· Development

· Production

· Implementation

· Evaluation

· Management

· Administration

· Support

· Quality Improvement

· Delivery

(b) The Visio process flow diagrams are to be a common representation of the offeror’s processes. The Visio process flow diagrams are to show the steps in the process as boxes. The boxes are to be ordered by connecting them with arrows. This diagrammatic representation shall give a step-by-step solution for the processes required in each Functional Area. Data shall be represented in these boxes and the arrows connecting them represent direction of the flow of data. The following standardized approach to symbols should be used. If the offeror’s corporate flow diagrams are documented as part of a quality system certification process and deviate from the definitions below, do not rework them. Instead, provide a narrative defining your symbology and rules for construction on the first page of the Volume 1 Technical Proposal.

(c) Symbols definitions are:

· Arrow - an arrow represents control passing from one symbol to another (in the direction of the arrow)

· Cylinder - a data file

· Circles - symbol signaling the start or end of a process

· Parallelogram - input/output

· Diamond - condition or decision containing a Yes/No question

· Right-angled trapezoid, with the top irregularly sloping up from left to right - a manual input

· Rectangle - processing steps

· Rectangle, with a wavy base - a document

· Trapezoid with the longest parallel side at the top - operation or adjustment to process that can only be made manually

(d) In order to speed the review of the flowchart, common rules shall be applied, to include:

· Arrows shall be labeled

· Decisions shall be used when required

· Two or more arrows may be used if a complex decision is required or the decision may be broken-down further, or replaced with the "pre-defined process" symbol

· Connectors shall be used to represent converging paths in the flowchart. Circles will have more than one arrow coming into them but only one going out

· Iterative processes or loops shall have an arrow pointing to another arrow. A loop may consist of a connector where control first enters, processing steps, a conditional with one arrow exiting the loop, and one going back to the connector

· Off-page connectors shall be used to signify a connection to a (part of another) process held on another sheet or screen. All connections shall be presented in order (sequence)

· All processes shall flow from top to bottom and left to right.

B1.1.2 ORAL PRESENTATIONS

(a) An offeror will be required to orally present aspects of its Volume 1 Technical proposal using the Visio process flow diagrams of its repeatable processes delivered as part of Technical Capability. Individual presentations will be conducted for each of the Functional Areas proposed to by the offeror. The oral presentations will be conducted at the Naval Air Warfare Center Training Systems Division in Orlando, Florida. The Contracting Officer will notify all offerors of the date, time and specific location of the oral presentation after the Government receives the offers in response to this solicitation. The Government anticipates that oral presentations will commence as early as two (2) business days after the solicitation closing date. The Government will make random selections when scheduling offerors for the oral presentations with two considerations; the Government will consider the (1) Functional Area(s) proposed and (2) the offeror’s travel requirements when establishing the schedule for the oral presentations. Offerors proposing to more than one Functional Area will be scheduled to complete the oral presentations for all Functional Areas on the same day.

(b) As part of Technical Capability, offerors are required to prepare Microsoft Office 2007 Visio process flow diagrams to facilitate the conduct of oral presentations. The Visio process flow diagrams shall serve as a basis for and facilitate the conduct of the oral presentations in response to the scenario provided, as addressed below, for each Functional Area the offeror has elected to pursue and will demonstrate the implementation of repeatable processes for the conduct of work and development of intermediate and final training products. Visio process flow diagrams, once delivered as part of the offeror’s written technical proposal, may not be altered prior to oral presentations.

(c) During its oral presentation an offeror will be given a scenario and question(s) about the scenario, which would be a typical work problem that may occur at the DO/TO level. The scenario(s) and question(s) for each Functional Area are referenced as Attachments (3), (4), and (5) and will be provided on the day of each offeror’s oral presentation(s). The offeror will be given 30 minutes to organize its speakers and prepare after receiving the scenario. Preparation time will be provided for each scenario if an offeror has elected to pursue more than one Functional Area. The scenario will define the work problem and in the oral presentation, the offeror will describe how it would approach solving the problem through the use of its Visio process flow diagrams. The oral presentations will allow the offeror to demonstrate that it can apply its processes and sub-processes to allow it to manage technical, cost and schedule risks, while solving job performance and/or training problems. Price, cost or fee information shall not be discussed during the oral presentation.

(d) The oral presentation for each individual Functional Area shall not exceed 1 hour. The offeror will not be disrupted by the Government during the conduct of the oral presentation for a Functional Area. At the conclusion of each Functional Area oral presentation, the Government intends to probe capability information from the offeror using the FAR 15.306(a) clarification process. This process will be used to allow the Government to better understand the offeror’s repeatable processes and approach for solving the scenario work problem. This probing period will not constitute discussions, is expected to last no longer than 30 minutes, and is not part of the offeror’s one hour presentation.

(e) If the offeror elects to pursue more than one Functional Area, there will be a 15 minute break after completion of the preceding presentation. After the break, the Government will provide the offeror the scenario and the related questions to the next Functional Area being pursued. The offeror will have 30 minutes to prepare for the second presentation after receipt of the scenario. The same process will be repeated if the offeror elects to pursue a third Functional Area. The offeror’s set-up time for the next presentation and the Government’s time to change the DVDs associated with the filming described in Section L, paragraph B1.1.2 (h) below will not be counted against the time for Functional Area preparation or oral presentation.

(f) The oral presentation team for the offeror shall be full-time personnel, employed by the offeror. No subcontractors shall present or participate in the oral presentations in any way. Accordingly, each presenter will be asked to state how long they have been employed by the offeror and what positions they have held in the last five years. The Government recommends that oral presenters should be knowledgeable in program management, ISD, human performance, and training delivery systems. In selecting oral presentation participants, the government recommends the offeror consider the knowledge and experience level of each individual and his/her ability to problem solve using the ISD and Human Performance models within the framework of its repeatable processes. The oral presentation scenario(s) will not be specific to any customer, service or government agency. The scenario(s) will be tailored to the execution of the ISD and Human Performance models. The offeror shall be allowed no more than four speakers and one additional person that is a non-participating observer for a particular Functional Area; if proposing to more than one Functional Area, the offeror may swap any personnel during the 15 minute break prior to being handed the subsequent scenario(s).

(g) The Government will provide a computer, overhead projector and screen for the offeror’s use. The offeror shall use the Microsoft Visio process flow diagrams delivered as part of Volume 1 to support its oral presentation. The government will ensure the offeror’s Visio files submitted as part of its proposal are preloaded on the computer and ready for presentation. The room will be available to the offeror’s team 15 minutes prior to the delivery of the scenario(s) to allow the offeror’s team to become accustomed to the space and the equipment.

(h) Offerors are notified that the Government will use a digital video camera to make a record of the speakers and the visuals (Visio process flow diagrams) during the oral presentations. The Government will also use the digital video camera to record the Government clarification questions and offeror’s responses. Attendance at the oral presentations by the offeror and its participants will constitute consent for this video recording.

B1.2 SMALL BUSINESS UTILIZATION STRATEGY (LOT I OFFERORS ONLY)

For each Functional Area proposed, the LOT I offerors shall describe their Small Business Utilization Strategy for implementation of the following elements for the individual DO/TO:

(1) The process that will be used to determine the complexity and variety of the work small firms are to perform; and

(2) The process that will be used to ensure maximum practicable utilization of small firms for each DO/TO.

Note: Identification of specific small business utilization and goals will be evaluated at the DO/TO level as requirements materialize.

B2.0 RELEVANCY, VOLUME 2 EXPERIENCE AND VOLUME 3 PAST PERFORMANCE

(a) Offerors shall provide representative contracts demonstrating relevant performance for the Experience and Past Performance Volumes no older than five years from the TDPC proposal due date. Experience and Past Performance information older than 5 years will not be considered relevant. Contracts beginning before the five year period but ending during the five year period will be considered in whole. Relevant work may be previous federal, state or local Government contracts and private/commercial contracts performed which are similar in nature and relevant to the efforts required by this solicitation and described in paragraphs B2.1 through B2.3 below. Information provided should be related to similar programs in the same division, or price centers in which the offeror proposes to perform this effort. The offeror shall only provide work examples that are “Corporate”, meaning that experience has been gained through contracted work vice the experience of its personnel. Recent contracts will be considered more relevant than older contracts.

(b) Relevant is defined as something that has a logical connection with the matter under consideration. Aspects of relevance that will be considered include the ISD Phases, the work processes and sub-processes within a Phase, the training products being delivered, and the work assigned between prime and subcontractors. Relevant projects must require the delivery of products specifically geared to training. Training is defined as the events and activities designed to facilitate the learning and development of new and existing skills for the purpose of improving job performance. Relevant work does not include training devices or simulators, or any work activities performed by podium instructors, Learning Resource Center Facilitators, Contractor Support Services (CSS) performing program support, or any work performed as a schoolhouse manager, administrator, or staff. Work that an offeror performed, as part of a contract, that imparted general knowledge, developed the powers of reasoning and judgment, or generally prepared an individual intellectually for mature life is considered education and is not relevant. Training products vice educational products are relevant for this acquisition.

(c) Relevant work may be from a previous contract as a prime, subcontractor or joint venture. The offeror shall not describe project work performed by other team members, subcontractors, or by individual employee’s experience from previous employment. Work must be performed by the company proposing on the TDPC to be considered relevant. Any work that assigns an individual worker to another contractor for the purpose of augmenting its team is not considered relevant work. Relevant work also does not include body shops where employees were provided to another contractor to perform singular activities (such as graphics or programming). Relevant work shall not be a summary of any of the offeror’s employees’ career experiences while working outside the company. The following data provides offerors descriptive characteristics to be used in determining relevancy for contracts offered as part of the Experience Volume and the Past Performance Volume for each Functional Area.

B2.1 FUNCTIONAL AREA 1 RELEVANT WORK

(a) Relevant work for Functional Area 1 Analysis, Design and Evaluation includes work activities performed by the offeror to identify and analyze organizational, team and individual needs or gaps in performance. Needs or gaps may be identified by analyzing the organization, environment, materiel, resources, manpower, personnel, policy, doctrine, processes, or training. One or more solutions may be identified to fill the need/gap. Relevant work for Functional Area 1 includes the analysis to identify the need or gap and the subsequent processes to design a training intervention or performance support system. The work description for this Functional Area requires the design of training alternatives and training delivery methods, media, strategies, fidelity levels, and interactivity requirements to fill a performance gap, solve a performance deficiency or provide the training /support required to ensure employees can perform work in the intended environment, to the required proficiency.

(b) Any pass through of work that does not require the offeror to perform Functional Area 1 processes and sub-processes including Program Management, Front End Analysis, Training Systems Requirements Analysis, Evaluation, Configuration Management and Quality Control of the intermediate products is not relevant. Direct and indirect training solutions are relevant. Direct training is defined as a performance intervention designed to provide the knowledge and skills in a structured environment. This method is generally referred to as traditional, formal, or live classroom training. Indirect training interventions provide workers with the skills and knowledge they need in the form of performance support tools, job aids, checklists, etc. Solutions other than direct and indirect training solutions are not considered relevant for this evaluation.

B2.2 FUNCTIOANL AREA 2 RELEVANT WORK

(a) Relevant work activities for Functional Area 2 include the Development, Production and Implementation of new training solutions for self-paced, group-paced, learner assessments, and/or performance support systems. The work in this Functional Area is limited to development/production activities such as, (1) developing Course and Lesson Flow Diagrams; (2) constructing scripts and storyboards; (3) developing multimedia assets including text, graphics, animations, audio, video, and simulations; (4) developing production plans, edit decision lists, and production resource requirements documents; (5) programming of development tools and templates for training product development, authoring learning content; (6) developing learner assessments and certification exams; (7) setting up and integrating Learning, Training and Content Management Systems with training products, setting up management system reporting, tracking and scheduling systems, developing and executing a Training System Implementation Plan; and (8) designing, installing and configuring the hardware and software for a fully integrated training system. Relevant work will also include the implementation of the training solutions produced as well as preparation of training the managers, administrators, staff and instructors on the operation and maintenance of the newly developed training system. Functional Area 2 relevant activities also include demonstrated work in the management of multiple production teams working concurrently to produce, deliver and install a fully operational training system that will deliver, track, report, schedule, and manage learning as well as the training system. Relevant work will also include the production of training products that do not require integration with a Learning, Training or Content Management System.

(b) Any pass through of work that does not require the offeror to perform Functional Area 2 processes and sub-processes including Program Management, production of group and self-paced training solutions, and development, installation and test of the integrated training system is not relevant. A contract that requires only the purchase of training system hardware and software (electronic classrooms and learning resource centers including servers, peripherals, computers, and development applications) is not relevant to this Functional Area. Hardware and software procurement must be integral to the development of a total training system by the offeror. Previous contracts that only supported realignment of an organization, modification of organization mission/vision/goal statements, or the modification of operating procedures, policy or doctrine are not relevant work.

B2.3 FUNCTIONAL AREA 3 RELEVANT WORK

(a) Sustainment work requires the modification of self-paced, group-paced, learner assessments, or performance support systems. Relevant work activities, for Sustainment, will include any previous requirement for a contractor to perform an integrated approach to the Analysis, Design, Development, Production, Implementation, and Evaluation of a training system to maintain the currency, accuracy, efficiency and effectiveness This type of relevant work will require the offeror to modify, update, and enhance, or alter a training system that currently is implemented in the Fleet, schoolhouse or a training organization. The sustainment of the training system may have required any type of training product (Lesson Plans, Trainee Guides, Grade Sheets, Briefing Guides, Workbooks, Technical Manuals, and Learner Assessments) to be modified, enhanced or updated. Sustainment may also include activities that required the offeror to only produce the change required by the Government or a Commercial entity. A previous contract that required the full ISD model to be applied to identify, design, develop, implement and evaluate change or an approach that required only production and implementation of customer identified changes are both considered relevant work.

(b) Any pass through of work that does not require the offeror to perform Functional Area 3 processes and sub-processes including Program Management, analysis, design, production, integration and evaluation of an existing training system is not relevant. All work in Sustainment must be for the sole purpose of maintaining currency of the total training system through the application of the ISD model. The need for change may be identified by the Contractor, the training organization, or may be a combination of the two. Relevant work must be for the modification of the total training system and its intermediate training products through the application of the ISD model. To be relevant, all work must include the application of the analysis, design, development, production, implementation and evaluation of intermediate training products within the total training solution.

B3.0 VOLUME 2 EXPERIENCE:

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

(a) For each Functional Area for which the offeror is proposing, the offeror shall provide information on Attachment (6) – Experience Data Input Form. This Form will provide a description of the offeror’s relevant corporate experience relating to the Functional Area relevancy described in Sections B2.1 through B2.3 above. The offeror shall submit one Experience Data Input Form for each contract that is relevant to the Functional Area the offeror has elected to propose to. Offerors may include their project experience in as a Prime, Subcontractor, or Joint Venture (JV) member. The offeror shall not describe project work performed by other team members, subcontractors, or by individual employee’s experience from previous employment.

NOTE: If the offeror has a contract that crosses Functional Areas, a separate Experience Data Input Form shall be inserted in each Functional Area that applies. The offeror must describe which portion of its performance applies to each Functional Area. The TDPC Experience Forms shall be inserted in Volume 2, by Functional Area, from the most recent to the oldest across the allowable five year period.

B4.0 VOLUME 3: PAST PERFORMANCE

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

(a) For each Functional Area proposing to, the offeror shall identify contracts that provide evidence of its organization’s ability to perform the effort required for this program as it relates to relevancy described in paragraphs B2.1 through B2.3. 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. These contracts should be the same contracts identified in the Experience Volume but only those that are within five years of this proposal submission. When possible, these contracts should include at least five of the most relevant contracts. If proposing as a Joint Venture (JV), the offeror should provide 5 past performance references for the JV. If the offeror determines that the past performance references available for the JV, do not sufficiently support the Functional Areas being proposed, each member of the JV should individually submit the 5 references in addition to their JV references.

(b) The following is a list of the Section J Past Performance Attachments that the offeror shall utilize to provide Past Performance information as required for this Volume:

(1) Attachment (7) Past Performance Contract List – Provide list of Past Performance contracts, along with summary information, to include contact information for any Past Performance and CPARs Update Questionnaires sent out. Additionally, provide information on show-cause notices, cure notices, or termination for default on any contract that has occurred within the last five years . If there have been no show-cause notices, cure notices, or terminations for default within the five year period, then so state.

(2) Attachment (8) Past Performance Individual Contract Information – Provide past performance information by individual contract to include areas outlined in Section L, paragraphs B4.0(c) and (f) below.

(3) Attachment (9) CPARs Update Questionnaire – Submit to customers for past performance information if required per Section L, paragraph B4.0(d).

(4) Attachment (10) Past Performance Questionnaire – Submit to customers for past performance information if required per Section L, paragraph B4.0(d).

NOTE: For each Functional Area being proposed, the offeror shall provide a Past Performance Contract List (Attachment (7)) followed by the Past Performance Individual Contract Information sheets inserted starting from the most recent work to the oldest across the allowable five year period. If the offeror is proposing the same contract across multiple Functional Areas, a Past Performance Individual Contract Information sheet (Attachment (8)) shall be inserted in each Functional Area being proposed. The offeror must insert a description of the work performed that is specific to each Functional Area within the sheet.

(c) For each contract identified, provide contract data, relevancy, past performance and systemic improvement. Include supporting rationale of why the offeror believes the contract is relevant to a Functional Area pursued and any relevant systemic improvements information. 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.

(d) For contracts that have CPARs that are more than 6 months old, i.e., the completion date is more than 6 months before the due date for this Past Performance Volume; the offeror will forward a copy of the CPARs Update Questionnaire (Attachment (9)) to that contract customer’s Program Manager. For all contracts identified which do not have CPARs, the offeror will forward a copy of the Past Performance Questionnaire (Attachment (10)) to that contract customer’s PCO, Administrative Contracting Officer, Program Manager, and Technical Lead. All questionnaires shall be forwarded within four weeks from the RFP release date. The offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to Mr. Rafael Soberal, at rafael.soberal@navy.mil, thereby allowing the customer approximately 2 weeks to complete its 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.

(e) 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) and the Past Performance Questionnaires will be the primary methods used to evaluate Past Performance. It is incumbent upon the offeror to explain the relevance of the data provided and substantiate that improvements from Past Performance problems are being made. 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.

(f) Small Business Subcontracting Goal (Required for large businesses only) - All large business offerors shall provide past performance information regarding accomplishment of Small Business Subcontracting Goals. Within Attachment (8), for each contract, note whether the offeror 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. In addition, the offeror shall provide copies of SF 294s for the three most 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, it shall provide copies of three final or most recent SF 295s. Additional systems such as eSRS may be utilized.

B5.0 VOLUME 4 PRICE PROPOSAL/OTHER

Volume 4 shall be divided into two Sections as follows:

Section B5.1 --- Pricing Content

Section B5.2 --- Other Content

B5.1 Volume 4 Pricing Content:

(a) This Volume shall contain the information requested below. For price evaluation purposes, the Government has specified labor categories and labor hours for a representative tasking under each Functional Area (and for each year of the ordering period, including options). For each Functional Area being proposed, offerors shall populate and provide the associated section(s) of the Attachment (11) Price Matrix (MS Excel Workbook File). The Price Matrix is intended to reflect a typical labor mix representative of future TDPC DO/TO requirements; the pricing information will be used to establish a representative total evaluated price for each Functional Area being proposed. Although these labor and indirect rates shall reflect the offeror’s current actual rates, they will be used for evaluation purposes only. No pricing will be established at the MAC contract level nor will labor rates or indirect rates be incorporated into the basic contracts.

(b) The Price Matrix is organized by worksheets, also referred to herein as tab(s). The tabs are arranged within the workbook in the sequence listed in paragraph (d) below. The input fields within the worksheets are identified in the yellow highlighted areas and discussed in Section L, paragraph B5.1.1, below. The offeror shall utilize its Direct Labor and Indirect Rates applicable for the month identified in Block 5, of this solicitation (SF 33). For evaluation of the basic MAC, profit rates will not be evaluated or required to be submitted. Within all Excel spreadsheets, the offeror shall use formulas and functions to the maximum extent possible and avoid using output type “ value only” cells. For evaluation of the basic MAC, profit rates will not be evaluated or required to be submitted.

(c) In accordance with FAR clause 52.217-5, Evaluation of Options,…