QUESTIONS_ATS_Cap_Dev__proposal.docx

DOCX document 349 KB Posted

Attached to
Tactical Air Traffice Services
Solicitation number
W9124G-17-T-0001
Issued by

About this file

Response to Questions/Additional Information

View the file

Other files

File Type Posted
PWS_PERFORMANCE_WORK_STATEMENT_FY17.pdf PDF
Solicitation.pdf PDF
WD.pdf PDF
QASP_ATS_Cap_Dev.pdf PDF
Quote_Sheet.doc DOC document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

QUESTIONS

Do you need proposals or resumes in addition to the bid?

We need proposals or letters of intent; we would like resumes.

How should the travel CLINS be bided on?

We are not allowing bidding on travel. We have estimated travel requirements and cost. Once travel funding runs out, that is the end of travel.

What is the personnel requirements for the project?

We are not specifying how many personnel are required. We have provided the requirements for the work effort IOF the bidders to figure out how many are required. This allows us to discriminate between the bidders.

There are the mention of a Quality Manager and Program Manager as key positions but no mention of other employees.

These positions are not required for the project; but it is a reference to a company’s staff that manages a /their contractor/s employee/s so that we are not the ones supervising.

There is a wage determination chart included so we would like to verify the personnel level anticipated for this project in order to bid appropriately.

GS-12

PWS Section 3.0 identifies several instances of travel to TBD locations and also includes "Other conferences as identified by TCM-AB". The CLINs for travel (0001 and 0003) are FFP CLINs. It is impossible to provide a Firm Fixed Price for these CLINs based on the stated requirements. Will the Government consider providing a Not To Exceed (NTE) value for the Travel CLINs? If not, please provide more details as to travel locations and the locations, durations and number of "other conferences".

- Program Management Reviews (PMR) (4 days x 2) – Huntsville, AL

- User Conferences, (4 days x 2) – Huntsville, AL

- Fielding Conferences, (4 days x 2) – Huntsville, AL

- Airspace Conferences, (3 days) – Leavenworth, KS

- AIMS Conferences, (4 days) – Charleston, SC

- Central Technical Support Facility (4 days) – Killeen, TX

- Testing, Evaluation, Validation and Verification Events (10 days) – (5) Huntsville, AL / (5) Killeen, TX

- Network Integration Exercise, (15 Days) – El Paso, TX

PWS Section 4.0 refers to "the attached DD Form 254, Department of Defense Contract Security Classification Specification". Will this document be provided?

This document has already been approved by the USAACE Security Division.

The solicitation package includes a DOL Wage Determination (WD 15-4631) however, the applicability of this document is unclear as the following clauses, while mentioned in the RFP, have not been specified:

a) 52.222-17, Nondisplacement of Qualified Workers (May 2014) (E.O. 13495). Are there existing qualified employees that the Government wishes to retain?

No.

b) 52.222-42, Statement of Equivalent Rates for Federal Hires (MAY 2014) (29 U.S.C. 206 and 41 U.S.C. chapter 67). What are the equivalent labor categories and federal rates?

GS-12

c) 52.222-43, Fair Labor Standards Act and Service Contract Labor Standards--Price Adjustment (Multiple Year and Option Contracts) (MAY 2014) (29 U.S.C. 206 and 41 U.S.C. chapter 67). Will price adjustment be allowed if the Service Contract Act applies and the DOL Wage Determination is used?

No, this is Fix-firm price.

PWS Paragraph 7.4 requires a Travel Report within 3 business days of completion of travel. This appears to be inconsistent with the reporting required in section 3.0 Travel, and the supporting task deliverables listed in the table following section 7.5, and the reporting described in paragraph 7.7.2 which all mention five business days. Please clarify the requirement.

- PWS para 3.0, No change.

- PWS para 7.4 should read …a trip report within 5 working days after completion of travel. The trip report shall include…

- PWS para 7.5 Table, Task 3, line 8 – Timeline, should read “Within 5 working days after completion of travel”.

- PWS para 7.5 Table, Task 3, line 9 – Timeline, either delete entire line or change to read “Within 5 working days after completion of travel/event”.

- PWS para 7.7.2, should read “Within 5 working days after completion of travel”.

Paragraphs 2.0 and 7.7.1 of the Performance Work Statement (PWS) provides the required qualifications of the subject matter expert. However, the 16 page solicitation document (W9124G-17-T-0001) makes no reference to a technical response. Please confirm that at a minimum a resume for the SME is required as part of the quote submission.

As stated, we need proposals/letter of intent. Resumes will be great to have.

PWS paragraph 7.6.4 references a “technical portion” describing the Contractor’s approach to providing qualified personnel. However, the solicitation makes no reference to a technical portion. Please clarify if a technical portion is requested and the format and page limitation associated with requested response.

Submit no more than a two page industry standard resume that outlines a potential contractor candidate’s past and current performance (doesn’t the MICC require this?)

The solicitation document (W9124G-17-T-0001) makes no reference to a Government review of an offeror’s past performance. Please clarify whether the Government intends to review an offeror’s past performance.

Yes.

SF 1449 states the Method of Solicitation is Request for quotation (RFQ) and a Quote Sheet has been provided by the Government. Please clarify if this procurement will be evaluated using a Best Value approach taking into consideration price, technical capability, and past performance or if a low price technically acceptable evaluation will be made.

SME/technical approach is more important than cost.

Please provide an estimated start date for the Base Year and Option Year 1. Proposals are due on 23 January 17. It appears the earliest start date may be 1 February 2017 with a Base Year end date of 31 January 2018. However, Page 5 of the solicitation states the end delivery date for all CLINS are listed as 05 JAN 2017. Please clarify.

Start date should be O/A 6 Feb 17; Option Year 1 should be O/A 5 Feb 18.

image1.emf

DD FORM 254.pdf

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

(The requirements of the DoD Industrial Security Manual apply to all security aspects of this effort.)

1. CLEARANCE AND SAFEGUARDING

a. FACILITY CLEARANCE REQUIRED

b. LEVEL OF SAFEGUARDING REQUIRED

2. THIS SPECIFICATION IS FOR: (X and complete as applicable)

a. PRIME CONTRACT NUMBER

b. SUBCONTRACT NUMBER

c. SOLICITATION OR OTHER NUMBER DUE DATE (YYYYMMDD)

3. THIS SPECIFICATION IS: (X and complete as applicable)

a. ORIGINAL (Complete date in all cases)

REVISION NO.

c. FINAL (Complete Item 5 in all cases)

DATE (YYYYMMDD)

b. REVISED (Supersedes all previous specs)

4. IS THIS A FOLLOW-ON CONTRACT? YES NO. If Yes, complete the following:

Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract.

5. IS THIS A FINAL DD FORM 254? YES NO. If Yes, complete the following:

In response to the contractor's request dated , retention of the classified material is authorized for the period of

6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)

a. NAME, ADDRESS, AND ZIP CODE b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

7. SUBCONTRACTOR

a. NAME, ADDRESS, AND ZIP CODE b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

8. ACTUAL PERFORMANCE

a. LOCATION b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

9. GENERAL IDENTIFICATION OF THIS PROCUREMENT

10. CONTRACTOR WILL REQUIRE ACCESS TO: 11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL:YES NO YES NO

a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION

b. RESTRICTED DATA

c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION

d. FORMERLY RESTRICTED DATA

e. INTELLIGENCE INFORMATION

(1) Sensitive Compartmented Information (SCI)

(2) Non-SCI

f. SPECIAL ACCESS INFORMATION

g. NATO INFORMATION

h. FOREIGN GOVERNMENT INFORMATION

i. LIMITED DISSEMINATION INFORMATION

j. FOR OFFICIAL USE ONLY INFORMATION

k. OTHER (Specify)

a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT ANOTHER

CONTRACTOR'S FACILITY OR A GOVERNMENT ACTIVITY

b. RECEIVE CLASSIFIED DOCUMENTS ONLY

c. RECEIVE AND GENERATE CLASSIFIED MATERIAL

d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE

e. PERFORM SERVICES ONLY

f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE THE U.S., PUERTO RICO, U.S. POSSESSIONS AND TRUST TERRITORIES

g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL INFORMATION

CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION CENTER

h. REQUIRE A COMSEC ACCOUNT

i. HAVE TEMPEST REQUIREMENTS

j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS

k. BE AUTHORIZED TO USE THE DEFENSE COURIER SERVICE

l. OTHER (Specify)

DD FORM 254, DEC 1999 PREVIOUS EDITION IS OBSOLETE. Adobe Professional X

12. PUBLIC RELEASE. Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the Industrial Security Manual or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release

a. TYPED NAME OF CERTIFYING OFFICIAL

Direct Through (Specify)

d. ADDRESS (Include Zip Code)

Yes No to the Directorate for Freedom of Information and Security Review, Office of the Assistant Secretary of Defense (Public Affairs)* for review.

*In the case of non-DoD User Agencies, requests for disclosure shall be submitted to that agency.

13. SECURITY GUIDANCE. The security classification guidance needed for this classified effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes; to challenge the guidance or the classification assigned to any information or material furnished or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended. (Fill in as appropriate for the classified effort. Attach, or forward under separate correspondence, any documents/guides/extracts referenced herein. Add additional pages as needed to provide complete guidance.)

14. ADDITIONAL SECURITY REQUIREMENTS. Requirements, in addition to ISM requirements, are established for this contract.

(If Yes, identify the pertinent contractual clauses in the contract document itself, or provide an appropriate statement which identifies the additional requirements. Provide a copy of the requirements to the cognizant security office. Use Item 13 if additional space is needed.)

Yes No15. INSPECTIONS. Elements of this contract are outside the inspection responsibility of the cognizant security office.

(If Yes, explain and identify specific areas or elements carved out and the activity responsible for inspections. Use Item 13 if additional space is needed.)

16. CERTIFICATION AND SIGNATURE. Security requirements stated herein are complete and adequate for safeguarding the classified information to be released or generated under this classified effort. All questions shall be referred to the official named below.

b. TITLE c. TELEPHONE (Include Area Code)

e. SIGNATURE

17. REQUIRED DISTRIBUTION

a. CONTRACTOR

b. SUBCONTRACTOR

c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR

d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY ADMINISTRATION

e. ADMINISTRATIVE CONTRACTING OFFICER

f. OTHERS AS NECESSARY

DD FORM 254 (BACK), DEC 1999

fac_clear:

safe_level:

prime_no:

xprime: Off sub_no:

xsub: Off xsolic: Off solic_no:

due_date:

xspec3: Off orig_date:

rev_no:

rev_date:

final_date:

xfollowon: Off prec_no:

xfinal: Off req_dated:

period:

ctr_name:

ctr_cage:

ctr_ofc:

sub_name:

sub_cage:

sub_ofc:

perf_loc:

perf_cage:

perf_ofc:

gen_id:

x10a: Off x10b: Off x10c: Off x10d: Off x10e1: Off x10e2: Off x10f: Off x10g: Off x10h: Off x10i: Off x10j: Off x10k: Off other10k:

x11a: Off x11b: Off x11c: Off x11d: Off x11e: Off x11f: Off x11g: Off x11h: Off x11i: Off x11j: Off x11k: Off x11l: Off other11l:

xrelease: Off release_thru:

guidance:

xaddlsec: Off addl_sec:

xinsp: Off inspections:

cert_name:

cert_title:

cert_phone:

cert_addr:

x17a: Off x17b: Off x17c: Off x17d: Off x17e: Off x17f: Off other_dist:

File details come from the government source that posted it. Updated .