Document:

exv10w1

Exhibit 10.1

Confidential Materials omitted and filed separately with the

Securities and Exchange Commission. Asterisks denote omissions.

 

 

Section B — Supplies or Services and Prices

	 	 	 	 	 	 	 	 	 	 	 
	 	 	 	 	UNIT	 	 	 	 	 
	 	 	 	 	Dollars,	 	 	 	 	 
	ITEM NO	 	SUPPLIES/SERVICES QUANTITY	 	U.S.	 	UNIT PRICE	 	AMOUNT	 
	0001
	 	 	 	 	 	 	 	$	2,449,835.99	 
	 
	 	 	 	 	 	 	 	 	 	 
	 	 	Cost & Fixed Fee Base Year	 	 	 	 
	 	 	CPFF	 	 	 	 
	 	 	Base Year Cost and Fixed Fee for the Littoral Expeditionary Autonomous	 	 	 	 
	 	 	PowerBuoy (LEAP) System.	 	 	 	 
	 
	 	 	 	 	 	 	 	 	 	 
	 	 	In accordane with Statement of Work LEAP Buoy 1DIQ Contract Task Order 1	 	 	 	 
	 
	 	 	 	 	 	 	 	 	 	 
	 	 	FOB: Destination	 	 	 	 
	 	 	PURCHASE REQUEST NUMBER: 91521426	 	 	 	 
	 
	 	 	 	 	 	 	 	 	 	 
	 	 	ESTIMATED COST	 	$	2,268,366.66	 
	 	 	FIXED FEE	 	$	181,469.33	 
	 
	 	 	 	 	 	 	 	 	 
	 	 	TOTAL EST COST + FEE	 	$	2,449,835.99	 
	 
	 	 	ACRN AA	 	$	2,449,835.99	 
	 	 	CIN: 915214260001	 	 	 	 

	 	 	 	 	 	 	 	 	 	 	 
	 	 	 	 	UNIT	 	 	 	AMOUNT	 
	ITEM NO	 	SUPPLIES/SERVICES QUANTITY	 	Group	 	UNIT PRICE	 	NSP	 
	0002
	 	 	 	 	 	 	 	 	 	 
	 	 	Contract Data Requirements List	 	 	 	 
	 	 	CPFF	 	 	 	 
	 
	 	 	 	 	 	 	 	 	 	 
	 	 	CDRL A0001 in accordance with the Statement of Work Section
5.1 on basic contract for Contractors Progress, Status and
Management Report. Delivery dates: 15th day of the month for
work performed in the previous month. Deliveries shall go to
the Contracting Officer’s Representative. Craig Bleile at
craig.bleile@navy.mil. Referenced in Section J.	 	 	 	 
	 
	 	FOB: Destination	 	 	 	 	 	 	 	 
	 
	 	 	 	 	 	 	 	 	 	 
	 
	 	ESTIMATED COST	 	$	0.00	 
	 
	 	FIXED FEE	 	$	0.00	 
	 
	 	 	 	 	 	 	 	 	 
	 
	 	TOTAL EST COST + FEE	 	$	0.00	 

 

 

Section C — Descriptions and Specifications

STATEMENT OF WORK

Littoral Expeditionary Autonomous Power (LEAP) Buoy

IDIQ Contract Task Order 1

Statement of Work

Prepared For:

Ocean Power Technologies Inc. (OPT)

1590 Reed Road

Pennington. NJ 08534

Prepared By:

NIJWC Division, Keyport

 

TABLE OF CONTENTS

	 	 	 	 	 
	1.0 Introduction

	 	 	5	 
	1.1 Background

	 	 	5	 
	1.2 Program Overview

	 	 	6	 
	1.3 Scope

	 	 	6	 
	2.0 SYSTEM REQUIREMENTS

	 	 	8	 
	2.1 System Functional Requirements

	 	 	8	 
	2.2 Subsystem Requirements

	 	 	8	 
	2.3 Environmental Requirements

	 	 	8	 
	3.0 STATEMENT OF WORK

	 	 	9	 
	3.1 Task 1: LEAP VDST Requirements Analysis and Definition

	 	 	9	 
	3.2 Task 2: Systems Engineering Planning

	 	 	9	 
	3.3 Task 3: Design LEAP VDST Subsystems

	 	 	9	 
	3.3.1 Design PowerBuoy Power Take-Off (PTO) Subsystem

	 	 	9	 
	3.3.2 Configure FIE Radar System

	 	 	10	 
	3.3.3 Design Vessel Detection Processor

	 	 	10	 
	3.3.4 Design [**] Network Interface Processor

	 	 	10	 
	3.3.5 Configure [**] System

	 	 	10	 
	3.4 Task 4: Build and Test Prototype Subsystems

	 	 	10	 
	3.4.1 Build and Test PowerBuoy PTO Subsystem

	 	 	10	 
	3.4.2 Build and Test HF Radar System

	 	 	10	 
	3.4.3 Build and Test Vessel Detection Processor

	 	 	11	 
	3.4.4 Configure and Test [**] Network Interface Processor

	 	 	11	 
	3.4.5 Configure and Test [**] System

	 	 	11	 
	3.5 Task 5: Preliminary Subsystem Testing

	 	 	11	 
	      3.6 Task 6: Test Data Reduction and Analysis

	 	 	11	 
	3.7 Task 7: Real-Time System Transition Studies

	 	 	11	 
	3.8 Task 8: Follow-on Work

	 	 	12	 
	3.9 Task 9: Program Management

	 	 	12	 
	4.0 DELIVERABLES

	 	 	13	 
	4.1 Documentation

	 	 	13	 
	5.0 Government Furnished Items

	 	 	14	 
	5.1 Government Furnished Information (GFI).

	 	 	14	 
	5.2 Return of Government Furnished Items.

	 	 	14	 
	6.0 Deliverables

	 	 	15	 
	7.0 Special Conditions

	 	 	16	 
	7.1 SB1R Phase 111

	 	 	16	 
	7.2 SBIR Data Rights

	 	 	16	 
	7.3 Packaging and Marking

	 	 	16	 

4

 

1.0 Introduction

     1.1 Background

The Littoral Expeditionary Autonomous Power Buoy (LEAP) System is established to enhance the Navy’s
Anti-Terrorism/Force Protection (ATIFP) by providing persistent afloat and port maritime
surveillance in the near coast, harbors, piers and littorals worldwide. Waterborne threats, both
domestic and overseas, that include boats, swimmers, mini-subs, autonomous vehicles, and highly
lethal submerged mines form a substantial window of vulnerability for naval and civilian assets. A
viable system for protecting critical infrastructure and military assets from surprise maritime
terrorist attacks must include a system that detects and locates surface and subsurface threats.
There is a need for persistent and dependable, long-term operation of a surveillance network to
provide operational surface vessel tracking capabilities to prevent attacks from small, high-speed
vessels. This effort is intended to provide capabilities that bring persistent power at sea to
provide power to forward deployed sensors and communications equipment that can detect, track and
communicate target information in sufficient time in order to provide decision making capability
and operational execution against such threats.

[**]

     1.2 Program Overview

The LEAP Program objective is to leverage a combination of existing technologies which includes a
wave energy conversion buoy, sensors and communications systems to improve force protection by
combining their features and capabilities into a single system. The systems integration shall be
achieved through the use of the [**] for integrating with sub-systems and to create a flexible and
net-centric architecture that can be distributed across multiple nodes and present a unified
Common Operating Picture (COP) to the operators.

The LEAP Program is based on the Ocean Power Technologies (OPT) PowerBuoy® wave energy conversion
system, which is an enabling technology for providing power to remote. at-sea sensors and
communications technologies. The operational experience and user inputs gained from ocean
demonstrations shall indicate those features to be implemented to increase the capability in the
near term and provide the cornerstone for further technological enhancements.

     1.3 Scope

The scope of this Task Order 1 Statement of Work covers tasks to be performed during Year 1 (the
Base Year) of a proposed four-year program to develop a LEAP-based Vessel Detection System Testbed
(VDST). The VDST shall be deployed off the Atlantic coast of New Jersey and used to develop and
test hardware and software technology for real-time detection of vessels in its littoral coverage
area.

5

 

The VDST system architecture shall be based on:

	 	•	 	OPT’s PowerBuoy Wave Energy Conversion (WEC) technology, which provides a
persistent at-sea buoy platform for HE radar transmitters
	 
	 	•	 	COTS multistatic HF radar equipment developed by [**], including at-sea transmitters
and shore-based radar transceivers
	 
	 	•	 	The existing Rutgers Coastal Ocean Observatory Laboratory (COOL) facility
	 
	 	•	 	New radar signal processing and vessel detection algorithms to be developed by Rutgers
Institute of Marine And Coastal Sciences, [**]
	 
	 	•	 	[**] which provides a Common Operating Picture to the user.

6

 

Major tasks currently planned for this Task Order in the Base Year of the contract are:

	 	•	 	Development and laboratory testing of the PowerBuoy Power Take-off (PTO) subsystem

	 
	 	•	 	Deployment of first VDST shore station and HF radar transceiver
	 
	 	•	 	Development and testing of radar signal processing and non-real-time vessel
detection algorithms based [**], using VDST shore station in conjunction with an
existing radar shore site
	 
	 	•	 	Initial investigations of [**] and signal processing algorithms

7

 

2.0 SYSTEM REQUIREMENTS

     2.1 System Functional Requirements

The LEAP Vessel Detection System shall:

	 	•	 	Detect small surface vessels within its coverage area
	 
	 	•	 	Provide vessel detection reports to the [**] using standard communications protocols
and message formats
	 
	 	•	 	Meet applicable environmental requirements
	 
	 	•	 	Support extended deployment lifetimes and 24/7 operation
	 
	 	•	 	Be scalable to large coverage areas.

     2.2 Subsystem Requirements

Detailed requirements for each major LEAP VDST subsystem shall be developed under Task 1,
Requirements Analysis and Definition. Subsystem requirements shall be documented in deliverable
reports as defined in Institute of Electrical & Electronics Engineers, Inc. (IEEE) Standard 1220
processes, such as System Requirements Specifications (SRS) and Interface Control Documents
(ICD).

     2.3 Environmental Requirements

Environmental requirements shall be defined separately for at-sea and onshore subsystems.

8

 

N00253-09-D-0005

0001

Page 9 of 21

3.0 STATEMENT OF WORK

     3.1 Task 1: LEAP VDST Requirements Analysis and Definition

	 	•	 	Define detailed system requirements

	 	•	 	Vessel detection parameters and probabilities
	 
	 	•	 	Detailed environmental requirements
	 
	 	•	 	Shore station infrastructure
	 
	 	•	 	Deployment and recovery infrastructure
	 
	 	•	 	Communications network infrastructure
	 
	 	•	 	Extended lifetime and deployment area considerations
	 
	 	•	 	Integration with [**] and other Navy/Coast Guard (CG) systems

	 	•	 	Define detailed program objectives and test requirements

	 	•	 	Develop phased VDST implementation plan
	 
	 	•	 	Develop detailed test plans
	 
	 	•	 	Define post-processing data analysis and management methods
	 
	 	•	 	Establish performance objectives

     3.2 Task 2: Systems Engineering Planning

The contractor shall use a formal process development methodology to plan and control all aspects
of system development. The methodology used shall be tailored from the requirements of IEEE Std
1220-2005. The contractor team shall develop a System Engineering Management Plan in accordance
with IEEE 1220 including:

	 	•	 	Interface definitions
	 
	 	•	 	Subsystem functional requirements
	 
	 	•	 	Hardware/Software (NW/SW) tradeoffs
	 
	 	•	 	Commercial Off The Shelf (COTS) vs. custom design
	 
	 	•	 	Applicability of existing equipment/facilities
	 
	 	•	 	Real-time system and transition requirements
	 
	 	•	 	Requirements documents

     3.3 Task 3: Design LEAP VDST Subsystems

The contractor shall investigate technical trade-offs. conduct laboratory investigations and
develop detailed hardware/software designs for each subsystem, as follows. Design documents shall
be developed in standard and contractor formats.

          3.3.1 Design PowerBuoy Power Take-Off (PTO) Subsystem

	 	•	 	Develop PTO requirements specification
	 
	 	•	 	Develop PTO subsystem design specifications
	 
	 	•	 	Conduct PTO conceptual design and trade-offs
	 
	 	•	 	Develop detailed H W/SW designs
	 
	 	•	 	Develop manufacturing drawings

 

 

N00253-09-D-0005

0001

Page 10 of 21

	 	•	 	Conduct design reviews 3.3.2

          Configure HF Radar System

	 	•	 	Procure COTS [**] (1 unit), to be deployed at first VDST shore station. This consists of radar transmitter, receiver and radar signal processor.
	 
	 	•	 	Procure and install COTS [**] (1 unit)
	 
	 	•	 	Identify potential locations for radar systems
	 
	 	•	 	Procure and install COTS [**] Software Package [**] (1 unit), to be deployed at first VDST shore station
	 
	 	•	 	Procure COTS [**] (1 unit), to be deployed on PowerBuoy platform

          3.3.3 Design Vessel Detection Processor

	 	•	 	Define and optimize threshold levels for vessel detection
	 
	 	•	 	Define and optimize background noise levels for vessel detection
	 
	 	•	 	Define and optimize integration times for vessel detection

          3.3.4 Design [**] Network Interface Processor

	 	•	 	Define host and network requirements
	 
	 	•	 	Define LEAP VDST interface
	 
	 	•	 	Define [**] protocol and network interfaces
	 
	 	•	 	Evaluate Government Furnished (GFI) Software used in [**] and CG systems
	 
	 	•	 	Design [**] message processing SW
	 
	 	•	 	Design [**] network protocol/interface processing SW

          3.3.5 Configure [**] System

	 	•	 	Configure [**] system for LEAP testing using COTS I-IW and GFI SW

     3.4 Task 4: Build and Test Prototype Subsystems

          3.4.1 Build and Test PowerBuoy PTO Subsystem

	 	•	 	PTO manufacturing and procurement
	 
	 	•	 	Perform acceptance testing of PTO components
	 
	 	•	 	Perform preliminary PTO system integration
	 
	 	•	 	Conduct PTO laboratory testing and measure power generation capacity
	 
	 	•	 	Perform redesign/rework as needed

          3.4.2 Build and Test HF Radar System

	 	•	 	Install and calibrate first High Frequency (HF) radar system at shore station
	 
	 	•	 	Configure and integrate [**] transmitter electronics

 

 

N00253-09-D-0005

0001

Page 11 of 21

          3.4.3 Build and Test Vessel Detection Processor

	 	•	 	Test and analyze performance of vessel detection processor, based on bistatic operation using first VDST shore station
and existing Rutgers shore site
	 
	 	•	 	Examine environmental conditions (sea state, radio interference, external noise) impacting performance of VDST
	 
	 	•	 	Plan development for real time VDST

          3.4.4 Configure and Test [**] Network Interface Processor

	 	•	 	Configure standard Wintel host and network interfaces
	 
	 	•	 	Develop and test LEAP VDST interface
	 
	 	•	 	Develop and test [**] protocol and network interfaces
	 
	 	•	 	Integrate GFI SW as needed
	 
	 	•	 	Develop and test [**] message processing SW
	 
	 	•	 	Develop and test [**] network protocol/interface processing SW
	 
	 	•	 	Software integration and standalone testing

          3.4.5 Configure and Test [**] System

	 	•	 	Procure COTS HW (Wintel, Sun server for Common Joint Mapping Tool Kit)
	 
	 	•	 	Install GFI [**] SW
	 
	 	•	 	Preliminary SW testing and familiarization

     3.5 Task 5: Preliminary Subsystem Testing

	 	•	 	Radar/VDST integration testing
	 
	 	•	 	VDST/[**] integration testing
	 
	 	•	 	[**] integration testing
	 
	 	•	 	VDST/[**] integration testing

     3.6 Task 6: Test Data Reduction anti Analysis

	 	•	 	Correlation of VDST results with known shipping traffic
	 
	 	•	 	Correlation of VDST results with known ambient wave climate
	 
	 	•	 	VDST performance analysis including detection and false alarm probabilities and dependence on ambient wave/wind climates
	 
	 	•	 	Identify and resolve anomalies

     3.7 Task 7: Real-Time System Transition Studies

	 	•	 	Develop real-time vessel detection system architecture
	 
	 	•	 	Investigate technical trade-offs in conversion from offline to real-time signal processing and vessel detection
algorithms
	 
	 	•	 	Investigate signal processing partitioning between VDST and [**] trackers and data fusion framework
	 
	 	•	 	Plan phased implementation of real-time system

 

 

N00253-09-D-0005

0001

Page 12 of 21

     3.8 Task 8: Follow-on Work

	 	•	 	Develop recommendations for follow-on work
	 
	 	•	 	Identify key performance drivers and operational improvements
	 
	 	•	 	Identify production transition issues and risk mitigation strategies

     3.9 Task 9: Program Management

The contractor shall designate a project manager who shall be responsible for the control and
coordination of all work performed on this delivery order. The contractor shall provide the project
manager’s name, in writing, to the PCO within 7 days after issuance of delivery order.The
contractor PM shall establish and maintain a program plan, schedules, budgets, work
assignments/allocations, and delivery plans.

 

 

N00253-09-D-0005

0001

Page 13 of 21

4.0 DELIVERABLES

     4.1 Documentation

Documentation deliverables are shown in Table 1. These deliverables may be revised as necessary in
accordance with the IEEE Std 1220 process development methodology to be used in the proposed
program.

	 	 	 	 	 
	B001

	 	System Specification
	 	One time
	 
	 	 	 	 
	B002

	 	System Interface Specification
	 	One time
	 
	 	 	 	 
	B003

	 	Subsystem Specification
	 	One per subsystem
	 
	 	 	 	 
	B004

	 	Subsystem Interface Specifications
	 	One per subsystem
	 
	 	 	 	 
	B005

	 	Subsystem Integration Test Plan
	 	One time
	 
	 	 	 	 
	B006

	 	System Test Plan
	 	One time
	 
	 	 	 	 
	B007

	 	System Test Results
	 	One time
	 
	 	 	 	 
	B008

	 	Program Status Report
	 	bimonthly
	 
	 	 	 	 
	B009

	 	Final Technical Report for Task Order I
	 	One time

Table 1: Deliverable Documentation

 

 

N00253-09-D-0005

0001

Page 14 of 21

5.0 Government Furnished Items

     5.1 Government Furnished Information (GFI).

The contractor shall identify and request any Government Furnished Information (GFI) deemed
necessary to complete SOW requirements. The Government will assist the contractor in
obtaining information. This includes technical manuals, training materials and information.
drawings, specifications. procedures, processes, and quality system documents required for
the performance of engineering, logistics. and technical support. Software related to the
[**] will be made available for use on contractor hardware to assist in integration
tasking, if the contractor should desire. The government shall assist in loading and
configuring [**] software at Keyport. Wa. As required.

     5.2 Return of Government Furnished Items.

All GFI and GFE provided to or acquired by the contractor shall be returned to the
Government upon completion of assigned tasking.

 

 

N00253-09-D-0005

0001

Page 15 of 21

6.0 Deliverables

The Contractor shall provide data in accordance with the Statement of Work (SOW) and DD Form
1423, CDRLs, as specified under each task order issued under this contract. The base SOW
contains the following deliverable data:

	 	 	 	 	 	 	 	 	 
	CDRL	 	SOW PARA	 	TITLE OF DATA ITEM	 	FREQUENCY
	A001

	 	 	5.1	 	 	Contractors Progress,
Status and Management
Report
	 	15th day of the month
for work performed in
the previous month.

Documentation shall be delivered to the Government in MS Office soft copy format and hard copy
using Contractor format. If unable to submit electronically, data shall be provided by mail to:
Craig M. Bleile. NAVSEA KPWA 44, 610 Dowell Street, Keyport, WA 98345-7610.

 

 

N00253-09-D-0005

0001

Page 16 of 21

7.0 Special Conditions

The following special conditions shall apply to the contractor in the performance of the
tasks under this IDIQ contract.

     7.1 SBIR Phase III

The LEAP technology was originally developed under the Small Business Innovation Research
(SBIR) Program. specifically Topic Number N00-116. entitled Modular 100kW Wave Powered
Electric Generator (SBIR Phase I Contract Number N00014-01-M-0041 and Phase 11 Contract
Number N00014-02-C-0034). The work to be performed under this IDIQ contract extends the
work performed under these prior SBIR Phase I and Phase II contracts, and as such is
accorded all rights of an SBIR Phase III funding agreement.

     7.2 SBIR Data Rights

This contract incorporates the following clause:

DFARS 252.227-7018 Rights In Noncommercial Technical Data And Computer
Software—Small Business Innovation Research (SBIR) Program (JUN 1995) (Also
applies to STTR programs)

     7.3 Packaging and Marking

Preservation, packaging, packing and marking of all deliverable contract line items
shall conform to normal commercial packing standards to assure safe delivery at
destination.

All reports. briefs, technical documents, etc. submitted to the Government under
this contract should contain the following legend:

SBIR or STTR DATA RIGHTS

	 	 	 
	Topic Numbers:

	 	N95-074 and N00-116
	Contract No.:

	 	N00014-09-C-01 15
	Contractor Name:

	 	Ocean Power Technologies, Inc.
	Contractor Address:

	 	1590 Reed Road; Pennington, NJ 08534-5010

The Government’s rights to use, modify, reproduce, release, perform, display, or disclose
technical data or computer software marked with this legend are restricted as provided in
paragraph (b)(4) of DFARS 252-227-7018. Rights in Noncommercial Technical Data and
Computer Software—Small Business Innovative Research (SBIR) Program.

 

 

N00253-09-D-0005

0001

Page 17 of 21

Section E — Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

	 	 	 	 	 	 	 	 	 
	CLIN	 	INSPECT AT	 	INSPECT BY	 	ACCEPT AT	 	ACCEPT BY
	0001

	 	Destination
	 	Government
	 	Destination
	 	Government
	0002

	 	Destination
	 	Government
	 	Destination
	 	Government

 

 

N00253-09-D-0005

0001

Page 18 of 21

Section F — Deliveries or Performance

DELIVERY INFORMATION

	 	 	 	 	 	 	 	 	 
	CLIN	 	DELIVERY DATE	 	QUANTITY	 	SHIP TO ADDRESS	 	UIC
	 
	 	 	 	 	 	 	 	 
	0001

	 	POP 25-SEP-2009 TO

24-SEP-2010
	 	N/A
	 	NAVAL UNDERSEA WARFARE CENTER RECEIVING

OFFICER

ATTN: DIVISION KEYPORT SUPPLY

OFFICER

BLDG 893

610 DOWELL STREET

KEYPORT WA 98345-7610

360 396-2776

FOB: Destination
	 	N00253
	 
	0002

	 	POP 25-SEP-2009 TO

24-SEP-2010
	 	N/A
	 	N/A

FOB: Destination	 	 

 

 

N00253-09-D-0005

0001

Page 19 of 21

Section G — Contract Administration Data

ACCOUNTING AND APPROPRIATION DATA

AA: 1791319 75XZ 253 SASLM 0 068342 2D 527530 9D90A000C0NO

AMOUNT: $2,449,835.99

CIN 915214260001: $2,449,835.99

	 	 	 	 	 	 	 	 	 	 	 	 	 
	CLIN	 	JOB ORDER	 	FUNDS EXP. DATE	 	FUNDED QTY	 	FUNDED AMT
	0001

	 	0195SBR
	 	30-SEP-2009
	 	 	1.00	 	 	$	2,449,835.99	 

CLAUSES INCORPORATED BY FULL TEXT

HQ G-2-0007 INVOICE INSTRUCTIONS (NAVSEA) (OCT 2006)

     (a) In accordance with the clause of this contract entitled “ELECTRONIC SUBMISSION OF
PAYMENT REQUESTS" (DFARS 252.232-7003), the Naval Sea Systems Command (NAVSEA) will
utilize the DoD Wide Area Workflow Receipt and Acceptance (WAWF) system to accept
supplies/services delivered under this contract. This web-based system located at
https://wawf.eb.mil provides the technology for government contractors and authorized
Department of Defense (DoD) personnel to generate, capture and process receipt and
payment-related documentation in a paperless environment. Invoices for supplies/services
rendered under this contract shall be submitted electronically through WAWF. Submission of hard
copy DD250/invoices may no longer be accepted for payment.

     (b) It is recommended that the person in your company designated as the Central
Contractor Registration (CCR) Electronic Business (EB) Point of Contact and anyone
responsible for the submission of invoices, use the online training system for WAWF at
http://wawftraining.com. The Vendor. Group Administrator (GAM), and sections marked
with an asterisk in the training system should be reviewed. Vendor Quick Reference Guides
also are available at http://acquisition.navy.mil/navyaos/content/view/ful1/3521/.
The most useful guides are “Getting Started for Vendors” and “WAWF Vendor Guide”.

     (c) The designated CCR EB point of contact is responsible for activating the company’s
CAGE code on WAWF by calling 1-866-618-5988. Once the company is activated. the CCR EB point of
contact will self-register under the company’s CAGE code on WAWF and follow the instructions
for a group administrator. After the company is setup on WAWF, any additional persons
responsible for submitting invoices must self-register under the company’s CAGE code at
https://wawf.eb.mil.

     (d) The following information regarding invoice routing is provided for completion of the
invoice in WAWF:

	 	 	 
	WAWF Invoice Ty pe	 	Cost Voucher
	Pay DoDAAC

	 	HQ0337
	Admin DODAAC

	 	S3915A
	Inspection

	 	Desination
	Acceptance

	 	Desination
	Fast Pay (FAR 52.213-1 required)

	 	No

 

 

N00253-09-D-0005

0001

Page 20 of 21

	 	 	 
	WAWF Invoice Ty pe	 	Cost Voucher
	Ship To Code (DoDAAC)
	 	N00253
	LPO DODAAC (if applicable)
	 	***
	DCAA DODAAC (if applicable)
	 	HAA310
	Applicable CLIN/SLIN
	 	0001

For detailed instructions on submitting documents in WAWF, please review the information posted at
the following link:

http://acquisition.navy.mil/rda/home/acquisition_one_source/ebusiness/don_ebusiness_solutions/wawf_overview/vendor_information

Attachments created in any Microsoft Office product may be attached to the WAWF invoice, e.g.,
backup documentation, timesheets. etc. Maximum limit for size of each file is 2 megabytes. Maximum
limit for size of files per invoice is 5 megabytes.

(e) Before closing out of an invoice session in WAWF, but after submitting the document(s), you
will be prompted to send additional email notifications. Click on “Send More Email Notification”
and add the acceptor/receiver email addresses noted below in the first email address block, and add
any other additional email addresses desired in the following blocks. This additional notification
to the government is important to ensure that the acceptor/receiver is aware that the invoice
documents have been submitted into WAWF.

Send Additional Email Notification To:

Receiptcontrol.nuwckpt.fct@navy.mil

Tariq.al-agba@navy.mil

Craig.bleile@navv.mil

(f) The contractor shall submit invoices for payment per contract terms and the government
shall process invoices for payment per contract terms.

(g) For specific questions regarding your invoice please contact the Keyport Vendor Pay group
at (360) 315-8500 or at vendorpay.nuwckpt.fct@navy.mil. If you have any questions regarding WAWF,
please contact the WAWF helpdesk at the above 1-866 number or the NAVSEA WAWF point of contact
Margaret Morgan at (202) 781-4815 or margaret.morgan@navy.mil.

(End of Text)

 

 

N00253-09-D-0005

0001

Page 21 of 21

Section J — List of Documents, Exhibits and Other

Attachments LIST OF ATTACHMENTS

Attachment

1. Contract Data Requirements List (CDRL) A0001exv4w1

Exhibit 4.1

AMENDMENT

          This
Amendment (this “Amendment”), dated and effective as of
December 10, 2009 (the “Effective
Time”), is made and entered into by and between MGIC Investment Corporation, a Wisconsin
corporation (the “Company”), and Wells Fargo Bank, N.A., a national banking association, as rights
agent (the “Rights Agent”), under that certain Amended and Restated Rights Agreement, dated as of
July 7, 2009 as amended through and including November 30, 2009 (the “Rights Agreement”).

RECITALS:

          WHEREAS, pursuant to Section 27 of the Rights Agreement, under circumstances set forth
therein, the Company may supplement or amend any provision of the Rights Agreement; and

          WHEREAS, the Company desires to amend the Rights Agreement as set forth herein and directs the
Rights Agent to execute this Amendment.

AGREEMENT:

          NOW, THEREFORE, for good and valuable consideration, the receipt and sufficiency of which are
hereby acknowledged, and intending to be legally bound hereby, the parties agree as follows:

     1. Amendment of the Rights Agreement. Section 1 of the Rights Agreement is amended to
read in its entirety as follows as of the Effective Time:

     Certain Definitions. For purposes of this Agreement, the following terms have
the meanings indicated:

     (a) “Acquiring Person” means any Person that is or has become, by itself or together
with its Affiliates and Associates, a Beneficial Owner of 5.0% or more of the Common Shares
then outstanding, but shall not include:

     (i) any Related Person;

     (ii) any Grandfathered Person, provided that if the Percentage Stock Ownership
of any Person that had qualified as a Grandfathered Person ceases to be at least
5.0%, then such Person shall not be deemed to be an Acquiring Person until such
later time (if any) as the Percentage Stock Ownership of such Person is 5.0% or
more, and then only if such Person does not qualify (A) for the exception in
subsection (iii) of this Section 1(a), (B) as a Grandfathered Person pursuant to
subsection (m)(ii) of this Section 1, or (C) in the case of any Person who was a
Grandfathered Person pursuant to subsection (m)(i) of this Section 1, as a
Grandfathered Person pursuant to subsection (m)(ii) of this Section 1, which shall
be applied to such Person as if the Percentage Stock Ownership of such Person at the
Amendment Effective Time had been less than 5.0%; and

 

 

     (iii) any Person that the Board determines, in its sole discretion, has, at or
after the Amendment Effective Time, by itself or together with its Affiliates and
Associates, inadvertently become a Beneficial Owner of 5.0% or more of the Common
Shares then outstanding (or has inadvertently failed to continue to qualify as a
Grandfathered Person); provided that such Person promptly enters into, and delivers
to the Company, an irrevocable commitment promptly to divest or cause its Affiliates
and Associates to divest, and thereafter such Person or its Affiliates and
Associates promptly divest (without exercising or retaining any power, including
voting power, with respect to such Common Shares (or other securities the beneficial
ownership of which by a Person also results in such Person beneficially owning
Common Shares)), sufficient Common Shares (or other securities the beneficial
ownership of which by a Person also results in such Person beneficially owning
Common Shares) so that such Person’s Percentage Stock Ownership is less than 5.0%
(or, in the case of any Person who or which has inadvertently failed to continue to
qualify as a Grandfathered Person, Common Shares (or other securities the beneficial
ownership of which by a Person also results in such Person beneficially owning
Common Shares) in an amount sufficient to reduce such Person’s beneficial ownership
of Common Shares by the number of Common Shares that caused such Person to so fail
to qualify as a Grandfathered Person); provided further that any such Person shall
cease to qualify for the exclusion from the definition of “Acquiring Person”
contained in this subsection (iii) from and after such time (if any) as the Person,
together with its Affiliates and Associates, subsequently becomes a Beneficial Owner
of 5.0% or more of the Common Shares then outstanding (or fails to continue to
qualify as a Grandfathered Person), unless the Person independently meets the
conditions set forth in this subsection (iii) with respect to the circumstances
relating to the Person, together with its Affiliates and Associates, subsequently
becoming a Beneficial Owner of 5.0% or more of the Common Shares then outstanding
(or failing to continue to qualify as a Grandfathered Person).

     (b) “Affiliate” and “Associate” shall have the respective meanings ascribed to such
terms in Rule 12b-2 of the General Rules and Regulations under the Securities Exchange Act
of 1934, as amended (the “Exchange Act”), as in effect on the date of this Agreement and, to
the extent not included within the foregoing provisions of this Section 1(b), shall also
include, with respect to any Person, any other Person whose Common Shares are treated, for
purposes of Section 382 of the Code and the Treasury Regulations thereunder, as being (i)
owned by such first Person (or by a Person or group of Persons to which the Common Shares
owned by such first Person are attributed pursuant to Treasury Regulation Section
1.382-2T(h)), or (ii) owned by the same “entity” (as defined in the second sentence of
Treasury Regulation Section 1.382-3(a)(1)(i)) as is deemed to own the Common Shares owned by
such first Person; provided, however, that a Person shall not be deemed to be an Affiliate
or Associate of another Person solely because either or both Persons are or were directors
or officers of the Company.

     (c) “Amendment Effective Time” means the close of business on July 7, 2009.

2

 

     (d) A Person shall be deemed a “Beneficial Owner” of, and shall be deemed to
“beneficially own,” any securities:

     (i) which such Person or any of such Person’s Affiliates or Associates
beneficially owns, directly or indirectly;

     (ii) which such Person or any of such Person’s Affiliates or Associates,
directly or indirectly, has the right to acquire (whether such right is exercisable
immediately or only after the passage of time) pursuant to any agreement,
arrangement or understanding (whether or not in writing) or upon the exercise of
conversion rights, exchange rights, warrants, options, or other rights (in each
case, other than upon exercise or exchange of the Rights); provided, however, that a
Person shall not be deemed a Beneficial Owner of, or to beneficially own, securities
tendered pursuant to a tender or exchange offer made by or on behalf of such Person
or any of such Person’s Affiliates or Associates until such tendered securities are
accepted for purchase or exchange;

     (iii) which such Person or any of such Person’s Affiliates or Associates,
directly or indirectly, has or shares the right to vote or dispose of, or has
“beneficial ownership” (as defined under Rule 13d-3 of the General Rules and
Regulations under the Exchange Act) of, including pursuant to any agreement,
arrangement or understanding (whether or not in writing); or

     (iv) with respect to which any other Person is a Beneficial Owner, if the
Person referred to in the introductory clause of this Section 1(d) or any of such
Person’s Affiliates or Associates has any agreement, arrangement or understanding
(whether or not in writing) with such other Person (or any of such other Person’s
Affiliates or Associates) with respect to acquiring, holding, voting or disposing of
any securities of the Company;

provided, however, that the preceding provisions of this Section 1(d) shall not be applied
to cause a Person to be deemed a “Beneficial Owner” of, or to “beneficially own,” any
security (A) solely because such Person has the right to vote such security pursuant to an
agreement, arrangement or understanding (whether or not in writing) which (1) arises solely
from a revocable proxy given to such Person in response to a public proxy or consent
solicitation made pursuant to, and in accordance with, the applicable rules and regulations
of the Exchange Act, and (2) is not also then reportable on Schedule 13D under the Exchange
Act (or any comparable or successor report), or (B) if such beneficial ownership arises
solely as a result of such Person’s status as a “clearing agency,” as defined in Section
3(a)(23) of the Exchange Act; provided further, however, that nothing in this Section 1(d)
shall cause a Person engaged in business as an underwriter of securities or member of a
selling to group to be a Beneficial Owner of, or to “beneficially own,” any securities
acquired through such Person’s participation in good faith in an underwriting syndicate
until the expiration of 40 calendar days after the date of such acquisition, or such later
date as the directors of the Company may determine in any specific case. Notwithstanding
anything herein to the contrary, to the extent not within the foregoing provisions of this
Section 1(d), a Person shall be deemed a “Beneficial

3

 

Owner” of, and shall be deemed to “beneficially own” or have “beneficial ownership” of, any
securities that are owned by another Person and that are treated, for purposes of Section
382 of the Code and the Treasury Regulations thereunder, as being (x) owned by such first
Person (or by a Person or group of Persons to which the securities owned by such first
Person are attributed pursuant to Treasury Regulation Section 1.382-2T(h)), or (y) owned by
the same “entity” (as defined in the second sentence of Treasury Regulation Section
1.382-3(a)(1)(i)) as is deemed to own the securities owned by such first Person.

     (e) “Board” means the Board of Directors of the Company.

     (f) “Business Day” means any day other than a Saturday, a Sunday or a day on which
banking institutions in the State of Wisconsin are authorized or obligated by law or
executive order to close.

     (g) “close of business” on any given date shall mean 5:00 P.M., Milwaukee, Wisconsin
time, on such date; provided, however, that if such date is not a Business Day it shall mean
5:00 P.M., Milwaukee, Wisconsin time, on the next succeeding Business Day.

     (h) “Common Shares” means the shares of common stock, par value $1.00, of the Company.

     (i) “Distribution Date” has the meaning set forth in Section 3(a) hereof.

     (j) “Exchange Act” has the meaning set forth in subsection (b) of this Section 1.

     (k) “Expiration Date” means earliest of (i) Final Expiration Date; (ii) the time at
which the Rights are redeemed as provided in Section 23 hereof (the “Redemption Date”);
(iii) the time at which the Rights are exchanged as provided in Section 24 hereof; (iv) the
repeal of Section 382 of the Code if the Board determines that this Agreement is no longer
necessary for the preservation of the Tax Benefits; and (v) the beginning of a taxable year
of the Company to which the Board determines that no Tax Benefits may be carried forward.

     (l) “Final Expiration Date” means the close of business on August 17, 2012, subject to
extension.

     (m) “Grandfathered Person” means:

     (i) any Person who does not qualify as an “Acquiring Person” (as defined in the
Original Rights Agreement) immediately prior to the Amendment Effective Time and who
at the Amendment Effective Time is a Beneficial Owner of 5.0% or more of the Common
Shares outstanding at the Amendment Effective Time; provided that any such Person
shall cease to be a Grandfathered Person from and after such time (if any) as the
Person’s Percentage Stock Ownership shall be increased from such Person’s lowest
Percentage Stock Ownership at or after the Amendment Effective Time, other than any
increase pursuant to or as a

4

 

result of (A) an acquisition of Common Shares by the Company and/or (B) such
Person becoming the Beneficial Owner of additional Common Shares due solely to (x)
such Person beneficially owning the Company’s 9% Convertible Junior Subordinated
Debentures due 2063 (the “2063 Debentures”) immediately prior to the Amendment
Effective Time and (y) during the period thereafter in which the 2063 Debentures
then beneficially owned continue to be beneficially owned by such Person, the
occurrence of one or more 2063 Debenture Adjustment Events (as such term is defined
at the end of this Section 1(m));

     (ii) any Person who (x) at the Amendment Effective Time is not a Beneficial
Owner of 5.0% or more of the Common Shares outstanding at the Amendment Effective
Time and (y) if the definition of Acquiring Person did not include an exclusion for
any Grandfathered Person, would qualify as an Acquiring Person after the Amendment
Effective Time as a result of (I) an acquisition of Common Shares by the Company
and/or (II) such Person becoming the Beneficial Owner of additional Common Shares
due solely to the occurrence of one or more 2063 Debenture Adjustment Events during
the period in which 2063 Debentures are beneficially owned by such Person; provided
that any such Person shall cease to be a Grandfathered Person from and after such
time (if any) as the Person’s Percentage Stock Ownership shall be increased from
such Person’s lowest Percentage Stock Ownership on or after the date of the first
occurrence of any event described in clause (I) or (II), other than any increase
pursuant to or as a result of (A) an acquisition of Common Shares by the Company
and/or (B) such Person becoming the Beneficial Owner of additional Common Shares due
solely to the occurrence of one or more 2063 Debenture Adjustment Events during the
period in which 2063 Debentures are beneficially owned by such Person;

     (iii) any Person who (x) at all times on or prior to November 30, 2009 is not
and was not a Beneficial Owner of 5.0% or more of the Common Shares then outstanding
and (y) if the definition of Acquiring Person did not include an exclusion for any
Grandfathered Person, would qualify as an Acquiring Person on or after December 1,
2009 as a direct result of an acquisition or merger involving all or part of the
asset management business of a financial institution headquartered in the United
Kingdom that closes or is effective on or after December 1, 2009 but no later than
December 15, 2009 and has a transaction value in excess of $10 billion; provided
that any such Person shall cease to be a Grandfathered Person from and after the
earlier to occur of (x) such time (if any) as the Person’s Percentage Stock
Ownership shall be increased above 10.0%, other than any increase pursuant to or as
a result of (A) an acquisition of Common Shares by the Company and/or (B) such
Person becoming the Beneficial Owner of additional Common Shares due solely to the
occurrence of one or more 2063 Debenture Adjustment Events during the period in
which 2063 Debentures are beneficially owned by such Person or (y) January 15, 2010;
and

     (iv)
Leon G. Cooperman and his Affiliates, including Omega Advisors, Inc. and Omega Associates, L.L.C.
(each, an “Omega Person” and, collectively, the “Omega Persons”); provided that the Omega Persons
shall cease to be a Grandfathered Person from and after the earlier to occur of (x) such time (if
any) as the Omega Persons become the Beneficial Owner of a number of Common Shares that is more
than the number of Common Shares that the Omega Persons beneficially owned at the close of business
on December 3, 2009 (it is understood that the transfer of beneficial ownership of Common Shares to
any Omega Person without any consideration for such transfer given by any Omega Person shall not
result in an increase in beneficial ownership by the Omega Person until the Omega Person accepts
such transfer) or (y) January 15, 2010.

5

 

If any Person that had qualified as a Grandfathered Person ceases to so qualify, then for purposes
of Section 1(a) such Person and such Person’s Affiliates and Associates shall be deemed to have
become, as of the time the Person ceased to qualify as a Grandfathered Person, a Beneficial Owner
of the Common Shares that such Person and such Person’s Affiliates and Associates then beneficially
own. For the avoidance of doubt, it is
understood that the qualifications and exceptions in subsections (m)
(i), (ii) and  (iii) of this Section 1 with respect to 2063 Debenture Adjustment Events do not apply to
Common Shares attributable to 2063 Debenture Adjustment Events that are delivered and
beneficially owned on conversion of 2063 Debentures. “2063 Debenture Adjustment Events”
means each of (x) effective as of each date on which the interest so deferred would have
been due and payable in the absence of such deferral, the Company deferring the payment of
interest on the 2063 Debentures, (y) effective as of each date on which such compounded
interest accrues, compounded interest on account of such a deferral, and (z) an increase
pursuant to the terms of the 2063 Debentures in the number of Common Shares that are
deliverable on conversion of the 2063 Debentures. Changes in the average price per Common
Share that affect the number of Common Shares deliverable on conversion of the 2063
Debentures shall be considered adjustments under the immediately preceding clause (z).

     (n) “Percentage Stock Ownership” of a Person means the percentage calculated by
dividing (i) the number of Common Shares as to which the Person, together with its
Affiliates and Associates, is a Beneficial Owner, divided by (ii) the number of Common
Shares then outstanding.

     (o) “Person” means any individual, firm, corporation, partnership, trust, association,
limited liability company, limited liability partnership, governmental entity, or other
entity, or any group of any one or more of the foregoing making a “coordinated acquisition”
of shares or otherwise treated as an entity within the meaning of Treasury Regulation
Section 1.382-3(a)(1)(i) and shall include any successor (by merger or otherwise) of any
such entity.

     (p) “Redemption Date” has the meaning set forth in subsection (k) of this Section 1.

     (q) “Related Person” means the Company, any Subsidiary of the Company (in each case
including, without limitation, in any fiduciary capacity), any employee benefit

6

 

plan or compensation arrangement of the Company or any Subsidiary of the Company, or
any entity or trustee holding Common Shares to the extent organized, appointed or
established by the Company or any Subsidiary of the Company for or pursuant to the terms of
any such employee benefit plan or compensation arrangement.

     (r) “Securities Act” means the Securities Act of 1933, as amended.

     (s) “Shares Acquisition Date” means the first date of public announcement (which, for
purposes of this definition, shall include, without limitation, a report filed or amended
pursuant to Section 13(d) under the Exchange Act), by the Company or a Person or an
Affiliate of the Person, (i) that the Person has become an Acquiring Person or (ii) of
information that leads the Board to conclude that the Person has become an Acquiring Person.

     (t) “Subsidiary” of any Person means any other Person of which securities or other
ownership interests having ordinary voting power, in the absence of contingencies, to elect
a majority of the board of directors or other Persons performing similar functions are at
the time directly or indirectly owned by such first Person.

     (u) “Tax Benefits” means the net operating loss carryovers, capital loss carryovers,
general business credit carryovers, alternative minimum tax credit carryovers and foreign
tax credit carryovers, as well as any loss or deduction attributable to a “net unrealized
built-in loss” within the meaning of Section 382 of the Code, of the Company or any of its
Subsidiaries.

     (v) “Treasury Regulation” means a final, proposed or temporary regulation of the U.S.
Department of Treasury promulgated under the Code.

     2. No Further Amendment. Except as specifically supplemented and amended, changed or
modified in Section 1 above, the Rights Agreement shall be unaffected by this Amendment and shall
remain in full force and effect.

     3. Governing Law. This Amendment shall be deemed to be a contract made under the laws
of the State of Wisconsin and for all purposes shall be governed by and construed in accordance
with the laws of such State applicable to contracts to be made and performed entirely within such
State.

     4. Counterparts. This Amendment may be executed in any number of counterparts, and
each of such counterparts shall for all purposes be deemed to be an original, and all such
counterparts shall together constitute but one and the same instrument.

     5. Descriptive Headings. Descriptive headings of the Sections of this Amendment are
inserted for convenience only and shall not control or affect the meaning or construction of any of
the provisions of this Amendment.

7

 

          IN WITNESS WHEREOF, the parties hereto have caused this Amendment to be duly executed and
delivered, all as of the day and year first above written.

	 	 	 	 	 	 	 	 	 	 	 
	MGIC INVESTMENT CORPORATION	 	 	 	WELLS FARGO BANK, N.A., as
Rights Agent	 	 
	 
	 	 	 	 	 	 	 	 	 	 
	By:

	 	/s/ J. Michael Lauer
 

	 	 	 	By:
	 	/s/ Jennifer Leno
 

	 	 
	 

	 	Name: J. Michael Lauer
	 	 	 	 	 	Name: Jennifer Leno	 	 
	 

	 	Title: Executive Vice President and
Chief Financial Officer
	 	 	 	 	 	Title: Vice President	 	 

8

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00166-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00166-of-00352.parquet"}]]