N00024-19-R-5393_modification_A00003_07.11.2019.pdf

N0002417NR43064

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

This modification to the solicitation includes the follow ing change (all major changes highlighted):

1) Section C Part 1 Paragraph 3.4.1 to align Cybersecurity Encryption of Data at Rest requirements w ith DFARS 252.204-7012.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 58

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 11-Jul-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0002419R5393

X 9B. DATED (SEE ITEM 11)

30-Apr-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

11-Jul-2019

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2040

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002419R5393

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

SPECIAL INSTRUCTIONS

SECTION C

PART 1 - CONTRACT LINE ITEM DESCRIPTIONS

The MK 41 Vertical Launching System (VLS) is the primary missile launching system in Navy surface combatants and is used to store and launch multiple missile variants. The VLS has the capability to launch all STANDARD Missile (SM) 2, TOMAHAWK, Vertical Launch Anti-Submarine Rocket, NATO SEASPARROW, Evolved NATO SEASPARROW, SM-3 and SM-6 missile variants. The VLS program provides launchers, launch control units, canisters and associated support equipment for TICONDEROGA and ARLEIGH BURKE Class United States Navy surface combatants. The MK 41 VLS has been sold to and integrated into multiple allied navies including Australia, Canada, Germany, Japan, the Netherlands, New Zealand, Norway, South Korea, Spain, and Turkey.

The Electronics & Computer Programs Engineering Agent Contractor shall provide system and other multi-discipline engineering, installation, repair, logistic and management services as described below in support of all current and legacy MK 41 VLS Launcher electronic systems, tactical and ancillary computer programs, launcher support and test equipment and production support equipment including but not limited to Automated Test Equipment. This support shall be provided for the design, development, production, test, product improvement and sustaining phases of the program.

The Electronics & Computer Programs Engineering Agent Contractor shall serve as the electronic systems and computer programs technical expert and key member of the VLS engineering team that consists of the Mechanical Systems Engineering Agent, Components Engineering Agent, Technical Direction Agent (TDA), System Integration Agent (SIA) and In-Service Engineering Agent (ISEA). The Contractor shall closely coordinate and collaborate with the Mechanical Systems Engineering and Components Engineering Agents on all projects that require a combination of VLS mechanical, electronic and/or digital designs or modifications.

The Mechanical Systems Engineer Agent Contractor shall provide system and other multi-discipline engineering, installation, repair, logistic and management services as described below in support of all current and legacy MK 41 VLS Launcher mechanical systems, Canister Assemblies, Launcher Ancillary Equipment, Canister & Launcher handling equipment, Cartridge Actuated Devices and associated production support equipment including but not limited to Automated Test Equipment. This support shall be provided for the design, development, production, test, product improvement and sustaining phases of the program.

The Mechanical Systems Engineer Agent Contractor will serve as the mechanical systems technical expert and key member of the VLS engineering team that consists of the Electronics & Computer Programs Engineering Agent, Components Engineering Agent, Technical Direction Agent (TDA), System Integration Agent (SIA) and In-Service Engineering Agent (ISEA). The Contractor shall closely coordinate and collaborate with the Electronics & Computer Programs and Components Engineering Agents on all projects that require a combination of VLS mechanical, electronic and/or digital designs or modifications.

All contractor personnel assigned to performance of this contract shall be U.S. citizens. All contractor key personnel assigned to the performance of this contract shall have at least a SECRET clearance.

The services to be furnished shall be performed in accordance with the following descriptions, specifications and requirements addressed herein. All tasks to be performed under this contract shall be described and authorized in writing by Technical Instructions (Tls) approved by the Procuring Contracting Officer (PCO) and Contracting Officer Representative (COR).

The following Open Architecture requirements apply to all Items described below:

The Government intends to design and procure system(s) having Open Architecture designs and corresponding components to the maximum extent practical for the MK 41 VLS. The contractor shall define, document, and follow an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus based standards. The contractor shall develop, maintain, and use an open systems management plan and demonstrate compliance with that plan during all design reviews. As part of an open systems management plan, the contractor shall identify to the Government all Commercial-Off-the-Shelf/Non-development Item (COTS/NDI) components, their functionality, and provide copies of license agreements related to the use of these components for Government approval prior to use. The contractor shall analyze the costs and risks of individual open interfaces and address these findings into the open systems management plan. The proposed open systems management plan will be incorporated into the contract with any changes, alterations, and/or modifications requiring Government approval.

1. In satisfying the Government's requirements, the following design approach characteristics shall be utilized:

a. Open Architecture - The contractor shall develop and maintain an architecture that incorporates appropriate considerations for configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b. Modular, Open Design - The contractor shall develop an architecture that is layered and modular and uses COTS/NDI hardware, operating systems, and middleware that utilize non-proprietary or non-vendor unique, key Application Programming Interfaces (APIs). As part of its open system management plan, the contractor will be required, at a minimum, to describe how the proposed system architecture meets these goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable.

c. System Requirements Accountability - The contractor shall ensure that all system requirements (including those contained in the Initial Capabilities Document, Capabilities Development Document, Capabilities Production Document, and in this Section C are accounted for through a demonstrated ability to trace each requirement to one or more modules that consist of components that are self-contained elements with well-defined, open and published interfaces implemented using open standards.

d. Inter-component Dependencies - The design shall minimize inter-component dependencies to allow components to be decoupled and reused, where appropriate, across various naval programs and platforms.

e. Modular Open Systems Approach (MOSA) - The contractor shall describe its rationale for the modularization choices made to generate the design. The contractor's rationale must explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system. The MOSA requirements will not apply to the legacy components that exist within the MK 41 VLS.

f. MOSA Objectives - The contractor shall specify how it plans to use MOSA to enable the system to adapt to evolving requirements and threats; accelerate transition from science and technology into technology and deployment; facilitate systems reconfiguration and integration; reduce the development cycle time and total life cycle cost; maintain continued access to cutting edge technologies and products from multiple suppliers; and mitigate the risks associated with technology obsolescence, being locked into proprietary or vendor-unique technology, and reliance on a single source of supply over the life of the system.

g. Open Systems Management Plan - The contractor shall provide a plan for supporting the proposed Modular Open System Approach, including, but not limited to, plans for integrating the systems under development both internally and externally, a strategy for maintaining the currency of the technology (through COTS and other reusable NDI insertion, technology refresh strategies, and other appropriate means) and creation of different processes necessary to support MOSA.

h. Technology Insertion - The contractor's architectural approach shall support the rapid and affordable insertion and refreshment of technology through modular design, the use of open standards and open interfaces.

i. Life-Cycle Sustainability - The contractor shall consider use of COTS/NDI and open standards to enhance the system's life-cycle supportability by implementing performance-based logistics arrangements to sustain the components through their life cycle.

j. Interface Design and Management - The contractor shall:

i. Clearly define and describe all component and system interfaces;

ii. Define and document all subsystem and configuration item (CI) level interfaces to provide full functional, logical, and physical specifications;

iii. Identify processes for specifying the lowest level (i.e. subsystem or component) at and below which it intends to control and define interfaces by proprietary or vendor-unique standards and the impact of that upon its proposed logistics approach. Interfaces described shall include, but not be limited to, mechanical, electrical (power and signal wiring), software, firmware, and hardware;

iv. Identify the interface and data exchange standards between the component, module or system and the interconnectivity or underlying information exchange medium;

v. Consider using these interfaces to support an overall information assurance strategy that implement Information Assurance Processes (IA);

vi. If applicable, select external interfaces from existing open or Government standards with an emphasis on enterprise-level interoperability. The contractor shall describe how its selection of interfaces will maximize the ability of the system to easily accommodate technology insertion (both hardware and software) and facilitate the insertion of alternative or reusable modular system elements

k. Treatment of Proprietary or Vendor-Unique Elements - The contractor shall explain the use of proprietary, vendor-unique or closed components or interfaces. If applicable, the contractor will define its process for identifying and justifying proprietary, vendor-unique or closed interfaces, code modules, hardware, firmware, or software to be used. When interfaces, hardware, firmware, or modules that are proprietary or vendor unique are required, the contractor shall demonstrate to the Government that those proprietary elements do not preclude or hinder other component or module developers from interfacing with or otherwise developing, replacing, or upgrading open parts of the system.

l. Open Business Practices - The contractor shall demonstrate that the modularity of the system design promotes the identification of multiple sources of supply and/or repair, and supports flexible business strategies that enhance subcontractor competition. The contractor shall conduct a market survey to identify COTS candidates and other reusable NDI capable of achieving the performance requirements of solutions that it proposes to custom build. The survey results shall be provided to support each major review. COTS and other reusable NDI selection criteria shall address the following factors, at a minimum: Electrostatic Sensitive Device (ESD) immunity;

Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC); Integrated Logistics Support requirements; Safety; Reliability consistent with the environment described in the System Specification;

Maintainability; Subsystem performance trade-offs; Power, cooling, and physical form factors; Open system architecture break out compatibility; Cost; Manufacturer's quality assurance provisions; Market acceptability;

Obsolescence; Adequacy of available technical and intellectual property data and re-procurement data rights on the product; and Merits of the software supported by the product.

m. Reuse of Pre-existing or Common Items - The contractor shall reuse pre-existing or common items unless a determination is made by the contractor to not reuse. Contractor decisions not to reuse pre-existing items must be accompanied by one or more justifications such as cost (both of adoption and life cycle support), schedule, functional and non-functional performance, etc. The general objective of these efforts shall be the development of common system and/or common elements or components which meet the performance requirements of the various U.S. Navy or Marine Corps platform missions, where commonality offers the greatest technical and cost benefits.

n. Third Party Development - The contractor shall address how it will provide to the Government information needed to support third-party development and delivery of competitive alternatives of designs for other components or modules on an ongoing basis. The contractor shall provide a list of those proprietary, vendor-unique elements that it requests be exempt from this review.

o. Life Cycle Management and Open Systems - The contractor's architecture shall provide for insertion of COTS into the system and demonstrate that COTS, reusable NDI, and other components are logistically supported throughout the life cycle. The contractor shall describe and demonstrate the strategy for reducing product or system and associated supportability costs through insertion of COTS and other reusable COTS or NDI products.

The contractor shall establish a process to logistically support COTS or NDI products. The contractor shall describe the availability of commercial repair parts and repair services, facilities, and manpower required for life cycle support and demonstrate they are adequate to ensure long term support for COTS or NDI products. The contractor shall provide the proposed methodology for pass through of COTS warranties to the Government

p. Use of Standards - In designing the system(s), the contractor shall use the following standards in descending order of importance:

(i.) Standards as specified within the contract

(ii.) Commercial standards

a. Standards developed by international or national industry standards bodies that have been widely adopted by industry. Examples of widely adopted standards are:

1. SQL for databases

2. HTML for presentation layer

3. XML for data transfer

4. Web Services for remote system calls

b. Standards adopted by industry consensus-based standard bodies and widely adopted in the market place.

c. De facto standards (those widely adopted and supported in the market place).

2. The following engineering process and support requirements apply to all Items described below:

a. The contractor shall provide support to the TDA, SIA, ISEA and VLS Production Activities.

b. The contractor shall use the PEO IWS Systems Engineering Operations Manual, PEO TSC Instruction 4810.2, Software Development, Verification and Validation (V&V), Design Reuse, and Metrics Policy, PEO TSC Instruction 4810.3, Guidance for Prime Item Development Specification (PIDS) Document Preparation, and PEO IWS Instruction 5239.2, PEO IWS Surface Navy Combat System Cybersecurity, as applicable for engineering tasks.

c. The contractor shall collaborate with and support the VLS Mechanical Systems Engineering Agent and VLS Components Engineering Agent.

d. The contractor shall perform qualification testing and evaluation in accordance with requirements identified in WS 20313. MIL-HDBK-781A shall be used for guidance in planning of engineering tests and to support of alternate sources qualification.

e. The contractor shall use IEEE P1220, Standard for Application and Management of the Systems Engineering Process, EIA Standard IS-632, Systems Engineering, and/or EIA Standard IS-731, Systems Engineering Capability Model, for system engineering processes.

f. The contractor shall maintain a system Reliability & Maintainability (R&M) program and shall:

i. Support R&M program planning activities.

ii. Provide reliability assessments using MIL-HDBK-217 as a guide.

iii. Conduct failure analyses of design-related failures.

iv. Ensure components and subassemblies obtained from subcontractors and suppliers for use under this contract meet allocated R&M requirements.

g. The contractor shall generate or update and maintain a System Safety Program (SSP) that is fully integrated into the design process in accordance with CDRL B001. The SSP shall promote early identification, evaluation and resolution of hazards. The contractor shall ensure qualified engineers and managers are assigned to support the

VLS SSP.

i. The System Safety Program, in accordance with NAVSEA 5100.12-M and MIL-STD-882E, shall impose design requirements and establish management controls in order to eliminate any hazard or reduce the associated risk of the contractor designed subsystem or equipment to an acceptable level. The contractor is responsible to ensure subsystems or equipment can be operated, maintained and supported safely.

ii. The contractor shall submit a System Safety Program Progress Report (SSPPR) contractor when authorized by Technical Instruction and documented in accordance with CDRL B003.

iii. The contractor shall ensure that Commercial Off the Shelf (COTS) components and subassemblies obtained from subcontractors and suppliers for use under this contract meet allocated safety requirements and that sufficient data will be obtained to perform safety analysis of safety critical functionality.

iv. The VLS System Safety Program Plan (SSPP) shall be updated and implemented by the contractor when authorized by Technical Instruction and documented in accordance with CDRL B001.

v. The contractor shall perform the appropriate Hazard Analysis identified by the SSPP for the requirements, design, testing and operations phases. The Hazard Analyses shall be documented in accordance with CDRL B002.

vi. The contractor shall support System Safety Working Groups (SSWGs), Weapon System Explosive Safety Review Board (WSESRB) meetings, IPT meetings and meetings with other Government certifying activities.

vii. The contractor shall implement a method to identify, document and track hazards and the associated risks identified from the hazard analysis. Hazard documentation and tracking shall be accomplished using a Government provided database. Database updates shall be submitted in accordance with CDRL B005. The method implemented to identify hazards shall evaluate the equipment during performance as well as the safety impacts due to inadvertent functioning or functional failure. In addition, subsystems (equipment) that interface to the procured equipment shall be evaluated to ensure hazards and risks are mitigated to an acceptable level.

h. The contractor shall establish and conduct a Logistics Support Analysis (LSA) Program in accordance with TechAmerica Standard, GEIA-STD-0007 and the requirements contained therein as tailored by the Technical Instruction statement of work. The contractor shall establish and employ procedures for monitoring subcontractor and vendor activities to ensure they likewise establish and maintain procedures consistent with the requirements of the statement of work. The LSA program shall provide the basis for the integration of all logistic support elements and integrated logistics support programs. The LSA program shall be the analytical logistics effort within the system engineering process and shall constitute a composite of technologies used in the definition of specific logistic support requirements and in the injection of support criteria into the design and subsystem integration process.

i. The contractor shall develop training products including Interactive Multimedia Instruction (IMI), new IMI course curricula, and other IMI related tasks. Each of the training products shall be in conformance with MIL- PRF-29612B. Provide technical input and training updates when applicable as a result of integration programs or new product integration to the MK 41 Operation and Maintenance (O&M) Difference Course. Provide technical support in the conduct of ENCAN/DECAN and Dockside Handling Courses.

j. The contractor shall have a risk management process for identifying, assessing and prioritizing the cost, schedule and technical risks of the program. The risk management process shall be an integral element of the program's planning, management and reporting processes. A Risk Management Program shall conform to the process defined in in NAVSEAINST 5000.8, Navy SYSCOM Risk Management Policy.

k. The contractor shall integrate human factors into the design of items in accordance with MIL-STD-46855A and

MIL-STD-1472G.

l. The contractor shall analyze reported problems and provide timely recommendations/solutions.

m. The contractor shall use a parts control program based on existing part selection wherever possible and only introduce new parts when a MK 41 VLS part does not meet the design requirements.

n. The contractor shall provide cost estimate comparisons of options for various trade studies, perform Cost as an Independent Variable Analysis and /or support Cost Analysis Requirements Description (CARD) activities.

o. The contractor shall provide progress, status, cost and management reports.

p. Costs specifically identifiable to a Foreign Military Sales (FMS) Case shall be segregated and shall be charged to that FMS Case contract line item. TIs issued for FMS tasks will identify the billable contract line item.

q. The contractor shall provide the Government and Government support contractors electronic access to the contractor’s electronic engineering information data base system throughout the term of the contract.

r. All technical documentation and engineering reports shall be provided in editable electronic format within 30 days after task completion to the PMO and NSWC DD.

s. All software deliveries shall include, but not limited to, source code, executable(s) and compiler generated files.

Software documentation (requirements, design, user’s manual, concept of operation, supplemental engineering documentation) and test documentation (test plan, test report, traceability matrix, test data, scenarios, step-by-step list, log files, sniffer data) shall be provided in an editable electronic format within 30 days after task completion to the PMO and NSWC DD.

t. New TDP documents shall be provided in editable electronic format (i.e. Pro-E files/SolidWorks) within 30 days after task completion to NSWC DD in accordance with CDRL D005. TDP documents include models, and related design & engineering documents and drawings.

u. The contractor shall provide all deliverables procured and developed with Government funding including, but not limited to, technical documentation, engineering reports, software, source code, software documentation and TDP in editable electronic format quarterly to NSWC DD. Delivery of hardcopy deliverables shall be directed by the PCO/COR.

v. The Government will provide MK 41 VLS components, test sets, simulators and other equipment as needed as Government Property (GP) for design, development and test activities that are specified by TIs. If GP is provided to the contractor, the contractor shall manage the continued operation and updates of GP (including test equipment). This effort includes the purchase of Commercial Off-The-Shelf (COTS) tools and products that will enhance MK 41 VLS testability, troubleshooting, and data collection for VLS laboratories. The contractor shall perform general preventative maintenance on the GP residing at the contractor’s facility. The contractor shall repair or replace components of the GP equipment when damage occurs during required testing.

w. The contractor shall not use any internal funding (e.g. IRAD, other internal funds) in conjunction with tasks authorized under this contract.

x. All hardware and software designs and data rights belong to the US Government and the contractor has no proprietary rights.

y. All technical data shall be marked in accordance with MK 41 Vertical Launching System Standing Instruction 94-1F.

z. Contractor personnel requiring access to the Corporate Data Management System (CDMS), Standard Automated VLS On-Line Requisitioning System (SAVORS), VLS Interface Documents Library database or VLS Trouble Report database shall submit the appropriate registration forms as instructed by Attachment 8, Government Web Site Access Information. Users must have a Government issued Common Access Card (CAC) in order to access Government web sites. Awardee must complete and submit Form DD-1172 to the Contracting Officer’s Representative (COR) within 30 days after contract award. Users will be granted approval for CACs on a need to know basis.

The following general requirements apply to all Items described below:

1. CONTRACT PROGRAM MANAGEMENT - Government-Contractor Interface

1.1. The contractor shall establish and maintain lines of communication with PEO IWS 3LTask Engineers and such other Government and commercial organizations as are necessary to accomplish technical work requirements prepared and issued in accordance with Section H. The contractor shall attend scheduled conferences and meetings on specific technical requirements outlined in specific TIs, and provide meeting agendas, minutes, conference reports and trip reports. The contractor's role in such conferences and meetings is limited to technical discussions, recommendations of technical approaches to problem resolution, and other matters of a technical advisory nature. The contractor shall not engage in efforts which are basic management functions of PEO IWS 3L or perform work of a policy, decision-making or managerial nature that is a direct responsibility of PEO IWS 3L personnel.

1.2. Need-to-know certifications for those efforts detailed in the SOW shall be prepared and processed in accordance with the COR's direction.

1.3. The contractor shall establish and implement an action item/follow-up or status accounting system to assist in assuring the timely accomplishment of meeting/conference action items, problem solutions, etc., related to specific technical issues.

1.4. The contractor shall designate a Program Director to serve as the contractor representative authorized to technically represent the contractor in written communications. i.e., in authenticating contractor estimates of costs of work to be performed, certifying expenditures in monthly progress/status reports, etc. The contractor shall identify, by name, the Program Director in applicable reports.

1.5. The contractor shall designate Team Leaders as the TI technical points of contact for efforts in major areas of work under this contract. The contractor shall identify, by name(s), the Team Leader(s) in Tls and reports.

1.6. Subcontracting: The contractor may subcontract portions of TI efforts in the event the contractor lacks a particular expertise, facility, or both to fully successfully accomplish the TI efforts. The contractor shall maintain detailed records, such as purchase requests, solicitations, proposal evaluations, Subcontractor recommendations and associated Subcontractor correspondence and shall provide reports on Subcontractors' documentation upon written instructions from the COR.

1.7. As directed, the contractor shall give formal contract progress presentations. Presentations shall outline, in brief, the progress and status of all efforts performed during the period reported. Except as otherwise agreed to by the COR, the presentation shall be given at PEO IWS 3L at times and dates specified by the COR. The Contracting Officer shall be notified in advance of these presentations.

2. CHANGE CONTROL ENGINEERING

2.1. CONFIGURATION MANAGEMENT PROGRAM

2.1.1. The contractor shall maintain a Configuration Management program.

2.1.2. The contractor shall create and retain documentation and other evidence as needed to show any configuration change made under this contract results in continued compliance with WS 20313.

2.1.3. The contractor shall develop and implement procedures that will delineate the status of changes from the baseline, and proposed effectivity and status of implementation of government approved changes.

2.1.4. The contractor shall prepare Advance Change Study Notices (ACSN) and Ship Change Documents (SCD) for incorporation of design changes into the Vertical Launching System. ACSNs and SCDs submitted for Navy approval shall be in accordance with the MK 41 Vertical Launching System Configuration Management Plan; Volume 1, TL130-AD-PLN-010/VLS, Volume 2, TL130-AD-PLN- 020/VLS and Volume 3, TL130-AD-PLN-030/VLS.

2.1.5. The contractor shall establish a configuration audit and review program that will ensure the functional and physical characteristics match those characteristics specified by the configuration identification. It will be the responsibility of the contractor to provide the hardware and software to be audited, facilities, personnel, documentation (including drawings) and other support as may be required.

2.1.6. The contractor shall ensure that all design releases are processed through the CM authority and that configuration identification, change control and status accounting of engineering releases are accurately maintained to ensure compatibility, traceability, integrity and control of configuration items.

2.1.7. Major and minor deviations and waivers shall be submitted for approval in accordance with the VLS CM Plan TL130-AD-PLN-010/VLS. Minor deviations and waivers shall be submitted to the TDA, NSWCDD, for approval.

2.1.8. For drawings maintained by the contractor, ECPs/NORs or Change Notices (CNs) are acceptable forms when submitting a Class II change to the government. ECPs and NORs shall be used for drawings not maintained by the contractor, as defined in CDRL C001. All Class II changes to drawings that have been Navy approved and later placed under contractor control shall be submitted to the TDA for concurrence in classification. All ECPs or CNs submitted by the contractor for Government concurrence and/or approval shall include a complete package of drawing revision sheets, Notices of Revision, Specification Change Notices, revised parts lists and other necessary technical data package change pages to document the proposed change. This documentation shall be of sufficient quality and accuracy for release concurrent with ECP/CN approval by the Government.

A Safety Hazard Assessment Report (HAR) shall be submitted with the ECP/CN if there is a safety impact, as defined in CDRL B002.

2.2. DRAWINGS/TECHNICAL DATA PACKAGES

2.2.1. Background. This Statement of Work (SOW) establishes general Technical Data Package (TDP) requirements.

2.2.1.1. Applicable Documents. The documents identified in this section are applicable to drawing requirements.

2.2.1.2. Definitions. Unless specified otherwise herein, the definitions in MIL-STD-31000 apply.

2.2.2. General TDP Requirements. The TDPs shall be developed and maintained in accordance with MIL- STD-31000 and this SOW. The TDP product baseline is intended to include data developed under this contract for the product drawings and associated lists along with special inspection equipment, special tooling drawings, specifications, firmware, program documentation, test requirements and critical manufacturing process descriptions. In the event of any conflict between MIL-STD-31000 and these requirements, these requirements shall take precedence. These requirements are equally applicable to TDPs prepared by Subcontractors. TDPs are required for all new parts or items designed, developed or modified under this contract. Submission of data in electronic format is required. Prior Government approval is required if an automated electronic data item generation capability is used and it modifies the submission formal of the Contract Data Requirements Lists (CDRL). Existing drawings not in conformance with these requirements, but adequate to meet the intended drawing purpose and level, may not be redrawn.

2.2.3. Additional Requirements:

2.2.3.1. For items not developed at Government expense or for which the Government has not acquired unlimited rights and for which design disclosure drawings are not available, a TDP shall be developed that provides sufficient description, directly or by reference to permit procurement and logistic support of the same item in the future from the original manufacturer, or functionally and physically interchangeable items from other sources. If there are spare and repair part differences between the interchangeable items, then the item is not interchangeable.

2.2.3.1.1. Such drawings shall include as applicable, but shall not necessarily be limited to, details of performance, outline and mounting dimensions, input and output parameter tolerances, diagrams, mechanical and electrical connections, finishes and materials, essential operations and interchangeability, inspection test & evaluation requirements/criteria, calibration data and vendor item identification of sources of supply.

2.2.3.1.2. The TDP will normally be similar to a Vendor Item Control Drawing (Specification Control Drawing) or Source Control Drawing. Such drawings shall be prepared down to the assembly/subassembly level as defined in IEEE STD 200. The established provisioning and maintenance requirements for the equipment shall decide the level of breakdown.

2.2.3.2. For items not developed at Government expense and for which design disclosure data are available complete design disclosure product TDPs shall be created in lieu of control drawings.

As a minimum such drawings shall meet or shall be changed to meet the following:

2.2.3.2.1. The drawings shall be identified by name and address of the design activity, Commercial and Government Entity (CAGE) code, if available, and drawing (part) number.

2.2.3.2.2. Drawing practices and symbols used (including the use of legends/explanations for nonstandard symbols) shall be such that their intent and interpretation are clear and unambiguous.

2.2.3.3. NOTE: The term "Government expense" shall mean not only developed under this contract but also developed under any other Government contract.

2.2.3.4. The system equipment top drawing(s) shall be kept current by revision or Notice of Revision and included in the product TDP.

2.2.3.5. The parts list shall identify all reference documents cited on the associated drawing. In addition, they shall also list all schematics, specifications, (excluding those specifications that are determined by the contractor to be applicable to notes on the assembly drawings), unique process sheets, special tooling requirements (including stable base mylars, tapes or other media used in the implementation of all types of circuit cards), acceptance test requirements, applicable reference designations for each find number etc. which are essential for the manufacture and inspection of the item.

2.2.3.6. Unique processes and special tooling (e.g. Gerber files and master artwork) referenced on the engineering parts list and utilized in manufacturing shall be made a part of the product baseline and controlled in accordance with the CM requirements defined in paragraph 2.1.

2.2.3.7. The Quality Conformance inspection and acceptance test requirements shall be documented and submitted as part of the product TDP.

2.2.3.7.1. Environmental Stress Screening requirements, which include circuit card assembly temperature and random vibration cycling and production reliability tests, shall be documented and submitted as part of the TDP. These requirements shall be referenced on the appropriate part and assembly drawing or parts list.

2.2.3.8. Drawings shall specify the requirements for item marking in accordance with MIL-STD- 130 and for reference designation marking in accordance with IEEE STD 200, Unit Numbering Method.

2.2.3.8.1. Electrostatic Discharge Control requirements and symbol location shall be specified on the appropriate device and assembly drawing. Marking requirements shall be in accordance with MIL-STD-1686C, paragraph 5.7.

2.2.3.8.2. Drawings shall not be marked with a statement indicating the item to be "SIMILAR TO", "EQUIVALENT TO" or "SAME AS".

2.2.3.8.3. The following note shall be included on new Source Control Drawings and on existing Source Control Drawings when these are affected by an engineering change: "Any procurement of this source control item from the vendors identified herein shall be to this document only."

2.2.3.9. Firmware program documentation shall be identified with a drawing number and shall be in accordance with the Paragraph 2.1 CM requirements.

2.2.3.10. The contractor shall accord the Contracting Officer and designated representatives of the procuring activity every reasonable access and assistance in the performance of in-process and final completeness review of the TDP, which will include, but is not limited to the following:

2.2.3.10.1. Reviewing the contractor's engineering drawing practices in an in-process review.

2.2.3.10.2. Reviewing the contractor's Quality Assurance (QA) procedures pertaining to the TDP.

2.2.3.10.3. Visiting the contractor's plant to determine if the TDP the Government is purchasing under this contract is being used to procure, manufacture and test the parts and equipment.

2.2.3.10.4. Reviewing preliminary copies of the TDP and providing guidance to the contractor.

2.2.3.10.5. Conducting a final review of the TDP. Acceptance of the TDP will be as specified in the CDRL.

2.2.3.10.6. The contract number shall appear in the appropriate box of the title block on the first sheet of the drawing and associated parts list.

2.2.3.10.7. The metric measurement system may be used on TDPs that have international use.

Other use shall be as specified by the applicable TI.

2.2.3.10.8. Delivery of original and un-dimensioned, stable base drawings, magnetic tapes and disks may be required at the option of the procuring activity.

2.2.3.10.9. Unclassified data shall be prepared for shipment in accordance with ASTM D3951. Classified data shall be packed and shipped in accordance with the Industrial Security Manual for Safeguarding Classified Information.

2.2.3.10.10. Reference designations in accordance with ANSI/IEEE STD 200 shall not be used as find numbers or item numbers on the parts list.

2.2.3.10.11. Additional Requirements:

2.2.3.10.12. Drawing notes shall appear on the drawing. Local notes shall not be numbered

(or lettered), i.e. only one “NOTE 1” shall appear on multi sheet drawings.

2.2.3.10.13. Drawings redrawn without change shall be revision level advanced.

2.2.3.10.14. Revision history shall be maintained in its entirety.

2.2.3.10.15. Added sheets shall be numbered in alphanumeric sequence.

2.2.3.10.16. Parts lists may be integral or separate.

2.2.3.10.17. The angle of projection shall be 3rd angle.

2.2.3.10.18. The English language shall be used.

2.2.3.10.19. When the product baseline is established, all minor waivers or deviations require prior Government concurrence or approval.

2.2.3.10.20. Copies of digitally maintained drawings shall include the following NOTE beneath the last entry of the revision block area: “CAD MAINTAINED CHANGES

SHALL BE INCORPORATED BY THE DESIGN ACTIVITY.”

2.2.3.10.21. An artwork master drawing (master pattern) shall be prepared as an original master. Duplicates of the artwork master drawing, made from the original base artwork of CAD system shall be marked “DUPLICATE REPRODUCTION MASTER. DO NOT REVISE” in the revision block area or adjacent to the pictorial

2.2.3.10.22. Revisions to master drawings shall be made on the original artwork master drawing only.

2.2.3.10.23. Initial release of documents shall have all the required signatures in the title block of the original issue drawing. The revision block shall require signatures. The contractor shall assure and document to the procuring activity’s satisfaction how CAD generated drawings will have these authentication signatures identified and controlled (e.g. by an electronic authorization and approved system).

2.2.3.10.24. When applicable, the inclusion of a revision letter block is mandatory.

2.2.3.10.25. The inclusion of a CAGE code identification block and number is mandatory.

2.2.3.10.26. The total number of sheets for a multi-sheet drawing shall be shown on sheet 1 only. This also applies to computer-generated drawings. The total number of sheets shall refer to active drawing sheets only. Canceled and superseded sheets shall not be counted.

2.2.3.10.27. Separate Selected Item drawings shall be required. Two or more sources are required and shall be listed if two or more sources are readily available. If a second source is not readily available, second source development shall be performed if funded by the TI.

2.2.3.10.28. A Design Control drawing may only be used during the design development of a new item. The contractor’s or Subcontractor’s detail design top assembly drawing for the new item shall be identified in the applicable next higher assembly drawing.

2.2.3.10.29. Wiring Harness and Cable Assembly drawings shall be submitted as a part of the product TDP.

2.2.3.10.30. When an entire note on a drawing is deleted, the note shall be replaced with the word

“DELETED”.

2.2.3.10.31. The crossing out method shall not be used except when making selections that are optional and are part of the printed drawing format.

2.2.3.10.32. Reproductions of drawings maintained and controlled by a CAD system shall not be considered redraws. CAD generated revisions shall be considered “replots” and not “redraws” or “superseding” revisions and shall not be marked as such. However, reproductions of drawings from a CAD system that are not always maintained and controlled by the CAD system shall be considered redraws.

2.2.3.10.33. Revision symbols in the field of the drawing are not required.

2.2.3.10.34. Use of the ZONE column is not required.

2.2.3.10.35. Entry of revision description is not required. Entry of the authorizing document

(NOR) number is sufficient.

2.2.3.10.36. Drawings maintained on a CAD system that have originals for each revision level do not require entry of revision history. Only the current revision information is required.

2.2.3.10.37. The sheet revision level method shall not be used.

2.2.3.10.38. The “all sheets same revision level” method may be used for lists produced by automatic data processing such as parts lists.

2.2.3.10.39. For printed wiring board drawings, an artwork layer revision status block shall also be included on the first sheet.

2.3. TECHNICAL PUBLICATIONS

2.3.1. The PEO IWS technical publications acquisition process includes the use of Modular Specifications

Systems which are a computerized system for producing Technical Manual Contract Requirements (TMCR) documents. The system uses standardized specification modules (requirements) that define format, style and content of the manual.

2.3.2. TMCRs will be provided to the contractor with the Technical Manual Work Package.

2.3.3. The Technical Manuals produced shall meet the requirements of the applicable TMCR as defined and tailored by the ordering TI and Work Package.

2.4. OZONE DEPELETING SUBSTANCES

2.4.1. New drawings, specifications, Engineering Change Proposals, as identified in CDRL C001, Ship Change

Documents, Notice of Revisions and other similar documents generated under this contract shall not include any specification or standard that requires the use of Class I Ozone Depleting Substance (ODS) unless specifically authorized in writing by the PCO. The contractor agrees that when releasing information related to this contract, such release shall include a statement to the effect that the project or effort depicted was or is sponsored by the agency set forth below:

MK 41 Vertical Launching System (VLS) Program Program Executive Office for Surface Launching Systems Code: PEO IWS 3L 2450 Crystal Drive Suite 700 Arlington, VA 22202

2.4.1.1. For the purpose of this SOW, “Information” includes but is not limited to news releases, articles, manuscripts, brochures, advertisements and motion pictures, speeches, trade association meetings, symposia, etc.

2.4.1.2. Nothing in the foregoing shall affect compliance with the requirements of the SOW of this contract entitled “Military Security Requirements”.

2.4.1.3. All material, except scientific articles or papers published in scientific journals, must, in addition to any notices or disclaimers by the contractor, also contain the following disclaimer: Any opinions, findings and conclusions or recommendations expressed are those of the author(s) and do not necessarily reflect the views of the Naval Sea Systems Command. The contractor further agrees to include this disclaimer in any subcontract awarded as a result of this contract.

2.5. NON-DISCLOSURE OF INFORMATION

2.5.1. It is recognized by the parties that the contractor performing work under this contract may have access to different kinds of information which must not be disclosed either outside of the Government, to other Government personnel than those having authorized access to the information or to employees of the contractor other than those assigned to this contract. The information which must not be disclosed includes, but is not limited to: National security information or related material require a substantial degree of protection which has been classified under “Top Secret”, “Secret” or “Confidential” categories;

internal personnel rules and practices; commercial or financial information obtained from a person outside the Government which is privileged or confidential; inter-agency or intra-agency memoranda or letters relating to the deliberative process of the Government; and information which would constitute a clearly unwarranted invasion of personal privacy in the performance of work required to carry out this contract. The contractor shall take suitable steps to prevent disclosure of such information to any party other than the Government or the party outside the Government whose information is uninvolved. The contractor agrees to indoctrinate company personnel who will have access to this information as to the nature of the confidential relationship under which the contractor has possession of such information and shall stress that the information shall not be disclosed to any other party or the contractor personnel who do not need to know the contents thereof for the performance of this contract. Contractor personnel shall also be informed that they shall not engage in any other action, venture or employment wherein this information will be used for the profit of any party other than the party furnishing the information.