PPN_and_TN_Submission_Template.docx
DOCX document 32 KB Posted
- Attached to
- SBEAS FINAL REQUEST FOR PROPOSAL Federal contract opportunity
- Solicitation number
- FA8771-17-R-1000
About this file
See attachment.
View the file
Other files for this federal contract opportunity
Show all 50
SBEAS FINAL REQUEST FOR PROPOSAL has more files on GovTribe.
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
Technical Experience Narrative Submission Template
Volume II – Technical Narratives (TNs) INSTRUCTIONS (delete prior to submission): These instructions apply to all TNs submitted.
Project Name: Enter the name of the project for each TN.
Contract/Project Number: Enter the project’s Contract Number/Project Number (or equivalent). If proposing as a Joint Venture (JV), the Offeror shall enter the JV company name and if the reference is NOT in the name of the JV, then the Offeror shall also enter the member name.
Period of Performance (PoP): Enter start and end dates of performance for the project.
Narrative: Use this space to describe the technical experience that supports all the technical elements where points are claimed on the self-scoring worksheet in relation to the referenced contract for the project. Offeror may address multiple technical elements in each technical narrative; however, each narrative shall only reference one project/ contract number.
Do NOT repeat a project’s contract number in different TNs. You may submit no more than six narratives (but may submit fewer if fewer than six narratives support the points you claim). The pages allotted may be used at the Offeror’s discretion, but cannot exceed 20 pages for all six TNs. (For example, Offerors may be using TN #1 (Contract reference #1) to cover points taken for multiple sub-elements so the Offeror may choose to use 8 pages for TN #1; but TN #2 may only cover points taken for one sub-element, so it may only take one page.)
TN #1
Project Name: XYW Logistics Systems Support Contract/Project Number: FA8771-15-F-XXXX Period of Performance (PoP): 31 November 2014 – 29 October 2017 Technical narrative: XYW Logistics Systems Support….
TN #2
(This example shows how to combine 3 task orders under an IDIQ) Project Name: Ground System Software Maintenance and Migration Services Contract/Project Number: FA8771-15-D-XXXX: Task Order Number FA8771-15-D-XXXX XXXX; Task Order Number FA8771-15-D-XXXX XXXX; Task Order Number FA8771-15-D-XXXX XXXX Period of Performance (PoP): 15 July 2015 – 14 July 2016 Technical narrative: Ground System…
TN #3
(This example shows how to list JV references that are NOT in the name of the JV) Project Name: Ground System Software Maintenance and Migration Services Contract/Project Number: FA8771-15-C-XXXX: (JV Company Name, Member Company Name) Period of Performance (PoP): 15 July 2015 – 14 July 2016 Technical narrative: Ground System…
Past Performance Narrative Submission Example Volume III – Past Performance Narratives (PPNs) INSTRUCTIONS (delete prior to submission): These instructions apply to all PPNs submitted.
Project Name: Enter the name of the project for each PPN.
Contract/Project Number: Enter the project’s Contract Number/Project Number (or equivalent). If proposing as a Joint Venture (JV), the Offeror shall enter the JV company name and if the reference is not in the name of the JV, then the Offeror shall also enter the member name.
Period of Performance (PoP): Enter start and end dates of performance for the project.
Narrative: Use this space to describe past performance that supports the three (3) past performance sub-factors in relation to the referenced project for which you provided a contract/project number. Offeror may address multiple sub-factors in each Past Performance Narrative; however, each narrative shall only reference one project’s contract number. Do NOT repeat a project’s contract numbers in different PPNs. You may submit no more than six narratives (but may submit fewer if fewer than six narratives support your past performance for the sub-factors).
The pages allotted may be used at the Offeror’s discretion, but cannot exceed 25 pages for all PPNs. (For example, Offeror may be using PPN #1 (Contract reference #1) to cover two sub-factors, so the offeror may choose to use 15 pages for PPN #1; but PPN #2 may only cover part of one sub-factor so it may only take 1 page.)
PPN #1
Project Name: XYW Logistics Systems Support Contract/Project Number: FA8771-15-F-XXXX Period of Performance (PoP): 31 November 2014 – 29 October 2017 Technical narrative: XYW Logistics Systems Support….
PPN #2
(This example shows how to combine 3 task orders under an IDIQ) Project Name: Ground System Software Maintenance and Migration Services Contract/Project Number: FA8771-15-D-XXXX: Task Order Number FA8771-15-D-XXXX XXXX; Task Order Number FA8771-15-D-XXXX XXXX; Task Order Number FA8771-15-D-XXXX XXXX Period of Performance (PoP): 15 July 2015 – 14 July 2016 Technical narrative: Ground System…
PPN #3
(This example shows how to list JV references that are NOT in the name of the JV) Project Name: Ground System Software Maintenance and Migration Services Contract/Project Number: FA8771-15-C-XXXX: (JV Company Name, Member Company Name) Period of Performance (PoP): 15 July 2015 – 14 July 2016 Technical narrative: Ground System…
File details come from the government source that posted it. Updated .