A_E_IDIQ_Sources_Comment_Matrix__2-08-16_IDIQ_Montana.pdf

PDF 37 KB Posted

Attached to
USDA-NRCS MONTANA LAND SURVEY ID/IQ
Solicitation number
AG-4D90-S-16-0004
Issued by

View the file

Other files

File Type Posted
AG-4D90-S-16-0004_DRAFT.pdf PDF
AG-4D90-S-16-0004_DRAFT.pdf PDF

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

COMMENTS MATRIX FOR NRCS-NM ISSUANCES: USDA-NRCS Montana Land Survey ID/IQ

(Please read instructions on back before completing form.)

# CLASS

COMPONENT AND

POC NAME, PHONE,

AND E-MAIL

PAGE # PARA # COMMENT

TYPE (C/S) COMMENTS, JUSTIFICATION, AND ORIGINATOR JUSTIFICATION FOR RESOLUTION

A/ R/ P

SD FORM 818, JAN 09 PREVIOUS EDITION IS OBSOLETE

e-mail dated 1/21/2016

S

Bidder Comment: Could you please clarify whether this Area is Montana or if there are specific areas within MT.

Requirement: FACTOR NO.6. LOCATION IN THE GENERAL GEOGRAPHIC

AREA OF THE PROJECT AND KNOWLEDGE OF THE LOCALITY OF THE

PROJECT AREA. Evaluation will be based on the firms location to the geographic area for each of the Areas for which they wish to be considered and knowledge of the locality of the Area. For firms outside the general project area(s) provide a plan to provide service in a cost effective manner.

Firms must dearly indicate the office location from which the work will be performed. For firms outside of the general project area, provide a plan to provide service in a cost effective manner.

Resolution: Montana. Firms that cannot perform these efforts throughout the state would be ranked lower in this category. The government may find that geo-graphic division to obtain the services will be best, but cannot make that determination at this time.

The sources sought notice is specifically aimed to determine a firm/s ability to meet the requirement statewide. Should no firm be able to do this, then the Government may issue multiple regional ID/IQ or other contractual instruments based upon responses to the call for SF-330s.

A

# CLASS

COMPONENT AND

POC NAME, PHONE,

AND E-MAIL

PAGE # PARA # COMMENT

TYPE (C/S) COMMENTS, JUSTIFICATION, AND ORIGINATOR JUSTIFICATION FOR RESOLUTION

A/

1/19/2016 and 1/22/2016

Bidder Comment:

(1) What is the estimated volume of work expected under this contract?

(2) Is the maximum for all 5 years (base year + 4 option years) $2,500,000 or $500,000?

This clarification will help us properly address the capacity question.

Resolution: Reviewing prior year purchase data under the FOIA, this estimated volume will be re-phrased.

Data from 2012-2015, PSC Code R404 (NAICS 541370) for Montana:

FY12 - 7 Orders; Total Value $28,847.08 FY13 – 6 Orders; Total Value $63,275.64 Realistic volume will be between $0 and $100,000 per year; total potential overall value $500,000.

A

3 e-mail dated 1/19/2016

C Bidder Comment: What firm or firms are currently under contract to do this work?

Resolution: None. Current services are purchased on an ad-hoc basis.

A

4 e-mail dated 1/19/2016

Bidder Comment: Are the six evaluation factors weighted equally or do some have more weight than others, such as in a points system?

Resolution:

Factor 1: PROFESSIONAL QUALIFICATIONS – 15 Points Factor 2: SPECIALIZED EXPERIENCE – 25 points Factor 3: CAPACITY – 15 points Factor 4: QUALITY – 15 points Factor 5: PAST PERFORMANCE – 20 Points Factor 6: LOCATION – 10 points

P

5 e-mail dated 1/19/2016 S

Bidder Comment: Will this program be run out of your Bozeman office or some other office?

Resolution: The program will be administered by a contracting officer located in a different state. The Contracting Officer Representative (COR) will be located within the tasking geographic location within MT.

1/19/2016 Bidder Comment: Are you currently requesting solicitations in other Northern Plains states besides Montana at this time? If so which ones?

Resolution: No. Notice AG-1A23-S-16-0003 was posted to FedBizOpps on 12/9/2015 and closed on 1/9/2016. This was for the state of Michigan.

# CLASS

COMPONENT AND

POC NAME, PHONE,

AND E-MAIL

PAGE # PARA # COMMENT

TYPE (C/S) COMMENTS, JUSTIFICATION, AND ORIGINATOR JUSTIFICATION FOR RESOLUTION

A/

INSTRUCTIONS FOR COMPLETING SD FORM 818

COORDINATING OSD COMPONENT: Use this form to provide consolidated critical and substantive comments to the OSD Component that originated the issuance. Complete the classification header and footer, columns 1 through 5, and the first two entries in column 6. REVIEW THE COMMENTS, RESOLVE ANY CONFLICTING VIEWS, AND CONFIRM THAT THE COMPLETED MATRIX ACCURATELY REPRESENTS YOUR COMPONENT’S POSITION. Upload the form to the DoD Directives Program Portal IN MICROSOFT WORD FORMAT, with a scanned copy of the sign SD Form 106, “DoD Directives Program Coordination Record,” or coordination memorandum.

ORIGINATING OSD COMPONENT: Use this form to consolidate comments from all coordinators and to record adjudication of the comments. (To add comments from an SD 818 submitted by a coordinator, use the “Copy” and “Paste” tools on the Microsoft Word Standard Toolbar.) When consolidating comments, place them in the order of the pages/paragraphs they apply to (e.g., all comments from all coordinators that apply to page 1, paragraph 1.a., should be grouped together as the initial entries; all comments that apply to page 1, paragraph 1.b., should be grouped together next, and so on). Complete column 7 and the third entry in column 6. Adjust the classification header and footer and columns 1 and 2 as appropriate.

CLASSIFICATION – Enter the highest classification of the comments. If all are unclassified, mark the header and footer accordingly and ignore the column.

COLUMN 1 – Enter the number of the comment. Enter comments in the order of the pages/paragraphs they apply to.

COLUMN 2 – Enter the classification of the comment. If all comments are unclassified, mark the header and footer accordingly and ignore the column.

COLUMN 3 – Enter the appropriate information.

COLUMN 4 – Enter the appropriate information.

COLUMN 5 – Enter the appropriate information.

COLUMN 6 – Enter the comment type. Place only one comment per row. Do NOT include administrative comments concerning non-substantive aspects of an issuance, such as dates of references, organizational symbols, and/or grammatical errors.

(C) CRITICAL: When a Component has one or more critical comments, that Component’s coordination shall reflect a nonconcur. THE JUSTIFICATION FOR CRITICAL COMMENTS

MUST IDENTIFY:

– Violations of the law or contradictions of Executive Branch policy or of policy established in DoD issuances. The GC, DoD, or his or her representative shall identify legal objections as critical comments.

– Unnecessary risks to safety, life, limb, or DoD materiel; waste or abuse of DoD appropriations; or imposition of an unreasonable burden on a Component’s resources.

(S) SUBSTANTIVE: Substantive comments are made when a section in the issuance appears to be or is potentially unnecessary, incorrect, misleading, confusing, or inconsistent with other sections, or when a Component disagrees with the proposed responsibilities, requirements, and/or procedures. A substantive comment is usually not sufficient justification for a Component to nonconcur on an issuance. Several substantive comments when taken together may be grounds for a nonconcurrence.

COLUMN 7 – COORDINATING COMPONENT: Enter the comment in the area provided. Enter your justification for the comment and your requested or recommended changes in the area provided.

YOU MUST PROVIDE CONVINCING SUPPORT FOR CRITICAL COMMENTS IN THE JUSTIFICATION.

– ORIGINATING COMPONENT: Enter your justification for disposition of the comment in the area provided. Include any related communications with the coordinating Component. You must provide convincing support for rejecting critical comments.

COLUMN 8 – Enter whether you accepted (A), rejected (R), or partially accepted (P) the comment. Your justification for disposition of the comment in column 6 must be consistent with this entry.

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