HC1047-14-R-4021-0002.pdf
PDF 457 KB Posted
- Attached to
- Joint Command and Control (C2) Architecture Support Federal contract opportunity
- Solicitation number
- HC1047-14-R-4021
- Issued by
- Defense Information Systems Agency
About this file
HC1047-14-R-4021-0002
View the file
Other files for this federal contract opportunity
Show all 20
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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 0002 is to:
1. Provide additional administrative revisions to clauses and formatting.
2. The proposal due date remains the same at 12:00 noon; 08 May 2014. No further extensions w ill be considered.
1. CONTRACT ID CODE PAGE OF PAGES
S 1 27
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 07-May-2014
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 HC1047-14-R-4021
X 9B. DATED (SEE ITEM 11)
04-Apr-2014
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
07-May-2014
CODE
DISA/PL62
P. O. BOX 549
FORT MEADE MD 20755
HC1047 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
HC1047-14-R-4021
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION G - CONTRACT ADMINISTRATION DATA
The following have been added by reference:
52.242-15 Stop-Work Order AUG 1989
52.242-17 Government Delay Of Work APR 1984
252.232-7003 Electronic Submission of Payment Requests and Receiving
Reports
JUN 2012
The following have been added by full text:
52.232-19 AVAILABILITY OF FUNDS FOR THE NEXT FISCAL YEAR (APR 1984)
Funds are not presently available for performance under this contract beyond TBD . The Government's obligation for performance of this contract beyond that date is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise for performance under this contract beyond TBD, until funds are made available to the Contracting
Officer for performance and until the Contractor receives notice of availability, to be confirmed in writing by the
Contracting Officer.
(End of clause)
The following have been deleted:
52.232-9001 Funds Not Presently Available SEP 2012
The following were previously included by full text and are now included by reference:
52.232-18 Availability Of Funds APR 1984
SECTION H - SPECIAL CONTRACT REQUIREMENTS
The following have been modified:
SECTION H
H.1. CONTRACTOR EMPLOYMENT OF GOVERNMENT / DEPARTMENT OF
DEFENSE PERSONNEL.
The Contractor is strictly prohibited from employing any person who is an employee of the
United States Government. Reference Paragraph 4
(http://www.dod.mil/dodgc/defense_ethics/advisories/2006_advisories/adv_0608.htm) issued by the DoD
Office of General Counsel.
H.2. ORGANIZATIONAL AND CONSULTANT CONFLICTS OF INTEREST (OCCI)
– DARS 52-209-9000.
a. An Offeror shall identify in its proposal, quote, bid or any resulting contract, any potential or actual Organizational and Consultant Conflicts of Interest (OCCI) as described in FAR Subpart
9.5, if applicable.
The Offeror shall provide an affirmation statement that no OCI exists; or, if applicable, submit an OCI plan that identifies any potential or actual Organizational and Consultant Conflicts of
Interest (OCCI) as described in FAR Subpart 9.5.
This includes actual or potential conflicts of interests of proposed subcontractors. If an Offeror identifies in its proposal, quote, bid or any resulting contract, a potential or actual conflict of interest, the Offeror shall submit an Organizational and Consultant Conflicts of Interest Plan
(OCCIP) to the Contracting Officer. The OCCIP shall describe how the Offeror will address potential or actual conflicts of interest and identify how they will avoid, neutralize, or mitigate present or future conflicts of interest.
b. Offerors must consider whether their involvement and participation raises any OCCI issues, especially in the following areas when:
(1) Providing systems engineering and technical direction.
(2) Preparing specifications or work statements and/or objectives.
(3) Providing evaluation services.
(4) Obtaining access to proprietary information.
c. If a prime contractor or subcontractor breaches any of the OCCI restrictions, or does not disclose or misrepresents any relevant facts concerning its conflict of interest, the Government may take appropriate action, including terminating the contract, in addition to any remedies that may be otherwise permitted by the contract or operation of law.
H.3. GOVERNMENT-CONTRACTOR RELATIONSHIPS.
http://www.dod.mil/dodgc/defense_ethics/advisories/2006_advisories/adv_0608.htm
a. Non-personal Services. The parties agree that the services to be provided under this contract are non-personal and that no employer / employee or master / servant relationships exist or will exist between the Government and the Contractor‘s employees.
b. Prohibitions. Contractor personnel under this contract shall not:
(1) Be placed in a position where they are appointed or employed by a Federal Official, or are under the supervision, direction, or evaluation of a Federal Officer, Military or
Civilian.
(2) Be placed in a staff or policy making position or be asked to exercise personal judgment or discretion on behalf of the Government.
(3) Be placed in a position of command, supervision, administration or control over
Military or Civilian Personnel, or personnel of other contractors, or become a part of the
Government organization.
(4) Be used for the purpose of avoiding manpower ceilings or other personnel rules and regulations of the DoD or the Federal Government.
(5) Be used in administration or supervision of military procurement activities.
c. Employee Relationship. Local rules, regulations, directives and requirements issued by military and civilian authorities pursuant to their responsibility for the administration and security of Government and military installations are applicable to contractor personnel entering the offices or installations or traveling via Government-owned transportation.
The Contractor agrees that compliance will not be construed to establish any degree of
Government control consistent with a personal services contract.
H.4. TRAVEL AND PER DIEM.
a. Contractor personnel will be required to travel to support the requirements of this contract as stated in Section 9 of the PWS. Local travel will be required in the
Continental United States (CONUS). The Government has provided travel estimates in
Section L.6.4.2.2.1 - Cost / Price Summary Spreadsheet of the RFP. The Contractor shall coordinate travel arrangements with the COR to obtain advance, written approval for all travel to be conducted under the Contract. The Contractor’s request for travel shall be in writing and contain the dates, locations, and estimated costs of the travel.
b. To the extent that reimbursement of Contractor travel, lodging, meals and incidental expenses are specifically authorized elsewhere in this Contract, such reimbursements shall be limited to rates or amounts considered reasonable and allowable as defined in
FAR 31.205-46. In general, airfare will be limited to the lowest standard or coach airfare available unless documented and justified. Lodging, subsistence, and other incidental expenses will normally be limited to the ceiling amounts established in the Joint Travel
Regulation (JTR) for Federal civilian employees, the Federal Travel Regulations (FTR) or the Standardized Regulations; as applicable.
c. Only travel specifically authorized in advance and in writing by the COR will be reimbursed under this Contract. The Contractor shall not be reimbursed for any amount that exceeds the amount for travel set forth in the Contract. If any travel arrangements cause additional costs to the Contract that exceed those previously negotiated, written approval by Contract modification issued by the KO is required, prior to undertaking such travel. Costs associated with contractor travel shall be in accordance with FAR
31.205-46, Travel Costs (this includes the Department of Defense (DoD) deviation from the Office of the Secretary of Defense (OSD), dated 16 Sep 1999).
d. In special or unusual situations, actual costs in excess of maximum per diem rates may be allowable provided they do not exceed the higher actual cost amounts authorized for
Federal civilian employees in the Joint Travel Regulation (JTR), Federal Travel
Regulations (FTR) or the Standardized Regulations and that all four of the conditions in
FAR 31.205-46(a)(3) are met.
e. Approved travel charges are billable / invoiced against the appropriate Travel CLIN /
SubCLIN.
f. Contractor employees may use Government vehicles, or accompany Government representatives in Government vehicles, IAW 41 CFR 102-34.215 when the motor vehicles are used for official purposes only. The Contractor has this option only for the purposes of contract performance and when in the best interest of DISA. Government motor vehicles cannot be used for transportation between residence and duty station, unless authorized in accordance with 31 U.S.C. 1344 and CFR 102-5. Contractors must establish and enforce suitable penalties against employees who use or authorize the use of, such motor vehicles for unofficial purposes or for other than in the performance of the contract; and pay any expenses or cost, without Government reimbursement, for using such motor vehicles other than in the performance of the contract.
H.5. LOCAL TRAVEL.
Local travel will be reimbursed. Local travel is hereby defined to mean any and all travel within a fifty (50) mile radius of the primary place of performance performed in support of the
Performance Work Statement (PWS). Travel must be pre-approved by the COR. The
Contractor is authorized to invoice on a monthly basis for approved costs incurred in accordance with FAR 31.205-46.
H.6. RELEASE OF INFORMATION / PUBLICATIONS.
No news release (including photographs and films, public announcements, denial or confirmation of the same) on any part of the subject matter of this contract or any phase of the tasks hereunder shall be made without the prior written approval of the KO and DISA Public
Affairs Office and if Congressionally related, DISA‘s Congressional Affairs. See also Section I, DFARS clause 252.204-7000 ―Disclosure of Information and item 12 of the DD Form 254.
H.7. OBSERVANCE OF LEGAL HOLIDAYS AND EXCUSED ABSENSES.
a. The Government hereby provides notice and the Contractor hereby acknowledges receipt that Government personnel observe the listed days as holidays:
* New Year‘s Day
* Martin Luther King Jr. Day
* Presidents‘ Day
* Memorial Day
* Independence Day
* Labor Day
* Columbus Day
* Veterans Day
* Thanksgiving Day
* Christmas
b. In addition to the days designated as holidays, the Government observes the following days:
* Any other day designated by Federal Statute
* Any other day designated by Executive Order
* Any other day designated by a President‘s Proclamation
c. It is understood and agreed between the Government and the Contractor that observance of such days by Government personnel shall not otherwise be a reason for an additional period of performance, or entitlement to compensation except when services are required by the Government and actually performed on a holiday.
Whenever the Government is shut down for some unforeseen reason (i.e. death of a former President, unusually severe weather), the shut down falls within the scope of
Executive Order 11582 of February 11, 1971 and of 5 USC 5546 and 6103(b), all of which govern the observance of holidays by Government agencies. Unforeseen shut downs will be treated as a Federal holiday and will be applied to Contractor personnel accordingly. Section 2 of the Executive Order does allow agencies to require that certain personnel report for work on days that the Government is shut down for reasons of national security, defense, or other public need.
H.8. TRANSITION.
A smooth and orderly transition between the Contractor and a predecessor or successor
Contractor is necessary to assure minimum disruption to vital Government business. The
Contractor shall not recruit on Government premises or otherwise act to disrupt official
Government business.
SECTION I - CONTRACT CLAUSES
The following have been added by reference:
252.219-7011 Notification to Delay Performance JUN 1998
52.222-38 Compliance With Veterans' Employment Reporting
Requirements
SEP 2010
52.232-19 Availability Of Funds For The Next Fiscal Year APR 1984
52.246-4 Inspection Of Services--Fixed Price AUG 1996
252.217-7011 Access to Vessel DEC 1991
252.232-7003 Electronic Submission of Payment Requests and Receiving
Reports
JUN 2012
252.232-7006 Wide Area WorkFlow Payment Instructions MAY 2013
252.239-7001 Information Assurance Contractor Training and Certification JAN 2008
Section 508 Section 508 Compliance NOV 2003
SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS
252.239-7001 Information Assurance Contractor Training and Certification JAN 2008
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
SECTION L
Section L – Instructions, Conditions and Notices to Offerors
L.1. PROGRAM STRUCTURE AND OBJECTIVES
The objective is to provide support to the Defense Information Systems Agency (DISA) Program
Executive Office for Command and Control Capabilities (PEO C2C) in the accomplishment of
Joint C2 Architecture development activities. Specifically, this includes support for Joint C2 standards, Joint C2 architecture compliance assessment, multi-party engineering activities, and
Joint C2 architecture repository and analysis.
L.2. GENERAL INSTRUCTIONS
L.2.1 This section of the Information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), and all applicable attachments. Any proposal that omits any data and / or information requested by the RFP, or fails to adhere to the terms, conditions and requirements of the solicitation may be deemed non-responsive and may be determined ineligible for award.
L.2.2 The Government reserves the right to reject any proposal that does not comply with these proposal preparation instructions.
L.2.3 The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity 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 these requirements. Offerors shall assume that the
Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror's proposal.
L.2.4 Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and not desired.
L.2.5 The proposal acceptance period is 120 days. The Offeror shall make a clear statement in
Section A of Volume V – Contract Documentation that the proposal is valid through this date.
L.2.6 In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the
Government will destroy extra copies of such unsuccessful proposals.
L.3. GENERAL INFORMATION
L.3.1 Points of Contact.
The Contracting Officer (KO) and the Contracting Specialist (CS) are the sole points of contact for this procurement. Address any questions or concerns you may have to the KO & CS.
Written requests for clarification must be sent to the KO, Charlotte K. Hunter, charlotte.k.hunter.civ@mail.mil and CS, Christina Murray, christina.y.murray.civ@mail.mil. Oral communications are not permissible.
mailto:charlotte.k.hunter.civ@mail.mil mailto:christina.y.murray.civ@mail.mil
L.3.2 Competitive Range Determination
The Government reserves the right to make award without discussions or establishment of a competitive range. In the event a competitive range is established and the KO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the KO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition. In accordance with FAR Part 15.306(c)(2), Offerors are advised that the competitive range may be further reduced for purposes of efficiency.
L.3.3 Debriefings
The KO will promptly notify Offerors of any decision to exclude them from the competitive range; whereupon, the Offeror may request a debriefing in accordance with FAR 15.505.
Offerors excluded from the competitive range may request and receive a pre-award debriefing or they may request a debriefing pre-award and choose to wait until after the source selection decision to receive a post-award debriefing. However, Offerors excluded from the competitive range are entitled to request no more than one debriefing. The KO will notify unsuccessful
Offerors in the competitive range of the source selection decision in accordance with FAR
15.503. Post Award debriefing will be issued in writing in accordance with FAR 15.506. Post award debriefings will be issued at the same time of notification to unsuccessful Offerors.
L.3.4 Discrepancies
If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the KO & CS in writing with supporting rationale as well as the remedies the Offeror is asking the KO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions and / or clarifications.
This reservation includes matters of additional or substitute pages of the initial proposal.
L.3.5 Electronic Reference Documents
All referenced documents for this solicitation will be posted on the Federal Business
Opportunities website at https://www.fbo.gov/. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.
L.3.6 Oral Presentations
There will be no oral presentations as part of this solicitation.
L.3.7 Communications
Exchanges of source selection information between the Government and Offerors will be controlled by the KO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR
2.101 & 3.104” in the Subject line. Otherwise, source selection information may be transmitted to Offerors via the U.S. Postal Service or other carrier (e.g., FedEx, UPS, etc) and mailed to the following address:
Defense Information Systems Agency
Procurement Directorate (DITCO-NCR)
Attn: Ms. Charlotte K. Hunter
Contracting Officer, PL62
6910 Cooper Avenue
Ft. George G. Meade, MD 20755-0549
Reference: RFP HC1047-14-R-4021
L.4. ORGANIZATION / FORMAT / NUMBER OF COPIES / PAGE LIMITATIONS.
L.4.1 The Offeror shall prepare the proposal as set forth in the Proposal Organization Table
(Table L.4.1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified.
The contents of each proposal volume are described in Section L.5 - Instructions for Preparation of Proposal Content as noted in the table below.
Table L.4.1 - Proposal Organization Table
VOLUME RFP Paragraph
Number
VOLUME TITLE COPIES PAGE LIMIT
I Section L, L.5.1 Executive Summary
(Must be in MS Word 2007 or PDF format)
1 electronic copy
Part A L.5.1.1 Narrative Summary Shall not exceed 4 pages.
Part B L.5.1.2 Master Table of Contents No limit
Part C L.5.1.3 Glossary / Acronym List No limit
II Section L, L.5.2 Technical / Management
Part A L.5.2.3.1 Table of Contents No limit
Part B L.5.2.3.2 List of Tables and Drawings No limit
Part C L.5.2.3.3 Glossary No limit
Part D L.5.2.3.4 Compliance and
Cross Reference Matrix
No limit
Part E L.5.2.3.5 Management Approach Shall not exceed 15 pages
Part F L.5.2.3.6 Technical Approach Shall not exceed 25 pages
Part G L.5.2.3.7 Key Personnel Resumes shall not exceed 2 pages for each resume proposed
III Section L, L.5.3 Past Performance
Part A L.5.3.2.1 Summary Pages Shall not exceed 5 pages
Part B L.5.3.2.2 Consent Letters Shall not exceed 1 page for each subcontractor, teaming partner, and / or joint venture partner
Part C L.5.3.2.3 Client Authorization Letters Shall not exceed 1 page for each commercial contract reference
Part D L.5.3.2.4 Past Performance
Information Sheets
The Offeror shall not exceed
6 references, and shall not exceed 5 pages for each reference.
Part E L.5.3.2.5 Organizational Structure
Change History
Shall not exceed 4 pages
IV Section L, L.6.4 Cost / Price
(Must be in MS Excel 2007 format)
Part A L.6.4.2.1 Introduction Shall not exceed 8 pages
Part B L.6.4.2.2 Microsoft Excel Spreadsheets No limit
Part C L.6.4.2.3 Other Information No limit
Part D L.6.4.2.4 Final Proposal Revision, if needed
To be provided with request for Final Proposal Revision
Part E L.6.4.2.5 Sanitized Cost Proposal No limit
V Section L, L.6.5 Contract Documentation
Part A L.6.5.1 Transmittal Letter and SF 33
Shall not exceed 3 pages
Part B L.6.5.2 Sections G, H, I and K and an Organizational Conflict of
Interest Mitigation Plan (if applicable)
No limit
Part C L.6.5.3 Company Information
Specific to the Resultant
Contract
Shall not exceed 3 pages
L.4.2 Page Limitations
Page limitations shall be treated as maximums. Failure to adhere to the specified page limitations may result in the Offeror’s proposal being deemed non-compliant with the RFP. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal.
Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Each page shall be counted as one page except for the following: Title / Cover Pages, Table of
Contents, Drawings, Resumes, Glossary of Terms and Acronyms, Compliance and Cross-reference Matrix and Blank Pages, which shall not count against the page limitations.
L.4.3 Page Size and Format
L.4.3.1 A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. The page format shall have a 1.0 line spacing. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 point.
Page limitations shall not be circumvented by including internet links to additional information;
such links are not acceptable and will not be considered part of a proposal. Pages shall be numbered sequentially by volume as defined in Section L.4.1. These page format restrictions shall apply to responses to ENs. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins.
The cost / price proposal spreadsheet shall be a separate document from the technical proposal and shall be submitted in MS Excel 2007 format. All formulas shall remain present in the spreadsheet for verification.
The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this RFP.
L.4.3.2 Legible tables, charts, graphs and figures shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc. For tables, charts, graphs and figures, the text shall be no smaller than 11 point.
L.4.3.3 Labeling
The Contractor shall apply all appropriate markings including those prescribed in accordance with FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal
Information and Source Selection Information.
L.4.3.4 Indexing
Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.
L.4.3.5 Glossary of Abbreviations and Acronyms
Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries of Abbreviations and Acronyms do not count against the page limitations for their respective volumes.
L.4.3.6 Cross-Referencing
To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.
The Offeror shall provide a cross-reference matrix indicating / linking by Government document name (RFP, PWS, etc.) and by specification page / paragraph number, with the corresponding proposal paragraph in that section that addresses the referenced item.
L.4.3.7 Proposal Offer Submissions
The Offeror shall submit Volumes I through V in electronic format by email to the attention of the Contracting Officer, Charlotte K. Hunter, charlotte.k.hunter.civ@mail.mil and Contract Specialist, Christina Murray, christina.y.murray.civ@mail.mil. The maximum size of each email transmission to the Contracting Officer and Contract Specialist shall not exceed 20 MBs. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2007, MS
Office Excel 2007, MS Office Project 2007, and MS Office Power Point 2007, as applicable.
For electronic copies, indicate on each document the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any.
L.4.3.7.1 Use of the software and procedures described in this section will reduce the amount of time and effort needed by the Government to receive and install proposals into an electronic evaluation system and will help to ensure that proposals are suitable for reading electronically.
Information regarding electronic products listed herein should not be construed as Government endorsement for such products.
L.4.3.7.2 Efforts by the Government to clarify or expedite installation of electronic proposal submissions, in accordance with FAR 15.207(c), will not be considered discussions. The
Government is under no obligation to seek clarification regarding electronic proposal submissions if submissions cannot be opened or accessed.
L.4.3.8 Cost / Pricing Information
No cost or pricing information of any kind shall be included in any volume except Volume IV, Cost / Price Proposal. Cost trade-off information, work-hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.
L.4.3.9 Classified Information
Your response should not include classified information. If an Offeror believes its response must include classified information in order to be responsive to this solicitation, the Offeror shall immediately notify the Contracting Officer and Contract Specialist in writing with specific rationale.
L.5 INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT.
L.5.1 Volume I - Executive Summary
In the executive summary volume, the Offeror shall provide the following information which shall not exceed 4 pages in length:
L.5.1.1 Narrative Summary
The Narrative Summary shall explain and provide the Offeror’s overall approach and supporting rationale for operating and managing the Joint C2 Architecture Support requirement;
to include addressing significant risks and highlighting any key or unique features excluding cost
/ price. Direct lines of control, responsibility, functional relationships, and authority among the organizational elements, including proposed teaming partners / subcontractors, joint ventures and
/ or significant subcontractors arrangements shall be defined.
The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost / price. The salient features should tie in with Section M evaluation factors / subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.
L.5.1.2 Table of Contents
Include a master table of contents of the entire proposal. This allows evaluators to readily locate proposal material that may be germane to their particular evaluation portion but is not included in the proposal volume with which they are primarily involved.
L.5.1.3 Glossary / Acronym List
Include a master glossary / acronym list defining all acronyms utilized throughout the proposal.
L.5.2 Volume II – Technical / Management
Offerors shall submit their Technical / Management Approach as Volume II of the written proposal. This Volume shall not include price information, classified information, or "For
Official Use Only" information.
The Offeror shall provide the following information which shall not exceed 40 pages total: The
Management Approach Subfactor shall not exceed 15 pages. The Technical Approach Subfactor shall not exceed 25 pages. The Key Personnel Subfactor is not included in the 40 page limit for the Technical / Management Volume II. Resumes for Key Personnel shall not exceed 2 pages for each resume proposed.
L.5.2.1 General
The Technical / Management Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the technical / management subfactors defined in Section M, “Evaluation Factors for Award.” Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing / satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. ***Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.***
L.5.2.2 Format and Specific Content
L.5.2.2.1 Technical / Management Volume
The Offeror shall address its proposed approach to meet or exceed the minimum performance or capability requirements of each Technical / Management subfactor, as well as the risks in its proposed approach in terms of technical / performance, cost, and / or schedule.
L.5.2.2.2 Technical / Management Risk
Address Technical / Management Risk by identifying those aspects of your proposal you consider to have the potential for disruption of the schedule; unsatisfactory performance;
increased Government oversight; or the likelihood of unsuccessful contract performance.
Classify each risk in accordance with the “DoD Source Selection Procedures,” dated March 4, 2011, (principally, Table 3, “Technical Risk Ratings,” on page 16 of the document.) Provide the rationale for each risk and its rating, including quantitative estimates of the impact on schedule and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (e.g., PWS requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.
Note: This technical / management risk analysis provided by the Offeror may be referenced by the Government for its optional price realism analysis (see paragraph L.6.4.1.1 “Cost / Price
Reasonableness and Realism.”)
L.5.2.3 Volume Organization
The Technical / Management Volume shall be organized according to the following general outline:
a) Part A – Table of Contents
b) Part B – List of Tables and Drawings
c) Part C – Glossary
d) Part D – Compliance and Cross Reference Matrix
e) Part E – Management Approach (shall not exceed 15 pages)
f) Part F – Technical Approach (shall not exceed 25 pages)
g) Part G – Key Personnel (resumes shall not exceed two (2) pages for each resume submitted)
L.5.2.3.1 Part A – Table of Contents
Include a Table of Contents for the Technical / Management Volume.
L.5.2.3.2 Part B – List of Tables and Drawings
Include a list of Tables and Drawings utilized throughout the Technical / Management Volume.
L.5.2.3.3 Part C -- Glossary
Include a master glossary / acronym list defining all acronyms utilized throughout the Technical
/ Management Volume.
L.5.2.3.4 Part D – Compliance and Cross Reference Matrix
The Offeror shall provide a compliance and cross-reference matrix indicating / linking by
Government document name (PWS, CLIN numbers, Sections L and M, Deliverables, QASP, etc.) the corresponding paragraph in the technical volume which addresses the referenced item.
If this matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over this matrix. In addition, to the extent this matrix discloses details as to the extent or manner by which the Government intends to evaluate
Offerors’ proposals for award, Section M references in the matrix are for information purposes only and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of Section M of the solicitation. The matrix does not count against the page limitations set forth in L.4.1.
See Sample Below:
SOLICITATION COMPLIANCE AND CROSS REFERENCE MATRIX
PWS
Para
Section L Section M Deliverables Task Order/
CLIN
Offeror’s Proposal
L.5.2.3.5 Part E – Management Approach
The Offeror’s proposal shall demonstrate a comprehensive management approach that ensures trained, high-quality personnel are provided to meet the requirements of the PWS; and, the contractor’s approach shall demonstrate the ability to track and manage cost, schedule and performance against tasks in the PWS (PWS Task 6.1). Resumes for key personnel are required for evaluation purposes. Resumes for key personnel are outside of the management and technical proposal page count limits and limited to two pages for each resume. This shall not exceed 15 pages. The offeror shall not submit resumes for Key Personnel in this section. Resumes for Key
Personnel shall be submitted as part of Part G – Key Personnel.
L.5.2.3.6 Part F – Technical Approach
Offeror’s proposal shall demonstrate a complete understanding of all technical requirements outlined in the PWS. Additionally, the contractor shall demonstrate the ability to contribute to technical modernization of a portfolio of complex systems that do not have a single directive authority (PWS Tasks 6.2.1 6.2.2, 6.2.3, 6.2.4). The contractor shall demonstrate a plan to fully meet the requirements using collaborative tools and Systems Modeling Language (SysML) compliant tools (PWS tasks 6.2.3 and 6.2.5). It is critical, as underscored in paragraph L.5.2.1, that an Offeror’s proposal “not merely reiterate the objectives or reformulate the requirements specified in the solicitation.” This shall not exceed 25 pages.
L.5.2.3.7 Part G – Key Personnel
The Offeror shall provide Key Personnel who are capable of performing the requirements of the
PWS and who fully meet all of the requirements outlined in Section J, Attachment 8. Key
Personnel labor categories include: Project Manager and Principal Systems Architect. The
Offeror shall propose resumes for all Key Personnel listed. The resumes must demonstrate the
Offeror’s Key Personnel fully meet all requirements specified in Section J, Attachment 8.
Resumes shall not exceed two (2) pages each.
L.5.3 Volume III - Past Performance
L.5.3.1 General
Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in this RFP. This information is required on the Offeror and all subcontractors, teaming partners, and / or joint venture partners who are proposed to perform 20% percent or more of the proposed effort based on the total proposed price, or perform aspects of the effort the Offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each Offeror in this volume and data obtained from other sources in the evaluation of past performance.
Along with the information required in this paragraph, the Offeror shall submit a consent letter executed by each subcontractor, teaming partner, and / or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the
Offeror's performance.
L.5.3.2 Format and Specific Content
The Past Performance volume will be organized according to the following general outline:
L.5.3.2.1 Part A – Summary Pages
In accordance with the page limitations set forth in L.4.1, describe the role of the Offeror and each teaming partner, joint venture partner, and / or significant subcontractor that the Offeror is providing a Past Performance Volume Template on (Section J – Attachment 5).
L.5.3.2.2 Part B – Consent Letters
In accordance with the page limitations set forth in L.4.1, the Offeror shall provide
Subcontractor / Teaming Partner Consent Letters executed by each teaming partner, joint venture partner and / or significant subcontractor authorizing the release of past performance information so the Offeror can respond to such information. A sample consent letter is provided in Section J
- Attachment 6.
L.5.3.2.3 Part C – Client Authorization Letters
In accordance with the page limitations set forth in L.4.1, the Offeror shall provide Client
Authorization Letters for each identified effort for a commercial customer authorizing release to the Government of requested information on the Offeror’s performance. Refer to Section J -
Attachment 7.
L.5.3.2.4 Part D – Past Performance Volume Template for Recent and Relevant Contracts
In accordance with the page limitations set forth in L.4.1, the Offeror shall submit information in accordance with the RFP Past Performance Volume Template, Section J - Attachment 5. The information submitted shall reference the Offeror's past performance and the past performance of the Offeror's teaming partners / subcontractors, joint venture partners, and / or significant subcontractors.
Offerors will be evaluated on performance under existing and prior contracts for similar products or services. Offerors shall submit no more than three (3) total recent past performance efforts for evaluation, and each cited past performance effort shall not exceed 3 pages. Recent efforts are those, which have been performed during any portion of the last three (3) years, including ongoing efforts which must have been in place at least six (6) months before the proposal due date. (Note: Individual task orders under an ID/IQ contract are each considered to be one (1) past
/ present performance effort.) Information on up to two (2) recent contracts (at least one of which must be in a prime contractor role) performed by an Offeror’s significant teaming partners / subcontractors and significant subcontractors considered most relevant in demonstrating their ability to perform the proposed effort may be submitted. The Government considers a significant subcontractor and / or teaming partner to be a company who provides 20% or more of the support required, and / or a company who provides a critical portion of the effort required and / or influences the results of performance. The maximum number of past performance efforts submitted by the Prime Offeror and its teaming partners may not exceed three (3) total. Recent efforts submitted will be reviewed for relevancy and quality, and then an overall confidence assessment will be given for the past performance factor. A current point of contact for each past performance effort. References other than those identified by offerors may be contacted by the
Government, and the information received may be used in the past performance evaluation.
Offerors for whom information on past performance is not available or so sparse that no confidence assessment rating can be reasonably assigned will not be evaluated favorably or unfavorably on past performance and as a result will receive an “Unknown Confidence” rating for the Past Performance Factor. If a Past Performance Information Retrieval System (PPIRs) entry exists, it will take precedence for the evaluation team over any other reference.
Recency is defined as an effort that is ongoing or has been performed during the past three (3) years from the date of issuance of this solicitation, or for ongoing efforts, must have been in place at least six (6) months before the proposal due date.
Specific Content:
For all Past Performance Information submitted, include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, see Section M.2.2 “Past Performance Factor,” and subparagraphs, thereto.
Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of these actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate. For example: submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific technical / management subfactors and cost / price factor used to evaluate the proposal.
L.5.3.2.5 Part E – Organizational Structure Change History
In accordance with the page limitations set forth in L.4.1, the Offeror shall provide an
Organizational Change History (Reference: RFP Section entitled Organizational Structure
Change History), if applicable.
Many companies have acquired, been acquired by, or otherwise merged with other companies, and / or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this procurement. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation / performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offerors, your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources. This requirement is only applicable to the Offeror proposing as the prime contractor.
L.5.3.2.6 Questionnaires
The Offeror shall provide the Past Performance Questionnaire and Cover Letter, found in
Section J, Attachment - 3, to each of the customer Points of Contact identified for each of the relevant past performance efforts. In order to expedite the assessment process, the Offeror may complete Sections 1, 2, and 3 of the Past Performance Questionnaire for the convenience of the
Points Of Contact (POCs). The Offeror shall not, however, complete any other section of the
Past Performance Questionnaire. Once the questionnaires are completed by the POCs, the information contained therein shall be considered Source Selection Information in accordance with FAR 2.101 and 3.104 and shall not be released to the Offeror. Early submission of the
Past Performance Questionnaires is encouraged. Questionnaires shall be sent directly via email to the Contracting Officer, Charlotte K. Hunter, charlotte.k.hunter.civ@mail.mil, and Contract
Specialist, Christina Murray, christina.y.murray.civ@mail.mil no later than the proposal due date.
Past Performance Questionnaires submitted for an Offeror’s significant teaming partners / subcontractors and significant subcontractors shall clearly indicate the name of the Offeror within the questionnaire. All Past Performance Questionnaires will be considered if complete.
However, if there is a record of the Past Performance Information (PPI) contained on a questionnaire in the Government’s Past Performance Information Retrieval System (PPIRS), the
PPIRS PPI entry will take precedence over the questionnaire. The questionnaire may not be considered by the Government.
L.6.4 Volume IV – Cost / Price
L.6.4.1 General Instructions
The following instructions are applicable to the prime offeror, subcontractors, teaming partners and joint venture partners.
L.6.4.1.1 Cost / Price Reasonableness and Realism
This section is to assist you in submitting information other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed cost / price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal.
Note that unrealistically low or high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the Offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an Offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs / prices rests with the Offeror.
L.6.4.1.2 Estimating Techniques and Methods
When responding to the Cost / Price Volume requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating
Relationships, commercially available parametric cost models, in-house developed parametric cost models, etc.) to…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .