Attachment_J-2a_-_CDRL_Information.docx
DOCX document 37 KB Posted
- Solicitation number
- N0002418R2400
View the file
Other files
Show all 40
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
N00024-18-R-2400
LCAC SLEP
N00024-18-R-2400
ATTACHMENT J-2a
CONTRACT DATA REQUIREMENTS LIST (CDRL)
DD FORM 1423
CDRL INFORMATION
27 March 2018
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; (Administrative or Operational Use)(27 March 2018). Other requests for this document 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.
| CDRL | Contract Data Requirements List |
| CLIN | Contract Line Item Number |
| GFI | Government Furnished Information |
| IAW | In Accordance With |
| IDE | Integrated Digital Environment |
| LT | Letter of Transmittal |
| NLT | Not Later Than |
| OTIME | One Time |
| R/ASR | Revisions 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:
A. BACKGROUND: The CDRLs for the Contract are organized in two exhibits:
· Exhibit A: Pertains to Programmatic Plans, Status Reports, Procurement/Production Schedules, Configuration Management, Financial Analysis and Reports, and Craft Test technical documentation.
· Exhibit B: Pertains to Integrated Logistics Support, Technical Manuals, and Outfitting documentation.
B. DETAILED CDRL (DD FORM 1423) INFORMATION:
GENERAL DEFINITION: Days = Calendar Days unless otherwise specified.
Block A - Contract Line Item No. - The Contract Line Item Number (CLIN) that is associated with this Contract Data Requirements List (CDRL).
Block B - Exhibit - The exhibit identifier for this CDRL, e.g., “A”, “B”, “C” (See DFARS 204.7105-3 for exhibit identifiers).
Block C - Category - An “X” categorizes the data required in the exhibit, i.e., either Technical Data Package (TDP), Technical Manual, or “Other” data (Other).
Block D - System/Item -The system, item, project designator or name, or title of services being acquired that the data will support.
Block E - Contract/Pr No. - The Procurement Instrument Identification Number (PIIN) (i.e. the contract number, the Purchase Request (PR) number, the Request for Proposal (RFP) number or other appropriate designator).
Block F - Contractor - The contractor’s name, if known.
Block 01 – Data Item No. – 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 Data Item Description (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 No.) – Block 04 contains the DID (DD Form 1664) number. DID identification number is the prefix code for a standard DID.
Block 05 - Contract Reference - Indicates the specific paragraph number of Section C that contains the tasking that generates a requirement for the data.
Block 06 - Requiring Office - The office responsible for advising the contracting officer on the technical adequacy of the data.
Block 07 - DD 250 Req. – 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 - App 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.
This field is “N/A” if approval is not required.
Block 09 - Dist Stmt Rqd – A “D” corresponding to the distribution statement to be marked on the data item by the contractor is entered here. The distribution statement is cited in Block 16.
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.
| CODE | KEY | |||
| DAILY | Daily submittals | |||
| WEKLY | Weekly (Once A Week) | |||
| BI-WE | Every Two Weeks (bi-weekly) | |||
| MTHLY | Monthly | |||
| BI-MO | Every Two Months (bi-monthly) | |||
| QRTLY | Quarterly | |||
| ANNLY | Annually | |||
| SEMIA | Every 6 Months (semi-annually) | |||
| OTIME | One Time (does not include draft submissions) | |||
| ONE/R | One Time with Revisions | |||
| ASREQ | As Required. See Block 16 for explanation of conditions or triggering event | |||
| DACDR | Days After Critical Design Review | |||
| ONE/P | One-Time Preliminary Draft | |||
| ASGEN | As Generated. See Block 16 for explanation of conditions or triggering event | |||
| CP/RQ | Change Pages as Required | |||
| R/ASR | Revisions as Required | |||
| XTIME | Multiple separate submittals (2TIME, 3TIME, etc.) Does not include draft submissions. | |||
| SEE | Requirement is fully described in Block 16. | |||
| BLOCK 16 | Used 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 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.
This field is “N/A” if an “As of Date” is not required.
Block 12 - Date for First Submission - Due date for initial data submission.
| CODE | DEFINITION | |
| XDAC | Days After Contract | |
| XDACM | Days After Contract Modification | |
| XDARP | Days After Reporting Period | |
| XDARC | Days After Receipt of Comments | |
| XDATC | Days After Test Completion | |
| XDPTT | Days Prior To Test | |
| DFDEL | Deferred Delivery | |
| EOC | End of Contract | |
| EOM | End of Month | |
| EOQ | End of Quarter | |
| NLT | No Later Than | |
| RFM | Release for Manufacture (Release given by Contractor for vendor to proceed with manufacturing | |
| SEE BLOCK 16 | Used to indicate requirement is fully described 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 - The due date(s) for subsequent data submission(s), if data is to be submitted more than once. (See table above.)
Block 14 - Distribution - Code of addressees and the number of copies (hardcopy or electronic) each addressee is to receive.
Block 15 – Distribution Total - Summation of the requirements listed in Block 14.
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…)
FY17/19 LCAC SLEP ADDRESSEE LIST
CONTRACT NUMBER: N00024-18-R-2400
| BLOCK 14 ENTRY | COMPLETE ADDRESS | |
| PMS377 IDE | www.ideservicecenter.com |
ACU 4 Commanding Officer Assault Craft Unit Four (ACU 4) Joint Expeditionary Base Little Creek-Fort Story Virginia Beach, VA 23521-5004 Notify LT. Jeffery Carter at jeffery.carter@navy.mil and Mr. Mike Ott at mike.ott@c-gcon.com
SUPERVISOR/MARMC Commander Mid-Atlantic Regional Maintenance Center (MARMC) Attn: Mr. James Davitt Code 330 9170 2nd Street, Suite 120 Norfolk, VA 23511-2393 Notify Mr. James Davitt at james.davitt@navy.mil
PCO Contracting Officer Naval Sea Systems Command Attn: Linda C. Squires, SEA 02242 1333 Isaac Hull Avenue SE, STOP 2020 Washington Navy Yard DC 20376-2020 Notify Ms. Linda C. Squires at linda.squires@navy.mil
NSWCPD NSWCPD Code 423 Naval Surface Warfare Center, Philadelphia Division 1000 Kitty Hawk Ave Building 77L Code 423 (D. DiMatteo) Philadelphia, PA 19112-1408 Notify Mr. Dennis DiMatteo, Code 423, at dennis.dimatteo@navy.mil
ATTACHMENT J-2a
File details come from the government source that posted it.