W91ZLK-13-R-0005-0003.pdf

W23SR30166ME21

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to post Questions and Answ ers as of 28 November 2012.

1. CONTRACT ID CODE PAGE OF PAGES

1 19

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

16C. DATE SIGNED

BY 29-Nov-2012

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W91ZLK-13-R-0005

X 9B. DATED (SEE ITEM 11)

25-Oct-2012

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

29-Nov-2012

CODE

ACC APG, AICD - W91ZLK

ABERDEEN INSTALLATION CONTRACTING DIV.

4118 SUSQUEHANNA AVENUE

ABERDEEN PROVING GROUND MD 21005-3013

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91ZLK-13-R-0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The DPAS code 03 has been deleted.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

J.1. SAMPLE TASK #1

(APPLICABLE TO SMALL BUSINESSES AND LARGE BUSINESSES)

TASK ORDER TITLE: Vulnerability Analysis for Combatant Command Ground Mobile

Target - Fan Song Radar and 170mm Self Propelled Gun Mounted on a T-

54 Chassis

1.0 Scope

1.1 Background: The Combatant Commands (CoCom) have identified several thousand weapon-target pairings that are required for inventory weapons and others to be fielded soon.

The list includes missile launchers, radars, tactical ballistic missiles, electronics vans, coastal fire control systems, aircraft on the ground, artillery systems, and surface-to-air missiles. The Joint

Technical Coordinating Group for Munitions Effectiveness (JTCG/ME) Program Office and

Joint Munitions Effectiveness Manual (JMEM) Working Group chairs are responsible for providing target vulnerability and weapons effectiveness data in support of the Combatant

Command requirements. Under the JTCG/ME CoCoM Targets Execution Group (CTEG), several of these targets will be addressed.

1.2 Objective: The objective of this task is to perform vulnerability analysis on the Fan Song

Radar and the 170mm Self-propelled gun mounted on a T-54 Chassis. The vulnerability analysis includes the collection of target intelligence data from various agencies, completion of three dimensional (3D) target geometric models (TGM), and the calculation of component, Cell x Cell, and total target vulnerability data for various weapon damage mechanisms including, generic fragments, projectiles, shaped-charge effects, explosively formed penetrator (EFP), and Kinetic

Energy (KE) rounds. The Advanced Joint Effectiveness Model (AJEM v2.24 or greater) model will be used to conduct the vulnerability analysis. Documentation required shall be in accordance with the 61JTCG/ME-1-8 and the Joint Service Target Data Standardization Group (JSTDSG)

Phase Checklist requirements. Documentation will utilize standard JTCG/ME nomenclature and definitions.

2.0 Applicable Documents:

2.1 61JTCG/ME-1-8, Requirements for Generating, Documenting, Reviewing, and Approving

JTCG/ME Vulnerability Data

2.2 Advanced Joint Effectiveness Model (AJEM) Standard Usage Guidance (ASUG) for

JTCG/ME Studies

2.3 Target Description Standards for Ballistic Survivability, Lethality and Vulnerability

Analyses of Ground Mobile Vehicles and Aircraft, ARL-TR-3905

2.4 JTCG/ME Joint Service Target Data Standardization Group (JSTDSG) FY12 Checklist

Requirements for Phases 1 through 4

2.5 JTCG/ME AJEM Weapon Parameter List (AWPL) for FY12 CTEG Execution

2.6 Classification Marking Guidance on CLASSIFIED JPIAW WEB site

3.0 Requirements: In accordance with Section C, paragraphs C.3.1.1, C.3.1.2, and C.3.1.4 of the basic contract. The contractor, as an independent contractor and not as an agent of the

Government, shall provide the necessary resources (except for Government-furnished property listed herein) to perform the following work:

3.1 The contractor shall comply with the JSTDSG Checklist Requirements (reference paragraph

2.4) throughout the period of performance of this task order. In addition, the contractor shall comply with vulnerability data generation guidelines and processes as outlined in: 61JTCG/ME-

1-8, Requirements for Generating, Documenting, Reviewing, and Approving JTCG/ME

Vulnerability Data; Advanced Joint Effectiveness Model (AJEM) Standard Usage Guidance

(ASUG) for JTCG/ME Studies Revision 3.3, November 2007; Target Description Standards for

Ballistic Survivability, Lethality and Vulnerability Analyses of Ground Mobile Vehicles and

Vehicles; and, JTCG/ME Approved Weapon Parameter List for FY12 CTEG Execution

(references paragraphs 2.1, 2.2, 2.3, and 2.5).

3.2 Target Information Collection: The contractor shall research and obtain any existing Fan

Song and 170-mm SP Gun target description and intelligence data from Department of Defense

(DoD) intelligence agencies [for planning purposes assume National Ground Intelligence Center

(NGIC) and National Air and Space Intelligence Center (NASIC)]. The contractor shall travel to the NGIC and the NASIC. The contractor shall conduct data acquisition to include physical and functional attributes of the two systems.

3.3 Classification of Deliverables: All deliverables from the contractor shall be marked with appropriate classification (i.e., UNCLASSIFIED, CONFIDENTIAL, or SECRET). All classified deliverables must be releasable to at least the United States, United Kingdom, Australia, and Canada.

3.4 Phase 1 Package: The contractor shall provide responses to the JSTDSG Phase 1 checklist, (Reference paragraph 2.4), as an appendix to the second status report, in accordance with Exhibit

Line Item Number (ELIN) A001 of the basic contract. Deliverables as specified in the Phase 1 checklist shall be formatted and delivered in accordance to the specifications in the checklist as well as in the templates and examples given on the classified JPIAS site.

3.5 Phase 2 Package: The contractor shall provide responses to the JSTDSG Phase 2 checklist, (Reference paragraph 2.4). Deliverables as specified in the Phase Checklist shall be formatted and delivered in accordance to the specifications in the checklist as well as in the latest templates and examples given on the classified JPIAS site.

3.5.1 Target Geometric Models (TGM): In accordance with the Phase 2 package, the contractor shall construct TGMs in the Ballistic Research Laboratory Computer-Aided Design

(BRL-CAD v7.6.2 or greater) format functional data obtained from government and contractor sources. Materiel type, sizes, and thickness parameters for target structures and components shall be included in the TGM. The contractor shall develop the target description in accordance with Target Description Standards for Ballistic Survivability, Lethality and Vulnerability

Analyses of Ground Mobile and Aircraft Vehicles (reference paragraph 2.3).

3.5.2 Create drawings of the target from the BRL-CAD Model and add dimensions. Aspects include 0az/0el, 90az/0el, 180az/0el, 90az/90el, 45az/45el, 270az/0el.

3.5.3 Conduct a Criticality Analysis (includes FMECA and Component Code List) and develop vulnerability input methodology for inclusion in the vulnerability analysis methodologies to be employed for each target.

3.5.4 Develop a Failure, Analysis and Logic Tree (FALT) that ties back to the Criticality

Analysis.

3.6 Phase 3 Package: The contractor shall provide responses to the JSTDSG Phase 3 checklist, and delivered in accordance to the specifications in the checklist as well as in the latest templates

3.6.1 Create AJEM Input Streams. The contractor shall create AJEM input files (with the exception of the weapon files) for all weapon-target combinations listed in the AWPL for the target’s category (reference 2.5). The AJEM weapon input files will be supplied to the contractor for each weapon-target combination listed in the AWPL.

3.6.2 Run Test Cases. The contractor shall create and execute select AJEM test cases as indicated in the Phase 3 checklist of deliverables (reference 2.5) for the target’s category.

3.7 Phase 4 Package: The contractor shall provide responses to the JSTDSG Phase 4 checklist, and delivered in accordance to the specifications in the checklist as well as in the latest templates

3.8 Documentation: The contractor shall generate draft Technical Reports (TRs) in accordance with 61JTCG/ME-1-8, Requirements for Generating, Documenting, Reviewing, and Approving

JTCG/ME Vulnerability Data (reference paragraph 2.1) and ELIN A003 of the basic contract.

3.9 Status briefings: The contractor shall provide two status briefings at the CTEG. (For planning purposes assume three days each at Eglin AFB, FL and Aberdeen Proving Ground, MD).

3.10 Post-Processing: The contractor shall use post-processing utilities available within the

JTCG/ME Threat Characterization Database in conjunction with manual post-processing to extract key information from the various AJEM output files and consolidate the information into formats required by the JTCG/ME. The contractor shall coordinate with the Government technical lead and JSTDSG to verify the exact data output needs and formats required prior to production-level processing. Based on the “JTCG/ME Joint Service Target Data Standardization

Group (JSTDSG) FY12 Checklist Requirements for Phases 1 through 4” and the Government

Tri-Service Review and Approval Process Team (RAPT) review and concurrence, the contractor shall prepare final outputs for the specified targets.

3.11 Task Meetings, Planning, and Reviews. The contractor shall coordinate and communicate status of progress and results in accordance with the following:

3.11.1 Kickoff Meeting. The Contractor shall conduct an initial kickoff meeting at the government site within (ten) 10 work days after task award. (For planning purposes assume the

Naval Surface Warfare Center, Dahlgren, VA) The meeting will include Government representatives as well as the contractor. The purpose of the meeting shall be to identify any limitations in data availability and accuracy and discuss the planned approach to complete the target efforts. The contractor shall provide the presentation material in accordance with ELIN

A003 of the basic contract.

3.11.2 Reviews. The contractor shall prepare the JTCG/ME Target Standardized Checklists in accordance with the “JTCG/ME Joint Service Target Data Standardization Group (JSTDSG)

FY12 Checklist Requirements for Phases 1 through 4” and distribute them to RAPT members.

The contractor shall include all inputs and formatted outputs developed in support of the target analysis efforts. The contractor shall also update the final technical reports (in accordance with paragraph 5.2).

3.11.3 Combatant Command Target Execution Group (CTEG) Meetings. The contractor shall prepare for and present a formal status of efforts during scheduled CTEG meetings. For planning purposes assume Eglin AFB, FL and Aberdeen Proving Ground, MD, each three (3) work days in duration. The contractor shall ensure that all AJEM related inputs generated are entered into the JSTDSG SIPRNET website for Government review. The contractor shall provide the presentation material in accordance with ELIN A003 of the basic contract.

3.12 Document Target Vulnerability Assessment Results. The contractor shall document target vulnerability information suitable for storage in a JTCG/ME vulnerability archive. The contractor shall generate target vulnerability information in accordance with JSTDSG Checklist

Requirements for Phase 1 thru Phase 4. The contractor shall also incorporate formatted outputs into the final technical reports in accordance with ELIN A002 of the basic contract.

3.13 Technical Report. The contractor shall generate a Technical Report in accordance with

ELIN A002 of the basic contract for each target containing vulnerability assessment data in accordance with “61JTCG/ME-1-8, Requirements for Generating, Documenting, Reviewing, and

Approving JTCG/ME Vulnerability Data”. It is important to note that the TR shall be marked in accordance with Para 3.3.

4.0 Testing Requirements: None.

5.0 Deliverables: The contractor shall deliver the following:

5.1 Task Order Plan. The contract shall implement and maintain the Government-approved

Task Order Plan submitted with the proposal and incorporated by reference herein. The contractor shall submit proposed revisions to the plan to the Government technical lead

(specified in paragraph 10.0 below) as an appendix to ELIN A001 of the basic contract.

5.2 Technical Report. The contractor shall provide an updated final technical report, documenting all phases of this task order for the Fan Song Radar and 170mm SP Gun (in accordance with ELIN A002 of the basic contract). The contractor shall deliver these reports no later than twelve (12) months from date of award. The address for these organizations will be provided by the Government Technical Lead at the initial kick-off meeting to be held at the government site ten (10) days after task order award.

5.2.1 The contractor shall provide the target technical reports in Microsoft Word format (Word

97 or later) of the vulnerability assessment data discussion, vulnerability input data files, and output data files shall be provided to the JMEM Production Contractor on CD-ROM. The address for the JMEM Production Contractor will be provided by the Government Technical

Lead at the initial kick-off meeting to be held at the government site ten (10) days after task order award.

6.0 Government Furnished Property:

6.1 The government will provide the following documents referenced in section 2.0 with this task order: 2.1, 2.2, 2.3, 2.4, and 2.6.

6.2 The Government will provide cleared personnel access to the JPIAS website. The contractor shall obtain the document cited in 2.6 via the JPIAS website. (Sample unclassified documents will be provided if the contractor does not have access to the JPIAS website.) During the course of the task, the contractor shall check the JPIAS site to ensure the latest reference document from para 2.2 has been retrieved.

7.0 Hazard Information: There are no physical hazards associated with this task.

8.0 Period of Performance: All work including receipt of the approved final documentation by the government shall be completed no later than twelve (12) months after contract award.

9.0 Security Requirements: The contractor must possess a minimum of SECRET security clearance. The contractor shall access and safeguard classified material up to the SECRET level where the work is to be performed The contractor shall comply with the requirements specified in the DD Form 254 provided in Section J of the basic contract.

J.2. SAMPLE TASK #2

(APPLICABLE TO LARGE BUSINESSES ONLY)

TASK ORDER TITLE: Methodology to Predict Damage from Closely Spaced Warhead

Fragment Impacts

1.0 Scope

1.1 Background: Current target vulnerability methodology focuses on the assessment of damage based on single independent fragment impacts, i.e. ignoring the proximity of other fragments. Testing indicates that there can be a synergistic affect from fragment impacts closely spaced in time and/or separation distance in terms of target damage. It is expected that as guidance and fuzing continues to improve and the corresponding trend of weapons detonating in closer proximity to the target the modeling of this affect will become more important for the

Joint Technical Coordinating Group for Munitions Effectiveness (JTCG/ME) Program in their role of providing target vulnerability and weapons effectiveness data in support of the Combatant

Command requirements.

1.2 Objective: The objective of this task is to develop an initial capability methodology that can predict target damage from multiple fragment impacts. Initial capability will focus on flat single material plates impacted by steel fragments. Targets can consist of multiple plates of different materials with different orientations (roll, pitch and yaw) with respect to the original shotline.

The initial steel fragments of interest will range from 10- to 2500 grains in weight. Fragment length-to-diameter ratios will range from 0.5 to 5. Impact speeds will range from 500- to 7000 ft/s for the initial capability. Orientation of the fragment will be either user defined or random and shotline obliquities will range from 0 – to 60 degrees (where 0 degrees is normal to the plane of the target) plan for the initial capability. The target can have fragments striking at multiple obliquities. Target plate materials will be predominately aluminum alloy and steel, but capability should extend to a reasonable range of target materials found in targets in the fixed and rotary wing aircraft, ground mobile and small watercraft categories typically considered by the

JTCG/ME CoCoM Targets Execution Group (CTEG).

This task will produce a methodology that can be utilized as a standalone Graphical User

Interface (GUI) driven code or as a module that can be called by a higher-level code such as

Computation of Vulnerable Area Tool (COVART) or Advance Joint Effectiveness (AJEM)

Model.

Capability shall include prediction of target damage (total area removed from plate, descriptor or mapping of area removed from plate, plate material description behind the target (including shatter), energy transfer to plate, and other metrics as developed in the course of research) and residual fragment description (weight, velocity, shape of striking particles that perforate the plate, including any fragment shatter that may occur and other metrics as developed in the course of research).

Specifications of initial conditions for the fragments include starting position (x, y, and z), orientation (roll, pitch and yaw), velocity vector, shape (sphere, cylinder, and parallelepiped) dimensions, and weight. For each single fragment the input of initial conditions shall match the inputs utilized by FATEPEN.

For conditions where synergism does not exist, penetration and damage shall be predicted by the existing JTCG/ME fragment predictive code Fast Air Target Encounter Penetration (FATEPEN) methodology.

2.0 Applicable Documents:

2.1 FATEPEN User’s and FATEPEN Analyst’s Manuals will be made available upon request.

3.0 Requirements: In accordance with Section C, paragraphs C.3.1.1, C.3.1.2, and C.3.1.4 of the basic contract, the contractor as an independent contractor and not as an agent of the

Government, shall provide the necessary resources (except for Government-furnished property listed herein) to perform the following work:

3.1 Methodology Structure: The contractor shall provide an initial outline of the structure of the methodology during a specially scheduled meeting. Electronic copy shall be provided.

Details shall be discussed during teleconference.

3.2 Data Collection: The contractor shall gather applicable test data and analytical predictions for use in methodology development. Summation of gathered materials shall be provided with access to full materials if requested.

3.3 Methodology Development: Contractor shall develop methodology capable of meeting the objective described in 1.2.

3.4 Software Development: Software shall be developed capable of operating in both a

Windows and Linux environment (environment operating system versions will be established at initial meeting) utilizing programming language agreed upon at initial meeting.

3.9 Task Meetings, Planning, and Reviews: The contractor shall coordinate and communicate status of progress and results in accordance with the following:

3.9.1 Kickoff Meeting: The Contractor shall conduct an initial kick-off meeting at the government site within ten (10) workdays after task award. (For planning purposes assume the

Naval Surface Warfare Center, Dahlgren, VA.) The meeting will include Government representatives as well as the contractor. The purpose of the meeting shall be to walk through contractors initial plan and schedule and answer detailed questions about task. The contractor shall provide the presentation material in accordance with ELIN A003 of the basic contract.

3.9.2 Penetration Panel Meetings. The contractor shall prepare for and present a formal interim status of efforts during a Penetration Panel meeting. For planning purposes assume

Dahlgren, VA as the location and two (2) workdays in duration. The contractor shall provide the presentation material in accordance with ELIN A003 of the basic contract. If contract execution schedule does not link with this meeting, a separate meeting of similar length at same location shall be assumed. The meeting will include Government representatives as well as the contractor along with other interested government and contractor representatives.

3.9.1 Summary Meeting. The Contractor shall conduct a summary kick-off meeting at the government site approximately thirty (30) days prior to scheduled task completion. For planning purposes assume the Naval Surface Warfare Center, Dahlgren, VA as the location and two (2) workdays in duration.) The purpose of the meeting is to conduct a detailed review of the methodology. The meeting will include Government representatives as well as the contractor.

3.10 Technical Report: The contractor shall generate Technical Reports in accordance with

ELIN A002 of the basic contract. Technical Reports will include an analyst manual, a users manual an interface control document and a summary document that provides an overview of the task including documentation of the process utilized for developing the methodology, recommendations for future improvements to the methodology, and recommendations for testing needed either for future development or for methodology verification.

4.0 Testing Requirements: None.

5.0 Deliverables:

5.1 Task Order Plan: The contract shall implement and maintain the Government-approved

Task Order Plan submitted with the proposal and incorporated by reference herein. The contractor shall submit proposed revisions to the plan to the Government technical lead

(specified in paragraph 10.0 below) as an appendix to Exhibit Line Item Number (ELIN) A001 of the basic contract.

5.2 Technical Report: The contractor shall provide an updated final technical report (in accordance with ELIN A002 of the basic contract) to Army Research Laboratory (TBD) – paper copy, NSWCDD (Dickinson) – electronic and paper copies. The contractor shall deliver these reports no later than twelve (12) months from date of award. The address for these organizations will be provided by the Government Technical Lead at the initial kick-off meeting to be held at the government site ten (10) days after task order award.

5.2.1 Format. The contractor shall provide the target technical reports in Microsoft Word format

(Word 97 or later) on CD-ROM or other agreed to electronic delivery medium. The contractor shall deliver these reports no later than twelve (12) months from date of award.

6.0 Government Furnished Property:

6.1 The government will provide the following documents referenced in section 2.0 with this task order: 2.1.

7.0 Hazard Information: There are no physical hazards associated with this task.

8.0 Security Requirements: The contractor must possess a minimum of SECRET security clearance. The contractor shall access and safeguard classified material up to the SECRET level where the work is to be performed. The contractor shall comply with the requirements specified in the DD Form 254 provided in Section J of the basic contract.

9.0 Period of Performance: All work including receipt of the approved final documentation by the government shall be completed twelve (12) months after task order award.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L.1. INSTRUCTIONS TO OFFERORS

L.1. SUBMISSION OF PROPOSALS

L.1.1. Mailing Address. The offeror’s proposal package (one hard copy of the entire proposal with original signatures, along with one copy on CD ROM. Files on CD ROM may be .PDF format and/or MS Office, i.e. Word, Excel, Powerpoint), along with the required proposal volumes as listed in subparagraph 1.3., shall be submitted to:

Army Contracting Command – Aberdeen Proving Ground

ATTN: CCAP-SCI, Mr. David Macintyre

4118 Susquehanna Avenue

Aberdeen Proving Ground, MD 21005-3013

L.1.2. Sample Tasks. There are two (2) sample tasks included in Section J of this solicitation which will be used in the evaluation of proposals submitted in response to this solicitation.

Sample Task #1 is applicable to both large and small businesses alike. Sample Task #2 is ONLY applicable to large businesses. The NAICS code for this procurement is 541712; the small business size standard is 500 employees.

L.1.3. Format. The offeror’s proposal shall consist of five (5) volumes:

Volume I – Technical. One original, plus five (5) copies, of the Technical proposal, comprised of separate sections for Sample Tasks #1 and #2 (if applicable). One original plus five (5) copies of the Quality Control (QC) Plan.

Volume II – Management. One original, plus five (5) copies, of the Management proposal, comprised of separate sections for Sample Tasks #1 and #2 (if applicable).

Volume III - Cost. One original, plus one copy, of the Cost/Price proposal, comprised of separate sections for Sample Tasks #1 and #2 (if applicable).

Volume IV - Past Performance and Small Business Participation. One original, plus five

(5) copies, of each of the following: Past Performance information, Small Business

Participation Plan, the Small Business Subcontracting Plan (if applicable), and the

Organizational Conflict of Interest (OCI) Plan.

Volume V - Solicitation, Offer, and Award Documents and

Certifications/Representations; one (original) copy.

L.1.3. The proposal package shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents should be included.

L.1.4. Page Limitation. Volumes I (Technical) and II (Management), cumulatively, shall not exceed 240 pages. Quality Control Plan and any resumes submitted will not count against this limitation.

L.1.5. Timeliness. Proposals are required to be submitted by the due date and time as specified on the Request for Proposal IAW FAR 15.208(b).

L.2. GENERAL INFORMATION

L.2.1. These instructions provide guidance to the offeror in preparing the proposal and describe the approach for development and presentation of the proposed data in response to this solicitation.

L.2.2. The proposal must comply fully with these instructions. FAILURE TO DO SO MAY BE

CAUSE FOR REJECTION. The proposal shall include all of the information requested in these instructions. Alternate proposals are not allowed and will not be considered or evaluated by the

Government.

L.2.3. The offeror shall clearly state in its proposal how it intends to accomplish this contract.

Mere acknowledgment or restatement of a requirement or task is not acceptable. Relevance to the effort listed herein is critical. Each volume shall be specific and complete. All the requirements under the solicitation are mandatory. The information in the proposal shall be presented in a clear, coherent, and concise manner.

L.2.4. Proposals shall be UNCLASSIFIED.

L.3. VOLUME DESCRIPTIONS:

L.3.1. Volume I – Technical. The Offeror is responsible for including sufficient details (without reference to contract cost) to permit a complete and accurate evaluation.

L.3.1.1. Format: The Technical Proposal shall provide a narrative discussion that addresses the basic Statement of Work (SOW) in Section C as well as Sample Tasks #1 and #2 (if applicable) in Section J. This section shall have an index that contains narrative titles referencing the paragraph number of the Basic SOW and in the Sample Task(s) as well as the page numbers. The narrative discussions shall be related to the applicable SOW and the task SOW paragraphs by referencing the appropriate SOW paragraph number, task number and, if applicable, task SOW paragraph numbers at the beginning of the discussion text.

L.3.1.2. Content: The Technical Proposal shall contain the following:

(a) Understanding the Requirements: The offeror shall include a discussion of its understanding of the requirements in the SOW (Section C) and Sample Tasks #1 and #2

(if applicable) (Section J). The offeror shall identify major problems anticipated in meeting the requirements, shall identify technical uncertainties and assumptions associated with the Basic SOW and the Sample Task(s) and provide specific proposals for resolution.

(b) Technical Approach to Basic SOW and Sample Tasks #1 and #2 (if applicable): The offeror shall include the planned sequence of steps to be taken, critical path, milestones, and interface and integration among tasks. The offeror shall present a technical approach that is clear, logical, practical, efficient and complete. The offeror shall identify potential risks as well as a means to mitigate them.

(c) Resources Required (For the Sample Tasks Only): The offeror shall include a matrix of labor hours showing the number of hours by labor category, skill level, and grade for each phase of work in the task, identification of any subcontractor labor used and a discussion of all work to be performed by the subcontractor in the Task(s), a travel schedule listing number of trips and number of personnel, and a description of all assumptions used to respond to Sample Tasks #1 and #2 (if applicable) to include assumptions used to calculate costs for labor, materials, equipment, subcontracts and travel (actual costs shall not be included in the technical proposal). The offeror shall discuss all equipment and materials to be used in the Sample Task(s).

L.3.2. Volume II –Management. The Offeror is responsible for including sufficient details

(without reference to contract cost) to permit a complete and accurate evaluation strictly from a management standpoint.

L.3.2.1. Format: This section shall have an index that contains narrative titles which are cross-referenced to the applicable paragraph number of the Basic SOW and Sample Tasks #1 and #2

(if applicable) as well as the proposal paragraph and page numbers, which discuss the title. The narrative discussions shall be related to the applicable Basic SOW and Sample Task SOW paragraphs by referencing the appropriate Basic SOW paragraph or, if applicable, Sample Task

SOW paragraph numbers.

L.3.2.2. Content: The Management Proposal shall contain the following:

(a) Personnel: The offeror shall provide resumes of personnel including subcontractor personnel proposed for the contractual effort. The resumes (no more than one page per person) shall also include a description of the individual's responsibilities. The certified resume shall be signed by both the offeror and the person the resume represents certifying that the information is true and complete and that the individual will be available to perform under the proposed contract. The offeror shall provide the percent availability of each proposed technical person with required skills for this contract and Sample Tasks #1 and #2 (if applicable). The offeror's discussion shall demonstrate availability of sufficient numbers of personnel having direct experience in engineering, management and technical writing.

(b) Project Management and Schedule: The offeror shall identify and explain specific project management tools which shall be employed to track cost and performance. The offeror’s discussion will include evidence of the following: adequate program visibility of this contract at Senior Management Levels, timely reaction to problems and adequate schedule and cost control. The offeror shall provide an organization plan for contract performance illustrating the interface between various elements of the organization during performance, including interface with any subcontractors and the Government, method of recognizing and reacting to problems, method of reporting actual performance versus projected progress, and techniques for controlling expenditures. The offeror shall explain its understanding of the contract requirements as well as the sequence, complexity and interrelationship of events in implementing the work of Sample Tasks #1 and #2 (if applicable). The offeror shall explain how it will schedule and track multiple tasks and deliverables. The offeror shall also provide a discussion of subcontracting involvement.

(c) Facilities: The offeror shall include a description of all facilities proposed for use in this contract and for Sample Tasks #1 and #2 (if applicable). The offeror must identify the primary facilities at which the majority of the effort will be performed. The discussion shall demonstrate the suitability of the facilities for timely and effective completion of the work described in the solicitation. The offeror must indicate which facilities are owned, leased, subcontracted, or Government-owned.

L.3.3. Volume III - Cost Proposal. Sample Tasks #1 and #2 (if applicable) shall be priced on a cost-plus-fixed fee basis. The Cost Proposal shall contain the following:

L.3.3.1. Content and Format. The offeror shall prepare a cost proposal that shall include a separate breakout of cost and fee/profit for Sample Tasks #1 and #2 (if applicable) including DD

Form 1861, “Contract Facilities Capital Cost of Money”, if applicable. Proposed costs and fee for each cost element shall be adequately broken down and explained in sufficient detail to permit a thorough analysis. Costs shall be based on an offeror's normal work week and predicated on the work set forth in the statements of work for Sample Tasks #1 and #2 (if applicable). If an offeror's normal work week is more or less than 40 hours per week, the offeror shall so state in the proposal.

(a) The offeror shall also provide a summary sheet, that incorporates each cost element for all work proposed under the solicitation.

(b) Offerors are cautioned to include all estimated per diem and travel costs involved.

(c) The offeror shall submit verifiable cost or pricing data, which will adequately support its proposal. For materials and subcontracting effort, the offeror shall provide such data as vendor quotes, invoice prices, subcontracted services, sources, quantities, prices, degree of competition, type of subcontract, etc. This data is required to support cost realism analysis. In the event adequate price competition does not result for this solicitation, the

Government reserves the right to request a Certificate of Current Cost and Pricing Data pursuant to FAR 15.804.

(d) The offeror shall provide a summary of all direct and indirect rates (labor, overhead, G&A, etc.) applicable to the total period of performance of the contract, to include the bases for estimates. Indicate how indirect cost were computed and applied, including cost breakdowns. List all other costs (e.g., travel, and computer usage) and provide bases for pricing. For travel specify each trip, from/to, number of people, duration, airfare, per diem, rental car, local mileage amount, total cost per trip, and total cost for travel.

(e) Compensation Plan. The offeror shall provide a compensation plan in accordance with

FAR 52.222-46, setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract. If the offeror proposes specific personnel for key positions on this contract (who are not current employees of the offeror) the offeror shall present letters of commitment. The letters of commitment shall indicate that the individual acknowledges intent to accept a reasonable offer of employment should an award to the offeror be made.

(f) The cost proposal shall contain the information requested in this part and shall not use the information as an extension of1he technical proposal. However, the hours and labor categories contained in the technical proposal must agree with and be traceable to the cost proposal.

(g) The offeror shall submit supporting computations and summaries contained in the cost proposal on CD-ROM using MS Excel.

(h) In order to be considered for award, an offeror must be able to have in place an-accounting system approved by Defense Contract Audit Agency before award.

(i) Subcontractors are required to submit the same information required of the prime contractor. Subcontractor cost information that is proprietary may be submitted through the prime contractor in a separate sealed package. A proposal will not be accepted directly from subcontractors. It must be submitted through the prime contractor as part of the total proposal package.

(j) The offeror shall furnish all information that could have a bearing on cost and financial matters and which is of mutual interest in the contemplated acquisition; for example, if the proposal is to be a joint venture arrangement, explain how the financial matters are to be handled.

L.3.3.2. Cost Realism. A proposal is presumed to represent an offeror's best efforts to respond to the solicitation, Any inconsistency, whether real or apparent, between promised performance and cost, shall be explained in the proposal, For example, if the intended use of new and innovative techniques is the basis for an abnormally low estimate, the nature of these techniques and their impact on cost must be explained, Any significant inconsistency, if unexplained, which raises a fundamental issue of the offeror's understanding of the nature and scope of the work required and of its financial ability to perform the contract, may be grounds for rejection of the proposal or grounds for adjusting the proposed cost. THE BURDEN OF PROOF AS TO COST

CREDIBILITY RESTS WITH THE OFFEROR.

L.3.4. Volume IV - Past Performance and Small Business Participation.

L.3.4.1. Past Performance. The offeror is responsible for including sufficient details to permit a complete and accurate evaluation strictly from a past performance standpoint.

L.3.4.1.1. Format: This part shall have a narrative discussion and shall be segregated to a separate section of the proposal to be used for a Performance Risk Assessment.

L.3.4.1.2. Content: The Past Performance Information shall contain the following:

(a) The offeror shall identify the extent to which it, or its proposed major subcontractors, has been involved as either a prime or a subcontractor on previous contracts for work similar to that required under this solicitation during the past five (5) years, technical, management, and cost performance will also be considered,

(b) The offeror shall provide a Performance Evaluation for at least three (3) Government or private-sector contracts or task orders physically completed within the past five (5) years.

Only contracts/task orders that have been physically completed (i.e., no work in progress) shall be considered acceptable to satisfy this requirement. Performance Evaluations for subcontractors (as part of teammate contracts) are acceptable. Agency personnel for whom the offeror has performed work must complete the Past Performance

Questionnaire found in Appendix H. A sample cover letter is also included. These Past

Performance Evaluation Questionnaires must be provided by the offeror to those who can further provide information on past performance, Once completed, the person(s) who completed the evaluations must email these evaluations directly to david.a.macintyre.civ@mail.mil and the persons completing these evaluations shall be informed that their names will be held in confidence, These evaluations must be received by the Government no later than the date the offeror's proposal is due. Additionally, the offeror shall provide the following information about each of these completed projects:

A detailed narrative for each contract cited

Similarities/relevance of that work to the work required by this solicitation

Objectives achieved

Cost growths and/or schedule delays encountered.

(c) Offerors shall provide copies of any Quality Deficiency Reports and Corrective Actions submitted by the Defense Contract Management Agency (DCMA) office within the past

3 years. For Government contracts that did not nor do not meet original requirements with regard to either cost) schedule or technical performance the contractor shall provide a brief explanation of the reason(s) for such factor(s) and any corrective actions taken to avoid recurrence.

(d) The offeror shall include the following prime or subcontractor information:

Name, address and telephone number of the Government contracting activity and the Procuring Contracting Officer (for subcontracts, the Administrative

Contracting Officer).

Name and telephone number of the Government contracting activity's technical representative or Contracting Officer's Representative (for subcontracts, the

Government Contract Administration Activity).

Contract or subcontract number.

Type of contract.

Award Cost/Price.

Final or projected final, Cost/Price.

Original delivery schedule.

Final or projected final delivery schedule.

If the offeror has not held Government contracts, include comparable data regarding non-Government contracts.

Proprietary or privileged information is NOT to be included.

(e) The offeror shall also provide the aforementioned information for all contracts terminated in whole or In part, for any reason during the past three (3) years, to include those currently in the process of such termination as well as those that are not for work similar to the proposed effort. The offeror shall also provide the aforementioned information for any proposed subcontractor who will perform significant portions of the effort.

mailto:david.a.macintyre.civ@mail.mil

(f) New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the offeror shall discuss in detail the role performed by these individuals in the prior contracts cited.

(g) Offerors shall include in their proposal the written consent of their proposed significant subcontractors to allow the Government to discuss the subcontractor's past performance evaluation with the offeror during negotiations.

L.3.4.2. Small Business Participation. Large businesses are required to submit Small Business

Participation Plan information in accordance with DFARS 215.304. The proposal will (at a minimum) describe the activities anticipated to be subcontracted, proposed targets based on total acquisition value of the contract, and past performance in achieving small business goals.

L.3.4.2.1. The following is the required format:

(a) Type of Business of Prime Contractor (check all applicable boxes)

{} Large

{} Small (also check type of Small Business below)

{} Small Non-Disadvantaged Business

{} Small Disadvantaged Business

{} Woman-Owned Small Business

{} HUB Zone Small Business

{} Veteran Owned Small Business

{} Service Disabled Veteran Owned Small Business (SDVOB)

(b) Percentage of Total Contract Value as a Prime Contractor %_______

(c) Percentage of Total Contract Value of Subcontracts Planned For:

(d) Percentage of Total Contract Value of Subcontracts:

Large %_________

Total Small %_________

Small (Non-Disadvantaged) %________

Small (Disadvantaged) %________

Woman Owned SB %________

HUB Zone SB %________

Veteran Owned SB %________

SDVOB %________

Each participation percentage above shall be accompanied by detailed supporting documentation regarding the individual commitments.

NOTE: The sum of the dollar values and percentages of Small

NonDisadvantaged and Small Disadvantaged should equal the entries for “Total

Small”.

(e) List principal supplies/services to be subcontracted to:

Company Type of Service/

Business Type Name/CAGE Supply (incl. NAICS code)

Large:

Total Small:

Small (Non-Disadvantaged):

Small (Disadvantaged):

Woman-Owned SB:

HUB Zone SB:

Veteran-Owned SB:

SDVOB:

NOTE: For purpose of subcontracting, Historically Black Colleges and

Universities/Minority Institutions (HBCUs/MIs) are considered as disadvantaged and should be broken out separately.

(f) Prior Performance Information: Provide any information substantiating the offeror’s track record of utilizing small business on past contracts. For Large Business: include ACO rating and SF 295 Information. For Large and Small businesses: provide descriptive information for all small business categories. Any information concerning long term relationships with Small Business subcontractors, such as mentor protégé relationships, should be provided.

(g) Extent of Commitment: Provide documentation regarding enforceable commitments to utilize any Small Business category, as defined in FAR Part 19, as subcontractors.

(h) Each Large Business offeror shall provide a Small Business Subcontracting Plan that contains all the elements required by FAR 52.2199. This plan shall be submitted separately from the Small Business Participation Plan information required above, which applies to both large and small businesses. The Small Business Subcontracting Plan is not a requirement for evaluation in source selection, but rather a requirement for award to a large business and will be incorporated into any resultant contract.

L.3.4.3. Organizational Conflict of Interest Plan. The offeror shall:

(a) Explain how actual or potential organizational conflicts of interest are identified, to include a discussion relating to a review of the offeror's corporate structure, existing contracts, and procedures for overseeing, implementing and updating the plan.

(b) Explain the strategy to mitigate the effects of a conflict if a conflict is identified.

(c) Describe the mechanisms in place for notification when an actual or potential conflict is discovered, to include a description of how information is protected, the methods employed by the offeror to ensure the plan is working, a description of the training for the employees, an example of the offeror's nondisclosure agreements(s), whether or not the plan is subject to independent verification, and an enforceable mechanism for disciplinary action in the event there is a violation of the plan's procedures.

L.3.5. VOLUME V – Solicitation, Offer, and Award Documents and

Certifications/Representations

L.3.5.1. Certifications and Representations. Each offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

Section A – Standard Form (SF) 33, “Solicitation, Offer and Award”

Section K – Representations, Certifications and Other Statements of Offerors

(End of Summary of Changes)