N00024-16-R-2449_J-2a_CDRL_Instructions.docx

DOCX document 31 KB Posted

Attached to
Landing Craft, Utility (LCU) 1700 Design Studies and Analysis
Solicitation number
N00024-16-R-2449
Issued by

About this file

N00024-16-R-2449 J-2a CDRL Instructions

View the file

Other files

File Type Posted
N00024-16-R-2449_Amendment_0005.docx DOCX document
N00024-16-R-2449_Amendment_0004.docx DOCX document
N00024-16-R-2449_Amendment_0003.docx DOCX document
N00024-16-R-2449_Amendment_0002.docx DOCX document
N00024-16-R-2449_Amendment_0001.docx DOCX document
N00024-16-R-2449.docx DOCX document
N00024-16-R-2449_J-4_Question_Submittal_Form.docx DOCX document
N00024-16-R-2449_J-3_PMS377_IDE_Service_Center.docx DOCX document
N00024-16-R-2449_J-2b_CDRLs__Exhibit_A.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

ATTACHMENT J-2a

LANDING CRAFT, UTILITY (LCU) 1700

DESIGN STUDIES AND ANALYSES

N00024-16-R-2449

CONTRACT DATA REQUIREMENTS LIST (CDRL)

INSTRUCTIONS

5 FEBRUARY 2016

GENERAL CDRL INSTRUCTIONS

Data item submittals shall be prepared in the Contractor's format, unless otherwise specified in the specific CDRL. Data item submittals shall be clear, legible, and prepared in the English language. Data items shall be assigned a sequential one-character revision letter to reflect changes from the previous submittal.

1. Electronic media and digital files shall be compatible with computers using the Windows 7 operating system, unless otherwise specified. The following electronic format products shall be utilized: Microsoft Office 2010 ™, Microsoft Project 2010 ™, Adobe Acrobat 9.0 ™, and AutoCAD 2009™ unless otherwise specified. Alternative software or versions of software may be used if agreed to between the Government and the Contractor. Electronic files shall not be password protected.

2. If provided to support an analysis, drawings shall be submitted in AutoCAD format and in PDF. Other documents shall not be submitted in PDF format unless specified in the Data Item's Data Description. Drawings shall not be submitted in "read only" formats. All engineering drawings and associated lists shall be as identified in TYPES AND APPLICATIONS OF ENGINEERING DRAWINGS, ASME Y14.24 and ASSOCIATED LISTS, ASME Y14.34M. Each drawing shall be assigned a Contractor drawing number.

3. Each data item shall be provided with a separate letter of transmittal. Multiple drawings or documents may be submitted under the same letter of transmittal; however subtitles, revision designations, and sheet quantities shall be identified. Each letter of transmittal shall be assigned a trackable correspondence serial number. Each letter of transmittal shall provide the following information:

· Contractor's name, correspondence serial number, and actual date of transmittal.

· The contract number, Data Item number and Data Item Title.

· A revision letter and respective revision date.

· Digital file name and respective digital file date.

· Each transmittal letter shall provide a brief explanation of the submittal.

4. In accordance with DODD 5230.24 and DODD 5230.25, each Data Item submittal shall include Distribution Statement D at the bottom of each cover sheet as follows:

“DISTRIBUTION STATEMENT D: Distribution authorized to the DoD and U.S. DoD Contractors only. Other requests shall be referred to PEO SHIPS, PMS377, Washington Navy Yard, 1333 Isaac Hull Ave. SE, Washington, DC 20376-2101."

ACRONYMS

An alphabetical list of acronyms follows. The list includes those acronyms used most frequently in the Contract Data Requirements List.

CDRLContract Data Requirements List
CLINContract Line Item Number
GFIGovernment Furnished Information
IAWIn Accordance With
IDEIntegrated Digital Environment
LTLetter of Transmittal
NLTNot Later Than
OTIMEOne Time
R/ASRRevisions as Required

GLOSSARY

The items listed below are explanations of the headings and blocks on the Data Requirements List (DRL).

DETAILED CDRL (DD FORM 1423) INFORMATION:

Block 01 – Data Item Number – The CDRL numbering system is maintained from the CDRL packages. If a CDRL is deleted, it retains its CDRL number in Block 01 but is annotated as “UNUSED” in Block 02.

Block 02 - Title of Data Item - Exact title of the DID cited in Block 04.

Block 03 - Subtitle - Title of the data item, if it differs from the official title of the DID or provides further identification.

Block 04 - Authority (Data Acquisition Document Number) – Block 04 contains the DID (DD Form 1664) number. DID identification number is the prefix code for a standard DID, Unique DID Item (UDI) for a unique DID and One-Time (OT) for a one-time DID. If more than one data item description number is listed, it indicates consolidation of two or more DIDs to meet the data requirement. This relationship will be further explained in Block 16. Its designated number and a copy will be attached.

Block 05 - Contract Reference - Indicates the specific effort within the contract from which data is a product or by-product.

Block 06 - Requiring Office - The office is responsible for advising the contracting officer on the technical adequacy of the data.

Block 07 - DD Form 250 Requirement – Except in extraordinary cases, Block 07 should contain “LT” to indicate that only a Letter of Transmittal (also referred to as a Shipper Document) is required. No DD Form 250 is required. Data may still be rejected for non-compliance by the Procuring Contracting Officer (PCO) or PCO designee.

In the cases where a DD Form 250 is required, Block 07 should contain “DD”. Inspection and acceptance are both at destination. The first addressee in Block 14 is assumed unless otherwise specified. See Block 16 for distribution limitations or clarifications.

Block 08 - Approval Code – This field contains an “A” (SEE BLOCK 16) if approval is required by a Government Representative prior to final acceptance by the Government, or prior to publication and distribution of the final version of the document to Block 14 addressees. Clarification of approval will be defined in Block 16 as to its scope and depth. CDRLs requiring approval are those where:

Cost of correcting deficiencies in final deliverable is high and the cost of correcting deficiencies in drafts is relatively low. Generally, this includes Technical Manuals and other published documentation.

Approval of the data is required, per ship specifications or SOW, before the contractor can proceed with an action that may result in considerable cost increases to achieve contract requirements.

This field is left Blank if approval is not required.

Block 09 – Distribution Statement Required – A “D” indicates that a distribution statement is required and is to be cited in Block 16. (See Attachment (1) Block 16 for paragraph containing Block 09 distribution statement.) If Block 09 is left blank, no distribution statement is required.

Block 10 - Frequency - The appropriate frequency code of data requirements indicated in this block are from the codes in the table below. If data is of a recurring type, it is to be submitted at the end of the reporting period established in this block unless otherwise indicated in Blocks 12, 13, or 16.

CODEKEY
DAILYDaily submittals
WEKLYWeekly (Once A Week)
BI-WEEvery Two Weeks (bi-weekly)
MTHLYMonthly
BI-MOEvery Two Months (bi-monthly)
QRTLYQuarterly
ANNLYAnnually
SEMIAEvery 6 Months (semi-annually)
OTIMEOne Time (does not include draft submissions)
ONE/ROne Time with Revisions
ASREQAs Required. See Block 16 for explanation of conditions or triggering event
DACDRDays After Critical Design Review
ONE/POne-Time Preliminary Draft
ASGENAs Generated. See Block 16 for explanation of conditions or triggering event
CP/RQChange Pages as Required
R/ASRRevisions as Required
XTIMEMultiple separate submittals (2TIME, 3TIME, etc.) Does not include draft submissions.
SEERequirement is fully described in Block 16.
BLOCK 16Used in lieu of the above codes where they are inadequate to define
requirement(s), or used with the codes to provide clarification in Block 16.

Block 11 - As of Date - Date for cutting off collection of data. For single submittal of data, date will be entered as follows: year/month/day. For recurring type data, a numeral will indicate the number of days prior to the end of the report period, established in Block 10, that data collection will be cut off. Block 16 may be used for further explanation.

Block 12 - Date for First Submission - Due date for initial data submission. This is normally the postage date or date delivered to the ACO, entered as follows: year/month/day, or keyed to an event as shown in the table below:

CODEDEFINITION
XDACDays After Contract
XDACMDays After Contract Modification
XDARPDays After Reporting Period
XDARCDays After Receipt of Comments
XDATCDays After Test Completion
XDPTTDays Prior To Test
DFDELDeferred Delivery
EOCEnd of Contract
EOMEnd of Month
EOQEnd of Quarter
NLTNo Later Than
RFMRelease for Manufacture (Release given by Contractor for vendor to proceed with manufacturing
SEEUsed to indicate requirement is fully
BLOCK 16described in Block 16. Used in lieu of above codes where such are inadequate to define requirement, or used with codes to provide clarification in Block 16.

(NOTE: "X" is assigned a value indicating the number of days, e.g., 30 DAC.)

Block 13 - Date Subsequent Submission - Actual due dates by year/month/day or keyed to an event as shown in the table above.

Block 14 - Distribution - Code of addressees and the number of copies (hardcopy or electronic) each addressee is to receive. Hardcopies required will be to the left of the slash mark and electronic copies to the right. Format of hardcopy and electronic copy is explained in Block 16 if not described in the DID.

For data deliverables provided electronically and in hardcopy, Block 14 shall be as follows:

BLOCK 14

DISTRIBUTION:IDE0/1
AS SPECIFIED ON EACH CDRL1/0

The above distribution implies that the Contractor is only obligated to submit an electronic CDRL to the IDE and one (1) hardcopy of the CDRL to the distribution as specified for each CDRL. Any other Government user shall obtain a copy of the data deliverable from the IDE.

Block 15 – Distribution Total - Summation of the requirements listed in Block 14. For example, the number of hardcopies required will be to the left of each slash mark and number of electronic to the right.

BLOCK 14

DISTRIBUTION:IDE0/1
SUPSHIP1/0
PMS3771/0

BLOCK 15

DIST TOTAL: 2/1

The above Block 14 distribution instructs the Contractor to provide Block 15 total distribution of an electronic Letter of Transmittal to the IDE only and 2 hardcopies of the deliverable: One to SUPSHIP and one to PMS377.

Block 16 - Remarks - Contains all pertinent data information not specified elsewhere in the CDRL and any amplification of other blocks on this form (e.g., DID tailoring, use of contractor format, approval criteria and authority, inspection and acceptance clarifications, submission clarification, distribution statements, etc…)

LCU 1700 ADDRESS LIST

CONTRACT NUMBER: N00024-16-R-2449

DD FORM 1423 (CDRL)

BLOCK 14 ENTRYCOMPLETE ADDRESS
PMS377 (IDE)www.ideservicecenter.com

Attachment J-2a

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