FRC_COR_Section000_Phase_II_A00004.pdf

USCG Fast Response Cutter (FRC) Solicitation HSCG23-15-R-FRCPII

Part III – List of Documents, Exhibits, and Other Attachments Section J, Attachment 2: Circular Of Requirements (COR)

Section 000 – General Guidance and Administration

PART III, SECTION J, ATTACHMENT 2 000 - 1 Circular of Requirements

TABLE OF CONTENTS

SECTION 041. [RFP] CONFIGURATION MANAGEMENT

041-1 [RFP] General 041-2 [RFP] Definitions, Abbreviations and Acronyms 041-3 [RFP] Configuration Baselines 041-4 [RFP] Configuration Control 041-5 [RFP] Information Management

SECTION 042. [RFP] GENERAL ADMINISTRATIVE REQUIREMENTS

042-1 [RFP] General 042-2 [RFP] Terms and Definitions 042-3 [RFP] Referenced Documents 042-4 [RFP] Effective Issue 042-5 [RFP] Order of Precedence 042-6 [RFP] Contract Data Requirements 042-7 [RFP] Correspondence 042-8 [RFP] Schedules 042-9 [RFP] Meetings 042-10 [RFP] Integrated Product Data Environment (IPDE) 042-11 [RFP] Contract Work Breakdown Structure (CWBS) 042-12 [RFP] Integrated Master Plan (IMP) 042-13 [RFP] Integrated Master Schedule (IMS) 042-14 [RFP] Copies of Purchase Orders

SECTION 043. [RFP] LIFE CYCLE COSTING INPUT

043-1 [RFP] Life Cycle Cost Estimate Input

SECTION 045. [RFP] CARE OF CUTTER DURING CONSTRUCTION

045-1 [RFP] General 045-2 [RFP] Performance Requirements 045-3 [RFP] Protection of Machinery, Equipment and Materials 045-4 [RFP] Launching, Docking and Undocking 045-5 [RFP] Damage Control – General 045-6 [RFP] Monitoring, Alarms and Controls

SECTION 068. [RFP] INTEGRATION AND ENGINEERING

068-1 [RFP] System Integration and Engineering 068-2 [RFP] Design Reviews

SECTION 070. [RFP] GENERAL REQUIREMENTS FOR DESIGN AND CONSTRUCTION

070-1 [RFP] Laws, Classifications Rules, Regulations, Standards and Certification

070-2 [RFP] Characteristics 070-3 [RFP] Command and Control 070-4 [RFP] Design Conditions 070-5 [RFP] Design Loads 070-6 [RFP] Templates and Patterns 070-7 [RFP] Workmanship 070-8 [RFP] Habitability 070-9 [RFP] SI (Metric) Measurement Units

SECTION 071. [RFP] ACCESS

071-1 [RFP] General

PART III, SECTION J, ATTACHMENT 2 000 - 2 Circular of Requirements

071-2 [RFP] Headroom 071-3 [RFP] Watertight Integrity and Structural Limitations 071-4 [RFP] Pilothouse 071-5 [RFP] Machinery Compartments 071-6 [RFP] Forepeak 071-7 [RFP] Lazarette 071-8 [RFP] Access to Equipment and Machinery

SECTION 073. [RFP] NOISE AND VIBRATION

073-1 [RFP] Definitions 073-2 [RFP] Noise Level Limiting Criteria 073-3 [RFP] Far Field Noise 073-4 [RFP] Mechanical Vibration 073-5 [RFP] Mountings, Resilient Type 073-6 [RFP] Resilient Mount Data 073-7 [RFP] Rotating Machinery Balance

SECTION 074. [RFP] WELDING AND FABRICATION

074-1 [RFP] General 074-2 [RFP] Performance Requirements 074-3 [RFP] Qualification Requirements 074-4 [RFP] Welding Quality Control 074-5 [RFP] Inspection Requirements 074-6 [RFP] Welding Filler Materials 074-7 [RFP] Hull Structure Welding Design 074-8 [RFP] Structural Castings

SECTION 075. [RFP] THREADED FASTENERS

075-1 [RFP] Performance Requirements

SECTION 076. [RFP] RELIABILITY, MAINTAINABILITY AND AVAILABILITY

076-1 [RFP] General 076-2 [RFP] Definitions 076-3 [RFP] Design Reliability, Maintainability and Availability (RMA) Requirements and Analysis

SECTION 077. [RFP] SYSTEM SAFETY PROGRAM

077-1 [RFP] General 077-2 [RFP] Material Safety Data Sheets (MSDS)

SECTION 078. [RFP] MATERIALS

078-1 [RFP] General 078-2 [RFP] Materials 078-3 [RFP] Miscellaneous Requirements 078-4 [RFP] Electrolytically Dissimilar Metals and Corrosion Protection 078-5 [RFP] Toxic Products and Safety 078-6 [RFP] Mercury Exclusion

SECTION 079. [RFP] STABILITY AND SEAKEEPING

079-1 [RFP] General 079-2 [RFP] Stability Analysis 079-3 [RFP] Intact and Damage Stability 079-4 [RFP] Trim and List Limits 079-5 [RFP] Stability and Loading Data Booklet

PART III, SECTION J, ATTACHMENT 2 000 - 3 Circular of Requirements

SECTION 080. [RFP] INTEGRATED LOGISTICS SUPPORT

080-1 [RFP] Integrated Logistic Support (ILS) Program

SECTION 081. [RFP] MAINTENANCE

081-1 [RFP] General 081-2 [RFP] Terms and Definitions 081-3 [RFP] Coast Guard Maintenance Philosophy for the FRC 081-4 [RFP] Master Equipment List (MEL) 081-5 [RFP] Maintenance Development

SECTION 083. [RFP] SUPPLY SUPPORT

083-1 [RFP] General 083-2 [RFP] Performance Requirements 083-3 [RFP] Definitions, Abbreviations and Acronyms 083-4 [RFP] Provisioning 083-5 [RFP] Outfitting Material Procurement 083-6 [RFP] Outfitting 083-7 [RFP] Modular, High Density Equipment Storage Cabinets

SECTION 084. [RFP] PACKAGING, HANDLING, STORAGE, AND TRANSPORTATION 89

084-1 [RFP] Delivery of the FRC 084-2 [RFP] Preparing the FRC for transport to the delivery location 084-3 [RFP] Shipments 084-4 [RFP] Packing and Preservation Data 084-5 [RFP] Hazardous Materials 084-6 [RFP] Containerization

SECTION 085. [RFP] DRAWINGS

085-1 [RFP] Performance Requirements 085-2 [RFP] Definitions 085-3 [RFP] Drawing Submission 085-4 [RFP] General Drawing Requirements 085-5 [RFP] Required Ship Construction Drawings 085-6 [RFP] Supplemental Requirements for Drawings 085-7 [RFP] Final Drawings 085-8 [RFP] Selected Record Drawings 085-9 [RFP] Calculations 085-10 [RFP] Lists 085-11 [RFP] 3-Dimensional Technical Data Package (3D TDP) 085-12 [RFP] 2-Dimensional (2D) Product Drawings and Associated Lists

SECTION 086. [RFP] TECHNICAL MANUALS

086-1 [RFP] Performance Requirements 086-2 [RFP] XML Data Modules 086-3 [RFP] Content 086-4 [RFP] Technical Manuals and Data 086-5 [RFP] Illustrated Parts Breakdown 086-6 [RFP] Technical Data Validation 086-7 [RFP] Delivery

SECTION 087. [RFP] FACILITIES

087-1 [RFP] Project Resident Office (PRO) 087-2 [RFP] Temporary PRO Facilities 087-3 [RFP] PRO Facilities 087-4 [RFP] Primary Crew Assembly Facility (PCAF)

PART III, SECTION J, ATTACHMENT 2 000 - 4 Circular of Requirements

SECTION 088. [RFP] HUMAN FACTORS ENGINEERING

088-1 [RFP] Performance Requirements 088-2 [RFP] Communications 088-3 [RFP] Accessibility 088-4 [RFP] Maintainability 088-5 [RFP] Controls, Displays and Alarms 088-6 [RFP] Error-Tolerant Design 088-7 [RFP] Workstation Design 088-8 [RFP] Labeling

SECTION 089. [RFP] PERSONNEL AND TRAINING

089-1 [RFP] General 089-2 [RFP] Definitions 089-3 [RFP] Training Requirements 089-4 [RFP] Factory Training 089-5 [RFP] Familiarization Training 089-6 [RFP] Additional Training Requirements

SECTION 090. [RFP] QUALITY ASSURANCE

090-1 [RFP] General

SECTION 092. [RFP] TEST ADMINISTRATION

092-1 [RFP] General 092-2 [RFP] Performance Requirements 092-3 [RFP] Test and Evaluation Program Plan 092-4 [RFP] Test Reports - General 092-5 [RFP] In-Plant Tests (IPT) 092-6 [RFP] Shipboard Tests

SECTION 094. [RFP] TRIALS

094-1 [RFP] Builder's At-Sea Trials (BT) 094-2 [RFP] Preliminary Acceptance Trials (PAT) 094-3 [RFP] Final Acceptance Trials (FAT)

SECTION 095. [RFP] SHIPBOARD TESTS

095-1 [RFP] General 095-2 [RFP] Watertight/Weathertight Tests 095-3 [RFP] Fuel System Test 095-4 [RFP] Control System Test 095-5 [RFP] Fixed Fire Extinguishing System Installation Testing 095-6 [RFP] Helm Control 095-7 [RFP] Bells, Whistles, Navigation Lights 095-8 [RFP] Tanks and Voids Testing 095-9 [RFP] Windshield Washer/Wiper Testing 095-10 [RFP] Electrical/Electronic Test 095-11 [RFP] Fire and Smoke Detection System Tests

SECTION 096. [RFP] WEIGHTS

096-1 [RFP] Definitions 096-2 [RFP] Weight Control Program Requirements 096-3 [RFP] Determination of Weights - Submission of Calculations 096-4 [RFP] Weight Reports 096-5 [RFP] Weight Report Requirements

PART III, SECTION J, ATTACHMENT 2 000 - 5 Circular of Requirements

SECTION 097. [RFP] INCLINING EXPERIMENT

097-1 [RFP] Performance Requirements

SECTION 098. [RFP] MODELS AND MOCKUPS

098-1 [RFP] Display Model 098-2 [RFP] Mock-ups

PART III, SECTION J, ATTACHMENT 2 000 - 6 Circular of Requirements

SECTION 041. [RFP] CONFIGURATION MANAGEMENT

041-1 [RFP] General

041-1.1 [RFP] Configuration Management is an integral part of the system engineering process. The US Coast Guard uses a configuration-based, maintenance driven, centralized supply approach to obtain life-cycle supportability. This ensures all Integrated Logistics Support (ILS) elements (described in COR Section 080) are considered throughout the life-cycle of the FRC.

041-1.2 [RFP] Configuration Management (CM) Program. A CM program shall be established and maintained throughout the performance period for the FRC contract that implements the guidance contained in MIL-HDBK-61A and

ANSI/EIA-649-A.

041-1.3 [RFP] CM Plan. The contractor shall develop, provide, and follow a Configuration Management Plan (CMP) for establishing and maintaining the FRC baseline configurations (CDRL 041-001) in accordance with MIL-HDBK-61A.

The CMP shall describe the contractor’s CM organization and shall identify contractor responsibilities in configuration planning, management, identification, control, status accounting, and verification and audit, to establish and maintain the functional, allocated, development, and product configuration baselines. The CMP shall describe how the contractor will ensure subcontractor / vendor compliance with the CM requirements of the contract.

041-1.4 [RFP] Configuration Status Accounting. As part of the CM Program, Configuration Status Accounting (CSA) shall be conducted by the Contractor to capture configuration data for each FRC by hull. The Contractor shall maintain CSA until the end of each FRC’s warranty period. A class baseline shall be maintained by the Contractor throughout the performance period of the contract until the last FRC is out of warranty. CSA tasks shall be recorded in accordance with Table 7-3 of MIL-HDBK-61A.

041-1.4.1 [RFP] The Contractor shall maintain a CSA system for all end items and support items and report in accordance with CDRL 041-002. During provisioning (COR Section 083) and maintenance development (COR Section 081), Configuration Items (CIs) will be defined by the government through the assignment of an Allowance Parts List (APL). For all CI’s the government will provide, as GFI, a unique APL for each CI to be incorporated into the contractor’s CSA system.

041-1.4.2 [RFP] The CSA system shall be consistent with the Master Equipment List (MEL) (COR Section 081-4) and associated provisioning parts lists, established, and populated prior to the Critical Design Review (CDR), maintained during ship construction, continue through the production contract, and shall provide all necessary information for a complete, accurate and verified "as delivered" approved product configuration baseline for each

FRC.

041-1.4.3 [RFP] The CSA system shall maintain change status for all Configuration Items and reflect the current system/equipment configuration with Engineering Change Notice (ECN) and Engineering Change Proposal (ECP) approval and implementation status.

PART III, SECTION J, ATTACHMENT 2 000 - 7 Circular of Requirements

041-1.4.4 [RFP] The CSA report shall reflect the accurate name plate data. All configuration managed equipment shall have visible name plate data located in an accessible position on all installed equipment. The name plate data shall be easily read without the aid of any objects to enhance its visibility or clarity. Name plate data shall clearly state the type of equipment installed (noun name or nomenclature of equipment), make, model and/or serial number, manufacturer’s name, date of manufacture, place of manufacture and National Stock Number (NSN) if available in accordance with MIL-HDBK- 61A.

041-2 [RFP] Definitions, Abbreviations and Acronyms 041-2.1 [RFP] The definitions below and those cited in DI-SESS-81884 shall be used to meet the requirements of the Circular of Requirements (COR).

041-2.2 [RFP] Expanded Ship Work Breakdown Structure (ESWBS): An expansion of the SWBS to a five digit functional indenturing system that provides uniform, top-down breakdown by single digit indentured levels. The ESWBS defines and establishes the system boundaries, system descriptions, and functional nomenclature for all systems for each FRC.

041-2.3 [RFP] Selected Record Drawing: Selected Record Drawings are the Coast Guard approved drawings that are to be used as the ship construction drawings for follow-on FRCs constructed under contract options. No departure from a Selected Record Drawing is permissible without specific written approval by the Contracting Officer.

041-3 [RFP] Configuration Baselines 041-3.1 [RFP] The Functional Configuration Baseline (FCB) consists of the FRC’s technical, mission, operational (including availability) and functional requirements, interoperability and interface characteristics, and design constraints as contained in the FRC contract. The FCB will be established at contract award.

041-3.2 [RFP] The Allocated Configuration Baseline (ACB) formally breaks out the functional requirements identified in the FCB into more detailed functional requirements and interface characteristics that are allocated from those of the higher level Configuration Item (CI) for the System and major subsystems. The ACB shall represent the performance-oriented requirements from the FCB, how the contractor allocates their design characteristics to these performance-oriented requirements, and the verification required to demonstrate achievement of those specified characteristics.

041-3.3 [RFP] The Development Configuration Baseline (DCB) represents the approved “build to” technical data package for the initial FRCs. The technical data package includes all the information that defines the configuration of the FRC. The DCB will be established, in phases, as a result of a design review of the technical data package by CG personnel. When the Contracting Officer has approved a deliverable, its contents become part of the DCB. The DCB is established when all deliverables associated with the design review, COR Section 068-2, have been approved.

041-3.4 [RFP] The Product Configuration Baseline (PCB) represents the approved validation of the DCB. It will be established upon approval of a Physical Configuration Audit (PCA) on the FRC designated by the Contracting Officer.

PART III, SECTION J, ATTACHMENT 2 000 - 8 Circular of Requirements

041-3.5 [RFP] Physical Configuration Audit (PCA). The Government will conduct a

Physical Configuration Audit prior to acceptance on two FRCs designated by the Contracting Officer. The contractor shall make provisions for and support this effort, which is expected to last two calendar weeks. The contractor shall assist the government in preparing for and conducting these PCAs, which will entail comprehensive comparisons of technical data produced under this contract with physical hull, installed systems/equipment, and system software configurations.

The contractor shall provide at a minimum access to the cutter, drawings and other technical data and provide FRC subject matter expert personnel. The contractor shall record the minutes of the audit and report the results in accordance with CDRL 041-003. Discrepancies, if any, must be resolved to the satisfaction of the Contracting Officer and the audit repeated for all affected items.

041-4 [RFP] Configuration Control 041-4.1 [RFP] General. It is imperative that configuration of the FRC System be controlled and maintained throughout the performance period and that the configuration baseline(s) be current, complete, and correct. The Contractor shall not change an established configuration baseline without an approved Engineering Change Proposal, or an approved Request For Deviation, issued by the Contracting Officer in the form of a contract change.

041-4.2 [RFP] Engineering Change Proposal (ECP). The contractor shall propose changes to the configuration baseline, in response to a request from the Contracting Officer or on the Contractor's own initiative, by submitting an Engineering Change Proposal (ECP) in accordance with clause H.4 and CDRL 041-004. ECPs are categorized into two classes defined in MIL-HDBK-61A. The Contractor shall implement the Engineering Change only with the authorization of the Contracting Officer.

041-4.3 [RFP] Request For Deviation (RFD). Deviations may be requested from a particular requirement of an item’s configuration baseline documentation, for a specific hull or number of hulls, or for a specific period of time, by submitting a Request For Deviation (RFD) (CDRL 041-005). An RFD shall identify the affected item(s), provide a detailed description of the difference between the configuration of the item and the configuration baseline document, provide justification for the deviation, provide a discussion of the consequences of approval, to include technical details explaining the degree of non-compliance and the effects on cutter equipment or system operation constraints, and describe how the deviation will be documented in the hull(s) configuration documentation. The RFD shall only be implemented with the authorization of the Contracting Officer.

041-5 [RFP] Information Management 041-5.1 [RFP] The contractor shall develop, implement and maintain a Technical

Information Management and Control Plan (TIMCP) CDRL 041-006 that establishes the policy, procedures and processes that will be used to develop, integrate, check, distribute, update, manage the configuration of, and deliver the technical information necessary to design, construct and deliver the FRC and all other contract products and deliverables. The TIMCP shall address the planning and processes to ensure data is made available on the Integrated Product Data Environment (IPDE) required in COR Section 042-10.

PART III, SECTION J, ATTACHMENT 2 000 - 9 Circular of Requirements

041-5.2 [RFP] The Contractor shall ensure security of all data and information associated with this contract. At a minimum, the following procedures shall be used:

041-5.2.1 [RFP] A copy of all electronic files and documents shall be stored in a fire-proof, water resistant cabinet off-site from the Contractor’s facility to ensure that in the event of a fire, flood, hurricane, tornado or other natural or man made disaster, a backup copy of this information is available to the Contractor and the Government.

041-5.2.2 [RFP] All electronic information shall be archived on an incremental weekly basis. At no time will anymore than one working day of information be lost.

041-5.2.3 [RFP] Sufficient redundancy shall be built into all computer systems to minimize data loss in the event of failure or loss.

041-5.2.4 [RFP] In the event of failure, loss, or other disaster, the contractor shall provide full data restoration, either on site or to the government, within one working day.

PART III, SECTION J, ATTACHMENT 2 000 - 10 Circular of Requirements

SECTION 042. [RFP] GENERAL ADMINISTRATIVE REQUIREMENTS

042-1 [RFP] General

042-1.1 [RFP] The necessary building facilities, labor, materials, and management shall be provided to design, build, inspect, test, launch, outfit and ready the FRC for service. The upkeep, the tests, and the trials for the FRCs built under this contract shall be provided until the vessels are delivered to the Coast Guard.

042-2 [RFP] Terms and Definitions 042-2.1 [RFP] See Section J, Attachment 1 for a list of applicable Terms and Definitions.

042-3 [RFP] Referenced Documents 042-3.1 [RFP] Documents which are referred in this Circular of Requirements are termed

"referenced documents".

042-3.1.1 [RFP] Contract Drawing – A drawing identified as a "Contract Drawing" which delineates design features of the ship. The current revision in effect for each Contract Drawing will be defined in the contract.. No departure from a Contract Drawing is permitted without specific written authorization from the Contracting Officer.

042-3.1.2 [RFP] Standard Drawing – A NAVSEA or USCG drawing identified as a "Standard Drawing" or "Fleet Drawing" which delineates arrangements or details of systems, equipment or components. No departure from a standard drawing is permitted without specific written authorization from the Contracting Officer.

042-3.1.3 [RFP] Project Peculiar Document – A document or drawing included in the list of Project Peculiar documents. These documents represent the configuration of the Phase I FRC and are provided for guidance only.

042-3.1.4 [RFP] First Tier and Sub-tier References - Any referenced document which is directly cited for use or application by an identifying number or name in the Circular of Requirements is a first tier reference for each particular use or application for which it is so cited. Any document which is cited in a first tier reference, or in a document referenced therein, is a sub-tier reference. A document which is a sub-tier reference in one application may be a first tier reference in another application when it is cited directly.

042-3.1.5 [RFP] Government Specifications are specifications such as Federal (Fed.

Spec), Military (Mil. Spec.) and DOD Standards that describe the essential technical requirements for items, materials or services required and used primarily for acquisition.

042-3.1.6 [RFP] Government Standards are Government documents that establish engineering and technical limitations and applications of items, materials, processes, methods, design, and engineering practices.

042-3.1.7 [RFP] U.S. Navy Design Data Sheets (DDS) contain information for guidance in the design and construction of ship features or systems. Design Data Sheets illustrate typical design and calculation methods and procedures which are acceptable to the Coast Guard.

042-3.1.8 [RFP] Industry Standards are documents issued by recognized non-government organizations such as ABS, Institute of Electrical and

PART III, SECTION J, ATTACHMENT 2 000 - 11 Circular of Requirements

Electronics Engineers (IEEE), American National Standards Institute (ANSI) and American Society for Testing and Materials (ASTM) that establish engineering and technical limitations and applications for items, materials, processes, methods, design and engineering practice.

042-4 [RFP] Effective Issue 042-4.1 [RFP] The issue of reference documents in effect on the dates shown in Section

J, Attachment 4, "External Reference List" shall be used.

042-5 [RFP] Order of Precedence 042-5.1 [RFP] The order of precedence of requirements of sections within this Circular of

Requirements is as specified below:

042-5.1.1 [RFP] Requirements within a section applicable to the entire FRC (for example, General Requirements for Design and Construction) state the broadest requirements and apply to all systems and equipment, unless otherwise specified in the more detailed sections, in which case the detailed section requirements apply.

042-5.1.2 [RFP] Specific requirements within a lead section (for example, a section which includes the general or common requirements for a number of similar systems, such as General Requirements for Piping Systems) are the next broadest category of requirements, and shall apply to all systems and equipment in its grouping, unless otherwise specified in detail system sections.

042-5.1.3 [RFP] Specific requirements within a detailed system section (for example, a section which includes the details of a particular FRC system such as Fresh Water Systems) are the most detailed requirements. Requirements in these detailed system sections apply for the system covered in the detailed section.

042-5.1.4 [RFP] The omission in one section of details covered in another section shall not be considered an inconsistency.

042-6 [RFP] Contract Data Requirements 042-6.1 [RFP] Background. Throughout this contract, the contractor is required to develop, prepare, and submit data as a contract deliverable in support of the FRC in accordance with the instructions in the contract, including the CDRLs, Data Item Descriptions (DIDs), associated support data, equipment, and supplies, for use by the United States Coast Guard.

042-6.2 [RFP] CDRL Index. Attachment 3 to Section J provides an index of the CDRLs included in this contract. From the on-line version of the contract, the CDRL Index provides links to each individual CDRL, as well as the associated DID(s), references, and attachments. The CDRL Index also provides links to each individual CDRL in a format suitable for printing, and a link to a file that contains all CDRLs in a format suitable for printing or viewing off-line.

042-6.3 [RFP] Attachments 9 and 10 to Section J of this contract, respectively, list all contract drawings and project peculiar documents provided by the government for the contractor's reference in Phase II. In the event that no changes have been made to affect the Phase I design/analyses, a Phase I CDRL deliverable may be submitted under the Phase II contract. The Contractor shall certify that each Phase I CDRL deliverable being submitted under the Phase II contract is still valid and that no changes have been made that affect the deliverable’s

PART III, SECTION J, ATTACHMENT 2 000 - 12 Circular of Requirements validity to satisfy the Phase II CDRL requirements. This certification shall appear on the CDRL cover as described in COR Section 042-6.5.1.5.

042-6.4 [RFP] CDRL Description. Not all elements of the general DD Form 1423 are used in this contract. For the sake of consistency with the DD Form 1423, however, elements used in this contract retain the same block number as found in the DD Form 1423, though in some cases the name of the block has changed to improve readability for those not familiar with the DD Form 1423. For this contract, CDRLs are composed of the following elements:

042-6.4.1 [RFP] Block 1 (BLK01) of the CDRL identifies the CDRL number, made up of a three-digit SWBS code most closely reflecting the subject of the requirement, followed by a three-digit sequence number.

042-6.4.2 [RFP] Block 2 is not used.

042-6.4.3 [RFP] Block 3 (BLK03) of the CDRL identifies title of the CDRL, as it is referred to in this contract.

042-6.4.4 [RFP] Block 4 (BLK04) of the CDRL identifies the DID(s) associated with the CDRL. The DID, as tailored by Block 16 or elsewhere in the contract, provides the content and format for the data deliverables. More than one DID may apply to a single CDRL, and a single DID may be applied in more than one CDRL, though often will be tailored differently for each application.

042-6.4.5 [RFP] Block 5 (BLK05) of the CDRL identifies the relevant contract section(s) that invoke the CDRL.

042-6.4.6 [RFP] Block 6 is not used.

042-6.4.7 [RFP] Block 7 (BLK07) of the CDRL identifies the location for performance of Government inspection and acceptance, using the following codes:

Table 42-1 – CDRL Block 7 Code Description

[RFP]

CODE INSPECTION ACCEPTANCE

SS Source (DD Form 250)* Source (DD Form 250)*

DD Destination (DD Form 250) Destination (DD Form 250)

SD Source (DD Form 250)* Destination (DD Form 250)

DS Destination (DD Form 250) Source (DD Form 250)*

LT Letter of Transmittal only **

NO No inspection or acceptance required

XX Inspection and acceptance requirements specified else-where in contract

* Source indicates Government inspection performed at the contractor’s facility.

** For electronic transmittal, an e-mail constitutes transmission.

042-6.4.8 [RFP] Block 8 (BLK08) of the CDRL identifies whether or not the deliverable requires Contracting Officer’s approval before the submission is considered final.

042-6.4.8.1 [RFP] An "A" indicates that written approval from the Contracting Officer, or his or her designated representative, is required prior to publication and distribution of the final deliverable. The use of “N/A” or a null entry in Block 8 does not forfeit or otherwise affect the Government’s right to

PART III, SECTION J, ATTACHMENT 2 000 - 13 Circular of Requirements consider unacceptable any submission of data that does not comply with the contract requirements.

042-6.4.8.2 [RFP] The contractor shall maintain internal quality control to ensure submittals are complete and adequate and shall not rely on Government review comments to ensure the technical accuracy of data.

042-6.4.8.3 [RFP] On all submissions prior to receiving Government approval, the contractor shall clearly indicate that the submission is draft or preliminary and has not been approved.

042-6.4.8.4 [RFP] The time period for Government review, identified in the data requirements list, commences at Government acknowledgment of receipt of the data by the PRO or other designated Government agency responsible for providing approval.

042-6.4.8.5 [RFP] The Government response to a draft or preliminary submission that requires approval will generally fall into one of three categories:

approved, approved with comments, or returned with comments.

042-6.4.8.5.1 [RFP] Approved without comment. The submittal is approved and requires no further changes to the data content. The contractor shall prepare the final deliverable in accordance with this COR Section.

042-6.4.8.5.2 [RFP] Approved with comments. The submittal is approved subject to resolution of issues raised by review comments. If all issues can be successfully resolved without further Government interaction, the contractor may make the appropriate changes and distribute the final deliverable. In the event the contractor disagrees with the intent of the review comments, or does not understand or is unable to comply with or resolve issues raised, the contractor shall follow the requirements of this COR Section.

042-6.4.8.5.3 [RFP] Returned with comments. The submittal is not approved. The contractor must make the necessary changes to address the comments and resubmit. In the event the contractor does not understand or is unable to comply with or resolve issues raised, the contractor shall resubmit the deliverable with correspondence explaining the reasons the issues cannot be resolved, and any propose suitable alternatives, with supporting rationale.

042-6.4.8.5.4 [RFP] On approved final submissions, the contractor shall clearly indicate that the submission is final and note the date of Government approval. Approved final submissions are required to be submitted within the timeframe specified in Block 13, and shall be distributed in accordance with Block 14.

042-6.4.9 [RFP] Block 9 (BLK09) of the CDRL identifies the distribution statement required for the deliverable, according to the codes in the table below. The cover page of the preliminary or draft submittals shall be marked with the full distribution statement F, unless otherwise noted in Block 16. For deliverables where no specific distribution statement is required, mark the transmittal letter with distribution statement F.

Code Statement

A Approved for public release; distribution is unlimited.

PART III, SECTION J, ATTACHMENT 2 000 - 14 Circular of Requirements

Code Statement

B Distribution authorized to U.S. Government Agencies only. Other requests for this document shall be referred to Commandant (CG-9324).

C Distribution authorized to U.S. Government Agencies and their contractors. Other requests for this document shall be referred to Commandant (CG-9324).

D Distribution authorized to the Department of Homeland Security and U.S.

DHS contractors only. Other requests shall be referred to Commandant

(CG-9324).

E Distribution authorized to U.S. Coast Guard only. Other requests shall be referred to Commandant (CG-9324).

F Further dissemination only as directed by Commandant (CG-9324) or higher Coast Guard authority.

X Distribution authorized to U.S. Government Agencies and private individuals or enterprises eligible to obtain export-controlled technical data in accordance with current law and regulation. The controlling Coast Guard office is Commandant (CG-9324). All technical documents that are determined to contain export-controlled technical data shall be marked “WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et.

seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with current Coast Guard policy.” When it is technically infeasible to use the entire statement, an abbreviated marking may be used, and a copy of the full statement included in the transmittal letter.

042-6.4.10 [RFP] Block 10 (BLK10) of the CDRL identifies the frequency of the deliverable requirement, using the codes listed below. If the deliverable is of a recurring type, it shall be submitted for the data as of the end of the reporting period identified, unless otherwise indicated in Blocks 12, 13, or 16.

Deliverables are due, delivered to the ACO or accepted digitally as described in the IPDE, on or before the due date listed in block 12, 13, and or 16.

Code Frequency

ANNLY Annually

ASREQ As Required. See Block 16.

DAILY Daily

MTHLY Monthly

ONE/R Once, and any time revisions are made.

OTIME One Time

2TIME Two Times

WEEKLY Weekly

042-6.4.11 [RFP] Block 11 is not used.

042-6.4.12 [RFP] Block 12 of the CDRL identifies the required date of the first submission, in days relative to one of the milestones identified by the codes listed below. Draft or partial submissions, if required, will be identified in

PART III, SECTION J, ATTACHMENT 2 000 - 15 Circular of Requirements

Block 16. Government response time will generally be stated in Block 16. If Government response time is not stated in Block 16, assume 30 days.

Code Milestone

CDD Cutter Delivery Date

DAC Days After Contract Award

DAOE Days After Option Exercised

DARC Days After Receipt of Comments

LCDD Lead Cutter Delivery Date

DPPDR Days Prior to Preliminary Design Review

DPCDR Days Prior to Critical Design Review

MPTD Months Prior to Delivery

DARP Days After Reporting Period

DAPAT Days After Preliminary Acceptance Trials

DATC Days After Test Complete

DPPAT Days Prior to Preliminary Acceptance Trials

BT Builder’s Trials

042-6.4.13 [RFP] Block 13 (BLK13) of the CDRL identifies the required date of subsequent submissions, relative to the milestones identified by the codes listed above. Block 13 is not used for deliverables that do not require approval in Block 8. Draft or partial submissions, if required, will be identified in Block 16. Government response time will generally be stated in Block 16.

If Government response time is not stated in Block 16, assume 30 days.

042-6.4.14 [RFP] Block 14 (BLK14) of the CDRL identifies the distribution of the deliverable.

042-6.4.14.1 [RFP] Electronic distribution. One electronic copy of each submission is always required. Electronic copies shall be source files delivered via the IPDE, described in this COR Section, with e-mail notification to the PRO upon posting. The source files shall be submitted in formats compatible with the Coast Guard Standard Workstation, or as agreed to by the Government. Note that the Portable Document Format (.pdf) file format is generally unacceptable except for cover letters bearing a signature.

Current CG workstation operating systems and software include:

042-6.4.14.1.1 [RFP] Microsoft® Windows 7 Enterprise

042-6.4.14.1.2 [RFP] Microsoft® Office Professional Plus 2007 Microsoft ® Office 2003 applications

042-6.4.14.1.3 [RFP] InfoPath 2010

042-6.4.14.1.4 [RFP] Tumbleweed Desktop Validator

042-6.4.14.1.5 [RFP] AutoCAD® version 2012

042-6.4.14.2 [RFP] Hard Copy distribution. Hard copies of the final deliverable, and preliminary and/or draft submissions as identified in Block 16, shall be distributed in the quantities identified. Hard copy means paper, PART III, SECTION J, ATTACHMENT 2 000 - 16 Circular of Requirements photograph, videocassette, CD-ROM, or DVD, or the like, as appropriate for the deliverable or as otherwise identified in the contract. Hard copies shall be sent by traceable means to the appropriate address, identified by the following codes:

CODE ADDRESS

PRO Address to be determined after contract award.

Cutter Provide a copy with the FRC at delivery.

CG-9324 Mailing address for CG-9324:

For US Mail delivery:

Commandant (CG-9324) ATTN: Major Systems Acquisition Program Manager (Patrol Boats) US Coast Guard Stop 7800 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7800

Shipping address for CG-9324:

For commercial courier and hand-carried deliveries:

United States Coast Guard (CG-9324) ATTN: SK1 Mark Solomon, (202) 475-3315 2701 Martin Luther King Jr Ave SE Gate 6, Building 50 Washington, DC 20032

CG-9125 Mailing address for CG-9125:

For US Mail delivery:

Commandant (CG-9125) ATTN: Formal Contracts Division V US Coast Guard Stop 7828 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7828

Shipping address for CG-9125:

For commercial courier and hand-carried deliveries:

United States Coast Guard (CG-9324) Attn: SK1 Mark Solomon, (202) 475-3315 2701 Martin Luther King Jr Ave SE Gate 6, Building 50 Washington, DC 20032

PART III, SECTION J, ATTACHMENT 2 000 - 17 Circular of Requirements

CODE ADDRESS

SFLC-ESD Mailing address for SFLC-ESD:

Surface Forces Logistics Center Engineering Services Division 707 E. Ordnance Road Baltimore, MD 21226

CG-751 Mailing address for CG-751:

For US Mail delivery:

Commandant (CG-751) ATTN: Office of Cutter Forces US Coast Guard Stop 7324 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7324

CG-1134 Mailing address for CG-1134:

For US Mail delivery:

Commandant (CG-1134) ATTN: Division of Safety Afloat US Coast Guard Stop 7907 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7907

CG-1B Mailing address for CG-1B:

For US Mail delivery:

Commandant (CG-1B) ATTN: Strategy & Human Resource Capability US Coast Guard Stop 7907 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7907

CG-452 Mailing address for CG-452:

For US Mail delivery:

Commandant (CG-452) ATTN: Resources Management Division US Coast Guard Stop 7714 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7714

C4ITSC (BOD-TAB) Mailing address for C4ITSC (BOD-TAB):

For US Mail delivery:

Commandant (C4ITSC (BOD-TAB)) ATTN: C4IT Service Center - Technical Authority Branch (BOD-TAB) US Coast Guard Stop 7710 2703 Martin Luther King Jr Ave SE Washington, DC 20593-7710

PART III, SECTION J, ATTACHMENT 2 000 - 18 Circular of Requirements

042-6.4.15 [RFP] Block 15 (BLK15) of the CDRL identifies the total number of copies of the CDRL to be distributed, in electronic and hard copy form.

042-6.4.16 [RFP] Block 16 (BLK16) in the CDRL provides additional requirements and amplifying instructions for any other block.

042-6.4.17 [RFP] For all drawings, hard copy shall mean paper unless otherwise required.

042-6.5 [RFP] Cover Format.

042-6.5.1 [RFP] All hard copy submittals shall be provided with a cover sheet. The cover sheet shall provide the following information unless otherwise specified in Block 16 or the Data Item Description (DID):

042-6.5.1.1 [RFP] A revision letter and date shall be included to reflect the revision of any previously submitted document. The cover sheet may provide a brief explanation of the reason for the change or a more detailed discussion may be included in the content of the submittal.

042-6.5.1.2 [RFP] The Contract number, CLIN number, and subtitle of Block 03 (or Block 02 if no Block 03 subtitle applies) shall be included. When multiple submissions are made under the same subtitle, a subtier title shall be included to further identify the content.

042-6.5.1.3 [RFP] Submittals requiring approval shall state: "This document requires Government approval." If approval has been granted, the approved version shall state: "This document has been reviewed and approved by the Government."

042-6.5.1.4 [RFP] Incremental submittals and documents regarding recurring meetings or events shall identify the specific increment/event date (if not otherwise identified in the subtitle).

042-6.5.1.5 [RFP] In the event that a Phase I CDRL deliverable is being submitted under the Phase II contract, the contractor shall provide the following certification on the cover sheet.

"This is a re-submittal of a Phase I CDRL deliverable. No changes have been made to the data, analyses, or system design reflected in this deliverable."

042-6.5.2 [RFP] The front matter of all digital submittals shall contain the same information as the hard copy submittals above.

042-6.6 [RFP] Transmittal.

042-6.6.1 [RFP] For distribution, a transmittal document shall be submitted for each copy of a submittal. All addressees shall receive the document with a Letter of Transmittal.

042-6.6.2 [RFP] The transmittal document shall be limited to one page. If additional space is necessary for information that cannot be incorporated into the data submittal, enclosures to the transmittal document may be appropriate. As a minimum, the following information shall be included on each letter of transmittal:

042-6.6.2.1 [RFP] Contractor's serial number and date;

042-6.6.2.2 [RFP] Contract number, CLIN number, and subtitle;

PART III, SECTION J, ATTACHMENT 2 000 - 19 Circular of Requirements

042-6.6.2.3 [RFP] Occurrence for the specific CLIN (for example, 1st, 2nd, 3rd);

042-6.6.2.4 [RFP] References to prior correspondence relating to the CLIN being submitted and, as appropriate, related CLINs with a brief explanation of the relationship;

042-6.6.2.5 [RFP] Any pertinent information not included in the text of the submittal that may relate to impending change action or resolution of design issues (such as "Update may/will be required pending resolution of ECP...");

042-6.6.2.6 [RFP] If not stated elsewhere, indication of whether the submittal is partial, complete, or resubmitted to reflect revisions;

042-6.6.2.7 [RFP] Government approval requirements and potential scheduling impact that could affect the work effort if Government response is untimely;

042-6.6.2.8 [RFP] Subtier titles and related identification numbers may be provided as an enclosure in the event of multiple submissions under the same CLIN; and

042-6.6.2.9 [RFP] Distribution and quantity of copies being sent (Block 14 of the

CDRL).

042-7 [RFP] Correspondence 042-7.1 [RFP] All correspondence by the Contractor with the Coast Guard shall be addressed to the Contracting Officer (original and two copies). Three copies of all correspondence (including phone conversation summaries) between the Contractor and Regulatory and Standards Bodies shall be provided to the Contracting Officer. (CDRL 042-001)

042-8 [RFP] Schedules 042-8.1 [RFP] The following general schedules shall be reflected in the Integrated

Master Schedule (IMS) required in COR Section 042-13:

042-8.1.1 [RFP] Erection Sequence Schedule

042-8.1.2 [RFP] Drawing Schedule

042-8.1.3 [RFP] Key Event Schedule

042-8.1.4 [RFP] Schedule of Required Dates for Materials

042-8.1.5 [RFP] Material Ordering Schedule

042-8.1.6 [RFP] Data Submission Schedule

042-8.1.7 [RFP] Factory and Familiarization Training Schedule

042-9 [RFP] Meetings 042-9.1 [RFP] General. The contractor shall host meetings as required throughout the contract, and ensure they are reflected in the IMP and IMS. For all meetings hosted, the contractor shall provide agendas (CDRL 042-002) and minutes

(CDRL 042-003).

042-9.2 [RFP] Routine Meetings. The Contractor shall conduct regular informal status meetings with the PRO to review and discuss contract administration issues.

Meetings shall occur at the request of either the Contractor or the Coast Guard, PART III, SECTION J, ATTACHMENT 2 000 - 20 Circular of Requirements but not more frequently than weekly, or less frequently than monthly, unless otherwise agreed to by the Contracting Officer.

042-9.3 [RFP] Formal Meetings. The Contractor may request formal meetings with the Government by providing at least thirty days notice, or as otherwise agreed to by the Contracting Officer.

042-10 [RFP] Integrated Product Data Environment (IPDE) 042-10.1 [RFP] General. The Contractor shall provide and maintain an Integrated Product

Data Environment (IPDE) to support the exchange and archiving of contract data.

The contractor shall submit all electronic contract deliverables and data via the IPDE for the Government to access and receive. Hard copy requirements are addressed in this COR Section.

042-10.2 [RFP] The IPDE shall, at a minimum, provide the following capabilities:

042-10.2.1 [RFP] Availability. The IPDE shall be operational and successfully tested by both the Contractor and the Government prior to the submission of any review materials required by the design review described in COR SECTION

068. Testing shall demonstrate the proper handling, storage, and retrieval of documents. The IPDE shall be available 24 hours a day, 7 days a week.

042-10.2.2 [RFP] Authorized Users. Access to the IPDE shall be restricted to authorized users through a controlled access web-enabled application.

Access to the IPDE shall be controlled by an initial challenge upon access.

The IPDE shall provide various levels of access rights and privileges specified at the user level (e.g., administrator, guest, user, super-user) and at the data/deliverables level (i.e., ability to allow access to specific data/deliverables to selected users only). The Contracting Officer, or his or her representative, will routinely provide the contractor with the names of authorized users, which will include contracted support personnel, and the level of access authorized for each. The contractor shall maintain and control authorized user access and provide an online list of valid users throughout the performance period.

042-10.2.3 [RFP] Access. The IPDE shall be internet accessible. Authorized personnel shall be able to access the IPDE via the internet using a standard web browser without the need to install or download additional client software.

Existing Government portals and websites will not be made available to host the IPDE.

042-10.2.4 [RFP] Data Exchange. The IPDE shall include a location and process to exchange contract documents between the Contractor and the Government.

The process shall include e-mail notification of data posted for exchange.

The intent is that the contractor will submit electronic data deliverables to the Government via this means, and provide email notification to the designated Government representative(s) of a waiting submittal. The Government representative(s) will then access the IPDE, download the submittal to a Government system, and acknowledge receipt of the submittal via email notification to the designated Contractor representative(s). A similar process shall be available for the Government to use to in providing data to the contractor.

042-10.2.5 [RFP] Archive Library. The IPDE shall include an archive library of all submittals exchanged via the data exchange process. The archive library shall be an electronic repository providing for the storage, posting, filing, PART III, SECTION J, ATTACHMENT 2 000 - 21 Circular of Requirements archiving, retrieving, moving, deleting, and locking/unlocking of data, information, and deliverables. Upon receipt of acknowledgement that the Government has received a submittal via the data exchange process, the Contractor shall remove the submittal from the data exchange location and archive it to the IPDE library. The archive library shall provide the capability to create, modify, delete, restrict, and move electronic folders and electronic folder structures while ensuring data integrity. File revisions shall be tracked and assigned different version numbers for auditing and rollback. The archive shall be indexed and provide the capability to search for information (data, deliverables, events, tasks, forums, etc.).

042-10.2.6 [RFP] Calendar. The IPDE shall provide an electronic calendar that reflects the Integrated Master Schedule for events and tasks that are related to the FRC acquisition. Attributes of events and tasks shall include type, title, description, start/end dates, recurrence, assignee, and owner. The IPDE shall provide the capability to view events and tasks in a chronological list or monthly tables, and shall allow for filtering and sorting by any or all of the attributes.

042-10.2.7 [RFP] Industry standard back up capability shall be provided and all back up media shall be kept, at a minimum, for the length of the performance period.

Back up media shall be indexed to provide straightforward access in case of information requests. In the event of an IPDE failure (including compromise due to hacker or virus attacks), lost information shall be limited to activities that have occurred within the preceding 24 hour period.

042-10.2.8 [RFP] The Contractor shall develop and provide IPDE user support for a Government user population estimated at approximately 50 users at any given time. User support shall promote rapid acquisition of the skills needed to use the IPDE and quick access to assistance when encountering problems during use, and may consist of classroom instruction, help desk support, printed desk guides, online help, Frequently Asked Questions (FAQs), and other similar methods. The mix of support formats should consider turnover of IPDE users, estimated at approximately every two years.

042-11 [RFP] Contract Work Breakdown Structure (CWBS) 042-11.1 [RFP] The Contractor shall develop a Contract Work Breakdown Structure

(CWBS) and CWBS Dictionary based on the CLIN structure in Contract Section B, including at a minimum the elements and sub-elements identified in Attachment 5 to Contract Section J, FRC Production CWBS.

042-11.2 [RFP] There shall be only one CWBS and it will be utilized and consistent throughout the contract. The CWBS shall provide the basis for communication throughout the FRC System acquisition process. It shall be the common link which unifies the planning, scheduling, cost estimating, budgeting, contracting, configuration management, and performance reporting disciplines. It is intended to provide a means of consistent communication to permit government and industry managers to evaluate progress in terms of contract performance. The CWBS forms the basis for the structure of the Systems Engineering Management Plan (SEMP), detailed design, configuration management, drawings, and provisioning.

042-11.3 [RFP] The CWBS shall provide clear traceability of all work efforts and end products. The CWBS shall be sufficiently detailed to identify all major

PART III, SECTION J, ATTACHMENT 2 000 - 22 Circular of Requirements subsystems or components using the guidance in MIL-HDBK-881A.