041-1.1 [Orig] This statement of work establishes requirements for the design, construction, testing, delivery, and operational support of a Response Boat – Medium (RB-M) System. The RB-M is primarily intended to recapitalize the capability of the multi-mission 41’ Utility Boats and to replace some of the Coast Guard’s larger non-standard boats.

041-1.2 [Orig] The primary role of the RB-M is outlined in Section J, Attachment 2, RB-M Specification, Section 044-1.

041-1.3 [Orig] The contractor shall manage the entire work effort to design, fabricate, construct, test, deliver and support the RB-M System including craft, cradle, logistics and data meeting the requirements of the Statement of Work and Specification for the base period and all exercised option periods.

041-2 [Orig] Contract Data Requirements

041-2.1 [Orig] Background. Throughout this contract, the contractor is required to develop, prepare, and submit data as a contract deliverable in support of the RB-M System. Where the type of data, the frequency of submission, and the format in which the data must be prepared is straightforward, the data requirements are often simply called out within the text of the contract. Where the data requirements may not be as straightforward, this contract makes use of Contract Data Requirement Lists (CDRLs), which are loosely based on the general DD Form 1423, to describe the characteristics of the data deliverable in a consistent, systematic way. CDRLs are located in Attachment 3 to Section J.

041-2.2 [Orig] General. The contractor shall develop, prepare, and submit data in accordance with the instructions in the contract, including the CDRLs and associated Data Item Descriptions (DIDs).

041-2.3 [Orig] 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.

041-2.4 [Orig] 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:

041-2.4.1 [Orig] 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.

041-2.4.2 [Orig] Block 2 is not used

041-2.4.3 [Orig] Block 3 (BLK03) of the CDRL identifies title of the CDRL, as it is referred to in this contract.

041-2.4.4 [Orig] 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.

041-2.4.5 [Orig] Block 5 (BLK05) of the CDRL identifies the relevant contract section(s) that invoke the CDRL.

041-2.4.6 [Orig] Block 6 is not used.

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

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

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

041-2.4.8.1 [Orig] 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 consider unacceptable any submission of data that does not comply with the contract requirements.

041-2.4.8.2 [Orig] 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.

041-2.4.8.3 [Orig] 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.

041-2.4.8.4 [Orig] 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.

041-2.4.8.5 [Orig] 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.

041-2.4.8.5.1. [Orig] 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 paragraph 041-2.4.8.6.

041-2.4.8.5.2. [Orig] 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 paragraph 041-2.4.8.5.3.

041-2.4.8.5.3. [Orig] 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.

041-2.4.8.6 [Orig] 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.

041-2.4.9 [A00006] 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, unless otherwise noted in Block 16. For deliverables where no specific distribution statement is required, mark the cover page with distribution statement F.

Code	Statement
A	Approved for public release; distribution is unlimited.
B	Distribution authorized to U.S. Government Agencies only. Other requests for this document shall be referred to Commandant (G-ARB).
C	Distribution authorized to U.S. Government Agencies and their contractors. Other requests for this document shall be referred to Commandant (G-ARB).
D	Distribution authorized to the Department of Homeland Security and U.S. DHS contractors only. Other requests shall be referred to Commandant (G-ARB).
E	Distribution authorized to US Coast Guard only. Other requests shall be referred to Commandant (G-ARB).
F	Further dissemination only as directed by Commandant (G-ARB) 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 (G-ARB). 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.

041-2.4.10 [Orig] 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.
WEKLY	Weekly

041-2.4.11 [Orig] Block 11 is not used.

041-2.4.12 [Orig] 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 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
DAC	Days After Contract Award
DA1002	Days After Delivery Order with CLIN 1002
DAx003	Days After Delivery Order with CLIN x003
DBIBR	Days Before Integrated Baseline Review (IBR)
DAPAT	Days After Preliminary Acceptance Trials (PAT)
DBPAT	Days Before Preliminary Acceptance Trials (PAT)
DBRBML	Days Before Delivery of first RB-M
DARBML	Days After Delivery of first RB-M
DARBM	Days After Delivery of an RB-M
DARBMP	Days After Delivery of the first RB-M designated as Production
DARC	Days After Receipt of Comments
DATC	Days After Test Completion

041-2.4.13 [Orig] 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.

041-2.4.14 [Orig] Block 14 (BLK14) of the CDRL identifies the distribution of the deliverable.

041-2.4.14.1 [Orig] Electronic distribution. One electronic copy of each submission is always required. Electronic copies shall be source files delivered via the IPDE, described in section 041-6, 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:

041-2.4.14.1.1. [Orig] Microsoft® Windows XP® operating system

041-2.4.14.1.2. [Orig] Microsoft® Office 2003 applications

041-2.4.14.1.3. [Orig] AutoCAD® version 2005

041-2.4.14.2 [Orig] 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, 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.
Boat	Provide a copy with the RB-M at delivery.
G-ARB	For US Mail delivery: Commandant (G-ARB) Attn: Response Boat - Medium U.S. Coast Guard Headquarters 2100 Second Street, SW, JR1100 Washington, DC 20593-0001 For commercial courier and hand-carried deliveries: US Coast Guard (G-ARB) Attn: SK2 Xavier Storr, (202)475-3321 1900 Half St SW, Suite 11-0705 Washington, DC 20024
G-ACS	For US Mail delivery: Commandant (G-ACS-4/SP) M/F: HSCG23-06-D-ARB001 U. S. Coast Guard Headquarters 2100 Second Street SW, JR11-0116 Washington, DC 20593-0001
ELC-014	Commanding Officer (014) Attn: Chief, Standard Boat Branch USCG Engineering Logistic Center 2401 Hawkins Point Road, Mail Stop 26 Baltimore, MD 21226-5000
ELC-024	Commanding Officer (024) Attn: Chief, Boat Engineering Branch USCG Engineering Logistic Center 2401 Hawkins Point Road, Mail Stop 25 Baltimore, MD 21226-5000
Office Code G-OCS G-OCS-2 CG-1134 CG-1321 CG-452 CG-641	Suite # 3208 3208 5304 5100 6210 6414	Commandant (office code) U.S. Coast Guard Headquarters 2100 Second Street, SW, Suite #### Washington, DC 20593-0001

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

041-2.4.14.4 [Orig] Block 16 (BLK16) in the CDRL provides additional requirements and amplifying instructions for any other block.

041-2.5 [Orig] Cover Format

041-2.5.1 [Orig] 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):

041-2.5.1.1 [Orig] 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.

041-2.5.1.2 [Orig] 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.

041-2.5.1.3 [Orig] 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."

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

041-2.5.2 [Orig] The front matter of all digital submittals shall contain the same information as the hard copy submittals above.

041-2.6 [Orig] Transmittal

041-2.6.1 [Orig] 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.

041-2.6.2 [Orig] 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:

041-2.6.2.1 [Orig] Contractor's serial number and date;

041-2.6.2.2 [Orig] Contract number, CLIN number, and subtitle;

041-2.6.2.3 [Orig] Occurrence for the specific CLIN (for example, 1st, 2nd, 3rd);

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

041-2.6.2.5 [Orig] 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...");

041-2.6.2.6 [Orig] If not stated elsewhere, indication of whether the submittal is partial, complete, or resubmitted to reflect revisions;

041-2.6.2.7 [Orig] Government approval requirements and potential scheduling impact that could affect the work effort if Government response is untimely;

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

041-2.6.2.9 [Orig] Distribution and quantity of copies being sent (Block 14 of the CLIN).

041-3 [Orig] Information Management

041-3.1 [Orig] The con tractor shall develop, implement and maintain a Technical Information Management and Control Plan (TIMCP) CDRL 041-001 that establishes the policy, procedures and processes that will be used to develop, check, distribute, update, manage the configuration of, and deliver the technical information necessary to design, construct and deliver the RB-M and all other contract products and deliverables.

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

041-3.2.1 [Orig] 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-3.2.2 [Orig] 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-3.2.3 [Orig] Sufficient redundancy shall be built into all computer systems to minimize data loss in the event of failure or loss.

041-3.2.4 [Orig] 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.

041-3.2.5 [Orig] All electronic data is to be provided to the Government in accordance with the Contract requirements so it can be read into the Government’s interim logistics, warranty, contract and Fleet Logistics System (FLS) software, via CD, DVD, or the internet, without any modifications.

041-4 [Orig] Information Technology Integrator

041-4.1 [Orig] The contractor shall provide an Information Technology Integrator (ITI) to coordinate the development and implementation of the various information systems required to support the RB-M System.

041-4.2 [Orig] In addition to the resources the Contractor requires to support RB-M System requirements, the ITI shall provide the following full time equivalent positions to support the Coast Guard in developing the interface between the Contractor-developed RB-M System information support systems and the existing and emerging Coast Guard logistics information systems. These ITI representatives shall, on a best effort basis, coordinate and attend meetings with Coast Guard and other agency representatives, provide a conduit for the exchange of information between the Contractor and the Coast Guard regarding the RB-M System information support systems, develop and define requirements for these systems, develop and define requirements for the interface between these systems, and develop and implement solutions to meet those requirements from initial deployment to full time sustainment. Representatives must possess excellent communications skills, be fully versed with the technical aspects of the information systems being used, and be fully capable of implementing solutions, including writing code. Any required travel or other direct costs associated with the performance of their duties must be authorized by the Contracting Officer in advance as part of a task order against CLIN x006 or x007, as appropriate.

041-4.2.1 [Orig] One representative located at the contractor’s facility to serve as the CG liaison to the Integrated System Model (ISM) development and maintenance team. The ISM is described in paragraph 041-5.

041-4.2.2 [Orig] One representative located at the Coast Guard PRO facility to serve as the liaison to the Coast Guard user community.

041-4.2.3 [Orig] One representative located at Coast Guard Headquarters in Washington, DC, to serve as the liaison to the organizations responsible for the development and maintenance of Coast Guard logistics information support systems.

041-4.2.4 [Orig] Additional representatives to support these or other ITI-related tasks may be required and are within the scope of this contract but will be the subject of a contract change to definitize the requirements and duration of performance.

041-4.3 [Orig] The contractor shall utilize the IT Integrator, and the information gained through the representatives provided in section 041-4.2, to continually determine the data and interface requirements necessary for the ISM to achieve and maintain full functionality with existing Coast Guard logistics information systems. The contractor shall prepare and submit IT Integrator Reports (CDRL 041-002) as necessary to identify concerns and recommendations on ISM-related topics, including the following general categories:

041-4.3.1 [Orig] Conversion and implementation support

041-4.3.2 [Orig] Data/records management

041-4.3.3 [Orig] Database planning and design

041-4.3.4 [Orig] Network services, programming

041-4.3.5 [Orig] Network services, project management

041-4.3.6 [Orig] Resources and facilities management

041-4.3.7 [Orig] Systems analysis and design

041-4.3.8 [Orig] Data security

041-4.3.9 [Orig] Integration into existing systems

041-4.3.10 [Orig] Training and recommendations for sustainment personnel

041-4.3.11 [Orig] Hardware/software recommendations

041-4.3.12 [Orig] Requirements definitions (with CG-442)

041-5 [Orig] Integrated System Model (ISM)

041-5.1 [Orig] Definition. The ISM is defined as a Contractor-provided information system which implements a product lifecycle model for the RB-M System, in order to efficiently satisfy the data requirements of both the Government and Contractor. The ISM shall integrate the RB-M System support data products, such as drawings, technical data, supply support data, configuration data, technical documentation, and maintenance data, with the program execution information, such as plans and procedures to create, maintain, and dynamically deliver this information in support of the performance of this contract. The ISM need not be a single all-encompassing application, but must be capable of integrating the RB-M System data, potentially stored in different applications, used to support all of the required functions. Typically, each of the functions listed as requirements for the ISM is developed and executed as isolated individual software applications, often by different organizations or different groups within a single large organization, with cumbersome business rules and process used to attempt to ensure that data duplicated throughout many applications is kept current. The purpose of the ISM is to explicitly require these applications to be integrated. Integration in this context is synonymous with the database term normalization, so that any data element for the RB-M (configuration item, part number, casualty entry, tech manual instruction, contact information, etc.) is saved only once in the ISM, with the end result that a change to data supporting the RB-M need only to be made once, inherently affording data integrity. The ISM is expected to provide the capability to concurrently develop, capture, update and re-use data, in electronic form, in a fashion that leads to data integrity, efficiency, and effective control of the configuration of the RB-M System throughout the contract performance period, and throughout the RB-M System lifecycle.

041-5.2 [Orig] General.

041-5.2.1 [Orig] The contractor shall develop, deploy, and operate an Integrated System Model (ISM) designed to support the RB-M System during design development, construction, production, and the remainder of its life cycle.

041-5.2.2 [Orig] At the end of the contract performance period, or earlier if directed by the Contracting Officer, the contractor shall deliver the populated ISM, required documentation, associated software, and the necessary rights to that data and software, so that the Government may deploy, operate, modify, and maintain it for the duration of the RB-M life cycle. Details of final delivery requirements are discussed in 041-5.7.

041-5.3 [Orig] Plan and Schedule. The contractor shall develop an ISM Implementation Plan and Schedule (IIPS) as a subsection of the Technical Information Management and Control Plan required under 041-3.1 (CDRL 041-001). The IIPS shall fully describe how the ISM will be developed, tested, approved, maintained, deployed and delivered using a logical time-phased methodology. It shall address at a minimum:

041-5.3.1 [Orig] A schedule for ISM development and deployment which identifies milestones and phases for completion of all ISM requirements.

041-5.3.2 [Orig] A description of the change management system for the ISM.

041-5.3.3 [Orig] A description of the relationship between the contractor and the IT Integrator, and the responsibilities the IT Integrator has for the development, deployment, and delivery of the ISM.

041-5.3.4 [Orig] A description of applicable testing and documentation necessary to demonstrate functionality.

041-5.3.5 [Orig] A discussion of how the ISM can be adapted for interfacing with future Government logistics support systems.

041-5.4 [Orig] Functionality.

041-5.4.1 [Orig] The ISM shall integrate, at a minimum:

041-5.4.1.1 [Orig] The 2D Product Drawing package as described in section 085-2.

041-5.4.1.2 [Orig] The 3D Technical Data package as described in section 085-1.

041-5.4.1.3 [Orig] Supply support data, including the Master Equipment Configuration List (MECL), as described in section 085-4, provisioning information as described in section 083-1.1, and other required data.

041-5.4.1.4 [Orig] All technical documentation and other data required in section 086.

041-5.4.1.5 [Orig] The Integrated Product Data Environment (IPDE), as described in section 041-6.

041-5.4.1.6 [Orig] Maintenance, casualty tracking, warranty administration, trouble call response, and other required data as described in section 080-2.

041-5.4.1.7 [Orig] The various components of the configuration management system, including the Engineering Change Request Tracking system, described in section 068-2.

041-5.4.1.8 [Orig] The Field Support Desk web site described in section 080-2.2.

041-5.4.1.9 [Orig] Deployment of the design exploration model as described in section 041-4.3.

041-5.4.2 [Orig] The ISM shall provide user interaction through a standard browser interface conforming to the Government’s current information technology infrastructure and have a single access point through the Field Support Desk website described in section 080-2.2. The standard browser interface shall support industry recognized interface protocols such as Simple Object Access Protocols (SOAP).

041-5.4.3 [Orig] The ISM shall also support the existing and developing Coast Guard logistics support systems. The Coast Guard logistics information systems infrastructure, where the data contained in the ISM will eventually reside, is undergoing significant transformation. At various points during the performance period, after portions of this infrastructure have sufficiently matured, the contractor shall be required to deliver certain data to the Coast Guard. Transformation of the data from Contractor format to Coast Guard format, including the development of the requirements to make such a transformation, is within the scope of this contract and may be accomplished by the Information Technology Integrator on a best effort basis as part of the requirements of SOW 041-4.2, or be the subject of a contract change to definitize the requirements and duration of performance.

041-5.5 [Orig] ISM Development

041-5.5.1 [Orig] The ISM shall be developed using multidimensional product model methodology. The ISM shall be one or more relational databases capable of real-time synchronization and real-time external interfacing.

041-5.5.2 [Orig] The ISM shall be developed from the start to support an end-state fleet of the maximum ordering quantity identified in section B.3, and shall be able to incorporate the data associated with each RB-M as it is produced with no performance degradation as the number of boats delivered and fielded increases.

041-5.5.3 [Orig] The ISM shall be extensible, to prevent obsolescence and facilitate growth and modification that may be necessary as the Coast Guard logistics information system(s) mature throughout the lifecycle of the RB-M. Changes to the ISM required during the performance period to accommodate the maturation of the Coast Guard logistics information systems are within the scope of this contract and may be accomplished by the Information Technology Integrator on a best effort basis as part of the requirements of SOW 041-4.2, or be the subject of a contract change to definitize the requirements and duration of performance.

041-5.5.4 [Orig] The ISM shall be developed to incorporate and support existing and new business processes used between the Coast Guard users (Project and Field) and the contractor to support the RB-M System. To the extent practicable, the ISM should also be developed to incorporate and support the contractor’s internal business processes to promote data integrity, efficiency, and configuration control throughout the production of the RB-M System.

041-5.5.5 [Orig] The ISM shall be developed to include a design exploration model, capable of loading current and archived ISM data to allow the Coast Guard and the contractor to explore what-if scenarios in support of design development, engineering changes, deviations, and the like. The design exploration model may draw data in real-time from the current data within the ISM but shall not be capable of altering the current data within the ISM. The design exploration model shall be available to the Coast Guard for use at any time after the ISM is deployed. It need only be capable of supporting one exploration session at a time but shall be capable of saving and loading design exploration sessions so that multiple unrelated sessions may be explored without interfering with each other or the current data within the ISM. Loading current ISM data and previously saved data must be simple enough to be accomplished by the user of the model. Loading of archived ISM data, if cumbersome, may be accomplished on a best effort basis as described in section 041-4.2.

041-5.6 [Orig] Deployment

041-5.6.1 [Orig] The contractor shall provide, operate, and maintain the ISM throughout the performance period, ensuring full continuous capability until final delivery of the system is made in accordance with section 041-5.7.

041-5.6.2 [Orig] The contractor shall develop, provide, and maintain manuals and other performance interventions to assist users in effectively utilizing the ISM.

041-5.6.3 [Orig] The contractor shall develop user training or other performance interventions to enable users to effectively utilize the ISM. The contractor shall provide the training as requested on a best effort basis as described in section 041-4.2.

041-5.6.4 [Orig] The contractor shall develop and maintain manuals and other performance interventions to assist contractor personnel in effectively manipulating and sustaining the ISM. The products of these efforts shall be included as part of the final delivery of the ISM as described in section 041-5.7.1.

041-5.6.5 [Orig] The contractor shall develop and maintain data/system manager training or other performance interventions to enable government representatives to effectively manipulate and sustain the ISM. The products of these efforts shall be included as part of the final delivery of the ISM as described in section 041-5.7.1.

041-5.7 [Orig] Delivery

041-5.7.1 [Orig] At the end of the contract performance period, or when notified by the Contracting Officer, the contractor will cease operating the ISM and transfer it, including the data, user interface, source code, supporting software, related documentation, and the rights to use, modify, maintain, and operate it (see FAR 52.227-14(c)(1) and FAR 52.227-19(c)(3) incorporated at I.1), to the Government for deployment on a Government system.

041-5.7.2 [Orig] The contractor shall develop and follow a final delivery plan to coordinate this transfer. The final delivery plan shall be a part of the IIPS, required at paragraph 041-5.3, and be updated annually to reflect the current state of the ISM as well as the current state of the Government systems, as understood by the IT Integrator. At a minimum, the final delivery plan shall address:

041-5.7.2.1 [Orig] A detailed technical description of the ISM, including the data, user interface, supporting software, and related documentation.

041-5.7.2.2 [Orig] The resource requirements necessary to deploy the ISM, including:

041-5.7.2.2.1. [Orig] Sof