1. CONTRACT ID CODE P AGE OF P AGES
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT U 1 16
2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/P URCHASE REQ. NO. 5. P ROJECT NO.(If applicable)
6. ISSUED BY CODE M67854 7. ADMINISTERED BY (If other than item 6) CODE
MARINE CORPS SYSTEM COMMAND See Item 6
2200 LESTER STREET
QUANTICO VA 22134
8. NAME AND ADDRESS OF CONT RACT OR (No., Street, County, State and Zip Code) X 9A. AMENDMENT OF SOLICIT AT ION NO.
X 9B. DAT ED (SEE IT EM 11)
10A. MOD. OF CONT RACT /ORDER NO.
10B. DAT ED (SEE IT EM 13)
CODE FACILIT Y CODE
11. T HIS IT EM ONLY APPLIES T O AMENDMENT S OF SOLICIT AT IONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE P LACE DESIGNATED FOR THE RECEIP T OF OFFERS P RIOR TO THE HOUR AND DATE SP ECIFIED 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. ACCOUNT ING AND APPROPRIAT ION DAT A (If required)
13. T HIS IT EM APPLIES ONLY T O MODIFICAT IONS OF CONT RACT S/ORDERS.
IT MODIFIES T HE CONT RACT /ORDER NO. AS DESCRIBED IN IT EM 14.
A. T HIS CHANGE ORDER IS ISSUED PURSUANT T O: (Specify authority) T HE CHANGES SET FORT H IN IT EM 14 ARE MADE IN T HE
CONT RACT ORDER NO. IN IT EM 10A.
B. T HE ABOVE NUMBERED CONT RACT /ORDER IS MODIFIED T O REFLECT T HE ADMINIST RAT IVE CHANGES (such as changes in paying
office, appropriation date, etc.) SET FORT H IN IT EM 14, PURSUANT T O T HE AUT HORIT Y OF FAR 43.103(B).
C. T HIS SUPPLEMENT AL AGREEMENT IS ENT ERED INT O PURSUANT T O AUT HORIT Y OF:
D. OT HER (Specify type of modification and authority)
E. IMPORT ANT : Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPT ION OF AMENDMENT /MODIFICAT ION (Organized by UCF section headings, including solicitation/contract subject matter
The reason for this amendment is to extend the RFP due date to 11 November 2011, 1130AM local time. Section L-4.8 is hereby revised to
reflect the updated RFP due date and submission POC. All other terms and conditions remain unchanged.
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 T IT LE OF SIGNER (T ype or print) 16A. NAME AND T IT LE OF CONT RACT ING OFFICER (T ype or print)
15B. CONT RACT OR/OFFEROR 15C. DAT E SIGNED 16B. UNIT ED ST AT ES OF AMERICA 16C. DAT E SIGNED
(Signature of person authorized to sign) (Signature of Contracting Officer)
EXCEPT ION T O SF 30 30-105-04 ST ANDARD FORM 30 (Rev. 10-83)
APPROVED BY OIRM 11-84 Prescribed by GSA
FAR (48 CFR) 53.243
Page 2 of 16
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
INSTRUCTIONS TO OFFERORS
L-1 GENERAL INSTRUCTIONS
L-1.1 The Procuring Contracting Officer (PCO) is the sole Point of Contact (POC) for this acquisition. Address any
questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO via email.
L-1.1.1 The PCO for this acquisition is:
Mr. Paul D. Rogers
Marine Corps Systems Command
2200 Lester Street
Quantico, VA 22134
L-1.2 This request for proposal is written in the Uniform Contract Format described in FAR 15.204-1. The
Government advises prospective Offerors to read the terms and conditions of the model contract carefully and to
refer any questions to Paul Rogers at email: email@example.com.
L-1.3 Questions about the solicitation documents are due by 1700 (5:00 PM) local time on 26 September 2011 in
the following table format. Please do not bundle multiple questions into one long question. Questions received after
the above time and date may not receive a response. Additionally, all questions shall be submitted via email.
Government responses will be posted on FBO.gov and the NECO website via amendment.
Document/Section Paragraph Question/Issue/Concern
L-2 SOURCE SELECTION METHODOLOGY
L-2.1 The Government contemplates award of multiple Cost Plus Fixed-Fee contracts. This is a best value source
selection based on proposals received from Offerors. The Government will select for award the most advantageous
proposals representing the best value to the Government using the stated Factors, Subfactors, Elements and general
considerations. Proposals will be evaluated for compliance with the terms, conditions, and requirements set forth by
the solicitation. Offerors that provide non-responsive proposals may not be eligible for award and will not be further
evaluated for consideration. Alternate proposals are not allowed. Proposals with contingent terms and conditions
may be deemed non-responsive and could result in the rejection of an Offeror’s proposal. It is the Government’s
intent to award to the Offerors whose proposals are determined to provide the best overall value to the Government;
however the Government reserves the right to make a single award or no award. The proposal instructions in this
section are designed to assist Offerors in preparing a complete response that reflects a full understanding of the
proposed approach to accomplish all contractual requirements. Section M provides further detail as to how the
proposals will be evaluated.
Page 3 of 16
L-2.2 As prescribed by FAR 52.215-1, the Government may award on the basis of initial offers received, without
discussions. Therefore, each initial offer should contain the Offeror’s best terms from a technical, management and
L-3 PROPOSAL PREPARATION INSTRUCTIONS
L-3.1 The Offeror's proposal shall include data and information requested and shall be submitted In Accordance
With (IAW) these instructions. Non-conformance with the instructions provided may result in an unfavorable
proposal evaluation or rejection of an Offeror’s proposal, rendering it ineligible for award. An Offeror’s proposal
must encompass and be compliant with all stated requirements.
L-3.2 The Offeror’s proposal shall be clear, concise, and include sufficient detail for effective evaluation by the
Government and for substantiation of stated claims. The proposal shall not simply rephrase or restate the
Government's requirements; but rather shall provide convincing rationale to address how the Offeror intends to meet
the Factors and Subfactors to be evaluated. Offerors shall assume that the Government has no prior knowledge of its
experience and will base its evaluation on the information presented in the Offeror's proposal. The Offeror’s
proposal must respond to all Factors and Subfactors. The proposal must demonstrate that the Offeror possesses the
capability to plan, organize, and deliver the PERM Engineering and Manufacturing Development (EMD) effort in a
coordinated, technically competent fashion that is timely and cost efficient.
L-3.3 An Offeror should formulate its proposal using, to the greatest extent practicable, any technical data, computer
software or computer software documentation (as defined in Defense Federal Acquisition Regulation Supplement
(DFARS] 252.227-7013 and DFARS 252.227-7014) generated in the performance of a Government contract.
Therefore, all Offerors are given express Government permission to use technical data or computer software or
computer software documentation for which the Government has a royalty free, world-wide, nonexclusive,
irrevocable unlimited, or Government purpose license as established and defined in DFARS 252.227-7013 and
DFARS 252.227-7014. Determinations as to the Government's rights for any technical data or computer software
generated in the performance of the referenced contracts or any subcontracts should be made in reliance upon
Contractor or subcontractor records established IAW paragraph (g) of DFARS 252.227-7013 and 252.227-7014.
L-3.3.1 Technical data furnished by the Government is in an "as is" condition without any warranty as to its
accuracy, completeness, or adequacy. The Offeror shall use this technical data at its own risk. The Government
assumes no responsibility for such furnished data/documentation nor will the Government have any liability for an
Offeror’s proposal should such data/documentation prove to be inaccurate, incomplete, or otherwise defective. The
Contractor shall use technical data as marked and IAW DFARS 252.227-7013 and 252.227-7014.
L-3.4 The Offeror shall organize the proposal as set forth in the Proposal Organization Table, below. The titles and
contents of the volumes shall be as defined in this table, shall be within the required page limits and with the number
of copies as specified in the table. The volumes identified in the table should be separately bound in three-ring,
loose-leaf binders. The contents of each proposal volume are described in the proposal organization paragraphs as
noted in the table below.
Page Paper Electronic
Limit Copies Copies
Executive Summary Letter of Transmittal and Executive Summary 3 Pages N/A N/A
Volume 1* Technical Volume 100 Pages 5 5
Volume 2** Management Volume 50 Pages 3 3
Page 4 of 16
Volume 3 Cost Volume No Limit 2 2
Volume 4 Contract Information Volume No Limit 1 1
NOTE: Each volume shall be submitted both as a paper version and as an electronic version on a separate CD or
DVD. The stated number of copies, both paper and electronic, shall be submitted in addition to 1 original copy of
each volume. The Executive Summary shall be submitted as part of the Contract Information Volume. Therefore,
the Executive Summary shall be subject to the copy requirements, paper and electronic, stated for the Contract
*Volume 1, Technical, shall be divided into three (3) subparts: 1) System Design; 2) Test and Evaluation; and 3)
Systems Engineering. The Design Verification Plan and Software Development Plan may be included as Annexes
within the Technical Volume and shall not count against the page limitation – the Offeror is responsible for ensuring
that the proposal narrative for each Subfactor/Element in which the Plans are required clearly references, and points
to, the respective Annex within the Technical Volume.
**Volume 2, Management, shall be divided into three (3) subparts: 1) Program Management; 2) Schedule; and 3)
Past Performance. The Integrated Master Schedule (IMS) may be included as an Annex within the Management
Volume and shall not count against the page limitation – the Offeror is responsible for ensuring that the proposal
narrative for each Subfactor/Element in which the IMS is required clearly references, and points to, the respective
Annex within the Management Volume.
L-3.5 Page limitations for each volume and subpart shall be treated as maximums. If the volume and subpart page
limitation is exceeded, the excess pages will not be read or considered in the proposal evaluation. When both sides
of a sheet display printed material, it shall be counted as two pages. These limitations apply to both paper and
Each page shall be counted except the following:
1. Cover pages
2. Table of Contents
3. List of Tables and Figures
6. Blank pages
7. Online Representations and Certifications Applications (ORCA) information
8. Cross Reference Matrix
9. Any other item that is specifically excluded herein
L-3.6 Page size shall be 8.5 x 11 inches, not including foldouts (discussed below). The text size shall be no less than
12 point font using Microsoft Word Times New Roman; except for the reproduced sections of the solicitation
document or as stipulated in L-3.8. Use at least 1-inch margins on the page top, bottom, and sides. Pages shall be
numbered sequentially by volume. In the event the Offeror creates a page numbering ambiguity; the Government
may exercise its own discretion in counting pages. Extra credit or special considerations will not be given for the use
of colors, pictures, or unnecessary/elaborate graphics. Other than the solicited electronic media; audio recordings,
video recordings, or any other electronic media will not be accepted.
L-3.7 The Government may need to conduct discussions with Offerors which will be in the form of Evaluation
Notices (EN) issued by the PCO. If the Government issues ENs; specific page limits, format limitations, and
submittal timelines will be established for Offeror EN responses. The specified limits for individual EN responses
will be identified in the PCO letters forwarding the ENs to the respective Offeror. ENs most likely will be sent
electronically via e-mail at the discretion of the Government. The ENs typically will request an e-mail or a paper
response; but may request both and/or CD/DVD updates. If a paper version is requested, the initial EN response
shall be submitted on a light blue colored paper; to distinguish between the original document and the initial EN
Page 5 of 16
responses. If further iterations of ENs are required, the Government will stipulate the page limits, format limitations,
and submittal timelines, and required EN response paper color.
L-3.8 Foldout pages may not be used for pages of text; but may be used for large tables, charts, graphs, diagrams,
and schematics. Tables, charts, graphs, diagrams, and schematics shall be used wherever practical, to depict data
such as organizations, systems layout, implementation schedules, design drawings, and graphic plans. These
displays shall be uncomplicated, legible, and pages shall not exceed 11 x 17 inches in size. Each printed side of a
foldout will count as two pages and will be considered within the volume page limitation. For tables, charts, graphs,
and figures, the font size shall be no smaller than 8 point and acceptable fonts may be Arial, Calibri, or Times New
Roman. All information (except documentation numbers, classification markings, and page numbers) shall be
contained within an image area no larger than 9 x 15 inches. Foldout pages shall fit entirely within the volume and
fold so that the Government can read and evaluate provided information without removing the page from the
L-3.9 Each volume shall contain a glossary of abbreviations and acronyms used for the entire proposal, with an
explanation for each. Glossaries do not count against the page limitations for its respective volumes.
L-3.10 Each volume shall contain a detailed table of contents to delineate the sub paragraphs within that volume.
(Note: Volume 4, Contract Information Volume, shall include a master table of contents of the entire proposal).
L-3.11 Tab indexing shall be used to identify parts and/or sections within each volume. The Offeror shall index the
major sections identified in the volume organization table of contents. Tabs, dividers, and blank pages do not count
against the page limitations for its respective volumes.
L-3.12 Tables and figures are not required, but may be used to illustrate quantitative or qualitative data. If provided,
each volume shall contain a list of tables and figures within that volume. The list of tables and figures will not count
against the page limitations for the volume.
L-3.13 With the exception of CLIN-level pricing provided in Section B of the SF-33 document, to be included as part of
the Contract Information Volume, all pricing information shall be addressed in Volume 3 – Cost Volume. NO pricing
information shall be included within the Technical or Management volumes.
L-3.14 The Technical, Management and Cost volumes shall include a cross reference matrix. This matrix shall
cross reference the proposal volume and paragraphs to specific RFP requirements, CLINs, WBS, and other parts of
the proposal that contain relative information
L-4 PROPOSAL COPIES AND ADDRESS
L-4.1 Copies (paper and electronic) of an Offeror’s proposal must be submitted together IAW the scheduled
submission date for the particular volumes. The Contractor and team member information must be incorporated into
one coherent submittal. Be sure to identify appropriate markings such as the legend at FAR 52.215-1(e), Restriction
on Disclosure and Use of Data.
L-4.2 Each paper copy volume of the proposal shall be separately bound in a three-ring loose-leaf binder;
adequately sized to permit the volume pages to lie flat when open. Staples shall not be used. A cover sheet should be
bound in each book, clearly marked as to volume number, copy number, Offeror’s name, solicitation title, and
solicitation number [reference FAR 52.215-1(c)(2)].
L-4.3 A label shall be placed in the front cover of each binder clearly identifying volume number, copy number,
Offeror’s name, Offeror’s address, solicitation title, and solicitation number. A label shall be placed in the spine of
each binder clearly identifying volume number, copy number, Offeror’s name, solicitation title, and solicitation
L-4.4 Complete electronic volumes shall be submitted in Microsoft Office format, readable by Microsoft (MS)
Word 2007, Excel 2007, Project 2007, and Power Point 2007, as applicable and compatible with the following
Page 6 of 16
available Government equipment and software products: Microsoft Office 2007. Electronic versions shall be
submitted on a CD/DVD in a protector (jewel box or sleeve). The CD/DVD shall be clearly marked as to volume
number, Offeror’s name, solicitation title, and solicitation number. Offerors shall ensure electronic versions on
CD/DVDs are virus free. If electronic files contain links, the links must be intact and maintained through all
revisions. Electronic files contained on the CD/DVD may not be read/write/password protected.
L-4.5 The electronic versions (MS Word, Excel, Project, and Power Point) of the proposal shall be an exact
duplicate of the paper versions. Page format restriction and limitations outlined in paragraph L-3.4 apply. The
CDs/DVDs will also be used during the proposal evaluation process. The Government will not perform a word-by-
word check of the paper version vs. the electronic versions. If discrepancies are identified between the paper version
and the electronic versions, the paper version will prevail.
L-4.6 Sound or video, e.g., MPEG files, shall not be embedded into the proposal files.
L-4.7 Cost volume CD/DVD requirements. The Offeror shall use Microsoft Excel format for the financial data in
the cost proposal. Files contained on the CD/DVD may not be read/write/password protected. If files contain links,
the links must be intact and maintained through all revisions.
L-4.8 Proposals shall be submitted to the following address no later than 1130AM Local Time, 11 November
Marine Corps Systems Command
Attn: Paul Rogers, Contracting Officer
2200 Lester Street
Quantico, VA 22134
L-5 CONTENT OF PROPOSAL VOLUMES
L-5.1 Letter of Transmittal/Executive Summary
L-5.1.1 This section shall not exceed three (3) pages and shall be placed at the front of the Contract Information
Volume. This section shall consist of Offeror’s Letter of Transmittal and Executive Summary. The Letter of
Transmittal shall include any exceptions taken to the specified format prescribed herein or any contingent terms and
conditions included in the proposal, and the certification provided at L-188.8.131.52 Offerors should note that proposals
with contingent terms and conditions may be deemed non-responsive and could result in the rejection of an
Offeror’s proposal. The Letter of Transmittal shall also include the proposal validity period, which shall be no less
than six (6) months from the date of submission. The Executive Summary shall include a brief summary of the
Offeror’s PERM. No price information shall be contained in the Letter of Transmittal/Executive Summary.
Contents of this volume will not be considered in the Government’s best value evaluation and determination under
Offerors shall execute and include the following Certification in the Executive Summary unless exceptions and/or
assumptions have been identified.
I hereby certify that our offer dated (INSERT DATE) in response to solicitation M67854-11-R-6013 meets and/or
exceeds all of the requirements delineated in solicitation M67854-11-R-6013. In addition, I hereby certify that our
offer dated (INSERT DATE) in response to solicitation M67854-11-R-6013 does not take any exception to, deviate
from or otherwise request a waiver for any of the requirements delineated in solicitation M67854-11-R-6013 unless
otherwise stated. Moreover, I hereby certify that our offer dated (INSERT DATE) in response to solicitation
M67854-11-R-6013 does not include any ground rules, assumptions, or any other verbiage which conditions or
Page 7 of 16
otherwise limits our offer dated (INSERT DATE) in response to solicitation M67854-11-R-6013 unless otherwise
L-5.2 Volume 1 – Technical (Factor 1)
The Offeror’s proposal shall describe the approach to accomplish stated technical requirements in this RFP and the
process for how the Offeror will furnish the effort to achieve program objectives and work content as stated in the
Statement of Work (SOW) and Performance Specification (PS). The Offeror’s proposal shall be responsive to the
L-5.2.1 - Subfactor 1 – System Design
The Offeror’s proposal shall describe how the Offeror’s design will meet the requirements of the PERM SOW and
PS. The proposal shall be responsive to the following elements:
Element 1 - Performance
This area shall address the Offeror’s demonstration hardware technical performance relative to all of the
requirements in the PERM PS. The Offeror’s proposal shall substantiate that the proposed system will achieve the
performance required in the performance specification through actual performance, analysis, testing, and/or
Element 2 - Approach
The Offeror shall provide a detailed description of the overall approach to develop an end-item that meets the
requirements presented in the PERM SOW and PS. Within this approach, the Offeror shall detail the corresponding
scope of work involved in the design and fabrication of PERM demonstration rounds, addressing all major
components and subcomponents, and provide this detail in a Contract Work Breakdown Structure (CWBS). The
CWBS shall include a CWBS Dictionary and shall trace to the Government Work Breakdown Structure, provided as
Attachment 3 to the RFP. Any differences between the Offeror’s proposed CWBS and the Government’s WBS
shall be highlighted.
The Offeror shall summarize the design description at a level of detail that is both necessary and sufficient to
document the design maturity, to include hardware/software component and sub-component technology readiness
levels (TRL), and the use of qualified subcomponents. The Offeror shall completely itemize with substantiating
detail each TRL assessment conclusion.
L-5.2.2 - Subfactor 2 – Test and Evaluation
The Offeror’s proposal shall describe how the Offeror will meet the requirements set forth in Section 3.12 of the
PERM SOW, the requirements of the PERM Demonstration Testing and Design Analysis SoW (Attachment 2), as
well as its approach to validate that the proposed design meets the requirements set forth in the PERM PS. The
proposal shall be responsive to the following elements:
Element 1 - Design Verification Plan
The Offeror shall provide a design verification plan to substantiate its understanding of, approach toward, and ability
to verify that the Offeror's design of the demonstration round meets all performance requirements. The proposal
shall describe the test team structure, processes, roles and responsibilities, and assumptions relating these aspects of
Page 8 of 16
the design verification effort. The Offeror shall indicate what verification will be done by the Offeror or by other test
Element 2 - Support for Government Testing
The Offeror's proposal shall demonstrate an understanding of, approach toward and ability to provide support for the
Government testing set forth in Section 3.12 of the PERM SOW as well as the requirements set forth in the PERM
Demonstration Testing and Design Analysis SoW (Attachment 2).
L-5.2.3 - Subfactor 3 – Systems Engineering
The Offeror’s proposal shall describe the application of their system and software engineering processes as they
relate to meeting requirements set forth in Sections 3.5 (Systems Engineering), 3.8 (ESOH) and 3.9 (Configuration
Management) of the PERM SOW, as well as the PERM PS. The proposal shall be responsive to the following
Element 1 – Approach
The Offeror shall describe its approach to meeting requirements set forth in sections 3.5, 3.8 and 3.9 of the PERM
SOW, and the technical requirements set forth in the PERM PS. The Offeror’s approach shall clearly document
methodology that will be used to ensure traceability of the actions required by the Offeror and its supplier base to
Element 2 – Software Development Plan
The Offeror shall submit a Software Development Plan with its proposal. The SDP shall describe the Offeror’s
approach to software development and control of the software baseline, including supporting rationale. Supporting
rationale shall demonstrate how the Offeror’s proposed processes are equivalent to those articulated by CMMI
capability level 3 or some other equivalent process model. The SDP shall also include previous system and process
experience, demonstrating previous experience in developing software of the same nature as that being proposed.
L-5.3 Volume 2 - Management (Factor 2)
L-5.3.1- Subfactor 1 – Program Management
The Offeror’s proposal shall describe how the Offeror will manage the effort in order to meet the requirements of
the PERM SOW and PS. The proposal shall be responsive to the following elements:
Element 1 - Approach
The Offeror shall describe its program management approach and how the Offeror will meet the requirements set
forth in Sections 3.1 (Program Management), 3.2 (Government Furnished Property) and 3.3 (Meetings, Formal
Reviews, and Conferences) of the PERM SoW. The proposal shall include, at a minimum, a detailed description of
how the Offeror will manage the effort including (1) execution of work and work content, (2) managing work, (3)
coordinating with Government program and contracting teams, and as applicable to its proposed approach, (4)
The proposal shall also document, at a minimum, how the Offeror’s plans for facilities (location and description),
fabrication and test equipment, including GFE, labor requirements, and how they will be integrated in conducting
the PERM EMD effort. In addition, the Offeror shall identify any new resources, capabilities or personnel that do
not currently exist or are assigned to other programs that may be used in support of this effort.
The Offeror shall describe the organizational structure of the proposed Offeror’s team with emphasis on integration
with the Government IPT; technical and budgetary reviews; and the approach to communication, including
Page 9 of 16
Government participation and insight. Describe the relevant capabilities and commitment of the proposed Offeror’s
Element 2 - Risk Management Plan
The Offeror shall identify all Medium and High risks associated with performance, cost, and schedule as defined in
the Risk Management Guide for DoD Acquisition, dated August 2006. Describe the program management risk
assessment methodology and assumptions. Discuss the event or task, impact, and mitigation for each risk including
an explanation of how the effect of mitigation plans will be measured.
L-5.3.2 - Subfactor 2 – Schedule
The Offeror shall provide an Integrated Master Schedule (IMS) that substantiates the Offeror’s ability to meet
contractual schedule requirements, delineating the Offeror’s planned schedule for all activities, events, milestones,
and critical paths, based on critical path analysis, associated with all PERM EMD efforts. The IMS shall include
tasks and activities necessary to complete the work effort scoped within the PERM SOW and PS. All proposed
tasks, events and milestones shall be traceable to PERM SOW and PS requirements. The IMS shall be developed
using predecessor and successor logic to network all discrete Contractor and principal and critical subcontractor
activities from contract award through program completion.
The IMS shall be submitted electronically in Microsoft Project. Additional instruction for completing the IMS is
a) The Offeror shall include Government furnished equipment or information, critical items from suppliers and
teammates, significant external interfaces and dependencies for the entire contractual effort. The Offeror shall
provide an IMS that has the capability to roll-up from the lowest manageable level to the highest summary level
with complete horizontal and vertical traceability and capability to produce a calculated program critical path. The
IMS shall identify proposed labor hours by functional labor category (e.g., design engineering, systems engineering,
or manufacturing) for each task. The Offeror shall include a narrative on the assumptions of the IMS that related to
all program milestones and events as well as a rationale for durations of activities with moderate-to-high technical or
b) The Offeror shall propose a single numbering system that ties all activities in the network schedule to the events
in the Contractor Work Breakdown Structure.
c) The Offeror shall use a calendar consistent with the company’s work schedule. A listing of company holidays,
for each year of the proposed plan, should also be included in the schedule narrative.
d) The Offeror shall identify any customized fields used in the Microsoft Project schedule file and address their
applicability in the schedule narrative. The schedule shall contain the following data, as a minimum for each event,
activity, task, and milestone in the IMS:
-- Duration (most likely) (use of elapsed days is only permitted for CDRLs)
-- Constraint Type (minimal constraints should be used)
-- Constraint Date
-- WBS (WS field)
-- SOW Reference
Page 10 of 16
The Offeror shall describe its current or proposed schedule management system and how it will be used to plan,
coordinate, integrate, control and manage the schedule of the program, including the plan for electronic data transfer
of schedule information to the Government, within the schedule narrative.
L-5.3.3 – Volume 2 – Past Performance (Factor 3)
The Offeror shall identify recent relevant programs that provide evidence of its organization’s (including the
Offeror’s principal subcontractors, critical subcontractors, and team members) ability to perform the effort required
for this program on similar programs. Information provided should be related to similar programs in the same
division or price centers in which the Offeror proposes to perform this effort. In general, recent performance will be
considered more relevant than older performance.
The Offeror shall identify contracts whose performance is within three years of this proposal submission and
contains efforts similar to those efforts, e.g., tasks, contract type, location, contract dollar value, etc., required by this
solicitation. List the contracts from the most relevant to the least relevant. For each contract identified, provide
contract data, relevancy, past performance and systemic improvement information as described below. As this
information is presented in the proposal, demonstrate the relevancy of your, and if applicable, your principal
subcontractors, critical subcontractors, and team members past performance and systemic improvements with
respect to the solicitation requirements. For each past performance problem identified, describe the status of the
systemic improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort
had on resolving the problem such that it would not reoccur.
Offerors are reminded that both independent data and data provided by the Offerors in their proposals may be used
to evaluate past performance. The Government reserves the right to use Past Performance information obtained from
sources other than those identified by the Offeror. This information will be used for the evaluation of past contractor
performance. The Past Performance Information Retrieval System (PPIRS) shall be the primary, paperless, method
used when conducting evaluations and/or source selections.
It is incumbent upon the Offeror to explain the relevance of the data provided. The Government does not assume the
duty to search for data to cure the problems it finds in the information provided by the Offeror. The burden of
providing thorough and complete past performance information remains with the Offeror.
Past Performance Data Requirements and Contract Data
The Offeror shall provide a Past Performance Reference Matrix providing, at minimum, the following information:
• Title of Contract, Contract Number, and Sponsoring Organization;
• Name, mailing address, telephone and email address for the Technical POC and Contracting Officer;
• Type of Contract, Contract Value, Award and Completion Dates;
• Brief description of the services performed, problems identified and corrective action taken,
• Costs – initial estimate vs. actual
• Cure/Show Cause notices received, and reasons.
• A relevance assessment with supporting rationale
L-5.4 Volume 3 - Cost (Factor 4)
L-5.4.1 - Compliance
Failure to comply with RFP requirements for cost information may result in an adverse assessment of an Offeror’s
proposal and reduce or eliminate the potential for award. When an Offeror fails to furnish pricing information
required by the RFP, the Offeror bears full responsibility for any adverse impact upon the evaluation of its proposal.
It is important that all fields/files in the cost proposal remain unlocked, non-password protected and/or unprotected.
Page 11 of 16
L-5.4.2 - General Instructions
Proposals shall include proposed cost and fee in the following formats: Contractor Fiscal Year (CFY), Government
Fiscal Year (GFY) and Contract Line Item (CLIN). CFY and GFY formats shall be provided in summary total and
for each Contract Line Item Number (CLIN) by using the attached Cost Worksheet (Attachment 5) example. CLIN
format shall be presented IAW L-5.4.17 instructions. The Cost volume consists of proposed costs, fees and
supporting information. Propose IAW the CLIN structure as set forth in Section B of the SF33 RFP document.
The Offeror shall ensure the information presented in the Cost Volume is consistent with the information contained
in the other proposal volumes. The Offeror, intra-corporate work transfers, and subcontractors shall ensure the
information presented in this volume is consistent with the information contained in the other proposal volumes and
conform to the Section L Volume 3 Cost Factor pricing instructions. Subcontractors and intra-corporate work
transfers should provide supporting rationale to the Offeror for inclusion within the Offeror’s proposal.
Subcontractors are not required to disclose proprietary cost information to the Offeror. Subcontractor proposals shall
be forwarded directly to the Government no later than the closing date of the solicitation and should clearly
reference the Offeror’s proposal to which the information applies.
The Offeror, intra-corporate work transfers, and subcontractors shall provide a brief description of how the cost
proposal was prepared. This portion of the cost proposal shall include a basic description of the basis of the
proposal, including the direct and indirect rates used to develop the proposal; basis of proposed fee percent, and any
other details which provide insight into the proposal methodology.
IAW FAR 15.305 (a) (1), adequate price competition is anticipated which will establish price reasonableness.
Therefore, certified cost or pricing data is not required at this time. Data other than certified cost or pricing data shall
be required. However, if after receipt of proposals, the PCO determines that there is inadequate price competition,
and none of the exceptions in FAR 15.403-1 apply, the Offeror(s) shall be required to submit certified cost or pricing
data. The information should be sufficiently detailed to demonstrate the realism and reasonableness of proposed
The Offeror, intra-corporate work transfers, and subcontractors shall ensure that the electronic version of the Cost
proposal contains all of the formulas and links between the spreadsheets and tables presented in its proposal.
L-5.4.3 - Fee Limitations on Travel Cost
The Offeror, intra-corporate work transfers, and subcontractors shall exclude all travel costs from the fee base prior
to calculating proposed fee on all CLINs.
L-5.4.4 - Estimating, Purchasing, and Accounting Systems
The Offeror, intra-corporate work transfers, and subcontractors shall provide a summary description of their
estimating, purchasing, and accounting systems. The Offeror shall require the same information for any
subcontractor with which they intend to establish a cost or incentive-type subcontract arrangement. The Offeror
must have accounting system suitable for determining costs applicable to the contract IAW FAR 16.301-3(a) (1) and
9.104-1(e). The Offeror shall state whether their accounting system have been reviewed by the Government and
provide evidence of review and/or the Defense Contract Management Agency (DCMA) approval. Provide a
statement of any known/cited accounting system deficiencies and identify any deviations from the Offeror’s
standard procedures in preparing this proposal.
The Offeror, intra-corporate work transfers, and subcontractors shall provide a summary description of their current
Cost Accounting Standards (CAS) disclosure statement. The Offeror, intra-corporate work transfers, and
subcontractors shall state whether the current CAS disclosure statement has been reviewed by the Government and
provide evidence of review and/or DCMA approval. The Offeror, intra-corporate work transfers, and subcontractors
shall provide any currently known/cited CAS non-compliances and identify any deviations from their currently
approved CAS disclosure statement used in preparing this proposal.
Page 12 of 16
Include the following data for the Offeror and subcontractors, as applicable.
Pre-Award Disclosure Statement
Cost Accounting Practices and Certifications was executed on _____________. The cognizant Defense Contract
Audit Agency (DCAA) auditor determined the Disclosure Statement was current, accurate, and complete on
___________. The cognizant DCMA Administrative Contracting Officer (ACO) has determined the Disclosure
Statement accurately describes the Contractor's accounting system on ___________.
The Offeror provided the ACO with an Estimating System Disclosure Statement on ________. The ACO
determined the Offeror's Estimating System was adequate on _______________.
The Offeror has an approved purchasing system as determined by the ACO on ____________. The Offeror has a
material requirements planning system that was approved by the ACO on ______________.
L-5.4.5 - Cost Traceability
To ensure the traceability of cost information, the Offeror, intra-corporate work transfers, and subcontractors shall
include within the cost volume a cross-reference list to specific page numbers of BOEs between the Technical,
Management Volumes and the Cost Volume for each CLIN.
L-5.4.6 - Basis of Estimates (BOEs)
The Offeror, intra-corporate work transfers, and subcontractors shall provide BOEs for all CLINs proposed at the
Contractor Work Breakdown Structure (CWBS) level or lower which includes summary labor hours phased by
quarter or month. The BOEs shall provide table information as requested by CFY that support the pricing exhibits.
The BOEs must provide an overall technical description and related detailed cost of the proposed work. The
descriptions must be in sufficient detail to ensure the Government understands the technical content and cost
estimating methodology. The BOE must provide at a minimum, the following:
a. Estimate of costs by CWBS level to describe work content.
b. Identify specific key ground rules and assumptions.
c. Proposed labor categories and hours.
L-5.4.7 - Estimating Rationale
The Offeror shall provide a detailed description of the methodology for developing the BOEs generally developed
b. Cost estimating relationships.
c. Commercial models or company bidding system.
d. Subcontractor estimates.
e. Material quotes.
f. Engineering judgment.
• For estimates based on analogies, provide relevant analogy technical and programmatic data including program
• For estimates based on cost estimating/statistical relationships, provide the historical data/analysis that supports the
development of these relationships.
• For hardware and software estimates generated using commercial models, identify the model and vendor; identify
inputs, outputs, calibration, and a trace to the estimate. For estimates based on a company standard bidding system,
provide details of methodology and reference any DoD agency certifications.
Page 13 of 16
• For subcontractors or intra-corporate work transfers, provide (a) supplier name, (b) description of effort, (c) type of
contract, (d) cost and hours proposed by each, (e) cost and hours included in Offeror’s proposal to the Government
(provide explanation for any differences), and (f) specific methodology and supporting documentation.
• For material, submit a listing of each material item, showing part/reference number, quantity required, unit price,
and/or total price. Provide material substantiation, including non-recurring and recurring methodology of material
estimate, data, equations, assumptions, etc. For material estimate, material factors provide any adjustments made to
vendor quotes/estimates, and factors applied to material costs for scrap, rework, yields, and quantity adjustments.
• For software estimates, identify software by Source Lines of Code (SLOC) count (new, modified, reuse, equivalent
SLOC); provide the basis for SLOC counts; identify the computer language; SLOC productivity factors; and provide
historical information on other analogous programs (size, productivity, language, etc).
L-5.4.8 - Labor Categories
The Offeror, intra-corporate work transfers, and subcontractors shall include supporting schedule/exhibit
information (Excel spreadsheet/not pdf) within the cost volume presenting the labor categories that are proposed as
well as any labor categories that are proposed as mixed/blended categories and include explanatory rationale of the
mixed/blended labor categories with traceability to applicable forward pricing rates. Offerors, intra-corporate work
transfers, and subcontractors shall include definitions of all levels of labor categories proposed including
explanatory notes of the types of managerial, technical, business, or specialized knowledge or experience or
education level requirements for the level of each proposed labor category.
L-5.4.9 - Schedule of Hours by Labor Categories
The Offeror, intra-corporate work transfers, and subcontractors shall include supporting summary schedule/exhibit
information (excel spreadsheet/not pdf) within the cost volume presenting the proposed labor hours for each CLIN
by proposed labor categories by CFY.
L-5.4.10 - Direct Labor Rates/Indirect Rates/Escalation
The Offeror, intra-corporate work transfers, and subcontractors shall submit supporting schedule/exhibit information
within the cost volume presenting proposed direct labor rates, indirect rates, factors, G&A and escalation. Provide
copies of current Forward Pricing Rate Agreements (FPRAs). If applicable, details explaining the use of
uncompensated overtime should be shown clearly and in sufficient detail to allow determination of impact to the
base labor rates.
L-5.4.11 - Other Direct Costs (ODCs) and Travel
The Offeror, intra-corporate work transfers, and subcontractors shall submit supporting schedule/exhibit information
within the cost volume presenting proposed ODC and travel. The Offeror, intra-corporate work transfers, and
subcontractor’s proposals shall include cost BOEs for ODC and travel proposed for each CLIN by CFY. Narratives
shall explain rationale and basis of each ODC and travel proposed.
L-5.4.12 - Recurring and Non-recurring Costs
The Offeror, intra-corporate work transfers, and subcontractors shall submit supporting schedule/exhibit information
within the cost volume presenting proposed recurring and non-recurring costs separated by labor dollars,
subcontract, intra-corporate work transfers, and ODC/travel and material by CLIN.
L-5.4.13 – Material
The Offeror, intra-corporate work transfers, and subcontractors shall submit a Bill of Material (BOM) with proposed
material items exceeding $5,000 (unit price) and $100,000 (extended price) presenting proposed amounts shown
Page 14 of 16
within the Cost Worksheet (Attachment 5) example for each CLIN. The BOM shall be sorted in consolidated
quantities by descending extended value with source identification of proposed unit price, vendor names, quantities,
and nomenclature. Provide hardcopy and electronic spreadsheet (excel spreadsheet/not pdf) format that lists
proposed material costs allocations to individual CLINs summarized by CFY.
L-5.4.14 - Other Costs or Factors
Use this section to submit any additional information or supporting documents the Offeror considers essential to
support the cost position.
L-5.4.15 - Contract Work Breakdown Structure
Documentation is required for each Offeror’s Contract Work Breakdown Structure (CWBS) element priced out for
this effort. The Offeror shall develop a CWBS and CWBS Dictionary that traces to the Offeror’s Integrated Master
Schedule and the Government Work Breakdown Structure, provided as Attachment 3 to the RFP. Any differences
between the Offerors proposed CWBS and the Government’s WBS shall be highlighted. However, the Government
is not dictating the level of the CWBS for estimate substantiation purposes. The Offeror shall provide substantiation
at the lowest level at which the Offeror's estimate was developed.
L-5.4.16 - Offeror’s Prices by Government Fiscal Year (GFY)
Offerors shall prepare summary Excel spreadsheets (WITHOUT detail of rates, hours, labor categories, cost
elements, factors, etc.) presenting the distribution of total proposed prices for each CLIN by GFY.
L-5.4.17 – Pricing Instructions for SF33 Section B CLINs
Offerors shall submit pricing as follows:
CLIN 0100 – PERM Round Engineering and Manufacturing Development
The total value of CLIN 0100 shall be determined by adding the total estimated cost and fixed fee for the
development and delivery of 42 PERM Rounds to include 37 All-up tactical PERM rounds, 2 PERM rounds with
live energetics only, 2 PERM rounds with live tactical warheads and 1 PERM Round with Live Propelling
Total EMD Cost + Fixed Fee = CLIN Total Cost
CLIN 0101 - Contract Data Requirements List (CDRL) - DD Form 1423
The total value of CLIN 0101 shall be determined by adding the estimated total cost to deliver all required CDRLs
and the proposed fixed fee.
Total CDRL cost + Fixed Fee = CLIN Total Cost
CLIN 0102 - Projectile Interface Device
The total value of CLIN 0102 will be determined by adding the estimated total cost to develop and deliver the PID
and the proposed fixed fee.
Estimated PID cost + Fixed Fee = CLIN Total Cost
CLIN 0103 - Extractor Tool
The total value of CLIN 0103 will be determined by adding the estimated cost to develop and deliver the Extractor
tool plus the proposed fixed fee.
Page 15 of 16
Estimated Extractor Tool cost + Fixed Fee = CLIN Total Cost
CLIN 0104 - Engineering Test Support
The total value of CLIN 0104 will be determined by adding the total estimated cost for Engineering Test Support
and the proposed fixed fee.
Estimated Engineering Test Support + Fixed Fee = CLIN Total Cost
L-5.4.18 Cost Inconsistencies.
The Government assumes a proposal represents the Offeror’s best efforts to respond to the solicitation. Any
inconsistency, whether real or apparent, between promised performance and price, should be explained in the
proposal. Any significant inconsistencies, if unexplained, raise a fundamental issue of the Offeror’s understanding
of the nature and scope of work required and financial ability to perform the contract. This may result in the
proposal being determined to be unacceptable.
L-5.5 Volume 4 - Contract Information
This volume will include the Letter of Transmittal/Executive Summary and two complete and signed solicitation
(SF33) documents, including all required fill-in data for Sections B through K, a completed DD 254 and any other
information required to complete the contract. It will include a master table of contents for the overall proposal,
identification of technical data and computer software which the Contractor intends to provide, at the time of
delivery, with limited rights or restricted rights. This volume shall also include the Offeror’s Subcontracting Plan in
accordance with FAR 52.219-9.
L-5.5.1 Company Information. Including its subcontractors, the Offeror shall provide the company/division address,
identifying codes, and applicable designations, company/division's street address, county and facility code,
Commercial and Government Entity (CAGE) code, Data Universal Numbering System (DUNS) code, size of
business (large or small), and labor surplus area designation. The Offeror shall also provide the mailing address, e-
mail address, telephone numbers, fax numbers, and facility codes for the cognizant Contract Administration Office,
Defense Contract Audit Agency (DCAA), and Government paying office including the name, e-mail address,
telephone number, and fax number for the Administrative Contracting Officer (ACO). Offeror shall provide a single
point of contact and one alternate for all matters dealing with its proposal; including name, position title, address,
telephone number, fax number, and e-mail address.
L-5.5.2 Table of Contents. This volume shall include a master table of contents of the entire proposal (Note: include
the master table of contents in Volume 4 only).
L-5.5.3 Section A - Solicitation/Contract Form. Complete blocks, 14, 15A, 15B, 15C, and signature and date for
blocks 16, 17, 18. Signature by the Offeror on the Standard Form 33 constitutes an offer, which the Government
may accept. The "original" copy should be clearly marked under separate cover.
L-5.5.4 The following provides additional information on how to complete each of the columns in DFARS 252.227-
7017, Identification and Assertion of Use, Release, or Disclosure Restrictions. This volume shall also include any
technical data and computer software which the Contractor intends to provide with limited rights or restricted rights
at the time of delivery IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure
Restrictions for the table titled, List of Technical Data Computer Software to be Furnished with Restrictions.
Column 1. Technical Data or Computer Software to be Furnished with Restrictions
(Note. Identify the deliverable technical data and the Item, Component, or Process (ICP) to which it pertains.)
Column 2. Basis for Assertion
Page 16 of 16
(Note. Specify whether “development” of the ICP or software was EXCLUSIVELY or PARTIALLY at private
expense. Provide evidence of private expense, such as IR&D account numbers. “Developed” is defined at 252.227-
7013(a)(6) for technical data and 252.227-7014(a)(6) for software. Indicate whether the ICP or the software will be
further developed with Government funding. If so, indicate whether the new development can be segregated from
Column 3. Asserted Rights Category
(Note. Identify the expiration date for Government Purpose Rights and Small Business Innovative Research (SBIR)
Data Rights. Commercial technical data and software should be listed separate from the noncommercial items. See
252.227-7015(b) for the Government’s license rights in commercial technical data. Commercial software licenses
must comply with DFARS 227.7202-1; attach a copy of the license.)
Column 4. Name of Persons Asserting Restrictions
Column 5. 252.227-7028 – Similar Item Delivered to the Government
(Note. Identify if the same or similar technical data or software has been produced for, delivered to, or is subject to
delivery to the Government under any contract or subcontract. Identify the contract number, organization, and any
limitations on the Government’s rights to use and disclose [to include applicable expiration date].)
Printed Name and Title
L-5.5.5 Section K - Representations, Certifications, and other Statements of Offerors. Offerors shall complete
representations, certifications, acknowledgments, and statements via ORCA at http://orca.bpn.gov. A copy shall be
included in Volume 4 of the Offeror’s proposal. Any additional Section K information shall also be included in this
L-5.5.6 DD Form 254 – Security Classification Specification. The Offeror shall complete the DD 254 included as
Attachment 4 to the RFP. A copy of the completed DD 254 shall be included in Volume 4 of the Offeror’s
(End of Summary of Changes)