W15P7T17R0009-0001.pdf
PDF 47 KB Posted
- Attached to
- Software In-Service Support (SwISS) MA-IDIQ Federal contract opportunity
- Solicitation number
- W15P7T-17-R-0009
About this file
SwISS RFP Amendment 0001
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SwISS_RFP_Questions_and_Answers_CLARIFICATION.pdf | ||
| RFP_Attachment_0002_Section_L_Tables_Amdnt_01_12JUL2017.docx | DOCX document | |
| RFP_Exhibit_C_Admin_Management_Data_CDRL_PRICED.pdf | ||
| SwISS_RFP_Question_and_Answers_FINAL.pdf | ||
| SwISS_RFP_W15P7T17R0009.pdf | ||
| SwISS_RFP_DRAFT.pdf | ||
| DRAFT_PdM_WF_SWISS_RFP_W15P7T-17-R-0009.pdf |
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 1. Contract ID Code Page Of
2. Amendment/Modification No.
3. Effective Date
4. Requisition/Purchase Req No.
5. Project No. (If applicable)
6. Issued By Code 7. Administered By (If other than Item 6) Code
8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)
9A. Amendment Of Solicitation No.
9B. Dated (See Item 11)
10A. Modification Of Contract/Order No.
10B. Dated (See Item 13) Code Facility Code
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS
It Modifies The Contract/Order No. As Described In Item 14.
A. This Change Order is Issued Pursuant To: 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 data, 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.)
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)
16A. Name And Title Of Contracting Officer (Type or print)
15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed
By (Signature of person authorized to sign) (Signature of Contracting Officer)
NSN 7540-01-152-8070
PREVIOUS EDITIONS UNUSABLE
30-105-02 STANDARD FORM 30 (REV. 10-83)
Prescribed by GSA FAR (48 CFR) 53.243
SEE SCHEDULE
X
Cost Plus Fixed Fee
0001 2017JUL13
W15P7T
ARMY CONTRACTING CMD-APG
6001 COMBAT DR, APG, MD 21005-1846
GREGG MARTIN
EMAIL: GREGG.G.MARTIN.CIV@MAIL.MIL
W15P7T-17-R-0009
2017JUN27
X
X
/SIGNED/
2 signed
SEE SECOND PAGE FOR DESCRIPTION
1 17
CONTINUATION SHEET
Reference No. of Document Being Continued Page of
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION A - SUPPLEMENTAL INFORMATION
Buyer Name: GREGG MARTIN
Buyer Office Symbol/Telephone Number: CCAP-CCB/(443)861-4975
Type of Contract 1: Cost Plus Fixed Fee
Type of Contract 2: Cost Plus Incentive Fee (Cost Based)
Kind of Contract: Service Contracts
*** End of Narrative A0000 ***
\*Riched20 10.0.14393
Request for Proposal (RFP) Amendment 0001:
This Amendment 0001 addresses industry's questions received in response to solicitation W15P7T-17-R-0009, as specified in the "SwISS RFP
Questions and Answers" document provided with this amendment and the corresponding Uniform Contract Format (UCF) Sections.
Attachments provided with this Amendment and updated in Section J supersede all prior versions.
*** END OF NARRATIVE A0001 ***
2 17
W15P7T-17-R-0009 0001
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS
\*Riched20 10.0.14393
CONTRACT DATA
B. Type of Contract
B-1 This is an indefinite-delivery indefinite-quantity contract in accordance with FAR 16.504.
B-2 Individual orders issued under the basic contract will be on a Cost-Plus-Fixed-Fee, Cost-Plus-Incentive-Fee, Cost-reimbursement (no fee), and Firm-Fixed-Price basis.
B-3 The Government is obligated to procure, from the contractor, a minimum amount of $2,500.00 in supplies and or services under this contract over the contract ordering period. This is the minimum guarantee for the contract. Please note this minimum guarantee applies to the contract, refer to clause 52.216-19 for the minimum amount associated with an order.
B-4 The total maximum ceiling amount of this contract is $249,600,000.00 which represents the maximum limitation value of all orders placed under this contract. The total of all orders issued under the contract will be closely monitored to ensure the contract ceiling is not exceeded. Please note this maximum ceiling value applies the contract, refer to clause 52.216-19 for the maximum amount associated with an order.
B-5
CLINs 0001-0007, CLIN 0010 and all associated ELINs (C001-C003), and CLIN 0012 apply to the Base Ordering period and are for orders placed from the date of contract award through 60 months after contract award.
CLINs 1001-1007, CLIN 1010 and all associated ELINs (C101-C103), and CLIN 1012 apply to the Optional Ordering period (if exercised) and are for orders placed from the date the option is exercised through 60 months after the date the option is exercised.
CLIN 0008 and all associated ELINs (A001-A039) apply to both the Base Ordering period and Optional Ordering period.
CLIN 0009 and all associated ELINs (B001-B017) apply to both the Base Ordering period and Optional Ordering period.
CLIN 0011 and all associated ELINs (D001) apply to both the Base Ordering period and Optional Ordering period.
B-6
Agency Task and Delivery Order Ombudsman:
Cynthia Jackson
6001 Combat Drive
Aberdeen Proving Ground, MD 21005 cynthia.a.jackson64.civ@mail.mil
(443) 861-5349
*** END OF NARRATIVE B0001 ***
3 17
PIIN/SIIN
Page of
Name of Offeror or Contractor:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
Reference No. of Document Being Continued
MOD/AMD
0010 ADMINSTRATIVE AND MANAGEMENT DATA (PRICED) __________________________________________
C001 MANAGEMENT PLAN $ _______________ __________________
SERVICE REQUESTED: MANAGEMENT PLAN PRICED
\*Riched20 10.0.14393
Contractor shall provide Management Plan in accordance with PWS paragraph 3.3.1 and Data Item
Description (DID) DI-MGMT-80004A.
The price proposed for this CDRL will establish a ceiling price which shall be valid for 365 days from the date of contract award.
(End of narrative B001)
C002 WORK BREAKDOWN STRUCTURE $ ________________________ __________________
SERVICE REQUESTED: CONTRACT WORK BREAKDOWN STRUC
\*Riched20 10.0.14393
Contractor shall provide Work Breakdown Structure in accordance with PWS paragraph 3.3.2 and Data Item
Description (DID) DI-MGMT-81334D.
The price proposed for this CDRL will establish a ceiling price which shall be valid for 365 days from the date of contract award.
(End of narrative B001)
C003 SUPPLY CHAIN RISK MANAGEMENT PLAN $ _________________________________ __________________
SERVICE REQUESTED: MANAGEMENT PLAN
\*Riched20 10.0.14393
Contractor shall provide Supply Chain Risk Management
Plan in accordance with PWS paragraph 3.3.3 and Data
Item Description (DID) DI-MGMT-80004A.
4 17
Page of
Name of Offeror or Contractor:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
Reference No. of Document Being Continued
MOD/AMD
The price proposed for this CDRL will establish a ceiling price which shall be valid for 365 days from the date of contract award.
(End of narrative B001)
1010 ADMINSTRATIVE AND MANAGEMENT DATA (OPTION) __________________________________________
C101 MANAGEMENT PLAN (OPTION) $ ________________________ __________________
SERVICE REQUESTED: MANAGEMENT PLAN (OPTION)
\*Riched20 10.0.14393
Contractor shall provide Management Plan in accordance with PWS paragraph 3.3.1 and Data Item
Description (DID) DI-MGMT-80004A.
(End of narrative B001)
Deliveries or Performance _________________________
C102 WORK BREAKDOWN STRUCTURE (OPTION) $ _________________________________ __________________
SERVICE REQUESTED: WBS OPTION
\*Riched20 10.0.14393
Contractor shall provide Work Breakdown Structure in accordance with PWS paragraph 3.3.2 and Data Item
Description (DID) DI-MGMT-81334D.
(End of narrative B001)
Deliveries or Performance _________________________
C103 SUPPLY CHAIN RISK MANAGEMENT PLAN (OPTION) $ __________________________________________ __________________
SERVICE REQUESTED: SCRM PLAN OPTION
5 17
Page of
Name of Offeror or Contractor:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
Reference No. of Document Being Continued
MOD/AMD
\*Riched20 10.0.14393
Contractor shall provide Supply Chain Risk Management
Plan in accordance with PWS paragraph 3.3.3 and Data
Item Description (DID) DI-MGMT-80004A.
(End of narrative B001)
Deliveries or Performance _________________________
6 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION J - LIST OF ATTACHMENTS
List of Number List of Number
Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________
Exhibit C ADMINSTRATIVE MANAGEMENT DATA CDRL (PRICED) 13-JUL-2017 006 EMAIL
Attachment 0002 RFP SECTION L TABLES 13-JUL-2017 002 EMAIL
7 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS
\*Riched20 10.0.14393
L-22 GENERAL INSTRUCTIONS FOR PROPOSAL SUBMISSION
NOTE: This section (L-22) is separated into subparagraphs as referenced by the letter L, point (.) and numerically ordered. All references L.# shall be referenced to Section L-22.
L.1 GENERAL INSTRUCTIONS________________________
Each Offeror shall submit no more than one (1) proposal via email to the Contract Specialist, gregg.g.martin.civ@mail.mil no later than
11:59 p.m. Eastern Standard Time (EST) on August 9, 2017. Offerors shall NOT submit proposals via the FedBizOpps website. The Offerors proposal shall be submitted in electronic format only. No hard copy(ies) of an Offerors proposal is requested, nor will be accepted by the Government. The Offeror is responsible for ensuring any electronic format file is free from viruses, malware, or other malicious types of code. Electronic format files submitted by the Offeror that are found to contain viruses, malware, or other malicious types of code will be set aside, and the contents of those files will not be considered by the Government. No classified information shall be submitted by the offer in response to this solicitation.
The e-mail proposal submittal shall consist of separate files as set forth and named below. Microsoft Office 2007 software or higher, and Adobe software if applicable, shall be used to create the required files. Offerors may encrypt and/or password protect proprietary information as they see fit. However, if the Government is unable to access the documents, the proposal may not be considered for award.
Proposals shall not contain any classified data or information.
The Offeror shall prepare proposal volumes as follows:
1) Volume I - Solicitation, Offer, and Award Documents
File Name: B01-xxxx COVERLETTER MMDDYY.docx or .pdf
2) Volume II - Technical/Management, File Name: B01-xxxx TECH MMDDYY.docx or .pdf
3) Volume III Past Performance, File Name: B01-xxxx PASTPERF MMDDYY.docx or .pdf
4) Volume IV Small Business Utilization Plan, File Name: B01-xxx SBUP MMDDYY.docx or .pdf
5) Volume V - Cost/Price
File Names: B01-xxxx COST MMDDYY.xls, B01-xxxx COSTNARR MMDDYY.docx or .pdf, B01-xxxxSANITIZED MMDDYY.xls
The Offerors shall replace xxx with the company name and MMDDYY with the date of the proposal.
Price or cost information shall not appear in Volume I, Volume II, Volume III, or Volume IV. Proposals received that fail to separate price or cost information from Volume I, Volume II, Volume III, or Volume IV may be determined unacceptable and may not be considered for award. Offerors are responsible for including sufficient details to permit a complete, thorough, and accurate evaluation of the submitted proposal. Proprietary information shall be clearly marked.
All communications shall be submitted in writing and directly to the Contract Specialist; Gregg Martin at the following email address:
gregg.g.martin.civ@mail.mil. Offerors shall not contact any other Government personnel other than the person identified above.
Contacting any other Government personnel other than the Contract Specialist identified may result in an organizational conflict of interest (OCI) and may result in an Offeror being excluded from competition and award.
All questions shall be submitted via email to gregg.g.martin.civ@mail.mil no later than 11:59 p.m. Eastern Standard Time (EST) on July
06, 2017. Offerors shall NOT submit questions via the FedBizOpps website.
Section J attachments are available upon request from Contract Specialist: Gregg Martin gregg.g.martin.civ@mail.mil. Offerors shall not contact any other Government personnel other than the person identified above.
The Offeror shall disclose any potential OCI situations with itself, subcontractors, partners or any other Offeror as it applies to this solicitation for the base contract awards to the Contracting Officer (through the Contract Specialist) as soon as the OCI is identified;
including if identified prior to proposal submission, or the Offeror shall submit an affirmation statement in its proposal that they are not aware of any OCI in accordance with the Past Performance sub-factor instructions. The disclosure shall include the facts and an analysis of the actual or perceived conflict and recommend an approach to neutralize, mitigate, or avoid the potential conflict. The
Contracting Officer will determine if resolution is necessary and promptly respond to resolve any potential conflicts, which may include notifying an Offeror of their exclusion from the competition. If an Offeror fails to submit either a disclosure of potential OCI
8 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
situations or an affirmative statement that the Offeror is not aware of any OCI, the Offeror may not be considered for award.
The use of hyperlinks in proposals to a location in the current document is allowed; however, the use of hyperlinks in proposals to another file or document, or to a Web page, is prohibited.
Offerors are cautioned that "parroting" of the Technical requirements or the PWS with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete, thorough, and accurate evaluation of the submitted proposal. Proprietary information shall be clearly marked.
If an Offeror believes that the requirements in these instructions contain an error, omission, conflict, or are otherwise unsound; the
Offeror shall immediately notify the Contract Specialist identified above by e-mail with supporting rationale.
L.1.1 PAGE SIZE AND FORMAT__________________________
Pages with text shall be single spaced. Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial or Times New Roman fonts are required. Tables and illustrations may use a reduced font size no less than 8-point and may be landscape. A page is defined as a sheet of paper that contains information, to include an electronic representation of how a page would look if it were printed out in hard copy. Page limits exclude intentionally blank pages (NOTE: Intentional blank pages shall include the annotation "Page is Intentionally Blank" or other comparable legend), title pages, tables of contents, acronym lists, and lists of illustrations only; these pages shall not contain information needed for evaluating the proposal. All material shall be contained within the page limit identified for each volume, unless otherwise specified. Partial pages count as a full page. All pages within a page-limited volume shall be consecutively numbered, starting at page one, and shall not exceed the page limitation.
Footnotes to text shall not be used. A Table of Contents shall be included in each proposal volume, which shall be created using the
Table of Content feature in MS Word. If PDF files are provided, they shall be submitted as scanable and searchable, and Microsoft Office shall be used to create the PDF files. If PDF files are provided, the Offeror shall also provide the original Microsoft Office files in addition to the PDF versions. All textual document type files (i.e., pages that are either all text, all graphics/tables, or a mix of text and graphics/tables) shall use the following page setup parameters:
1. Margins Top, Bottom, Left, Right 1" Gutter 0"
2. From Edge Header, Footer 0.5"
3. Page Size Width 8.5", Height 11"
NOTE: 11X17 folded pages are acceptable for tables/graphic representations; however, each 11X17 page counts as two pages.
The following additional restrictions apply:
1. File Packaging. Files shall be in read-only format. All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2007.
All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. Copies of any certificates, approvals, letters, qualifications, etc. that are included in the Offerors proposal shall be legible and complete to be considered by the Government in the evaluation of the Offerors proposal. For any support information provided that is not included in the page count for a particular Sub-Factor, the content and support information shall be referenced within the related page count portion of that Sub-Factor.
L.1.2 PAGE LIMITATIONS AND FILE NAME/TYPE_________________________________________
Page limitations for this proposal are stated below. Proposal cover page, table of contents pages, separation pages between Sections, and assessment reports for Subfactor 1 will not be counted toward the page limitation. Any pages exceeding the limitations identified below will not be evaluated.
VOLUME I L2.1 Solicitation, Offer, and Award Page Limit: 3
VOLUME II L2.2 Technical Management Page Limit: N/A
VOLUME II L2.2.1 Subfactor 1: Waveform Porting Capability Page Limit: 10 + signed assessment report(s)
VOLUME II L2.2.2 Subfactor 2: Management Approach Page Limit: 40
VOLUME II L2.2.3 Subfactor 3: Technical Approach Page Limit: 25
VOLUME II L2.2.4 Subfactor 4: QASP Page Limit: 5
VOLUME III L2.3 Past Performance Page Limit: 9
VOLUME IV L2.4 Small Business Utilization Page Limit: No Limit
VOLUME V L2.5 Cost Page Limit: No Limit
L.1.3 Discussions_________________
9 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
The Government intends to evaluate proposals and award a contract without discussions with Offeror's. The Government reserves the right to conduct discussions if the Contract Officer determines them to be necessary.
In accordance with FAR 15.306(d), discussions may be held. Should discussions take place, the Government will specify a common amount of time for each Offeror in the competitive range to submit a final proposal revision.
If oral discussions are warranted, the Procuring Contracting Officer will schedule the discussion sessions. Appropriate security clearances shall be provided by the Offerors in sufficient time to process the requests. The Procuring Contracting Officer will provide additional instructions with the notification. Should they be warranted, the oral discussion sessions may take place at a facility of the Governments choosing in the Aberdeen, MD area or telephonically at the discretion of the Contracting Officer.
L.2 PROPOSAL VOLUMES____________________
The Offeror shall submit a written proposal addressing the sections below to enable the Government to make a thorough evaluation and arrive at a sound determination as to whether or not the Offeror will meet the requirements of the RFP.
VOLUME I: Solicitation, Offer, and Award Documents
VOLUME II: Technical/Management
Factor 1 Technical/Management
Subfactor 1: Waveform Porting Capability
Subfactor 2: Management Approach
Subfactor 3: Technical Approach
Subfactor 4: Quality Assurance Surveillance Plan (QASP)
VOLUME III: Past Performance
Factor 2 Past Performance
VOLUME IV: Small Business Utilization Plan
Factor 3 Small Business Utilization Plan
VOLUME V: Cost/Price
Factor 4 Cost/Price
L.2.1 VOLUME I SOLICITATION, OFFER AND AWARD DOCUMENTS_______________________________________________________
L.2.1.1 Offerors Cover Letter_____________________________
The cover letter shall state that it transmits an offer in response to the RFP, and shall include the solicitation number. The cover letter shall state the proposal remains valid for no less than 365 calendar days from the date the proposal is due. An executive of the company who possesses actual authority to contractually bind the Offeror shall sign the cover letter, to include the executives name and title. The cover letter shall also include the following:
a) The names, titles, and telephone and facsimile numbers (and electronic addresses if available) of persons authorized to negotiate on the Offerors behalf with the Government in connection with this solicitation.
b) The names, company titles, telephone numbers, and email addresses of two (2) individuals that the Offeror has designated as responsible for receiving and responding to Government ENs through email.
c) The Commercial and Government Entity (CAGE) number, DUNs Number, Taxpayer Identification Number (TIN), and physical and mailing address(es) of the location(s) at which the Offeror intends to perform the proposed effort.
d) The name, address and telephone number of the cognizant DCAA audit office.
e) The name, address and telephone number of the cognizant DCMA office.
f) The name, address, and telephone and facsimile numbers of the Offeror (and electronic address if available).
g) A statement which identifies the extent of to which the Offeror agrees with all terms, conditions, and provisions of this RFP, and agreement to furnish any or all items upon which prices are offered at the price set opposite each item.
h) Acknowledgement of receipt of all amendments (if any are issued) to the RFP in accordance with the provision at FAR 52.215-1(b).
The cover letter shall be limited to three (3) pages in length.
L.2.2 VOLUME II Technical/Management_____________________________________
Factor 1 Technical/Management
L.2.2.1 Acceptability of Offer______________________________
10 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
This volume shall consist of all information, required to support the Offerors proposed approach to Technical/Management requirements.
L.2.2.2 Subfactor 1: Waveform Porting Capability_________________________________________________
The Offeror shall provide signed assessment report(s), Government or vendor, of a ported performance of one of the following waveforms/network service software products: SRW v1.01.1 or later, WNW v4.2 or later, SINCGARS v1.4.6 or later, eOTAM v1.1 or later.
The current software baselines are SRW v1.2.2.1, WNW v4.2.2, SINCGARS v2.0, and eOTAM v1.1.
The Offerors assessment report shall demonstrate successful operation of the applicable demonstration cases for the specified waveform/network service software product indicated in Section J, Attachment 0002; titled "RFP Section L Tables" Table L-1: Summary of
Required Waveform/Networking Porting Demonstration Cases [specifically, four (4) demonstration cases for SRW, three (3) demonstration cases for WNW and SINCGARS or one (1) demonstration case for eOTAM].
L.2.2.3 Subfactor 2: Management Approach_________________________________________
The Offeror shall submit a Management plan that identifies the Offeror's proposed approach to satisfy the Government's requirements in the PWS Section 3.0. The Management plan shall clearly describe the ability to generate and maintain quality software, to protect national interest, and to adequately manage government property (outlined in Appendix 2 of the PWS). The Management Plan shall clearly describe the following:
1) Management Structure
a) Corporate Organization
b) Resources
c) Organization Conflict of Interest Mitigation
2) Processes
a) Requirements Management
b) Configuration Management
c) Risk Management
d) Quality Assurance
e) Subcontractor Management
f) Security Plans
g) Supply Chain Risk
h) Reliability
3) Program Protection
4) Software Development
a) Coding practices and standards
b) Information Assurance
c) Design Reviews
d) Integration & Test
e) Software Delivery
f) Software Quality
5) Property Management Plan: Offerors shall submit a Property Management Plan to describe their approach to managing Government property throughout performance of this contract, per FAR 45.202(b). This plan shall address each of the following ten outcomes (10) and provide a brief overview of how they are addressed within Offerors written Property Management Procedures. Government property includes
Government furnished property and contractor-acquired property, per FAR 52.245-1(a).
OUTCOME: DESCRIPTION
Acquisition: Offerors shall outline how property acquisitions are documented, per FAR 52.245-1(f)(1)(i).
Receipt: Offerors shall describe outline how property receipt is documented, recorded, and identified, per FAR 52.245-1(f)(1)(ii).
Records: Offerors shall outline how property records are created and maintained, per FAR 52.245-1(f)(1)(iii).
Physical Inventory: Offerors shall outline method to perform, record, and disclose physical inventory results, per FAR 52.245-
1(f)(1)(iv).
Subcontractor Control: Offerors shall outline whether contractual terms and conditions are flowed down to subcontractors, per FAR 52.245-
1(f)(1)(v)(A). Offerors shall outline how subcontracts are properly administered and when reviews of subcontractor Property Management
Systems are performed, per FAR 52.245-1(f)(1)(v)(B).
Reports: Offerors shall outline process to create and provide property-related reports, per FAR 52.245-1(f)(1)(vi).
Relief of Stewardship Responsibility and Liability: Offerors shall outline process to recognize, investigate, and report losses of
Government property, per FAR 52.245-1(f)(1)(vii).
11 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
Utilization: Offerors shall outline how Government property is to be used, consumed, moved, and stored, per FAR 52.245-1(f)(1)(viii).
Maintenance: Offerors shall outline how Government property is to be maintained, and when property requiring replacement and/or capital rehabilitation is to be reported to the Property Administrator, per FAR 52.245-1(f)(1)(ix).
Property Closeout: Offerors shall outline how property closeout is performed and when it is reported to the Property Administrator, per
FAR 52.245-1(f)(1)(x).
L.2.2.4 Subfactor 3: Technical Approach (Sample Task Order)_________________________________________
The Offeror shall submit a technical approach in response to the Sample Task Order located in Section J, Attachment 0003.
The Offeror's technical approach shall be organized in accordance Attachment 0003; "Sample Task Order", Section C, "Task Order
Performance Work Statement (PWS)".
The Offerors proposed technical approach shall demonstrate adequate knowledge and understanding of the technical requirements required to complete the tasks defined in Attachment 0003; Sample Task Order PWS. The Offeror's technical approach shall provide a detailed description of the approach and methodology which would be used in accomplishing the tasks under CLIN 0001 and 0002 of the Sample Task
Order, including detailed procedures of the process which will satisfy the Government's minimum requirements.
The Government's rights in commercial software are governed by the licensor's commercial software license agreements (unless the license terms are inconsistent with Federal procurement law or do not otherwise satisfy user needs). The Offeror's proposal shall include all applicable commercial software license agreements (which include terms and conditions that govern the Governments use of commercial software deliverables).
The Government shall not accept any commercial software license terms that conflict with federal procurement law or do not satisfy user needs. Commercial Software License terms that are unacceptable to the Government include (but are not limited to) indemnification provisions (and other types of provisions that include unauthorized or unbudgeted funding obligations), attorney's fees provision, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.
Pursuant to the requirements set forth in DFARS 252.227-7017, Offerors are required to specifically identify Data/Software Rights
Assertions related to technical data and software deliverables (at the base contract level and task order level). As indicated in DFARS
252.227-7017(e), an Offeror's failure to submit, complete, or sign the aforementioned Data and Software Rights Assertions with its offer may render the offer ineligible for award. In accordance with the content and formatting requirements for Data and Software Rights
Assertions (set forth in DFARS 252.227-7017), the Offeror's Data and Software Rights Assertions shall comply with the following requirements:
1) The Offeror shall not assert license restrictions on items, component, or processes themselves. The asserted license restrictions shall pertain to software or technical data that relates to items, components, or processes.
2) The Offeror's Assertions shall not include technical data or software that will not be furnished to the Government under this
Contract.
3) The Offeror shall provide a concise (but specific) description of the technical data and software deliverables that will be furnished to the Government with restrictions, rather than generically asserting license restrictions in "technical data" or "technology".
4) The Offeror is responsible for ensuring that Data and Software Rights Assertions from its subcontractors comply with the aforementioned content and formatting requirements (in accordance with DFARS 252.227-7017).
Offerors shall provide Data/Software Rights Assertions in a tabular format prescribed in DFARS 252.227-7017. However, in addition to the content and formatting requirements set forth in DFARS 252.227-7017, the Offerors Data/Software Rights Assertions table shall list technical data and software items that the Offeror intends to furnish to the Government with and without license restrictions. Thus, the Data/Software Rights Assertions table may include technical data and software items that are provided to the Government with an unlimited rights license. In the Offerors identification of technical data and software license rights, the Offeror shall use the prescribed categories of license rights referenced in DFARS 252.227-7014 and DFARS 252.227-7015 (e.g,. "Limited Rights", "Government
Purpose Rights", "Unlimited Rights", "Unrestricted Rights", or "Commercial Software License Agreement").
L.2.2.5 Subfactor 4: Quality Assurance Surveillance Plan (QASP)________________________________________________________________
In accordance with FAR 37.604 and FAR Subpart 46.4, the Offerors shall propose a QASP which describes how its performance shall be measured against the requirements of the Section J, Attachment 0003; Sample Task Order. Offerors shall submit a QASP that includes key metrics that will be used by the Government to assess the contractors quality of performance throughout the period of performance of the
Sample Task Order. At minimum, offerors proposals shall include the following key metrics within their proposed QASP (offerors are encouraged to propose more than the minimum):
12 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
Cost control.
Contractor Resource Control.
Performance.
Each metric proposed including the above key metrics shall include at a minimum its performance objective, standard to be met for evaluation of performance success, and how the Government shall conduct the surveillance to ensure the metric proposed is accurately measured and assessed. The metrics proposed shall be logical, relevant to the effort, and sufficient to measure performance. The proposed standard/Acceptable Quality Level (AQL) to be met shall be quantifiable. Additionally, the proposed QASP shall be based on the premise that the offeror, not the Government, is responsible for management and Quality Checks/ Quality Assurance (QC/QA) actions to successfully meet the terms of the contract. The QASP shall be proposed in a table format in accordance with Section J, Attachment 0002;
titled "RFP Section L Tables" Table L-2: QASP Template.
L.2.3 VOLUME III Past Performance__________________________________
Factor 2 Past Performance
This volume shall consist of all information, required to support the Offerors proposed approach to Past Performance requirements.
Proposal cover page, table of contents pages, separation pages between Sections, Government Test Reports, and attachments will not be counted toward the page limitation. Any pages exceeding the limitations identified below will not be evaluated.
Offerors are reminded that while the Government may elect to consider data obtained from other sources, the burden of providing thorough and complete past performance information rests with the Offeror.
Offerors shall submit three (3) recent and relevant past performance examples as defined below:
Recent - The effort shall have been performed since 1 October 2013. Past performance information that fails the recent condition will not be evaluated.
Relevant - Present or past performance similar in scope, magnitude of effort, and complexity may include, but is not limited to; (i) porting WNW, SRW, SINCGARS, or eOTAM waveforms to waveform development environment ecosystems and/or tactical software defined radios,
(ii) performing root cause analysis to problems in WNW, SRW, SINCGARS, and/or eOTAM waveforms, fixing the problems, and validating resolution, (iii) conducting information assurance and JTNC API self-certification on waveform source code, (iv) delivering modified waveform source code and supporting documentation to the Government for reuse by other NDI vendors and other Programs of Record, (v) condcuting NSA certification on tactical software defined radios including WNW, SRW, SINCGARS, and/or eOTAM waveforms.
One example constitutes: one (1) contract, one (1) order, OR multiple orders under the same IDIQ contract or BPA for identical requirements.
Each example shall not exceed three (3) pages and shall include the following:
a. Contract number, order number if applicable, CAGE code, DUNS number, and North American Industry Classification System (NAICS) code
b. Government contracting activity, Contracting Officer name, telephone number, and email address
c. Government Contracting Officer Representative (COR) and/or technical representative, telephone number, and email address
d. Government contract administration activity, Administrative Contracting Officer (ACO) name, telephone number, and email address
e. If Offeror performed as a subcontractor, prime contractor company name, point of contact name, telephone number, and email address in lieu of or in addition to the contact information required in (b), (c), and (d) above
f. Contract type
g. Awarded price/cost
h. Final (actual) or projected final (if ongoing) price/cost
i. Final (actual) or projected final (if ongoing) start and end dates of the period of performance
j. Percentage of effort, based on the total cost of the work required in the referenced contract or order, performed by the Offeror itself as prime contractor or subcontractor at the time of proposal submission
k. Description of the specific tasks or activities performed by the Offeror itself under the contract
l. Narrative: Offerors shall provide a narrative for each past performance example. The narrative shall describe the contract listed, the contract objectives achieved by the Offeror, and how the contract is relevant to the requirements of this solicitation.
m. Self-assessment: Offerors shall provide a self-assessment for each past performance example. The self-assessment shall address performance, including if the contractor met the schedule and technical requirements within the original estimated cost. If the original cost, schedule, or technical requirements of the contract were not met, the Offeror shall provide a brief explanation of the reason(s) the original requirements were not met and any corrective actions taken by the contractor. The Offeror shall identify each time the schedule (period of performance) or cost ceiling was revised and provide an explanation of why each revision was necessary.
Offerors shall submit copies of any and all of the following received on any contracts or orders within the past three (3) years, including those not proposed in response to this solicitation. There is no page limit for the required copies.
a. Termination for default (including the settlement agreement)
b. Notice of default (including the settlement agreement)
13 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
c. No-cost settlement (including the settlement agreement)
d. Show cause notice
e. Cure notice
f. Suspension or Debarment
g. Any security inspection or assessment ratings or reports indicating security programs or facilities are less than satisfactory, and/or any suspensions or revocations of a facility security clearance
h. Notifications received for violations of FAR 32.006
Offerors shall include a narrative explaining each event above, including any corrective actions taken, not to exceed one (1) page per event. Submission requirements page in accordance with L.1.2 are not included in the page limitations.
If none of the above were received within the past three (3) years, the Offeror shall state so in the proposal.
Offerors shall state if they have no recent or relevant past performance.
Joint Ventures______________
If an Offeror proposes as a legal joint venture, the CAGE provided shall be specifically for the joint venture submitting the proposal as the Offeror. If an Offeror proposes using the CAGE for only one of the companies participating in the joint venture, that company shall be considered the one and only Offeror, and the past performance of partners, teammates, or subcontractors shall not be submitted.
If an Offeror proposes as a legal joint venture, past performance examples from individual partners may be submitted; the Offeror shall note the relationship of the partner to the joint venture.
Predecessor Companies_____________________
If the proposed past performance was performed by a predecessor company, provide the information for the recent and relevant contract of the predecessor company, document the history of the evolution from the predecessor company, and provide explanation for why the past performance information of the predecessor company should be attributed to the Offeror, not to exceed one (1) page. Any past performance of a company that in the future might, but has not yet, become part of the Offeror's company, including but not limited to any pending novation agreements, mergers, and acquisitions, will NOT be considered. Any past performance of a predecessor company or division divested away from the Offeror also will NOT be considered. Submission requirements in accordance with this paragraph are not included in the page limitations for the three (3) recent and relevant past performance examples required above.
If an Offeror proposes a past performance example under a different CAGE from the Offeror, the Offeror shall describe the relationship within the legal entity of the Offeror and include an affirmative statement that the example was performed by the same legal entity as the Offeror and is not the past performance of a subcontractor or teammate.
Past performance information may be obtained from established systems such as the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), or other databases; and may be obtained from other sources available to the Government, such as the Defense Contract Management Agency; and interviews with Program Managers, Contracting Officers, Fee Determining Officials.
L.2.4 VOLUME IV Small Business Utilization Plan________________________________________________
Factor 3 Small Business Utilization Plan
1) The Extent of Small Business Participation Factor Volume is comprised of a single volume. Offerors are responsible for including sufficient detail to permit a complete evaluation.
2) All large business Offerors shall submit either: a) a complete copy (inclusive of all signatures) of its approved Small Business
Subcontracting Plan (Test Program) in accordance with (IAW) Defense Federal Acquisition Regulation Supplement (DFARS) 252.219-7004; or
b) a copy of its proposed Small Business Subcontracting Plan for this solicitation.
3) The Small Business Subcontracting Plan (Test Program)/Small Business Subcontracting Plan is not a requirement for evaluation in source selection, but is a requirement for award to a large business and will be incorporated into any resultant contract. The Offeror shall not submit its Small Business Subcontracting Plan (Test Program)/Small Business Subcontracting Plan as its Small Business
Participation Plan.
4) All Offerors shall submit a Small Business Participation Plan, which shall include the following information:
a. The extent to which the prime Offeror has proposed a first tier small, small disadvantaged, women-owned, Historically Underutilized
Business Zone (HUBZone), and service-disabled veteran-owned small business subcontractors which meet or exceed the following goals for this procurement based upon percent of total contract value:
SMALL BUSINESS CATEGORY: GOAL
Small Business: 10.00%
Small Disadvantaged Business: 3.00%
Women-Owned Small Business (WOSB): 2.50%
HUBZone: 0.50%
Service Disabled Veteran-Owned Small Business (SDVOSB): 0.50%
14 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
Offerors may propose lower small business participation percentages than the Small Business goals for this procurement identified above.
However, those offerors shall explain in detail in its proposal why the Government's goals cannot be met and why its proposed small business goals are realistic. Failing to provide a detailed explanation shall result in an offorer's proposal being found unacceptable and ineligible for award.
(NOTE: A participation plan that reflects 1% of the contract value for WOSB would also count towards the overall Small Business Goal.
The Small Business Participation Plan and negotiated goals are a material portion of the resultant contract. The content of the plan will be utilized in the compliance evaluations to be conducted thereafter.)
b. Submit the total combined percentage of work to be performed by both large and small businesses (include the percentage of work to be performed both by Prime and Subcontractors):
Example: If Prime proposed a price of $1,000,000 (including all options), and small business(es) will provide $250,000 in services/supplies as a prime or subcontractors, the % planned for small business is 25%; and 75% for large business equaling 100%.
* Note: When combined, Large and Small Business totals shall equal 100%.
c. State the total percentage of participation to be performed by each type of subcategory small business. An Offeror that qualifies as a small business shall include its prime Contractor dollars in calculating its proposed percentage goals in all of the small business categories that it qualifies for. The percentage of work performed by small businesses that qualify in multiple small business categories may be counted in each category.
Example: Victory Prop Mgt (WOSB and SDVOSB) performing 2%; and Williams Group (SDB, HUBZone, and WOSB) performing 3%. Results equate to:
SDB 3%, HUBZone 3%, WOSB 5%, SDVOSB 2%).
* NOTE: The sum of all the percentages need not equal 100% as individual subcontractors may be counted towards more than one category.
All percentages shall use TOTAL CONTRACT VALUE as a baseline.
d. The extent to which such firms, as defined in FAR Part 19, are specifically identified in proposals. The Offeror shall provide a listing of all proposed sub-contractors, their Commercial and Government Entity (CAGE) code(s) (if assigned), and respective type of business concern. Any sub-contractor identified as an 8(a) or HUBZone SHALL have an active Small Business Administration (SBA) certification of its status at the time of proposal. Any proposed sub-contractors with multiple CAGE codes shall include all of the codes where work will be performed for this acquisition. If any proposed sub-contractor does not have a CAGE code by the due date for receipt of proposals under this solicitation, the Offeror shall annotate N/A, as applicable.
e. Describe the extent of commitment to use small businesses as defined by FAR 19, as subcontractors. Offerors that have enforceable agreements shall provide fully executed copies (i.e. the entire agreement and not just the first and last pages). An enforceable commitment is defined as a written and signed agreement (by both parties) that details that all parties have agreed to a business relationship for this procurement. This document shall be clear that both parties have defined and agreed to the extent of the relationship to include the type or types of work the sub-contractors/partners shall perform and what areas of the SOW they will cover.
The agreement shall be specific in nature.
f. A list of supply/service each small business will provide. Offerors shall provide a detailed explanation (i.e. references to
Statement of Work, etc.) to demonstrate the variety and complexity of work for each Small Business listed within the Utilization Plan.
g. The realism of the proposal. Provide narrative information on how requirements for this effort were developed and why they are realistic. Requirements that simply reflect an Offerors goals stated in its comprehensive subcontracting plans approved under DFARS
252.219-7004, or a company / division-wide commercial subcontracting plan will not be considered realistic, as the Small Business
Participation Plan requires all Offerors to submit a proposal that addresses the requirements of this specific solicitation.
h. Small Business (SB) Sub-Category participation shall be expressed in dollars and percentages of TOTAL CONTRACT VALUE in each of the applicable authorized six digit 2012 North American Industry Classification System (NAICS) Industry Subsectors that the Offeror believes best describes the product or service planned for subcontracts (available at: ) and a total target for SB sub-categories participation by the Offeror. SB sub-category targets by NAICS code shall be incorporated into any resulting contract and the Offeror shall be required to report SB sub-category participation.
L.2.5 VOLUME V Cost/Price__________________________
Factor 4 Cost/Price
For proposal purposes, Offerors shall assume an award date of 08 January 2018 for both the base contract and Sample Task Order.
The Contracting Officer has determined there is a high probability of adequate price competition for this acquisition. However, in accordance with FAR 15.402, and FAR 15.403-4; if at any time during this solicitation the Contracting Officer determines that adequate
15 17
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
price competition no longer exists; the Offeror may be required to submit Certified Cost or Pricing Data to support a determination of a fair, reasonable, and realistic price.
Volume V, Part 1 "Management Data CDRLs" (Base Contract CDRL's)
The Offeror shall propose a seperate Firm-Fixed-Price (FFP) for the three (3) CDRL's, (ELINs C001, C002, and C003) in Section B, under
CLIN 0010 of the base contract. Prices proposed in response to Exhibit C, "ADMINISTRATIVE MANAGEMENT DATA CDRL (PRICED)" shall be valid for 365 days from the date of contract award and incorporated into the base contract as ceiling prices for the first year of the ordering period.
Volume V, Part 2 "SINCGARS v3.0: Cryptographic Modernization Initiative (CMI) Effort" (Sample Task Order)
The Offeror shall propose a separate cost and fee in Volume V in accordance with the requirements/tasks of Section J, Attachment 0003;
Sample Task Order Section B, CLINs 0001 and 0002. The higher of the fees proposed on CLINs 0001 and 0002 of the Sample Task Order, shall establish the maximum fee for all non experimental, development, or research work for Cost Plus Fixed Fee (CPFF) work to be performed throughout the duration of the contract and shall be implemented in section H-7 of the base contract at contract award.
The Offeror shall include all required costs to complete the requirements/tasks of the Sample Task Order. Offerors shall reference
Sample Task Order PWS paragraphs, and provide individual cost elements associated with the respective CLIN/SLIN in accordance with the instructions of this section (L-22).
The Offerors and/or…
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 .