16-R-0006_RFP.docx

N68936-16-R-0006

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

Email address: david.channer@navy.mil

U.S. Postal Service Mailing Address:

Direct Delivery Address (UPS, FedEx, etc.):

Section B - Supplies or Services and Prices

Routine Structures Engineering Analysis

FFP

The contractor shall perform and provide routine structural engineering analysis, structures design and solid modeling and advanced composites design analysis, in accordance with the Statement of Work (SOW) Para. 3.2. The level of effort for the performance of this CLIN is based upon an anticipated total estimated level of effort NTE 115,200 man-hours of direct labor.

Year 1 FOB: Destination

NET AMT

Hours

Man Hour Estimate/Analysis Plan

CPFF

The Contractor shall provide MH estimate that shall include a master schedule (and key dates) along with a MH breakdown for task estimates that are greater than 500 MH in accordance with the Statement of Work (SOW) Para 3.3. The level of effort for the performance of this CLIN is based upon an anticipated total estimated level of effort NTE 23,040 man-hours of direct labor.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Hours

Major Structural Analysis

CPFF

All major structural analysis performed by the Contractor shall be in accordance with the approved Analysis Plan (AP) and master schedule in accordance with the Statement of Work (SOW) Para 3.4.1. The Contractor shall be subject to progress reviews at 25% and 75% completion based on MH expended in accordance with the Statement of Work (SOW) Para 3.4.2. The level of effort for the performance of this CLIN is based upon an anticipated total estimated level of effort NTE 92,160 man-hours of direct labor.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Lot

Other Direct Costs (ODC's) Travel

COST

Travel costs in support of SOW Section C.

ESTIMATED COST

NSP

CDRLS in support of SOW Section C and Exhibit (a) DD Form 1423-1

CLIN 1 - Routine Structural Analysis

Labor Category

Engineer/Scientist III

Engineer/Scientist IV

Engineer/Scientist V *

Technical Writer II

Total Hours

* Key Labor Category

CLIN 2 - Man Hour (MH) Estimate / Analysis Plan (AP)

Labor Category

Engineer/Scientist III

Engineer/Scientist IV

Engineer/Scientist V *

Technical Writer II

Total Hours

* Key Labor Category

CLIN 3 - Major Structural Analysis

Labor Category

Engineer/Scientist III

Engineer/Scientist IV

Engineer/Scientist V *

Technical Writer II

Total Hours

* Key Labor Category

(b) FAR Clause 52.232-20, "Limitation of Cost" applies to fully funded orders and FAR Clause 52.232-22, "Limitation of Funds" applies to incrementally funded orders. Nothing in this clause amends the rights or responsibilities of the parties hereto under either of those two clauses. In addition, the notifications required by this clause are separate and distinct from any specified in either FAR Clause 52.232-20 or FAR Clause 52.232-22.

Section C - Descriptions and Specifications

STATEMENT OF WORK

STATEMENT OF WORK

F/A-18 AND EA-18G FLEET SUPPORT TEAM

ENGINEERING STRESS ANALYSIS AND DESIGN SERVICES

16 February 2016

SECTION C DESCRIPTIONS AND SPECIFICATIONS

1.0 INTRODUCTION

1.1 BACKGROUND. The Naval Air Systems Command (NAVAIR), F/A-18 & EA-18G Fleet Support Team (FST) In-Service Support Center (ISSC) at Fleet Readiness Center South West (FRCSW) Naval Air Station (NAS) North Island, California, commonly referred to as the F/A-18 FST, has requirements applicable to both the F/A-18 and E/A-18G (all Type/Model/Series (T/M/S)). These requirements are for improving the overall quality, timeliness, and efficiency of cognizant support systems, products and services.

The F/A-18 engineering team provides technical support on various aircraft repair and sustainment activities as well as aircraft operational service life extensions programs. Some of the aircraft repair and sustainment efforts include on-going depot repair production work such as the Planned Maintenance Interval (PMI-1 and PMI-2) and In-Service Repair (ISR). Engineering support for these activities is carried out by providing stakeholders with engineering repair instructions through Request For Technical Information (RFTI), Request for Engineering Information (REI) or Temporary Engineering Instruction (TEI). This type of support shall be referred as Tactical Engineering Support Services in this SOW. Support in the aircraft operational service life extension is accomplished through the Service Life Assessment Program (SLAP) and Service Life Extension Program (SLEP). The SLAP/SLEP program is part of the Service Life Management Plan (SLMP) and was designed to introduce High Flight Hour (HFH) inspections and modifications to the F/A-18. Select locations in the airframe were analyzed to evaluate their life with a fleet usage based fatigue spectrum. The United States Navy (USN) currently conducts inspections of F/A-18 aircraft as they reach 8,000 Flight Hours (FH) under the direction of the HFH bulletins. Many of the locations analyzed had lives less than the goal of 10,000 FH and require inspections and modifications to extend the aircraft service life. This type of support will be referred as Strategic Engineering Support Services in this SOW.

1.2 OBJECTIVE. The scope of this SOW is to perform engineering stress analysis and design modification on aircraft repairs for the purpose of increasing reliability, reducing total ownership cost, and obtaining additional service life from the F/A-18 weapon system. In support of this effort, the Contractor shall provide technical analysis and design services for both the Tactical and Strategic Engineering Support Services for the various F/A-18 maintenance programs.

1.3 SCOPE.

1.3.1 The Contractor shall provide support to the various Fleet Readiness Centers (FRC) which include FRCSW at Naval Air Station North Island, CA; FRCSE at Naval Air Station Jacksonville, FL; FRCMA at Naval Air Station Oceana, VA; FRCW at Naval Air Station Lemoore, CA; FRCNW at Naval Air Station Whidbey Island, WA; FRCWP at NAF Atsugi, Japan; Marine Corps Air Station (MCAS) Miramar, CA; MCAS Yuma, AZ; MCAS Beaufort, South Carolina; and any other Naval and Military installations as detailed in the requirements section of this SOW.

1.3.2 The Contractor shall provide engineering stress analysis and design services in the areas listed below which are further defined in Section 3.

a. Structures Engineering Stress Analysis

b. Structures Design and Solid Modeling

c. Advanced Composite Design and Analysis

2.0 APPLICABLE DOCUMENTS

2.1 INSTRUCTIONS/STANDARDS/PUBLICATIONS. The following is a list of known documents needed and referred to in the performance of the services required by this SOW. The documents listed below are the latest revisions at the writing of this SOW and are necessary to fully understand and perform the tasks described herein. Unless otherwise specified, the revision level and date of the documents cited or referred to in this solicitation are the revisions listed in the Department of Defense ASSIST Database (http://quicksearch.dla.mil/) that are in effect on the date of contract award. When required, publications are to be in accordance with DOD 5010.12-M.

The Government will provide all necessary reference documents not generally available to the Contractor as required. The documents prefaced with an asterisk (*) are proprietary documents that contain proprietary information. Access to such documents shall be in accordance with the requirements stipulated in Section 2.8 of this SOW.

a. DOD 5010.12-M, Procedures for the Acquisition and Management of Technical Data, May 1993.

b. OPNAVINST 3432.1A, Operations Security, 4 August 2011.

c. SECNAVINST 5510.30B, Department of the Navy (DON) Personnel Security Program (PSP) Instruction, 6 October 2006

d. SECNAVINST 5510.36A, Department of the Navy (DON) Information Security Program (ISP) Instruction, 6 October 2006.

e. DOD 5200.01V4, DOD Information Security Program: Controlled Unclassified Information (CUI), 24 February 2012.

f. DODD 5230.25, Withholding of Unclassified Technical Data from Public Disclosure, 06 November 1984, and Change 1, 18 August, 1995.

g. COMNAVAIRFORINST 4790.2B CH-1, The Naval Aviation Maintenance Program (NAMP), 15 June 2013.

h. NAVAIRINST 13120.1D CH-1, Fixed Wing Aircraft Structural Life Limits, 02 July 2013.

i. MMPDS-09, Metallic Materials Properties Development and Standardization (MMPDS), April 2014.

j. ANSI/NISO-Z39.18-2005, Scientific and Technical Reports – Preparation, Presentation, and Preservation, (R2010).

k. SOP NI F/A-18 AG-002-11 plus Amendment 1 & 2, F/A-18 Stress Analysis Submittal Standard Operating Procedure, Rev. A.

l. NAVAIR SWP4330-001, Standard Work Package, Strength Analysis and Documentation for Repairs and Modifications.

m. F18A-D Structural Areas Affected by Dynamic Loads, Jim Elgie, NAVAIR, North Island, 22 October 2012.

n. F18A-D High Flight Hour Aircraft Disposition Guidance, Jim Elgie, NAVAIR North Island, 02 July 2013.

o. Drawing Requirements Manual (DRM), Eleventh Edition, Global Engineering Documents, Change Date 2008.

p. Engineering Drawing Practices, American Society of Mechanical Engineers (ASME), ASME Y14.100-2013, 30 July 2013.

q. NAVAIR 01-1A-21, General Composite Repair, 1 August 2011.

r. NAVAIR 01-1A-08, Structural Hardware Manual, Change 3, 15 January 2013.

s. * MAC 339, McDonnell Aircraft Company Structures Handbook, Rev B, 01 June 1973.

t. * MDC A3960, F/A-18 A/B Structural Description Report, Rev A, 29 September 1978.

u. * MDC A4241, F/A-18 A/B/C/D/E/F Thermal Design and Evaluation, Rev B, 19 February 1993.

v. * MDC A5253: F/A-18 A-D Material Substantiating Data Analysis Report, 01 August 1978.

w. * MDC A7052, F/A-18A/B/C/D Composite Development Tests, January 1981.

x. * MDC 91B0330, McDonnell Douglas Composites Manual, Rev B, 23 December 1992.

y. * MDC 91B0615, F/A-18E/F Fastener Usage Policy, Rev A, 15 January 1994.

z. * MDC 92B0355, F/A-18 E/F Structural Description, CDRL Seq. No. A00N, Rev D, 18 October 1995.

aa. * MDC 92B0523, F/A-18E/F Supplemental Design Criteria and Analysis Guidelines, 01 November 1992.

ab. * MDC 93B0068, F/A-18E/F and EA-18G Material Substantiating Data Analysis Report, Rev T. 24 December 2008.

ac. * MDC 94B0043, F/A-18E/F Advanced Material Repair Development Program, Repair Guidance Document, Rev D, 23 December 1998.

ad. * MDC 97A0107, F/A-18A/B/C/D Bonded Joint Analysis Methodology (BJAM) Manual, Rev E, 01 November 2013.

ae. * BOE-STL 98A0089, F/A-18E/F and EA-18G Bonded Joint Analysis Methodology (BJAM) Manual, Rev B, 15 July 2014.

af. * BOE-STL 2005A0112, F/A-18E/F Depot Repair Guidance Document, 21 December 2005.

ag. F/A-18E/F-352C-3963, F/A-18E/F Composite Structure Disposition Manual, Rev B, 15 June 1995.

ah. EC-433-000-002, F/A-18A/B/C/D High Flight Hour (HFH) Wing Skin Analysis Description and Guidelines, Rev A, 04 August 2014.

ai. AS9100C, International Quality Management Systems - Requirements for Aviation, Space and Defense Organizations, 15 January 2009.

aj. AS9110B, Quality Maintenance Systems - Aerospace - Requirements for Maintenance Organizations, 26 April 2012.

ak. DoD 5205.02-M, DoD Operations Security (OPSEC) Program, March 6, 2006

al. FRCSWINST 13600.2, Translating 2-D Structural Drawings to 3-D Solid Models

am. FRCSWINST 4790.4, Local Manufacturing of Aviation Parts, 12 April 2012

an. * MDC 92B0273, F/A-18 Hornet Fatigue Analysis Procedure Manual (FAPM), Rev D, 21 February 2014.

ao. * MDC A8500, NARF Fatigue Information Report, 14 July 1986.

ap. * Applicable SLEP Decision Memo (SDM) and Contract Data Requirements List (CDRL), Technical Direction Letter (TDL), CTRD and ALL-METH to be provided by AIR 4.3.3.1 Strength Branch Lead or the designated Lead Stress Analyst as required.

aq. DoD 5400.7-R, DOD Freedom of Information Act (FOIA) Program, September 1998.

ar. SECNAV M-5510.36, DoN Information Security Program, June 2006.

as. DoDD 5205.02E, National Security Decision Directive 298, January 22, 1988.

at. ITAR 22 CFR 120-130, International Traffic In Arms Regulations (ITAR), 01 April 2014.

au. EC-433-000-007, Finite Element Model Verification Guidelines, 9 September 2015.

av. NAVAIR 22P4330-006, Standard Skill Package for Lifeworks Engineer Certification.

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 the requirements defined in this SOW.

The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this Contract, which reports to PBIS-IT, without a Naval Air Systems Command (NAVAIR) Command Information Officer (CIO) approved NAV-IDAS ITPR.

2.2 Clinger-Cohen Act:

The contractor shall conduct analysis of program/project needs, acquisition strategy and program artifacts to identify and capture specific factors required to satisfy the 11 elements of Clinger-Cohen Act (CCA) compliance listed in DODI 5000.02, Enclosure 1, Table 9. Using Microsoft Word, the contractor shall prepare a CCA compliance matrix following the organization and appearance of Table 11 with additional separate columns for the display of artifact: titles, date(s) of approval, page number(s), and paragraph or section number(s). The right-hand column shall include an embedded object permitting the reader to open unclassified artifacts. The column shall identify classified artifacts and shall describe approved classified channels for access of classified artifacts. The contractor shall support the program manager during CCA compliance review and assist in responding to reviewer comments if and when additional supporting information or revisions are required.

Updating approved CCA compliance packages: For updates of approved CCA compliance packages, the contractor shall conduct analysis of program/project needs, acquisition strategy and program artifacts to identify and to determine if each of the Eleven Elements of CCA has changed and if no change has occurred, a notation stating “no change” shall be entered in the CCA compliance matrix. If changes have been found, the Contractor shall update the CCA compliance matrix to reflect the changes.

The contractor shall support the program manager during CCA compliance review and assist in responding to reviewer comments if and when additional supporting information or revisions are required.

2.3 System Software / Application Compliance:

All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), Department of the Navy (DON)/Naval Air Systems Command (NAVAIR) Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates.

2.4 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services:

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. Office of Management and Budget Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised. http://www.whitehouse.gov/omb/circulars_a130_a130trans4

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04. <http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf>

c. Section 508 Amendment to the Rehabilitation Act of 1973. <https://www.section508.gov/content/learn/laws-and-policies>

d. Department of Defense Web Policies and Guidelines. <http://dodcio.defense.gov/dodwebpolicy>

e. Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team Website. <http://www.public.navy.mil/fcc-c10f/niocnorfolk/Pages/AboutWRA.aspx>

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B. <http://www.navy.mil/navydata/internet/secnav5720-47b.pdf>

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines). To request this policy contact the NAVAIR CIO office – 7.2.2 Applications Integration team – Web Manager: Shane Malamphy at 301- 342-1825.

h. Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN 061/08). <http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/NAV2008/NAV08061.txt>

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07. <http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/NAV2007/NAV07145.txt> Source: IRM Office UPDATED: August 2015 Page 7

j. DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators. <http://www.doncio.navy.mil/ContentView.aspx?ID=577>

k. Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible Navy Sites (ALCOM 129/09). <www.public.navy.mil/fcc-c10f/niocnorfolk/Documents/NTD-08-09.txt>

2.5 Software Development/Server Procurement:

Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.

2.6 Cybersecurity:

The contractor shall conduct investigation and analysis of acquisition program artifacts such as but not limited to Initial Capabilities Document (ICD), Capability Description Document (CDD), Capability Production Document (CPD), Navy urgent operational need (UON) and Marine Corps urgent universal need statement (UUNS), joint urgent operational needs (JUONs), threat assessments and acquisition strategies (AS). Knowledge gained from this analysis shall be used when developing the Cybersecurity Strategy (CS) needed to steer and inform the program’s development of a Security Plan (SP) in accordance with DoDI 8510.01, of 12 March 2014.

As a minimum, hardware, firmware, software, documentation (data deliverables) and/or Information Technology (IT) services delivered by this contract shall be in compliance with the following References:

The contractor shall conduct investigation and perform analysis including; criticality analysis, threat assessment and vulnerability assessments. All findings and recommendations shall be reported to the government in technical reviews and submitted as written reports or documents as listed in Contract Data Requirements Lists. The contractor shall support government efforts needed for Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems to successfully categorize the system, achieve favorable assessment for selection, implementation and testing of security controls and authorization (approval to operate) before use or interconnection in an operating environment in accordance with references (a), (b) and (c). This includes IT that is standalone and IT that is connected to other systems, networks or enclaves. Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems delivered prior to award of this contract but included in the performance of this contract may have been delivered in compliance with Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) and as such shall require transition to Risk Management Framework cybersecurity compliance. Transition planning proposed or performed under this contract shall be in compliance with reference (b) Enclosure 8, Figure 2 and all hardware, firmware and software deliverables shall be capable of receiving Authorization to Operate in accordance with reference (b).

Information technology services shall only be performed by personnel who are qualified and certified in accordance with reference (d). Personnel proposed and/or used in the performance of this contract as certified personnel shall be limited to those whose specifically assigned duties and responsibilities require certification.

The contractor shall investigate and conduct analysis in order to provide technical reviews to make a recommendation with data supporting the proposal(s) for the need for designation (or not) of the system, network or enclave as platform IT (PIT) or a PIT system in accordance with DoDI 8500.01, Cybersecurity, 14 March 2014. The proposal shall include all technical data required to engage in collaboration with the security control assessor, the authorizing official (staff) and PIT designating official(s). In the event the collaboration results in redesign or follow-up action after collaboration requiring additional or revised documentation, the contractor shall continue to assist the collaboration process.

The contractor shall investigate and conduct analysis in order to provide technical reviews to make a recommendation with data supporting characterization and selection of security controls in accordance with DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014, National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Security and Privacy Controls for Federal Information Systems and Organizations, Revision 4, April 2013, NIST SP 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems, February 2010, Federal Information Processing Standards Publication (FIPS 199, February 2004. Contractor performed analysis shall include; criticality analysis, threat assessment and vulnerability assessments. The contractor shall propose characterization of the system and selection of security controls use Committee on National Security Systems Instruction (CNSSI) 1253, Security Categorization and Control Selection for National Security Systems, 27 March 2014 to tailor the NIST guidance. The proposal shall include all technical data required to engage in collaboration with the security control assessor and the authorizing official (staff). In the event the collaboration results in redesign or follow-up action after collaboration requiring additional or revised documentation, the contractor shall continue to assist the collaboration process.

The contractor shall investigate and conduct analysis in order to provide technical reviews to make a recommendation with data supporting the development of the Security Plan. Contractor performed analysis shall include; criticality analysis, threat assessment and vulnerability assessments. The security Plan shall be prepared for the first program/project decision point and updated for each subsequent decision point. The proposal shall include all technical data required to engage in collaboration with the security control assessor and the authorizing official (staff). In the event the collaboration results in redesign or follow-up action after collaboration requiring additional or revised documentation, the contractor shall continue to assist the collaboration process.

All Cybersecurity shall be in compliance with the following listed instructions:

Source: IRM Office UPDATED: August 2015 Page 12 No. 11, Revised Fact Sheet National Information Assurance Acquisition Policy, July 2003.

All IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR cybersecurity polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These cybersecurity policies are standard across the Department and ensure cybersecurity compatibility and interoperability.

IT systems and or networks operated by contractors pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated in accordance with the NISPOM.

Approved contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet DoDI 8500.1 Cybersecurity (CS), is subject to validation scanning and must be approved by the NAVAIR site CS Manager prior to connection.

The following specific criteria must be met before the contractor can be connected to any DoD or NAVAIR network in support of this contract. Requirements include:

2.8 Proprietary Data and Computer Software

a. Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party who asserts that such data or software is proprietary. The Contractor is required to obtain a written Proprietary Information Agreement (PIA) with the owner of such proprietary data or software identified in Sections 2.1 and 3.1.4 of this SOW prior to gaining access to such data or software. The agreement shall address, at a minimum, (1) access to, and use of, the proprietary data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains proprietary. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

b. The Contractor agrees to the following:

1. Indoctrinate its personnel who will have access to the data or software as to the restrictions under which access is granted;

2. Not disclose the data or software to another party or other Contractor personnel except as authorized by the Task Order Contracting Officer;

3. Not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with the spirit and intent of this requirement;

4. Not disclose the data or software to any other party, including, but not limited to, joint venture, affiliate, successor, or assign of the Contractor; and

5. Reproduce the restrictive stamp, marking, or legend on each use of the data or software whether in whole or in part.

c. The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the Contractor has access in the performance of this contract that contains proprietary or other restrictive markings.

d. The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this contract to gain access to such proprietary information. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

e. The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.

f. Compliance with this requirement is a material requirement of this contract.

3.0 REQUIREMENTS

3.1 GENERAL SUPPORT REQUIREMENTS. This section provides information pertaining to Government and Contractor requirements and responsibilities including information regarding the level of expertise and resources required by the Government in support of this contract.

3.1.3 On-Site/Off-Site Provisioning.

a. On-Site Contractors. All hardware and software tools referenced in this SOW for Contractors working On-Site will be provided by the Government. The Government will supply office space, office supplies, computer equipment, telephone, and reproduction resources when the Contractor is working On-Site to the extent permitted by the NMCI/NGEN project and Contractor. Clause 5252.242-9515 details allowable costs and restrictions on the direct charging of materials costs.

b. Off-Site Contractors. All hardware and software tools referenced in this SOW for Contractors assigned Off-Site will not be provided by the Government. The Contractor shall furnish compatible Government hardware and software tools, including all software upgrades necessary to match Government capabilities. The Government reserves the right to provide Contractors working Off-Site software tools that are not available commercially. The Contractor shall furnish office space, office supplies, computer equipment, telephone, and reproduction resources for Contractor personnel working Off-Site.

c. RDT&E for Off-Site Contractors. To ensure data integrity for any files transmitted to the government that are produced from Off-site RDT&E IT Lab type locations for which the government does not administer DOD/DON/CIO standards, the Contractor assigned Off site shall adhere to the following best practice standards and contemporary industry standards to ensure that all data is compliant with the security and operational requirements of the Government.

1. The Contractor shall maintain an up to date antivirus protection on every workstation/server used to produce work product for the Government. The antivirus shall be configured for antivirus definition updates daily and a weekly full system scan shall be configured. No freeware antivirus programs shall be permitted. Either MacAfee or Symantec subscriptions are highly preferred.

2. The Contractor shall configure each workstation server to receive operating system critical updates and patches from Microsoft on a weekly basis by configuring the automatic update features from windows update. A manual review of patches before installation is acceptable. All critical updates and patches must be reviewed weekly for each asset used should the Contractor opt not to install patches automatically. The Contractor shall periodically check to ensure patches are being applied without errors.

3. All 3rd party software such as Adobe Pro, Flash and Java must be updated as each patch and version updates are released. Automatic notifications for Java and Flash and other frequently updated software packages are highly encouraged.

4. Assets used to produce work products for the Government shall be used for this explicit purpose only. To minimize the risk of cross platform contamination, the introduction of data from unknown or untrusted sources is explicitly forbidden.

3.1.4 Software Tool List. A comprehensive list of software tools used in this SOW is provided below. The Government reserves the right to change software or software version requirements as necessary. Software tools listed below that are prefaced with an asterisk (*) are proprietary software that contain proprietary information. Access to such tools shall be in accordance with the requirements stipulated in Section 2.8 of this SOW.

a. Adobe Acrobat

b. * Lifeworks

c. Mechanica - Creo Advanced Simulation

d. Mechanica - Creo Parametric

e. MS Office

f. MS Project

g. MSC Nastran Linear/Non Linear including Basic Dynamic Module

h. NX Advanced Simulation

i. NX Product Design Maintenance

j. NX Power Drafting Maintenance

k. MSC Patran

l. BEASY

m. * SLAPGEN/FEMGEN

n. Stress Check

o. Team Center Unified

p. MATLAB

q. Mathcad

3.1.5 WMS / CMPro User Account. The Contractor shall establish an active “Contractor” user type account as required by the Government for both the Naval Air Systems Command, North Island (NAVAIR NI) Configuration Management Professional (CMPro) system and the In-Service Support Workload Management System (ISS-WMS) system or any other system that the Government may transition into for the duration of this contract.

3.1.6 Tasking. All structural analysis tasking requirements will be established by a Government POC. The Contractor shall receive structural analyses tasking with an associated REI-TEI number via either the NAVAIR CMPro system or ISS-WMS system or any other system for which the Government has transitioned into in support of this contract. For all other tasking required by the Government that does not have an associated REI-TEI, a Government POC will be identified to approve the tasking in writing. No tasking shall be initiated without written authorization. The Government POC will inform the Contractor whether a task assigned is for Tactical or Strategic Engineering support.

3.1.7 Estimated Completion Date (ECD). An ECD provided by the Contractor shall assume that all government provided data will be available upon task commencement and that all subsequent Contractor requests for information will be answered in two business days. Delays by the government will result in allowable changes to the initial ECD. The Contractor shall notify the Government POC via email of any ECD changes. All ECD changes shall require Government approval.

3.1.8 Task Prioritization. All task prioritizations will be established by the Government. For instances when a new task assigned has a higher priority over tasks already in-work and the established ECDs for these tasks are going to be affected to accommodate the shift in task priorities, the Contractor shall identify the tasks affected and propose ECD changes to these tasks to the Government for consideration and approval. It is the Contractor’s responsibility to ensure that changes to the ECD for all tasks already in-work shall be kept to a minimum.

3.1.9 The Contractor shall have 3 days to finalize a report for a completed analysis.

3.1.10 The Contractor shall have 3 days to provide an estimated start date for all tasks that are in queue.

3.1.11 REI Structural Analysis Tracker. The Contractor shall provide a secure web portal as a means of tracking all tasks assigned by the Government. The tracking system shall include a list of all tasks assigned and shall be used as a management tool by all stakeholders for the purpose of monitoring tasks in progress and as a source of historical information for the duration of the contract. (CDRL A00A)

a. The REI Structural Analysis Tracker shall provide the data fields listed below (as a minimum) and shall have the ability to filter the information provided for data mining purposes.

1. Task Number

2. Aircraft BUNO Number

3. Associated 3R, REI or TEI Number

4. Associated Part Number (P/N)

5. Part Nomenclature

6. Planned MH (initial MH estimate and confirmed by Government POC to complete task)

7. Actual MH (current cumulative MH charged to a task In-Progress and updated daily)

8. Estimated Completion Date (ECD)

9. Status (In-Planning, In-Progress, Paused (include Pause Date/s), Navy Review, Closed)

10. Task Start Date

11. Task Completion Date or Task Delivery Date (corresponds to Navy Review Date)

12. Task Closeout Date

13. Government POC

14. Contractor Lead Analyst assigned

15. Revision (include Revision Date/s)

16. General Comments

b. The Contractor shall participate in a weekly conference call with the Government POC to discuss all tasks that are in-work in the REI Structural Analysis Tracker.

c. Task Number Data Field. The Contractor shall hyperlink the Task Number data field to a copy of the task definition.

d. Actual MH Data Field. The Contractor shall hyperlink the Actual MH data field to a spreadsheet that shall provide a detailed breakdown of MH charged to the task that is updated weekly.

e. Task Closeout Date Data Field. The Contractor shall hyperlink the Task Closeout Date data field to Government authorization approval email.

3.1.12 Structural Analysis Deliverables. The Contractor shall provide all deliverables to the Government by uploading a copy of the files using the system for which the tasking was assigned. All final deliverables including associated models and result files shall meet the requirements established in Section 3.2. All technical documents shall be prepared per reference Section 2.1 (k) and (l) and shall be in the form of one single stand-alone document in electronic adobe acrobat format. All supplemental data files applicable to the analyses shall be included as an attachment to the final deliverable. All final deliverables shall include a listing of all associated files pertinent to the task.

3.1.13 Travel. The Contractor shall travel as required in support of this effort and shall be approved by the Contractor Officer Representative (COR) prior to commencement of travel. The Contractor shall adhere to the Joint Travel Regulations (JTR) travel requirements. The Contractor shall submit a detailed travel report to the COR and copy the cognizant Government Project Lead (CDRL A003). The travel report for each trip taken shall address destination, dates, meeting overview, attendees, key personnel, and any action items assigned.

3.1.14 Technical Meetings. The Contractor shall participate in meetings, program reviews, in-process reviews, Maintenance Requirements Review (MRR) meetings, Technical Coordination Meetings (TCM), Preliminary Design Review (PDR) meetings, Critical Design Review (CDR) meetings, or other technical coordination meetings as required. The Contractor shall provide support in technical reviews, briefings, presentations and provide technical recommendations as required. The Contractor shall use Adobe Acrobat and Microsoft Office software tools as applicable to assist with preparation of technical documents and briefing materials including project summaries, timeline charts, Gantt charts, WBS, resource estimates, cost estimates, and funding expenditure graphs as required.

3.1.15 Technical Briefs and Reviews. The Contractor shall provide a brief of all deliverables including Man Hour (MH) estimates, Analysis Plans (AP), decision briefs, progress review briefs, all Structural Analysis Technical Deliverables including all associated files to complete the task as required by the Government. Technical reviews of all deliverables shall be coordinated and performed by a designated independent Government reviewer. (CDRL A001)

3.1.16 Communications. The Contractor shall control the quality and accuracy of all products in accordance with Government-mandated format, content, and timeliness for all data products. All deliverables whether draft or final, shall be documented via letter of transmittal, signed by both the Contractor Project Leader and the COR.

3.1.17 Other Direct Costs (ODC) are based on a per annum not-to-exceed amount. Approval shall be obtained from the COR prior to the purchase of any material or travel expenses. All materials purchased by the Contractor under this item are the property of the Federal Government. Costs associated with travel and lodging shall be reimbursed in accordance with the JTR. The number and types of trips, including the number of personnel traveling, shall be limited to the minimum required to accomplish work requirements and shall be coordinated with the Government Project Manager for each individual task and the COR. Other Direct Costs necessary for the performance of this contract shall be reimbursed in accordance with NAVAIR clauses 5252.232-9509, Reimbursement of Travel, Per Diem, and Special Material Costs, and 5252.242-9515, Restriction on the Direct Charging of Material. ODC may include General and Administrative (G&A) expenses, but shall not include profit/fee.