ShipWeight API and Data Entry SOW.pdf

Statement of Work for Development of ShipWeight API and USCG Database

(Revised 13 June, 2022)

1 Introduction

1.1 Background – The US Coast Guard is involved in early-stage design trade space and requirements investigations related to icebreaker design. Support is required to develop tools for use in an icebreaker design synthesis model for efficient trade space analysis and requirements development.

1.2 The objective of this effort is to develop an application programing interface to automate the parametric weight estimation capability of ShipWeight, a purpose-built software program for ship weight engineering. Once automated, ShipWeight can be included in an icebreaker design synthesis model to support the analysis of early-stage icebreaker designs. This capability is needed to allow USCG personnel the ability to populate a trade space with many feasible and effective hull forms to inform the decision making and requirements development process.

2 References

None.

3 Task Statements

The effort shall be performed according to the following task statements.

3.1 Task 1 – Develop an Application Programming Interface for ShipWeight

The contractor shall develop and implement an Application Programming Interface (API) for ShipWeight to perform automatic parametric weight estimation. The API shall be compatible with ModelCenter and allow ShipWeight to run as a component within a ModelCenter workflow.

The contractor shall research and identify the appropriate level of integration in collaboration with the USCG. The baseline approach shall be a file-based automation, where ModelCenter supplies an input file and ShipWeight responds with an output file containing the weight estimate. Other approaches include, but are not limited to, a direct call to ShipWeight via a dynamic link library (dll).

The API shall pass inputs of relevant ship and ship system parameters to ShipWeight from an XML, text, or other easily-manipulated file format. Relevant ship parameters include, but are not limited to, principal characteristics, ship type, ice class, crew size, deck area, volume, and main propulsion power.

The API shall output the estimated weight and centers of gravity for the lightship and approximate full load conditions from ShipWeight in an XML, text, CSV, or other easy-to-parse file format. The user shall have the option to output the estimates at the lightship, 1-digit, or 3-digit SWBS (Ship Weight Breakdown Structure) level, pending the availability and completeness of historical data (see Task 2).

A user guide or documentation for the API shall be provided.

3.2 Task 2 – Build a ShipWeight Database for Existing USCG Cutters

The contractor shall build a ShipWeight database for the existing USCG cutter fleet that includes the below classes:

‐ 420-WAGB

‐ 399-WAGB

‐ 418-WMSL

‐ 270-WMEC

‐ 240-WLBB

‐ 225-WLB

‐ 175-WLM

‐ 154-WPC

‐ 140-WTGB

The database shall be created from government furnished weight reports, which may be in PDF, Microsoft Word, or Microsoft Excel formats. The data shall be entered into ShipWeight in a consistent SWBS across all classes. If available, data shall be entered into ShipWeight at the 3-digit level, but otherwise at the 1-digit level. All parameters identified for use in the parametric estimation from Task 1 shall be entered into the database. Quality assurance checks shall be implemented to ensure alignment to a consistent SWBS. The USCG will assist with adjudicating any discrepancies.

If available, data shall be entered for two hulls from each class to improve accuracy. The results of inclining reports shall be compared to the weight report data and discrepancies between the two shall be appropriately spread through the weight groups.

ShipWeight regressions shall be used to perform quality assurance and accuracy checks on the data set. Any outliers shall be investigated and be either corrected or understood. USCG will provide support for these reviews.

3.3 Task 3 – Develop Reporting and Deliverables

The Contractor shall develop a final report documenting the work conducted. The Contractor shall meet with SFLC-ESD-NAME-NAV ARCH personnel, either online or at the SFLC office located in Glen Burnie, MD to present the results of this effort and demonstrate the capabilities of the tools and the database developed per each task. The deliverables shall include a descriptive report, User Manuals or guidance, and a copy of the final version of the software and database. Files shall be provided on CD/DVD and delivered via email or other electronic file transfer.

3.4 Task 4 – Provide Post-Delivery Support for Training and Implementation

The Contractor shall provide training to SFLC-ESD-NAME-NAV ARCH personnel on the use of the software and database deliverables, either online or in-person at the SFLC office located in Glen Burnie, MD. The training shall include a demonstration through a worked example for Task 1, and a review of the database, parameters, and estimating relationships developed in Task 2.

The Contractor shall provide post-delivery implementation support for the software and database deliverables.

4 Period of Performance Period of performance shall be 6 months from the date of award.

5 Schedule and Deliverables

5.1 Kickoff Meeting – within 2 weeks of contract award.

5.2 Application Programming Interface for ShipWeight – Due 5 months after contract award.

5.3 ShipWeight Database for Existing USCG Cutters – Due 5 months after contract award.

5.4 All contract items shall be presented and provided at a meeting with the USCG on or before the due date for the task.

5.5 Status Reports – Due Monthly after Kick-Off Meeting

‐ Reports should summarize work completed since last update (last monthly report);

highlight questions and concerns for USCG attention; and provide overall progress of project and remaining work.

5.6 Travel – Local travel may be required throughout the period of performance to the SFLC facility located at 707 E. Ordnance Road, Baltimore, MD. These trips may include the following: kickoff meeting, collaboration meetings (as required), and final presentation meeting and handoff of final deliverables.

6 Security Clearance

6.1. This work is not classified. No security clearance is required.

7 Contracting Officer’s Representative

7.1. The Contracting Officer’s Representative (COR) and technical point of contact at the U.S.

Coast Guard Surface Forces Logistics Center will be Mr. Ben Brainard, SFLC-ESD- NAME-NAV ARCH, Phone: (410) 762-6811, e-mail: Benjamin.C.Brainard@uscg.mil.

7.2. The Alternate Contracting Officer’s Representative (ACOR) at the U.S. Coast Guard Surface Forces Logistics Center will be Mr. Jeff Bloomer, SFLC-ESD-NAME-NAV ARCH, Phone: (410) 762-6136, e-mail: Jeffrey.A.Bloomer @uscg.mil

8 Notes

8.1 Use of Government Furnished Material – Government furnished material shall be used for the delivery order only and shall not be used or disseminated for any other purpose.

8.2 Rights in Data – The USCG shall retain Usage Rights in all data, including software, developed as part of the effort regardless of form or medium. Government furnished data are considered to be solely the property of the USCG and shall not be released without the written consent of the USCG. The Contractor shall retain Commercial Rights to all software developed under Task 1.