OBM_-_SOW_Draft.docx

DOCX document 34 KB Posted

Attached to
Outboard Motor (OBM) Inspection Repair/Refurbishment
Solicitation number
N61331-14-R-0010
Issued by

View the file

Other files

File Type Posted
N61331-14-R-0010_OBM-VA.doc DOC document
N61331-14-R-0010_CDRLS.doc DOC document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

STATEMENT OF WORK

FOR

SMALL OUTBOARD MOTOR (OBM)

INSPECTION, REPAIR, AND REFURBISHMENT

1.0 GENERAL

This Statement of Work identifies the requirements for the inspection, repair and refurbishment of small (55hp or less) Bombardier OBMs (including lower end units) in order to return the items to a reliable, operational condition that can be sustained with routine maintenance. The OBMs shall be picked up from and returned to Naval Amphibious Base (NAB) Little Creek, VA by the contractor in lots of one (1) to five (5), or more, and possibly in multiple lots. Pickup of the OBMs shall be made within two working days of notification by the Little Creek Naval Base point of contact, identified below, that they are ready for pickup. The contractor shall have all necessary equipment and authorizations to be able to drive in/out of NAB Little Creek and pick-up, at a minimum, (1) OBM, either palletized or unpalletized.

The contractor shall inspect each unit and provide a Limited Technical Inspection (LTI) (CDRL A001) report. The LTI shall detail the inspection results and specify the items recommended for repair or replacement not listed in Section 3.2 below titled “Refurbishment.” Repair or replacement items include, but are not limited to propellers, knobs, handles, switches, cylinders, valves, bearings and gears, etc. The desired turn-around time for completion of the LTI, refurbishment and repair of each lot of engines is within 45 days from date of pickup by the contractor.

1.1 Acronyms

CDRLContract Data List Requirements List
LTILimited Technical Inspection Report
OBMOutboard Motor
OEMOriginal Equipment Manufacturer
PCOProcuring Contracting Officer
SAESociety of Automotive Engineers
TMTechnical Manual

2.0 APPLICABLE DOCUMENTS

The Original Equipment Manufacturer’s (OEM) Technical Manual (TM), Service Bulletins, and other documentation shall govern the repair and maintenance.

3.0 REQUIREMENTS

3.1 Inspection (CDRL A001)

The contractor shall conduct a LTI on each OBM, including the gear case. The LTI shall be performed to sufficiently determine which items need to be repaired or replaced in order to return the unit to a reliable, operational condition. The LTI shall also include cylinder compression tests, cylinder leak-down tests and a check of the crank bearing clearances. The contractor shall perform the LTI on each unit in the lot shall than submit an estimate to repair that includes labor hours and parts required and estimated time to complete (date for return to Little Creek Naval Base) for each item. The LTI report and estimate for repair shall be submitted within ten (10) business days by e-mail to the Contracting Officer with a copy to the Little Creek Naval Base point of contact.

3.2 Refurbishment

Based on the LTI results the Government may to decide to repair and refurbish the units. Each unit to be refurbished shall be degreased and cleaned. All engine fluids shall be drained and replaced with new, manufacturer approved fluids. Additionally, the following items shall be replaced with new OEM parts:

a. Replace all spark plugs

b. Replace engine water pump

c. Replace engine thermostat

d. Replace engine fuel filter

e. Replace fuel lines and connectors.

f. Replace zincs

g. Replace lower unit seal(s)

h. Paint engine cowling, extension and lower gear case with OEM approved flat black paint

Refurbishment and repair shall be undertaken by the Contractor only after authorization has been granted in writing in the form of a contract modification. Authorization to proceed shall normally be provided within ten (10) working days of receipt by the Contracting Officer. Refurbishment and repair shall be accomplished in accordance with factory approved methods/procedures and the applicable documents identified in paragraph 2.0 above. Parts used shall be original equipment manufacturer (OEM) parts or Society of Automotive Engineers (SAE) approved parts for the correct year. Non-OEM parts shall be noted in the estimate.

Any delay in initially estimated date for return of individual lots of OBMs greater than one day that becomes evident during repair shall be reported in writing to the Contracting Officer and shall indicate the cause and a new estimated time to complete. This reporting of delay is required due to the tight scheduling of assets at Little Creek Naval Base.

3.3 Operational Testing

The contractor shall operate the engines for a minimum of 15 minutes in the test tank at NAB Little Creek with assistance of NAB personnel. NAB personnel will accept the engines if test is passed. A passed operational test shall include: ease of starting, operational check for leaks, visual inspection of exhaust, cooling water flow, unusual noises in engine and gear case, throttle response and post-operation visual inspection of engine upon completion of satisfactory 15 minute tank operation. If an engine fails operational testing the contractor will transport engine back to its facility and correct any deficiency.

3.4 Warranty

Contractor’s STANDARD commercial warranty for parts and labor shall apply to all refurbishment and repair actions.

3.5 Material Purchases

Only items directly used for this Contract, for work within the scope of the Performance Work Statement, shall be purchased under the Other Direct Cost (ODC) line items. Material purchases above $3,000 shall be approved by the Procuring Contracting Officer (PCO) prior to purchase by the contractor. The purchase request shall be itemized and contain the cost or price analysis performed by the contractor to determine the reasonableness of the pricing. The request and supporting documentation shall be submitted to the Contracting Officers Representative (COR) for concurrence prior to being submitted to the PCO for approval. The COR shall review and provide approval for material purchases at and below $3,000. Information Technology (IT) equipment, or services must be approved by the proper NSWC PCD approval authority. All IT requirements, regardless of dollar amount, submitted under this Contract shall be submitted to the Contracting Officer for review and approval prior to purchase. The definition of information technology is identical to that of the Clinger-Cohen Act, that is, any equipment or interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. Information technology includes computers, ancillary equipment, software, firmware and similar procedures, services (including support services), and related resources.

4.0 GOVERNMENT FURNISHED PROPERTY

The government shall utilize the Requisition And Invoice/Shipping Document (DD Form 1149) as the means for tracking each lot of engines turned over to the contractor for inspection and refurbishment. The government will identify the engines in each lot by serial number, which will be listed on the DD Form 1149. The DD Form 1149 shall be sent to Government contract personnel prior to engine pick-up by the contractor.

5.0 SECURITY

Data generated under this delivery order shall be UNCLASSIFIED. The Contractor will not be required to possess or store classified material in support of the SOW.

5.1 Minimum Requirements for Access to Controlled Unclassified Information (CUI)

Prior to access, contractor personnel requiring access to DON controlled unclassified information (CUI) or "user level access to DON or DoD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility, or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DON Central Adjudication Facility.

5.2 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides (OPNAVINST 5513 series) and unclassified limited documents (e.g., FOUO, Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.

5.3 Controlled Unclassified Information (CUI)

Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

5.4 For Official use Only (FOUO)

FOUO is a document designation, not a classification. This designation is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material, which although unclassified, disclosure to the public of the information would reasonably be expected to cause a foreseeable harm to an interest protected by one or more provisions of the FOIA. This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974, as amended. FOUO must be marked, controlled and safeguarded in accordance with DoD 5200.01, Vol. 4, DoD Information Security Program: Controlled Unclassified Information (CUI), February 24, 2012

5.5 Security of Unclassified DoD Information on Non-DoD Information Systems (DoD 8582.01) DoD Policy

Adequate security be provided for all unclassified DoD information on non-DoD information systems. Appropriate requirements shall be incorporated into all contracts, grants, and other legal agreements with non-DoD entities.

Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems, to the extent provided by the applicable contract, grant, or other legal agreement with the DoD.

Information Safeguards

Unclassified DoD information that has not been cleared for public release may be disseminated by the contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:

a. Non-public information provided to a contractor (e.g., with a request for proposal).

b. Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).

c. Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract-related event tracking).

It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However, all unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems shall minimally be safeguarded as follows:

a. Do not process unclassified DoD information on publically available computers (e.g., those available for use by the general public in kiosks or hotel business centers).

b. Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.

c. At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.

d. Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the contractor or teaming partner.

e. Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.

f. Transmit e-mail, text messages, and similar communications containing unclassified DoD information using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and transport layer security (TLS).

g. Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.

h. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

i. Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts).

j. Provide protection against computer network intrusions and data exfiltration, minimally including:

(1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

(2) Monitoring and control of both inbound and outbound network traffic (e.g., at the external boundary, sub-networks, individual hosts), including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services. Prompt application of security-relevant software patches, service packs, and hot fixes.

k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, critical program information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.

l. Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.

m. Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.

5.6 Operations Security

Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.

Critical information includes information regarding:

- Operations, missions, and exercises, test schedules or locations;

- Location/movement of sensitive information, equipment, or facilities;

- Force structure and readiness (e.g., recall rosters);

- Capabilities, vulnerabilities, limitations, security weaknesses;

- Intrusions/attacks of DoD networks or information systems;

- Network (and system) user IDs and passwords;

- Movements of key personnel or visitors (itineraries, agendas, etc.); and

- Security classification of equipment, systems, operations, etc.

The contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:

- Practice OPSEC and facilitate OPSEC awareness;

- Immediately retrieve documents from printers assessable by the public;

- Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;

- Protect information from personnel without a need-to-know;

- When promulgating information, limit details to that essential for legitimacy;

- During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.

6.0 PERIOD OF PERFORMANCE

The overall period of performance of this order shall not exceed five (5) years from date of award. Base period of performance is one (1) year, with four (4) one (1) year option periods.

7.0 GOVERNMENT-CONTRACTOR RELATIONSHIP

(a) The services to be delivered under this contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the contract between the Government and the Contractor's personnel. It is, therefore, in the best interest of the Government to afford both parties a full understanding of their respective obligations.

(b) All Contractor, subcontractor, and consultant personnel shall wear prominently displayed identification badges at all times when performing work on NSWC PCD property or attending meetings in the performance of this Task Order. The badge shall contain the individual's name, the company name and logo. When participating in such meetings (e.g., as a speaker, panel member), those individuals in Contractor employ must supplement physical identification (e.g., badges, place markers) with verbal announcements so that it is clear to the assembled group that they are employees of the Contractor, not NSWC PCD employees. In addition, when working on NSWC PCD property, all contractor, subcontractor, and consultant personnel shall have signs visible on their desks or at their work sites that clearly state that they are not NSWC PCD employees.

(c) The Contractor is responsible for supervision of all contractor personnel assigned to this contract. The Contractor shall exercise ultimate control over all aspects of Contractor personnel day-to-day work under this task order including the assignment of work, means and manner of Contractor employee performance and the amount of Contractor supervision provided. The Contractor shall be ultimately responsible for all aspects of performance under this contract including the work of its Contractor personnel.

Contractor personnel under this contract shall not:

(1) Be placed in a position where they are under the supervision, direction, or evaluation of a Government employee.

(2) Be placed in a position of command, supervision, administration or control over Government personnel, or over personnel of other Contractors under other NSWC PCD contracts, or become a part of the Government organization.

(3) Be used in administration or supervision of Government procurement activities.

(4) Have access to proprietary information belonging to another contractor without the express written permission of the owner of that proprietary information.

(d) Employee Relationship:

(1) The services to be performed under this contract do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

(2) Rules, regulations, directives and requirements that are issued by the U.S. Navy and NSWC PCD under its responsibility for good order, administration, and security are applicable to all personnel who enter the Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

(e) Inapplicability of Employee Benefits: This contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

(1) Payments by the Government under this contract are not subject to the Federal income tax withholdings.

(2) Payments by the Government under this contract are not subject to the Federal Insurance Contributions Act.

(3) The Contractor is not entitled to unemployment compensation benefits under the Social Security Act, as amended, by virtue of performance of this contract.

(4) The contractor is not entitled to workman's compensation benefits by virtue of this contract.

(5) The entire consideration and benefits to the Contractor for performance of this contract are contained in the provisions for payment under this contract.

(f) Notice. It is the Contractor's, as well as, the Government's responsibility to monitor contract activities and notify the Contracting Officer if the Contractor believes that the intent of this clause has been or may be violated.

(1) The Contractor should notify the Contracting Officer in writing promptly, within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this clause. The notice should include the date, nature, and circumstances of the conduct, the name, function and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct, identify any documents or substance of any oral communication involved in the conduct, and the estimate in time by which the Government must respond to this notice to minimize cost, delay or disruption of performance.

(2) The Contracting Officer will promptly, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

(i) confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) countermand any communication regarded as a violation

(iii) deny that the conduct constitutes a violation and when necessary direct the mode of further performance; or

(iv) in the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor and the date.

8.0 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA):

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil . Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.

File details come from the government source that posted it. Updated .