DRAFT_Maintenance-SLEP_SOW.PDF

SECTION C.

C.1.0 General Requirements:

The purpose of this contract is for the contractor to provide services to accomplish On Condition Cyclic Maintenance (OCCM) and Service Life Extension (SLEP) efforts on the Army Vessel Fleet identified in Exhibit XX, which will result in delivery of fully mission capable vessel(s). The contractor shall furnish all labor, materials, and equipment to accomplish the services identified in the applicable task order(s); and provide vessel certifications to the US Army Active and Reserve Vessels.

C.1.0.1 The contractor, as an independent contractor and not as an agent of the Government, shall only perform work under this contract to the extent authorized by written task orders signed and provided by the Contracting Officer (CO). Work authorized by task orders shall in no case require or constitute personal services as defined in the Federal Acquisition Regulation (FAR 37.104).

C.1.0.2 Scope The contractor shall be able to perform maintenance, repairs, modernization and modifications to the following systems, on any of the US Army’s vessel fleet, in attachment 0001.

a. Mechanical Systems

b. Electrical Systems

c. Air Conditioning Systems

d. Hydraulic Systems

e. Fuel Systems

f. Piping Systems

C.1.0.3 Services specified in individual task orders may include a single task or multiple tasks, in any combination as identified in the task order. Such repairs, modification, modernizations or maintenance services will fall into one or more of these categories:

a. Painting/Coating

b. Installation of Machinery

c. Fabrication of test asset hardware for trial installation and testing

d. Structural analysis on parts, components, and assemblies

e. Support of Government and third party tests

f. Field review of modification and failed parts or systems

g. Technology surveys

h. Annual and Cyclic Certifications

i. Towing the vessel

j. Source and procure materials

k. Welding

l. Replace obsolete equipment/systems

m. Add new capability to meet operational needs requirements

n. Maintain vessel configuration

C.1.0.4. Performance Period: The period of performance will be identified in the task order.

C.1.0.4.1. The performance period will begin upon the vessel’s arrival at the designated contractor’s facility, For vessels arriving at the Contractor’s facility prior to or at 12:00 noon, the performance period commences on the date of arrival. Vessels arriving after 12:00 noon, the performance period commences the following day. In the event the vessel is not picked up within seven calendar days or as stated in the contract/delivery order, after receiving the Notice to Proceed the performance period shall commence on the seventh after such notification has been given.

C.1.0.4.2 Any work which requires the CORs inspection will require two hour’ notice and shall be scheduled during the normal working hours and days. Working hours will coincide with commencement of the routine working hours of the contractor. For example, for those Contractors with a 0700 hours commencement time, the COR will be present during the hours of 0700 through 1530; for a 0730 commencement time, it would be 0730 through 1600 hours.

The COR will not be present on the following holidays:

New Year's Day Martin Luther King Jr.'s Birthday President's Day Memorial Day Independence Day Labor Day Columbus Day Veteran's Day Thanksgiving Day Christmas Day

C.1.0.4.3 The contractor shall not schedule interfacing work (meetings, approvals, deliveries, etc) with the Government on any of the recognized holidays in federal services, or any other day designated as a holiday by Federal Statue or by Executive Order except with prior approval from the Contracting Officer. If a holiday falls on a Saturday the official holiday will be celebrated the preceding Friday. If a holiday falls on a Sunday, the official holiday will be celebrated the following Monday

C. 1.0.4.4. Government Delivery and Pick-up of Vessel:

In the case of a Government vessel delivery to a contractor’s facility, the contractor shall provide location specific instruction to the vessel crew for the safe handling and docking of the vessel. If the Government determines that because of the location of the contractor’s shipyard, the vessel should be delivered to an alternate site (normally the Government facility nearest to the contractor’s facility), rather than the stream adjacent to the facility, the contractor shall take acceptance of the vessel at the alternate site immediately from the Army. Picking up the vessel at an alternate site shall be at no additional cost to the Government.

C. 1.0.4.5 If the Government chooses, it may pick-up the vessel from the contractor’s facility or other designated location(s). The contractor shall appropriately provide for the safekeeping of the vessel while awaiting the Government’s crew, in accordance with good business practices of the industry, for a period not to exceed seven calendar days, without charge to the Government.

C.1.0.4.6 In the case of the Government picking-up a vessel, the Government shall take acceptance of the vessel in the stream adjacent to the contractor’s plant and the contractor shall be responsible for the safe handling and undocking of vessel. If, because of the location of the contractor’s shipyard, the Army picks up the vessel at a site near the facility rather than the stream adjacent to the facility, the contractor shall redeliver the vessel to the alternate site for pickup by the Army. Redelivery of the vessel to the alternate site shall be at no additional cost to the Government.

C.1.0.4.7. Contractor Pick-up and Delivery. The contractor shall pick-up the vessel within seven calendar days of the notice to proceed. The contractor shall provide written notification to the Contracting Officer (CO) by email prior to picking up the vessel.

C.1.0.4.8 The vessel must be delivered back to the Government during normal working hours of the activity.

C.1.0.4.9 Additional pick-up and delivery instructions will be addressed in the Task Order.

C. 1.0.5 Weather: All requirements shall be completed no later than the number of calendar days stated in the Task Order upon commencement of the performance period. Normal weather variations at the Contractor’s plant must be taken into account when scheduling work under this contract/delivery order proposal. An extension of time for foul weather will not be granted unless the Contractor can present documentation substantiating (1) the weather was unusually severe, and (2) the work controlling the overall completion of the contract/delivery order was delayed by the unusually severe weather. Unusually severe weather is defined as weather that is abnormal compared to the past weather at the same location for the same time of year. The Contractor is responsible for presenting area specific weather statistics from the government weather service showing the weather recorded during the performance period was more severe than weather recorded over a five-year preceding period for the plant area.

C.1.0.6 Contractor Travel.

In the event travel is required by a contractor, necessary for the performance of assigned tasks and as approved by the Contracting Officer, the Government will reimburse the Contractor for actual transportation fare via the most direct routes (non-first class) between place of origin and destination. Cost for delays enroute (excluding Government caused delays) will not be reimbursed. Per Diem will be paid in accordance with Joint Travel Regulation (JTR).

C.1.0.7 Specialized Watercraft Information The contractor shall comply with all applicable regulations and standards, to include:

Department of Defense (DoD) regulations, Army Regulations (AR) 56-9, Watercraft, Code of Federal Regulations (CFR) Title 46, Technical Bulletin (TB) 043-144, American Bureau of Shipping (ABS) Rules, and discharge standards.

C.1.1 Environmental Compliance. The contractor shall ensure that all aspects of contract execution in this agreement are in compliance with applicable International, United States Federal, State, interstate and/or local environmental regulations and requirements. Such regulations, conditions, or instructions in effect or prescribed by any International, Federal, State, interstate or local governmental agency are hereby made a condition of this Agreement.

The contractor shall immediately notify the COR if the Government gives any instruction or direction the contractor believes may result in violation of applicable law(s) and/or regulation(s)

C.1.1.1 The Contractor shall submit test reports, IAW CDRL A008, establishing compliance with all Federal, state, and local environmental standards, or standards applicable in the country where the work is performed, pertaining to marine paints, painting processes, and the handling, storing, and disposal of hazardous wastes.

C.1.1.2 Hazardous Materials Management. For the purposes of this contract, hazardous materials shall be defined by FED-STD-313. A Radioactive material is defined as any source material, as defined by Title 10, Code of Federal Regulations, Part 40, “Domestic Licensing of Source Material”, in excess of 0.05 percent by weight. Specific prohibited hazardous materials are identified in the individual Task Order. Prohibited materials requirements shall apply to all components, parts, and materials provided under this contract, including items purchased through a subcontractor or supplier, Commercial off the Shelf (COTS) components, OEM parts, and manufactured parts

C.1.2 Painting: The contractor shall perform all surface preparation, priming and finish painting required in the contract or task order under the contractor's responsibility shall conform in all respects to the detailed instructions contained in Department of the Army Technical Bulletin 43- 0144, dated November 2005, entitled: "Painting of Watercraft" and manufacturer’s application instructions. In the even the TB and manufactures instruction contradict each other the manufacturer’s application instructions take precedence.

C.1.3. Drydocking Facilities: Watercraft (vessels) shall be drydocked without stress or strain by use of graving dock, floating drydock, marine railway, marine-travel lift or synchro-travel lift of sufficient capacity using multiple belly bands for lifting and travel. Use of a crane to drydock any vessel requires prior approval of all certification documentation on the crane prior to conducting the lift, and a vessel specific lift plan, IAW CDRL A009. Permission to lift a vessel by crane shall be granted by written approval from the Contracting Officer.

C. 1.3.1 The contractor shall provide all annual certifications (i.e. drydock certifications, insurance, etc.) in accordance with CDRL A009.

C.1.4. The contractor shall identify, IAW CDRL A002, any omissions from the drawings or specifications or the mis-description of details of work which are manifestly necessary to carry out the intent of the drawings and specifications, or which are customarily performed, shall not relieve the Contractor from performing such omitted or misdescribed details of the work, but shall be performed as if fully and correctly set forth and described in the drawings and specifications.

C.1.5. Protection of Vessel(s): The Contractor is responsible for the protection of the vessel(s) while under tow and in its yard. The Contractor must at all times have the vessel(s) secured and protected from fire, vandalism and theft.

C.1.6 Refueling. Refueling shall be treated as a commodity item. Individual task orders will address any refueling requirements. The fuel shall be reimbursed as “material” at the “actual” cost without any pass through costs, profit, or overhead added. Any associated labor for refueling of the vessel and any associated services required in order to conduct the refueling, i.e. barge services shall be reimbursed as labor.

C.1.7. Parts Standardization: In order to have uniformity within the class of vessels, equipment is sometimes shown as being manufactured by a particular manufacturer, with a set part number or National Stock Number. This specific identification can be in the specifications, the drawings or the vessel technical manuals. There shall not be any substitution for those pieces of equipment unless a Request for Variation (RFV) is submitted to the Contracting Officer IAW CDRL A010 and written approval for the substitution is granted.

C.1.7.1. Replacement parts procured shall conform to the materials listed in referenced drawings. Substitution of any part identified by part number, National Stock Number and/or Manufacturer shall an RFV submitted to the Contracting Officer IAW CDRL A010 and written approval for the substitution is granted. The written request shall include all applicable material information needed to determine whether the requested material meets Army requirements.

Submission for substitution does not constitute approval of the substitution. Permission for substitution of specified parts will be granted in writing by the Contracting Officer.

C.1.8. Subcontract Work on Additional and Extra Items: When work is to be subcontracted, the contractor shall include two or more quotes with its CR, if only one subcontractor is available, the contractor shall provide rationale as to why there is only one subcontractor that can do the work.

C.1.9. Payment and Performance Bonds: When payment and performance bonds are required, the Contractor shall submit them within 10 calendar days after contract award. Failure to provide bonds within 10 calendar days may result in termination for default without a Cure Notice being issued by the Contracting Officer. Proof that a performance and payment bond can be attained, and an estimated cost, shall be required prior to award. Contractors receiving a task order for the first time may be required to submit a performance bond.

C.1.10 Provisioning Performance Schedules:

The contractor shall, within five days after vessel pick up/delivery, prepare and submit to the Contracting Officer for approval an electronic provisioning performance schedule (referred to as schedule) IAW CDRL A001, listing work by individual item, and showing the order in which the contractor proposes to perform the work, and the dates on which the contractor contemplates starting and completing the work (including acquiring the material). All updates shall identify the actual start date of each item, actual completion dates, and clearly identify the impact on all critical path items that impact completion of the project. If the contractor fails to submit a schedule within the time prescribed, the Contracting Officer may withhold approval of progress payments until the contractor submits the required schedule and the Government accepts the schedule. When there are requirements for long lead time parts, the contractor shall include in each production schedule the initial order date, estimated parts delivery date, the earliest induction date, and projected completion dates for work being solicited.

C.1.10.1. The contractor shall keep the Schedule current by making entries to include added or deleted items of work or changes in scheduled dates, and upon doing so shall immediately deliver the updated schedule electronically to the Contracting Officer for approval. An updated Production Schedule shall be provided to the COR and the Contracting Officer a minimum of one update every 15 days. In the event of a significant change in schedule, a revised Schedule shall be submitted to the Contracting Officer within two days, IAW CDRL A001.

C.1.10.2 In the event of schedule delays, the contractor shall immediately notify the COR and the Contracting Officer by e-mail. The contractor shall detail the reasons for the schedule delay, proposed corrective action(s), and submit a revised schedule to the COR and Contracting Officer. The Government reserves the right to review and approve or disapprove any contractor proposed changes that affect the contract and task order schedules. Any request for PoP extension shall be requested in advance of the completion date established in the task order.

Any revisions to the schedule shall show the original start and completion dates, in addition to the amended dates, for each item of the contract.

C.1.11. Deliverables:

C.1.11.1. Condition Found Reports (CRs), supporting documents for CRs, test reports, certifications, load tests and all other documents required during performance of specification items shall be provided in accordance with the CDRLS identified in Section J.

C.1.11.1.1 CRs shall include labor hours required, material prices, and material availability and estimated freight charges. CRs will not be considered for additional action by the Contracting Officer unless all required information is included. All supporting subcontractor or vendor information shall be provided with the applicable CR.

C.1.11.2 Required certifications such as fire suppressions systems, potable water tanks, load tests, pull tests, quinquennial inspections shall be provided as an original copy with ink signature in accordance with CDRL A008.

C.1.11.3. Upon completion of all work in the contract, and prior to final invoicing, a complete copy of all Test and Inspection shall be submitted IAW CDRL A005.

C.1.11.4. A Request for Variance (RFV) is the mechanism used to document and request approval for a lack of compliance with a vessel’s approved technical drawings and/or technical manuals. The contractor shall not deviate from the provided TDP or any other baseline documentation without approval. By submitting an RFV IAW CDRL A010 the contractor may request to temporarily depart from a requirement specified in the TDP or any other baseline documentation. Approval or rejection for Alterations defined in this section may be granted within three business days of submitting an RFV unless otherwise specified per CDRL A010.

C.1.11.4.1. RFVs (shall contain marked up or redlined copies of affected drawings, clearly showing the temporary departure, and shall include supporting data necessary to fully understand the proposed variance, and when applicable, the shipyard CR and invoice with omitted cost information. The contractor shall not present any production items for acceptance with any nonconformance to the requirements in the TDP or other baseline documentation until notified by the Government that the RFV has been approved and incorporated into the contract.

C.2. WARRANTIES AND REPAIRS

C.2.1. Pass-through warranty. The contractor shall pass through all warranties on any purchased equipment installed or delivered under a task order. The contractor shall maintain documentation of all warranties.

C.2.1.1. The contractor shall maintain a warranty file on all equipment installed under each task order. The warranty file shall include all documentation of warranties on any equipment delivered or installed under the task order. The contractor shall maintain documentation of communications with vendors, manufacturers or other contractor’s pertinent to specific warranties and shall include all such documentation in the warranty file. The documentation shall be fully completed so that it can be used as a valid reference for the PCO’s use, i.e. date and time; person initiating, person called; nature of the problem; and the contractor’s response and resolutions. The contractor shall deliver the warranty file upon completion of the task order in accordance with CDRL A006.

C.2.1.2. Workmanship warranty. The contractor shall warrant all work performed under each task orders for no less than 90 days from the end of the task order PoP. Any failure of repaired or modified equipment occurring due to workmanship of the contractor during the warranty period shall be repaired or replaced at the contractor’s expense. Additionally, equipment improperly installed by the contractor that fails within a manufacturer’s warranty period due to poor workmanship or failure to follow manufacturer’s installation or operating instructions shall be repaired or replaced at the contractor’s expense. This determination shall be made by the PCO. The contractor shall report any difficulty in exercising manufacturer’s warranty to the COR and PCO.

C.2.1.2.1. Rebuilds of major subsystems such as, but not limited to, engines, generators, bow thrusters, reduction gears, pump sets, shall include a letter on company letterhead provided by the rebuild facility specifically stating warranty start date, the time interval, operating hours, limiting factors and maintenance/lubricant requirements necessary for warranty compliance. The contractor shall provide a combined warranty letter including all prime or subcontractor component rebuild and supplied warranty cards to the Contracting Officer no later than five working days after completion of sea/river trials. This warranty letter can extend, but cannot shorten, the 90 day period noted in DFARS 252.217-7013, Guarantees.

C. 2.1.3 Additional warranties. Task orders may require additional warranties for specific work.

Such warranty requirements will be detailed in the applicable task order.

C.3. Data Plate Information:

The contractor shall collect data plate information on all parts installed during performance of the contracted repairs.

C.3.1. The data plate information provided shall consist of part number, model number, serial number, size, performance rating and other relevant information on the manufacturer’s data plates.

C.3.2. Data plate information shall be provided in the form of a CR to include sequential identification number and submitted in accordance with CDRL A001 not later than two (2) working days after the vessel is delivered to the Army.

C.4. Security Guidelines.

There are types of information that are not classified but that require application of access and distribution controls and protective measures for a variety of reasons. This information is known as controlled unclassified information (CUI). The types of information considered CUI for the program are information marked For Official Use Only by the U.S. Government and technical data. When handling CUI material, all personnel are to comply with these requirements and follow their company policy and/or applicable Proprietary Information Agreements (PIA) concerning the protection of proprietary information in situations not clearly stated herein.

C.4.1. Technical Data Description. Any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process, or can be used to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The data may be graphic or pictorial delineations in media (e.g., computer software, drawings, or photographs), text in specifications, related performance or design documents, or computer printouts. Examples of technical data include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation.

C.4.2. For Official Use Only (FOUO) Information Description. For Official Use Only (FOUO) is a Government designation applied to unclassified information that may be exempt from mandatory release to the public under the Freedom of Information Act (FOIA). FOUO information includes information identified as such in the Security Classification Guide or information from a government document marked FOUO.

C.4.3. CUI Markings. The "Unclassified//For Official Use Only" (U//FOUO) marking is assigned to information at the time of its creation in a DoD User Agency. It is not authorized as a substitute for a security classification marking but is used on official government information that may be withheld from the public under exemptions 2 through 9 of the Freedom of Information Act (FOIA). The marking of records at the time of their creation provides notice of U//FOUO content. An unclassified document containing U//FOUO information shall be marked UNCLASSIFIED//FOR OFFICIAL USE ONLY in bold letters at the bottom on the outside of the front cover (if any), on each page containing U//FOUO information, and on the outside of the back cover (if any). Marking of FOUO documents will be in accordance with Army Regulation (AR) 25-55. Information extracted from an FOUO document will carry the FOUO marking until formally reviewed by the government. AR 25-55 can be found at http://www.apd.army.mil/pdffiles/r25_55.pdf.

C.4.4. Marking of Technical Data will include the statement provided in the Security Classification Guide. If the contents of the technical document require more than one Distribution Statement, apply the most restrictive statement. This does not preclude additional mandated markings as may be required by the contract.

C.5. Protection of CUI Information.

C.5.1. Access. CUI may be released only to an individual who has a valid need for such access in connection with the accomplishment of a lawful and authorized Government purpose.

Information in any media format may only be disseminated on a need-to-know basis. The need-to-know restricts the use or dissemination of CUI data to those individuals or organizations with direct affiliation with the given program or project. Further dissemination of such information will be at the discretion of the Government Security Manager. Personnel no longer requiring access to CUI must delete or surrender any in their possession and terminate future access to it.

C.5.2. Storing/Handling. During working hours, take reasonable steps to minimize risk of access to CUI by unauthorized personnel. After working hours, when not in physical possession of the owner, all CUI (whether hardcopy or media that contains CUI) must be afforded a reasonable degree of physical protection to prevent theft of program information (e.g., store CUI information in locked desks or file cabinets, locked rooms, cable lock laptops, storing in a trunk, storing out of site or similar means). Do not display CUI in public places (e.g., airports, airplanes, restaurants). Computers used to process CUI do not need to be accredited for classified use, but shall be in accordance with DFARS 252.204-7012 Safeguarding of Unclassified Controlled Technical Information. Do not process CUI on public computers (e.g., those available for use by http://www.apd.army.mil/pdffiles/r25_55.pdf the general public in kiosks, hotel business centers), public wireless networks or computers that do not have access control. Personally owned computers and personally owned devices are not authorized to process CUI. Mobile devices used to store CUI electronically (e.g., company-issued laptops, personal electronic devices [PED]) must be physically protected and use NIST/NIAP-approved cryptographic products/algorithms. These are available at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/cryptval/. All media shall be marked in accordance with the Security Classification Guide and protected as below:

C.5.2.1. Portable electronic devices (e.g., smartphones, laptop computers, tablets) and removable media (e.g., external hard drives, flash drives, USB drives; not including optical media) must be physically and electronically protected as described in this instruction.

C.5.2.2. Optical media (e.g., DVDs, CDs) and non-portable computers (e.g., desktop or tower computers) are required to be physically protected; however, they are not required to be electronically protected as described in this instruction.

C.5.3. Dissemination. CUI printed documents and material may be transmitted through mail channels or hand-carried without formal courier orders. FOUO information may be disseminated to DoD personnel and DoD contractors to conduct official business for the program. If dissemination is required outside of DoD personnel or DoD contractors, contact the Government Security Manager for approval. Technical data will follow the release instructions identified in the Distribution Statement. Use secure communications whenever possible; however, land-line telephones are more secure than cellular telephones and should be used whenever available for discussions involving CUI. Transmit voice and facsimile transmissions only when you have a reasonable assurance that only authorized recipients will have access to the transmission.

Transmittal documents shall call attention to the presence of U//FOUO attachments. Removal of the U//FOUO marking can only be accomplished by the originator or other competent authority.

Digital transmission shall comply with the below:

C.5.3.1. Transporting/Sending U//FOUO Information Via Mail. Records containing U//FOUO information shall be transported in a manner that precludes disclosure of the contents. When not commingled with classified information, U//FOUO information may be sent via first class mail or parcel post. Bulky shipments, such as distributions of U//FOUO Directives or testing materials, that otherwise qualify under postal regulations may be sent by fourth-class mail.

When material marked U//FOUO is removed from storage, attach DA Label 87 (For Official Use Only Cover Sheet).

C.5.3.2. Electronic Transmission and Dissemination. All transmission and/or dissemination of CUI (i.e., email and file transfers) must use NIST/NIAP-approved cryptographic products/algorithms, e.g., DoD-approved Public Key Infrastructure Certification or AMRDEC Safe Exchange at https://safe.amrdec.army.mil/safe. These are available at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/cryptval/.

This encryption requirement includes communications that contain passcodes to teleconferences or web conferences where there is a reasonable expectation that CUI may be discussed. When encryption is not available, a government collaborative suite (aka Integrated Digital Environment [IDE]) must be used to transmit CUI.

C.5.3.3. Contractor-hosted collaborative suites may be used for digital transmission and/or dissemination of CUI by personnel not located on a government backbone (e.g., NIPRNET), provided the following conditions apply:

http://csrc.nist.gov/cryptval/

C.5.3.3.1. Use only NIST/NIAP-approved cryptographic vendors and algorithms. The latest validation lists may be obtained at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/cryptval/.

C.5.3.3.2 Use an internally hosted service that does not use a third-party collaborative suite service provider.

C.5.3.4. Do not post CUI to web pages that are publicly available or have access limited only by domain/IP restrictions. As permitted by other contract provisions, CUI may be posted to web pages that control access through the use of a DoD approved Public Key Infrastructure Certification and that provide protection via use of secure sockets, or other equivalent technologies. These are available at http://iase.disa.mil/pki/eca.

C.5.3.5. As new technologies become available in the electronics arena, care should be given to providing a reasonable degree of protection from known vulnerabilities.

C.5.3.6. The Internet is Public Access. CUI must be reviewed and officially approved by the PEO CS&CSS Public Affairs Officer for public release before placing on the Internet. This is not applicable when the Internet is used for e-mail transmissions and encryption is used as noted above.

C.5.3.7. Disposal. Destroy CUI documents by any means approved for the destruction of classified information, i.e. cross-cut shredding or other means that would make it difficult to recognize or reconstruct the information. Clear, purge, or destroy CUI on removable media IAW BBP 03-PE-O-0003 Army Information Assurance Sanitization of Media to AR 25-2. This is available at https://informationassurance.us.army.mil.

C.5.3.8. Report of Loss of CUI. Report any loss of CUI or loss of CUI from a contractor information system that is known to the contractor within the period of performance of work on this contract and for any period of time after contract performance to the Government Security Manager. Initial reports shall be made as expeditiously as possible in all cases within 72 hours of discovery. If additional information is required after submission and review of the initial report, guidance will be provided at that time. Mark any reports For Official Use Only, exemptions 2 and 5 apply. Initial report content shall include the following information as available.

C.5.3.8.1. Applicable dates, including dates of compromise and dates of discovery.

C.5.3.8.2. Threat methodology, including all known resources used (e.g. IP addresses, domain names, software tools).

C.5.3.8.3. Account of what actions the threat(s) may have taken on victim system/network.

C.5.3.8.4. What information may have been compromised, exfiltrated, or lost, and its potential impact on government programs.

C.5.3.8.5. Report of Cyber Intrusions. Report cyber intrusions or other compromises of CUI to your supporting counterintelligence office, which will inform the DoD-DIB Common Information Sharing Environment (DCISE). Notify the Government Security Manager of any incidents as well. Refer to Report of Loss of CUI for what needs to be reported, when, and how.

C.5.4. OPSEC Guidelines.

http://csrc.nist.gov/cryptval/ http://iase.disa.mil/pki/eca

If the contractor generates unclassified Operations Security (OPSEC) sensitive information, this information shall be protected at the same level as FOUO information. OPSEC sensitive information may be disseminated within the contractor's internal computer network if it is protected with a firewall and individual access is controlled by using IDs and passwords. (Under no circumstances can classified information be transmitted over an unclassified network).

C.5.4.1. The contactor may disseminate FOR OFFICIAL USE ONLY (FOUO) information to its employees who have a need to know for the information in connection with the purchase order.

C.5.4.2. All FOUO material shall be destroyed by tearing or shredding to make unreadable.

Electronic media will be purged with approved software or destroyed through a physical process.

C.5.4.3. Because of antiterrorism/force protection, operations security, and counterintelligence concerns the contractor shall not release any diagrams, maps, floor plans, schematics, or digital pictures of the installation to outside organizations or companies without the approval of the COR and G2, TACOM. All information proposed for public release in any form (video, pictures, article, brochure, web site, etc.) will undergo a HQ TACOM OPSEC Review using STA Form 7114-E.

C.5.4.4. Examples of information that would be considered OPSEC sensitive:

- Equipment capabilities, limitations, and vulnerabilities.

- Detailed mission statements.

- Operation schedules.

- Readiness and vulnerability assessments.

- Test locations and dates.

- Inventory charts and reports.

- Detailed budget data.

- Photographs of components.

- Detailed organizational charts (with phones and e-mail listings).

- Technical and scientific data.

- Unclassified technical data with military applications.

- Critical maintenance information.

- Information extracted from a DOD Intranet web site.

- Lessons learned that could reveal sensitive military operations, exercises, or vulnerabilities.

- Logistics support (munitions, weapons, movement).

- Specific real time support to current or on-going military operations.

- Delivery schedules

- Manufacturing methods.

C.5.5. Distribution Statements.

C.5.5.1. The contractor shall follow the applicable Department of Defense (DoD) Technical Distribution Statement and Export Control Warning per DoD Instruction D5230.24 to all technical data delivered and in accordance with Security Classification Guide (SCG).

Preliminary determination for survivability data is Export Controlled with Distribution Statement C or D (when applicable).

C.5.5.2. DISTRIBUTION STATEMENT C: DISTRIBUTION AUTHORIZED TO U.S.

GOVERNMENT AGENCIES AND THEIR CONTRACTORS. REASON: EXPORT

CONTROLLED. DATE OF DETERMINATION: 10-10-2014. OTHER REQUESTS FOR THIS

DOCUMENT SHALL BE REFERRED TO THE TACOM LCMC. ARMY WATERCRAFT

PRODUCT OFFICE, ATTN: SFAE-CSS-TS-W, WARREN, MICHIGAN 48397-5000. 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 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

C.5.6. Security Classification Guide.

Post award the contractor must adhere to the respective Army Watercraft Systems Interim Security Classification Guide (SCG), dated 23 February 2015, when creating, developing, testing, producing, and/or disseminating any material which could contain U//FOUO and/or classified information.

C.6. Meetings/Reviews/Reporting.

C.6.1 The contractor shall participate in all planning/implementation meetings (consisting of IPT and working group meetings). In general, the IPT meetings will take place every two weeks in accordance with CDRL A003

C.6.1.1. Agendas. The contractor shall submit an agenda for all meetings and reviews IAW CDRL A007. Agenda shall include discussions on contract progress and issues (e.g.

performance goals, schedule progress, risks and mitigation, and cost impact).

C.6.1.2. Minutes. Following the Start of each meeting, the contractor shall provide meeting minutes within two calendar days in accordance with CDRL A003.

C.6.2. Start of Work Meeting (SOWM). SOWM shall take place within 30 days after contract award. The purpose of this meeting is to introduce and align the Government and contractor teams, review the Performance Work Statement (PWS), and address any questions or issues.

The meeting is anticipated to be a two day event.

C.6.2.1. The SOWM will be held at contractor's location and will not exceed two days. The contractor shall present its approach to manage and develop engineering and logistics products and services to include a detailed IMS with all logistics, engineering and test events. The SOWM will focus on reviewing the following.

a. Contract terms and conditions

b. Data requirements

c. Required specifications

d. Test requirements and schedules

e. Program Schedule to include all data deliverables

C.6.2.1.1. The contractor shall and Government will identify the personnel assigned to key roles at the SOWM. The key roles are as follows: Program Manager, Procurement, Quality, OPSEC, and Test.

C.6.3.2. Contractor Manpower Reporting (CMR). The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via secure data collection site.

The contractor is required to completely fill in all required data fields in the format using the following web address: https://cmra.army.mil.

The required information includes the following:

(1) Contracting Office, PCO, Contracting Officer's Technical Representative;

(2) Contract number, including task and delivery order number;

(3) Beginning and ending dates covered by reporting period;

(4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data;

(5) Direct labor hours (including sub-contractors);

(6) Direct labor dollars paid this reporting period (including sub-contractors);

(7) Total payments (including sub-contractors);

(8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each subcontractor if different);

(9) Data collection cost;

(10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

(11) Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

(12) Presence of deployment or contingency contract language; and

(13) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country).

C.6.3.2.1. 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, beginning with 2016. Contractors may direct questions to the help desk at: https://cmra.army.mil.

C.7. Over and Above Requirements

C.7.1. During performance of this Contract, it is expected that issues may be identified during the course of performing maintenance and repair efforts, that are in the general scope of the Contract, but that were not specifically included in the original Contract scope of work. When directed by the Government, and when funding is made available by the Contract modification, the contractor shall provide these services on an expedited basis. All requirements authorized under this provision shall be provided by the contractor in accordance with DFARS 252.217- 7028 and this scope of work. Pursuant to DFARS 252.217-7028, the Government may modify these procedures as appropriate.

C.7.1.1 When requested by the Government, or when a need is identified by the contractor, the contractor shall submit a CR, in contractor format, to the PCO and the COR.

At a minimum, the request shall include the following:

a. A description of the work to be performed;

b. Identification of the proposed repair procedure;

c. Replacement parts required (excludes GFP) for pricing purposes only;

https://cmra.army.mil/

d. Estimated labor hours and/or material costs; and

e. An assessment certifying the vessel or component will meet the applicable specification following the work to be performed.

The contractor shall also submit all supporting documentation along with the CR. Before work can begin, it must be authorized by the PCO and availability of funds must be verified.

C.7.1.2 The PCO will

a. Verify the necessity of the work;

b. Verify the conformance of the contractors proposed method of modification or repair and approved modification or repair procedures;

c. Verify whether the contractors proposed designation and identification of the work as

Over & Above is valid;

d. Determine whether an item will be repaired or replaced.

Normally an item will be replaced if the repair price is equal to or exceeds 65 percent of the replacement price;

e. Shall consider procurement lead time versus repair time in all repair or replace determinations; and

f. Agree to the estimated hours and/or estimated material costs.

C.7.1.3 As applicable under paragraph C.8.1.1 above, the PCO will notify the contractor within three (3) working days regarding whether the CR is authorized. Once such notification is received, funds will be requested and a Contract modification executed by the PCO. If the Contract modification is not executed within five (5) working days after notification of work request authorization, the contractor has no obligation to perform the work until such time as a properly executed modification has been completed. Upon receipt of the modification, the contractor may bill against the funded CLIN.

C.7.2 It is understood and agreed to by both parties that the Government is not under any Contractual obligation for the duration of the Contract to acquire any specific quantity or services covered by the clause and no liability shall be incurred by the contractor or the Government in the event that no acquisitions are made.

C.7.3 The contractor shall maintain records, available for Government review, of the funds committed, expended, and disbursed under the clause for each requisition.