14RJT81_0002.pdf
PDF 34 KB Posted
- Solicitation number
- N0016414RJT81
About this file
14RJT81_0002
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 14RJT81_0001.pdf | ||
| 14RJT81_sol.pdf | ||
| 14RJT81_sol_att.zip | ZIP file | |
| 14RJT81_syn.docx | DOCX document | |
| 14RJT81_syn_att.zip | ZIP file |
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
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 is to answ er technical questions and add clauses. See pages 2-5.
Note: Due to the date of issuance of Amendment 02, offeror's are permitted to sign, date and submit electronic copies of Amendment 02 only. All other proposal requirements remain unchanged.
1. CONTRACT ID CODE PAGE OF PAGES
J 1 5
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 11-Jul-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 N00164-14-R-JT81
X 9B. DATED (SEE ITEM 11)
01-May-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
11-Jul-2014
CODE
NAVAL SURFACE WARFARE CENTER CRANE DIV
D. BRIGHT (812-854-2938)
BLDG 3422
300 HIGHWAY 361
CRANE IN 47522-5001
N00164 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N00164-14-R-JT81
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION E - INSPECTION AND ACCEPTANCE
The following have been added by full text:
HQ E-2-0015 QUALITY MANAGEMENT SYSTEM REQUIREMENTS (NAVSEA) (SEP 2009)
Quality Management System Requirements. The Contractor shall provide and maintain a quality management system that, as a minimum, adheres to the requirements of ANSI/ISO/ASQ 9001-2008 Quality Management Systems and supplemental requirements imposed by this contract. The quality management system procedures, planning, and all other documentation and data that comprise the quality management system shall be made available to the Government for review. Existing quality documents that meet the requirements of this contract may continue to be used. The Government may perform any necessary inspections, verifications, and evaluations to ascertain conformance to requirements and the adequacy of the implementing procedures. The Contractor shall require of subcontractors a quality management system achieving control of the quality of the services and/or supplies provided. The Government reserves the right to disapprove the quality management system or portions thereof when it fails to meet the contractual requirements.
(End of Text)
NOTES
When used cite ANSI/ISO/ASQ 9001-2008 in paragraph (b) of FAR 52.246-11, HIGHER LEVEL CONTRACT REQUIREMENT. If another non-DoD quality system is used, insert the appropriate system title.
In implementing ANSI/ISO/ASQ 9001-2008, it may be desirable to include topics not thoroughly addressed in 9001-2008. Listed below is the title of standardized text, included elsewhere in Section E, for areas where such supplementation is desired for a given contract. Use is not mandatory and paragraphs should be selected to work in conjunction with other contract quality requirements. In accordance with current policy guidance, supplementation should be limited to those areas listed below.
– CALIBRATION SYSTEM REQUIREMENTS (HQ E-2-0003)
– COST QUALITY DATA (HQ E-2-0004)
– GOVERNMENT FURNISHED MATERIAL (HQ E-2-0006)
– INSPECTION AND TEST RECORDS (HQ E-2-0008)
– QUALITY IN SOFTWARE DEVELOPMENT AND PRODUCTION (HQ E-2-0014)
– USE OF CONTRACTOR’S INSPECTION EQUIPMENT (HQ E-2-0017)
Add reference to a Data Item Description for a program specific quality management system plan, if deemed necessary (see DoD 5010.12-L, Acquisition Management System and Data Requirements Control List).
HQ E-2-0008 INSPECTION AND TEST RECORDS (NAVSEA) (MAY 1995)
Inspection and Test Records: Inspection and test records shall, as a minimum, indicate the nature of the observations, number of observations made, and the number and type of deficiencies found. Data included in inspection and test records shall be complete and accurate, and shall be used for trend analysis and to assess corrective action and effectiveness.
HQ E-2-0014 QUALITY IN SOFTWARE DEVELOPMENT AND PRODUCTION
(NAVSEA) (MAY 1995)
Quality in Software Development and Production: The contractor's software quality program shall be an integral part of the overall Quality Assurance Program. Software quality program controls shall be applicable to all project software that is developed, maintained, or modified within the following categories:
(a) All deliverable software
(b) All deliverable software that is included as part of deliverable hardware or firmware.
(c) Non deliverable software (commercially available or user-developed) used for development, fabrication, testing, or acceptance of deliverable software or hardware (includes automated fabrication, test, and inspection/acceptance equipment software and software design, test, and inspection tools).
(d) Commercially available, reusable, or Government software designated as part of a deliverable item.
HQ E-2-0016 SUPPLEMENTAL QUALITY REQUIREMENTS (NAVSEA)
(MAR 2001)
Supplementary Quality Requirements: The contractor shall implement a documented inspection system in accordance with the following paragraphs/subparagraphs of ANSI/ASQC Q9002-1994, Quality Systems - Model for Quality Assurance in Production, Installation, and Servicing:
4.2 Quality System
4.2.1 General
4.2.2 Quality System Procedures
4.5 Document and Data Control
4.5.1 General
4.5.2 Document and Data Approval and Issue
4.5.3 Document and Data Changes
4.6 Purchasing
4.6.1 General
4.6.4.2 Customer Verification of Subcontracted Product
4.7 Control of Customer-Supplied Product
4.9 Process Control
4.10 Inspection and Testing
4.10.1 General
4.10.2 Receiving Inspection and Testing
4.10.2.1 Receiving Inspection and Testing
4.10.2.2 Receiving Inspection and Testing
4.10.2.3 Receiving Inspection and Testing
4.10.3 In-process Inspection and Testing
4.10.4 Final Inspection and Testing
4.10.5 Inspection and Test Records
4.11 Control of Inspection, Measuring, and Test Equipment
4.11.1 General
4.11.2 Control Procedures
4.12 Inspection and Test Status
4.13 Control of Nonconforming Product
4.13.1 General
4.13.2 Review and Disposition of Nonconforming Product
4.14 Corrective and Preventive Action
4.14.2 Corrective Action
4.16 Control of Quality Records
The Contractor may also elect to use another inspection system meeting the above requirements. Whichever inspection system the Contractor elects to implement shall be utilized throughout the entire life cycle of the contract.
In addition, the Contractor shall notify the PCO and the cognizant ACO, in writing, which system is selected.
HQ E-2-0017 USE OF CONTRACTOR’S INSPECTION EQUIPMENT
(NAVSEA) (MAY 1995)
Use of Contractor’s Inspection Equipment: The contractor's gages, and measuring and testing devices shall be made available for use by the Government when required to determine conformance with contract requirements. If conditions warrant, the contractor’s personnel shall be made available for operations of such devices and for verification of their accuracy and condition.
(End of Summary of Changes)
The following items are applicable to this modification:
TECHNICAL QUESTIONS
1. Q: This question pertains to technical proposal requirement documentation. In CNIN-L-0002, under Volume II –Subfactor C: Management Approach – is there an expectation that “all” Statement of Work (SOW) pargraphs 3.1 and 3.2 functions be addressed in the 10 page limit? Also, SOW function 4.0 is not addressed in the Volume. Is this to be addressed?
A: The Government’s intent is for the offeror to address areas within SOW Section 3.0 REQUIREMENTS that the offeror has relevant experience and capability as it applies to the specific technology area listed within SOW Section 1.2. Not all 3.0 functions will be required for each Job Order, it will be task dependent.
Yes, SOW section 4.0 should be addressed within the technical proposal.
2. Q: Section L instructions state that “A copy of the offeror’s SAM registration information from the SAM website”. Is a summary printout of the general information screen that is available after searching the organization by CAGE or DUNS acceptable?
A: Yes, a summary printout of the general information screen that is available is sufficient.
3. Q: This question pertains to past performance proposal requirement documentation. The Past Performance proposal is limited to a one (1) page matrix and a one (1) page narrative per reference. In order to show the required proof that the Past Performance questionnaire have been sent to the respective POCs, are we able to provide the email confirmations as an attachment to this Volume?
A: Yes, providing e-mail confirmations as an attachment is acceptable,
File details come from the government source that posted it. Updated .