A05 SOW.docx

DOCX document 52 KB Posted

Attached to
WEAPON SYSTEM ANALYSIS, MODELING AND SIMULATION SOFTWARE UPDATE, AND TEST SUPPORT
Solicitation number
N6893625R0009
Issued by

About this file

This Statement of Work (SOW) from the Naval Air Warfare Center Weapons Division (NAWCWD) in China Lake defines RDT&E support services for weapon performance and effects analysis, modeling and simulation software updates, and test support. The work covers multiple weapon systems including AIM-9, AIM-120 AMRAAM, AGM-65 Maverick, AGM-154 JSOW, Tomahawk, Excalibur, TOW, Standard Missile, ESSM, Talon, RAM, Pyros, SDB II, and Griffin missiles.

The key requirements include performing lethality analyses, creating target models, conducting simulations, evaluating weapon system performance, updating and validating lethality modeling tools, and providing test planning/support/analysis. The work will be performed 90% at contractor facilities and 10% at government sites including NAWCWD China Lake, Naval Base Ventura County, White Sands Missile Range, Eglin AFB, and NAS Patuxent River. Personnel must be U.S. citizens with appropriate security clearances up to TOP SECRET/SCI. The contractor must maintain capability to handle classified information and host classified meetings for up to 20 people. The period of performance begins August 2024 with amendments made in October 2024.

View the file

On GovTribe

Work with this file

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

Text version

CUI

STATEMENT OF WORK

WEAPON SYSTEM ANALYSIS, MODELING AND SIMULATION

SOFTWARE UPDATE, AND TEST SUPPORT

06 AUGUST 2024

Amended

22 OCTOBER 2024

Prepared by:

Naval Air Warfare Center Weapons Division China Lake, CA 93555

DISTRIBUTION STATEMENT D:

Distribution authorized to Department of Defense and U.S. DoD contractors only; Critical Technology; 30 July 2024. Other requests for this document shall be referred to Commander: Naval Air Warfare Center, Weapons Division (Code D55410), 1 Administration Circle, China Lake, CA 93555-6100.

SCOPE AND BACKGROUND

1.1 SCOPE

This Performance Work Statement (SOW) defines the Research Development Test and Evaluation (RDT&E) support services required for weapon performance and effects analysis, Modeling and Simulation (M&S) analysis software updates, and test support for United States Navy weapon systems including, but not limited to: Air Intercept Missile (AIM-9), AIM-120 Advanced Medium Range Air-to Air Missile (AMRAAM), AGM-65 Maverick, AGM-154 Joint Standoff Weapon (JSOW), Tomahawk Missile, XM982 Excalibur, BGM-71 TOW, Standard Missile, Evolved Sea Sparrow Missile (ESSM), Talon, Rolling Airframe Missile (RAM), Pyros, Small Diameter Bomb II (SDB II), and Griffin Missile.

This statement of work describes the technical requirements in the following general areas:

1.1.1 Studies and evaluations of weapon lethality performance

1.1.2 Updates to weapon lethality modeling software

1.1.3 Verification and validation of lethality modeling software

1.1.4 Target model creation

1.1.5 Test planning, support, analysis, and reporting

1.2 BACKGROUND

The mission of the Naval Air Warfare Center Weapons Division (NAWCWD) is to provide the United States Armed Forces with effective and affordable integrated warfare systems and life-cycle support to ensure battlespace dominance. NAWCWD performs RDT&E software integration, interoperability, modeling and simulation; and supports Network Centric Warfare for guided missiles, complex and advanced weapons, and weapon systems. NAWCWD performs RDT&E, in-service support for guided missiles, free-fall weapons, targets, support equipment, crew systems, and electronic warfare; and integrates weapons and avionics on tactical aircraft. NAWCWD operates the Navy’s western land and sea range test and evaluation complex; and develops and applies new technology to ensure battlespace dominance.

2.0 APPLICABLE DOCUMENTS

· DoD National Industrial Security Program Operating Manual (NISPOM), 32 CFR Part 117, 24 Feb 2021

· SECNAVINST 5510.36, Information Security Program, 12 Jul. 2019

· DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar. 2020

· OPNAVINST 3440.17A, Navy Installation Emergency Management Program, 9 Jul. 2018

2.1 Standard requirement documents (Government and Industry Specifications and Standards), reference texts, specific design requirements, and other references will be defined by individual Task Orders (TOs).

2.1.1 The Government will provide all necessary reference documents not generally available to the contractor when required by individual TOs. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to these requirements only as defined by individual TOs.

2.2 SPECIFICATIONS AND STANDARDS

National and international standards are fundamental to the acceptable performance of this requirement. American National Standards Institute (ANSI) and International Standards Organization (ISO) standards may be invoked under individual TOs. All commercially available hardware and software acquired by the contractor in response to a Government requirement shall be inventoried and must comply with the appropriate standards specified in the task order. All hardware shall be returned to the Government for proper disposition at the end of the TO or contract, whichever is more appropriate. Additional standards and specifications with a variety of origins and Department of Defense (DoD) standards will be utilized to the extent necessary to promote maximum utility, flexibility, and economy.

3.0 REQUIREMENTS

The following paragraphs describe technical task areas to be performed by the contractor. Work to be performed, required data deliverables, and applicable governing documents shall be specifically described in task orders to be issued by the Contracting Officer and shall be within the parameters of one or more of the tasks listed below. This work may be performed on assigned systems, subsystems, equipment, and/or components. The contractor shall provide a Contractor’s Monthly Progress, Status and Management report that shows planned expenditures over the life of the contract, task orders, and comparison of planned and actual expenditures. Technical tasking progress shall be summarized to include accomplishments, schedule compliance, issues, and risks to completion of the contract and task orders. (CDRL A001)

3.1 Design and Development

3.1.1 Design Analyses:

3.1.1.1 The Contractor shall perform lethality analyses on weapon systems. The Contractor shall create target models for simulation. The Contractor shall perform simulations against target models to determine lethality metrics. (CDRL A002)

3.1.1.2 The Contractor shall evaluate weapon system performance. The Contractor shall model and simulate the weapon system performance while in flight and during target engagement. (CDRL A002)

3.1.2 Software Development:

The Contractor shall update lethality modeling tools. The Contractor shall verify and validate lethality modeling tools. (CDRL A002)

3.2 Test and Evaluation

3.2.1 Test Planning:

The Contractor shall provide pre- and post-test simulations of expected system performance in test scenarios. The Contractor shall develop test exercise geometry and constraints necessary to implement test scenarios. The Contractor shall develop or evaluate and provide comments on test plans and procedures. The Contractor shall submit an evaluation report on the adequacy of such plans and provide rationale and assumptions. The Contractor shall provide inputs to detailed test procedures implementing test plan requirements. (CDRL A003)

3.2.2 Test Support:

The Contractor shall attend tests performed at both Government and private test sites to review the appropriate test requirements and provide analytical evaluations during testing and procedures, monitor the test being conducted, and document the test. (CDRL A003)

3.2.3 Test Analyses and Reports:

The Contractor shall review test data and perform analyses of the performance of units under test. The Contractor shall collect, review, prepare test data and documents and publish test documents and reports. The Contractor shall evaluate test report content and recommend changes with rationale. (CDRL A002)

4.0 GENERAL INFORMATION:

4.1 Compatibility - The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of TOP SECRET. The current operating environment required for this contract includes:

· Microsoft Windows

· Microsoft Project

· Microsoft Office

· Adobe Acrobat Pro

· Internet access

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications using current Government versions and if necessary, upgraded versions used during the performance period of the contract. The Contractor shall maintain state-of the-art anti-virus software and ensure that all media are virus free when delivered. The Contractor, and Contractor personnel, shall be capable of Internet and LAN communications, real-time communications (both voice and data transfer capabilities) with the Contracts Department, the Contracting Officer Representatives (COR), and all designated Technical Points of Contact (TPOC), during working hours whether at the Contractor work site or on travel.

4.2 Work Location and Facilities

4.2.1 Work location: Approximately 10 percent of work will be performed at Government site and 90 percent of work to be performed at Contractor site. Government site(s) include, but are not limited to: NAWCWD, China Lake, California; Naval Base Ventura County, California; White Sands Missile Range, New Mexico; Eglin Air Force Base, Florida; and Naval Air Station Patuxent River, Maryland

Contractors performing on-site support will be provided workspaces that include desk units, phones, and the computing equipment necessary for performance. The contractor shall be responsible for providing qualified personnel and all other necessary equipment to accomplish SOW requirements.

4.2.2 Meeting support: In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to TOP SECRET with the capacity to support a minimum of 20 persons and have contractor furnished telephone and VTC capability as well as sufficient equipment to conduct meetings with presentations including compatible software as required in Paragraph 4.1.1.

4.2.3 Contract Status Reporting. The contractor shall provide the following documentation.

4.2.3.1 Monthly Progress and Financial Status Report: The contractor shall prepare and submit a progress and status report in accordance with the Contract Data Requirement List (CDRL A001). The report shall include work accomplished since submittal of the last report. It shall identify work that is in process, along with any risks, challenges, or issues; the report shall also include both monthly and cumulative man-hours expended by labor category and personnel, labor costs expended by labor category and personnel, materials purchased, and travel costs, overtime, and hazard pay. All hours and costs must be broken down by CLIN and ACRN. All travel costs must be itemized, by each employee, to show individual costs for lodging, per diem, fuel, etc. The monthly report shall also include the funding remaining on the order, estimate to completion (ETC) and estimate at completion (EAC) forecasts.

4.2.4 Work Schedule to include Government Installation Work Schedule (CWS), holidays, and installation closure.

4.2.4.1 Work Schedule:

a. The Holidays applicable to this contract are: New Year's Day, Martin Luther King's Birthday, President's Birthday, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veteran's Day, Thanksgiving Day, and Christmas Day.

b. If any of the above holidays occur on a Saturday or Sunday, or alternate Friday, then such holiday shall be observed as they are by the assigned Government employees at the using activity.

c. The Naval Air Warfare Center Weapons Division works a 4/5/9, also referred to as a Compressed Work Schedule (CWS). Therefore, alternate Fridays are not a part of the normal workweek for work performed on-site at a Naval Air Warfare Center Weapons Division site. Most of NAWCWD Government offices are closed on alternate Fridays.

d. No deviation in the normal workweek will be permitted without express advance approval by the designated Contracting Officer with coordination of the using departments.

The Contractor may allow its employees to work a CWS schedule provided the requirements of this SOW are met. If the contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government to the COR.

4.2.4.2 Installation closure: When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.

In very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.

4.2.4.3 Telework: Telework eligibility may be authorized, by the COR, through individual task orders, both in the Contiguous United States (CONUS) and outside the Contiguous United States (OCONUS). Contractor work schedules shall be coordinated with the COR to ensure: 1) coverage during critical periods and critical tasking, 2) coordination of tasks involving other contractors, and 3) security compliance for buildings/areas where access is controlled. The Contractor, upon notification to, and concurrence from, the Contracting Officer's Representative (COR) that the employees' work tasking is eligible for telework, may utilize alternate worksites/locations and telework to support continued performance of its contract in accordance with company policy. Contractor discretion is required when making alternate worksite and telework decisions based upon the nature of support provided by the employees. In the event telework is utilized, the Contractor remains responsible for performance, and compliance with any applicable cost accounting standards and contract cost principles/procedures. The contractor shall adhere to all applicable federal laws and regulations and individual Department of Defense (DoD) Service guidelines shall be adhered to as well.

4.3 Travel: Temporary travel to other locations in support of program tasking is required. The Contractor shall be responsible for all transportation, billeting, and messing for the Contractor personnel except in those cases where Government transportation, billeting, and messing are the only services available. All travel costs will be in accordance with the Joint Travel Regulations. Travel may include general and administrative expenses but shall not include profit.

The Contractor shall be required to perform CONUS and OCONUS travel for the tasking defined in this SOW. Destinations will be defined based on individual task order requirements.

4.4 Material: All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Material costs may include general and administrative expenses but shall not include fee.

4.5 Contractor Acquired Property: Property acquired, fabricated, or otherwise provided by the contractor for performing this requirement, where the Government has title, shall be managed IAW FAR 52.245-1 until such time as the Government takes ownership or the property is disposed. Delivery of CAP shall be completed IAW DFARS PGI 245.402-71-Delivery of contractor-acquired property.

5.0 DELIVERABLES

CDRL
DID

Title

A001

Contractor’s Monthly Progress, Status and Management Report

A002

Technical Report-Study/Services- Design Engineering & Review Reports, Chemical Analyses Reports, Physics Analysis Reports, Environmental Services Reports, Technology Support Reports

A003

Test Plans/ Test Procedures

A004

Operations Security (OPSEC Plan)

A005

Program Protection Implementation Plan (PPIP)

6.0 SECURITY

6.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

1. The individual's name, date and place of birth, position title, and current citizenship.

2. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

3. A statement of the unusual expertise possessed by the applicant.

4. A statement that access will be limited to a specific government contract (specify contract number).

5. A statement that the Contractor has obtained an export license for the information required to perform the contract.

6.2 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR).

6.2.1 SAAR: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR forms are available at: https://www.esd.whs.mil/Portals/54/Documents/DD/forms/dd/dd2875.pdf. SAAR forms shall be submitted to the Contracting Officer’s Representative (COR).

6.2.2 Command Access Cards (CAC) / Local Badges: Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all Department of Defense and NAWCWD instructions. All CACs and identification badges issued to Contractor employees shall be returned to the Contracting Officer’s Representative following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with local security and facility requirements. To maintain access to Navy IT resources, the contractor shall ensure completion of the most current initial and annual DOD Cyber Awareness Challenge training. The contractor shall ensure completion of a Cyber Awareness Training Certificate or the latest version thereof, monitor expiration of requisite background investigations, and initiate re-investigations as required. If requested, the contractor shall provide to the COR or designated SAAR Government Sponsor documentation sufficient to prove that it is monitoring/tracking the SAAR requirements for its employees who are accessing Navy IT resources. For those contractor personnel not in compliance with the requirements of this clause, access to Navy IT resources will be denied/revoked.

6.2.3 DD-254: The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as CUI”. Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

6.2.3.1 Personnel Security. The contractor shall provide personnel with the appropriate personnel security clearance levels for the work to be performed. Performance of some task orders will require use and/or storage up to SCI and unescorted access to SCI areas. In addition, certain deliverables on this IDIQ, to be determined at the task order level, will contain SCI as defined in paragraphs 3.3.1 and 3.3.2. Access to TOP SECRET information is required in the performance of this contract and shall be in accordance with the 32 CFR Part 117, Feb 2021, National Industrial Security Program Operating Manual (NISPOM), applicable DoD personnel security regulations, and DoD Contract Security Classification Specification (DD Form 254). The contractor shall maintain sufficiently cleared personnel to perform the tasks required by this SOW IAW the DD Form 254 and the contract. All contractor personnel shall possess the requisite security clearance, accesses, and need-to-know commensurate with the requirements of their positions.

All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable Tier 1 (T1) investigation.

6.2.4 Information Security. Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAVISNT 5510.36B. The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with NISPOM 32 CFR Part 117, 24 Feb 2021, and SECNAVISNT 5510.36B. CUI information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDI 5200.48, Controlled Unclassified Information (CUI). Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

6.2.4.1 Marking: All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDI 5200.48, Controlled Unclassified Information (CUI). Contractor shall not store or transmit CUI on personal information technology systems or via personal e-mail. Unclassified e-mail containing any DoD CUI shall be encrypted. Prior to sending CUI to any non-Navy Marine Corps Internet (NMCI) addressees, the sender must first positively verify all recipients are authorized access to CUI and have need-to-know. Non-NMCI recipients must have a DoD compliant Private Key Infrastructure (PKI) certificate that enables electronic transmission via unclassified networks while protecting the CUI with a digital signature and encryption.

6.2.4.2 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.

6.2.5 Communications Security (COMSEC). The contractor will require access to COMSEC at government/contractor locations. U.S. cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is used, is for official use only. Publication or release of any related COMSEC information by any means, by the contractor, without prior written approval of the contracting officer is prohibited. The contractor must be a U.S. citizen, have a final Government security clearance with the appropriate personnel security background investigation for the level of classification involved, have strict need-to-know, have the appropriate COMSEC briefing before access is granted, and granted access only in conformance with procedures established for the particular type of COMSEC information involved. The contractor shall adhere to the DD Form 254 COMSEC security requirements, facility COMSEC material control and operating procedures, and all applicable COMSEC regulations, instructions, and policies. Prior approval from the Government Contracting Activity is required in order for a prime contractor to grant COMSEC access to a subcontractor.

6.2.6 Operations Security (OPSEC). The contractor shall comply with the OPSEC requirements outlined within the DD Form 254.The Contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract. The contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The OPSEC program shall be in accordance with DoD and DON operations security (OPSEC) requirements, to include:

1. Assignment of responsibility for OPSEC direction and implementation

2. Planning guidance for the use of the OPSEC Process to identify vulnerabilities and apply applicable countermeasures (Contact NAWCWD Industrial Security Office for a current OPSEC Annex and CI Guide.)

3. Establishment of OPSEC education and awareness training.

4. Provisions for management, annual review, and evaluation of OPSEC programs.

5. Oversight for accountability of OPSEC requirements to subcontractors.

The contractor shall prepare an Operations Security Plan for government review in accordance with the (CDRL A004)

6.2.7 Program Protection Plan (PPP): A Program Protection Plan (PPP) and supporting annexes will be provided as Government Furnished Information (GFI). The contractor will follow guidance in the PPP and annexes for protection of Critical Program Information (CPI) identified in the PPP. The contractor will, as requested by the government, provide input to updates of the PPP and associated annexes. Any modifications or deviations to the PPP or annexes will be made in writing by the Program Manager (PM). Requests for clarification of the PPP or annexes will be made by the contractor to the PM not later than thirty (30) days from receipt of the PPP, its annexes, or updates thereof.

6.2.8 Program Protection Implementation Plan (PPIP):

6.2.8.1 Security: The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information and to control distribution of controlled unclassified and classified information in accordance with the NISPOM 32 CFR Part 117, 24 Feb 2021. The DoD Contract Security Classification Specification, DD Form 254 Attachment X, defines program specific security requirements. All Contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, classified equipment and materials and other equipment and materials.

6.2.8.2 Program Protection Implementation Plan (PPIP): The Contractor shall develop (or update, as applicable) the PPIP to ensure effective and efficient protection of essential program information, technologies and systems, to ensure the following:

· The Security Management structure.

· The CPI physical locations under the Contractor’s or subcontractors’ control.

· The vulnerability of the CPI under the Contractor’s or subcontractors’ control to intelligence collection in the following areas: Human Intelligence (HUMINT); Open-Source Intelligence (OSINT); Signals Intelligence (SIGINT); Imagery Intelligence (IMINT); Computer Network Operations (CNO).

· Countermeasures at each site where CPI is held, from the following security domains (as applicable): physical security; personnel security; telecom and network security; application/systems development; cryptography; security architectures; operational security network and IT access control.

· Any special handling procedures required for CPI, and procedures for recovering CPI in the event of a mishap. The Contractor shall address these procedures for all phases of the program, including (but not limited to): RDT&E; production; operations; maintenance; logistics; transportation; training; disposal.

· Procedures for ensuring compliance with U.S. Government export statutes and regulations.

· Procedures for public release of program information. (CDRL A005)

During performance of this contract, the contractor may require access to Government facilities and Government furnished information. The contractor shall identify and request approval from the technical point of contact (TPOC) for each person expected to require access to a Government facility and authorized to open/close the facility.

7.0 PUBLIC DISTRIBUTION

Public Release. Disclosure of information is covered by DFARS 252.204-7000 Disclosure of Information, incorporated in Section I of the contract. Concerning subsection (a)(2), “information otherwise in the public domain” is information officially released into the public domain, e.g. via Distribution Statement A, and does not include information in the public domain that has not been officially released. For disclosure of unclassified information that has not been officially released, the contractor must seek specific approval from the Contracting Officer, with approval from the NAWCWD Public Affairs Office (PAO).

CUI

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