Statement of Work Ship Manager Reporting Tool.pdf

1 Background Reserve Force (RRF), National School Multi-mission Vessel (NSMV), Special Mission

Ships, Reserve Fleet Sites, and Legacy School Ships. The RRF is specifically structured to transport Department of Defense (DOD) unit equipment and initial resupply for forces deploying anywhere in the world during the critical period before adequate numbers of commercially available ships can be marshaled. The ships are maintained and operated by commercial ship management companies under contract with the U.S. Maritime Administration

(MARAD).

The NDRF uses the American Bureau of Shipping (ABS) Nautical System Enterprise (NSE) a client Server MySQL-based database application. NSE is the maintenance management and financial tracking system of record for the RRF program. MARAD had a custom reporting tool known as the Ship Manager Reporting Tool, to extract Data from NSE into a useful form to support the RRF Budget cycle and contractor support labor, to support the 5-year budget request process.

The Ship Manager Reporting Tool currently has 20 custom reports, that are used by MARAD to provide contract oversight, maintenance execution, and business planning and execution monitoring. Ship Managers use the tool to develop business plans, drydocks, and monitor execution of business plans from the current Fiscal Year.

2 Statement of Work

2.1 Licensing

MARAD requires licenses for the Ship Manager Reporting / Data Extraction Tool

(Application), granting access to the executable binaries for use by entities, currently under contract or awarded contracts, as Ship Managers or General Agents, by MARAD within the period of performance of this contract. Ship Managers shall be entitled to use the application only on their copy of the MARAD RMS NSE database. Licenses shall be issued from 15 January to 14 January.

2.2 Application Updates

2.2.1 Support of NSE Software upgrades

The Contractor shall maintain the application to be compatible with the latest release of MARAD’s NSE. The contractor is solely responsible for the quality assurance and testing of the product and of subsequent releases.

2.2.2 MARAD Requested Application Changes to Existing Reports

The Contractor shall update the reporting tool to include a business plan preparation, and Business Plan Execution Monitoring for the next fiscal year with updates requested from MARADs Business Planning Process Improvement Team (BPPIT). The updated release of the Ship Manager Reporting tool shall be deployed to all sites by the 3rd Friday in March.

2.2.3 Additional Reports

The Contractor shall build new reports to the Ship Manager Reporting Tool as required by MARAD.

2.3 Business Planning Process Improvement Meeting.

The contractor shall attend MARAD’s Business Planning Process Improvement Team (BPPIT) annual meeting to provide input to requested changes, to the Applications Business Plan Module for the next Fiscal Year.

2.4 Source Code

Source code for the application will be provided to MARAD in the event that the contractor chooses to, or is not able to, provide maintenance of the application.

2.5 Connections of the RCR Datawarehouse to other Business Intelligence Tools.

MARAD currently connects the RCR Datawarehouse to SAP Crystal Reports. The Contractor shall maintain all connections from the RCR database to any business intelligence tool that MARAD purchases.

3 Deliverables

3.1 Status Updates

The Contractor shall provide a Bi-weekly work plan to the Contracting Officer’s

Representative (COR), on the first business day of a bi-weekly period when tasking has been issued and continue until the tasking is complete. This work plan shall be in excel format.

The first report shall be provided on the 11th business day after award of the Order. The work plan shall include for each task:

• Description of the Task

• RMS Help Desk Ticket Number (If applicable)

• Personnel assigned to Task

• Percent completion of Task

• Estimated Completion Date of Task

3.2 Place of Performance / Delivery

Unless otherwise specified, deliverables shall be furnished, electronically, to the following addresses:

DOT/OST/OGC/MARAD

Attn: Aaron Gottlieb, COR 1200 New Jersey Avenue SE Washington, DC 20590 Phone: (202)-689-5899 E-mail: aaron.gottlieb@dot.gov

3.3 Billing

3.3.1 Licensing

An invoice for all software licenses shall be submitted for the COR’s review, no later then 1 month after the new contract year.

mailto:aaron.gottlieb@dot.gov

3.3.2 Labor

On a monthly basis, when applicable, no later than the seventh business day of each month, the contractor shall submit invoices for the COR’s review and approval. Invoices shall be submitted month in accordance with the Invoicing Requirements/Instructions.

4 Personnel

4.1 Personnel Security Requirements:

4.1.1 The Contractor personnel will follow the guideline of Privacy or Security

Safeguards prescribed in FAR 52.239-1.

4.1.2 All Contractor employees having access to (1) Department of Transportation information or a Department of Transportation information system or (2) sensitive data/information shall complete initial and periodic security training. To include but not limited to:

4.1.3 DOT Information System Responsibilities and Rules of Behavior for Users, Account Administrators, and System Operators.

4.1.4 Annual DOT Security Awareness Training (SAT).

4.1.5 DOT Annual Privacy Awareness training.

4.1.6 Personnel with NSE Database Administrator user profiles will be required to sign a Non-Disclosure Agreement (NDA) due to the proprietary nature of the ship mangers’ data.

4.1.7 All completed documents shall be provided to the COR.

4.2 Personnel Identity

4.2.1 It is the responsibility of the contractor to verify that all proposed contractor personnel for the contract meets federal employment eligibility, the validity of Social Security number (SSN) and is suitable for employment and/or access to Controlled Unclassified Information (CUI).

4.2.2 MARAD will not initiate requests for appropriate investigation on behalf on contractor’s personnel. The cost incurred from the security clearance shall be borne by the contractor.

4.2.3 Contractor staff may require using DOT-Issued Personal Identity Verification (PIV) card to access DOT network. The Government will issue the PIV cards to the contractor staff whose assigned duties require them.

4.2.4 The contractor shall not begin the performance of substantive work under this Contract until enough personnel have presented evidence that they have the required credential which has been approved by MARAD. The contractor further agrees to include this provision in any subcontract awarded pursuant to his contract.

5 Travel Requirements

5.1 Travel costs will be reimbursed at actual cost in accordance with the Federal Travel Regulation (FTR) and FAR part 31.205-46 Travel Costs. Substantiating receipts must be submitted in accordance with FTR 301-11.25. The Contractor will submit travel requests to the COR for approval, via email, in advance of each travel event. Reimbursement will not be approved for unauthorized travel.

5.2 The Contractor shall not charge local travel costs within a 50-mile radius of their home of record or to the Contractor’s office.

https://www.gsa.gov/policy-regulations/regulations/federal-travel-regulation https://www.gsa.gov/policy-regulations/regulations/federal-travel-regulation https://www.ecfr.gov/current/title-48/chapter-1/subchapter-E/part-31/subpart-31.2/section-31.205-46 https://www.ecfr.gov/current/title-41/subtitle-F/chapter-301/subchapter-B/part-301-11